Example of a reinstall
- CEDA reads the CSD and converts the definition into a builder parameter set (BPS).
- CEDA issues a DFHZCP INSTALL passing the BPS.
- Using the resource type code in the BPS, DFHZCQIS searches the DFHZCQRT table for the associated pattern.
- DFHZCQIS calls DFHTBSB passing the BPS and the pattern.
- DFHTBSB checks the pattern and creates a resource definition recovery action block (RRAB) for the audit trail.
- Using the pattern, DFHTBSB calls the CHECKSET entry point of the associated builder.
- The master builder does a DFHZGTI LOCATE to check whether the TCTTE already exists.
- A TCTTE is found to exist, so the builder issues DFHZCP DELETE passing the address of the old TCTTE.
- When a TCTTE is created, its position within the DFHZCQRT table is saved in the TCTTE. DFHZCQDL uses this value to find the pattern associated with this TCTTE.
- DFHZCQDL calls DFHTBSD passing the object to be deleted and the pattern.
- DFHTBSD extends the audit trail so that information about this delete can be recorded.
- DFHTBSD calls the UNREADY entry of each builder.
- Each builder (DFHBS*) checks whether its part of the TCTTE is being used (and vetoes the UNREADY if it is). It calls ZGTA QUIESCE and ZGTA DELETE to lock and remove the index entries.
- DFHTBSD updates the audit trail for each called builder.
- DFHTBSD returns.
- DFHZCQDL returns.
- The master builder checks the return code (that is, that no builder vetoed the UNREADY).
- The master builder returns.
- DFHTBSB checks the return code and recalls each builder at the BUILD entry point passing the BPS.
- Each builder obtains some storage and copies the parameters from the BPS. It uses ZGTA ADD calls to lock and add index entries
- DFHTBSB tidies up the RRAB and returns.
- DFHZCQIS records the position within DFHZCQRT that enables DFHZCQDL to find the pattern.
- DFHZCQIS Returns.
- CEDA checks the return code and issues DFHSP USER.Note: At this stage there are two TCTTEs: the old one that was UNREADY and the new one.
- CEDA calls: DFHTBSS is entered for the first time (phase 1). The audit trail consists of two parts (A and B). Part A contains the list of builders involved with the UNREADY; part B contains the list of builders that created the new TCTTE.
- CEDA writes a recovery record to the system log for Part A indicating that a delete is about to take place in phase 2.
- CEDA creates a recovery record from Part B which represents the new TCTTE to be built.
- CEDA calls each builder asking for its subcomponent (FLATTEN).
- DFHZQIX returns an address and length.
- CEDA concatenates each subcomponent into the recovery record.
- CEDA writes the recovery record to the system log.
- CEDA returns (end of phase 1).
- CEDA reenter for phase-2 processing.
- CEDA processes Part A, calling the DESTROY entry for each builder.
- Each builder frees its part of the old TCTTE.
- CEDA processes Part B of the audit trail.
- CEDA writes the recovery record to the catalog.
- CEDA calls the READY entry point for each builder on the audit trail.
- Each builder does any tidying up that needs to be done.
- CEDA returns.