Author |
Message
|
jeevan |
Posted: Fri May 21, 2010 3:05 pm Post subject: Not getting trace route report messag from- DSPMQRTE command |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
We are having problem in one of the stores that it is receiving message very very slow ( 5 minutes) so it does not reply as the message gets expired in the route. With some testing, I found that the message from the source qmgr to the stores is taking long time to reach, We know somewhere something is wrong. But we could not find anything. We woudl like to find the message travel route and I am trying to get dspmqrte work but invein. I used the follwoing syntax:
dspmqrte -m SOURCEQM -qm DESTQM -q DESTQ -rq REPLYTOQUEUE ac -ar -ro activity [-v summary]
In my undedrstanding, it should generate an activities report and send to the REPLYTOQ but it is not doing that.
It runs and gives following output:
AMQ8653: DSPMQRTE command started with options '-m SOURCEQM -qm DESTQM -q DESTQ -rq REPLYTOQ -ac -ar -ro activity'.
AMQ8659: DSPMQRTE command successfully put a message on queue 'SYSTEM.CLUSTER.TRANSMIT.QUEUE', queue manager 'SOURCEQM'.
AMQ8657: DSPMQRTE command used CorrelId 0x414D51204D51505244325F514D2020204BF4C1E120282603.
AMQ8674: DSPMQRTE command is now waiting for information to display.
AMQ8666: Queue 'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue manager 'SOURCEQM'.
AMQ8652: DSPMQRTE command has finished.
It never reaches the destination qmgr. However, when I looked at an example given in an IBM site, with less then these options, it seems the command reaches to the destination qmgr and queue:
Quote: |
dspmqrte -m QM1 -q TARG.AT.QM2 -rq ACTIV.REPLY.Q
AMQ8653: DSPMQRTE command started with options '-m QM1 -q TARG.AT.QM2 -rq ACTIV.REPLY.Q'.
AMQ8659: DSPMQRTE command successfully put a message on queue 'QM2', queue manager 'QM1'.
AMQ8674: DSPMQRTE command is now waiting for information to display.
AMQ8666: Queue 'QM2' on queue manager 'QM1'.
AMQ8666: Queue 'TARGET.Q' on queue manager 'QM2'.
AMQ8652: DSPMQRTE command has finished.
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp
|
Any idea what could have gone wrong?
Thanks
Last edited by jeevan on Sat May 22, 2010 5:30 pm; edited 1 time in total |
|
Back to top |
|
 |
bruce2359 |
Posted: Sat May 22, 2010 7:29 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Any errors in the error logs?
If the last thing you see from dspmqrte is the msg being put to the transmit queue, check to see if the channel is running.
If not, check to see that the the xmit queue is triggered to start the channel. Check to see that the initiation queue is defined and available (put and get enabled). Check to see that the channel initiator app is running, and monitoring the correct init queue. _________________ 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 |
|
 |
jeevan |
Posted: Sat May 22, 2010 10:22 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
bruce2359 wrote: |
Any errors in the error logs?
If the last thing you see from dspmqrte is the msg being put to the transmit queue, check to see if the channel is running.
If not, check to see that the the xmit queue is triggered to start the channel. Check to see that the initiation queue is defined and available (put and get enabled). Check to see that the channel initiator app is running, and monitoring the correct init queue. |
Bruce,
Both of these queue managers are in the same cluster and both are Partial Repository. The queue manager wherE I am trying to run the dspmqrte is in both clusters and is a bridge/gateway qmgr. So everyother partial repository has a channel running to and from to this queue manager.
Therefore, channel are always running between these qmgrs. Also, for my own satisfaction, I checked the channel stautus and both clustersdr and clusterreceiver channel are running.
The only think I am wondering is whether this command DSPMQRTE work in clustered environment?
Thanks |
|
Back to top |
|
 |
bruce2359 |
Posted: Sat May 22, 2010 2:29 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
AMQ8659: DSPMQRTE command successfully put a message on queue 'QM2', queue manager 'QM1'. |
This looks to me like a private (non-cluster) channel's transmission queue. Messages going to a cluster queue go through the system cluster transmission queue, not a queue named QM2. _________________ 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 |
|
 |
jeevan |
Posted: Sat May 22, 2010 2:34 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
bruce2359 wrote: |
Quote: |
AMQ8659: DSPMQRTE command successfully put a message on queue 'QM2', queue manager 'QM1'. |
This looks to me like a private (non-cluster) channel's transmission queue. Messages going to a cluster queue go through the system cluster transmission queue, not a queue named QM2. |
Bruce,
Please read my post. the one in quote is an example in ibm site. Output of my comand is just above to this.
thanks |
|
Back to top |
|
 |
bruce2359 |
Posted: Sat May 22, 2010 3:12 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
I used the follwoing syntax:
dspmqrte -m SOURCEQM -qm DESTQM -q DESTQ -rq REPLYTOQUEUE ac -ar -ro activity [-v summary] |
Exactly what command did you type? There is a typo in the syntax you quoted. _________________ 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 |
|
 |
jeevan |
Posted: Sat May 22, 2010 5:28 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
bruce2359 wrote: |
Quote: |
I used the follwoing syntax:
dspmqrte -m SOURCEQM -qm DESTQM -q DESTQ -rq REPLYTOQUEUE ac -ar -ro activity [-v summary] |
Exactly what command did you type? There is a typo in the syntax you quoted. |
Bruce,
The typo you are referring took place when I cophy command from unix console and pasted here. I think you are referring "-" in front of ac switch. But as I said in my earlier post, my problem is not that I cannot run the command due to the syntax error but I am not getting output what I am expecting according to IBM website.
I am expecting the output in the replytoqueue as below:
Quote: |
The output that is displayed follows:
AMQ8653: DSPMQRTE command started with options '-m QM1 -q TARG.AT.QM2 -rq ACTIV.REPLY.Q
-v outline identifiers'.
AMQ8659: DSPMQRTE command successfully put a message on queue 'QM2', queue manager 'QM1'.
AMQ8674: DSPMQRTE command is now waiting for information to display.
--------------------------------------------------------------------------------
Activity:
ApplName: 'cann\output\bin\dspmqrte.exe'
Operation:
OperationType: Put
Message:
MQMD:
MsgId: X'414D51204C4152474551202020202020A3C9154220001502'
CorrelId: X'414D51204C4152474551202020202020A3C9154220001503'
QMgrName: 'QM1 '
QName: 'TARG.AT.QM2 '
ResolvedQName: 'QM2 '
RemoteQName: 'TARGET.Q '
RemoteQMgrName: 'QM2 '
--------------------------------------------------------------------------------
Activity:
ApplName: 'cann\output\bin\runmqchl.EXE'
Operation:
OperationType: Get
Message:
MQMD:
MsgId: X'414D51204C4152474551202020202020A3C9154220001505'
CorrelId: X'414D51204C4152474551202020202020A3C9154220001502'
EmbeddedMQMD:
MsgId: X'414D51204C4152474551202020202020A3C9154220001502'
CorrelId: X'414D51204C4152474551202020202020A3C9154220001503'
QMgrName: 'QM1 '
QName: 'QM2 '
ResolvedQName: 'QM2 '
Operation:
OperationType: Send
Message:
MQMD:
MsgId: X'414D51204C4152474551202020202020A3C9154220001502'
CorrelId: X'414D51204C4152474551202020202020A3C9154220001503'
QMgrName: 'QM1 '
RemoteQMgrName: 'QM2 '
ChannelName: 'QM1.TO.QM2 '
ChannelType: Sender
XmitQName: 'QM2 '
--------------------------------------------------------------------------------
AMQ8652: DSPMQRTE command has finished.
The last operation that DSPMQRTE observed was a Send, therefore the channel is running. Now we must work out why we did not receive any more activity reports from queue manager QM2 (as identified in RemoteQMgrName).
To check whether there is any activity information on the system queue, start DSPMQRTE on QM2 to try and collect more activity reports. Use the following command to start DSPMQRTE:
dspmqrte -m QM2 -q SYSTEM.ADMIN.ACTIVITY.QUEUE
-i 414D51204C4152474551202020202020A3C9154220001502 -v outline
where 414D51204C4152474551202020202020A3C9154220001502 is the MsgId of the trace-route message that was put.
DSPMQRTE then performs a sequence of MQGETs again, waiting for responses on the system activity queue related to the trace-route message with the specified identifier.
DSPMQRTE gets one more activity report, which it displays. DSPMQRTE determines that the preceding activity reports are missing, and displays a message saying this. We already know about this part of the route, however.
The output that is displayed follows:
AMQ8653: DSPMQRTE command started with options '-m QM2 -q SYSTEM.ADMIN.ACTIVITY.QUEUE
-i 414D51204C4152474551202020202020A3C915420001502 -v outline'.
AMQ8674: DSPMQRTE command is now waiting for information to display.
--------------------------------------------------------------------------------
Activity:
Activity information unavailable.
--------------------------------------------------------------------------------
Activity:
ApplName: 'cann\output\bin\AMQRMPPA.EXE'
Operation:
OperationType: Receive
QMgrName: 'QM2 '
RemoteQMgrName: 'QM1 '
ChannelName: 'QM1.TO.QM2 '
ChannelType: Receiver
Operation:
OperationType: Discard
QMgrName: 'QM2 '
QName: 'TARGET.Q '
Feedback: NotDelivered
|
please do not get confused, this is not what I am getting this is what I am expecting. This is an example I have taken from IBM website.
thanks |
|
Back to top |
|
 |
bruce2359 |
Posted: Sat May 22, 2010 6:54 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Is the destination qmgr suspended?
When you do a dis clusqmgr(*) do you see the full repository qmgr?
Did you look in the error logs to see if there were any errors? _________________ 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 May 22, 2010 8:32 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Is the clustered chl TO.QM1 running on QM2?
Can you start it manually using runmqsc?
What does the error log in QM2 say about that channel?
What does dis chs(TO.QM1) all say when run on QM2?
What does dis clusqmgr(QM1) QMID say when run on QM2?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jeevan |
Posted: Sun May 23, 2010 3:23 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
bruce2359 wrote: |
Is the destination qmgr suspended?
No.
When you do a dis clusqmgr(*) do you see the full repository qmgr?
Yes. We have process document for trouble shooting. We check channel status, qmg, log etc and act on it if there is something. We even do refresh cluster in trouble mqgr like this.
Did you look in the error logs to see if there were any errors? |
Yes or no. Initially there was none. If I sent a message from outisde of the cluster, eg connecting rfhutilc to the qmgr, I can put the message in the queue in the DEST queue manager. That means, mq is working perfectly. Also our application folks prove mq is working as they can put and get message locally.
But I can not get the message through the cluster route. That is why I am focusing the DSPMQRTE
Last edited by jeevan on Sun May 23, 2010 11:22 am; edited 1 time in total |
|
Back to top |
|
 |
jeevan |
Posted: Sun May 23, 2010 3:34 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
fjb_saper wrote: |
Is the clustered chl TO.QM1 running on QM2?
Can you start it manually using runmqsc?
What does the error log in QM2 say about that channel?
What does dis chs(TO.QM1) all say when run on QM2?
What does dis clusqmgr(QM1) QMID say when run on QM2?  |
fjb_saper,
The QM1 and QM2 mentioned in my posts are from example. Anyway, we can use them symbolically. In fact, I have used term as SOURCEQM and DEST.
In short, MQ is working fine so we want to trace route the message travel. Therefore, we wanted to get the DSPMQRTE command working because, according to IBM website, it command gives the message travel path and time taken ( i hope).
As I explaned in response other post, channel between these two PRs are running.
Last edited by jeevan on Sun May 23, 2010 6:27 am; edited 1 time in total |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun May 23, 2010 5:56 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
As to your original problem...
I have seen very slow delivery of messages on a channel in retry. (sequence number mismatch) and yes the messages were persistent.
Also can you please specify if you use message compression on the channels? If yes which version of MQ are you using? (V6.0.2.6 and V6.0.2.7 need a patch)  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jeevan |
Posted: Sun May 23, 2010 6:24 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
fjb_saper wrote: |
As to your original problem...
I have seen very slow delivery of messages on a channel in retry. (sequence number mismatch) and yes the messages were persistent.
Also can you please specify if you use message compression on the channels? If yes which version of MQ are you using? (V6.0.2.6 and V6.0.2.7 need a patch)  |
We do not use any message compression on channel. The MQ version on the SOURCEQM is 6.0.2.7 and on the DEST qmgr, the mq version is 7.0.0.0.
I know, running base code ( n.0.0.0) is not recommended. We are suspecting whether the version difference is causing some problem specially for DSPMQRTE, and I am planning to talk to IBM ( open a PMR).
FYI, with -v all, I am now getting activities report however it is displaying on the console instead of putting a message in the replgytoqueue.
The working syntax is:
dspmqrte -m SOURCEQM -qm DESTINATIONQM -q TARGETQ -rq REPLYTOQUEUE -ac -ar -ro activity -v all -d yes
I will work futher to find out any setting or parameter to make the reply message to go to the replytoqueue. |
|
Back to top |
|
 |
|