Expanded Retention Option › Writing ERO Table Statements › Exceptional Condition Processing

Exceptional Condition Processing

Use the XCOND keyword for reports that contain JCL MSGCLASS data.

Syntax:

XCOND={YES|NO}

With XCOND you can specify whether CA View is to consider SYSOUTs that had exceptional conditions, for example, JCL errors, ABENDS, and so on, for ERO evaluation.

YES

The report is selected even though an exception is present.

NO

The report is bypassed for ERO processing when an exception is present.

You can set the following parameters:

• ERO initialization parameter PXCOND=NO to bypass JCL reports containing exceptional conditions for the entire database.
• ERO table parameter XCOND=NO for any individual table entry to bypass reports with exceptional conditions governed by that entry.

You can further refine conditional selection for ERO processing by creating user-defined exceptional conditions.

Notes:

• For more information about exceptional condition, see Exceptional Condition Checking in the chapter "Introduction."
• The default for XCOND depends on the setting of PXCOND:
  • The default for PXCOND is YES, which in turn sets the default for XCOND to YES.

    To exclude individual reports from ERO processing, set XCOND to NO when PXCOND is set to or defaulted to YES.

  • To include individual reports in ERO processing, set XCOND to YES when PXCOND is set to NO.