This control enables users to specify a maximum error severity level beyond which BTEQ terminates job processing.
where the following is true:
- The error severity level at which BTEQ terminates.
If a BTEQ script contains a Teradata SQL statement that produces an error severity level greater than the designated MAXERROR value, BTEQ immediately aborts. Therefore, to have BTEQ exit on an error severity level of 8, set MaxErrorLevel to 7.
If MAXERROR has not been specified, the automatic termination feature is disabled and the BTEQ job continues to execute until BTEQ encounters one of the following conditions:
- End-of-file for the primary command input file
- A QUIT command
- A fatal error
- When BTEQ receives an I/O abend, system error messages appear in the z/OS JES job log.
- When BTEQ receives an I/O error or an abend, the IBM/C runtime library produces an LSCX message that might contain more information about the error.