Advanced Topics › Product Activation Considerations › Startup Activities › CA MII Startup Activities

CA MII Startup Activities

CA strongly recommends that GDIF be started before any other products or subsystems that issue GDIF- managed ENQ requests because:

• GDIF propagates all ENQ requests outstanding at startup time, but it cannot eliminate outstanding hardware reserves.
• Neither GDIF nor EDIF can prevent damage from an outstanding integrity exposure.

CA MII can be started as SUB=MSTR. This is the earliest that CA MII can be started. To run with SUB=MSTR, append SUB=MSTR to the START command used to start CA MII. Running with SUB=MSTR has some restrictions:

• The CA MII startup JCL procedure must reside in a PROC library available to MASTER. The MSTJCLxx PARMLIB members or SYS1.LINKLIB members determine which libraries are searched, depending on the IEFJOBS and IEFPDSI DD-cards.
• The startup JCL procedure must not reference any SYSOUT data sets.
• Data sets referenced in the startup JCL procedure must either be cataloged in the master catalog, or must have UNIT= and VOLSER= hard-coded in the startup JCL procedure.
• When running SUB=MSTR, there is no JOBLOG.

CA MIM Early Start Mechanism

CA MII needs to start as early as possible in the z/OS IPL process to ensure integrity of shared resources. The CA MIM Early Start mechanism addresses this issue.

This startup mechanism uses SYS1.PARMLIB to install and activate module MIMESNQX it very early in the IPL process. MIMESNQX internally starts the CAMIMGR address space, and then immediately starts monitoring global resources. All RESERVE and SYSTEMS ENQ requests are suspended until the CAMIMGR address space is fully initialized.

Set Up the Early Start Mechanism

Important: Set up this mechanism only if you are starting the Global Data Integrity Facility (GDIF).

To set up the Early Start mechanism, edit the following members of the SYS1.PARMLIB data set:

• IEALPAxx

  Add the following statement to add the MIMESNQX module to LPA:

  INCLUDE LIBRARY(mimloadlibrary) VOLUME(xxxxxx) MODULES(MIMESNQX) 
  

• PROGxx

  Add the following statement to activate MIMESNQX:

  EXIT ADD EXITNAME(ISGNQXIT) MODNAME(MIMESNQX) STATE(ACTIVE) FIRST 
  

• IEASYSxx

  If new members were created for IEALPAxx and PROGxx, add the member specifications to the PROG and MLPA parameters.

The following are SYS1.PROCLIB requirements:

• The PROC that starts CA MII GDIF must be named ‘CAMIMGR’, and must reside in the SYS1.PROCLIB concatenation.
• All data set references in the CAMIMGR PROC must be cataloged in the master catalog, or the CAMIMGR PROC must contain UNIT and VOLSER information.
• The CAMIMGR PROC must specify PGM=MIMDRBGN, not MIMASCRE.
• The address space is started as a permanent system address space.
• The address space is started SUB=MSTR and therefore there has no JOBLOG.

Important! If the CAMIMGR address space fails to initialize for any reason, such as a parameter error in the MIMINIT member, the IPL will not complete, because one or more system address spaces will be suspended by MIMESNQX. Attempts to start CAMIMGR manually after correcting the error on another system will also fail, because MIMESNQX has special handling for the ASID created through ASCRE. The only option will be to restart the IPL process from the beginning.