An MQI client application receives MQRC_* reason codes in the same way as non-client MQI applications. However, there are additional reason codes for error conditions associated with clients. For example:
The most common time for errors to occur is when an application issues an MQCONN and receives the response MQRC_Q_MQR_NOT_AVAILABLE. An error message, written to the client log file, explains the cause of the error. Messages might also be logged at the server, depending on the nature of the failure.
Even though a client has terminated, the process at the server can still hold its queues open. Normally, this is only for a short time until the communications layer detects that the partner has gone.
When an error occurs with a client system, error messages are put into the error files associated with the server, if possible. If an error cannot be placed there, WebSphere MQ attempts to place the error message in an error log in the root directory of the client machine.
Error messages for UNIX clients are placed in the error logs in the same way as they are for the respective WebSphere MQ server systems. Typically these files appear in /var/mqm/errors on UNIX systems.
The location of the log file AMQERR01.LOG is set by the MQDATA environment variable. The default location, if not overridden by MQDATA, is the C drive. Working in the DOS environment involves the environment variable MQDATA.
This is the default library used by the client code to store trace and error information; it also holds the directory name in which the qm.ini file is stored. (needed for NetBIOS setup). If not specified, it defaults to the C drive.
| Note: | For Windows clients, the default library does not contain the directory name for the qm.ini file because configuration information is stored in the Windows Registry. |
The names of the default files held in this library are:
For more information about clients, see WebSphere MQ Clients.