Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!ugle.unit.no!hanche
From: hanche@imf.unit.no (Harald Hanche-Olsen)
Newsgroups: comp.sys.apollo
Subject: Re: Daylight Savings Time and SR10.3
Message-ID: <HANCHE.91Mar26190916@hufsa.imf.unit.no>
Date: 26 Mar 91 18:09:16 GMT
References: <1991Mar25.202013.27817@bwdls61.bnr.ca>
Sender: news@ugle.unit.no
Organization: The Norwegian Institute of Technology, Trondheim, Norway.
Lines: 32
In-Reply-To: marmen@bwdla31.bnr.ca's message of 25 Mar 91 20:20:13 GMT

In article <1991Mar25.202013.27817@bwdls61.bnr.ca> marmen@bwdla31.bnr.ca (Rob Marmen 1532773) writes:

    I need a quick, simple answer to the following question:

    Does TZ set the timezone correctly under sr10.3?

Yes, it does for me:

# date
Tue Mar 26 19:02:26 MET 1991
# tz 2:00 MED
# date
Tue Mar 26 20:03:22 EET 1991
# tz
Timezone:       MED
Delta from UTC: 2:00

# tz 1:00 MET

    It's that time of the year again, and I was verifying that
   TZ still changed the timezone on the workstation. It does,
   but does seem to affect the output of the DATE command.

And so it should!  However, as the above example shows, the date
command apparently uses some internal table for delta -> timezone name
conversion, hence making it look like I moved to Eastern Europe just
bacause I asked for DST.  Is this the effect you were talking about?

- Harald Hanche-Olsen <hanche@imf.unit.no>
  Division of Mathematical Sciences
  The Norwegian Institute of Technology
  N-7034 Trondheim, NORWAY