Plan to migrate IBM MQ to Version 9.2 on z/OS

Create a plan for migrating IBM MQ for z/OS to Version 9.2.


Before starting

If there are concepts about migration we do not understand, see Migration concepts and methods.


About this task

Use the following steps as a guide to creating your own plan to migrate your queue managers to Version 9.2. Incorporate the task to migrate a queue manager, Migrating IBM MQ for z/OS - order of tasks, into your plan.

Migration plan overview for the enterprise
Migration phase Required tasks
Phase I, before migration. Prepare each queue manager in your enterprise for migration.

See Preparing to migrate a single IBM MQ for z/OS queue manager for further information.
Phase II, migrate each single queue manager in the order listed. Carry out this process for each queue manager:

  • For queue managers in a cluster, migrate full repository queue managers before migrating any partial repository queue managers.
  • Migrate z/OS queue managers in a queue sharing group (QSG) before queue managers that are not in a QSG.

See Migrating a single IBM MQ z/OS queue manager to Version 9.2 for further information.

Phase III, post migration. See Post migration tasks for further information.


Procedure

  1. Review the IBM MQ system requirements for Version 9.2.

  2. Review all the changes in the product that affect you. For further information, see What's new and changed in Version 9.2.0.
  3. Review performance changes. See IBM MQ - Performance documents.
  4. Plan the sequence and timing of queue manager migrations.

    • Check that any products using the queue managers support Version 9.2.
    • If the queue manager is a member of a queue manager cluster, we must consider the order of migration of queue managers in the cluster; see Migrating a queue manager cluster.
    • Queue managers in a QSG, and queue managers in a cluster can be migrated in parallel, but at any time there should be enough queue managers working in the QSG, and cluster, to ensure that your business can operate satisfactorily while a staged migration takes place; see Queue sharing group migration.

  5. Plan to update any manual or automated procedures you have written with changes to messages and codes.
  6. Plan to update applications that might be affected by changes. Consider whether the application must be able to run on both the previous version and Version 9.2. We might be able to change the application to be compatible with both code levels. If we cannot, we can query the queue manager command level, and make the code conditional on the command level. Call MQINQ setting the MQIA_COMMAND_LEVEL selector.
  7. Decide on what regression tests to perform after migrating. Include the procedures and applications you identified in steps 5 and 6 in your regression tests.
  8. Plan to migrate other vendor software, such as WebSphere Application Server, or CICS to use the later version.
  9. Review any other installed SupportPacs for their applicability to Version 9.2.


What to do next

Perform the steps in your plan.

Parent topic: Migrating IBM MQ on z/OS