X-no-Archive:yes
I'll chime on with my position: we too have users in different time zones,
so we would like the time they see to be local time, but they also use
different accounts, so we aren't too worried about different users seeing
the wrong time for the same thing. Since the 3000 keeps local time and
calculates Universal / Greenwich Mean / Zulu Time (which is fine with me),
it could hurt to have to do additional calculations to adjust from the clock
time on one coast to the apparent time on another. But I would like to be
able to set this with variables somehow on the box, so that it all works
out, with the underlying reality preserved, not unlike the way NT kinda
sorta does. Whether those are tied SETVARs in UDCs at their various levels
or whatever, I don't really much care.

> -----Original Message-----
> From: Simpkins, Terry [SMTP:[log in to unmask]]
> Sent: Saturday, December 19, 1998 10:33 AM
> To:   [log in to unmask]
> Subject:      Utilities like HourGlass, TimeMachine, etc.
>
        <snip>
> We run a single HP3000 production machine that provides computing resource
> (MANMAN) for
> numerous manufacturing locations (8 and growing) around the world.  These
> plants are
> (naturally) in various time zones.  Each plant would like to see their
> transactions posted
> (and reported) in the local time, instead of Eastern Standard/Daylight
> Time.
        <snip>