Aborting a Request - Teradata Tools and Utilities

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

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Tools and Utilities
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2023-11-17
dita:mapPath
oxw1641281447623.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
vfj1470443597526
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.
    1. Set the Function to Abort.
    2. Set the Input CLIv2 Session Id used to initiate the request.
    3. Set the Input-CLIv2-request-number to the Output-CLIv2-request-number obtained when the request was initiated.
    4. 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) 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.