Example of an autoinstall

Consider the following: a terminal operator has logged on to the system and is being autoinstalled. The CATA transaction is responsible for collecting together the parameters required for the DFHZCQ INSTALL.

The process continues from the point where the DFHZCQ INSTALL is issued from CATA:
  1. A call has been made to cause an installation to occur. DFHZCQ ensures that other related modules are already loaded.
  2. DFHZCQ calls the installation-specific module (given in the parameter block passed to DFHZCQ)
  3. DFHZCQIS performs various checks on the parameters passed by the caller of DFHZCQ.
  4. DFHZCQIS finds a pattern in DFHZCQRT that matches with information given in the parameters.
  5. DFHZCQIS calls DFHTBS with the pattern and parameters.
  6. DFHTBS routes the request to DFHTBSB; it is omitted from further discussions.
  7. DFHTBSB checks that a valid pattern has been passed.
  8. DFHTBSB creates the RRAB which gets attached to the APRD Recovery Manager slot.
  9. DFHTBSB calls the next builder as defined by the pattern.
  10. Each builder (DFHBS*) creates its section of the TCTTE.
  11. DFHTBSB adds an action element to the RRAB giving information about this particular builder.
  12. Steps 9, 10, and 11 are repeated until the pattern is finished.
  13. DFHTBSB tidies up the RRAB and returns.
  14. DFHTBS returns.
  15. If the return code was 'OK', DFHZCQIS returns the address of the hidden TCTTE.
  16. DFHZCQ returns.
  17. The caller continues until DFHSP USER is issued or the task terminates.
  18. DFHAPRDR invokes DFHTBSS with the RRAB indicating phase 1.
  19. DFHTBSS examines the RRAB to determine phase.
  20. Using the action elements created in step 11, DFHTBSS recalls each builder asking for information to be saved on the recovery log.
  21. Each builder (DFHBS*) returns the address of the object built in step 10.
  22. Using these addresses, DFHTBSS builds the recovery record.
  23. DFHTBSS writes the recovery record to the system log.
  24. DFHTBSS saves the stored version for the next phase.
  25. DFHTBSS returns.
  26. Recovery Manager calls all other resource managers that have a part to play in the process; it knows this because there are addresses in the RM slots for this UOW.
  27. DFHTBSS is called for phase 2. It reuses the in-storage version of the recovery record to write to the catalog.
  28. DFHTBSS returns.