How to change node name in NET$CONFIG.DAT (DECnet-Plus)

[TonyMcGrath]

Hi guys,
I've just through the exercise of changing the node names in a 2-node cluster (2 x DS25, VMS 7.3-2). I followed the procedure in the VMS FAQ and most of it has gone to plan.
BUT! The SYS$NODE, SYS$NODE_FULLNAME and SYS$DECDTM_NODE_NAME logicals still point to the old node names.
I can see the old names in the SYS$SYSTEM:NET$CONFIG.DAT files on each node but I cannot for the life of me work out how to update that file. I've used the NET$CONFIGURE.COM file to change the name but it will not update NET$CONFIG.DAT
Am I on the right track, is that the correct file to modify. If so, how?
Am I missing something obvious?
Thanks in advance,
Tony

[Wim Van den Wyngaert · Accepted solution]

mc ncl rename new name local:.xxxx ?

[John Eerenberg]

Tony,
I've tried this in the past and two DECnet-Plus experts steered me away from use net$config to avoid the side effects you are seeing. In fact, they both say once you've run net$config for the initial install, in general never run it again.

Try Wim's suggestion first.

If that doesn't work, then look at editing the .ncl files for the relevent occurences (use caution, backup the .ncl files, etc.).

I'm sure suggesting to edit .ncl files will spark a debate, but IMHO it is the best way to take care of such things as node renames.

[TonyMcGrath]

Wim, you're a champion, absolutely spot on, worked a treat. It'd be real handy if that NCL command was in the VMS FAQ. Redefined the logicals as well as updating the NET$CONFIG.DAT file.

John, I had already searched all the SYS$MANAGER:*.NCL files for the node names. They're not in there. Should they be?

[Wim Van den Wyngaert]

Tony,

Had it several times and had to look too.

If you modify the ncl files, net$configure is not going to see them (it has some files containing all the parameters that are in the ncl scripts). Also : don't use logicals for the ncl files : net$configure doesn't handle it correctly.

Wim

[John Eerenberg]

> If you modify the ncl files, net$configure is
> not going to see them (it has some files
> containing all the parameters that are in the
> ncl scripts). Also : don't use logicals for
> the ncl files : net$configure doesn't handle
> it correctly.
Yes. That is our experince too. We have to use logical names though. I have removed every single file that is specific to a node to a common disk. This way I can upgrade or patch or both in a matter of minutes on the production nodes. Did an upgrade from VMS V7.2-x to VMS V7.3 in a matter of minutes. Alas, the price we pay is we do not use net$config anymore. I consider it worth it because of the benefits.
So you are defintely correct. I have chosen to travel the road less traveled. ;-)

[Wim Van den Wyngaert]

John,

Or save your .ncl files, use net$configure and add some of the generated files to your saved .ncl set. Then restore your files.

Wim