ABORT
Purpose
From mainframe-attached systems, aborts the previous request and returns control to the BTEQ prompt.
Not valid from workstation-attached client systems.
Syntax
Note: Before aborting a previous request, first send an interrupt to BTEQ. See “Using the Break Key on z/OS” on page 84 for instructions.
Usage Notes
|
Using the ABORT Command |
Result |
|
While waiting for an outstanding request |
If the ABORT command is specified while BTEQ is running more than one session, BTEQ initiates the abort procedure on the most recent request on all sessions. To continue as if the interrupt had never occurred, use the CONTINUE keyword. BTEQ recovers from the interrupt and continues. |
|
Before a request response is sent back |
If the abort reaches Teradata Database before the response to the original request has been sent: In this case, the ABORT command backs out any changes that the previous request made to the database. |
|
After a request response is sent back |
If the abort reaches Teradata Database after the response to the original request has been sent, the DBS cannot abort the original request since it has already been processed. |
|
To undo the result of the original request, if it was not embedded |
If the original request was not embedded in a transaction, undo the result of the original request by submitting a new request that negates it. For example, if the original request inserted a row, a new request can delete that row. If the original request was embedded in a transaction, undo the results of the original request by submitting a new request consisting of an ABORT command. All requests in the transaction are aborted, including the original request, and the transaction can then be correctly resubmitted. |