Changing the Value for 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
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-07
dita:mapPath
jen1488824663137.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

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-delayWait-during-delay
  N Y
Tell-if-delay N Invalid The application is not informed of the delay and waits for the delay to end.
Tell-if-delay 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.