IBM Support

IT31428: MQ control program dspmqtrn -e can incorrectly output some internally-created XA transactions

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

  • The dspmqtrn command, when used with the -e switch, can display
    XA transactions that were created by the local queue manager,
    and are in PREPARED state at that moment.
    
    This output is wrong, because the intended design of dspmqtrn -e
    is that it should only output XA transactions that were created
    by an external transaction manager (TM).
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who are concerned about the correctness of the dspmqtrn
    output, at a specific point in time.  However, be aware that, in
    normal running, a queue manager's transactions will be
    constantly changing state, and so it is rare to need to rely on
    the output at any specific time.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The dspmqtrn -e command requests a list of transactions from the
    queue manager.  According to the product design, only XA
    transactions that were not created by the local queue manager
    should be output.
    
    This search condition (only transactions created externally) was
    not being transferred from the dspmqtrn program to the layers of
    MQ code performing the search, so the unwanted transactions were
    returned in the list.
    

Problem conclusion

  • The MQ code has been corrected so that this search condition
    (only transactions created externally) is now transferred from
    the dspmqtrn program to the layers of MQ code performing the
    search.
    
    Therefore, the unwanted transactions are now not returned in the
    list.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.11
    v9.1 LTS   9.1.0.6
    v9.x CD    TBC.
    
    
    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

    IT31428

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-01-07

  • Closed date

    2020-06-17

  • Last modified date

    2020-06-22

  • 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 M/P

  • Fixed component ID

    5724H7261

Applicable component levels

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

Document Information

Modified date:
23 June 2020