In a recent note, McKown, John said: > Date: Wed, 15 Jun 2005 15:09:27 -0500 > > The TOD clock must only advance, never stay still or retreat. The local > time can rumba back and forth all it wants without causing any problems > to any __advanced__ software. IMS, DB2, and CICS/TS can all endure the > LOCAL clock going backwards. It confuses the <elided> out of the users, > but who cares? > Won't all these schemes to adjust only the LOCAL time leave the system in a the TIME macro returns an incorrect value for GMT, and the perceived difference between LOCAL and GMT differs from the canonical value for your geographic location? In particular, is the value returned by the UNIX time() function likely to be incorrect?
Wouldn't it be better to adjust the Leap Second offset, rather than the local time offset? This would cause the TIME macro to return correct and consistent values for both GMT and LOCAL time. Does anyone care about the offset between IAT and GMT, particularly since IBM has defined the TOD clock to run 10 seconds behind IAT? -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
