On 2024-11-13 20:00, Keith Halewood wrote:
I believe I now have a reasonable set of VMS 7.3
patches to look through. Nothing sticks out on a cursory scan suggesting a DECnet patch
but we live in hope.
Good luck...
Failing that....
Is all of this likely to be in EVL, presumably it's the process propagating the
events?
I would basically assume that this is at least a problem on the
receiving end. When receiving the event, it will check for reasonable
values, and if it's not, it just zeroes it.
The generating side might also have checks, but we can't say for sure in
this scenario.
Any intermediate propagation would probably not do anything with the data.
One would hope that the problem is in the creation of
the 16 bit value masked to 15 bits and that its interpretation downstream will be the
full16 bit value.
I think the receiving side is definitely catching it here. But there is
a somewhat simple way to check/test.
Have an up to date RSX machine for testing. We know that this system
will do 16 bit unsigned processing. Set a sink from RSX to VMS, and see
what dates you get from that. This will tell if you VMS receiving side
is catching values and clearing the date when it's out the expected range.
Then on the VMS side, set a sink towards RSX, and see if dates come
across correctly or not in that direction. That will tell you if the
generation of events are catching values with the high bit set or not.
Johnny
K
-----Original Message-----
From: Johnny Billquist [mailto:bqt@softjar.se]
Sent: 13 November 2024 18:53
To: hecnet(a)lists.dfupdate.se
Subject: [HECnet] Re: DECnet event date/time on VAX/VMS
I would not call it a bug. It was initially defined that way. However, RSX officially
decided to start treating it as an unsigned 16-bit value with the last releases, and
documented this.
And it's a change that do make sense.
But if others have not applied the same update, then it makes sense that they would zero
the value if it have the high bit set.
Johnny
On 2024-11-13 19:26, Paul Koning wrote:
The statement in the DECnet spec that julian
half-day is 15 bits is an
obvious bug with an obvious fix; clearly RSX and others have made that
fix. VMS needs to do likewise.
paul
On Nov 13, 2024, at 12:50 PM, John Forecast
<john(a)forecast.name
<mailto:john@forecast.name>> wrote:
Depends on the implementation. Nov 9, 2021 on VMS, Ultrix and
probably some others. RSX is good until 2065.
John.
On Nov 13, 2024, at 10:24 AM, Keith Halewood
<Keith.Halewood(a)pitbulluk.org <mailto:Keith.Halewood@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
<mailto:hecnet@lists.dfupdate.se> To unsubscribe send an email
tohecnet-leave(a)lists.dfupdate.se
<mailto:hecnet-leave@lists.dfupdate.se>
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
<mailto:hecnet@lists.dfupdate.se> To unsubscribe send an email to
hecnet-leave(a)lists.dfupdate.se
<mailto:hecnet-leave@lists.dfupdate.se>
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se To unsubscribe send an
email to hecnet-leave(a)lists.dfupdate.se
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol