The following are links to solutions in the IBM WebSphere MQ documentation for particular problems / issues.
- A cluster sender channel is in retry state
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13100_.htm - DISPLAY CLUSQMGR command shows CLUSQMGR names starting SYSTEM.TEMP
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13120_.htm - Applications get RC of 2035 (MQRC_NOT_AUTHORIZED) when trying to open a queue in the cluster
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13430_.htm - Applications get RC of 2085 (MQRC_UNKNOWN_OBJECT_NAME) when trying to open a queue in the cluster
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13140_.htm - Applications get RC of 2189 (MQRC_CLUSTER_RESOLUTION_ERROR) when trying to open a queue in the cluster
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13160_.htm - Messages are not appearing on the destination queues
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13180_.htm - Application gets RC of 2082 (MQRC_UNKNOWN_ALIAS_BASE_Q) when opening a queue in the cluster
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13440_.htm - Messages put to a cluster alias queue go to SYSTEM.DEAD.LETTER.QUEUE
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13200_.htm - A queue manager does not appear to have up to date information about queues and channels in the cluster
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13220_.htm - No changes in the cluster are being reflected in the local queue manager
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13240_.htm - DISPLAY CLUSQMGR command shows a queue manager twice
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13260_.htm - RESET CLUSTER and REFRESH CLUSTER commands were issued, but the queue manager would not rejoin the cluster
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13280_.htm - Out of date information in a restored cluster
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13310_.htm - The cluster DEMO force removed by mistake
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13320_.htm - Possible repository messages deleted
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13330_.htm - Two full repositories moved at the same time
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13340_.htm - Unknown state of a cluster
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc13350_.htm
Regards,
Roger Lacroix
Capitalware Inc.
