NU2.COM parses NETNODES.DAT for you already. That is how it works. You always have the latest DECnet database to work with.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Wednesday, October 09, 2013 4:50 PM
To: hecnet at Update.UU.SE
Cc: Hans Vlems
Subject: Re: [HECnet] Nodelist errors from MIM::
On 2013-10-09 22:27, Hans Vlems wrote:
$ mc ncp copy known nodes from sgc to both
Should give the same errors, assuming SGC has an up to date nodename
database.
The problem is when node names gets moved to new addresses. Old
information is not cleared out by an NCP COPY command, so you might get
duplicate information in that case.
There is a MIM::US:[DECNET]FIX.COM which will do the right thing on a
VMS system for you. And it gets updated whenever the nodename database
is updated, so VMS users could always use that, if they just want the
same nodename database as MIM.
An alternative is also to suck down MIM::US:[DECNET]NODENAMES.DAT and
parse it yourself, and do whatever you want to.
Johnny
*Van: *Steve Davidson
*Verzonden: *woensdag 9 oktober 2013 22:07
*Aan: *hecnet at Update.UU.SE
*Beantwoorden: *hecnet at Update.UU.SE
*Onderwerp: *RE: [HECnet] Nodelist errors from MIM::
$ Copy sgc::nu2.com *.*
$ @nu2
Be careful that your SCSSYSTEMID and DECnet node number are the same or
it will be a mess. You have been warned!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:04 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
Refresh my memory, how do I invoke that?
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 9 Oct 2013, at 22:02, Steve Davidson <jeep at scshome.net> wrote:
Sampsa,
As long as your SCSSYSTEMID and your DECnet node number are in sync
you
can use NetUpdate from SGC:: or SG
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 2:57 PM
To: hecnet at Update.UU.SE
Subject: [HECnet] Nodelist errors from MIM::
When I tried to update my nodelist just now on CHIMPY, I got a few
errors in Area 9.
Any ideas?
--- SNIP ----
CHIMPY$ mcr ncp copy known node from mim to both
%NCP-W-INVPVA, Invalid parameter value , Address
%NCP-W-INVPVA, Invalid parameter value , Address
Remote node = 9.1 (GEWT)
%NCP-W-INVPVA, Invalid parameter value , Address
%NCP-W-INVPVA, Invalid parameter value , Address
Remote node = 9.2 (MANDY)
%NCP-W-INVPVA, Invalid parameter value , Address
%NCP-W-INVPVA, Invalid parameter value , Address
Remote node = 9.4 (MINDY)
--
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
I've never trashed anything with that command. Served me well.
Van: Steve Davidson
Verzonden: woensdag 9 oktober 2013 22:35
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] Nodelist errors from MIM::
That can/will trash a cluster DECnet node database. Do NOT do it that way. Others on this have already been burned when running clusters.
-Steve
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Hans Vlems
Sent: Wednesday, October 09, 2013 4:27 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
$ mc ncp copy known nodes from sgc to both
Van: Steve Davidson
Verzonden: woensdag 9 oktober 2013 22:07
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] Nodelist errors from MIM::
$ Copy sgc::nu2.com *.*
$ @nu2
Be careful that your SCSSYSTEMID and DECnet node number are the same or
it will be a mess. You have been warned!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:04 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
Refresh my memory, how do I invoke that?
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 9 Oct 2013, at 22:02, Steve Davidson <jeep at scshome.net> wrote:
> Sampsa,
>
> As long as your SCSSYSTEMID and your DECnet node number are in sync
you
> can use NetUpdate from SGC:: or SG
>
> -----Original Message-----
> From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
> Behalf Of Sampsa Laine
> Sent: Wednesday, October 09, 2013 2:57 PM
> To: hecnet at Update.UU.SE
> Subject: [HECnet] Nodelist errors from MIM::
>
> When I tried to update my nodelist just now on CHIMPY, I got a few
> errors in Area 9.
>
> Any ideas?
>
> --- SNIP ----
>
> CHIMPY$ mcr ncp copy known node from mim to both
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.1 (GEWT)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.2 (MANDY)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.4 (MINDY)
>
>
>
>
On Wed, 9 Oct 2013, Ian McLaughlin wrote:
On Oct 9, 2013, at 1:56 PM, Sampsa Laine <sampsa at mac.com> wrote:
As far as I'm concerned, MIM has the canonical (and most up-to-date) node database of HECnet. Is this assumption correct?
If it's not in MIM::, then it doesn't exist, as far as I'm concerned ;) (even if it's on my own network)
My nodes are often in MIM::. Sometimes multiple times!
Ian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Oct 9, 2013, at 1:56 PM, Sampsa Laine <sampsa at mac.com> wrote:
As far as I'm concerned, MIM has the canonical (and most up-to-date) node database of HECnet. Is this assumption correct?
If it's not in MIM::, then it doesn't exist, as far as I'm concerned ;) (even if it's on my own network)
Ian
On 2013-10-09 22:56, Sampsa Laine wrote:
On 2013-10-09 22:35, Steve Davidson wrote:
That can/will trash a cluster DECnet node database. Do NOT do it
that way. Others on this have already been burned when running clusters.
I assume that is because you have nodename information locally that is not known at MIM, in which case yes, you might get burned.
I try to register all my node name/number allocations with BQT, seems like the sensible thing to do, have them in a central database somewhere.
As far as I'm concerned, MIM has the canonical (and most up-to-date) node database of HECnet. Is this assumption correct?
Yes. As far as "global" nodenames are concerned. Of course, since anyone can have other definitions of their own, for any individual, they might have more information that MIM do not know about.
But MIM is the only machine which I keep the database of all nodes that I'm told about. Since DECnet do not force a global namespace, this is a totally voluntary database, as a convenience to those who care.
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-10-09 22:35, Steve Davidson wrote:
That can/will trash a cluster DECnet node database. Do NOT do it
that way. Others on this have already been burned when running clusters.
I assume that is because you have nodename information locally that is not known at MIM, in which case yes, you might get burned.
I try to register all my node name/number allocations with BQT, seems like the sensible thing to do, have them in a central database somewhere.
As far as I'm concerned, MIM has the canonical (and most up-to-date) node database of HECnet. Is this assumption correct?
There is a MIM::US:[DECNET]FIX.COM which will do the right thing on a VMS system for you. And it gets updated whenever the nodename database is updated, so VMS users could always use that, if they just want the same nodename database as MIM.
Yup, FIX.COM fixed it.
On 2013-10-09 22:35, Steve Davidson wrote:
That can/will trash a cluster DECnet node database. Do NOT do it
that way. Others on this have already been burned when running clusters.
I assume that is because you have nodename information locally that is not known at MIM, in which case yes, you might get burned.
Johnny
-Steve
------------------------------------------------------------------------
*From:* owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
*On Behalf Of *Hans Vlems
*Sent:* Wednesday, October 09, 2013 4:27 PM
*To:* hecnet at Update.UU.SE
*Subject:* Re: [HECnet] Nodelist errors from MIM::
$ mc ncp copy known nodes from sgc to both
*Van: *Steve Davidson
*Verzonden: *woensdag 9 oktober 2013 22:07
*Aan: *hecnet at Update.UU.SE
*Beantwoorden: *hecnet at Update.UU.SE
*Onderwerp: *RE: [HECnet] Nodelist errors from MIM::
$ Copy sgc::nu2.com *.*
$ @nu2
Be careful that your SCSSYSTEMID and DECnet node number are the same or
it will be a mess. You have been warned!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:04 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
Refresh my memory, how do I invoke that?
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 9 Oct 2013, at 22:02, Steve Davidson <jeep at scshome.net> wrote:
> Sampsa,
>
> As long as your SCSSYSTEMID and your DECnet node number are in sync
you
> can use NetUpdate from SGC:: or SG
>
> -----Original Message-----
> From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
> Behalf Of Sampsa Laine
> Sent: Wednesday, October 09, 2013 2:57 PM
> To: hecnet at Update.UU.SE
> Subject: [HECnet] Nodelist errors from MIM::
>
> When I tried to update my nodelist just now on CHIMPY, I got a few
> errors in Area 9.
>
> Any ideas?
>
> --- SNIP ----
>
> CHIMPY$ mcr ncp copy known node from mim to both
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.1 (GEWT)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.2 (MANDY)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.4 (MINDY)
>
>
>
>
--
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-10-09 22:27, Hans Vlems wrote:
$ mc ncp copy known nodes from sgc to both
Should give the same errors, assuming SGC has an up to date nodename database.
The problem is when node names gets moved to new addresses. Old information is not cleared out by an NCP COPY command, so you might get duplicate information in that case.
There is a MIM::US:[DECNET]FIX.COM which will do the right thing on a VMS system for you. And it gets updated whenever the nodename database is updated, so VMS users could always use that, if they just want the same nodename database as MIM.
An alternative is also to suck down MIM::US:[DECNET]NODENAMES.DAT and parse it yourself, and do whatever you want to.
Johnny
*Van: *Steve Davidson
*Verzonden: *woensdag 9 oktober 2013 22:07
*Aan: *hecnet at Update.UU.SE
*Beantwoorden: *hecnet at Update.UU.SE
*Onderwerp: *RE: [HECnet] Nodelist errors from MIM::
$ Copy sgc::nu2.com *.*
$ @nu2
Be careful that your SCSSYSTEMID and DECnet node number are the same or
it will be a mess. You have been warned!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:04 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
Refresh my memory, how do I invoke that?
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 9 Oct 2013, at 22:02, Steve Davidson <jeep at scshome.net> wrote:
> Sampsa,
>
> As long as your SCSSYSTEMID and your DECnet node number are in sync
you
> can use NetUpdate from SGC:: or SG
>
> -----Original Message-----
> From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
> Behalf Of Sampsa Laine
> Sent: Wednesday, October 09, 2013 2:57 PM
> To: hecnet at Update.UU.SE
> Subject: [HECnet] Nodelist errors from MIM::
>
> When I tried to update my nodelist just now on CHIMPY, I got a few
> errors in Area 9.
>
> Any ideas?
>
> --- SNIP ----
>
> CHIMPY$ mcr ncp copy known node from mim to both
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.1 (GEWT)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.2 (MANDY)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.4 (MINDY)
>
>
>
>
--
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
That can/will trash a cluster DECnet node database. Do NOT do it that way. Others on this have already been burned when running clusters.
-Steve
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Hans Vlems
Sent: Wednesday, October 09, 2013 4:27 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
$ mc ncp copy known nodes from sgc to both
Van: Steve Davidson
Verzonden: woensdag 9 oktober 2013 22:07
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] Nodelist errors from MIM::
$ Copy sgc::nu2.com *.*
$ @nu2
Be careful that your SCSSYSTEMID and DECnet node number are the same or
it will be a mess. You have been warned!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:04 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
Refresh my memory, how do I invoke that?
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 9 Oct 2013, at 22:02, Steve Davidson <jeep at scshome.net> wrote:
> Sampsa,
>
> As long as your SCSSYSTEMID and your DECnet node number are in sync
you
> can use NetUpdate from SGC:: or SG
>
> -----Original Message-----
> From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
> Behalf Of Sampsa Laine
> Sent: Wednesday, October 09, 2013 2:57 PM
> To: hecnet at Update.UU.SE
> Subject: [HECnet] Nodelist errors from MIM::
>
> When I tried to update my nodelist just now on CHIMPY, I got a few
> errors in Area 9.
>
> Any ideas?
>
> --- SNIP ----
>
> CHIMPY$ mcr ncp copy known node from mim to both
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.1 (GEWT)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.2 (MANDY)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.4 (MINDY)
>
>
>
>
