| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Record timing of incoming and outgoing messages on AS400 |
« View previous topic :: View next topic » |
| Author |
Message
|
| limboonlee |
 Posted: Wed Apr 29, 2009 12:23 am Post subject: Record timing of incoming and outgoing messages on AS400 |
 |
|
Novice
Joined: 29 Apr 2009
Posts: 12
|
My user is saying that the messages that they sent to AS400 is taking a long time to return, but I could not find any evidence that the delay is at the AS400 side.
Is there a exit that I can install in my channels on AS400 (sdr and rcvr) to record the timing of messages coming and leaving these channels?
Thanks
BL |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Wed Apr 29, 2009 1:51 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
sounds like this is request - reply ? if you do a run with a single request message that will cause a reply, you can see from the channel status (last message date and time) of sender and receiver channel the time the incoming and outgoing message. it is in the form at hh:mm:ss, so it does not show very acurate when exactly the reply was sent, but it may give you an idea if there is a delay on the as400 end or not. (assuming we do not talk about very short delays here)
_________________
Regards, Butcher |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 29, 2009 3:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
We had a similar problem and opened a PMR with IBM. As we are on distributed... well it was pinpointed down to disk latency problems.
What you should do to help diagnose the problem:
MAKE SURE your requester and server hosts are time synched.
Have the server app do following:
record the time on the incoming msg (MQHD), record the time the incoming message was received (app), record the time before the put of the reply(app) and record the time after the put of the reply(app). You have then the means to check on the server side where your time is spent.
On the requester side: record the time after the put (and commit) of the request (app), record the time the reply message was sent (MQMD), record the time the reply message was received (app). This should allow you to pinpoint whether excessive time is being spent in the network.
Some message monitoring for average time spent on queue might help too.
Have fun 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
