Hello,
May I request a node address and node number pair to try to connect
using the bridge program?
I am running OpenVMS 7.3 on SIMH on a dedicated virtualbox VM and have
compiled the bridge program on the VM host, wanting to take the next step.
Thanks in advance,
Supratim
---
Johnny,
I would like to connect to you first (the easy solution) - please send
me the two numbers I can use.
Note: You will probably hear back from me after around a week when I
return from a work-related travel assignment.
Thanks,
Supratim
On 5/14/2016 7:46 PM, Johnny Billquist wrote:
Hi, Supratim.
On 2016-05-14 19:33, Supratim Sanyal wrote:
Dear Johnny,
I am taking the first steps in building a useful hobbyist OpenVMS
7.3/VAX machine and am at a point where I
(a) have downloaded and compiled the bridge program on a linux gateway
box, and
(b) am starting to configure DECNet Plus with the goal of getting on
HECNet.
I would like the nodename to be QCOCAL if possible (historical reasons,
the first nodename when I joined DEC was QCOCAL). Also, can you help me
with choosing between LOCAL and DECdns, and assign me an area and a node
number?
Once I have this configured, the next step will be to get bridge to work
and test if I can reach other Vaxen over HECnet.
The following is a dump of what I did so far. Also copying Poolak
Banerjee, a fellow ex-DEC VAX enthusiast and my ex-boss at DEC, who is
closely following progress on this VAX.
Well, the obvious questions are (as always), where to connect you, and
what area and node number to use.
Since you mention that you are planning to use the bridge, the easy
solution is to connect to me, but if you have some other plan just let
me know.
The question of area and node number depends on your system. I do not
really know much about DECnet Plus. Can you have an area router with
this, and would you like to have your own area, or would you prefer to
be placed in an existing area?
As far as choosing how to handle node names, I cannot really comment.
Like I said, I do not really know DECnet Plus that well, and found it
just complicated for my needs, so I "downgraded" back to plain Phase IV
DECnet on whatever VMS I have. But I mostly run PDP-11s myself. And
there are also many other type of systems as well.
Johnny
Thank you very much,
Supratim Sanyal
Germantown, Maryland, USA
--
*DUA1:[RUMTUK]$ start/network decnet**
*Copyright 2000 Compaq Computer Corporation. All rights reserved.
%NET$STARTUP-W-NONETCONFIG, this node has not been configured to run
DECnet-Plus for OpenVMS
use
SYS$MANAGER:NET$CONFIGURE.COM if you wish to configure
DECnet
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status
is OFF
*DUA1:[RUMTUK]$ @SYS$MANAGER:NET$CONFIGURE.COM**
*Copyright Compaq Computer Corporation 2000. All rights reserved.
DECnet-Plus for OpenVMS network configuration procedure
This procedure will help you create or modify the management scripts
needed to operate DECnet on this machine. You may receive help about
most questions by answering with a question mark '?'.
%NET$CONFIGURE-I-SETUPNEW, setting up for new configuration
You have the option of choosing the following directory services
for
your system:
Local file (LOCAL) - A local namespace that uses flat naming.
DECdns - A distributed namespace.
Domain - A naming service that uses DNS/BIND.
The Local file has the capability to hold 100,000 nodes, and it
can even
scale beyond that number. The actual number of nodes that the
Local file
can hold depends on the space available on your system.
If you choose to enter more than one directory service for your
system,
the ordering of this list is *very important*, as the first
directory
service entered in this list will be considered the primary
directory
service to use on the system. The primary directory service is
considered
the first choice to use when looking up naming information for the
system.
If you are running a DNS Clerk on this system, or plan to run a
DNS Clerk
on this system, DECdns *must* be the first service in the list.
Enter an *ordered* list of the directory services you want to
use on
the system. If you enter more than one directory service,
separate them
by commas.
* Enter the directory services to use on the system
[DECdns,Local,Domain] : Local
Enter a node name for each directory service chosen.
For the directory service Domain, you will enter a fully qualified
host name for DNS/BIND. The fully qualified host name includes the
host name part and the domain name part. For example:
Domain -
smilee.lkg.dec.com
For the directory services DECdns and Local file, you will enter a
node
full name. The node full name is the name of your system's node
object
in the directory service. It includes the namespace nickname,
and the
full list of directories leading to the node object name.
Examples of
node full names for the directory services DECdns and Local file
include:
Local file - LOCAL:.TomThumb
DECdns - XYZ_CORP:.sales.west_coast.WillyLoman
For the Local file, the namespace nickname LOCAL is prepended to
the
full name and is terminated with a colon (:). The namespace
nickname
"LOCAL" means that the Local file is used. The node object name
must
begin with a dot (.), and no element of the name (namespace name,
directory, or node object name) can be a null string. Please note
that
the namespace nickname "LOCAL" is reserved, and indicates that
the
Local file will be used on this system.
The Local file has the capability to hold 100,000 nodes, and it
can even
scale beyond that number. The actual number of nodes that the
Local file
can hold depends on the space available on your system.
** Enter the full name for directory service LOCAL :
**LOCAL:.QCOCAL**
*
The node synonym is an alphanumeric character string between 1
and 6
characters long that contains at least one alphabetic character.
If this
system had previously been running DECnet Phase IV software, then
the old
nodename should be used as the synonym. If this system is joining
a DECnet
network for the first time, any name can be used for the synonym,
as long
as it meets the criteria listed above, and is unique within the
network.
* What is the synonym name for this node? : QCOCAL
* What type of node (Endnode or Router)? [ENDNODE] :
A DECnet-Plus system may or may not use a DECnet Phase IV-style
node
address. A node address of 0.0 indicates that this DECnet-Plus
system
will be communicating with OSI systems only. If your network
contains
some systems running DECnet Phase IV, you may want to specify a
compatible
address in order to communicate with them. If your network
consists
solely of OSI systems, this is not required.
The DECnet Phase IV node address consists of an area number
(between 1
and 63), and a node number within the area (between 1 and 1023).
** Enter PhaseIV Address [1.1] :
**42.420**
*%NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait
Determining DTSS timezone rules from OpenVMS information...
%NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates
%NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher
configuration
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account
CML$SERVER
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account
MAIL$SERVER
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account
VPM$SERVER
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account
MIRRO$SERVER
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account
PHONE$SERVER
By default, MOP is not started by NET$STARTUP. In order to make
this system service MOP requests, NET$STARTUP_MOP must be
defined
to signal NET$STARTUP to load the MOP software. This symbol is
normally defined in
SYS$STARTUP:NET$LOGICALS.COM.
Answering YES to the following question will modify
SYS$STARTUP:NET$LOGICALS.COM for you, to enable MOP service on
this system. Answering NO will remove the logical name
definition
from
SYS$STARTUP:NET$LOGICALS.COM. Note that this will have no
effect if the NET$STARTUP_MOP is defined elsewhere.
* Load MOP on this system? [NO] :
Summary of Configuration
Node Information:
Node Type: ENDNODE
Directory Services Chosen: LOCAL
Primary Directory Service: LOCAL
Local Full name: LOCAL:.QCOCAL
Node Synonym: QCOCAL
Phase IV Address: 42.420
Phase IV Prefix: 49::
Autoconfiguration of Network Addresses: Enabled
Session Control Address Update Interval: 10
Routing ESHello Timer: 600
Routing ES Cache Size: 512
Device Information:
Device: XQA0 (DELQA):
Data Link name: CSMACD-0
Routing Circuit Name: CSMACD-0
Transport Information:
NSP Transport: Configured
Maximum number of logical links: 200
Maximum Transmit and Receive Window: 20
Maximum Receive Buffers: 4000
Flow Control Policy: Segment Flow Control
OSI Transport: Configured
Maximum number of logical links: 200
Maximum Transmit and Receive Window: 20
Maximum Receive Buffers: 4000
OSI applications over TCP/IP: Enabled
DECnet applications over TCP/IP: Enabled
Congestion Avoidance Disabled
Event Dispatcher Configuration:
Sinks: local_sink
Outbound Streams: local_stream
Phase IV Relay: Enabled
* Do you want to generate NCL configuration scripts? [YES] :
%NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts
* Do you want to start the network? [YES] :
%STDRV-W-NOTSYSTEM, STARTUP is not running from the SYSTEM account.
-STDRV-W-UNPREDICT, Results are unpredictable.
Copyright 2000 Compaq Computer Corporation. All rights reserved.
%NET-I-LOADED, executive image LES$LES_V30.EXE loaded
%NET-I-LOADED, executive image NET$ALIAS.EXE loaded
%NET-I-LOADED, executive image NET$SESSION_CONTROL.EXE loaded
%NET$STARTUP-I-STARTPROCESS, starting process DNS
%NET-I-LOADED, executive image SYS$NAME_SERVICES.EXE loaded
%RUN-S-PROC_ID, identification of created process is 00000273
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$NODE_STARTUP.NCL;
%NET-I-LOADED, executive image NET$CSMACD.EXE loaded
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$CSMACD_STARTUP.NCL;
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$SESSION_STARTUP.NCL;
%LES-S-PROC_ID, identification of created process is 00000274
%LES-I-LOADING, loading NET$ component NETMANPPI from
SYS$COMMON:[SYS$LDR]LES$NETMAN.EXE;1
%LES-I-LOADING, loading NET$ component NETMANLDR from
SYS$COMMON:[SYS$LDR]LES$NETMANLDR.EXE;1
%LES-I-LOADING, loading NET$ component LES$ROUTING from
SYS$COMMON:[SYS$LDR]NET$ROUTING_ES.EXE;1
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$ROUTING_STARTUP.NCL;
%NET-I-LOADED, executive image NET$TRANSPORT_NSP.EXE loaded
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$NSP_TRANSPORT_STARTUP.NCL;
%NET-I-LOADED, executive image NET$TPCONS.EXE loaded
%NET-I-LOADED, executive image NET$TRANSPORT_OSI.EXE loaded
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$OSI_TRANSPORT_STARTUP.NCL;
%NET-I-LOADED, executive image NET$OSVCM.EXE loaded
%NET$STARTUP-I-STARTPROCESS, starting process ACP
%RUN-S-PROC_ID, identification of created process is 00000275
%RUN-S-PROC_ID, identification of created process is 00000276
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$SEARCHPATH_STARTUP.NCL;
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is
RUNNING-MAJOR
%NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries
Node 0
at 2016-05-14-17:20:28.850+00:00Iinf
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.QCOCAL
Node 0 Session Control
at 2016-05-14-17:20:30.030+00:00Iinf
Node 0 Session Control
at 2016-05-14-17:20:30.040+00:00Iinf
Node 0 Session Control
at 2016-05-14-17:20:30.050+00:00Iinf
Node 0 Session Control
at 2016-05-14-17:20:30.060+00:00Iinf
Node 0 Session Control
at 2016-05-14-17:20:30.420+00:00Iinf
Characteristics
Maintain Backward Soft Links = True
Directory Service: Local name file
Error - Node name lookup failure
LOCAL:.QCOCAL
Number of nodes reported on: 0
%NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in
the LOCAL directory service
%NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import
file
Directory Service: Local name file
Updating nodes listed in
SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_QCOCAL.TXT
Number of nodes registered: 1
Number of nodes modified: 0
%NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in
the LOCAL directory service
Node 0
at 2016-05-14-17:20:32.940+00:00Iinf
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.QCOCAL
%STDRV-W-NOTSYSTEM, STARTUP is not running from the SYSTEM account.
-STDRV-W-UNPREDICT, Results are unpredictable.
Copyright 2000 Compaq Computer Corporation. All rights reserved.
%NET$STARTUP-I-STARTPROCESS, starting process EVD
%RUN-S-PROC_ID, identification of created process is 00000277
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$EVENT_STARTUP.NCL;
%NET$STARTUP-I-STARTPROCESS, starting process DTSS
%RUN-S-PROC_ID, identification of created process is 00000278
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script
SYS$SYSROOT:[SYSMGR]NET$APPLICATION_STARTUP.NCL;
%NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is
RUNNING-ALL
%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration
completed
On 5/13/2016 8:38 AM, Majordomo at Update.UU.SE wrote:
> --
>
> Welcome to the hecnet mailing list!
>
> Please save this message for future reference. Thank you.
>
> If you ever want to remove yourself from this mailing list,
> you can send mail to<Majordomo at Update.UU.SE> with the following
> command in the body of your email message:
>
> unsubscribe hecnet
>
> or from another account, besidessupratim at
riseup.net:
>
> unsubscribe hecnetsupratim at
riseup.net
>
> If you ever need to get in contact with the owner of the list,
> (if you have trouble unsubscribing, or have questions about the
> list itself) send email to<owner-hecnet at Update.UU.SE> .
> This is the general rule for most mailing lists when you need
> to contact a human.
>
> [Last updated on: Sun Sep 2 2:33:13 2001]
> Welcome to the mailing list for HECnet, the Hobbyist DECnet.
> If you want to be removed from the list, send a mail to
> majordomo at update.uu.se with "unsubscribe hecnet" in the body.
> For some information about HECnet, visit
>
http://www.update.uu.se/~bqt/hecnet.html