Difference between revisions of "DECnet on VMS"
m (Added another, wider category) |
m (→Administration: fixed typo) |
||
| (15 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | This is a guide to basic administration and use of the [[DECnet]] subsystem of [[VMS]]. | ||
| + | |||
| + | ==Administration== | ||
| + | |||
'''Setting up DECnet phase IV on VMS''' is a fairly straightforward procedure. | '''Setting up DECnet phase IV on VMS''' is a fairly straightforward procedure. | ||
Note: Before setting up any system I recommend you read up on [[DECnet Phase IV basics]]. | Note: Before setting up any system I recommend you read up on [[DECnet Phase IV basics]]. | ||
| − | Note: This procedure requires DECnet to already be installed. | + | Note: This procedure requires DECnet to already be installed. From VMS V5.0 onwards, DECnet is bundled with VMS. This also makes the assumption that DECnet phase V is ''not'' enabled, something which most VMS installations after 7.x will default to. |
| + | |||
| + | ===Licensing (VMS V5.x and newer)=== | ||
Make sure that your [[LMF|license]] is registered for DECnet. For an end-node (most cases) the license is DVNETEND. For a routing node, the license is DVNETRTG. (What the heck is "DVNETEXT"?) | Make sure that your [[LMF|license]] is registered for DECnet. For an end-node (most cases) the license is DVNETEND. For a routing node, the license is DVNETRTG. (What the heck is "DVNETEXT"?) | ||
| Line 22: | Line 28: | ||
$ LICENSE LIST DVNETEND/FULL | $ LICENSE LIST DVNETEND/FULL | ||
| + | |||
| + | === Configuring === | ||
To invoke the interactive DECnet configuration script, run (as SYSTEM or as a user with sufficient privileges): | To invoke the interactive DECnet configuration script, run (as SYSTEM or as a user with sufficient privileges): | ||
| Line 28: | Line 36: | ||
The [[DCL]] script will guide you through setting up your system with DECnet. | The [[DCL]] script will guide you through setting up your system with DECnet. | ||
| + | |||
| + | === Starting === | ||
To start DECnet, run | To start DECnet, run | ||
| Line 33: | Line 43: | ||
$ SET DEF SYS$MANAGER | $ SET DEF SYS$MANAGER | ||
$ @STARTNET | $ @STARTNET | ||
| + | |||
| + | === Stopping === | ||
To stop it, run | To stop it, run | ||
| Line 38: | Line 50: | ||
$ MCR NCP SET EXECUTOR STATE OFF | $ MCR NCP SET EXECUTOR STATE OFF | ||
| − | [[Category: VMS | + | this will immediately terminate all DECnet connections on the system. If, however, you want to shut it down a little more softly, execute |
| + | |||
| + | $ MCR NCP SET EXECUTOR STATE SHUT | ||
| + | |||
| + | which will keep existing connections, but make it impossible to open new connections. Once all connections have been closed, DECnet is fully shut down and the NETACP process ceases to execute. | ||
| + | |||
| + | == Use == | ||
| + | |||
| + | === Remote login === | ||
| + | |||
| + | Remote login over DECnet is trivial. Simply run | ||
| + | |||
| + | $ SET HOST ''hostname'' | ||
| + | |||
| + | ...and if the network is functioning, and the remote end is alive and configured to accept remote logins, you will get a login prompt. If the connection jams while in a session, press ^Y twice in succession. You will get the prompt: | ||
| + | |||
| + | Are you repeating ^Y to abort the remote session on node PYTHON? | ||
| + | |||
| + | If you answer yes, the connection will be terminated. | ||
| + | |||
| + | === Realtime chat === | ||
| + | |||
| + | VMS has a really neato UNIX talk(1)-a-like called PHONE. Simply run... | ||
| + | |||
| + | $ PHONE [''node::'']''username'' | ||
| + | |||
| + | ...and the person on the other end will recieve a call he can answer using the command '''PHONE ANSWER'''. This system allows for phone conferencing, file transfer, and many other really neat things. | ||
| + | |||
| + | === Mail === | ||
| + | |||
| + | VMS also has a mail system. It is relatively self-explanatory, so you should just try to run | ||
| + | |||
| + | $ MAIL | ||
| + | |||
| + | and toy around using the command-line interface. | ||
| + | |||
| + | [[Category: VMS Practical Guides]] | ||
| + | [[Category: DECnet]] | ||
Latest revision as of 09:03, 13 October 2024
This is a guide to basic administration and use of the DECnet subsystem of VMS.
Contents
Administration
Setting up DECnet phase IV on VMS is a fairly straightforward procedure.
Note: Before setting up any system I recommend you read up on DECnet Phase IV basics.
Note: This procedure requires DECnet to already be installed. From VMS V5.0 onwards, DECnet is bundled with VMS. This also makes the assumption that DECnet phase V is not enabled, something which most VMS installations after 7.x will default to.
Licensing (VMS V5.x and newer)
Make sure that your license is registered for DECnet. For an end-node (most cases) the license is DVNETEND. For a routing node, the license is DVNETRTG. (What the heck is "DVNETEXT"?)
To register and load the license. An example is shown below:
$ LICENSE REGISTER DVNETEND - /ISSUER=OPENVMS_HOBBYIST - /AUTHORIZATION=DECUS-USA-xxxxx-xxxxxxx - /PRODUCER=DEC - /UNITS=0 - /TERMINATION_DATE=9-APR-2008 - /ACTIVITY=CONSTANT=100 - /CHECKSUM=x-xxxx-xxxx-xxxx-xxxx $ LICENSE LOAD DVNETEND
To check the license, run
$ LICENSE LIST DVNETEND/FULL
Configuring
To invoke the interactive DECnet configuration script, run (as SYSTEM or as a user with sufficient privileges):
$ SET DEF SYS$MANAGER $ @NETCONFIG
The DCL script will guide you through setting up your system with DECnet.
Starting
To start DECnet, run
$ SET DEF SYS$MANAGER $ @STARTNET
Stopping
To stop it, run
$ MCR NCP SET EXECUTOR STATE OFF
this will immediately terminate all DECnet connections on the system. If, however, you want to shut it down a little more softly, execute
$ MCR NCP SET EXECUTOR STATE SHUT
which will keep existing connections, but make it impossible to open new connections. Once all connections have been closed, DECnet is fully shut down and the NETACP process ceases to execute.
Use
Remote login
Remote login over DECnet is trivial. Simply run
$ SET HOST hostname
...and if the network is functioning, and the remote end is alive and configured to accept remote logins, you will get a login prompt. If the connection jams while in a session, press ^Y twice in succession. You will get the prompt:
Are you repeating ^Y to abort the remote session on node PYTHON?
If you answer yes, the connection will be terminated.
Realtime chat
VMS has a really neato UNIX talk(1)-a-like called PHONE. Simply run...
$ PHONE [node::]username
...and the person on the other end will recieve a call he can answer using the command PHONE ANSWER. This system allows for phone conferencing, file transfer, and many other really neat things.
VMS also has a mail system. It is relatively self-explanatory, so you should just try to run
and toy around using the command-line interface.
