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®,

About this task

After we have migrated an IBM MQ queue manager on z/OS you need to carry out the detailed steps in this topic, using the links within this overview.

1. Check the changes in behavior made by default configuration changes; see Step 1
2. Modify the backup jobs to refer to the target version of IBM MQ libraries; see Step 2
3. Configure Advanced Message Security; see Step 3
4. Perform a full regression test; see Step 4
5. Update the ZPARM module if we have not already done so; see Step 5
6. Set OPMODE to NEWFUNC; see Step 6
7. Exploit the new functions provided by the migrated queue manager; see Step 7
8. Consider client application migration; see Step 8

.

Procedure

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, we can reverse queue manager migration as long as we have not enabled new function. You enable new function by setting the OPMODE parameter to (NEWFUNC,900) ; 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 Use the COMMAND function of CSQUTIL.

   You should also backup channel authentication records, which were introduced in IBM WebSphere MQ Version 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 system parameter (ZPARM) module if required. Note the following:
   • You should review changes to the ZPARM parameters between the version we have migrated from, and IBM MQ Version 9.0.
   • If you need to change the value of any parameters, you should generate a new ZPARM at this point. Do this by:
     1. Tailoring the ZPARM sample to use the new IBM MQ libraries
     2. Updating values for the parameters as necessary, and
     3. Recompiling, to generate the new ZPARM.
   • You do not have to recompile the ZPARM, if we do not change the values of any parameters.
   • There are no changes to the ZPARM between IBM MQ Version 8.0 and IBM MQ Version 9.0, so this step is not necessary when migrating from Version 8.0 to Version 9.0.
   Attention: If you re-create the ZPARM for a Version 9.0.0 queue manager that has been migrated from Version 8.0, and had previously been running at OPMODE=(NEWFUNC,800), you must set the value of OPMODE to (NEWFUNC,900) to allow the continued availability of Version 8.0 new functions.

   You must do this, only if you are satisfied with the stability of the latest version, and do not need to revert to the previous version.

6. Set OPMODE in ZPARM JCL to NEWFUNC, and recompile the JCL for a Version 9.0.0 Long Term Support (LTS) release queue manager. Attention: You do not need to change OPMODE for a Continuous Delivery (CD) release queue manager at this stage.

   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 we can take benefit of new capability now.

   Review What's new in IBM MQ Version 9.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 can be considered any time throughout the migration phase.

   Clients are backwards and forwards compatible. It is advisable to migrate the client libraries to same level as the queue manager, or later, so that the latest function is available.

Results

You have completed the migration of a single IBM MQ for z/OS queue manager.