On 2016-04-09, at 12:46, Alan Altmark wrote: > >> I have colleagues in Colorado, London, and Canberra, all using the >> same z/VM and z/OS systems. Only one of them can have proper "LOCAL" >> time (well, two in winter). > > In a CMS environment you're talking about "personal time zone" support so > that the guest could change its own tz offset and names. The DST changes > I see a subjunctive. Is it available? Is it planned?
> would still occur, managed by CP. > That would require CP to have encyclopedic knowledge. For example, nearly two weeks ago I set my clock *forward* one hour; one week ago my Australian colleagues set their clocks *back* one hour. > And as you suggest, CMS could move to handling time entirely on his own > without the help of CP. > Perhaps a server. Or a Shared Segment. Linux does it well: 456 $ TZ=America/Denver date; TZ=Australia/Canberra date Sat Apr 9 13:07:38 MDT 2016 Sun Apr 10 05:07:38 AEST 2016 "Register[ing] to hear about TZ changes" inecessary only for legislative action. Notification of semiannual boundaries (I avoid the word "changes"; it implies an improper paradigm) is unnecessary. Two weeks ago, something "changed" that shouldn't have, and timestamps on spool files from the week before appeared incorrect. -- gil
