Re: Language problem when a password expires

On 03-Jun-2016 16:00 -0500, Denis Robitaille wrote:

We have a situation here for which I am out of ideas.

We are an international company and have both French and English
speaking users. They work on the same LPAR and this is a requirement
(just trust me on this).

Currently, when the user logon, an initial program adjust the system
part of the library list so that the QSYS and QSYSxxxx libraries are
put in the correct order and so making sure that everything appear
in the appropriate language for each user.

Here is our problem.

When a password has expired, on the following login, you are
automatically prompted to change it. The language in which this is
presented to the user depends of the order of libraries in the
system part of the library list. But the request to change the
password occurs before the user initial program can run so all users
are presented with the request in the same language regardless.

Any suggestions?

As noted\understood, the Initial Program (INLPGM) is too late to establish the System Library List (SYSLIBL) for the system-presented Password-Expired\Change-Password panels.

As Marc alluded, the Routing Program (PGM) specified on the Add Routing Entry (ADDRTGE) for the Subsystem Description (SBSD) may be early enough to effect the required Change System Library List (CHGSYSLIBL) request. If not, then the devices would need to be allocated to the subsystem established with the appropriate language library; see the Subsystem Library (SYSLIBLE) parameter of the Create Subsystem Description (CRTSBSD) or Change Subsystem Description (CHGSBSD) commands in combination with the Add Workstation Entry (ADDWSE) command [and with any /device selection/ override capabilities that may exist].

FWiW: Another option is to prevent the system-presented panel from being presented, by intercepting the condition of password-expired, by instituting a change-password effect *prior to* the actual expiration. One way to do that would be to extend the Password Expiration Interval (PWDEXPITV and\or QPWDEXPITV) by several days for each user, and then present the Change Password (CHGPWD) in a signon that same number of [several] days in advance of the actual expiration-date. Noting of course, that in some situations the condition could not be resolved in that fashion; e.g. users returning from vacations that might span those several days, would still have those users encountering the system-presented prompting vs being presented with your coded prompting.