Home

 

Overlapping clusters

 

We can create clusters that overlap, as described in Putting across clusters. There are a number of reasons you might do this, for example:

• To allow different organizations to have their own administration.

• To allow independent applications to be administered separately.

• To create classes of service.

• To create test and production environments.

In Figure 1 the queue manager QM2 is a member of both the clusters illustrated. When a queue manager is a member of more than one cluster, we can take advantage of namelists to reduce the number of definitions we need. A namelist can contain a list of names, for example, cluster names. We can create a namelist naming the clusters, and then specify this namelist on the ALTER QMGR command for QM2 to make it a full repository queue manager for both clusters. See Task 7: Adding a new, interconnected cluster for some examples of how to use namelists.

If you have more than one cluster in your network, give them different names. If two clusters with the same name are ever merged, it will not be possible to separate them again. It is also a good idea to give the clusters and channels different names so that they are more easily distinguished when you look at the output from DISPLAY commands. Queue manager names must be unique within a cluster for it to work correctly.

• Defining classes of service
  

 

Parent topic:

Designing clusters

qc11260_

 

Home