4 Mar
2020
4 Mar
'20
8:59 p.m.
On Mar 3, 2020, at 10:38 PM, Robert Armstrong <bob
at jfcl.com> wrote:
Here?s a few more:
DECnet-RSX
Kernel interface requires a node name (up to 6 characters) so can only connect to nodes
which are in the system database.
Access control uses the syntax nodename/user/password/account::
DECnet-Ultrix (and the probably never released DECnet-SCO)
Kernel interface take a 16-bit binary node address. Applications typically use the
dnetconn() library routine which accepts all three node
address formats node::, 2.16:: and 2064::.
Like RSX, access control uses the syntax nodename/user/password/account::
DECnet-Linux
Similar kernel interface to DECnet-Ultrix.
The original code used VMS syntax for access control but that meant that you would either
have to escape each quote character or use an
extra pair of quotes, so either
?nodename?user password??:: or
nodename/user/password::
While working at DEC I had a PRO-350 in my office with a nodename of 4cast:: intended to
help shake out the nodename vs. node address
distinction.
John.
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:
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