Order of migration tasks on z/OS
Read this information that shows an overall migration plan for your system, together with the order in which you must undertake the tasks.
Before you begin
Read the information in Clustering: Best practices and Clustering: Topology design considerations to understand repositories.
About this task
The tables within this topic show the tasks required in each part of the process to migrate an overall system, and the order in which these tasks must be done. Notes:
- You must perform the tasks in the following order:
Queue managers in a queue sharing group (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.
If there are queue managers in clusters, ensure that you migrate the full repository queue managers before migrating any partial repository queue managers, so that the cluster always has a full picture of the current cluster architecture.
Table 1. Overview of migration on z/OS Task For your own use 1. Make your configuration ready for migration 2. Install the new code 3. Server application migration
Table 2. Migrating your system to the next release on z/OS Task For your own use Full repositories Overview - Migrate one full repository on IBM MQ for z/OSĀ® in a QSG 4. Migrate DB/2 tables and New CF structure definitions 5. Migrate the queue manager 6. Migrate other full repositories on IBM MQ for z/OS, if any 7. Full repositories not in a QSG 8. Full repositories on other platforms Other queue managers Overview - Migrate partial repositories on IBM MQ for z/OS, in a QSG 9. Migrate DB/2 tables and New CF structure definitions if not yet done 10. Migrate one queue manager 11. Test the migration and upgrade the other queue managers 12. Migrate the partial repositories not in a QSG Migrate queue managers not in a queue sharing group or cluster on IBM MQ for z/OS 13. Migrate partial repositories on other platforms 14. Migrate queue managers not in a cluster on other platforms Testing and using new function; see Post migration tasks 15. Regression tests 16. Use the new function available to you We can upgrade the client libraries at any time during the process. As a final task, recompile the clients using new functions and deploy.
Results
You have migrated your system to another release.