If you only have JES2 at your site, skip this step.
Note: By default, Control‑M does not support sites that use both JES2 and JES3. However, you can set the MULJESPP post-processing parameter in the CTMPARM member to Y. In such a case, jobs sent, using NJE, from a JES3 system to be executed on a JES2 system are post-processed by Control‑M using JES3 when the job output returns to the originating node.
If you want to use NJE to route jobs to other nodes, add DEFCLASS=NO to the NJERMT JES3 initialization statement.
If you are using the recommended method (see the next topic), jobs returning from JES2 must be set to HOLD=EXTWTR.
Set up the Control‑M working method. Two methods of running the Control‑M monitor and Tape Pull list utility under JES3 are provided:
The disadvantage of this method is that neither the TSO OUTPUT command nor option 3.8 under ISPF permits viewing of sysouts defined to JES3 as HOLD=EXWTR. Therefore, this method can only be used by users of products that are capable of reading the output using a technique other than TSO OUTPUT or ISPF 3.8. Use the following sample JES3 sysout definition in the JES3 initialization deck INISHDECK:
SYSOUT,CLASS=h,TYPE=(PRINT...),HOLD=EXTWTR,...
where h is the value of the HLDCLAS parameter in the CTMPARM member.
Using this method, Control‑M and the Tape Pull list utility can handle sysouts defined to JES3 as HOLD=TSO, and the TSO OUTPUT command or ISPF option 3.8 functions as usual.
Parent Topic |