| Author |
Message
|
| Inforz |
 Posted: Wed May 18, 2011 5:57 am Post subject: Queue displayed twice |
 |
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Hi,
When issuing the following two commands will there be any difference in the outputs??
1.dis ql(*) where (cluster eq '<clus name>')
2.dis qcluster(*)
will the output be same??
Prob 1.
In my case, the first command results in two queue names that have same name(LOGQ) and same properties except for the creation date and time and alteration date and time AND DIFFERENT CURDEPTHS(12 and 4185).
Prob 2.
The second command results in two queues that have different names(TESTLOGQ and LOGQ(the one with curdepth 12)). Why is the TESTLOGQ not displayed in the first command
 me to resolve the prob.
Thanks, |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Wed May 18, 2011 6:01 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
please show the exact output of the commands.
what mq version?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| exerk |
| Posted: Wed May 18, 2011 6:14 am Post subject: Re: Queue displayed twice |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Inforz wrote: |
When issuing the following two commands will there be any difference in the outputs??
1.dis ql(*) where (cluster eq '<clus name>')
2.dis qcluster(*) |
Yes!
| Inforz wrote: |
| ...will the output be same?? |
No!
| Inforz wrote: |
| In my case, the first command results in two queue names that have same name(LOGQ) and same properties except for the creation date and time and alteration date and time AND DIFFERENT CURDEPTHS(12 and 4185). |
And of course that the queue managers in which they are hosted will be different - you missed that detail.
| Inforz wrote: |
| ...Why is the TESTLOGQ not displayed in the first command? |
Probably because it is not a QL.
Your first command was very specific, your second very generic.
_________________
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: Wed May 18, 2011 6:36 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
As described in the MQSC manual...
DIS QL displays local queue objects only - whether or not they are part of a cluster.
DIS QCLUSTER displays queue objects known to the cluster - whether or not they are local.
_________________
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 |
|
|
| Inforz |
| Posted: Wed May 18, 2011 9:09 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
| Quote: |
Inforz wrote:
| Quote: |
In my case, the first command results in two queue names that have same name(LOGQ) and same properties except for the creation date and time and alteration date and time AND DIFFERENT CURDEPTHS(12 and 4185).
|
And of course that the queue managers in which they are hosted will be different - you missed that detail. |
Yeah I forgot to mention, but I jus checked again in all the queue managers(1FR and 5PRs). There is only one QM(LOGQM,which is a PR) that has this LOGQ. Also note that both LOGQ and TESTLOGQ are local cluster queues, but the latter is not displayed in the first cmd. 
FYI, (this may be wierd, but true outputs)
When I connect to this QM(LOGQM) thru putty(all are linux servers I am talking about), and gave a dis ql(*) I get this LOGQ(the one that has curdepth as 12) only once, but when connected from Windows MQ as a remote QM, only the LOGQ that has curdepth 4185 is seen.
Please explain if this happens to be true. Let me know if you need any more details.
Mr.Butcher, its
MQ 7.0.1.3
I am typing this in my PC as I have the connectivity (VPN) to the linux servers only in office, and now its long past my office hours. Will soon update you with the command outputs.
Thanks, |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 18, 2011 9:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Inforz wrote: |
| I jus checked again in all the queue managers(1FR and 5PRs). |
I told you in one of your earlier posts that WMQ clusters require 2 FRs.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 18, 2011 9:29 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
| Inforz wrote: |
FYI, (this may be wierd, but true outputs) ...
|
Please answer question that are asked. Please post your entire putty conversation; that is, the command you typed, AND the response from the command.
_________________
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 |
|
|
| mqjeff |
| Posted: Wed May 18, 2011 9:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
how many LOGQs do you see when you just "dis ql(*)", without the where clause?
If you see MORE THAN ONE, then something is wrong with your qmgr, because it is not possible to have more than one QLOCAL that has the same name.
Now, it's possible that you have one that is named "logq" and one that is named "LOGQ" and this is the confusion. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 18, 2011 10:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
I attempt to clarify:
It is not possible to have more than one QUEUE (local, model, alias, remote) that has the SAME NAME on the SAME queue manager.
_________________
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 |
|
|
| Inforz |
| Posted: Wed May 18, 2011 6:03 pm Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Yeah Vitor, I agree and I suggested the same to the tech architects. But since this is a test env we have such a setup was the answer to me. But in our prod env there is another copy of this setup present, meaning we have two strands of this setup(so 2FRs and 10PRs in that cluster).
For others: I will be in office soon and I shall give you the outputs.
Thanks, |
|
| Back to top |
|
|
| Inforz |
| Posted: Wed May 18, 2011 9:49 pm Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Here are the outputs
dis ql(*) where (cluster eq 'MQ_CLUSTER') curdepth
5 : dis ql(*) where (cluster eq 'MQ_CLUSTER') curdepth
AMQ8409: Display Queue details.
QUEUE(LOGQ) TYPE(QLOCAL)
CLUSTER(MQ_CLUSTER) CURDEPTH(12)
AMQ8409: Display Queue details.
QUEUE(LOGQ) TYPE(QLOCAL)
CLUSTER(MQ_CLUSTER) CURDEPTH(4185)
dis qcluster(*)
6 : dis qcluster(*)
AMQ8409: Display Queue details.
QUEUE(LOGQ) TYPE(QCLUSTER)
AMQ8409: Display Queue details.
QUEUE(TESTLOGQ) TYPE(QCLUSTER)
mqjeff, after a dis ql(*) (without where clause) all the system local queues plus the above two queues (LOGQ(curdepth=12) and TESTLOGQ) are seen.
Thanks, |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu May 19, 2011 7:43 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Is this shared or MF? Also is LOGQ by any chance part of a queue sharing group? So one entry would show the qdepth on the current qmgr and the other entry the qdepth on the qmgr in the queue sharing group?
Just a thought ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Inforz |
| Posted: Thu May 19, 2011 8:17 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Nopes... Nah.. No.. Sorry none are implemented/present. Will this be due to some migration prob, by any chance?? As I recently migrated from v6 to v7.
Thanks, |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu May 19, 2011 8:29 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
Please try this. Post the results.
DIS QL(LOGQ) ALL
DIS QCLUSTER(LOGQ) ALL
_________________
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 |
|
|
| Inforz |
| Posted: Thu May 19, 2011 8:34 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
| Both the results gave me the LOGQ details that has curdepth 12. |
|
| Back to top |
|
|
|
|
