Back in the PROFS days I supported a system that lived in Boulder but supported 
sales across the country.   We had a small CP/directory mod that gave each user 
their local timezones (just the  4 US zones at the time).   It seems that sales 
types couldn't handle their PROFS clock not being right....

Lee Stewart ● VM System Support ● Visa ● Phone:  6(750)4601 - +1-303-389-4601 ● 
[email protected]

-----Original Message-----
From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On 
Behalf Of Alan Altmark
Sent: Saturday, April 09, 2016 9:35 PM
To: [email protected]
Subject: Re: [CMS-PIPELINES] About DELAY after SET TIMEZONE

On Saturday, 04/09/2016 at 07:19 GMT, Paul Gilmartin <[email protected]> 
wrote:
> On 2016-04-09, at 12:46, Alan Altmark wrote:
> > 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?

It is neither available nor planned.  It is simply the name of the line item 
that would, if implemented, enable each virtual machine to set it's own 
timezone as it relates to the response from DIAGNOSE 0x00.  It was 
conceptualized back in VM/SP and the Days of PROFS and OfficeVision. Turns out 
the customers haven't been particularly hungry for the support. 

> > would still occur, managed by CP.
> >
> That would require CP to have encyclopedic knowledge.

No, it just means that you could set the virtual machine time zone to an 
arbitrary name and offset.

> "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.

Let's not split hairs.  While the wetware can savor the subtle difference 
between "change" and "cross" vis a vis a named boundary, the machine cannot.  
It just knows that the TZ name of UTC offset have been changed, for good or ill.

Alan Altmark

Senior Managing z/VM and Linux Consultant Lab Services System z Delivery 
Practice IBM Systems & Technology Group ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
[email protected]
IBM Endicott

Reply via email to