Fixes are available
APAR status
Closed as program error.
Error description
With Message Broker 7 (which uses the Publish-Subscribe engine of WebSphere MQ), the subscription response for a subscription request with an unknown subscription queue contains only the psc and the pscr folders. All other folders are removed from the request. This behavior is different compared to the behavior of Message Broker 6.1. In WMB 6.1, the subscription response contains all folders from the request. . When a negative reply message is sent to subscription request, a reply message is built with an RFH2 header containing the psc and pscr folders, and does not include the message data. This matches the documented behavior: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com. ibm.mq.amqnar.doc/ps23050_.htm . The response message is contained within the NameValueData field of the MQRFH2 header, in a <pscr> folder. . In the case of a warning or error, the response message contains the <psc> folder from the command message as well as the <pscr> folder. The message data, if any, is not contained in the queue manager response message. . What is not clear from this documentation is whether the message should also contain any other folders from the original request RFH2 header. At the moment MQ does not include them in the response message it builds, however Message Broker does include these folders. This difference in behavior is undesirable when migrating to MQ/MB v7 and since Message Broker is the reference for RFH2 behavior this APAR brings MQ inline with Message Broker.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere MQ Version 7 Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: When a queued pubsub command fails and a negative response message has been requested, the message is constructed containing only the psc folder containing the failing command, and the pscr folder containing the error response. Any other folders in the original request message's RFH2 header are not included in the response message.
Problem conclusion
The negative response message will now contain all folders from the original RFH2 header (including the psc folder), in addition to the pscr response folder. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.10 -------- -------------------- Windows 7.0.1.10 AIX 7.0.1.10 HP-UX (PA-RISC) 7.0.1.10 HP-UX (Itanium) 7.0.1.10 Solaris (SPARC) 7.0.1.10 Solaris (x86-64) 7.0.1.10 iSeries 7.0.1.10 Linux (x86) 7.0.1.10 Linux (x86-64) 7.0.1.10 Linux (zSeries) 7.0.1.10 Linux (Power) 7.0.1.10 v7.1 Platform Fix Pack 7.1.0.2 -------- -------------------- Windows 7.1.0.2 AIX 7.1.0.2 HP-UX (Itanium) 7.1.0.2 Solaris (SPARC) 7.1.0.2 Solaris (x86-64) 7.1.0.2 iSeries 7.1.0.2 Linux (x86) 7.1.0.2 Linux (x86-64) 7.1.0.2 Linux (zSeries) 7.1.0.2 Linux (Power) 7.1.0.2 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
Temporary fix
Comments
APAR Information
APAR number
IV14402
Reported component name
WMQ AIX V7
Reported component ID
5724H7221
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-31
Closed date
2012-07-09
Last modified date
2012-07-09
APAR is sysrouted FROM one or more of the following:
PM53766
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ AIX V7
Fixed component ID
5724H7221
Applicable component levels
R701 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023