IBM Support

IT42810: Many ZM013000 ztmTidyUpXASessions trcE_UNEXPECTED_RM_ERROR FDCs from MQ code in application

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

  • Failure data capture (FDC) records in /var/mqm/errors with the
    following contents were seen.  They are reporting that, when MQ
    called the xa_close API within a database client library, this
    library reported a return code of -7, which is XAER_RMFAIL.
    This return code generally means that the client lost contact
    with its server, either for planned or unplanned reasons.  MQ
    was calling xa_close to achieve the disconnected state, R0, so
    this is not in fact a reportable condition, and just consumes
    disk space for no benefit.
    
    Probe Id :- ZM013000
    Component :- ztmTidyUpXASessions
    Program Name :- java
    Major Errorcode :- trcE_UNEXPECTED_RM_ERROR
    Probe Description :- AMQ7605E: The XA resource manager DBAPRD
    has returned an unexpected return code -7, when called for
    xa_close.
    
    MQM Function Stack
    MQDISC
    zstMQDISC
    ztmTidyUpXASessions
    xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of XA by using the MQBEGIN API call, where the database
    client layer in the application disconnects or loses contact
    with the database server before the MQDISC API is called.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The FDC is not needed in this specific scenario, and consumes
    disk space without benefit.
    
    In other failure scenarios this FDC probe will continue
    correctly to be written out, but not in the XAER_RMFAIL
    scenario.
    

Problem conclusion

  • The MQ code has been corrected so that this FDC is not written
    in this specific scenario where it is unneeded.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.15
    v9.2 LTS   9.2.0.10
    v9.3 LTS   9.3.0.5
    v9.x CD    9.3.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

    IT42810

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-01-02

  • Closed date

    2023-02-22

  • Last modified date

    2023-02-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 MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 February 2023