How You Start CA MIM on a System New to Your Complex

Advanced Topics › Product Activation Considerations › How You Start CA MIM on a System New to Your Complex

How You Start CA MIM on a System New to Your Complex

To start CA MIM, on a system new to your complex depends on which of the following communication methods you selected:

For DASDONLY: Dynamically add an undefined system to the MIMPLEX.

Follow these steps:

Ensure that no systems have been REMOVED from the MIMPLEX by reviewing the DISPLAY SYSTEMS command output:

MIM0108I SYSTEMS DISPLAY                                              
   INDEX ALIAS SYSTEM   RELATION STATUS      OPSYS     LAST ACCESS    
    01    03   GK03     EXTERNAL ACTIVE      zOS  2012.013 12:25:45.38
    02    13   GK13     LOCAL    ACTIVE      zOS  2012.013 12:25:45.91
    03    23   GK23     EXTERNAL FREED

Verify that there are no gaps between the index numbers. If there are no gaps, then it is safe to proceed with the next step. Otherwise, update the DEFSYS statement, shut down globally, then restart globally with a control file format.

Update the DEFSYS statement in the CA MIMINIT member:

DEFSYS (GK03,03,XE03,INIT=FREED),  
       (GK13,13,XE13,INIT=FREED),  
       (GK23,23,XE23,INIT=FREED),  
       (GK62,62,XE62,INIT=FREED)      /* new system

Start MIM on the new LPAR (GK62 in this example) with FORMAT=CHKPT or FORMAT=NONE if no checkpoints exist.
The new system joins the established MIMPLEX and honors the MIM name and alias as coded on the DEFSYS statement.

Confirm the new system joined with the DISPLAY SYSTEMS command:

MIM0108I SYSTEMS DISPLAY

   INDEX ALIAS SYSTEM   RELATION STATUS      OPSYS     LAST ACCESS

    01    03   GK03     EXTERNAL ACTIVE      zOS  2012.013 12:26:26.39
    02    13   GK13     EXTERNAL ACTIVE      zOS  2012.013 12:26:26.88
    03    23   GK23     EXTERNAL FREED                                
    04    62   GK62     LOCAL    ACTIVE      zOS  2012.013 12:26:27.36

For XCF: Dynamically add an undefined system to the MIMPLEX.

Follow these steps:

Use the DISPLAY INIT command to ensure that the MIMPLEX is running with COMMUNICATION=XCF and COMPATLEVEL= 11.9 or greater.

Use the DISPLAY SYSTEM to verify that you have an active MIMPLEX. The new system cannot be the first active system in the MIMPLEX.

MIM0108I SYSTEMS DISPLAY                                             
  INDEX ALIAS SYSTEM   RELATION STATUS      OPSYS     LAST ACCESS    
   01    03   MIMMC003   LOCAL  MASTER       zOS  2012.026 10:52:21.82
   02    13   MIMMC013   EXTERNAL FREED

Issue the DEFSYS command with your preferred parameters.
```
DEFSYS (MIMMC062,62,XE62)
```
Verify that the following message appears:
```
MIM0408I - System Add Successful -  MIMMC062
```

Issue the DISPLAY SYSTEMS command to ensure that the new system was added correctly.

INDEX ALIAS SYSTEM   RELATION STATUS      OPSYS     LAST ACCESS    
  01    03   MIMMC003 LOCAL    MASTER      zOS  2012.026 10:57:06.16
  02    13   MIMMC013 EXTERNAL FREED

  03    62   MIMMC062 EXTERNAL FREED

Note: In order, for a new system to become a VCFMASTER system you must update the GLOBALVALUE parameter.

Follow these steps:

Issue a DISPLAY GLOBALVALUE command. Note the list of eligible master systems.

  MIM0373I MIM GLOBALVALUE display:                           
  ANYELIGIBLE=YES       MOSTPREFERRED=YES     NOMASTER=WAIT 
  VCFMASTER=( MIMMC003, MIMMC013 )                          
  ELIGIBLE MASTER LIST: MIMMC003, MIMMC013

Issue a GLOBALVALUE VCFMASTER={LIST} command. Only enter this command on one system. Note: copy the VCFMASTER list from the prior command and add the desired system.
```
GLOBALVALUE VCFMASTER=( MIMMC003, MIMMC013 , MIMMC062)  
```

Verify Output:

MIM0363I GLOBALVALUE command changes pending on external systems                                                                     
GLOBALVALUE command processing complete

Issue a DISPLAY GLOBALVALUE command again to verify that the desired system was added to the VCFMASTER list.

  MIM0373I MIM GLOBALVALUE display:                             
  ANYELIGIBLE=YES       MOSTPREFERRED=YES     NOMASTER=WAIT   
  VCFMASTER=( MIMMC003, MIMMC013, MIMMC062)                      
  ELIGIBLE MASTER LIST: MIMMC003, MIMMC013, MIMMC062

Update the GLOBALVALUE statement in the MIMINIT member to match the exact text of the operator command.

GLOBALVALUE VCFMASTER=(MIMMC003,MIMMC013, MIMMC062),
            ANYELIGIBLE=YES,                                
            NOMASTER=WAIT,                                  
            MOSTPREFERRED=YES

Update the DEFSYS statement in the MIMINIT member. Be sure to code the new system last on the system list.

DEFSYS (MIMMC003,03,XE03,INITIAL=FREED),  
          (MIMMC013,13,XE13,INITIAL=FREED),   
           (MIMMC062,62,XE62)

Allocate checkpoint files for the new system. Defined them using the CHKPTDSN statement in the MIMINIT member.
```
MIMINIT CHKPTDSN=CHIMA14.MIMMC0&SYSCLONE..MIMCKP
```
Start the new system with FORMAT=CHKPT.

Enter a DISPLAY SYSTEMS command to confirm the new system has been added.

MIM0108I SYSTEMS DISPLAY                                              
  INDEX ALIAS SYSTEM   RELATION STATUS      OPSYS     LAST ACCESS     
   01    03   MIMMC003 EXTERNAL MASTER      zOS  2012.026 11:05:55.14 
   02    13   MIMMC013 EXTERNAL FREED                                 
   03    62   MIMMC062 LOCAL    ACTIVE      zOS  2012.026 11:05:55.22

For CTCDASD or CTCONLY: Define system IDs and CTC paths for your new system through the DEFSYS and CTCPATH statements. Then, reformat the control files as you start CA MIM.

Important! Each CTC device that CA MIM uses must have an operational path and must be ONLINE before CA MIM attempts to allocate the CTC device. If either of these conditions is not met, the appropriate error message (MIM0464E or MIM0446E) is issued and CTC device allocation is bypassed. The CTC address becomes available to CA MIM after a VARY ONLINE.

More information:

How CA MIM Formats Control and Checkpoint Files

Tell Technical Publications how we can improve this information