Windows diagnostics
- From a command prompt change to the <mqe_install_dir>\mqe\Java\demo\Windows\ folder.
- Edit the MQeDiagnostics.bat file to suit your environment.
The file makes use of the JavaEnv.bat script, so either
ensure that JavaEnv.bat correctly sets up your CLASSPATH and PATH environment
variables, or set them up in the MQeDiagnostics.bat script.
- Run the MQeDiagnostics.bat file and follow the on
screen prompts.
- Once the tool has completed, look through the MQeDiagnostics.out file
for any errors. Common errors include:
- ".\MQeDiagnostics.properties could not be found"
The tool requires the MQeDiagnostics.properties file
to be supplied as input. Edit MQeDiagnostics.bat so that
it points to the correct location for this file and rerun the tool.
- "com.ibm.mqe.support.MQeDiagnostics is not recognized as an internal or
external command…"
JavaEnv.bat is not configured correctly. Edit MQeDiagnostics.bat and JavaEnv.bat if necessary and rerun the tool.
- "java.lang.NoclassDefFoundError: com/ibm/mqe/support/MQeDiagnostics"
Edit JavaEnv.bat and MQeDiagnostics.bat if
necessary so that the <mqe_install_dir>\MQe\Java\Jars\MQeDiagnostics.jar can
be found in the CLASSPATH environment variable.
Note: Not all MQe classes can supply version information,
so the MQeDiagnostics.out file may include some "Unknown
version!" messages.
- Send MQeDiagnostics.out to the MQe support personnel,
as described in Information required by IBM support.