Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Old code in JES Exit 6
34 views
Skip to first unread message
Tom Wasik
Feb 15, 2016, 11:56:34 AM2/15/16
to
In z/OS 2.1 JES2 implemented back to back converter/interpreter as an option. This calls the interpreter to process "right side of the equal sign" during the conversion phase of processing instead of waiting until the job is selected for execution. This has a number of benefits:
- JCL errors are detected earlier
- OUTPUT statements for the JESDS data sets (or DEFAULT and MERGE OUTPUT statements) can be processed even when there is a JCL error
- It actually performs a bit better
But to make this happen, the converter and interpreter code needed to capable of running outside the JES2 address space. When outside the JES2 address space, there is no access to the PCE (or the HCT and other JES2 private data areas). This required re-organizing a number of data areas so that there could be common structures in both environments.
The result is that there is still a PCE and DTE, but many of the data areas are now in $CIWORK (a private storage area used by the subtask). There is also a parameter list that is passed between the main task and the subtask called $CIPARM. This is how the main task communicates with the stubtask now.
The field you are looking for, JPCEIOT, has been moved to the $CIWORK field CIWIOT. It is also the case that the IOTs are no longer read in by the main task, but by the subtask (in either the JES2 address space or the CI address space). But that does not matter to exit 6. Exit 6 is passed an XPL data area if you want to change to use that. In that the field X006CIW points to the $CIWORK area. If you want to make minimal changes, then you can get the $CIWORK address from DCNVCIW. So a simple code change could be:
L R1,X6DTEADR ADDRESS OF DTE
USING DTE,R1
L R1,DCNVCIW ADDRESS OF CIWORK
USING CIWORK,R1
LTR R1,R1 IS THE CIWORK THERE ?
BZR R3 skip
L R2,CIWIOT GET ADDRESS OF 1ST IOT
That should get you to the IOT.
Hope this helps. And consider doing back to back conversion interpretation. Then the users can set whatever forms they want even if the job has a JCL error.
Tom Wasik
JES2 Development
- JCL errors are detected earlier
- OUTPUT statements for the JESDS data sets (or DEFAULT and MERGE OUTPUT statements) can be processed even when there is a JCL error
- It actually performs a bit better
But to make this happen, the converter and interpreter code needed to capable of running outside the JES2 address space. When outside the JES2 address space, there is no access to the PCE (or the HCT and other JES2 private data areas). This required re-organizing a number of data areas so that there could be common structures in both environments.
The result is that there is still a PCE and DTE, but many of the data areas are now in $CIWORK (a private storage area used by the subtask). There is also a parameter list that is passed between the main task and the subtask called $CIPARM. This is how the main task communicates with the stubtask now.
The field you are looking for, JPCEIOT, has been moved to the $CIWORK field CIWIOT. It is also the case that the IOTs are no longer read in by the main task, but by the subtask (in either the JES2 address space or the CI address space). But that does not matter to exit 6. Exit 6 is passed an XPL data area if you want to change to use that. In that the field X006CIW points to the $CIWORK area. If you want to make minimal changes, then you can get the $CIWORK address from DCNVCIW. So a simple code change could be:
L R1,X6DTEADR ADDRESS OF DTE
USING DTE,R1
L R1,DCNVCIW ADDRESS OF CIWORK
USING CIWORK,R1
LTR R1,R1 IS THE CIWORK THERE ?
BZR R3 skip
L R2,CIWIOT GET ADDRESS OF 1ST IOT
That should get you to the IOT.
Hope this helps. And consider doing back to back conversion interpretation. Then the users can set whatever forms they want even if the job has a JCL error.
Tom Wasik
JES2 Development
Gibney, David Allen,Jr
Feb 15, 2016, 12:47:55 PM2/15/16
to
Thank you. I know I can find it in the doc, but what is the JES2PARM that controls this back to back option?
Tom Wasik
Feb 15, 2016, 1:08:36 PM2/15/16
to
The option that controls this is JOBDEF INTERPRET=. You can set it to JES (so that it is done by JES as part of the conversion phase) or INIT (so that it is done the old way, under the initiator). Note that EXIT 6 is called only when INTERPRET=INIT. With INTERPRET=JES, the converter and interpreter are called in a separate address space and exit 60 is called instead of exit 6 (same parameters, just not in the JES2 address space).
Tom Wasik
JES2 Developement
Tom Wasik
JES2 Developement
0 new messages