No error messages issued

If no error messages have been issued, perform the following procedure to determine what is causing the problem:

1. Issue the z/OS commands

   DISPLAY A,xxxxMSTR
   DISPLAY A,xxxxCHIN

   (where

   xxxx is the WebSphere MQ for z/OS subsystem name). If you receive a message telling you that the queue manager or channel initiator has not been found, this indicates that the subsystem has terminated. This could be caused by an abend or by operator shutdown of the system.

2. If the subsystem is running, you will receive message IEE105I. This message includes the CT=nnnn field, which contains information about the processor time being used by the subsystem. Note the value of this field, and reissue the command.

   • If the CT= value has not changed, this indicates that the subsystem is not using any processor time. This could indicate that the subsystem is in a wait state (or that it has no work to do). If we can issue a command like DISPLAY DQM and you get output back, this indicates there is no work to do rather than a hang condition.

   • If the CT= value has changed dramatically, and continues to do so over repeated displays, this could indicate that the subsystem is very busy or possibly in a loop.

   • If the reply indicates that the subsystem is now not found, this indicates that it was in the process of terminating when the first command was issued. If a dump is being taken, the subsystem might take a while to terminate. A message is produced at the console before terminating.

     To check that the channel initiator is working, issue the DISPLAY DQM command. If the response does not show the channel initiator working this could be because it is getting insufficient resources (like the CPU). In this case, use the MVS monitoring tools, such as RMF, to determine if there is a resource problem. If it is not, restart the channel initiator.