Wait-during-delay - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

Wait‑during‑delay is a one byte EBCDIC field that specifies the disposition of a request whose execution is delayed. A delay may be loss of communication with the Teradata Database, a restart of the Database, or the request being delayed within the Database by workload Management, when the Database supports such notification. If such notification is not supported, workload delays will not be aware of the Wait‑during‑delay setting.

 

In this language...

The variable name for Wait‑during‑delay is...

COBOL

DBCAREA‑WAIT‑DURING‑DELAY

PL/I

WAIT_DURING_DELAY

C

wait_during_delay

IBM Assembler

DBODLYW

 

This routine...

Does this for Wait‑during‑delay...

DBCHINI

writes

DBCHCL

reads (CON; RSUP; IWPF; IRQ; CRQ)

 

Wait‑during‑delay is used by...

To...

applications

write

Wait‑during‑delay is initialized by DBCHINI to the default value provided for Wait‑during‑delay in the HSHSPB.

When the value for Wait‑during‑delay is not appropriate for the application, you should perform the following procedure before calling DBCHCL.

1 Set Change Options to 'Y'.

2 Change the value for Wait‑during‑delay as follows.

 

If CLIv2 is to return control to the application...

Then change the value for Wait‑during‑delay to...

after communication with the Teradata Database is restored

Y

as soon as the crash/restart is detected with a Return Code 286

N

The Tell‑if‑delay and Wait‑during‑delay DMCAREA options interact as described in the following table.

 

 

 

Wait‑during‑delay

 

 

 

N

Y

Tell‑if‑delay

N

Invalid

The application is not informed of the delay and waits for the delay to end.

Y

For delays due to loss of communication with or a restart of the Database, the application is informed that Tell‑if‑delay was honored with a final return code 286, and the session will be logged off when the Database becomes available (the request may or may not have executed). For delays by Database workload management, the application receives a response indicating the request was not executed rather than be delayed.

The application is informed that Tell‑if‑delay was honored with a preliminary return code 286, and subsequently receives the response when the delay ends and the request is executed.