<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>Pretty nifty, so I tried it and got up to <font size="+1"><tt>1.500
(HYUNA)</tt></font> 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.</p>
<p>What did you see on MIM? A time out? You can tell me about the
bug off list; sounds like fun.<br>
</p>
<p><br>
</p>
<p><tt>NCP>telL mim:: shoW knoWN noDES </tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>15:49:53 NCP</tt><tt><br>
</tt><tt> Request # 44 Accepted</tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>15:50:07 NCP</tt><tt><br>
</tt><tt><br>
</tt><tt>Request # 44; Show Known Nodes Summary Completed</tt><tt><br>
</tt><tt><br>
</tt><tt>Executor Node = 1.13 (MIM)</tt><tt><br>
</tt><tt><br>
</tt><tt> State = On</tt><tt><br>
</tt><tt> Identification = "RSX system at Update, Sweden"</tt><tt><br>
</tt><tt><br>
</tt><tt> Node State Active Delay Circuit
Next node</tt><tt><br>
</tt><tt> links</tt><tt><br>
</tt><tt> 1.1 (MAGICA) Reachable 0 4
UNA-0 1.1 (MAGICA)</tt><tt><br>
</tt><tt> 1.2 (ERNIE)
Unreachable </tt><tt><br>
</tt><tt> 1.3 (FNATTE)
Unreachable </tt><tt><br>
</tt><tt> 1.4 (GOBLIN)
Unreachable </tt><tt><br>
</tt><tt> 1.5 (ZEKE)
Unreachable </tt><tt><br>
</tt><tt> 1.6 (GNOME)
Unreachable </tt><tt><br>
</tt><tt> 1.7 (BJARNE)
Unreachable </tt><tt><br>
</tt><tt> 1.8 (KRILLE)
Unreachable </tt><tt><br>
</tt><tt> 1.9 (TEMPO)
Unreachable </tt><tt><br>
</tt><tt> 1.10 (SIGGE)
Unreachable </tt><tt><br>
</tt><tt> 1.11 (ROCKY)
Unreachable </tt><tt><br>
</tt><tt> 1.12 (PONY)
Unreachable </tt><tt><br>
</tt><tt> 1.14 (TINA)
Unreachable </tt><tt><br>
</tt><tt> 1.15 (PONDUS) Reachable 0 4 UNA-0
1.15 (PONDUS)</tt><tt><br>
</tt><tt> 1.16 (GNAT)
Unreachable </tt><tt><br>
</tt><tt> 1.17 (JOSSE)
Unreachable </tt><tt><br>
</tt><tt> 1.18 (PAMINA)
Unreachable </tt><tt><br>
</tt><tt> 1.19 (BEA)
Unreachable </tt><tt><br>
</tt><tt> 1.20 (WXP)
Unreachable </tt><tt><br>
</tt><tt> 1.21 (JOCKE) Reachable 0 4 UNA-0
1.21 (JOCKE) </tt><tt><br>
</tt><tt> 1.22 (PUFF)
Unreachable </tt><tt><br>
</tt><tt> 1.23 (WXP2)
Unreachable </tt><tt><br>
</tt><tt> 1.24 (SPEEDY)
Unreachable </tt><tt><br>
</tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>15:50:17 NCP</tt><tt><br>
</tt><tt> Node State Active Delay Circuit
Next node</tt><tt><br>
</tt><tt> links</tt><tt><br>
</tt><tt> 1.100 (FLETCH)
Unreachable </tt><tt><br>
</tt><tt> 1.150 (HORSE)
Unreachable </tt><tt><br>
</tt><tt> 1.151 (QEMUNT)
Unreachable </tt><tt><br>
</tt><tt> 1.200 (PLINTH)
Unreachable </tt><tt><br>
</tt><tt> 1.201 (CRISPS)
Unreachable </tt><tt><br>
</tt><tt> 1.202 (NIPPER)
Unreachable </tt><tt><br>
</tt><tt> 1.250 (TARDIS) Reachable UNA-0
1.250 (TARDIS)</tt><tt><br>
</tt><tt> 1.251 (MASTER)
Unreachable </tt><tt><br>
</tt><tt> 1.252 (DOCTOR)
Unreachable </tt><tt><br>
</tt><tt> 1.253 (SIDRAT) Reachable UNA-0
1.253 (SIDRAT)</tt><tt><br>
</tt><tt> 1.254 (DAVROS)
Unreachable </tt><tt><br>
</tt><tt> 1.255 (RUTAN)
Unreachable </tt><tt><br>
</tt><tt> 1.256 (VAROS)
Unreachable </tt><tt><br>
</tt><tt> 1.257 (THOROS)
Unreachable </tt><tt><br>
</tt><tt> 1.258 (MACRA)
Unreachable </tt><tt><br>
</tt><tt> 1.259 (CYGNUS)
Unreachable </tt><tt><br>
</tt><tt> 1.260 (SHARPE)
Unreachable </tt><tt><br>
</tt><tt> 1.261 (HARPER)
Unreachable </tt><tt><br>
</tt><tt> 1.262 (HAGMAN)
Unreachable </tt><tt><br>
</tt><tt> 1.263 (COOPER)
Unreachable </tt><tt><br>
</tt><tt> 1.264 (TONGUE)
Unreachable </tt><tt><br>
</tt><tt> 1.265 (PACMAN)
Unreachable </tt><tt><br>
</tt><tt> 1.266 (BLINKY)
Unreachable </tt><tt><br>
</tt><tt> 1.267 (PINKY)
Unreachable </tt><tt><br>
</tt><tt> 1.268 (INKY)
Unreachable </tt><tt><br>
</tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>15:50:56 NCP</tt><tt><br>
</tt><tt> Node State Active Delay Circuit
Next node</tt><tt><br>
</tt><tt> links</tt><tt><br>
</tt><tt> 1.269 (CLYDE)
Unreachable </tt><tt><br>
</tt><tt> 1.301 (ORAV23)
Unreachable </tt><tt><br>
</tt><tt> 1.302 (ORAV41)
Unreachable </tt><tt><br>
</tt><tt> 1.303 (RSX134)
Unreachable </tt><tt><br>
</tt><tt> 1.304 (RSX145)
Unreachable </tt><tt><br>
</tt><tt> 1.305 (RSX170)
Unreachable </tt><tt><br>
</tt><tt> 1.306 (RSX124)
Unreachable </tt><tt><br>
</tt><tt> 1.307 (RSX184)
Unreachable </tt><tt><br>
</tt><tt> 1.350 (ERSATZ)
Unreachable </tt><tt><br>
</tt><tt> 1.351 (DBIT)
Unreachable </tt><tt><br>
</tt><tt> 1.400 (VALAR)
Unreachable </tt><tt><br>
</tt><tt> 1.450 (DE1RSX)
Unreachable </tt><tt><br>
</tt><tt> 1.451 (KLIO)
Unreachable </tt><tt><br>
</tt><tt> 1.452 (DE1RSY)
Unreachable </tt><tt><br>
</tt><tt> 1.500 (HYUNA)
Unreachable </tt><tt><br>
</tt><tt><font color="red">, Operation failure,<br>
Response read failed </font></tt><tt><br>
</tt><tt><br>
</tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>15:51:04 -- DECnet link message --</tt><tt><br>
</tt><tt><br>
</tt><tt>Communication failure to the following nodes:</tt><tt><br>
</tt><tt>MIM </tt><tt><br>
</tt><tt><br>
</tt><tt>NCP></tt><br>
<br>
</p>
<div class="moz-cite-prefix">On 9/4/20 2:34 PM, Johnny Billquist
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9590c296-2795-fddb-6d34-1bf9fd70af4e@softjar.se">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.
<br>
<br>
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.
<br>
<br>
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::
<br>
Place it in that directory, and you're good after the next reboot.
<br>
If you want it fixed on your running system, then after copying
the file over, do the following two lines:
<br>
<br>
REM NMVACP
<br>
INS LB:[5,54]NMVACP
<br>
<br>
and then you are good.
<br>
<br>
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.
<br>
<br>
Johnny
<br>
<br>
On 2020-08-27 02:16, Johnny Billquist wrote:
<br>
<blockquote type="cite">On 2020-08-27 01:47, Dave McGuire wrote:
<br>
<blockquote type="cite">On 8/26/20 4:40 PM, Johnny Billquist
wrote:
<br>
<blockquote type="cite">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.
<br>
If not, let me know, and I can probably fix it.
<br>
</blockquote>
<br>
I'm sure I speak for all of us here when I say THANK YOU
for this.
<br>
</blockquote>
<br>
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.
<br>
<br>
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.)
<br>
<br>
My TCP/IP package already does that patch for you however, so
you should be good.
<br>
<br>
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.
<br>
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.
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">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.
<br>
<br>
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.
<br>
</blockquote>
<br>
Ah-HA!! I have seen exactly this. I thought I was losing
my mind.
<br>
</blockquote>
<br>
Well, now you know you aren't. :-)
<br>
<br>
Johnny
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
</body>
</html>