Fixes are available
WebSphere MQ V6.0 Fix Pack 6.0.2.12
WebSphere MQ V6.0 for iSeries Fix Pack 6.0.2.12
WebSphere MQ V7.5 Fix Pack 7.5.0.1
WebSphere MQ V7.0 Fix Pack 7.0.1.10
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.10
Fix Pack 7.1.0.3 for WebSphere MQ V7.1
WebSphere MQ 6.0 for HP OpenVMS Alpha and Itanium - Fix Pack 6.0.2.12
APAR status
Closed as program error.
Error description
If a queue manager ends other than in the normal way via endmqm (e.g. due to a sudden machine reboot), then recovery actions by the queue manager on restart may result in a damaged queue. The queue is at risk of becoming damaged in that circumstance, if it is used with a mixture of persistent and non-persistent messages. This problem may be more prevalent for transmit queues, which can often hold both persistent and non-persistent messages. It is also possible that the problem could manifest as the reappearance of previously got persistent messages on the queue, rather than the queue being reported as damaged. There is only a very small possibility of encountering this problem, due to a number of factors needing to co-exist for it to occur. The typical damaged queue resulting from this problem will be of size 1712 bytes, or more likely, 10240 bytes. Examination of the q file (by IBM Service) would reveal a non-null head of message chain, but no message.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: You may encounter this issue if you do not always end the queue manager gracefully, via endmqm. In addition, to encounter the problem you must also be using some queues with a mixture of persistent and non-persistent messages. Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: This problem requires the following sequence of operations to occur (some are user driven, and some are driven by the queue manager itself): Put some persistent messages to a queue. Flush the persistent messages to disk, other than by a checkpoint. That can happen when setting queue attributes. Get all of the persistent messages. Initiate a checkpoint. After initiating the checkpoint, but before the queue itself is checkpointed, put a non-persistent message. That sets up a possibility that the queue checkpoint will fail to flush a null head of message chain, and it may also truncate the queue to below the q file message area. It is important to flush a null head because all the persistent messages have been got and we had previously flushed the persistent messages to disk. If the queue manager is hard-crashed immediately after the checkpoint, then on queue manager restart the queue file may contain persistent messages that had previously all been got. Or, if the queue checkpoint operation before the queue manager crash truncated the queue, then the queue will be reported as damaged on attempting to access it.
Problem conclusion
The queue checkpoint logic was revised to correctly handle the problem situation described. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v6.0 Platform Fix Pack 6.0.2.12 -------- -------------------- Windows U200331 AIX U842074 HP-UX (PA-RISC) U842208 HP-UX (Itanium) U842213 Solaris (SPARC) U842209 Solaris (x86-64) U842216 iSeries tbc_p600_0_2_12 Linux (x86) U842210 Linux (x86-64) U842215 Linux (zSeries) U842211 Linux (Power) U842212 Linux (s390x) U842214 v7.0 Platform Fix Pack 7.0.1.10 -------- -------------------- Windows U200352 AIX U853055 HP-UX (PA-RISC) U853082 HP-UX (Itanium) U853087 Solaris (SPARC) U853083 Solaris (x86-64) U853089 iSeries 7.0.1.10 Linux (x86) U853084 Linux (x86-64) U853088 Linux (zSeries) U853085 Linux (Power) U853086 v7.1 Platform Fix Pack 7.1.0.3 -------- -------------------- Windows 7.1.0.3 AIX 7.1.0.3 HP-UX (Itanium) 7.1.0.3 Solaris (SPARC) 7.1.0.3 Solaris (x86-64) 7.1.0.3 iSeries 7.1.0.3 Linux (x86) 7.1.0.3 Linux (x86-64) 7.1.0.3 Linux (zSeries) 7.1.0.3 Linux (Power) 7.1.0.3 Platform v7.5 -------- -------------------- Multiplatforms 7.5.0.1 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
IV22043
Reported component name
WMQ LIN X86 V6
Reported component ID
5724H7204
Reported release
602
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-06-01
Closed date
2012-09-19
Last modified date
2012-09-19
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 LIN X86 V6
Fixed component ID
5724H7204
Applicable component levels
R602 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023