| Author |
Message
|
| piku_m |
 Posted: Fri Jul 25, 2008 4:45 am Post subject: Can two Qmgrs have same QMID? |
 |
|
Newbie
Joined: 12 Apr 2008
Posts: 6
|
Hi Experts,
We have created a two Qmgrs in two different systems(AIX & HPUX). The name of both the Qmgrs are same but with a different QMID(system generated). Is any any way to make the QMID of both the Qmgrs same?
Please advice.
Thanks
Subhra |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Jul 25, 2008 5:15 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
QMID is system-generated so that you can distinguish between two qmgrs with the same name. This means, for example, that you can issue a SUSPEND command with qmgr name or QMID.
Your application programs refer to the qmgr name, NOT the QMID.
_________________
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 |
|
|
| sami.stormrage |
| Posted: Fri Jul 25, 2008 6:15 am Post subject: |
|
|
Disciple
Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore
|
And Y would anyone require a 2 Qmgrs with same name.. what purpose does it serve? 
_________________
*forgetting everything  * |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Jul 25, 2008 7:12 am Post subject: Re: Can two Qmgrs have same QMID? |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| piku_m wrote: |
| The name of both the Qmgrs are same but with a different QMID(system generated). |
Before you get to far along, I'd suggest that you delete one of these queue managers and re-create it with a new name. Having two qmgrs with the same name is asking for trouble. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 25, 2008 7:15 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| And Y would anyone require a 2 Qmgrs with same name.. what purpose does it serve? |
One reason comes to mind:
I have three environments: TEST, QA, and PROD.
Applications exist that MQCONN to a qmgr named BOB. In order to test the application, it is compiled and tested in TEST qmgr BOB; then promoted to QA for validation on QA qmgr BOB; and then promoted to PROD on qmgr BOB.
_________________
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: Fri Jul 25, 2008 7:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bruce2359 wrote: |
| Quote: |
| And Y would anyone require a 2 Qmgrs with same name.. what purpose does it serve? |
One reason comes to mind:
I have three environments: TEST, QA, and PROD.
Applications exist that MQCONN to a qmgr named BOB. In order to test the application, it is compiled and tested in TEST qmgr BOB; then promoted to QA for validation on QA qmgr BOB; and then promoted to PROD on qmgr BOB. |
In the same breath you should probably confirm that your TEST, QA, and PROD MQ environments are entirely separate and do not communicate with each other... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 25, 2008 7:36 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Having two qmgrs with the same name is asking for trouble. |
That's why IBM recommends that you not have two (or more) qmgrs with the same name in the same network. Yes, complications can arise; but most are manageable. Diagnosing problems may become a big challenge. That's why the QMID.
Edit:
| Quote: |
| In the same breath you should probably confirm that your TEST, QA, and PROD MQ environments are entirely separate and do not communicate with each other... |
AFAIK there is no restriction about having two qmgrs with the same name having channels to each other.
_________________
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: Fri Jul 25, 2008 7:51 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bruce2359 wrote: |
Edit:
| Quote: |
| In the same breath you should probably confirm that your TEST, QA, and PROD MQ environments are entirely separate and do not communicate with each other... |
AFAIK there is no restriction about having two qmgrs with the same name having channels to each other. |
Remember that this is the cluster forum. Having 2 qmgrs with the SAME NAME in the SAME / overlapping CLUSTER is just ASKING for TROUBLE...
I never said you could not communicate if the other qmgr is outside of the cluster and you used qmgr aliases etc....
For your sake I hope that your TEST, QA and PROD MQ clusters do not overlap.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 25, 2008 7:58 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Back to the original post:
| Quote: |
| Is any any way to make the QMID of both the Qmgrs same? |
What are you trying to accomlish by doing this?
_________________
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 |
|
|
| sami.stormrage |
| Posted: Fri Jul 25, 2008 8:54 am Post subject: |
|
|
Disciple
Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore
|
its simply impossible to create 2 Qmgrs with same Qmid... if u requirement is to have 2 clones that look alike then it a different configuration.. and another way is ip virtualization.. I believe.
_________________
*forgetting everything * |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 25, 2008 9:13 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| its simply impossible to create 2 Qmgrs with same Qmid |
I seem to recall stumbling onto QMID in the Windows Registry; so I suppose I can alter it...
_________________
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 |
|
|
| piku_m |
| Posted: Fri Jul 25, 2008 12:06 pm Post subject: |
|
|
Newbie
Joined: 12 Apr 2008
Posts: 6
|
Thanks Guys for your valuable inputs.
We have DR & Prod environment. The same Qmgr name is being created on both DR & Prod server and with the same name. We have created the first Qmgr on DR box. Then by taking the saveqmgr object we have replicated the same on Prod box.
Now, both the Qmgrs are in cluster but not a full repository. At any point of time any one of the Qmgr should be running either Prod or DR. Few days back, after testing the DR box, we shutdown the DR Qmgr & started the same on Prod. FDC generated specifing that unable to put message on SYSTEM.CLUSTER.TRANSMIT.QUEUE with the DR QMID even though the DR Qmgr is down & Prod is up.
So, I am wonderering if it could create any issue going forward?
Thanks
Subhra |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 25, 2008 12:24 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| So, I am wonderering if it could create any issue going forward? |
Yes. Yes. Yes.
This is the exact issue fjb_saper pointed out earlier in this post, namely: having two (or more) qmgrs with the same name in the same cluster and visible in the network.
The DR qmgr contributed its definitions when you started it and it joined the cluster with the same name as another qmgr in the cluster - even though the other was shut down. This is working as designed.
The clusters manual (advanced tasks) tells you how to remove a qmgr from the cluster using the QMID.
_________________
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: Sat Jul 26, 2008 11:01 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| piku_m wrote: |
Thanks Guys for your valuable inputs.
We have DR & Prod environment. The same Qmgr name is being created on both DR & Prod server and with the same name. We have created the first Qmgr on DR box. Then by taking the saveqmgr object we have replicated the same on Prod box.
Now, both the Qmgrs are in cluster but not a full repository. At any point of time any one of the Qmgr should be running either Prod or DR. Few days back, after testing the DR box, we shutdown the DR Qmgr & started the same on Prod. FDC generated specifing that unable to put message on SYSTEM.CLUSTER.TRANSMIT.QUEUE with the DR QMID even though the DR Qmgr is down & Prod is up.
So, I am wonderering if it could create any issue going forward?
Thanks
Subhra |
For your scenario you should really use the same qmgr and have it hardware clustered. Then it does not matter that it is in an MQ cluster.
At the same time the HW cluster will allow you to specify the HW cluster DNSname or IP which will move at the same time the HW cluster service moves from one box to the other
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Jul 27, 2008 8:39 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| Quote: |
| And Y would anyone require a 2 Qmgrs with same name.. what purpose does it serve? |
One reason comes to mind:
I have three environments: TEST, QA, and PROD.
Applications exist that MQCONN to a qmgr named BOB. In order to test the application, it is compiled and tested in TEST qmgr BOB; then promoted to QA for validation on QA qmgr BOB; and then promoted to PROD on qmgr BOB. |
Hi Bruce, please take advice that industry best practice is to always use unique queue manager names. Its common to include the environment type and a sequence number in the name, eg. BOBTEST1, BOBQA1, BOBPROD1.
Applications should obtain qmgr name and queue names from configuration info somewhere (file, registry, factory etc), so that promotion of app programs from one environment to another will work transparently.
Your reasoning does not hold any water. The MQ object definition files that are promoted from one environment to the next should only contain queue objects. There should be no channel objects, as the connames will be different in each environment (unless you have also made the mistake of using the same host names for dev, qa & prod!)
_________________
Glenn |
|
| Back to top |
|
|
|
|
