After calling DBCHINI, set the crash/delay options as follows:
Given this combination, the steps if a Teradata Database crash/delay occurs are:
1 The application program calls DBCHCL for some function.
2 The system crashes or an AP resets before or after receiving information from DBCHCL.
3 The application program is not notified of crash or reset and does not gain control.
4 The database system restarts or an AP reset completes.
5 The application program regains control from CLI with a return code of EM_OK (0).
6 When the application program calls DBCHCL for the Fetch function, it obtains
7 The application program takes action appropriate to the application.
Before submitting a request, save a copy of the request in case it must be re-submitted. If a transaction spans several requests, save a copy of each request in the transaction in case the transaction must be re-submitted.
If a restart occurs during a logoff request, CLI automatically resubmits the request.
Note: The setting of Wait For Response has no effect on the processing shown above.