Are some of your queues working?
If you suspect that the problem occurs with only a subset of queues, select
the name of a local queue that you think is having problems.
- Display the information about this queue, using WRKMQMQSTS or DSPMQMQ.
- Use the data displayed to do the following checks:
- If CURDEPTH is at MAXDEPTH, the queue is not being processed. Check that
all applications are running normally.
- If CURDEPTH is not at MAXDEPTH, check the following queue attributes to
ensure that they are correct:
- If triggering is being used:
- Is the trigger monitor running?
- Is the trigger depth too big?
- Is the process name correct?
- Can the queue be shared? If not, another application could already have
it open for input.
- Is the queue enabled appropriately for GET and PUT?
- If there are no application processes getting messages from the queue,
determine why this is so (for example, because the applications need to be
started, a connection has been disrupted, or because the MQOPEN call has failed
for some reason).
If you cannot solve the problem, contact your IBM(R) support center for help.