DECnet on VMS - Revision history

Vaxorcist: /* Administration */ fixed typo

2024-10-13T08:03:56Z

‎Administration: fixed typo

2022-08-17T20:03:57Z

‎Administration: Added VMS V5.0 as the first version with DECnet included

2022-06-03T17:41:08Z

‎Licensing: "(VMS V5.x and newer)" added to "Licensing"

2007-05-17T01:42:15Z

added a couple links

2007-05-16T23:32:32Z

2007-05-16T19:42:55Z

‎Stopping

2007-05-16T19:38:36Z

spelling, and networking is a bad category

2007-05-16T19:38:07Z

2007-05-15T14:54:26Z

‎Remote login: Makering grammars gooder.

2007-05-15T02:51:21Z

‎Administration: Formatting whoopsie.

@@ Line 7: / Line 7: @@
 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.
+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)===

@@ Line 7: / Line 7: @@
 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. On modern versions of VMS (From what version on? 6.x? 7.x?), DECnet is bundled with VMS, but this cannot be taken for granted. This also makes the assumption that DECnet phase V is ''not'' enabled, something which most VMS installations after 7.x will default to.
+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)===

@@ Line 9: / Line 9: @@
 Note: This procedure requires DECnet to already be installed. On modern versions of VMS (From what version on? 6.x? 7.x?), DECnet is bundled with VMS, but this cannot be taken for granted. This also makes the assumption that DECnet phase V is ''not'' enabled, something which most VMS installations after 7.x will default to.
-===Licensing===
+===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"?)

← Older revision		Revision as of 01:42, 17 May 2007
Line 1:		Line 1:
−	This is a guide to basic administration and use of the DECnet subsystem of VMS.	+	This is a guide to basic administration and use of the [[DECnet]] subsystem of [[VMS]].

	==Administration==		==Administration==

@@ Line 86: / Line 86: @@
 and toy around using the command-line interface.
-[[Category: VMS practical guides]]
+[[Category: VMS Practical Guides]]
 [[Category: DECnet]]

← Older revision		Revision as of 19:42, 16 May 2007
Line 49:		Line 49:

	$ MCR NCP SET EXECUTOR STATE OFF		$ 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 ==		== Use ==

← Older revision		Revision as of 19:38, 16 May 2007
Line 81:		Line 81:

	[[Category: VMS practical guides]]		[[Category: VMS practical guides]]
−	[[Category: ~~DECNet]]~~	+	[[Category: DECnet]]
−	~~[[Category: Networking~~]]

@@ Line 58: / Line 58: @@
   $ 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 is jammed while in a session, press ^Y twice in succession. You will get the prompt:
+...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?