Thanks to all for suggestions.
It appears the copy of QDSIGNON2 we were using was somehow not quite right.
Reverting to the QSYS copy worked fine (our QINTER was pointing to one in
QUSRSYS). Although the sources for both appeared to match, there must have
been something awry when the QUSRSYS version was compiled.
I still cannot see any valid reason that two identical user profiles would
behave differently on the same sign on file on the same workstation session
and with the same passwords, but I guess at this point it is not a
problem.
Thanks again!

----------------------------------------
From: ALopez@xxxxxxxxxx
Sent: Wednesday, November 24, 2010 10:04 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Login Issues at QPWDLVL 2 for some users

All run in QINTER and all are getting the QDSIGNON2 -- I can tell
because

the password is 128 long on that screen.

In which case you'll have to fish. Possibilities:

- Is it possible someone has the DDS for QDISGNON2 (or the copy you use)
altered to upper case the password?
- Is it possible that someone modified the password levels during testing?
The sysval change doesn't take effect until the next IPL. Some changes
(moving to 3 then back to 2) blow away the weaker encryption of the
passwords.
- Is is possible that some users have a version of Client Access so old
that it doesn't support QPWDLVL 2?

If all else fails, I'd find a PC that isn't working and try repeatedly as
you alter the password to be all upper case and less than 11 characters,
alter the password to contain lower case/special characters, but still
less
than 11 characters and try again, etc.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.