[HECnet] DECnet-VAX V3.0, VMS V3.5 (Was Re: Oldest VAX/VMS for VAX-11/730 on HECNET) --> retract

[Paul Koning]

You may have a license problem.

If you have a DECnet that supports Ethernet, it must be Phase IV (or V, of course).  That means it is required to know about areas.  If you have a version that doesn't deal with areas, either it is terminally broken or it is crippled in a way that disables multi-area configurations.  You'll need to fix that in order to use it on HECnet.  While it's certainly possible to put a Phase III node anywhere in HECnet, with the reachability limitations that Phase III has, it isn't possible to use a "broken areas" Phase "IV" node at all.  (Well, unless you can connect it into area 1, I suppose.)

	paul

> On Dec 16, 2021, at 11:08 AM, Supratim Sanyal <supratim at riseup.net> wrote:
> 
> On 12/16/2021 05:41, R. Voorhorst wrote:
> > Question  remains, how did you get Decnet 3.0 running and did you obtain the necessary patch.
> Yes, applied the license. I  chose VAX/VMS 3.5 because in  March of 2020 you had gone as far as getting a license error on VMS3.0 that said it needed VMS3.4+. I also tried to use the licensed NETACP.EXE on vms3.0, does not look promising, says it has problems loading. At this point, Cisco may be  the answer with the nifty feature for DECnet NAT, I will explore it sometime. Anyway, my experiments are here if you or anyone is interested: https://www.dropbox.com/sh/x4e6ie4lrwi9wns/AABMogcguAcL8xPwMIDxOtNva?dl=0
> 
> On 12/16/2021 04:55, Johnny Billquist wrote:
> > Uh? The mac address AA-00-04-00-2A-7C means it has address 31.42. Just sayin...
> It's forced at the Linux/SimH level.
> 
> On 12/15/2021 20:05, Paul Koning wrote:
> > You've got to set MAX AREA large enough; 63 is the obvious value.  With it not set, the system apparently is defaulting it to 1, so when you gave it a node address without area number it defaulted the area number to 1, which of course can't work.
> 
> There is no option, at least in NCP, for any Area parameters.
> 
> NCP>help set exec
> 
> SET
> 
>   EXECUTOR
> 
> 
>     Use the SET EXECUTOR command to create or modify parameters in the
>     volatile database which controls the network on the executor node. Use
>     the DEFINE EXECUTOR command to create or modify parameters in the
>     volatile database which controls the network on the executor node.
> 
> 
>     SET     EXECUTOR        (parameters ...)
> 
> 
>     Additional information available:
> 
>     ALL        ADDRESS node-address  BROADCAST ROUTING TIMER
>     BUFFER SIZE number    COUNTER TIMER seconds DEFAULT ACCESS
>     DELAY FACTOR          DELAY WEIGHT          IDENTIFICATION
>     INACTIVITY TIMER      INCOMING TIMER        MAXIMUM ADDRESS
>     MAXIMUM BROADCAST NONROUTERS     MAXIMUM BROADCAST ROUTERS
>     MAXIMUM BUFFERS       MAXIMUM CIRCUITS      MAXIMUM COST
>     MAXIMUM HOPS          MAXIMUM LINKS         MAXIMUM VISITS
>     NONPRIVILEGED         OUTGOING TIMER        PIPELINE QUOTA
>     PRIVILEGED RETRANSMIT FACTOR     ROUTING TIMER
>     SEGMENT BUFFER SIZE   STATE      SUBADDRESS range      TYPE
>     Examples   NODE
> 
> SET EXECUTOR Subtopic?
> 
> SET EXECUTOR Subtopic? ex
> 
> SET
> 
>   EXECUTOR
> 
>     Examples
> 
> 
> 
>            NCP>SET EXECUTOR ADDRESS 11 BUFFER SIZE 576
> 
>                This command sets the executor node's address to 11 and buffer
>                size to 576 bytes.
> 
>            NCP>SET EXECUTOR STATE ON
> 
>                This command sets the executor node's operational state to ON.
> 
> 
> SET EXECUTOR Subtopic? ^Z
> NCP>exit
> $
> 
>