This IBM® Redbooks® publication is intended to make System Programmers, Operators, and Availability Managers aware of the enhancements to recent releases of 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 given system. Also, a planned outage is not necessarily a bad thing, as long as it does not impact application availability. In fact, running for too long without an IPL or subsystem restart may have a negative impact on application availability because it impacts your ability to apply preventive service. Therefore, we place more focus on decoupling the ability to make changes and updates to your system from IPLing or restarting your systems.
NOTE: This is an early edition of the book containing some empty chapters. These chapters will be filled in as they become ready.
Table of contents
Chapter 1. Planned outage considerations
Chapter 2. z/OS aspects of enhancements
Chapter 3. CICS considerations
Chapter 4. DB2 considerations
Chapter 5. IMS considerations
Chapter 6. WebSphere MQ for z/OS
Chapter 7. WebSphere Application Server z/OS considerations
Chapter 8. Project planning and user experiences
Appendix A. Items requiring an IPL or recycle
Appendix B. DB2 UNIX file system maintenance considerations
These pages are Web versions of IBM Redbooks- and Redpapers-in-progress. They are published here for those who need the information now and may contain spelling, layout and grammatical errors.
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. Your feedback is welcomed to improve the usefulness of the material to others.
IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a customer responsibility and depends upon the customer's ability to evaluate and integrate them into the customer's operational environment.