× 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.



Passwords that have been changed within the past 90 days - new users, result
of help desk calls, etc. - won't need an immediate change. The others will.

The good news is that the users aren't disabled, so they can still change
the passwords themselves. So as long as they don't flub the change, the
help desk won't be swamped. Along those lines, you might want to
temporarily up QMAXSIGN to give people extra retries when they inevitably
forget the new password.

One way to ease into it would be to change QPWDEXPITV to 366. Then, all IDs
that haven't been changed in more than a year will expire. A few days
later, drop it to 270, then 180, then 90.

Another option would be to do a WRKUSRPRF *ALL, select a range of users by
placing a 2 next to them, and then put PWDEXPITV(90) on the command line to
change that group. Repeat every few days until you've covered everyone.
Then change the system value. Then change all of the IDs back to *SYSVAL.
This is tedious but if most of your IDs are more than a year old it may be a
little less of a shock.

An initial step to get some passwords changed would be to look for default
passwords using ANZDFTPWD and set those to expired.

It might also be a good idea to take the opportunity to clean up unused
profiles. Use PRTUSRPRF and review the report to see who hasn't changed
their passwords in a long time. Apply your company's policy on profile
retention and disable/delete as appropriate.

On Thu, Jan 29, 2009 at 7:08 PM, Kirk Goins <kgoins@xxxxxxxxxxx> wrote:

OK let's say a system has had the sysval QPWDEXPITV set to *NOMAX for
YEARS and no wants to change it to say 90 days. Assuming the usrprf are
set to *SYSVAL will they all EXPIRE at the next signon or will they
start a 90 day timer? I know there's lots to be careful in doing this,
just can't find a straight answer on how current passwords will be handled.

Thanks

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.