> Other way around, but yes Ah! You are right, aren't you? I find time differences confusing (obviously, LOL).
My hypothetical mainframe is here in California. Local time is 8:02 am. UTC is 16:02. So I can set the HMC clock to UTC and except for losing eight hours out of its life, DB2 is good. If it's in Europe I would have to power down and wait, but fortunately for most of Europe the difference is only one hour, not five or more. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Tuesday, November 08, 2016 6:57 AM To: [email protected] Subject: Re: Time Change Problem #1398 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. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
