| Author |
Message
|
| paustin_ours |
 Posted: Tue Sep 07, 2010 12:27 pm Post subject: dspmqrte command |
 |
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
I ran the dspmqrte command and the output is of PCF format i think. How do i make sense of this output? Is there a read command that i need to run on this message output?
message format is MQHEPCF |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Sep 07, 2010 2:09 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
How to use the command is documented in the WMQ System Admin manual.
The output should be a human-readable chronology of message flow, including what MQI call, the queue, the qmgr, the channel, etc.
Post here the exact dspmqrte command you issued, and the output you received.
_________________
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 |
|
|
| paustin_ours |
| Posted: Wed Sep 08, 2010 6:43 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
command run:
dspmqrte -m test -ac -q test -rq route.ql -rqm test1 -v outline activity
I am getting 3 messages on the route.ql queue on test1 qmgr.
This is the output i am getting. It is unreadable
00000000 EPH ....`........... ....
00000032 ....$.......E...................
00000064 ............E...........0...Ð...
00000096 µ.......ebSphere MQ\bin\amqrmppa
00000128 .exe....................T...>...
00000160 µ...@...Receiving Message Channe
00000192 l Agent.........................
00000224 ................D...............
00000256 Ø...............<...µ.......2010
00000288 0908........=...µ.......14410868
00000320 ........G...............à...P...
00000352 ........H...............F...µ...
00000384 ....MD ........è...............
00000416 ç....@..........á...............
00000448 Ü...X...........Ý...............
00000480 Û..."...............ÿÿÿÿ........
00000512 Í...µ.......MQADMIN ........å...
00000544 ............ä...........(...e...
00000576 ....AMQ test (ë.L 3C.....
00000608 (...c.......AMQ test (ë.L
00000640 3C.........Ù...........D...C...
00000672 µ...0...route.ql
00000704 ....D...
00000736 D...µ...0...test1
00000768 ....
00000800 ...Ñ...µ.......mdhanikachal....
00000832 0...b... ..........`z.cÑ.bñšóÖ„K
00000864 ................4...?...µ... ...
00000896
00000928 ....................0...Ð...µ...
00000960 ....ebSphere MQ\bin\dspmqrte.exe
00000992 ........A...µ.......20100908....
00001024 ....B...µ.......14410868........
00001056 @...µ....... ....D...ß...µ...
00001088 0...test1
00001120 ....(......
00001152 µ.......to_test1 ....
00001184 ....ç...........D...á...µ...0...
00001216 test
00001248 ........D.......
00001280 ........Ø...............<...µ...
00001312 ....20100908........=...µ.......
00001344 14410868........G...............
00001376 à...P...........H...............
00001408 F...µ.......MD ........è.......
00001440 ........ç....@..........á.......
00001472 ........Ü...X...........Ý.......
00001504 ........Û..."...............ÿÿÿÿ
00001536 ........Í...µ.......MQADMIN ....
00001568 ....å...............ä...........
00001600 (...e.......AMQ test (ë.L
00001632 3C.....(...c.......AMQ test
00001664 (ë.L 3C.........Ù...........
00001696 D...C...µ...0...route.ql
00001728
00001760 ....D...D...µ...0...test1
00001792
00001824 .... ...Ñ...µ.......mdhanika
00001856 chal....0...b... ..........`z.cÑ
00001888 .bñšóÖ„K................4...?...
00001920 µ... ...
00001952 ....................0...
00001984 Ð...µ.......ebSphere MQ\bin\dspm
00002016 qrte.exe........A...µ.......2010
00002048 0908........B...µ.......14410868
00002080 ........@...µ....... ....D...
00002112 ß...µ...0...test1
00002144 ....
00002176 ....Ý...........D...à...µ...0...
00002208 test1
00002240 ........C.......
00002272 ........Ò...............Ó.......
00002304 ........é...............Õ.......
00002336 ........Ô...............Ö.......
00002368 ........ë...............×.... .. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 08, 2010 6:56 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Manual shows for -v switch:
-v summary | all | none | outline DisplayOption
summary The queues that the trace-route message was routed
through are displayed.
all All available information is displayed.
none No information is displayed.
Try this: dspmqrte -m test -ac -q test -rq route.ql -rqm test1 -v outline
_________________
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: Wed Sep 08, 2010 10:59 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| bruce2359 wrote: |
Manual shows for -v switch:
-v summary | all | none | outline DisplayOption
summary The queues that the trace-route message was routed
through are displayed.
all All available information is displayed.
none No information is displayed.
Try this: dspmqrte -m test -ac -q test -rq route.ql -rqm test1 -v outline |
I never got DSPMQRTE working. This is what I issued
./dspmqrte -m QMDSPMQRTECONNECTTO -ac -qm TARGQM -q TARGQ -rq REPLYTOQ -rqm REPLYTOQM -v outline
and followed is what I got.
AMQ8653: DSPMQRTE command started with options '-m QMDSPMQRTECONNECTTO -ac -qm TARGQM -q TARGETQ -rq REPLYTOQ -rqm REPLYTOQM -v outline'.
AMQ8659: DSPMQRTE command successfully put a message on queue 'SYSTEM.CLUSTER.TRANSMIT.QUEUE', queue manager 'XXXXXXXX'.
AMQ8674: DSPMQRTE command is now waiting for information to display.
--------------------------------------------------------------------------------
Activity:
ApplName: 'dspmqrte '
Operation:
OperationType: Put
QMgrName: 'XXXXXXXX '
QName: 'TARGQ '
ResolvedQName: 'SYSTEM.CLUSTER.TRANSMIT.QUEUE '
RemoteQName: 'TARGQ '
RemoteQMgrName: 'TARGQM '
--------------------------------------------------------------------------------
Activity:
ApplName: 'amqrmppa '
Operation:
OperationType: Get
QMgrName: 'XXXXXXXX '
QName: 'SYSTEM.CLUSTER.TRANSMIT.QUEUE '
ResolvedQName: 'SYSTEM.CLUSTER.TRANSMIT.QUEUE '
Operation:
OperationType: Send
QMgrName: 'XXXXXXXX '
RemoteQMgrName: 'TARGQM '
ChannelName: 'TO.TARGQM '
ChannelType: ClusSdr
XmitQName: 'SYSTEM.CLUSTER.TRANSMIT.QUEUE
it never reaches the target qm and target queue and I never got a reply back to my replytoq.
the reply to queue is clusterd queue. I put message from the targetqm and I can do it.
any suggestion would be appreciated |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 08, 2010 12:50 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| It never reaches the target qm and target queue and I never got a reply back to my replytoq. the reply to queue is clusterd queue. |
How do you know it never reaches the target qm and target queue?
Why are you using a clustered reply-to-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: Wed Sep 08, 2010 6:54 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| bruce2359 wrote: |
| Quote: |
| It never reaches the target qm and target queue and I never got a reply back to my replytoq. the reply to queue is clusterd queue. |
How do you know it never reaches the target qm and target queue?
Why are you using a clustered reply-to-queue? |
In an example given in IBM website, there is some activities at the target queue. Also, we should receive an activity messages in the REPLYTO queue in the REPLYTOQM but I am not getting it.
I also tried with just a local queue but did not work. So I thought it may be because the REPLYTOQ is not seen from the target queue manager as the REPLYTOQ resides on a partial repository and the TARGQM is another partial repository. But none of these work.
Last edited by jeevan on Thu Sep 09, 2010 3:05 am; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 08, 2010 7:14 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
Operation:
OperationType: Send
QMgrName: 'XXXXXXXX '
RemoteQMgrName: 'TARGQM '
ChannelName: 'TO.TARGQM '
ChannelType: ClusSdr
XmitQName: 'SYSTEM.CLUSTER.TRANSMIT.QUEUE
it never reaches the target qm and target queue |
From this it looks like it was sent across TO.TARGQM channel.
Take a look at the error logs on the target qmgr.
| Quote: |
| and I never got a reply back to my replytoq. |
The error logs there might offer some insight.
I'm confused. In your original post, you called the qmgrs test and test1; but in your last post you called them TARGQM and REPLYTOQM.
_________________
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: Wed Sep 08, 2010 9:21 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
bruce 2359,
test and test1 was the original poster - paustin_ours.
_________________
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 |
|
|
| jeevan |
| Posted: Thu Sep 09, 2010 3:02 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| exerk wrote: |
bruce 2359,
test and test1 was the original poster - paustin_ours. |
That is correct. :Please note that I have used two terms -QMDSPMQRTECONNECT and REPLYTOQM for the same queue manager where the DSPMQRTE connects to and where the activities reposrt should be received. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Sep 09, 2010 5:26 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
My mistake. I will read more carefully in the future.
_________________
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 |
|
|
| paustin_ours |
| Posted: Thu Sep 09, 2010 5:51 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
The output in my post is the message data in the reply queue. My reply queue is not clustered or anything. As you can see its unreadable.
Is that the activity report? How do i make sense out of that report?
Or are you guys looking at the command line output that you get once you run the dspmqrte command and not even worry about what lands in the reply to queue?
my command line output is the below.
C:\>dspmqrte -m test -ac -q test -rq route.ql -rqm test1 -v outline activity
AMQ8653: DSPMQRTE command started with options '-m test -ac -q test -rq route.ql
-rqm test1 -v outline activity'.
AMQ8659: DSPMQRTE command successfully put a message on queue 'test1', queue man
ager 'test'.
AMQ8657: DSPMQRTE command used MsgId 0x414D512074657374202020202020202028EB7F4C2
035FB02.
AMQ8652: DSPMQRTE command has finished. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Sep 09, 2010 6:04 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Did you try this command as I suggested? dspmqrte -m test -ac -q test -rq route.ql -rqm test1 -v outline
The output should be human-readable - like jeevan's.
_________________
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 |
|
|
| paustin_ours |
| Posted: Thu Sep 09, 2010 6:27 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
I did, 3 messages landed on the reply queue route.ql and none of them is readable.
the output on the command line after i ran the command is this:
C:\>dspmqrte -m test -ac -q test -rq route.ql -rqm test1 -v outline
AMQ8653: DSPMQRTE command started with options '-m test -ac -q test -rq route.ql
-rqm test1 -v outline'.
AMQ8659: DSPMQRTE command successfully put a message on queue 'test1', queue man
ager 'test'.
AMQ8657: DSPMQRTE command used MsgId 0x414D512074657374202020202020202028EB7F4C2
0361302.
AMQ8652: DSPMQRTE command has finished.
Am i missing something? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Sep 09, 2010 6:39 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What WMQ version/release on test qmgr? On test1 qmgr?
Are you issuing the dspmqrte on test qmgr? Or on a WMQ client platform?
Have you read the WMQ Monitoring manual. There is an entire section on dspmqrte.
_________________
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 |
|
|
|
|
