<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I took Bob's note as an invitation to perform a little experiment
on <font size="+1"><tt>ZITI::</tt></font>. It looks like my
suspicions were confirmed; if the node name isn't in Tops-20's
hash table, then you are not going there, no way, no how.</p>
<ul>
<li>I verified that <font size="+1"><tt>ZITI::</tt></font> was in
my area, online and that I could do a <font size="+1"><tt>SHOW
EXECUTOR</tt></font>, <br>
</li>
<li>I then undefined poor <font size="+1"><tt>ZITI::</tt></font>,
noticing that it subsequently was reported as offline (clearly a
vicious calumny).</li>
<li>The <font size="+1"><tt>NICE</tt></font> process (<font
size="+1"><tt>NCP</tt></font>) could no longer communicate
with it either by name <i>or by number</i>.<br>
</li>
<li>When I redefined <font size="+1"><tt>ZITI::</tt></font> with
<font size="+1"><tt>SETNOD</tt></font>, <font size="+1"><tt>SHOW
EXECUTOR</tt></font> started working again.</li>
</ul>
<p>I wonder why they never allowed real area.number connections in
Tops-20? I mean other than they were running away from the
product... Hum...<br>
</p>
<p><font size="+1"><tt>!</tt></font><font size="+1"><tt><font
size="+1"><tt>i dec</tt><tt><br>
</tt><tt> Local DECNET node: VENTI2. Nodes reachable: 6.</tt><tt><br>
</tt><tt> Accessible DECNET nodes are: A2RTR APOLLO
LEGATO TOMMYT VENTI2 ZITI</tt><tt><br>
</tt><tt>!</tt></font>opr</tt><tt><br>
</tt><tt>OPR>enter ncp</tt><tt><br>
</tt><tt>NCP>telL ziti:: shoW exeCUTOR </tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>23:20:29 NCP</tt><tt><br>
</tt><tt> Request # 5 Accepted</tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>23:20:30 NCP</tt><tt><br>
</tt><tt><br>
</tt><tt>Request # 5; Show Executor Node Summary Completed</tt><tt><br>
</tt><tt><br>
</tt><tt>Executor Node = 2.16 (ZITI)</tt><tt><br>
</tt><tt><br>
</tt><tt><br>
</tt><tt> Circuit = eth1</tt><tt><br>
</tt><tt> State = On</tt><tt><br>
</tt><tt> Identification = DECnet for Linux V4.4.0-148-generic
on x86_64</tt><tt><br>
</tt><tt>NCP>push</tt><tt><br>
</tt><tt><br>
</tt><tt> PANDA TOPS-20 Command processor 7.1(4454)-5</tt><tt><br>
</tt><tt> End of TOMMYT:<SLOGIN>COMAND.CMD.12</tt><tt><br>
</tt><tt>@enable</tt><tt><br>
</tt><tt>!setnod</tt><tt><br>
SETNOD>set nODE -1 . -1 nAME ZITI</tt><tt><br>
</tt><tt>SETNOD>insert</tt><tt><br>
</tt><tt>SETNOD>exi</tt><tt><br>
</tt><tt>!i dec</tt><tt><br>
</tt><tt> Local DECNET node: VENTI2. Nodes reachable: 5.</tt><tt><br>
</tt><tt> Accessible DECNET nodes are: A2RTR APOLLO
LEGATO TOMMYT VENTI2</tt><tt><br>
</tt><tt>!pop</tt><tt><br>
</tt><tt>NCP>telL ziti:: shoW exeCUTOR </tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>23:22:13 NCP</tt><tt><br>
</tt><tt> Request # 6 Accepted</tt><tt><br>
</tt><tt><br>
</tt><tt>23:22:13 NCP</tt><tt><br>
</tt><tt><br>
</tt><tt>Request # 6; Show Executor Node Summary Failed,
Listener link connect failed,</tt><tt><br>
</tt><tt>Link Failure = Node unreachable</tt><tt><br>
</tt><tt><br>
</tt><tt>NCP>telL 2.16 shoW exECUTOR </tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>23:22:23 NCP</tt><tt><br>
</tt><tt> Request # 7 Accepted</tt><tt><br>
</tt><tt><br>
</tt><tt>23:22:23 NCP</tt><tt><br>
</tt><tt><br>
</tt><tt>Request # 7; Show Executor Node Summary Failed, Invalid
identification,</tt><tt><br>
</tt><tt>Node address has no matching node name </tt><tt><br>
</tt><tt><br>
</tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>23:22:28 -- DECnet link message --</tt><tt><br>
</tt><tt><br>
</tt><tt>Communication failure to the following nodes:</tt><tt><br>
</tt><tt>ZITI </tt><tt><br>
</tt><tt>NCP>push</tt><tt><br>
</tt><tt>!c setnod</tt><tt><br>
</tt><tt>SETNOD>set nod 2.16 name ziti</tt><tt><br>
</tt><tt>SETNOD>insert</tt><tt><br>
</tt><tt>SETNOD>exi</tt><tt><br>
</tt><tt>!i dec</tt><tt><br>
</tt><tt> Local DECNET node: VENTI2. Nodes reachable: 6.</tt><tt><br>
</tt><tt> Accessible DECNET nodes are: A2RTR APOLLO
LEGATO TOMMYT VENTI2 ZITI</tt><tt><br>
</tt><tt>!pop</tt><tt><br>
</tt><tt>NCP>tel ziti:: shoW exeCUTOR </tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>23:23:35 NCP</tt><tt><br>
</tt><tt> Request # 8 Accepted</tt><tt><br>
</tt><tt>NCP></tt><tt><br>
</tt><tt>23:23:36 NCP</tt><tt><br>
</tt><tt><br>
</tt><tt>Request # 8; Show Executor Node Summary Completed</tt><tt><br>
</tt><tt><br>
</tt><tt>Executor Node = 2.16 (ZITI)</tt><tt><br>
</tt><tt><br>
</tt><tt><br>
</tt><tt> Circuit = eth1</tt><tt><br>
</tt><tt> State = On</tt><tt><br>
</tt><tt> Identification = DECnet for Linux V4.4.0-148-generic
on x86_64</tt><tt><br>
</tt><tt>NCP>exit</tt></font><br>
<br>
</p>
<div class="moz-cite-prefix">
<hr width="100%" size="2">On 3/3/20 10:38 PM, Robert Armstrong
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:000e01d5f1d6$62e3a880$28aaf980$@com">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">The area.node notation, and the Phase 3 numeric address notation, were
intended to be standard, not just limited to NCP. And indeed DECnet/E
(in RSTS) does both:
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
FWIW, VMS accepts all three notations too - e.g. ZITI::, 2.16:: and
2064::. It also accepts the node"name password":: notation as well.
Actually I thought this was a standard thing in all "modern" (i.e. Phase IV)
implementations. Are there systems that don't?
And the VMS parser doesn't limit the node name to 6 characters, so you can
say "63.1023::" (although HECnet has no such node).
Bob
</pre>
</blockquote>
</body>
</html>