Processing address space architecture and configuration

The address space architecture when IMS Database Recovery Facility is running with all the integrated auxiliary utilities active is described here.

Shown here is a comprehensive view of integrated auxiliary utility processing with address spaces shown.

Following is a list of the address spaces shown in the diagram. The associated configuration parameters are also described. The arrows leading from the RAUX box in the master address space illustrate this task as the central point of control of integrated auxiliary utility processing throughout all the address spaces participating in the recovery.

Master Address Space (MAS)

Created when the JCL for the job is submitted.

Recovery Sort Subordinate (RSS) Address Space (and multiples)

• Created by the MAS for restoring image copies and recovering database data sets.
• The procedure for this address space is given by the DRFPROC parameter.

  The name of the started task is prefixed with the contents of the ASPREF keyword.

• Subtasks related to IMS High Performance Image Copy, IMS High Performance Pointer Checker and DEDB Pointer Checker are active in the RSS when the IC or PC keywords are present on the ADD command.

FS-UAS

• Created by the MAS when the IMS Index Builder integrated auxiliary utility is requested by using the IB() keyword on the ADD command or in UTILGBL control statement parameter BLD_SECONDARY.
• The procedure for this address space is given by the DRFIAX control statement.

  The name of the started task is prefixed with the contents of the FSPREF keyword.

• The FS-UAS is created after all RSS address spaces have completed.

PR-UAS

• The PR-UAS is created by the MAS when the DFSPREC0 integrated auxiliary utility is requested via the HALDB keyword on the UTILGBL control statement or in the IB() keyword of the ADD command.
• The procedure for this address space is given by the DRFIAX control statement.

  The name of the started task is prefixed with the contents of the PRPREF keyword.

• This address space is created after all RSS address spaces have completed, but before recovery is ended.
• A new PR-UAS is started for each HALDB partition for which a PHIDAM primary index or ILDS data set rebuild is required, but only one is active at any given time.

IB-UAS

• Created by the MAS when the IMS Index Builder integrated auxiliary utility is requested by using the IB() keyword on the ADD command or in UTILGBL control statement parameters BLD_PRIMARY or BLD_SECONDARY.
• This is also known as the IMS Index Builder master address space because IMS Index Builder is started as a subtask in this address space.
• The procedure for this address space is given by the DRFIAX control statement.

  The name of the started task is prefixed with the contents of the IBPREF keyword.

• The IB-UAS is created after all RSS address spaces have completed.
• If the version of IMS Index Builder is 3.1, all the indexes are built here in the IB-UAS.

  However, one or more IBSS address spaces may be started for the purpose of running Image Copy and Pointer Checker for the rebuilt indexes.

• The first time you run IMS Index Builder, the client should first do this as a native batch job to ensure its procedures and parameters are installed correctly.

  It should be able to build indexes for IMS Database Recovery Facility restored databases.

  This test ensures that IMS Index Builder successfully runs as an integrated auxiliary utility.

• IMS Database Recovery Facility will not prevent you from both recovering and rebuilding an index in the same one-step recovery job.

  However this results in redundant processing and should be avoided.

IMS Index Builder Sort Subordinate (IBSS) Address Space (and multiples):

• The IBSS is created by the IB-UAS.
• The JCL procedure used to start the IBSS depends on the installed version of IMS Index Builder.

  In IMS Index Builder, the procedure used is always IIUBSRT and the started task names are IIUAPIFC and IIUSORTS.

  The procedure name and started task name can be overridden by using IIURPRMS module SIIULMOD.

• Subtasks for IMS High Performance Image Copy and IMS High Performance Pointer Checker may be active in the IBSS when image copy and pointer checker processing has been requested for the rebuilt indexes.
• The subordinate address spaces are built for the purpose of running IMS High Performance Image Copy and IMS High Performance Pointer Checker when requested by IMS Database Recovery Facility.

  The indexes are built in the IB-UAS (IMS Index Builder Master Address Space).

PC-UAS

• The PC-UAS, which runs the IMS High Performance Pointer Checker DMB Analyzer, is created by the MAS when the IMS High Performance Pointer Checker integrated auxiliary utility is requested for full-function databases via the PC keyword on the ADD command.
• The procedure for this address space is given by the PCPROCNM keyword and the stared task name is given by the PCJOBNM keyword. The PCPREF() control statement sets the prefix for the name of the PC-UAS started task.

IMS Library Integrity Utilities (LIU)

Although it is depicted separately in the diagram, IMS Library Integrity Utilities does not run in a separate address space. It is run in the MAS when the LIU@GOPT(xxxx) control statement is coded.

As a technique for correlating all the address spaces for a recovery, code the same three characters as the first part of the four character prefix for ASPREF, FSPREF, IBPREF, PCPREF, PRPREF and PCJOBNM.

For example: ASPREF(DR3S), FSPREF(DR3F), IBPREF(DR3I), PCPREF(DR3D), PRPREF(DR3P) and PCJOBNM(DR3C).

Also the job name for the MAS JCL should begin with these same three characters. This will make it easier to find the job output for the related address spaces.