| Author |
Message
|
| harish_td |
 Posted: Sun Sep 21, 2008 6:21 pm Post subject: DIS QCLUSTER() Not consistent |
 |
|
Master
Joined: 13 Feb 2006
Posts: 236
|
Dear All,
I have a GATEWAYQM that connects to 2 Full Repositories NODE1_QM and NODE2_QM.
On the GATEWAYQM i have a Queue Alias that resolves to a Target Queue that is defined on NODE1_QM and NODE2_QM.
If i issue q DIS QCLUSTER() for the first time on this queue within the GATEWAYQM then the queues defined within the FR's do not show up.
However when i try to put a test message on this queue the Queues show up and continue to be shown for quite some time there after.
Please see below for a screen capture of the same
To my understanding, once an object is added on to the Full Repositories and the Full Repositories exchange information about the new object the same should stay updated eternally. But this i cannot explain theoretically.
Would be very helpful if you can share your thoughts on the same.
Thanks in Advance,
Harish
Mon Sep 22 10:14:04 IST 2008
user@Server>runmqsc GATEWAYQM
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager GATEWAYQM.
DIS Q(ABC)
1 : DIS Q(ABC)
AMQ8409: Display Queue details.
QUEUE(ABC) TYPE(QALIAS)
ALTDATE(2008-03-30) ALTTIME(14.14.30)
TARGQ(ABC.DEF.XYZ) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) DEFBIND(NOTFIXED)
DEFPRTY(5) DEFPSIST(NO)
DESCR(Response Message from App1 to App2)
GET(ENABLED) PUT(ENABLED)
SCOPE(QMGR)
DIS QCLUSTER(ABC.DEF.XYZ)
2 : DIS QCLUSTER(ABC.DEF.XYZ)
AMQ8147: WebSphere MQ object ABC.DEF.XYZ not found.
end
3 : end
One MQSC command read.
No commands have a syntax error.
One valid MQSC command could not be processed.
user@Server>q -m GATEWAYQM -o ABC.DEF.XYZ
MQSeries Q Program by Paul Clarke [ V4.5 Build:Sep 15 2006 ]
Connecting ...connected to 'GATEWAYQM'.
user@Server>runmqsc GATEWAYQM
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager GATEWAYQM.
DIS Q(ABC)
2 : DIS Q(ABC)
AMQ8409: Display Queue details.
QUEUE(ABC) TYPE(QALIAS)
ALTDATE(2008-03-30) ALTTIME(14.14.30)
TARGQ(ABC.DEF.XYZ) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) DEFBIND(NOTFIXED)
DEFPRTY(5) DEFPSIST(NO)
DESCR(Response Message from App1 to App2)
GET(ENABLED) PUT(ENABLED)
SCOPE(QMGR)
DIS QCLUSTER(ABC.DEF.XYZ)
1 : DIS QCLUSTER(ABC.DEF.XYZ)
AMQ8409: Display Queue details.
QUEUE(ABC.DEF.XYZ) TYPE(QCLUSTER)
ALTDATE(2008-03-30) ALTTIME(14.00.52)
CLUSDATE(2008-09-22) CLUSTER(CLUSTER)
CLUSQMGR(NODE1_QM) CLUSQT(QLOCAL)
CLUSTIME(10.14.45) CLWLPRTY(0)
CLWLRANK(0) DEFBIND(NOTFIXED)
DEFPRTY(5) DEFPSIST(NO)
DESCR(Response Message from App1 to App2)
PUT(ENABLED) QMID(NODE1_QM_2008-03-30_12.58.50)
AMQ8409: Display Queue details.
QUEUE(ABC.DEF.XYZ) TYPE(QCLUSTER)
ALTDATE(2008-03-30) ALTTIME(14.02.35)
CLUSDATE(2008-09-22) CLUSTER(CLUSTER)
CLUSQMGR(NODE2_QM) CLUSQT(QLOCAL)
CLUSTIME(10.14.45) CLWLPRTY(0)
CLWLRANK(0) DEFBIND(NOTFIXED)
DEFPRTY(5) DEFPSIST(NO)
DESCR(Response Message from App1 to App2)
PUT(ENABLED) QMID(NODE2_QM_2008-03-30_13.03.55)
end
2 : end
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
user@Server> |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Sun Sep 21, 2008 6:43 pm Post subject: Re: DIS QCLUSTER() Not consistent |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| harish_td wrote: |
Dear All,
I have a GATEWAYQM that connects to 2 Full Repositories NODE1_QM and NODE2_QM.
On the GATEWAYQM i have a Queue Alias that resolves to a Target Queue that is defined on NODE1_QM and NODE2_QM.
If i issue q DIS QCLUSTER() for the first time on this queue within the GATEWAYQM then the queues defined within the FR's do not show up.
However when i try to put a test message on this queue the Queues show up and continue to be shown for quite some time there after. |
A partial repository queue manager will not have knowledge of clustered queues on other queue managers until something tries to open it locally.
The full repository queue manager does not "push out" all the clustered queue definitions to all the partial repository queue managers, it only sends them "on demand".
_________________
Glenn |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 22, 2008 3:13 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Don't know which would be considered better practice...
I generally don't define an alias queue on a qmgr that doesn't host the queue. I'd rather define it on the qmgrs hosting the queue and cluster it.
Or define it as a remote queue with the qmgr being a cluster alias.
Peter and all what is your practice there? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Sep 22, 2008 4:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Apologies if I'm gatecrashing...
A QA on the 'sending' queue manager, appropriately locked down with OAM.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 22, 2008 10:24 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| exerk wrote: |
Apologies if I'm gatecrashing...
A QA on the 'sending' queue manager, appropriately locked down with OAM. |
Same case could be made for a QR properly locked down... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Sep 22, 2008 11:28 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| exerk wrote: |
Apologies if I'm gatecrashing...
A QA on the 'sending' queue manager, appropriately locked down with OAM. |
Same case could be made for a QR properly locked down... |
I'm interested...how is that done in a cluster? (genuine question).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Sep 22, 2008 11:34 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I suppose one could create QAs with different auth that are not part of a cluster; but resolve to a QR with no auth that is part of the cluster. It's the first name (used at MQOPEN) that is auth checked.
_________________
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 |
|
|
| PeterPotkay |
| Posted: Mon Sep 22, 2008 4:57 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
One of the benefits of clustering is reduced administration. If you have 1000 QMs in a cluster each with QUEUE.APPLE and you want to add a new QM to cluster that can talk to QUEUE.APPLE on any of them, all you have to do is define a CLUSRCVR and a CLUSNDR to one FR. That's a-nice!
BUT, now an app connected to your new QM can send to any queue on any of those 1000 QMs.  The reason is that in order to realize this reduced administration, you have to grant access to the SYSTEM.CLUSTER.TRANSMIT.QUEUE. So your new app can send to QUEUE.APPLE, QUEUE.BANANA.....QUEUE.ZUCHINNI, even SYSTEM.ADMIN.COMMAND.QUEUE and SYSTEM.CLUSTER.COMMAND.QUEUE.
2 ways around this. First, you can tag the CLUSRCVR of every QM with an MCAUSER ID that does not have access to the SYSTEM.ADMIN.COMMAND.QUEUE. That at least eliminates QM to QM remote administration of your QMs. But if you need some of the QMs to have access to some of the queues and not others, you have to do this: On each QM, restrict access to the SYSTEM.CLUSTER.TRANSMIT.QUEUE, define a queue alias for each and every queue in the system you want your app to get to, and grant permissions to the app ID to only those queue aliases. Phooey! All of the sudden your reduced administration is no longer so reduced, although you do still save all the SNDR channels, RCVR channel and XMITQs you would have had to create without clustering.
Its to bad setmqaut commands weren't MQ cluster aware, so that you could grant / restrict an ID's access to QUEUE.APPLE, even if the queue did not exist locally on the QM you were setmqauting, although it was somewhere in the MQ cluster.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 22, 2008 7:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| fjb_saper wrote: |
Don't know which would be considered better practice...
I generally don't define an alias queue on a qmgr that doesn't host the queue. I'd rather define it on the qmgrs hosting the queue and cluster it.
Or define it as a remote queue with the qmgr being a cluster alias.
Peter and all what is your practice there? |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Sep 23, 2008 3:26 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I only define the queues where they are needed. I don't have remote q defs in the cluster pointing to local queues in the cluster.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
