IBM XCF
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
In IBM mainframes, a Cross-system Coupling Facility, or XCF, is a component of z/OS that manages communications between applications in a sysplex.[1][2][3][4][5] Applications may be on the same system or different systems.
Systems communicate using messages transported by one of two mechanisms:
- Dedicated channel-to-channel links (CTC links).
- Structures in a Coupling Facility, only available in Parallel Sysplex, not in base sysplex.
In a parallel sysplex decisions about which of these two transport mechanisms to use for routing a specific message are made dynamically.
Within a single z/OS system messages are transported using cross-memory services, rather than being routed through either of the physical transport mechanisms.
Applications join specific groups as individual members. On joining a group a member can send or receive messages. Individual messages are assigned to specific transport classes, based on the message's size. Each transport class owns input and output buffers. Routing decisions are made at the transport class level.
References
[edit]- ^ Eade, Arndt; Frerking, Randy; Jackson, Rich; Mathis, Kellie; Redbooks, I. B. M. (2018-02-21). IBM CICS and the Coupling Facility: Beyond the Basics (PDF). IBM Redbooks. ISBN 978-0-7384-4304-1.
- ^ "Networking on z/OS - Cross-system Coupling Facility (XCF)". IBM.
- ^ "Entire Net-Work XCF Option 6.6.1 - XCF Overview". Software AG.
- ^ "MIM for z/OS 12.5 - XCF as the Initial Communication Method". Broadcom Inc.
- ^ z/OS V2R4 - MVS Programming: Sysplex Services Guide (PDF). IBM. 2020-09-22.