If you only have JES3 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 JES2 system to be executed on a JES3 system are post-processed by Control‑M using JES2 when the job output returns to the originating node.

The sysout class on the JES3 system must be set to HOLD=TSO.

The automatic held output class that is defined in the HLDCLAS Control‑M installation parameter in the CTMPARM member must be defined to JES so that the three JES‑managed data sets, JOBLOG, JCL statement images, and system messages, will be fully produced and written to a held sysout for all jobs and started tasks monitored by Control‑M.

To specify the held output class, the following JES definition must be made:

OUTCLASS(h)  OUTDISP=(HOLD,HOLD)  /* IS A HELD CLASS   */

             OUTPUT=PRINT         /* PRINT CLASS       */

where h is the sysout class specified in the HLDCLAS parameter in the CTMPARM member.

To produce these files, MSGLEVEL must be set to (1,1) in all jobs monitored by Control‑M, and the following JES definition must be made for each execution class used by Control‑M jobs:

JOBCLASS(x) OUTPUT=YES,MS

GLEVEL=(1,1),LOG=YES

where x is the job execution class that is used by jobs monitored by Control‑M.

For started tasks, the following JES definition must be made:

JOBCLASS(STC) MSGLEVEL=(1,1),LOG=YES,MSGCLASS=h

where h is the sysout class specified in the HLDCLAS parameter in the CTMPARM member.

WARNING: Do not specify CONDPURG=YES in the above JOBCLASS initialization statements. Users who want to purge a job's JES2 system data sets should use the D(elete) option in the SYSOUT or DO SYSOUT Control-M job scheduling parameters. For more information, see the chapter about job production parameters in the Control-M for z/OS User Guide.

If started tasks (STCs) are not scheduled by Control‑M, the sysout class and the MSGLEVEL definition for started tasks have no relevance for Control‑M.

Note: Control‑M allocates a permanent internal reader for submitting jobs. Therefore, it may be necessary to increase the number of internal readers defined within JES2 by increasing the value of the RDINUM parameter in the INTRDR statement in the JES2PARM JES2 member.