On Tue, 8 Nov 2016 06:25:19 -0800, Charles Mills wrote: >@John, am I correct that if they are west of Greenwich (the Americas, >basically) they've got a real problem if the TOD clock is set to local time >and they want to "make it right"? Basically, they have to let the box sit idle >for five or more hours so that actual UTC time catches up to their previous >TOD clock setting, and DB2 does not step all over itself? > >If OTOH they are in the UK or east of Greenwich (EMEA, Asia) then things are >much simpler: just set the TOC clock correctly, set the timezone, and go, >correct? > Other way around, but yes. A few years ago someone here lamented being in such a situation. I don't know whether it was ever made right.
And why does ISPF persist in keeping member timestamps in civil time? And why does a TSO TRANSMIT followed by a RECEIVE on oppsite sides of the DST boundary (I avoid the word "change"; it's a symptom of a pernicious mindset) cause the timestamp to be in error by an hour? --gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
