Unix diagnostics

  1. From a command prompt change to the C folder name or the <mqe_install_dir>\mqe\Java\demo\UNIX\ folder.
  2. Edit the MQeDiagnostics script to suit your environment. The file makes use of the JavaEnv script, so either ensure that JavaEnv correctly sets up your CLASSPATH and PATH environment variables, or configure them directly from within the MQeDiagnostics script.
  3. Run the MQeDiagnostics script and follow the on screen prompts.
  4. 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 of this file and rerun the tool.

    "com.ibm.mqe.support.MQeDiagnostics : command not found"

    The file JavaEnv is not configured correctly. Edit the files MQeDiagnostics and JavaEnv if necessary and rerun the tool.

    "java.lang.NoClassDefFoundError: com/ibm/mqe/support/MQeDiagnostics"

    Edit the files JavaEnv and MQeDiagnostics if necessary so that the <mqe_install_dir>\MQe\Java\Jars\MQeDiagnostics.jar file 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.
  5. Send MQeDiagnostics.out to the MQe support personnel, as described in Information required by IBM support.

Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.