Migrating IBM MQ for z/OS - order of tasks

Perform these instructions, in the order shown, to migrate a single IBM® MQ for z/OS® queue manager.

Before migration

• Before migration, complete the following tasks:
  1. Make your existing queue manager ready for migration
  2. Install IBM MQ for z/OS 9.3
  3. Perform a backup operation
  4. Run CSQ5PQSG, if using queue sharing groups
  5. Update the STEPLIB concatenations for Batch, TSO, and RRS applications
  6. Update the libraries you added to connect CICS to the queue manager
  7. Update the libraries for the operations and control panels to the latest version IBM MQ libraries
  8. Update system libraries to format IBM MQ dumps using the Interactive Problem Control System (IPCS)
  9. Consider the migration of other server applications
  10. Prepare the mqweb server for migration

Migrating to the next release

• To migrate to the next release, complete the following tasks:
  1. Update the initialization input data sets
  2. Stop or disconnect all the applications using the queue manager
  3. Stop the queue manager and its channel initiator
  4. Update STEPLIB for the queue manager and the channel initiator
  5. Update the queue manager startup JCL to add the CSQMINI DD card
  6. If using Advanced Message Security set the AMSPROD attribute.
  7. If using a CipherSpec for a channel with SSLCIPH set to its direct hexadecimal value, for example 009D, update the channel initiator startup JCL to enable the relevant protocol .
  8. If migrating to IBM MQ 9.3.1 or later, increase the MEMLIMIT parameter in the channel initiator JCL to a minimum of 2G.
  9. Start the queue manager and channel initiator
  10. Test that everything is working correctly. If a problem occurs, revert the queue manager to a previous version
  11. Optionally, migrate the mqweb server

Post migration tasks

• After migration, complete the following tasks:
  1. Check the changes in behavior
  2. Modify the backup jobs to refer to the target version of IBM MQ libraries
  3. Update the ZPARM module, if required
  4. Perform a full regression test
  5. Migrate client applications
  6. Exploit the new functions provided by the migrated queue manager
  7. Optionally, stop the mqweb server for previous versions