Resynchronization
If a failure occurs between returning from the exit after performing phase 1 of a 2-phase commit and the subsequent phase 2 or back out call, the resource manager must be ready, on restart, to discover the state of the unit of recovery, and to act accordingly.
For programming information about restart resynchronization by using the EXEC CICS RESYNC command, see RESYNC ENTRYNAME.
If CICS® is indoubt about a unit of work, it sends the exit program a request to wait (UERTWAIT). When the status of the indoubt UOW is resolved, CICS initiates a resynchronization task, to inform the exit program of the outcome of the unit of work.
Information about indoubt units of work is retained across both warm and cold starts of CICS. CICS initialization and keypoint management routines recover from the system log all information associating resource managers with outstanding units of recovery, which are resolved automatically when CICS reconnects to the resource managers concerned.