Resolving indoubt units of work using DB2 restart-light
CICS supports the enhanced DB2 restart-light capability provided in DB2 Version 8.
Restart-light mode is intended for a cross-system restart in the event of an MVS™ system failure, where the CICS systems are configured to use group attach (see Using the DB2 group attach facility). In DB2 Version 7, the DB2 restart-light capability allowed a DB2 data-sharing member to restart with a minimal storage footprint, free retained locks, and then terminate normally. However, this only applied to in-flight units of work, and not indoubt units of work. For DB2 Version 8, this capability was extended to encompass indoubt units of work. This enables a CICS system to connect to a DB2 restart-light subsystem for the purpose of resynchronizing indoubt units of work. This capability is especially useful because DB2 does not support peer recovery; that is, one DB2 subsystem cannot resynchronize indoubt units of work on behalf of another DB2 subsystem.
In a typical scenario, if an MVS LPAR fails, a cross-system restart can be initiated which involves restarting the failed CICS systems on another LPAR, and bringing up the failed DB2 subsystem on that LPAR in restart-light mode. Assume that the CICS systems have been configured to use group attach, with RESYNCMEMBER(YES) and STANDBYMODE(RECONNECT) on the DB2CONN definition, and there are indoubt units of work outstanding in DB2. The DB2 restart-light subsystem initializes, frees retained locks for any in-flight UOWs, and then awaits resynchronization with CICS for the indoubt UOWs. Each CICS system initializes, and detects whether it has outstanding units of work and whether RESYNCMEMBER(YES) has been specified. Where both these conditions are true, the CICS system ignores group attach and reconnects back to the last DB2 subsystem, which is the DB2 restart-light subsystem. The indoubt UOWs are now resynchronized, but no new transactions are allowed to access DB2. When all the indoubt UOWs have been resolved in the DB2 restart-light subsystem, it terminates. Because the CICS systems are defined with STANDBYMODE(RECONNECT), when the DB2 restart-light subsystem terminates, they drop into standby mode and attempt a reconnection to DB2. Now, because all the indoubt units of work have been resolved, RESYNCMEMBER does not apply and group attach can be used. The CICS systems will reconnect to a normal, active DB2 subsystem.