Why is the listed XCODE always the last exception code in the job?

Document ID : KB000023024
Last Modified Date : 14/02/2018
Show Technical Document Details


Why does the View Selection List XCODE field show the last exception code in the job?


The parameters FIRST, LAST, and HIGH are provided to specify whether the exception code for the first, last or highest exception condition for the SYSOUT group should be retained in the group control record. The FIRST, LAST, and HIGH keywords are mutually exclusive. LAST is the system default.

If you want the First exception code to be the one that is listed, add a global entry to the Exception Code Table (SARXCTAB) as follows:

   /* FIRST

If you want to display JCL errors, use the HIGH parameter:

   /* HIGH

CA View looks at the JES data sets for messages.

The three JES data sets are archived in the following order:

  1. The messages log (JESMSGLG)
  2. The JCL (JESJCL)
  3. The system messages (JESYSMSG)


The default exception code processing is LAST. The JCL error message (IEF453I) appears in the JESMSGLG.

The condition code message (IEF142I) appears in the JESYSMSG, which would be the LAST exception code.

To see the JCL error, a global entry should be in the Exception Code Table (SARXCTAB) as follows:

   /* HIGH