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
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.
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…
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-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.
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-18 19:02, Ian McLaughlin wrote:
(bumping an old thread)
Johnny,
excuse my ignorance, but how do I execute your fix.cmd inside NCP? Is there a VMS DCL one-liner that I can type that will execute NCP and cause it to run your script?
Doh! I have always assumed that VMS was as generic as RSX, and that basically any program with a standard like interface like NCP took @filename as a possible command, meaning to read commands from that file. It would appear VMS don't do that.
Brian's sugegstion using PIPE looks reasonable, but I can create a more VMS-specific command file as well. Hang on...
I now have a MIM::US:[DECNET]FIX.COM, which should be usable from DCL on VMS...
Johnny
Thanks!
Ian
On 2013-01-29, at 10:53 AM, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-29 19:48, Ian McLaughlin wrote:
Johnny
Did you manage to fix the problem with mim not reporting the full node list? It's about time I grabbed an updated copy (with all of the new additions) but I didn't want to grab something that was corrupt.
I've been fighting MIM about that, but for some reason it just will not cooperate. I have two solutons for you:
1. Copy each area as individual commands (MIM knows it all, it just seems that the list of known nodes does not list all known nodes now. Bug in NCP methinks at this point...)
2. Grab MIM::US:[DECNET]FIX.CMD which contains all the DEFINE commands for NCP for all the nodes, and run it in NCP on your machine.
I can create command files in other formats easily if there are any special requests. Just let me know...
Johnny
Ian
On 2013-01-29, at 10:45 AM, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-29 17:22, Brian Hechinger wrote:
On 1/21/2013 5:36 PM, Dave McGuire wrote:
On 01/21/2013 05:20 PM, Johnny Billquist wrote:
A17RTR:: would work... :)
Hey, that's a good scheme. I will likely do that as well.
Several areas already do that. :-)
Excellent. :-) Would you please remove "GW" at 61.1 and add
"A61RTR" as 61.1023?
Sign me up for that as well.
Please add A52RTR as 52.1023
Done.
Johnny
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=0C3058926A4411E28…
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=33556D626A4511E2B…
--
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
Fred <fcoffey at misernet.net> writes:
On Mon, 18 Feb 2013, Sampsa Laine wrote:
On 18 Feb 2013, at 16:01, "Brian Schenkenberger, VAXman-"
<system at TMESIS.COM> wrote: > >> LSE is in the DECSET tool kit. If you
find a kit for DECSET, you can then >> selectively install the pieces in
it that you desire. >> >> LSE is built on/with TPU, BTW.
(To Brian)
On Mon, 18 Feb 2013, Sampsa Laine wrote:
On 18 Feb 2013, at 16:01, "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote:
LSE is in the DECSET tool kit. If you find a kit for DECSET, you can then
selectively install the pieces in it that you desire.
LSE is built on/with TPU, BTW.
(To Brian)
