10 Nov
2021
10 Nov
'21
11:11 p.m.
On 11/10/21 9:25 AM, Paul Koning wrote:
I see what's going on.
You have the original Evtlog. ?That time stamp is from the logger, not
FAL (it generates the event but the OS puts on the timestamp and
evtlog processes it). ?The 2034 date is what evtlog as shipped would
do. ?The patched version I created fixes it for dates after 2003. ?But
the fix is incomplete, it fails to handle Julian halfdate values with
the upper bit set.
Thanks Paul, understood. I realized it's the logger after sending the
email. I will patch RST101 with Tony's copy on DINGO. Thanks Tony too
for hosting it. Anyway looks like it is limited to logger messages,
RSTS/E itself happily stays on air.
Off-topic - Paul, do you think DECnet/Python might be made to have a
unique feature whereby I could do something like this from OpenVMS 7.3:
*MC NCP TELL PYRTR SHOW PAULSCOOLPING KARMA
*
and get back
*Paul's Cool Ping Summary as of 10-NOV-2021 21:40:56
??? Node?????????? State????? Circuit???? Next node
31.2 (KARMA)?????? Reachable? VDE-31????? 31.1023 (IMPRTR)
*
or in the format CISCO repond:
*IMPRTR>ping decnet karma
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 31.2, timeout is 5
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/24/44 ms
IMPRTR>
*
The problem is I can check if a CISCO is alive using the following DCL
kludge, but this is UGLY! (I use this in places like
http://sanyalnet-openvms-vax.freeddns.org:82/sanyalnet-labs-decnet-node-sta…
)
*$ WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML "<table
border=""1""><caption>SANYALnet Labs: Node Reachability over
DECn
et</caption>"
$ NEXT = 0
$ LOOP:
$?? NODE = F$ELEMENT(NEXT,",",NODELIST)
$?? IF (NODE .NES. ",")
$?? THEN
$?????? ! TRY A LOOP; IF RESULT IS ANYTHING EXCEPT
"%SYSTEM-F-UNREACHABLE" ASSUME NODE IS REACHABLE
$?????? PIPE (NCP LOOP NODE 'NODE') | SEARCH SYS$INPUT
"%SYSTEM-F-UNREACHABLE"
$?????? NCPSTAT=$STATUS? ! SEARCH RESULT: %X10000001 = SUCCESS,
%X18D78053 = FAILED
$?????? IF NCPSTAT .EQ. %X10000001? ! NODE IS UNREACHABLE
$?????? THEN
$?????????? WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML "<tr><td
bgcolor=""red""> </td>"
$?????????? WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML
"<td><strong><pre><a
target=""_blank"" href=""http://mim.update
.uu.se/hecnod?node=''NODE'"">''NODE'
»</a></pre></strong></td>"
$?????????? WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML "<td
bgcolor=""red""><font
color=""white""><pre>"
$?????????? DEFINE/USER SYS$OUTPUT FD_OUTPUTHTML ! Valid for only next
image execution
$?????????? NCP SHOW NODE 'NODE'
$?????????? WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML
"</pre><br><pre>%SYSTEM-F-UNREACHABLE, remote node is not curre
ntly reachable</pre></font></td></tr>"
$?????? ELSE ! IS REACHABLE
$?????????? WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML "<tr><td
bgcolor=""#55ff55""> </td>"
$?????????? WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML
"<td><strong><pre><a
target=""_blank"" href=""http://mim.update
.uu.se/hecnod?node=''NODE'"">''NODE'
»</a></pre></strong></td>"
$?????????? WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML "<td
bgcolor=""#55ff55""><pre>"
$?????????? DEFINE/USER SYS$OUTPUT FD_OUTPUTHTML ! Valid for only next
image execution
$?????????? NCP SHOW NODE 'NODE'
$?????????? DEFINE/USER SYS$OUTPUT FD_OUTPUTHTML ! Valid for only next
image execution
$?????????? NCP TELL 'NODE' SHOW EXECUTOR SUMMARY
$?????????? DEFINE/USER SYS$OUTPUT FD_OUTPUTHTML ! Valid for only next
image execution
$?????????? NCP SHOW NODE 'NODE' COUNTERS
$?????????? WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML
"</pre></td></tr>"
$?????? ENDIF
$?????? NEXT = NEXT + 1
$?????? GOTO LOOP
$?? ENDIF
$ WRITE/ERROR=ERR_EXIT FD_OUTPUTHTML "</table>"*
Regards,
/s.
paul
--
On Nov 10, 2021, at 9:16 AM, Supratim Sanyal
<supratim at riseup.net> wrote:
On 11/10/21 9:01 AM, Paul Koning wrote:
Curious. ?And you're running those with the
actual time, not a date
in the past?
FAL says "27-Oct-34", show date looks correct (assuming not 1921).
Event type 33.0, Remote file access
Occurred 27-Oct-34 14:11:53.7 on node 31.28 (RST101)
Access: Local
Function: OPEN/Read
Remote node = 0 (RST101)
Remote process = 0 1 2 NFT002
Local process = 17 50 1 FAL006
User = 50,1
File accessed = 1 SY:[50,1]INFO.TXT
$
$
$
$ show date
? 10-Nov-21 02:12 PM
I wonder if the copy of DECnet I have is from
before some patches
that fix some of these issues.
paul
--
<SANYALNET-LABS-QR-CODE.png> On Nov 10, 2021, at 6:47 AM, Supratim Sanyal
<supratim at riseup.net>
wrote:
On 11/10/21 5:14 AM, Keith Halewood wrote:
> I?m running RSTS/E 10.1-L out of the box so to speak. I?m not
> seeing any error messages.
No such errors on 31.28 (RST101) either.
/s.
> Keith
> *From:*owner-hecnet at Update.UU.SE[mailto:owner-hecnet at Update.UU.SE]*On
> Behalf Of*Tony Nicholson
> *Sent:*10 November 2021 08:46
> *To:*hecnet at update.uu.se
> *Subject:*Re: [HECnet] RSTS/E started emitting "?EVTLOG (BLDNIC)
> -- %Integer error" messages
> Paul Koning is working on a fix.
> The RSTS/E DECnet event logger has an integer overflow too.? He
> said in a e-mail to me -
> ??I think I found the problem, yes it's a signed overflow.? The
> "julian halfdays" used in the event log timestamp overflows on
> 10-Nov-2021.? I fixed an unsigned issue in the INPUT to the
> function that converts RSTS date to julian halfday, but I didn't
> notice the unsigned issue in the formula for the output.?
> Tony
> On Wed, 10 Nov 2021 at 19:14, Wilm Boerhout <wboerhout at gmail.com>
> wrote:
>
> I am receiving the same messages on the console since today. I
> am running the ?latest? DECnet images that I picked up in July
> 2020.
>
> --
> Tony Nicholson <tony.nicholson at computer.org>
--
<SANYALNET-LABS-QR-CODE.png>