          DECserver 200J     ______________________________________________________________________         	Software Installation Guide 	(VMS)        
 	June 1989 	 D 	This guide tells you how to install the DECserver 200 distribution N         software onto a VMS system, how to configure the system as a down-lineG 	load host, and how to verify the installation. This guide is intended  3 	for the VMS system manager or the network manager.           ; 	Supersession/Update Information:	This is a revised manual.   / 	Operation System and Version:		VMS 4.7 and 5.0   & 	Software Version			DECserver 200 V3.0  G 	This manual applies to Version 3.0 of DECserver 200 and all subsequent ; 	maintenance releases up to the next major product release.                     DIGITAL     	Order No. AA-HL79C-TK        6 	_____________________________________________________ 						     Contents   2 	1.	Introducing the DECserver 200 Terminal Server   0 		1.1 What Is the DECserver 200 Terminal Server? 		1.2 DECserver 200 Concepts 		1.2.1 Connections  		1.2.2 Services& 		1.2.3 Service Nodes and LAT Protocol 		1.2.4 LAT Software* 		1.3 Performing the Software Installation: 		1.3.1 Installing the DECserver 200 Distribution Software1 		1.3.2 Configuring the Load Host's Node Database " 		1.3.3 Verifying the Installation. 		1.3.3.1 Verifying the Load Host Installation2 		1.3.3.2 Verifying the Server System Installation  6 	2.	Installing the DECserver 200 Distribution Software   		2.1 Overview of VMSINSTAL 1 		2.2 Preparing to Run the Installation Procedure  		2.3 VMSINSTAL Conventions  		2.4 Running VMSINSTAL ; 		2.5 Special Installation Considerations for DSVCONFIG.COM * 		2.6 Installing onto Alternate Load Hosts& 		2.6.1 Installing onto Single Systems# 		2.6.2 Installing onto VAXclusters / 		2.6.3 Installing onto Other Operating Systems  		2.7 After Exiting VMSINSTAL     / 	3.	Configuring the Load Host's Node Database      		3.1 Overview of DSVCONFIG ' 		3.1.1 Databases Affected by DSVCONFIG 4 		3.1.2 DSVCONFIG Options for the Software Installer8 		3.2 Specifying DECnet Characteristics During DSVCONFIG 		3.2.1 DECnet Node Name 		3.2.3 DECnet Node Address  		3.2.3 Ethernet Address 		3.2.4 Server Type % 		3.2.5 Load File (Server Image File)  		3.2.6 Dump File Name 		3.2.7 Service Circuit 2 		3.3 Preparing to Run the Configuration Procedure, 		3.4 DSVCONFIG Conventions and Requirements 		3.5 Running DSVCONFIG ( 		3.5.1 List Known DECservers (Option 1)" 		3.5.2 Add a DECserver (Option 2). 		3.5.3 Restore Existing DECservers (Option 5)9 		3.6 Restoring with the Restore Parameter and from Your   		    Start-Up Procedure% 		3.7 Configuring on VAXcluster Nodes , 		3.7.1 Running DSVCONFIG for the First Time/ 		3.7.2 Running This Version of DSVCONFIG Again  		3.8 Exiting DSVCONFIG " 		3.9 After Exiting from DSVCONFIG   	4.	Verifying the Installation  * 		4.1 Verifying the Load Host Installation' 		4.1.1 If You Are Loading a New Server - 		4.1.2 If You Are Loading an Existing Server " 		4.1.2.1 Loading During Off-Hours    & 		4.1.2.2 Warning Users Before Loading/ 		4.1.3 Down-Line Loading with the LOAD Command ( 		4.1.3.1 Preparing for the LOAD Command" 		4.1.3.2	Issuing the LOAD Command$ 		4.1.3.3 Using DECnet Event Logging. 		4.2 Verifying the Server System Installation  $ 	A.	DECserver 200 Distribution Files    % 	B.	Using the Remote Console Facility     7 	C.	Examples: Installation, Configuration, Verification     		C.1 Example of an Installation  		C.2 Example of a Configuration 		C.2.1 Starting DSVCONFIG.COM1 		C.2.2 Listing Known Terminal Servers (Option 1) + 		C.2.3 Adding a Terminal Server (Option 2) 6 		C.2.4 Swapping an Old Unit for a New Unit (Option 3)? 		C.2.5 Deleting a Terminal Server from the Database (Option 4) < 		C.2.6 Restoring Existing Terminal Servers to the Database  		      (Option 5)A 		C.3 Example of Verification: Verifying a Load Host Installation * 		C.3.1 Using RCF and Warning Server Users? 		C.3.2 Enabling DECnet Event Logging and Checking Server Names / 		C.3.3 Down-Line Loading with the LOAD Command 7 		C.3.4 DECnet Event-Logging Display After Issuing LOAD $ 		C.3.5 Checking the Service Circuit; 		C.3.6 Conclusion of a Load Host Installation Verification ; 		C.4 Example of Verification: Verifying the Server System   		    Installation     	D.	How to Report a Problem    		D.1 Submitting an SPR & 		D.2 Reporting Documentation Problems 		D.3 Handling Severe Errors   		         Preface   -      This installation guide explains how to:   I      o  Install the DECserver 200 distribution software onto a VMS system P         running DECnet so that this system can then perform as a load host. The I         potential load host can be a single system or a member node of a           VAXcluster.   0      o  Configure the load host's node database.  O      o  Verify the installation by first down-line loading the server image to  F         the DECserver 200 unit and then testing a few server commands.   Intended Audience   K      This guide is intended for system managers or network managers who are L      responsible for making server products available on their Ethernets. A J      system manager is responsible for the VMS system that is about to be M      established as a load host. A network manager is the person responsible  &      for the local area network (LAN).  L      To use this guide effectively, you should be familiar with both DECnet >      network management concepts and the VMS operating system.   Structure of This Manual  7      This manual has four chapters and four appendixes:   G      Chapter 1	Introduces the DECserver 200 product and summarizes the  ; 		installation, configuration, and verification procedures.   L      Chapter 2	Describes first how to prepare for the installation and then + 		how to install the distribution software.     G      Chapter 3	Explains how to configure the load host's node database.   J      Chapter 4	Explains how to verify the installation by first down-line B 		loading the server image and then testing a few server commands.  O      Appendix A	Lists the names of the files in the DECserver 200 distribution   		kit.  D      Appendix B	Discusses briefly the Remote Console Facility (RCF).  H      Appendix C	Contains examples of the installation and configuration ? 		procedures and examples of verification by down-line loading.   K      Appendix D	Contains instructions for reporting problems, if any occur   		during the installation.   Other DECserver 200 Documents   "      o	Using DECserver 200 Manuals  I 	Directs you to information contained in the DECserver 200 documentation  A 	set. Flowcharts suggest logical reading sequences for different  I 	audiences. This document is intended for all users of the DECserver 200   	documentation set.   %      o	DECserver 200 Management Guide   G 	Describes all the initial and day-to-day management tasks required of  H 	the DECserver 200 manager. The topics cover all the information needed N         to configure the ports and to customize the permanent and operational N         databases of the server. This guide is intended for the DECserver 200 	 	manager.   !      o	DECserver 200 User's Guide   G 	Describes the user interface and the general functions of the server.  C 	This guide gives complete information for using all nonprivileged  D 	server commands. It is intended for users of interactive terminals " 	connected to DECserver 200 ports.  ,      o	Terminal Server User's Reference Card  H 	Describes on a reference card the most frequently used server commands.    9      o	DECserver 200 Hardware Installation/Owner's Manual   I 	Describes environmental requirements for the DECserver 200 unit and the  C 	installation of the hardware unit. This guide is intended for the   	hardware installer.  (      o	DECserver 200 Identification Card  A 	Provides the space to record identification information for the  H 	DECserver 200 unit. This document is intended for the network manager, 0 	the software installer, and the server manager.  ,      o	Terminal Server Commands and Messages  @ 	Describes the usage and syntax of all terminal server commands E 	(privileged and nonprivileged). This guide also lists and describes  G 	all status and error messages issued by the server. This reference is  F 	intended for the server manager but is useful for terminal users who * 	want more detailed reference information.  ,      o	DECserver 200 Commands Mini-Reference  A 	Summarizes all privileged and nonprivileged server commands and  D 	characteristics in a pocket-size mini-reference. This reference is F 	intended as a memory jog of command syntaxes for both privileged and  	nonprivileged users.   0      o	DECserver 200 Problem Determination Guide  A 	Describes the server's troubleshooting tools and procedures. It  G 	explains how to isolate server faults and how to repair the server to  B 	the field-replaceable unit level. This guide is intended for the  	server manager.        o	Terminal Server Glossary   G 	Defines terms used in server documentation. This document is intended  ; 	as a reference tool for all users of server documentation.   ,      o	DECserver 200 System Technical Manual  I 	Describes how the DECserver 200 system software and hardware components  F 	interact to perform server functions. This manual also describes the ? 	hardware specifications, the controls and indicators, and the  F 	diagnostics self-test program. Detailed descriptions of the hardware F 	components are not included but are found in the hardware manual for E 	the specific component. This manual is intended for training, field  & 	service, and manufacturing personnel.       Associated Documents  !      o	LAT Network Concepts Guide   H 	Presents information about local area transport (LAT) and LAT networks.F 	It discusses LAT concepts and definitions and provides guidelines to G 	coordinate the configuration, performance, and troubleshooting of LAT   	servers and service nodes.   (      o	Guide to Terminal Server Manager    	and    4 	Terminal Server Manager Software Installation Guide  B 	Explain how to install and run the Terminal Server Manager (TSM) F 	software, an optional network management product, which is installed H 	onto a VMS system running DECnet-VAX. These guides describe how to use H 	TSM to manage a mix of Digital Equipment Corporation Ethernet terminal H 	servers connected to the same Ethernet as a VAX computer. These guides H 	are intended for the installer and manager of the TSM software product.   				Note  ? 	If you have the TSM software, read the documentation for this  = 	product before you look at the DECserver 200 documents. TSM  0 	affects the way you install and manage servers.     Conventions Used in This Manual   L       Familiarizing yourself with the conventions discussed in this section K       will help you use this manual effectively. The following conventions         apply to numbers:   7       o	All numbers are decimal unless otherwise noted.   8       o	All Ethernet addresses are given in hexadecimal.  ' Graphic Conventions Used in This Manual   O       _________________________________________________________________________        Convention	MeaningO       _________________________________________________________________________     M       Special type     This special type in examples indicates system output  K                        or user input. System output is in black type; user  ,                        input is in red type.  L       UPPERCASE	       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 or to the TSC.   F      lowercase	       Lowercase italics in command syntax or examples ,      italics	       system supplies a value.  F      BOLD	       In summaries of characteristics, bold type indicates  		       default values.  E      bold	       In text, words appearing in bold type introduce new  A 		       terms or concepts and can also be found in the glossary.   D      [  ]	       Square brackets in command lines 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.     = 		       In the installation dialog, square brackets enclose  ; 		       default answers. To choose the default, press the  ? 		       RETURN key. To specify another value, type the answer  5 		       after the question and press the RETURN key.     H      <key> 	       Press the specified key. For example, <RETURN> means <                        that you should press the RETURN key.  F      <CTRL/x>	       Hold down the CONTROL key and then press the key 6 		       specified by x. The server displays this key  		       combination as ^x.             =                                                             1 / 		_____________________________________________ 0 		Introducing the DECserver 200 Terminal Server     . 1.1 What Is the DECserver 200 Terminal Server?  O      The DECserver 200 terminal server is a hardware and software product that  N      connects to an Ethernet local area network (LAN). The server connects as L      many as eight terminals (or other asynchronous port devices) to a LAN, J      allowing each device to communicate with the other nodes on that LAN.  M      The software that you are about to install consists of the files in the  H      DECserver 200 distribution kit. After you install the distribution O      software onto your system, you will configure your system's node database  I      for all new servers. Next, you verify the installation by down-line  O      loading one test server. Down-line loading means sending the server image  L      from the established load host to the server. Finally, you issue a few N      server commands to test the server system. Installation requires the NET ?      VMS, UTIL VMS, and VMS REQUIRED SAVESET tailoring classes.    1.2 DECserver 200 Concepts  O      The DECserver 200 unit gives terminals access to all services of the LAN,  2      supporting both direct and modem connections.       1.2.1 Connections   J      Port devices can be connected directly to the server, or they can be N      connected remotely by using modems. The DECserver 200 unit also supports N      printers and connections to hosts that support EIA 232-D or asynchronous M      connections. With the DECserver 200/DL unit, terminals and printers can  I      be attached with DECconnect cables. With the DECserver 200/MC unit,  G      terminals and printers can	be attached by using modem connections.    1.2.2 Services  N      The DECserver 200 unit gives terminals access to services offered on the N      LAN. A service is a resource such as a computer. Each DECserver 200 user H      can maintain up to eight simultaneous connections to these various       services.  $ 1.2.3 Service Nodes and LAT Protocol  N      Server users are offered services by service nodes. A service node is anyN      node on the LAN that implements the local area transport (LAT) protocol. M      The server, in turn, uses the same LAT protocol to connect terminals to  D      these services. LAT architecture uses Ethernet to make logical I      connections between terminals and service nodes on the same network.   N      When connected to a service, a terminal appears to be connected directly N      to the service node. DECnet is not necessary for VMS systems to function       as LAT service nodes.  H      The DECserver 200 unit itself can be configured as a service node, N      offering printers, dial-out modems, and non-LAT host systems as services       on the LAN.   1.2.4 LAT Software  I      LAT V5.1 is implemented on a VMS node by LAT/VMS. This includes the  O      LTDRIVER, which is a port driver in direct communication with the system's J      terminal class driver. LTDRIVER implements the protocol necessary to N      communicate with devices connected to the server and is used in place of N      a local port driver, such as the DZDRIVER. A LAT Control Program (LATCP) J      provides the command interface to the LTDRIVER. LATCP can be used to @      start and stop the driver as well as to set and to display #      characteristics of the driver.d e  N      A network node does not need LAT to perform load-host functions, but LAT K      software is required for a system to offer services as a service node.v  N      On remote-access ports, the DECserver 200 unit permits VMS service nodes M      with this software to make requests for printers on server ports. These i1      requests are called host-initiated requests.   ( 1.3 Performing the Software Installation  B      As a software installer, you are responsible for three tasks:  :      1. Installing the DECserver 200 distribution software  1      2. Configuring the load host's node databased  3      3. Verifying the installation, which includes:_  A 	- Verifying the load host installation by down-line loading the   	  server image   D 	- Verifying the server system installation by testing a few server  	  commands   N      Completion of these tasks establishes your VMS system as a load host for K      one or more servers. A load host is a system that contains the server  O      image and whose node database has entries for specific servers, and, as a hI      result, can down-line load the server image to servers on the local  M      Ethernet. In addition, a load host performs maintenance activities such t0      as receiving up-line dumps from the server.  M      A load host can be a single VMS system, or it can be a member node of a aL      VAXcluster. For a VMS system to act as a load host, it must be running I      DECnet Phase IV, and it must be located on the same Ethernet as the gG      server. For supported version numbers of DECnet software, see the .@      Software Product Description for the DECserver 200 product.  H      A load host must have 850 free blocks of disk space to install the M      DECserver 200 distribution files. Another 768 free blocks of disk space f'      is required for each up-line dump.p n  G      Load hosts are assigned by the network manager. Digital Equipment gK      Corporation advises that you establish more than one system as a load tN      host for each server. Alternate hosts free the server from dependence on N      one particular load host. For each server, Digital Equipment Corporation N      suggests a minimum of two load hosts. Digital Equipment Corporation also A      recommends one load host for every ten servers on a network.   O      When selecting alternate load hosts, you can choose any Digital Equipment nF      Corporation system for which a DECserver 200 distribution kit is K      available. DECserver 200 software distribution kits are available for s      these systems:n  .      o	VMS V4.7 through V5.2 and MicroVMS V4.7        o	RSX-11M-PLUS         o	Micro/RSX        o	ULTRIX-32  I      For information on installing the server distribution software onto uM      another operating system and configuring that system's node database in .L      order to establish it as an alternate load host, see the DECserver 200 1      software installation guide for that system.	  L      In addition to the three tasks just described, you must coordinate the I      total software installation procedure with both the server hardware aM      installer of a new server and the server manager of an existing server. FJ      For example, the software should be installed before the hardware is G      powered up for the first time. Chapter 4 details the coordination  I      necessary among you, the hardware installer, and the server manager.   8 1.3.1 Installing the DECserver 200 Distribution Software  L      You install the server distribution software onto a VMS system with an F      automated procedure called VMSINSTAL. The DECserver 200 software N      distribution kit includes a procedure file that VMSINSTAL uses to do the 0      installation. VMSINSTAL does the following:  E      o	Copies the files from the distribution media to the load host.r  9      o	Creates the appropriate directory for these files.  .  I      o	Prints the DECserver 200 Release Notes. VMSINSTAL gives you three rF 	choices: (1) display the release notes, (2) print the release notes, , 	or (3) display and print the release notes.  L      See Chapter 2 for instructions on installing the distribution software.   				Note  @ 	If you have the Terminal Server Manager (TSM) software V1.2 or > 	later, 	an optional network management product available for @ 	VMS load hosts, read the documentation for this product before A 	you install the DECserver 200 software. TSM affects the way you t 	install and manage servers.  / 1.3.2 Configuring the Load Host's Node Database   L      Once you copy the distribution software to your VMS system, you should F      configure the system's node database to support new servers. You O      configure this database with an automated procedure called DSVCONFIG. The aI      DSVCONFIG configuration procedure file is part of the DECserver 200 u      software distribution kit.r  L      Configuration of the load host's node database means defining an entry L      for each server in three places: (1) a data file called DSVCONFIG.DAT, O      (2) the DECnet operational (also called "volatile") database, and (3) the  E      DECnet permanent database. The DSVCONFIG.DAT file is the server        configuration database.    O      DSVCONFIG.DAT is automatically created by DSVCONFIG and is part of a load V      host's node database.  N      When you use DSVCONFIG to configure a new server, DSVCONFIG automaticallyM      adds an entry in the three places mentioned above. The entry identifies n	      the:         o	Server type  8      o	Server's DECnet node name and DECnet node address  "      o	Server's service circuit-ID         o	Server's Ethernet address        o	Server image  C  G      When you complete the configuration procedure, your VMS system is CN      established as a load host for each server that has an entry in the node M      database. See Chapter 3 for instructions on configuring the load host's t&      node database to support servers.  N      To configure a server on a VAXcluster, install the distribution software O      onto one member node and then configure the node databases of the members oK      that you want to establish as load hosts. See Section 3.7 for details.   L      Besides allowing you to configure a new server in the load host's node M      database, DSVCONFIG allows you to list all servers currently defined in DN      the DSVCONFIG.DAT file and to restore to the host's DECnet databases all O      server configurations defined in DSVCONFIG.DAT. Chapter 3 explains how to eM      use these options. Appendix C has examples showing how to use these and  L      two other options: (1) Replacing an existing DECserver unit with a new O      DECserver 200 unit (or changing the characteristics of an existing unit), 0P      and (2) removing a DECserver 200 unit from the node database. Normally you L      do not use these latter two options during the installation procedure. A      The DECserver 200 Management Guide explains how to use them.     1.3.3 Verifying the Installation  J      After configuring the node database, your final responsibility is to N      verify the installation. Actually, you need to perform two verifications:  O      1. To verify the installation of the load host, down-line load the server  I      image to a server, and then read the DECnet event-logging messages.  O      Verifying the installation of the load host means checking that this load r
      host:  ;      -	Has the appropriate files in the correct directory. i  D      -	Has a correct entry in its node database for the test server.  8      -	Can successfully down-line load the server image.  J      2. To verify the total server system installation, test a few server N      commands at an interactive terminal connected to a server port. Verifying1      the system installation means checking that:n  <      -	The correct version of the software is in the server.  :      -	The server hardware operates with the new software.  0      -	The new software is running successfully. .  , 1.3.3.1 Verifying the Load Host Installation  P      To verify that your VMS system has been successfully established as a load N      host, use it to perform a down-line load. Down-line loading means sendingB      the server image from an established load host to the server.  N      Use the NCP LOAD NODE command from your VMS load host to down-line load. N      Then, check the DECnet event-logging messages in order to verify that the      load was successful.o  0 1.3.3.2 Verifying the Server System Installation  J      Using a few server commands at an interactive terminal attached to a O      server port completes your verification of the server system installation.w  G      See Chapter 4 for details on the two verification procedures. See sH      Appendix A for a list of the DECserver 200 distribution files. See O      Appendix B for a brief discussion of the Remote Console Facility. Finally, E      see Appendix C for step-by-step examples of the entire software v      installation.   a      B                                                                  24 		__________________________________________________4 		Installing the DECserver 200 Distribution Software  N      This chapter describes how to prepare for installation and how to installI      the DECserver 200 distribution software onto your VMS load host. To  L      install the software, use VMSINSTAL.COM, an automated procedure, which )      is part of the VMS operating system.r   2.1 Overview of VMSINSTALi  G      VMSINSTAL is an interactive procedure that calls and controls the oL      DECserver 200 installation procedure. VMSINSTAL performs the following       tasks:t  O      o	Creates a directory called SYS$SYSROOT:[DECSERVER] on the load host, if r
 	necessary  G      o	Copies the files from the distribution media into this directory   H      o	Prints a copy of the DECserver 200 Release Notes when you specify         OPTIONS Nn  / 2.2 Preparing to Run the Installation Procedures  ;      Before you actually run VMSINSTAL, follow these steps:l  M      1.	Determine which systems are designated as load hosts for the server. TN         You must install the distribution software onto all of these systems. N         Ask your network manager or the person responsible for assigning load ;         hosts to tell you which are the designated systems.  	  M         Note that you do not need a separate license for each load host, but t7         you do need a separate license for each server.a  M      2.	Check that there are 850 free blocks of disk space on each load host nL         for copying the distribution files. Another 768 free blocks of disk ) 	space is required for each up-line dump.   F 	Ensure that the network and utility classes are tailored on the load  	host.   2.3 VMSINSTAL Conventionsh  N     VMSINSTAL is an interactive procedure. When you start VMSINSTAL, a series O     of questions displays. After each question, the default response, if there _N     is one, displays in square brackets ( [ ] ). At the end of each question, 6     either a colon (:) or a question mark (?) appears.  N     o	To answer a question, type your response immediately after the colon or 1         question mark; then press the RETURN key.   N     o	To respond to a question with the default answer, press only the RETURN  	key.   J     o	To get help after any question, type a question mark (?). After the ( 	help display, the question is repeated.  F     See the VMS documentation for a complete description of VMSINSTAL.   2.4 Running VMSINSTALd  L     Running VMSINSTAL.COM requires the appropriate privileges. To determine *     what they are, see the system manager.  J     Run VMSINSTAL.COM from the system manager's account. The installation G     procedure takes approximately 10 to 15 minutes. Follow these steps:r  E     1. Place the distribution medium on the appropriate device drive.   ,     2. Log in to the system manager account. w  +     3. Start VMSINSTAL with these commands:f  # 	$ SET DEFAULT SYS$UPDATE  <RETURN> 7 	$ @VMSINSTAL DS2 device-identifier OPTIONS N <RETURN> 	  J     Here, DS2 is the VMS three-letter facility code for the DECserver 200 J     product and device-identifier is the device on which the distribution H     medium is mounted. OPTIONS N tells VMSINSTAL to ask you, during the D     procedure, if you want to print the DECserver 200 Release Notes.   				Note  ; 	Digital Equipment Corporation recommends that you specify r? 	OPTIONS N on the command line.  See the VMS documentation set  > 	if you do not want to print the release notes, or if you are ) 	interested in VMSINSTAL's other options.T  I     If you are installing onto alternate load hosts with copied savesets, D     the VMSINSTAL command line format differs slightly. See the VMS      documentation on VMSINSTAL.   N     VMSINSTAL displays the procedure title and the date and time. It continuesO     with the following (the warning message appears only if DECnet is running):   @     %VMSINSTAL-W-DECNET, Your DECnet network is up and running. +     * Do you want to continue anyway [NO]? s  J     4.	Type YES and press the RETURN key to proceed with the installation.       5.	VMSINSTAL asks:  ? 	* Are you satisfied with the backup of your system disk [YES]?o  E     6.	If you answer NO, the installation procedure terminates. Take n2 	appropriate action and start the procedure again.  C 	If the backup is satisfactory, press the RETURN key to answer YES.o  J     7.	If you are installing from the distribution media rather than from B 	copied savesets, VMSINSTAL prompts you to mount the first volume:  ? 	Please mount the first volume of the set on device-identifier.g 	* Are you ready?   E 	Type YES and press the RETURN key. A confirmation message says that e 	the medium is mounted.. n       8.	The procedure continues:   * 	The following products will be processed:  	 	DS2 Vn.nh  - 		Beginning installation of DS2 Vn.n at hh:mmS  6 	%VMSINSTAL-I-RESTORE, Restoring product saveset A...      				Note  = 	DECserver 200 software version numbers are not specified in  > 	this manual. For example, the release notes file is shown as @ 	DS2_nnn.RELEASE_NOTES. Here, nnn represents the version number;> 	if you are installing Version 3.0, the release notes file is  	DS2030.RELEASE_NOTES.  L     9.	Some types of distribution media require several volumes. (More than F 	one distribution medium is delivered with your distribution kit.) For> 	these types of distribution media, the procedure gives you a = 	continuation message and tells you to mount the next volume t/ 	(each volume is labeled with a volume number):   G 	%BACKUP-I-READYREAD, mount volume 2 on device-identifier: for reading e 	Enter "YES" when ready:    ; 	Mount the next volume, type YES, and press the RETURN key.r  I     10.	The procedure lists your options for printing and displaying the a 	release notes:i   	Release Notes Options:   " 	        1.  Display Release Notes  	        2.  Print Release Notes 	        3.  Both 1 and 2    	* Select option [3]:   F 	Select one of these options. Digital Equipment Corporation recommends 	that you select Option 2.   t# 	- If you select Option 1, you see:s  1 	  VMI$ROOT:[SYSUPD.DS2nnn]DS2nnn.RELEASE_NOTES;1a  B 	  The release notes immediately start scrolling at your terminal.   				Note  5 	     The release notes might contain up to 30 pages.e  E 	- If you select Option 2, VMSINSTAL asks you which queue you want too! 	  send the file to for printing:    	  * Queue name [SYS$PRINT]: C  B 	  Press the RETURN key to print the release notes on the default E 	  printer, or specify another print queue. A message indicates that   	  the system queued the file.  I 	- If you select Option 3, VMSINSTAL first asks you which queue you want s$ 	  to send the file to for printing:   	  * Queue name [SYS$PRINT]:  B 	  Press the RETURN key to print the release notes on the default E 	  printer, or specify another print queue. A message indicates that eE 	  the system queued the file for printing. Next, VMSINSTAL displays   	  the release notes:   2 	  VMI$ROOT:[SYSUPD.DS2nnn]DS2nnn.RELEASE_NOTES;1   B 	  The release notes immediately start scrolling at your terminal.  M     11.	After the system's queue message and the release notes are displayed  M         (if you selected one of the display options), the procedure continues          by asking:  1 	* Do you want to continue the installation [N]? v  C 	Press the RETURN key to stop the procedure and review the release vA 	notes. Check for any changes that can affect this installation. nH 	(VMSINSTAL places the release notes file, DS2nnn.RELEASE_NOTES, in the  	SYS$HELP directory.)S  P     12.	Run the procedure again when you are ready to continue. Enter this form  	of the command:  , 	$ @VMSINSTAL DS2 device-identifier <RETURN>      I     13.	VMSINSTAL displays the procedure title and the date and time. It nB 	continues with the following (the warning message appears only if 	DECnet is running):  < 	%VMSINSTAL-W-DECNET, Your DECnet network is up and running.& 	Do you want to continue anyway [NO]?   D 	Type YES and press the RETURN key to proceed with the installation.       14.	VMSINSTAL asks:e  ? 	* Are you satisfied with the backup of your system disk [YES]?   $ 	Press the RETURN key to answer YES.  K     15.	If you are installing from the distribution media rather than from  B 	copied savesets, VMSINSTAL prompts you to mount the first volume:  ? 	Please mount the first volume of the set on device-identifier.n 	* Are you ready? *t  # 	Type YES and press the RETURN key.   N     16.	A confirmation message says that the medium is mounted. The procedure  	continues:a  * 	The following products will be processed:   	  DS2 Vn.n   4 	        Beginning installation of DS2 Vn.n at hh:mm  6 	%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]?e  O     17.	If your distribution media require more than one volume, the procedure rB 	gives you a continuation message and tells you to mount the next 5 	volume. Each volume is labeled with a volume number.n  G 	%BACKUP-I-READYREAD, mount volume 2 on device-identifier: for reading   	Enter "YES" when ready:  ; 	Mount the next volume, type YES, and press the RETURN key.d s  H     18.	If you are on a VAXcluster node, the following message displays:  F 	If you intend to execute this layered product on other nodes in your E 	VAXcluster, and you have the appropriate software license, you must  E 	prepare the system-specific roots on the other nodes by issuing the oF 	following command on each node (using a suitably privileged account):  G 	$ CREATE/DIRECTORY SYS$SPECIFIC:[DECSERVER]/PROTECTION=(S:RWED,O:RWED)e  L     19.	You have finished the first part of the installation. The procedure  	continues:   D 	- It tells you that the installation is complete, meaning that the @ 	  distribution files have all been copied to their appropriate F 	  directories. (See Appendix A for descriptions of the DECserver 200  	  VMS distribution files.)   $ 	- It instructs you how to continue.  E 	- It mentions the additional software you must install at this time.   D     Your installation is now complete. After exiting from VMSINSTAL:  F     1.  Edit your system start-up file so that it defines the logical F 	MOM$LOAD as a search string with a value equal to the current search K         string plus the added element SYS$SYSROOT:[DECSERVER]. For example:   ;         DEFINE/SYSTEM/EXEC/NAME_ATTRIBUTE=NO_ALIAS/NOLOG - n@         MOM$LOAD 'current-search-string',SYS$SYSROOT:[DECSERVER]  ? 	If the current search string associated with MOM$LOAD in your  A 	start-up file is SYS$SYSROOT:[DECSERVER] or if you have already i@ 	made this change for a previous installation, there is no need  	to edit this file.s  D         This command ensures that the location of the server image  D         is defined each time the system is rebooted, necessary for  %         successful down-line loading.e  8     2.  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 nA 	installations, you need to configure only any additional units. n8 	All previously defined units will still be configured.       e  L     3.  The Installation Verification Procedure (IVP) for the DECserver 200 M 	can be found in SYS$TEST and may be run at any time by executing the        o 	command procedure DS2$IVP.COM.a  @     20.  VMSINSTAL runs the Installation Verification Procedure:  9     %VMSINSTAL-I-RESTORE, Restoring product saveset B... DD     %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target      directories ...  c  I     Beginning installation verification procedure for DECserver 200 Vn.n.u  :     Successfully located SYS$SYSROOT:[DECSERVER] directory  E     Successfully located SYS$SYSROOT:[DECSERVER]DS2nnn.RELEASE_NOTES v  =     Successfully located SYS$SYSROOT:[DECSERVER]PR0801ENG.SYSo  =     Successfully located SYS$SYSROOT:[DECSERVER]DSVCONFIG.COMr  >     Successfully located SYS$SYSROOT:[DECSERVER]DSVCONFIG.DAT   D     Successfully located SYS$SYSROOT:[DECSERVER]DS2_nnn_DEFAULTS.COM  @     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_ADD_     LOCAL_SERVICE.COMc  D     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_CTS_RTS_     PRINTER.COM      E     Sucessfully located SYS$SYROOT:[DECSERVER]TSM$DS2_nnn_DEDIC_SERV_      PRINTER.COM   B     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DEDIC_     SERV_TERM.COM   D     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DIAL_IN_
     MODEM.COM   A     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DIAL_      IN_OUT_MODEM.COM  E     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DIAL_OUT_i
     MODEM.COMu  D     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DSR_DTR_     TERM.COM  @     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_GET_     CHAR.COM  A     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_HOST_o     INIT_PRINTER.COM  @     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_NON_     LAT_HOST.COM  D     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_PC_TERM_     OR_SERV.COM.  A     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_PORT_u     DEFAULT.COMn  A     Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_TERM_l     SWITCH.COM  J     Installation verification procedure for DECserver 200 Vn.n successful.3         Installation of DS2 Vn.n completed at nn:nnd  )         VMSINSTAL procedure done at nn:nne     $u t              		           Note  A              If you are installing files onto a VAXcluster node, l9 	     the messages indicate that the files are copied to r+ 	     the SYS$COMMON:[DECSERVER] directory.   J     MOM$LOAD is a logical name that your load host uses to find the image I     file of any product that must be down-line loaded. For each product, hE     MOM$LOAD has an associated equivalence string that specifies the lN     location of the product's image file. Thus, the following command equates O     the logical name MOM$LOAD to the location of your DECserver 200 image file:a  @     DEFINE/SYSTEM/EXEC/NAME_ATTRIBUTE=NO_ALIAS/NOLOG MOM$LOAD -      SYS$SYSROOT:[DECSERVER]   M     If your system is a load host for several products, then the location of hJ     each image file must be defined by a list of equivalence strings. For N     example, the following command defines the location of a LAN Bridge image 1     file as well as the DECserver 200 image file:a  @     DEFINE/SYSTEM/EXEC/NAME_ATTRIBUTE=NO_ALIAS/NOLOG MOM$LOAD - 3     SYS$SYSTEM:[MOM$SYSTEM],SYS$SYSTEM:[DECSERVER]    I     Two or more equivalence strings make up a search list. When your VMS  J     system is requested to down-line load a product, it looks through the H     search list until it finds the location of the product's image file.  L     Your host cannot down-line load the DECserver 200 image file unless the K     search list defined for MOM$LOAD has the correct location of the image .M     file. To see what the current search string is for MOM$LOAD, use the DCL S     SHOW LOGICAL command:l  $     $ SHOW LOGICAL MOM$LOAD <RETURN>  K     If SYS$SYSROOT:[DECSERVER] is defined for MOM$LOAD, you do not have to e-     define MOM$LOAD. Define MOM$LOAD only if:r  J     - No equivalence string exists for MOM$LOAD (the SHOW LOGICAL command K       results with the message "No translation for logical name MOM$LOAD").f       or  B     - The equivalence strings defined for MOM$LOAD do not include        SYS$SYSROOT:[DECSERVER].  F     If MOM$LOAD is already defined for other products but not for the B     DECserver 200 product, you must define MOM$LOAD by specifying N     SYS$SYSROOT:[DECSERVER] along with the current search string(s), as shown J     in the VMSINSTAL example. If you specify only SYS$SYSROOT:[DECSERVER] >     for MOM$LOAD excluding the current search string(s), then L     SYS$SYSROOT:[DECSERVER] will replace the current search string(s). Your C     VMS system will not be able to load the image files located by  !     the current search string(s).	  M     21.	Depending on your system, VMSINSTAL may now let you make an entry in 03 	the Software History log. The procedure concludes:   5                     VMSINSTAL procedure done at hh:mmt   	$  # 	See Section 2.7 for the next step.o  9 2.5 Special Installation Considerations for DSVCONFIG.COMT  N     The configuration command procedure, DSVCONFIG.COM, which is part of this I     distribution kit, accommodates the DECserver 100, DECserver 200, and eM     DECserver 500 products. However, some previous releases of DSVCONFIG.COM NE     cannot accommodate the DECserver 500 product. Therefore, for all y9     configurations use the command file on your kit only.c  I     When installing new versions of DECserver products, always check the tF     product release notes for information on the latest DSVCONFIG.COM.  ( 2.6 Installing onto Alternate Load Hosts  O     Digital Equipment Corporation recommends that you establish alternate load lM     hosts for each server. Alternates free the server from dependence on one sP     particular load host because an alternate load host can perform a down-line O     load if the original load host is unavailable. In addition, alternate load a1     hosts can receive up-line dumps from servers.     J     Regarding the assignment of load hosts, Digital Equipment Corporation       suggests both the following:  O     o For each server, at least one other load host as a backup to the originale  2     o At least one load host for every ten servers  D     As with the original load host, an alternate VMS load host must:       o Be running DECnete  D     o Have an Ethernet controller on the same Ethernet as the server  .     o Have the distribution software installed  F     o Have DECserver 200 entries in its server configuration database L       (DSVCONFIG.DAT file), the DECnet operational database, and the DECnet        permanent database  /     o Have the latest load file (see Chapter 3)   3     o Have its Ethernet circuit enabled for services  $ 2.6.1 Installing onto Single Systems  P     To install the server distribution software onto an alternate VMS load host C     that is not a member of a VAXcluster, use one of these methods:t  J     o If the alternate load host has the same load device as the original N       host, place your distribution media on the appropriate device of the newN       load host and repeat the installation procedure detailed in Section 2.4.  K     o If the alternate load host does not have the same load device as the pK       original host, load and extract the savesets from the kit, using the .       following procedure:  =       -	Type the following command on the original load host:   # 	$ SET DEFAULT SYS$UPDATE: <RETURN>o  B 	$ @VMSINSTAL DS2 device-identifier OPTIONS G SYS$UPDATE: <RETURN>  G 	Here, DS2 is the VMS three-letter facility code for the DECserver 200  7 	product. OPTIONS G extracts the savesets from the kit.D U  M       -	Copy the savesets to the alternate load host's SYS$UPDATE directory. 	( 	The savesets are DS2nnn.A and DS2nnn.B.  1       -	Run VMSINSTAL on the alternate load host:   & 	$ @VMSINSTAL DS2 SYS$UPDATE: <RETURN>  ! 2.6.2 Installing onto VAXclusterse  G     To install the server distribution software onto an alternate load  >     host that is a member of a VAXcluster, follow these steps:  O     1. Run DSVCONFIG on all cluster members that are to act as load hosts. (Do n;        not reinstall the software on homogeneous clusters.)   I        The software is installed onto the common cluster disk. Since the oM        distribution files are in SYS$COMMON:[DECSERVER], all cluster members e        have access to them.m  L     2. Follow the steps in Section 3.7 to keep accurate each member's three         databases for servers.p  - 2.6.3 Installing onto Other Operating Systemss  H    To install the DECserver 200 distribution software onto an operating G    system other than VMS, follow the instructions in the DECserver 200  K    Software Installation Guide for that system. You can find the guide for hM    one of the other supported operating systems in the software distribution AL    kit for that operating system. Or you can separately order any DECserver @    200 Software Installation Guide for another operating system.   2.7 After Exiting VMSINSTALd  0    After you exit VMSINSTAL, follow these steps:  N    1. Check the DECserver 200 Release Notes to see if you have to install any L       additional software from the distribution media. If so, install those        distribution files.   A    2. Give the DECserver 200 Release Notes to the server manager.r  L    3. Run the configuration procedure, DSVCONFIG.COM, to configure the load O       host's node database. See Chapter 3 for information about this procedure.i   o      9                                                         3n, 		__________________________________________- 		Configuring the Load Host's Node Database  e  N    This chapter explains how to configure a VMS load host's node database for P    new servers. Configuring this database is part of the software installation. M    After this procedure, your VMS system is established as a valid load host s    for the new servers..  M    To configure the load host's node database for a new server, use the Add  .O    option of DSVCONFIG.COM, an automated, menu-driven procedure. DSVCONFIG.COM FL    prompts you for information about the new server and then configures the J    load host's node database by adding an entry for the new server to the I    DSVCONFIG.DAT file (the server configuration database) and the DECnet eP    databases. You also can configure the load host's node database by restoring N    to the DECnet databases the server entries that exist in the DSVCONFIG.DAT     file.  A    If you ran the installation procedure described in Chapter 2,  L    DSVCONFIG.COM is now in the SYS$SYSROOT:[DECSERVER] directory for single O    systems and in SYS$COMMON:[DECSERVER] for VAXcluster members. The load host  D    creates and maintains all server-related files in this directory.   				Note  8 	DSVCONFIG.COM, which is part of this distribution kit, > 	accommodates the DECserver 100, DECserver 200, and DECserver @ 	500 products. However, some previous releases of DSVCONFIG.COM > 	do not accommodate the DECserver 500 product. Therefore, use 5 	the command file on this kit for all configurations.h i   3.1 Overview of DSVCONFIGQ  J    DSVCONFIG has five configuration options, all of which affect the node I    database on the load host. When you start the DSVCONFIG procedure, it i*    displays the following menu of options:  &      DECserver Configuration Procedure$ 		                     Version: V1.7              Menu of Options      1 - List known DECservers      2 - Add a DECserver R$      3 - Swap an existing DECserver &      4 - Delete an existing DECserver $      5 - Restore existing DECservers$    CTRL/Z - Exit from this procedure  L    To configure your load host's node database for new servers, use the ListM    and Add options.  You may also need to use the Restore option (especially sI    for configuring VAXcluster nodes). This chapter discusses these three tM    options only. The Swap and Delete options are used by the server manager. pH    The Swap option is recommended for use when the server hardware unit G    malfunctions and must be replaced. The Delete option is useful when cK    reconfiguring the network or changing load hosts for a server. Examples  I    showing the use of these options are included in Appendix C. For more EE    information on these options and DSVCONFIG, see the DECserver 200      Management Guide.  I    This chapter first discusses the databases that the DSVCONFIG options e.    affect. Subsequent sections explain how to:  B    o	Specify DECnet characteristics during DSVCONFIG (Section 3.2)  0    o	Prepare for running DSVCONFIG (Section 3.3)    DH    o	Respond to DSVCONFIG and comply with its requirements (Section 3.4)  I    o	Start DSVCONFIG and use the List, Add, and Restore options (Section E 	3.5)y  M    o	Start DSVCONFIG with the RESTORE parameter to restore your local DECnet s 	database (Section 3.6)o  =    o	Configure VAXcluster nodes using DSVCONFIG (Section 3.7)   &    o	Exit from DSVCONFIG (Section 3.8) b  H    See the DECserver 200 Management Guide for a complete description of 
    DSVCONFIG.v  % 3.1.1 Databases Affected by DSVCONFIGo  M    The DSVCONFIG procedure operates on three distinct databases contained in  !    the load host's node database:i  M    1. The server configuration database for servers. This database is stored fP       in the file DSVCONFIG.DAT. It has the information you see when you select .       Option 1, List, from the DSVCONFIG Menu.  +    2. The operational host DECnet database.A  )    3. The permanent host DECnet database.e  P    When you run DSVCONFIG, server information is transferred from the DSVCONFIG D    database to the DECnet database. These two databases must remain     synchronized.  O    The DSVCONFIG procedure automatically keeps these databases synchronized on  I    the load host. Though DSVCONFIG includes several NCP commands, do not YO    execute these commands yourself to configure the load host's node database. :)    NCP affects only the DECnet databases.r  D    On a VAXcluster load host, the DSVCONFIG procedure automatically L    synchronizes the databases on the load host but not on the other members M    of the VAXcluster. Section 3.7 explains how to configure VAXcluster nodes c9    so that the databases are synchronized on all members.   2 3.1.2 DSVCONFIG Options for the Software Installer  I    As a software installer, you use the List, Add, and Restore DSVCONFIG C    options for new servers.S  J    1. List known DECservers - Lists servers that are currently defined in        DSVCONFIG.DAT.  L    2. Add a DECserver - Adds an entry for a new server in DSVCONFIG.DAT and        in the DECnet databases. e  L       Adding an entry supplies information that identifies the server on theM       Ethernet and, thus, establishes this system as a load host for the new  
       server.   G    3. Restore existing DECservers - Restores servers that exist in the  L       DSVCONFIG.DAT file to the load host's DECnet operational database and         DECnet permanent database.  F    This option copies server entries from DSVCONFIG.DAT to the DECnet K    databases. For example, if the load host system is brought down, server :J    entries may not be automatically restored to the DECnet databases when M    the system comes up  again, especially if a central node database is used ]M    with NCP. Because server entries remain intact in the DSVCONFIG.DAT file,  M    you can use the Restore option to copy these server entries to the DECnet  
    databases.a  6 3.2 Specifying DECnet Characteristics During DSVCONFIG  F    Several DECnet characteristics apply to servers. DECnet uses these K    characteristics for down-line loading and up-line dumping. For each new lM    server, you must specify some of the following characteristics; DSVCONFIG  <    supplies the load file and dump file name automatically.   H    _____________________________________________________________________B    DECnet Characteristic      You Specify      	DSVCONFIG SuppliesH    _____________________________________________________________________      DECnet node address	      X      DECnet node name	      Xa    V    Server type		      XP      Service circuit-ID	      X          Ethernet address	      X		n  &    Load file		      	               	X  $    Dump file name		                XH    _____________________________________________________________________    K    The DECserver 200 information that you must specify is recorded on each nN    unit's DECserver 200 Identification Card. Ask the hardware installer or the!    network manager for this card.s e   3.2.1 DECnet Node Name  P    Each DECserver 200 unit must have a unique DECnet node name. This name must  N    have from 1 to 6 alphanumeric characters with at least one character being O    an alphabetic character. For example, DSV5 and LION77 are valid DECnet node N	    names.   F    The network manager assigns DECnet node names. During the hardware L    installation, the hardware installer records the DECnet node name on the 5    DECserver 200 Identification Card for each server.   N    DSVCONFIG does not set up the server name on the server itself. The server K    name, a server characteristic stored in the server's databases, must be EO    defined on the server by the server manager. To avoid confusion, the server O*    name should match the DECnet node name.   3.2.3 DECnet Node Addressl  N    Each DECserver 200 unit has a unique DECnet node address. This number must &    be a decimal number from 1 to 1023.  P    If your DECnet network is divided into areas, each DECnet node address takes M    the form aa.nnnn. Here, aa is a decimal area number from 2 to 63, nnnn is OI    the node address, and the period distinguishes area from address. For d,    example, 17.1003 is a valid node address.  J    The network manager assigns DECnet node addresses. During the hardware O    installation, the hardware installer records the DECnet node address on the _5    DECserver 200 Identification Card for each server.S   3.2.3 Ethernet Address  H    Each DECserver 200 unit is delivered with a unique Ethernet hardware N    address. This address is six pairs of hexadecimal digits with a hyphen (-) M    separating each pair. For example, 08-00-01-00-AB-CD is an address with a c    valid format.  O    The Ethernet address is on the control/indicator panel of the DECserver 200 nN    unit. During the hardware installation, the hardware installer records the E    Ethernet address on each unit's DECserver 200 Identification Card.t n   3.2.4 Server Types  M    The server type that you specify is "DS200," which defines your unit as a r    DECserver 200 server.  # 3.2.5 Load File (Server Image File)e  P    The DECserver 200 load file is the server's software image that is down-line P    loaded by the host to the server. You do not have to supply this information.  <    The name of the DECserver 200 load file is PR0801ENG.SYS.   3.2.6 Dump File Name  M    Each server has a unique dump file name, DS2node-name.DMP. Here, node-name L    is the DECnet node name of the server. For example, a DECserver 200 unit G    with the DECnet node name TIGER has the dump file name DS2TIGER.DMP.   P    You do not have to supply the dump file name. When you use the Add option to P    define a new DECserver 200 unit, DSVCONFIG assigns a name for the dump file. P    See the DECserver 200 Problem Determination Guide for information on up-line O    dumping, the creation of the server's up-line dump file, and for using this Y    file for problem analysis.w   3.2.7 Service Circuiti  J    The service circuit is the Ethernet circuit that the load host uses to K    reach the server when loading and dumping occur. The load host may have lM    more than one active Ethernet circuit, so you have to specify the service  K    circuit-ID to identify which circuit is to be used for loads and dumps. sH    The service circuit-ID is stored in the load host's DECnet databases.  J    DSVCONFIG prepares your node as a load host by enabling SERVICE on the N    service circuit. SERVICE must be enabled before a down-line load can occur. O    H    _____________________________________________________________________+    Service Circuit-ID		Ethernet ControllersLH    _____________________________________________________________________    UNA-n 			DEUNAm      UNA-n 			DELUA  r      QNA-n 			DEQNA       BNA-n *			DEBNT        BNT-n			DEBNT d      SVA-n			DESVA :  ,    Here, n is an integer (typically 0 or 1)..    *  BNA-n replaces BNT-n in VMS Version 5.0.H    _____________________________________________________________________    O    When you run DSVCONFIG to add more than one unit, the procedure asks you to LL    specify the service circuit each time. The first time you are asked, the O    default is the service circuit for the processor type of your VMS load host.eK    If you respond by specifying a different service circuit, that response  O    becomes the default until either you specify another service circuit or you d    exit the procedure.  A    The possible default values for each load host's CPU type are:T  H    _____________________________________________________________________     CPU Type			Service Circuit-IDH    _____________________________________________________________________    VAX-11/780, 782, 785		UNA-0      VAX-11/730,750		UNA-0      VAX 8600, 8650		UNA-0  '    VAX 8200, 8300, 8500,	UNA-0 or BNT-0C    8550, 8700, 8800       MicroVAX II			QNA-0 0      VAXstation II		QNA-0     s    MicroVAX 2000		SVA-0M      VAXstation 2000		SVA-0eH    _____________________________________________________________________  L    If your CPU supports more than one Ethernet controller, you can choose a -    service circuit-ID number other than zero.s o  0 3.3 Preparing to Run the Configuration Procedure  0    Before beginning the configuration procedure:  C    1. Check that DECnet is installed and running. For information  l2       about DECnet, see the VMS documentation set.  F    2. Check that all the distribution software was installed in these        directories:  . 	- SYS$SYSROOT:[DECSERVER] for single systems   ) 	- SYS$COMMON:[DECSERVER] for VAXclustersd  5 	See Appendix A for a list of the distribution files.   I    3. Check that each new server's DECnet node name and node address are  
       unique.b  O       Ask the hardware installer for the DECserver 200 Identification Card for uH       each new DECserver 200 unit. The network manager and the hardware K       installer recorded the server's DECnet node name and node address as  F       well as the Ethernet address on this card. You need to know the N       server's DECnet node name, DECnet node address, and Ethernet address to &       answer prompts during DSVCONFIG.  P       You can check the uniqueness of the server's DECnet node address and node L       name by specifying the address or name with the NCP SHOW NODE command:         $ MCR NCP  <RETURN>  e6       NCP>SHOW NODE node-name CHARACTERISTICS <RETURN>         or  8       NCP>SHOW NODE node-number CHARACTERISTICS <RETURN>  M       If NCP shows a node already defined, see the network manager to resolve        the conflict in names.    * 3.4 DSVCONFIG Conventions and Requirements  M       DSVCONFIG is an interactive procedure. When you start DSVCONFIG, a menurF       of options displays. Within the Add option, you get a series of M       questions. After each question, the default response, if there is one, eN       displays in brackets ([ ]). At the end of each question, either a colon N       (:) or a question mark (?) appears. The following list tells you how to        use DSVCONFIG:  I       o	To select an option, type a menu number and press the RETURN key.   M       o	To answer a question, type your response immediately after the colon e, 	or question mark, and press the RETURN key.  P       o	To respond to a question with the default answer, press only the RETURN  	key.        L       o	To get help after any question, type a question mark (?). After the ( 	help display, the question is repeated.  M       o	To exit an option without making any changes, type <CTRL/Z> . You areg) 	returned to the DSVCONFIG Menu. <CTRL/Z>r  K       o	To exit DSVCONFIG at the menu level, type. You are returned to the f 	DCL prompt.  A       DSVCONFIG has some additional conventions and requirements:h  J       o	When you finish an option, DSVCONFIG automatically returns you to  	the DSVCONFIG Menu.  A       o	At the end of the Add option, you might get NCP messages t@ 	(information, confirmations, and errors). In the case of error A 	messages, the operation might not have been successful. For the h; 	meanings of these messages, see the VMS documentation set.   I       o	To run DSVCONFIG on a particular VMS load host, the distribution m5 	software must already be installed onto that system.w     3.5 Running DSVCONFIGs  J       To run DSVCONFIG.COM, you need OPER and SYSPRV privileges. To start        DSVCONFIG:  J       1. Log in to the system account or any account with OPER and SYSPRV 
 	 privileges.t  &       2. Enter the following commands:  ! 		$ SET DEFAULT MOM$LOAD <RETURN>n 		$ @DSVCONFIG <RETURN>s   				Note  / 		The latter command assumes you have  defined g0 		MOM$LOAD to locate the DECserver 200 software 4 		image in SYS$SYSROOT:[DECSERVER]. See Section 2.4.  *       DSVCONFIG starts with these actions:  G       o	It determines whether the DECnet key is installed. If DECnet iseG 	missing, DSVCONFIG prints a message and exits. You must have DECnet toD 	run this procedure.  A       o	It checks the existence and format of a data file called ,H 	DSVCONFIG.DAT. It finds one of three possible situations and continues 
 	accordingly:o  ; 	- The DSVCONFIG.DAT file does not exist in the directory   5 	  SYS$SYSROOT:[DECSERVER]. The procedure creates the_G 	  DSVCONFIG.DAT file and displays a message telling you that the file  + 	  was not found and a new one was created.r  < 	- SYS$SYSROOT:[DECSERVER] already has this file, formatted G 	  correctly. This is the case if DSVCONFIG was previously used to add rE 	  DECserver 200 entries. The procedure continues with its next task.t n  0 	- SYS$SYSROOT:[DECSERVER] (or for VAXclusters, C 	  SYS$SPECIFIC:[DECSERVER]) already has this file, but not in the M? 	  correct format. The procedure reformats the file. Regarding sE 	  VAXclusters, SYS$SPECIFIC:[DECSERVER] on each VAXcluster node may lB 	  have an older version of the DSVCONFIG.DAT file. The DSVCONFIG D 	  procedure copies the server entries from that data file into the G 	  DSVCONFIG.DAT file on SYS$COMMON:[DECSERVER], a directory shared by aF 	  the VAXcluster nodes. The procedure renames the DSVCONFIG.DAT file H 	  in SYS$SPECIFIC so that the DSVCONFIG.DAT file in SYS$COMMON is used  	  thereafter.  	 					Note   8 		On VAXclusters, DSVCONFIG creates and writes files in < 		the common area, SYS$COMMON:[DECSERVER].  See Section 3.7 ? 		for special i nstructions on running DSVCONFIG for the first a 		time on VAXclusters.  E 	- It informs you that each DECserver unit must have a unique DECnet i% 	  node name and DECnet node address.s  - 	- It asks you either to continue or to exit:o  / 		Press <RET> to start, or <CTRL/Z> to exit... .  F 	  Press the RETURN key if you have the information you need for each  	  new server.         3. DSVCONFIG displays:  0 	              DECserver Configuration Procedure- 			                             Version: V1.7f  ( 	                        Menu of Options- 	                  1 - List known DECservers  ' 	                  2 - Add a DECserver :2 	                  3 - Swap an existing DECserver 4 	                  4 - Delete an existing DECserver 2 	                  5 - Restore existing DECservers0 	             CTRL/Z - Exit from this procedure    		Your selection?e  E 	  Type the number of the option you want. Then press the RETURN key.t o  & 3.5.1 List Known DECservers (Option 1)  L      Select Option 1 to list the DECservers in the DSVCONFIG.DAT data file. M      Type 1 and press the RETURN key. The contents of the DSVCONFIG.DAT file lI      displays in seven columns. Option 1 displays a listing such as this:a  #      DECnet  DECnet Server Service rM      Address Name   Type   Circuit Ethernet Address  Load  File    Dump File aN      ------- ----   ----   ------- ----------------  -----------   -----------N      28.900  BUNNY  DS200  BNT-0  08-00-2B-02-F0-99 PR0801ENG.SYS DS2BUNNY.DMPM      28.1001 BACH   DS200  UNA-0  08-00-2B-02-24-CC PR0801ENG.SYS DS2BACH.DMP O      28.1002 BEETHO DS200  UNA-0  08-00-2B-03-AA-2B PR0801ENG.SYS DS2BEETHO.DMPnO      28.1003 MOZART DS100  UNA-0  08-00-2B-02-24-DD PS0801ENG.SYS PSDMP24DD.SYSoN      28.1005 HAYDN  DS200  UNA-1  08-00-2B-03-AA-F1 PR0801ENG.SYS DS2HAYDN.DMPO      28.1019 OCELOT DS500  UNA-0  08-00-2B-03-EE-FF DS5OCELOT.SYS DS5OCELOT.DMP(O      28.1022 JAGUAR DS500  UNA-0  08-00-2B-03-E1-F1 DS5JAGUAR.SYS DS5JAGUAR.DMPeO      28.1023 BEATLE DS100  UNA-0  08-00-2B-02-24-2D PS0801ENG.SYS PSDMP242D.SYSc  #     Total of 8 DECservers defined. w        (Press RETURN for menu) o    3.5.2 Add a DECserver (Option 2)  B    Select Option 2 to add an entry for a new server in the server L    configuration database (DSVCONFIG.DAT), the DECnet operational database, J    and the DECnet permanent database. To create an entry, you must supply:      o	The DECserver typeC  5    o	A unique DECnet node name for the DECserver units     8    o	A unique DECnet node address for the DECserver unit     /    o	The Ethernet address of the DECserver unitr      o	The service circuit  '    To add a server, follow these steps:h  &    1. Type 2 and press the RETURN key.      2. DSVCONFIG asks:t   	DECserver type?    % 	Type DS200 and press the RETURN key.e        3. DSVCONFIG asks:t   	DECnet node name for unit?o  6       Specify the DECnet node name for the new server.      4. DSVCONFIG asks:    	DECnet node address for unit? a  9       Specify the DECnet node address for the new server.o      5. DSVCONFIG asks:s   	Ethernet address of unit?  5       Specify the Ethernet address of the new server.       6. DSVCONFIG asks:   - 	* DECnet Service Circuit-ID [default-id]?  *   M       Press the RETURN key if the default service circuit is the same as the  G       circuit  that connects the load host to the same Ethernet as the oM       server. If not, specify the service circuit-ID of the desired Ethernet A       controller:.          -	UNA-n	for DEUNA or DELUA         -	QNA-n	for DEQNAd         -	BNA-n*	for DEBNT         -	BNT-n	for DEBNTC         -	SVA-n	for DESVAa  I       Here, n is an integer (typically 0 or 1).  See Section 3.2.7 for a e%       discussion of service circuits.s  1       *  BNA-n replaces BNT-n in VMS Version 5.0.t  J     DSVCONFIG adds the entry for the new server to the databases and sets H     SERVICE ENABLED on the specified service circuit, both of which are $     necessary for down-line loading. p   				Cautionn  @ 	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 6 	not entered in the DECnet databases. To correct this - 	synchronization problem, follow these steps:h  F 	1. Use Option 4 to delete the entry. (See the example in Appendix C, 4 	   or refer to the DECserver 200 Management Guide.)  / 	2. Fix the condition causing the DECnet error.l  @ 	3. Return to Option 2 to add the server again with the correct  	   information.  : 	If you specify a node address that is already defined in E 	DSVCONFIG.DAT, you get a DSVCONFIG error, nothing is added, and the C 	Add option is terminated.  , 3.5.3 Restore Existing DECservers (Option 5)  M     Select Option 5 to restore your system's DECnet databases to include the bN     servers in DSVCONFIG.DAT. The Restore option affects both the operational P     and permanent DECnet databases. It performs NCP SET and NCP DEFINE commands.  N     If your DECnet network contains a large number of nodes, you might store  N     your DECnet database on a central remote node and copy this database upon H     each system startup. However, if many servers exist on the network, L     Digital Equipment Corporation advises against defining these servers in      that central database.  O     If servers are not defined in the central database, you must restore them  eI     whenever you copy your local DECnet database from the central DECnet eN     database. Each time you copy the central DECnet database, use Option 5 to +     restore existing server configurations.   H     Type 5 and press the RETURN key. The following messages confirm the      restoration:  : 	Restoring existing DECservers to host DECnet database... + 	Host DECnet database successfully restoredi    I 3.6 Restoring with the Restore Parameter and from Your Start-Up Procedureo  O     There is another way, which can be automated, to restore your local DECnet n7     database. Run DSVCONFIG with the RESTORE parameter:    		$ @DSVCONFIG RESTORE <RETURN>a  L    Using RESTORE bypasses the menu and lets you include this restoration in J    your system start-up procedures. If you want to restore servers to the K    DECnet database at system startup, edit your system start-up file. Then hA    edit your start-up procedure so that it follows this sequence:r      1. Starts DECnet.  $    2. Defines all DECnet node names.  G    3. Restores servers. Use the following command in the start-up file:r  , 	$ @SYS$SYSROOT:[DECSERVER]DSVCONFIG RESTORE  N    For VAXcluster nodes, a fourth step is sometimes required.  For each node  M    that has a different service circuit-ID from the rest of the nodes on the  8    cluster, add another line to your start-up procedure:  @ 	@SYS$COMMON:[DECSERVER]DSVCONFIG SET_CIRCUIT service-circuit-ID  =    See Section 3.2.7 for a list of valid service circuit-IDs.n  F    The SET_CIRCUIT parameter is similar to the RESTORE parameter, but O    SET_CIRCUIT affects only the DECnet operational, rather than the permanent, rH    database. This parameter ensures the correct definitions for service K    circuit-IDs for each node after a cluster reboot. DSVCONFIG RESTORE and iI    DSVCONFIG SET_CIRCUIT also turn on all the specified service circuits._  # 3.7 Configuring on VAXcluster Nodesf  M    For VAXcluster nodes as load hosts, you must keep up to date each node's  eI    databases. The procedure you should follow depends on whether you are  M    running for the first time the version of DSVCONFIG in your DECserver 200      software distribution kit.  h  * 3.7.1 Running DSVCONFIG for the First Time  G    Older versions of DSVCONFIG place DSVCONFIG.DAT in the SYS$SPECIFIC nO    directory. When you run the version of DSVCONFIG in your DECserver software rM    distribution kit for the first time, follow this procedure to ensure that sK    DSVCONFIG updates the DSVCONFIG.DAT file correctly and places it in the s    SYS$COMMON directory:  H    1. Run DSVCONFIG at one node to add servers. DSVCONFIG looks for the @       original DSVCONFIG.DAT file in the SYS$SPECIFIC directory.  O       After finding an existing DSVCONFIG.DAT file, DSVCONFIG copies the server @       entries from that data file into the DSVCONFIG.DAT file onO       SYS$COMMON:[DECSERVER], ignoring any servers with names already existing eC       in the SYS$COMMON file. The procedure looks at each entry in eJ       SYS$SPECIFIC and determines if that entry is already in SYS$COMMON. K       If the entry is in SYS$COMMON, it is not merged. If the entry is not  "       in SYS$COMMON, it is merged.  O       Then, DSVCONFIG renames the old DSVCONFIG.DAT file on the SYS$SPECIFIC   vK       directory to DSVCONFIG_SPECIFIC.DAT. As a result, you still have the h<       original entries in case you need to repeat the merge.  G    2. At every other node, run DSVCONFIG and select the List option.   rL       DSVCONFIG merges all the existing server entries to the DSVCONFIG.DAT        file in SYS$COMMON.m  K    3. Verify that the merge was successful. The List option should display  N       the correct service circuit-IDs at each node. Since the individual nodesM       have the correct service circuit-ID for each server entry, the correct lK       IDs are merged into the new file. Informational messages display the t+       status of the merge as it progresses.u  @       After you verify that the merge is successful, delete the "       DSVCONFIG_SPECIFIC.DAT file.  P       If the service circuit-IDs are not correct for a particular node, you can M       correct them in one of two ways. You can run DSVCONFIG at the node with M       the errors (use the Swap option to change the service circuit-IDs). Or DK       you can run DSVCONFIG SET_CIRCUIT at that node (for VAXclusters, the r       latter method is better).  l  O       The following example shows the messages DSVCONFIG displays as it merges _       old server entries:    		$ @DSVCONFIG <RETURN>a  O       Merging SYS$SPECIFIC:[DECSERVER]DSVCONFIG into SYS$COMMON:[DECSERVER]DSV-e       CONFIG  F       8 servers were defined in SYS$SPECIFIC:[DECSERVER]DSVCONFIG.DAT D       3 servers were already in SYS$COMMON:[DECSERVER]DSVCONFIG.DAT ?       5 servers merged into SYS$COMMON:[DECSERVER]DSVCONFIG.DATf  L       You must assign a unique DECnet node name and DECnet node address for        each new DECserver unit.  . 	Press <RET> to start, or <CTRL/Z> to exit...   - 3.7.2 Running This Version of DSVCONFIG Again_  M       To establish the system as a load host immediately and make additional _N       configuration changes for servers, run DSVCONFIG at each node and selectN       the appropriate options. Running DSVCONFIG at each node ensures correct L       service circuit-IDs. Use the Restore option at each node. This option K       restores the server's DSVCONFIG.DAT definitions into each node's NCP -       database._  L       You do not have to perform the procedure at each node if you can wait J       for the next reboot of the system before it can act as a load host. M       At reboot, the start-up procedures correct all service circuit-IDs for o       each node.   3.8 Exiting DSVCONFIGt         When you exit DSVCONFIG:  P       1. Give the server manager the DECserver 200 Identification Card for each !          server that you defined.   N       2. Direct the server manager to store the card in the notebook with the 6          documentation set for DECserver 200 software.    3.9 After Exiting from DSVCONFIG  K       After you complete the configuration procedure, verify the load host e@       installation. See Chapter 4 for details of this procedure.   b    A                                                                 4oA      ____________________________________________________________r2                         Verifying the Installation  C     To complete the software installation, you need to perform two tM     verifications. First, you verify the load host installation by down-line DM     loading the server image. Then, after loading the server, you verify the ND     server system installation. Here, system installation means the L     installation of the complete server system - the hardware unit with the I     correct software loaded and running. You verify the server system by eL     testing a few server commands at an interactive terminal, which must be      connected to the server.  ( 4.1 Verifying the Load Host Installation  N     To verify the installation of the load host, use it to down-line load the O     server image to one DECserver 200 unit; then read the DECnet event-logging e:     messages. The messages confirm that the new load host:  8     o Has the appropriate files in the correct directory  =     o Has a correct entry in its node database for the server   D     o Can successfully down-line load the server image to the server  K     Even though there are several ways to down-line load the server image, wK     use the NCP LOAD NODE command to verify the installation, as explained  O     later in this section. This is the only method that tests the installation mN     of the software from a specific load host. The LOAD NODE command lets you O     specify the load host, ensuring that the load host that does the down-line yM     load is your VMS system. (A discussion of all the ways to down-line load f3     appears in the DECserver 200 Management Guide.)     I     You can down-line load the new server image to a new server or to an rO     existing server that is currently operating on the network. Each situation  1     has its own requirements, as explained below..  % 4.1.1 If You Are Loading a New Servero  M     A new server has no operating software in it until the initial down-line mM     load, which occurs automatically upon server start-up. When the hardware  L     installer powers up a unit, the server automatically requests a load of E     its image from any available load host. An established load host s@     recognizes the request and down-line loads the server image.  N     The hardware installer can then verify the hardware installation with the I     appropriate diagnostic lights (LEDs) on the DECserver hardware unit.  M     However, if the server image cannot be properly down-line loaded as soon pL     as the server is powered up, the hardware installer sees server errors. G     Therefore, your coordination with the server hardware installer is tN     important. You should complete the entire software installation procedure 9     before the hardware is powered up for the first time.   M     Note that this automatic down-line load verifies the hardware, but it is O<     not sufficient for verifying the load host installation.  + 4.1.2 If You Are Loading an Existing Servere  L     When an operating server is loaded, all sessions with service nodes are M     disconnected. Therefore, if an existing server is about to be loaded withkI     a new image, your coordination with the server manager is important. sK     Digital Equipment Corporation recommends that you talk with the server VM     manager and the system manager about the needs of their users. It may be  M     best to delay the verification of the installation and to down-line load g     during off-hours.   J     Ask the server manager of an existing server to alert the interactive M     users on the server of the shutdown due to reloading. The server manager rN     should have at least 30 minutes notice to disable connections and queuing E     to local services of the server if necessary. (The DECserver 200  H     Management Guide discusses the issues involved in shutting down the      server.) e    4.1.2.1 Loading During Off-Hours  N     You and the server manager can perform the down-line load during off-hoursN     to be least disruptive to the nodes affected by the server. To do so, you @     can put the LOAD command in a batch job and run it at night.  $ 4.1.2.2 Warning Users Before Loading  K     If you decide to reload an installed and running DECserver unit during ON     normal working hours, either you (if you know the privileged password) or L     the server manager can use the server interface to issue the privileged O     BROADCAST ALL command to warn server users. If you wish, you can broadcast  O     the VERIFYING THE LOAD HOST INSTALLATION warning on a remote console port. cN     See Appendix B for information on using the Remote Console Facility (RCF)      on a VMS system.  M     Issue the BROADCAST ALL command at the server prompt (Local>). BROADCAST  G     ALL sends a message to all the ports. The message can be up to 115 uG     characters in length. Note that the reception of broadcasts can be OI     disabled on ports even when it is enabled on the server. Some users,  M     therefore, may not receive your message. However, the command also lists oO     the ports that did not receive the broadcast message; so you can then warn D2     these users using another method if necessary.  K     The following command warns users at all ports that the server will be       reloaded in three minutes:  N     Local> BROADCAST ALL "The server will be reloaded in 3 minutes." <RETURN>                 o- 4.1.3 Down-Line Loading with the LOAD Commandy  K     Down-line loading the server image for load host verification involves t     three steps:  O     1. Following the steps listed in the next section ("Preparing for the LOAD o     Command").        2. Issuing the LOAD command.  I     3. Reading the event-logging message that reports the down-line load.v S  & 4.1.3.1 Preparing for the LOAD Command  @     Perform the following tasks before issuing the LOAD command:  K     1. Check the DECnet node name or DECnet node address of the server. To  D        execute the LOAD command, you need to know one of these node M        identifiers. If you do not remember this information from running the 0O        DSVCONFIG procedure (see Chapter 3), run the procedure again and select 0O        the List option from the menu. The List option displays the DECnet node 0K        name and DECnet node address of all the servers you defined in this .!        load host's node database.0  J     2. Ask the server manager for the server's DECnet service password if H        there is one (the server manager may know it as the "maintenance O        password"). For a previously configured server, you may need to specify i3        this password on the LOAD NODE command line.   L     3. Enable DECnet event logging. Event-logging messages are generated by ?        the Network Control Program (NCP). Enter these commands:e          $ MCR NCP <RETURN>a4        NCP> SET LOGGING CONSOLE EVENT 0.3,7 <RETURN>1        NCP> SET LOGGING CONSOLE STATE ON <RETURN>o1        NCP> SET LOGGING MONITOR STATE ON <RETURN>   P        DECnet uses the Operator Communication (OPCOM) facility to display event N        messages on the operator's console. Make sure OPCOM is running on your N        host. The DCL SHOW SYSTEM command displays the status of all processes K        on your system. If OPCOM is not running, start it with the followinge        command:C  +        $ @SYS$SYSTEM:STARTUP OPCOM <RETURN>   K     4. If you are reloading an existing server, warn the interactive users  J        with the BROADCAST command. See Section 4.1.2.2 for information on %        issuing the BROADCAST command.I  
 	 			 Note  9 	All the other commands needed for down-line loading are s@ 	part of DSVCONFIG and are executed when you run that procedure > 	(see Chapter 3). In addition, SERVICE must be enabled on the 7 	service circuit, which is also performed by DSVCONFIG.i i    4.1.3.2	Issuing the LOAD Command  N     After warning interactive users of an operating server and after enabling I     event logging, you are ready to load the server. Issue the LOAD NODE LP     command at a terminal connected to your VMS load host. On the command line, O     enter either the DECnet node name or the DECnet node number. The following )J     example loads an existing server named BEETHO, with a node address of      28.1002.       $ MCR NCP <RETURN>"     NCP> LOAD NODE BEETHO <RETURN>       or  #     NCP> LOAD NODE 28.1002 <RETURN>   L     If the server manager previously set a server maintenance password, you L     have to include the SERVICE PASSWORD keywords and specify this password D     as the DECnet service password on the command line, for example:  0     NCP> LOAD NODE BEETHO SERVICE PASSWORD 0F23         To exit from NCP, type EXIT:       NCP> EXIT <RETURN>     $o  " 4.1.3.3 Using DECnet Event Logging  M     After you have executed the LOAD command, check the DECnet event-logging rN     messages that report the load to confirm that it was successful. Read the M     event-logging messages at your system operator's console. These messages tB     identify your VMS system as the node that generated the event.  J     If no errors are reported, you can assume that the down-line load was M     successful. You have finished verifying the new load host. See Appendix CeM     for an example of DECnet event logging after a successful down-line load.v  K     If you do see errors on the event-logging messages, contact the server  N     hardware installer. Check that the hardware is working satisfactorily. If G     it is, the problem is probably with the load host. Check your node  O     database, especially the Ethernet address you entered when you defined the  N     test server. Check that the server image is in the appropriate directory. =     Check that DECnet is running. Try the LOAD command again.e   				Note  8 	When event logging is set up on a DECnet node, you can < 	specify the destination (called the sink) of the messages. < 	Digital Equipment Corporation suggests that you set up one ? 	DECnet sink node to receive all the logging events associated  > 	with down-line loading. In this way, all load request status & 	information is available at one node.  , 4.2 Verifying the Server System Installation  N     To verify the total server system installation, test a few server commandsN     at an interactive terminal connected to a server port. This step confirms 	     that:a  ;     o The correct version of the software is in the server.m  9     o The server hardware operates with the new software.N  /     o The new software is running successfully.R       Follow this sequence:R  .     1.	Press the RETURN key two or more times.  A 	The following message and prompt should appear. The second line rE 	displayed ("Robin's Server") is the server's identification defined   	by the server manager.n  
 	    <RETURN>s
 	    <RETURN>r  : 	    DECserver 200 Terminal Server Vn.n (BLnn) - LAT V5.1  	    Robin's ServerE  , 	    Please type HELP if you need assistance   	    Enter username>   				Note  / 		Be sure that the software version number and S3 		base-level number (BLnn) match those shown here; e/ 		otherwise, you might be running old software.i  N     2.  Read the identification message to ensure that the correct version of D 	the server image was down-line loaded. If you fail to receive this  	display, the problem could be:-   		a. With the load hostf   		b. With the terminal  5 		c. That the incorrect software was down-line loaded   I     3.	Enter your user name (any string of 1 through 16 charfacters that iE 	identifies you) and press the RETURN key. The port should now enter  5 	local mode, where the local prompt (Local>) appears:r   		Enter username> SWINSTALLER   	 		Local> S  I     4.	Use the TEST PORT command, which verifies whether the terminal is iB 	receiving valid character data. On the command line, specify the E 	number of lines and the number of columns you would like displayed. bB 	For example, this command displays 5 lines of 80 characters each:  $ 		Local> TEST PORT COUNT 5 WIDTH 80   G 	Note that you can interrupt this test by pressing any key. Appendix C  ) 	shows an example of a TEST PORT display.e  O     5.	Issue the SHOW PORT command to display the characteristics of your port r 	and their values:   		Local> SHOW PORT I  C 	A port-characteristics display should appear. Appendix C shows an  + 	example of a port-characteristics display.V  L     6.	Use the SHOW SERVICES command to show what services are available to C 	you. The following server command produces a list of services and S 	service announcements:    		Local> SHOW SERVICES f  8 	Appendix C shows an example of a SHOW SERVICES display.  K     7.	Select an available service that you are authorized to use. Use the tF 	CONNECT command to verify that the server can logically connect your D 	terminal to that service. On the command line, specify the service G 	name to which you want to connect. The following example connects yourC( 	terminal to a VMS system, named SYSTEM:   		Local> CONNECT SYSTEM   H 	When the server successfully connects your terminal to the service you @ 	specified, you no longer see the local prompt; rather, you are F 	communicating with the service, in this example, your own VMS system.  N     8.	Enter several commands to verify the ability of the server to exchange C 	data with the service. For example, in this case, you could enter F" 	LOGIN, SHOW TIME, and SHOW USERS.  J     9.	Press the BREAK key or log out from the service to return to local A 	mode. Note that pressing the BREAK key does not end the service s 	session you started.h  -     10. Log out the terminal from the server:-   		Local> LOGOUT   M     If the server system verification encounters any problem, see the server e     manager.  O     If you complete the above steps successfully, the test server is operating eL     correctly, and you can report the successful load host installation and N     server system installation to the server manager. If this installation is M     a software upgrade, either you or the server manager must now reload all       existing servers.n     o      	 								AnA     _____________________________________________________________ # 			DECserver 200 Distribution Filesr  3     These are the DECserver 200 distribution files:e  A     _____________________________________________________________       File Name				DescriptionhA     _____________________________________________________________i5     KITINSTAL.COM			Command file used by VMSINSTAL 		P) 					for part of the installation proce-	:) 					dure. This file is temporary; it is e& 					not left on the system after the  					installation completes.  .     DSVCONFIG.COM	  		Configuration procedure.  '     DSVCONFIG.DAT			Data file used by  $          				DSVCONFIG.COM.A  =     DS2_nnn_ DEFAULTS.COM		Command file used by the Terminal n         				Server Manager.n  /     DS2$IVP.COM 			Command file used for the 		R/         				automated Installation Verification          				Procedure.  (     DS2nnn.RELEASE_NOTES		Release notes.     (nnn=version number)  1     PR0801ENG.SYS			DECserver 200 software image.V  J     TSM$DS2_nnn_ADD_LOCAL_SERVICE.COM	Adds a local service to a designated         				server/port.  G     TSM$DS2_nnn_CTS_RTS_PRINTER.COM	Sets up a printer with CTS/RTS flows          				control.s  J     TSM$DS2_nnn_DEDIC_SERV_PRINTER.COM	Sets up a printer with a dedicated            				service.  H     TSM$DS2_nnn_DEDIC_SERV_TERM.COM	Sets up a terminal with a dedicated          				service.  @     ____________________________________________________________   d  @     ____________________________________________________________     File Name				Description@     ____________________________________________________________D     TSM$DS2_nnn_DIAL_IN_MODEM.COM	Sets up a port for attachment of a         	 			dial-in modem.   H     TSM$DS2_nnn_DIAL_IN_OUT_MODEM.COM	Sets up a dynamic access port for -         				attachment of a dial-in/dial-out f         				modem.  E     TSM$DS2_nnn_DIAL_OUT_MODEM.COM	Sets up a port for attachment of ae         				dial-out modem.i   B     TSM$DS2_nnn_DSR_DTR_TERM.COM	Sets up a printer with DSR/DTR 		         				flow control.		   >     TSM$DS2_nnn_GET_CHAR.COM		Command file of DCL procedures.	  K     TSM$DS2_nnn_HOST_INIT_PRINTER.COM	Sets up a printer and service for it.   9     TSM$DS2_nnn_NON_LAT_HOST.COM	Sets up a non-LAT host.	o  F     TSM$DS2_nnn_PC_TERM_OR_SERV.COM	Sets up a personal computer used 	  					as a terminal and service.	 	r  C     TSM$DS2_nnn_PORT_DEFAULT.COM	Resets port characteristics to de-s 					fault settings.		  F     TSM$DS2_nnn_TERM_SWITCH.COM		Sets up a port for use as a terminal  					switch.		  @     ____________________________________________________________          	 								ByA      ____________________________________________________________h$ 			Using the Remote Console Facility  K     The DECserver 200 unit supports the VMS Remote Console Facility (RCF). iH     This appendix explains how to use RCF from a VMS host. If you issue J     the BROADCAST command yourself to warn users of an upcoming down-line "     load, you may want to use RCF.  L     To connect to the server with RCF, use the CONNECT NODE command. On the M     command line, specify either the DECnet node name or DECnet node address dN     of the server. This example shows a connection to the server named BEETHO:   	$ MCR NCP l 	NCP> CONNECT NODE BEETHO 2     Console connected (press CTRL/D when finished)       or  2 	NCP> CONNECT NODE 28.1002 SERVICE PASSWORD 0F23  2     Console connected (press CTRL/D when finished)  N     Press the RETURN key to start the log-in sequence for the remote console. K     Log-in password protection is enabled for the the DECserver 200 remote  J     console port. Therefore, you must supply the log-in password when the N     server prompts you with a pound sign (#), as shown below (an audible beep C     signal accompanies the prompt). The default password is ACCESS.s       #t  N     The prompt indicates that the link to the server has been made. After you K     enter the correct password, you can begin using DECserver 200 commands.   M     You can also use the CONNECT command with the server's Ethernet address. dP     The following example shows a connection from a VMS system with the service M     circuit-ID UNA-0 to a server with the Ethernet address 08-00-2B-04-AA-2B:g  :     NCP> CONNECT VIA UNA-0 PHYSICAL ADD 08-00-2B-04-AA-2B   O     You may have to specify the service password with the CONNECT command if a iK     maintenance password is specified on the server. To do so, include the  L     SERVICE PASSWORD keywords on your command line and specify the password.  #     To exit from RCF, type: CTRL/D:l   	Local>  CTRL/D <RETURN>        To exit from NCP, type EXIT:       NCP> EXIT <RETURN>         $   "                               Note  . 	If you log out from the server with a LOGOUT 0 	command, the port is logged out but the remote 2 	console session remains active. Type to exit the  	remote console session.  N     The service node prompt reappears, and control passes back to NCP on your D     VMS system. See the DECserver 200 Management Guide for detailed      information on RCF.g   e  	 								CnA      ____________________________________________________________ =           Examples: Installation, Configuration, Verificationo  K     This appendix shows examples of the installation and the configuration  N     procedures. It also shows the verification of a load host installation by J     down-line loading and reading DECnet event-logging messages. Finally, I     Appendix C shows the verification of a server system installation by t     testing server commands.   C.1 Example of an Installation  N     The following example shows a successful installation procedure onto a VMSK     V5.0 system. (In this example, server software version numbers are not aN     supplied.) This example assumes a type of distribution media that requiresJ     only one medium, for example, a magnetic tape. For types such as TU58 N     cartridges, which require more than one volume, additional prompts during ?     the procedure instruct you to mount the additional volumes.m  K     This example also shows the procedure as Digital Equipment Corporation f     suggests you run it:  4     1.	Use the option that prints the release notes.       2.	Print the release notes.n  '     3.	Stop the procedure to read them.d       4.	Rerun the procedure.n  $ 		$ SET DEFAULT SYS$UPDATE <RETURN> + 		$ @VMSINSTAL DS2 MTA2 OPTIONS N <RETURN> r 	l> 	         VAX/VMS Software Product Installation Procedure V5.0  ! 	    It is 17-JAN-1989 at 14:08.  4 	    Enter a question mark (?) at any time for help.  A 	    %VMSINSTAL-W-DECNET, Your DECnet network is up and running. w7 	    * Do you want to continue anyway [NO]? Y <RETURN> rD 	    * Are you satisfied with the backup of your system disk [YES]?  	      <RETURN>  u8 	    Please mount the first volume of the set on MTA2:. ! 	    * Are you ready? Y <RETURN> g, 	    %MOUNT-I-MOUNTED, DS2 mounted on MTA2:   . 	    The following products will be processed:  
 	    DS2 Vn.nt  . 		 Beginning installation of DS2 Vn.n at 14:08  9 	    %VMSINSTAL-I-RESTORE, Restoring product saveset A...r   	    Release Notes Options:h  # 	        1.  Display Release Notes h! 	        2.  Print Release Notes s 	        3.  Both 1 and 2D+ 	        4.  Copy Release Notes to SYS$HELPe9 	        5.  Do not display, print, Or copy Release Notess  (         * Select option [3]: 2 <RETURN> +         * Queue name [SYS$PRINT]: <RETURN> hI         Job DS2nnn.RELEASE NOTES (queue SYS$PRINT, entry 314) started on   	SYS$PRINT d: 	* Do you want to continue the installation [N]? <RETURN>   " 	VMSINSTAL procedure done at 14:09  	         $   0     Read the release notes. Run VMSINSTAL again:    	$ @VMSINSTAL DS2 Mua0 <RETURN>     C 	              VAX/VMS Software Product Installation Procedure V5.1a  ! 	    It is 14-MAR-1989 at 14:07. e4 	    Enter a question mark (?) at any time for help.  A 	    %VMSINSTAL-W-DECNET, Your DECnet network is up and running. t9 	    * Do you want to continue anyway [NO]? yes <RETURN> CD 	    * Are you satisfied with the backup of your system disk [YES]?  	      <RETURN> 8 	    Please mount the first volume of the set on MUA0:. # 	    * Are you ready? yes <RETURN> e- 	    %MOUNT-I-MOUNTED, DS2 mounted on _MUA0:    ,    The following products will be processed:  
 	    DS2 Vn.n   8 	            Beginning installation of DS2 Vn.n at 14:09    ;       %VMSINSTAL-I-RESTORE, Restoring product saveset A... hE        %VMSINSTAL-I-RELMOVED, The product's release notes have been  e%       successfully moved to SYS$HELP.o@       * Do you want to run the IVP after the installation [YES]?:       %VMSINSTAL-I-RESTORE, Restoring product saveset B...  G       Your installation is now complete. After exiting from VMSINSTAL:    H       1.  Edit your system start-up file so that it defines the logical E           MOM$LOAD as a search string with a value equal to itself,  sF           plus the added element SYS$SYSROOT:[DECSERVER]. For example:  =           DEFINE/SYSTEM/EXEC/NAME ATTRIBUTE=NO_ALIAS/NOLOG - NB           MOM$LOAD 'current-search-string',SYS$SYSROOT:[DECSERVER]  H           If the current search string associated with MOM$LOAD in your C           start-up file is SYS$SYSROOT:[DECSERVER] or if you have  nG           already made this change for a previous installation, there  s'           is no need to edit this file..  F           This command ensures that the location of the server image  F           is defined each time the system is rebooted, necessary for  '           successful down-line loading.c  ;       2.  Configure the server into your host's database.  1B           Execute a command procedure called DSVCONFIG.COM. This  I           command procedure is in the SYS$SYSROOT:[DECSERVER] directory. pD           If you have already executed this procedure from previous J           installations, you need to configure only any additional units. @           All previously defined units will still be configured.  M       3.  The Installation Verification Procedure (IVP) for the DECserver 200tG 	  can be found in SYS$TEST and may be run at any time by executing thet$           command procedure DS2$IVP.  F       %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target        directoriesn  K       Beginning installation verification procedure for DECserver 200 Vn.n.e  <       Successfully located SYS$SYSROOT:[DECSERVER] directory  G       Successfully located SYS$SYSROOT:[DECSERVER]DS2nnn.RELEASE_NOTES >  ?       Successfully located SYS$SYSROOT:[DECSERVER]PR0801ENG.SYSy  ?       Successfully located SYS$SYSROOT:[DECSERVER]DSVCONFIG.COME  @       Successfully located SYS$SYSROOT:[DECSERVER]DSVCONFIG.DAT   F       Successfully located SYS$SYSROOT:[DECSERVER]DS2_nnn_DEFAULTS.COM  H       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_ADD_LOCAL_       SERVICE.COM   F       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_CTS_RTS_       PRINTER.COM   I       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DEDIC_SERV_t       PRINTER.COM   J       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DEDIC_SERV_        TERM.COM  F       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DIAL_IN_       MODEM.COMr  J       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DIAL_IN_OUT_       MODEM.COMn  G       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DIAL_OUT_g       MODEM.COMe  F       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_DSR_DTR_       TERM.COM  J       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_GET_CHAR.COM       H       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_HOST_INIT_       PRINTER.COMe  F       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_NON_LAT_       HOST.COM  F       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_PC_TERM_       OR_SERV.COM   C       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_PORT_u       DEFAULT.COM   C       Successfully located SYS$SYSROOT:[DECSERVER]TSM$DS2_nnn_TERM_        SWITCH.COM  M       Depending on your system, VMSINSTAL might let you make an entry in the l4       Software History log. The procedure concludes:  4                    VMSINSTAL procedure done at 14:28         $o   C.2 Example of a Configuration  3       This section gives examples of the following:r         o	Starting DSVCONFIG  1       o	Listing known terminal servers (Option 1)n  +       o	Adding a terminal server (Option 2)   L       o	Swapping an old terminal server for a new terminal server (Option 3)  ?       o	Deleting a terminal server from the database (Option 4)   F       o	Restoring existing terminal servers to the database (Option 5)   C.2.1 Starting DSVCONFIG.COM  E       The following example shows the beginning of the configuration nK       procedure. This example assumes that the latest version of DSVCONFIG dH       has already been run so that the DSVCONFIG.DAT file exists in the K       correct format. (See Chapter 3 for the prompts that are displayed if  G       the procedure has to either create DSVCONFIG.DAT or reformat it.)	  &       $ SET DEFAULT MOM$LOAD <RETURN>        $ @DSVCONFIG <RETURN>   I       You must assign a unique DECnet node name and DECnet node address   5       for each DECserver you are going to configure. o  ?       Press <RETURN> to start, or <CTRL/Z> to exit... <RETURN> n  /               DECserver Configuration Procedureh 						Version: Vn.n     *                            Menu of Options  .                      1 - List known DECservers(                      2 - Add a DECserver3                      3 - Swap an existing DECservere5                      4 - Delete an existing DECservern4                      5 - Restore existing DECservers3                 CTRL/Z - Exit from this procedure  o  +       Your selection?                      c  / C.2.2	Listing Known Terminal Servers (Option 1)l  O       This section and the following ones show how the configuration procedure eN       continues for each option. With the exception of List, each option ends 1       by automatically returning you to the menu.C  !       Your selection? 1 <RETURN> n  !    DECnet  DECnet Server Service kL    Address Name   Type   Circuit  Ethernet Address   Load File     Dump FileO    ------- ------ ------ ------  ----------------- ------------- ------------- lM    28.1001 BACH   DS200  UNA-0   08-00-2B-02-24-CC PR0801ENG.SYS DS2BACH.DMP AN    28.1003 MOZART DS100  UNA-0   08-00-2B-02-24-DD PS0801ENG.SYS PSDMP24DD.SYSM    28.1005 HAYDN  DS200  UNA-1   08-00-2B-03-AA-F1 PR0801ENG.SYS DS2HAYDN.DMPo  $       Total of 3 DECservers defined.  ) C.2.3	Adding a Terminal Server (Option 2)   <     This example adds a new DECserver 200 unit named BEETHO.  #         Your selection? 2 <RETURN> n  5         Type a ? at any time for help on a question. eG 	Type CTRL/Z for any question to return to the menu without adding the   	unit.  ! 	DECserver type? DS200  <RETURN> i- 	DECnet node name for unit? BEETHO <RETURN>  n1 	DECnet node address for unit? 28.1002  <RETURN>  6 	Ethernet address of unit? 08-00-2B-03-AA-2B <RETURN> - 	DECnet Service Circuit-ID? [UNA-0] <RETURN> o  J     If you get an error message now, the new unit won't be added, and you (     should delete it from the directory.  P     If you use the List option to get a listing of servers, you see that BEETHO '     appears on the listing of entries. e  4 C.2.4	Swapping an Old Unit for a New Unit (Option 3)  L     In this example, an existing DECserver 100 unit named MOZART is swapped L     for a new DECserver 200 unit, which is given the same DECnet node name. L     The DECnet node address always stays the same with Swap. The new server M     also has the same service circuit-ID as the old server. (If you use Swap tN     to change the characteristics of the same server, you have to specify the 5     Ethernet address even though it will not change.)y  #         Your selection? 3 <RETURN> o  1     Type a ? at any time for help on a question. iL     Type CTRL/Z for any question to return to the menu without changing the 	     unit.i  ;     What is the DECnet node name you want to swap? MOZART  rF     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.e  ) 	DECserver type? [DS100] DS200  <RETURN> u0 	DECnet node name for unit? [MOZART]   <RETURN> 7 	Ethernet address of unit? 08-00-2B-03-AA-AB  <RETURN> i. 	DECnet Service Circuit-ID? [UNA-0]  <RETURN>   = C.2.5 Deleting a Terminal Server from the Database (Option 4)   N     This example shows the deletion from the load host's node database of the 3     existing server with the DECnet node name BACH.f   	Your selection? 4 <RETURN>   *         (Press CTRL/Z to return to menu.) C 	Enter the DECnet node name of the server you want to delete? BACH D 	<RETURN>  A  , 	%NCP-I-NMLRSP, listener response - Success  	Remote node = 28.1001 (BACH) 0         %NCP-I-RECDELET, Database entry deleted   N     If you use the List option to get a listing of servers, you see that BACH      no longer appears. R  D C.2.6	Restoring Existing Terminal Servers to the Database (Option 5)  L     This example shows the restoration of the local down-line load database.   	Your selection? 5 <RETURN>   : 	Restoring existing DECservers to host DECnet database... , 	Host DECnet database successfully restored.  ? C.3	Example of Verification: Verifying a Load Host Installation   K     The following example, presented in five parts, shows the installation _I     verification for a VMS load host. This procedure tests that your VMS  N     system can perform successfully as a down-line load host for a particular      server._  N     In this example, the VMS system is named SYSTEM. The server that is loadedG     is a DECserver 200 unit with DECnet node name BEETHO. BEETHO is an nM     existing server currently operating on the network. This example assumes dN     that the down-line load is performed during normal working hours and that I     server users are warned of the upcoming down-line load by way of RCF.   ( C.3.1	Using RCF and Warning Server Users  C     This example uses the server's default log-in password, ACCESS.n  9     $ MCR NCP CONNECT NODE BEETHO SERVICE PASSWORD FF23   3     Console connected (press CTRL/D when finished) 	     <RETURN> 	$     # ACCESS  <RETURN> (not echoed) 8     DECserver 200 Terminal Server V3.0 (BL33) - LAT V5.1  +     Please type HELP if you need assistancen  *     Enter username> SWINSTALLER  <RETURN>   "     Local>SET PRIVILEGED <RETURN> .     Password> password (not echoed)  <RETURN> N     Local> BROADCAST ALL "The server will be reloaded in 3 minutes." <RETURN>      Local> <CTRL/D>      $   = C.3.2	Enabling DECnet Event Logging and Checking Server Namesc  3     NCP> SET LOGGING CONSOLE EVENT 0.3,7  <RETURN> _0     NCP> SET LOGGING CONSOLE STATE ON  <RETURN> 0     NCP> SET LOGGING MONITOR STATE ON  <RETURN>      NCP> EXIT <RETURN> m  $     $ SET DEFAULT MOM$LOAD <RETURN>      $ @DSVCONFIG <RETURN>   G     You must assign a unique DECnet node name and DECnet node address   3     for each DECserver you are going to configure. m  =     Press <RETURN> to start, or <CTRL/Z> to exit... <RETURN> o    3                   DECserver Configuration Proceduret 				Version: Vn.nE  *                            Menu of Options/                      1 - List known DECservers a)                      2 - Add a DECserver h4                      3 - Swap an existing DECserver 6                      4 - Delete an existing DECserver 5                      5 - Restore existing DECservers C2                 CTRL/Z - Exit from this procedure        Your selection? 1 <RETURN>  "     DECnet  DECnet Server Service K     Address Name   Type   Circuit Ethernet Address  Load File     Dump FileiO     ------- ------ ------ ------- ----------------- ------------- -------------uO     28.1002 BEETHO DS200  UNA-0   08-00-2B-03-AA-2B PR0801ENG.SYS DS2BEETHO.DMPi  "     Total of 1 DECserver defined.     3                   DECserver Configuration Procedureo 				Version: Vn.n     *                            Menu of Options/                      1 - List known DECservers  )                      2 - Add a DECserver E4                      3 - Swap an existing DECserver 6                      4 - Delete an existing DECserver 4                      5 - Restore existing DECservers2                 CTRL/Z - Exit from this procedure        Your selection? <CTRL/Z>       $4  - C.3.3	Down-Line Loading with the LOAD CommandD  2 	$ MCR NCP LOAD NODE BEETHO PASSWORD FF23 <RETURN>  5 C.3.4	DECnet Event-Logging Display After Issuing LOADa  6 	NCP> LOAD NODE BEETHO SERVICE PASSWORD FF23  <RETURN>* 	DECnet event 0.3, automatic line service 3 	From node 4.205 (SYSTEM), 18-JAN-1989 01:35:20.47  9 	Circuit UNA-0, Load, Requested, Node = 28.1002 (BEETHO) >@ 	File = MOM$LOAD:PR0801ENG, Operating system Ethernet address =  	08-00-2B-03-AA-2B    * 	DECnet event 0.3, automatic line service 4 	From node 4.205 (SYSTEM), 18-JAN-1989 01:43:21.14  : 	Circuit UNA-0, Load, Successful, Node = 28.1002 (BEETHO) @ 	File = MOM$LOAD:PR0801ENG, Operating system Ethernet address =  	08-00-2B-04-AA-2B  " C.3.5 Checking the Service Circuit  E 	This part is optional, and is presented in case the service circuit  A 	becomes disabled. Type the following command to verify that the _$ 	service circuit, BNA-0, is enabled:  , 	NCP>SHOW CIR BNA-0 CHARACTERISTICS <RETURN>  ; 	Circuit Volatile Characterisitics as of 17-Jun-89 08:23:45    	Circuit = BNA-0   	State                      =ont% 	Service                    =disabledh, 	Designated router          = 4.378 (LKGRT3) 	Cost                       =4 	Router priority            =64C 	Hello timer                =15e% 	Type                       =Ethernet , 	Adjacent node              = 4.378 (LKGRT3) 	Listen timer               =90   I     If the state is disabled, first check that the system is not busy by i!     typing the following command:n   	NCP>SHOW KNOWN LINKS  <RETURN>i  8     Known Link Volatile Summary as of 17-Jun-89 08:25:23  I      Link     Node            PID    Process     Remote Link  Remote User   B     33848  2.119 (DSSDEV)  24203120  MCGREGOR          34655  MAILC     8615   3.264 (RITA)    2420372C  POOR                309  CTERMmI     34154  4.10  (SMAUG)   24203F2B  MAIL_34154        33388  DECNET_MAILo       NCP>  O     The example shows that there are three users. If you enable the circuit at  O     this time, you will disable the current users. If the circuit is not busy,  E     type the following commands to enable the service circuit, BNA-0.V  % 	NCP>SET CIR BNA-0 STATE OFF <RETURN>l4 	NCP>SET CIR BNA-0 SERVICE ENABLED STATE ON <RETURN>     9 C.3.6 Conclusion of a Load Host Installation Verificatione  0 	NCP> CLEAR LOGGING CONSOLE EVENT 0.3,7 <RETURN> 	NCP> EXIT <RETURN>C 	$  E C.4 Example of Verification: Verifying the Server System Installation   N     This example shows the verification of a server system installation. This N     procedure tests the hardware, the correctness of the software version, and8     the ability of the new software to run successfully.  L     It assumes that you are at a terminal connected to the server's Port 1, K     that your user name is SWINSTALLER, that your user password is SQUIDS, AH     that you will test the server by connecting to your own VMS system, C     SYSTEM, and that the new DECserver 200 software is Version 3.0.e  	 	<RETURN> 	 	<RETURN>t5 	DECserver 200 Terminal Server V3.0 (BL33) - LAT V5.1e  ( 	Please type HELP if you need assistance  % 	Enter username> SWINSTALLER <RETURN>o  , 	Local> TEST PORT COUNT 5 WIDTH 65  <RETURN>  B 	!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^ ` C 	!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^ `a iC 	"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^ `ab  C 	#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^ `abc MB 	$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^ `abcd   	Local> SHOW PORT <RETURN>  I     The display at the port of a new DECserver 200 unit should match the nI     following example, which contains the factory-set values, except for  "     the port number and user name:       Port 1: SWINSTALLER   :     Character Size:        8      Input Speed:        9600:     Flow control:        XON      Output Speed:       9600:     Parity:             None      Modem Control:  Disabled  :     Access:            Local      Local Switch:       None<     Backward Switch:    None      Name:             PORT 1  :     Break:             Local      Session Limit:         4:     Forward Switch:     None      Type:               Soft       Preferred Service: NoneV       Authorized Groups:   0     (Current)  Groups:   0       Enabled Characteristics:  M     Autobaud, Autoprompt, Broadcast, Input Flow Control, Loss Notification,  R4     Message Codes, Output Flow Control, Verification    -     Local> SHOW SERVICES ALL SUMMARY <RETURN>I  3     Service Name        Status       Identification 3     -----------         ------       --------------   G     DEVELOP           2 Connected    Hardware Timesharing Service Idente>     DOCUMENT            Available    Documentation Timesharing-     TEST                Unavailable  As usual @     TIMESHARING	        Unknown      Server Software Development1     SYSTEM              Available    VAX/VMS 8600    	Local> CONNECT SYSTEM <RETURN>t5 	Local -010- Session 1 to SYSTEM established <RETURN>n    ?              SYSTEM -- VAX 8600, The Best for Down-line Loadingr      	Username: SWINSTALLER  <RETURN>( 	Password: SQUIDS  (not echoed) <RETURN>    5 		    Welcome to VAX/VMS version V5.0 on node SYSTEM n< 	    Last interactive login on Wednesday, 17-JAN-1989 07:25 E             Last non-interactive login on Thursday, 27-DEC-1988 17:18   1 	SYS$MANAGER:NOTICE.TXT -- SYSTEM System Notices  D 	-------------------------------------------------------------------D 	-------------------------------------------------------------------    0 	18-Jan-1989 All users, please purge your files!       		$ SHOW TIME  <RETURN>n 		  18-JAN-1989 07:00:09 		$ SHOW USERS <RETURN>r  ?              VAX/VMS Interactive Users 18-JAN-1989 07:00:13.13 n/         Total number of interactive users =   4E  6     Username     Process Name      PID        TerminalE     ----------------------------------------------------------------- E     DAISY        DAISY           20A0257A     VTA3341        LTA3341: E     HEATHER      HEATHER         20A02217     VTA3391        LTA3391: I     IVY          IVY             20A020D2     VTA3234        DisconnectedEE     ROSE         ROSE            20A02321     VTA3471        LTA3471:nE     SWINSTALLER  SWINSTALLER     20A02001     VTA3471        LTA3511:R   	$ LOGOUT <RETURN>5 	  SWINSTALLER logged out at 18-JAN-1989 07:00:20.98 O/ 	Local -011- Session 1 disconnected from SYSTEMS   	 Local> LOGOUT <RETURN> 	Local -020- Logged out port 1 T   S    	 								DE; 	        __________________________________________________E$ 		         		How to Report a Problem  N     If you discover a problem with the operation of the DECserver 200 terminalI     server software, check to see if the problem is already known before $K     submitting an SPR. If it is, workarounds or corrections may already be SH     available, which will minimize any disruption caused by the problem.  J     To check this, perform the troubleshooting procedures outlined in the K     DECserver 200 Problem Determination Guide and verify the source of the  N     problem. Also, read Sections 5 and 6 of the Release Notes, which describe 6     known restrictions and problems with this release.  I     If the software is still under warranty, or if you purchased Digital sK     Equipment Corporation support services, call the telephone hot line to  J     report your problem. They may be able to provide you with information 5     and workarounds to solve the problem immediately.E   D.1 Submitting an SPRA  N     When completing a Software Performance Report (SPR), describe one problem P     at a time. This simplifies record keeping and facilitates a quick response. K     Keep the description simple yet accurate. Illustrate a general problem SL     with several examples. If a FATAL BUGCHECK error occurs, message number K     nnnnn, submit a crash dump. See Chapter 8 of the DECserver 200 Problem o)     Determination Guide for more details.   M     Because problems are often difficult to reproduce with different system  iO     configurations, please include as much detail as possible when reporting a iO     problem. Define as precisely as possible the state of your system when the iK     problem occurred, and indicate the sequence of events or commands that oI     caused the problem. Attempt to reproduce the situation, if it can be o2     reproduced, using the minimum number of steps.  P     If one of your user programs causes a problem in the DECserver 200 terminal F     server, and you are unable to send the program to Digital, try to L     reproduce the problem with a standard utility. If this is not possible, K     try to describe the program's operation before and after the suspected       failure.  J     When an SPR contains concise information about a problem, we are more J     likely to be able to reproduce and correct the problem. Please ensure L     that any questions are direct and simply stated so they can be answered      clearly and directly.   $ D.2 Reporting Documentation Problems  O     When describing a problem found in a manual, specify the full title of the >P     manual and identify the appropriate section, figure, table, or page number. I     Describe what the manual says and also describe any of the suggested  K     corrections. You can use the Reader's Comments Card in the back of the rO     manual. If you are reporting an error with on-line HELP, identify the full D?     command and screen, and specify TUTORIAL or REFERENCE HELP.i   D.3 Handling Severe Errors  J     Severe errors may cause your DECserver 200 terminal server to hang or H     bugcheck. Server hangs are usually recovered after 20 seconds by an I     automatic power fail, followed by a down-line load. If this sequence  L     occurs, please describe as best you can the operating conditions on the #     server at the time of the hang.t  N     If a FATAL BUGCHECK occurs, a bugcheck message (message nnnnn) is printed L     out on the console terminal, showing the vital registers at the time of K     the bugcheck. Normally, an up-line crash dump is automatically created -!     upon a fatal bug check error.   K     For other types of problems a crash dump is also an extremely valuable  O     tool: if you experience a problem that is not easily reproducible, a crash UF     dump normally allows Digital to fix the problem even if it is not A     reproducible. You can force a crash by typing `CRASH' at the  K     Local>prompt in privileged local mode. A code 300 fatal bug check will r     occur immediately.  E     The location of the crash dump file may be determined as follows:f  O     1.	After the server reinitializes, enter privileged local mode and issue a pG 	SHOW SERVER STATUS command. Information in this display indicates the CH 	Ethernet address of the dump host. You can identify the dump host from  	this address.  O     2.	The crash dump will be located in the directory SYS_$COMMON:[DECSERVER] rB 	on the dump host, and the file name will be DS2xxxxxx.DMP. Here, H 	xxxxxx is the DECnet node name assigned to the server unit, as defined - 	using the DSVCONFIG configuration procedure.e  H 	For example, if the DECserver 200 with node name LAT041 bugchecks, the G 	crash dump will be found in SYS_$COMMON:[DECSERVER]- DS2LAT041.DMP on   	the dump host.   N     Copy the crash dump file to magtape (preferred), RX50, TK50, RX01 or TU58 P     media. Indicate on a label the format of the copy (COPY, BACKUP, FLX, etc.).  L     All media sent to Digital Equipment Corporation will be returned to the      sender.h  