IBM Support

IT05827: IBM MQ V8 COA REPORT MESSAGE DESTINED TO A REMOTE QUEUE ENDS UP IN DLQ WITH MQRC_MDE_ERROR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When sending messages having RFH2 and the Confirm on Arrival
    (COA) destination specified to a remote queue, the COA message
    ends up on the DLQ. The sender client application is on a remote
    machine and the RFH2 message is sent to a remote queue manager
    which in turn sends the COA message to a remote queue on another
    remote queue manager. The COA message shows up on the Dead
    Letter Queue of the remote queue manager with MQRC_MDE_ERROR.
    

Local fix

  • COA messages destined for a local queue works.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ V8 who use the Confirm On Arrival report message
    feature.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a message containing an RFH2 is specified with COA whose
    destination is set to a remote queue, the COA message is
    incorrectly built by the queue manager. This causes the COA
    message to be delivered to the Dead Letter Queue with
    MQRC_MDE_ERROR.
    The sender application sends the RFH2 message to a remote queue
    and this message has its COA destination set to another remote
    queue. The COA is then sent to the remote queue and while doing
    this, the queue manager incorrectly builds the COA message with
    the wrong format and thus causes the COA message to end up in
    the remote queue manager's Dead Letter Queue.
    The problem is not seen if the destination of the COA message is
    set to a local queue.
    

Problem conclusion

  • The queue manager code is modified so that the COA message is
    built correctly, meaning that the message can be delivered to
    the respective remote queue successfully.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.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

    IT05827

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-12-01

  • Closed date

    2015-02-12

  • Last modified date

    2016-01-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 BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP

[{"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:
27 January 2016