IBM Support

IJ10803: With XMS .NET if the MQMD is corrupted a rollback puts the message back in the original queue not to the backout queue.

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

  • XMS .NET application should always send a poison message to the
    backout if the backout threshold limit is reached and backout
    queue is defined.
    
    But if the data length of a poison message is 0 then XMS fails
    to send the message to the backout queue.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    XMS.NET APPLICATIONS RECEIVEING A MSG WITH DATA LENGTH 0 AND
    MQMD.FORMAT IS SET TO MQRFH2
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    XMS .NET application should always send a poison message to the
    backout if the backout threshold limit is reached and backout
    queue is defined.
    
    But if the data length of a poison message is 0 then XMS fails
    to send the message to the backout queue. XMS rollsback the
    message to the queue which is incorrect behavior.
    

Problem conclusion

  • If backout threshold limit is reached and backout queue is
    defined XMS should always send the message to the backout queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.2
    
    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

    IJ10803

  • Reported component name

    IBM MQ XMS V9.1

  • Reported component ID

    5724H7277

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-26

  • Closed date

    2018-11-02

  • Last modified date

    2019-03-14

  • APAR is sysrouted FROM one or more of the following:

    IJ08636

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    IBM MQ XMS V9.1

  • Fixed component ID

    5724H7277

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":"910","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 March 2019