Chapter 14. Solving problems
This chapter discusses the following topics:
- WebSphere MQ client fails to make a connection
- Stopping WebSphere MQ clients
- Error messages with WebSphere MQ clients
- How to read the error log and FFDCs for DOS and Windows 3.1
- Using trace on DOS and Windows 3.1
- Using trace on OS/2 Warp, Windows, and Windows 95
- Using trace on AIX and AT&T GIS UNIX
- Using trace on Compaq OpenVMS Alpha, HP-UX, SINIX, DC/OSx, and Solaris
- Using trace on VM/ESA
An application running in the WebSphere MQ client environment receives MQRC_* reason codes in the same way as WebSphere MQ server applications. However, there are additional reason codes for error conditions associated with WebSphere MQ clients. For example:
- Remote machine not responding
- Communications line error
- Invalid machine address
The most common time for errors to occur is when an application issues an MQCONN or MQCONNX and receives the response MQRC_Q_MQR_NOT_AVAILABLE. Look in the client error log for a message explaining the failure. There might also be errors logged at the server, depending on the nature of the failure. Also, check that the application on the WebSphere MQ client is linked with the correct library file.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
AIX is a trademark of the IBM Corporation in the United States, other countries, or both.