Examples of synchronization points
In Figure 1, task A is a nonconversational
(or pseudoconversational) task with one UOW, and task B is a multiple UOW
task (typically a conversational task in which each UOW accepts new data from
the user). The figure shows how UOWs end at syncpoints. During the task, the
application program can issue syncpoints explicitly, and, at the end, CICS® issues
a syncpoint.
Figure 1. Units of work and syncpoints

Figure 2 shows that database changes made by a task are not committed until a syncpoint is executed. If task processing is interrupted because of a failure of any kind, changes made within the abending UOW are automatically backed out.
If there is a system failure at time X:
- The change(s) made in task A have been committed and are therefore not backed out.
- In task B, the changes shown as Mod 1 and Mod 2 have been committed, but the change shown as Mod 3 is not committed and is backed out.
- All the changes made in task C are backed out.
Figure 2. Backout of units of work
