Wait Across Delay - Call-Level Interface Version 2

Wait Across Delay

Usage Notes

The Wait Across Delay field specifies how CLI should handle a request that it is unable to initialize or complete because the database computer has crashed and is being restarted.

If a restart occurs during a logoff request, CLI automatically resubmits the request.

Language	Variable Name
COBOL:	DBCAREA-WAIT-ACROSS-DELAY
C: DBCAREA.H:	wait_across_delay

Routine	Action Taken
DBCHINI:	writes
DBCHCL:	reads (CON; RSUP: IRQ; FET; REW; ERQ; ABT)

Used by	Action Taken
application program	writes

Wait Across Delay is initialized by DBCHINI to the default value in the site’s SPB.

If the value provided is not appropriate for the application, before calling DBCHCL, the application program may set:

Change Options to Y, and

Wait Across Delay to:

Y, if CLI is to return control to the application program after the Teradata Database restart completes.

N, if CLI is to return control to the application program as soon as the database computer crash/restart is detected.

The Fetch, Rewind, End Request, and Abort functions read and use the value of Wait Across Delay, but do not store it.

APRC and Wait Across Delay

With AP Reset Containment (APRC), the change in nomenclature (from Crash to Delay) is a more accurate designation of this variable. To prevent the need for users having to make changes to their applications, the actual field name in the structure/record definition supplied remains as Wait Across Crash.

Used with Tell About Delay

The combination of Wait Across Delay set to N and Tell About Delay set to N is not allowed.

If Wait Across Delay and Tell About Delay are both set to Y, an intermediate return code of 220 is returned when communication is lost with the Teradata server. If the request is still pending, the response’s final status will be returned after communication is restored.