Post migration tasks

Follow the steps to perform the tasks you need to carry out after migrating a single IBM® MQ queue manager on z/OS®,

1. Check the changes in behavior made by default configuration changes.
   The default values of some properties might have been changed in the new version, which can lead to changes in behavior.

   SHARECNV allows multiple connections to the queue manager to permit the use of the same TCP/IP connection. If a client is using Version 6 code to connect to a version 7, or later, IBM MQ queue manager, SHARECNV is set to 0 automatically; see Default behavior for more details about this change.

   On z/OS, you can reverse queue manager migration as long as you have not enabled new function. You enable new function by setting the OPMODE parameter to (NEWFUNC,800) ; see OPMODE for more information.

2. Modify backup, and other administrative, jobs to refer to the target version of IBM MQ libraries, such as backup IBM MQ objects and MAKEDEF jobs.
   For example using CSQUTIL COMMAND MAKEDEF(..); see Using the COMMAND function of CSQUTIL.

   You should also backup channel authentication records, which were introduced in IBM WebSphere® MQ 7.1.0.

3. If the queue manager is configured to use Advanced Message Security (AMS) perform the steps in the Post migration tasks for Advanced Message Security section of the Migrating Advanced Message Security topic.
4. Perform a full regression test.
5. Update the ZPARM module if you have not already done so.
   See Update the ZPARM module for further information.
6. Set OPMODE in ZPARM JCL to NEWFUNC and recompile the JCL.
   For more information about NEWFUNC, see OPMODE.
7. Exploit the new functions provided by the migrated queue manager.
   Your queue manager has been fully migrated to a new version level, and you can take benefit of new capability now.

   Review What's new in IBM MQ 8.0 and check which features best serve your business needs. Plan your action to develop new applications, or changing configurations, to enable those features.

8. Migrate client applications.
   Client applications running on z/OS, or other distributed platforms, can be considered any time throughout the migration phase.

   The client libraries need to be at the same level as the lowest IBM MQ queue manager level to which they connect. So, if a client can connect to Version 701, Version 710, or Version 800 IBM MQ queue managers, the client needs to be at Version 701. Once all the IBM MQ queue managers have been migrated to Version 800 you can migrate the clients to Version 800.

   For further information, see Migrating an IBM MQ MQI client on UNIX platforms, and Windows to the latest version and select the platform that you require.