Upgrading IBM MQ
Upgrading is the process of taking an existing IBM® MQ installation and upgrading to a new level of code.
Before you begin
This task assumes that you understand the difference between Long Term Support and Continuous Delivery releases, and the maintenance delivery model that applies in each case. For more information, see IBM MQ Release Types and versioning.
About this task
When you upgrade from one release to another, or apply maintenance, including fix packs, cumulative security updates (CSUs), or interim fixes, the impact of the change
depends on the extent of the change in the VRMF level:
- The term upgrade applies to increasing the version
V, releaseR, or modificationMlevel. - The term fix applies to increasing the fix
Flevel.
V, R, or M level, the
command level on the queue manager changes. On a change to the F level, the command
level does not change.
On Multiplatforms, after an upgrade has been applied, the only way
to back out a VRM change is by taking one of the following actions:- Uninstalling the product code and reinstalling the code.
- Installing the old level of code alongside the existing code and using the setmqm command to associate the queue manager with the other installation.
The general rule, is that if you have carried out an install that causes the command level of the new installation to be updated, and started the queue manager, you cannot back out the changes.
On z/OS®, you can install new
releases of IBM MQ to upgrade IBM MQ to a new VRM level. For more information, see Upgrade and migration of IBM MQ on z/OS.