| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| dspmqrte did NOT display the activity report on remote QM |
« View previous topic :: View next topic » |
| Author |
Message
|
| wangr |
 Posted: Wed Jun 19, 2013 7:44 pm Post subject: dspmqrte did NOT display the activity report on remote QM |
 |
|
Newbie
Joined: 19 Jun 2013
Posts: 5
|
I would like to test how dspmqrte works. In order to do this, I choose a working example of a typical distibuted MQ environment, like this:
messages are sent to QM1 and finally reaches QM2 (sender -> receiver).
I can successfully do this by put a message to the remote queue on QM1 and I can see the messages reaches the corresponding remote queue on QM2. Fairly straight forward.
However, when I use the dspmqrte -q remoteQ -m QM1 -v outline, I can only see the activity report on QM1 (like how remoteQ is resolved to local XmitQ and send to QM2 through a sender channel)
the issue is, there is no activity report on QM2. Nothing is displayed about QM2. As per IBM docs, activity report on QM2 should also be displayed. Could anyone help to advise how I can also get that on QM2?
Thanks. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jun 19, 2013 9:06 pm Post subject: Re: dspmqrte did NOT display the activity report on remote Q |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wangr wrote: |
I would like to test how dspmqrte works. In order to do this, I choose a working example of a typical distibuted MQ environment, like this:
messages are sent to QM1 and finally reaches QM2 (sender -> receiver).
I can successfully do this by put a message to the remote queue on QM1 and I can see the messages reaches the corresponding remote queue on QM2. Fairly straight forward.
However, when I use the dspmqrte -q remoteQ -m QM1 -v outline, I can only see the activity report on QM1 (like how remoteQ is resolved to local XmitQ and send to QM2 through a sender channel)
the issue is, there is no activity report on QM2. Nothing is displayed about QM2. As per IBM docs, activity report on QM2 should also be displayed. Could anyone help to advise how I can also get that on QM2?
Thanks. |
Does QM2 have a DEFAULT path back to QM1? This is a must for the results to be reported back to QM1... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wangr |
| Posted: Thu Jun 20, 2013 11:29 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2013
Posts: 5
|
Thanks for the quick feedback, fjb_saper! (May I call like this?)
I thought the reply from QM2 will be covered by MQ automatically (through tcp/ip connection). If not, does that mean the trace route message will go through mq level (channels and queues)? If so, then I have to configure on QM2 so that trace route messages can flow back to QM1? I'm not sure how. Could you shed the light?
Note I do have two way communications between QM1 and QM2, but that's for application communication...
Thanks again. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 20, 2013 12:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| wangr wrote: |
| I thought the reply from QM2 will be covered by MQ automatically (through tcp/ip connection). |
How would WMQ know the address of the sender except in terms of the WMQ information? 
| wangr wrote: |
| If not, does that mean the trace route message will go through mq level (channels and queues)? |
Oddly IBM's principle communication product uses it's own communication methods to communicate. Go figure.
| wangr wrote: |
| If so, then I have to configure on QM2 so that trace route messages can flow back to QM1? |
As my most worthy associate has already said.
| wangr wrote: |
I'm not sure how. Could you shed the light?
Note I do have two way communications between QM1 and QM2, but that's for application communication... |
These 2 statements are at variance. There's no difference between communication between queue managers for applications and for this kind of system traffic. The only part you're missing is that there must be a default route between them, which could (and in a simple toplogy should) be the only route. It's fairly advanced to have more than 1 route between 2 queue managers & there are a limited number of occassions you'd do it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 20, 2013 1:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wangr wrote: |
So, then I have to configure on QM2 so that trace route messages can flow back to QM1? I'm not sure how. Could you shed the light?
Thanks again. |
The intercommunications manual tells you all about it. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wangr |
| Posted: Fri Jun 21, 2013 11:49 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2013
Posts: 5
|
Thanks for the valuable advise from user fjb_saper and Vitor! Now the issue is resolved. The following is the how:
First to be clear about "dspmqrte".
dspmqrte, which is like any other mq utilities, is just an MQ application, except making a mark of "recording operations" in the message header when it puts trace-route message, which indicates the different mq components (like MCA and channel initiator) to report their activities when they begin to process the "trace-route" message.
Regarding to this: what I did is just to define a reply-to queue in the sender of QM1, and then define whatever needed for QM2 to send back the message to QM1. In this case, the name "QM1", which appears in the header of the message, needs to be resolved so that QM2 knows how to reply (this means you need to define an alias of it and associated the alias with a transmission queue and corresponding channels (from QM2 to QM1). After this, the message should be replied back to QM1 and consumed by dspmqrte app, therefore the MQ activities on QM2 can be displayed.
Back to my issues at first (which I didn't specify a reply-to queue), I guess dspmqrte will choose a default reply-to queue on both QM1 and QM2. However, since QM2 has no idea of how to send back the message to QM1, therefore only the reports on QM1 can be displayed. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jun 21, 2013 12:40 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| wangr wrote: |
| Back to my issues at first (which I didn't specify a reply-to queue), I guess dspmqrte will choose a default reply-to queue on both QM1 and QM2. |
No. The name of the reply-to-queue is selected on the qmgr where you run dspmqrte. By default, the QM1 qmgr will insert its own name in the reply-to-qmgr field. There will need to be an xmit queue, likely named QM1, on QM2 for messages to flow from QM2 to QM1.
| wangr wrote: |
| However, since QM2 has no idea of how to send back the message to QM1, therefore only the reports on QM1 can be displayed. |
QM2 only knows of objects explicitly defined on it. Software doesn't "know" anything.
_________________
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.
Last edited by bruce2359 on Sat Jun 22, 2013 5:06 am; edited 1 time in total |
|
| Back to top |
|
|
| wangr |
| Posted: Fri Jun 21, 2013 6:25 pm Post subject: |
|
|
Newbie
Joined: 19 Jun 2013
Posts: 5
|
sounds reasonable.
thanks |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Jun 26, 2013 11:46 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| You will be far better served to use an alias Qmgr named QM1 at QM2 with an XMITQ of your choosing (QM1.XMITQ seems likely). Why, because you can put the alias Qmgr in an MQ Cluster so everybody in the cluster knows a route to QM1... And you can even make more then one route, but the reasons why are complex and only interesting to those in need of it. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
