Introduction to IBM MQ migration
These topics explain the concepts that you must understand before planning migration
tasks, where to find migration topics, and which migration paths are supported.
Migration paths
An overview of the migration paths between different IBM MQ versions. For some IBM MQ for z/OS® migration paths, you can revert to the version you were using prior to migration. For other platforms, you cannot easily revert to a previous version.
The version naming scheme for IBM MQ for z/OS
On IBM MQ for z/OS , releases have a three-digit Version, Release, and Maintenance (VRM) level code. The code is significant; it identifies the service life of a release. To run a queue manager at a different VRM level, you must migrate the queue manager, its applications, and the environment in which it runs. Depending on the migration path, the migration might require more or less effort.
The version naming scheme for IBM MQ (On platforms other than z/OS )
IBM MQ releases have a four-digit Version, Release, Modification, and Fix (VRMF) level code.
Internet Protocol Version 6 (IPv6) migration
This section deals with using IPv4 and IPv6 when you are thinking of installing IBM MQ
Overview of migration methods
An overview of the various methods of migrating IBM MQ from one release to another are explained, together with a brief description of the difference between maintenance, migration, and upgrading.
Maintenance, upgrade, and migration
Maintenance is a reversible change to the code level of IBM MQ . Maintenance requires no migration. Upgrading is the process of changing the code level of IBM MQ . Migration is the process of updating queue managers, and other objects, such as applications or administrative procedures.
Coexistence, compatibility, and interoperability
The definitions of the IBM MQ terms coexistence, compatibility, and interoperability.
Queue manager migration
After upgrading an installation, queue manager migration might be required. Migration takes place when you start a queue manager.
Reverting a queue manager to a previous version
You can remove an upgrade before you have started a queue manager. After a queue manager has been started, if you remove the upgrade, the queue manager will not work.
IBM MQ MQI client migration
IBM MQ MQI client migration is the process of converting IBM MQ MQI client configurations, and client and server channels from one version to another. Client migration can take place after upgrading the IBM MQ MQI client , and are reversible.
Application migration and interoperation
IBM MQ supports running applications compiled and linked against previous versions of IBM MQ , with later levels of IBM MQ .
Queue manager cluster migration
You can migrate queue managers in a cluster all at once, or one at a time, which is called a staged migration. Migrate full repository queue managers in a cluster before partial repository queue managers.
Queue-sharing group migration
You can combine queue managers from different releases in a queue-sharing group. Limit the time you manage a mixed group to only as long as it takes to migrate all the queue managers to the same command level. You cannot combine a queue manager at Version 8.0 or later in the same queue-sharing group as queue managers earlier than Version 7.0.1 . You must update all queue managers in a queue-sharing group with a coexistence PTF, before migrating any of them. All queue managers in the queue-sharing group must be at the same version before any queue manager can be migrated to Version 8.0 .
Migrating a queue manager in a high-availability configuration
Follow standard procedures to migrate a queue manager that is part of a high-availability configuration. (On platforms other than z/OS .)