Password validation using "in-house" program

[brunfish@newnorth.net]

This would be correct. The pop up window is signing you into the iseries. BUT it has nothing to do with the interactive 5250 at that time. It allows you to run operations navagator,5250. Think of it as logging onto a network and the 5250 an application you want to use on that network. Some sites configure so that the 5250 signon is bypassed. You have to set system value QRMTSIGN to *VERIFY and check the box bypass signon in the configure 5250 sesion at the PC. Then when the user signs on in the popup window they are taken into there first mennu and not another signon.

[mark_reynolds@dart.biz]

We've created our own program to do additional password validation but we're running into problems displaying the error message. We used the sample program from the iSeries Security Reference Manual as a template. Message are sent using the SNDPGMMSG command. The message displays correctly when the user has already established a 5250 session. However, if the user is going through client access and is prompted (by a pop up window) for the userid / password, the message is not displayed. I suspect it is because the 5250 session is not established. Any Thoughts?

[Guest.Visitor]

Yes, the exit program is not called from Client Access, only when you change your password from the 5250 session.