The XCF initial communications method is similar to CTCONLY; however, the VCF is passed from the master to the client systems through the z/OS Cross System Coupling Facility (XCF).
The XCF communication method is available in sites that are configured in a sysplex. XCF is not available on z/VM systems.
The XCF component of z/OS provides multisystem management services in a sysplex. CA MIM uses the XCF component of z/OS to transport the virtual control file from the master system to the client systems.
CA MIM uses the CA XCF Standard Component (LXCF) module LXCFMAIN to interface with XCF on its behalf. LXCF uses standard IBM XCF macros to exploit XCF services. The LXCFMAIN module is distributed with CA Common Services for z/OS.
XCF is a sysplex-only transport service. Therefore, the CA MIM XCF communication option is available only to those sites that have MIMplex systems in the defined sysplex. If the MIMplex includes systems outside of the sysplex, you can add the CTCPATH statements for those systems. CA MIM supports a simultaneous mixture of XCF and CTC devices for the VCF communication.
Signaling describes the mechanism through which the XCF component of z/OS transmits application data across systems in the sysplex. XCF component signaling is accomplished using 3088 or ESCON CTC devices or coupling facility list structures. The signaling methods used by the XCF component are transparent to the application exploiting XCF services. While the method of signaling used by the XCF component is transparent to CA MIM, the performance of the signaling service has a direct impact on the performance of CA MIM.
Note: Although you may have specified XCF as your initial communication method, CA MIM allows the simultaneous use of CTC and XCF communication paths. You can place CTCPATH definitions in your MIMINIT member or issue the CTCPATH command dynamically to define CTC devices for use by CA MIM.
|
Copyright © 2014 CA.
All rights reserved.
|
|