There are four types of queue object available in WebSphere MQ.
Before applications can send messages to a queue on another queue manager, you must have defined a transmission queue and channels between the queue managers, unless you have grouped one or more queue managers together into a cluster. For more information about clusters, see Remote administration using clusters.
An alias queue is not a queue, but an object that you can use to access another queue.
Dynamic queues defined in this way can be temporary queues, which do not survive product restarts, or permanent queues, which do.
Queues are defined to WebSphere MQ using:
The commands specify the type of queue and its attributes. For example, a local queue object has attributes that specify what happens when applications reference that queue in MQI calls. Examples of attributes are:
For further details about defining queue objects, see the WebSphere MQ Script (MQSC) Command Reference or WebSphere MQ Programmable Command Formats and Administration Interface.
WebSphere MQ uses some local queues for specific purposes related to its operation. You must define these queues before WebSphere MQ can use them.
If a queue manager is to use triggering, at least one initiation queue must be defined for that queue manager. See Managing objects for triggering and runmqtrm (start trigger monitor). For more information about triggering, see the WebSphere MQ Application Programming Guide.
Each queue manager can have a default transmission queue. When a queue manager that is not part of a cluster puts a message onto a remote queue, the default action, if there is no transmission queue with the same name as the destination queue manager, is to use the default transmission queue.
A queue manager that is part of the cluster can send messages on the cluster transmission queue to any other queue manager that is in the same cluster.
During name resolution, the cluster transmission queue takes precedence over the default transmission queue.
When a queue manager is part of a cluster, the default action is to use the SYSTEM.CLUSTER.TRANSMIT.QUEUE, except when the destination queue manager is not part of the cluster.
For distributed queuing, define a dead-letter queue on each queue manager involved.
A command queue is created automatically for each queue manager when that queue manager is created.
When an instrumentation event occurs, the queue manager puts an event message on an event queue. This message can then be read by a monitoring application, which might inform an administrator or initiate some remedial action if the event indicates a problem.
For more information about instrumentation events, see Monitoring WebSphere MQ.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
quem |