# MQRC 2189: Cluster resolution error Source: https://wndsoftware.com/mainframe-errors/mqrc-2189 ### MQRC 2189: Cluster resolution error MQRC 2189 (MQRC_CLUSTER_RESOLUTION_ERROR, hex 088D) means an MQOPEN, MQPUT or MQPUT1 on a cluster queue failed because the queue manager needed an answer from the cluster repository about where the queue lives, and didn't get one. #### Other names for this code Also written as `RC2189`, `reason code 2189`, `MQ 2189`, `MQ error 2189`, `MQRC_CLUSTER_RESOLUTION_ERROR`, `088D`, `0x088D`, `cluster resolution error`, `MQJE001 Reason 2189`, `MQ cluster queue 2189`. ### What it means In an MQ cluster, each queue manager keeps a partial repository of the cluster objects it has used. The first time an application opens a cluster queue that this queue manager hasn't seen, the local repository manager asks a full repository for the queue's definition and hosts. If no answer comes, the call fails with MQCC_FAILED and reason 2189. IBM's troubleshooting page names the usual cause. The queue manager is opening the queue for the first time and can't reach any full repository. That points straight at the cluster-sender (CLUSSDR) channels to the full repositories, which are probably failing to start. The local repository manager process may also be down. On distributed MQ that is a queue manager process. On z/OS it runs in the channel initiator, so a stopped CHIN stops cluster resolution too. IBM also notes the code can appear while REFRESH CLUSTER runs, because the local cluster information is being thrown away and rebuilt. Queues the queue manager already knows about usually keep working, which is why 2189 often hits only new queues or newly started applications. ### Common causes - The cluster-sender channels to the full repositories are stopped or retrying because of network, TLS or definition problems. - Both full repositories are down, or this queue manager points to full repositories that no longer exist. - The repository manager on this queue manager isn't running. On z/OS, the channel initiator is down. - A REFRESH CLUSTER is in progress on this queue manager. - The queue or channel definitions are wrong, so the full repository never published what the application asks for. ### How to find the problem - Run `DISPLAY CLUSQMGR(*) QMTYPE STATUS`. Full repositories show QMTYPE(REPOS). A STATUS other than RUNNING on them is the likely cause. - Check the cluster-sender channels with `DISPLAY CHSTATUS(TO.FULLREPOS1) ALL` and read the error log for why they don't start. - Check whether the queue is known at all with `DISPLAY QCLUSTER(ORDERS.IN)`. - On z/OS, check that the CHIN address space is up and look for CSQX messages about the repository manager in its job log. On distributed MQ, check the error log for repository manager messages. ### How to fix it - Fix the connection to at least one full repository. Start the CLUSSDR channel, correct its CONNAME, or fix the TLS or network problem behind it. - Restart the channel initiator on z/OS, or the queue manager on distributed MQ, if the repository manager has stopped. - Keep two full repositories so one outage doesn't stop resolution. - If a REFRESH CLUSTER is running, wait for it to finish and let applications retry. Avoid running REFRESH CLUSTER during busy periods. ### IBM documentation [IBM documentation: MQRC 2189](https://www.ibm.com/docs/en/ibm-mq/9.4.x?topic=codes-2189-088d-rc2189-mqrc-cluster-resolution-error). Use the documentation for your installed release. [Report a correction to WND Software](https://wndsoftware.com/contact#message). Technical reviewer: [Albert Joseph](https://wndsoftware.com/authors/albert-joseph), WND Software. Last reviewed 2026-10-18 by the WND Software team. Written in our own words. For the full reference, check IBM’s MQ documentation for your version. ### Related codes [MQRC 2085 MQRC_UNKNOWN_OBJECT_NAME Read →](https://wndsoftware.com/mainframe-errors/mqrc-2085) [MQRC 2082 MQRC_UNKNOWN_ALIAS_BASE_Q Read →](https://wndsoftware.com/mainframe-errors/mqrc-2082) [MQRC 2087 MQRC_UNKNOWN_REMOTE_Q_MGR Read →](https://wndsoftware.com/mainframe-errors/mqrc-2087) [MQRC 2538 MQRC_HOST_NOT_AVAILABLE Read →](https://wndsoftware.com/mainframe-errors/mqrc-2538) [MQRC 2009 MQRC_CONNECTION_BROKEN Read →](https://wndsoftware.com/mainframe-errors/mqrc-2009) ### Questions #### Why do some cluster queues work while others give 2189? Queues this queue manager already knows about are in its partial repository and don't need a full repository. A queue opened for the first time does, so it fails while the full repositories are unreachable. #### Is 2189 the same as 2085 for cluster queues? No. 2085 means the name wasn't found. 2189 means the queue manager couldn't get an answer from the full repository, so it doesn't know yet. #### Can REFRESH CLUSTER cause 2189? Yes. IBM notes that applications can get 2189 while REFRESH CLUSTER rebuilds the local cluster information. [IBM MQ reason codes](https://wndsoftware.com/mainframe-errors/mq-reason-codes) · [MQRC 2162](https://wndsoftware.com/mainframe-errors/mqrc-2162) · [MQRC 2195](https://wndsoftware.com/mainframe-errors/mqrc-2195) [← All error codes](https://wndsoftware.com/mainframe-errors/)