If you have not previously used queue-sharing groups, do not introduce them now. Wait until you have migrated to Version 6.0. If you are using queue-sharing groups, you must migrate them to Version 5.3.1.
This might affect Tasks 8, 9, and 15 in Customizing your queue managers.
The steps outlined below are designed to let you migrate an existing queue-sharing group containing Version 5.2 queue managers to Version 5.3.1. The sequence has been designed so that at no stage is an outage of the entire queue-sharing group required. Version 5.2 and 5.3.1 queue managers can coexist within a queue-sharing group, however, some functions are not supported on the Version 5.2 queue managers and some operations are not available until all queue managers in the queue-sharing group have been migrated to Version 5.3.1. See Coexistence of WebSphere MQ V5.3.1 and earlier versions for more information about the coexistence of different versions.
You cannot add a Version 5.3.1 queue manager to a queue-sharing group, or start an existing queue manager in a queue-sharing group at Version 5.3.1 level, until all the queue managers in the DB2(R) data-sharing group have had a migration & coexistence PTF applied. This is because Version 5.3.1 requires new DB2 tables and additional changes to existing DB2 tables.
Similarly, once a Version 5.3.1 queue manager has been started in a queue-sharing group you cannot start a Version 5.2 queue manager as a member of the group unless it has the migration & coexistence PTF applied.
You need to take the following steps:
BIND PLAN(CSQR221) - MEMBER(CSQR220) - ...
binds replacement DBRM CSQR220 into a new plan CSQR221.
This means that you have two sets of plans, those with a 220 version number for queue managers without the PTF, and those with a 221 version number for queue managers with the PTF applied. Module CSQ5PLAN (and its aliases) also changes the DB2 plans to be used by WebSphere MQ in the PTF names, so after applying the migration & coexistence PTF, MQSeries(R) for OS/390(R) Version 5.2 expects plans with a 221 version number to exist.
If you have queue managers defined in the data-sharing group that cannot be started with the PTF, they can be removed from the data-sharing group using the CSQ5PQSG utility.
To migrate the tables:
If these jobs fail because of a DB2 locking problem, it is probably due to contention for a DB2 resource, especially if the system is being heavily used. Resubmit the job later, preferably when the system is lightly used or quiesced.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
migqsga |