Craig Otway wrote:
I need some RACF help. I have a large group of users that I would like for
their passwords to expire before the currently set date of ever 105 days(I know
that is a long time, but please don't go down that road). I do not want to
force everyone, just this group I can identify. I want them to be able to
change the password like they usually do every 106th day, without having to
call the help desk.
What if I run a job with this group of userid's as follows:
PASSWORD USER(MRPC021) INTERVAL(3)
Then on day 5(prevent some from doing this twice and catch those who were out), I will run the same job with the following change:
PASSWORD USER(MRPC021) INTERVAL
If I leave off the interval(day) it should default back to the master setting of 105, RIGHT??
Will interval by itself, change from 3 days, back to the SETROPTS global
setting of 105?
That should all work nicely in your intended way. Notice that RACF
ignores the INTERVAL parameter if specified incorrectly. Thus, if
nothing happens, you've done something wrong :-)
--
Ulrich Boche
SVA GmbH, Germany
IBM Premier Business Partner
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
