Successful Run Startup Operation - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
15.00
Language
English (United States)
Last Update
2018-09-25
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

Successful Run Startup Operation

The sequence of operations for a successful run startup operation is:

1 Call DBCHCL for DBFRSUP

2 Check that return code is zero

See “DBFFET” on page 210 for steps to take until response is “consumed” or no longer required (if rewind is required, see “DBFREW” on page 212 and then “DBFFET” on page 210)

3 Call DBCHCL for DBFERQ

4 Check that return code is zero

If the application program calls DBCHCL for the DBFRSUP without first calling DBCHCL for DBFCON, DBCHCL returns with a return code “first do a connect” (NO SESSION 304).

If the call to DBCHCL for the DBFRSUP results in a non-zero return code, the run startup has failed for the reason indicated by the value of the return code. CLI internal structures for the non-existing request can (and should) be de-allocated by calling DBCHCL for DBFERQ. The Output Request Id from the DBFRSUP is the appropriate value to place in Input Request Id for DBFERQ.

The startup request is not to contain a USING clause. Thus, the value of Use Presence Bits is read and stored, but not used.