IBM Parallel Sysplex

Last updated

In computing, a Parallel Sysplex is a cluster of IBM mainframes acting together as a single system image with z/OS. Used for disaster recovery, Parallel Sysplex combines data sharing and parallel computing to allow a cluster of up to 32 systems to share a workload for high performance and high availability.

Contents

Sysplex

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:

Users of a (base) Sysplex include:

Parallel Sysplex

Schematic representation of a Parallel Sysplex GDPS.svg
Schematic representation of a Parallel Sysplex

IBM introduced [1] the Parallel Sysplex with the addition of the 9674 [2] Coupling Facility (CF), new S/390 models, [3] [4] [5] upgrades to existing models, coupling links for high speed communication and MVS/ESA SP V5.1 [6] operating system support, in April 1994. [7]

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. [8]

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

Databases running on the System z server that can take advantage of this include:

Other components can use the Coupling Facility to help with system management, performance, or reduced hardware requirements. Called “Resource Sharing”, uses include:

Tape Switching uses the GRS structure to provide sharing of tape units between z/OS images.

Multi-system enclave management for improved performance

Major components of a Parallel Sysplex include:

The Coupling Facility may be either a dedicated external system (a small mainframe, such as a System z9 BC, specially configured with only coupling facility processors) or integral processors on the mainframes themselves configured as ICFs (Internal Coupling Facilities). [9] It is recommended that at least one external CF be used in a parallel sysplex. [10] It is recommended that a Parallel Sysplex has at least two CFs and/or ICFs for redundancy, especially in a production data sharing environment. Server Time Protocol (STP) replaced the Sysplex Timers beginning in 2005 for System z mainframe models z990 and newer. [11] A Sysplex Timer is a physically separate piece of hardware from the mainframe, [12] whereas STP is an integral facility within the mainframe's microcode. [13] With STP and ICFs it is possible to construct a complete Parallel Sysplex installation with two connected mainframes. Moreover, a single mainframe can contain the internal equivalent of a complete physical Parallel Sysplex, useful for application testing and development purposes. [14]

The IBM Systems Journal dedicated a full issue to all the technology components. [15]

Server Time Protocol

Maintaining accurate time is important in computer systems. For example, in a transaction-processing system the recovery process reconstructs the transaction data from log files. If time stamps are used for transaction-data logging, and the time stamps of two related transactions are transposed from the actual sequence, then the reconstruction of the transaction database may not match the state before the recovery process. Server Time Protocol (STP) can be used to provide a single time source between multiple servers. Based on Network Time Protocol concepts, one of the System z servers is designated by the HMC as the primary time source (Stratum 1). It then sends timing signals to the Stratum 2 servers through use of coupling links. The Stratum 2 servers in turn send timing signals to the Stratum 3 servers. To provide availability, one of the servers can be designated as a backup time source, and a third server can be designated as an Arbiter to assist the Backup Time Server in determining if it should take the role of the Primary during exception conditions.

STP has been available on System z servers since 2005.

More information on STP is available in “Server Time Protocol Planning Guide”. [16]

Geographically Dispersed Parallel Sysplex

Geographically Dispersed Parallel Sysplex (GDPS) is an extension of Parallel Sysplex of mainframes located, potentially, in different cities. GDPS includes configurations for single site or multiple site configurations: [17]

See also

Related Research Articles

IBM mainframes are large computer systems produced by IBM since 1952. During the 1960s and 1970s, IBM dominated the computer market with the 7000 series and the later System/360, followed by the System/370. Current mainframe computers in IBM's line of business computers are developments of the basic design of the System/360.

<span class="mw-page-title-main">MVS</span> Operating system for IBM mainframes

Multiple Virtual Storage, more commonly called MVS, is the most commonly used operating system on the System/370, System/390 and IBM Z IBM mainframe computers. IBM developed MVS, along with OS/VS1 and SVS, as a successor to OS/360. It is unrelated to IBM's other mainframe operating system lines, e.g., VSE, VM, TPF.

<span class="mw-page-title-main">Mainframe computer</span> Large and powerful computer

A mainframe computer, informally called a mainframe or big iron, is a computer used primarily by large organizations for critical applications like bulk data processing for tasks such as censuses, industry and consumer statistics, enterprise resource planning, and large-scale transaction processing. A mainframe computer is large but not as large as a supercomputer and has more processing power than some other classes of computers, such as minicomputers, servers, workstations, and personal computers. Most large-scale computer-system architectures were established in the 1960s, but they continue to evolve. Mainframe computers are often used as servers.

<span class="mw-page-title-main">Transaction Processing Facility</span> IBM real-time operating system

Transaction Processing Facility (TPF) is an IBM real-time operating system for mainframe computers descended from the IBM System/360 family, including zSeries and System z9.

z/OS 64-bit operating system for IBM mainframes

z/OS is a 64-bit operating system for IBM z/Architecture mainframes, introduced by IBM in October 2000. It derives from and is the successor to OS/390, which in turn was preceded by a string of MVS versions. Like OS/390, z/OS combines a number of formerly separate, related products, some of which are still optional. z/OS has the attributes of modern operating systems but also retains much of the older functionality that originated in the 1960s and is still in regular use—z/OS is designed for backward compatibility.

<span class="mw-page-title-main">CICS</span> IBM mainframe transaction monitor

IBM CICS is a family of mixed-language application servers that provide online transaction management and connectivity for applications on IBM mainframe systems under z/OS and z/VSE.

A logical partition (LPAR) is a subset of a computer's hardware resources, virtualized as a separate computer. In effect, a physical machine can be partitioned into multiple logical partitions, each hosting a separate instance of an operating system.

In IBM System/390 and IBM Z mainframe computers, a Coupling Facility or CF is a piece of computer hardware or virtual machine that coordinates multiple processors.

<span class="mw-page-title-main">IBM System z9</span> Line of mainframe computers

IBM System z9 is a line of IBM mainframe computers. The first models were available on September 16, 2005. The System z9 also marks the end of the previously used eServer zSeries naming convention. It was also the last mainframe computer that NASA ever used.

Dynamic Logical Partitioning (DLPAR), is the capability of a logical partition (LPAR) to be reconfigured dynamically, without having to shut down the operating system that runs in the LPAR. DLPAR enables memory, CPU capacity, and I/O interfaces to be moved nondisruptively between LPARs within the same server.

In IBM System z9 and successor mainframes, the System z Integrated Information Processor (zIIP) is a special purpose processor. It was initially introduced to relieve the general mainframe central processors (CPs) of specific Db2 processing loads, but currently is used to offload other z/OS workloads as described below. The idea originated with previous special purpose processors, the zAAP, which offloads Java processing, and the IFL, which runs Linux and z/VM but not other IBM operating systems such as z/OS, DOS/VSE and TPF. A System z PU is "characterized" as one of these processor types, or as a CP, or SAP. These processors do not contain microcode or hardware features that accelerate their designated workloads. Instead, by relieving the general CP of particular workloads, they often lead to a higher workload throughput at reduced license fees.

IBM Z Family of mainframe computers

IBM Z is a family name used by IBM for all of its z/Architecture mainframe computers. In July 2017, with another generation of products, the official family was changed to IBM Z from IBM z Systems; the IBM Z family now includes the newest model, the IBM z16, as well as the z15, the z14, and the z13, the IBM zEnterprise models, the IBM System z10 models, the IBM System z9 models and IBM eServer zSeries models.

Global Resource Serialization (GRS) is the component within the IBM z/OS operating system responsible for enabling fair access to serially reusable computing resources, such as datasets and tape drives or virtual resources, such as lists, queues, and control blocks. Programs can request exclusive access to a resource, usually requested when a program needs to update the resource or shared access, usually requested when a program only needs to query the state of the resource. GRS manages all requests in FIFO order.

In IBM mainframes, a Cross-system Coupling Facility, or XCF, is a component of z/OS that manages communications between applications in a sysplex. Applications may be on the same system or different systems.

On IBM mainframes running the z/OS operating system, Intelligent Resource Director (IRD) is software that automates the management of CPU resources and certain I/O resources.

In IBM mainframes, Workload Manager (WLM) is a base component of MVS/ESA mainframe operating system, and its successors up to and including z/OS. It controls the access to system resources for the work executing on z/OS based on administrator-defined goals. Workload Manager components also exist for other operating systems. For example, an IBM Workload Manager is also a software product for AIX operating system.

<span class="mw-page-title-main">IBM System z10</span> Line of mainframe computers

IBM System z10 is a line of IBM mainframes. The z10 Enterprise Class (EC) was announced on February 26, 2008. On October 21, 2008, IBM announced the z10 Business Class (BC), a scaled-down version of the z10 EC. The System z10 represents the first model family powered by the z10 quad core processing engine. Its successors are the zEnterprise System models introduced in 2010 and 2012.

HiperDispatch is a workload dispatching feature found in recent IBM mainframe models running recent releases of z/OS. HiperDispatch was introduced in February 2008. Support was added to z/VM in its V6R3 release on July 26, 2013.

IBM WebSphere Application Server for z/OS is one of the platform implementations of IBM's WebSphere Application Server family. The latest version is Version 9.0.

<span class="mw-page-title-main">IBM System/390</span> Line of mainframe computers

The IBM System/390 is a discontinued mainframe product family implementing ESA/390, the fifth generation of the System/360 instruction set architecture. The first computers to use the ESA/390 were the Enterprise System/9000 (ES/9000) family, which were introduced in 1990. These were followed by the 9672, Multiprise, and Integrated Server families of System/390 in 1994–1999, using CMOS microprocessors. The ESA/390 succeeded ESA/370, used in the Enhanced 3090 and 4381 "E" models, and the System/370 architecture last used in the IBM 9370 low-end mainframe. ESA/390 was succeeded by the 64-bit z/Architecture in 2000.

References

  1. ↑ "S/390 Parallel Sysplex Overview". Announcement Letters. IBM. April 6, 1994. 194-080.
  2. ↑ "IBM S/390 Coupling Facility 9674 Model C01". Announcement Letters. IBM. April 6, 1994. 194-082.
  3. ↑ "S/390 Parallel Sysplex Offering". Announcement Letters. IBM. April 6, 1994. 194-081.
  4. ↑ "IBM ES/9000 Water-Cooled Processor Enhancements: New Ten-Way Processor, Parallel Sysplex Capability, and Additional Functions". Announcement Letters. IBM. April 6, 1994. 194-084.
  5. ↑ "IBM Enterprise System/9000 Air-Cooled Processors Enhanced with Additional Functions and Parallel Sysplex Capability". Announcement Letters. IBM. April 6, 1994. 194-084.
  6. ↑ "IBM MVS/ESA SP Version 5 Release 1 and OpenEdition Enhancements". Announcement Letters. IBM. April 6, 1994. 294-152.
  7. ↑ System/390 Parallel Sysplex Performance (PDF) (Fourth ed.). International Business Machines Corporation. December 1998. SG24-4356-03. Archived from the original (PDF) on 2011-05-18. Retrieved 2007-09-17.
  8. ↑ David Raften (November 2019). "Coupling Facility Configuration Options". Positioning paper. IBM. ZSW01971USEN.
  9. ↑ "Coupling Facility Definition". PC Magazine.com. Archived from the original on December 2, 2008. Retrieved April 13, 2009.
  10. ↑ "Coupling Facility" (PDF). Archived from the original (PDF) on July 17, 2011. Retrieved April 13, 2009.
  11. ↑ "Migrate from a Sysplex Timer to STP". IBM. Retrieved April 15, 2009.
  12. ↑ "Sysplex Timer". Symmetricom. Retrieved April 15, 2009.
  13. ↑ "IBM Server Time Protocol (STP)". IBM. Archived from the original on June 13, 2008. Retrieved April 15, 2009.
  14. ↑ Johnson, John E. "MVS Boot Camp: IBM Health Checker". z/Journal. Retrieved April 15, 2009.[ permanent dead link ]
  15. ↑ "IBM's System Journal on S/390 Parallel Sysplex Clusters". Archived from the original on 9 March 2012. Retrieved 24 April 2017.
  16. ↑ Server Time Protocol Planning Guide (PDF) (Fourth ed.). International Business Machines Corporation. June 2013. SG24-7280-03.{{cite book}}: |work= ignored (help)
  17. ↑ Ahmad, Riaz (March 5, 2009). GDPS 3.6 Update & Implementation. Austin, TX: SHARE. Retrieved April 17, 2009.[ permanent dead link ]
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.