| Author |
Message
|
| goffinf |
 Posted: Fri Feb 03, 2006 2:18 am Post subject: Getting an accurate local time |
 |
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Using MBv6 on Windows 2003 Server.
When calling any of the datetime function in eSQL, the date always returns the correct value but time is always out by around 31 minutes !!
For example I used the following eSQL as a test :-
SET OutputRoot.XMLNSC.result.CURRENT_DATE = CURRENT_DATE;
SET OutputRoot.XMLNSC.result.CURRENT_TIME = CURRENT_TIME;
SET OutputRoot.XMLNSC.result.CURRENT_TIMESTAMP = CURRENT_TIMESTAMP;
SET OutputRoot.XMLNSC.result.CURRENT_GMTDATE = CURRENT_GMTDATE;
SET OutputRoot.XMLNSC.result.CURRENT_GMTTIME = CURRENT_GMTTIME;
SET OutputRoot.XMLNSC.result.CURRENT_GMTTIMESTAMP = CURRENT_GMTTIMESTAMP;
SET OutputRoot.XMLNSC.result.LOCAL_TIMEZONE = LOCAL_TIMEZONE;
and it produced (I added the comment at the top manually) :-
<!-- Actual dateTime = 2006-02-03 09:43:00
Date = CORRECT
Time = 31 minutes behind ??
-->
<result>
<CURRENT_DATE>2006-02-03</CURRENT_DATE>
<CURRENT_TIME>09:11:59.794868</CURRENT_TIME>
<CURRENT_TIMESTAMP>2006-02-03 09:11:59.794868</CURRENT_TIMESTAMP>
<CURRENT_GMTDATE>2006-02-03</CURRENT_GMTDATE>
<CURRENT_GMTTIME>09:11:59.794868</CURRENT_GMTTIME>
<CURRENT_GMTTIMESTAMP>2006-02-03 09:11:59.794868</CURRENT_GMTTIMESTAMP>
<LOCAL_TIMEZONE>INTERVAL '0' MINUTE</LOCAL_TIMEZONE>
</result>
The local m/c is set for Greenwich Mean Time, Dublin, Edinbugh, Lisbon, London (as can be seen from LOCAL_TIMEZONE (offset is 0))
Reginal settings for m/c are all UK.
Are there any MB specific config settings that I have missed ?
Is there something else that I am doing wrong ??
Cheers
Fraser. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Feb 03, 2006 5:15 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Moved to the correct forum.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| AndreasMartens |
| Posted: Fri Feb 03, 2006 6:41 am Post subject: Strange indeed |
|
|
Acolyte
Joined: 30 Jan 2006
Posts: 65
Location: Hursley, UK
|
This is strange indeed, could you check that "mqsiservice -t" returns the expected time, date and timezone?
In addition it is worth noting that the CURRENT_* variables in ESQL are the time upon entry into the node at runtime and are fixed through the entire duration of your ESQL execution. If your ESQL flow is heavy it could be a little off (though 31 minutes is unexpected).
If mqsiservice -t returns the expected and correct results the next step is to take a service trace of the dataflowengine.
How are you measuring the "actual time", is that the time you placed the input message on the MQ queue, the time of arrival of the message on the output queue or something else?
thanks
Andreas |
|
| Back to top |
|
|
| AndreasMartens |
| Posted: Fri Feb 03, 2006 6:45 am Post subject: Raise a PMR |
|
|
Acolyte
Joined: 30 Jan 2006
Posts: 65
Location: Hursley, UK
|
Actually, can you raise a PMR for this so we can get to the bottom of it more quickly?
Thanks  |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Dec 15, 2006 9:06 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Did you log any PMR for this problem?
It seems there is a problem with the CURRENT_TIMESTAMP function in the v6 Broker. We have a message flow which calls this function when inserting a row into the DB table. The returned timestamp is off by as much as 1-5 Hrs. The Message flow is configured to run with multiple instances. There is no impact to the Message Flow as the MF does a lookup in the DB table by CorrelID & MessageID. Some of the reports produced from this table are incorrect due to this Timestamp issue. We are now logging a PMR with IBM for this problem.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Dec 15, 2006 9:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Kirani- Are you sure that you aren't getting a timestamp in the wrong timezone?
Secondly, it's known that you won't get different time stamps within the same ESQL module invocation.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Dec 15, 2006 9:48 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
No, the timezone settings are corect. It's set to Pacific timezone.
As I mentioned earlier, the behavior is random. Sometimes it works, and sometimes it does not. FYI. We just migrated this app from Ver 2.1 to the new Broker and we are seeting this problem only on the new (V6) Broker.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
