Checking Both Code Sources - 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

There are times when both client and database sources must be checked.

For example, on a call to DBCHCL for the Fetch function, a return code of zero indicates that the client software has set a pointer to information in the response buffer. But not until the information is examined does the application program know what the database “has to say.” The return code may be zero and the parcel successfully pointed to may be a Failure parcel.