| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to Open Remote Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| tigerstone |
 Posted: Thu Jun 25, 2015 5:54 am Post subject: Unable to Open Remote Queue |
 |
|
Novice
Joined: 06 Feb 2014
Posts: 20
|
The Application is to write Output Data to a Remote Queue owned by another Queue Manager.
I receive the following error when attempting to do so
Error-Number:2666
Error-Message: Failed to open queue.
ErrorDescription:-1. MQW101. 2196. Rem.Out
Are there any configurations to the Remote Queue Definition to be able to Open this Queue ? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Jun 25, 2015 6:46 am Post subject: Re: Unable to Open Remote Queue |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9405
Location: US: west coast, almost. Otherwise, enroute.
|
| tigerstone wrote: |
The Application is to write Output Data to a Remote Queue owned by another Queue Manager.
I receive the following error when attempting to do so
Error-Number:2666
Error-Message: Failed to open queue.
ErrorDescription:-1. MQW101. 2196. Rem.Out
Are there any configurations to the Remote Queue Definition to be able to Open this Queue ? |
What application? IBM MQ posts 4-digit ReasonCodes and/or error messages that look like AMQnnnn.
Presuming that the app has displayed the RC 2666 and RC 2196, the RC 2196 indicates that the QRemote definition the app attempted to open did not specify an XMITQ.
You can search google for these and other ReasonCodes such as 'mqrc 2196'
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 25, 2015 8:00 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| Quote: |
2196 (0894) (RC2196): MQRC_UNKNOWN_XMIT_Q
Explanation
On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager. The ObjectName or the ObjectQMgrName in the object descriptor specifies the name of a local definition of a remote queue (in the latter case queue-manager aliasing is being used), but the XmitQName attribute of the definition is not blank and not the name of a locally-defined queue. |
So it may be that the definition of a remote queue is missing the needed XMITQ, but it might also mean that you messed up in defining a default route to the target qmgr.
So you have to check both... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
