IBM Support

PH67852: MQ REASON CODE 2018 (MQRC_HCONN_ERROR) RETURNED ON AN MQCONNX CALL

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere Application Server for z/OS is configured to connect
    to a queue manager (via the IBM MQ 9.3.0.20 resource adapter)
    using the BINDINGS transport. It returns a RC2018
    (MQRC_HCONN_ERROR) on an MQCONNX call into the native method
    lpiSPISetContext . This started happening only after moving to
    MQ V9.4 edition.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 4 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Attempts to connect to a queue manager  *
    *                      from an application server using the MQ *
    *                      resource adapter can fail due to        *
    *                      Exception:                              *
    *                      "MQJCA1011: Failed to allocate a JMS    *
    *                       connection., error code:               *
    *                       MQJCA1011 An internal error caused an  *
    *                       attempt to allocate a connection to    *
    *                       fail."                                 *
    *                                                              *
    *                      Trace and/or linked exceptions          *
    *                      show the failure is due to an           *
    *                      unexpected MQRC_HCONN_ERROR (MQRC2018). *
    ****************************************************************
    When MQCONNX is issued from the WAS or WMB adapter, and the TCB
    is already connected to the queue manager,
    MQRC_ALREADY_CONNECTED (MQRC 2002) is returned to the issuer,
    however the adapter fails to update the hConn parameter with
    details of the existing connection handle. Subsequent attempts
    to use the returned connection handle will fail with
    MQRC_HCONN_ERROR (MQRC2018).
    
    When the MQCONNX was part of an MQI call issued by the MQ
    Resource Adapter (e.g. in WSAS or Liberty), the unexpected
    MQRC_HCONN_ERROR cause the reported exceptions to be thrown and
    the connection to fail.
    

Problem conclusion

  • The affected MQ adapters are updated to correctly return the
    hConn value when the TCB is already connected to the queue
    manager.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH67852

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-08-21

  • Closed date

    2025-08-28

  • Last modified date

    2025-10-02

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

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

    UO04680

Modules/Macros

  • CSQBASTB CSQBWSTB
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R400 PSY UO04680

       UP25/09/13 P F509

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":"BU048","label":"IBM Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"400","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
02 October 2025