On Tue, 8 Mar 2016 15:20:03 +0100, Peter Hunkeler <p...@gmx.ch> wrote:
>Cross-Posted to IBM-Main and JES2-L lists > > >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). > > > > >The above mentioned messages 1 & 2 document when the job was submitted, >messages ICH70001I and especially $HASP373 document when the job was selected >by an initiator, i.e. when execution began. > > >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. > > >Reader or Conversion processing could write the date message, since that is >independent of any JCL or JECL statement content. The message comes from RACROUTE REQUEST=VERIFYX, and I think JES2 invokes that service during READER processing. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
