× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I am a non-sysadmin (P/A) on a v5r3 system.

I would like to know if there is any impact from changing QPWDLVL (Password
level) from 0 to 2. As a reference:
0 = User profile passwords with a length of 1-10 characters are supported.
2 = User profile passwords with a length of 1-128 characters are
supported.

Also, according to the security reference, when using QPWDLVL=0, the rules
for specifying passwords are the same as those used for user profile names.
Because our network passwords are required to use special characters, it
would be nice if I could use the same password for the network and our
AS/400s. But I find that I am unable to use most special characters on my
AS/400 password.

So, if I make a suggestion to the sysadmins to change the QPWDLVL to 2, I
would like to be able to tell them that there is no impact for doing so.
I.e., users will not have to change their existing passwords, and the other
password-related system values still apply, and when users passwords expire,
they will be able to enter any password they would otherwise have been able
to when QPWDLVL=0. The *only* difference is that users *may* begin using
special characters in their passwords.

Hmmm, users would also need to remember that the passwords would be
case-sensitive. But they need to do that now with their network passwords,
so that shouldn't be a big issue.

Am I on the right track with this thinking?

TIA,
Dan

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.