| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| qmgr aliases - inconsistent behaviour? |
« View previous topic :: View next topic » |
| Author |
Message
|
| tonym |
 Posted: Thu May 27, 2004 7:59 am Post subject: qmgr aliases - inconsistent behaviour? |
 |
|
Novice
Joined: 22 Sep 2003
Posts: 11
|
Suppose I create a qmgr alias called INVOICES on a local queue manager.
I now run a local application which opens QX@INVOICES. The local queue manager will resolve the qmgr alias and send the message to a queue called QX at the correct destination.
However, if I define a remote queue QR, with RNAME of "QX" and RQMNAME of "INVOICES", then I can't open the queue (MQRC_XMIT_Q_ERROR) - I assume that the qmgr expects to find an XMITQ called INVOICES.
If MQ is smart enough to resolve the qmgr alias when it is invoked via the API, why can't it resolve it when it is contained within a remote queue definition? Is it just one of those things or is there a valid reason for the difference? |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Thu May 27, 2004 8:08 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I think the rationale behind this behaviour is,
when you don't know everything (hence the QueueManager Alias) MQ will 'help' you where possible (in this case, not all cases....  )
when you pretend to know everything (by defining a specific remoteQ),
MQ let's you sweat when you make an error ... and does not lend a 'hand'...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 27, 2004 10:07 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I think something is wrong. It is perfectly valid to create a remote queue def and only specify the RNAME and RQMNAME, and leave the XMITQ blank. Then Name resolution will put the message to the XMITQ that has the same name as the RQMNAME. If it worked in the first case, it should work in the second, unless you have a typo or something.
RQMNAME:
If an application opens the local definition of a remote queue,
RQMNAME must not be blank or the name of the local queue manager.
When the open occurs, if XMITQ is blank there must be a local queue of
this name, which is to be used as the transmission queue.
XMITQ:
If XMITQ is blank, a queue with the same name as RQMNAME is used as
the transmission queue.
This parameter is ignored if the definition is being used as a queue
manager alias and RQMNAME is the name of the local queue manager.
Also, what is the exact error you got? MQRC_XMIT_Q_ERROR is not a real error.
Maybe post your Q defs.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| tonym |
| Posted: Wed Jun 02, 2004 11:39 pm Post subject: |
|
|
Novice
Joined: 22 Sep 2003
Posts: 11
|
Peter,
I'm talking about qmgr aliases, not remote queues |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jun 03, 2004 3:29 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You asked why your put to the remote queue failed.
| Quote: |
If MQ is smart enough to resolve the qmgr alias when it is invoked via the API, why can't it resolve it when it is contained within a remote queue definition?
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| frankdk |
| Posted: Thu Jun 10, 2004 1:02 pm Post subject: |
|
|
Novice
Joined: 10 Jun 2004
Posts: 20
Location: Copenhagen, Denmark
|
Hi
Your problem is that MQ resolves these names in "stages". It will start with the qmgr name and hence the Qmgr alias. When it gets to the q-name the qmgr part is over and it will threat your qmgrname on the remote queue as an override.
Therefore you need the INVOICES XmitQ.
Regards
Frank |
|
| 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
|
|
|
|
