A fix is available
APAR status
Closed as program error.
Error description
You migrate MQ V7 z/OS V1.10 to MQ V8 z/OS V2.0.1 Failing scenario: 1. Message is PUT when queue manager is at V710. 2. MQ queue manager is upgraded to MQ V800. 3. MQ queue manager is backwards-migrated to V710. The message is not retrievable after backwards migration. This problem is applicable to any private queue where the application is geting by msgtoken (MQMO_MATCH_MSG_TOKEN). Even after migration forward to MQ V8 again, the message can not be gotten by matching on MQMO_MATCH_MSG_TOKEN. . 5655W9700 R000
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Backwards migration may result in MQGET * * calls not returning the message when * * used with the match option, * * MQMO_MATCH_MSG_TOKEN, resulting in MQRC * * 2033 (MQRC_NO_MSG_AVAILABLE). This * * occurs when the original messages were * * put to the queue prior to the initial * * migration to a later version. This also * * affects messages retrieved through MDBs * * or by the CICS Bridge. * **************************************************************** * RECOMMENDATION: * **************************************************************** MQMO_MATCH_MSG_TOKEN processing ensures the DMC pointer for the IRH of the message being requested matches that of the queue object being used for the MQGET. However during migration to a later level of the queue manager, a new internal object is created to hold the updated object version, with the object retaining a pointer to the old object, oldDMCP. However during backwards migration, this pointer is cleared. This results in the matching processing not correctly identifying the message as the one being requested by the MQGET, resulting in the message not being retrieved.
Problem conclusion
Backwards migration code has been updated to no longer clear the oldDMCp field, to allow the match option to correctly get the message requested. 100Y CSQEDB2R CSQEKATM CSQERIND CSQERWI1 CSQESTRF CSQE197N CSQIDEL5 CSQIECUR CSQIERS3 CSQIEXP1 CSQILEPL CSQILOC2 CSQMCIGI CSQMDURR CSQP1INI CSQXRFIC CSQYSCMD CSQ5AROB CSQ5CONN CSQ5LOBC CSQ5PQSG CSQ5READ CSQ5R710
Temporary fix
Comments
APAR Information
APAR number
PI54383
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
100
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-12-17
Closed date
2016-01-14
Last modified date
2016-11-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI34475
Modules/Macros
CSQEDB2R CSQEKATM CSQERIND CSQERWI1 CSQESTRF CSQE197N CSQIDEL5 CSQIECUR CSQIERS3 CSQIEXP1 CSQILEPL CSQILOC2 CSQMCIGI CSQMDURR CSQP1INI CSQXRFIC CSQYSCMD CSQ5AROB CSQ5CONN CSQ5LOBC CSQ5PQSG CSQ5READ CSQ5R710
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI34475
UP16/02/03 P F602 {
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.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
29 November 2016