How can I migrate MQ cluster full repository queue managers to new servers?

https://developer.ibm.com/answers/questions/183882/how-can-i-migrate-mq-cluster-full-repository-queue.html

Q:
I want to move my MQ cluster full repository queue managers to new servers. What's the best way to migrate to new servers without causing any downtime or cluster errors?

ANS:
We have to be careful with how we do this since the goal is to make the change as transparent to users as much as possible and also preserve cluster information integrity as much as we can. So if there are multiple full repositories, we can move each repository over from one box to another ONE at a time. Please move full repositories to new location first and then follow up with partials.

1. Alter QM1 to be a partial repository 
   alter qmgr repos(' ')
   
2. suspend QM1 from the cluster
   suspend qmgr cluster(cluster name)
   
3. alter cluster receiver on QM1 to take it out of a cluster 
   alter channel (channel name) chltype(clusrcvr)cluster (' ') 
   - stop channel 
   - delete channel
   
4. alter cluster sender to QM2 to take it out of the cluster 
   alter channel (channel name) chltype(clussdr)cluster (' ') 
   - stop channel 
   - delete channel 
   NOTE: At this point cluster has only one full repository QM2 and QM1 is out of the cluster. 
   All partial repositories will be able to function as they have 
   established connections to remaining full repository queue managers.

5. Issue RESET cluster command on QM2 and reference queue manager 
   name as QM1 to take all info about this queue manager from the 
   cluster out. This step will delete all information about QM1 including
   autodefined cluster sender channels in the cluster 
   reset cluster (cluster name) qmname(QM1) action(forceremove) queues(yes) 
   Issue display clusqmgr(*) to make sure that QM1 is no longer in the 
   cluster.
   
6. Take steps to define this queue manager on a new box and configure it to join your cluster. 
   Once queue manager is created on a new box: 
   - fill in REPOS attribute of a queue manager with the cluster name 
   - create a cluster receiver 
   - create a cluster sender channel pointing to QM2 
   NOTE: at this point, cluster has two full repositories again: one on a
   new box and one on an old box. Two full repositories will sink up 
   cluster information.

7. Repeat steps 1 - 5 for queue manager QM2 
   Reset cluster will have to be issued on QM1 referencing QM2 
   NOTE: At this point, cluster has only one full repository QM

8. Create QM2 on a new box and configure it to join cluster (by 
   this time NAT'd table changes should take place to service routing to 
   this new box if one is used) 
   Once queue manager is created on a new box 
   - fill in REPOS attribute of a queue manager with the cluster name 
   - create a cluster receiver 
   - create a cluster sender channel pointing to QM1 on a new box. 
   NOTE:Cluster has two new full repositories now that are connected to 
   each other!

9. Manually defined cluster sender channels from partial to full 
   repositories will have to be altered to contain a new conname that 

   points to a new location of a full repository of choice. 

https://developer.ibm.com/answers/questions/183882/how-can-i-migrate-mq-cluster-full-repository-queue.html