13 Nov
2024
13 Nov
'24
6:31 p.m.
The problem is in the network management spec. From the Phase IV spec, an event message
contains an "event time" encoded as follows:
EVENT TIME Is the source node date and time of event
processing. Consists of:
JULIAN SECOND MILLISECOND
HALF DAY
where:
JULIAN HALF DAY (2) : B Number of half days
since 1 Jan 1977 and
before 9 Nov 2021
(0-32767). For
example, the morning
of Jan 1, 1977 is 0.
SECOND (2) : B Second within current
half day (0-43199).
MILLISECOND (2) : B Millisecond within
current second
(0-999). If not
supported, high order
bit is set, remainder
are clear, and field
is not printed when
formatted for output.
Note "before 9 Nov 2021". The obvious fix is to disregard the
"0-32767" comment, which tells us to treat it as a 15-bit value, and make it 16
bits instead. I did that in DECnet/E, and in PyDECnet. I suspect VMS could be patched to
do the analogous fix, but I have no idea how to do that.
paul
On Nov 13, 2024, at 10:24 AM, Keith Halewood
<Keith.Halewood(a)pitbulluk.org> wrote:
Hi,
It has been mentioned elsewhere and maybe a while back too but I’m not quite sure when
DECnet (VAX/VMS 7.3) started serving up jewels like:
%%%%%%%%%%% OPCOM 13-NOV-2024 15:15:13.82 %%%%%%%%%%%
Message from user DECNET on TUPILE
DECnet event 4.10, circuit up
From node 29.109 (TUPILE), 1-JAN-1977 00:00:53.64
Circuit UNA-0
Regards
Keith
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se