Queue Manager Clusters: Moving a full repository to another queue manager

Moving a full repository to another queue manager

Scenario

The INVENTORY cluster has been set up as described in Adding a new queue manager that hosts a queue and modified as described in Removing a cluster queue from a queue manager and Removing a queue manager from a cluster.
For business reasons you now want to remove the full repository from queue manager LONDON, and replace it with a full repository at queue manager PARIS. The AMSTERDAM queue manager is to continue holding a full repository.

1. Alter PARIS to make it a full repository queue manager

On PARIS, issue the following command:
ALTER QMGR REPOS(INVENTORY)
2. Add a CLUSSDR channel on PARIS

PARIS currently has a cluster-sender channel pointing to LONDON. Now that LONDON is no longer to hold a full repository for the cluster, PARIS must have a new cluster-sender channel that points to AMSTERDAM, where the other full repository is held.
DEFINE CHANNEL(TO.AMSTERDAM) +
        CHLTYPE(CLUSSDR) +
        TRPTYPE(TCP) +
        CONNAME(AMSTERDAM.CHSTORE.COM) +
        CLUSTER(INVENTORY)
+
        DESCR('Cluster-sender channel from PARIS to repository at AMSTERDAM')
3. Define a CLUSSDR channel on AMSTERDAM that points to PARIS

Currently AMSTERDAM has a cluster-sender channel pointing to LONDON. Now that the other full repository has moved to PARIS, you need to add a new cluster-sender channel at AMSTERDAM that points to PARIS.
DEFINE CHANNEL(TO.PARIS) +
        CHLTYPE(CLUSSDR) +
        TRPTYPE(TCP) +
        CONNAME(PARIS.CHSTORE.COM) +
        CLUSTER(INVENTORY) +
        DESCR('Cluster-sender channel from AMSTERDAM to repository at PARIS')
When you do this, the PARIS queue manager immediately learns all about the cluster from AMSTERDAM and builds up its own full repository.

4. Alter the queue-manager definition on LONDON

Finally alter the queue manager at LONDON so that it no longer holds a full repository for the cluster. On LONDON, issue the command:
ALTER QMGR REPOS(' ')
The queue manager no longer receives any cluster information. After 30 days the information that is stored in its full repository expires. The queue manager LONDON now builds up its own partial repository.

5. Remove or change any outstanding definitions

When you are sure that the new arrangement of your cluster is working as expected, you can remove or change any outstanding definitions that are no longer up-to-date. It is not essential that you do this, but you might choose to in order to tidy up.
On the PARIS queue manager, delete the cluster-sender channel to LONDON.
DELETE CHANNEL(TO.LONDON)
On the AMSTERDAM queue manager, delete the cluster-sender channel to LONDON.
DELETE CHANNEL(TO.LONDON)
Replace all other cluster-sender channels in the cluster that point to LONDON with channels that point to either AMSTERDAM or PARIS. (In this small example there are no others.) To check whether there are any others that you have forgotten issue the DISPLAY CHANNEL command from each queue manager, specifying TYPE(CLUSSDR). For example:
DISPLAY CHANNEL(*) TYPE(CLUSSDR)