Customising VMS and networking on a new TCS machine

These notes are designed to be used after the installation of VMS on a new machine which is a replacement for an existing machine. If VMS has simply been upgraded, these notes can be used to check whether the existing setup is correct.

For a new installation, these notes should be read in conjunction with the post-installation procedures given in the Upgrade and Installation Manual.

Login to the new machine as SYSTEM.

Register licenses

Check the currently registered licences:

• SHOW LIC

The VMS licence should be listed, for an Alphastation it is called OPENVMS-ALPHA. If it is not listed, it must be registered using the data on the paper licence for the machine in question.

The following licences need to be registered using the VMS PAKS CD: DW-MOTIF, OPENVMS-ALPHA-USER, DVNETEND, VOLSHAD & UCX.

On the development machine, the following licences are also required from the VMS PAKS CD: C, FORTRAN & VAXSET.

Backup disk

Backup to the second disk. This disk will be used as a shadow disk later in this process, but it is convenient to use it as a temporary backup disk in the meantime.

Modify VMS system files

This applies specifically to VMS 7.3-2, but should apply to later versions also. For later versions of VMS, check whether the modifications are already present, in which case there will be less to do!

The following files are in SYS$MANAGER, the home directory of the SYSTEM account. These files can be changed before networking is configured.

SYLOGICALS.COM

• uncomment line: DEFINE /SYSTEM/TRANSLATION_ATTRIBUTES=TERMINAL EVE$KEYPAD EDT
• after line: $! Define any site-specific logical names below
  add line: $ DEFINE/SYSTEM/EXEC SYS$DECDTM_INHIBIT YES

SYLOGIN.COM

• copy symbols from a current SYLOGIN.COM file using cut-and-paste in the editor
• delete lines that apply to third-party TCPIP packages

DECW$PRIVATE_SERVER_SETUP.COM

• COPY DECW$PRIVATE_SERVER_SETUP.TEMPLATE DECW$PRIVATE_SERVER_SETUP.COM
• Uncomment line: decw$server_transports == "DECNET,LOCAL,TCPIP"

Configuring networks

For new installations, set up the queue manager

If a new machine has VMS already installed, the queue manager might have been set up. To check this, enter the command:

• SHOW/QUEUE/MANAGER/FULL

The following response shows that a queue manager has been set up and is running:

Master file: SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;

Queue manager SYS$QUEUE_MANAGER, running, on LPAS7::
/ON=(*)
Database location: SYS$COMMON:[SYSEXE]

If the queue manager has not been set up, enter the command:

• START/QUEUE/MANAGER/NEW

Configure and start DECnet

Enter the command:

• @NETCONFIG

and respond to the prompts:

• DECnet node name should be LPASn
• DECnet address should be 62.N where N = 100+n
• take defaults for all other questions
• DECnet should be started

Add DECnet nodes to database

Add other VMS machines to the remote node database, the following commands show how to add the current VMS machines.

• MC NCP DEFINE NODE 62.88 NAME LPVG
• MC NCP DEFINE NODE 62.93 NAME LPVF
• MC NCP DEFINE NODE 62.101 NAME LPAS1
• MC NCP DEFINE NODE 62.102 NAME LPAS2
• MC NCP DEFINE NODE 62.103 NAME LPAS3
• MC NCP DEFINE NODE 62.104 NAME LPAS4
• MC NCP SET NODE 62.88 NAME LPVG
• MC NCP SET NODE 62.93 NAME LPVF
• MC NCP SET NODE 62.101 NAME LPAS1
• MC NCP SET NODE 62.102 NAME LPAS2
• MC NCP SET NODE 62.103 NAME LPAS3
• MC NCP SET NODE 62.104 NAME LPAS4

Configure and start TCPIP

Before starting, obtain the IP address and a list of name servers (BIND servers) from CFG. To list the name servers on a particular VMS machine, use the command:

• TCPIP SHOW NAME

Enter the command:

• @SYS$STARTUP:TCPIP$CONFIG

choose 1. Domain

domain name = ing.iac.es

choose 2. Interfaces

choose 1. Configure interface manually
host name = lpasn.ing.iac.es
Internet address = 161.72.6.xxx
Network mask = 255.255.255.0
Broadcast mask = 161.72.6.255
Configure failover target for failSAFE IP : NO

choose 3. Routing

Dynamic ROUTED or GATED? : NO
Do you want to configure a default route? : YES
Default Gateway : 161.72.6.1
Default Gateway host name: [Return]

choose 4. BIND Resolver

Enter your BIND server name: enter IP address from list
[Return] to skip entering name
Repeat for other addresses on list
[Return] to exit

choose 5. Time Zone

should say that time zone verified OK

choose option 2. Client components

choose and enable FTP, FTP_SERVER, NFS_CLIENT, REXEC & RSH, RLOGIN, SSH client, TELNET and TELNETSYM

choose option 3. Server components

choose and enable PORTMAPPER

E to exit

choose option 6. Startup HP TCP/IP Services for OpenVMS

press [Return] when requested

E to exit TCPIP$CONFIG

Copy over necessary files

Copy command and site-specific files from SYS$SYSDEVICE:[UTILITY.SETUP] on the development machine (currently this is LPAS3) into the SYSTEM home directory. The command files are used to complete the customisation, and to create the necessary user accounts and top level directories. Either DECnet COPY or ftp can be used to copy the files.

Copy the files (using ftp as an example):

• SET DEF SYS$MANAGER
• ftp to LPAS3 as SYSTEM
• set def sys$sysdevice:[utility.setup]
• get *.*;
• quit

Copy machine-specific files from whichever machine will be replaced by this one (using DECnet COPY from LPAS3 as an example):

• SET DEF SYS$MANAGER
• COPY LPAS3"SYSTEM password"::SYS$COMMON:[SYSMGR]WELCOME.TXT SYS$COMMON:[SYSMGR]
• COPY LPAS3"SYSTEM password"::SYS$LIBRARY:SYSDEVCTL.TLB SYS$LIBRARY
• COPY LPAS3"SYSTEM password"::SYS$MANAGER:LOG_TIDY.COM []
• COPY LPAS3"SYSTEM password"::SYS$MANAGER:LOGIN.COM []
• COPY LPAS3"SYSTEM password"::SYS$MANAGER:TCS_STARTUP.COM []
• COPY LPAS3"SYSTEM password"::SYS$MANAGER:LPAS3_STARTUP.COM []

The name of the last file copied (LPAS3_STARTUP.COM) will depend on the machine it is copied from, e.g. on LPAS2 it is called LPAS2_STARTUP.COM.
Once this file has been copied, it should be renamed to suit the machine it is copied to, for example:

• RENAME LPAS3_STARTUP.COM LPAS12_STARTUP.COM

Define forms and start queues

• Edit START_QS.COM and replace each instance of LPASn with the name of the new machine.
• @DEFINE_HPFORMS
• @START_QS

Set up TCP/IP host database and access for local networks

• Check that the file setting up the local host database is up-to-date. To display the file, type:
  TYPE TCPIP_SETHOST.COM
• Edit TCPIP_SETHOST.COM if necessary. Make sure that the hostname of the new machine is not included.
• @TCPIP_SETHOST
• Check that the file setting up the local network access is up-to-date. Display the file:
  TYPE TCPIP_SET_NET_ACCESS.COM
  and edit TCPIP_SET_NET_ACCESS.COM if necessary.
• @TCPIP_SET_NET_ACCESS

Modify SYSTARTUP_VMS.COM

• Uncomment the line $ DEFINE /SYSTEM SYS$WELCOME "@SYS$MANAGER:WELCOME.TXT"
• Uncomment the line $ START/NETWORK DECNET


• At the end of the file, before $ EXIT, add the line: $ @SYS$MANAGER:LPASn_STARTUP,
  replacing LPASn with the name of the new machine

Reboot and check

• The SYSTEM account should have the symbols REBOOT, SHUTDOWN and SHUTDOWN1 defined in its LOGIN.COM file. This can be checked by typing:
  SHOW SYMBOL REBOOT
• If it is defined, reboot the system by typing REBOOT.
• If it is not defined, reboot the system by typing @SYS$SYSTEM:SHUTDOWN and answering the prompts.
• As the system boots, check the messages on the console screen for any errors.
• Once booted, login as SYSTEM.
• Check that both DECnet and TCP/IP have started.

On development machine ONLY: install layered products - Fortran, C and DECset

If there is a later version of TCP/IP than the currently installed version, install the later version. However, it is wise to wait a couple of months before installing a new version of TCP/IP, and to check for patches to the new version.

Check the installation guides to see if there are sufficient global pages and global sections available. Also check the installation guide for the correct installation method, some products use the command PRODUCT INSTALL, and some use the VMSINSTAL command.
The installation guides are on CD, for HP Campus they are in [product.DOCUMENTATION]*_IGUIDE.TXT; they are also available on HP's website.

Mount the correct CD for each layered product

• MOUNT/OVERRIDE=ID DKA400:

Create log of installation if DECnet is running

• SET HOST/LOG=product.LOG 0
• login as SYSTEM

Install layered product (examples given for current methods for Fortran, C and DECset)

Fortran 7.6

• PRODUCT INSTALL FORRTL /SOURCE=DKA400:[ALPHA_FORT076.KIT]
• PRODUCT INSTALL FORTRAN /SOURCE=DKA400:[ALPHA_FORT076.KIT]

C 6.5

• @SYS$UPDATE:VMSINSTAL CC065 DKA400:[CC065.KIT] OPTIONS N

DECset 12.5

• @SYS$UPDATE:VMSINSTAL DECSET125 DKA400:[DECSET125.KIT]

When installation has finished:

• LOGOUT
• DISMOUNT DKA400

Repeat for each layered product.

Backup disk

Backup to the second disk.

Install patches if necessary

Instructions for downloading and applying patches. These instructions are for VMS 7.3-2, but can easily be adapted for other VMS versions.

Copy TCS related files

Instructions for copying TCS related files.

Run AUTOGEN

See Upgrade and Installation Manual.

Backup disk

Backup the disk to tape and store the tape in the sea-level firesafe.

Enable shadowing

Instructions for creating a shadow set.