IBM Support

IV22043: Following restart of a crashed queue manager, a queue may be reported as damaged.


You can track all active APARs for this component.


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
    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

  • ****************************************************************
    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)
    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
    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:
    Platform           Fix Pack
    --------           --------------------
    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
    Platform           Fix Pack
    --------           --------------------
    Windows            U200352
    AIX                U853055
    HP-UX (PA-RISC)    U853082
    HP-UX (Itanium)    U853087
    Solaris (SPARC)    U853083
    Solaris (x86-64)   U853089
    Linux (x86)        U853084
    Linux (x86-64)     U853088
    Linux (zSeries)    U853085
    Linux (Power)      U853086
    Platform           Fix Pack
    --------           --------------------
    HP-UX (Itanium)
    Solaris (SPARC)
    Solaris (x86-64)
    Linux (x86)
    Linux (x86-64)
    Linux (zSeries)
    Linux (Power)
    Platform           v7.5
    --------           --------------------
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'

Temporary fix


APAR Information

  • APAR number


  • Reported component name

    WMQ LIN X86 V6

  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention


  • Submitted date


  • Closed date


  • Last modified date


  • 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


Applicable component levels

  • R602 PSY


[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ5M","label":"APAR"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
19 September 2012