The DELETE process

By examining the hierarchy (see Figure 1), you can see that there are certain rules that have to be established. Firstly, check that the TCTTE and its subcomponents are quiesced; that is, there is no activity in progress. Secondly, the top node must not be the first object to be freed. From this, you can derive two basic rules, or functions, that must be supplied by any DFHBS*:
UNREADY
For all nodes associated with the master node. Ensures that no activity is occurring; for example, that a CLSDST is not in progress. It must also achieve exclusive ownership of the object; for example, ZGTA QUIESCE ensures no locates on the given TCTTE succeed and that no other UOWs can install another similarly named object until syncpoint. Further, it initiates the ZGTA DELETE, which does a TMP DELETE to remove the entry.
DESTROY
Lower objects first. See What about the “lower objects first” rule?. Frees the storage that belongs to the node.


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