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
This diagram shows the elapsed time, as two lines, for task A and task B. In each case, the ends of the line indicate the start and end of the tasks and, in each case, end-of-task also shows a syncpoint. However, the whole of task A from start to finish represents only one UOW, and the end-of-task syncpoint is the only one. The line for Task B, on the other hand, is much longer than task A and is divided into a number of separate UOWs, with the task taking a syncpoint at three intervals in addition to the end-of-task syncpoint.

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
This diagram shows the elapsed time, as three horizontal lines, for tasks A, B, and C, showing that each task modifies some recoverable resources. Tasks A and C do not take explicit syncpoints and rely on the implicit syncpoint taken by CICS at end-of-task. Task B comprises four separate UOWs, with each UOW performing updates, indicated as Mod1 through Mod4. Before tasks B and C can complete, there is a system failure (represented by a vertical line that cuts through tasks B and C). Task A completes before the system failure, therefore the syncpoint is taken and the updates are committed. In task B the system failure occurs during UOW 3, and in task C the failure occurs after both updates but before the end-of-task syncpoint. The recovery for tasks B and C is as indicated in the text.


dfht2c0035.html | Timestamp icon Last updated: Sunday, 4 June 2017