|
|
|
The XCF 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 configured in a sysplex. It is not available on z/VM systems. The XCF component of z/OS provides multi-system 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.
Because XCF is a sysplex-only transport service, 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, then you must choose another CA MIM communication method.
The XCF communication method is similar to the CTCONLY communication method in that a master system passes the virtual control file (VCF) to client systems on demand. The only difference is the transport medium. CTCONLY transmits the VCF through CTC devices allocated to the CA MIM address space, while XCF transmits the VCF through the z/OS XCF facility.
Signaling is the term used to describe 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.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |