Using tool Dependency Walker to diagnose in WMQ Windows: user exit could not be loaded, errors AMQ6188 and AMQ9535
Your team built a WebSphere MQ (WMQ) user exit, which was installed in a queue manager in Windows.
Upon restart of the queue manager you see messages in the error log:
AMQ6188: The system could not dynamically load the library D:\Program Files\IBM\WebSphere MQ\exits\Exit.dll due to a problem with the dll. The errno was 536895880. The queue manager will continue without this module.
EXPLANATION: This message applies to Windows systems only. The dynamically loadable file D:\Program Files\IBM\WebSphere MQ\exits\Exit.dll failed to load correctly due to a problem with the dll.
ACTION: Check that the dll is in the correct place with the correct file permissions etc. and has not been corrupted.
AMQ9535: User exit not valid.
EXPLANATION: Channel program 'X' ended because user exit 'Exit(MQMDH001)' is not valid.
ACTION: Ensure that the user exit is specified correctly in the channel definition, and that the user exit program is correct and available.
Diagnosing the problem
To help you diagnose the common problem in Windows of not including all the dependencies, you can use the Microsoft tool "Dependency Walker". For more information consult:
Article ID: 198038 - Last Review: October 26, 2007 - Revision: 3.4
INFO: Useful Tools for Package and Deployment Issues
This article discusses the following utilities:
Extract.exe Extract files from a CAB file.
Makecab.exe Builds CAB Files.
Cabview View/Manipulate the contents of a CAB file.
Cabarc.exe Build and extract files from a CAB file.
Regsvr32.exe Registers ActiveX Components.
Regocx32.exe Registers ActiveX Controls (.OCX Files).
Regit.exe Registers in process ActiveX servers (.OCX/.DLL Files).
Depends.exe View file dependencies.
Depends.exe Profiling Options.
Filemon.exe Monitors file access activity.
Regmon.exe Monitors registry access activity.
Clireg32.exe Registers Distributed Component Object Model Components
on Client computers.
Vbrun60.exe Installs core Visual Basic files.
Setup Toolkit Used to customize Visual Basic application
The rest of this note only mentions the Dependency Walker:
The Dependency Walker, Depends.exe, is used to determine the explicit dependencies a file has.
A dependency is a secondary file, which is necessary for a file to load/run properly. For example, a Microsoft Visual Basic application is dependent upon the Microsoft Visual Basic run-time files.
Depends.exe also presents plenty of valuable information about dependent components, such as their export table, internal version number, and so forth.
Depends.exe ships with Microsoft Visual Basic and is located on the installation CD's at the following location:
Copy all the files from the Depend folder into the System (or System32) folder.
To use depends.exe, perform the following steps:
1. From the Windows Start menu, choose Run.
2. Type in the path and name to the Depends.exe file. You can also run the Depends.exe file by double-clicking the file through the Windows Explorer. Once Depends.exe executes at least once on your system, you may right-click any .exe, .dll, .ocx or other file and select View Dependencies from the shortcut menu to launch the Depends.exe file.
3. When Depends.exe launches, select File and then choose Open.
4. Browse in the Open dialog box for an .exe, .dll, or .ocx file and then click Open.
5. The explicit dependencies for that particular component will appear.
To download the Dependency Walker utility, visit the following Dependency Walker Web site:
Dependency Walker Profiling Options
To profile an application, follow these steps:
1. Click Start, and then click Run.
2. In the Run box, type the path to the Depends.exe file and type the name of the Depends.exe file.
Alternately, you can use Windows Explorer to run the Depends.exe file.
3. When Depends.exe launches, click File, and then click Open.
4. Find the .exe file in the Open dialog box, and then click Open.
5. On the Profile menu, click Start Profiling.
6. Configure any of the options on the Profile module dialog box that are displayed, and then click OK.
Files are loaded and calls are made in the log window.
Note For more information about the Depends.exe file, see the Utilities On-line help.
WebSphere MQ WMQ