Applying upgrades and fixes to IBM MQ
The term upgrade applies to changing the version V, release R, or modification M of a product. The term fix applies to a change in the F digit.
About this task
When you upgrade from one release to another, or apply fix packs, or interim fixes, the impact of the change depends on the extent of the change in the V, R, M, F level. The V, R, M are explained in The version naming scheme for IBM MQ for Multiplatforms.
At each change of V, R, or M, the command level on the queue manager changes, but on a change to F, the command level does not.
On IBM MQ for Multiplatforms, after an upgrade has been applied, the only way to back out a V.R.M change is by:
- Uninstalling the product code and reinstalling the code, or
- 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, we cannot back out the changes.
- Characteristics of upgrades and fixes
For IBM MQ, the term upgrade applies to changing the version V, release R, or modification M of a product. The term fix applies to a change in the F digit.- Upgrading an IBM MQ installation on Windows
To upgrade an IBM MQ server installation on Windows, from one version, release, and modification level to a later one, we can use either the Launchpad or msiexec. To upgrade a client installation, we can use either the GUI installer or msiexec.- Upgrading RDQM (replicated data queue managers)
We can upgrade RDQM when applying a fixpack by using the supplied upgrade script.Parent topic: Maintain and migrate IBM MQ
Related concepts