On Sat, 25 Oct 2025 08:58:47 -0500, Jon Perryman wrote: >On Fri, 24 Oct 2025 16:01:50 -0500, Paul Gilmartin wrote: > >>This problem was solved long ago: <https://www.iana.org/time-zones> >>Inexplicably, IBM shuns that solution, almost pervasive elsewhere. NIH? > >IANA solution does not solve the time change problem (DST nor ST). > >Unix & Windows completely ignore the implications of that hour change. These >machines are so much slower where an hour time change goes unnoticed. A single >z/OS is many times more active and SYSPLEX makes this far more complex. > WTF‽ I know no processor, back through Babbage's difference engines, "so much slower where an hour time change goes unnoticed."
IANA solution does solve the time "change" problem. I know my desktop and I'm confident my mobile systems rely on IANA. I am displaying a world Clock.app on each, both displaying local time and UTC. I'm confident they will continue to do so before, during, and after that critical hour. There will be no system disruptions nor duplicate or anachronistic timestamps. A paradigm shift is necessary. Nothing changes, neither system control blocks nor code. at 02:00 on that Sunday morning. Rather there is a subroutine which, given as inputs a system clock value and a timezone yields identical result for identical input regardless when it is called. z/OS should awaken to this fact, well known everywhere else in the IT world, -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
