Previous Topic: Modes of OperationNext Topic: Disclaimer


Error Handling

When error conditions occur during a Reporting Facility run, it is likely that one of the following basic problems is responsible:

The Reporting Facility documents each error as it occurs and provides tools for solving complicated problems. When errors occur, see the CA Datacom/DB Message Reference Guide for solutions.

The functions that the Reporting Facility performs while processing a request are compilation and execution. The input commands are processed sequentially and compiled. Then, when it is possible to continue, the system performs the processes it was instructed to execute. During compilation, the Reporting Facility generates diagnostic messages as a result of comprehensive syntax and lexical analysis performed on the input source statements.

In most cases, the Reporting Facility discovers and prints an error message at the point in the program where it occurs. However, more complex error conditions may not be discovered until the entire source statement, or even the entire source program, has been analyzed. In this situation, the message may not print next to the error.

A complete summary of the total number of errors or warnings issued prints at the end of the compilation phase. Even if OPTION LIST OFF is specified, all compiler diagnostic messages print.

After the compilation phase is completed and free of errors, the execution phase can begin. If an abend occurs during the execution phase, a message prints and the run terminates.

In some circumstances, the Reporting Facility can correct an error and continue processing. For example, if a numeric field does not contain valid numeric data, a program check interruption and an abend normally occurs. However, the Reporting Facility can fix the numeric field and continue processing.