[HECnet] Configuring py-decnet --> patches

Fri Sep 4 13:52:45 PDT 2020

Pretty nifty, so I tried it and got up to 1.500 (HYUNA) before it failed 
with a read error (see below).  However, I strongly suspect that this is 
how the KLH10 NI implementation is functioning, not Tops-20 or RSX.

What did you see on MIM?  A time out?  You can tell me about the bug off 
list; sounds like fun.

NCP>telL mim:: shoW knoWN noDES
NCP>
15:49:53     NCP
         Request # 44 Accepted
NCP>
15:50:07     NCP

Request # 44; Show Known Nodes Summary Completed

Executor Node = 1.13 (MIM)

   State = On
   Identification = "RSX system at Update, Sweden"

       Node       State       Active  Delay  Circuit Next node
                              links
     1.1 (MAGICA) Reachable      0       4 UNA-0          1.1 (MAGICA)
     1.2 (ERNIE) Unreachable
     1.3 (FNATTE) Unreachable
     1.4 (GOBLIN) Unreachable
     1.5 (ZEKE) Unreachable
     1.6 (GNOME) Unreachable
     1.7 (BJARNE) Unreachable
     1.8 (KRILLE) Unreachable
     1.9 (TEMPO) Unreachable
    1.10 (SIGGE) Unreachable
    1.11 (ROCKY) Unreachable
    1.12 (PONY) Unreachable
    1.14 (TINA) Unreachable
    1.15 (PONDUS) Reachable      0       4   UNA-0 1.15 (PONDUS)
    1.16 (GNAT) Unreachable
    1.17 (JOSSE) Unreachable
    1.18 (PAMINA) Unreachable
    1.19 (BEA) Unreachable
    1.20 (WXP) Unreachable
    1.21 (JOCKE)  Reachable      0       4   UNA-0 1.21 (JOCKE)
    1.22 (PUFF) Unreachable
    1.23 (WXP2) Unreachable
    1.24 (SPEEDY) Unreachable

NCP>
15:50:17     NCP
       Node       State       Active  Delay  Circuit Next node
                              links
   1.100 (FLETCH) Unreachable
   1.150 (HORSE) Unreachable
   1.151 (QEMUNT) Unreachable
   1.200 (PLINTH) Unreachable
   1.201 (CRISPS) Unreachable
   1.202 (NIPPER) Unreachable
   1.250 (TARDIS) Reachable                  UNA-0 1.250 (TARDIS)
   1.251 (MASTER) Unreachable
   1.252 (DOCTOR) Unreachable
   1.253 (SIDRAT) Reachable                  UNA-0 1.253 (SIDRAT)
   1.254 (DAVROS) Unreachable
   1.255 (RUTAN) Unreachable
   1.256 (VAROS) Unreachable
   1.257 (THOROS) Unreachable
   1.258 (MACRA) Unreachable
   1.259 (CYGNUS) Unreachable
   1.260 (SHARPE) Unreachable
   1.261 (HARPER) Unreachable
   1.262 (HAGMAN) Unreachable
   1.263 (COOPER) Unreachable
   1.264 (TONGUE) Unreachable
   1.265 (PACMAN) Unreachable
   1.266 (BLINKY) Unreachable
   1.267 (PINKY) Unreachable
   1.268 (INKY) Unreachable

NCP>
15:50:56     NCP
       Node       State       Active  Delay  Circuit Next node
                              links
   1.269 (CLYDE) Unreachable
   1.301 (ORAV23) Unreachable
   1.302 (ORAV41) Unreachable
   1.303 (RSX134) Unreachable
   1.304 (RSX145) Unreachable
   1.305 (RSX170) Unreachable
   1.306 (RSX124) Unreachable
   1.307 (RSX184) Unreachable
   1.350 (ERSATZ) Unreachable
   1.351 (DBIT) Unreachable
   1.400 (VALAR) Unreachable
   1.450 (DE1RSX) Unreachable
   1.451 (KLIO) Unreachable
   1.452 (DE1RSY) Unreachable
   1.500 (HYUNA) Unreachable
, Operation failure,
Response read failed

NCP>
15:51:04       -- DECnet link message --

Communication failure to the following nodes:
MIM

NCP>

On 9/4/20 2:34 PM, Johnny Billquist wrote:
> Happy to announce that I have found and fixed the bug in the DECnet 
> code in RSX that could cause operations like "SHOW KNOWN NODES" to 
> skip some nodes under some circumstances.
>
> So anyone getting node definitions from MIM can now safely do that 
> using NCP (in VMS), or NNS (in RSX) and be sure they do get the 
> complete list.
>
> For anyone using RSX, this is another component you want to update. 
> The file in question is [5,54]NMVACP.TSK, and you can copy it from MIM::
> Place it in that directory, and you're good after the next reboot.
> If you want it fixed on your running system, then after copying the 
> file over, do the following two lines:
>
> REM NMVACP
> INS LB:[5,54]NMVACP
>
> and then you are good.
>
> If anyone wants to know itty gritty details on the bug, let me know 
> and I can explain it. But suffice to say for now, that this bug was 
> introduced with the nodename server in RSX, which I think only came in 
> M+ V4.6.
>
>   Johnny
>
> On 2020-08-27 02:16, Johnny Billquist wrote:
>> On 2020-08-27 01:47, Dave McGuire wrote:
>>> On 8/26/20 4:40 PM, Johnny Billquist wrote:
>>>> Let me put it this way. If any tool causes you any problems, first 
>>>> check if there is something newer on MIM, and if so - grab and test 
>>>> that.
>>>> If not, let me know, and I can probably fix it.
>>>
>>>    I'm sure I speak for all of us here when I say THANK YOU for this.
>>
>> The thing is - some of the bugs and issues I've worked on are rather 
>> obscure. You might occasionally observe there is something funny 
>> going on, but understanding where the problem is, and finding the 
>> fixed file on MIM is not always so easy, nor how to apply it.
>>
>> Take MCR, for example. There are multiple things I've fixed. Both in 
>> MCR... and ...MCR (they are two different things). And applying them 
>> needs that you update things through VMR. Can't be done on a running 
>> system. (Well, ...MCR can, but MCR... cannot.)
>>
>> My TCP/IP package already does that patch for you however, so you 
>> should be good.
>>
>> Hey, here is something for people to look at, to make you aware of 
>> things you might be interested in: MIM::US:[BQT]FIX.TXT contains all 
>> the work I've been doing for a possible future V5.0 release of 
>> RSX-11M-PLUS.
>> A lot of those fixes apply just fine also for V4.6, but don't ask 
>> about the subdirectory stuff. That is just too complex to patch up, 
>> and there are still a couple of corners I'm not done with.
>>
>>>> And while I'm on it. At the moment there is a long standing bug in 
>>>> NICE on RSX, which have been annoying me slightly for a long time, 
>>>> but which is now starting to become serious enough that I need to 
>>>> look deeper into it. If you do a "NCP TELL MIM SHOW KNOWN NODES" 
>>>> the list is incomplete. If you look carefully, some nodes are 
>>>> missing, which will be there, if you explicitly ask for them.
>>>>
>>>> This becomes a larger problem because if someone on a VMS system 
>>>> does an "NCP COPY KNOWN NODES FROM MIM ..." they will not be 
>>>> getting the full list either. And the same goes for RSX users using 
>>>> NNC to copy the known nodes from MIM.
>>>
>>>    Ah-HA!!  I have seen exactly this.  I thought I was losing my mind.
>>
>> Well, now you know you aren't. :-)
>>
>>    Johnny
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20200904/55bc7894/attachment-0001.html>