IT32673: MSCS Cluster log reports error 126 MQ DLL not found, but the correct error is Resource Name is unknown

APAR status

• Closed as program error.

Error description

• The cluster log reports that an MQ DLL file was not found in a
  case where the correct error would be that the Resource Name is
  unknown.
  
  In the cluster log an error like this is seen:
  
  [RHS] s_RhsRpcCreateResType: (126) because of Error loading
  resource DLL C:\IBMMQInstallationDir\bin64\amqmclrn.dll
  
  When the user checked on disk, the MQ DLL file amqmclrn.dll did
  exist.  The error message was incorrect, and led to the wrong
  investigation being performed by the system administrator.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users beginning the first use of MQ with Microsoft Failover
  Clustering on a given installation.
  
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The MQ DLL amqmclrn.dll containing the Startup routine is loaded
  and run within the Cluster Service on the Windows platform.
  MQ's Startup routine was returning the wrong error code when the
  name of the resource type was not equal to "IBM MQSeries MSCS".
  
  The user dumped the cluster log using the command
  "get-clusterlog -destination C:\temp" in PowerShell.
  
  The error being returned by the MQ code from its Startup routine
  was ERROR_MOD_NOT_FOUND, 126.
  
  This error code 126 means that the MQ DLL amqmclrn.dll does not
  exist on the system, but in fact it did exist.
  
  According to the example provided for the Startup routine by
  Microsoft, the correct error code in this case (incorrect
  resource type passed into the routine) should have been:
  ERROR_CLUSTER_RESNAME_NOT_FOUND, 5080.
  

Problem conclusion

• The MQ Startup routine has been changed so that the correct
  error code (ERROR_CLUSTER_RESNAME_NOT_FOUND, 5080) is returned
  by the MQ Startup routine in amqmclrn.dll in this scenario where
  a resource type name other than "IBM MQSeries MSCS" is passed by
  the caller.
  
  Any error text that is now logged in the cluster log in this
  scenario will now be the correct error, because MQ has returned
  the correct error code.  However, please note that the full
  error text in the cluster log is still generated by the Cluster
  Service, not by MQ itself.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 CD    TBC.
  v9.1 LTS   9.1.0.6
  
  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