[Info-vax] SYS$TIMEZONE.DAT
Stephen Hoffman
seaohveh at hoffmanlabs.invalid
Mon Mar 16 10:52:46 EDT 2015
On 2015-03-16 10:15:06 +0000, Paul Sture said:
> Hoff alluded to this the other day in his mention of how VMS handles
> time zones and what happens at a daylight saving time change. This is
> a much deeper problem for VMS.
Technically, all members of a cluster must be configured to use the
same timezone. Probably technically also configured for the same DST
settings, too. That's AFAIK the only constraint. Beyond that, the
further skewed the time is across the cluster, the more problems
there'll be. Beyond Paul's reference to batch-related problems,
DECset CMS will start reporting errors at ~30 seconds of skew, for
instance. Logs and audits become increasingly difficult to match up,
and folks that erroneously used a localtime timestamp as an increasing
serial number will have issues with cluster shared files beyond the
mess DST causes, obviously. It would not surprise me that there are
additional issues that will arise with larger skews and with specific
products.
--
Pure Personal Opinion | HoffmanLabs LLC
More information about the Info-vax
mailing list