Exporting a WebSphere MQ V5.3 queue manager by using exportmqm

Use mig/exportmqm to export a WebSphere MQ V5.3 queue manager.

The exportmqm utility exports queue manager non-SYSTEM.* objects and their configurations, Channel Synchronization records, user and object security settings, SSL files (if present) and, if selected, all the messages on the application local queues.

The exportmqm utility has the following syntax:

exportmqm -m QueueManagerName

exportmqm -m QM1

Where QM1 is the name of the WebSphere MQ V5.3 queue manager being migrated.

The exportmqm utility uses four files located in the install_path/opt/mqm/bin/mig directory of the IBM® MQ V8 installation. If there is no IBM MQ installation on the system where the queue manager is being exported from, these files must be copied to that system and the directory containing the files must be added to the PATH environment variable. If it is not present in PATH, the directory should be added to it, for example, export PATH=$PATH:dirname where dirname is the full path to the directory where these files are located.

exportmqm can be run on any H or J-Series system and with any supported version of WebSphere MQ V5.3.

To run exportmqm, you must source the IBM MQ wmqprofile file. This is because exportmqm requires that the MQNSKOPTPATH, MQNSKVARPATH, and _RLD_LIB_PATH environment variables are set.

The WebSphere MQ V5.3 queue manager must be running and its command server must also be running. The queue manager must be in a quiet state. This means that no application queues (that is, non SYSTEM.* queues) can be open, and all channels must be either inactive or STOPPED. The exportmqm utility checks for these conditions and does not continue if any of these conditions are not met.

The exportmqm utility also verifies that it has access to the \tmp directory on the system, and that it can run the required commands (for example, mkdir, tar). If any of the required commands cannot be run, exportmqm stops.

All checks and steps performed by exportmqm are recorded in a log file that is located in the local directory.

You are asked if you want to export messages that are on their application local queues. If you answer YES at the prompt, all messages in each queue are loaded into an individual file whose name contains the name of the queue.

As exportmqm is running, details of what it is doing are displayed. All the steps are also recorded in the log file.

exportmqm creates a compressed tarball file and a md5sum file in the directory from which it was run, for example MQ5EXPORT.MQ1.20170329-083048-1778385097.tar.Z and MQ5EXPORT.MQ1.20170329-083048-1778385097.tar.Z.md5 . Copy these two files to the location where you plan to run the import utility. This location could be on another NonStop system or on the local system, depending on where the IBM MQ V8 installation is.