[HECnet] HECnet Area Request

Grab the file SG1::[DECNET]NU2.COM. Ignore the errors. It does depend on MIM being defined as 1.13. This procedure makes use of the file MIM::DU4:[DECNET]NODENAMES.DAT. Johnny creates this file for this procedure. I will not update your area nodes - that is your responsibility. It can be run interactively or via batch. It must be run from a priv'd account. -Steve From: owner-hecnet at Update.UU.SE on behalf of Johnny Billquist Sent: Mon 2/18/2013 19:36 To: hecnet at Update.UU.SE Cc: Ian McLaughlin Subject: Re: [HECnet] HECnet Area Request On 2013-02-19 01:29, Johnny Billquist wrote: > On 2013-02-18 19:28, Ian McLaughlin wrote: >> >> On 2013-02-18, at 10:19 AM, "Brian Schenkenberger, VAXman-" >> <system at TMESIS.COM> wrote: >>> >>> $ PIPE MCR NCP < FIX.CMD >> >> When I do this, I get a bunch of errors like: >> >> %NCP-W-INVPVA, Invalid parameter value , Name >> Remote node = 32.5 (YELLOW) >> >> >> Am I doing something wrong? > > Nope. (This on a VMS box with a rather outdated nodename database): > > $ mcr ncp > NCP>sho nod yellow > > > Node Volatile Summary as of 19-FEB-2013 01:26:09 > > Node State Active Delay Circuit Next node > Links > > 32.5 (YELLOW) ISA-0 1.13 (MIM) > NCP>tell mim sho nod yellow > > > Node Volatile Summary as of 19-FEB-2013 01:26:16 > > Node State Active Delay Circuit Next node > Links > > 13.5 (YELLOW) > > > Notice that the node YELLOW already exists, but with another number. > That cause an error when you try and set it. > > You need to clear nodes where you see that error. By the way, I could do a generic clear in the VMS command procedure, before starting the defines. Would people prefer that? Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol