IBM Support

IT25942: When using isolated bindings xa_open fails with XAER_RMERR (0xFFFFFFFD / -3)

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

  • A Connection from an XA application in isolated bindings mode
    fails on xa_open with XAER_RMERR (0xFFFFFFFD / -3)
    
    An MQ trace of the application shows that the function
    "zisConnectToAgent" immediately returns MQRC_RESOURCE_ERROR
    without calling any further functions.
    

Local fix

  • 1. Change the binding type to SHARED bindings. To achieve this.,
    either remove the
     Connection:
       DefaultBindType=ISOLATED
    from qm.ini
    
    or set it to:
    Connection:
       DefaultBindType=SHARED
    
    
    2. Alternatively, alter the XA application to connect to the
    queue manager in client mode.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of IBM MQ XA programs who are using a
    transaction manager or configuration which issues the xa_open
    call before MQCONN, and are connecting in isolated bindings
    mode.
    
    This issue was initially observed when using IBM TXSeries in
    combination with MQ, but could also be encountered in other XA
    configurations.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When connecting to the queue manager in ISOLATED bindings mode,
    a validation check is made on an internal queue manager
    configuration attribute. However, the attribute being validated
    was only set properly during an MQCONN operation. If an xa_open
    call was received prior to MQCONN, the attribute validation
    failed.
    
    This caused the connection attempt to fail.  Internally a return
    code of MQRC_RESOURCE_ERROR can be observed if a trace is taken,
    but this is not returned to the application or through the XA
    interfaces.
    

Problem conclusion

  • The MQ ISOLATED bindings connection logic has been updated to
    ensure that the necessary internal attribute is correctly set
    during xa_open, prior to attempting to connect to the queue
    manager.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.6
    v9.1 CD    9.1.1
    v9.1 LTS   9.1.0.1
    
    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

    IT25942

  • 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

    2018-08-22

  • Closed date

    2018-08-24

  • Last modified date

    2018-08-24

  • 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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
24 August 2018