Parallel Sysplex
Parallel Sysplex
Parallel Sysplex
Sysplex[edit]
In 1990, IBM mainframe computers introduced the concept of a Systems Complex,
commonly called a Sysplex, with MVS/ESA SPV4.1. This allows authorized
components in up to eight logical partitions (LPARs) to communicate and cooperate
with each other using the XCF protocol.
Components of a Sysplex include:
A common time source to synchronize all member systems' clocks. This can
involve either a Sysplex timer (Model 9037), or the Server Time Protocol (STP)
Global Resource Serialization (GRS), which allows multiple systems to access
the same resources concurrently, serializing where necessary to ensure exclusive
access
Cross System Coupling Facility (XCF), which allows systems to
communicate peer-to-peer
Couple Data Sets (CDS)
Users of a (base) Sysplex include:
Console services – allowing one to merge multiple MCS consoles from the
different members of the Sysplex, providing a single system image for Operations
Automatic Restart Manager (ARM) – Policy to direct automatic restart of failed
jobs or started tasks on the same system if it is available or on another LPAR in the
Sysplex
Sysplex Failure Manager (SFM) – Policy that specifies automated actions to take
when certain failures occur such as loss of a member of a Sysplex or when
reconfiguring systems
Workload Manager (WLM) – Policy based performance management of
heterogeneous workloads across one or more z/OS images or even on AIX
Global Resource Serialization (GRS) - Communication – allows use of XCF links
instead of dedicated channels for GRS, and Dynamic RNLs
Tivoli OPC – Hot standby support for the controller
RACF (IBM's mainframe security software product) – Sysplex-wide RVARY and
SETROPTS commands
PDSE file sharing
Multisystem VLFNOTE, SDUMP, SLIP, DAE
Resource Measurement Facility (RMF) – Sysplex-wide reporting
CICS – uses XCF to provide better performance and response time than using
VTAM for transaction routing and function shipping.
zFS – Using XCF communication to access data across multiple LPARs
Parallel Sysplex[edit]
The Parallel Sysplex was introduced with the addition of the Coupling Facility (CF) with
coupling links for high speed communication, with MVS/ESA V5.1 operating system
support, together with the mainframe models in April 1994. [1]
The Coupling Facility (CF) may reside on a dedicated stand-alone server configured
with processors that can run Coupling Facility control code (CFCC), as integral
processors on the mainframes themselves configured as ICFs (Internal Coupling
Facilities), or less common, as normal LPARs. The CF contains Lock, List, and Cache
structures to help with serialization, message passing, and buffer consistency between
multiple LPARs.[2]
The primary goal of a Parallel Sysplex is to provide data sharing capabilities, allowing
multiple databases for direct reads and writes to shared data. This can provide benefits
of
Help remove single points of failure within the server, LPAR, or subsystems
Application Availability
Single System Image
Dynamic Session Balancing
Dynamic Transaction Routing
Scalable capacity
Databases running on the System z server that can take advantage of this include:
DB2
IBM Information Management System (IMS).
VSAM (VSARM/RLS)
IDMS
Adabas
DataCom
Oracle
Other components can use the Coupling Facility to help with system management,
performance, or reduced hardware requirements. Called “Resource Sharing”, uses
include: