Fixes are available
WebSphere MQ V7.5 Fix Pack 7.5.0.3
WebSphere MQ V7.0 Fix Pack 7.0.1.12
Fix Pack 7.1.0.5 for WebSphere MQ V7.1
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
WebSphere MQ Java PCF messages ecapsulated within an XMIT message which do not use MQGMO_CONVERT generate a 3013 MQRCCF_STRUCTURE_TYPE_ERROR when browsed. . An example of the exception reported is: . MQJE001: Completion Code '2', Reason '3013'. java.lang.RuntimeException: com.ibm.mq.headers.MQDataException: MQJE001: Completion Code '2', Reason '3013'. ??? at com.ibm.mq.headers.MQHeaderIterator.nextHeader (MQHeaderIterator.java:289) ??? at abc.testapps.XQHTester.getHeaders(XQHTester.java:45) ??? at abc.testapps.XQHTester.main(XQHTester.java:23) Caused by: com.ibm.mq.headers.MQDataException: MQJE001: Completion Code '2', Reason '3013'.
Local fix
Explicitly set the MQMD.encoding flag to ensure the default of MQENC_NATIVE is used. For example: MQMessage msg = new MQMessage(); msg.encoding = MQC.MQENC_INTEGER_REVERSED;
Problem summary
**************************************************************** USERS AFFECTED: This issue effects the WebSphere MQ classes for Java client that is receiving messages that contain more than one MQMD header. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java +Java zOS **************************************************************** PROBLEM SUMMARY: When an application made use of the WebSphere MQ classes for Java to inspect the Headers of an MQMessage using the class: com.ibm.mq.headers.MQHeaderIterator the following exception was seen: com.ibm.mq.headers.MQDataException: MQJE001: Completion Code '2', Reason '3013' The cause of this exception was that the MQMessage contained multiple MQMD headers, for example because the message being iterated over was a XMIT message, which contained two MQMD structures, one for the message and one for the wrapped message being transmitted, and the WebSphere MQ classes for Java used the wrong MQMD to determine how the rest of the message was encoded. When a message encoding flag contained within the first MQMD is different to that of the second MQMD, then it is the second encoding value from the MQMD for the XMIT header which describes the encoding of the following headers and message data. The exception associated with this APAR occurred because the WebSphere MQ classes for Java were incorrectly using the encoding value recorded in the first MQMD, to determine how to decode the bytes for the PCF headers which followed the second MQMD in the message. If the encoding values differed between the MQMDs, then the PCF headers would be incorrectly decoded, resulting in a MQRC 3013 'MQRCCF_STRUCTURE_TYPE_ERROR' exception being thrown.
Problem conclusion
This APAR solves the issue by making sure that the correct encoding is used when more than one MQMD is present in an MQ Message. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.12 v7.1 7.1.0.5 v7.5 7.5.0.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
IC93960
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-07-08
Closed date
2013-08-30
Last modified date
2013-08-30
APAR is sysrouted FROM one or more of the following:
IC93950
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
R701 PSY
UP
Document Information
Modified date:
28 April 2022