This chapter explains the various ways in which an application running in a WebSphere MQ client environment can connect to a queue manager. It covers the following topics:
When an application running in an WebSphere MQ client environment issues an MQCONN or MQCONNX call, the client identifies how it is to make the connection. When an MQCONNX call is issued by an application on a WebSphere MQ client, the MQI client library searches for the client channel information in the following order:
/var/mqm/AMQCLCHL.TAB
C:\Program Files\IBM\Websphere MQ\amqclchl.tab
The first of the options described above (using the ClientConnOffset or ClientConnPtr fields of MQCNO) is supported only by the MQCONNX call. If the application is using MQCONN rather than MQCONNX, the channel information is searched for in the remaining three ways in the order shown above. If the client fails to find any of these, the MQCONN or MQCONNX call fails.
The channel name (for the client connection) must match the server-connection channel name defined on the server for the MQCONN or MQCONNX call to succeed.
If you receive an MQRC_Q_MGR_NOT_AVAILABLE return code from your application with an error message in the error log file of AMQ9517 - File damaged, see Migrating to a later release level of WebSphere MQ.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
manyqm |