I've been having a weird error for some users calling CHKPWD from a CLP
after we changed to LVL 2 for PWDLVL. Some users work fine for example
with all lower case and #'s (didn't try mixed case with them). Another
user fails unless the pwd is set to all caps. The user that fails
unless all caps was *YES for lvl 0 or 1 and lvl 2 or 3 before the change
just like most of the other users.
I'm wondering could it be because of the CHKPWD cmd needing a ptf (the
system and I assume the cmd is at 5.4) or something of that nature. I
don't have access to the CL code, but I know from the job log that it
getting hung on the CHKPWD cmd. I think the way that the cmd works is
that it encrypts the supplied pwd and checks it against the already
encrypted as400 pwd and then just returns a 0 or 1 so I can't see that
the CLP could be affecting it.
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact