>Peter Hunkeler wrote: >>A job's JES2 joblog starts with a date message and (presuming RACF) message >>IRR010I. For example: >>10.37.42 J0012345 ---- TUESDAY, 01 MARCH 2016 ---- >>10.37.42 J0012345 IRR010I USERID JOHNDOE IS ASSIGNED TO THIS JOB. >>Next messages are RACF's last access message (ICH70001I) and JES2's >>handover-to-the-initiator message ($HASP373).
>>I'd be interested to understand *when* the first two messages are written, >>i.e. what can I conclude from their timestamps? In what phase of JES >>processing are they written? >>I assume the internal reader does not parse the JOB statement (nor any JCL >>other statement), so it does not know if there is a USER= keyword for this >>job. Therefore JES2 Conversion would be the first process able to call RACF >>(well, SAF) and pass it the userid from the USER= parameter or the userid >>inherited from the submitter. The result being documentes as IRR010I. AFAIK - at the execution node. (I have to look at a job running on other system just to be sure. ;-D ) Walter Farrell wrote: >The message comes from RACROUTE REQUEST=VERIFYX, and I think JES2 invokes that >service during READER processing. Very true. In fact these messages are written AFTER the ACEE of that job has been established in the job's address space. It means that the USER=<submitter> (and password) or the job's token as well as the SURROGAT and NODES classes, if applicable, have all been processed at that stage. And no, I don't know what JES2 exit has been called or not at that stage. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
