The ABORT command is used as both a Teradata SQL statement and an ITEQ command. It is interpreted as an ITEQ command if it is entered while the status area indicates “COMMAND IN PROCESS.”
To abort an operation that is in process on MVS/TSO:
To abort an operation that is in process on VM/SP CMS:
Processing is interrupted as indicated by the message “ITEQ ATTENTION HANDLING” in the display area.
While processing is interrupted, the following actions may be taken:
Execution of the ABORT command has much the same effect as entering the Teradata SQL ROLLBACK (ABORT) statement. That is, it aborts the current transaction and rolls back any affects it may have had on the database. However, the Teradata SQL ROLLBACK statement is used within a macro or a transaction that is processed by a language preprocessor to abort a transaction unconditionally in response to an error condition. The ABORT command, by contrast, is used interactively -- and may not be executed in time to stop a transaction. (Refer to item 3 in the dialogue described in Tables 4-4 and 4-5 of the Interactive Teradata Query User Guide [B035-2452].)
If the statement aborted by the ABORT command is a data definition or data manipulation statement, any change made to the database is backed out. For a Teradata SQL SELECT statement, any result is deleted. Locks on the database that were initiated by the aborted statement are released. (For information on lock types and modes, refer to “Concurrency Control” in Database Administration.)
The simplest way to execute the ABORT command is to press a PF key assigned to the command via a startup string (see the Interactive Teradata Query User Guide [B035-2452] for more information).