Windows: Migrating a queue manager from a previous version to the latest version

Follow these instructions to migrate a queue manager from your current version to the latest version.

Before you begin

Create a migration plan; see Planning migration to the latest version
For more information about the versions of Windows that IBM® MQ 8.0 supports, see System Requirements for IBM MQ V8.0.
Review the IBM MQ system requirements for the latest version; see System Requirements for IBM MQ.
Back up your system before you install the latest release of IBM MQ over a previous release. Once you have started a queue manager you cannot revert to the previous release.
If you must restore the system, you cannot recover any work, such as changes to messages and objects, performed by the latest version of IBM MQ. For more information about backing up your system, see Backing up and restoring IBM MQ queue manager data.
Review any other installed SupportPacs for their applicability to the latest release.
If you are running on a server with multiple IBM MQ installations, you must identify the installation. Make sure that the commands you enter run against the correct installation; see setmqenv.

About this task

Complete this task to migrate a queue manager to the latest version of IBM MQ from an earlier version.

All the objects that you previously created are maintained. The components that were previously installed are preselected in the feature options when you install the new level. If you leave these components selected, you can keep them or reinstall them. If you clear any of these components, the installation process uninstalls them. By default, a typical migration installs only the same features that were installed in the previous version installation.

For example, if MQ Explorer was not installed in an earlier installation, it is not stored in a later installation. If you want MQ Explorer, select a custom installation, and select the MQ Explorer feature on the Features panel. If you do not want MQ Explorer, uninstall the MQ Explorer feature by selecting a custom installation. Then clear the MQ Explorer feature on the Features panel. For more information about how to uninstall features, see Modifying the installation using IBM MQ Installation Launchpad.

You can also migrate a queue manager to a later release, on a system where a previous version has been uninstalled. The queue manager data must have been retained, or restored from a backup.

Procedure

Log in as a user in group mqm.
Stop all applications using the IBM MQ installation.
If you use the MQ Managed File Transfer (MFT) component, ensure that any MFT agents have finished all of the file transfers that they were engaged in. There should be no incomplete transfers associated with the agents, and their SYSTEM.FTE.STATE queues should contain no messages.
End all the activity of queue managers associated with the IBM MQ installation.
1. Run the dspmq command to list the state of all the queue managers on the system.
  Run either of the following commands from the installation that you are updating:
```
dspmq -o installation -o status
dspmq -a
```
  dspmq -o installation -o status displays the installation name and status of queue managers associated with all installations of IBM MQ.
  
  dspmq -a displays the status of active queue managers associated with the installation from which the command is run.
2. Run the MQSC command, DISPLAY LSSTATUS(*) STATUS to list the status of listeners associated with a queue manager.
```
echo "DISPLAY LSSTATUS(*) STATUS" | runmqsc QmgrName
```
3. Run the endmqm command to stop each running queue manager associated with this installation.
  The endmqm command informs an application that the queue manager it is connected to is stopping; see Stopping a queue manager.
  - For the maintenance to proceed, applications must respond to an endmqm command by disconnecting from the queue manager and releasing any IBM MQ libraries they have loaded. If they do not, you must find another way to force applications to release IBM MQ resources, such as by stopping the applications.
  - You must also stop applications that are using the client libraries that are part of the installation. Client applications might be connected to a different queue manager, running a different installation of IBM MQ. The application is not informed about queue managers in the current installation being shut down.
  - Any applications that continue to have IBM MQ shared libraries from the installation loaded prevent you applying IBM MQ maintenance. An application might disconnect from a queue manager, or be forcibly disconnected, but keep an IBM MQ shared library loaded.
  Note: The topic, Applying maintenance level updates to multi-instance queue managers, describes how to apply maintenance to a multi-instance queue manager. A multi-instance queue manager can continue to run on one server, while maintenance is applied to another server.
4. Stop any listeners associated with the queue managers, using the command:
```
endmqlsr -m QMgrName
```
Back up the queue manager.
Stop the MQSeries® Service and exit the Service icon application.
Modify the IBM MQ installation, if necessary, by using one of these procedures:
- Modifying the installation using IBM MQ Installation Launchpad
- Silently modifying an IBM MQ server installation using msiexec
Reenter domain, user ID, and password information

When the installation of the latest version completes, the Prepare WebSphere MQ Wizard starts automatically.

Where UAC is enabled: If you rerun the Prepare WebSphere MQ Wizard, ensure that the wizard is run with Administrator privilege, otherwise the wizard might fail.
If you are running IBM WebSphere® MQ 7.0.1.6 or later, optionally uninstall the current version of IBM MQ.
Note, that you carry out this step only if you are doing a single stage migration; see UNIX, Linux, and Windows: Single-stage migration to a later version

What to do next

You might be restoring a previous version on a server with multiple IBM MQ installations. If one of the installations is primary, after restoring the previous version that installation, by default, becomes the primary installation.

You must review how applications connect to an installation. After restoring the previous version, some applications might connect to the wrong installation.