Scenario: Recovering from communication failure

A communication failure can cause an indoubt thread.

Symptoms

A communication failure occurred between Seattle (SEA) and Los Angeles (LA) after the database access thread (DBAT) at LA completed phase 1 of commit processing. At SEA, the TSO thread, LUWID=16 and TOKEN=2 B, cannot complete the commit with the DBAT at LA4.

At SEA, NetView® alert A006 is generated, and message DSNL406 is displayed, indicating that an indoubt thread at LA because of a communication failure. At LA, alert A006 is generated, and message DSNL405 is displayed, to indicate that a thread is in an indoubt state because of a communication failure with SEA.

Causes

A communication failure caused the indoubt thread.

Environment

The following figure illustrates the environment for this scenario.

Figure 1. Resolution of indoubt threads. Scenarios for resolving problems with indoubt threads contains a detailed description of the scenario depicted in this figure.
Begin figure description. This figure is a flowchart that depicts threads between four systems that are located at three different locations. End figure description.

At SEA, an IFCID 209 trace record is written. After the alert is generated and the message is displayed, the thread completes the commit, which includes the DBAT at SJ 3. Concurrently, the thread is added to the list of threads for which the SEA Db2 subsystem has an indoubt resolution responsibility. The thread shows up in a DISPLAY THREAD report for indoubt threads. The thread also shows up in a DISPLAY THREAD report for active threads until the application terminates.

The TSO application is informed that the commit succeeded. If the application continues and processes another SQL request, it is rejected with an SQL code to indicate that it must roll back before any more SQL requests can be processed. This is to ensure that the application does not proceed with an assumption based on data that is retrieved from LA, or with the expectation that cursor positioning at LA is still intact.

At LA, an IFCID 209 trace record is written. After the alert is generated and the message displayed, the DBAT 4 is placed in the indoubt state. All locks remain held until resolution occurs. The thread shows up in a DISPLAY THREAD report for indoubt threads.

The Db2 subsystems, at both SEA and LA, periodically attempt to reconnect and automatically resolve the indoubt thread. If the communication failure affects only the session that is being used by the TSO application, and other sessions are available, automatic resolution occurs in a relatively short time. At this time, message DSNL407 is displayed by both Db2 subsystems.

Resolving the problem

Operator response: If message DSNL407 or DSNL415 for the thread that is identified in message DSNL405 is not issued in a reasonable period of time, contact the system programmer. A communication failure is making database resources unavailable.

System programmer response: Determine and correct the cause of the communication failure. When the problem is corrected, automatic resolution of the indoubt thread occurs within a short time. If the failure cannot be corrected for a long time, call the database administrator. The database administrator might want to make a heuristic decision to release the database resources that are held for the indoubt thread.