Determining the coordinator's commit or abort decision

You can use several methods to ascertain the status of indoubt units of work at other systems.

Procedure

To ascertain the status of indoubt units of work, use one of the following approaches:

  • Use a NetView program. Write a program that analyzes NetView alerts for each involved system, and returns the results through the NetView system.
  • Use an automated z/OS® console to ascertain the status of the indoubt threads at the other involved systems.
  • Begin general-use programming interface information.Use the command DISPLAY THREAD TYPE(INDOUBT) LUWID(luwid).

    If the coordinator Db2 system is started and no Db2 cold start was performed, you can issue a DISPLAY THREAD TYPE(INDOUBT) command. If the decision was to commit, the display thread indoubt report includes the LUWID of the indoubt thread. If the decision was to abort, the thread is not displayed. End general-use programming interface information.

  • Read the recovery log by using DSN1LOGP.

    If the coordinator Db2 cannot be started, DSN1LOGP can determine the commit decision. If the coordinator Db2 performed a cold start (or any type of conditional restart), the system log should contain messages DSNL438I or DSNL439I, which describe the status of the unit of recovery (LUWID).