BTEQ Return Codes - Basic Teradata Query

BTEQ's return code is the value it returns to the client operating system when its execution is complete. The value of the return code indicates the completion status of the job or task as follows:

The value of BTEQ's default return code is determined by the most severe error code BTEQ receives back from the Teradata Database over the course of time it is executing input instructions. BTEQ assigns a default severity value to each error code (as shown in the following tables) for return codes of 0, 4, 8 and 12. If, for example, an SQL request results in database error 3737, "Name is longer than 30 characters", BTEQ will minimally use 4 as its return code upon exit unless a difference value is explicitly used on the EXIT command.

BTEQ exposes the return code's current value prior to exit through the ERRORLEVEL status value keyword. That keyword can be used in IF and ELSEIF command conditions to make it easier to determine an appropriate course of action based on hitting a particular severity level rather than having to explicitly test for multiple specific error codes.

There is also an ERRORLEVEL command which can be used to change the severities mapped to database error codes, and add additional levels of error severity. Any Teradata Database message not contained in the following tables is mapped to an 8 severity value, unless the ERRORLEVEL command is used to override that default. See the ERRORLEVEL command, as described in the following subsection.

The default severity mapped to a 2631 error is 0. For more details, see Usage Notes for the RETRY command.

To support detection of the more egregious compiler error results, the default severity map includes associations to cover the common warning codes for compiling objects and their execution. These mappings will only be in effect when the ERRORONDBSWARNING command setting is ON.