| Author |
Message
|
| bdrummond |
 Posted: Thu Aug 09, 2007 8:05 am Post subject: MQ Explorer (v6) not showing cluster queues |
 |
|
Disciple
Joined: 06 May 2004
Posts: 164
|
I have installed WMQ v6.0.1.1 and have created a test cluster.
Everything works ok and I can put messages to all QM's across the cluster, however, the only way I can see the clustered queues in MQ Explorer is if I create a new filter.
Clustered queues don't seem to be part of the 'All Queues' filter.
Is this correct..?
If so, this poses another question....how do I use the 'put message' function to put a message on to a clustered queue within the Explorer...? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Aug 09, 2007 9:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You mean that you don't see QCLUSTERs in the "Queues" list in the MQExplorer, directly under a given qmgr in the Queue Managers Folder.
If, however, you look in the Queue Manager Clusters folder... it's a different story.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bdrummond |
| Posted: Mon Aug 13, 2007 6:11 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Yes, that's what I mean.
I can see the queues in the Queue Manager Clusters folder(s) but how would I put a test message to one of the clustered queues from one of the clustered queue managers if they only have local queues listed..? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 13, 2007 11:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well. If you apply your filter that lets you see QCLUSTERS, in the regular queue list, then you can "Put Test message" on it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bdrummond |
| Posted: Wed Aug 15, 2007 4:59 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
| jefflowrey wrote: |
| Well. If you apply your filter that lets you see QCLUSTERS, in the regular queue list, then you can "Put Test message" on it. |
Yes, I've been able to do that but I find it strange that Cluster Queues aren't included in the 'All Queues' filter. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 15, 2007 6:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| bdrummond wrote: |
| Yes, I've been able to do that but I find it strange that Cluster Queues aren't included in the 'All Queues' filter. |
I don't disagree that it's strange.
There just isn't anything I can tell you about how to fix it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bdrummond |
| Posted: Wed Aug 15, 2007 6:51 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
No worries. I thought that I was doing something stupid but in this instance, it looks like I wasn't. Wonders will never cease. 
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Aug 16, 2007 6:22 am Post subject: |
|
|
Guest
|
There are two places where queue definitions may be found. One is in the local filesystem under qmgrs/queues (or pageset 0 for mainframe MQ); the other is in a repository.
Name resolution will cause the qmgr to look first for locally defined objects. If the name is not found there, the qmgr will look next in repositories: first in the locally held partial repository, and if not found there, in a full repository.
Refer to the Queue Manager Clusters manual. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 16, 2007 6:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| bruce2359 wrote: |
There are two places where queue definitions may be found. One is in the local filesystem under qmgrs/queues (or pageset 0 for mainframe MQ); the other is in a repository.
Name resolution will cause the qmgr to look first for locally defined objects. If the name is not found there, the qmgr will look next in repositories: first in the locally held partial repository, and if not found there, in a full repository.
Refer to the Queue Manager Clusters manual. |
That's very informative.
It has absolutely nothing to do with the question.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Aug 16, 2007 7:55 am Post subject: |
|
|
Guest
|
"It has absolutely nothing to do with the question." Hmmm.
If the original poster-person looks only at objects locally defined, such as: DIS Q(*), clustered objects will not be displayed. The explorer uses the same kind of script commands to gather info to populate into its panes.
A clustered object definition is held in the repository, and requires a different DISPLAY command.
As to the question about how to use the 'put a message' option in the explorer: name resolution is the same.
It appeared to me that the poster jumped from 'can't see a clustered object with explorer' to 'can't see a clustered object with the WHERE function', to can't put a message from the 'put a message' option'.
Understanding where MQ keeps its object definitions and how they are searched for, should be of some relevance.
Sorry if I misunderstood... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 16, 2007 8:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, at least you've now explained why QCLUSTERs don't show up in the All Queues Filter - because "dis q(*)" doesn't show them.
Except, of course, that the MQExplorer uses PCF messages and not MQSC - AFAIK. So the reason is that "Inquire Queue" or "Inquire Queue Names" doesn't show QCLUSTERs when you give it a "*" for a queue name.
But name resolution has nothing to do with using the 'Put Test Message' function of MQExplorer.
That action is apparently only scoped to appear in the queue list, and not in the Queue Manager Clusters Cluster Queue list.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Aug 16, 2007 9:12 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
On my explorer you have to look in the Queue Manager Cluster 'folder' to see the cluster queues...but you also have to be connected to the queue manager in the queue managers 'folder'.
In other words. Connect to your queue manager.
Open the "Queue Manager Clusters" 'folder.
You should see your cluster name in there. Expand it and you should see full and partial repositories 'folders'.
Look in those for your queue manager name and highlight it. The queues should then be displayed.
Well it works on mine that way  |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Aug 16, 2007 9:14 am Post subject: |
|
|
Guest
|
"Except, of course, that the MQExplorer uses PCF messages and not MQSC - AFAIK."
True. Admin applications, like the explorer, use PCF messages to do admin - the equivalent task of MQSC commands. The SYSTEM.COMMAND.INPUT queue is the destinatoin for admin commands. The command server processes these admin messages and manipulates the objects.
In order to have the explorer put a message on a queue, it must MQPUT it to the queue. The MQOPEN names the queue, which drives name resolution. We're now back to the questions: where does the queue manager look for definintions in order to resolve them; and why DIS Q(*) will not find a clustered object definition. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 16, 2007 9:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
In order to have MQExplorer PUT to a queue, you must select an object that has the "Put Test Message" Action enabled on it. 
The "Put Test Message" action is not enabled on queues listed in the Queue Managers Cluster view. It is only enabled/in scope for the queues that show up in the main queue list.
In order for the PUT to succeed, the qname has to be resolvable. But if the qname weren't resolvable, it wouldn't show up in the MQExplorer queue list view!
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Aug 16, 2007 10:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
For a partial repository this looks like a catch 22 to me.
Thanks to good old MO71 I can change the destination in the popup while putting the test message. And I will get the 2085, 2087, and could not resolve cluster info(2089?) return messages
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
