How do you Rename a VMS Server

[Karen Lee_3]

I need to build a new VMS server but use an existing server name. I plan on building the server with the name TEST and after it's built and tested (including Network and Pathworks), I need to rename it to AUSTIN.

What all is involved in renaming a server? Bad idea?

[Jefferson Humber · Accepted solution]

Karen,

There's a page on the OpenVMS FAQ which highlights what needs to be changed.

http://h71000.www7.hp.com/faq/vmsfaq_007.html#mgmt9

I have done before with a cluster and it was OK, the license DB was the hardest bit. Single nodes are far easier to do, you shouldn't have too many problems.

Jeff

[Robert Gezelter]

Karen,

All that needs be done is change:

- the SCSNODE
- the SCSSYSTEMID
- the DECnet Node Name
- the DECnet Node number (must equal SCSSYSTEMID)

You will also need to recreate Queues and other things.

It is documented, and I have done it many times without problems.

- Bob Gezelter, http://www.rlgsc.com

[Colin Butcher]

Well, there's quite a few things you need to change:

SCSNODE
SCSSYSTEMID
DECnet node name
DECnet node address(es)
TCPIP host name(s)
TCPIP host address(es)
Proxy account database?
Rightslist entry
Queue names (usually a case of removing the 'old' ones)
Any node specific names written into command files by product installations (especially look for disc names in the $ format
Licence database for /include nodenames
DECnet and TCPIP databases on other systems
Proxy databases on other systems

As has already been pointed out - there are notes in the OpenVMS FAQ.

In general - be careful and you should be OK. It's not that difficult, but you will need to test everything carefully afterwards. There are quite a few places where the nodename and address get used.

Good luck,
Cheers, Colin.

[Thomas Ritter]

As Jefferson wrote, the license database will require careful consideration. If you have license with references to node names, be careful. You may need to obtain modified licenses.
This example would require a new license.

-----------------------------------
Issuer: LEGACY
Authorization: KBLOCK-NODEA-06214-001
Product Name: KBLOCK
Producer: LEGACY
Units: 0
Version: 4.46
Release Date: (none)
PAK Termination Date: 30-APR-2004
Availability: 0
Activity: 000000100
Options: NO_SHARE
Product Token: 9694D1B1-5DFSDFSDF9394280A
Hardware ID: 1978

Revision Level: 3
Status: Disabled
Command: DISABLE
Modified by user: SECRET
Modified on: 6-APR-2004 14:06:38.54
Include: NODEA

[Wim Van den Wyngaert]

I would suggest to do the 4th point of the faq : search the system disk (and others if you moved stuff of system disk) for the names of the old nodes after the change.

If you use sysman startup : node specific startup is possible. Some logins may test node names. Some startup script may test node names. Unless you know all, do your quality control with search.

Hey, since all .com files may test nodes names, search all files on all disks.

Wim

[Lachnitt_1]

Hi,

Don't forget that the IP-Config is stored to the Host name!
So if you change the Host name, you have to configure IP again!

Bye Kuddel