Recovering IMS indoubt units of work that need to be rolled back
When units of recovery between IMS and Db2 are indoubt at restart time, Db2 and IMS sometimes handle the indoubt units of recovery differently. When this situation happens, you might need to roll back the changes.
Symptoms
The following messages are issued after a Db2 restart:
DSNM005I IMS/TM RESOLVE INDOUBT PROTOCOL PROBLEM WITH SUBSYSTEM xxxx DFS3602I xxxx SUBSYSTEM RESOLVE-INDOUBT FAILURE,RC=yyyy
Causes
The reason that these messages are issued is that indoubt units of work exist for a Db2-IMS application, and the way that Db2 and IMS handle these units of work differs.
At restart time, Db2 attempts to resolve any units of work that are indoubt. Db2 might commit some units and roll back others. Db2 records the actions that it takes for the indoubt units of work. At the next connect time, Db2 verifies that the actions that it took are consistent with the IMS decisions. If the Db2 RECOVER INDOUBT command is issued prior to an IMS attempt to reconnect, Db2 might decide to commit the indoubt units of recovery, whereas IMS might decide to roll back the units of recovery. This inconsistency results in the DSNM005I message being issued. Because Db2 tells IMS to retain the inconsistent entries, the DFS3602I message is issued when the attempt to resolve the indoubt units of recovery ends.
Environment
- The connection between Db2 and IMS remains active.
- Db2 and IMS continue processing.
- No Db2 locks are held.
- No units of work are in an incomplete state.
Resolving the problem
- Enter the IMS command /DISPLAY OASN SUBSYS DB2 to display the IMS list of units of recovery that need to be resolved. This command generates the list of OASNs in a decimal format, not in a hexadecimal format.
- Issue the IMS command /CHANGE SUBSYS DB2 RESET to reset all the entries in the list. (No entries are passed to Db2.)
- Use DFSERA10 to print the log records that were recorded at the time of failure and during restart. Look at the X'37', X'56', and X'5501FE' records at reconnect time. Notify IBM® Support about the problem.
- Determine what the inconsistent unit of recovery was doing by examining the log information, and manually make the IMS and Db2 databases consistent.