| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| PUT date/time |
« View previous topic :: View next topic » |
| Author |
Message
|
| George Carey |
 Posted: Thu Aug 05, 2010 2:24 pm Post subject: PUT date/time |
 |
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
I would like to get a quick check from anyone on what the PUT date/time is in the MQ explorer column heading of same.
Is that the origin context Put Data/time (original application put Date/Time I believe carried in the XQH info) if carried across a sdr/rcvr channel or is it the actual Date/time put onto the target queue( MQMD info). I need the later(actual time it was put onto destination queue).
The heading I am referring to is seen when you do a browse on a message queue.
(may have to do empirical check when I can)
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Aug 05, 2010 2:50 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Two issues here.
At mqput, the qmgr inserts date/time in the app-created mqmd as the message is put to the local queue.
If the message is destined for an xmit queue, the original message (mqmd and app data) is encapsulated (cool term), with a new mqmd and routing data (dest qmgr, dest q).
When ultimately deployed to the destination queue (or dlq) the encapsulating mqmd is removed.
_________________
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 |
|
|
| gbaddeley |
| Posted: Thu Aug 05, 2010 3:31 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
The MQMD PutDate / PutTime is when the originating application first put the message. That's the only date / time available to the consuming application.
_________________
Glenn |
|
| Back to top |
|
|
| George Carey |
| Posted: Thu Aug 05, 2010 5:06 pm Post subject: OK MQ explorer |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Ok, then the PUT date/time heading then in the MQ Explorer panel when one browses messages is the original application Put date/time???
Is that what you are saying, I believe?
So no way to see the actual date and time stamp of when a message gets stuffed onto a final destination target queue if it was coming from another MQ server and was stuck on a xmit queue for some hours and finally got to the target queue hours later than the originating application Put it.
Your saying then the MQ Explorer still would show the originating application's Put Date/time on the MQ Explorer message browse view?
And, thus one wouldn't know if the message came immediately across the channel or was as I say stuck for an hour or more before coming across?
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Aug 05, 2010 5:49 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Your saying then the MQ Explorer still would show the originating application's Put Date/time on the MQ Explorer message browse view? |
Yes. There is only one date/time in the md, and it is that of the originating apps mqput to the xmit queue.
I've seen a few apps that use date/time of the originating (request) message for validity (of the transaction), rather than specifying expiry - and dealing with report messages.
_________________
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 |
|
|
| PeterPotkay |
| Posted: Sat Aug 07, 2010 10:36 am Post subject: Re: OK MQ explorer |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| George Carey wrote: |
Your saying then the MQ Explorer still would show the originating application's Put Date/time on the MQ Explorer message browse view?
And, thus one wouldn't know if the message came immediately across the channel or was as I say stuck for an hour or more before coming across? |
If you know the Expiry value on the original put and you capture its value on the get you can perhaps make some assumptions.
The put time in the MQMD can be completely bogus because its possible the putting side has authority to set it them selves and if so who knows if the value they entered is correct.
We use MQ API exists to capture the actual times.
It would be neat if the messages had an extra set of administrative properties that carried actual put/get times, although the overhead, particularly for small messages, may not make that feasible.
The LastPutTime attribute of the queue may also be of interest to you.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
