Sujet : Re: [OT] Time flies...
De : arne (at) *nospam* vajhoej.dk (Arne Vajhøj)
Groupes : comp.os.vmsDate : 10. Jan 2025, 03:36:14
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vlq12u$3l00q$1@dont-email.me>
References : 1 2 3
User-Agent : Mozilla Thunderbird
On 1/9/2025 9:00 PM, Johnny Billquist wrote:
On 2025-01-09 20:35, Stephen Hoffman wrote:
On 2025-01-08 16:21:20 +0000, Johnny Billquist said:
On 2025-01-02 14:44, Simon Clubley wrote:
BTW, it's now a little over 13 years to the end of the world...
>
For some Unix systems, yes. Not sure if that is relevant in a newsgroup for VMS...
>
I'm aware of 2038 bugs that were found and fixed within OpenVMS some years back, and there may well be others awaiting.
>
The OpenVMS Y2K evalation expressly excluded testing of 2038 and later dates, as well. Terra (or tempora) incognita.
>
If you're running production on OpenVMS for the next decade or so, boot up a test guest, and test your code and test your environment past 2038.
I can definitely see that for C code using C functions. Also, wasn't there some issue with C code in some runtime environment under VMS where times were expressed as delta times which hit a problem at 10000 days?
But apart from things centered around C one way or another, I can't see that VMS would care.
Stuff using real VMS time will obviously not have a problem.
But there are a lot of C code also on VMS. Newer applications
written within the last 25 years. Applications and platform
software ported from *nix.
I would expect it to be a 2106 problem though not a 2038
problem due to time_t being unsigned on VMS.
Arne
[OT] Time flies...
Re: [OT] Time flies...