Achieving the highest levels of Parallel Sysplex availability / / [Frank Kyne ... et al.]

• Pubblicazione: [S.l.], : IBM, International Technical Support Organization, c2004
• Edizione: 1st ed.
• Descrizione fisica: xiv, 274 p. : ill
• Disciplina: 004/.35
• Soggetto topico: Parallel processing (Electronic computers); Application software - Development; Computer architecture
• Altri autori: KyneFrank
• Note generali: "December 2004."; "SG24-6061-00."
• Nota di bibliografia: Includes bibliographical references and index.
• Nota di contenuto: Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. Introduction -- 1.1 Why availability is important to you -- 1.2 Cost of an outage -- 1.2.1 Component outage versus service outage -- 1.2.2 Availability overview -- 1.3 Continuous availability in a Parallel Sysplex -- 1.3.1 Availability definitions -- 1.3.2 Spectrum of availability factors -- 1.4 What this book is all about -- Chapter 2. Hardware -- 2.1 Environmental -- 2.1.1 Power -- 2.1.2 Cooling -- 2.1.3 Geographic location -- 2.1.4 Physical security -- 2.1.5 Automation -- 2.1.6 Physical configuration control -- 2.2 Central Processing Complexes (CPCs) -- 2.2.1 How many CPCs to have -- 2.2.2 Availability features -- 2.2.3 Concurrent upgrade -- 2.2.4 Redundant capacity -- 2.2.5 Hardware configuration -- 2.3 Coupling Facilities -- 2.3.1 Coupling Facility Capacity -- 2.3.2 Failure isolation -- 2.3.3 Recovering from CF failure -- 2.3.4 How many CFs -- 2.3.5 Coupling Facility Control Code Level considerations -- 2.3.6 CF maintenance procedures -- 2.3.7 CF volatility -- 2.3.8 Nondisruptive Coupling Facilities hardware upgrades -- 2.4 9037 Sysplex Timers considerations -- 2.4.1 Sysplex Timer® Models -- 2.4.2 Recovering from loss of all timer signals -- 2.4.3 Maximizing 9037 availability -- 2.4.4 Message time ordering -- 2.5 Intelligent Resource Director -- 2.5.1 An IRD Illustration -- 2.5.2 WLM LPAR CPU Management -- 2.5.3 Dynamic Channel-path Management (DCM) -- 2.5.4 Channel Subsystem I/O Priority Queueing -- 2.6 Switches -- 2.6.1 ESCON Directors -- 2.6.2 FICON Switches -- 2.7 DASD -- 2.7.1 Peer to Peer Remote Copy (PPRC) -- 2.7.2 Extended Remote Copy (XRC) -- 2.8 Geographically Dispersed Parallel Sysplex™ -- 2.8.1 Data consistency -- 2.8.2 The HyperSwap -- 2.9 Other hardware equipment. ; 2.9.1 3494 Tape library/VTS -- 2.9.2 Stand-alone tape -- 2.9.3 3174, 2074 -- Chapter 3. z/OS -- 3.1 Configure software for high availability -- 3.1.1 Couple Data Sets -- 3.1.2 Other important data sets -- 3.1.3 Sysres and master catalog sharing -- 3.2 Consoles -- 3.2.1 Addressing WTO and WTOR buffer shortages -- 3.2.2 EMCS consoles -- 3.2.3 Using the HMC as a console -- 3.2.4 Hardware consoles -- 3.2.5 Console setup recommendations -- 3.3 Coupling Facility management -- 3.3.1 Defining CFs and structures -- 3.3.2 Structure placement -- 3.3.3 Structure rebuild considerations -- 3.3.4 Structure duplexing -- 3.3.5 Structure monitoring -- 3.3.6 Structure recommendations -- 3.4 CF operations -- 3.5 IBM Health Checker for z/OS and Sysplex -- 3.5.1 Health Checker description -- 3.5.2 IBM Health Checker recommendations -- 3.6 z/OS msys for Operations -- 3.6.1 Automated Recovery Actions -- 3.6.2 Sysplex operation -- 3.6.3 z/OS msys for Operations recommendations -- 3.7 Sysplex Failure Management (SFM) -- 3.7.1 Configuring for status update missing conditions -- 3.7.2 Configuring for signaling connectivity failures -- 3.7.3 Configuring for Coupling Facility failures -- 3.7.4 SFM recommendations -- 3.8 Automatic Restart Manager (ARM) -- 3.8.1 Configuring for Automatic Restart Management -- 3.8.2 ARMWRAP - The ARM JCL Wrapper -- 3.8.3 ARM recommendations -- 3.9 System Logger (LOGR) -- 3.9.1 Logstream types -- 3.9.2 CF structure considerations -- 3.9.3 System-Managed CF Structure Duplexing -- 3.9.4 DASD based staging data set considerations (DASD-Only) -- 3.9.5 DASD-based staging data set considerations (Coupling Facility) -- 3.9.6 DASD-based log data set considerations -- 3.9.7 Offload considerations -- 3.9.8 Log data retention -- 3.9.9 GMT considerations -- 3.9.10 System Logger recovery -- 3.9.11 System Logger recommendations. ; 3.10 Cross-system Coupling Facility (XCF) -- 3.10.1 XCF systems, groups, and members -- 3.10.2 XCF signaling paths -- 3.10.3 XCF Transport Classes -- 3.10.4 XCF signal path performance problems -- 3.10.5 XCF message buffer length performance problems -- 3.10.6 XCF message buffer space performance problems -- 3.10.7 XCF Coupling Facility performance problems -- 3.10.8 XCF recommendations -- 3.11 GRS -- 3.11.1 GRS start options -- 3.11.2 Dynamic RNLs -- 3.11.3 GRS Ring Availability considerations - Fully connected complex -- 3.11.4 GRS Ring Availability considerations - Mixed complex -- 3.11.5 GRS Star Availability considerations -- 3.11.6 SYNCHRES option -- 3.11.7 Resource Name Lists (RNLs) -- 3.11.8 RNL design -- 3.11.9 GRS monitor (ISGRUNAU) -- 3.11.10 RNL syntax checking -- 3.11.11 GRS recommendations -- 3.12 Tape sharing -- 3.12.1 IEFAUTOS -- 3.12.2 ATS Star -- 3.12.3 Coexistence between Dedicated, IEFAUTOS, and ATS Star -- 3.12.4 Tape-sharing recommendations -- 3.13 JES2 -- 3.13.1 JES2 SPOOL considerations -- 3.13.2 JES2 Checkpoint considerations -- 3.13.3 JES2 Checkpoint access -- 3.13.4 JES2 Checkpoint performance -- 3.13.5 JES2 Checkpoint management -- 3.13.6 JES2 Health Monitor -- 3.13.7 Scheduling environment -- 3.13.8 WLM-managed initiators -- 3.13.9 JESLOG SPIN data sets -- 3.13.10 JES2 recommendations -- 3.14 WLM -- 3.14.1 Service classes -- 3.14.2 WLM recommendations -- 3.15 UNIX System Services -- 3.15.1 Shared HFS -- 3.15.2 Automove -- 3.15.3 zFS -- 3.15.4 BRLM issues -- 3.15.5 UNIX System Services recommendations -- 3.16 RACF -- 3.16.1 RACF sysplex communication -- 3.16.2 RACF non-data sharing mode -- 3.16.3 RACF data sharing mode -- 3.16.4 RACF read-only mode -- 3.16.5 RACF recovery procedures -- 3.16.6 PKI Services -- 3.16.7 RACF recommendations -- 3.17 DFSMShsm -- 3.17.1 Common Recall Queue. ; 3.17.2 Hot standby (Secondary Host promotion) -- 3.17.3 Use of record level sharing (RLS) for CDSs -- 3.17.4 DFSMShsm recommendations -- 3.18 Catalog -- 3.18.1 VVDS mode catalog sharing -- 3.18.2 Enhanced catalog sharing (ECS) -- 3.18.3 Catalog integrity -- 3.18.4 Catalog performance -- 3.18.5 Catalog sizing -- 3.18.6 Catalog backup and recovery -- 3.18.7 Catalog security -- 3.18.8 Catalog recommendations -- 3.19 Software maintenance -- 3.19.1 Types of maintenance -- 3.19.2 Classification of maintenance -- 3.19.3 Sources of maintenance -- 3.19.4 Consolidated Service Test (CST) -- 3.19.5 Enhanced Holddata -- 3.19.6 Software maintenance recommendations -- 3.20 Testing the sysplex -- 3.20.1 Test Sysplex -- 3.20.2 Sysplex testing recommendations -- 3.21 Planned outages -- 3.21.1 APPC/MVS configuration -- 3.21.2 APPC/MVS Transaction Scheduler -- 3.21.3 Authorized Program Facility (APF) -- 3.21.4 Diagnostics -- 3.21.5 Dump options -- 3.21.6 Dump Analysis and Elimination (DAE) -- 3.21.7 Console management -- 3.21.8 Console group management -- 3.21.9 Exits -- 3.21.10 Global Resource Serialization (GRS) -- 3.21.11 IODF management -- 3.21.12 IOS -- 3.21.13 LNKLST -- 3.21.14 LOGREC error recording -- 3.21.15 LPALST -- 3.21.16 Message Processing Facility (MPF) -- 3.21.17 MVS Message Service (MMS) -- 3.21.18 Local Page Data Sets -- 3.21.19 Parmlib concatenation -- 3.21.20 Products -- 3.21.21 Program properties table -- 3.21.22 Run-time library services (RTLS) -- 3.21.23 SLIP -- 3.21.24 System Measurement Facility (SMF) -- 3.21.25 Storage Management Subsystem (SMS) -- 3.21.26 Subsystem Names (SSN) -- 3.21.27 System Resources Manager (SRM) -- 3.21.28 Time Sharing Option (TSO) -- 3.21.29 UNIX System Services (USS) -- 3.21.30 XCF -- 3.21.31 Planned outages recommendations -- 3.22 Unplanned outages -- 3.22.1 Dump options -- 3.22.2 ABEND dumps -- 3.22.3 SVC dumps. ; 3.22.4 Stand-alone dump -- 3.22.5 Dump suppression -- 3.22.6 SLIP traps -- 3.22.7 System Hardcopy log -- 3.22.8 Environmental Record Editing and Printing (EREP) -- 3.22.9 Unplanned outages recommendations -- Chapter 4. Systems Management -- 4.1 Overall Availability Management processes -- 4.1.1 Develop availability practices -- 4.1.2 Develop standards -- 4.2 Service Level Management -- 4.2.1 Business requirements -- 4.2.2 Negotiating objectives -- 4.2.3 Documenting agreements - Managing expectations -- 4.2.4 Building infrastructure - Technical and support -- 4.2.5 Measuring availability -- 4.2.6 Track and report availability -- 4.2.7 Customer satisfaction -- 4.3 Change Management -- 4.3.1 Develop and prepare change -- 4.3.2 Assess and minimize risk -- 4.3.3 Testing -- 4.3.4 Back-out planning -- 4.3.5 Verify change readiness -- 4.3.6 Schedule change -- 4.3.7 Communicate change -- 4.3.8 Implement and document -- 4.3.9 Change record content -- 4.3.10 Review quality -- 4.4 Organization -- 4.4.1 Skills -- 4.4.2 Help desk activities -- 4.4.3 Operations -- 4.4.4 Automation -- 4.4.5 Application testing -- 4.4.6 Passive and active monitoring -- 4.5 Recovery Management -- 4.5.1 Terminology -- 4.5.2 Recovery potential initiatives -- 4.5.3 Recovery Management activities -- 4.5.4 Event Management -- 4.5.5 Incident Management -- 4.5.6 Crisis Management -- 4.6 Problem Management -- 4.6.1 Data tracking and reporting -- 4.6.2 Causal analysis -- 4.6.3 Maintenance policies -- 4.7 Performance Management -- 4.8 Capacity planning -- 4.9 Security Management -- 4.9.1 Security policy -- 4.9.2 Physical security -- 4.10 Configuration Management -- 4.10.1 Component Failure Impact Analysis -- 4.11 Enterprise architecture -- 4.11.1 Infrastructure simplification -- 4.11.2 Ideal mainframe implementations -- 4.11.3 Ideal BladeCenter implementation. ; 4.11.4 Examples and scenarios demonstrate real infrastructure simplification efforts.
• Sommario/riassunto: This IBM Redbooks publication provides an example of the "ideal" Parallel Sysplex environment (one that is configured to deliver the highest levels of application availability), and describes the features and functions used in this environment. For each function, we describe briefly what it does and what its benefit is, and refer to the appropriate implementation documentation. In this document, we discuss how to configure hardware and software, and how to manage systems processes for maximum availability in a Parallel Sysplex environment. We discuss the basic concepts of continuous availability and describe a structured approach to developing and implementing a continuous availability solution. This document provides a list of items to consider for trying to achieve near-continuous application availability and should be used as a guide when creating a high-availability Parallel Sysplex. Information is provided in recommendations lists and will help you configure and manage your IT environment to meet your availability requirements. This publication is intended to help customers’ systems and operations personnel and IBM systems engineers to plan, implement, and use a Parallel Sysplex in order to get closer to a goal of continuous availability. It is not intended to be a guide to implementing or using Parallel Sysplex as such. It only covers topics related to continuous availability.
• Titolo autorizzato: Achieving the highest levels of Parallel Sysplex availability
• Formato: Materiale a stampa
• Livello bibliografico: Monografia
• Lingua di pubblicazione: Inglese
• Record Nr.: 9910810926003321
• Lo trovi qui: Univ. Federico II
• Serie: IBM redbooks.