Author |
Message
|
velocity |
Posted: Tue Sep 08, 2009 6:19 am Post subject: Cluster queues |
|
|
Centurion
Joined: 30 Nov 2007 Posts: 126
|
Hi Guys - I guess I am a little confused.
Lets say there are 3 QMS A, B, & C in a cluster ABC
There is a clustered local queue called 1.2.3 ONLY on QM B defined to the ABC cluster.
Can I not display the clustered queue from QM A by issuing
DIS QCLUSTER(1.2.3)
For some reason I can only display the queue from QM B. |
|
Back to top |
|
 |
exerk |
Posted: Tue Sep 08, 2009 6:36 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
You'll see it in a Full Repository, but not from a Partial Repository, until it has been referenced. It's all in the manual.
Moving this to the appropriate forum... _________________ 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: Tue Sep 08, 2009 6:59 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
The usual narrative is: a full repository knows everything about a cluster; a partial repository only knows what it has expressed interest in.
This means that until an application MQOPENs a clustered queue from a PR, the PR will not know of the queues existence. _________________ 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 |
|
 |
sumit |
Posted: Tue Sep 08, 2009 7:03 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006 Posts: 398
|
Queue 1.2.3 will not be visible in any of the partial repos (except where it is defined) till you access that queue for put/get.
Use utilities for put/get operation and analyse the result. _________________ Regards
Sumit |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Sep 08, 2009 7:08 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
till you access that queue for put/get. |
Discovery from an FR takes place as a result of name resolution. such as MQOPEN or MQPUT1. _________________ 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 |
|
 |
gbaddeley |
Posted: Tue Sep 08, 2009 4:46 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
Wow, 4 posts basically said the same thing. _________________ Glenn |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Sep 08, 2009 6:37 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
Wow, 4 posts basically said the same thing. |
Not really. Some clarity was added. _________________ 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 |
|
 |
exerk |
Posted: Tue Sep 08, 2009 11:28 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
sumit wrote: |
Queue 1.2.3 will not be visible in any of the partial repos (except where it is defined) till you access that queue for put/get). |
You cannot, cannot GET from an instance of a clustered queue that is not 'local' to the application (and before anyone jumps in with the caveat that you can with client...) and a 'local' GET will not cause that queue to show up in a PR (even if you did use client, before anyone jumps in again).
gbaddeley, fair comment, but sometimes hammering in the knowledge is needed  _________________ 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 |
|
 |
|