Starting Your Product › How to Configure Without CA CSM › Step 12: (Optional) Exceptional Condition Checking

Step 12: (Optional) Exceptional Condition Checking

Perform this step if you want the product to check for exceptional conditions; otherwise go to the next step.

Upgrade Considerations

For more information about upgrading and information that applies to this step, see the chapter Migration Information.

General Considerations for All Users

CA View records job-end condition codes and stores them with the SYSOUT. Certain CA View features (such as the Expanded Retention Option and the XPRINT initialization parameters) use these condition codes to determine processing. The product provides the following system default exceptional condition specifications:

• Non-zero condition code
• Data set not deleted
• Data set not cataloged
• Data set not recataloged
• Data set not uncataloged
• JCL error
• Operator cancel in allocation recovery
• System ABEND
• User ABEND
• User defined character strings

If these defaults are not correct for your system, proceed with this step; otherwise go to the next step.

Creating Exceptional Condition Statements

The product allows you to create exceptional condition statements.

Note: For more information about exceptional condition, see Exceptional Condition Checking in the chapter "Archival" in the Reference Guide.

The DD statement SARXCTAB in your SARSTC startup JCL and SARFSS JCL points to the file that contains your exceptional condition code checking statements.

Note: To save the information for a later step, be sure to enter the name of your exceptional condition statements data set next to the SARXCTAB ddname on your Archival Started Task Worksheet.