Is WebSphere MQ for z/OS waiting?
If your investigations indicate that WebSphere MQ itself is waiting, check
the following:
- Use the DISPLAY THREAD(*) command to check if anything is connected
to WebSphere MQ.
- Use SDSF DA, or the z/OS command DISPLAY A,xxxxMSTR to determine
whether there is any CPU usage (as shown in Has your application or WebSphere MQ for z/OS stopped processing work?).
- If WebSphere MQ is using some CPU, reconsider other reasons why WebSphere MQ might be
waiting, or consider whether this is actually a performance problem.
- If there is no CPU activity, check whether WebSphere MQ responds to commands.
If you can get a response, reconsider other reasons why WebSphere MQ might be waiting.
- If you cannot get a response, check the console log for messages that
might explain the wait (for example, WebSphere MQ might have run out of active log
data sets, and be waiting for an off-load).
If you are satisfied that WebSphere MQ has
actually stalled, use the STOP QMGR command in both QUIESCE and FORCE mode
to terminate any programs currently being executed.
If the STOP QMGR command fails to respond, cancel the queue manager with
a dump, and restart. If the problem recurs, refer to Working with IBM(R) to solve your problem for
further guidance.