Fixes are available
APAR status
Closed as program error.
Error description
Using the RFHUtil tool, a message with an RFH2 header is sent to a queue with the persistence field set to 'not-persistent' in the MQMD. When this message is received using a WebSphere MQ (WMQ) v6 Java Message Service (JMS) Client, the JMSDeliveryMode field on the RFH2 header is set to 'not-persistent' When the same message is received using a WMQ v7 JMS Client, the JMSDeliveryMode field on the RFH2 is always set to 2 (Persistent), in spite of the Persistence field having been set to 'non-persistent' by the sender application.
Local fix
Use a WebSphere MQ v7+ JMS MessageProducer to send messages to the destination queue.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users who receive a message with an RFH2 header (whose persistence field on the MQMD alone has been set to not-persistent) using a WMQ v7 JMS application. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: When a message with an RFH2 header is received using a WMQ v7 JMS application, in case the JMSDeliveryMode field in the RFH2 has not been set by the sender application, the JMSDeliveryMode field at the receiving end will be set to the default value, which is 'Persistent'. This is different from the behaviour of the WMQ v6 JMS client in that the WMQ v6 JMS Client considers the value of Persistence on the MQMD when the JMSDeliveryMode has not been set by the sender application.
Problem conclusion
The WMQ v7 JMS client code has been changed to ensure that when only the MQMD persistence field is set by a sending application, the JMSDeliveryMode at the receiving application will be set to the value that has been set on the MQMD by the sender application, and not to the default value which is 2 (persistent). --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.3 -------- -------------------- Windows tbc_p700_0_1_3 AIX tbc_p700_0_1_3 HP-UX (PA-RISC) tbc_p700_0_1_3 HP-UX (Itanium) tbc_p700_0_1_3 Solaris (SPARC) tbc_p700_0_1_3 Solaris (x86-64) tbc_p700_0_1_3 iSeries tbc_p700_0_1_3 Linux (x86) tbc_p700_0_1_3 Linux (x86-64) tbc_p700_0_1_3 Linux (zSeries) tbc_p700_0_1_3 Linux (Power) tbc_p700_0_1_3 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
IC67026
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-09
Closed date
2010-03-27
Last modified date
2010-03-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R700 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","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023