A fix is available
APAR status
Closed as new function.
Error description
Allow V701 or V710 queue-manager backwards migration from V8, and coexistence with a V8 queue-manager in a queue-sharing group. . Trying to migrate to V8 without the queue-managers in the queue-sharing group having been previously started with the PTF for this APAR will result in CSQ5005E and the queue-manager terminating with CSQV086E REASON 00F50029. . Note for L2/L3 : after applying the PTF and restarting the queue-manager, MVERSIONH (T02_MVERSIONH) in DB2 will be updated to 7 if all queue-managers are at the same level (i.e. all at V701 or all at V710; MVERSIONH 4 will 4 otherwise). . Additional keywords: MQ0800C/K toleration
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 0 Modification 1 and Version 7 * * Release 1 Modification 0 * **************************************************************** * PROBLEM DESCRIPTION: Enable backward migration to version * * 7.0.1 after a queue manager has been * * started with the version 8.0.0 code. * * * * Enable backward migration to version * * 7.1.0 after a queue manager has been * * started with the version 8.0.0 code. * * * * Enable version 7.0.1 queue managers to * * co-exist in a queue sharing group with * * version 8.0.0 queue managers. * * * * Enable version 7.1.0 queue managers to * * co-exist in a queue sharing group with * * version 8.0.0 queue managers. * **************************************************************** * RECOMMENDATION: * **************************************************************** PTFs for the backward migration APAR must be applied on version 7 queue managers prior to attempting fallback from IBM MQ for z/OS version 8.0.0. Attempting to restart a queue manager, which has been run with version 8.0.0 libraries, at version 7 without this PTF will result in abnormal termination of the queue manager with ABEND5C6 reason code 00C90D01. The WebSphere MQ for z/OS ISPF administration panels, CSQOREXX, are not updated by this APAR. The version 8.0.0 CSQOREXX application is able to connect to and administer both version 7.0.1 and 7.1.0 queue managers and you are advised to use either version 8.0.0 panels, or those at the same level as your queue manager during the period of migration. In a mixed version queue sharing group, version 8 panels must be used for group operations such as modifying QSGDISP(GROUP) objects and targeting operations at the entire queue sharing group. Version specific notes follow: When reverting to Version 7.0.1 after running a queue manager at version 8.0.0 the following should be considered: - CHLAUTH objects are stored on the SYSTEM.CHLAUTH.DATA.QUEUE. They will not be visible at Version 7.0.1 but will reappear when the queue manager is subsequently restarted at Version 8.0.0 - New object attributes introduced in Version 8.0.0 will not be present in Version 7.0.1, and when you subse1uently migrate to Version 8.0.0 they will be reset to default values. - If you are using the MQ Explorer to administer your queue manager then after migration between releases the following Explorer actions must be performed: 1: Remove the migrated z/OS queue manager 2: Add Remote Queue Manager - AUTHINFO objects with AUTHTYPE(IDPWOS) will be deleted on backward migration. Any QSGDISP(GROUP) AUTHINFO objects with AUTHTYPE(IDPWOS) will be invisible to a Version 7.0.1 queue manager in a mixed Version 8.0.0 and Version 7.0.1 queue sharing group. - TOPIC objects with CLROUTE(TOPICHOST) attribute set will be deleted on backward migration. Any QSGDISP(GROUP) TOPIC objects having CLROUTE(TOPICHOST) attribute set are hidden from a Version 7.0.1 queue manager in a mixed Version 8.0.0 and Version 7.0.1 queue sharing group. - Proxy subscriptions created on behalf of remote subscribers for TOPICs defined with CLROUTE(TOPICHOST) attribute will be deleted when the TOPIC object is removed on backwards migration. - When there are subscribers on the queue manager being backward migrated, for TOPICs defined with CLROUTE(TOPICHOST) on different queue managers, the proxy subs for these subscribers will be left on the queue managers hosting the topic. The local subscriber will continue to receive publications. If the queue manager hosting the TOPIC is also backwards migrated, then the proxy subs will be deleted. These subscriptions can be identified by issuing DISPLAY SUB(SYSTEM.PROXY_2*) SUBTYPE(PROXY) on the remote host queue managers and looking for subscriptions with a DESTQMGR matching the local queue manager which is being backwards migrated. They can then be deleted as for any administrative subscription using the DELETE SUB command. When reverting to Version 7.1.0 after running a queue manager at version 8.0.0 the following should be considered: - New object attributes introduced in Version 8.0.0 will not be present in Version 7.1.0, and when you subsequently migrate to Version 8.0.0 they will be reset to default values. - If you are using the MQ Explorer to administer your queue manager then after migration between releases the following Explorer actions must be performed: 1: Remove the migrated z/OS queue manager 2: Add Remote Queue Manager - AUTHINFO objects with AUTHTYPE(IDPWOS) will be deleted on backward migration. Any QSGDISP(GROUP) AUTHINFO objects with AUTHTYPE(IDPWOS) will be invisible to a Version 7.1.0 queue manager in a mixed Version 8.0.0 and Version 7.1.0 queue sharing group. - TOPIC objects with CLROUTE(TOPICHOST) attribute set will be deleted on backward migration. Any QSGDISP(GROUP) TOPIC objects having CLROUTE(TOPICHOST) attribute set are hidden from a Version 7.1.0 queue manager in a mixed Version 8.0.0 and Version 7.1.0 queue sharing group. - Proxy subscriptions created on behalf of remote subscribers for TOPICs defined with CLROUTE(TOPICHOST) attribute will be deleted when the TOPIC object is removed on backwards migration. - When there are subscribers on the queue manager being backward migrated, for TOPICs defined with CLROUTE(TOPICHOST) on different queue managers, the proxy subs for these subscribers will be left on the queue managers hosting the topic. The local subscriber will continue to receive publications. If the queue manager hosting the TOPIC is also backwards migrated, then the proxy subs will be deleted. These subscriptions can be identified by issuing DISPLAY SUB(SYSTEM.PROXY_2*) SUBTYPE(PROXY) on the remote host queue managers and looking for subscriptions with a DESTQMGR matching the local queue manager which is being backwards migrated. They can then be deleted as for any administrative subscription using the DELETE SUB command.
Problem conclusion
Temporary fix
Comments
×**** PE15/12/17 FIX IN ERROR. SEE APAR PI54383 FOR DESCRIPTION
APAR Information
APAR number
PI19721
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
010
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-06-11
Closed date
2014-10-03
Last modified date
2016-01-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI21966 UI21967
Modules/Macros
CSQERIND CSQERIN1 CSQERWI1 CSQESTRF CSQIECUR CSQIERS3 CSQMCIGI CSQMDURR CSQP1INI CSQXRFIC CSQYSCMD CSQ5AROB CSQ5AUOB CSQ5CONN CSQ5LOBC CSQ5PQSG CSQ5READ CSQ5R701 CSQ5R710 CSQ5UPDT CSQ5U701
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 January 2016