The creation/deletion state machine

Figure 1 shows the symmetry between the various builder functions.
Figure 1. Create/delete state diagram
The states shown are as follows: State 1 — TCTTE visible. State 2 — TCTTE hidden and vetoed. State 3 — TCTTEs hidden. State 4 — (Partial) TCTTEs and vetoed. State 5 — Nothing. The builder functions to move between pairs of states are as follows: State 1 to States 2 or 3, UNREADY. States 2 or 3 to State 1, READY. State 3 to State 5, DESTROY. State 5 to State 3, BUILD and CONNECT. State 4 to State 5, DESTROY. State 5 to State 4, BUILD.

The starting point can be either state 5 (installing a TCTTE) or state 1 (deleting a TCTTE). Thus, if several TCTTEs had been successfully built, but the last one resulted in an error, we would end up in state 4. If it were not for the last one, we would have ended up in state 3. So the caller is returned an error response, and issues a DFHSP ROLLBACK. This causes DFHTBSS to call the DESTROY function of the builders for all elements on the audit trail—even for those that were “successfully” built in this atom, or UOW. Thus, an install of a atom can be perceived as one complete unit. During the DESTROY process, if the atom is being rolled-back, the builders call ZGTA QUIESCE and ZGTA DELETE to remove index entries for the new TCTTE. Likewise during the READY process, if a delete is being rolled back, the builders call ZGTA ADD to re-instate index entries for the TCTTE.



dfhs3c00130.html | Timestamp icon Last updated: Monday, 5 June 2017