IC75039: WEBSPHERE MQ V7 CLIENT APPLICATION CALLING MQCONNX IN AN API EXIT FAILS WITH REASON CODE 2012 (MQRC_ENVIRONMENT_ERROR)

WebSphere MQ V7.0 Fix Pack 7.0.1.6
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.6

APAR status

• Closed as program error.

Error description

• Inside a user-written API exit, a call to MQCONNX is made, to
  obtain the HConn for the existing connection.
  
  The call to the API exit is being made within the SVRCONN
  channel thread, serving the client application.
  
  The MQCONNX call returns with Reason Code 2012,
  MQRC_ENVIRONMENT_ERROR.
  
  Trace on the server shows:
  
  ----------{  zutCallApiExitsAfterPut
  -----------{  APIExit
  ApiExit->Name:exitname ExitReason:2, Function:9
  .
  .
  ---------------}! zstMQConnect (rc=MQRC_ENVIRONMENT_ERROR)
  --------------}! zstMQCONNX (rc=MQRC_ENVIRONMENT_ERROR)
  -------------}! trmzstMQCONNX (rc=MQRC_ENVIRONMENT_ERROR)
  ------------}! MQCONNX (rc=MQRC_ENVIRONMENT_ERROR)
  
  The MQCNO contains:
  MQCNO.Options          = 0
  
  The actual outcome of this MQCONNX call was:
  CompCode = MQCC_FAILED
  Reason   = MQRC_ENVIRONMENT_ERROR  (rc=000007DC / 2012)
  
  The expected outcome of this MQCONNX is:
  CompCode = MQCC_WARNING
  Reason   = MQRC_ALREADY_CONNECTED (rc=000007D2 / 2002)
  HConn    = (the HConn in use by the SVRCONN channel)
  
  The MQCONNX in the user-written API exit works for server or
  locally connected applications, but fails for client
  applications.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users writing or running API exits for WebSphere MQ, intending
  these to be used in SVRCONN channels serving client programs.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows)
  ****************************************************************
  PROBLEM SUMMARY:
  Incorrect checks were being performed during the MQCONNX call,
  leading to the observed failure.
  
  The expectations of users in this scenario is that the MQCONNX
  call should complete with Reason Code MQRC_ALREADY_CONNECTED and
  the HConn returned is for the connection in use by the running
  SVRCONN channel.
  

Problem conclusion

• The incorrect checks have been removed, and an MQCONNX call that
  specifies no MQCNO_HANDLE_SHARE_* options will now complete with
  Reason Code MQRC_ALREADY_CONNECTED, also returning the HConn in
  use by the SVRCONN channel.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.6
  --------           --------------------
  Windows            U200328
  AIX                U840698
  HP-UX (PA-RISC)    U841555
  HP-UX (Itanium)    U841560
  Solaris (SPARC)    U841556
  Solaris (x86-64)   U841562
  iSeries            tbc_p700_0_1_6
  Linux (x86)        U841557
  Linux (x86-64)     U841561
  Linux (zSeries)    U841558
  Linux (Power)      U841559
  
  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 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 WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R700 PSY

     UP