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 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.