It has been on GMT for a couple decades. Still, it took an IPL before 1.7 when SET TIMEZONE became available.
The further question isn't so much semi-annual changes as it is clock drift. Takes a POR to fix that. And yah, maybe used sysplex timers are getting cheap. Cheap is not free, which is what NTP is for any other box. Some may have noticed a recession going on. Currently, we need approval from the Governor! To spend $5K or more. Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Robert A. Rosenberg > Sent: Thursday, March 12, 2009 10:49 PM > To: [email protected] > Subject: Re: Time Change (Sync) > > At 14:29 -0700 on 03/12/2009, Gibney, Dave wrote about Re: Time Change > (Sync): > > > Clocks are a different story. Twice a year I have to take the sh*t > >about how hard or expensive it is to have our z9 in sync with the rest > >of the world. > > Why is your CPU clock not set to GMT/UT? That would insure that there > is no need to reset the clock - Just update the local time offset > twice a year. So long as time stamps are in GMT, the DST/ST switches > should not affect anything important. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
