Dynamically rename the CA MIM Control Files in a DASDONLY or CTCDASD environment.

Document ID : KB000113526
Last Modified Date : 12/09/2018
Show Technical Document Details
Introduction:
CA MIM for z/OS address spaces can communicate with one another through any one of several cross-system communication methods. A shared DASD file or a shared coupling facility structure can be used as a physical control file. Alternatively, CA MIM for z/OS private storage can be used as a virtual control file (VCF) buffer and be passed between systems using natively allocated CA MIM for z/OS CTC devices or XCF services.
CA MIM for z/OS does not support control files on the high portion of the Extended Address Volume (EAV). If you use EAV, make sure you allocate data sets with EATTR=NO.

ISometimes it can be necessary to rename the Control Files, due to Company Global Standard changes. 

How to do this activity dynamically, having shared Control Files in a MIMPLEX ? 


 
Environment:
CA MIM in a MIMPLEX - Z/OS in SYSPLEX 
Instructions:
The following steps should be performed to rename the CA MIM Control Files used in a MIMPLEX installation.

 From all systems in the MIMPLEX:

        1. Display the Control Files Status with command "F MIMGR,DISPLAY FILES" and verify they are in the expected state. e.g. 00 is in use and 01 is available. 

        2. De-allocate the Secondary DASD Control File with command  "F MIMGR,DEALLOCATE DDNAME=MIMTBL01". 

        3. Display again the Control Files Status with command  "F MIMGR,DISPLAY FILES" and verify 01 is de-allocated. 

From one system in the MIMPLEX:

        4. Rename the Secondary DASD Control File from "oldname.CF01" to "newname.CF01" using ISPF OPT3.4 for example

From all systems in the MIMPLEX:

        5. Allocate to CA MIM the renamed Secondary DASD Control File with command  "F MIMGR,ALLOCATE DDNAME=MIMTBL01,DSN=newname.CF01" 

        6. Display again the Control Files Status with command  "F MIMGR,DISPLAY FILES" and verify 01 is allocated and has the right dataset name. 

From one system in the MIMPLEX:

        7. Migrate the DASD Control File to the Secondary with command "F MIMGR,MIGRATE CONTROLFILE=01" 

From all systems in the MIMPLEX:

        8. Display again the Control Files Status with command  "F MIMGR,DISPLAY FILES" and verify they are in the expected state. e.g. 00 is available and 01 is in use. 

        9. De-allocate the Primary DASD Control File with command  "F MIMGR,DEALLOCATE DDNAME=MIMTBL00". 

        10.  Display again the Control Files Status with command  "F MIMGR,DISPLAY FILES" and verify 00 is de-allocated. 

From one system in the MIMPLEX:

        11. Rename the Primary DASD Control File from "oldname.CF00" to "newname.CF00" using ISPF OPT3.4 for example

From all systems in the MIMPLEX:

        12. Allocate to CA MIM the renamed Primary DASD Control File with command  "F MIMGR,ALLOCATE DDNAME=MIMTBL00,DSN=newname.CF00"

        13. Display again the Control Files Status with command  "F MIMGR,DISPLAY FILES" and verify 00 is allocated and has the right dataset name. 

From one system in the MIMPLEX:

        14. Migrate the DASD Control File to the Primary with command "F MIMGR,MIGRATE CONTROLFILE=00" 
 
From all systems in the MIMPLEX:

        15. Display again the Control Files Status with command  "F MIMGR,DISPLAY FILES" and verify they are in the expected state. e.g. 00 is in use and 01 is available.