IBM Support

IT23705: Asynchronous MQGET failing with MQRC_TRUNCATED_MSG_FAILED error updates the queue statistics incorrectly

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • During an asynchronous MQGET when MQRC_TRUNCATED_MSG_FAILED
    error is encountered , the GetCount of queue is incremented even
    though the message was not dequeued.
    
    If the MQGET of the truncated message which failed initially is
    retried by the application with increased buffer, the GetCount
    on the queue is incremented again. So GetCount on the queue is
    incremented twice for the same message.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All MQ users using asynchronous get can be affected. This
    includes users of JMS and XMS where asynchronous consume may be
    used by the underlying MQ API calls.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the MQRC_TRUNCATED_MSG_FAILED condition occurred during an
    asynchronous consume operation, the failure condition was not
    considered when updating the queue statistics.
    

Problem conclusion

  • The MQ queue manager statistics and accounting logic has been
    corrected so that asynchronous consume operations which fail
    with MQRC_TRUNCATED_MSG_FAILED do not update the GetCount for
    the queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.12
    v9.0 LTS   9.0.0.6
    
    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

    IT23705

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-11

  • Closed date

    2019-01-03

  • Last modified date

    2019-01-03

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7251

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 January 2019