<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Yeah man hardcore it ! :)<br><br><div dir="ltr"><div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">---</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Supratim Sanyal, W1XMT</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">QCOCAL::SANYAL via <a href="http://www.update.uu.se/~bqt/hecnet.html">HECnet</a></span></div></div><div><br></div></div><div dir="ltr"><br><blockquote type="cite">On Nov 10, 2021, at 5:24 PM, Paul Koning <paulkoning@comcast.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span></span><br><span></span><br><blockquote type="cite"><span>On Nov 10, 2021, at 5:11 PM, Supratim Sanyal <supratim@riseup.net> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On 11/10/21 9:25 AM, Paul Koning wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>I see what's going on.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>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.</span><br></blockquote></blockquote><blockquote type="cite"><span>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.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>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:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>MC NCP TELL PYRTR SHOW PAULSCOOLPING KARMA</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>and get back</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Paul's Cool Ping Summary as of 10-NOV-2021 21:40:56</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Node State Circuit Next node</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>31.2 (KARMA) Reachable VDE-31 31.1023 (IMPRTR)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>or in the format CISCO repond:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>IMPRTR>ping decnet karma</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Type escape sequence to abort.</span><br></blockquote><blockquote type="cite"><span>Sending 5, 100-byte DECnet echos to atg 0 area.node 31.2, timeout is 5 seconds:</span><br></blockquote><blockquote type="cite"><span>!!!!!</span><br></blockquote><blockquote type="cite"><span>Success rate is 100 percent (5/5), round-trip min/avg/max = 12/24/44 ms</span><br></blockquote><span></span><br><span>It's tricky. Naturally there isn't a standard NCP request, or NICE encoding for one, to ask for a Cisco DECNet ping message to be sent. It would be easy enough to add such a thing as a system-specific operation. But system specific operations are known only to that implementation. There isn't any way to ask a VMS NCP to send a RSTS-specific operation request (such as "show objects"), nor any way to send a PyDECnet-specific operation.</span><br><span></span><br><span>It would be possible to come up with a crazy kludge to do this, for example a rule that a "loop node" command where the loop data length is 4242 means send a ping instead.</span><br><span></span><br><span> paul</span><br><span></span><br><span></span><br></div></blockquote></body></html>