9 Dec
2021
9 Dec
'21
2:44 a.m.
On Dec 8, 2021, at 5:32 PM, Johnny Billquist <bqt
at softjar.se> wrote:
While I'm sure there were various Y2K bugs around, the basic design in VMS was
intended from day 0 to handle dates beyond Y2K.
So I would just try to set the correct date to start with, and if something seriously
breaks, then I would consider shifting it back to an earlier year.
Oh... I set the time and date when prompted during the installations, and then when the
system time displayed as 1982, I assumed it was not Y2K capable. So I tried setting the
time after booting:
$ show time
8-DEC-1982 17:39:46
$ set time=08-DEC-2021:17:40
$ show time
8-DEC-2021 17:40:02
And then after rebooting:
VAX/VMS Version V3.0 26-APR-1982 16:21
%OPCOM, 8-DEC-2021 17:42:34.01, logfile initialized by operator OPA0
logfile is SYS$MANAGER:OPERATOR.LOG
Login quotas - Interactive limit=64, Current interactive value=0
SYSTEM job terminated at 8-DEC-2021 17:42:35.06
Username: SYSTEM
Password:
Welcome to VAX/VMS version V3.0
$ show time
8-DEC-2021 17:42:53
How about that!
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/