Home

 

Naming Convention

 

When setting up a new cluster, consider a naming convention for the queue managers. Every queue manager must have a different name, but it might help you to remember which queue managers are grouped where if you give them a set of similar names.

Every cluster-receiver channel must also have a unique name. One possibility is to use the queue-manager name preceded by the preposition TO. For example TO.QM1, TO.QM2, and so on. If you have more than one channel to the same queue manager, each with different priorities or using different protocols you might extend this convention to use names such as TO.QM1.S1, TO.QM1.N3, and TO.QM1.T4. A1 might be the first SNA channel, N3 might be the NetBIOS channel with a network priority of 3, and so on.

The find qualifier might describe the class of service the channel provides. See Defining classes of service for more details.

Remember that all cluster-sender channels have the same name as their corresponding cluster-receiver channel.

Do not use generic connection names on your cluster-receiver definitions. In WebSphere MQ for z/OS we can define VTAM generic resources or Dynamic Domain Name Server (DDNS) generic names, but do not do this if you are using clusters. If you define a CLUSRCVR with a generic CONNAME there is no guarantee that your CLUSSDR channels will point to the queue managers you intend. Your initial CLUSSDR might end up pointing to any queue manager in the queue-sharing group, not necessarily one that hosts a full repository. Furthermore, if a channel goes to retry status, it might reconnect to a different queue manager with the same generic name and the flow of your messages will be disrupted.

 

Parent topic:

Designing clusters

qc11250_

 

Home