IT37148: FDCs with probe identifiers RM632001/RM632002 are generated while running an IBM MQ C client application

APAR status

• Closed as program error.

Error description

• Client applications connecting to a queue manager and
  registering a callback may cause failure data capture (FDC)
  records to be generated and
  MQRC_HCONN_ERROR is returned to the application.
  
  Two FDC records will be written as follows:
  
  IBM MQ First Failure Symptom Report
  
  Probe Id          :- RM632001
  Component         :- reqGetConn
  Major Errorcode   :- MQRC_HCONN_ERROR
  Minor Errorcode   :- OK
  Probe Type        :- INCORROUT
  Probe Severity    :- 4
  Probe Description :- AMQ6125E: An internal IBM MQ error has
  occurred.
  FDCSequenceNumber :- 0
  Arith1            :- 3 (0x3)
  
  
  IBM MQ First Failure Symptom Report
  
   Probe Id          :- RM632002
  Component         :- reqGetConn
  Major Errorcode   :- OK
  Minor Errorcode   :- OK
  Probe Type        :- INCORROUT
  Probe Severity    :- 4
  Probe Description :- AMQ6125E: An internal IBM MQ error has
  occurred.
  FDCSequenceNumber :- 1
  Comment1          :- FFST generated by
  xcsImpersonateThreadAndFFST
  

Local fix

• Delay the call to MQCLOSE on the main thread to give the
  MQCTL(SUSPEND) call a chance to complete.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users with IBM MQ C client applications which use the
  asynchronous consume feature may be affected by this issue.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  MQCLOSE was called from the main thread of an application that
  uses asynchronous consume and MQCTL(SUSPEND) was running in
  parallel on the asynchronous consume callback thread.  Both
  threads attempted to take ownership of the connection and this
  caused an error.
  

Problem conclusion

• The IBM MQ C client code has been corrected to prevent both the
  MQCLOSE and MQCTL(SUSPEND) API calls from attempting to take
  ownership of the connection at the same time.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.12
  v9.2 LTS   9.2.0.7
  v9.3 LTS   9.3.0.1
  v9.x CD    9.3.1
  
  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

  IBM MQ BASE MP

• Fixed component ID

  5724H7271

Applicable component levels