Improving z/OS Application Availability by Managing Planned Outages

Improving z/OS Application Availability by Managing Planned Outages

Released December 2014
Publisher(s): IBM Redbooks
ISBN: None

Read it now on the O’Reilly learning platform with a 10-day free trial.

O’Reilly members get unlimited access to books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial

Book description

This IBM® Redbooks® publication is intended to make System Programmers, Operators, and Availability Managers aware of the enhancements to recent releases of IBM z/OS® and its major subsystems in the area of planned outage avoidance. It is a follow-on to, rather than a replacement for, z/OS Planned Outage Avoidance Checklist, SG24-7328.

Its primary objective is to bring together in one place information that is already available, but widely dispersed. It also presents a different perspective on planned outage avoidance. Most businesses care about application availability rather than the availability of a specific system. Also, a planned outage is not necessarily a bad thing, if it does not affect application availability. In fact, running for too long without an IPL or subsystem restart might have a negative impact on application availability because it impacts your ability to apply preventive service. Therefore, this book places more focus on decoupling the ability to make changes and updates to your system from IPLing or restarting your systems.

Table of contents

  1. Front cover
  2. Notices
    1. Trademarks
  3. IBM Redbooks promotions
  4. Preface
    1. Authors
    2. Now you can become a published author, too!
    3. Comments welcome
    4. Stay connected to IBM Redbooks
  5. Chapter 1. Planned outage considerations
    1. 1.1 What is a planned outage?
    2. 1.2 System availability or application availability?
    3. 1.3 Planned outage avoidance or control?
    4. 1.4 Differences between planned and unplanned outages
    5. 1.5 Reasons for planned outages
    6. 1.6 What this book covers
    7. 1.7 Layout of this book
    8. 1.8 Live Guest Relocation
  6. Chapter 2. Project planning and user experiences
    1. 2.1 Project planning considerations
    2. 2.2 Setting the rules
    3. 2.3 Teams to involve
    4. 2.4 Researching and developing a strategy
    5. 2.5 Changes and how to control them
    6. 2.6 How frequently should I IPL or restart my subsystems?
    7. 2.7 Systems Management considerations
    8. 2.8 User experiences
      1. 2.8.1 Batch schedulers
      2. 2.8.2 Session manager products
      3. 2.8.3 Tasks using Getmain and Freemain
      4. 2.8.4 Log files and data sets
  7. Part 1 z/OS components
  8. Chapter 3. z/OS enhancements: Availability and diagnostics
    1. 3.1 List of z/OS enhancements
    2. 3.2 PARMLIB management for availability
      1. 3.2.1 Syntax checker: Language Environment
      2. 3.2.2 Syntax checker: z/OS UNIX
      3. 3.2.3 Syntax checker: TSO/E
      4. 3.2.4 Syntax checker: BCP PARMLIB Processor
      5. 3.2.5 Syntax checker: JES3
      6. 3.2.6 Syntax checker: Other products
    3. 3.3 Dynamic exit support for availability
      1. 3.3.1 Dynamic exit support for DADSM IGGPRE00 and IGGPOST0 exits
      2. 3.3.2 Dynamic exit support for CSVLLIX1 and CSVLLIX2 (LLA exits)
    4. 3.4 Scalability for availability
      1. 3.4.1 Extended Address Volume (EAV)
      2. 3.4.2 Base Control Program Internal Interface (BCPii)
    5. 3.5 Diagnostics for availability
      1. 3.5.1 IBM Health Checker for z/OS
      2. 3.5.2 Runtime Diagnostics component
      3. 3.5.3 Runtime Diagnostics with OMVS latch contention
      4. 3.5.4 Enhanced SLIP DUMP for non-dispatchable (MAXNDSP and DEFERTND)
      5. 3.5.5 Verify processor type and number with CONFIG
      6. 3.5.6 Diagnosing catalog contention issues
      7. 3.5.7 Enhanced D GRS,ANALYZE command
      8. 3.5.8 Restartable SMSPDSE1 address space
      9. 3.5.9 Improved IPL-time support for corrupted LNKLST PDSE data sets
      10. 3.5.10 Enhanced commands to identify corrupted PDSE control blocks
      11. 3.5.11 IEBPDSE utility to check for damaged PDSEs
      12. 3.5.12 Dynamically start and stop VSAM record management trace
      13. 3.5.13 Detecting a single point of failure programmatically (IOSSPOF)
      14. 3.5.14 Hardware Instrumentation Service (HIS) detects change in CPU speed
      15. 3.5.15 Predictive Failure Analysis (PFA)
  9. Chapter 4. z/OS enhancements: Base Control Program
    1. 4.1 List of Base Control Program enhancements
    2. 4.2 Change nearly any value in ALLOCxx without an IPL
      1. 4.2.1 The issue
      2. 4.2.2 How this is addressed in z/OS 1.11
      3. 4.2.3 Restrictions or considerations
      4. 4.2.4 Rollback
      5. 4.2.5 Further information
    3. 4.3 More effective use of space in ECSA
      1. 4.3.1 The issue
      2. 4.3.2 How this is addressed in z/OS 1.10
      3. 4.3.3 How this is addressed in z/OS 1.13
      4. 4.3.4 Restrictions or considerations
      5. 4.3.5 Rollback
      6. 4.3.6 Further information
    4. 4.4 PROG enhancement: Dynamic LNKLST
      1. 4.4.1 The issue
      2. 4.4.2 How this is addressed in z/OS 1.12
      3. 4.4.3 Restrictions or considerations
      4. 4.4.4 Rollback
      5. 4.4.5 Further information
    5. 4.5 PROG enhancement: Dynamic LPA
      1. 4.5.1 The issue
      2. 4.5.2 How this is addressed in z/OS 1.12
      3. 4.5.3 Restrictions or considerations
      4. 4.5.4 Rollback
      5. 4.5.5 Further information
    6. 4.6 PROG enhancement: Dynamic exit replacement
      1. 4.6.1 The issue
      2. 4.6.2 How this is addressed in z/OS 1.12
      3. 4.6.3 Restrictions or considerations
      4. 4.6.4 Rollback
      5. 4.6.5 Further information
    7. 4.7 SETPROG enhancement: SVC enhancement
      1. 4.7.1 The issue
      2. 4.7.2 How this is addressed in z/OS 1.12
      3. 4.7.3 Restrictions or considerations
      4. 4.7.4 Rollback
      5. 4.7.5 Further information
    8. 4.8 Enhancements to LLA processing
      1. 4.8.1 The issue
      2. 4.8.2 How this is addressed in z/OS 1.12
      3. 4.8.3 Restrictions or considerations
      4. 4.8.4 Rollback
      5. 4.8.5 Further information
    9. 4.9 System REXX availability enhancements
      1. 4.9.1 The issue
      2. 4.9.2 How this is addressed in z/OS 1.9 and later
      3. 4.9.3 Restrictions or considerations
      4. 4.9.4 Rollback
      5. 4.9.5 Further information
    10. 4.10 Dynamically change system symbols
      1. 4.10.1 The issue
      2. 4.10.2 How this is addressed in z/OS 2.1
      3. 4.10.3 IEASYMU2 and IEASYMUP usage
      4. 4.10.4 Restrictions or considerations
      5. 4.10.5 Rollback
      6. 4.10.6 Further information
    11. 4.11 Add more than RESERVED number of CPs without an IPL
      1. 4.11.1 The issue
      2. 4.11.2 How this is addressed in z/OS 1.10
      3. 4.11.3 How this is addressed in z/OS 2.1
      4. 4.11.4 Restrictions or considerations
      5. 4.11.5 Rollback
      6. 4.11.6 Further information
    12. 4.12 Switching between primary and secondary DASD without an IPL
      1. 4.12.1 The issue
      2. 4.12.2 How this is addressed in z/OS 1.10
      3. 4.12.3 Restrictions or considerations
      4. 4.12.4 Rollback
      5. 4.12.5 Further information
    13. 4.13 Specify NOBUFFS action (SMF) at the log stream level
      1. 4.13.1 The issue
      2. 4.13.2 How this is addressed in z/OS 1.12
      3. 4.13.3 Restrictions or considerations
      4. 4.13.4 Rollback
      5. 4.13.5 Further information
    14. 4.14 Forcing hung commands to avoid an IPL
      1. 4.14.1 The issue
      2. 4.14.2 How this is addressed in z/OS 1.13
      3. 4.14.3 Restrictions or considerations
      4. 4.14.4 Rollback
      5. 4.14.5 Further information
    15. 4.15 Dynamically configure storage-class memory (SCM)
      1. 4.15.1 The issue
      2. 4.15.2 How this is addressed in z/OS 1.13
      3. 4.15.3 Restrictions or considerations
      4. 4.15.4 Rollback
      5. 4.15.5 Further information
    16. 4.16 End a task with new operand on FORCE
      1. 4.16.1 The issue
      2. 4.16.2 How this is addressed in z/OS 2.1
      3. 4.16.3 Restrictions or considerations
      4. 4.16.4 Rollback
      5. 4.16.5 Further information
    17. 4.17 Auto-reply for WTOR
      1. 4.17.1 The issue
      2. 4.17.2 How this is addressed in z/OS 1.12
      3. 4.17.3 Restrictions or considerations
      4. 4.17.4 Rollback
      5. 4.17.5 Further information
    18. 4.18 DCCF support for WTOR Auto-Reply
      1. 4.18.1 The issue
      2. 4.18.2 How this is addressed in z/OS 2.1
      3. 4.18.3 Restrictions or considerations
      4. 4.18.4 Rollback
      5. 4.18.5 Further information
    19. 4.19 New MODIFY VLF command
      1. 4.19.1 The issue
      2. 4.19.2 How this is addressed in z/OS 2.1
      3. 4.19.3 Restrictions or considerations
      4. 4.19.4 Rollback
      5. 4.19.5 Further information
    20. 4.20 Add/Remove MCS consoles dynamically
      1. 4.20.1 The issue
      2. 4.20.2 How this is addressed in z/OS 2.1
      3. 4.20.3 How this is addressed in z/OS 1.10
      4. 4.20.4 Restrictions or considerations
      5. 4.20.5 Rollback
      6. 4.20.6 Further information
    21. 4.21 New Message Flood Automation
      1. 4.21.1 The issue
      2. 4.21.2 How this is addressed in z/OS 1.9
      3. 4.21.3 How this is addressed in z/OS 1.11
      4. 4.21.4 How this is addressed in z/OS 1.13
      5. 4.21.5 Restrictions or considerations
      6. 4.21.6 Rollback
      7. 4.21.7 Further information
    22. 4.22 Added LPA defer wait capability
      1. 4.22.1 The issue
      2. 4.22.2 How this is addressed in z/OS 1.12
      3. 4.22.3 Restrictions or considerations
      4. 4.22.4 Rollback
      5. 4.22.5 Further information
    23. 4.23 Auto-IPL using DIAGxx
      1. 4.23.1 The issue
      2. 4.23.2 How this is addressed in z/OS 1.10
      3. 4.23.3 Restrictions or considerations
      4. 4.23.4 Rollback
      5. 4.23.5 Further information
    24. 4.24 z/OS reusable address space support and usage
      1. 4.24.1 The issue
      2. 4.24.2 How this is addressed since z/OS 1.9
      3. 4.24.3 Restrictions or considerations
      4. 4.24.4 Rollback
      5. 4.24.5 Further information
    25. 4.25 z/OS report on linkage indexes
      1. 4.25.1 The issue
      2. 4.25.2 How this is addressed in z/OS 1.9
      3. 4.25.3 Restrictions or considerations
      4. 4.25.4 Rollback
      5. 4.25.5 Further information
  10. Chapter 5. z/OS enhancements: GRS
    1. 5.1 Moving GRS contention notification system role
      1. 5.1.1 The issue
      2. 5.1.2 How this is addressed in z/OS 1.8
      3. 5.1.3 Restrictions or considerations
      4. 5.1.4 Rollback
      5. 5.1.5 Further information
    2. 5.2 Control the maximum number of ENQs in a system
      1. 5.2.1 The issue
      2. 5.2.2 How this is addressed in z/OS 1.8
      3. 5.2.3 Restrictions or considerations
      4. 5.2.4 Rollback
      5. 5.2.5 Further information
    3. 5.3 Changing to GRS without sysplex IPL
      1. 5.3.1 The issue
      2. 5.3.2 How this is addressed in z/OS 1.10
      3. 5.3.3 Restrictions or considerations
      4. 5.3.4 Rollback
      5. 5.3.5 Further information
  11. Chapter 6. z/OS enhancements: Resource Recovery Services
    1. 6.1 RRS internal restart
      1. 6.1.1 The issue
      2. 6.1.2 How this is addressed in z/OS 2.1
      3. 6.1.3 Restrictions or considerations
      4. 6.1.4 Rollback
      5. 6.1.5 Further information
    2. 6.2 Clean RRS shutdown option
      1. 6.2.1 The issue
      2. 6.2.2 How this is addressed in z/OS 1.13
      3. 6.2.3 Restrictions or considerations
      4. 6.2.4 Rollback
      5. 6.2.5 Further information
    3. 6.3 Ability to dynamically turn on and off RRS archive log
      1. 6.3.1 The issue
      2. 6.3.2 How this is addressed in z/OS 1.10
      3. 6.3.3 Restrictions or considerations
      4. 6.3.4 Rollback
      5. 6.3.5 Further information
  12. Chapter 7. z/OS enhancements: XCF and System Logger
    1. 7.1 System Status Detection Partitioning Protocol
      1. 7.1.1 The issue
      2. 7.1.2 How this is addressed in z/OS 1.11
      3. 7.1.3 Restrictions or considerations
      4. 7.1.4 Rollback
      5. 7.1.5 Further information
    2. 7.2 CRITICALPAGING function for HyperSwap environments
      1. 7.2.1 The issue
      2. 7.2.2 How this is addressed in z/OS 1.12
      3. 7.2.3 Restrictions or considerations
      4. 7.2.4 Rollback
      5. 7.2.5 Further information
    3. 7.3 Non-disruptive CF dump
      1. 7.3.1 The issue
      2. 7.3.2 How this is addressed in z/OS 1.13
      3. 7.3.3 Restrictions or considerations
      4. 7.3.4 Rollback
      5. 7.3.5 Further information
    4. 7.4 XCF command to get structures to primary CF
      1. 7.4.1 The issue
      2. 7.4.2 How this is addressed in z/OS 1.8
      3. 7.4.3 Restrictions or considerations
      4. 7.4.4 Rollback
      5. 7.4.5 Further information
    5. 7.5 Force disconnection or deletion of a log stream without restarting the Logger address space
      1. 7.5.1 The issue
      2. 7.5.2 How this is addressed in z/OS 1.11
      3. 7.5.3 Restrictions or considerations
      4. 7.5.4 Further information
    6. 7.6 IXGCNFxx PARM
      1. 7.6.1 The issue
      2. 7.6.2 How this is addressed in z/OS 1.13
      3. 7.6.3 Restrictions or considerations
      4. 7.6.4 Rollback
      5. 7.6.5 Further information
    7. 7.7 System Logger threshold messages
      1. 7.7.1 The issue
      2. 7.7.2 How this is addressed in z/OS 2.1
      3. 7.7.3 Restrictions or considerations
      4. 7.7.4 Rollback
      5. 7.7.5 Further information
    8. 7.8 Multiple logstream/data set management
      1. 7.8.1 The issue
      2. 7.8.2 How this is addressed in z/OS 1.11
      3. 7.8.3 Restrictions or considerations
      4. 7.8.4 Rollback
      5. 7.8.5 Further information
    9. 7.9 Dynamic log stream updates for duplexing
      1. 7.9.1 The issue
      2. 7.9.2 How this is addressed in z/OS 1.10
      3. 7.9.3 Restrictions or considerations
      4. 7.9.4 Rollback
      5. 7.9.5 Further information
  13. Chapter 8. z/OS enhancements: Communications Server
    1. 8.1 Specify a hot standby server to Sysplex Distributor
      1. 8.1.1 The issue
      2. 8.1.2 How this is addressed in z/OS 1.12
      3. 8.1.3 Restrictions or considerations
      4. 8.1.4 Rollback
      5. 8.1.5 Further information
    2. 8.2 Resolver start error tolerance
      1. 8.2.1 The issue
      2. 8.2.2 How this is addressed in z/OS 2.1
      3. 8.2.3 Restrictions or considerations
      4. 8.2.4 Rollback
      5. 8.2.5 Further information
    3. 8.3 Command to verify TCP profile syntax
      1. 8.3.1 The issue
      2. 8.3.2 How this is addressed in z/OS 2.1
      3. 8.3.3 Restrictions or considerations
      4. 8.3.4 Rollback
      5. 8.3.5 Further information
    4. 8.4 RPCBIND/NFS re-registration
      1. 8.4.1 The issue
      2. 8.4.2 How this is addressed in z/OS 2.1
      3. 8.4.3 Restrictions or considerations
      4. 8.4.4 Rollback
      5. 8.4.5 Further information
  14. Chapter 9. z/OS enhancements: DFSMS
    1. 9.1 Dynamically activate changes to DEVSUPxx member
      1. 9.1.1 The issue
      2. 9.1.2 How this is addressed in z/OS 1.8
      3. 9.1.3 How this is addressed in z/OS 1.10
      4. 9.1.4 Restrictions or considerations
      5. 9.1.5 Rollback
      6. 9.1.6 Further information
    2. 9.2 Dynamically modify size of SMSPDSE hiperspaces
      1. 9.2.1 The issue
      2. 9.2.2 How this is addressed in z/OS 1.8
      3. 9.2.3 Restrictions or considerations
      4. 9.2.4 Rollback
      5. 9.2.5 Further information
    3. 9.3 VSAM CA reclaim for KSDSs
      1. 9.3.1 The issue
      2. 9.3.2 How this is addressed in z/OS 1.12
      3. 9.3.3 Restrictions or considerations
      4. 9.3.4 Rollback
      5. 9.3.5 Further information
    4. 9.4 Support for very large catalogs and catalogs on extended address volumes (EAVs)
      1. 9.4.1 The issue
      2. 9.4.2 How this is addressed in z/OS 1.12
      3. 9.4.3 Restrictions or considerations
      4. 9.4.4 Rollback
      5. 9.4.5 Further information
    5. 9.5 Minimizing application disruption during catalog maintenance
      1. 9.5.1 The issue
      2. 9.5.2 How this is addressed in z/OS 2.1
      3. 9.5.3 Restrictions or considerations
      4. 9.5.4 Rollback
      5. 9.5.5 Further information
    6. 9.6 DADSM and CVAF support for dynamic corrective service activation
      1. 9.6.1 The issue
      2. 9.6.2 How this is addressed in z/OS 1.13
      3. 9.6.3 Restrictions or considerations
      4. 9.6.4 Rollback
      5. 9.6.5 Further information
    7. 9.7 DFSMShsm Control Data Set backup enhancements
      1. 9.7.1 The issue
      2. 9.7.2 How this is addressed in z/OS 1.13
      3. 9.7.3 Restrictions or considerations
      4. 9.7.4 Rollback
      5. 9.7.5 Further information
    8. 9.8 Allow XRC primary volumes to be offline when the XSTART and XADDPAIR commands are issued
      1. 9.8.1 The issue
      2. 9.8.2 How this is addressed in z/OS 2.1
      3. 9.8.3 Restrictions or considerations
      4. 9.8.4 Rollback
      5. 9.8.5 Further information
    9. 9.9 Metro Mirror (PPRC) support for Remote Pair FlashCopy
      1. 9.9.1 The issue
      2. 9.9.2 How this is addressed in z/OS 1.11
      3. 9.9.3 Restrictions or considerations
      4. 9.9.4 Rollback
      5. 9.9.5 Further information
    10. 9.10 Remove need to offline/online volume after VTOC change
      1. 9.10.1 The issue
      2. 9.10.2 How this is addressed in z/OS 1.13
      3. 9.10.3 Restrictions or considerations
      4. 9.10.4 Rollback
      5. 9.10.5 Further information
    11. 9.11 Dynamically update maximum number of tape drives OAM allocates
      1. 9.11.1 The issue
      2. 9.11.2 How this is addressed in z/OS 1.13
      3. 9.11.3 Restrictions or considerations
      4. 9.11.4 Rollback
      5. 9.11.5 Further information
  15. Chapter 10. z/OS enhancements: Distributed File Service (zFS)
    1. 10.1 zFS internal restart
      1. 10.1.1 The issue
      2. 10.1.2 How this is addressed in z/OS 1.13
      3. 10.1.3 Restrictions or considerations
      4. 10.1.4 Rollback
      5. 10.1.5 Further information
    2. 10.2 zFS automatic re-enable of disabled file systems
      1. 10.2.1 The issue
      2. 10.2.2 How this is addressed in z/OS 1.13
      3. 10.2.3 Restrictions or considerations
      4. 10.2.4 Rollback
      5. 10.2.5 Further information
  16. Chapter 11. z/OS enhancements: Security Server (RACF)
    1. 11.1 Sample passphrase ICHPWX11 exit uses System REXX
      1. 11.1.1 The issue
      2. 11.1.2 How this is addressed in z/OS 1.9
      3. 11.1.3 Restrictions or considerations
      4. 11.1.4 Rollback
      5. 11.1.5 Further information
    2. 11.2 Sample password ICHPWX01 exit uses System REXX
  17. Chapter 12. z/OS enhancements: ICSF
    1. 12.1 ICSF: Improve product stability
      1. 12.1.1 The issue
      2. 12.1.2 How this is addressed in z/OS 1.12
      3. 12.1.3 Restrictions or considerations
      4. 12.1.4 Rollback
      5. 12.1.5 Further information
  18. Chapter 13. z/OS enhancements: JES2
    1. 13.1 Dynamic JES2 exit support
      1. 13.1.1 The issue
      2. 13.1.2 How this is addressed in z/OS 1.9
      3. 13.1.3 Restrictions or considerations
      4. 13.1.4 Rollback
      5. 13.1.5 Further information
    2. 13.2 Dynamic changes to JES2 parameters
      1. 13.2.1 The issue
      2. 13.2.2 How this is addressed in z/OS 1.13
      3. 13.2.3 Restrictions or considerations
      4. 13.2.4 Rollback
      5. 13.2.5 Further information
    3. 13.3 Early release of job log from long running jobs and started tasks
      1. 13.3.1 The issue
      2. 13.3.2 How this is addressed in z/OS 1.13
      3. 13.3.3 Restrictions or considerations
      4. 13.3.4 Rollback
      5. 13.3.5 Further information
    4. 13.4 Use SPIN=UNALLOC JCL keyword to spin off spool files
      1. 13.4.1 How this is addressed in z/OS 1.13
      2. 13.4.2 How this is addressed in z/OS 1.13
      3. 13.4.3 Restrictions or considerations
      4. 13.4.4 Rollback
      5. 13.4.5 Further information
    5. 13.5 Ability to stop a JES2 job at the end of the current step
      1. 13.5.1 The issue
      2. 13.5.2 How this is addressed in z/OS 1.13
      3. 13.5.3 Restrictions or considerations
      4. 13.5.4 Rollback
      5. 13.5.5 Further information
    6. 13.6 Dynamically modify a JES2 spool volume
      1. 13.6.1 The issue
      2. 13.6.2 How this is addressed in z/OS 1.13
      3. 13.6.3 Restrictions or considerations
      4. 13.6.4 Rollback
      5. 13.6.5 Further information
    7. 13.7 Support for over four billion spin data sets
      1. 13.7.1 The issue
      2. 13.7.2 How this is addressed in z/OS 2.1
      3. 13.7.3 Restrictions or considerations
      4. 13.7.4 Rollback
      5. 13.7.5 Further information
  19. Chapter 14. z/OS enhancements: JES3
    1. 14.1 Dynamically modify TCP/IP NJE information
      1. 14.1.1 The issue
      2. 14.1.2 How this is addressed in z/OS 1.8
      3. 14.1.3 Restrictions or considerations
      4. 14.1.4 Rollback
      5. 14.1.5 Further information
    2. 14.2 Ability to dynamically add spool volumes to JES3
      1. 14.2.1 The issue
      2. 14.2.2 How this is addressed in z/OS 1.13
      3. 14.2.3 Restrictions or considerations
      4. 14.2.4 Rollback
      5. 14.2.5 Further information
    3. 14.3 Ability to dynamically remove spool volumes from JES3
      1. 14.3.1 The issue
      2. 14.3.2 How this is addressed in z/OS 2.1
      3. 14.3.3 Restrictions or considerations
      4. 14.3.4 Rollback
      5. 14.3.5 Further information
  20. Chapter 15. z/OS enhancements: Infoprint Server
    1. 15.1 Dynamic configuration changes for most InfoPrint options
      1. 15.1.1 The issue
      2. 15.1.2 How this is addressed in z/OS 2.1
      3. 15.1.3 Restrictions or considerations
      4. 15.1.4 Rollback
      5. 15.1.5 Further information
    2. 15.2 Print Services Facility (PSF) installation is disassociated from SYS1.NUCLEUS
      1. 15.2.1 The issue
      2. 15.2.2 How this is addressed in z/OS V2.1
      3. 15.2.3 Restrictions or considerations
      4. 15.2.4 Rollback
      5. 15.2.5 Further information
  21. Chapter 16. z/OS enhancements: TSO/E
    1. 16.1 Support for VTAM unconditional reconnect for TSO/E users
      1. 16.1.1 The issue
      2. 16.1.2 How this is addressed in z/OS 1.11
      3. 16.1.3 Restrictions or considerations
      4. 16.1.4 Rollback
      5. 16.1.5 Further information
  22. Chapter 17. z/OS enhancements: z/OS UNIX
    1. 17.1 Support dynamic modification of AUTOCVT setting
      1. 17.1.1 The issue
      2. 17.1.2 How this is addressed in z/OS V1.13
      3. 17.1.3 Restrictions or considerations
      4. 17.1.4 Further information
    2. 17.2 Prevent content overlay during mount
      1. 17.2.1 The issue
      2. 17.2.2 How this is addressed in z/OS 1.13
      3. 17.2.3 Restrictions or considerations
      4. 17.2.4 Rollback
      5. 17.2.5 Further information
    3. 17.3 Change sysplex root data set without sysplex IPL
      1. 17.3.1 The issue
      2. 17.3.2 How this is addressed in z/OS 1.10
      3. 17.3.3 Restrictions or considerations
      4. 17.3.4 Rollback
      5. 17.3.5 Further information
    4. 17.4 Support for alternate sysplex root data set
      1. 17.4.1 The issue
      2. 17.4.2 How this is addressed in z/OS 1.10
      3. 17.4.3 Restrictions or considerations
      4. 17.4.4 Rollback
      5. 17.4.5 Further information
    5. 17.5 Change number of common inet ports without OMVS restart
      1. 17.5.1 The issue
      2. 17.5.2 How this is addressed in z/OS 1.12
      3. 17.5.3 Restrictions or considerations
      4. 17.5.4 Rollback
      5. 17.5.5 Further information
    6. 17.6 Remount with same mount mode
      1. 17.6.1 The issue
      2. 17.6.2 How this is addressed in z/OS 1.11
      3. 17.6.3 Restrictions or considerations
      4. 17.6.4 Rollback
      5. 17.6.5 Further information
  23. Part 2 z/OS middleware
  24. Chapter 18. CICS considerations
    1. 18.1 Possible reasons to schedule stopping a CICS region
    2. 18.2 Techniques to reduce unavailability through configuration changes
      1. 18.2.1 Reloading programs
      2. 18.2.2 Partitioned Data Set Load Library versus Extended
      3. 18.2.3 Dynamic program library management
      4. 18.2.4 Dynamic allocation of files and Extrapartition Transient Data Queues
      5. 18.2.5 Changes to CICS System Initialization Table values.
      6. 18.2.6 Reload an updated RACF Certificate key ring
      7. 18.2.7 Change of Local Time on z/OS system
      8. 18.2.8 RACF changes
      9. 18.2.9 Tracking dynamic changes to a CICS region
      10. 18.2.10 Applying Service
      11. 18.2.11 Upgrading CICS
    3. 18.3 Reduction of preventive recycles of CICS
      1. 18.3.1 Storage shortage
    4. 18.4 Reducing shutdowns through runtime dependencies
    5. 18.5 Reducing shutdowns to allow resource access by non-CICS tasks
      1. 18.5.1 Backups
      2. 18.5.2 Batch access to data sets
    6. 18.6 CICS still must be stopped, so what next?
  25. Chapter 19. DB2 considerations
    1. 19.1 DB2 subsystem or data sharing group member outage
      1. 19.1.1 Applying DB2 service (PTF/RSU/CST)
      2. 19.1.2 Version to version upgrade/fallback
      3. 19.1.3 DSNZPARM changes
      4. 19.1.4 Convert BSDS to Extended RBA/LRSN in DB2 11
      5. 19.1.5 Dynamic addition of active logs
    2. 19.2 Database changes
      1. 19.2.1 DB2 for z/OS Version 8
      2. 19.2.2 DB2 for z/OS 9
      3. 19.2.3 DB2 for z/OS 10
      4. 19.2.4 DB2 for z/OS 11
  26. Chapter 20. IMS considerations
    1. 20.1 IMS database considerations
      1. 20.1.1 Database reorganization
      2. 20.1.2 Dynamic database buffering
      3. 20.1.3 Miscellaneous database considerations
    2. 20.2 IMS Transaction Manager Considerations
      1. 20.2.1 Dynamic change for OTMA routing descriptors
      2. 20.2.2 Dynamically change the IMS Connect configuration
      3. 20.2.3 MSC dynamic reconfiguration
    3. 20.3 IMS system considerations
      1. 20.3.1 Member Online Change (MOLC)
      2. 20.3.2 ACBLIB dynamic allocation
      3. 20.3.3 ACBIN64
      4. 20.3.4 Language Environment dynamic runtime options
      5. 20.3.5 Refreshable user exits
      6. 20.3.6 Dynamic LOCKTIME
      7. 20.3.7 Dynamic resource definition (DRD)
      8. 20.3.8 DBRC
      9. 20.3.9 IMS Version upgrades without an IPL
    4. 20.4 Resources still requiring a recycle of IMS to change
      1. 20.4.1 Variable storage pools
      2. 20.4.2 Fixed size (SPM) storage pools
      3. 20.4.3 Log buffers
  27. Chapter 21. WebSphere MQ for z/OS
    1. 21.1 Basic concepts and terms
      1. 21.1.1 Messages / message queues
      2. 21.1.2 Queues
      3. 21.1.3 Unit of work
    2. 21.2 Availability and planned outages
      1. 21.2.1 Minimizing a queue manager outage due to an image IPL
      2. 21.2.2 Availability of messaging in a QSG during an image IPL
      3. 21.2.3 Can a WebSphere MQ channel be automatically rerouted if a queue manager is made unavailable?
      4. 21.2.4 Can a queue remain available if a queue manager is stopped and you are not using shared queues?
      5. 21.2.5 How can a message be processed by a different queue manager or queue without changing an application?
      6. 21.2.6 Improving availability to client applications during a planned outages
      7. 21.2.7 Further information
    3. 21.3 Applying maintenance during subsystem operation
      1. 21.3.1 Concurrent code levels
      2. 21.3.2 Do you need to bind DB2 application plans following maintenance?
      3. 21.3.3 Catering to a DB2 outage in a QSG
      4. 21.3.4 Performing maintenance on a queue manager in a cluster
      5. 21.3.5 How can a queue manager be made to slow the rate of messages in the event of an IMS message flood?
    4. 21.4 Changes that can be made dynamically
      1. 21.4.1 Can the buffer pools be changed while the queue manager is up?
    5. 21.5 Changes requiring a queue manager restart or IPL
      1. 21.5.1 Does an early code upgrade need a queue manager restart or IPL?
    6. 21.6 Error recovery (without a system or subsystem restart)
      1. 21.6.1 What happens to coordinated unit of recovery in a QSG?
      2. 21.6.2 WebSphere MQ peer recovery in a QSG
      3. 21.6.3 Toleration for CF connectivity loss and recovery enhancements
  28. Appendix A. Items requiring an IPL or recycle
    1. Items requiring an IPL or recycle to implement
  29. Appendix B. DB2 UNIX file system maintenance considerations
    1. Type 2 and type 4 connectivity
    2. Example of DB2 maintenance and the zFS
  30. Related publications
    1. IBM Redbooks
    2. Other publications
    3. Online resources
    4. Help from IBM
  31. Back cover
  32. IBM System x Reference Architecture for Hadoop: IBM InfoSphere BigInsights Reference Architecture
    1. Introduction
    2. Business problem and business value
    3. Reference architecture use
    4. Requirements
    5. InfoSphere BigInsights predefined configuration
    6. InfoSphere BigInsights HBase predefined configuration
    7. Deployment considerations
    8. Customizing the predefined configurations
    9. Predefined configuration bill of materials
    10. References
    11. The team who wrote this paper
    12. Now you can become a published author, too!
    13. Stay connected to IBM Redbooks
  33. Notices
    1. Trademarks

Product information

  • Title: Improving z/OS Application Availability by Managing Planned Outages
  • Author(s):
  • Release date: December 2014
  • Publisher(s): IBM Redbooks
  • ISBN: None