Moving a queue manager to a different operating system

Follow these instructions to move a queue manager from one operating system to another. Note that this is not a migration of a queue manager.

About this task

You move a queue manager by re-creating it on the target system. The procedure re-creates the configuration of the queue manager, it does not attempt to re-create the current state of the queue manager by, for example, unloading and reloading queues.

Procedure

1. Log in to the source system as a user in the IBM MQ administrators (mqm) group.
2. Save the configuration information of the queue manager that we want to move by typing the following command:

   dmpmqcfg -a -m QM_name > QM_file
   

   Where:
   • QM_name is the name of the queue manager that we want to move.
   • QM_file is the name and path of a local file on the source system that the configuration information is written to.

   See dmpmqcfg for more information.

3. If the queue manager is part of a distributed configuration, quiesce the queue manager. Ensure that there are no messages in flight, then stop the queue manager.
4. Optional: If we are moving from one version of the product to another, migrate the queue manager on your current operating system, to the latest version. If your current operating system is:
   • Windows, see Migrating a queue manager to a later version on Windows
   • UNIX or Linux, see Migrating a queue manager on UNIX and Linux

   We should ensure that your existing applications still work.

5. Create an empty queue manager on your new operating system, using crtmqm.
6. Copy your object definitions across to the new queue manager you have just created, using dmpmqcfg. We should take great care when you copy the object definitions, because some manual modification of the definitions might be needed:
   • Various attributes need to be checked and might need to be changed. These include:
     • Ip addresses and ports in channels, listeners, and other objects
     • Security information such as user IDs
     • startcmd in services
     • Various other attributes.

   • Durable subscribers that are not administered might lose messages.
   • Other queue managers might also need to be changed so that their channels connect to the moved queue manager.

   Once the definitions have been copied across, the application messages from the queue manager, on your original operating system, need to be copied to the queue manager on your new operating system, using an application that moves messages. Then check the applications still work.

Parent topic: Migrating IBM MQ