IBM Parallel Sysplex: Difference between revisions

Revision as of 23:32, 8 February 2012

Revision as of 15:16, 13 April 2012

Line 2:

==Sysplex==

In 1990, [[IBM]] [[mainframe computer]]s, introduced the concept of a '''Systems Complex''', commonly called a '''Sysplex''', allowswith multiple[[MVS]]/ESA processors to be joined into a single unit, sharing the same ''Sysplex name'' and Couple Data SetsSPV4.1 in Put another way, a Sysplex is a single logical system running on one or more physical systems1990. SysplexesThis areallows oftenauthorized isolatedcomponents withinin aup singleto system,eight but[[LPAR]]s Parallelcommunicate Sysplexand technologycooperate allowswith multipleeach mainframesother tousing actXCF asprotocol. one.

Components of a Sysplex include:

* A Sysplexcommon Timertime whichsource synchronizesto synchronize all member systems' clocks. This can be done with either a Sysplex timer, or with 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 ([[IBM XCF|XCF]]), which allows systems to communicate [[peer-to-peer]];

* Couple Data Sets (CDS);

Users of a (base) Sysplex includes:

* 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

* [[z/OS Workload Manager]] (WLM) – Policy based performance management of heterogeneous workloads across one or more z/OS image

* [[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]] – 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==