Abort, Cancel, and Restart Processing - Teradata Tools and Utilities

Teradata® Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

Product
Teradata Tools and Utilities
Release Number
16.20
Published
September 2019
Language
English (United States)
Last Update
2019-10-12
dita:mapPath
dsu1527114222346.ditamap
dita:ditavalPath
dsu1527114222346.ditaval
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

Any time a segment request is active, the CLIv2 Abort function may be used to abort processing. Any time a segment request is not active and before sending the last segment, processing may be cancelled by setting the appropriate Segment-data option and initiating another request (the Request-pointer and Request-length are ignored). The response from such a cancellation will be a Failure parcel.

After the first segment has been successful, segmenting is active even after CLIv2 return codes or Error parcels, so segmenting must either be completed normally, cancelled, receive a Failure parcel, or the session logged off.If the database restarts, any segments that were received will be discarded and the next segment sent will receive a Failure response.

Advanced Applications

Advanced applications can build the request buffers to send a procedure to the Teradata Database. If it becomes necessary to cancel the sending of a procedure, then a Cancel parcel (flavor 7) may be included after a Multi-TSR parcel that sets the flag indicating that this is the last segment.

Using the Procedure

To invoke a previously compiled and saved procedure, an SQL CALL statement is sent to the Database.