Solving WebSphere MQ base Java problems

If a program does not complete successfully, run the installation verification program, and follow the advice given in the diagnostic messages. Both of these programs are described in Using WebSphere MQ classes for Java (WebSphere MQ base Java).

If the problems continue and you need to contact the IBM(R) service team, you might be asked to turn on the trace facility. Refer to the following sections for the appropriate procedures for your system.

Tracing the sample application

To trace the MQIVP program, enter the following:

java -Djava.library.path=library_path MQIVP -trace n
where library_path is the path to the WebSphere MQ Java libraries

(see The WebSphere MQ Java libraries), and n is a number between 1 and 5, depending on the level of detail required (the greater the number, the more information that is gathered).

For more information about how to use trace, see Tracing WebSphere MQ base Java programs.

Error messages

Here are some of the more common error messages that you might see:

Unable to identify local host IP address
The server is not connected to the network.

Connect the server to the network and retry.

MQRC_ADAPTER_CONN_LOAD_ERROR
If you see this z/OS(TM) error , ensure that the WebSphere(R) MQ SCSQANLE and SCSQAUTH datasets are in your STEPLIB statement.