Organizing a cluster

Select which queue managers to link to which full repository. Consider the performance effect, the queue manager version, and whether multiple CLUSSDR channels are desirable.

Having selected the queue managers to hold full repositories, we need to decide which queue managers to link to which full repository. The CLUSSDR channel definition links a queue manager to a full repository from which it finds out about the other full repositories in the cluster. From then on, the queue manager sends messages to any two full repositories. It always tries to use the one to which it has a CLUSSDR channel definition first. We can choose to link a queue manager to either full repository. In choosing, consider the topology of our configuration, and the physical or geographical location of the queue managers.

Queue managers on IBM MQ z/OS Version 6.0 or later support PCF commands. The IBM MQ Explorer can use them to query information about the cluster (in just the same way as with distributed queue managers).

z/OS queue managers up to IBM MQ v5.3.1 do not support PCF commands. The IBM MQ Explorer cannot use them to query information about the cluster. For this reason, the IBM MQ Explorer does not allow you to select IBM MQ v5.3.1 z/OS queue managers at the source of the information about a cluster.

Because all cluster information is sent to two full repositories, there might be situations in which we want to make a second CLUSSDR channel definition. We might define a second CLUSSDR channel in a cluster that has many full repositories spread over a wide area. We can then control which two full repositories your information is sent to.

Parent topic: Designing clusters