RE: Zulu Time (was: Who else was awake at 2am this Sunday babysitting thetime change???)

I think that is the plan....  The system will at some point store all date-time 
types as GMT (UTC 0), but will apply either *sys or *jobd UTC offsets to the 
dates as they are retrieved/stored.  At this point, each job could run under 
its own UTC offset, allowing users in different timezones to see their correct 
time in their jobs.  


Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Tom Jedrzejewicz
Sent: Monday, October 30, 2006 10:38 AM
To: Midrange Systems Technical Discussion
Subject: Zulu Time (was: Who else was awake at 2am this Sunday
babysitting thetime change???)


On 10/30/06, Holder, Ken <kkh@xxxxxxxxxxxxx> wrote:

Or even better (holding my breath) if we got ride of DST altogether
(turning purple). OK (breathing again) not going to happen anytime soon.

Actually, as this discussion went on in various forms over the last few
weeks, I started to wonder why the "local" time  is used at all.  I would
think that every system should keep a standard time (i.e.Zulu
time<http://en.wikipedia.org/wiki/Coordinated_Universal_Time>)
and present it in local time.

I would think this would be particularly useful for messaging systems, such
as MQ.

Any thoughts or comments?