On Tue, 19 Feb 2013 08:49:52 +0100, you wrote:
NCP> copy known nodes from rullfs using permanent to volatile
Would that also work from MIM?
But other executor parameters would remain lost after a purge.
Just out of curiosity, which executor parameters would you loose with 'copy
known nodes'? We (Italian DECnet) usually do a 'copy known nodes from xxxxxx
using permanent to both with purge' and never noticed any problems (as long as
there are no "private" nodes locally defined and not registered into the node
we consider the authoritative database for node names).
The above works for VMS (at least down to V4.7); TOPS-10 has to be manually
updated; RSTS too; I do not remember about TOPS-20 any more: too much time has
passed since my last experiments with it.
Bye, :)
G.
Yes; but "SET KNOWN NODES *" gives a syntax error. This seems to work:
NCP> copy known nodes from rullfs using permanent to volatile
Would that also work from MIM?
But other executor parameters would remain lost after a purge.
On Mon, Feb 18, 2013 at 11:31:40PM -0800, Ian McLaughlin wrote:
Perhaps the script needs a "CLEAR NODE *" at the beginning and a "SET KNOWN NODES *" at the end?
Ian
On 2013-02-18, at 11:19 PM, Erik Olofsen <e.olofsen at xs4all.nl> 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.
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=76F0C5CA7A2C11E29…
--
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=C40A12D47A6411E28…
Perhaps the script needs a "CLEAR NODE *" at the beginning and a "SET KNOWN NODES *" at the end?
Ian
On 2013-02-18, at 11:19 PM, Erik Olofsen <e.olofsen at xs4all.nl> 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.
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=76F0C5CA7A2C11E29…
--
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=C40A12D47A6411E28…
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.
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=76F0C5CA7A2C11E29…
--
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
On 19 Feb 2013, at 02:00, Ian McLaughlin <ian at platinum.net> wrote:
D'oh!
Sorry - thanks for catching the typo. I typed it correctly on 7.3, but wrong on 8.3.
;)
Time for sleep methinks :)
Perhaps. :)
Ian
On 2013-02-18, at 10:58 PM, Cory Smelosky <b4 at gewt.net> wrote:
On 19 Feb 2013, at 01:57, Ian McLaughlin <ian at platinum.net> wrote:
Johnny,
The script appears to work as advertised on VAX VMS 7.3. However, on Alpha VMS 8.3, I get this:
$ @mim::fix.cmd
FIX.COM, instead.
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
(etc)
Any ideas?
Ian
On 2013-02-18, at 5:02 PM, Johnny Billquist <bqt at softjar.se> 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=76F0C5CA7A2C11E29…
--
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=2190C4B47A3011E28…
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=DAD6594E7A6111E28…
D'oh!
Sorry - thanks for catching the typo. I typed it correctly on 7.3, but wrong on 8.3.
Time for sleep methinks :)
Ian
On 2013-02-18, at 10:58 PM, Cory Smelosky <b4 at gewt.net> wrote:
On 19 Feb 2013, at 01:57, Ian McLaughlin <ian at platinum.net> wrote:
Johnny,
The script appears to work as advertised on VAX VMS 7.3. However, on Alpha VMS 8.3, I get this:
$ @mim::fix.cmd
FIX.COM, instead.
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
(etc)
Any ideas?
Ian
On 2013-02-18, at 5:02 PM, Johnny Billquist <bqt at softjar.se> 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=76F0C5CA7A2C11E29…
--
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=2190C4B47A3011E28…
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=DAD6594E7A6111E28…
On 19 Feb 2013, at 01:57, Ian McLaughlin <ian at platinum.net> wrote:
Johnny,
The script appears to work as advertised on VAX VMS 7.3. However, on Alpha VMS 8.3, I get this:
$ @mim::fix.cmd
FIX.COM, instead.
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
(etc)
Any ideas?
Ian
On 2013-02-18, at 5:02 PM, Johnny Billquist <bqt at softjar.se> 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=76F0C5CA7A2C11E29…
--
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=2190C4B47A3011E28…
Johnny,
The script appears to work as advertised on VAX VMS 7.3. However, on Alpha VMS 8.3, I get this:
$ @mim::fix.cmd
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\NAME\
(etc)
Any ideas?
Ian
On 2013-02-18, at 5:02 PM, Johnny Billquist <bqt at softjar.se> 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=76F0C5CA7A2C11E29…
--
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=2190C4B47A3011E28…
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
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=76F0C5CA7A2C11E29…
--
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
