ABEND (AB)

The ABEND parameter sets end-of-job (EOJ) processing based on abnormal conditions that occur during execution. The installation default value is active for the ABEND parameter until the $$DD control cards are processed with an override. All data allocation errors will act on the default ABEND value. When a logic error occurs during an open or close operation or at EOV processing, File-AID traps the error, logs it on the SYSPRINT dataset, and continues processing the next valid control card or volume. Because File-AID logs and ignores DCB abends, the ABEND parameter is used to create an external warning that reflects these problems. ABEND specifies whether or not File-AID abends when I/O errors occur.

The syntax of the ABEND parameter is:

ABEND=[n]

n

Value of 0, 1, 2, 3, or 4. The values are defined as:

0

File-AID completes normal EOJ processing by closing all the files and reflecting the highest return code issued.

1

(Default) When an I/O error is found (resulting in a return code of 12 or higher), File-AID completes normal EOJ processing by closing all files, then initiates a user abend that reflects the condition code in the user code field. This value flushes the job stream and does not produce a dump.

2

File-AID initiates an abend when any nonzero return code is found. The condition code is placed in the user code field. This value flushes the job stream and does not produce a dump.

3

When an I/O error is found, File-AID terminates all processing and produces a dump of user code 12. All subsequent $$DDxx control cards are not processed.

4

When the number of data checks specified in the ERRS parameter is surpassed, File-AID terminates all processing and produces a dump of user code 12. All subsequent $$DDxx control cards are not processed.

Example:

This example causes File-AID to abend if any nonzero return code is generated during execution.