[HECnet] HECnet Area Request

[Erik Olofsen]

May be it is best if FIX.COM does not change the node parameters
of those in the local area.

On the other hand, your solution of purging/clearing names only
would only affect unregistered names.

Would the ncp copy command from MIM work (although I'm not sure
it is completely safe)?

Erik

On Tue, Feb 19, 2013 at 12:54:57PM +0100, Johnny Billquist wrote:
On 2013-02-19 08:19, Erik Olofsen wrote:
Johnny,

After the "define node"s in FIX.COM without "set node" I thought it would
be easiest to reboot, which gave errors reading the data base, and I think
this happened because the executor data had also been purged. After setting
the executor data, I could define all nodes.

Oh! Good point. I forgot about the volatile database. I'll fix that.

What happened with the executor data? What should I fix?

	Johnny


Erik

On Tue, Feb 19, 2013 at 02:02:59AM +0100, Johnny Billquist wrote:
On 2013-02-19 01:48, Ian McLaughlin wrote:
Yes, I would like this. I assume that you are the authoritive list, so I have no need to keep any data on my end.   A generic script that I can execute on the command line that clears and updates all in one would be great.

Ok. Done. For VMS users, just grab MIM::FIX.COM, and run it under DCL,
with appropriate privileges, and you'll have an up-to-date nodename
database.

	Johnny


Thanks.

Ian

Sent from my iPad

On 2013-02-18, at 4:36 PM, Johnny Billquist <bqt at softjar.se> wrote:

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


---
Filter service subscribers can train this email as spam or not-spam here:     http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=76F0C5CA7A2C11E29BFCAD6693ED0201


--
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


-- 
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