Advanced Topics › Product Activation Considerations › How You Dynamically Change CA MIM Communication Methods › Activate XCF Communication when COMMUNICATION=DASDONLY

Activate XCF Communication when COMMUNICATION=DASDONLY

This procedure dynamically activates the XCF communication and works with either DASD control files or XES list structures. The MIMplex is three systems using XES list structures with the MIM system names of GK03, GK13, and GK62.

Note: Be sure that your COMPATLEVEL is set to 12.0 or higher.

The following steps demonstrate how to dynamically activate the XCF communication when COMMUNICATION=DASDONLY.

Follow these steps:

1. Set up your XCF communication:
   • Confirm that all systems in the MIMplex are also within the same sysplex.
   • Set MIMINIT VCFBUFFERSIZE to 32768 or larger.
   • Review the XCF configuration and options in the SYS1.PARMLIB(COUPLExx) member.
   • You do not need to define a special transport class to CA MIM. However, we recommend at least one CLASSLEN of 32768 or larger to avoid possible performance problems. CLASSLEN is an XCF parameter and is coded in the SYS1.PARMLIB(COUPLExx) member.
   • If some of the LPARS are geographically remote, then IBM recommends that XCF use both CTC and list structures.

   Note: You do not need to create the Checkpoint files. However, CA MIM has no issues when you are already using them.

2. Activate your XCF communication.
   1. Verify that CA MIM automatically created your XCF paths on XE03:

      @D PATH 
      MIM0067I Command DISPLAY 960
      MIM0176 MIM PATH DISPLAY:
      LAST RESTART AT  14:30:23 ON 2013.171
       DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES
       XCF  GK62     USABLE                  0        0                    0
       XCF  GK13     USABLE                  0        0                    0
       N/A   GK03    LOCAL                   0        0                    0
      

   2. Verify that CA MIM automatically created your XCF paths on GK13:

      @D PATH
      MIM0067I Command DISPLAY 444
      MIM0176 MIM PATH DISPLAY:
      LAST RESTART AT  14:30:45 ON 2013.171
       DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES
       XCF  GK62     USABLE                  0        0                    0
       N/A  GK13     LOCAL                   0        0                    0
       XCF  GK03     USABLE                  0        0                    0
      

   3. Verify that CA MIM automatically created your XCF paths on GK62:

      @D PATH 
      MIM0067I Command DISPLAY 837
      MIM0176 MIM PATH DISPLAY:
      LAST RESTART AT  14:30:53 ON 2013.171
       DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES
       N/A  GK62     LOCAL                   0        0                    0
       XCF  GK03     USABLE                  0        0                    0
       XCF  GK13     USABLE                  0        0                    0
      

   CA MIM automatically creates a GLOBALVALUE, when not already coded in the INIT member:

   @D GLOBALVALUE
   MIM0067I Command DISPLAY 956
   MIM0373I MIM GLOBALVALUE display:
      ANYELIGIBLE=YES       MOSTPREFERRED=NO      NOMASTER=WAIT
      VCFMASTER=NONE
      ELIGIBLE MASTER LIST: GK03, GK13, GK62
   

3. Order the VCFMASTER list from the busiest system to the least busy system.

   Performance is improved as it reduces the total amount of I/O.

4. Enter the DISPLAY IO command on all systems and pick the system with the largest RATE: CYC.

   In this example, we have determined that GK62 is the busiest, followed by GK13, followed by GK03.

5. Enter the GLOBALVALUE command on one system only:

   @GLOBALVALUE VCFMASTER(GK62,GK13,GK03)
   MIM0067I Command GLOBALVALUE 263
   MIM0193I GLOBALVALUE command processing initiated
   MIM0363I GLOBALVALUE command changes pending on external systems 
   MIM0362I GLOBALVALUE command processing complete
   

6. Verify the new VCFMASTER list:

   @D GLOBALV
   MIM0067I Command DISPLAY 273 
   MIM0373I MIM GLOBALVALUE display:
      ANYELIGIBLE=YES       MOSTPREFERRED=NO      NOMASTER=WAIT
      VCFMASTER=( GK62, GK13, GK03 )
      ELIGIBLE MASTER LIST: GK62, GK13, GK03
   

7. Update the initialization member with the new GLOBALVALUE statement.
8. Use the MIGRATE command and move the control file up to the VCF on GK62.

   @MIGRATE MASTER=GK62
   MIM0067I Command MIGRATE 307
   MIM0232I VCF migration SCHEDULED   - MASTER=GK62
   MIM0377I VCF migration IN PROGRESS - MASTER=GK62
   MIM0342I system GK62 VCF activation      COMPLETE - MASTER=GK62
   

9. Confirm that the Virtual Control file is active on GK62:

   @D SYS
   MIM0067I Command DISPLAY 211
   MIM0108I SYSTEMS DISPLAY
      INDEX ALIAS SYSTEM   RELATION STATUS      OPSYS     LAST ACCESS
       01    03   GK03     EXTERNAL ACTIVE      zOS  2013.171 14:54:51.19 
       02    13   GK13     EXTERNAL ACTIVE      zOS  2013.171 14:54:51.14 
       03    62   GK62     LOCAL    MASTER      zOS  2013.171 14:54:51.22
   

The XCF communication is activated and GK62 is now the VCFMASTER.