Home

 

Are some of your queues failing?

 

If you suspect that the problem occurs with only a subset of queues, check the local queues that you think are having problems:

1. Display the information about each queue. We can use the MQSC command DISPLAY QUEUE to display the information.

2. 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 great? That is, does it generate a trigger event often enough?

       • Is the process name correct?

       • Is the process available and operational?

     • 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. It could be because the applications need to be started, a connection has been disrupted, or the MQOPEN call has failed for some reason.

     Check the queue attributes IPPROCS and OPPROCS. These attributes indicate whether the queue has been opened for input and output. If a value is zero, it indicates that no operations of that type can occur. The values might have changed; the queue might have been open but is now closed.

     You need to check the status at the time you expect to put or get a message.

If you are unable to solve the problem, contact your IBM Support Center for help.

 

Parent topic:

Looking at problems in more detail

fa15040_

 

Home