Jobs or started tasks monitored by Control‑M should have the three system data files known as JESYSMSG, JESJCL, and JESMSGLG, fully produced. Started tasks should be in the sysout class defined in the HLDCLAS parameter in member CTMPARM.

The JESYSMSG, JESJCL, and JESMSGLG files are known as SYSDATA in the IOA environment.

Use the following sample JES3 definition to define the default MSGLEVEL for batch jobs, and MSGCLASS and default MSGLEVEL for started tasks:

CIPARM PARM=...ef...,PARMID=n

where the e and f options in the options list should be set to 1, which is also the default setting in JES3.

• For batch jobs, set the MSGLEVEL parameter to (1,1) in the JCL JOB statement, or in the JES initialization parameter, as follows:

  STANDARDS INPTMID=n

  where n is the PARMID of the CIPARM statement.

• For started tasks, set the JES initialization parameter:

  STANDARDS STCPMID=n

  where n is the PARMID of the CIPARM statement.

  The h option in the CIPARM statement (referred to by STCPMID=n) should be set to the same MSGCLASS as the HLDCLAS parameter, as described in Step 2.1 – Control-M operational parameters. All the sysdata output of the started tasks will be routed to the Control‑M HLDCLAS.

  If started tasks (STCs) are not scheduled by Control‑M, the definition for started tasks has no relevance for Control‑M.

• For TSUs, set the JES initialization parameter:

  STANDARDS TSOPMID=n

  where n is the PARMID of the CIPARM statement.

  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 JES3 by increasing the value of the INTRDR parameter in the OPTIONS statement in the JES3 member JES3INxx.