ROLLBACK
What happens when an error occurs during the installation process? An example of this would be when one TCTTE within a group is still in service when a CEDA COPY command is being processed for the group with the REPLACE option specified. Example of a reinstall shows such a replace operation. The builders for the existing TCTTE are called (UNREADY) in order to check that the DELETE (FREEMAIN) can proceed. Thus, the audit trail refers to all called builders.
If the “total vote” from all the UNREADY builder calls indicates OK, the build proceeds for the new TCTTE that is to replace the existing one. Thus, at the end of the process, the audit trail consists of a list of references to builders associated with the old TCTTE, and a list of references to builders for the new TCTTE (lists A and B).
Consider the case when the group contains definitions for three TCTTEs, and a VETO occurs for the last one. This means that there is an audit trail for A1, B1, A2, B2 for which there was success, and list A3 for the unsuccessful UNREADY for the third TCTTE.
The failure condition is returned to the caller (CEDA), which then issues a DFHSP ROLLBACK.
Recovery Manager invokes DFHAPRDR which in turn invokes the DFHTBSS module, with a parameter that indicates a rollback is required. Thus, the “A” lists are processed, and all the READY entry points of the builders are called. Then the “B” lists are processed, and the DESTROY builder entry is called to free the storage obtained for the supposedly new TCTTEs.
To summarize, the rollback operation for UNREADY is READY, and the one for BUILD is DESTROY.