IBM Support

PI49236: A TUXEDO MQ XA CLIENT CAUSES AN ABEND 5C6-00D4007D.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An Oracle Tuxedo MQ client connects to MQ on z/OS via client
    connections and receives an ABEND5C6 reason code 00D4007D.
    
    CSQY291E CSQWDSDM SDUMPX FAILED, RC=00000B08,xxxx,
             ABN=5C6-00D4007D,LOC=CSQMLPLM.CSQMXARH+xxxxxxxx
    CSQY291E CSQXDMPS SDUMPX FAILED, RC=00000B08,xxxx,
             ABN= 5C6-00E7014F,LOC=CSQXADPM.CSQXADPM+xxxxx
    CSQX209E CSQ1 CSQXRESP Connection unexpectedly terminated
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using Oracle Tuxedo as an external *
    *                      transaction manager, connecting to MQ   *
    *                      z/OS over an XA client connection,      *
    *                      XA_PREPARE requests may fail with abend *
    *                      5C6-00D4007D.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An MQ client application is running under the control of an
    external transaction manager which uses XA calls to perform
    transaction coordination.
    
    The application connects to MQ on z/OS and performs some
    in-syncpoint work. To register the work as part of an XA
    transaction, the transaction manager makes XA_START and XA_END
    calls on the application's connection to MQ.
    
    When the application requests that the transaction manager
    completes the transaction, the transaction manager may decide to
    use a different MQ connection to make the XA_PREPARE call.
    
    In these circumstances, MQ z/OS is not able to perform the
    necessary processing to prepare the XA transaction. The chinit
    task for the connection is abended 5C6-00D4007D, and the client
    receives return code -3 (XAER_RMERR).
    

Problem conclusion

  • This APAR provides changes to XA client connections on z/OS
    which allow the transaction manager to prepare a transaction on
    a different connection.
    The change is not enabled by default. To make use of the change
    it must be explicitly enabled on the svrconn definition used
    by the XA client.
    
    This APAR also includes fixes for the issues reported in
    PI56679 and PI68962.
    
    Documentation changes for V800 Knowledge Center:
    A new Knowledge Center page will be added as a sub-topic of:
    WebSphere MQ
     > Configuring
       > Configuring connections between the server and client
         > Configuring an extended transactional client
    
    https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm
    .mq.con.doc/q016530_.htm
    
    Title: MQ z/OS considerations for extended transactional
           client connections
    
    Some XA transaction managers use sequences of transaction
    coordination calls which are incompatible with the features
    normally available to clients connecting to MQ on z/OS.
    
    Where an incompatible sequence is detected, MQ on z/OS may
    issue an abend for the connection and return an error response
    to the client.
    e.g.
    xa_prepare receives abend 5C6-00D4007D, with return code -3
    (XAER_RMERR) returned to the client.
    For transaction managers which encounter this situation, the
    following actions should be taken to allow the transaction
    manager to interact with MQ on z/OS:
     - Apply the fix for APAR PI49236.
     - Enable the change provided by PI49236 for the SVRCONN
       channel used by the transaction manager.
       The change is enabled by specifying the keyword
       CSQSERVICE1 (in upper case) anywhere in the description
       field of the SVRCONN channel.
    
    Channels with the CSQSERVICE1 keyword have the following
    restrictions:
    
     - GROUP unit of recovery disposition is not permitted.
       Only QMGR unit of recovery disposition is allowed.
       An xa_open call specifying the QSG name in the xa_info
       parameter will fail with xaer_inval.
    
     - The MQGMO_LOCK and MQGMO_UNLOCK options are not permitted.
       An MQGET call with MQGMO_LOCK or MQGMO_UNLOCK will fail
       with MQRC_ENVIRONMENT_ERROR.
    000Y
    CMQXRSRV
    CSQMCALH
    CSQMCLMT
    CSQMCPRH
    CSQMDALL
    CSQMDCOH
    CSQMGETV
    CSQMXARH
    CSQMXCLN
    CSQXADPM
    CSQ7CBMC
    

Temporary fix

Comments

  • ×**** PE17/11/23 FIX IN ERROR. SEE APAR PI90533  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI49236

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-09-23

  • Closed date

    2017-05-09

  • Last modified date

    2017-11-30

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

    PI36807

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

    PI73140 UI47093

Modules/Macros

  • CMQXRSRV CSQMCALH CSQMCLMT CSQMCPRH CSQMDALL CSQMDCOH CSQMGETV
    CSQMXARH CSQMXCLN CSQXADPM CSQ7CBMC
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI47093

       UP17/06/06 P F706

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 November 2017