Aborting a LOB Request: Example - Call-Level Interface Version 2

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

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Call-Level Interface Version 2
Release Number
20.00
Published
January 2024
Language
English (United States)
Last Update
2024-05-14
dita:mapPath
bmn1691484839905.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
fvz1470444150352
Product Category
Teradata Tools and Utilities

Applications can abort a deferred client-to-server transfer of LOB data or create a UDF request. For example, assume a session has been created and a request transfer of LOB data in deferred mode is initiated. If the application wants to abort the request, the DBCAREA field continuation_code to 'C'. Then set the DBCAREA function code to DBFCRQ and call DBCHCL

DBCHCL

DBCHCL allocates a request buffer and places a PclUCABORT parcel in the message body part of the Request Buffer. DBCHCL places the session and Request Ids in the MTDPCB, sets the function code to MTDPABOT, and calls MTDP.

MTDP

MTDP prepares and sends an Abort Request message to the database, and waits for the Abort Response message. MTDP then returns control to DBCHCL.

DBCHCL

If the return code in the MTDP Control Block is not normal, DBCHCL returns the error message pointed to by the DBCAREA to the application. Otherwise, the buffers allocated to the request are returned to free memory and the RCB is removed from its RCB list and returned to free memory.

If the return code or error flag in the DBCAREA is not normal, the application makes the appropriate changes and then re-submits the DBCAREA to DBCHCL.