<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Helvetica, Arial, sans-serif"><font face="Calibri,
sans-serif">I appear to have neither <font size="+1"><tt>CIRCUIT
VERIFICATION</tt></font> nor <font size="+1"><tt>NODE
TRANSMIT PASSWORD</tt></font>, viz:</font><br>
</font></p>
<blockquote>
<p><font face="Courier New, Courier, monospace">NCP>set cirCUIT
ni-0 ? ALL<br>
or one of the following:<br>
ACTIVE BABBLE BLOCKING CHANNEL COST
COUNTER DEAD<br>
DTE DYING HELLO INACTIVE LINE
LISTEN MAXIMUM<br>
NUMBER OWNER POLLING RECALL
ROUTER SERVICE STATE<br>
TRANSMIT TRIBUTARY TYPE USAGE<br>
<br>
</font><font face="Courier New, Courier, monospace"><font
face="Courier New, Courier, monospace">NCP></font>set
noDE venti2:: ? ALL<br>
or one of the following:<br>
ADDRESS CIRCUIT<br>
or one of the following:<br>
AREA BROADCAST BUFFER CONSOLE
COUNTER<br>
CPU DELAY DIAGNOSTIC DUMP
HARDWARE<br>
HOST IDENTIFICATION INACTIVITY INCOMING
LOAD<br>
MAXIMUM OUTGOING RETRANSMIT ROUTING
SECONDARY<br>
SEGMENT SERVICE </font><font face="Courier New,
Courier, monospace"> SOFTWARE STATE
SUBADDRESSES<br>
TERTIARY TYPE</font></p>
</blockquote>
<p><font face="Calibri, sans-serif">I may be mis-remembering how our
DN200 was configured. I believe the Top-20 NCP parser may have
shared keyword tables with other DECnet implementations via
BLISS at one point. Anyway, I recall at least some of it was
BLISS. I haven't look in that particular box lately, but the
parse tables appear to assembler now, with heavy uses of GLXMAC
macros.</font></p>
<p><font face="Calibri, sans-serif">The Tops-20 operator interface
has two 'sub-modes', as it were: NCP and LCP. NCP parses DECnet
related keywords. LCP is used for LAT configuration. The
operator subsystem is kind of neat; OPR parsers send packets to
Orion, a communications server and router. It notes an NCP
subset and routes that to NMLT20 which contains just what you
think it would.</font></p>
<p><font face="Calibri, sans-serif">Early versions of NMLT20 (about
1980) appeared insufficiently productized. It could hang in a
loop or (more frequently) crash for no readily apparent reason.
We submitted a rather large number of SPR's... However, it's
quite stable now; I don't believe I've had a single crash. I
have yet to come to a fully informed conclusion about the
lexical interface; I sometimes get the impression that it parses
for more than it can actually do.</font></p>
<p><font face="Calibri, sans-serif">Elsewhere in Tops-20, DECnet
implementation is a mixed bag; most of the monitor code appears
finished; I go months without reboots and that is with active
development. The user mode code is another matter entirely. I
had my hands full fixing a number of issues with DAP and FAL.
It was <i>invaluable</i> having heterogeneous HECnet nodes to
test against, RSX 11M+ and VMS. SETNOD needs some finishing and
perhaps some additional functionality. I have yet to look at
FTS; I don't see how it can get or generate any traffic at all.
The monitor interface (NFT:) does not appear to be operational.
Elsewhere (perhaps Galaxy) appears to have no submission
interface. Johnny and I have some minor tweaks to flush out
with MAIL11 (in addition to the changes that I've already put
in).<br>
</font></p>
<br>
<div class="moz-cite-prefix">On 3/2/20 3:25 PM, Robert Armstrong
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:011201d5f0d0$c052e6e0$40f8b4a0$@com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p><span style="color:#1F497D">></span>I don't see where I
would set an id and password in 7-1-CONFIG or in NCP.<span
style="color:#1F497D"><o:p></o:p></span></p>
<p><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
Don’t know about TOPS-20, but in NCP/NICE/NML it’s<o:p></o:p></span></p>
<p><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
SET CIRCUIT … VERIFICATION ENABLED<o:p></o:p></span></p>
<p><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">and<o:p></o:p></span></p>
<p><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
SET NODE … TRANSMIT PASSWORD …<o:p></o:p></span></p>
<p><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The
password the remote node sends has to match the one that’s
associated with that node in the local DECnet database.<o:p></o:p></span></p>
<p><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Bob<o:p></o:p></span></p>
<p><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
</div>
</blockquote>
</body>
</html>