Job monitoring

You can monitor a job through:
  • Elapsed time (time since the job started)
  • Processor time (actual time spent executing instructions)
  • Output
    • Lines and cards produced
    • Pages produced
    • Number of bytes of output produced.

Use the ESTIME statement to cause JES2 to write a message to the operator when a job exceeds the elapsed time specified by the JOBPARM statement, and an additional message at each interval specified by the INT= parameter on this same statement. You can use the IEFUTL installation exit routine to enforce these values, if the IEFUJV installation exit routine places the time in the SMF user ID field. See z/OS MVS Installation Exits for information about these exits.

The JCL EXEC statement, the JOB statement, and the converter parameters on the JOBCLASS(v) statement allow you to specify the maximum execution time for a job. If a job exceeds this value, the system enters an IEFUTL installation exit routine, which can cancel the job or allow it to continue (after writing a warning to the job submitter). See z/OS MVS Installation Exits for information about this exit.

Use the ESTLNCT, ESTPAGE, ESTPUN, and ESTBYTE JES2 initialization statements to specify the total number of printed lines, printed pages, punched cards, and SYSOUT bytes that a job can produce before JES2 takes action. The OPT= parameter specifies the action JES2 should take. You can allow the job to continue after writing a message to the operator or cancel the job with or without a dump.

Even if a previous step ends with a completion code of 722 (output limit exceeded), the MVS™ scheduler selects (and begins executing) the next step if COND=EVEN or COND=ONLY appears on the EXEC statement. This step does not end immediately with ABEND722 for producing excessive line, page, or byte SYSOUT but ends when the job exceeds the next excess output interval (that is, NUM= specification plus INT= specification for the specific ESTLNCT, ESTPAGE, or ESTBYTE initialization statement).

Use JES2 Exit 9 to control job output overflow. See z/OS JES2 Installation Exits for information about this exit.

Your installation can specify SMF output limiting by class, with the JOBCLASS JES2 initialization statements. SMF can monitor the output (OUTLIM= on DD statement) for each data set.