Continuing a Teradata SQL Request - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-04-19
dita:mapPath
xen1544831946512.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

When an ElicitData, ElicitFile, or ElicitName response parcel is fetched, the database requires additional information to complete the request. To provide that information, CLI performs the following steps:

  1. Modifies the DBCAREA.
    1. Set the Function to 15 (ContinueRequest).
    2. Set the Input CLI Session Id to the Output CLI Request Id returned when the session was established.
    3. Set the Input CLI Request Id to the Output CLI Request Id returned when the request was initiated.
    4. Set the Request Pointer field.
    5. Set the Request Length field.
    6. Optionally set the following fields:
      • Fetch Buffer Length field
      • Message Area Pointer field
      • Message Area Length field
    7. Optionally set the Change Options option to 'Y', and set the following:
      • C2S Conversion option
      • Locate Mode option
      • Maximum Parcel option
  2. Calls DBCHCL to perform the ContinueRequest function.
  3. Checks the return code from DBCHCL.
    Return Code Result
    0 Calls DBCHCL to perform a Fetch function to get the final status of the rewind and the first part of the response. For more information, see Fetching the Response.
    anything else Processes the return code and DBCAREA message.
  4. Calls DBCHCL to perform the End Request function. For more information, see Ending a Request.