Digital PDFs

AA-NE45A-TE

May 1989

65 pages

Original

2.0MB

Document:	DECserver 300 Software Installation VMS Jun89
Order Number:	AA-NE45A-TE
Revision:	0
Pages:	65
Original Filename:	AA-NE45A-TE_DECserver_300_Software_Installation_VMS_Jun89.pdf

OCR Text

DEC server 300

Software Installation (VMS)

Order No . AA-NE45A-TE

DECserver 300

Software Installation (VMS)

June 1989
This manual explains how to install the DECserver 300
distribution software onto VMS systems, how to configure these
systems as a down-line load hosts, and how to down-line load
the DECserver 300 image. This manual is intended for the VMS
system manager or the network manager.
Supersession/Update Information:

This is a new manual.

Operating System and Version:

VMS VS.O

Software Version:

DECserver 300 V1.0

This manual applies to Version 1.0 of the DECserver 300
software and Version S.O of the VMS operating system, and all
subsequent maintenance releases up to the next major product
release.

Order Number: AA-NE45A-TE

AA-NE45A-TE
June 1989

The information in this document is subjectto change without notice and should not be construed as a
commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may only be used or copied
in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied by
Digital or its affiliated companies.

The following are trademarks of Digital Equipment Corporation:
DEBNA
DEBNET
DEC

DESVA

DECconnect
DECnet

LAN Bridge
LA120

ThinWire

DECserver

LN01

ULTRIX-32

DECUS

LN03
LQP02
MASSBUS
Micro/RSX
MicroVAX

UNIBUS

PDP

VMS

DELNI
DELUA
DELQA
DEMPR
DEQNA

oESOA

Q-Bus

DEUNA

mOmDOmO

Rainbow
RSX
RSX-11 M-PLUS

VAX
VAXcluster
VAXmate
VAXstation

Professional

This manual was produced by Networks and Communications Publications.

Contents

Preface
1

Installation Overview
1.1
1.2
1.3
1.4
1.5

Installation Flow Chart ..................... . . . . . . . 1-1
Installing the Distribution Software ................... 1-4
Configuring the Load Host's Node Database ........... 1-4
Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Prerequisite and Optional Products . . . . . . . . . . . . . . . . . . . 1-6

Installing the Distribution Software
2.1
2.2
2.3
2.3.1
2.3.2
2.4

Preparing for Installation ........................... 2-1
Installing on the PriInary Load Host .................. 2-2
Installing onto Alternate Load Hosts .................. 2-9
Installing onto Single Systems .................... 2-10
Installing onto Other Operating Systems ............ 2-10
After Exiting VMSINSTAL ........................ 2-10

iii

Configuring the Load Host's Node Database
3.1
3.2
3.2.1
3.2.2
3.2.3
3.3
3.4

Preparing for Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Configuring on the Load Host ....................... 3-3
List Known DECservers (Option 1) ................. 3-6
Add a DECserver (Option 2) ...................... 3-6
Options 3, 4, and 5 ............................. 3-8
Verifying a Merge on VAXcluster Nodes ............... 3-8
Exiting DSVCONFIG .............................. 3-9

Verifying the Installation
4.1
4.2

Verifying the Load Host Installation .................. 4-1
Verifying the Server System Installation ............... 4-2

DECserver 300 Distribution Files

Using the Remote Console Facility

Examples: Installation, Configuration, Verification
C.1
C.2
C.2.1
C.2.2
C.2.3
C.2.4
C.2.5
C.2.6
C.3
C.3.1

Example of an Installation. . . . . . . . . . . . . . . . . . . . . . . .. C-1
Example of a Configuration. . . . . . . . . . . . . . . . . . . . . . .. C-4
Starting DSVCONFIG.COM ..................... C-5
Listing Known DECservers (Option 1) .............. C-5
Adding a DECserver (Option 2) .................. C-6
Swapping an Old Terminal Server for a New Terminal
Server (Option 3) .............................. C-6
Deleting a DECserver from the Database (Option 4) . .. C-7
Restoring Existing DECservers to the Database (Option
5) .......................................... C-7
Example of Verification: Verifying a Load Host Installation C-7
Using RCF and Warning Server Users ............. C-7

C.3.2
C.3.3
C.3.4
C.3.5
C.3.6
C.4

Enabling DECnet Event Logging and Checking Server
Names ...................................... C-8
Down-Line Loading with the LOAD Comlnand ...... C-9
DECnet Event-Logging Display after Issuing LOAD ... C-9
Checking the Service Circuit ..................... C-I0
Conclusion of a Load Host Installation Verification .... C-l1
Example of Verification: Verifying the Server System
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-l1

Index

Figures
1-1
1-2

Terminal Server Software Installation Flow Chart .......... 1-2
Load Host Node Database Configuration ................ 1-5

Preface

This installation manual explains how to:
•

Install the DECserver 300 distribution software onto a VMS system
running DECnet Phase IV so that this systetn can perfonn as a load
host. The load host can be a single system or a member node of a
VAXcluster.

•

Configure the load host's node database.

•

Verify the installation by first down-line loading the server image to
the DECserver 300 terminal server and then testing a few server COlnmands.

Intended Audience
This manual is for system managers or network managers who are responsible for making server products available on their Ethernet LANs. A system
manager is responsible for the VMS system that is about to be established as
a load host. A network manager is the person responsible for the local area
network (LAN).
To use this manual effectively, you should be familiar with both DECnet
Phase IV network management concepts and the VMS operating systeol.

vii

Structure of This Manual
This manual has four chapters and three appendixes:
Chapter 1

Provides an overview of the installation and preparation procedures.

Chapter 2

Explains how to install the distribution software.

Chapter 3

Explains how to configure the load host's node database.

Chapter 4

Explains how to verify the installation by first down-line loading the server image and then testing a few server commands.

Appendix A

Usts the names of the files in the DECserver 300 distribution
kit.

Appendix B

Discusses briefly the remote console facility (RCF).

Appendix C

Contains examples of the installation and configuration procedures, and examples of verification by down-line loading.

Conventions Used in This Manual
Familiarizing yourself with the conventions discussed in this section helps
you use this manual effectively.
The following conventions apply to numbers:
•

All numbers are decimal unless otherwise noted.

•

All Ethernet addresses are given in hexadecimal.

Graphic Conventions Used in This Manual

Convention

Meaning
This special type indicates system output or user input.
System output is in black type; user input is in red type.

Special type

UPPERCASE

viii

Uppercase letters in command lines indicate keywords
that must be entered. You can enter keywords in either
uppercase or lowercase. You can abbreviate command
keywords to the smallest number of characters that distinguishes the keyword to the server.

Convention

Meaning

lowercase italics

Italics in command syntax or examples indicate variables
for which either the user or the system supplies a value.

[ ]

Square brackets in command syntax statements indicate
that the enclosed value(s) are optional. You can enter
none or one. Default values apply for unspecified options. (Do not type the brackets.)

BOLD

In summaries of characteristics, bold type indicates default values.

bold

In text, words appearing in bold type introduce new
terms or concepts and can also be found in the glossary.
Press the specified key. For example, IRETI means that
you should press the RETURN key.

!CTRLlx!

Hold down the CONTROL key and then press the key
specified by x. The server displays this key combination
as AX.

1
Installation Overview

The software that you are about to install consists of the files in the DEC server
300 distribution kit. First you install the distribution software onto your VMS
system, then you configure your systenl node database for all new servers.
Next, you verify the installation by down-line loading one test server. Downline loading means sending the server image from the established load host
to the server. Finally, you issue a few server cOlnmands to test the server
system.
NOTE

If you have the Terminal Server Manager

(TSM) software, an optional network management product available for VMS load hosts,
read the documentation for TSM before you
install the DECserver 300 software. TSM affects the way you install and manage servers.

1.1 Installation Flow Chart
This chapter provides a flow chart of the installation process (see Figure 1-1).
Also, there is an overview of installing the distribution software, and an
overview of configuring the load host's node database.

1-1

Figure 1-1:

Terminal Server Software Installation Flow Chart

DETERMINE WHICH SYSTEMS ARE THE
LOAD HOSTS

Refer to Section 2. 1

CHECK FOR FREE DISK SPACE

PLACE DISTRIBUTION MEDIUM ON
DEVICE DRIVE

INVOKE VMSINST AL AND ANSWER THE
VMSINST AL QUESTIONS

PRINT IDISPLA Y
(recommended)

REST ART VMSINST AL (If you stopped to
read the release notes)

Refer to Section 2.2

INITIATE THE INSTALLATION VERIFICATION
PROCEDURE (lVP) (recommended)

READ THE MESSAGES AND EXIT
VMSINSTAL

EDIT SYSTEM START-UP FILE IF
NECESSARY

LKG-2868-89J

Figure 1-1

1-2

DECserver 300 Software Installation (VMS)

Figure 1-1 (Cont.):

Terminal Server Software Installation Flow Chart

INSTALL DISTRIBUTION SOFTWARE ON
THE ALTERNATE HOST

Refer to Section 2.3

CHECK THAT DECnet PHASE IV IS
INSTALLED AND RUNNING
CHECK THAT THE DISTRIBUTION SOFTWARE
IS INSTALLED IN THE CORRECT DIRECTORY

Refer to Section 3. 1

LOCATE SERVER IDENTIFICATION CARD

CHECK THAT EACH NEW SERVER DECnet
NODE NAME AND NODE ADDRESS ARE UNIQUE

INVOKE DSVCONFIG

Refer to Section 3.2

CHOOSE YOUR CONFIGURATION OPTION(S)

IF APPROPRIATE. VERIFY MERGE ON
V AXcluster NODES

Refer to Section 3.3

EXIT DSVCONFIG

Refer to Section 3.4

VERIFY LOAD HOST INST ALLA TION

Refer to Section 4. 1

VERIFY SERVER SYSTEM INST ALLA TION

Refer to Section 4.2

LKG-2869-891

Installation OveNiew

1-3

1.2 Installing the Distribution Software
You install the server distribution software onto a VMS system with an automated procedure called VMSINSTAL. VMSINSTAL is an interactive procedure that calls and controls the DEC server 300 installation procedure.
The DECserver 300 software distribution kit includes a procedure file that
VMSINSTAL uses to do the installation. The first page of Figure 1-1 shows
the steps of this procedure.
When you run VMSINSTAL, the following tasks are performed:
•

Creates a directory called SYS$SYSROOT:[DECSERVER] on the load
host, if necessary

•

Copies the files from the distribution media into this directory

•

Optionally prints a copy of the DECsel'vel' 300 Release Notes

VMSINSTAL also provides an installation verification procedure (IVP) that
can optionally be used to verify that the DEC SERVER directory exists, that
all the files from the distribution kit are in the directory, and that the release
notes are in the SYS$HELP directory.
Chapter 2 contains the procedure to install the distribution software.

1.3 Configuring the Load Host's Node Database
Once you copy the distribution software to your VMS system, you should
configure the system node database to support new servers. You configure
this database with an automated procedure called DSVCONFIG. The second
page of Figure 1-1 shows the steps of this procedure. DSVCONFIG also
automatically enables the service circuit. The DSVCONFIG configuration
procedure file is part of the DECserver 300 software distribution kit.
DSVCONFIG uses DECnet commands to carry out the configuration; therefore, DECnet must be running on your VMS system.
Configuration of the load host's node database means defining an entry for
each server in three places:
1.

Data file called DSVCONFIG.DAT
The DSVCONFIG.DAT file is the server configuration database.
DSVCONFIG.DAT is automatically created by DSVCONFIG and is part
of a load host's node database (see Figure 1-2).

1-4

DECserver 300 Software Installation (VMS)

DECnet operational (also called "volatile") database

DECnet permanent database.

Figure 1-2:

Load Host Node Database Configuration

LOAD HOST NODE OAT ABASE

I
DECnet
OPERA TIONAL
DATABASE

DECnet
PERMANENT
DATABASE

I
SERVER
CONFIGURA TION
DATABASE
(DSVCONFIG.DAT)

LKG-2870-891

When you complete the configuration procedure, your VMS system is established as a load host for each server that has an entry in the load host's node
database.
When installing new versions of DECserver products, always check the
product release notes for information on the latest DSVCONFIG.COM.
Chapter 3 contains the procedure to configure the load host's node database.
For more information on DSVCONFIG, see the DECserver 300 Management
manual.

Installation Overview

1-5

1.4 Verifying the Installation
After you configure the load hosts' node databases, you perform two verifications. First, you verify the load host installation by down-line loading the
server image. Then, after loading the server, you verify the server system installation. You verify the server system by testing a few server commands at
an interactive terminal, which must be connected to the server.
Chapter 4 contains the procedures to verify the load host and server system
installation.

1.5 Prerequisite and Optional Products
The DECserver 300 Software Product Description contains a list of prerequisite
and optional products for the DECserver 300 terminal server.

1-6

DECserver 300 Software Installation (VMS)

Installing the Distribution Software

This chapter provides a step-by-step procedure for installing the DECserver
300 distribution software onto your VMS load host. Install the software using VMSINST AL. COM, which is an automated procedure that is part of the
VMS operating system. Figure 1-1 provides an overview of the installation
process.
VMSINSTAL has the following conventions:
•

At the end of each question, either a colon (:) or a question mark (7)
appears. To answer a question, type your response imll1ediately after
the colon or question mark; then press the RETURN key.

•

After each question, the default response, if there is one, displays in
brackets ([ D. To respond to a question with the default answer, press
only the RETURN key.

•

To get help after any question, type a question mark (?). After the help
display, the question is repeated.

See the VMS doculnentation for a complete description of VMSINSTAL.

2.1 Preparing for Installation
Digital Equipment Corporation advises that you establish more than one
systeln as a load host for each server. Alternate hosts free the server from
dependence on one particular load host. For each server, Digital suggests
a minimum of two load hosts. Digital also recommends one load host for
every ten servers on a network.

2-1

This procedure requires the VMS operating system, which includes the VMS
Required Saveset and Network Support tailoring classes, to be installed on
the load host.
Perform the following procedure before you install the distribution software
on a load host.
Step 1: Determine which systems are the load hosts.

You must install the distribution software onto all of the systems designated
as load hosts. Ask your network manager or the person responsible for assigning load hosts to tell you which are the designated systems.
When selecting alternate load hosts, you can choose any Digital system for
which a DECserver 300 distribution kit is available. DECserver 300 software
distribution kits are available for the VMS and ULTRIX-32 systems.
Note that you do not need a separate software license for each load host, but
you do need a separate license for each server.
Step 2: Back Up the system disk (recommended).

At this point, you might wish to back up your system disk.
Step 3: Check for free disk space.

The DECserver 300 software requires 800 free blocks of disk space on each
load host for copying the distribution files; however, the software uses a
peak of 1218 blocks during installation. An additional 2048 free blocks of
disk space is required for each up-line dump.

2.2 Installing on the Primary Load Host
Perform the following procedure to install the distribution software on the
primary or first load host. The software installation procedure takes approximately 10 to 15 minutes.
If you wish to abort the installation procedure at any time, press 1CTRLIY I.
The installation procedure then deletes all files it has created up to that point

and returns you to the DCL level. You must invoke VMSINSTAL again to
retry the installation procedure.
Step 1: Place the distribution medium on the appropriate device drive.

2-2

DECserver 300 Software Installation (VMS)

Step 2: Invoke VMSINSTAL.

Invoking VMSINSTAL. COM requires the appropriate privileges. Refer to the
VMS System Manager's Manual for a list of the necessary privileges.
Log in to the system manager account, and enter the following cOlumands:
$ SET DEFAULT SYS$UPDATE IRETI
$ @VMSINSTAL DS3 device-identifier OPTIONS N IRETI
Here, DS3 is the VMS three-letter facility code tor the DECserver 300 product, and device-identifier is the device on which the distribution mediunl is
Inounted.
OPTIONS N is an optional parameter that indicates you want to be prompted
to display or print the DECserver 300 Release Notes. If you do not include the
OPTIONS N parameter, VMSINSTAL does not prompt you to display or
print the release notes. You are strongly recommended to read the release
notes before proceeding with this installation. If you do not want to print the
release notes or if you are interested in VMSINSTAL's other options, see the
VMS System Manager's Manual, which is part of the VMS docUlnentation set.
If you are installing onto alternate load hosts with copied savesets, the
VMSINSTAL command line format differs slightly. See the VMS documentation on VMSII'JSTAL.

Step 3: Answer the VMSINSTAL questions.

VMSINSTAL displays the procedure title and the date and time. It continues
with the following (the warning luessage appears only if DECnet is running):
%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]?

1. Type YES and press the RETURN key to proceed with the installation.

VMSINST AL asks:
* Are you satisfied with the backup of your system disk [YES]?

If backup is satisfactory, press the RETURN key to answer YES.
If you answer NO, the installation procedure terminates. Take appro-

priate action and start the procedure again.

Installing the Distribution Software

2-3

If you are installing from the distribution media rather than from copied

savesets, VMSINSTAL prompts you to mount the first volume, which
you did at step 1:
Please mount the first volume of the set on device-identifier.
* Are you ready?

3. Type YES and press the RETURN key. A confirmation message says
that the medium is mounted.
The procedure continues:
The following products will be processed:
DS3 Vn.n
Beginning installation of DS3 Vn.n at hh:mm
%VMSINSTAL-I-RESTORE, Restoring product saveset A ...

NOTE

DEC server 300 software version numbers
are not specified in this manual. For example, the release notes file is shown as
DS3n1Ul.RELEASE_NOTES. Here, 111111 represents the version number; if you are installing Version 1.0, the release notes file is
DS3010.RELEASE_NOTES.
Step 4: Print and/or display the release notes (recommended).

Next, the procedure lists your options for printing and displaying the release
notes.
Release Notes Options:
1.
2.
3.
4.
5.

Display Release Notes
Print Release Notes
Both 1 and 2
Copy release notes to SYS$HELP
Do not display, print, or copy release notes

* Select option [3]:

Select one of these options. Digital recommends that you select option 2.
•

If you select option 1, you see:
VMI$ROOT:[SYSUPD.DS3nnn]DS3nnn.RELEASE_NOTESi1

The release notes immediately start scrolling at your terminal. The release notes might contain up to 30 screens.

2-4

DECserver 300 Software Installation (VMS)

•

If you select option 2, VMSINST AL asks you which queue you want to

send the file to for printing:
* Queue name [SYS$PRINT):

Press the RETURN key to print the release notes on the default printer,
or specify another print queue. A message indicates that the systeln
has queued the file.
•

If you select option 3, VMSINSTAL first asks you which queue you
want to send the file to for printing:
* Queue name [SYS$PRINT):

Press the RETURN key to print the release notes on the default printer,
or specify another print queue. A message indicates that the system
has queued the file for printing. Next, VMSINSTAL displays the following, then the release notes immediately start scrolling at your ternlinal.
VMI$ROOT:[SYSUPD.DS3nnn)DS3nnn.RELEASE_NOTESil

After the system queue message and the release notes are displayed (if you
selected one of the display options), the procedure continues by asking:
* Do you want to continue the installation [N)?

If you haven't read the release notes, press the RETURN key to stop the pro-

cedure and review the release notes. Check for any changes that can affect
this installation. (VMSINSTAL places the release notes file, DS3111111.RELEASE_
NOTES, in the SYS$HELP directory.)
Step 5: Restart VMSINSTAL if you stopped to read the release notes.
If you discontinued the installation procedure at the end of step 4, then enter

this form of the VMSINST AL command to restart the procedure:
$ @VMSINSTAL DS3 device-identifier

IRETI

After typing this command, you must answer the VMSINST AL questions (re- .
fer to step 3).

Installing the Distribution Software

2-5

Step 6: Initiate the Installation Verification Procedure (IVP) (recommended).

After the release notes option menu, the procedure continues:
The following products will be processed:
DS3 Vn.n
Beginning installation of DS3 Vn.n at hh:mm
%VMSINSTAL-I-RESTORE, Restoring product saveset A .•.
%VMSINSTAL-I-RELMOVED, The product's release notes have been successfully
moved to SYS$HELP.
* Do you want to run the IVP after the installation [YES]?

The installation verification procedure (IVP) verifies that the DEC SERVER directory exists, that all the files from the distribution kit are in the directory,
and that the release notes are in the SYS$HELP directory. Digital recomlnends that you press the RETURN key to initiate the IVP.
Step 7: Read the messages and exit VMSINSTAL.

If you are on a VAXc1uster node, the following message displays:
If you intend to execute this layered product on other nodes in your
VAXcluster, and you have the appropriate software license, you must
prepare the system-specific roots on the other nodes by issuing the
following command on each node (using a suitably privileged account):
$ CREATE/DIRECTORY SYS$SPECIFIC:[DECSERVER]/PROTECTION=(S:RWED,O:RWED)

VMSINSTAL continues, as follows, for both single and VAXc1uster nodes:
%VMSINSTAL-I-RESTORE, Restoring product saveset B .•.
Your installation is now complete. After exiting from VMSINSTAL:
1.

Edit your system start-up file so that it defines the logical
MOM$LOAD as a search string with a value equal to the current search
string plus the added element SYS$SYSROOT:[DECSERVERJ. For example:
DEFINE/SYSTEM/EXEC/NAME_ATTRIBUTE=NO_ALIAS/NOLOG MOM$LOAD 'current-search-string',SYS$SYSROOT:[DECSERVERJ
If the current search string associated with MOM$LOAD in your
start-up file is SYS$SYSROOT:[DECSERVER] or if you have
already made this change for a previous installation, there
is no need to edit this file.
This command ensures that the location of the server image
is defined each time the system is rebooted, necessary for
successful down-line loading.

2-6

DECserver 300 Software Installation (VMS)

Configure the server into your host's database.
Execute a command procedure called DSVCONFIG.COM. This
command procedure is in the SYS$SYSROOT:[DECSERVERj directory.
If you have already executed this procedure from previous
installations, you need to configure only any additional units.
All previously defined units will still be configured.

The Installation Verification Procedure (IVP) for the DECserver 300
can be found in SYS$TEST and may be run at any time by executing
the command procedure DS3$IVP.COM.

You have finished the first part of the installation. The procedure continues
as follows:
NOTE

If you are installing files onto a VAXcluster
node, the messages indicate that the files are
copied to the SYS$COMMON:[DECSERVER]
directory, instead of SYS$SYSROOT:[DECSERVER).
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories ...
Beginning installation verification procedure for DECserver 300 Vn.n.
Successfully located SYS$SYSROOT:[DECSERVERj directory
Successfully located SYS$SYSROOT:[SYSHLPjDS3010.RELEASE_NOTES
Successfully located SYS$SYSROOT:[DECSERVERjSH1601ENG.SYS
Successfully located SYS$SYSROOT:[DECSERVERjDSVCONFIG.COM
Successfully located SYS$SYSROOT:[DECSERVERjDSVCONFIG.DAT
Successfully located SYS$SYSROOT:[DECSERVERjDS3_010_DEFAULTS.COM
Successfully located SYS$SYSROOT:[DECSERVERjTSM$DS3_nnn_ADD_LOCAL_SERVICE.COM
Successfully located SYS$SYSROOT:[DECSERVERjTSM$DS3_nnn_DEDIC_SERV_PRINTER.COM
Successfully located SYS$SYSROOT:[DECSERVERjTSM$DS3_nnn_DEDIC_SERV_TERM.COM
Successfully located SYS$SYSROOT:[DECSERVERjTSM$DS3_nnn_DSR_DTR_TERM.COM
Successfully located SYS$SYSROOT:[DECSERVERjTSM$DS3_nnn_GET_CHAR.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_nnn_HOST_INIT_PRINTER.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_nnn_PC_TERM_OR_SERV.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_nnn_PORT_DEFAULT.COM
Installation verification procedure for DECserver 300 Vn.n successful
Installation of DS3 Vn.n completed at hh:mm

NOTE

The Terminal Server Manager (TSM) files are
used only if you have the Terminal Server
Manager software.
The procedure concludes:
VMSINSTAL procedure done at hh:mm

Installing the Distribution Software

2-7

Proceed to step 8 if you need to edit your system start-up file. If you do not
need to edit your system start-up file, you can either proceed to Section 2.3
to install the distribution software onto an alternate load host, or to Section 2.4
to finish the VMSINSTAL installation procedure.
Step 8: Edit your system start-up file, if necessary.

MOM$LOAD is a logical name that your load host uses to find the image file of any product that must be down-line loaded. For each product,
MOM$LOAD has an associated equivalence string that specifies the location
of the product' s image file. Thus, the following command equates the logical
natne MOM$LOAD to the location of your DECserver 300 image file:
~/DEFINE/SYSTEM/EXEC/NAME_ATTRIBUTE=NO_ALIAS/NOLOG

MOM$LOAD -

SY$$SYSROOT:[DECSERVER]

If your system is a load host for several products, then the location of each
image file must be defined by a list of equivalent strings. For example, the
following command defines the location of other Ethernet product image
files as well ~s the DECserver 300 image file:
DEFINE/SYSTEM/EXEC/NAME_ATTRIBUTE=NO_ALIAS/NOLOG MOM$LOAD SYS$SYSROOT: [MOM$SYSTEM],SYS$SYSROOT: [DECSERVER]

Two or more equivalence strings make up a search list. When your VMS systeln is requested to down-line load a product, it looks through the search list
until it finds the location of the product's image file.
Your host cannot down-line load the DECserver 300 itnage file unless the
search list defined for MOM$LOAD has the correct location of the image
file. To see what the current search string is for MOM$LOAD, use the DCL
SHOW LOGICAL command: u{Y\on,:tl.or.:-IO'1 :. "rt\on-t.ss'{s-n:M: {u,lni5YST6t1_IV
I,

$ SHOW LOGICAL MOM$LOAD IRETI~\(y)oYY\S5'15Tf.M·' ~ "5y51>S'{5'eoo-r:LNll)'fV\A'':;:;yS~em:111

(\....NM4
\:~fi·- T~
If SYS$SYSROOT:[DECSERVER] is defined for MOM$LOAD, you do not
have to define MOM$LOAD. Define MOM$LOAD only if:
•

No equivalence string exists for MOM$LOAD (the SHOW LOGICAL
command results with the message "N 0 translation for logical name
MOM$LOAD")
or

•

2-8

The equivalence strings defined for MOM$LOAD do not include
SYS$SYSROOT:[DECSERVER).

DECserver 300 Software Installation (VMS)

If MOM$LOAD is already defined for other products but not for the DECserver

300 product, you must define MOM$LOAD by specifying
SYS$SYSROOT:[DECSERVER] along with the current search string(s), as
shown in the VMSINSTAL example. If you specify only
SYS$SYSROOT:[DECSERVER] for MOM$LOAD excluding the current
search string(s), then SYS$SYSROOT:[DECSERVER] will replace the current
search string(s). Your VMS system will not be able to load the image files
located by the current search string(s).
Proceed to Section 2.3 to install the distribution software onto an alternate
load host, or proceed to Section 2.4 to finish the VMSINSTAL installation
procedure.

2.3 Installing onto Alternate Load Hosts
Digital recommends that you establish alternate load hosts for each server.
Alternates free the server frOIn dependence on one load host because an alternate load host can perform a down-line load if the original load host is unavailable. In addition, alternate load hosts can receive up-line dunlps fronl
servers.
Regarding the assignment of load hosts, Digital suggests both the following:
•

At least one other load host as a backup to the original for each server

•

At least one load host for every ten servers

As with the original load host, an alternate VMS load host must:
•

Be running DECnet Phase IV

•

Have an Ethernet controller on the same Ethernet as the server

•

Have the distribution software installed

•

Have DECserver 300 entries in its server configuration database
DSVCONFIG.DAT, the DECnet operational database, and the DECnet
permanent database

Installing the Distribution Software

2-9

2.3.1 Installing onto Single Systems

To install the server distribution software onto an alternate VMS load host
that is not a member of a VAXcluster, use one of these two methods:
•

Place your distribution media on the appropriate device of the new load
host, and repeat the installation procedure detailed in Section 2.2.

•

Follow this procedure:
1.

Type the following command on the original load host:
$ @VMSINSTAL DS3 device-identifier OPTIONS G SYS$UPDATE:

IRETI

In this case, option G gets the savesets and stores them in the
SYS$UPDATE directory.
2.

Copy the savesets from the original load host to the alternate load
host's SYS$UPDATE directory. The savesets are DS3111111.A and
DS3111111.B.
Here, 111111 equals the version number of the DECserver 300 software (e.g., 111111 equals 010 for V1.0).

Run VMSINSTAL on the alternate load host.
$ @VMSINSTAL DS3 SYS$UPDATE:

IRETI

2.3.2 Installing onto Other Operating Systems

To install the DEC server 300 distribution software onto an operating systen1 other than VMS, follow the instructions in the DECserver 300 Software
Il1stallatiol1 manual for that system. The appropriate installation n1anual is included with the documentation kit that comes with the software distribution
kit for that operating system.

2.4 After Exiting VMSINSTAL
After you exit VMSINST AL, follow these steps:

2-10

Check the DECserver 300 Release Notes to see if you have to install any
additional software from the distribution media. If so, install those distribution files.

Give the DECserver 300 Release Notes to the server manager.

Go to Chapter 3 to configure the load host's node database.

DECserver 300 Software Installation (VMS)

Configuring the Load Host's Node
Database

This chapter provides a step-by-step procedure for configuring a VMS load
host's node database for new servers with an automated procedure called
DSVCONFIG. Configuring this database is part of the software installation.
After this procedure, your VMS system is established as a valid load host for
the new servers. Figure 1-1 provides an overview of the installation process.
If you ran the installation procedure described in Chapter 2, DSVCONFIG.COM

is now in the SYS$SYSROOT:[DECSERVER] directory for single systems and
in SYS$COMMON:[DECSERVER] for VAXc1uster members. The load host
creates and maintains all server-related files in this directory.
NOTE

DSVCONFIG.COM accommodates such
products as the DECserver 100, DECserver
200, DECserver 300, and DECserver 500.
However, some previous releases of DSVCONFIG.COM
do not accommodate all the DECserver products. Therefore, use the command file on this
kit for all configurations.
DSVCONFIG has the following conventions and requirements:
•

To select an option, type a J1lenu number and press the RETURN key.

•

To answer a question, type your response itnmediately after the colon
or question mark, and press the RETURN key.

3-1

•

After each question, the default response, if there is one, displays in
brackets ([ D. To respond to a question with the default answer, press
only the RETURN key.

•

To get help after any question, type a question mark (?). After the help
display, the question is repeated.

•

To exit an option without making any changes, type I CTRUzl. You are
returned to the DSVCONFIG Menu.

•

To exit DSVCONFIG at the menu level, type I CTRuzl. You are returned
to the DCL prompt.

•

When you finish an option, DSVCONFIG automatically returns you to
the DSVCONFIG Menu.

See the DECserver 300 Management manual for a complete description of
DSVCONFIG.

3.1 Preparing for Configuration
Perform the following to prepare for configuring the load host's node database:
Step 1: Check that DECnet Phase IV is installed and running.

For infornlation about DECnet Phase IV, see the VMS DECnet-VAX System
Managei"s Guide.
Step 2: Check that all distribution software was installed in these directories:

•

SYS$SYSROOT:[DECSERVER] for single systems

•

SYS$COMMON: [DEC SERVER] for VAXc1usters

See Appendix A for a list of the distribution files.
Step 3: Locate the server Identification Card.

Ask the hardware installer for the DECserver 300 Identification Card for each
new DECserver 300 terminal server. The network manager and the hardware
installer recorded the server's DECnet node nalne and node address as well
as the Ethernet address on this card. You need to know this information to
answer prompts during DSVCONFIG.

3-2

DECserver 300 Software Installation (VMS)

If your DECnet network is divided into areas, each DECnet node address

takes the form aa.11111111. Here, aa is a decimal area number frOln 2 to 63,
11111111 is the node address, and the period distinguishes area from address.
For example, 17.1003 is a valid node address.
Each DECnet node name must have from 1 to 6 alphanumeric characters
with at least one character being an alphabetic character. For example, DSV5
and LION77 are valid DECnet node names.
Each DECserver 300 terminal server is delivered with a unique Ethernet
hardware address. This address is six pairs of hexadecimal digits with a hyphen (-) separating each pair. For example, 08-00-01-00-AB-CD is an address
with a valid format. The Ethernet address is on the control/indicator panel of
the DECserver 300 terminal server.

3.2 Configuring on the Load Host
Perform the following procedure to configure the load host's node database.
The load host can be a single system or a VAXc1uster node.
CAUTION

Do not execute any DECnet commands that
are a part of DSVCONFIG separate from the
following DSVCONFIG procedure; otherwise,
DECnet databases could be changed without changing DSVCONFIG.DAT, causing a
synchronization problem.
Step 1: Check that each new server DECnet node name and node address are unique.

Check the uniqueness of the server's DECnet node address and node name
by specifying the address or name with the NCP SHOW NODE command:
$ MCR NCP

!RET!

NCP>SHOW NODE node-name CHARACTERISTICS

!RET!

or
NCP>SHOW NODE node-number CHARACTERISTICS

!RET!

If NCP shows a node already defined, see the network manager to resolve
the conflict in names.

Configuring the Load Host's Node Database

3-3

Step 2: Invoke DSVCONFIG.

To invoke DSVCONFIG.COM, you need OPER and SYSPRV privileges.
Log in to the system account or any account with OPER and SYSPRV privileges, and enter the following cOlnmands:
$ SET DEFAULT MOM$LOAD:
$ @DSVCONFIG

IRETI

IRETI
NOTE

The former command assumes you have defined MOM$LOAD to locate the DECserver
300 software image in
SYS$SYSROOT:[DECSERVER] (see Section 2.2).
DSVCONFIG starts with these actions:
•

It determines whether the DECnet key is installed. If DECnet is miss-

ing, DSVCONFIG prints a message and exits. You must have DECnet
to run this procedure because DSVCONFIG executes DECnet commands.
•

It checks the existence and format of a data file called DSVCONFIG.DAT.
It finds one of three possible situations and continues accordingly:

The DSVCONFIG.DAT file does not exist in
SYS$SYSROOT:[DECSERVER]. The procedure creates
DSVCONFIG.DAT and displays a message telling you that the file
was not found and a new one was created.
SYS$SYSROOT:[DECSERVER] already has this file formatted correctly. This is the case if DSVCONFIG was previously used to add
DECserver 300 entries. The procedure continues with its next task.
SYS$SYSROOT:[DECSERVER] or for VAXclusters,
SYS$SPECIFIC:[DECSERVER] already has this file, but not in the
correct fonnat. The procedure reformats the file.
For VAXclusters, SYS$SPECIFIC:[DECSERVER] on each VAXcluster
node might have an older version of the DSVCONFIG.DAT file.
In this case, the DSVCONFIG procedure copies the server entries
from that data file into the DSVCONFIG.DAT file on the
SYS$COMMON:[DECSERVER], a directory shared by the VAXcluster
nodes. The procedure renames the DSVCONFIG.DAT file in
SYS$SPECIFIC so that the DSVCONFIG.DAT file in SYS$COMMON
is used thereafter.

3-4

DECserver 300 Software Installation (VMS)

Refer to Section 3.3 for further information.
•

It informs you that each DECserver terminal server must have a unique

DECnet node name and DECnet node address.
•

It asks you to either continue or to exit:

Press <RET> to start, or <CTRL/z> to exit ...

Press the RETURN key to see the DSVCONFIG options menu.
Step 3: Choose your configuration option(s).

DSVCONFIG displays:
DECserver Configuration Procedure
Version: Vn.n
1 2 3 4 5 CTRL/z -

Menu of Options
List known DECservers
Add a DECserver
Swap an existing DECserver
Delete an existing DECserver
Restore existing DECservers
Exit from this procedure

Your selection?

Type the number of the option you want. Then press the RETURN key.
Section 3.2.1 contains the procedure for option I, list known DECservers.
Section 3.2.2 contains the procedure for option 2, add a DECserver. Appendix
C contains examples of each option.

Configuring the Load Host's Node Database

3-5

3.2.1 List Known DECservers (Option 1)

Select option 1 to list the DECserver terminal servers in the DSVCONFIG.DAT
data file. Type the number one and press the RETURN key. The contents of
the DSVCONFIG.DAT file are listed in seven columns. Option 1 displays a
listing such as this:
DECnet DECnet Server Service
Type
Address Name
Circuit Ethernet Address

------28.900 BUNNY DS200
DS300
28.1001 BACH
28.1002 BEETHO DS300
28.1003 MOZART DS100
28.1005 HAYDN DS300
28.1019 OCELOT DS500
28.1022 JAGUAR DS500
28.1023 BEATLE DS100

Load File

Dump File

------- ----------------- ------------- -------------

BNA-O
UNA-O
UNA-O
UNA-O
UNA-1
UNA-O
UNA-O
UNA-O

08-00-2B-02-FO-99 PR0801ENG.SYS DS2BUNNY.DMP
08-00-2B-02-24-CC SH1601ENG.SYS DS3BACH.DMP
08-00-2B-03-AA-2B SH1601ENG.SYS DS3BEETHO.DMP
08-00-2B-02-24-DD PS0801ENG.SYS PSDMP24DD.SYS
08-00-2B-03-AA-F1 SH1601ENG.SYS DS3HAYDN.DMP
08-00-2B-03-EE-FF DS50CELOT.SYS DS50CELOT.SYS
08-00-2B-03-E1-F1 DS5JAGUAR.SYS DS5JAGUAR.SYS
08-00-2B-02-24-2D PS0801ENG.SYS PSDMP242D.SYS

Total of 8 DECservers defined.
(Press RETURN for menu)

3.2.2 Add a DECserver (Option 2)

Select option 2 to add an entry for a new server in the server configuration
database DSVCONFIG.DAT, the DECnet operational database, and the
DECnet permanent database. You will need the DECserver 300 Identification
Card.
To add a server, follow these steps:
1. Type 2 and press the RETURN key.
DSVCONFIG asks:
DECserver type?

2. Type DS300 and press the RETURN key.
DSVCONFIG asks:
DEC net node name for unit?

Specify the DECnet node name for the new server.
DSVCONFIG asks:
DECnet node address for unit?

3-6

DECserver 300 Software Installation (VMS)

Specify the DECnet node address for the new server. If you specify
a node address that is already defined in DSVCONFIG.DAT, you get
a DSVCONFIG error, nothing is added, and the Add option is terminated.
DSVCONFIG asks:
Ethernet address of unit?

Specify the Ethernet address of the new server.
DSVCONFIG asks:
DECnet Service Circuit-ID [default-id]?

Press the RETURN key if the default ID is the load host's service circuit. If not, specify the service circuit-ID of the load host's Ethernet
controller as follows:
UNA-n

for DEUNA or DELUA

QNA-n

for DELQA, DEQNA, or DESQA

BNA-n

for DEBNA

SVA-n

for DESVA

Here, n is an integer (typically 0 or 1).
DSVCONFIG adds the entry for the new server to the databases and sets
SERVICE ENABLED on the specified service circuit, both of which are
necessary for down-line loading. If the selvice circuit becOInes disabled,
Appendix C contains the commands to enable the service circuit.
At the end of the Add option, you might get network control program (NCP)
messages (information, confirmations, and errors). In the case of error nlessages, the operation might not have been successful. For the explanations of
these messages, see the VMS System, Messages and Recovery Procedures Reference
Manual.

Configuring the Load Host's Node Database

3-7

CAUTION

If you get an error from DECnet while you

are adding a server, the entry is added to the
DSVCONFIG.DAT file even though it is not
entered in the DECnet databases. To correct
this synchronization problem, follow these
steps:
1.

Use option 4 to delete the entry. (See
the example in Appendix C, or refer to
the DECseI'Ver 300 Management manual.)

Fix the condition causing the DECnet
error.

3. Return to option 2 to add the server
again with the correct information.
3.2.3 Options 3, 4, and 5
Options 3, 4, and 5 are not normally used during the installation procedure.
Refer to the DECserver 300 Management manual for a description of these options.

3.3 Verifying a Merge on VAXcluster Nodes
The DSVCONFIG procedure looks at each entry in SYS$SPECIFIC and
determines if that entry is already in SYS$COMMON. If the entry is in
SYS$COMMON, it is not merged. If the entry is not in SYS$COMMON,
it is merged.
In the case of a merge, DSVCONFIG renames the old DSVCONFIG.DAT
file on the SYS$SPECIFIC directory to DSVCONFIG_SPECIFIC.DAT. As
a result, you still have the original entries in case you need to repeat the
merge. The following DSVCONFIG messages appear if a merge occurs:
Merging SYS$SPECIFIC:[DECSERVER]DSVCONFIG into SYS$COMMON:[DECSERVER]DSVCONFIG
8 servers were defined in SYS$SPECIFIC:[DECSERVER]DSVCONFIG.DAT
3 servers were already in SYS$COMMON:[DECSERVER]DSVCONFIG.DAT
5 servers merged into SYS$COMMON:[DECSERVER]DSVCONFIG.DAT
You must assign a unique DECnet node
address for each new DECserver unit.

name

and

DECnet

node

Press <RET> to start, or <CTRL/Z> to exit •..

3-8

DECserver 300 Software Installation (VMS)

If a merge occurs, follow this procedure to ensure that DSVCONFIG updates

the DSVCONFIG.DAT file correctly and places it in the SYS$COMMON directory:
1.

Select the List option to verify that the merge was successful.
The List option should display the correct service circuit-IDs at each
node. Informational messages display the status of the merge as it progresses.

2. Verify that the service circuit-ID is correct.
Since the individual nodes have the correct service circuit ID for each
server entry, the correct IDs are merged into the new file. If the service
circuit IDs are not correct for a particular node, you can correct thenl in
one of two ways:
•

You can run DSVCONFIG SET_CIRCUIT at that node (for VAXclusters,
this method is better). The following shows an example of the
command you would use:
$ @DSVCONFIG SET_CIRCUIT UNA-O

•

You can run DSVCONFIG at the node with the errors and use the
Swap option to change the service circuit-IDs.

3.4 Exiting DSVCONFIG
When you exit DSVCONFIG:
1.

Give the server manager the DEeserver 300 Ide11tification Card for each
server that you defined.

Ask the selver manager to store the card in the notebook with the documentation set for the DECselver 300 software.

Proceed to Chapter 4 to verify the load host and server system installation.

Configuring the Load Host's Node Database

3-9

Verifying the Installation

To complete the software installation, you need to perform two verifications.
First, you verify the load host installation by down-line loading the server
image. Then, after loading the server, you verify the server systenl installation. Here, system installation means the installation of the complete seIVer
system-the hardware with the correct software loaded and running. You
verify the server system by testing a few server commands at an interactive
terminal, which must be connected to the server.

4.1 Verifying the Load Host Installation
To verify the installation of the load host, use it to down-line load the server
image to one DECserver 300 terminal server; then read the DECnet eventlogging messages. The messages confirm that the new load host:
•

Has the appropriate files in the correct directory

•

Has a correct entry in its node database for the server

•

Can successfully down-line load the server image to the server

The DECserver 300 down-line loading procedure does not let you specify
which load host loads a server. The server sends a DECnet message requesting a down-line load to all load hosts. The first load host to "volunteer" is
the host that does the loading. Make sure that the verification server is configured only on load hosts that have the latest server software. If the verification server remains configured on any host with an older version of the
server software, that load host might be the node that down-line loads the
server.

4-1

To find out if a load host has the target server listed, execute the LIST option
of the DSVCONFIG (see Section 3.2.1).
The server image is down-loaded to the server when you initialize the server.
You initialize the server by powering up the hardware unit or with the server
INITIALIZE command. The DEeserver 300 Management manual has details
about initializing the server.

4.2 Verifying the Server System Installation
To verify the total server system installation, test a few server commands at
an interactive terminal connected to a server port. This step confirms that:
•

The correct version of the software is in the server.

•

The server hardware operates with the new software.

•

The new software is running successfully.

Follow this sequence:
1. Press the RETURN key two or more times.
The following message and prompt should appear.

IRETI
IRETI
DECserver 300 Terminal Server Vn.n (BLnn) - LAT V5.1
Pleass type HELP if you need assistance
/Enter username>

2. Read the identification message to ensure that the correct version (Vl1.n)
of the. server image was down-line loaded. If you fail to receive this display, the problem could be:
•

With the load host

•

With the terminal

•

That the incorrect software was down-line loaded

3. Enter your user name (any string of 1 through 16 characters that identifies you) and press the RETURN key. The port should now enter local
mode, where the local prompt (Local» appears:
Enter username> SWINSTALLER

IRETI

Local>

4-2

DECserver 300 Software Installation (VMS)

Use the following server command to see which load host down-line
loaded the server software:
Local> SHOW SERVER STATUS

IRETI

The Load Address field in the display tells you which host loaded the
server. If that load host does not have the current server software, either install the current server software on the host, or delete the verification server from its load host node database. See Chapter 2 for installing the software, or Appendix C for deleting a server from the node
database.
5. Use the TEST PORT command, which verifies whether the terminal is
receiving valid character data. On the command line, specify the number of lines and the number of columns you would like displayed. For
example, this command displays 5 lines of 80 characters each:
Local> TEST PORT COUNT 5 WIDTH 80

IRETI

Note that you can interrupt this test by pressing any key. Appendix C
shows an example of a TEST PORT display.
6. Issue the SHOW PORT command to display the characteristics of your
port and their values:
Local> SHOW PORT

IRETI

A port-characteristics display should appear. Appendix C shows an example of a port-characteristics display.
7. Use the SHOW SERVICES command to show what services are available to you. The following server command produces a list of services
and service announcements:
Local> SHOW SERVICES

IRETI

Every terminal and service node in a LAT network is a member of one
or more groups, which are specified by a list of numbers from 0 to 255.
A terminal user is only aware of the services that are offered by the
nodes in the same group as the user's terminal. The DECserver 300
defaults to Group O. When you use the SHOW SERVICES command,
it must be a service that recognizes Group O. The server manger can
change the group setting of the DECserver 300 terminal server.
Appendix C shows an example of a SHOW SERVICES display.

Verifying the Installation

4-3

Select an available service that you are authorized to use. Use the
CONNECT command to verify that the server can logically connect
your terminal to that service. On the command line, specify the service name to which you want to connect. The following example connects your terminal to a VMS system offering the LAT service named
SYSTEM:
Local>

CONNECT SYSTEM

IRETI

When the server successfully connects your terminal to the service you
specified, you no longer see the local prompt; rather, you are communicating with the service, in this example, your own VMS system.
9. Enter several commands to verify the ability of the server to exchange
data with the service. For example, in this case, you could enter LOGIN,
SHOW TIME, and SHOW USERS.
10. Press the BREAK key or log out from the service to return to local
mode. Note that pressing the BREAK key does not end the service session you started.
11. Log out the terminal from the server:
Local>

LOGOUT

IRETI

If the server system verification encounters any problem, see the server man-

ager.
If you complete the above steps successfully, the test server is operating cor-

rectly, and you can report the successful load host installation and server
system installation to the server manager. If this installation is a software upgrade, either you or the server manager must now reload all existing servers.

4-4

DECserver 300 Software Installation (VMS)

A
DECserver 300 Distribution Files

These are the DECserver 300 distribution files:

File name

Description

KITINSTAL.COM

Command file that VMSINSTAL
uses to do part of the installation
procedure. This file is temporary;
it is not left on the system after the
installation is done.

DS3$IVP .COM

Installation verification procedure.

DSVCONFIG.COM

Configuration procedure.

DSVCONFIG.DAT

Data file used by DSVCONFIG.COM.

DS3_nnn_DEFAULTS.COM

File used by the Terminal Server
Manager (TSM) software.

DS3nnn.RELEASE_NOTES

Release notes.
(nnn=version number)

SH1601ENG. SYS

DECserver 300 software image.

TSM$DS3_nnn_ADD _LOCAL_SERVICE. COM

File used by the TSM software.

TSM$DS3_nnn_DEDIC_SERV_PRINTER.COM

File used by the TSM software.

TSM$DS3_nnn_DEDIC_SERV_TERM.COM

File used by the TSM software.

TSM$DS3_nnn_DSR_DTR_TERM. COM

File used by the TSM software.

A-1

A-2

File name

Description

TSM$DS3_nnn_ GET_CHAR. COM

File used by the TSM software.

TSM$DS3_nnn_HOST_INIT_PRINTER. COM

File used by the TSM software.

TSM$DS3_nnn_PC_TERM_OR_SERV.COM

File used by the TSM software.

TSM$DS3_nnn_PORT _DEFAULT. COM

File used by the TSM software.

DECserver 300 Software Installation (VMS)

Using the Remote Console Facility

The DECserver 300 terminal server supports the VMS RelTIote Console
Facility (RCF). This appendix explains how to use RCF from a VMS host. If
you issue the BROADCAST command yourself to warn users of an upcoming down-line load, you may want to use RCF.
To connect to the server with ReF, use the CONNECT NODE command.
On the command line, specify either the DECnet node name or DECnet
node address of the server. This example shows a connection to the server
named BEETHO:
$ MCR NCP

IRETI

NCP> CONNECT NODE BEETHO
Console connected (press CTRL/D when finished)

or
NCP> CONNECT NODE 28.1002 SERVICE PASSWORD OF23
Console connected (press CTRL/D when finished)

IRETI

Press the RETURN key to start the log-in sequence for the remote console.
Log-in password protection is enabled for the the DECserver 300 remote
console port. Therefore, you must supply the log-in password when the
server prompts you with a pound sign (#), as shown below (an audible beep
signal accompanies the pronlpt). The default password is ACCESS.
#

The prompt indicates that the link to the server has been made. After you
enter the correct password, you can begin using DECserver 300 commands.

8-1

You can also use the CONNECT command with the server's Ethernet address. The following example shows a connection from a VMS system with
the service circuit-ID UNA-O to a server with the Ethernet address 08-00-2B04-AA-2B:
NCP> CONNECT VIA UNA-O PHYSICAL ADD 08-00-2B-04-AA-2B IRETI

You may have to specify the service password with the CONNECT command if a maintenance password is specified on the server. To do so, include the SERVICE PASSWORD keywords on your command line and specify the password.
To exit from RCF, type 1CTRLID I:
Local>

I CTRLlO I

To exit from NCP, type EXIT:
NCP> EXIT IRETI
$

NOTE

If you log out from the server with a LOGOUT
command, the port is logged out but the remote console session remains active. Type
1CTRLlD 1 to exit the remote console session.

The service node prompt reappears, and control passes back to NCP on
your VMS system. See the DEeserver 300 Management manual for detailed
information on RCF.

8-2

DECserver 300 Software Installation (VMS)

Examples: Installation, Configuration,
Verification

This appendix shows examples of the installation and the configuration
procedures. It also shows the verification of a load host installation by
down-line loading and reading DECnet event-logging messages. Finally,
Appendix C shows the verification of a server system installation by testing
server commands.

C.1 Example of an Installation
The following example shows a successful installation procedure onto a VMS
VS.O system. This example also shows the procedure as Digital Equipment
Corporation suggests you run it:
1.

Use the option that prints the release notes.

Print the release notes.

Stop the procedure to read them.

Rerun the procedure.

C-1

$ SET DEFAULT SYS$UPDATE

IRETI

$ @VMSINSTAL DS3 MTA2 OPTIONS N

IRETI

VAX/VMS Software Product Installation Procedure V5.0
It is 17-JUN-1989 at 14:08.
Enter a question mark (?) at any time for help.
%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? Y
* Are you satisfied with the backup of your system disk [YES]?
Please mount the first volume of the set on MTA2:.
* Are you ready? Y
%MOUNT-I-MOUNTED, DS3
mounted on _MTA2:

IRETI

The following products will be processed:
DS3 V1.0
Beginning installation of DS3 V1.0 at 14:08
%VMSINSTAL-I-RESTORE, Restoring product saveset A .•.
Release Notes Options:
1.
2.
3.
4.
5.

Display Release Notes
Print Release Notes
Both 1 and 2
Copy release notes to SYS$HELP
Do not display, print, or copy release notes

* Select option [3]: 2 IRETI
* Queue name [SYS$PRINT]: IRETI
Job DS3010.RELEASE_NOTES (queue SYS$PRINT, entry 314) started on SYS$PRINT
* Do you want to continue the installation [N]?

IRETI

VMSINSTAL procedure done at 14:09
$

C-2

DECserver 300 Software Installation (VMS)

Read the release notes. Run VMSINSTAL again:
$ @VMSINSTAL DS3 MTA2

IRETI

VAX/VMS Software Product Installation Procedure V5.0
It is 17-JUN-1989 at 14:25.
Enter a question mark (?) at any time for help.
%VMSINSTAL-W-DECNET, Your DECnet network ~ and running.
* Do you want to continue anyway [NO]? Y ~
* Are you satisfied with the backup of your system disk [YES]?
Please mount the first volume of the set on MTA2:.
* Are you ready? Y
%MOUNT-I-MOUNTED, DS3
mounted on MTA2:

IRETI

The following products will be processed:
DS3 Vl.0
Beginning installation of DS3 Vl.0 at 14:25
%VMSINSTAL-I-RESTORE, Restoring product saveset A .•.
%VMSINSTAL-I-RELMOVED, The product's release notes have been successfully
moved to SYS$HF.LP.
* Do you want to run the IVP after the installation [YES]?
%VMSINSTAL-I-RESTORE, Restoring product saveset B ..•

IRETI

Your installation is now complete.
1.

After exiting from VMSINSTAL:

Edit your system start-up file so that it defines the logical
MOM$LOAD as a search string with a value equal to the current search
string, plus the added element SYS$SYSROOT:[DECSERVER]. For example:
DEFINE/SYSTEM!EXEC!NAME_ATTRIBUTE=NO_ALIAS!NOLOG MOM$LOAD 'current-search-string',SYS$SYSROOT:[DECSERVER]
If the current search string associated with MOM$LOAD in your
start-up file is SYS$SYSROOT:[DECSERVER] or if you have
already made this change for a previous installation, there
is no need to edit this file.
This command ensures that the location of the server image
is defined each time the system is rebooted, necessary for
successful down-line loading.

Configure the server into your host's database.
Execute a command procedure called DSVCONFIG.COM. This
command procedure is in the SYS$SYSROOT:[DECSERVER] directory.
If you have already executed this procedure from previous
installations, you need to configure only any additional units.
All previously defined units will still be configured.

The Installation Verification Procedure (IVP) for the DECserver 300
can be found in SYS$TEST and may be run at any time by executing
the command procedure DS3$IVP.COM.

Examples: Installation, Configuration, Verification

C-3

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories ...
Beginning installation verification procedure for DECserver 300 VI.O
Successfully located SYS$SYSROOT:[DECSERVER] directory
Successfully located SYS$SYSROOT:[SYSHLP]DS3010.RELEASE_NOTES
Successfully located SYS$SYSROOT:[DECSERVER]SH160IENG.SYS
Successfully located SYS$SYSROOT:[DECSERVER]DSVCONFIG.COM
Successfully located SYS$SYSROOT:[DECSERVER]DSVCONFIG.DAT
Successfully located SYS$SYSROOT:[DECSERVER]DS3_010_DEFAULTS.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_vl0_ADD_LOCAL_SERVICE.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_vIO_DEDIC_SERV_PRINTER.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_vl0_DEDIC_SERV_TERM.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_vl0_DSR_DTR_TERM.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_vl0_GET_CHAR.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_vl0_HOST_INIT_PRINTER.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_vl0_PC_TERM_OR_SERV.COM
Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS3_vl0_PORT_DEFAULT.COM
Installation verification procedure for DECserver 300 vl.O successful
Installation of DS3 Vl.0 completed at 14:28
VMSINSTAL procedure done at 14:28
$

NOTE

The Terminal Server Manager (TSM) files are
used only if you have the Terminal Server
Manager software.

C.2 Example of a Configuration
This section gives examples of the following:

C-4

•

starting DSVCONFIG

•

listing known terminal servers (option 1)

•

adding a terminal server (option 2)

•

swapping an old terminal server for a new terminal server (option 3)

•

deleting a terminal server from the database (option 4)

•

restoring existing terminal servers to the database (option 5)

DECseNer 300 Software Installation (VMS)

C.2.1 Starting DSVCONFIG.COM

The following example shows the beginning of the configuration procedure.
This example assumes that the latest version of DSYCONFIG has already
been run so that the DSYCONFIG.DAT file exists in the correct format. (See
Chapter 3 for the prompts that are displayed if the procedure has to either
create DSYCONFIG.DAT or reformat it.)
$ SET DEFAULT MOM$LOAD
$ @DSVCONFIG

IRETI

You must assign a unique DECnet node name and DEC net node address
for each DECserver you are going to configure.
Press <RET> to start, or <CTRL/Z> to exit •..

IRETI

DECserver Configuration Procedure
version: Vl.8
1 2 3 4 5 CTRL/Z -

Menu of Options
List known DECservers
Add a DECserver
Swap an existing DECserver
Delete an existing DECserver
Restore existing DECservers
Exit from this procedure

Your selection?

C.2.2 Listing Known DECservers (Option 1)

This section and the following ones show how the configuration procedure
continues for each option. Each option ends by automatically returning you
to the menu.
Your selection? 1

IRETI

DECnet DECnet Server Service
Address Name
Type
Circuit Ethernet Address Load File
------- ----------------- -------------------28.1001 BACH
DS300 UNA-O
08-00-2B-02-24-CC SH1601ENG.SYS
28.1003 MOZART DS100 UNA-O
08-00-2B-02-24-DD PS0801ENG.SYS
28.1005 HAYDN DS200 UNA-1
08-00-2B-03-AA-Fl PR0801ENG.SYS

Dump File

------------DS3BACH.DMP
PSDMP24DD.SYS
DS2HAYDN.DMP

Total of 3 DECservers defined.

Examples: Installation, Configuration, Verification

C-5

C.2.3 Adding a OECserver (Option 2)

This example adds a new DECserver 300 terminal server named BEETHO.
Your selection? 2

!RETI

Type a ? at any time for help on a question.
Type CTRL/Z for any question to return to the menu without adding the unit.

IRETI

DECserver type? DS300
DECnet node name for unit? BEETHO

IRETI
IRETI

DECnet node address for unit? 28.1002

Ethernet address of unit? 08-00-2B-03-AA-2B
DECnet Service Circuit-ID? [UNA-OJ

IRETI

If you get an error message now, the new unit won't be added,
and you should delete it from the directory.

If you use the List option to get a listing of servers, you see that BEETHO

appears on the listing of entries.
C.2.4 Swapping an Old Terminal Server for a New Terminal Server (Option 3)

In this example, an existing DECserver 100 terminal server named MOZART
is swapped for a new DECserver 300 terminal server, which is given the
same DECnet node name. The DECnet node address always stays the saIne
with Swap. The new server also has the same service circuit-ID as the old
server. (If you use Swap to change the characteristics of the same server,
you have to specify the Ethernet address even though it will not change.)
Your selection? 3

IRETI

Type a ? at any time for help on a question.
Type CTRL/Z for any question to return to the menu without changing the unit.

IRET!

What is the DEC net node name you want to swap? MOZART
DECserver at Ethernet address 08-00-2B-02-24-DD is being modified.
Enter the new Ethernet address, and any other DECnet
characteristics you want to modify.
DECserver type? [DS100] DS300

IRET!

DECnet node name for unit? [MOZART]

IRETI

Ethernet address of unit? 08-00-2B-03-AA-AB
DECnet Service Circuit-ID? [UNA-O]

C-6

!RET!

IRETI

DECserver 300 Software Installation (VMS)

C.2.5 Deleting a DECserver from the Database (Option 4)

This example shows the deletion from the load host's node database of the
existing server with the DECnet node name BACH.
Your selection? 4

IRETI

(Press CTRL/Z to return to menu.)
Enter the DECnet node name of the server you want to delete? BACH
%NCP-I-NMLRSP, listener response - Success
Remote node = 28.1001 (BACH)
%NCP-I-RECDELET, Database entry deleted

IRETI

If you use the List option to get a listing of servers, you see that BACH no
longer appears.
C.2.6 Restoring Existing DECservers to the Database (Option 5)

This example shows the restoration of the local down-line load database.
Your selection? S

IRETI

Restoring existing DECservers to host DECnet database ...
Host DECnet database successfully restored.

C.3 Example of Verification: Verifying a Load Host Installation
The following example, presented in six parts, shows the installation verification for a VMS load host. This procedure tests that your VMS system can
perform successfully as a down-line load host for a particular server.
In this example, the VMS system is named SYSTEM. The server that is
loaded is a DECserver 300 ternlinal server with DECnet node name BEETHO.
BEETHO is an existing server currently operating on the network. This example assumes that the down-line load is performed during normal working
hours and that server users are warned of the upcoming down-line load by
way of RCF.
C.3.1 Using RCF and Warning Server Users

This example uses the server's default log-in password, ACCESS.
$ MCR NCP CONNECT NODE BEETHO SERVICE PASSWORD FF23
Console connected (press CTRL/D when finished)

IRETI

* ACCESS IRETI (not echoed)
DECserver 300 Terminal Server V1.0 (BL7) - LAT VS.1
Please type HELP if you need assistance

Examples: Installation, Configuration, Verification

C-7

Enter username>

SWINSTALLER

Local>SET PRIVILEGED

IRETI

IRETI
IRETI

Password> password (not echoed)
Local> BROADCAST ALL "The server will be reloaded in 3 minutes."
Local>

IRETI

I CTRLlO I

C.3.2 Enabling DECnet Event Logging and Checking Server Names

IRETI
IRETI
IRETI

NCP> SET LOGGING CONSOLE EVENT 0.3,7
NCP> SET LOGGING CONSOLE STATE ON
NCP> SET LOGGING MONITOR STATE ON
NCP> EXIT

IRETI

$ SET DEFAULT MOM$LOAD
$

@DSVCONFIG

IRETI

You must assign a unique DECnet node name and DECnet node address
for each DECserver you are going to configure.
Press <RET> to start, or <CTRL/z> to exit ..•

IRETI

DECserver Configuration Procedure
version: Vl.8
1 2 3 4 5 CTRL/z Your selection? 1

Menu of Options
List known DECservers
Add a DECserver
Swap an existing DECserver
Delete an existing DECserver
Restore existing DECservers
Exit from this procedure

IRETI

DECnet DECnet Server Service
Address Name
Type
Circuit Ethernet Address
28.1002 BEETHO DS300

UNA-O

Load File

Dump File

08-00-2B-03-AA-2B SH1601ENG.SYS DS3BEETHO.DMP

Total of 1 DECserver defined.

C-8

DECserver 300 Software Installation (VMS)

DECserver Configuration Procedure
Version: V1.8
1 2 3 4 5 CTRL/Z Your selection?

Menu of Options
List known DECservers
Add a DECserver
Swap an existing DECserver
Delete an existing DECserver
Restore existing DECservers
Exit from this procedure

ICTRLlZ I

C.3.3 Down-Line Loading with the LOAD Command
$ MCR NCP LOAD NODE BEETHO PASSWORD FF23

IRETI

C.3.4 DECnet Event-Logging Display after Issuing LOAD
NCP> LOAD NODE BEETHO SERVICE PASSWORD FF23 IRETI
DECnet event 0.3, automatic line service
From node 4.205 (SYSTEM), 18-JUN-1989 01:35:20.47
Circuit UNA-O, Load, Requested, Node = 28.1002 (BEETHO)
File
MOM$LOAD:SH1601ENG, Operating system Ethernet address
03-AA-2B
DECnet event 0.3, automatic line service
From node 4.205 (SYSTEM), 18-JUN-1989 01:43:21.14
Circuit UNA-O, Load, Successful, Node = 28.1002 (BEETHO)
File = MOM$LOAD:SH1601ENG, Operating system Ethernet address
04-AA-2B

Examples: Installation, Configuration, Verification

08-00-2B-

C-9

C.3.S Checking the Service Circuit

This part is optional, and is presented in case the service circuit becomes
disabled. Type the following command to verify that the service circuit,
BNA-O, is enabled:
NCP>SHOW CIR BNA-O CHARACTERISTICS

IRETI

Circuit Volatile Characteristics as of 17-Jun-89 08:23:45

Circuit = BNA-O
=on
=disabled
= 4.378 (LKGRT3)
=4
=64
=15
=Ethernet
= 4.378 (LKGRT3)
=90

state
Service
Designated router
Cost
Router priority
Hello timer
Type
Adjacent node
Listen timer
NCP>

If the state is disabled, first check that the system is not busy by typing the

following command:
NCP>SHOW KNOWN LINKS

IRETI

Known Link Volatile Summary as of 17-Jun-89 08:25:23
Link
33848
8615
34154
NCP>

Node
2.632 (JOEDEV)
3.118 (MERLE)
4.54
(SMAUG)

PID
24203120
2420372C
24203F2B

Process

Remote Link

Remote User

34655
309
33388

MAIL
CTERM
DECNET_MAIL

MCGREGOR
POOR
MAIL_34154

The example shows that there are three users. If you enable the circuit at
this time, you will disable the current users. If the circuit is not busy, type
the following commands to enable service circuit, BNA-O.

IRETI

NCP>SET CIR BNA-O STATE OFF
NCP>SET CIR BNA-O SERVICE ENABLED STATE ON

C-10

IRETI

DECserver 300 Software Installation (VMS)

C.3.6 Conclusion of a Load Host Installation Verification
NCP> CLEAR LOGGING CONSOLE EVENT 0.3,7
NCP> EXIT

!RET!

C.4 Example of Verification: Verifying the Server System
Installation
This example shows the verification of a server system installation. This procedure tests the hardware, the correctness of the software version, and the
ability of the new software to run successfully.
It assumes that you are at a terminal connected to the server's Port 1, that
your username is SWINSTALLER, that your user password is SQUIDS, that
you will test the server by connecting to your own VMS system, SYSTEM,
and that the new DEC server 300 software is Version 1.0.

!RET!
!RET!
DECserver 300 Terminal Server Vl.O (BL7) - LAT V5.1
Please type HELP if you need assistance
Enter username>

SWINSTALLER

!RET!

Local> TEST PORT COUNT 5 WIDTH 65

!RET!

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]~_'
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]~_ 'a

"#$%&'()*+,-./0123456789:i<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]I\_ 'ab
#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]"_ 'abc
$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]"_ 'abcd
Local> SHOW PORT

!RET!

The display at the port of a new DECserver 300 terminal server should
match the following example, which contains the factory-set values, except
for the port number, user name, and server name:
Port 1:

SWINSTALLER

Server: LAT_08002B03AA2B

Character Size:
Flow control:
parity:

XON
None

Input Speed:
Output Speed:
Modem Control:

9600
9600
Disabled

Access:
Backward Switch:
Break:
Forward Switch:

Local
None
Local
None

Local Switch:
Name:
Session Limit:
Type:

None
PORT_l
4
Soft

Examples: Installation, Configuration, Verification

C-11

Preferred Service: None
Authorized Groups:
(Current) Groups:

0
0

Enabled Characteristics:
Autobaud, Autoprompt, Broadcast,' Input Flow Control, Loss Notification,
Message Codes, Output Flow Control, Verification
Local> SHOW SERVICES ALL SUMMARY

IRETI

Service Name

Identification

Status

DEVELOP
DOCUMENT
TEST
TIMESHARING
SYSTEM

2 Connected
Available
Unavailable
Unknown
Available

Hardware Timesharing Service Ident
Documentation Timesharing
As usual
Server Software Development
VAX/VMS 8600

Local> CONNECT SYSTEM I~ETI
Local -010- Session 1 to SYSTEM established
SYSTEM -- VAX 8600, The Best for Down-line Loading

IRETI
IRETI (not echoed)

Username: SWINSTALLER
Password: SQUIDS

Welcome to VAX/VMS version V5.0 on node SYSTEM
Last interactive login on Wednesday, 17-JUN-1989 07:25
Last non-interactive login on Thursday, 27-MAR-1989 17:18
SYS$MANAGER:NOTICE.TXT -- SYSTEM System Notices
18-Jun-1989

All users, please purge your filest

$ SHOW TIME IRETI
18-JUN-1989 07:00:09
$ SHOW USERS IRETI
VAX/VMS Interactive Users
Total number of interactive users
Username
Process Name
PID
DAISY
DAISY
20A0257A
HEATHER
HEATHER
20A02217
20A020D2
IVY
IyY
ROSE
ROSE
20A02321
SWINSTALLER SWINSTALLER
20A02001

18-JUN-1989 07:00:13.13
4

Terminal
VTA3341
VTA3391
VTA3234
VTA3471
VTA3471

LTA3341 :
LTA3391 :
Disconnected
LTA3471:
LTA3511 :

$ LOGOUT IRETI
SWINSTALLER
logged out at 18-JUN-1989 07:00:20.98
Local -011- Session 1 disconnected from SYSTEM
Local> LOGOUT IRETI
Local -020- Logged out port 1 on server LAT_08002B03AA2B

C-12

DECserver 300 Software Installation (VMS)

Index

Aborting the installation, 2-2
Alternate load hosts
assignments, 2-9
installing software onto single
systems, 2-10
recommendation, 2-1
requirements, 2-9
using, 2-10

B
BROADCAST command
example, C-8
using RCF to issue, B-1

C
CLEAR LOGGING CONSOLE
EVENT command, C-11
Command procedures
see DSVCONFIG.COM
see VMSINSTAL.COM
Commands
BROADCAST, B-1, C-8

Commands (cont' d.)
CLEAR LOGGING CONSOLE
EVENT, C-11
CONNECT, 4-4, B-1, C-7, C-12
CREATE, 2-6
DEFINE, 2-7, 2-8
INITIALIZE, 4-2
LOAD, 4-1, C-9
LOGOUT, 4-4, C-12
SET CIRCUIT, 3-9, C-10
SET DEFAULT, 3-4, C-2, C-5,
C-9
SET LOGGING CONSOLE EVENT,
C-9
SET LOGGING CONSOLE STATE,
C-9
SET LOGGING MONITOR STATE,
C-9
SET PRIVILEGED, C-8
SHOW CIRCUIT, C-10
SHOW KNOWN LINKS, C-10
SHOW LOGICAL, 2-8
SHOW NODE, 3-3
SHOW PORT, 4-3, C-11
SHOW SERVER, 4-3
SHOW SERVICES, 4-3, C-12
SHOW TIME, C-12
SHOW USERS, C-12

Index-1

Commands (cont'd.)
TEST PORT, 4-3, C-11
Configuration of node database
see Node database
CONNECT command, 4-4, B-1,
C-7, C-12
Conventions
of DSVCONFIG.COM, 3-1 to 3-2
of VMSINSTAL. COM, 2-1
Coordinating
with server manager, 4-4
CREATE command, 2-6

D
Databases
keeping synchronized, 3-8
list of, 1-5
overview, 1-5
DECnet, 3-2, 3-4
DECnet commands, 1-4
DECnet databases, 3-3
DECnet error messages, 3-8
DECnet event logging
see Event logging
DECnet node address
description, 3-3
ensuring uniqueness, 3-3
specifying, 3-6
DECnet node name
description, 3-3
ensuring uniqueness, 3-3
specifying, 3-6
DECnet operational database, 1-5,
3-6
DECnet permanent database, 1-5,
3-6
DECnet Phase IV
see DECnet
DECnet warning message, 2-3

Index-2

DECserver 300 Identification Card, 3-2
to 3-3, 3-6, 3-9
DECserver 300 Software Product
Description, 1-6
DECserver type, 3-6
Default-id, 3-7
DEFINE command, 2-7,2-8
Device-identifier, 2-3
Disk space requirements, 2-2
Distribution files, 2-7, A-1 to A-2
Distribution media, 2-2, 2-4
Distribution software
directories, 3-2
disk space required, 2-2
file names, A-1
in distribution kit, 1-1
media, 2-2
Down-line loading
definition, 1-1
disk space required, 2-2
for verification, 4-1
load file nal11e, A-2
with LOAD command, 4-1, C-9
DSVCONFIG. COM
actions, 3-4 to 3-5
adciing servers, 3-6 to 3-7
conventions, 3-1 to 3-2
different versions of, 3-1
enabling service circuit, 1-4
error, 3-7
example of, C-4
Add option, C-6
Delete option, C-7
List option, C-5
Restore option, C-7
Swap option, C-6
exiting from, 3-9
invoking, 3-4
listing servers, 3-6
menu, 3-5, C-5
merge messages, 3-8

DSVCONFIG.COM (cont'd.)
option 1, 3-6
option 2, 3-6
option 3, 3-8
option 4, 3-8
option 5, 3-8
overview, 1-4
requirements, 3-1 to 3-2
running the procedure, C-5
using for DECserver 100 terminal
servers, 3-1
using for DECserver 200 terminal
servers, 3-1
using for DECserver 500 terminal
servers, 3-1
DSVCONFIG.DAT
contents of, 3-6
definition, 1-5
DSVCONFIG_SPECIFIC.DAT, 3-9

E
Error messages, 3-7
Ethernet address, 3-3, 3-7
Event logging
disabling, C-ll
enabling, C-8
example of, C-9
messages, 4-1
reading the messages, C-9

F
File names, A--,l
G
Group numbers, 4-3

H
Hardware, 4-1, 4-2

Identification card

see DECserver 300 Identification Card
INITIALIZE command, 4-2
Installation, 2-10
aborting, 2-2
disk space required, 2-2
example of, C-1 to C-4
flow chart, 1-2, 1-3
onto alternate load hosts, 2-9, 2-10
onto other operating systems, 2-10
overview, 1-1, 1-4
procedure
see VMSINST AL. COM
recomnlended procedure, C-1
verifying, 4-1
Installation Verification Procedure
initiating, 2-6
location, 2-7
overview, 1-4
IVP
see Installation Verification
Procedure

L
LOAD command, 4-1, C-9
Load host's node database
see Node database
Load hosts
alternates, 2-1
disk space requirements, 2-2
primary, 2-2
recommended number, 2-1
VAXc1usters as, 3-8

Index-3

Loading
see Down-line loading
LOGOUT command, 4-4, C-12

M
Merge on VAXcluster nodes, 3-8 to
3-9
MOM$LOAD, 2-6; 2-8 to 2-9, 3-4

N
Network Control Program (NCP)
commands
see Commands
messages, 3-7
Node database
configuration overview, 1-4, 1-5
example configuration, C-4

o
Optional products, 1-6
OPTIONS G, 2-10
OPTIONS N, 2-3

p
Passwords
server maintenance password, B-1,
B-2
service password (DECnet service
password), B-1, B-2
Prerequisite products, 1-6

R
RCF
connecting to node, B-1
disconnecting from node, B-2

Index-4

RCF (cont'd.)
example of use, C-7
using to issue BROADCAST, B-1
Release notes
checking, 2-10
directory in, 2-5
displaying, 2-3, 2-4
file natne, 2-4, A-2
printing, 2-3, 2-4, 2-5, C-l, C-2,
C-5
Release notes options menu, 2-4
Remote Console Facility
see RCF

s
Savesets, 2-3, 2-10
Server configuration database
see DSVCONFIG.DAT
Server image, I-I, 1-6, 2-6, 4-1, 4-2
Server software
see Distribution software
see Server image
Service circuit
checking, C-I0
enabling automatically, 1-4
enabling manually, C-I0
types, 3-7
SET CIRCUIT command, 3-9, C-I0
SET DEFAULT command, 3-4, C-2,
C-5, C-9
SET LOGGING CONSOLE EVENT
command, C-9
SET LOGGING CONSOLE STATE
command, C-9
SET LOGGING MONITOR STATE
command, C-9
SET PRIVILEGED command, C-8
SHOW CIRCUIT command, C-I0
SHOW KNOWN LINKS command,
C-I0

SHOW LOGICAL command, 2-8
SHOW NODE command, 3-3
SHOW PORT command, 4-3, C-11
SHOW SERVER comlnand, 4-3
SHOW SERVICES command, 4-3,
C-12
SHOW TIME command, C-12
SHOW USERS conlmand, C-12
Software license, 2-2, 2-6
Synchronizing databases, 3-8
System disk
back up, 2-2, 2-3
disk space required, 2-2
System installation definition, 4-1
System start-up file, 2-7 to 2-8

T
Terminal Server Manager
see TSM
Testing server commands
for verification, 4-1
TEST PORT command, 4-3, C-11
TSM, 1-1, 2-7, A-1, A-2

u
Up-line dumping
disk space required, 2-2
received by load host, 2-9

Verifying the installation
of load host, 4-1
by down-line loading, 4-1
example of, C-7 to C-11
disabling event logging,
C-11
down-line loading, C-9
event logging, C-9
LOAD command, C-9
using DECnet event
logging, C-8
using RCF, C-7
warning server users,
C-7
of server system, 4-2
example of, C-11 to C-12
VMSINSTAL
aborting, 2-2
conventions, 2-1
displaying release notes, 2-3, 2-4
example of, C-1
exiting, 2-7
invoking, 2-3
overview, 1-4
printing release notes, 2-3, 2-4,
2-5, C-1, C-2, C-5
restarting, 2-5
running on VMS V5.0, C-1
VMS tailoring classes, 2-2

v
VAXclusters
as load host, 3-8
installing distribution software onto,
2-6
merge procedure, 3-4 to 3-5
verifying merge, 3-8 to 3-9

Index-5

DECserver 300
Software Installation (VMS)
AA-NE45A-TE
READER'S COMMENTS
What do you think of this manual? Your comments and suggestions will help us to improve the quality
and usefulness of our publications.
Please rate this manual:
Poor
Accuracy
Readability
Examples
Organization
Completeness

1
1
1
1
1

2
2
2
2
2

3
3
3
3
3

4
4
4
4
4

Excellent
5
5
5
5
5

Did you find errors in this manual? If so, please specify the error(s) and page number(s).

General comments:

Suggestions for improvement:

Name _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Date _ _ _ _ _ _ _ _ _ __
Title _ _ _ _-

_ _ _ _ _ _ _ _ _ _ _ _ _ _ Department

Company _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Street
City_ _ _ _ _ _ _ _ _ _ State/Country _ _ _ _ _ _ _ _ Zip Code _ _ __

DO NOT CUT - FOLD HERE AND TAPE

111111
BUSINESS REPLY LABEL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

momDDmO™
Networks and
Communications Publications
550 King Street
Littleton, MA 01460-1289
DO NOT CUT - FOLD HERE

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES