WebSphere MQ queue managers

A queue manager provides queuing services to applications, and manages the queues that belong to it. It ensures that:

• Object attributes are changed according to the commands received.

• Special events such as trigger events or instrumentation events are generated when the appropriate conditions are met.

• Messages are put on the correct queue, as requested by the application making the MQPUT call. The application is informed if this cannot be done, and an appropriate reason code is given.

Each queue belongs to a single queue manager and is said to be a local queue to that queue manager.

The queue manager to which an application is connected is said to be the local queue manager for that application. For the application, the queues that belong to its local queue manager are local queues.

A remote queue is a queue that belongs to another queue manager.

A remote queue manager is any queue manager other than the local queue manager. A remote queue manager exists on a remote machine across the network, or on the same machine as the local queue manager.

WebSphere MQ for iSeries supports multiple queue managers on the same machine.

A queue manager object can be used in some MQI calls. For example, you can inquire about the attributes of the queue manager object using the MQI call MQINQ.

Note:

We cannot put messages on a queue manager object; messages are always put on queue objects, not on queue manager objects.