MIM setup of standalone system with non-shared DASD

Products

• MIM Resource Sharing (MIM)

Issue/Introduction

You are setting up a stand alone system where DASD will not be shared.

This article will outline the basic recommendations for initial setup of a MII environment.

Environment

Release : 12.5

Resolution

• In the MIMINIT member, create a DEFSYS with only 2 systems on it - 1 is for the actual system and 1 is for a "dummy" system
  

  DEFSYS (SYS1,S1,SYS1,INITIAL=FREED),
         (DUMMY,XX,DUMMY,INIT=FREED)

• In the MIMINIT member, specify GDIINIT PROCESS=ALLSYSTEMS, RESERVES=CONVERT
  
  
• The GDIF exempt member (MIMEXMPT) should be mostly empty with the exception of the following DEFAULT statement. The reason being that we don't want MIM to KEEP any reserves on LOCAL statements.
  

  DEFAULT  RESOURCE=GLOBAL,   /* RESOURCE NAME IS GLOBAL
  JOB=GLOBAL                  /* JOBNAME IS GLOBAL

• The MIMQNAME member should only have the one arbitrary qname in it
  

  DUMMYQNM GDIF=YES

• For first time startup, specify FORMAT=BOTH in the CAMIMGR proc. After MIM comes up successfully, change it to FORMAT=NONE.

Additional Information

1. The SyntaxSCAN Utility can be used to detect any possible issues with the syntax that could cause a U40 during startup
2. If you are not customizing any MIM message text you can remove the MIMMSGS DD from the CAIMIMGR JCL proc which would eliminate any MIM0867I messages.
3. The MIM Early Start Mechanism is recommended when setting up for MII, However, diagnosing Early Start issues is difficult as JES doesn't come up and you can't get syslogs.
4. If you do try Early Start Mechanism and experieince a problem, verify the following:

• • No MIM0061W messages
  • The MIM0023I message was issued
  • A MIM DISPLAY SYSTEMS command shows the local system ACTIVE and the external system FREED
  • If still no clear cause, first review a KB article related to a MIMES004I message. Last resort is to take a SAD and provide to Broadcom MIM support for review.