PH41602: WEBSPHERE APPLICATION SERVER BINDINGS CONNECT MQRC 2009

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Users running MQ 9.2 for z/OS report that an activation
  specification fails with MQRC 2009 after it had previously been
  connected to MQ (z/OS) via BINDINGS mode. This follows an
  MQDISC then subsequent MQCONNX failing. Additional errors
  include :  JSCMQ0001: IBM MQ call failed with compcode '2'
  ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN'). MQ
  Development finds this is during an attempt to reuse an invalid
  RRS context when a specific QSG name is specified for
  connectivity.
  *
  Additional keywords and symptoms:
  .
  CWSJY0003W: JMSCC3036: An exception has been delivered to the
  connection's exception listener: '
    Message :
    com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ1107: A
    problem with this connection has occurred.
          ...
    Caused by [1] --> Message : com.ibm.mq.MQException:
    JMSCMQ0001: IBM MQ call failed with compcode '2'
    ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').
  .
  MQJCA1011: Failed to allocate a JMS connection.
    ...
    Caused by: com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call
    failed with compcode '2' ('MQCC_FAILED') reason '2351'
    ('MQRC_GLOBAL_UOW_CONFLICT').
  .
  2009 MQRC_CONNECTION_BROKEN
  2351 MQRC_GLOBAL_UOW_CONFLICT
  

Local fix

• It is feasible to connect to a specific qmgr that would avoid
  the issue until implementation of the permanent fix.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
  *                 Release 2 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a WebSphere Application Server     *
  *                      application uses an activation          *
  *                      specification, with authentication, to  *
  *                      monitor an MQ queue in a QSG, if the    *
  *                      QSG name is used for the binding        *
  *                      connection name rather than a qmgr      *
  *                      name, RC=2009 'MQRC_CONNECTION_BROKEN'  *
  *                      may be seen on redeployment or          *
  *                      activation specification restart.       *
  ****************************************************************
  To optimise connection authentication processing, adapter stub
  code checks if there is an existing connection to the qmgr.
  When the QSG name is used for the connection the stub code can't
  detect the connection. CSQBCON processing has to be repeated,
  including authentication, reusing the bloa from the existing
  qmgr connection. There may be invalid residual data in the
  qrpl used for the ExpressInterest call in CSQMCPRH, leading to
  'CTX_CONTEXT_TOKEN_INV' and hence 'MQRC_CONNECTION_BROKEN'.
  
  As a workaround the activation specification can be set to bind
  with a named qmgr instead of the QSG name.
  

Problem conclusion

• CSQBCON has been corrected so as not to use residual qrpl data
  and tracing has been improved in CSQMCPRH.
  

Temporary fix

Comments

APAR Information

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

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

  UI79326

Modules/Macros

• CSQBCON  CSQMCPRH
  

Fix information

• Fixed component name

  IBM MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R200 PSY UI79326

     UP22/03/11 P F203

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.