I didn't see any other replies to this question. What I understand and have always coded for is this:
1. JES2 (re)initializes all JCTUSER fields for each new 'job' (J, S, or T) and thereafter leaves them alone for the life of that job 2. The fields are initialized to X'00' In practice, when I'm not sure what 'unset' means, I often code this way: CLI FIELD,X'40' Any value set? BNH NOTSET N: bypass value processing This code works whether 'unset' means blanks or binary zeroes. . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] IBM Mainframe Discussion List <[email protected]> wrote on 02/21/2006 06:53:33 AM: > I need an information: does JES2 initialise the JCT user fields JCTUSER0 > through JCTUSERF prior to the initial call to the JOB-card-scan exit > (exit 2), whether for a batch job, an STC or a TSO logon, or are those > 64 bytes left uninitialised by JES2 and must they therefore be initialised by > exit 2 upon initial entry for a new job? > > If initialised by JES2, what are they initialised to: binary zeroes, > blanks, other? ---------------------------------------------------------------------- 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
