Migrating one cluster queue manager
Follow these steps to migrate a single queue manager in a cluster, starting with a queue manager in your test system. Base these steps on the cluster migration plan.
Procedure
- Suspend the queue manager that we want to migrate from the cluster:
- Issue the MQSC command:
SUSPEND QMGR CLUSTER(cluster name)- Check that no messages are sent to the queue manager.
We must close any application that continues to send messages to this queue manager. The cluster workload algorithm might choose the suspended queue manager. If there are no other valid destinations, or if an application has an affinity with the queue manager, it might select the queue manager.
- Save a record of all cluster objects known by this queue manager. This data is used after migration to check that objects have been migrated successfully.
- Issue the command to view cluster queue managers.
DISPLAY CLUSQMGR(*)- Issue the command to view cluster queues.
DISPLAY QC(*)- Issue the command to view cluster topics.
DISPLAY TCLUSTER(*)
- Save a record from the full repository of its view of the cluster objects owned by this queue manager. The record is used after migration to check that objects have been migrated successfully.
- Issue the command on the full repositories to display this queue manager.
DISPLAY CLUSQMGR(migrated queue manager name)- Issue the command on the full repositories to display the cluster queues for this queue manager
DISPLAY QC(*) WHERE(CLUSQMGR EQ migrated queue manager name)- Issue the command on the full repositories to display the cluster topics for this queue manager.
DISPLAY TCLUSTER(*) WHERE(CLUSQMGR EQ migrated queue manager name)
- Migrate the queue manager.
Do one of the queue manager migration tasks, depending on the platform; see Migrating a queue manager on Windows.
The queue manager migration process is, in outline:
- Stop the queue manager.
- Take a backup of the queue manager.
- Install the new version of IBM MQ .
- Restart the queue manager.
- Ensure that all cluster objects have been migrated successfully.
- Issue the command to view cluster queue managers and check the output against the data saved before migration.
DISPLAY CLUSQMGR(*)- Issue the command to view cluster queues and check the output against the data saved before migration.
DISPLAY QC(*)- Issue the command to view cluster topics and check the output against the data saved before migration.
DISPLAY TCLUSTER(*)
- Check that the queue manager is communicating with the full repositories correctly.
- Check that cluster channels to full repositories can start.
- Check that the full repositories still have information about the migrated cluster queue manager, its cluster queues, and its cluster topics.
- Issue the command on the full repositories and check the output against the data saved before migration.
DISPLAY CLUSQMGR(migrated_queue_manager_name)- Issue the command on the full repositories and check the output against the data saved before migration.
DISPLAY QC(*) WHERE(CLUSQMGR EQ migrated_queue_manager_name)- Issue the command on the full repositories and check the output against the data saved before migration.
DISPLAY TCLUSTER(*) WHERE(CLUSQMGR EQ migrated_queue_manager_name)
- Test that applications on other queue managers can put messages to queues owned by the migrated cluster queue manager.
- Test that applications on the migrated queue manager can put messages to the queues owned by other cluster queue managers.
- Resume the queue manager by issuing the following command:
RESUME QMGR CLUSTER(cluster name)- Closely monitor the queue manager and applications in the cluster for a while.
What to do next
When you have completed the migration of one queue manager in a cluster, on your test system, complete the migration of the other queue managers in each cluster on the test system.
When you have competed the migration of all of the queue managers on your test system, migrate each of the queue managers on your production system.
Parent topic: Migrating a queue manager cluster
Related concepts
Related information