Checking Both Code Sources - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
16.20
Published
September 2019
Language
English (United States)
Last Update
2019-10-12
dita:mapPath
uny1527114222311.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

There are times when both client and the Teradata 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 Teradata Database “has to say.” The return code may be zero and the parcel successfully pointed to may be a Failure parcel.