Use - 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.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
ggf1488824663364.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

The following table lists the common routines and describes how they are used.

Uses of Routines and Functions 
Routine Description
DBCHINI What: Initializes the application program allocated by DBCAREA and allocates and initializes internal CLI memory areas.
Why: To prepare for interaction with the Teradata Database
Where: All clients
DBCHCL What: Manages interaction with the Teradata Database. Each type of interaction is called a function.
Why: To send Teradata SQL requests to, and receive Teradata SQL from, the Teradata Database
Where: All clients
Function Use
DBFCON Logs a session on to the Teradata Database and specifies a set of services.
DBFCRQ Sends LOB data in deferred mode
DBFRSUP Submits a request to execute the Startup Request stored in the Teradata Database
DBFIRQ Submits a Teradata SQL request from the application
DBFABT Aborts a request asynchronously
DBFFET Makes available the next parcel or buffer (which one depends on the setting of Parcel Mode) of the Teradata SQL response
DBFREW Repositions to start of Teradata SQL response (spool file)
DBFERQ Closes a Teradata SQL request and has the Teradata Database discard the response
DBFDSC Logs off and deletes a session from the Teradata Database
DBCHCLN What: Releases the internal CLI memory areas that were allocated by DBCHINI
Why: To clean up after interacting with the database computer
Where: All clients