Recovery functions
If CICS® is indoubt about a unit of work because of a communication failure, it can either suspend commitment of updated resources, or decide to commit or back out local resources.
How you can influence which of these two actions CICS takes is described in The indoubt attributes of the transaction definition.
- Suspend commitment of updated resources until the systems are next in communication. The unit of work is shunted. When communication is restored, the decision to commit or back out is obtained from the coordinator system; the unit of work is unshunted, and the updates are committed or backed out on the local system in a process called resynchronization.
- Take a unilateral decision to commit or back out local resources. In this case, the decision may be inconsistent with other systems; at the restoration of communications, the decisions are compared and CICS warns of any inconsistency between neighboring systems (see Messages that report CICS recovery actions).
There is a trade-off between the two functions: the suspension of indoubt UOWs causes updated data to be locked against subsequent access; this disadvantage has to be weighed against the possibility of corruption of the consistency of data, which could result from taking unilateral decisions. When unilateral decisions are taken, there might be application-dependent processes, such as reconciliation jobs, that can restore consistency, but there is no general method that can be provided by CICS.