Home

 

Cluster transmission queue

 

Each cluster queue manager has a cluster transmission queue called SYSTEM.CLUSTER.TRANSMIT.QUEUE. A definition for this queue (and others required for clustering) is created by default on every queue manager except on z/OS where it can be defined using the supplied sample CSQ4INSX.

A queue manager that is part of a cluster can send messages on the cluster transmission queue to any other queue manager that is in the same cluster.

Applications must not write directly to the cluster transmission queue. They write to named queues that resolve to the cluster transmission queue. Similarly, not specify the cluster transmission queue as a named transmission queue in a remote queue definition, or specify it as the queue manager's default transmission queue.

Queue managers can also communicate with other queue managers that are not part of a cluster. To do this, a queue manager must define channels and a transmission queue to the other queue manager, in the same way as in a distributed-queuing environment.

During name resolution, the cluster transmission queue takes precedence over the default transmission queue. When a queue manager that is not part of a cluster puts a message to 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. When the sending queue manager is part of a cluster, the default action, if there is no transmission queue with the same name as the destination queue manager, is to use SYSTEM.CLUSTER.TRANSMIT.QUEUE, except when the destination queue is not part of the cluster. In short, if the normal resolution takes place, the normal transmission queue is used if the queue is resolved using the full repository, SYSTEM.CLUSTER.TRANSMIT.QUEUE is used.

 

Parent topic:

Components of a cluster

qc10730_

 

Home