On Thu, 2005-11-10 at 08:31 -0500, Charles Mills wrote:
> I'm engaged in an internal dispute about best practice for the TOD clock:
> should it be set to universal time (or whatever GMT is now called) with the
> appropriate local offset, or alternatively, to local time (with an offset of
> zero)?
Yes, definitely set it to GMT. This makes semiannual DST changes a
snap. And your Unix environment wants GMT.
===
Slightly OT but an interesting thing I just noticed: our MVS console
reports the following time in response to a "D T" command:
IEE136I LOCAL: TIME=08.46.20 DATE=2005.314 GMT: TIME=13.44.27
DATE=2005.314
We're in the U.S. eastern time zone, five hours offset from GMT. You'll
notice that my local time isn't exactly five hours offset from the TOD
clock -- this is because the TOD clock drifts over time (we don't have
an ETR) and we adjust the local offset every week to compensate.
I just noticed that in a Unix shell, the time is apparently derived as a
hardcoded five-hour offset from the TOD clock:
# date
Thu Nov 10 08:44:27 EST 2005
So it ~appears~ that the Unix environment (or at least the "date"
command) doesn't use the CVTTZ (or CVTLDTO) offset.
Maybe this is aparable? Or do I have a configuration error?
--
David Andrews
A. Duda and Sons, Inc.
[EMAIL PROTECTED]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
