IC76746: AN FDC WITH PROBE ID MC050011 IS GENERATED WHEN REBOOTING PASSIVE NODE IN MSCS CLUSTER.

WebSphere MQ v7.0.1.7 Hypervisor for AIX
WebSphere MQ V7.0 Fix Pack 7.0.1.7
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.7

APAR status

• Closed as program error.

Error description

• After taking all WebSphere MQ v7 Queue Manager resources
  offline and rebooting the active node in the MSCS cluster, the
  cluster group resources are failed over to the passive node.
  The Queue Manager resource remains offline as expected, however
  an FDC is produced on the node that has been rebooted.
  The FDC generated is as follows:
  Probe Id          :- MC001002
  component         :- MQMOpen
  Process Name      :- C:\Windows\SysWOW64\rhs.exe
  Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
  Probe Description :- AMQ6119: An internal WebSphere MQ error
  has occurred
  (***CMQMException Caught***: Unable to open Parameters key.
  Error: 70)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users who have WebSphere MQ configured in MSCS environment.
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM SUMMARY:
  The MSCS process rhs.exe started by the cluster service tries to
  initialize the queue manager resource by invoking the MQ
  callback function MQMOpen. The MQMOpen routine in turn calls the
  cluster API ClusterRegCreateKey to open the Parameters registry
  key for the queue manager resource and this call fails with the
  windows error 70 (ERROR_SHARING_PAUSED). The FDC with the
  ProbeID MC001002 is generated to report this error.
  

Problem conclusion

• Upon discussing this issue with Microsoft it was concluded that
  the error is getting reported due to the incorrect invocation
  of the cluster API ClusterRegCreateKey in the Open routine. The
  correct usage is documented in the below msdn article.
  http://msdn.microsoft.com/en-us/library/aa368990(v=vs.85).aspx
  
  Do not call ClusterRegCreateKey from the following resource DLL
  entry point functions:
  Close
  Offline
  Online
  Open
  Terminate
  ClusterRegCreateKey can be safely called from any other
  resource DLL entry point function or from a worker thread. For
  more information, see Function Calls to Avoid in Resource DLLs.
  
  The MQMOpen routine has been modified to invoke
  ClusterRegOpenKey instead of ClusterRegCreateKey.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.7
  --------           --------------------
  Windows            U200333
  
  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

• R701 PSY

     UP