On Sun, 8 Feb 2009 22:21:12 -0500, David Andrews wrote: > >TOD clocks drift. Those of us without sysplex timers *have* to rely >upon SET CLOCK, which in turn sets CVTLDTO to an offset that doesn't >necessarily fall on a conventional TZ boundary. > Doesn't this leave the critical GMT incorrect?
>I sort of take your point though. So let's instead wish that the Unix >time mechanism was smart enough to (a) look at CVTLDTO, (b) look at >SYS1.PARMLIB(CLOCKxx), (c) look at the TZ environment variable, and (d) >evaluate time the same way the rest of MVS sees it. > Mightn't this cause the Unix time to go backwards for some values of the adjustment. And I repeat my earlier question: What if instead of the complexity you propose one simply fudged the content of CVTLSO, not CVTLDTO, to an offset that doesn't necessarily match the conventional leap second count? GMT would be correct; Unix times would be correct. -- gil ---------------------------------------------------------------------- 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
