IBM Support

IT25365: MQINPUT NODE FAILS TO BACKOUT MESSAGE TO DLQ AFTER FIXPACK UPGRADE

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

  • After fix pack upgrade to 10.0.0.10 or higher, a user may
    encounter the following failure when a message flow tries to
    back out a failed MQ message of type MQMT_REPORT to the queue
    manager's dead letter queue:
    
    BIP2613E: Unable to backout a message; MQPUT to queue ' '
    failed: MQCC=2; MQRC=2252.
    
    This is similar to APAR IT24352 which addresses the same
    failure when backing out an MQ report message to a Backout
    Queue. But if there is no backout queue defined or if the MQPUT
    to the backout queue fails, the message flow will then try to
    back out the message to the dead letter queue where the same
    fix is needed.
    
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0.0.10 or higher and IBM
    App Connect Enterprise V11 using the MQInput node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    After fix pack upgrade to 10.0.0.10 or higher, a user may
    encounter the following failure when a message flow tries to
    back out a failed MQ message of type MQMT_REPORT to the Queue
    Manager's dead letter queue:
    
    BIP2613E: Unable to backout a message; MQPUT to queue ' '
    failed: MQCC=2; MQRC=2252. (MQRC_ORIGINAL_LENGTH_ERROR)
    
    This is similar to APAR IT24352 which addresses the same failure
    when backing out an MQ report message to a Backout Requeue
    Queue. But if there is no backout queue defined or if the MQPUT
    to the backout queue fails, the message flow will then try to
    back out the message to the dead letter queue where the same fix
    as IT24352 is needed.
    

Problem conclusion

  • The MQInput node no longer fails with mqrc 2252 when backing out
    a failed report message to the Queue Manager's dead letter
    queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.14
    v11.0      11.0.0.2
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25365

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-06-14

  • Closed date

    2018-09-19

  • Last modified date

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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

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

Document Information

Modified date:
19 September 2018