Resolving problems with queue manager clusters Use the advice given here to help you to resolve common problems that can arise when you use queue manager clusters. A cluster-sender channel is continually trying to start DISPLAY CLUSQMGR shows CLUSQMGR names starting SYSTEM.TEMP. Return code=2035 MQRC_NOT_AUTHORIZED Return code=2085 MQRC_UNKNOWN_OBJECT_NAME when trying to open a queue in the cluster Return code=2189 MQRC_CLUSTER_RESOLUTION_ERROR when trying to open a queue in the cluster Return code=2082 MQRC_UNKNOWN_ALIAS_BASE_Q opening a queue in the cluster Messages are not arriving on the destination queues Messages put to a cluster alias queue go to SYSTEM.DEAD.LETTER.QUEUE A queue manager has out of date information about queues and channels in the cluster No changes in the cluster are being reflected in the local queue manager DISPLAY CLUSQMGR displays a queue manager twice A queue manager does not rejoin the cluster Out of date information in a restored cluster Cluster queue manager force removed from a full repository by mistake Possible repository messages deleted Two full repositories moved at the same time Unknown state of a cluster What happens when a cluster queue manager fails What happens when a repository fails What happens if a cluster queue is disabled for MQPUT