DBCHPEC - 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

DBCHPEC sets the global CLI attention flag to indicate that the application has responded to a BREAK interrupt.

DBCHPEC also wakes the process from a wait state (for example, if it is in DBCHWAT or a waiting DBCHCL function).

Using a control-C break/abort and if a break handler is posted (for example, through a signal C call), the application should not post the abort call within the signal handler routine; if DBCHCL is called from the signal handler, erroneous results could occur. To properly handle the break/abort, the application should wait for any pending DBCHCL operation to complete by returning the EM_BREAK return code and then post the Abort function.

Parameters

DBCHPEC (ReturnCode, UserECB)

where the following is true:

The parameter... Is the...
ReturnCode four-byte address of an area allocated by the application program for storage of a four-byte signed integer.
UserECB four-byte address of the area allocated by the application program for use as UserECB.

Usage Notes

After control returns from DBCHPEC, the integer contains a code whose value represents success or failure. A return code of zero indicates success; a non-zero return code indicates failure, and the value specifies the reason for the failure.