Aborting a Request - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

If an application must terminated a request prior to its completion, an asynchronous abort can be attempted. To abort a request, an application must perform the following steps:

1 Modify the DBCAREA.

a Set the Function to Abort.

b Set the Input CLIv2 Session Id used to initiate the request.

c Set the Input CLIv2 Request Id to the Output CLIv2 Request Id obtained when the request was initiated.

d Optionally set the following:

  • Message Area Pointer
  • Message Area Length
  • 2 Check the return code from DBCHCL.

     

    Return Code

    Results

    0

    Call DBCHCL to perform a Fetch function (see “Fetching the Response for a Request” on page 58) to await the final status of the original request.

    A failure indication should be returned with a code of “user abort” (3110) if the abort is successful.

    anything else

    Process the return code and DBCAREA message.