HX
Purpose
From mainframe-attached systems, the HX (Halt eXecution) command aborts the previous request and any transaction in which the request was embedded, logs off the current set of sessions, and exits from BTEQ. (The HX command is not valid from workstation-attached client systems.)
Syntax
Usage Notes
Before halting execution, BTEQ must first be interrupted. See “Using the Break Key on z/OS” on page 84 for instructions.
The results depend on the timing of the abort request:
|
Abort Request |
Results |
|
When the abort request reaches the Teradata Database before the response to the original request has been sent. |
A failure message is received because the abort causes the original request to fail. |
|
|
The response to the original request is discarded, and any transaction in which the original request was embedded is aborted. |
|
|
In this case, the abort operation backs out any changes that the previous request made to the database. |
|
When the abort request reaches the 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. |
|
|
If the original request was embedded in a transaction, the entire transaction is aborted and any effect that the statements in the transaction had on the database are backed out. |
|
|
In either case, the current set of sessions is logged off, and the user exits from BTEQ. |