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.
>
Kind of like:
https://en.wikipedia.
TOD Clock Service
The time-of-day (TOD) clock service provides a caller, including your
exit routine,
with a TOD clock image. In the clock image, bit 0 is set on to allow
the service to
handle values from May 11,1971, at 11:56:53.685248 to January 25,
2114, at
11:50:41.055743.
On Fri, 28 Dec 2018 21:57:43 -0600, Joe Monk wrote:
>>"By my arithmetic, January 1, 1900 + 143 years = January 1, 2043".
>
>Ummm ... Did you forget the year 1900? Theres only 142 years left after you
>subtract the Year 1900.
>
WTF!?
So, by that reasoning, January 1, 1900 + 1 year = January 1, 19
"By my arithmetic, January 1, 1900 + 143 years = January 1, 2043".
Ummm ... Did you forget the year 1900? Theres only 142 years left after you
subtract the Year 1900.
"How are those bits numbered? 0 to 103? What's the value of bit 0? What's
the value of bit 103?"
Yes, 0 to 103. Bit 51 is inc
On Fri, 28 Dec 2018 18:18:51 -0600, Joe Monk wrote:
>So if you read the POO, you see:
>
> - Communication between systems is facilitated by establishing a
> standard time origin that is the calendar date and time to which a clock
> value of zero corresponds. January 1, 1900, 0 a.m. Coordinat
So if you read the POO, you see:
- Communication between systems is facilitated by establishing a
standard time origin that is the calendar date and time to which a clock
value of zero corresponds. January 1, 1900, 0 a.m. Coordinated Universal
Time (UTC) is recommended as this origin,
