ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » 6.1 Current_timestamp ESQL

Post new topic  Reply to topic
 6.1 Current_timestamp ESQL « View previous topic :: View next topic » 
Author Message
ChrisBUK
PostPosted: Tue Aug 11, 2009 8:28 am    Post subject: 6.1 Current_timestamp ESQL Reply with quote

Newbie

Joined: 25 Mar 2008
Posts: 8

Hi,
We have recently migrated to 6.1 and have noticed a strange occurence with ESQL current_timestamp.
I will simplify the flow but basically we have 2 flows the first inserts a record with current_timestamp and the second inserts another "version" using current_timestamp.
A message arrives at 1625 BST (local time) and the first flow inserts with a timestamp of 1525 GMT, the second flow inserts a new version correctly with 1625 BST, so we always end up with a 1 hour gap on the records.

Data looks like:-
110 11-AUG-09 15.25.27.797928000
199 11-AUG-09 15.25.27.821661000
300 11-AUG-09 16.25.27.912374000
310 11-AUG-09 16.25.28.042833000
600 11-AUG-09 16.25.28.067183000


First 2 rows are from flow 1 and the last rows are in the next flow.
Ive checked the timezone settings as much as i can and they all seem to check out (unless there are other things I can check).
But this whole behaviour just seems very odd and very consistent (its bascially happening all the time)
Has anyone seen this before or would have any ideas what else I can check?
Thanks in advance,
Chris
Back to top
View user's profile Send private message
Luke
PostPosted: Wed Aug 12, 2009 12:37 am    Post subject: Reply with quote

Centurion

Joined: 10 Nov 2008
Posts: 128
Location: UK

Hi Chris,

I have seen something similar - when one developer coded using CURRENT_TIMESTAMP and another used CURRENT_GMTTIMESTAMP ...

Are you sure you haven't somehow picked up an old version of one of the flows when you migrated? I've known similar things happen sometimes in migrations when the latest version of source has not been checked in to the repository?

Have you run a trace on both and confirmed they are using the same function and inserting the data in the same way? Assuming the flows are running on the same LPAR/server?

Cheers
Back to top
View user's profile Send private message
Luke
PostPosted: Wed Aug 12, 2009 12:52 am    Post subject: Reply with quote

Centurion

Joined: 10 Nov 2008
Posts: 128
Location: UK

Thinking about this again, the way you describe it sounds like both times are correct to me, technically speaking -

Isn't 1525 GMT and 1625 BST the same time? Perhaps you're ignoring the timezone when inserting the timestamp, or reading the timestamp. What are you inserting them in to and how are you inserting them and reading them?

Cheers
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » 6.1 Current_timestamp ESQL
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.