Re: JES2 EXIT 52 - JCTCLASS
FROM JES2 INSTALL EXITS DOC: (section 63.4, z/OS 1.7) " Module HASPINJR invokes installation Exit 52 for initial JOB statement images. Input service has obtained and initialized the job control table (JCT) and the IOT before calling installation Exit 52. After performing the processing you coded in Exit 2, input services complete scanning the JOB statement and allocate spool space for the job." It's clearly states the JCT has been "initialized"hmmm, initialized to what is the question. I read that to mean that it was populated with appropriate values based on field descriptions in the JCT. Silly me. Thanks again to everyone for their feedback. -- 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
Re: JES2 EXIT 52 - JCTCLASS
>PS: JES2 discussions probably belong on JES2-L, rather than IBM-MAIN. See http://listserv.vt.edu/cgi-bin/wa?SUBED1=jes2-l&A=1 1. Why - if JES2 isn't mainframe related, what is? 2. JES2-L is moribund! - Too busy driving to stop for gas! -- 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
Re: JES2 EXIT 52 - JCTCLASS
Regarding Q2: Probably the easiest way to look at JES2 control blocks, and to trace exit logic, is to get a copy of z/XDC from www.colesoft.com. The cost is pretty small when you figure out how much time it saves! The other approach is to use the $TRACE facility. I have a trivial general purpose trace format routine that is defined for trace ids (240-255). It just uses a $CALL to TRCPUT to put out a general title line, and then a call to TRCDUMP to generate a hex dump of the trace entry header, and another call to TRCDUMP to dump the actual data of interest. The trace header includes things like the name from the $TRACE macro, so you can use the header information to figure out what you are looking at. The entire formatting routine is about 20 lines of code. It is then a simple matter to add $TRACE macros at the start of my exit routines so I can see exactly what is being passed to the exit. I usually use a unique trace id per exit routine, to make it easy to just get the data that I am interested in. PS: JES2 discussions probably belong on JES2-L, rather than IBM-MAIN. See http://listserv.vt.edu/cgi-bin/wa?SUBED1=jes2-l&A=1 /jack - Original Message - From: "Dooley, Robert" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: Sent: Friday, July 25, 2008 2:05 PM Subject: JES2 EXIT 52 - JCTCLASS Q1: I have tried, unsuccessfully, to interrogate the JCTCLASS field in EXIT 52. Should JCTCLASS (or JCTJCLAS) be available in EXIT 52? Q2: Sort of related to Q1. Please excuse my JES2 naïveté, albeit how do I dump a control block? I have reviewed $TRACE and it is not obvious to me how to accomplish such an obvious request. I have reviewed some of the source in SHASSRC that shows how IBM is doing it for the $XPL when using $TRACEDEF...etc to create $TRCFIL. However I have to believe that there is an easier way to do this. Thank you for any assistance and guidance you may have to offer. -- 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
Re: JES2 EXIT 52 - JCTCLASS
At exit 52 time, the job card parameters have not been processed yet. That is why these fields contain the reader default class. Maybe exit 53 or exit 50 would be better places for whatever logic you want to implement based on the final job class. "Dooley, Robert" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Thank you for your reply. > > I did find out that JCTCLASS and JCTJCLAS and JMRCLASS all contain the > letter "A" no matter what job class I use when submitting. Based on the > verbage in the JES2 EXITS manual about the JCT being available it just seems > a bit odd that it wouldnt' be populated with the information from the job card. > > Any-hoo, I plan on using the RCARDSCN interface to retrieve the CLASS > parameter. Ya I could tip-toe through the STMT buffer but that seems so old > school. > > :-) > > -- > 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
Re: JES2 EXIT 52 - JCTCLASS
Thank you for your reply. I did find out that JCTCLASS and JCTJCLAS and JMRCLASS all contain the letter "A" no matter what job class I use when submitting. Based on the verbage in the JES2 EXITS manual about the JCT being available it just seems a bit odd that it wouldnt' be populated with the information from the job card. Any-hoo, I plan on using the RCARDSCN interface to retrieve the CLASS parameter. Ya I could tip-toe through the STMT buffer but that seems so old school. :-) -- 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
Re: JES2 EXIT 52 - JCTCLASS
Dooley, Robert wrote: Q1: I have tried, unsuccessfully, to interrogate the JCTCLASS field in EXIT 52. Should JCTCLASS (or JCTJCLAS) be available in EXIT 52? Since a perfectly valid thing for Exit 52 to do is to change CLASS=x on the job card, I would say no. Q2: Sort of related to Q1. Please excuse my JES2 naïveté, albeit how do I dump a control block? I have reviewed $TRACE and it is not obvious to me how to accomplish such an obvious request. I have reviewed some of the source in SHASSRC that shows how IBM is doing it for the $XPL when using $TRACEDEF...etc to create $TRCFIL. However I have to believe that there is an easier way to do this. I find IF SLIP traps and IPCS sufficient to my needs. Bob -- 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
