Sujet : Re: Upcoming time boundary events
De : arne (at) *nospam* vajhoej.dk (Arne Vajhøj)
Groupes : comp.os.vmsDate : 19. May 2025, 20:19:57
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <100g08t$1oqob$1@dont-email.me>
References : 1
User-Agent : Mozilla Thunderbird
On 5/19/2025 1:18 PM, Simon Clubley wrote:
I realised that today is exactly 28 years since the 10,000 day
issue in VMS. I am starting to feel old. :-(
On a more serious note, I wonder what upcoming time boundaries
we are about to hit.
The obvious one is 2038, but I also wonder how many had 2030 as
their Y2K pivot point.
Any others you know of (both VMS and non-VMS) ?
30 years before 32 bit signed seconds since 1970 => 18-Jan-2008
10 years before 32 bit signed seconds since 1970 => 18-Jan-2028
32 bit signed seconds since 1970 => 18-Jan-2038
split 2 digits year to support 1950-2049 (*) => 01-Jan-2050
30 years before 32 bit unsigned seconds since 1970 => 07-Feb-2076
10 years before 32 bit unsigned seconds since 1970 => 07-Feb-2096
32 bit unsigned seconds since 1970 => 07-Feb-2106
everything is going to have issues at Y10K
all common 64 bit times should first break after Y10K (**)
*) Common in many databases, but it is usually configurable,
so it can be changed to like 1970-2069 when needed.
**) But in order: Windows file time, VMS time, milliseconds
since 1970, seconds since 1970.
Arne