>> *I* double-checked with TPTB and, the way things are today, the user >> WILL be revoked for inactivity.
>> It's on the list of things he WANTs to fix, but it's not on the FIXED >> list. And other than setting the password or logging on (with a valid >> password), you aren't going to reset the Last Accessed date. You could >> use the ACCESS command with a fake UCOMDIR NAMES entry but with a VALID >> password in it to change the Last Accessed date. >> -- Chuckie OK - that is fine. Saves me setting up a test and then having to remember to check it in 60+ days. For server machines we found that a 'RAC ALU userid RESUME' will reset the last access date so we have connected them all to a know RACF group (VMDSC) and an authorised server does a weekly resume of everything in that group. (yes, I know there is a risk but some of these can be running uninterrupted for far more than 60 days). I guess we will have do a similar thing for functional userids (although that is, maybe, a little higher risk). Thanks also to Bruce for prompting Chuckie to wake up. Colin Allinson Amadeus Data Processing GmbH
