DBCHCL ERQ Function - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-07
dita:mapPath
jen1488824663137.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

Purpose

ERQ (End Request) explicitly closes a request, discard its response, and deallocated internal data structures related to the request.

Usage Notes

  • If Return Code is 0, the ERQ has successfully completed.
  • CLIv2 will keep the response buffer if Save-response-buffer was Y when the request was submitted. This permits CLIv2 to reuse the response buffer for the next Initiate Request without allocating a new one.

DBCAREA Input Fields

Before using the EndRequest function, the application must set the DBCAREA fields in the first table and may optionally set those in the second table depending on the application's requirements.

DBCAREA Input Fields Required for the EndRequest Function
DBCAREA Input Fields Required for the EndRequest Function
Function Input-CLIv2-request-number
Input-CLIv2-connection-number  
DBCAREA Input Fields Optional for the EndRequest Function
DBCAREA Input Fields Optional for the EndRequest Function
Message-area-length Message-area-pointer

DBCAREA Output Fields

Upon completion of the EndRequest function, CLIv2 will always set DBCAREA fields in the first table and will set those in the second table if the function was successful.

DBCAREA Output Fields Always Set for the EndRequest Function
DBCAREA Output Fields Always Set for the EndRequest Function
Message-text Message-length
Message-text-length Return Code
DBCAREA Output Fields Set by Successful EndRequest Functions
DBCAREA Output Fields Set by Successful EndRequest Functions
Open-requests Message-return-code