MAXERROR Command | Basic Teradata Query - MAXERROR (ME) - Basic Teradata Query

Basic Teradata® Query Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Basic Teradata Query
Release Number
20.00
Published
October 2023
ft:locale
en-US
ft:lastEdition
2025-04-02
dita:mapPath
gxl1691484661681.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
psp1479308573013
Product Category
Teradata Tools and Utilities

Purpose

This control enables users to specify a maximum error severity level beyond which BTEQ terminates job processing.

Syntax



Shorthand Syntax (Interactive Mode Only)
Command Shorthand
MAXERROR ME

where the following is true:

n
The error severity level at which BTEQ terminates.

Usage Notes

If a BTEQ script contains an 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.

The DEFAULTS command does not affect MAXERROR setting.

The MAXERROR command is valid in an SQL macro.