2059 (080B) (RC2059): MQRC_Q_MGR_NOT_AVAILABLE
Explanation
This error occurs:
- On an MQCONN or MQCONNX call, the queue manager identified by the QMgrName parameter is not available for connection.
- On z/OS®:
- For batch applications, this reason can be returned to applications running in LPARs that do not have a queue manager installed.
- For CICS® applications, this reason can occur on any call if the original connect specified a queue manager with a name that was recognized, but which is not available.
- There might be a system wide ECSA shortage, or the storage available for creating new queue manager connections might be limited by the ACELIM system parameter. See message CSQ3202E for more information.
- On IBM® i, this reason can also be returned by the MQOPEN and MQPUT1 calls, when MQHC_DEF_HCONN is specified for the Hconn parameter by an application running in compatibility mode.
- On z/OS®:
- On an MQCONN or MQCONNX call from an IBM MQ MQI client application:
- Attempting to connect to a queue manager within an MQ-client queue manager group when none of the queue managers in the group is available for connection (see the QMgrName parameter of the MQCONN call).
- If the client channel fails to connect, perhaps because of an error with the client-connection or the corresponding server-connection channel definitions.
- If a command uses the CommandScope parameter specifying a queue manager that is not active in the queue sharing group.
- In a multiple installation environment, where an application attempts to connect to a queue manager associated with an installation of IBM WebSphere® MQ 7.1, or later, but has loaded libraries from IBM WebSphere MQ 7.0.1. IBM WebSphere MQ 7.0.1 cannot load libraries from other versions of IBM MQ.
Completion code
MQCC_FAILED
Programmer response
Ensure that the queue manager has been started. If the connection is from a client application, check the channel definitions, channel status, and error logs.
In a multiple installation environment, ensure that IBM WebSphere MQ 7.1, or later, libraries are loaded by the operating system. For more information, see Connecting applications in a multiple installation environment.