SA22-7832-11 (z14 level of Principles of Operation) explains how the TOD clock and clock comparator deal with the next epoch.
I can't say what the z/OS services will do, because we haven't worked on that yet. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" <[email protected]> wrote on 12/29/2018 12:36:14 PM: > From: "Paul Gilmartin" <[email protected]> > To: [email protected] > Date: 12/29/2018 01:53 PM > Subject: Clock Windowing (was: BLSUXTOD) > Sent by: "IBM Mainframe Discussion List" <[email protected]> > > On Sat, 29 Dec 2018 11:54:48 -0500, Peter Relson wrote: > > ... > >What this is likely trying (but failing) to say is that this service > >applies a windowing technique, which much of z/OS will do in the coming > >years, as we approach the end of the standard epoch. > > > I forgot to ask: > > How will this play with the comparator register? Presumably no problem unless > the interval spans epochs. Or will the comparator assume a sliding window, > always current time ± 71 years? But what of programmers who code > x'FFFF...' to mean "never (well, hardly ever)" or x'0000...' to mean > "immediately"? > > https://en.wikipedia.org/wiki/Maya_calendar#Long_Count > > -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
