Importing IBM MQ V8 data back into WebSphere MQ V5.3 using mig/importmqm

Use mig/importmqm to import queue data back into a WebSphere MQ V5.3 queue manager.

You should ensure that back ups are available before you use the utility.

The importmqm utility imports all the messages on the application local queues.

The importmqm utility has the following syntax:

importmqm -f ExportedFileName -m QueueManagerName

Where ExportedFileName is the name of the file that you are importing from, and -m QueueManagerName specifies a name for queue manager you are loading the data to.

importmqm -f MQ8EXPORT.MQ1.20170329-083048-1778385097.tar.Z  -m newQM

The importmqm 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.

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

To run importmqm, you must source the IBM MQ wmqprofile file. This is because importmqm 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 importmqm utility checks for these conditions and does not continue if any of these conditions are not met.

The importmqm utility also verifies that it has access to the 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, importmqm stops.

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

You are asked if you want to import messages that are on their application local queues. If you answer YES at the prompt, all messages in each queue are loaded from the archive to be imported.

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

Since importmqm only imports queue data, channels may have to be reset.

Queue data can only be migrated back to queue managers of the same name.