z/OS MVS Programming: Sysplex Services Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Introduction to Sysplex Services for Data Sharing (XES)

z/OS MVS Programming: Sysplex Services Guide
SA23-1400-00

Sysplex services for data sharing allow subsystems, system products and authorized applications running in a sysplex use a coupling facility for high-performance, high-availability data sharing. Sysplex services support data sharing while maintaining data integrity and consistency by:
  • Allowing users to store and access data in a coupling facility in any of three types of structures (list, lock, or cache).
  • Guaranteeing that individual operations on coupling facility data are either completed or, if necessary, backed out to their original state. Users are prevented from accessing data that is being changed.
  • Providing services to help users protect data when recovering from a failure.
  • Enabling users to ensure that their local copies of shared data are valid.
  • Allowing users who change shared data to automatically notify other users that their local copies are no longer valid.
  • Providing functions that allow users to create a customized set of locks and locking protocols including:
    • Application-defined:
      • Resource locks
      • Lock states
      • Lock state compatibility rules
    • A mechanism to allow users to resolve lock contention. When contention arises for a lock, the system passes control to the lock owner's contention exit to resolve the lock contention according to the user's defined protocols.
    • Support of failure recovery options through the retention of lock-related information that will persist across system or sysplex outages.

Coupling Facility Structures

Instead of accessing data in a coupling facility by address, you can allocate three types of objects, called structures, and access data in the structures as logical entities (by name, for instance). The ability to access data in this manner frees coupling facility users from having to be concerned with the physical location or address of the data.

Each type of structure, described in detail in Types of Coupling Facility Structures, provides a unique set functions and offers a different way of using a coupling facility. The types of structures are:
  • Cache structure
  • List structure
  • Lock structure

A coupling facility can hold one or more structures of any type, however, each structure must reside entirely in a single coupling facility. Applications are not limited to using a single coupling facility structure. They can use multiple structures of the same type or different types.

Products and subsystems that exploit the coupling facility indicate their coupling facility structure requirements as part of their installation information. For instance, a product might require a lock structure of a certain size, with particular attributes, and a certain name. Or, a product might require that a structure be allocated in a certain level (CFLEVEL) of a coupling facility because of the functionality it provides.

When system administrators or system programmers install software that requires a coupling facility structure, they create a coupling facility resource management (CFRM) policy that specifies the name, size, and attributes of each structure to be allocated. The CFRM policy also allows the installation to limit the amount of storage each structure can occupy and control where each structure is allocated, through a “preference list”, for multiple coupling facilities.

Once the policy is defined, the operator needs to issue the SETXCF command to activate the policy. The activated policy does not cause the structures to be allocated. A structure is allocated only when the first user connects to the structure.

For More Information

To learn more about the following coupling facility topics, see z/OS MVS Setting Up a Sysplex:
  • What is a coupling facility?
  • What is the role of the coupling facility in a sysplex?
  • How does an installation define coupling facility structures?
  • What is a CFRM policy and how does an installation define one?
  • What are the hardware requirements for the coupling facility?
  • What are the software requirements for the coupling facility?
  • What are the planning considerations for using a coupling facility?
The following information is about the coupling facility:
  • z/OS Parallel Sysplex Overview
  • PR/SM™ Planning Guide

For the most up-to-date information about a coupling facility, see the Parallel Sysplex website at http://www.s390.ibm.com/pso/.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014