Exception processing

While processing JES data sets during output capture, Output Manager automatically looks for the following conditions, in the order shown:
  1. JCL errors
  2. Abends
  3. Non-zero return codes

More specifically, Output Manager parses the JES data sets to look for the following messages:

IEF452I - JCL error.

IEF453I - JCL error.

IEFC452I - JCL error.

IEF450I - Abend.

IEF142I - Step completion code.

Output Manager records information for the first JCL error that is encountered (if any) in the Output Manager archive table.

If the condition code from IEF142I is zero, Output Manager does not indicate an exception.

If a job has a non-zero condition code but neither abends nor creates a JCL error, Output Manager records either the last non-zero condition code or the highest condition code, depending on how you set the configuration parameter CONDITION_CODE. Only one exception is recorded in the archive table for a JES data set.

Tip: This automatic processing can be augmented with Output Manager TPL (Text Processing Language) rules. For example, if a particular string in a sysout indicates an error, but the job completes successfully, you could create a TPL rule to post a WTO to trigger automation based on that error message.