UNIX systems - migrating a queue manager from your current version to the latest version

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

Before you begin

The upgrade from your current version to the latest version of the product requires a full migration of queue managers. Create a migration plan. Use the planning task, Planning migration to the latest version , as a guide.
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.

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.
Log in as root.
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
If you are running IBM WebSphere MQ 7.0.1.5 or earlier, uninstall the current version of IBM MQ.
If you require a side-by-side migration or multistage migration only, you must upgrade to IBM WebSphere MQ 7.0.1.6
Install the latest version of the product.
See the appropriate topic for the platform that your enterprise uses:
Move the queue manager to the new IBM MQ installation.
You need to carry out this step, only if you are running IBM WebSphere MQ 7.0.1.6 or later, and did not uninstall your current version of IBM MQ.
See UNIX, Linux, and Windows: Side-by-side migration to a later version or UNIX, Linux, and Windows: Multi-stage migration to a later version for further information.
Start the queue manager.
```
strmqm QmgrName
```
When you first start a queue manager after migration:
- Any new attributes for existing objects are set to their default values.
- Any new default objects are created.
- Queue manager data is migrated.
Important: Do not use the -c option to start the queue manager, unless you explicitly want to reset or recreate the default system objects.

You must start IBM MQ before you start any listeners.