Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ucbvax.UUCP
Path: utzoo!linus!decvax!tektronix!ucbcad!ucbvax!root
From: root@ucbvax.UUCP
Newsgroups: fa.info-vax
Subject: VMS Time Representation and Time Zones
Message-ID: <738@ucbvax.UUCP>
Date: Fri, 9-Sep-83 09:17:32 EDT
Article-I.D.: ucbvax.738
Posted: Fri Sep  9 09:17:32 1983
Date-Received: Sat, 10-Sep-83 08:24:23 EDT
Sender: root@ucbvax.UUCP
Organization: U. C. Berkeley Computer Science
Lines: 16

From GEOFF5@SRI-CSL  Fri Sep  9 06:17:16 1983
Just wanted to let you know from the horse's mouth that the VMS time
format is indeed local time. We thought about implementing time zones,
but when you start dealing with things like time stamps on objects
(e.g., files) and viewing them from different machines in different
time zones (or transporting a disk from one time zone to another),
things can get very confusing and hairy. We finally decided that the best
solution was to keep it simple and run the system in local time, and
have everyone understand what was going on. Or, you can run your
system(s) on GMT and really understand what's going on.

By the way, the 64 bit clock isn't really hardware. It's just a quadword
in the exec that gets updated by the clock interrupt service routine,
which drives off the machine's interval timer. While the format has
100ns resolution, it only gets updated at 100hz.
   --------