Is a batch or TSO program waiting?

Consider the following points:

Your program might be waiting on another resource

For example, a VSAM control interval (CI) that another program is holding for update.

Your program might be waiting for a message that has not yet arrived

This might be normal behavior if, for example, it is a server program that constantly monitors a queue.

Alternatively, your program might be waiting for a message that has arrived, but has not yet been committed.

Issue the DIS CONN(*) TYPE(HANDLE) command and examine the queues in use by your program.

If you suspect that your program has issued an MQI call that did not involve an MQGET WAIT, and control has not returned from WebSphere MQ, take an SVC dump of both the batch or TSO job, and the WebSphere MQ subsystem before cancelling the batch or TSO program.

Also consider that the wait state might be the result of a problem with another program, such as an abnormal termination (see Messages do not appear when expected), or in WebSphere MQ itself (see Is WebSphere MQ for z/OS waiting?). Refer to WebSphere MQ dumps (specifically Figure 2) for information about obtaining a dump.

If the problem persists, refer to Finding solutions to similar problems and Working with IBM to solve your problem for information on reporting the problem to IBM.