What a queue manager is
In MainView AutoOPERATOR for MQ, queues on individual systems are managed by a component called a queue manager.
The queue manager provides messaging and queuing services to applications. The queue manager’s job is to make sure messages are either put on the correct queue or delivered to another queue manager to accomplish the job. Applications do this process through Message Queue Interface (MQI) statements to the queue manager.
On certain platforms (such as IBM z/OS) you can have more than one queue manager per system. On other platforms, you might be restricted to only one queue manager per system. To learn more about platform restrictions, refer to the correspondent platform-specific IBM MQ manual.
The following table describes different types of queues and queue managers.
Queue manager type | Description |
|---|---|
Local Queue Manager | A local queue manager is a queue manager that is on the same system as the connecting application. For example, in IBM MQ for z/OS, the queue manager can be identified by the subsystem ID in the IEFSSN member of SYS1.PARMLIB. On z/OS platforms, there may be more than one local queue manager on a z/OS image. |
Remote Queue Manager | A remote queue manager is a queue manager other than the queue manager to which the application is currently connected. |
Dead Letter Queue | A dead letter queue is a queue where a queue manager (or application) delivers messages when it cannot deliver the message to its correct destination. |
Transmission Queue | A transmission queue is a local queue (to which a channel is connected) where messages that are targeted to a remote queue are temporarily stored. |