DSNL411E COLD START CONNECTION BY COORDINATOR location ACCEPTED. INDOUBT THREADS NEED MANUAL RESOLUTION. INFORMATION RECORDED IN TRACE RECORD WITH IFCID=204 AND IFCID SEQUENCE NUMBER=seq-no

Explanation

Db2 has participant responsibility for indoubt threads. The coordinator informed Db2 that it performed a cold start operation and lost all knowledge of indoubt threads. The indoubt threads at this Db2 must be manually resolved with the RECOVER INDOUBT command.

location
This field contains one of the following:
  • The requester's relational database name (location name)
  • The requester's VTAM® LU name (<luname>)
  • The requester's IP address
seq-no
The IFCID sequence number associated with the trace record. The sequence number is printed in hexadecimal format. If the sequence number is zero, then IFCID 204 was not active or it was active with a destination of the resident trace table only. IFCID 204 is a member of statistics class 4, which has a default destination of SMF.

This condition can falsely occur if the DDF communications database (CDB) contains definitions that allow a subsystem to remotely access itself through SNA. To avoid this false condition, remove self-referencing CDB definitions.

System action

The connection with the partner is accepted. Alert A001 is generated. A trace record whose IFCID=204 is written.

System programmer response

Call the database administrator.

Database Administrator Action: Db2 is a participant with one or more indoubt threads where the coordinator is 'location'. The DBMS at 'location' performed a cold start. The Db2 participant assumes that the coordinator recovery log was lost or damaged and indoubt thread resolution cannot be achieved. There is probably inconsistent data at the coordinator. A list of indoubt threads involving the coordinator 'location' can be displayed using the DISPLAY THREAD command for indoubt type threads by including the LOCATION('location') parameter in the command.

The heuristic decision (that is, to commit or abort the logical unit of work) should be coordinated with any other participants. The existence of other participants might not be easy to determine. The information might be available in the coordinators recovery log even though the coordinator performed a cold start. If the coordinator is a Db2, then it might be possible to execute the DSN1LOGP utility to produce a summary report. If this is possible, the following information might be produced:
  • The LUWID of the thread.
  • The NID used by IMS or CICS® to identify the thread.
  • The name of all participants.
  • The name of an upstream coordinator if the coordinator is also a participant. This could happen when an application requester accesses a Db2 AS using application-directed access, which in turn accesses another Db2 server with system-directed access. (The local Db2 might be the third system in this scenario.)

At this Db2 participant, all indoubt threads coordinated by the cold starting location must be resolved with the RECOVER INDOUBT command. Locked data remains unavailable until resolution. Threads that were already resolved with this command are discarded. Threads not yet resolved are discarded after resolution with the command.

The commit or abort decision provided using the RECOVER INDOUBT command for a logical unit of work are propagated to all downstream participants, if any.