Resetting the status of an indoubt thread

After manual recovery of an indoubt thread, allow the systems to resynchronize automatically. Automatic resynchronization resets the status of the indoubt thread. However, you might need to take additional steps if heuristic damage or a protocol error occurs.

Procedure

To delete indoubt thread information for a thread whose reset status is set to YES:

Issue the RESET INDOUBT command.

Db2 maintains this information until normal automatic recovery. You can purge information about threads where Db2 is either the coordinator or participant. If the thread is an allied thread that is connected to IMS or CICS®, the command applies only to coordinator information about downstream participants. Information that is purged does not appear in the next display thread report and is erased from the Db2 logs.

Examples

Begin general-use programming interface information.

Resetting indoubt threads with IP address and resync port number

For example, assume that you issue a DISPLAY THREAD command with TYPE(INDOUBT), and the output includes the following DSNV406I message:

DSNV406I -DB2C INDOUBT THREADS -                 
COORDINATOR          STATUS      RESET URID                 AUTHID
FFFF:10.97.217.50.   COMMITTED-H YES   0000000056765A422C57 PAULMCW
.1332

You can issue the following command to reset the indoubt unit of work by specifying the IP address (FFFF:10.97.217.50) and the resync port number of the coordinator (1332) from the message:

RESET INDOUBT IPADDR(::FFFF:10.97.217.50..1332)

Resetting indoubt threads with LUWIDs or tokens

Assume that you need to purge information about two indoubt threads. The first has an LUWID of DB2NET.LUNSITE0.A11A7D7B2057.0002, and the second has a token of 442. You can use the following command to purge the information:

-RESET INDOUBT LUWID(DB2NET.LUNSITE0.A11A7D7B2057.0002,442)

End general-use programming interface information.