| Author |
Message
|
| pandeg |
 Posted: Thu Jan 28, 2016 10:05 am Post subject: Transaction time from one qmgr to another qmrg remotely |
 |
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| Hi, I am trying to find the message transaction time from one Queue Manager to another Queue Manager connected remotely for analysis. Is there a way MQ keep track of when the message (date and time stamp) is reached to queue and when it left from the queue. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jan 28, 2016 10:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
MQ provides a lot of statistics.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jan 28, 2016 10:38 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
If you are interested in the time it takes to transmit messages across a channel, then you might google 'mq channel statistics'
_________________
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 |
|
|
| umatharani |
| Posted: Fri Jan 29, 2016 11:22 pm Post subject: |
|
|
Apprentice
Joined: 23 Oct 2008
Posts: 39
|
Real time monitoring will be helpful to better understand the performance.
* Enable MONQ on the XMITQ and then check the QTIME in dis qs.
This attribute will be helpful to understand whether the messages stay
longer in the XMITQ.
QTIME - Interval, in microseconds, between messages being put on the queue and then being destructively read.
* Enable MONCHL on the SDR channel and the check the NETTIME.
NETTIME - Amount of time, displayed in microseconds, to send a request to the remote end of the channel and receive a response. This time only measures the network time for such an operation. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Jan 30, 2016 4:14 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
And what happens to your stats when someone used the same physical link as the MQ Channel to copy a Backup down from a server?
Any figures you get will have to take into consideration things that are outside control on MQ or any of the applications using it to send or receive messages that use this channel.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| tczielke |
| Posted: Sat Jan 30, 2016 7:02 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
Activity tracing (TraceLevel=HIGH, I think) and strmqtrc tracing can record the microsecond timestamp of when a PUT and GET completed. Of course, there is overhead for running tracing that needs be understood in your nunmbers. From some of the performance testing I have done for tracing, the overhead for running tracing is usually under a millisecond per API call.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
|
|
