IBM Support

IT04808: A COBOL PROGRAM THAT EXECUTES A PROGRAM USING XA FAILS OR APPLICATION FAILS WITH SIGSEGV IN XTRESTABLISHTRACESTATUS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Applications likely to fail with one of the following errors.
    
    * COBOL programs cannot be used for external coordination by an
       XA-compliant application. The COBOL program fails with reason
    code
       2018 (MQRC_HCONN_ERROR) during MQOPEN.
    
    * Application fails with SIGSEGV in xtrEstablishTraceStatus
      with xtrEstablishTraceStatus and xtr_FNC_entry at the top
      of the stack.
    
      Stack trace examples:
    
      xtrEstablishTraceStatus
      xtr_FNC_entry
      ...
    
      xtrEstablishTraceStatus
      xtr_FNC_entry
      xcsGetIniFilename
      xcsGetQMDetailsEx
      zswChooseInstallation
      zswGetEntryPointsByName
      zswMQCONN_Call
      main
    
      xtrEstablishTraceStatus
      xtr_FNC_entry
      xihCSThreadClear
      xcsCreateSharedThread
      xcsInitializeEx
      zstInitCS
      zstMQConnect
      zstMQCONNX
      MQCONNX_Server_Call
      zswGetEntryPointsByName
      zswMQCONNX_Call
      ...
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ with extended transaction XA clients in a
    TXSeries/CICS COBOL environment or users of single or
    multi-threaded MQ applications connecting to the queue manager.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    CICS COBOL applications using MQ API return error 2018
    (MQRC_HCONN_ERROR) during MQOPEN API when attempting to connect
    to a queue manager using the client bindings libraries
    (libmqcxa.a and libmqcxa64.a). This problem is not seen when
    using CICS C client applications.
    
    The SIGSEGV in xtrEstablishTraceStatus occurred because MQ trace
    setting was not initialized
    correctly during MQCONN.
    

Problem conclusion

  • The MQ libraries have been updated to allow COBOL applications
    to use the extended transaction client interface within
    TXSeries/CICS and to fix the SIGSEGV problem in
    xtrEstablishTraceStatus.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.5
    v8.0       8.0.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

    IT04808

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-10-08

  • Closed date

    2014-11-06

  • Last modified date

    2015-03-06

  • 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

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]

Document Information

Modified date:
24 September 2021