Activate XCF Communication on a Subset of the Systems

Advanced Topics › Product Activation Considerations › How You Dynamically Change CA MIM Communication Methods › Activate XCF Communication on a Subset of the Systems

Activate XCF Communication on a Subset of the Systems

This procedure dynamically activates XCF communication on a subset of the MIMplex when COMMUNICATION=CTCDASD or CTCONLY. The MIMplex is four systems with system names of GK03, GK13, GK23, and GK62. GK03, GK13, and GK62 are in one sysplex. GK23 is in a different sysplex.

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

Follow these steps:

Set up your XCF communication on a subset of systems:
- 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 lease 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, if you are already using them CA MIM has no issues.

Confirm the current paths by entering the DISPLAY PATH command on all four systems.

On GK03:

@D PATH
MIM0067I Command DISPLAY 422
MIM0176 MIM PATH DISPLAY:
LAST RESTART AT  08:38:10 ON 2013.176
 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.000382   3,269
 184A GK62     USABLE  IDLE         3,268    3,268                    0
 180A GK62     USABLE  IDLE             0        0                    0
 0B4A GK62     USABLE  IDLE             0        0                    0
 186A GK23     USABLE  IDLE         3,268    3,268                    0
 182A GK23     USABLE  IDLE             0        0                    0
 0B6A GK23     USABLE  IDLE             0        0                    0
 183A GK13     USABLE  IDLE         3,254    3,254                    0
 154A GK13     USABLE  IDLE             0        0                    0
 0B3A GK13     USABLE  IDLE             0        0                    0

In the previous display, CA MIM automatically created the XCF paths to external systems that are in the same sysplex as the local system. No actions were required to accomplish this task. Also notice that CA MIM does not show the path currently IN-USE. The behavior of the DISPLAY PATH command is required to use the command on the client systems to determine the current path.

On GK13:

@D PATH
MIM0067I Command DISPLAY 673
MIM0176 MIM PATH DISPLAY:
LAST RESTART AT  08:38:20 ON 2013.176
 DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES
 XCF  GK62     USABLE                   0        0                    0
 N/A  GK13     LOCAL                    0        0                    0
 187A GK62     USABLE  IDLE             0        0                    0
 0BFA GK62     USABLE  IDLE             0        0                    0
 0B7A GK62     USABLE  IDLE             0        0                    0
 185A GK23     USABLE  IDLE             0        0                    0
 181A GK23     USABLE  IDLE             0        0                    0
 0B5A GK23     USABLE  IDLE             0        0                    0
>183A GK03     IN-USE  BUSY         3,540    3,540     0.001925   3,540
                       RESERVE
 154A GK03     USABLE  IDLE             0        0                    0
 0B3A GK03     USABLE  IDLE             0        0                    0
 XCF  GK03     USABLE                   0        0                    0

Note the XCF paths to GK03 and GK62 in the previous display.

On GK23:

@D PATH
MIM0067I Command DISPLAY 327
MIM0176 MIM PATH DISPLAY:
LAST RESTART AT  08:38:29 ON 2013.176
 DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES
 N/A  GK23     LOCAL                    0        0                    0
 183A GK62     USABLE  IDLE             0        0                    0
 154A GK62     USABLE  IDLE             0        0                    0
 0B3A GK62     USABLE  IDLE             0        0                    0
 185A GK13     USABLE  IDLE             0        0                    0
 181A GK13     USABLE  IDLE             0        0                    0
 0B5A GK13     USABLE  IDLE             0        0                    0
>186A GK03     IN-USE  IDLE         3,657    3,657     0.002053   3,657
 182A GK03     USABLE  IDLE             0        0                    0
 0B6A GK03     USABLE  IDLE             0        0                    0

The previous display shows no XCF paths to GK03, GK13, and GK62 because GK23 is in a different sysplex.

On GK62:

@D PATH
MIM0067I Command DISPLAY 136
MIM0176 MIM PATH DISPLAY:
LAST RESTART AT  08:38:36 ON 2013.176
 DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES 
 N/A  GK62     LOCAL                    0        0                    0 
 183A GK23     USABLE  IDLE             0        0                    0 
 154A GK23     USABLE  IDLE             0        0                    0 
 0B3A GK23     USABLE  IDLE             0        0                    0 
 187A GK13     USABLE  IDLE             0        0                    0 
 0BFA GK13     USABLE  IDLE             0        0                    0 
 0B7A GK13     USABLE  IDLE             0        0                    0 
>184A GK03     IN-USE  IDLE         3,796    3,796     0.002015   3,796 
 180A GK03     USABLE  IDLE             0        0                    0 
 0B4A GK03     USABLE  IDLE             0        0                    0 
 XCF  GK03     USABLE                   0        0                    0 
 XCF  GK13     USABLE                   0        0                    0

So, all four systems are currently using CTCs to communicate, but systems GK03, GK13, and GK62 can now communicate through XCF. Use the SET MIM VCFPREFERENCE=CTC/XCF command for specifying whether CA MIM uses the CTC or XCF connection. The default is CTC when COMMUNICATION=CTCONLY or CTCDASD.

Activate your XCF communication

Issue the SET MIM VCFPREFERENCE=XCF command on GK13 and GK62 to switch from CTC to XCF. The command is not needed on the current VCFMASTER(GK03) because it detects the switch from the clients.

On GK13:

@SET MIM VCFPREF=XCF
MIM0067I Command SETOPTION 169
MIM0052I SETOPTION MIM processing complete
MIM0292I VCF switched to alternate VCF path XCF

On GK62:

@SET MIM VCFPREF=XCF
MIM0067I Command SETOPTION 169
MIM0052I SETOPTION MIM processing complete
MIM0292I VCF switched to alternate VCF path XCF

The activation is now complete.

Update the commands member with:
```
IFSYS GK03,GK13,GK62
SET MIM VCFPREFERENCE=XCF
ENDIF
```
Note: GK23 was not included in the command as we want it to continue using CTC which is the default for COMMUNICATION=CTCDASD or CTCONLY.

Verify the current connectivity by entering the DISPLAY PATH command on all client systems.

On GK62:

@D PATH
MIM0067I Command DISPLAY 180
MIM0176 MIM PATH DISPLAY:
LAST RESTART AT  08:38:36 ON 2013.176
 DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES
 N/A  GK62     LOCAL                    0        0                    0
 183A GK23     USABLE  IDLE             0        0                    0
 154A GK23     USABLE  IDLE             0        0                    0
 0B3A GK23     USABLE  IDLE             0        0                    0
 187A GK13     USABLE  IDLE             0        0                    0
 0BFA GK13     USABLE  IDLE             0        0                    0
 0B7A GK13     USABLE  IDLE             0        0                    0
 184A GK03     USABLE  IDLE         4,769    4,769     0.001856   4,769
 180A GK03     USABLE  IDLE             0        0                    0
 0B4A GK03     USABLE  IDLE             0        0                    0
>XCF  GK03     IN-USE                  95       95     0.000408      95
 XCF  GK13     USABLE                   0        0                    0

Notice how the XCF path is now being used between GK62 and GK03.

On GK13:

@D PATH
MIM0067I Command DISPLAY 776
MIM0176 MIM PATH DISPLAY:
LAST RESTART AT  08:38:20 ON 2013.176
 DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES
 XCF  GK62     USABLE                   0        0                    0
 N/A  GK13     LOCAL                    0        0                    0
 187A GK62     USABLE  IDLE             0        0                    0
 0BFA GK62     USABLE  IDLE             0        0                    0
 0B7A GK62     USABLE  IDLE             0        0                    0
 185A GK23     USABLE  IDLE             0        0                    0
 181A GK23     USABLE  IDLE             0        0                    0
 0B5A GK23     USABLE  IDLE             0        0                    0
 183A GK03     USABLE  IDLE         5,266    5,266     0.001632   5,266
 154A GK03     USABLE  IDLE             0        0                    0
 0B3A GK03     USABLE  IDLE             0        0                    0
>XCF  GK03     IN-USE                 105      105     0.001399     105

Notice how the XCF path is now being used between GK13 and GK03.

On GK23:

MIM0176 MIM PATH DISPLAY:
LAST RESTART AT  08:38:29 ON 2013.176
 DEV  SYSTEM   STATE   IO-STAT     READS   WRITES  ERR TIME/RSV  CYCLES
 N/A  GK23     LOCAL                    0        0                    0
 183A GK62     USABLE  IDLE             0        0                    0
 154A GK62     USABLE  IDLE             0        0                    0
 0B3A GK62     USABLE  IDLE             0        0                    0
 185A GK13     USABLE  IDLE             0        0                    0
 181A GK13     USABLE  IDLE             0        0                    0
 0B5A GK13     USABLE  IDLE             0        0                    0
>186A GK03     IN-USE  IDLE         3,657    3,657     0.002053   3,657
 182A GK03     USABLE  IDLE             0        0                    0
 0B6A GK03     USABLE  IDLE             0        0                    0

GK23 is still using a CTC connection to GK03 because there are no XCF paths between GK23 and GK03.