It was uglier than that. The revoked user is also a production HLQ....So we were unable to create any new datasets with that HLQ!
Jeff Ruegsegger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mautalen Juan Guillermo Sent: Friday, May 26, 2006 10:59 AM To: [email protected] Subject: Re: RACF user id revocation REVOCATION condition is not checked at start time of STCs. So, an STC can start even when the user associated to it (via STARTED class, or ICHRIN03) is REVOKED. That said, dependeing upon what the procedure does, it can face problems afterwards. For instance, if it submits a job to an internal reader, the job will fail (because then the REVOCATION condition of the USER will be checked). Juan G. Mautalen -----Mensaje original----- De: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] En nombre de Matthew Stitt Enviado el: Viernes, 26 de Mayo de 2006 02:48 p.m. Para: [email protected] Asunto: Re: RACF user id revocation Most likely what got you was the "inactive user" auto-revocation time limit. If this STC has been running for continuously longer than that time limit, then you restart it, this may happen. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
