28 Dec
2020
28 Dec
'20
2:03 a.m.
That doesn't fully answer the question. What you see is the system log, which
presumably uses VMS time stamps. Those have a wide range. The question is what the
DECnet events would show, when encoded in the NICE protocol. If you configure it to send
events (like node reachable or circuit up) to another node, what do the timestamps look
like on that other node?
paul
On Dec 27, 2020, at 7:42 PM, Jason Brady <jr_brady
at fastmail.com> wrote:
Booted test Alpha system running OpenVMS 8.4 and set the date to 27-DEC-2022. Started
DECnet Phase IV. No errors.
From node APOLLO, no problem transferring files from the test system and displaying
network info (TELL ... SHOW EXEC, etc.).
Snippet from test system NML$SERVER.LOG:
--------------------------------------------------------
Connect request received at 27-DEC-2022 16:29:25.54
from remote process APOLLO::"0=JASON"
for object "SYS$COMMON:[SYSEXE]NML.EXE"
--------------------------------------------------------
Snippet from test system FAL$SERVER.LOG:
--------------------------------------------------------
Connect request received at 27-DEC-2022 16:26:56.85
from remote process APOLLO::"0=JASON"
for object "SYS$COMMON:[SYSEXE]FAL.EXE"
--------------------------------------------------------
Is the above satisfactory, at least for OpenVMS Alpha?
Regards,
Jason
On Sun, Dec 27, 2020, at 10:06 AM, Robert Armstrong wrote:
> > John Forecast wrote:
> >DECnet event logging for any system may fail after Nov 9th 2021.
>
> Oh, that's a much bigger deal! Do you happen to know if VMS handles this field
as unsigned?? A lot of people here are going to be bummed if VMS quits working next
fall...
>
> Bob