It's not the API that's doing it. The actual culprit is the Client Access ODBC driver, it's just that the logon screen my program displays looks an awful lot like the one CA shows.
Turns out it was a misconfiguration in iSeries Navigator on the affected PCs, and the users somehow managed to get into it and incorrectly change the logon defaults. Needless to say, the users have no idea how it got changed...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.