0% found this document useful (0 votes)

142 views

Parallel Sysplex Overview

Uploaded by

gborja8881331

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

142 views

Parallel Sysplex Overview

Uploaded by

gborja8881331

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 88

GC28-1860-03

OS/390

Parallel Sysplex Overview:

Introducing Data Sharing and
Parallelism in a Sysplex
IBM
GC28-1860-03
OS/390

Parallel Sysplex Overview:

Introducing Data Sharing and
Parallelism in a Sysplex
Note: Before using this information and the products it supports, be sure to read the general information under “Notices” on
page ix.

Fourth Edition, December, 1998

This is a major revision of GC28-1860-02.

This edition applies to Parallel Sysplex environment function that includes System/390 data sharing and parallelism. The Parallel
Sysplex uses the MVS/ESA SP Version 5 or the OS/390 operating system.

Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the
address below.

IBM welcomes your comments. A form for readers' comments may be provided at the back of this publication, or you may address
your comments to the following address:
International Business Machines Corporation
Department 55JA, Mail Station P384
522 South Road
Poughkeepsie, NY 12601-5400
United States of America

FAX (United States & Canada): 1+914+432-9405

FAX (Other Countries):
Your International Access Code +1+914+432-9405

IBMLink (United States customers only): IBMUSM10(MHVRCFS)

IBM Mail Exchange: USIB6TC9 at IBMMAIL
Internet e-mail: [email protected]
World Wide Web: http://www.s390.ibm.com/os390/

If you would like a reply, be sure to include your name, address, telephone number, or FAX number.

Make sure to include the following in your comment or note:

Title and order number of this book
Page number or topic related to your comment

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.

 Copyright International Business Machines Corporation 1994, 1998. All rights reserved.
Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Who Should Use This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Notes on Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Notes on Product Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Determining If a Publication Is Current . . . . . . . . . . . . . . . . . . . . . . xiv
Where to Find More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
| Task Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
| Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
| Parallel Sysplex Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
| Getting Started Parallel Sysplex Publications . . . . . . . . . . . . . . . . . xxvi
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Introduction to Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
What is a Sysplex? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Sysplex Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Sysplex Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Why Sysplex? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
An Evolutionary Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Single System Uniprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Tightly Coupled Multiprocessors . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Loosely Coupled Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Base Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Parallel Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Data Sharing in a Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Data Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Data Validity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Multisystem Data Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Using a Single Data Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Partitioning Data Across Multiple Systems . . . . . . . . . . . . . . . . . . 13
Sharing Data Between Two Systems . . . . . . . . . . . . . . . . . . . . . 14
Sharing Data Using the Coupling Facility Technology . . . . . . . . . . . 15
The Coupling Facility Technology . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Exploiters of the Coupling Facility . . . . . . . . . . . . . . . . . . . . . . . . . 17
Other Exploiters of the Coupling Facility . . . . . . . . . . . . . . . . . . . 18

Parallel Processing in a Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . 19

What is Parallel Processing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Problems Solved by Parallel Processing . . . . . . . . . . . . . . . . . . . . . 20
Running Work in Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Online Transaction Processing (OLTP) . . . . . . . . . . . . . . . . . . . . . . 24
Software that Enables Parallelism for OLTP . . . . . . . . . . . . . . . . . . . . 24
Transaction Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

 Copyright IBM Corp. 1994, 1998 iii

Data Management Systems . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Managing Work in a Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Defining Performance Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Hardware that Enables Parallel Processing . . . . . . . . . . . . . . . . . . . . . 29

Products in a Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Coupling Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Coupling Facility Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
System/390 Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Sysplex Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Enterprise Systems Connection (ESCON) . . . . . . . . . . . . . . . . . . . . 32
ESCON Control Units and I/O Devices . . . . . . . . . . . . . . . . . . . . . . 33
System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
MVS/ESA or OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
JES2 or JES3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
DFSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Networking Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Virtual Telecommunications Access Method (VTAM) . . . . . . . . . . . . . 34
Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Information Management System Database Manager (IMS DB:) . . . . . . . 34
DATABASE 2 (DB2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Virtual Storage Access Method (VSAM) - component of DFSMS . . . . . . . 34
Transaction Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Customer Information Control System (CICS/ESA and CICS Transaction
Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Information Management System Transaction Manager (IMS TM) . . . . . . 35
Systems Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
System Management Facilities (SMF) - component of MVS . . . . . . . . 35
Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
CICSPlex System Manager/ESA (CICSPlex SM) . . . . . . . . . . . . . . 35
Operations Planning and Control (OPC/ESA) . . . . . . . . . . . . . . . . 35
Workload Manager (WLM) - component of MVS . . . . . . . . . . . . . . 35
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
System Automated for OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . 35
Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . 36
System Display and Search Facility (SDSF) . . . . . . . . . . . . . . . . . 36
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Resource Measurement Facility (RMF) . . . . . . . . . . . . . . . . . . . . 36
Enterprise Performance Data Manager/MVS (EPDM) . . . . . . . . . . . . 36
Service Level Reporter (SLR) . . . . . . . . . . . . . . . . . . . . . . . . . 36
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Resource Access Control Facility (RACF) or the Security Server . . . . . 36
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
System Automation for OS/390 . . . . . . . . . . . . . . . . . . . . . . . . 37
Hardware Configuration Definition (HCD) . . . . . . . . . . . . . . . . . . . 37

Introduction to Sample Sysplex Configurations . . . . . . . . . . . . . . . . 39

Large Systems Data Sharing Sysplex . . . . . . . . . . . . . . . . . . . . . . . . 39
S/390 Microprocessor Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Mixed Processor Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

iv OS/390 V2R5.0 Parallel Sysplex Overview

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Sources of Terms and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Explanation of Cross-References . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Contents v
vi OS/390 V2R5.0 Parallel Sysplex Overview
Figures
1. Parallel Sysplex Library Books . . . . . . . . . . . . . . . . . . . . . . . . . xv
2. Sysplex Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. A Uniprocessor with One MVS Image . . . . . . . . . . . . . . . . . . . . . 5
4. A Tightly Coupled Multiprocessor . . . . . . . . . . . . . . . . . . . . . . . . 6
5. A Loosely Coupled Configuration . . . . . . . . . . . . . . . . . . . . . . . . 7
6. A Base Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7. A Parallel Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Data Sharing with a Single Data Server . . . . . . . . . . . . . . . . . . . 13
9. Data Sharing with Partitioned Data . . . . . . . . . . . . . . . . . . . . . . 14
10. Data Sharing Between Two Systems . . . . . . . . . . . . . . . . . . . . 15
11. Sysplex Data Sharing Using the Coupling Facility . . . . . . . . . . . . . . 16
12. Multiprocessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
13. Workload that Exceeds Processing Capability . . . . . . . . . . . . . . . . 21
14. Increasing Throughput for a Workload . . . . . . . . . . . . . . . . . . . . 21
15. Processing a Lengthy Application . . . . . . . . . . . . . . . . . . . . . . . 22
16. Decreasing the Processing Time of a Lengthy Application . . . . . . . . . 23
17. Parallel OLTP Applications in a Single System . . . . . . . . . . . . . . . 25
18. Parallel OLTP Applications in a Sysplex Parallel Environment . . . . . . 26
19. Products in a Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
20. Large Systems Sysplex Configuration . . . . . . . . . . . . . . . . . . . . 40
21. Sysplex in a S/390 Microprocessor Cluster Configuration . . . . . . . . . 41
22. Mixed Processor Sysplex Configuration . . . . . . . . . . . . . . . . . . . 42

 Copyright IBM Corp. 1994, 1998 vii

viii OS/390 V2R5.0 Parallel Sysplex Overview
Notices
References in this publication to IBM products, programs, or services do not imply
that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only IBM's product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any of IBM's
intellectual property rights may be used instead of the IBM product, program, or
service. Evaluation and verification of operation in conjunction with other products,
except those expressly designated by IBM, is the user's responsibility.

IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries in writing to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504–1785
U.S.A.

Licensees of this program who wish to have information about it for the purpose
enabling: (i) the exchange of information between independently created programs
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:

IBM Corporation
Mail Station P300
522 South Road
Poughkeepsie, NY 12601-5400
U.S.A.
Attention: Information Request

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

 Copyright IBM Corp. 1994, 1998 ix

x OS/390 V2R5.0 Parallel Sysplex Overview
Trademarks
The following terms are trademarks of the IBM Corporation in the United States
and/or other countries:
Advanced Peer-to-Peer Networking
APPN
BookManager
CBPDO
CICS
CICS/ESA
CICSPlex
DATABASE 2
DB2
DFSMS
DFSMS/MVS
Enterprise Systems Connection Architecture
ES/9000
ESCON
Hardware Configuration Definition
IBM
IBMLink
IMS
IMS/ESA
MVS/ESA
NetView
OPC
OpenEdition
OS/2
OS/390
Parallel Sysplex
Processor Resource/Systems Manager
PR/SM
RACF
Resource Measurement Facility
RMF
S/390
SP
Sysplex Timer
System/390
SystemView
VisualLift
VTAM

 Copyright IBM Corp. 1994, 1998 xi

xii OS/390 V2R5.0 Parallel Sysplex Overview
About This Publication
This publication is about System/390 data sharing and parallelism in a sysplex and
how it can meet the needs of your computing environment.

It introduces high-level concepts and information useful for anyone who will plan
for, exploit, implement, or operate a sysplex that shares data and processes work
in parallel.

This publication describes:

What a sysplex is and how it compares to existing non-sysplex computing
environments
New features that enhance sysplex function
Work that a sysplex supports
Products that make up a sysplex
Various sysplex configurations and their benefits
Sysplex and Product Availability (“Roll-Out”): The sysplex is a large system
computing environment that is evolving. Since the introduction of the
sysplex, the coupling facility technology was developed to enhance sysplex
capabilities. With a coupling facility in a sysplex, the participating MVS
systems can do high performance data sharing. A sysplex with a coupling
facility is called a Parallel Sysplex.

Note that this publication does not differentiate between a sysplex

without a coupling facility and a sysplex with a coupling facility. When
you see the term sysplex, understand it to mean a sysplex with a
coupling facility (a Parallel Sysplex).

The roll-out of sysplex support across products is occurring over time, in

phases. This publication discusses primarily those functions that are either
available or announced. Where possible, however, functions planned for
follow-on phases are included to give you an opportunity to do strategic
planning. Note that information about follow-on phases represents IBM's
intent, and is subject to change or withdrawal.

There might be changes to the implementation or availability of new

products or functions. For information about availability of hardware and
software sysplex support, consult your IBM representative.

Who Should Use This Publication

This publication is intended for anyone who wants an introduction to data sharing
and parallelism in a sysplex. It discusses sysplex evolution, purpose, benefits,
products, and services (hardware and software). The reader can be an executive,
technical consultant, information systems manager, technical planner, or system
programmer.

 Copyright IBM Corp. 1994, 1998 xiii

Notes on Terminology
Please note the following regarding terminology in this publication:
When you see the term Parallel Sysplex, understand it to mean a sysplex with
a coupling facility, which is a Parallel Sysplex.
When you see the term MVS in this book, understand it to mean either the
MVS/ESA product or an element of OS/390.
The first time a product is referenced in the text, its entire name is spelled out
and its acronym specified. From then on, only the acronym is used. For quick
reference, the glossary contains product acronyms used in this publication, and
what they stand for.
The term system is one that is used heavily in many publications to mean
many different things. Often you must attempt to discern its exact meaning from
the context in which it is used. This publication uses the term system to mean
an MVS system. Here are some important definitions:

MVS system. An MVS image together with its associated hardware, which
collectively are often referred to simply as a system, or MVS system.

MVS image. A single occurrence of the operating system that has the ability
to process work.

In this publication, the licensed program DB2 for MVS/ESA is referred to as

DB2.
In this publication, the licensed program CICS Transaction Server for OS/390 is
called CICS Transaction Server and refers to the product that contains
Customer Information Control System (CICS), CICSPlex Systems Management
(CICSPLex SM), and others.
The licensed program System Automation for OS/390 includes all of the
function previously provided by the program products Automated Operations
Control/MVS (AOC/MVS), Target System Control Facility (TSCF), and ESCON
Manager.

Notes on Product Availability

The term “follow-on phase” will be used whenever discussing function planned to
be available in future phases of the roll-out of sysplex support across products. If
“follow-on phase” is not specified, assume that the function is available or
announced. Note that the information about follow-on phases represents IBM's
intent, and is subject to change or withdrawal.

Determining If a Publication Is Current

As needed, IBM updates its publications with new and changed information. For a
given publication, updates to the hardcopy and associated BookManager softcopy
are usually available at the same time. Sometimes, however, the updates to
hardcopy and softcopy are available at different times. Here's how to determine if
you are looking at the most current copy of a publication:
1. At the end of a publication's order number there is a dash followed by two
digits, often referred to as the dash level. A publication with a higher dash level

xiv OS/390 V2R5.0 Parallel Sysplex Overview

is more current than one with a lower dash level. For example, a dash level -01
means that the publication is more current than the previous level, -00.
2. If a hardcopy publication and a softcopy publication have the same dash level,
it is possible that the softcopy publication is more current than the hardcopy
publication. Check the dates shown in the Summary of Changes. The softcopy
publication might have a more recently dated Summary of Changes than the
hardcopy publication.
3. To compare softcopy publications, you can check the last two characters of the
publication's filename (also called the book name). The higher the number,
the more recent the publication. For example, E0S1P103 is more recent than
E0S1P102. Also, next to the publication titles in the CD-ROM booklet and the
README files, there is a change code (N, E, S, or T) that indicates whether a
publication is new or changed, as follows:
N=new
E=softcopy enhancement
S=service change
T=technical change

Where to Find More Information

This publication is part of a library of Parallel Sysplex planning books. IBM strongly
recommends that you read each of the books in this library before you begin
planning your Parallel Sysplex. Here is the complete list of publications in the
Parallel Sysplex planning library, along with their order numbers:

Figure 1. Parallel Sysplex Library Books

Order
Publication Title Number Description
OS/390 Parallel Sysplex GC28-1860 Use this publication as an overview to the sysplex and coupling
Overview facility data sharing. It describes highlights and the value of the
sysplex to your business.
OS/390 Parallel Sysplex GC28-1861 Use this publication to understand planning considerations for
Systems Management systems management in the sysplex, including business,
change, configuration, operations, performance, and problem
management.
OS/390 Parallel Sysplex GC28-1862 Use this publication to plan for hardware and software
Hardware and Software migration to a Parallel Sysplex that uses the coupling facility for
Migration the purpose of data sharing.
OS/390 Parallel Sysplex GC28-1863 Use this publication to understand planning considerations for
Application Migration the parallel processing of applications that run on Customer
Information Control System (CICS)/ESA and Information
Management System (IMS)/ESA software in the Parallel
Sysplex.

About This Publication xv

| Task Roadmap
| The following list of tasks and books can help you start to understand, plan, and
| implement a Parallel Sysplex. You can use it as a task roadmap to guide you
| through information for the Parallel Sysplex, including program product information
| for CICS Transaction Server (CICS TS), IMS/ESA, and DB2.

| Getting Started
| This topic describes planning and implementing tasks for the Parallel Sysplex. Each
| task refers to books that you can select to obtain task specific information. If you
| are using the OS/390 CD Collection Kit (SK2T-6700-11 or later), select the book,
| and BookManager places you in the Table of Contents for that book. Under each
| book in the task list, you can also find the appropriate topic within the book that
| helps you locate specific details for the task.

| Parallel Sysplex Tasks

| The following tasks are included in the task roadmap:
| “Planning the Parallel Sysplex”
| “Migrating to a Parallel Sysplex” on page xvii
| “Planning for Availability” on page xviii
| “Planning Capacity” on page xviii
| “Planning for Connectivity” on page xviii
| “Planning Performance” on page xviii
| “Planning for Workloads” on page xviii
| “Planning for Security” on page xix
| “Planning for Automation” on page xix
| “Cloning Systems and Images” on page xix
| “Planning for the Coupling Facility” on page xx
| “Developing Naming Conventions for Data Sharing Products” on page xx
| “Planning and Implementing Parallel Sysplex Policies” on page xxi
| “Installing the Parallel Sysplex” on page xxii
| “Planning the Network Configuration for the Parallel Sysplex” on page xxiii
| “Setting up Data Sharing” on page xxiii
| “Planning Day-to-Day Operations” on page xxiv
| “Planning Recovery” on page xxv
| “Developing Applications” on page xxvi

| Planning the Parallel Sysplex

| Designing the Parallel Sysplex

| OS/390 MVS Parallel Sysplex Configuration, Volume 1: Overview
| – "High Level Design Concepts for the Parallel Sysplex"

xvi OS/390 V2R5.0 Parallel Sysplex Overview

| Selecting Software - Overview

| OS/390 Parallel Sysplex Hardware and Software Migration
| – "Overview of Sysplex Software"
| DB2 Data Sharing: Planning and Administration
| – "Software and Hardware Requirements"
| IMS/ESA Common Queue Server (CQS) Guide and Reference
| – "Hardware and Software Requirements

| Migrating to a Parallel Sysplex

| Migrating to OS/390 - Overview
| OS/390 Parallel Sysplex Hardware and Software Migration
| – "Introduction to Parallel Sysplex Migration Tasks"
| S/390 Parallel Sysplex Migration Paths
| – "Understanding Parallel Sysplex Migration Options"
| OS/390 Parallel Sysplex Test Report
| This document is a quarterly report written by a team of IBM S/390 testers and
| system programmers. The team runs a Parallel Sysplex that migrates to each
| release of OS/390, and does IMS, DB2, and VSAM RLS data sharing using
| both CICS and IMS as transaction managers. The report provides details and
| examples of the team's setup and migration experiences, along with hints and
| tips. All editions of the report are available on the team's Web site at
| http://www.s39ð.ibm.com/os39ð/support/os39ðtst/

| Migrating Applications to a Parallel Sysplex

About This Publication xvii

| Planning Capacity
| OS/390 Parallel Sysplex Capacity Planning
| – "Capacity Planning in a Parallel Sysplex"

| Planning for Connectivity

| Parallel Sysplex Configuration, Volume 3: Connectivity
| – "Connectivity in a Parallel Sysplex"

| Planning Performance
| Analyzing and Improving Performance - Overview
| S/390 Parallel Sysplex Performance
| – "Overview of Parallel Sysplex Performance"

| Monitoring Performance in a Parallel Sysplex

| Planning for Workloads

xviii OS/390 V2R5.0 Parallel Sysplex Overview

| – "Workload Management Participants"
| – "Migrating to Workload Management"

| Planning for Security

| Planning for Automation

| Cloning Systems and Images

| OS/390 Parallel Sysplex Systems Management
| – "Configuration Planning"
| OS/390 Parallel Sysplex Application Migration
| – "Planning the Subsystem Configuration for a Sysplex"
| IMS/ESA Administration Guide: Transaction Manager
| – "Part 1. Administering an IMS Transaction Manager Network"
| – "Part 2. Administering the Extended Terminal Option"
| – "Part 3. Administering Multiple Systems Coupling"
| – "Part 5. Administering IMS in a Client/Server Environment"
| IMS/ESA Operations Guide
| – "Making Online Changes"

About This Publication xix

| Planning for the Coupling Facility
| Understanding Coupling Facility Concepts and Options
| OS/390 Parallel Sysplex Hardware and Software Migration
| – "Coupling Facility"
| – "Availability of Coupling Facility Data in the Sysplex"
| Parallel Sysplex Configuration, Volume 2: Cookbook
| – "A Structured View of CF Structures"

| Understanding Coupling Facility Levels and Functions for Hardware and

| Software
| PR/SM Planning Guide
| – "Coupling Facility Level (CFLEVEL) Considerations"

| Planning the Sizing of Structures

| Shutting down the Coupling Facility and Removing Structures

| OS/390 Parallel Sysplex Systems Management
| – "Actions to Remove a Coupling Facility from a Sysplex"
| – "Actions to Remove a Structure from a Coupling Facility"
| OS/390 Parallel Sysplex Systems Management
| – "Sharing Software Resources"
| – "Implementing Effective Naming Conventions"
| – "Sharing and Placement of Data Sets"

| Developing Naming Conventions for Data Sharing Products

| OS/390 Parallel Sysplex Application Migration
| – "Planning Naming Conventions for CICS and Related Subsystems"
| DB2 Data Sharing: Planning and Administration
| – "Planning a Naming Convention"
| IMS/ESA Release Planning Guide
| – "Ensuring Consistency across IMS Systems"

xx OS/390 V2R5.0 Parallel Sysplex Overview

| Planning and Implementing Parallel Sysplex Policies
| Creating the SFM policy
| OS/390 MVS Parallel Sysplex Configuration, Volume 1: Overview
| – "Sysplex Failure Management (SFM)"
| OS/390 MVS Setting Up a Sysplex
| – "Controlling System Availability and Recovery through the SFM Policy"

| Creating the ARM policy

| Implementing the WLM policy

| Creating the CFRM policy

| OS/390 MVS Setting Up a Sysplex
| – "Planning a Coupling Facility Policy"

About This Publication xxi

| Installing the Parallel Sysplex

| Installing the Sysplex Foundation
| OS/390 Parallel Sysplex Hardware and Software Migration
| – Planning Basic Sysplex Hardware and Software - General Steps
| – Planning Basic Sysplex Hardware and Software - Detailed Steps

| Defining Data Sets

| Defining Signalling
| OS/390 MVS Setting Up a Sysplex
| – "Planning Signalling Services in a Sysplex"

| Defining JES2
| OS/390 JES2 Initialization and Tuning Guide
| – "JES2 Initialization"

| Defining JES3
| OS/390 JES3 Initialization and Tuning Guide
| – "Initializing JES3"

xxii OS/390 V2R5.0 Parallel Sysplex Overview

| Defining Global Resource Serialization
| OS/390 MVS Planning: Global Resource Serialization
| – "Part 1 - Global Resource Serialization"
| – "Part 2 - Global Resource Serialization Star"
| Parallel Sysplex Configuration, Volume 2: Cookbook
| – "GRS Star Structures"

| Defining DFSMS and the SMS Configuration

| DFSMS/MVS DFSMSdfp Storage Administration Reference
| – "Introducing the Storage Management Subsystem"
| – "Calculating the Size of Storage and Active Control Data Sets"
| – "Defining Storage Groups"

| Planning the Network Configuration for the Parallel Sysplex

| Parallel Sysplex Configuration, Volume 3: Connectivity
| – "Network Connectivity for Parallel Sysplex"
| VTAM in a Parallel Sysplex Environment
| – "The Sysplex Networking Environment"

| Setting up Data Sharing

| Planning and Implementing CICS Data Sharing

| Planning and Implementing IMS Data Sharing

| OS/390 Parallel Sysplex Application Migration
| – "Migrating IMS Applications"
| IMS/ESA Installation Volume 2: System Definition and Tailoring
| – "Defining Coupling Facility Structure Names for Sysplex Data Sharing"
| IMS/ESA Administration Guide: System
| – "Administering Sysplex Data Sharing"

About This Publication xxiii

| Planning and Implementing DB2 Data Sharing
| DB2 Data Sharing: Planning and Administration
| – "Installing and Enabling DB2 Data Sharing"

| Planning and Implementing VSAM RLS Data Sharing

| Planning Day-to-Day Operations

| Starting and Stopping Systems
| OS/390 MVS Setting Up a Sysplex
| – "Adding MVS Systems to a Sysplex"
| OS/390 Program Directory
| This document provides overview and procedural information on both the
| planned and unplanned removal of an MVS system from a Parallel Sysplex.

| Starting and Stopping Subsystems

xxiv OS/390 V2R5.0 Parallel Sysplex Overview

| Managing Hardware and Software
| OS/390 Parallel Sysplex Systems Management
| – "Operations Planning"
| – "Summary of Parallel Sysplex Systems Management"

| Monitoring the Parallel Sysplex

| Planning Recovery
| Performing Problem Determination
| OS/390 Parallel Sysplex Systems Management
| – "Planning for Problem Management"

| Recovering from Problems

About This Publication xxv

| Getting Started Parallel Sysplex Publications

| The following publications contain important information for planning and
| implementing the Parallel Sysplex. They are listed in alphabetical order.

| ITSO Publications
| Automation for S/390 Parallel Sysplex
| CICS and VSAM Record Level Sharing: Implementation Guide
| Getting the Most Out of a Parallel Sysplex
| IMS/ESA Sysplex Data Sharing: An Implementation Case Study
| OS/390 Parallel Sysplex Capacity Planning
| OS/390 MVS Parallel Sysplex Configuration, Volume 1: Overview
| Parallel Sysplex Configuration, Volume 2: Cookbook
| Parallel Sysplex Configuration, Volume 3: Connectivity
| OS/390 Parallel Sysplex Application Considerations Presentation Guide
| S/390 Parallel Sysplex Migration Paths
| S/390 Parallel Sysplex Performance
| VTAM in a Parallel Sysplex Environment

| Hardware Publications
| PR/SM Planning Guide

| CICS Transaction Server Publications

| CICS Transaction Server for OS/390 Installation Guide
| CICS Operations and Utilities Guide
| CICS Recovery and Restart Guide

| CICSPlex Systems Management Publications

| CICSPlex SM Managing Workloads

| DB2 Publications
| DB2 Administration Guide
| DB2 Data Sharing: Planning and Administration
| DB2 Installation Guide

xxvi OS/390 V2R5.0 Parallel Sysplex Overview

| DFSMS/MVS Publications
| DFSMS/MVS DFSMSdfp Storage Administration Reference

| Parallel Sysplex Planning Publications

Acknowledgements
The IBM Sysplex Information Development team would like to express its
appreciation to all the people who helped make this publication possible.

Because a sysplex is made up of many types of products, presenting a high-level,

cross-product view required a great deal of cooperation. Scores of people —
including writers, editors, product designers, developers and testers — from many
IBM sites worked together to develop and review this information. Additionally, we
worked with customers to validate the relevance of topics presented and to
maintain an appropriate level of detail for the intended audience.

To everyone who contributed, our sincere thanks.

About This Publication xxvii

xxviii OS/390 V2R5.0 Parallel Sysplex Overview
Summary of Changes
| Summary of Changes
| for GC28-1860-03
| as Updated December, 1998
| online only for SK2T-6700-11

| The following changes appear only in the online version of this publication. A
| vertical line ( | ) in the left margin indicates changes to the text and illustrations.

| This revision includes a task roadmap for Parallel Sysplex information. The task
| roadmap can guide you through information for the Parallel Sysplex, including
| program product information for CICS Transaction Server (CICS TS), IMS/ESA, and
| DB2. See “Task Roadmap” on page xvi.

| This revision reflects the deletion, addition, or modification of information to support

| miscellaneous maintenance items.

Summary of Changes
for GC28-1860-02
OS/390 Release 2 Release 4

This publication contains information previously presented in:

OS/390 Parallel Sysplex Overview: Introducing Data Sharing and Parallelism in
a Sysplex, GC28-1860-01
This edition contains updates for OS/390 Release 4 and MVS/ESA SP Version 5 as
well as maintenance and editorial changes. In addition, it contains new information
for the following:
System Automation for OS/390

Technical changes or additions to the text and illustrations are indicated by a

vertical line to the left of the change.

Summary of Changes
for GC28-1860-01
OS/390 Release 2

This publication contains information previously presented in:

OS/390 Parallel Sysplex Overview: Introducing Data Sharing and Parallelism in
a Sysplex GC28-1860-00.
This edition contains updates for OS/390 Release 2 and MVS/ESA SP Version 5 as
well as maintenance and editorial changes.

Technical changes or additions to the text and illustrations are indicated by a

vertical line to the left of the change.

Summary of Changes
for GC28-1860-00
as Updated June, 1996
online only for SK2T-6700-01

 Copyright IBM Corp. 1994, 1998 xxix

The following changes appear only in the online version of this publication. A pair of
vertical dots ( : ) in the left margin indicates changes to the text and illustrations.

This revision reflects the deletion, addition, or modification of information to support

miscellaneous maintenance items.

Summary of Changes
for GC28-1860-00
OS/390 Release 1

This publication contains information previously presented in:

System/390 Sysplex Overview: Introducing Data Sharing and Parallelism in a
Sysplex GC28-1208
This edition contains updates for OS/390 and MVS/ESA SP Version 5 as well as
maintenance and editorial changes.

Technical changes or additions to the text and illustrations are indicated by a

vertical line to the left of the change.

xxx OS/390 V2R5.0 Parallel Sysplex Overview

Introduction to Sysplex
The word sysplex might not be new to you. The MVS/ESA sysplex has been
available since 1990 when it was announced as a platform for an evolving large
system computing environment.

What's new is what a sysplex can now do for you. It's more than a platform. It has
become the large system computing environment that offers you improved
price/performance through cost effective processor technology and enhanced
software. This technology builds on existing data processing skills and will run
existing applications—an additional cost saver. A sysplex can also increase system
availability, and at the same time, it increases your potential for doing more work.

In case you're not sure what a sysplex is, this chapter starts with a definition of a
sysplex, and then describes the new capabilities of a sysplex and why you might be
interested in it.

What is a Sysplex?
A sysplex is a collection of MVS systems that cooperate, using certain hardware
and software products, to process work. A conventional large computer system also
uses hardware and software products that cooperate to process work. A major
difference between a sysplex and a conventional large computer system is the
improved growth potential and level of availability in a sysplex. The sysplex
increases the number of processing units and MVS operating systems that can
cooperate, which in turn increases the amount of work that can be processed. To
facilitate this cooperation, new products were created and old products were
enhanced.

The following diagram shows the visible parts of a sysplex, namely the hardware.
The software, which helps to enable the interaction and cooperation among the
systems, is described later.

 Copyright IBM Corp. 1994, 1998 1

Figure 2. Sysplex Structure

2 OS/390 V2R5.0 Parallel Sysplex Overview

Sysplex Hardware
The following types of hardware participate in a sysplex.

Coupling Facility: The Coupling Facility enables high performance multisystem

data sharing.

Coupling Facility Channels: Coupling facil provide high speed connectivity

between the Coupling Facility and the central processor complexes (CPCs) that use
it.

Sysplex Timers: A Sysplex Timer synchronizes the time-of-day (TOD) clocks in

multiple CPCs in a sysplex.

System/390 Processors: Selected models of S/390 processors can take

advantage of a sysplex. These include large water-cooled processors, air-cooled
processors, and microprocessor cluster.

ESCON Channels and Directors: Enterprise Systems Connection (ESCON)

channels enhance data access and communication in the sysplex. The ESCON
Directors add dynamic switching capability for ESCON channels.

ESCON Control Units and I/O Devices: ESCON control units and I/O devices in a
sysplex provide the increased connectivity necessary among a greater number of
systems.

Sysplex Software
The following software works with the hardware to enable interaction and
cooperation among systems in a sysplex.

System Software: Base system software that is enhanced to support a sysplex

includes the MVS operating system, JES2 and JES3, and DFSMS).

Networking Software: Virtual Telecommunications Access Method (VTAM)

supports the attachment of a sysplex to a network.

Data Management Software: The data managers that support data sharing in a
sysplex are Information Management System Database Manager (IMS DB),
DATABASE 2 (DB2), and Virtual Storage Access Method (VSAM).

Transaction Management Software: The transaction managers that support a

sysplex are Customer Information Control System (CICS/ESA and CICS
Transaction Server) and Information Management System Transaction Manager
(IMS TM).

Systems Management Software: A number of software products are enhanced to

run in a sysplex and exploit its capabilities. The products manage accounting,
workload, operations, performance, security, and configuration, and they make a
sysplex easier to manage by providing a single point of control.

More information about the specific hardware and software products is available in
“Products in a Sysplex” on page 31.

Introduction to Sysplex 3
Why Sysplex?
Now that you've been introduced to the pieces that make up a sysplex, you might
be wondering what a sysplex could do for you. If your data center is responsible for
even one of the following types of work, you could benefit from a sysplex.
Large business problems—ones that involve hundreds of end users, or deal
with a very large volume of work that can be counted in the millions of
transactions per day.
Work that consists of small work units, such as online transactions, or large
work units that can be subdivided into smaller work units, such as queries.
Concurrent applications on different systems that need to directly access and
update a single database without jeopardizing data integrity and security.

A sysplex shares the processing of work across MVS/ESA systems, and as a result
offers benefits, such as:
Reduced cost through:
– Cost effective processor technology
– Continued use of large system data processing skills without re-education
– Protection of MVS/390 application investments
– The ability to manage a large number of systems more easily than other
comparably performing multisystem environments
Platform for continuous availability so that applications can be available 24
hours a day, 7 days a week, 365 days a year (or close to it)
Ability to do more work
– Greater capacity
– Improved ability to manage response time
– Platform for further capacity and response time advances
Greater flexibility
– Ability to mix levels of hardware and software
– Ability to dynamically add systems
– An easy path for incremental growth
– Varied platforms for applications, including parallel, open, and client/server

Depending on your data center's goals and needs, some of these benefits might be
more attractive to you than others. Your IBM marketing representative will be able
to discuss, in more detail, how a benefit can specifically apply to your situation.

An Evolutionary Approach
A sysplex is the most recent development in the evolution of IBM large systems.
Large system configurations have evolved from a single system uniprocessor
through tightly coupled multiprocessors, to a loosely coupled configuration, to the
sysplex.

4 OS/390 V2R5.0 Parallel Sysplex Overview

Single System Uniprocessor
A system is made up of hardware products including a central processor (CP), and
software products, with the primary one being an operating system such as MVS.
Other types of software—system application programs, end-user application
programs, tools—run on the system. The CP is the functional hardware unit that
interprets and processes program instructions. The CP and other system
hardware, such as channels and storage, make up a central processor complex
(CPC).

The System/390 architecture defines that a single CP process one and only one
instruction from a program at a time. The MVS operating system manages the
instructions to be processed and the resources required to process them. When a
single copy of the MVS operating system (MVS image) manages the processing of
a CPC that has a single CP, the system configuration is called a uniprocessor.

Figure 3. A Uniprocessor with One MVS Image

Summary
Capacity Equal to the size of the largest single CP
Availability Contains single points of failure; disruptive change
Systems Management Easy to manage work

Tightly Coupled Multiprocessors

When you add more CPs to the central processor complex (CPC), you add the
capability of processing program instructions simultaneously. When all the CPs
share central storage and a single MVS image manages the processing, work is
assigned to a CP that is available to do the work. If a CP fails, work can be routed
to another CP. This hardware and software organization is called a tightly coupled
multiprocessor.

A tightly coupled multiprocessor has more than one CP and a single MVS image
sharing central storage. The CPs are managed by the single MVS image, which
assigns work to them.

Introduction to Sysplex 5
Figure 4. A Tightly Coupled Multiprocessor

Summary
Capacity Increased over that of a uniprocessor but limited by the
maximum number of CPs in the CPC
Availability Increased over that of a uniprocessor but limited by
some characteristics, including one system image, that
may represent single points of failure and disruptive
change
Systems Management Easy to manage work

Loosely Coupled Configuration

A tightly coupled multiprocessor provides CP backup in case of failure. But what
about software backup? Can you have more than one MVS image in a
configuration?

Systems outside a sysplex can coordinate more than one MVS image with the MVS
job entry subsystem components (JES2 and JES3) and global resource
serialization. These components establish a means of sharing a work input queue
across a number of systems to allow shared data sets, printers, and consoles. This
type of system configuration is called loosely coupled.

A loosely coupled configuration has more than one CPC, possibly tightly coupled
multiprocessors, sharing DASD but not central storage. The CPCs can connect by
channel-to-channel communications and are managed by more than one MVS
image. Work is distributed from a shared job queue to each MVS.

Although a loosely coupled configuration increases system capacity, it is not as

easy to manage as either a uniprocessor or a tightly coupled multiprocessor. Each
system must be managed separately, often by a human operator, who monitors
product-specific messages on a set of consoles for each system.

Products and applications that need to communicate and are running on separate
systems have to create their own communication mechanism. These varied
communication mechanisms add to the difficulty of managing a loosely coupled
configuration.

6 OS/390 V2R5.0 Parallel Sysplex Overview

Figure 5. A Loosely Coupled Configuration

Summary
Capacity Increased system capacity over tightly coupled
multiprocessors and a uniprocessor
Availability Increased system availability over tightly coupled
multiprocessors and a uniprocessor
Systems Management Requires additional systems management—separate
MVS images communicate to share data sets, printers,
and consoles

Base Sysplex
To help solve the difficulties of managing many MVS systems, IBM introduced the
MVS systems com plex or sysplex in September of 1990. The base sysplex lays
the groundwork for simplified multisystem management through the cross-system
coupling facility (XCF) component of MVS/ESA. XCF services allow authorized
applications on one system to communicate with applications on the same system
or on other systems. In a base sysplex, CPCs connect by channel-to-channel
communications and a shared dataset to support the communication. When more
than one CPC is involved, a Sysplex Timer synchronizes the time on all systems.

The base sysplex is similar to a loosely coupled configuration in that more than one
CPC (possibly a tightly coupled multiprocessor) shares DASD and is managed by
more than one MVS image. A sysplex is different from a loosely coupled
configuration because through XCF, there is a standard communication mechanism
for MVS system applications.

Introduction to Sysplex 7
Figure 6. A Base Sysplex

Summary
Capacity The same system capacity as loosely coupled
Availability The same system availability as loosely coupled
Systems Management Better and simpler systems management than loosely
coupled
Greater degree of communication and cooperation
among systems
Introduction of XCF as a common communication
mechanism that provides high availability
A more unified system image—single MVS console
to manage all components

Parallel Sysplex
Since the introduction of the sysplex, IBM has developed technologies that enhance
sysplex capabilities. The Parallel Sysplex supports a greater number of systems
and significantly improves communication and data sharing among those systems.

High performance communication and data sharing among a large number of MVS
systems could be technically difficult. But with the Parallel Sysplex, high
performance data sharing through a new coupling technology (coupling Facility)
gives high performance multisystem data sharing capability to authorized
applications, such as MVS subsystems. Use of the Coupling Facility by
subsystems, such as Information Management System (IMS), ensures the integrity
and consistency of data throughout the entire sysplex.

The capability of linking together many systems and providing multisystem data
sharing makes the sysplex platform ideal for parallel processing, particularly for
online transaction processing (OLTP) and decision support. More discussion about
parallel processing follows in “Parallel Processing in a Sysplex” on page 19.

In short, a Parallel Sysplex builds on the base sysplex capability, and allows you to
increase the number of CPCs and MVS images that can directly share work. The
Coupling Facility enables high performance, multisystem data sharing across all the

8 OS/390 V2R5.0 Parallel Sysplex Overview

systems. In addition, workloads can be dynamically balanced across systems with
the help of new workload management functions.

Figure 7. A Parallel Sysplex

Summary
Capacity Increased system capacity over loosely coupled and
base sysplex
Ability to add incremental capacity to match workload
growth
Availability Increased system availability over loosely coupled and
base sysplex
Systems Management Better systems management than with the base sysplex
Multisystem data sharing capability
Multisystem workload balancing
Enhanced single-system image

Summary
The unique characteristics of a Parallel Sysplex can allow you to reduce your total
cost of computing over prior offerings of comparable function and performance.
Sysplex design characteristics mean that you can run your business continuously,
even when it is growing or changing. You can dynamically add and change
systems in a sysplex and configure them for no single points of failure. If your
revenue depends on continuously available systems, a sysplex can protect your
revenue. If you need to grow beyond the limits imposed by today's technology, a
sysplex lets you go beyond those limits, and helps you avoid the complex and
expensive splitting and rejoining of data centers.

The innate robustness and reliability of the MVS operating system and System/390
processors are the foundation of a sysplex. That robustness and reliability are
extended to all systems in a sysplex through cross system workload balancing and
data sharing using the coupling technologies. Therefore applications on multiple
systems can be continuously available to end users, yet the applications are
shielded behind a single-system view.

Introduction to Sysplex 9
The applications that run in a sysplex are the same applications you run today.
Reuse of applications and data processing skills reduce the costs of application
development, re-engineering, and retraining.

Therefore, the sysplex can reduce your overall cost of compu now and can
position your data processing center for continued savings in the future.
As You Read On...:

In this introductory chapter, you have seen how large systems have evolved
into a sysplex. The sysplex itself is evolving, and the roll-out of sysplex
support across software products will occur over time. For information about
availability of sysplex software support, consult your IBM marketing
representative.

The rest of this publication will not differentiate between the base sysplex
capability and the Parallel Sysplex capability. When you see the term
sysplex, understand it to mean the Parallel Sysplex with its enhanced
capability.

10 OS/390 V2R5.0 Parallel Sysplex Overview

Data Sharing in a Sysplex
Connecting a large number of systems together brings with it special
considerations, such as how the large number of systems communicate and how
they cooperate to share resources. These considerations affect the overall
operation of MVS systems.

A sysplex significantly changes the way MVS systems can share data. As the
number of systems increase, it is essential to have an efficient way to share data
across systems. The Coupling Facility enables centrally accessible, high
performance data sharing for authorized applications, such as subsystems and
MVS components, that are running in a sysplex. These subsystems and
components then transparently extend the benefits of data sharing to their
applications.

Use of the Coupling Facility substantially improves the feasibility of connecting

many MVS systems together in a sysplex to process work in parallel.

This chapter describes:

Multisystem data sharing
The Coupling Facility and its exploiters

Data Sharing
Data sharing is not new. Different applications within a system often need to access
the same information, sometimes to read it and other times to update it. Sometimes
several copies of the data exist and with that comes the requirement of keeping all
the copies identical. If the system fails, you need a way to preserve the data with
the most recent changes.

Data validity is controlled by a data management system. Within a single MVS

system, the data management system keeps track of which piece of data is being
accessed or changed by which application in the system. It is the data
management system's responsibility to capture and preserve the most recent
changes to the data, in case of system failure.

When two or more MVS systems share data, each system has its own copy of a
data management system. Communication between the data management systems
is essential.

Therefore, multisystem data sharing hinges on high performance communication to

ensure data validity among multiple data management systems and it requires high
speed data accessing methods.

Data Validity
When many applications share data, within the same MVS system or among
several MVS systems, they need mechanisms to guarantee data validity. Two such
mechanisms are serialization and data consistency (buffer invalidation).

Serialization is a mechanism that allows control over the access and update of
data. Through serialization, only one application can access and change a given

 Copyright IBM Corp. 1994, 1998 11

piece of data at a time. As the number of applications increases, contention over a
piece of data becomes more likely, and performance slows. One way to allow more
applications on multiple systems to access more data at the same time is to allow
serialization on smaller pieces of data. Generally, serialization at a lower level of
granularity increases overhead, which slows performance. But by using the
Coupling Facility, data management systems can afford to serialize at a low level
with acceptable performance.

Another requirement for maintaining data validity is a mechanism that ensures

consistency among local copies of data. One such mechanism is buffer invalidation.
This mechanism indicates to each of the data sharing systems whether their local
data reflects the most recent changes.

Database managers need high speed serialization and data consistency

mechanisms across systems. Not until data sharing based on the Coupling Facility
has it been possible to efficiently share data using these mechanisms across more
than two MVS systems.

Multisystem Data Access

Before sysplex, the options for accessing shared data across multiple copies of a
data management system were:
Using a single data server
Partitioning data across multiple systems
Sharing data between two systems

These three options are contrasted with accessing shared data using the Coupling
Facility.

Using a Single Data Server

With the single data server option, one system controls data access and update.
Other systems must funnel requests through the data server, and the cross system
messaging that results can adversely affect performance. If the single data server
fails, other systems can no longer access data.

12 OS/390 V2R5.0 Parallel Sysplex Overview

Figure 8. Data Sharing with a Single Data Server

When the data server reaches its capacity, there may be no way to expand, other
than to install a larger capacity system or to go to another data sharing option.

Summary
Response Time Limited by the capability of the single server
Throughput Limited by the capability of the single server
Continuous Availability Limited by the availability of the single server
Growth Requires upgrade of server or change to a different
option
Data Management Managed as a single data management system

Partitioning Data Across Multiple Systems

Splitting the data among systems gives each data server control over a portion of
data. Requests for specific data are routed to the data server that controls that
data. This option gives you more capacity than a single data server, but can
impose a significant systems management burden to partition the data for adequate
performance.

To allow for changes in demand for data, you need to configure the size of each
system to handle the peak demand for that data, which requires extra capacity.
Without that extra capacity, dynamic swings in demand for a particular partition of
data could make performance erratic.

If a system fails, its portion of data cannot be accessed unless there is an alternate
path to the data from another system. The other system must then have enough
spare capacity to assume the additional work.

Data Sharing in a Sysplex 13

Figure 9. Data Sharing with Partitioned Data

When capacity is reached and you need to add another system, the data must be
re-partitioned.

Summary
Response Time Depends on how appropriately the data is partitioned
Throughput Depends on the demand for data
Continuous Availability Depends on the back-up alternate routing provisions
and the capacity of the alternate system
Growth Requires re-partitioning of the data
Data Management Requires carefully partitioned data for adequate
performance

Sharing Data Between Two Systems

Using the Information Management System Database Manager (IMS DB) without
the Coupling Facility, you can efficiently share data between two different MVS
systems. Whenever one of the sharing IMS DB systems needs to access the
database, it sends a message to the other.

14 OS/390 V2R5.0 Parallel Sysplex Overview

Figure 10. Data Sharing Between Two Systems

If you increase the number of IMS DB systems sharing the database to more than
two, the number of messages from one sharing IMS system to the others would
slow all the systems down.

Summary
Response Time Acceptable
Throughput Limited by the two IMS DB systems
Continuous Availability Limited by the two IMS DB systems
Growth Limited by the two MVS systems
Data Management Managed as a single data management system

Sharing Data Using the Coupling Facility Technology

In contrast to the options discussed, data sharing based on the Coupling Facility
makes it practical for you to have read/write data sharing among more than two
MVS systems. The Coupling Facility allows data management systems to
communicate so that they can directly share data. There is no single system
creating a bottleneck; the data does not need to be partitioned or re-partitioned
when you add another system; and there is no longer a two-system limitation.

Data Sharing in a Sysplex 15

Figure 11. Sysplex Data Sharing Using the Coupling Facility

Summary
Response Time Relieves poor response time due to system overload
Throughput Increases throughput far beyond the current limits
Continuous Availability Extends availability far beyond the current limits
Growth Incremental expansion is not disruptive to existing
systems
Data Management Managed as a single data management system

The Coupling Facility Technology

The technology that makes high performance sysplex data sharing possible is a
combination of hardware and software services available in the supporting MVS
release.

A Coupling Facility is a microprocessor unit. High bandwidth fiber optic links called
coupling facility channels, provide high speed connectivity between the Coupling
Facility and systems directly connected to it.

Within the Coupling Facility, storage is dynamically partitioned into structures.

MVS services manipulate data within the structures. Each of the following
structures has a unique function:
Cache structure - Supplies a mechanism called buffer invalidation to ensure
consistency of cached data. The cache structure can also be used as a
high-speed buffer for storing shared data with common read/write access.

16 OS/390 V2R5.0 Parallel Sysplex Overview

List structure - Enables authorized applications to share data that is organized
in a set of lists, for implementing function such as shared work queues and
shared status information.
Lock structure - Supplies shared and exclusive locking capability for
serialization of shared resources down to a very small unit of data.

Exploiters of the Coupling Facility

Authorized applications, such as subsystems and MVS components in the sysplex,
can use the Coupling Facility services to cache data, share queues and status, and
access sysplex lock structures in order to implement high performance data sharing
and rapid recovery from failures. The subsystems and components transparently
provide the data sharing and recovery benefits to their applications.

Some IBM data management systems that are using the Coupling Facility include
database managers and a data access method.

Information Management System Database Manager (IMS DB): IMS DB is IBM's

strategic hierarchical database manager. It is used for numerous applications that
depend on its high performance, availability, and reliability. A hierarchical database
has data organized in the form of a hierarchy (pyramid). Data at each level of the
hierarchy is related to, and in some way dependent upon, data at the higher level
of the hierarchy.

IMS database managers on different MVS systems can access data at the same
time. By using the Coupling Facility in a sysplex, IMS DB can efficiently provide
data sharing for more than two MVS systems and thereby extends the benefits of
IMS DB data sharing. IMS DB uses the Coupling Facility to centrally keep track of
when shared data is changed. IRLM is still used to manage data locking, but does
not notify each IMS DB of every change. IMS DB does not need to know about
changed data until it is ready to use that data.

DATABASE 2 (DB2) DB2 is IBM's strategic relational database manager. A

relational database has the data organized in tables with rows and columns.

DB2 data sharing support allows multiple DB2 subsystems within a sysplex to
concurrently access and update shared databases. DB2 data sharing uses the
Coupling Facility to efficiently lock, to ensure consistency, and to buffer shared
data. Similar to IMS, DB2 serializes data access across the sysplex through
locking. DB2 uses Coupling Facility cache structures to manage the consistency of
the shared data. DB2 cache structures are also used to buffer shared data within a
sysplex for improved sysplex efficiency.

Virtual Storage Access Method (VSAM) VSAM, a component of DFSMS, is an

access method rather than a database manager. It is an access method that gives
CICS and other application programs access to data stored in VSAM-managed
data sets.

DFSMS supports a new VSAM data set accessing mode called record level sharing
(RLS). RLS uses the Coupling Facility to provide sysplex-wide data sharing for
CICS and the other applications that use the new accessing mode. By controlling
access to data at the record level, VSAM enables CICS application programs
running in different CICS address spaces, called CICS regions, and in different
MVS images, to share VSAM data with complete integrity. The Coupling Facility

Data Sharing in a Sysplex 17

provides the high performance data sharing capability necessary to handle the
requests from multiple CICS regions.

Other Exploiters of the Coupling Facility

In addition to data management systems, there are other exploiters of the coupling
facility, such as Resource Access Control Facility (RACF) or the Security Server
element of OS/390, and JES2. Transaction management systems also exploit the
Coupling Facility to enhance parallelism as described topicref 26.

18 OS/390 V2R5.0 Parallel Sysplex Overview

Parallel Processing in a Sysplex
Parallel processing is a technology that increases application availability. It gives
you more servers for enhanced throughput; and if the enhanced throughput relieves
system overload, parallel processing will visibly reduce end-user response time.

One reason for setting up a sysplex is to enable parallel processing. Special

purpose parallel systems for engineering and scientific applications have been
available for years. The sysplex, however, can provide parallel processing for
commercial online transactions.

The sysplex brings together parallel capability on many levels—in the applications,
the supporting sysplex software, and the hardware. Applications can be replicated
to run in parallel on a single tightly coupled multiprocessing system. When you run
parallel applications in a sysplex with subsystems that support enhanced
communication across systems, you have a greater degree of parallelism. And
when you add hardware to that greater degree of parallelism, hardware with the
capability for modular, incremental growth—you have the broad based parallelism
that is available in a sysplex.

This chapter discusses:

A definition of parallel processing
Running work in parallel
Software that enables parallelism for OLTP
Hardware that enables parallelism

What is Parallel Processing?

Parallel processing in a sysplex is the ability to simultaneously process a particular
workload on multiple CPCs, each of which may have multiple CPs. A CP can
generally process one unit of work at a time. Typically the more CPs in a system,
as in a tightly coupled multiprocessor, the more work can be processed
simultaneously. When you have multiple CPCs processing the same workload, you
can significantly reduce elapsed processing time.

Parallel processing is a type of multiprocessing. For the purposes of this

publication, the distinction between multiprocessing and parallel processing is in
whether the same kind of work is being processed. While multiprocessing is the
simultaneous processing of work, it is not necessarily the same kind of work;
parallel processing in a sysplex is the simultaneous processing of one type of work,
whether it is many small but distinct units of work, or a larger unit of work that is
broken down to run in parallel.

 Copyright IBM Corp. 1994, 1998 19

Figure 12. Multiprocessing

In a multiprocessing environment, at a particular moment in time, one CP might be

running a payroll batch application, while another CP processes online transactions.
The different work runs at the same time. If the payroll batch application takes
hours to complete, and if the application is structured as a single task, it can only
use the power of one CP. The fact that there is more than one CP available does
not split up the long-running batch application. But if the batch application is
structured as multiple tasks, it can be processed simultaneously on many CPs—in
other words, in parallel.

Similarly, if there are more online transactions than one CP can handle, adding
more CPs allows the online transactions to run in parallel.

Therefore, parallel processing is the ability to use many CPs to simultaneously

process a particular workload; and by running a workload in parallel, it is possible
to make a noticeable improvement in the response time for the end user.

In a sysplex, it is possible to have one workload running on many tightly coupled

multiprocessors that are sharing data using the Coupling Facility. How many CPs
you have depends on the configuration. For example, a configuration of 16 CPCs
with 6 CPs per system gives you a total of 96 CPs that can process a workload in
parallel.

Problems Solved by Parallel Processing

Parallel processing in a sysplex can be used for two different programming problem
situations—when the number of transactions noticeably slows response time and
when a long-running application takes too long to complete. Both situations can
adversely affect end-user response time.

20 OS/390 V2R5.0 Parallel Sysplex Overview

Increased Number of Transactions: When the number of incoming transactions
exceeds the processing capability, transactions are delayed and response time
increases. The following graphic shows how a large number of transactions can
build up when they exceed the processing capability.

Figure 13. Workload that Exceeds Processing Capability

By adding processors and running transactions in parallel, you can reduce end-user
response time by increasing throughput. The following graphic shows how adding
processing capability increases throughput.

Figure 14. Increasing Throughput for a Workload

Parallel Processing in a Sysplex 21

Similarly in your environment, when an increased number of transactions slows
throughput, you can use a sysplex and the Coupling Facility to increase the number
of CPs running in parallel.

Lengthy Application: To shorten the processing time of a single, long-running

application, subdivide it into smaller units of work, if possible. These smaller units
can then run in parallel. The following graphic shows how a lengthy application is
processed one piece at a time when there is only one CP.

Figure 15. Processing a Lengthy Application

When the lengthy application is divided into smaller units of work and there are
many parallel processors, the smaller units of work can run simultaneously and in
parallel. The following graphic shows how a lengthy application can be processed
in parallel by dividing it among many parallel processors.

22 OS/390 V2R5.0 Parallel Sysplex Overview

Figure 16. Decreasing the Processing Time of a Lengthy Application

You can use this same approach in a sysplex to speed up the processing of a
long-running application, such as a complex query.

Running Work in Parallel

MVS is known for its strength and dependability in processing applications that
solve large business problems. These are some characteristics of a business
problem, each of which makes it a large problem:
Volume of work, up to millions of transactions per day
Number of end users, up to thousands
Amount of storage required, such as terabytes of data
Bandwidth requirements for sending data in a network, such as megabytes of
data in seconds
Stringent requirements for continuous availability (24 hours a day, 7 days a
week, 365 days a year)

Some common MVS applications that deal with large business problems and can
be made to run in parallel are batch, query, and online transaction processing
(OLTP).

A batch workload consists of multiple job streams, which can be unrelated and can
therefore run in parallel. A single job stream, however, runs in sequence and

Parallel Processing in a Sysplex 23

usually cannot take advantage of parallelism. When a single job stream is lengthy,
it can take considerable time to complete. IBM provides a product called Parallel
Sysplex, to help you exploit parallelism in a single job stream within a single MVS
image. For more information, see Parallel Sysplex Introduction (GC28-1214).

Queries are a diverse type of workload and usually rely on partitioned data when
running in parallel. To help you process queries in parallel, IBM is offering a parallel
query server. The parallel query server is a self-contained system made up of
hardware, software, and database services. The system is fully installed,
customized, and serviced by IBM. The parallel query server is used to process
large queries in a shared relational database. For more information about the
parallel query server, see your IBM marketing representative.

OLTP applications are a common MVS application type that can take advantage of
parallelism. They are the focus of the following topics, because there is extensive
software support for OLTP processing in a sysplex, and the number of OLTP
applications are on the increase.

Online Transaction Processing (OLTP)

OLTP applications are used by banks, airlines, insurance companies, and other
businesses that give online users direct access to information. The OLTP
applications process units of work, called transactions. A single transaction might
request a bank balance; another might update that balance to reflect a deposit.

An application can be replicated to run in parallel on a tightly coupled

multiprocessor so that it can simultaneously process multiple transactions. The
degree of parallelism depends on the system software, the transaction manager,
and the hardware that the OLTP application runs on.

Software that Enables Parallelism for OLTP

OLTP applications use system software services provided by transaction managers
and they access data controlled by data management systems. To balance the
transactions dynamically across systems, MVS workload manager, a component of
MVS, works with the transaction managers. This section first discusses the
transaction managers and then describes workload management.

Transaction Managers
From the time the transaction manager obtains the transaction from the network
until it returns the completed transaction to the network, it is responsible for:
Sending the transaction to the appropriate application
Converting transaction data to a form that can be used
Reconverting results to a form that can be displayed on an output device

If the transaction manager can simultaneously process copies of an application in

multiple address spaces within a single system, an OLTP application can run in
parallel.

24 OS/390 V2R5.0 Parallel Sysplex Overview

Figure 17. Parallel OLTP Applications in a Single System

If the transaction manager can take advantage of sysplex support and

simultaneously process copies of an application across different MVS systems, the
OLTP application can run with a greater degree of parallelism.

Parallel Processing in a Sysplex 25

Figure 18. Parallel OLTP Applications in a Sysplex Parallel Environment

Two MVS transaction managers, which have provided parallel support in a single
system, provide an additional degree of parallel support in a sysplex. The two
transaction managers are Customer Information Control System (CICS) and
Information Management System Transaction Manager (IMS TM).

26 OS/390 V2R5.0 Parallel Sysplex Overview

Customer Information Control System (CICS): CICS enables online transactions
entered at terminals to be processed concurrently by user-written application
programs. Originally CICS ran in a single MVS address space that was responsible
for terminals, applications, and files.

Using CICS multi-region operation, you can separate function into individual
regions—namely terminal-owning regions (TORs), application-owning regions
(AORs), and file-owning regions (FORs). These individual resource-owning regions
can then be linked together and managed in what is called a CICSplex.

One of the benefits of separating the CICS functions into a number of

resource-owning regions is to take advantage of multiprocessor systems, as each
region (address space) can run on a different CP. You can structure a CICS
environment such that the application-owning regions can process transactions in
parallel.

Replicating regions and running multiple regions on multiple systems in a sysplex

further increases the parallelism. The greater the number of regions, the greater the
CICS availability in the event of a system failure.

Information Management System Transaction Manager (IMS TM): The IMS

Transaction Manager (IMS TM) is an IBM transaction processing product that is
designed to take advantage of multiprocessors. IMS TM is a multi-address space
product so that one IMS TM running under one MVS can effectively use tightly
coupled multiprocessors.

IMS TM can also take advantage of the sysplex. Several IMS TMs can coordinate
work among themselves by using IMS's Multiple Systems Coupling (MSC) support.
Through MSC, transactions entered from one IMS can be routed to another IMS for
processing and the results returned to the original IMS. To the end user, the
transfer of information from one IMS to another is transparent.

Transaction message traffic workloads can be balanced using MSC. IMS will
continue to enhance and unify management of IMS systems and present a
single-system view of IMS in a sysplex.

Data Management Systems

When an OLTP application needs to access data, the data management system
controls the data access and update. Data management systems are responsible
for validity of the data, providing a way to recover data in case of failure, and a way
to secure data from unauthorized access.

If the data management system takes advantage of the Coupling Facility, the OLTP
applications can avoid shipping data back and forth between systems. By using the
Coupling Facility for data sharing and for queuing and status control, data
management systems and transaction managers can perform their duties more
quickly and therefore manage more systems efficiently. This increase in the number
of systems that can be managed, increases the degree of parallelism even further.

The data management systems that take advantage of the Coupling Facility are
IMS DB, DB2, and VSAM. These data management systems were described in
Exploiters of the Coupling Facility topicref 17.

Parallel Processing in a Sysplex 27

Managing Work in a Sysplex
Along with parallelism comes the need for simple and dynamic multisystem
workload balancing. When you are in an environment with multiple systems, the set
of performance issues changes. Existing mechanisms for managing system
performance are complex and single-system oriented.

To reduce the complexity of managing a sysplex, MVS workload management

provides dynamic sysplex-wide management of system resources. MVS workload
management is the combined cooperation of various subsystems (such as CICS,
IMS, and VTAM) with the MVS workload manager (WLM) component. An
installation defines performance goals and a business importance to workloads
through WLM. Workload management focuses on attaining these goals through
dynamic resource distribution.

This type of workload management is different from the way workloads were
previously managed. The new emphasis is on defining performance goals for work,
and having MVS and the subsystems adapt to meet the goals.

Defining Performance Goals

An installation defines performance goals in a service policy. Service policies are
defined through an ISPF application and they set goals for all types of
MVS-managed work. An installation can create multiple service policies to adjust
performance goals for different periods of time.

The scope of a service policy is the sysplex. Each service policy has a name, and
can be activated by the ISPF application, an operator command, or an automation
package. Only one policy can be active at a time. When it is activated, all systems
in the sysplex process towards the goals defined in the policy.

Workload management coordinates and shares performance information across the

sysplex. Each MVS system handles its own system resource management and
dynamically matches resources to work according to the goals defined in the
service policy. During processing, the system monitors how well the goals are being
met and adapts accordingly as the environment changes. If there is contention for
resources, each system makes the appropriate trade-offs based on the importance
of the work and how well the goals are being met. This way, all systems can
cooperate to protect work that is critical to your installation.

Reporting
Resource Measurement Facility (RMF) combines MVS system management
facilities (SMF) data for the sysplex, and reports how well the sysplex is doing to
achieve the goals defined in the service policy. In addition, execution delay
information is available in SMF records that show where delays are occurring. If
there is a problem, you can use this information to help adjust the performance
goals, focus on specific subsystems having a problem, or make work scheduling
adjustments.

28 OS/390 V2R5.0 Parallel Sysplex Overview

Hardware that Enables Parallel Processing
Sysplex parallel processing depends on Coupling Facility technology and the ability
to connect to it. Several models of S/390 processors are able to connect to the
Coupling Facility including large capacity water-cooled processors and smaller
capacity air-cooled processors. In addition, a separately orderable parallel
microprocessor cluster can have an integrated Coupling Facility and run as a
parallel transaction server.

The significance of adding S/390 microprocessor clusters to a sysplex is the

improved price/performance and incremental growth possible by using large
numbers of relatively small CPCs to process work in parallel. But regardless of
processor size, the use of new hardware technology makes sysplex parallel
processing a cost effective alternative.

Parallel Processing in a Sysplex 29

30 OS/390 V2R5.0 Parallel Sysplex Overview
Products in a Sysplex
A sysplex is not a single product that you install in your data center. Rather, a
sysplex is a collection of products, both hardware and software, that work together.

Figure 19. Products in a Sysplex

The products that work together in a sysplex can be categorized as hardware,

system software, networking software, data management, transaction management,
and systems management. Following are sysplex products grouped by area.
Note: A sysplex is not limited to the products described in this chapter. Additional
IBM and non-IBM products might be able to run in a sysplex or exploit
sysplex function. For a current list of products that can take advantage of a
sysplex, see your IBM marketing representative.

Hardware
Hardware for the Parallel Sysplex includes the following.

Coupling Facility
The Coupling Facility is a microprocessor unit that allows high performance
multisystem data sharing among certain S/390 processors and within a cluster of
S/390 microprocessor complex.

MVS services allow authorized applications, such as subsystems and MVS

components, to use the Coupling Facility to cache data, exchange status, and
access sysplex lock structures in order to implement high performance data sharing
and rapid recovery from failures.

Coupling Facility Channels

Coupling facility channels are high bandwidth fiber optic links that provide high
speed connectivity between the Coupling Facility and the CPCs that use the
Coupling Facility. Coupling facility channels are directly attached between the CPCs
and the Coupling Facility.

System/390 Processors
Note: All ES/9000 processors can participate in a base sysplex, but only the
following processors can link to the Coupling Facility.
9021 711-based models
The 9021 711-based models are water-cooled CPCs, which were announced in
February, 1993.
9121 511-based models
The 9121 511-based models are air-cooled CPCs, which were announced in
February, 1993.
Microprocessor cluster
A microprocessor cluster comes with an integrated Coupling Facility and flexible
packaging options, and it runs as a parallel transaction server. In addition, an
easy-to-use console provides cross system management capability. For a
description of the console, see “Hardware Management Console” on page 36.

Sysplex Timer
The Sysplex Timer is a unit that synchronizes the time-of-day (TOD) clocks in
multiple CPCs in a sysplex. The time stamp from the Sysplex Timer is a way to
monitor and sequence events within the sysplex.

Enterprise Systems Connection (ESCON)

ESCON channels have a channel-to-control-unit I/O interface that uses optical
cables as a transmission medium. ESCON Directors (ESCDs) add dynamic
switching capability for ESCON channels, further increasing connectivity and device
sharing.

32 OS/390 V2R5.0 Parallel Sysplex Overview

ESCON I/O and the interconnect technologies become very important in a sysplex
to speed access to shared data on disk or tape, and to enhance communication
among systems. In addition, they offer improved availability.

ESCON Control Units and I/O Devices

To ease the management of logical paths and increase connectivity, use control
units and devices that provide a higher number of logical paths, such as:
3990 Storage Control Model 6
9343 Storage Controller and 9345 Direct Access Storage Device
I/O devices that are ESCON capable (3490E, 3172, 3174, 3745, 3746)

System Software
System software for the Parallel Sysplex includes the following.

MVS/ESA or OS/390
The MVS/ESA or OS/390 operating system for S/390 is known for its ability to
handle thousands of concurrent interactive users and for its sophisticated data
management, reliability, security, and auditing features in a commercial
environment.

MVS enables the new coupling technology, extends system support beyond the
previous limit of 8 MVS systems, and increases the number of I/O devices allowed
per MVS system beyond the previous limit of 4096. It is the platform for simplified
systems management of a sysplex, including configuration management, availability
management, workload management, and single-image operations. Further
enhancements include problem determination and recovery in a sysplex.

For information about OS/390, see OS/390 Introduction and Release Guide.

JES2 or JES3
These two job entry subsystem products control job queues and dispatch work in a
sysplex. JES2 expands its 7-member multi-access spool (MAS) capability to a
32-member MAS. Additionally, JES2 uses the Coupling Facility to enhance its
performance. JES3 can support a maximum of 32 members in a JES3 complex and
supports ESCON CTCs or the coupling facility.

DFSMS
DFSMS enables the automatic placement, migration, backup, recall, recovery, and
deletion of data for MVS. An SMS configuration can contain 32 names, but the
names can be a combination of system names and system group names. DFSMS
also supports the increased number of I/O devices beyond the previous limit of
4096.

Products in a Sysplex 33
Networking Software
Networking software for the Parallel Sysplex includes the following.

Virtual Telecommunications Access Method (VTAM)

VTAM monitors and controls the activation and connection of resources in a
network. When VTAM is part of the sysplex, duplicate applications on different
systems in a VTAM network can identify themselves by a single generic resource
name. By distributing sessions among a number of duplicate resources under a
single name, instead of to a uniquely named single resource, VTAM is capable of
balancing the session workload.

Data Management
Data management for the Parallel Sysplex includes the following.

Information Management System Database Manager (IMS DB:)

IMS DB is a database manager of hierarchical data that provides multisystem
support across two MVS systems. By using the Coupling Facility, IMS DB extends
data sharing across multiple MVS systems.

DATABASE 2 (DB2)
DB2 is a database manager of relational data. DB2 provides data sharing support
that uses the Coupling Facility for read/write sharing of DB2 databases within a
sysplex.

Virtual Storage Access Method (VSAM) - component of DFSMS

VSAM is an access method that gives application programs access to data stored
in VSAM-managed data sets. DFSMS supports a new VSAM data set accessing
mode called record level sharing (RLS). VSAM RLS provides sysplex data sharing
and will use the Coupling Facility for locking and data caching.

Transaction Management
Transaction management for the Parallel Sysplex includes the following.

Customer Information Control System (CICS/ESA and CICS

Transaction Server)
CICS/ESA and CICS Transaction Server are transaction managers that provide
services for online transactions. Both CICS/ESA and CICS Transaction Server
enhance the multiregion operation (MRO) links to provide more efficient cross
system communication for CICS. They support the MVS workload manager
component and VTAM generic resource as described previously. They also support
sysplex data sharing for IMS DB and DB2. CICS Transaction Server provides
support for record-level sharing of data for VSAM.

34 OS/390 V2R5.0 Parallel Sysplex Overview

Information Management System Transaction Manager (IMS TM)
IMS TM is a transaction manager that provides services for online transactions in a
multisystem environment. It cooperates with the MVS workload manager
component for better performance.

Systems Management
Systems management software includes the following.

Accounting

System Management Facilities (SMF) - component of MVS

This component of MVS keeps records of resources used in the system. SMF
record keeping expands beyond the previous 8 system limit. Also SMF provides
new records specifically for a sysplex.

Workload

CICSPlex System Manager/ESA (CICSPlex SM)

This product provides a single-system image for a CICSplex across a range of
system management applications. These applications include dynamic workload
balancing and separation in cooperation with the MVS workload manager, CICS
master terminal operations, online access to CICS data and statistics, and the
ability to detect exceptional events based on CICS state data for an operator or for
automation purposes.

Operations Planning and Control (OPC/ESA)

OPC/ESA is a product that helps you manage your installation's batch production
workload. From one system you can plan, control, and monitor all workloads.
OPC/ESA has been enhanced to present a single-system image in a sysplex
environment. This enhancement will give a TSO user access to the OPC/ESA
dialog even when the OPC/ESA Controller and the TSO user are active on different
MVS systems.

Workload Manager (WLM) - component of MVS

To manage workloads throughout a sysplex, WLM cooperates with transaction and
resource managers that span systems. WLM uses customer-defined policies for
performance objectives to help balance workloads.

Operations

System Automated for OS/390

System Automation for OS/390 provides system automation for subsystem start
and shutdown, automation for messages, timers, system data set offload, and
policy dialogs. System Automation for OS/390 also provides enterprise resource
monitoring through a workstation graphical interface where the enterprise can
include one or more sysplexes with coupling facilities. Where appropriate,
resources are monitored at the sysplex level.

Products in a Sysplex 35
System Automation for OS/390 also eases the task of propagating automation
policy to multiple systems. System Automation for OS/390 consolidates access to
other products (for example, SDSF and RMF) from a single workstation.

System Automation for OS/390 also extends the control, monitoring, and
automation capabilities of the NetView program to provide consolidated
management for hardware (system) and software (operator) consoles in
heterogeneous System/390 environments. System Automation for OS/390 supports
both automated and manual operations on a sysplex.

Hardware Management Console

An enhanced hardware system console provides a single point of control for the
systems in a microprocessor cluster. Using icons and a mouse, you can operate
one system, and you can perform an operation for all systems or for a user-defined
group of systems.

System Display and Search Facility (SDSF)

SDSF helps you efficiently monitor and control the operation of an MVS/JES2
system. It supports the increased number of systems that can be defined in a JES2
multi-access spool and it supports the MVS workload manager component.

Performance

Resource Measurement Facility (RMF)

RMF gathers performance data about system resources and writes SMF records
70-79. To reduce the complexity of performance management in a sysplex, RMF
introduces the concept of a single system view for reporting on sysplex-wide data.
It also supports the Coupling Facility and the MVS workload manager component.

Enterprise Performance Data Manager/MVS (EPDM)

EPDM is a system log data set post processor and reporter that reads any
sequential log data set. It uses DB2 to support data summarization and reporting
on new and changed data for sysplex-related SMF records. Reporting can be done
online through an OS/2 dialog or through ISPF, and also in batch.

Service Level Reporter (SLR)

SLR is a system log data set post processor and reporter that reads any sequential
log data set. It supports data summarization and reporting on new and changed
data for sysplex-related SMF records. Reporting can be done online through ISPF
and also in batch.

Security

Resource Access Control Facility (RACF) or the Security Server

RACF or the Security Server element of OS/390 provides security for the MVS
system. RACF or the Security Server operates in a sysplex environment and takes
advantage of the Coupling Facility to reduce I/O to the RACF database. It also
provides additional systems management function.

36 OS/390 V2R5.0 Parallel Sysplex Overview

Configuration

System Automation for OS/390

System Automation for OS/390 helps manage the complexities of active I/O
configurations. When running on a sysplex, System Automation for OS/390
manages the sysplex as a unified system image. Using System Automation for
OS/390, you can graphically view and change the connectivity between systems
and I/O objects (shared and non-shared, ESCON and non-ESCON).

Hardware Configuration Definition (HCD)

HCD is the configuration management program for MVS. It replaces the MVS
configuration program (MVSCP) and creates input statements to the I/O
configuration program. In a S/390 microprocessor complex complex, HCD is the
focal point for all the I/O configuration data set (IOCDS) management function.
HCD can also define I/O for the Coupling Facility including the channel paths
associated with the coupling facility channels.

Products in a Sysplex 37
38 OS/390 V2R5.0 Parallel Sysplex Overview
Introduction to Sample Sysplex Configurations
In a sysplex, you can think of MVS systems and system hardware components as
building blocks that you can select for specific purposes and replicate or combine in
different configurations.

Following are some sample sysplex configurations. All configurations assume:

Shared DASD with ESCON connections
Appropriate levels of enabling software
Possible connection to a network

Large Systems Data Sharing Sysplex

This configuration connects two large CPCs in a sysplex that uses the Coupling
Facility to share data. The CPCs can be either 9021 711-based models, 9121
511-based models, or one of each.

Benefits: This configuration combines the inherent strengths of large systems with
multisystem data sharing provided by the Coupling Facility. It can be used for both:
An easy migration path for initiating and testing data sharing using the Coupling
Facility.
A reliable production environment

Figure 20. Large Systems Sysplex Configuration

The parts of this configuration are:

ES/9000 large processor, such as:
– 9021 711-based CPC
– 9121 511-based CPC
A standalone Coupling Facility, such as the 9674 Coupling Facility, with an
optional second Coupling Facility as backup
A Sysplex Timer with the high availability feature

S/390 Microprocessor Cluster

This separately orderable sysplex configuration consists of an independent S/390
microprocessor cluster with an integrated Coupling Facility, and it runs as an
System/390 Parallel Sysplex Offering

Benefits: In addition to the standard sysplex benefits, such as improved

price/performance, greater parallel capacity for a single workload, and
environmental savings (space, power, cooling, and weight), this configuration:
Offers the reliability of a production environment
Allows non-disruptive incremental growth of the S/390 microprocessor cluster, a
single CPC at a time

40 OS/390 V2R5.0 Parallel Sysplex Overview

Can be easily added to an existing sysplex to increase capacity

Figure 21. Sysplex in a S/390 Microprocessor Cluster Configuration

The parts of this configuration are:

S/390 microprocessor cluster with an integrated Coupling Facility
A Sysplex Timer

Mixed Processor Sysplex

This configuration combines a large processor and a S/390 microprocessor cluster
in a sysplex production environment. The processors share Coupling Facilities.

Benefits: In addition to the standard sysplex benefits, such as improved

price/performance, greater parallel capacity for a single workload, and
environmental savings (space, power, cooling, and weight), this configuration:
Offers the reliability of a production environment
Extends sysplex data sharing across different types of processors

Introduction to Sample Sysplex Configurations 41

Allows non-disruptive incremental growth of the S/390 microprocessor cluster, a
single CPC at a time

Figure 22. Mixed Processor Sysplex Configuration

The parts of this configuration are:

ES/9000 large processor, such as:
– 9021 711-based CPC
– 9121 511-based CPC
S/390 microprocessor cluster with an integrated Coupling Facility
A Sysplex Timer with the high availability feature
A standalone Coupling Facility, such as the 9674 Coupling Facility.

42 OS/390 V2R5.0 Parallel Sysplex Overview

Glossary
databases and message queues. BMPs run online, but
Sources of Terms and Definitions like programs in a batch environment, they are started
with job control language (JCL).
This glossary includes terms and definitions from:
The IBM Dictionary of Computing New York: batch-oriented BMP program. A BMP program that
McGraw-Hill, 1994. has access to online databases and message queues
while performing batch-type processing. A
The Information Technology Vocabulary developed batch-oriented BMP does not access the IMS message
by Subcommittee 1, Joint Technical Committee 1, of queues for input or output. It can access online
the International Organization for Standardization databases, GSAM databases, and MVS files for both
and the International Electrotechnical Commission input and output.
(ISO/IEC JTC1/SC1). Definitions taken from draft
international standards, committee drafts, and BMP. Batch message processing (BMP) program.
working papers being developed by ISO/IEC
JTC1/SC1 are identified by the symbol (T) after the
definition, indicating that final agreement has not yet C
been reached among the participating National
Bodies of SC1. cache structure. A coupling facility structure that
enables high-performance sharing of cached data by
multisystem applications in a sysplex. Applications can
use a cache structure to implement several different
Explanation of Cross-References types of caching systems, including a store-through or a
store-in cache.
The following cross-references are used in this
glossary: cache structure services. MVS services that enable
Contrast with. This refers to a term that has an applications in a sysplex to perform operations such as
opposed or substantively different meaning. the following on a coupling facility cache structure:
See. This refers the reader to multiple-word terms in Manage cache structure resources
which this term appears. Store data into and retrieve data from a cache
See also. This refers the reader to terms that have structure
a related, but not synonymous, meaning. Manage accesses to shared data
Determine when shared data has been changed
Determine whether a local copy of shared data is
A valid.

ACDS. Active control data set. CBPDO. Custom Built Product Delivery Offering.

ANO/MVS. Automated Network Operations. CEC. Synonym for central processor complex (CPC).

AOC/MVS. Automated Operations Control. The central processor (CP). The part of the computer that
licensed program System Automation for OS/390 contains the sequencing and processing facilities for
includes all of the function previosuly provided by instruction execution, initial program load, and other
AOC/MVS. machine operations.

AOR. Application-owning region central processor complex (CPC). A physical

collection of hardware that includes main storage, one
APPN. Advanced Peer-to-Peer Networking. or more central processors, timers, and channels.

CFRM. Coupling facility resource management.

B
channel-to-channel (CTC). Refers to the
basic mode. A central processor mode that does not communication (transfer of data) between programs on
use logical partitioning. Contrast with logically opposite sides of a channel-to-channel adapter (CTCA).
partitioned (LPAR) mode.
channel-to-channel adapter (CTCA). An input/output
batch message processing (BMP) program. An IMS device that is used by a program in one system to
batch processing program that has access to online communicate with a program in another system.

CICS. Customer Information Control System. DB2. DATABASE 2 for MVS/ESA.

CICSplex. A group of connected CICS regions. DB2 data sharing group. A collection of one or more
concurrent DB2 subsystems that directly access and
CICSPlex SM. CICSPlex System Manager change the same data while maintaining data integrity.

CMOS. Complementary metal-oxide semiconductor. DB2 PM. DB2 Performance Monitor.

COMMDS. Communications data set. DFSMS. Data Facility Storage Management

Subsystem.
complementary metal-oxide semiconductor
(CMOS). A technology that combines the electrical dpAM. IBM SystemView Data Processing Accounting
properties of positive and negative voltage requirements Manager/MVS.
to use considerably less power than other types of
semiconductors.
E
couple data set. A data set that is created through the
XCF couple data set format utility and, depending on its EMIF. ESCON Multiple Image Facility.
designated type, is shared by some or all of the MVS
systems in a sysplex. See also sysplex couple data set. Enterprise Systems Connection (ESCON). A set of
products and services that provides a dynamically
coupling facility. A special logical partition that connected environment using optical cables as a
provides high-speed caching, list processing, and transmission medium.
locking functions in a sysplex.
EPDM. IBM SystemView Enterprise Performance Data
coupling facility channel. A high bandwidth fiber Manager/MVS.
optic channel that provides the high-speed connectivity
required for data sharing between a coupling facility and ESCD. ESCON Director.
the central processor complexes directly attached to it.
ESCM. ESCON Manager. The licensed program
coupling services. In a sysplex, the functions of XCF System Automation for OS/390 includes all of the
that transfer data and status between members of a function previosuly provided by ESCM.
group residing on one or more MVS systems in the
sysplex. ESCON. Enterprise Systems Connection.

CP. Central processor. ETR. External Time Reference. See also Sysplex
Timer.
CPC. Central processor complex.

cross-system coupling facility (XCF). XCF is a F

component of MVS that provides functions to support
FOR. File-owning region.
cooperation between authorized programs running
within a sysplex.
frame. For a System/390 microprocessor cluster, a
frame contains one or two central processor complexes
CTC. Channel-to-channel.
(CPCs), support elements, and AC power distribution.

D G
DAE. Dump analysis and elimination.
global resource serialization. A function that
DASD. Direct access storage device. provides an MVS serialization mechanism for resources
(typically data sets) across multiple MVS images.
data sharing. The ability of concurrent subsystems
(such as DB2 or IMS DB) or application programs to global resource serialization complex. One or more
directly access and change the same data while MVS systems that use global resource serialization to
maintaining data integrity. serialize access to shared resources (such as data sets
on shared DASD volumes).
DBCTL. IMS Database Control.
GSAM. Generalized Sequential Access Method.
DBRC. Database Recovery Control.
GTF. Generalized trace facility.

44 OS/390 V2R5.0 Parallel Sysplex Overview

ISPF. Interactive System Productivity Facility.
H
Hardware Management Console. A console used to J
monitor and control hardware such as the System/390
microprocessors. JES2. Job Entry Subsystem 2.

HCD. Hardware Configuration Definition. JES3. Job Entry Subsystem 3.

highly parallel. Refers to multiple systems operating

in parallel, each of which can have multiple processors. L
See also n-way.
LIC. Licensed Internal Code.

I list structure. A coupling facility structure that enables

multisystem applications in a sysplex to share
ICMF. Integrated Coupling Migration Facility. information organized as a set of lists or queues. A list
structure consists of a set of lists and an optional lock
image server. A high-capacity optical storage device table, which can be used for serializing resources in the
or a computer that each computer and image list structure. Each list consists of a queue of list
workstation on a network can use to access and entries.
retrieve image objects that can be shared among the
attached computers and image workstations. list structure services. MVS services that enable
multisystem applications in a sysplex to perform
IMS. Information Management System. operations such as the following on a coupling facility
list structure:
IMS DB. Information Management System Database
Manager. Read, update, create, delete, and move list entries
in a list structure
IMS DB data sharing group. A collection of one or Perform serialized updates on multiple list entries in
more concurrent IMS DB subsystems that directly a list structure
access and change the same data while maintaining Monitor lists in a list structure for transitions from
data integrity. empty to non-empty.

IMS TM. Information Management System Transaction lock structure. A coupling facility structure that
Manager. enables applications in a sysplex to implement
customized locking protocols for serialization of
in-doubt period. The period during which a unit of application-defined resources. The lock structure
work is pending during commit processing that involves supports shared, exclusive, and application-defined lock
two or more subsystems. See also in-doubt work unit. states, as well as generalized contention management
and recovery protocols.
in-doubt work unit. In CICS/ESA and IMS/ESA, a
piece of work that is pending during commit processing; lock structure services. MVS services that enable
if commit processing fails between the polling of applications in a sysplex to perform operations such as
subsystems and the decision to execute the commit, the following on a coupling facility lock structure:
recovery processing must resolve the status of any Request ownership of a lock
work unit that is in doubt. Change the type of ownership for a lock
Release ownership of a lock
integrated operations workstation. A programmable
Manage contention for a lock
workstation (PWS) from which an individual can access
Recover a lock held by a failed application.
multiple products to perform a set of tasks, in some
cases without knowing which particular product logical partition (LP). A subset of the processor
performs a specific task. hardware that is defined to support an operating
system. See also logically partitioned (LPAR) mode.
IOCDS. Input/output configuration data set.
logically partitioned (LPAR) mode. A central
IOCP. Input/output configuration program.
processor complex (CPC) power-on reset mode that
enables use of the PR/SM feature and allows an
IODF. Input/output definition file.
operator to allocate CPC hardware resources (including
IRLM. Internal resource lock manager. central processors, central storage, expanded storage,

Glossary 45
and channel paths) among logical partitions. Contrast multisystem environment. An environment in which
with basic mode. two or more MVS images reside in one or more
processors, and programs on one image can
loosely coupled. A multisystem structure that requires communicate with programs on the other images.
a low degree of interaction and cooperation between
multiple MVS images to process a workload. See also multisystem sysplex. A sysplex in which two or more
tightly coupled. MVS images are allowed to be initialized as part of the
sysplex. See also single-system sysplex.
LP. Logical partition.
MVS image. A single occurrence of the MVS/ESA
LPAR. Logically partitioned (mode). operating system that has the ability to process work.

MVS system. An MVS image together with its

M associated hardware, which collectively are often
referred to simply as a system, or MVS system.
m-image. The number (m) of MVS images in a
sysplex. See also n-way. MVS/ESA. Multiple Virtual Storage/ESA.

massively parallel. Refers to thousands of processors MVSCP. MVS configuration program.

in a parallel arrangement.

member. A specific function (one or more N

modules/routines) of a multisystem application that is
defined to XCF and assigned to a group by the n-way. The number (n) of CPs in a CPC. For example,
multisystem application. A member resides on one a 6-way CPC contains six CPs.
system in the sysplex and can use XCF services to
communicate (send and receive data) with other NJE. Network job entry.
members of the same group.

microprocessor. A processor implemented on one or O

a small number of chips.
OLTP. Online transaction processing.
mixed complex. A global resource serialization
complex in which one or more of the systems in the OPC/ESA. Operations Planning and Control.
global resource serialization complex are not part of a
operating system (OS). Software that controls the
multisystem sysplex.
execution of programs and that may provide services
MP. Multiprocessor. such as resource allocation, scheduling, input/output
control, and data management. Although operating
MRO. Multiregion operation. systems are predominantly software, partial hardware
implementations are possible. (T)
MSC. Multiple Systems Coupling.

multi-MVS environment. An environment that P

supports more than one MVS image. See also MVS
image and sysplex. parallel processing. The simultaneous processing of
units of work by many servers. The units of work can be
Multiple Systems Coupling (MSC). An IMS facility either transactions or subdivisions of large units of work
that permits geographically dispersed IMS subsystems (batch). See also highly parallel.
to communicate with each other.
Parallel Sysplex. A sysplex that uses one or more
multiprocessing. The simultaneous execution of two coupling facilities.
or more computer programs or sequences of
instructions. See also parallel processing. partitionable CPC. A CPC that can be divided into 2
independent CPCs. See also physical partition,
multiprocessor (MP). A CPC that can be physically single-image mode, MP, side.
partitioned to form two operating processor complexes.
physical partition. Part of a CPC that operates as a
multisystem application. An application program that CPC in its own right, with its own copy of the operating
has various functions distributed across MVS images in system.
a multisystem environment.

46 OS/390 V2R5.0 Parallel Sysplex Overview

physically partitioned (PP) configuration. A system one CPC. By definition, a uniprocessor (UP) operates in
configuration that allows the processor controller to use single-image mode. Contrast with physically partitioned
both central processor complex (CPC) sides as (PP) configuration.
individual CPCs. The A-side of the processor controller
controls side 0; the B-side of the processor controller single-MVS environment. An environment that
controls side 1. Contrast with single-image (SI) supports one MVS image. See also MVS image.
configuration.
single-system sysplex. A sysplex in which only one
PR/SM. Processor Resource/Systems Manager. MVS system is allowed to be initialized as part of the
sysplex. In a single-system sysplex, XCF provides XCF
processor controller. Hardware that provides support services on the system but does not provide signalling
and diagnostic functions for the central processors. services between MVS systems. See also multisystem
sysplex, XCF-local mode.
Processor Resource/Systems Manager (PR/SM).
The feature that allows the processor to use several SLR. Service Level Reporter.
MVS images simultaneously and provides logical
partitioning capability. See also LPAR. SMF. System management facilities.

SMP/E. System Modification Program Extended.

Q
SMS. Storage Management Subsystem.
QOR. Queue-owning region.
SMS communication data set. The primary means of
communication among systems governed by a single
R SMS configuration. The SMS communication data set
(COMMDS) is a VSAM linear data set that contains the
RACF. Resource Access Control Facility. current utilization statistics for each system-managed
volume, which SMS uses to help balance space usage
RMF. Resource Measurement Facility. among systems.

SMS configuration. The SMS definitions and routines

S that the Storage Management Subsystem uses to
manage storage.
SCDS. Source control data set.
SMS system group. All systems in a sysplex that
SDSF. System Display and Search Facility.
share the same SMS configuration and communications
SEC. System Engineering Change. data sets, minus any systems in the sysplex that are
defined individually in the SMS configuration.
serialized list structure. A coupling facility list
structure with a lock table containing an array of structure. A construct used by MVS to map and
exclusive locks whose purpose and scope are manage storage on a coupling facility. See cache
application-defined. Applications can use the lock table structure, list structure, and lock structure.
to serialize on parts of the list structure, or resources
support element. A hardware unit that provides
outside the list structure.
communications, monitoring, and diagnostic functions to
side. A part of a partitionable CPC that can run as a a central processor complex (CPC).
physical partition and is typically referred to as the
symmetry. The characteristic of a sysplex where all
A-side or the B-side.
systems, or certain subsets of the systems, have the
single point of control. The characteristic a sysplex same hardware and software configurations and share
displays when you can accomplish a given set of tasks the same resources.
from a single workstation, even if you need multiple IBM
SYSLOG. System log
and vendor products to accomplish that particular set of
tasks.
sysplex. A set of MVS systems communicating and
cooperating with each other through certain multisystem
single system image. The characteristic a product
hardware components and software services to process
displays when multiple images of the product can be
customer workloads. See also MVS system, Parallel
viewed and managed as one image.
Sysplex.
single-image (SI) mode. A mode of operation for a
multiprocessor (MP) system that allows it to function as

Glossary 47
sysplex couple data set. A couple data set that
contains sysplex-wide data about systems, groups, and U
members that use XCF services. All MVS systems in a
uniprocessor (UP). A CPC that contains one CP and
sysplex must have connectivity to the sysplex couple
is not partitionable.
data set. See also couple data set.
UP. Uniprocessor.
Sysplex Timer. An IBM unit that synchronizes the
time-of-day (TOD) clocks in multiple processors or
processor sides. External Time Reference (ETR) is the
MVS generic name for the IBM Sysplex Timer (9037).
V
VM. Virtual Machine.
system control element (SCE). Hardware that
handles the transfer of data and control information VSAM. Virtual Storage Access Method.
associated with storage requests between the elements
of the processor. VTAM. Virtual Telecommunications Access Method.

System/390 microprocessor cluster. A configuration

that consists of central processor complexes (CPCs) W
and may have one or more coupling facilities.
WLM. MVS workload management.

T
X
tightly coupled. Multiple CPs that share storage and
are controlled by a single copy of MVS. See also XCF. Cross-system coupling facility.
loosely coupled, tightly coupled multiprocessor.
XCF PR/SM policy. In a multisystem sysplex on
tightly coupled multiprocessor. Any CPC with PR/SM, the actions that XCF takes when one MVS
multiple CPs. system in the sysplex fails. This policy provides high
availability for multisystem applications in the sysplex.
TOR. Terminal-owning region.
XCF-local mode. The state of a system in which XCF
TSCF. Target System Control Facility. The licensed provides limited services on one system and does not
program System Automation for OS/390 includes all of provide signalling services between MVS systems. See
the function previosuly provided by TSCF. also single-system sysplex.

XRF. Extended recovery facility.

48 OS/390 V2R5.0 Parallel Sysplex Overview

Index
data sharing (continued)
Numerics data access (continued)
9021 511-based models 32 sharing data using the Coupling Facility 15
9021 711-based models 32 using a single data server 12
using partitioned data 13
data validity
A consistency 12
AOC/MVS (Automated Operations Control) 35
serialization 11
Automated Operations Control 35
description 11
See also AOC/MVS (Automated Operations Control)
in a sysplex 11
using DB2 17
B using IMS DB 17
DATABASE 2 34
batch
running in parallel 23 See also DB2 (DATABASE 2)
benefits DB2 (DATABASE 2) 34
of a sysplex 4 exploitation of Coupling Facility 17
DFSMS 33

C E
CICS (Customer Information Control System) 34
as transaction manager for parallel OLTP 27 Enterprise Performance Data Manager 36
CICSPlex SM (CICSPlex System Manager/ESA) 35 See also EPDM (IBM SystemView Enterprise
CICSPlex System Manager/ESA 35 Performance Data Manager/MVS)
See also CICSPlex SM (CICSPlex System Enterprise Systems Connection 32
Manager/ESA) See also ESCON (Enterprise Systems Connection)
configuration EPDM (IBM SystemView Enterprise Performance
large systems data sharing 39 Data Manager/MVS) 36
sysplex sample 39 ES/9000 processors
using a S/390 microprocessor cluster 40 9021 511-based models 32
using mixed processors 41 9021 711-based models 32
consistency of data 12 ESCD (ESCON Director) 32
Coupling Facility ESCM (ESCON Manager) 37
description 16 ESCON (Enterprise Systems Connection) 32
exploiters 17 ESCON control units
multisystem data sharing 15 3990 Storage Control Model 6 33
structures 16 9343 Storage Controller 33
technology 16 9345 Direct Access Storage Device 33
cross-system coupling facility 7 ESCON Director 32
See also XCF (cross-system coupling facility) See also ESCD (ESCON Director)
Customer Information Control System 34 ESCON I/O devices
See also CICS (Customer Information Control 3172 33
System) 3174 33
3490E 33
3745 33
D 3746 33
Data Facility Storage Management Subsystem 33 ESCON Manager 37
See also DFSMS See also ESCM (ESCON Manager)
data management system evolution of sysplex 4
for OLTP parallelism 27
data sharing
comparison to multisystem data sharing 12
data access
sharing data between two systems 14

multiprocessing (continued)
F description 20
follow-on phase multisystem data sharing
definition xiv partitioning data 13
sharing data between two systems 14
single data server 12
H using the Coupling Facility 15
hardware
MVS (Multiple Virtual Storage)
Coupling Facility 32
use of term xiv
coupling facility channels 32
MVS workload manager 28
ES/9000 processors 32
See also WLM (MVS workload manager)
ESCD (ESCON Director) 32
MVS/ESA 33
ESCON 32
ESCON control units 33
I/O 33
in a sysplex 3
O
OLTP (online transaction processing) 24
microprocessor cluster 32 online transaction processing
S/390 processors 32 See also OLTP (online transaction processing)
Sysplex Timer 32 running in parallel 24
Hardware Configuration Definition 37 OPC/ESA (Operations Planning and Control) 35
See also HCD (Hardware Configuration Definition) Operations Planning and Control 35
HCD (Hardware Configuration Definition) 37 See also OPC/ESA (Operations Planning and
Control)
OS/390
I and MVS xiv
I/O 33
in a sysplex 33
IMS DB (Information Management System Database
Manager) 34
exploitation of Coupling Facility 17
IMS TM (Information Management System
P
parallel processing
Transaction Manager) 35 comparison to multiprocessing 20
as transaction manager for parallel OLTP 27 description 19
Information Management System Database for a lengthy application 22
Manager 34 for an increased number of transactions 21
See also IMS DB (Information Management System for batch 23
Database Manager) for OLTP 24
Information Management System Transaction for queries 24
Manager 35 hardware that enables 29
See also IMS TM (Information Management System potential in a sysplex 20
Transaction Manager) running MVS workloads 23
software that enables parallelism for OLTP 24
parallel query server 24
J parallel transaction server 29, 32, 40
JES2 33
performance goals 28
JES3 33
product availability
follow-on phase xiv
L products in a sysplex
loosely coupled configuration hardware
definition 6 9021 511-based models 32
work potential 7 9021 711-based models 32
Coupling Facility 32
coupling facility channels 32
M ESCD (ESCON Director) 32
microprocessor cluster 32 ESCON 32
multiprocessing ESCON control units 33
comparison to parallel processing 20 I/O 33
I/O devices 33

50 OS/390 V2R5.0 Parallel Sysplex Overview

products in a sysplex (continued) software (continued)
hardware (continued) CICSPlex SM 35
microprocessor cluster 32 DB2 34
S/390 processors 32 DFSMS 33
Sysplex Timer 32 EPDM 36
OS/390 33 ESCM 37
software HCD 37
AOC/MVS 35 IMS DB 34
CICS 34 IMS TM 35
CICSPlex SM 35 in a sysplex 3
DB2 34 JES2 33
DFSMS 33 JES3 33
EPDM 36 MVS workload manager 35
ESCM 37 MVS/ESA 33
HCD 37 OPC/ESA 35
IMS DB 34 OS/390 33
IMS TM 35 RACF 36
JES2 33 RMF 36
JES3 33 SDSF 36
MVS workload manager 35 SLR 36
MVS/ESA 33 SMF 35
OPC/ESA 35 VSAM 34
OS/390 33 VTAM 34
RACF 36 sysplex
RMF 36 announced as a platform 1
SDSF 36 benefits 4
SLR 36 configurations 39
SMF 35 data sharing 15
VSAM 34 definition 1
VTAM 34 enhancements 8
evolution of 4
hardware 3, 32
Q origin of name 7
queries products 32
running in parallel 24 sample configuration
large systems data sharing 39
using a S/390 microprocessor cluster 40
R using mixed processors 41
RACF (Resource Access Control Facility) 36
software 3, 33
Resource Access Control Facility 36
work potential
See also RACF (Resource Access Control Facility)
of base sysplex 8
Resource Measurement Facility 36
of Parallel Sysplex 9
See also RMF (Resource Measurement Facility)
Sysplex Timer 32
RMF (Resource Measurement Facility) 36
System Display and Search Facility 36
See also SDSF (System Display and Search Facility)
S system management facilities 35
See also SMF (system management facilities)
SDSF (System Display and Search Facility) 36
serialization 11 System/390 Parallel Sysplex Offering 40
Service Level Reporter 36
See also SLR (Service Level Reporter)
SLR (Service Level Reporter) 36
T
tightly coupled multiprocessor
SMF (system management facilities) 35
definition 5
software
work potential 6
AOC/MVS 35
transaction
CICS 34
description 24

Index 51
transaction (continued)
running in parallel 24
transaction manager
CICS 27
IMS TM 27
support for OLTP parallelism 24

U
uniprocessor
definition 5
work potential 5

V
Virtual Storage Access Method 34
See also VSAM (Virtual Storage Access Method)
Virtual Telecommunications Access Method 34
See also VTAM (Virtual Telecommunications Access
Method)
VSAM (Virtual Storage Access Method) 34
exploitation of Coupling Facility 17
VTAM (Virtual Telecommunications Access
Method) 34

W
WLM (MVS workload manager) 28, 35
defining performance goals 28
work potential
of a base sysplex 8
of a loosely coupled configuration 7
of a tightly coupled multiprocessor 6
of a uniprocessor 5
of an Parallel Sysplex 9
workload management 28
workload management
dynamic resource balancing 28
in a sysplex 28
reporting 28

X
XCF (cross-system coupling facility) 7

52 OS/390 V2R5.0 Parallel Sysplex Overview

Readers' Comments — We'd Like to Hear from You
OS/390
Parallel Sysplex Overview:
Introducing Data Sharing and
Parallelism in a Sysplex
Publication No. GC28-1860-03

Overall, how satisfied are you with the information in this book?
Very Very
Satisfied Satisfied Neutral Dissatisfied Dissatisfied
Overall satisfaction Ø Ø Ø Ø Ø

How satisfied are you that the information in this book is:
Very Very
Satisfied Satisfied Neutral Dissatisfied Dissatisfied
Accurate Ø Ø Ø Ø Ø
Complete Ø Ø Ø Ø Ø
Easy to find Ø Ø Ø Ø Ø
Easy to understand Ø Ø Ø Ø Ø
Well organized Ø Ø Ø Ø Ø
Applicable to your tasks Ø Ø Ø Ø Ø

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? Ø Yes Ø No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments
in any way it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.
Cut or Fold
Readers' Comments — We'd Like to Hear from You

IBM
Along Line
GC28-1860-03


Fold and Tape Please do not staple Fold and Tape

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM Corporation
Department 55JA, Mail Station P384
522 South Road
Poughkeepsie, NY 12601-5400

Fold and Tape Please do not staple Fold and Tape

Cut or Fold
GC28-1860-03 Along Line
IBM 

File Number: S370/S390-34

Program Number: 5647-A01

Printed in U.S.A.

GC28-186ð-ð3

WD515G 2.0 en WD5152LSG
No ratings yet
WD515G 2.0 en WD5152LSG
114 pages
au-LPM Troubleshooting PDF
No ratings yet
au-LPM Troubleshooting PDF
19 pages
Netezza System Admin Guide
100% (1)
Netezza System Admin Guide
556 pages
IBM DS8900F Performance Best Practices and Monitoring
No ratings yet
IBM DS8900F Performance Best Practices and Monitoring
294 pages
Doc
No ratings yet
Doc
500 pages
Front Cover: Ibm Infosphere Information Server Administration V9.1
No ratings yet
Front Cover: Ibm Infosphere Information Server Administration V9.1
560 pages
IBM System Storage DS8870 Performance With High Performance Flash Enclosure
No ratings yet
IBM System Storage DS8870 Performance With High Performance Flash Enclosure
32 pages
Powerha Systemmirror For Aix V7.1 Two-Node Quick Configuration Guide
No ratings yet
Powerha Systemmirror For Aix V7.1 Two-Node Quick Configuration Guide
34 pages
GPFS Commands
No ratings yet
GPFS Commands
2 pages
ES074STUD
No ratings yet
ES074STUD
456 pages
AIX 7.1 Operating System and Device Management PDF
No ratings yet
AIX 7.1 Operating System and Device Management PDF
670 pages
Ibm Aix Power Vs Linux x86 en
No ratings yet
Ibm Aix Power Vs Linux x86 en
21 pages
At 911 Stud
No ratings yet
At 911 Stud
144 pages
DS8000 - Training
No ratings yet
DS8000 - Training
55 pages
Front Cover: Ibm Infosphere Information Server Administration V9.1
0% (1)
Front Cover: Ibm Infosphere Information Server Administration V9.1
166 pages
WM 6761 Inst
100% (2)
WM 6761 Inst
1,206 pages
Platform Acl, Pop
No ratings yet
Platform Acl, Pop
23 pages
ZM100 - Student Notebookv2
No ratings yet
ZM100 - Student Notebookv2
214 pages
MIMIX Operations 5250
No ratings yet
MIMIX Operations 5250
403 pages
Ejercicios II
No ratings yet
Ejercicios II
124 pages
Creating IBM I Client Partition
No ratings yet
Creating IBM I Client Partition
24 pages
CICS Tutorial
No ratings yet
CICS Tutorial
57 pages
Front Cover: What's New in IBM I 7.3 and IBM POWER8 Systems
No ratings yet
Front Cover: What's New in IBM I 7.3 and IBM POWER8 Systems
29 pages
z16-Technical-Overview-50M-KennyStine
No ratings yet
z16-Technical-Overview-50M-KennyStine
64 pages
Exercise Guide ESU03GX-3
No ratings yet
Exercise Guide ESU03GX-3
134 pages
GDV9P km130 Instructorexercises
No ratings yet
GDV9P km130 Instructorexercises
88 pages
OSA Implementation PDF
No ratings yet
OSA Implementation PDF
290 pages
IBM I Disk Management
No ratings yet
IBM I Disk Management
158 pages
IBM System Storage DS8000 Architecture and Implementation
No ratings yet
IBM System Storage DS8000 Architecture and Implementation
656 pages
Vmware
No ratings yet
Vmware
208 pages
Ol 629 Stud
No ratings yet
Ol 629 Stud
436 pages
Configuring External Authentication Interface (EAI) : Lab Exercises
No ratings yet
Configuring External Authentication Interface (EAI) : Lab Exercises
18 pages
San Ibm Redbook Ficon
No ratings yet
San Ibm Redbook Ficon
452 pages
Rexx PDF
100% (1)
Rexx PDF
218 pages
Debugging Core Files Crash Dumps UNIX Linux
No ratings yet
Debugging Core Files Crash Dumps UNIX Linux
91 pages
Ieav2r4 SDSF
100% (1)
Ieav2r4 SDSF
94 pages
Front Cover: Query and Manage XML Data With DB2 9
No ratings yet
Front Cover: Query and Manage XML Data With DB2 9
14 pages
CICS Administration Reference
No ratings yet
CICS Administration Reference
575 pages
DB2 For I-7-2overview
No ratings yet
DB2 For I-7-2overview
64 pages
IMS Transaction Message Processing: Unit 6
No ratings yet
IMS Transaction Message Processing: Unit 6
23 pages
Cloud Pak For Data System Certification Path
No ratings yet
Cloud Pak For Data System Certification Path
15 pages
CE1319XSTUD
No ratings yet
CE1319XSTUD
114 pages
Hercules General Info
No ratings yet
Hercules General Info
176 pages
Ds8000 Architecture Configuration
No ratings yet
Ds8000 Architecture Configuration
131 pages
CertStudyGuideIDGv7.1SolnImplSlides 20150814
100% (2)
CertStudyGuideIDGv7.1SolnImplSlides 20150814
54 pages
Unit1 Cloud Intro v2021
No ratings yet
Unit1 Cloud Intro v2021
67 pages
WB 8141 Stud
No ratings yet
WB 8141 Stud
636 pages
42 POWER8 Enterprise E870 From Experience
100% (1)
42 POWER8 Enterprise E870 From Experience
63 pages
Solaris To Linux Migration
No ratings yet
Solaris To Linux Migration
450 pages
Front Cover: AIX Internals & Performance IV: I/O Management - Part 2 (Specialized I/O)
No ratings yet
Front Cover: AIX Internals & Performance IV: I/O Management - Part 2 (Specialized I/O)
46 pages
Front Cover: Linux Network Administration I: TCP/IP and TCP/IP Services
No ratings yet
Front Cover: Linux Network Administration I: TCP/IP and TCP/IP Services
26 pages
Programming Backup Recovery and Media Services For i5/OS Commands
No ratings yet
Programming Backup Recovery and Media Services For i5/OS Commands
526 pages
000 377exam
No ratings yet
000 377exam
10 pages
DRBD-Cookbook: How to create your own cluster solution, without SAN or NAS!
From Everand
DRBD-Cookbook: How to create your own cluster solution, without SAN or NAS!
Joerg Christian Seubert
No ratings yet
VMware Horizon View Essentials
From Everand
VMware Horizon View Essentials
Peter von Oven
No ratings yet
IBM InfoSphere Replication Server and Data Event Publisher
From Everand
IBM InfoSphere Replication Server and Data Event Publisher
Pav Kumar-Chatterjee
No ratings yet
IBM Integration Bus Third Edition
From Everand
IBM Integration Bus Third Edition
Gerardus Blokdyk
No ratings yet
DB2 Exam C2090-320 Practice Questions
From Everand
DB2 Exam C2090-320 Practice Questions
Robert Wingate
No ratings yet
DB2 Exam C2090-313 Practice Questions
From Everand
DB2 Exam C2090-313 Practice Questions
Robert Wingate
No ratings yet
Getting Started: Journey To Modernization With Ibm Z
No ratings yet
Getting Started: Journey To Modernization With Ibm Z
90 pages
IBM Fibre Channel Endpoint Security For IBM DS8900F and IBM Z
No ratings yet
IBM Fibre Channel Endpoint Security For IBM DS8900F and IBM Z
116 pages
Four Ways To Transform Your Mainframe For A Hybrid Cloud World
No ratings yet
Four Ways To Transform Your Mainframe For A Hybrid Cloud World
30 pages
Paper: Converting Adabas To Ibm Db2 For Z/Os With Consistads
No ratings yet
Paper: Converting Adabas To Ibm Db2 For Z/Os With Consistads
36 pages
sg248850 - IBM z15 Technical Introduction
No ratings yet
sg248850 - IBM z15 Technical Introduction
130 pages
IBM Security Guardium Key Lifecycle Manager: Books
No ratings yet
IBM Security Guardium Key Lifecycle Manager: Books
128 pages
Preparing CICS Connections
No ratings yet
Preparing CICS Connections
10 pages
sg248460 - IBM z14 Configuration Setup
No ratings yet
sg248460 - IBM z14 Configuration Setup
428 pages
Storage Multi-Tenancy For Red Hat Openshift Platform With Ibm Storage
No ratings yet
Storage Multi-Tenancy For Red Hat Openshift Platform With Ibm Storage
54 pages
sg248377 - Practical Migration From x86 To LinuxONE
No ratings yet
sg248377 - Practical Migration From x86 To LinuxONE
228 pages
Sg247851 - IBM ZOS Management Facility V2R3
No ratings yet
Sg247851 - IBM ZOS Management Facility V2R3
614 pages
sg245444 - IBM Z Connectivity Handbook
No ratings yet
sg245444 - IBM Z Connectivity Handbook
238 pages
Redbook - IBM Personal Communications and IBM zOS TTLS Enablement - Technical Enablement Series
No ratings yet
Redbook - IBM Personal Communications and IBM zOS TTLS Enablement - Technical Enablement Series
42 pages
Sg248427 - A Guide To JES3 To JES2 Migration
No ratings yet
Sg248427 - A Guide To JES3 To JES2 Migration
288 pages
Configuring TN3270 Server
No ratings yet
Configuring TN3270 Server
80 pages
Configuring IBM Channel Attach
No ratings yet
Configuring IBM Channel Attach
20 pages
CISCO CIP Migration Scenario
No ratings yet
CISCO CIP Migration Scenario
18 pages
Sample Router Configurations
No ratings yet
Sample Router Configurations
8 pages
Configuring Cisco Mainframe Channel Connection Adapters
No ratings yet
Configuring Cisco Mainframe Channel Connection Adapters
80 pages
Jes Material
100% (1)
Jes Material
20 pages
TK5-Introduction-and-User-Manual
No ratings yet
TK5-Introduction-and-User-Manual
51 pages
Zos Installation
No ratings yet
Zos Installation
304 pages
Jes2 Notes
No ratings yet
Jes2 Notes
16 pages
IBM 360 Series Mainframe OSTL
No ratings yet
IBM 360 Series Mainframe OSTL
71 pages
Jes2 Commanly Used Command
No ratings yet
Jes2 Commanly Used Command
2 pages
System Commands
No ratings yet
System Commands
796 pages
Mainframe Refresher
No ratings yet
Mainframe Refresher
182 pages
SYSA - Bravo Scan - May2012
No ratings yet
SYSA - Bravo Scan - May2012
18 pages
IBM EC12 sg248049
No ratings yet
IBM EC12 sg248049
490 pages
Progress Report South RMGF - 30th Jan 2015
No ratings yet
Progress Report South RMGF - 30th Jan 2015
66 pages
Jclprintvital 1
No ratings yet
Jclprintvital 1
38 pages
Idac400 v2r3
No ratings yet
Idac400 v2r3
130 pages
IBM High Level Assembler
100% (1)
IBM High Level Assembler
2 pages
Parallel Sysplex
No ratings yet
Parallel Sysplex
4 pages
Mainframe Operator Certificate Level II 28Feb
No ratings yet
Mainframe Operator Certificate Level II 28Feb
1 page
ABCs of Z-OS System Programming Vol. 5 -Sg246985
No ratings yet
ABCs of Z-OS System Programming Vol. 5 -Sg246985
336 pages
Resume of Alinkjobs
No ratings yet
Resume of Alinkjobs
2 pages
SHARE Boston 2013 Common zOS Problems
No ratings yet
SHARE Boston 2013 Common zOS Problems
40 pages
JCL Example
No ratings yet
JCL Example
8 pages
VSAM - Patni
No ratings yet
VSAM - Patni
75 pages
Zos Basics (Lpar, Sysplex Coupling Facility Concepts)
No ratings yet
Zos Basics (Lpar, Sysplex Coupling Facility Concepts)
7 pages
IBM Mainframe History
100% (1)
IBM Mainframe History
42 pages
Interskill Learning Course Assessment List
No ratings yet
Interskill Learning Course Assessment List
5 pages
Test Job Preparation
No ratings yet
Test Job Preparation
5 pages
DUMBS
100% (2)
DUMBS
60 pages
Systemz 06
No ratings yet
Systemz 06
1 page
ZSeries and ZOS Reference Guide
No ratings yet
ZSeries and ZOS Reference Guide
49 pages
Cics VR
No ratings yet
Cics VR
32 pages
Program Directory For Websphere MQ For Z/Os
No ratings yet
Program Directory For Websphere MQ For Z/Os
68 pages

Parallel Sysplex Overview

Uploaded by

Parallel Sysplex Overview

Uploaded by

GC28-1860-03

Parallel Sysplex Overview:

Parallel Sysplex Overview:

Fourth Edition, December, 1998

This is a major revision of GC28-1860-02.

FAX (United States & Canada): 1+914+432-9405

IBMLink (United States customers only): IBMUSM10(MHVRCFS)

Make sure to include the following in your comment or note:

About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Data Sharing in a Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Parallel Processing in a Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . 19

 Copyright IBM Corp. 1994, 1998 iii

Introduction to Sample Sysplex Configurations . . . . . . . . . . . . . . . . 39

iv OS/390 V2R5.0 Parallel Sysplex Overview

 Copyright IBM Corp. 1994, 1998 vii

IBM Director of Licensing

Such information may be available, subject to appropriate terms and conditions,

 Copyright IBM Corp. 1994, 1998 ix

 Copyright IBM Corp. 1994, 1998 xi

This publication describes:

Note that this publication does not differentiate between a sysplex

The roll-out of sysplex support across products is occurring over time, in

There might be changes to the implementation or availability of new

Who Should Use This Publication

 Copyright IBM Corp. 1994, 1998 xiii

 In this publication, the licensed program DB2 for MVS/ESA is referred to as

Notes on Product Availability

Determining If a Publication Is Current

xiv OS/390 V2R5.0 Parallel Sysplex Overview

Where to Find More Information

Figure 1. Parallel Sysplex Library Books

About This Publication xv

| Parallel Sysplex Tasks

| Planning the Parallel Sysplex

| Designing the Parallel Sysplex

xvi OS/390 V2R5.0 Parallel Sysplex Overview

| Selecting Software - Overview

| Migrating to a Parallel Sysplex

| Migrating Applications to a Parallel Sysplex

About This Publication xvii

| Planning for Connectivity

| Monitoring Performance in a Parallel Sysplex

| Planning for Workloads

xviii OS/390 V2R5.0 Parallel Sysplex Overview

| Planning for Security

| Planning for Automation

| Cloning Systems and Images

About This Publication xix

| Understanding Coupling Facility Levels and Functions for Hardware and

| Planning the Sizing of Structures

| Shutting down the Coupling Facility and Removing Structures

| Developing Naming Conventions for Data Sharing Products

xx OS/390 V2R5.0 Parallel Sysplex Overview

| Creating the ARM policy

| Implementing the WLM policy

| Creating the CFRM policy

About This Publication xxi

| Installing the Parallel Sysplex

| Defining Data Sets

xxii OS/390 V2R5.0 Parallel Sysplex Overview

| Defining DFSMS and the SMS Configuration

| Planning the Network Configuration for the Parallel Sysplex

| Setting up Data Sharing

| Planning and Implementing CICS Data Sharing

| Planning and Implementing IMS Data Sharing

About This Publication xxiii

| Planning and Implementing VSAM RLS Data Sharing

| Planning Day-to-Day Operations

| Starting and Stopping Subsystems

xxiv OS/390 V2R5.0 Parallel Sysplex Overview

| Monitoring the Parallel Sysplex

| Recovering from Problems

About This Publication xxv

| Getting Started Parallel Sysplex Publications

| CICS Transaction Server Publications

In this publication, the licensed program DB2 for MVS/ESA is referred to as