| Author |
Message
|
| Hassan |
 Posted: Wed Apr 06, 2005 11:58 am Post subject: Same Queue Manager Names |
 |
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
Is it possible to have 2 queue managers with exactly the same names communicate with eachother by using Remote Queues.
Example:
QM1 and QM1, both have remote Qs defined to the other.
I have set this up but keep getting a 2087 (Unknown Remote Q Manager), when I try to do a sample put on either of these remote Qs.
Channels (Senders and the Receivers) on both sides can be started with no problem.
TIA,
Hassan |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Wed Apr 06, 2005 12:03 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| This question has come up before, and I believe the answer is that it is possible. However, why would you want to do it? You'd never really know which queue manager you are dealing with. Queue manager names really should be unique. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Apr 06, 2005 12:10 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1197
Location: Arizona
|
Indeed.
You can name all your children George too but then they never know who you're talking to at the dinner table.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| Hassan |
| Posted: Wed Apr 06, 2005 12:13 pm Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
QM1 is currently running on an AS/400 and (among other connections) communicating to an outside vendor.
We are looking at moving some code off the AS/400 and onto a WINTEL box, and to minimize the "chargeable" changes this vendor has to make, we are looking at creating another QM1 on this WINTEL and have the messages passed on to&from the original QM1 (on the AS/400).
I also think logically there should not be an issue (other than to confuse the hek out of ppl.) but I keep running into this 2087.
Thanks! |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Apr 06, 2005 1:53 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
Post the queue definitions - maybe something is wrong there.
But it is a bad, bad, bad, bad idea to name them both the same! Why are you doing this to yourself? You still have not given a reason why the new QM can't be called QM1A, or QM2.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Apr 06, 2005 2:02 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1197
Location: Arizona
|
| PeterPotkay wrote: |
Post the queue definitions - maybe something is wrong there.
But it is a bad, bad, bad, bad idea to name them both the same! Why are you doing this to yourself? You still have not given a reason why the new QM can't be called QM1A, or QM2. |
or George....
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 06, 2005 2:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| Hassan wrote: |
QM1 is currently running on an AS/400 and (among other connections) communicating to an outside vendor.
We are looking at moving some code off the AS/400 and onto a WINTEL box, and to minimize the "chargeable" changes this vendor has to make, we are looking at creating another QM1 on this WINTEL and have the messages passed on to&from the original QM1 (on the AS/400).
I also think logically there should not be an issue (other than to confuse the hek out of ppl.) but I keep running into this 2087.
Thanks! |
If you want your qmgr "GEORGE" to act like it's name was "MARY" do not create it under the name MARY but use a qmgr alias in GEORGE:
| Code: |
| def qr(MARY) rqmname(GEORGE) |
You could as well change a local queue on the AS to a remote queue pointing to wintel.
enjoy  |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Wed Apr 06, 2005 11:29 pm Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
| csmith28 wrote: |
Indeed.
You can name all your children George too but then they never know who you're talking to at the dinner table. |
Well, If they all have different last names  |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Apr 07, 2005 3:34 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| sebastianhirt wrote: |
| csmith28 wrote: |
Indeed.
You can name all your children George too but then they never know who you're talking to at the dinner table. |
Well, If they all have different last names |
Or if one of them was a girl.... |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Apr 07, 2005 5:23 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
I can sympathise with Hassan. We also have to have some same named queue managers....and all because a vendor doesn't understand MQ. They insisted on using the name QM_QICLINK on one end and QM_THG on the other end of 'their' application.....why? because that is how their install scritps are set up. It was all I could do to get them to let me trigger the channels for them. This isn't the first vendor of MQ software or services that I have come across that doesn't have the first clue about MQ.
Sadly arguing with them results in a 'this is the only method we support, deviate and we won't support it'
Back to the point....... We have same named queue managers but they are seperate and ditinct from each other, one in development and one in production....they have no requirement to talk to each other nor does anything (other than our monitor) have to talk to both. My chioce would be to avoid having the same names if only for sanitys sake! |
|
| Back to top |
|
|
| Hassan |
| Posted: Thu Apr 07, 2005 8:20 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
Thank you all very much for the enlightenment, I will make sure that not even a single kid of mine is named George.
Now for the problem at hand. Is this possible or not ? |
|
| Back to top |
|
|
| Hassan |
| Posted: Thu Apr 07, 2005 8:42 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
Thanks PeterPotkay
Here is the Q Def. from one of the QMs
Display MQ Queue
Queue manager name . . . . . . : TESTQM
Queue name . . . . . . . . . . : REMOTE_TODC06
Queue type . . . . . . . . . . : *RMT
Put enabled . . . . . . . . . : *YES
Default message priority . . . : 0
Default message persistence . : *NO
Default binding . . . . . . . : *OPEN
Remote queue . . . . . . . . . : LOCAL_TODC06
Remote Message Queue Manager . : TESTQM
Transmission queue . . . . . . : TTESTQM
===================
Here is the sample PUT with the error....
Sample AMQSPUT0 start
target queue is REMOTE_TODC06
MQOPEN ended with reason code 2087
unable to open queue for output
Sample AMQSPUT0 end
Press ENTER to end terminal session.
TIA |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 07, 2005 1:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Ok
There is a way to make this work
on the remote end put
def qr(GEORGE) rqmname(TESTQM)
On the local end
on your remote queue
alter qr(REMOTE_TODC06) rqmname(GEORGE)
add a remote queue
def qr(GEORGE) rqmname(GEORGE) xmitq(TTESTQM)
And tell them they need to put GEORGE as reply to qmgr into their apps
Enjoy |
|
| Back to top |
|
|
| Hassan |
| Posted: Fri Apr 08, 2005 4:40 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
Thanks! will try.
Rgds.
Hassan |
|
| Back to top |
|
|
| Hassan |
| Posted: Fri Apr 08, 2005 6:16 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
Great it's working.... only thing left to do is to make sure nothing is named George.....
Again Thanks fjb_saper. |
|
| Back to top |
|
|
|
|
