IBM Support

IT26699: AMQ9544 error message is incorrectly reported in a scenario where AMQ9527 should be reported

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

  • Consider a scenario where requester/receiver/cluster receiver
    channel that has asked for a batch of messages, but a local
    target queue is full, lets assume we don't have DLQ's defined at
    either end. As we can't DLQ at the requester end, we reject the
    batch and the sender/server then states it also can't DLQ and
    sends us the ESH with rfpERR_CAN_NOT_STORE. In this scenario
    rrcI_MSGS_PUT_TO_REMOTE_DLQ(AMQ9544) is reported when the
    partner has sent an ESH of rfpERR_CAN_NOT_STORE instead of
    reporting rrcE_MSG_NOT_RECEIVED(AMQ9527).  Reporting
    rrcI_MSGS_PUT_TO_REMOTE_DLQ when the partner has sent an ESH of
    rfpERR_CAN_NOT_STORE is incorrect as it means that the partner
    MCA has encountered one of
    
    rrcE_MQOPEN_FAILED
    rrcE_MQPUT_FAILED
    rrcE_NO_DLQ
    
    None of these could indicate a successful remote DLQ operation.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All MQ users
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A programming error resulted in incorrectly reporting AMQ9544
    error message in the scenario where AMQ9527 should be reported.
    

Problem conclusion

  • The MQ code has been modified to make an ESH containing
    rfpERR_CAN_NOT_STORE always issue rrcE_MSG_NOT_RECEIVED
    (AMQ9527) instead of reporting
    rrcI_MSGS_PUT_TO_REMOTE_DLQ(AMQ9544) for receivers, requesters
    and cluster receivers.
    
    ---------------------------------------------------------------
    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.7
    v9.1 CD    9.1.2
    v9.1 LTS   9.1.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

    IT26699

  • 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-10-22

  • Closed date

    2019-03-21

  • Last modified date

    2019-03-21

  • 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:
21 March 2019