XCF (Cross-System Coupling Facility) is a z/OS base component that enables communication, coordination, and synchronization between different z/OS systems in a Parallel Sysplex.

It is not the Coupling Facility itself—instead, it is the software messaging and coordination layer that uses CF and coupling links underneath.

1. What XCF is (core idea)

XCF provides:

A reliable inter-system communication framework for sending messages, detecting failures, and coordinating workloads across sysplex members.

Think of it as:

• A system-to-system messaging backbone
• A membership and health monitoring service
• A coordination layer for sysplex-aware applications

2. Where XCF fits in sysplex architecture

In a Parallel Sysplex:

• CF (Coupling Facility) → shared data + locks + cache structures
• XCF → messaging + group coordination between z/OS images
• z/OS applications (CICS, DB2, IMS) → use XCF services indirectly or directly

👉 XCF sits at the operating system coordination layer

3. Main functions of XCF

A. Inter-system messaging

XCF allows systems to send messages:

• One-to-one
• One-to-many
• Group-based communication

Used for:

• Synchronization events
• State updates
• Work coordination

B. Group services

XCF manages groups of cooperating systems or tasks.

A group:

• Has members (systems or subsystems)
• Has a defined protocol
• Shares status and coordination logic

Examples:

• DB2 data sharing group
• Sysplex-wide workload components

C. Membership management

XCF continuously tracks:

• Which systems are active in sysplex
• Which systems joined or left
• Whether a system is healthy or failed

👉 This is critical for high availability.

D. Failure detection

XCF detects:

• System outages
• Lost heartbeat signals
• Communication failures

It triggers:

• Membership rebuild
• Recovery actions in subsystems

4. How XCF communication works

Step 1: Message creation

A system issues an XCF send request.

Step 2: Transport selection

XCF chooses transport path:

• CF signaling (fast path)
• Coupling links
• Internal sysplex channels

Step 3: Delivery

Message is delivered to:

• Target system
• Or all group members

Step 4: Acknowledgment / processing

Receiver processes message and optionally responds.

5. XCF signaling vs CF structures (important distinction)

👉 XCF is communication; CF is shared state.

6. Transport mechanism (how it is implemented)

XCF uses multiple transport options:

• CF signaling structures (fastest path)
• CF links (hardware interconnect)
• CPC internal pathways

It dynamically selects the fastest available path.

7. XCF groups in practice

Each group has:

• Group name
• Membership list
• Protocol definition
• Message types

Example behavior:

• Member joins group → XCF broadcasts update
• Member fails → XCF removes it and notifies others

8. Role in high availability

XCF is critical for:

• Sysplex-wide failure detection
• Automatic workload redistribution
• State synchronization across systems

If a system fails:

• XCF immediately informs all members
• Recovery processes are triggered

9. Interaction with other sysplex components

XCF works closely with:

Coupling Facility (CF)

• Uses CF signaling structures for fast messaging
• Relies on CF for shared state coordination

WLM (Workload Manager)

• Uses XCF to coordinate workload distribution decisions

DB2 / CICS / IMS

• Use XCF groups for data sharing and cluster coordination

10. Performance characteristics

XCF is designed for:

• Very low-latency messaging (microseconds–milliseconds)
• High message throughput
• Minimal CPU overhead per message
• High reliability under system stress

11. Simple mental model

Think of XCF as:

A high-speed, system-to-system messaging and membership control system that keeps all z/OS instances in a sysplex aware of each other and coordinated.

Key takeaway

XCF (Cross-System Coupling Facility) is the z/OS sysplex communication and coordination layer that:

• Sends messages between systems
• Manages sysplex membership and health
• Enables group-based coordination
• Supports failure detection and recovery
• Works alongside CF but focuses on communication, not shared memory