[Info-vax] Changing VMS node name

[Gotfryd]

On Mon, 9 Apr 2012, Single Stage to Orbit wrote:

> Yep, I did look at the VMS FAQ, but following the steps did not appear
> to change the node name. Perhaps I missed something. :(

  I could in the moment not say for sure on what condition,
but the steps mentioned in FAQ can be not enought.
  You may have a problem with improper SYS$NODE logical,
not set properly even if NET$CONFIGURE is run and the
system is rebooted.
  Of course, applies only when Decnet Plus is installed,
and *possibly* some other condition applies (I do not know)
  Do not know what (is set wrong), but at least the SYS$NODE
(with "old" nodename) is a visible symptom (also, as the name
is used on login screen by the X-windows server, it is
a "visible symptom" here), even if SCSNODE is changed (and
properly set both in current and active parameters) and
NET$CONFIGURE was properly run before rebooting.
  AFAIR (but not for sure), both BASIC and ADVANCED run of
NET$CONFIGURE did not help.
  Repettion od NET$CONFIGURE also did not help (for sure).

  May be a NET$CONFIGURE bug or dependence, as have found
a resolution, finding the reason I put away "for later"
(and still lies in the state ;))
  Must admit, that I did not check the values set in *.NCL

  The resolution - remove the logical(s) (works for sure)
or set it to the "new" name (may work).
  SYS$NODE may be enought, but remove both.

  *After* the change of the SCS node name and identifier(s)
(with reboot!) deassing the SYS$NODE* logicals:

$ deassing/system/executive SYS$NODE
$ deassing/system/executive SYS$NODE_FULLNAME

*then* run NET$CONFIGURE
...and report if that was the reason.

*Probably* setting the names to the "new" value also may
help, but did not remember the result (was while ago).

  Best regards, Gotfryd