Stopping MIM from starting up at IPL

Products

• MIM Resource Sharing (MIM)
• MIM Data Sharing (MII)

Issue/Introduction

You would like to perform a partial IPL on a system, and do not want MIM to come up at all.

The preference is for MIM to not come up at all, versus having it come up at IPL and then shutting it down.

You are trying to understand how MIM (CAMIMGR) gets started during the IPL process.

Environment

z/OS

Cause

• You are only running CAMIMGR for MII
  
  
• You are not using an automation product/tool to control the startup
  
  
• There is nothing found in the system parmlib that relates to any startup being issued
  
  
• You are most likely utilizing the MIM Early Start Mechanism as this is a Best Practice
  • The Early Start Mechanism uses the system parmlib (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.

To set up the Early Start mechanism, the following members of SYS1.PARMLIB need to be modified as follows:

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

Resolution

To prevent CAMIMGR from being started, comment the GRS exit (ISGNQXIT) in the PROGxx member. This will prevent the GRS exit from being loaded which will prevent the internal START CAMIMGR command from being executed from within the exit.