Invoking the MQeDiagnostics Tool

If you need to use this tool it can be invoked as follows.

On Windows NT and Windows 2000

  1. From a command prompt change to the ...\mqe\Java\demo\Windows\ folder.
  2. 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 configure them directly from within the MQeDiagnostics.bat script.
  3. Run the MQeDiagnostics.bat file 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 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\Java\Jars\MQeDiagnostics.jar can be found in the CLASSPATH environment variable.
    Note:
    Not all WebSphere MQ Everyplace classes can supply version information, so the MQeDiagnostics.out file may include some "Unknown version!" messages.
    5) Send MQeDiagnostics.out to the WebSphere MQ Everyplace support personnel.

On UNIX systems

  1. From a command prompt change to the C folder name or the ...\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"
    JavaEnv is not configured correctly. Edit MQeDiagnostics and JavaEnv if necessary and rerun the tool.

    "java.lang.NoClassDefFoundError: com/ibm/mqe/support/MQeDiagnostics"
    Edit JavaEnv and MQeDiagnostics if necessary so that the ...\MQe\Java\Jars\MQeDiagnostics.jar file can be found in the CLASSPATH environment variable.
    Note:
    Not all WebSphere MQ Everyplace classes can supply version information, so the MQeDiagnostics.out file may include some "Unknown version!" messages.
  5. Send MQeDiagnostics.out to the WebSphere MQ Everyplace support personnel.

Other systems

On other systems, the MQeDiagnostics tool should be invoked directly.

  1. Add the MQeDiagnostics.jar file to your classpath.
  2. Invoke the com.ibm.mqe.support.MQeDiagnostics class from the Java runtime environment. For example:
    C example
    
    java com.ibm.mqe.support.MQeDiagnostics 
    MQeDiagnostics.properties > MQeDiagnostics.out
    

    The program takes the MQeDiagnostics.properties file as an argument.

  3. Send the output from the tool to the WebSphere MQ Everyplace support personnel.


© IBM Corporation 2002. All Rights Reserved