Case 3: Just Tell - 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.10
Published
October 2021
Language
English (United States)
Last Update
2021-11-02
dita:mapPath
ttt1608578409164.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities
After calling DBCHINI, set the crash/delay options as follows:
  • Tell About Crash (or Tell About Delay) to Y
  • Wait Across Crash (or Wait Across Delay) to N
Given this combination of options, a database crash or AP reset can be handled as follows:
  1. The application program calls DBCHCL for some function.
  2. The Database crashes or an AP resets before or after receiving information from DBCHCL.
  3. CLI returns control to the application program, with return code of EM_DBC_CRASH_B or EM_DBC_CRASH_A.
  4. The application program takes action appropriate to the application.

Before submitting a request, save a copy of the request in case it must be re-submitted. If a transaction spans several requests, save a copy of each request in the transaction in case the transaction must be re-submitted.

Tell and wait may be useful to terminal-oriented applications to distinguish excessive response time from the unlikely, but possible, database crash, or AP reset.

The application program may set Wait Across Crash to 'Y' and proceed as in Tell and Wait.