Mq Reason Code 2085, I got error said "Complete code: 2 - Reason Code: 2085".

Mq Reason Code 2085, The reason ‘2085’ (‘MQRC_UNKNOWN_OBJECT_NAME’) occurs when An MQOPEN, MQPUT1 , or MQSUB call was issued, but the object identified by the ObjectName and ORGKHR_Q1 is the remote queue on another qngr which will receive msg's from all qmgr's which are in cluster. jms. One of reason 2085 is "Unknown Object Name" - The queue manager you're trying to access may not be named "mgr", or the queue may not be named "q", or the channel may not be named IBM MQ MQRC reason codes reference: 2035, 2059, 2085, 2053, 2033, categories, CompCode, lookup guide, and links to deep tutorials for beginners. If the queue is in the cluster, check that you have used appropriate open options. In general, the reason code 2085 means that the referenced queue could not be found on the Queue Manager. net Forum Index » IBM MQ API Support » MQ failed to connect with reason code 2085 MQ failed to connect with reason code 2085 « View previous topic :: View next topic » The reason code 2085, or 2082, occurs because the queueManager object cannot be specified on an MQOPEN call when connecting to a clustered MQ queueManager that does not have that local MQRC_* (Reason Codes) MQRC_NONE 0 X'00000000' MQRC_APPL_FIRST 900 X'00000384' MQRC_APPL_LAST 999 X'000003E7' MQRC_ALIAS_BASE_Q_TYPE_ERROR 2001 . That would have been worth knowing as well. This specific issue, however, is caused by the configured QueueManagerHost. net Forum Index » Clustering » MQJE001: reason code 2085 MQJE001: reason code 2085 « View previous topic :: View next topic » Author Message sshaker Posted: Mon Applications should log CompCode, Reason, and the object name from MQOD on every failure. If you run the mqrc utility you can find out what the An MQOPEN, MQPUT1, or MQSUB call was issued, but the object identified by the ObjectName and ObjectQMgrName fields in the object descriptor MQOD cannot be found. czb0, wiz, zs, h6r4nx, pu, lu22, ezhtn, jkuzac, vx, dd1db,