Introduction › Processing and Features › Exceptional Condition Checking

Exceptional Condition Checking

Using CA View, production JCL listings and messages can be automatically archived and retained for as long as you want. You can optionally specify the action to take whenever an exceptional condition is encountered; actions include issuing a message to the operator and printing the SYSOUT for the job.

CA View checks for the following exceptional conditions:

• Nonzero condition code
• System or user abend
• JCL error
• Data set cataloging error
• Data set not deleted error
• Allocation request canceled by operator
• User-specified condition

The conditions can be modified as needed by using control statement inputs to the CA View started task (SARSTC).