After calling DBCHINI, set the delay options as follows.
Given this combination of options, a delay can be handled as follows:
- The application calls DBCHCL for some function
- The delay occurs before or after receiving information from DBCHCL
- CLIv2 returns control to the application, with a return code of 286
- The application takes action appropriate to the application
Before submitting a request, save a copy of the request in case it must be resubmitted. If a transaction spans several requests, save a copy of each request in the transaction in case the transaction must be resubmitted.
CLIv2 logs the session off when it encounters the delay. CLIv2 sends the logoff request to the Teradata Database when communication is re-established.