Starting Your Product › Configure Your Product › Required Manual Configuration › Set Up the CA MIM Early Start Mechanism

Set Up the CA MIM Early Start Mechanism

When running CA MII Global Data Integrity Facility (GDIF), we recommend using the CA MIM Early Start Mechanism.

If CA MII synchronization does not occur early in the IPL process, unconverted reserves, deadly embraces, or integrity exposures can occur. Use the CA MIM Early Start mechanism to prevent these issues.

The Early Start Mechanism uses SYS1.PARMLIB to install and execute the module MIMESNQX early in the IPL process. MIMESNQX internally starts the CAMIMGR address space to start monitoring global resources. All RESERVE and SYSTEMS ENQ requests are suspended until the CAMIMGR address space is fully initialized.

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.

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

IEALPAxx

To add the MIMESNQX module to LPA, add the following statement to the member:

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

PROGxx

To execute MIMESNQX, add the following statement:

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

IEASYSxx

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

Review the following requirements:

• The PROC that starts CA MII GDIF must be named CAMIMGR, and must reside in a proclib allocated by MSTJCL.
• 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. All data sets must be PDSs and not PDSEs.
• The CAMIMGR PROC must specify PGM=MIMDRBGN, (MIMDRRM when using Restart Manager), not MIMASCRE.
• The CA MIM address space is started with SUB=MSTR. The startup messages are present in the MIMLOG before JES starts.
• The startup JCL procedure must not reference any SYSOUT data sets.
• The address space is started as a permanent system address space.

When using the CA MIM Early Start Mechanism, consider the following restriction:

• The Early Start Mechanism can be implemented one system at a time.