WebSphere for z/OS is a complex product made up of many components, similar to the human body. And, like the human body, WebSphere for z/OS can experience problems that need to be diagnosed and corrected.
If a WebSphere for z/OS problem occurs, this IBM Redpaper can help you to determine what happened and why it happened.
We first introduce you to the general problem determination methodology, then show you how to diagnose various problem symptoms encountered in a WebSphere for z/OS environment.
We use flow charts that guide you through the analysis process in a step-by-step approach. Based on tasks you need to do and answers that you give to a series of questions designed to filter out irrelevant facts we attempt to take you to the problem area. If solutions exist to your errors or exceptions, we suggest them. We also mention analysis tools and reference information sources related to the symptoms. When no feasible solution is apparent, you are directed to prepare documentation and contact IBM.
This Redpaper is intended for system programmers and administrators working with WebSphere Application Server for z/OS V6. It is targeted toward those who need to identify problems, analyze them, and fix them efficiently so that they can deliver good support for the WebSphere environment. Another objective is to assist IBM support and technical professionals as well as Java developers who work in this environment.
Table of contents
Chapter 1. Problem determination methodology
Chapter 2. Exceptions and error messages
Chapter 3. Abend
Chapter 4. Hang
Chapter 5. Timeout
Chapter 6. Does not stop
Chapter 7. Job failed
Chapter 8. No resource access
Chapter 9. High CPU utilization
Appendix A. Messages and codes
Appendix B. Contacting IBM: information
Appendix C. Information sources