Dealing with applications that are running slowly or have stopped on z/OS
Waits and loops can exhibit similar symptoms. Use the links in this topic to help differentiate between waits and loops on z/OS .
Waits and loops are characterized by unresponsiveness. However, it can be difficult to distinguish between waits, loops, and poor performance.
Any of the following symptoms might be caused by a wait or a loop, or by a badly tuned or overloaded system:
- An application that appears to have stopped running (if IBM MQ for z/OS is still responsive, this problem is probably caused by an application problem)
- An MQSC command that does not produce a response
- Excessive use of processor time
To perform the tests shown in these topics, we need access to the z/OS console, and to be able to issue operator commands.
- Distinguishing between waits and loops on z/OS
- Dealing with waits on z/OS
- Dealing with loops on z/OS
- Distinguishing between waits and loops on z/OS
Waits and loops on IBM MQ for z/OS can present similar symptoms. Use this topic to help determine if we are experiencing a wait or a loop.- Dealing with waits on z/OS
Waits can occur in batch or TSO applications, CICS transactions, and other components on IBM MQ for z/OS. Use this topic to determine where waits can occur.- Dealing with loops on z/OS
Loops can occur in different areas of a z/OS system. Use this topic to help determine where a loop is occurring.Parent topic: Dealing with performance problems on z/OS
Related tasks