                 H                     DECnet-Plus_for_OpenVMS_____________________________8                     Installation and Basic Configuration  -                     Order Number: AA-QPSUB-TE     !                     November 1996   G                     This book explains how to install and configure the G                     DECnet-Plus for OpenVMS software and how to perform /                     the postinstallation steps.               C                     Revision/Update Information:  This is a revised 9                                                   manual.   G                     Operating Systems:            OpenVMS Alpha Version 5                                                   7.1 I                                                   OpenVMS VAX Version 7.1   I                     Software Versions:            DECnet-Plus for OpenVMS =                                                   Version 7.1 H                                                   X.25 for OpenVMS Alpha=                                                   Version 7.1                         1                     Digital Equipment Corporation *                     Maynard, Massachusetts                 N               ________________________________________________________________               November 1996   D               Digital Equipment Corporation makes no representationsE               that the use of its products in the manner described in F               this publication will not infringe on existing or futureF               patent rights, nor do the descriptions contained in thisF               publication imply the granting of licenses to make, use,B               or sell equipment or software in accordance with the               description.  F               Possession, use, or copying of the software described inE               this publication is authorized only pursuant to a valid H               written license from Digital or an authorized sublicensor.  F               Digital conducts its business in a manner that conservesG               the environment and protects the safety and health of its 6               employees, customers, and the community.  H                Digital Equipment Corporation 1996. All rights reserved.  ?               The following are trademarks of Digital Equipment E               Corporation: Bookreader, DDCMP, DEC, DECdirect, DECnet, @               DECNIS, DECserver, DECsystem, DECwindows, Digital,C               DNA, InfoServer, OpenVMS, PATHWORKS, ULTRIX, VAX, VAX D               DOCUMENT, VAXcluster, VAXstation, VMS, VMScluster, and               the DIGITAL logo.   7               The following are third party trademarks:   I               Macintosh is a registered trademark of Apple Computer, Inc. H               MS-DOS is a registered trademark of Microsoft Corporation.=               Multinet is a registered trademark of TGV, Inc. F               OS/2 is a registered trademark of International Business#               Machines Corporation. >               OSF/1 is a registered trademark of Open Software               Foundation, Inc.I               PATHways is a registered trademark of The Wollongong Group. ?               SCO is a trademark of Santa Cruz Operations, Inc. C               TCPware is a registered trademark of Process Software                Corporation.E               UNIX is a registered trademark in the United States and F               other countries, licensed exclusively by X/Open Co. Ltd.  D               All other trademarks and registered trademarks are the3               property of their respective holders.                                  F      _________________________________________________________________  F                                                               Contents      F      Preface...................................................    vii  1      Part I  DECnet-Plus for OpenVMS Installation     4      1  Preparing to Install DECnet-Plus for OpenVMS  5            1.1   The POLYCENTER Software Installation F                  Utility.......................................    1-1F            1.2   Inspecting the Distribution Kit...............    1-13            1.3   Time Required for Installation and F                  Configuration.................................    1-3F            1.4   Prerequisite Software and Licenses............    1-3F            1.4.1     Software and Licenses.....................    1-37            1.4.1.1     DECnet and OSI Applications over F                        TCP/IP..................................    1-4F            1.4.2     Checking Licenses.........................    1-5F            1.5   System Requirements...........................    1-5F            1.5.1     Disk Space................................    1-5F            1.5.2     Required Memory...........................    1-7F            1.5.3     Required System Parameters................    1-7<            1.5.3.1     SYSGEN Parameters for OpenVMS ClusterF                        Members.................................    1-8F            1.6   Privileges and Rights Identifiers.............    1-8F            1.7   Backing Up the System Disk....................    1-9F            1.8   Notifying Users...............................    1-9                F                                                                    iii                   !         2  Pre-Installation Tasks   8               2.1   Information Required to Complete theI                     Installation Planning Checklist...............    2-1 I               2.2   Installation Planning Checklist...............    2-1   -         3  Installing DECnet-Plus for OpenVMS   I               3.1   Recommended Order for Installing Software.....    3-3 =               3.1.1     Installing DECnet-Plus for an OpenVMS I                         Alpha System..............................    3-3 I               3.1.2     Installing DECnet-Plus for a VAX System...    3-6 ?               3.2   Installing DECnet-Plus Using the POLYCENTER I                     Software Installation Utility.................    3-8 <               3.2.1     Sample DECnet-Plus for OpenVMS AlphaI                         Installation .............................    3-8 :               3.2.2     Sample DECnet-Plus for OpenVMS VAXI                         Installation..............................    3-9 I               3.3   Files Installed on Your System................   3-11   <         Part II  DECnet-Plus for OpenVMS BASIC Configuration            4  Configuration Options  I               4.1   Selecting a Configuration Option..............    4-2 I               4.2   How to Run NET$CONFIGURE .....................    4-4 I               4.2.1     Local and Global Symbols..................    4-5 <               4.2.2     Running the Procedure from DifferentI                         Processes.................................    4-6   .         5  Using the FAST Configuration Option  I               5.1   Invoking the FAST Configuration Option........    5-1 9               5.2   Changing a Current DECnet-Plus System I                     Configuration.................................    5-6                     
         iv                   /         6  Using the BASIC Configuration Option   I               6.1   Invoking the BASIC Configuration Option.......    6-1 I               6.2   Directory Name Services.......................    6-2 I               6.2.1     Node Full Name............................    6-3 I               6.2.2     Specifying the Node Type..................    6-5 I               6.2.3     Specifying Routing Information............    6-5 I               6.2.4     Node Synonym..............................    6-6 ?               6.2.5     Specifying a DECnet Phase IV-Compatible I                         Address...................................    6-6 I               6.2.6     Specifying a Phase IV Prefix..............    6-7 I               6.2.7     Configuring Network Addresses.............    6-7 I               6.2.8     DNA Address Format........................    6-7 I               6.3   Configuring Devices...........................    6-7 I               6.3.1     Configuring an Alpha System ..............    6-8 I               6.3.2     Configuring a VAX System..................    6-9 I               6.4   Configuring Transports........................   6-11 I               6.5   Configuring Time Zone Differential Factors....   6-11 I               6.6   Configuring an Event Dispatcher...............   6-11 I               6.7   Configuring an Application Database...........   6-11 I               6.8   Configuring a Cluster Alias ..................   6-12 9               6.9   Changing a Current DECnet-Plus System I                     Configuration.................................   6-18   !         7  Managing Name Services   I               7.1   Names Services Overview.......................    7-1 I               7.1.1     The Local Namespace ......................    7-1 I               7.1.1.1     Creating a Local Namespace..............    7-2 I               7.1.1.2     Managing the Local Namespace............    7-2 <               7.1.2     The Digital Distributed Name ServiceI                         (DECdns)..................................    7-2 I               7.1.2.1     Creating a New Namespace................    7-3 I               7.1.2.2     Creating a DECdns Namespace.............    7-4 I               7.1.3     Domain Name System........................    7-7 I               7.1.4     Namespace Management......................    7-8 I               7.2   Name Service Search Path......................    7-8 I               7.2.1     Configuring the Search Path Information...    7-9 I               7.2.1.1     Naming Search Path in a Cluster.........   7-10 I               7.2.2     Displaying the Search Path Information....   7-10 I               7.2.3     Modifying the Search Path Information.....   7-10 @               7.2.4     Creating a Site-Specific Search Path NCLI                         Script....................................   7-11 I               7.2.5     Using the Search Path to Ease Migration...   7-12   I                                                                         v                    I               7.2.6     Setting Up Naming Templates...............   7-12 I               7.3   Domain Synonyms...............................   7-13 ?               7.3.1     Search Path Naming Template Support for I                         Domain Synonyms...........................   7-14 I               7.3.2     Local Aliases.............................   7-14 I               7.4   Node Synonym Directories......................   7-15 :               7.4.1     Defining an Alternate Node SynonymI                         Directory.................................   7-15 I               7.4.2     When to Use the Logical Name..............   7-15 ?               7.5   Using a DNS Version 1 Namespace with DECdns I                     Version 2.....................................   7-16 ?               7.5.1     Preparing a DNS Version 1 Namespace for I                         Use by DECdns Version 2...................   7-17 I               7.5.2     Using the DNS Version 1 Namespace.........   7-18 I               7.6   Registering a Node in the Namespace...........   7-19 I               7.6.1     Export/Import File Format.................   7-19 I               7.6.2     Problems Registering a Node...............   7-19   5         Part III  Additional Installation Information     7         A  The POLYCENTER Software Installation Utility   I               A.1   DCL Help with POLYCENTER......................    A-2 I               A.1.1     DCL Command Summary.......................    A-3 >               A.2   Creating and Using a Product ConfigurationI                     File..........................................    A-6 I               A.2.1     Responding to Installation Questions......    A-8 I               A.3   Verifying Pre-installation Tasks..............    A-8 I               A.4   Resolving Conflicts...........................    A-9 I               A.5   Determining Installation Progress.............    A-9 I               A.6   Possible Installation Errors..................   A-10 I               A.7   Reporting Problems............................   A-10   @         B  Installing DECnet-Plus for OpenVMS from an InfoServer  <               B.1   Steps to Installing the Software from anI                     InfoServer....................................    B-1 I               B.2   Install Commands..............................    B-2             
         vi                   2         C  System Files Loaded During Installation  
         Index              Figures   @               3-1       Installation and Configuration FlowchartI                         (Alpha Only)..............................    3-5   @               3-2       Installation and Configuration FlowchartI                         (VAX Only) ...............................    3-8            Tables  :               1-1       Disk Space Requirements - OptionalI                         Software..................................    1-6   A               1-2       Minimum System Parameters Required - Base I                         Software Installation.....................    1-7   I               2-1       Installation Planning Checklist...........    2-2   I               4-1       Choosing Your Configuration Option........    4-3   I               A-1       DCL PRODUCT Commands and Qualifiers.......    A-3                                       I                                                                       vii                              I         _________________________________________________________________   I                                                                   Preface       D               This is the first installation book you should read inG               order to successfully install DECnet-Plus for OpenVMS. It D               also includes how to configure DECnet-Plus for OpenVMSA               using the FAST and BASIC configuration options, and .               information about name services.  C               The second installation book (DECnet-Plus for OpenVMS C               Applications Installation and Advanced Configuration) D               describes using the ADVANCED configuration option, and+               how to install and configure:   '               o  X.25 for OpenVMS Alpha   A               o  VAX P.S.I. and VAX P.S.I. Access for OpenVMS VAX   3               o  OSI layered software applications:   @                  -  File Transfer, Access, and Management (FTAM)  )                  -  Virtual Terminal (VT)   2                  -  OSI Applications Kernel (OSAK)  F                 ________________________ Note ________________________  A                 DECnet-Plus for OpenVMS must be installed on your E                 system before you can install X.25, FTAM, VT, or OSAK                  software.   F                 ______________________________________________________        I                                                                       vii                             Intended Audience   '               This book is written for:   (               o  OpenVMS system managers  0               o  DECnet-Plus software installers  .               o  Network planners and managers           Structure of This Book  (               This book has three parts:  E               Part I  Describes the pre-installation and installation I                       steps necessary to install DECnet-Plus for OpenVMS.   D               Part    Provides help to determine which configurationG               II      option to use: FAST, BASIC or ADVANCED. Describes B                       how to run a FAST configuration, and a BASICI                       configuration including examples for an Alpha and a I                       VAX system. Also includes an overview of the naming C                       services you can select during configuration.   A               Part    Includes a basic overview on the POLYCENTER B               III     Software Installation utility, an example of@                       installing DECnet-Plus for OpenVMS from anC                       InfoServer, and a list of system files loaded *                       during installation.           Terminologyl  H               The following terms are used interchangeably in this book:                 o  Alpha and AXP  )               o  Transition and migrations  -               o  Phase IV and DECnet Phase IVn  (               o  End system and end node  /               o  Intermediate system and routeru  (               o  DECnet-Plus and Phase V           viii M  l                       Related Documents   A               The following books provide additional information:   F               o  DECnet-Plus for OpenVMS Applications Installation and'                  Advanced Configuration   A                  The second installation book to read in order to D                  successfully install and configure X.25 for OpenVMSF                  Alpha, P.S.I and P.S.I. Access for OpenVMS VAX, FTAM,H                  VT, and OSAK. It also includes how to configure DECnet-I                  Plus for OpenVMS using the ADVANCED configuration option_3                  and how to modify a configuration._  F               o  DECnet-Plus for OpenVMS Introduction and User's Guide  D                  Introduces the DECnet-Plus for OpenVMS features andC                  tools, and how to use and manage a DECnet-Plus for B                  OpenVMS end system. Also provides a comprehensive5                  glossary of DECnet-Plus terminology.c  +               o  DECnet-Plus Planning Guides  G                  Explains in detail the transition from DECnet Phase IV G                  to DECnet-Plus, providing configuration guidelines ande                   planning tasks.  .               o  DECnet-Plus DECdns Management  .               o  DECnet-Plus DECdts Management  ;               o  DECnet-Plus for OpenVMS Network Managementd  5               o  X.25 for OpenVMS Configuration Guide   :               o  OpenVMS License Management Utility Manual  E               o  OpenVMS System Management Utilities Reference Manual   H               For additional information on the DECnet-Plus products andG               services, access the Digital OpenVMS World Wide Web site.o$               Use the following URL:  ,               http://www.openvms.digital.com  I                                                                        ix, T  ,                       Reader's Commentsu  I               Digital welcomes your comments on this manual or any of the I               DECnet-Plus documents. Send us your comments through any ofi%               the following channels:e  4               Internet    openvmsdoc@zko.mts.dec.com  F               Fax         603 881-0120, Attention: OSSG Documentation,$                           ZKO3-4/U08  >               Mail        OSSG Documentation Group, ZKO3-4/U08,                           110 Spit Brook Rd./                           Nashua, NH 03062-2698   -         How To Order Additional DocumentationH  G               Use the following table to order additional documentation =               or information. If you need help deciding whichCC               documentation best meets your needs, call 800-DIGITALo               (800-344-4825).i                                                	         x     t                       Conventions   >               The following conventions are used in this book.  I               ___________________________________________________________ I               Convention_______Meaning____________________________________  D               special type     Indicates a literal example of systemG                                output or user input. In text, indicates.H                                command names, keywords, node names, fileG                                names, directories, utilities and tools.V  E               UPPERCASE        Indicates keywords that you enter. You F                                can type the characters in uppercase orD                                lowercase. You can abbreviate commandA                                keywords to the smallest number ofuD                                characters that OpenVMS, NCP, NCL, or6                                the other tools accept.  D                                Uppercase also indicates the names ofD                                files, directories, utilities, tools,D                                commands, parameters, and procedures.  4               italic type      Indicates a variable.  G               bold             Indicates a new term defined in the text 8                                or important information.  G               <Return>         Indicates that you press the Return key.   G               Ctrl/x           Indicates that you press the Control key7B                                while you press the key noted by x.  G               [YES]            Brackets indicate that the enclosed item D                                is a default value in an installation&                                prompt.  H               { }              In command format descriptions, indicatesA                                you must enter at least one listed I               _________________element.__________________________________P          I                                                                        xi                          I                                                                    Part IiI         _________________________________________________________________t  I                                      DECnet-Plus for OpenVMS Installationf            B               Part I describes the prerequisite steps necessary toE               install DECnet-Plus for OpenVMS, and how to install it.   I               o  Chapter 1 - Preparing to Install DECnet-Plus for OpenVMS   3               o  Chapter 2 - Pre-Installation Taskst  ?               o  Chapter 3 - Installing DECnet-Plus for OpenVMS. .  .                    I                                                                         1 I         _________________________________________________________________.  I                              Preparing to Install DECnet-Plus for OpenVMSn    F               This chapter describes the tasks you must perform beforeD               installing and configuring the DECnet-Plus for OpenVMS               distribution kit.   8         1.1 The POLYCENTER Software Installation Utility  C               The POLYCENTER Software Installation utility replaces H               VMSINSTAL as the method of installing layered products forH               OpenVMS systems. It allows you to install several software-               products with a single command.   I               Full details for using the POLYCENTER Software Installation E               utility to install and manage software products on yournB               system are provided in the OpenVMS System ManagementC               Utilities Reference Manual. This manual also providesf?               information on removing products along with other @               POLYCENTER Software Installation utility features.  C               See Appendix A for a basic overview of the POLYCENTERu,               Software Installation utility.  +         1.2 Inspecting the Distribution Kit.  F               Before you install the DECnet-Plus for OpenVMS software,I               make sure you have a complete software distribution kit. If.I               you have the OpenVMS condist CD-ROM distribution kit, check.E               the CD master index for the kit location. If you have a.H               magtape or TK50 kit, supply the device name when requested>               by the POLYCENTER Software Installation utility.  G               Check that the kit contains everything listed on the bill.D               of materials (BOM). If anything is missing or damaged,2               contact your Digital representative.      I                          Preparing to Install DECnet-Plus for OpenVMS 1-1n e  e      4         Preparing to Install DECnet-Plus for OpenVMS+         1.2 Inspecting the Distribution Kit     G               The distribution kit contains the following component kit                files:  )               o  Base components software.  4                  -  DECnet-Plus for OpenVMS base kit  "               o  Optional software  @                  -  OSI remote file operations support kit (FTAM                     software)r  @                  -  OSI applications support kit (OSAK software)  6                  -  Virtual Terminal (VT) software kit  6               For a more detailed list, see Chapter 3.                                                        8         1-2 Preparing to Install DECnet-Plus for OpenVMS           I                              Preparing to Install DECnet-Plus for OpenVMS I                                       1.2 Inspecting the Distribution Kit     F                 ________________________ Note ________________________  ?                 Before installing any of the software, read the F                 DECnet-Plus Planning Guide (included with your DECnet-D                 Plus for OpenVMS core documentation set). This guideE                 contains installation planning information, including 0                 namespace planning instructions.  F                 ______________________________________________________  <         1.3 Time Required for Installation and Configuration  H               The time required to complete the DECnet-Plus installationD               and configuration procedures depends on the following:  E               o  Configuration option used (FAST, BASIC, or ADVANCED)g  ,               o  Optional software installed  "               o  CPU on the system  +               o  Type of distribution media   D               The time required to install and configure DECnet-PlusC               can vary from 30 minutes to 2 hours, depending on the B               combination of choices you make from the above list.  .         1.4 Prerequisite Software and Licenses  D               Before you can install and configure the software, theI               system must have the required operating system software andt               license(s)..  #         1.4.1 Software and Licenses   F               The prerequisites for installing DECnet-Plus for OpenVMS&               software are as follows:  <               o  OpenVMS operating system Version 7.0 or 7.1  :               o  One of the available DECnet-Plus licenses  H               The specific license required on your system is determined/               by the functions you want to use:.  H               o  Basic function license (DVNETEND) - provides end system                  support..  I                          Preparing to Install DECnet-Plus for OpenVMS 1-3. .  7      4         Preparing to Install DECnet-Plus for OpenVMS.         1.4 Prerequisite Software and Licenses    G               o  Extended function license (DVNETEXT) for Alpha systemsNF                  - provides end system support, DECdts server, cluster6                  alias, and OSI applications gateways.  E               o  Extended function license (DVNETRTG) for VAX systemseE                  - provides end system support, DECdns server, DECdts.F                  server, cluster alias, and OSI applications gateways.  B                  For the extended function licenses, the TELNET/VTF                  gateway also requires the Digital TCP/IP Services for!                  OpenVMS product.t  =               o  X.25 license (Alpha systems only) - provides.=                  functionality over a wide area network link..  I               At least one node of an OpenVMS Cluster system requires theC=               extended function license to use cluster alias..  7         1.4.1.1 DECnet and OSI Applications over TCP/IPg  E               If you plan to use the DECnet-Plus over TCP/IP feature,rE               then TCP/IP software is a prerequisite. Your end systemnD               will be able to operate over TCP/IP if and only if theG               TCP/IP product used on your system supports the PATHWORKS 1               Internet Protocol (PWIP) interface.1  G               The PWIP interface is currently supported by the products1H               listed below. Contact the vendor for the required versions               of their product.a  4               o  Digital TCP/IP Services for OpenVMS                 o  TCPware  -                  Process Software Corporationo#                  959 Concord Street %                  Framingham, MA 01701                   800-722-7770 !                  info@process.com   %               o  MultiNet for OpenVMS   9                  Cisco Systems, Inc. (formerly TGV, Inc.)t"                  101 Cooper Street%                  Santa Cruz, CA 95060                   408-457-5200t$                  sales@tgv.cisco.com  $               o  PATHway for OpenVMS  8         1-4 Preparing to Install DECnet-Plus for OpenVMS           I                              Preparing to Install DECnet-Plus for OpenVMS.I                                    1.4 Prerequisite Software and Licenses     E                  The Attachmate Corp. (formerly The Wollongong Group,l                  Inc.)&                  1129 San Antonio Road,                  Palo Alto, California 943032                  800-872-8649 (800-962-8649 in CA)                  sales@twg.com  F                 ________________________ Note ________________________  C                 For more information on using DECnet over TCP/IP or F                 the OSI applications over TCP/IP, refer to the DECnet-:                 Plus for OpenVMS Network Management guide.  F                 ______________________________________________________           1.4.2 Checking Licenses   G               To determine the OpenVMS operating system version number, .               enter the following DCL command:  $               $ show system <Return>  G               To determine whether a DECnet-Plus license is registered,d.               enter the following DCL command:  ,               $ show license dvnet* <Return>  B               If the system does not have the required license(s),E               obtain the Product Authorization Key (PAK) and register E               the license. For instructions on registering a license, E               refer to the OpenVMS License Management Utility Manual.h           1.5 System Requirementsn  <               Before you install the DECnet-Plus for OpenVMSF               software, make sure that your system meets the following               requirements.            1.5.1 Disk Space  I               If this is the first time you are installing DECnet-Plus on I               a particular system, ensure that you have enough free space F               on the system disk. You need enough space to install theE               DECnet-Plus Base components and any options you select.   A               If you already have DECnet-Plus installed, you need_G               considerably less free space for the installation because I               the earlier installation allocated most of the space that a ,               subsequent installation needs.  I                          Preparing to Install DECnet-Plus for OpenVMS 1-5f r  n      4         Preparing to Install DECnet-Plus for OpenVMS         1.5 System Requirements     3               Required Disk Space - Base Components   D               The total amount of disk space required to install theC               software for base components is 77,000 blocks for VAX :               systems and 85,000 blocks for Alpha systems.  ,               Disk Space - Optional Software  H               Table 1-1 shows the amount of disk space needed to installC               the optional software. Make sure you have enough free E               space to install the required software and the optionalc               software.n  I               Table_1-1_Disk_Space_Requirements_-_Optional_Software______   +                                  Blocks foreI               Component__________Alpha____________Blocks_for_VAX_________a  6               DECdts server      1400             1800  9               DECdns server      N/A              3000[1]   6               VAX P.S.I.         N/A              7000  6               VAX WANDD          N/A              5500  5               X.25               12144            N/A   7               FTAM               28000            12000t  6               Virtual Terminal   4000             2000  6               OSAK               6900             6000I               [1]Approximate_amount_-_actual_amount_depends_on_the_size__-  I               of the namespace, the number of logs created, and so forth.eI               The amount of required disk space could double when running H               tests, then return to original amount when duplicate files               are deleted.I               ___________________________________________________________d  H               To find out how many free blocks exist on the system disk,*               enter the following command:  2               $ show device sys$sysdevice <Return>  I               If the number of required blocks exceeds the number of freep>               blocks, you must clear space on the system disk.  8         1-6 Preparing to Install DECnet-Plus for OpenVMS -  s      I                              Preparing to Install DECnet-Plus for OpenVMSnI                                                   1.5 System Requirementsd             1.5.2 Required Memory   D               The minimum amount of memory required is 24 MB for VAX2               systems and 64 MB for Alpha systems.  A               To check memory on your system, enter the followingn               command:  )               $ show memory/full <Return>n  (         1.5.3 Required System Parameters  @               This section provides information about the system?               parameters, their values, and how to modify them.e  H               Table 1-2 lists the minimum system parameters required for                the base software.  A               Table 1-2 Minimum System Parameters Required - BasetI               __________Software_Installation____________________________M  0                                          MinimumB                                          Value for   Minimum ValueI               Parameter__________________Alpha_______for_VAX_____________   8               MIN_GBLSECTIONS            512         400  :               MIN_GBLPAGES               100000      60000  9               MIN_GBLPAGFIL              1024        4096   8               MIN_CLISYMTBL              750         500  8               MIN_KSTACKPAGES            2           N/A  I               MIN_VIRTUALPAGES___________N/A_________35000_______________   F               To check these parameters, invoke the SYSGEN utility and*               enter the following command:                 $ mcr sysgen&               SYSGEN> show gblsections  I               If any of the system parameters need to be modified, follow.               these steps:  9               1. Edit the modparams.dat file by entering:u  0                  $ edit sys$system:modparams.dat  I                          Preparing to Install DECnet-Plus for OpenVMS 1-7  p  c      4         Preparing to Install DECnet-Plus for OpenVMS         1.5 System Requirements     H               2. Enter the values into the file in the following format:  "                  SCSSYSTEMID=65187  !                  SCSNODE="SUPER1"n$                  MIN_GBLSECTIONS=512                  .                  .                  .#                  MIN_GBLPAGFIL=1024n  &               3. Exit from the editor.  ?               4. Run AUTOGEN by entering the following command:e  5                  $ @sys$update:autogen getdata rebootr  F                 ________________________ Note ________________________  D                 Run AUTOGEN to ensure that your system is tuned with+                 the appropriate parameters.   F                 ______________________________________________________  =         1.5.3.1 SYSGEN Parameters for OpenVMS Cluster Members   C               When installing DECnet-Plus for OpenVMS on an OpenVMS B               Cluster, make sure that all cluster members have theE               suggested SYSGEN parameters set correctly. If a node in H               the cluster does not have the required minimum parameters,D               startup of the network will fail. If the network failsF               to start for this reason, the logical NET$STARTUP_STATUSA               is set to OFF-AUTOGENREQ. Set the parameters to thet>               recommended values before you run net$configure.  -         1.6 Privileges and Rights Identifiers   G               Digital recommends that you install and configure DECnet->G               Plus from the SYSTEM account. If you are configuring fromxF               another account, make sure the account has the followingC               privileges and rights identifiers in place before youS               begin.  9               Required account privileges are as follows:                  o  CMKRNL                  o  NETMBX                  o  SYSPRV   8         1-8 Preparing to Install DECnet-Plus for OpenVMS i  c      I                              Preparing to Install DECnet-Plus for OpenVMS I                                     1.6 Privileges and Rights Identifiers                    o  TMPMBX                  o  OPER                  o  SYSNAM                  o  WORLD  F                 ________________________ Note ________________________  E                 The account cannot have the locked password (LOCKPWD)                  flag set.   F                 ______________________________________________________  9               Required rights identifiers are as follows:                  o  NET$MANAGE                  o  NET$SECURITY   &               o  NET$REGISTERDNSOBJECT  F                 ________________________ Note ________________________  E                 If your account has the BYPASS privilege, then you doo;                 not need to grant these rights identifiers.   F                 ______________________________________________________  &         1.7 Backing Up the System Disk  I               Use the OpenVMS BACKUP utility to make a copy of the system                disk.            1.8 Notifying Userss  C               Inform users on the system that you plan to install au1               product and that they must log out.t  I               Use the reply/all command and be sure to indicate the exact D               time you plan to begin running the POLYCENTER Software0               Installation utility. For example:  (               $ set logins/interactive=0I               $ reply/all "Installing software at 18:00; Please log out."s  I               If possible, give users an estimated time when they will beE+               able to log in to the system.t  I                          Preparing to Install DECnet-Plus for OpenVMS 1-9p i                       I                                                                         2oI         _________________________________________________________________   I                                                    Pre-Installation Tasks     G               Before installing the software, complete the installationaG               planning checklist in this chapter. This ensures that you H               have the information you need to complete the installationA               and configuration in the minimum amount of time. IniI               addition to identifying necessary information and directing G               you to sources of help, the checklist also assists you inv)               choosing optional software.p  F         2.1 Information Required to Complete the Installation Planning             Checklist.  B               Determine the following information before you beginF               the installation and configuration procedure. Enter thisB               information on your installation planning checklist:  G               o  System's full name (you may have a DECdns full name, a F                  Local namespace full name, and a fully qualified host<                  name for the Domain Name System [DNS/BIND])                 o  Node synonymw  G               o  Phase IV-compatible address to interface with Phase IVs                  nodes                  o  Phase IV prefix                  o  Network address  +         2.2 Installation Planning Checklist   H               Complete the checklist in Table 2-1 before continuing with'               the installation process.K        I                                                Pre-Installation Tasks 2-1  o                  Pre-Installation Tasks+         2.2 Installation Planning Checklist     I               Table_2-1_Installation_Planning_Checklist__________________   I               Question_____________________Yes__No___For_More_Information   4               Have you backed up your      <  > <  >               system disk?  '               If not, then do so before_)               you start the installation.o  I               ___________________________________________________________n  D               Will the system get network  <  > <  > See Section 6.2%               addresses from a DECdns                name server?  !               If yes, what is then"               system's DECdns node                name (for example,               ACME:.BOSTON)?  I               ___________________________________________________________C  D               Will the system store        <  > <  > See Section 6.2$               network addresses in a               Local database?o  !               If yes, what is theC!               system's Local nodeI                name (for example,               LOCAL:.BOSTON)?   I               ___________________________________________________________   D               Is TCP/IP installed on the   <  > <  > See Section 6.2%               system? Will the systemm(               store network addresses in$               the DNS/BIND database?  !               If yes, what is the.)               system's DNS/BIND name (for (               example, BOSTON.ACME.COM)?  I               ___________________________________________________________   F               What is the system's node              See Section 6.2.4#               synonym (for example,r               BOSTON)?  I                                                  (continued on next page)   "         2-2 Pre-Installation Tasks           I                                                    Pre-Installation Tasks I                                       2.2 Installation Planning Checklist     I               Table_2-1_(Cont.)_Installation_Planning_Checklist__________   I               Question_____________________Yes__No___For_More_Information   I               ___________________________________________________________   F               Will the system communicate  <  > <  > See Section 6.2.5F               with Phase IV nodes?                   and Section 6.2.6  $               o  Phase IV-compatible&                  address (for example,                  2.38)  %               o  Phase IV Prefix (theo!                  default is 49::)t  I               ___________________________________________________________e  F               Will the system              <  > <  > See Section 6.2.7'               autoconfigure its network.               addresses?  )               If not, you'll need network )               entity titles (for example,D6               47:24:02-01-0A-04:08-00-2B-93-ED-99:00).  I               ___________________________________________________________   I               Do you want to install       <  > <  > Refer to the DECnet-tI               DECdts server software?                Plus Planning Guide.x  I               ___________________________________________________________O  I                                                  (continued on next page)l                      I                                                Pre-Installation Tasks 2-3                     Pre-Installation Tasks+         2.2 Installation Planning Checklistp    I               Table_2-1_(Cont.)_Installation_Planning_Checklist__________o  I               Question_____________________Yes__No___For_More_Informationr  I               (For VAX only.) Do you       <  > <  > Refer to the DECnet-rE               want to install VAX WANDD              Plus for OpenVMSDA               software for VAX?                      Applications A               You must install this                  InstallationCA               software if you want to                and Advanced I               use any of the following:              Configuration guide.M  '               -  Non-LAN connections tos                  the network  )               -  Routing over synchronous                   connections  #               -  X.25 software overt"                  synchronous lines  I               ___________________________________________________________l  I               (For Alpha only.) Do         <  > <  > Refer to the DECnet-gE               you want to install X.25               Plus for OpenVMS A               software for Alpha?                    ApplicationsAA               You must install this                  InstallationIA               software if you want to                and Advanced I               use any of the following:              Configuration guide.   (               -  X.25 communications via                  DEC X25gatewayt  (               -  X.25 communications via                  X.25 MultihostE  $               -  X.25 communications&                  on local system (X.25                  Native)  '               -  LAN X.25 (LLC Class 2)d  !               -  DECnet over X.25_  I               ___________________________________________________________   I                                                  (continued on next page)   "         2-4 Pre-Installation Tasks :         I                                                    Pre-Installation TaskseI                                       2.2 Installation Planning Checklistn    I               Table_2-1_(Cont.)_Installation_Planning_Checklist__________e  I               Question_____________________Yes__No___For_More_Informationt  I               Do you want to install       <  > <  > Refer to the DECnet-nE               DECnet-Plus for OpenVMS                Plus for OpenVMSeA               OSAK software?                         Applications A               If you plan to use an OSI              Installation A               application such as FTAM or            and Advanced I               Virtual Terminal, you must             Configuration guide.t  $               install this software.  I               ___________________________________________________________u  I               Do you want to install       <  > <  > Refer to the DECnet-sE               DECnet-Plus for OpenVMS                Plus for OpenVMS A               FTAM software?                         Applications,A               If you plan to copy files              InstallationaA               to and from other OSI-                 and AdvancedmI               compliant systems or                   Configuration guide.   $               manage such files, you)               must install this software.   I               ___________________________________________________________R  I               Do you want to install       <  > <  > Refer to the DECnet- E               DECnet-Plus for OpenVMS                Plus for OpenVMS A               Virtual Terminal (VT)                  Applications A               software?                              Installation A               If you plan to support                 and Advanced I               remote logins and access               Configuration guide.w  '               to remote applications on (               OSI-compliant systems, youI               must_install_this_software._________________________________                I                                                Pre-Installation Tasks 2-5k o                       I                                                                         3dI         _________________________________________________________________A  I                                        Installing DECnet-Plus for OpenVMS0    B               The DECnet-Plus for OpenVMS distribution software isF               provided on compact disc (CD-ROM). The software consists*               of the following components:  *               Components for Alpha Systems                  o  Base Components  4                  -  DECnet-Plus for OpenVMS base kit  !                  -  DECdts servers  I               o  Optional Components (included with the base kit but mustf)                  be installed separately)d                    -  FTAM  )                  -  Virtual Terminal (VT)t                    -  OSAK  =               o  X.25 for Alpha (requires a separate license)_  (               Components for VAX Systems                  o  Base Components  4                  -  DECnet-Plus for OpenVMS base kit                    -  VAX P.S.I.  !                  -  WANDD for VAXd  !                  -  DECdns servere  !                  -  DECdts servere  I               o  Optional Components (included with the base kit but musts)                  be installed separately)e                    -  FTAM                    -  VT  I                                    Installing DECnet-Plus for OpenVMS 3-1            *         Installing DECnet-Plus for OpenVMS                        -  OSAK                                                                                        .         3-2 Installing DECnet-Plus for OpenVMS    c      I                                        Installing DECnet-Plus for OpenVMS       F                 ________________________ Note ________________________  D                 The DECnet-Plus base components, FTAM, OSAK, and VT,A                 are all packaged as separate installation kits on A                 the distribution medium. They are usually locateddA                 in the same directory. The X.25 for OpenVMS Alphai>                 kit, however, is a separately licensed product>                 and as such is in a different directory on theC                 distribution medium. Consult the documentation with E                 your distribution medium for the location of the kits_                 you desire._  F                 ______________________________________________________  I               Use the POLYCENTER Software Installation utility to install A               the base components and any combination of optionalLE               components. See Appendix A for information on using the E               DCL interface with the POLYCENTER Software InstallationA               utility.  5         3.1 Recommended Order for Installing Software   D               The following sections describe the order in which youE               should install the DECnet-Plus for OpenVMS software for ,               either an Alpha or VAX system.  @         3.1.1 Installing DECnet-Plus for an OpenVMS Alpha System  @               If you choose to install all the software productsA               at the same time, install and configure the OpenVMSgD               operating system and layered products in the followingF               order, referring to the appropriate documentation. For aE               quick reference, see Figure 3-1. After OpenVMS has beenf5               installed, perform the following steps:   .               1. Inspect the distribution kit.  G               2. Verify that all prerequisite software and licenses are                   installed.L  ?                  Refer to the OpenVMS system documentation set..  D               3. Shut down all network-related applications and tell"                  users to log out.  1               4. Install DECnet-Plus for OpenVMS._  !                  See Section 3.2.   I                                    Installing DECnet-Plus for OpenVMS 3-3r i         *         Installing DECnet-Plus for OpenVMS5         3.1 Recommended Order for Installing Software     +               5. Set the system parameters.   #               6. Reboot the system.u  H               7. Install X.25 for OpenVMS Alpha and WANDD, if necessary.  B                  Refer to the DECnet-Plus for OpenVMS Applications?                  Installation and Advanced Configuration guide.h  H               8. Configure DECnet-Plus for OpenVMS. First, see Chapter 4I                  to determine which configuration option to choose: FAST,a$                  BASIC, or ADVANCED.  ?                  For a FAST configuration, see Chapter 5. For aeD                  BASIC configuration, see Chapter 6. For an ADVANCEDD                  configuration, refer to the DECnet-Plus for OpenVMSE                  Applications Installation and Advanced Configurationc                  guide.i  2               9. Configure X.25 for OpenVMS Alpha.  B                  Refer to the DECnet-Plus for OpenVMS Applications?                  Installation and Advanced Configuration guide.   F               10.Install and configure the OSI Applications (FTAM, VT,                  OSAK).   B                  Refer to the DECnet-Plus for OpenVMS Applications?                  Installation and Advanced Configuration guide.e                                .         3-4 Installing DECnet-Plus for OpenVMS    v      I                                        Installing DECnet-Plus for OpenVMSOI                             3.1 Recommended Order for Installing Software     H               Figure 3-1 Installation and Configuration Flowchart (Alpha                          Only)                                                                                      I                                    Installing DECnet-Plus for OpenVMS 3-5i r  r      *         Installing DECnet-Plus for OpenVMS5         3.1 Recommended Order for Installing SoftwareR    5         3.1.2 Installing DECnet-Plus for a VAX System_  @               If you choose to install all the software productsA               at the same time, install and configure the OpenVMSrD               operating system and layered products in the followingF               order, referring to the appropriate documentation. For aE               quick reference, see Figure 3-2. After OpenVMS has beent/               installed, perform the following:o  .               1. Inspect the distribution kit.  G               2. Verify that all prerequisite software and licenses areu                  installed.   ?                  Refer to the OpenVMS system documentation set.   D               3. Shut down all network-related applications and tell"                  users to log out.  1               4. Install DECnet-Plus for OpenVMS.   !                  See Section 3.2.t  F                 ________________________ Note ________________________  D                 If you want to install VAX P.S.I., select the option=                 now while installing DECnet-Plus for OpenVMS.n  F                 ______________________________________________________  +               5. Set the system parameters.   #               6. Reboot the system._  A               7. Configure DECnet-Plus for OpenVMS. First, review E                  Chapter 4 to determine which configuration option toe2                  choose: FAST, BASIC, or ADVANCED.  ?                  For a FAST configuration, see Chapter 5. For asD                  BASIC configuration, see Chapter 6. For an ADVANCEDD                  configuration, refer to the DECnet-Plus for OpenVMSE                  Applications Installation and Advanced Configurationo                  guide.   %               8. Configure VAX P.S.I.s  B                  Refer to the DECnet-Plus for OpenVMS Applications?                  Installation and Advanced Configuration guide.n  F               9. Install and configure the OSI applications (FTAM, VT,                  OSAK).   .         3-6 Installing DECnet-Plus for OpenVMS e  e      I                                        Installing DECnet-Plus for OpenVMS I                             3.1 Recommended Order for Installing Software     B                  Refer to the DECnet-Plus for OpenVMS Applications?                  Installation and Advanced Configuration guide.                                                                                       I                                    Installing DECnet-Plus for OpenVMS 3-7f           *         Installing DECnet-Plus for OpenVMS5         3.1 Recommended Order for Installing Softwaret    F               Figure 3-2 Installation and Configuration Flowchart (VAX                          Only)                @         3.2 Installing DECnet-Plus Using the POLYCENTER Software              Installation Utility  I               This section describes the steps for installing DECnet-PluslI               software using the POLYCENTER Software Installation utility_E               (for more information on this utility, see Appendix A).uI               You must have SYSPRV privileges on the local or remote node 1               where you want to run this utility.   ?         3.2.1 Sample DECnet-Plus for OpenVMS Alpha Installation_  <               To start the installation, follow these steps:  .               1. Log in to the SYSTEM account.  H               2. Mount the software CD-ROM. Refer to the OpenVMS LayeredG                  Products Compact Disc User's Guide for instructions on(6                  mounting and removing a compact disc.  F               3. Enter the following command, substituting the name of:                  your device for the devicename parameter:  P                  $ product install decnet_osi /source=devicename:[dnvosi071.kit]  F               You are then prompted for installation information as inG               the following example. In this example, numbered callouts_G               (1, 2, 3, . . . ) guide you through the sequence of steps I               that require your response. For Alpha systems, you will seet;               AXPVMS as product information on your screen.n  7                The following product has been selected:y=                    DEC AXPVMS DECNET_OSI V7.1     [Available]   7               1 Do you want to continue? [YES] <Return>_  K                DEC AXPVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS AXPi  W                    Copyright  Digital Equipment Corporation 1996. All rights reserved.   0                    Digital Equipment Corporation  .         3-8 Installing DECnet-Plus for OpenVMS           I                                        Installing DECnet-Plus for OpenVMS I  DECnet-Plus           Using the POLYCENTER Software Installation Utility.    O                    This product requires one of two PAKS: DVNETEND or DVNETEXT.P  P               2 Do you want the defaults for all product options? [YES] <Return>  >               3 Do you want to view the options? [NO] <Return>  +                Execution phase starting ...   7                The following product will be installed:5-                    DEC AXPVMS DECNET_OSI V7.1   P                Portion Done: 0%...10%...20%...30%...40%...50%...80%...90%...100%  8                The following product has been installed:-                    DEC AXPVMS DECNET_OSI V7.1f  G                1  At this point, you can stop the installation process._F                  If you want to continue, press Return. If you want to2                  stop, type NO, then press Return.  I                2  This question allows you to select which optional partsrG                  of the DECnet-Plus product you want to install. If you-F                  want to install just the base software, press Return.E                  If you want to select the optional software, type NOaH                  and press Return. The procedure then displays a list of!                  choices for you.G  D                3  This question allows you to review and change yourG                  current selections. Type YES if you are satisfied witheE                  the current selected options. Type NO if you want to                   make changes.  =         3.2.2 Sample DECnet-Plus for OpenVMS VAX Installation   <               To start the installation, follow these steps:  .               1. Log in to the SYSTEM account.  H               2. Mount the software CD-ROM. Refer to the OpenVMS LayeredG                  Products Compact Disc User's Guide for instructions on 6                  mounting and removing a compact disc.  F               3. Enter the following command, substituting the name of:                  your device for the devicename parameter:  P                  $ product install decnet_osi /source=devicename:[dnvosi071.kit]  I                                    Installing DECnet-Plus for OpenVMS 3-9n i  M      *         Installing DECnet-Plus for OpenVMSU         3.2 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility     D               The installation prompts you for information as in theG               following example. In this example, numbered callouts (1,_H               2, 3, . . . ) guide you through the sequence of steps thatF               require your response. For VAX systems, you will see DEC;               VAXVMS as product information on your screen.   7                The following product has been selected:l<                    DEC VAXVMS DECNET_OSI V7.1    [Available]  7               1 Do you want to continue? [YES] <Return>s  K                DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAXX  W                    Copyright  Digital Equipment Corporation 1996. All rights reserved.t  0                    Digital Equipment Corporation  O                    This product requires one of two PAKS: DVNETEND or DVNETRTG.   P               2 Do you want the defaults for all product options? [YES] <Return>  @               3 Do you want to view the options? [NO] y <Return>  K                DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAXn7                    DEC VAXVMS VMS V7.1      [Available] ;                    VAX P.S.I. or P.S.I. Access software: NO 3                    VAX Wide Area Device Drivers: NO -                    DECdns Server software: NOn-                    DECdts Server software: NOi  G                    Are you satisfied with these options? [YES] <Return>_  +                Execution phase starting ...   7                The following product will be installed:n-                    DEC VAXVMS DECNET_OSI V7.1   J                Portion Done: 0%...10%...20%...30%...40%...80%...90%...100%  8                The following product has been installed:-                    DEC VAXVMS DECNET_OSI V7.1c  G                1  At this point, you can stop the installation process.nF                  If you want to continue, press Return. If you want to2                  stop, type NO, then press Return.  /         3-10 Installing DECnet-Plus for OpenVMS     o      I                                        Installing DECnet-Plus for OpenVMSPI  DECnet-Plus           Using the POLYCENTER Software Installation Utilityr    I                2  This question allows you to select which optional partseG                  of the DECnet-Plus product you want to install. If you F                  want to install just the base software, press Return.E                  If you want to select the optional software, type NO I                  and press Return. (For example, if you want to configure_H                  wide area devices such as WANDD, X.25, or P.S.I, answerH                  NO to this question. The procedure then displays a list%                  of choices for you.)M  D                3  This question allows you to review and change yourG                  current selections. Type YES if you are satisfied with E                  the current selected options. Type NO if you want to                   make changes.    *         3.3 Files Installed on Your System  F               The DECnet-Plus installation procedure installs a numberC               of files on your system. To list the files, enter the_                following command:  7               $ product show object /product=decnet_osik                                              I                                   Installing DECnet-Plus for OpenVMS 3-11_ _  _                    I                                                                   Part IIsI         _________________________________________________________________n  I                               DECnet-Plus for OpenVMS BASIC Configuration.            H               Part II describes how to configure DECnet-Plus for OpenVMS=               using the FAST and BASIC configuration options.   1               It includes the following chapters:t  2               o  Chapter 4 - Configuration Options  @               o  Chapter 5 - Using the FAST Configuration Option  A               o  Chapter 6 - Using the BASIC Configuration Option   3               o  Chapter 7 - Managing Name Services     -                    I                                                                         4nI         _________________________________________________________________   I                                                     Configuration Options     G               This chapter explains the three configuration options you E               can use to configure your system for DECnet-Plus. ThesenG               configuration options enable you to configure the DECnet-eI               Plus for OpenVMS base components so that the system becomes 4               a DECnet-Plus end system on a network.  H               The procedure you use to configure your system for DECnet-G               Plus is sys$manager:net$configure.com. You can use any of @               the following net$configure configuration options:  6               o  FAST configuration option (Chapter 5)  E                  The FAST configuration allows you to quickly upgrade_F                  a non-clustered system from DECnet Phase IV to DECnet                  Phase V.e  7               o  BASIC configuration option (Chapter 6)a  E                  The BASIC configuration allows you to configure your.H                  system for DECnet-Plus by answering a few questions and5                  using the default answers on others.a  G               o  ADVANCED configuration option (DECnet-Plus for OpenVMS E                  Applications Installation and Advanced Configurationm                  guide)   H                  The ADVANCED configuration allows you to customize your0                  system's network configuration.  D               This chapter presents additional information about the               following topics:t  1               o  Selecting a configuration option   &               o  Running net$configure  G               See Section 1.6 for a list of account privileges you needn#               to run net$configure.I  I                                                 Configuration Options 4-1t i  S               Configuration Optionsn,         4.1 Selecting a Configuration Option    ,         4.1 Selecting a Configuration Option  G               If you installed the required software, you can configure F               your system using the net$configure configuration optionG               for the FAST configuration, using the net$configure basiceH               configuration option for the BASIC configuration, or usingE               the net$configure advanced configuration option for thei%               ADVANCED configuration.r  @               Table 4-1 provides some guidelines for making your#               configuration choice.o  G               If you choose to use either the FAST configuration option C               or the BASIC configuration option, continue with this G               section. If you prefer to customize your system's networkMI               configuration with the ADVANCED configuration option, refertF               to the DECnet-Plus for OpenVMS Applications Installation/               and Advanced Configuration guide.                                                       !         4-2 Configuration Optionsu o  p      I                                                     Configuration Options I                                      4.1 Selecting a Configuration Options        I         Table_4-1_Choosing_Your_Configuration_Option_____________________l  I         Option..._Choose_if...___________________________________________   G         FAST      You are upgrading from a DECnet Phase IV node and you B                   plan to use the existing Phase IV configuration.  /                   The node is not in a cluster.   E                   You are running the configuration procedure for the                    first time.   I         _________________________________________________________________   +         BASIC     The node is in a cluster.D  A                   You are upgrading or reconfiguring DECnet-Plus.O  @                   You need to access a DECdns server for network                   addresses.  F                   You want to run DECnet over TCP/IP (RFC 1859) and/or:                   OSI applications over TCP/IP (RFC 1006).  A                   You only have one communications device, or you F                   have multiple devices, all of which will be used for-                   DECnet-Plus communications.t  G                   You want to use the default names for all devices andn#                   routing circuits.   H                   You want to autoconfigure your network addresses only.  G                   You want to configure both the NSP and OSI transports I                   and only want to create default OSI templates. You wantiG                   to enable both DECnet over TCP/IP or OSI applications                    over TCP/IP.  I                   You do not want to enable FDDI large packet support (if 1                   you have an FDDI-type circuit).   @                   You want to set the routing characteristic DNAE                   Address Format to TRUE (this attribute controls theo9                   interpretation of address structuring).-  :                   You want to use integrated mode routing.  I         _________________________________________________________________f  I                                                  (continued on next page)e  I                                                 Configuration Options 4-3F a                  Configuration Optionsr,         4.1 Selecting a Configuration Option    I         Table_4-1_(Cont.)_Choosing_Your_Configuration_Option_____________   I         Option..._Choose_if...___________________________________________r  0         ADVANCED  Your configuration is complex.  E                   You need to customize your network's configuration.   I                   Your system has multiple communication devices, and you 6                   want them to run a mix of protocols.  H                   You want to configure a cluster with both DECnet Phase.                   IV and DECnet Phase V nodes.  C                   You want the option to give specific names to all H                   devices and routing circuits. You also want the optionI                   of not configuring all of your devices for DECnet-Plus.S  G                   You want the option of manually entering your network                    addresses.  C                   You want to configure either the NSP transport or B                   the OSI transport (or both). You want the optionB                   to create additional OSI templates. You want theD                   option of enabling/disabling DECnet over TCP/IP or/                   OSI applications over TCP/IP.e  C                   You want the option of enabling FDDI large packetl=                   support (if you have an FDDI-type circuit).   <                   You want the option of setting the routingD                   characteristic DNA Address Format to TRUE or FALSEI                   (to control the interpretation of address structuring).n  E                   You want the option of using either integrated mode 5                   routing or segregated mode routing.   E                   You want the option to provide default accounts for I         __________FAL.___________________________________________________   $         4.2 How to Run NET$CONFIGURE  H               The net$configure.com procedure configures the DECnet-PlusD               for OpenVMS software. This command creates or modifiesH               the Network Control Language (NCL) scripts required to run3               DECnet-Plus for OpenVMS on your node.   I               The net$configure.com procedure is an interactive procedureoG               that displays a series of questions. After each question,fH               the default response, if there is one, appears in brackets  !         4-4 Configuration Optionsi t  P      I                                                     Configuration OptionsnH                                             4.2 How to Run NET$CONFIGURE    F               ([ ]). At the end of each question, a colon (:) appears.3               Respond in one of the following ways:   H               o  To get help after a question, type a question mark (?).E                  After the help display, the same question reappears.C  >               o  To select the default response, press Return.  D               o  To enter information, type it immediately after the;                  colon or question mark; then press Return.M  -               o  Type Y for YES and N for NO.P  :               o  To terminate the procedure, press Ctrl/Y.  G               If you execute net$configure.com without specifying BASICtG               or ADVANCED, the BASIC configuration option is invoked byi               default.  F                 ________________________ Note ________________________  B                 If you are running the configuration procedure for>                 the first time on a system that was previously>                 configured for Phase IV and you do not specifyB                 BASIC or ADVANCED, the initial default is the FAST(                 configuration procedure.  B                 However, the FAST configuration procedure can onlyA                 be run once on a system, and after that the BASIC A                 configuration procedure automatically becomes the                  default.  F                 ______________________________________________________  H               To invoke net$configure.com with the default BASIC option,"               enter the following:  *               $ @sys$manager:net$configure  &         4.2.1 Local and Global Symbols  G               The net$configure.com procedure deletes all of your local E               and global symbols at the beginning of the procedure inPB               order to free the symbol table. This happens becauseB               net$configure.com creates and uses a large number ofG               symbols. If the symbols were not deleted at the beginning>D               of the procedure, net$configure would often run out ofE               symbol table space to use while configuring the system.o  I                                                 Configuration Options 4-5.                    Configuration Options.$         4.2 How to Run NET$CONFIGURE    <         4.2.2 Running the Procedure from Different Processes  B               Although net$configure.com can be run simultaneouslyC               on different nodes in a cluster, it should not be runIG               simultaneously from different processes on the same node.o                                                                                !         4-6 Configuration Options                          I                                                                         5sI         _________________________________________________________________t  I                                       Using the FAST Configuration Optionu    I               This chapter describes how to configure the DECnet-Plus for I               OpenVMS base components using the FAST configuration optionrF               so that the system becomes a DECnet-Plus for OpenVMS end"               system on a network.  F                 ________________________ Note ________________________  >                 If you have already run the FAST configuration@                 procedure once on your system, the configuration=                 procedure automatically defaults to the BASICD(                 configuration procedure.  F                 ______________________________________________________  2         5.1 Invoking the FAST Configuration Option  F               To invoke the net$configure.com procedure using the FAST@               configuration option, enter the following command:  4               $ @sys$manager:net$configure  <Return>  #               The procedure starts:   T               Copyright (c) Digital Equipment Corporation 1996. All rights reserved.  M                       DECnet-Plus for OpenVMS network configuration procedure   V                   This procedure will help you create or modify the management scriptsV                   needed to operate DECnet on this machine. You may receive help aboutG                   most questions by answering with a question mark '?'.t  I               %NET$CONFIGURE-I-SETUPNEW, setting up for new configuration J               %NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found  :                                  FAST CONFIGURATION OPTION  I                                   Using the FAST Configuration Option 5-1n u  [      +         Using the FAST Configuration OptionO2         5.1 Invoking the FAST Configuration Option    Q                    You have the option of using the existing Phase IV information V                    to quickly configure DECnet-Plus. This provides full network accessW                    and uses a local file to hold naming information. Very few questionsr!                    will be asked.>[                    If you want to use the fast configuration option, answer YES to the nextX                    question.  W                    If you are running a DNS Server on this system, or plan to run a DNS T                    Server on this system, you *must* answer NO to the next question.Y                    If you want more flexibility when configuring DECnet-Plus, also answerC                    NO.  P                    Answering NO will cause some additional questions to be asked+                    regarding configuration.   V               * Do you want the fast default configuration?          [YES] :  <Return>  B               Press Return to continue with the FAST configuration               option.   B               The procedure informs you that the Phase IV database'               conversion has completed.   R               %NET$CONFIGURE-I-PHASEIVCOMPL, Phase IV database conversion complete  I               Determining DTSS timezone rules from OpenVMS information...,  O               %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates [               %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configurationeZ               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER  .                       Summary of Configuration                   Node Information:  5                       Node Type:              ENDNODE ;                       Directory Services Chosen:      LOCAL ;                       Primary Directory Service:      LOCALy4                       Node Synonym:           NCLGUI3                       Phase IV Address:       4.260r2                       Phase IV Prefix:        49::E                       Autoconfiguration of Network Addresses: Enabled H                       Session Control Address Update Interval:        101                       Routing ESHello Timer:  600   "                Device Information:  *                       Device: EWA (TULIP):3                               Data Link name: EWA-0 ;                               Routing Circuit Name:   EWA-0Y  /         5-2 Using the FAST Configuration Optiona n  o      I                                       Using the FAST Configuration OptionsI                                5.1 Invoking the FAST Configuration Optionh    %                Transport Information:   B                       NSP Transport:                    ConfiguredA                          Maximum number of logical links:     200 @                          Maximum Transmit and Receive Window: 20B                          Maximum Receive Buffers:             4000  3                       Congestion Avoidance Disabledt  .                Event Dispatcher Configuration:  2                       Sinks:            local_sink4                       Outbound Streams: local_stream/                       Phase IV Relay:   Enabledt  V               * Do you want to apply this configuration?             [YES] :  <Return>  C               Answer YES to apply this configuration. If you answer C               NO, the procedure defaults to the BASIC configuration                procedure.  @               If you answer YES, the following message displays:  L               %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts  U                * Do you want to start the network?                  [YES] :  <Return>   F               Answer YES if you want to start the network and complete2               your system's network configuration.  F               If you want to postpone starting the network, answer NO.F               When you answer NO, the procedure displays the following               message:  R               ********************************************************************J               You have decided not to start the network. NET$CONFIGURE.COMP               cannot complete your system's network configuration since it needsM               the network to be partially started in order to perform certain R               operations.  As a result, your system may be left in an inconsistentO               state if you try to startup the network manually or if you decidee$               to reboot your system.  H               Once you are ready to start the network, please invoke theL               NET$CONFIGURE.COM procedure, choose menu Option 2 (Change nodeN               name/namespace name), and respond YES to starting the network soO               that the configuration procedure can finish your system's network                configuration.R               ********************************************************************  (               Network Startup Incomplete  I                                   Using the FAST Configuration Option 5-3  s  e      +         Using the FAST Configuration Optiona2         5.1 Invoking the FAST Configuration Option    B               Digital recommends that you answer YES and start the               network.  A               When you choose to start the network, the procedurei<               displays information similar to the following:  V                 Copyright (c) Digital Equipment Corporation 1996. All rights reserved.                 .                  .i                 .eX                 %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is                 RUNNING-MAJORq  _                 sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.   8                 Your default namespace nickname is ACME.  Z                 Your default namespace NSCTS is 08-00-2B-0D-2E-89-23-5B-15-9E-F1-85-95-00.                   Node 06                 at 1995-05-26-14:12:24.170-04:00I0.404  ]                 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMERr  )                 Directory Service: DECdns   I               You can ignore the Error - Node name lookup failure message                during startup.n  0                 Error - Node name lookup failure'                      ACME:.WABBIT.ELMER   /                 Number of nodes reported on:  0N  Y                 %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in then(                 DECdns directory service  2                 Directory Service: Local name file  0                 Error - Node name lookup failure!                      LOCAL:.ELMER   /                 Number of nodes reported on:  0i  Y                 %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the '                 LOCAL directory service_[                 %NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import file_  )                 Directory Service: DECdnsr  /         5-4 Using the FAST Configuration Option            I                                       Using the FAST Configuration OptioniI                                5.1 Invoking the FAST Configuration Option     Z                 Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT  -                 Number of nodes registered: 1 -                 Number of nodes modified:   0   Y                 %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in thea(                 DECdns directory service  2                 Directory Service: Local name file  Z                 Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT  -                 Number of nodes registered: 1t-                 Number of nodes modified:   0l  Y                 %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the '                 LOCAL directory servicee                   Node 06                 at 1995-05-26-14:13:25.980-04:00I0.411  J                 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to"                 ACME:.WABBIT.ELMER  K                 Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMERS6                 at 1995-05-26-14:13:35.360-04:00I0.411  O                 %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node   A                 Node 0 Session Control Backtranslation Softlink * 6                 at 1995-05-26-14:13:43.360-04:00I0.412  A                 Node 0 Session Control Backtranslation Softlink * 6                 at 1995-05-26-14:13:43.370-04:00I0.412  Y                 %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for nodeaW                 %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration_                 completed                  $   B               You have just completed the initial configuration of@               a DECnet-Plus for OpenVMS system. It should now be:               operational as an end system on the network.  B               See Figure 3-1 and Figure 3-2 to determine your nextH               step. According to the flowcharts, you have just completed.               configuring the base components.  I                                   Using the FAST Configuration Option 5-5  t  z      +         Using the FAST Configuration Option ?         5.2 Changing a Current DECnet-Plus System Configuration     ?         5.2 Changing a Current DECnet-Plus System Configuration   C               You can use the net$configure procedure to modify the G               current configuration. Depending on which menu option youoE               select, net$configure either modifies the configurationcI               automatically or produces modified NCL scripts that you can 7               use to modify the system's configuration.a  D               See Chapter 4 to determine whether you want to use theC               BASIC or ADVANCED configuration option to change yoursA               configuration. Refer to the DECnet-Plus for OpenVMShF               Applications Installation and Advanced Configuration forD               instructions on how to run the ADVANCED configuration.                                                                /         5-6 Using the FAST Configuration Optionl e  c                    I                                                                         6aI         _________________________________________________________________A  I                                      Using the BASIC Configuration Optioni    E               This chapter describes how to configure the DECnet-PlusiG               for OpenVMS base components using the BASIC configurationrI               option so that the system becomes a DECnet-Plus for OpenVMSt&               end system on a network.  I               The BASIC configuration option allows you to configure yourIG               system by answering a few questions and using the defaulte                answers on others.  H               If you have already configured the DECnet-Plus for OpenVMSG               software and you want to customize the configuration, seepD               Chapter 4 to determine if you want to use the BASIC or               ADVANCED option.  3         6.1 Invoking the BASIC Configuration Optione  G               To invoke the net$configure.com procedure using the BASICs@               configuration option, enter the following command:  0               $ @sys$manager:net$configure basic  #               The procedure starts:   Z               Copyright (c) Digital Equipment Corporation 1993, 1996. All rights reserved.  O                   DECnet-Plus for OpenVMS BASIC network configuration proceduren  R               This procedure will help you create or modify the management scriptsR               needed to operate DECnet on this machine. You may receive help aboutC               most questions by answering with a question mark '?'.   R               You have chosen the BASIC configuration option.  This option enablesS               you to quickly configure your system by answering a few questions and V               using most of the default answers.  If you would rather do some specificR               tailoring of your  system's network configuration, you should invokeK               NET$CONFIGURE.COM with the ADVANCED configuration option, ie: @                              @SYS$MANAGER:NET$CONFIGURE ADVANCED  L               * Do you want to continue?                             [YES] :  I                                  Using the BASIC Configuration Option 6-1a I  n      ,         Using the BASIC Configuration Option3         6.1 Invoking the BASIC Configuration Option     C               Press Return to continue with the BASIC configurationo               option.   G               The procedure informs you that this is the first time you I               are configuring your system to use DECnet-Plus for OpenVMS:e  I               %NET$CONFIGURE-I-SETUPNEW, setting up for new configuration_  H               If a Phase IV database exists on the system, the procedure-               displays the following message:   J               %NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found  I               You have the option of using the existing Phase IV database D               to generate the Network Control Language (NCL) scriptsE               and configure the system. If you do not want to use the D               existing Phase IV database to generate the NCL scriptsE               and configure the system, then net$configure configures C               the system based on your answers to the configuration                questions.  K               * Do you want to convert Phase IV database?           [YES] :   E               If you answer YES, the net$configure procedure uses thetI               system's existing Phase IV database to generate NCL scriptsn'               and configure the system.   D               If you answer NO, the net$configure procedure does notE               use the system's existing Phase IV database to generate C               NCL scripts and proceeds to ask all the configuration D               questions, starting with the directory services to useE               on the system. If you need more information to answer a H               question, you can type a question mark (?) at the prompts.E               Review the installation planning checklist in Chapter 2_                before continuing.  #         6.2 Directory Name Servicesi  I               DECnet-Plus provides access to the node name and addressingnC               information stored in one or more name services. ThisnE               release of DECnet-Plus supports the following directoryl               name services:  G               o  Local namespace - A discrete, nondistributed namespace_D                  that stores name and address information locally inH                  database files, the Local namespace replaces the DECdnsF                  Local Naming Option (LNO). It also has the ability toF                  hold 100,000 nodes, and can scale beyond that number.  0         6-2 Using the BASIC Configuration Option    .      I                                      Using the BASIC Configuration OptiongI                                               6.2 Directory Name Services     H                  The actual number of nodes that the Local namespace canD                  hold depends on the space available on your system.A                  For more detailed information on namespaces, see                   Section 7.1.1.p  E               o  DECdns distributed namespace - Digital's DistributedeC                  Name Service, DECdns is a distributed, global name B                  service. For more information, see Section 7.1.2.  G               o  Domain Name System - The Domain Name System (DNS/BIND)'C                  is supported for storage of IP addresses. For moref0                  information, see Section 7.1.3.  A               If you choose to enter more than one directory name G               service for your system, enter them in order of priority.hD               The ordering of this list is very important: the firstF               directory service entered in this list is considered theI               primary directory service to use on the system. The primaryIE               directory service is considered the first choice to usei@               when looking up naming information for the system.  F               Enter an ordered list of the directory services you wantH               to use on the system. If you enter more than one directory:               service, separate each service with a comma.  Y               * Enter the directory services to use on the system [LOCAL,DECDNS,DOMAIN] :            6.2.1 Node Full Name  A               The DECnet-Plus for OpenVMS configuration procedure G               net$configure.com prompts you for the system's full name.aF               You can enter a DECdns full name, a Local namespace fullC               name, a fully qualified host name for the Domain NameiC               System (DNS/BIND), or all three. For DECdns and LocalnE               namespace full names, you must specify a node full name D               that includes a namespace nickname (this complies withG               DECdns distributed namespace requirements). The full name E               format is the same for distributed namespaces and LocalO               namespaces.e  4               The full name uses the following form:  9               NamespaceNickname:.DirectoryPath.NodeObjectN  I               The following are the guidelines for selecting a full name:T  I               o  For DECdns and Local, the node full name must begin with I                  the namespace nickname and a colon (:). The nickname fornB                  the Local namespace is always LOCAL: (or local:).  I                                  Using the BASIC Configuration Option 6-3  N  D      ,         Using the BASIC Configuration Option#         6.2 Directory Name Servicesr    I               o  For DECdns and Local, the directory path must begin with                   a dot (.).   D               o  The full name can be up to 511 characters long: theD                  namespace nickname can be up to 255 characters, andD                  the directory path and node object can be up to 255                  characters.  I               o  The full name can be any combination of letters, digits,oG                  and certain punctuation characters from the ISO Latin- F                  1 character set. Some other characters are allowed asI                  long as they are enclosed in quotation marks. For a list F                  of all allowable characters, refer to the DECnet-Plus)                  DECdns Management guide.   D               o  For DNS/BIND, enter a fully qualified IP host name.  C               The following are some examples of suitable node full                names:  +               AU:.chemistry$lab.Sunil$Sethin6               XYZ_CORP:.sales.east_coast.BrianMacKrill;               Mbi:.MIS.Europe.Monaco_headquarters.F_Rivierai               local:.bryan"               smilee.mass.acme.edu  F                 ________________________ Note ________________________  @                 If you plan to use a Local namespace and you areD                 converting a Phase IV system to DECnet-Plus, DigitalB                 recommends that you use the system's Phase IV node?                 name in the DECnet-Plus full name (for example,S                 LOCAL:.PASTRY).y  F                 ______________________________________________________  E               You should plan node full names carefully and make surefC               they are unique within the namespace. If your network,D               administrator has not assigned a unique node full nameG               for your system, be sure to read the DECnet-Plus Planning F               Guide before you assign a node name for your system. For?               more information on name services, see Chapter 7.   F               At the prompt, enter a node full name for each directoryD               service chosen. The node full name is the name of yourH               system's node object in the directory service. It includesE               the namespace nickname and the full list of directoriesC  0         6-4 Using the BASIC Configuration Option '  e      I                                      Using the BASIC Configuration OptionrI                                               6.2 Directory Name Serviceso    D               leading to the node object name. Examples of node full               names include:  1                Local namespace -  LOCAL:.TomThumbe4                DECdns          -  ACME:.wabbit.Elmer7                Domain          -  elmer.wabbit.acme.edu   F               For the Local namespace, the namespace nickname LOCAL isG               prepended to the full name and is terminated with a coloneD               (:). The namespace nickname LOCAL means that the LocalE               namespace is used. The node object name must begin with*D               a dot (.), and no element of the name (namespace name,C               directory, or node object name) can be a null string.nE               Note that the namespace nickname LOCAL is reserved, andaH               indicates that the Local namespace is used on this system.D               For example, if you enter "Local,DECdns,Domain" at theH               previous prompt, you will be asked for a DECdns full name,H               a Local full name, and a fully qualified host name for DNS               /BIND.  P               * Enter the full name for directory service LOCAL   : LOCAL:.ELMER  V               * Enter the full name for directory service DECDNS  : ACME:.WABBIT.ELMER  Y               * Enter the fully qualified host name for DNS/BIND  : ELMER.WABBIT.ACME.EDUe  &         6.2.2 Specifying the Node Type  H               Prior to DECnet-Plus Version 7.1, DECnet-Plus systems wereC               end nodes. Dedicated routers on the network performed-D               routing functions for the end nodes as necessary. WithE               the Version 7.1 release, DECnet-Plus allows a system toTE               run integrated IS-IS, thus providing host-based routingE>               functionality. The default is to be an end node.  L               * What type of node (Endnode or Router)?           [ENDNODE] :  ,         6.2.3 Specifying Routing Information  G               This section only applies if your DECnet-Plus system is a                router.o  L               * Type of routing node (L1 or L2)?                      [L1] :  I               Enter L1 if your DECnet-Plus system will provide intra-area F               level 1 routing capability. Enter L2 if your DECnet-PlusH               system will provide inter-area level 2 routing capability.4               The default is to be a level 1 router.  I                                  Using the BASIC Configuration Option 6-5            ,         Using the BASIC Configuration Option#         6.2 Directory Name Servicesr             6.2.4 Node Synonym  B               The node synonym is an alphanumeric character stringF               between one and six characters long. The first characterI               must be an alphabetic character; after the first character, A               the string can contain either alphabetic or numeric                characters.   I               The node synonym is primarily a transition tool that allowsrD               you to use a Phase IV-style node name for your DECnet-E               Plus node. Other users can then find your node by usingsH               this synonym rather than your full name. If you were usingE               DECnet Phase IV, consider using your Phase IV node nameiC               as your synonym. The synonym is required for Phase IV C               applications that can only handle Phase IV-style nodebF               names. If your network has only DECnet-Plus or OSI (OpenG               Systems Interconnection) systems, you may not need a nodei               synonym.  E               The default node synonym is the first six characters of1D               the system's last simple name. The last simple name isB               the string that follows the last period of your fullE               name. For example, if you specify XYZ_CORP:.sales.east_ G               coast.BrianMacKrill as a node full name, the default nodeE                synonym is BrianM.  H               If this system had previously been running DECnet Phase IVI               software, then you should use the old Phase IV node name as I               the synonym. If this system is joining a DECnet network for F               the first time, you can use any name for the synonym, asG               long as it meets the criteria listed above, and is unique !               within the network.T  L               * What is the synonym name for this node?            [ELMER] :  C               For more information on node synonym directories, seer               Section 7.4.  =         6.2.5 Specifying a DECnet Phase IV-Compatible Addressr  B               If you want your system to communicate with Phase IVD               nodes, you must specify a Phase IV address and a PhaseG               IV prefix. These will be used to construct a DECnet Phaseh$               IV-compatible address.  0         6-6 Using the BASIC Configuration Option -         I                                      Using the BASIC Configuration OptionaI                                               6.2 Directory Name Servicese    C               A DECnet Phase IV-compatible address is a DECnet-Plus$I               address (NSAP - network service access point) that conformspE               to the Phase IV area and node limits; that is, the areaiF               number is from 1 to 63, and the node number is from 1 to               1023.s  H               If there are no Phase IV systems on your network or you doG               not want to communicate with Phase IV systems, you do not E               need a Phase IV-compatible address. Entering a Phase IV F               address of 0.0 at configuration time indicates that thisD               DECnet-Plus system will not have a Phase IV-compatibleD               address, and will not communicate with Phase IV nodes.  L               * Enter PhaseIV Address                              [15.27] :  I               Enter the Phase IV address you want to use, or enter 0.0 if A               you do not want to communicate with Phase IV nodes._  *         6.2.6 Specifying a Phase IV Prefix  H               The net$configure basic configuration option provides 49::I               as the default value for the Phase IV prefix. If you do nothF               enter a Phase IV-compatible address, you will not have a               Phase IV prefix.  +         6.2.7 Configuring Network Addresses   I               The net$configure basic configuration option autoconfiguresI*               one network address for you.            6.2.8 DNA Address Format  D               The net$configure basic configuration sets the routing8               characteristic DNA address format to TRUE.           6.3 Configuring Devices   G               The net$configure procedure checks for network devices on E               the system that are supported by net$configure and then I               configures them. If the procedure finds that you have WANDD D               or X.25 installed but not configured, you will see the$               following information:  N               You have installed wide area device support, but it has not been@               configured.  You may configure it now if you want.  N               * Do you want to configure Wide Area devices?          [YES] : NV               %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait  I                                  Using the BASIC Configuration Option 6-7            ,         Using the BASIC Configuration Option         6.3 Configuring Deviceso    )         6.3.1 Configuring an Alpha System'  G               For an Alpha system, the procedure displays the following                information:  L               DEC X.25 software has been installed on this system.  You have@               the option of configuring DECnet to run over X.25.  L               * Do you want to configure DECnet over X.25?            [NO] :  C               Answer YES if you want to configure DECnet over X.25.o  G               If you answer YES, you will see a list of choices for theF*               type of X.25 circuit to use:  *                    Types of X.25 circuits:  3                    [1] - X.25 Dynamic Assigned (DA)C2                    [2] - X.25 Static Incoming (IN)3                    [3] - X.25 Static Outgoing (OUT)i-                    [4] - X.25 Permanent (PVC)   N               * Which type of X.25 circuit do you want to use?             : 4L               * Routing Circuit Name to use?                   [X25-PVC-0] :L               * Template name?                                 [X25-PVC-0] :L               * Configure another X.25 routing circuit for DECnet?    [NO] :  E               Enter the number for the type of circuit you want, theneE               enter a routing circuit name and a template name to useCI               for that circuit. If you do not want to configure any other F               X.25 routing circuits, press Return for the default. TheG               configuration procedure continues with the next series of G               questions (such as time zone or transports, for example).i  H               If no devices are found on the Alpha system, the procedure,               displays the following prompt:  L               * Should a SYSMAN IO AUTO be executed?                       :  H               If you answer YES, the net$configure procedure invokes theF               SYSMAN IO AUTO command to find devices on the system. If?               you answer NO, there are no devices to configure.t      0         6-8 Using the BASIC Configuration Option           I                                      Using the BASIC Configuration Option I                                                   6.3 Configuring Devices     &         6.3.2 Configuring a VAX System  @               If you answer YES to the question, "Do you want toC               configure Wide Area devices?" and you are using a VAX G               system, the procedure displays the following information:   L               * Do you want to configure Wide Area devices?          [YES] :  D               Answer YES if you want to configure DECnet over P.S.I.  F               If you answer YES, the procedure displays the following:  <                  This is the Configuration Procedure for the<                  ===========================================  D                        VAX Wan Device Drivers for DECnet/OSI for VMSD                        =============================================  P                 The Wide Area Network Datalinks and Drivers are  a  prerequisiteP                 for  DECnet/OSI.  They  also  provide  synchronous  datalinks inB                 systems that do not use DECnet/OSI for networking.  P                 Access to DECnet/OSI datalinks (created by NCL) is  possible viaP                 the QIO interface to the WAN pseudo-driver, WANDRIVER.   LayeredP                 products  that use synchronous devices  do not  normally requireP                 programming  access to WANDRIVER.  For  further information, seeA                 the "DECnet/OSI for VMS WANDD Programming" guide.a  2               Do you wish to use WANDRIVER [N] ? y)               Will you use DEC HDLC [Y] ? D               Will you use LAPB/E (VAX P.S.I. requires LAPB/E) [Y] ?  T                 The DSV11 (Q-bus), DIV32 (Q-bus), DSB32 (BI-bus), DSF32 (MI-bus) andT                 DSW devices are soft-loadable. The WANDD startup procedure will load<                 the microcode for these devices if required.  R               Do you have any soft-loadable microcode devices on this system [N] ?@               Will you use the VAXft DSF32 device driver [N] ? y  P                 The  VAXft  DSF32  software  supports the  pairing  of  physicalP                 controllers to  provide  a fault-tolerant  configuration. Such aP                 pairing  is  called  a  Failover Set. The  DSF32 device does notP                 automatically create the failover sets, so you will need to pairD                 controllers using the Failover Set Manager software.  I                                  Using the BASIC Configuration Option 6-9.           ,         Using the BASIC Configuration Option         6.3 Configuring Devicesu    P                 This  management  software can be  invoked during system startupP                 from within the command procedure WANDD$STARTUP_SF.COM, which isP                 placed  in  the SYS$STARTUP  directory  by the  kit installationP                 procedure. If you want to have these Failover Sets automaticallyP                 configured  when  the system  starts up  you will need to modifyO                 WANDD$STARTUP_SF.COM to  include  Failover Set Manager commands !                 that you require.   E               Are you satisfied with the answers you have given [Y] ?   P                 If you have already started up the  WAN  Drivers  and  DatalinksP                 (that    is,    if    you    have   already   successfully   runP                 SYS$STARTUP:WANDD$STARTUP.COM  since  your   system   was   lastP                 booted),  then  you will need to reboot your system for your new-                 configuration to take effect.   V               %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please waitP               * Do you want to configure DECnet over X.25?            [NO] : yes  )                   Types of X.25 circuits:   2                   [1] - X.25 Dynamic Assigned (DA)1                   [2] - X.25 Static Incoming (IN)a2                   [3] - X.25 Static Outgoing (OUT),                   [4] - X.25 Permanent (PVC)  N               * Which type of X.25 circuit do you want to use?             : 1L               * Routing Circuit Name to use?                    [X25-DA-0] :L               * Template name?                                  [X25-DA-0] :L               * Filter name?                                    [X25-DA-0] :L               * Do you want to configure any reachable addresses?     [NO] :L               *  Configure another X.25 routing circuit for DECnet?   [NO] :  A               The procedure continues to ask for information. See G               Section 6.3.1 for the types of questions you will see and /               possible responses you can enter.   F               If no devices are found on the VAX system, the procedure,               displays the following prompt:  L               * Should a SYSGEN AUTOCONFIGURE ALL be executed?             :  D               If you answer YES, the net$configure procedure invokesE               the SYSGEN AUTOCONFIGURE ALL command to find devices onlC               the system. If you answer NO, there are no devices toh               configure.  1         6-10 Using the BASIC Configuration OptionM E  p      I                                      Using the BASIC Configuration OptioneI                                                6.4 Configuring Transports_    "         6.4 Configuring Transports  ?               Next, the NSP transport and the OSI transport areg               configured.t  F               The procedure displays the following message to indicate?               that the default OSI templates have been created:e  O               %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates_  E               The default OSI templates are used by the OSAK and FTAMlF               installation verification procedures (IVPs) for loopbackC               testing. You will not be able to use OSI applicationssE               to make connections to other OSI systems unless you usetG               the net$configure advanced configuration option to create H               additional OSI templates. You can do this at a later time.  6         6.5 Configuring Time Zone Differential Factors  @               The UTC (Coordinated Universal Time) is calculatedG               automatically by using the OpenVMS UTC, and the proceduree-               displays the following message:   I               Determining DTSS timezone rules from OpenVMS information...-  G               After the initial system configuration, you can choose to H               reconfigure the system's time zone rule (TZR) by selectingH               Option 5 in the top-level net$configure menu in either the8               BASIC or ADVANCED configuration procedure.  +         6.6 Configuring an Event Dispatcherc  F               The procedure then provides the default Event Dispatcher               configuration:  [               %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuratione  /         6.7 Configuring an Application Databasef  H               The procedure creates the DECnet-Plus default applicationsC               to include in the application database. The procedureTC               creates default user accounts for the CML, MAIL, VPM, G               MIRROR, and PHONE applications (no account is created forj               FAL):l  I                                 Using the BASIC Configuration Option 6-11  a         ,         Using the BASIC Configuration Option/         6.7 Configuring an Application Database     Z               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER[               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER Z               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER\               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER\               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER  B               o  CMIP Management Listener (CML) is the DECnet-PlusH                  management module that implements DNA Common ManagementH                  Information Protocol (DNA CMIP). CML provides access to                  CMIP.  @               o  MAIL allows users to send and receive messages.  F               o  VMScluster Performance Monitor (VPM) needs an accountG                  for your system to support the OpenVMS Monitor utilityb)                  command MONITOR CLUSTER.   B               o  MIRROR is needed for particular forms of loopback                  testing.n  D               o  PHONE allows users on the same or different OpenVMS6                  systems to communicate interactively.  '         6.8 Configuring a Cluster Alias   E               The following steps describe how to configure a clustere               alias.  >               1. If the node is a OpenVMS Cluster member or ifG                  net$configure finds an alias NCL script on the system, F                  the procedure prompts you to enter the full name of a                  cluster alias.n  N                   * Full name of Cluster Alias             : ACME:.WABBIT.HELP  H                  If you do not want the node to participate in a cluster%                  alias, press Return.a  H                  If you want the node to participate in a cluster alias,C                  specify the full name that uniquely identifies theaE                  cluster alias node (for example, ACME:.WABBIT.HELP).   E               2. If you entered a cluster alias full name in responseoC                  to the previous prompt, the procedure displays the "                  following prompt:  Y                  * Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) : 12.139   1         6-12 Using the BASIC Configuration OptionI o  e      I                                      Using the BASIC Configuration Option H                                          6.8 Configuring a Cluster Alias    F                  Do not use your address for the cluster alias. If youH                  are unsure which address to enter, consult your network                  manager.s  C                  Specify either the DECnet Phase IV node address or 8                  Ethernet physical address of the alias.  ?                  The Phase IV node address has the format area- :                  number.node-number (for example, 12.139).  D                  The Ethernet physical address has the format AA-00-F                  04-00-xx-xx, where xx-xx is calculated from the PhaseD                  IV node address. To determine the Ethernet physical-                  address, proceed as follows:s  D                  a. Convert the Phase IV node address to its decimal*                     equivalent as follows:  K                     (area-number * 1024) + node-number = decimal equivalent D                     (For example, (12 * 1024) + 139 = 12427 decimal)  G                  b. Convert the decimal node address to its hexadecimal I                     equivalent and reverse the order of the bytes to form:>                     the hexadecimal node address. For example:  N                     (12427 decimal = 308B hex, reversed = 8B30 hexnodeaddress)  C                  c. Incorporate the hexadecimal node address in thei%                     following format:,  .                     AA-00-04-00-hexnodeaddress4                     (For example, AA-00-04-00-8B-30)  H               3. If you entered a cluster alias full name and a Phase IVF                  address, the procedure displays the following prompt:  O                  * Selection weight for this cluster node [0 for satellites]  :   I                  The selection weight determines the number of sequentialIF                  incoming connects passed to this alias member node inG                  the round-robin sequence before proceeding to the next H                  member node in the sequence. A value of zero means thisH                  node is not eligible to receive incoming connections toI                  this alias address. Selection weight apportions incoming D                  alias connections according to the capacity of eachG                  alias member. For example, nodes with greater capacity E                  should have larger values of selection weight, while I                  OpenVMS Cluster satellites should generally have a valuedI                  of zero. Specify a nonzero selection weight if this nodeeE                  is connected locally to a dual-ported disk, or if it   I                                 Using the BASIC Configuration Option 6-13     n      ,         Using the BASIC Configuration Option'         6.8 Configuring a Cluster Alias     E                  will be serving any multihost disks, such as RFxx or G                  HSC-connected disks, to other cluster members. Digital 4                  recommends values between 0 and 10.  -               4. The procedure then displays:   =                                      Summary of Configurationh  "                   Node InformationL                          Directory Services Chosen:      DECDNS,LOCAL,DOMAIN?                          Primary Directory Service:      DECDNSoC                          DECdns Full name:       ACME:.WABBIT.ELMERs=                          Local Full name:        LOCAL:.ELMER (                          Fully QualifiedF                          Host name:              ELMER.WABBIT.ACME.EDU6                          Node Synonym:           ELMER6                          Phase IV Address:       15.275                          Phase IV Prefix:        49::eH                          Autoconfiguration of Network Addresses: Enabled  :                          Alias Name:     ACME:.WABBIT.HELP  %                   Device Information:y.                          Device: ESA0 (DESVA):9                                  Data Link name: CSMACD-0NA                                  Routing Circuit Name:   CSMACD-0a  (                   Transport Information:K                          NSP Transport:                          ConfiguredoG                            Maximum number of logical links:         200oF                            Maximum Transmit and Receive Window:     20H                            Maximum Receive Buffers:                 4000  K                          OSI Transport:                          Configured G                            Maximum number of logical links:         200yF                            Maximum Transmit and Receive Window:     20H                            Maximum Receive Buffers:                 4000  6                          Congestion Avoidance Disabled  1                   Event Dispatcher Configuration: 5                          Sinks:            local_sink 7                          Outbound Streams: local_stream[2                          Phase IV Relay:   Enabled  O                  * Do you want to generate NCL configuration scripts?   [YES] :   1         6-14 Using the BASIC Configuration Optiont    ?      I                                      Using the BASIC Configuration Option[H                                          6.8 Configuring a Cluster Alias    @                  Answer YES to accept the configuration you justE                  specified. The procedure automatically generates the H                  NCL scripts and then configures the system according to.                  the information you supplied.  O                  %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scriptsr  F                 ________________________ Note ________________________  F                 The net$configure procedure only provides checksums ofD                 those NCL management scripts it creates or modifies.B                 It does not provide checksums of user-modified NCL                 scripts.  F                 ______________________________________________________  =               5. The procedure displays the following prompt:u  N                   * Do you want to start the network?                  [YES] :  I                  Answer YES if you want to start the network and complete 5                  your system's network configuration.   I                  If you want to postpone starting the network, answer NO.tI                  When you answer NO, the procedure displays the followingi                  message:f  U                  ******************************************************************** M                  You have decided not to start the network. NET$CONFIGURE.COM S                  cannot complete your system's network configuration since it needsyP                  the network to be partially started in order to perform certainU                  operations.  As a result, your system may be left in an inconsistentpR                  state if you try to startup the network manually or if you decide'                  to reboot your system.=  K                  Once you are ready to start the network, please invoke therO                  NET$CONFIGURE.COM procedure, choose menu Option 2 (Change node=Q                  name/namespace name), and respond YES to starting the network so R                  that the configuration procedure can finish your system's network                  configuration.mU                  ********************************************************************t  +                  Network Startup Incomplete   E                  Digital recommends that you answer YES and start thed                  network.   I                                 Using the BASIC Configuration Option 6-15a n  a      ,         Using the BASIC Configuration Option'         6.8 Configuring a Cluster AliasA    D               6. When you choose to start the network, the procedure?                  displays information similar to the following:i  Y                    Copyright (c) Digital Equipment Corporation 1995. All rights reserved.V                    .                    .                    .[                    %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status isc                     RUNNING-MAJOR  b                    sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.  ;                    Your default namespace nickname is ACME.   ]                    Your default namespace NSCTS is 08-00-2B-0D-2E-89-23-5B-15-9E-F1-85-95-00.r                      Node 0n9                    at 1995-05-26-14:12:24.170-04:00I0.404e  `                    %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER  ,                    Directory Service: DECdns  D               7. You can ignore the Error - Node name lookup failure(                  message during startup.  3                    Error - Node name lookup failureo*                         ACME:.WABBIT.ELMER  2                    Number of nodes reported on:  0  \                    %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the+                    DECdns directory servicel  5                    Directory Service: Local name filea  3                    Error - Node name lookup failuree$                         LOCAL:.ELMER  2                    Number of nodes reported on:  0  \                    %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the*                    LOCAL directory service^                    %NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import file  ,                    Directory Service: DECdns  ]                    Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT   1         6-16 Using the BASIC Configuration Optiono    s      I                                      Using the BASIC Configuration OptionsH                                          6.8 Configuring a Cluster Alias    0                    Number of nodes registered: 10                    Number of nodes modified:   0  \                    %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the+                    DECdns directory servicem  5                    Directory Service: Local name fileo  ]                    Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXTa  0                    Number of nodes registered: 10                    Number of nodes modified:   0  \                    %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the*                    LOCAL directory service                      Node 0r9                    at 1995-05-26-14:13:25.980-04:00I0.411   M                    %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to %                    ACME:.WABBIT.ELMER   N                    Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMER9                    at 1995-05-26-14:13:35.360-04:00I0.411   R                    %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node  D                    Node 0 Session Control Backtranslation Softlink *9                    at 1995-05-26-14:13:43.360-04:00I0.412   D                    Node 0 Session Control Backtranslation Softlink *9                    at 1995-05-26-14:13:43.370-04:00I0.412k  \                    %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for nodeZ                    %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration                    completed                    $  B               You have just completed the initial configuration of@               a DECnet-Plus for OpenVMS system. It should now be:               operational as an end system on the network.  B               See Figure 3-1 and Figure 3-2 to determine your nextH               step. According to the flowcharts, you have just completed.               configuring the base components.  I                                 Using the BASIC Configuration Option 6-17E I  P      ,         Using the BASIC Configuration Option?         6.9 Changing a Current DECnet-Plus System Configuration     ?         6.9 Changing a Current DECnet-Plus System Configuration   C               You can use the net$configure procedure to modify the G               current configuration. Depending on which menu option you E               select, net$configure either modifies the configuration I               automatically or produces modified NCL scripts that you can 7               use to modify the system's configuration.   D               See Chapter 4 to determine whether you want to use theD               FAST, BASIC or ADVANCED configuration option to changeF               your configuration. Refer to the DECnet-Plus for OpenVMSF               Applications Installation and Advanced Configuration forD               instructions on how to run the ADVANCED configuration.                                                                1         6-18 Using the BASIC Configuration Option  h  t                    I                                                                         7tI         _________________________________________________________________   I                                                    Managing Name ServicesD    G               If this is the first time you are configuring the DECnet-fG               Plus for OpenVMS software on your system, the informationhF               in this chapter further explains some of the topics that<               appear as you run the configuration procedure.  #         7.1 Names Services Overview   E               While configuring DECnet-Plus, the system administratorjC               specifies one or more of the following directory nameAG               services to use on the node: the Local namespace, DECdns,fG               or Domain Name System (for DNS/BIND). See Section 6.2 for                more information.A  G               o  Local namespace - A discrete, nondistributed namespaceCD                  that stores name and address information locally inH                  database files. DECnet-Plus includes a Local namespace.  ?               o  DECdns - Digital's Distributed Name Service, ah2                  distributed, global name service.  G               o  Domain Name System - The Domain Name System (DNS/BIND) 7                  supported for storage of IP addresses.   I               For more information on name services, refer to the DECnet-D"               Plus Planning Guide.  !         7.1.1 The Local NamespaceM  D               DECnet-Plus includes a Local namespace, independent ofC               DECdns, that is designed to scale to at least 100,000e               nodes.  I               The Local namespace is a discrete, nondistributed namespaceMF               that exists on a single node and provides that node withC               a local database of name and address information. The H               prefix LOCAL: (or local:) is reserved to indicate that theH               information for the node is stored in the Local namespace.  I                                                Managing Name Services 7-1p e  i               Managing Name Services#         7.1 Names Services Overview     F               DECnet-Plus recognizes that when a node full name beginsC               with LOCAL:, information for that node is stored in auH               Local namespace. The following are typical node full namesH               properly formatted for the Local namespace: LOCAL:.xyz.abc!               and local:.maximum.o  @               Unlike DECdns, the Local namespace does not employB               backtranslation directories for address-to-node-name               translation.  *         7.1.1.1 Creating a Local Namespace  <               If you want to create a Local namespace, enterF               LOCAL:.DirectoryPath.NodeObject at the following prompt:  @               * Enter the full name for directory service LOCAL:  F               The directory path identifies the namespace subdirectoryB               (if any). The node object is the system's node name.  ,         7.1.1.2 Managing the Local Namespace  C               The DECdns distributed namespace is not a requirement F               for DECnet-Plus and the Local namespace is not dependentD               on DECdns. However, the DECdns clerk software is stillF               required on each node. You cannot use the DECdns ControlG               Program (DNSCP) to manage information stored in the Local H               namespace. Instead, use decnet_register to manage the nodeH               name and address information stored in your namespace. TheF               decnet_register tool is described in the DECnet-Plus for/               OpenVMS Network Management guide.9  ;         7.1.2 The Digital Distributed Name Service (DECdns)r  D               DECdns is a networkwide service that makes it possibleE               to use network resources without knowing their physical E               location. Users and applications can assign DECnet-Plus E               names to resources such as nodes. The creator of a name C               also supplies other relevant information, such as the2I               resource's network address, for DECdns to store. Users then1I               need to remember only the name, and DECdns acts as a lookup E               service, providing the rest of the data when necessary.v      "         7-2 Managing Name Services           I                                                    Managing Name ServicesdI                                               7.1 Names Services Overviewn    (         7.1.2.1 Creating a New Namespace  G               You need to create a new DECdns namespace only if you are-G               configuring the first DECdns server for the network or if F               you are creating an additional namespace. If you alreadyF               have a DECdns namespace, you do not need to create a newG               namespace to be able to run DECnet-Plus. However, if thisiH               is the first system in a network where no namespace existsH               and you do not intend to use the Local namespace, you must7               create (and populate) a DECdns namespace.o  @               If you are unsure whether you need to create a newF               namespace or configure your system as a server, see yourH               network manager. For information about namespace planning,6               refer to the DECnet-Plus Planning Guide.  G               To create a new namespace while configuring a DECnet-Plusm!               for OpenVMS system:t  D               o  The DECdns server software must be installed on the                  system.  G               o  DECdns must be specified as one of the naming services *                  configured on the system.  H               When you create a namespace, you need a namespace nicknameG               and clearinghouse name. The namespace nickname is part ofrI               the full name of every subsequent system in the network andiF               should be unique to your network. The namespace nicknameH               that you specify becomes the actual name of the namespace.H               A clearinghouse is a collection of directory replicas thatG               contains the names and addresses of objects (for example,a&               servers, clerks, files).  :               Digital recommends that you create namespaceB               directories before using the configuration procedureG               (net$configure.com) to create the namespace. Follow these 4               steps to create namespace directories:  I               1. Invoke decnet_register and select option 10 ("Manage theC%                  directory service").l  D               2. Follow directions. Be sure to specify DECdns as theD                  directory service to manage (the Local namespace isD                  the default). The decnet_register procedure invokesE                  sys$manager:decnet_register_decdns.com to create thec'                  namespace directories.d  I                                                Managing Name Services 7-3     e               Managing Name Services#         7.1 Names Services Overview     E               3. When finished, invoke the configuration procedure to *                  create the new namespace.  G               For more information on decnet_register, refer to DECnet-a2               Plus for OpenVMS Network Management.  +         7.1.2.2 Creating a DECdns Namespacel  H               If you select DECdns as a directory service, net$configure<               prompts you for the full name you want to use:  [               * Enter the full name for directory service DECDNS:   new_ns:.mrv042 <Return>C  G               If this is a new namespace, net$configure prompts you for I               more information once the configuration procedure completes G               and you have started the network. The startup information /               will be similar to the following:a  _               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-                MAJOR   5               The namespace you specified was NEW_NS.[  V               %DNS-E-NOMATNS, The specified namespace is not being served on your LAN.;                       please choose from the following list4                  [1]  BB_NSn                [2]  DOMAIN                [3]  LOCAL                 [4]  X500  (                [0]  - Reject this list -  7                Pick a number from the list: 0  <Return>   E               Because you are creating a new namespace, the namespace I               you specified at the prompt, "What is the full name of thisLF               node?" does not appear in the list. To continue, enter 02               and press Return to reject the list.  U                      If you are installing DECnet-Plus for OpenVMS for the first time_P                      and you want to create a namespace, type Y.  If you want toH                      attempt a WAN connection to a remote DECdns server,>                      type N (default) at the following prompt:  R               Do you want to proceed with creating a new namespace [n]: y <Return>  "         7-4 Managing Name Services _  _      I                                                    Managing Name Services I                                               7.1 Names Services Overview     A               At this point, the configuration procedure needs to F               determine whether you intend to configure your system asG               a clerk on a WAN (connect to an off-LAN server) or create F               a new namespace. Since you cannot create a new namespaceE               unless you have installed DECdns server software on the*B               system, the procedure first verifies that the server*               software has been installed.  D               If you want to create a new namespace, type YES at theH               prompt and press Return. The procedure continues promptingC               you for information necessary to create the namespacelE               and the appropriate directories. The procedure displaysiI               information about the namespace, the directories, and other G               network parameters, then tells you when the configurationt               is complete.  Q                      Your next input will determine the name of the clearinghouse O                      in your namespace new_ns.  Enter the clearinghouse name as ?                      alphanumeric and/or underscore characters.u  T               Enter a simple name for the clearinghouse: .mrv042_new_ns_ch  <Return>                 Node 02               at 1995-04-06-15:49:35.420-04:00Iinf  0               Creating DECdns Server process ...K               %RUN-S-PROC_ID, identification of created process is 00000122   8               Your default namespace nickname is new_ns.                 Node 02               at 1995-04-06-15:49:42.100-04:00Iinf  J               %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries                 Node 02               at 1995-04-06-15:49:47.180-04:00Iinf  W               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to new_ns:.mrv042nM               %NET$CONFIGURE-I-NEWNAMESPACE, a new namespace has been created   U               %NET$CONFIGURE-I-ADDGROUP, adding .WorldRead_Group to the new namespacer  7               Create the initial namespace directories. H               Press Ctrl/Z at any question to cancel the initialization.  O               * Phase IV prefix value [afi:idi:predsp, Def=47:0027:]:  <Return> H               * Maximum Phase IV area to use [1-63, Def=63]: 2  <Return>  I                                                Managing Name Services 7-5  5  -               Managing Name Services#         7.1 Names Services OverviewA    Z               The DECdns namespace groups and directories will now be created.  This mightP               take up to 6 minutes or more, depending on the speed of the DECdnsE               server system and the amount of traffic on the network.   7               Creating the NEW_NS:.DNA_Registrar group.EA               Creating the NEW_NS:.DNA_BackTranslation directory. J               Creating the NEW_NS:.DNA_BackTranslation.%X470027 directory.Q               Creating the NEW_NS:.DNA_BackTranslation.%X470027.%X0001 directory.cQ               Creating the NEW_NS:.DNA_BackTranslation.%X470027.%X0002 directory.r=               Creating the NEW_NS:.DNA_NodeSynonym directory.ND               Creating the NEW_NS:.DTSS_GlobalTimeServers directory.  I               DECdns namespace initialization for DECnet use is complete.L  U               If this is the first time you have initialized the namespace for DECnete9               use, use SYS$SYSTEM:DECNET_REGISTER.EXE to:y  T                 - Create a command file to automatically register previously definedP                   Phase IV nodes.  Execute this command file before you manuallyP                   register any other nodes using SYS$SYSTEM:DECNET_REGISTER.EXE.  Z                 - Create any directories you need for node names that should be registeredZ                   immediately, according to your namespace design.  This includes the node/                   you are currently running on.   \                 - Be sure to add backtranslation directories for any non PhaseIV areas/IPDs.\                   Failure to do so will lead to Backtranslation Failures.  Once you've addedT                   the necessary backtranslation directories, you may need to use theK                   ncl flush session control naming cache entry "*" command.   V                 - Change the local node's registered name from its default name to itsX                   final full name.  The local node will be registered as a Phase IV nodeU                   with a default name when you execute the Phase IV node registrationE%                   command file above.   Y                 - Change the currently registered names of other nodes from their defaultnZ                   names to their final full names when appropriate (for example, when they<                   are upgraded to run DECnet-Plus software).  @               Continue to use SYS$SYSTEM:DECNET_REGISTER.EXE to:  Y                 - Create any additional directories you need for node names, as new nodes 0                   are brought up on the network.  K                 - Register new nodes as they are brought up on the network.   P                 - Add members to the NEW_NS:.DNA_Registrar access control group.  F               Additionally, you can use the DECdns control utility to:  "         7-6 Managing Name Services c  l      I                                                    Managing Name ServicesoI                                               7.1 Names Services Overviewo    V                 -  Add specific access control to individual directories, objects, and                    soft links.  2                 -  Create replicas of directories.  )               The following were created:   5                    Group:       NEW_NS:.DNA_Registrar ;                    Directory:   NEW_NS:.DNA_BackTranslation D                    Directory:   NEW_NS:.DNA_BackTranslation.%X470027F                    Directories: NEW_NS:.DNA_BackTranslation.%X470027.*7                    Directory:   NEW_NS:.DNA_NodeSynonym >                    Directory:   NEW_NS:.DTSS_GlobalTimeServers  S               %NET$CONFIGURE-I-CREATEINITDIR, created initial namespace directoriese  1               Registering the node NEW_NS:.mrv042 #                 Type is DECnet-Pluse!                 Synonym is MRV042   W               %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in theo'               !NEW_NS directory service                  Node 02               at 1995-04-06-15:50:29.390-04:00Iinf  W               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to new_ns:.mrv042I  ?                       .               .                       .o?                       .               .                       . ?                       .               .                       .e?                       .               .                       . ?                       .               .                       .t  L               %NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded_               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-t               ALLm_               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completedn            7.1.3 Domain Name System  B               Refer to your BIND server documentation for specificE               installation and configuration instructions. For a listeE               of supported vendors, see Section 1.4.1.1. Any properlyiI               constructed DNS/BIND node name is supported by DECnet-Plus.m  I                                                Managing Name Services 7-7                     Managing Name Services#         7.1 Names Services Overview     "         7.1.4 Namespace Management  B               DECnet-Plus includes a new in-memory naming cache toD               improve performance of name and address resolution forG               all supported name services. Refer to the DECnet-Plus for D               OpenVMS Network Management guide for more information.  I               DECnet-Plus includes several new features to ease namespace C               management including decnet_register (a new namespacesD               management tool), several new Network Control LanguageI               (NCL) commands, and Common Trace Facility (CTF) support for :               monitoring node name and address resolution.  C               The decnet_register tool, an executable image locatediB               in SYS$SYSTEM:, centralizes and simplifies namespaceD               management tasks by replacing functionality previouslyB               provided by both the decnet_dns_register and decnet_D               loc_register command procedures, which were located inH               SYS$MANAGER:. The decnet_register tool manages informationG               in both the DECdns distributed name service and the LocaleH               namespace. The decnet_register manage command assists withH               setting up tasks for the DECdns name service. For example,E               it creates namespace directories and access groups, andnG               enables autoregistration. Refer to the section on decnet_ H               register in the DECnet-Plus for OpenVMS Network Management)               guide for more information.y  $         7.2 Name Service Search Path  A               The name service search path applies systemwide andeE               allows DECnet-Plus to search a list of name services intG               a predetermined order when looking up names or addressing D               information. The search path includes naming templatesI               that tell DECnet-Plus how to interpret any abbreviated nodeO%               names entered by users.   F               The ordering of the name services is very important. TheC               first name service listed is the primary name service C               to use on the system. The primary name service is the.D               first choice used when looking up names and addressingE               information. The remaining name services listed are the 9               secondary name services used on the system.n  G               The search path contains a list of name service keywords,aA               each followed by a naming template that specifies aDF               "defaulting rule" so users can enter shorter node names.  "         7-8 Managing Name Services           I                                                    Managing Name Services I                                              7.2 Name Service Search Path     5         7.2.1 Configuring the Search Path Information   H               During DECnet-Plus configuration, the system administratorF               uses net$configure.com to set up one, two, or three name$               services on each node.  H               From the information provided by the system administrator,C               net$configure creates NET$SEARCHPATH_STARTUP.NCL, themD               standard search path NCL startup script which containsD               the name service search path information for the node.  C               The system administrator supplies one or two properly G               formatted DECnet-Plus node full names (in the case of thenF               Local namespace and the DECdns distributed name service)I               and one fully qualified host name for DNS/BIND (if DNS/BIND )               is to be used on the node)..  G               The first full name is specified in the proper format for I               the name service to be searched first. The second and third H               node names are properly formatted for the name services to*               be searched second and last.  F               If more than one name service is to be used on the node,C               the name services are searched in the order specifiednE               by the system administrator. For example, if the systemoF               administrator specifies Local, DECdns and Domain for theH               name services to use on the system, the Local namespace is@               searched before the DECdns namespace and DNS/BIND.  D               The following configuration example illustrates how toE               upgrade to DECnet-Plus Version 7.1 and use the new namenC               service access features. Invoke net$configure.com anduF               select Option 2 ("Change node name/namespace name"). The,               following prompt is displayed:  X               * Enter the directory services to use on the system [LOCAL,DECDNS,DOMAIN]:  G               At the prompt, you can choose the following name servicesiE               for the system: LOCAL, DECDNS, and DOMAIN. If you enteryI               more than one name service, separate each name with commas.a  F               For example, entering DECDNS,LOCAL,DOMAIN at the prompt,"               means the following:  E               o  You want to use the name services DECdns, Local, ande                  DNS/BIND.  4               o  The primary name service is DECdns.  I                                                Managing Name Services 7-9t                    Managing Name Services$         7.2 Name Service Search Path    G               o  The secondary name services are Local and DNS/BIND, inr                  that order.  F                 ________________________ Note ________________________  F                 If your node is also a DECdns server, the primary name'                 service must be DECdns.   F                 ______________________________________________________  /         7.2.1.1 Naming Search Path in a Cluster   C               All members in a cluster should have identical naming D               search paths configured. This will help to ensure thatC               nodes are recognized in the various services you have                identified.r  A               For example, if you receive mail on one node in the H               cluster, the "from" node name would be LOCAL:.NODE::SMITH.E               If you attempt to reply to this node from a node in thevE               cluster that does not have Local configured, the systema8               would indicate that there is no such node.  4         7.2.2 Displaying the Search Path Information  =               The system maintains two separate search paths:M  G               o  One search path supports forward translation or naming 4                  (node-name-to-address translation).  B                  $ mcr ncl show session control naming search path  F               o  Another separate search path supports backtranslation4                  (address-to-node-name translation).  K                  $ mcr ncl show session control backtranslation search pathh  F               Refer to DECnet-Plus OpenVMS Network Management for more               information.  3         7.2.3 Modifying the Search Path Informationg  D               Digital recommends that you rerun net$configure.com toI               revise the standard search path NCL script (NET$SEARCHPATH_aE               STARTUP.NCL) whenever it is necessary to reorder access F               to the name services on the node. To modify the standardG               search path startup script, run net$configure.com and use ;               Option 2 ("Change node name/namespace name").   #         7-10 Managing Name Services]    e      I                                                    Managing Name Services I                                              7.2 Name Service Search Path     F                 ________________________ Note ________________________  F                 Whenever you directly edit an existing NET$SEARCHPATH_?                 STARTUP.NCL script, or when you use the NCL setIB                 command to change the script (rather than changing@                 the script by rerunning net$configure.com), your@                 edits are overwritten by any new NET$SEARCHPATH_@                 STARTUP.NCL scripts you subsequently generate by,                 rerunning net$configure.com.  F                 ______________________________________________________  =         7.2.4 Creating a Site-Specific Search Path NCL Script   I               Digital recommends that you allow net$configure.com (and in H               some cases net$startup.com) to create and use the standardB               NCL search path script (NET$SEARCHPATH_STARTUP.NCL).  H               However, if you need to make site-specific changes to yourF               search path NCL script and you do not want net$configureH               to overwrite these changes, you can create a site-specificD               search path NCL script by renaming the standard searchI               path script (NET$SEARCHPATH_STARTUP.NCL) to NET$SEARCHPATH_n@               LOCAL.NCL and making your changes to the new file.  D               For example, you might want to use the NCL set commandG               described in Section 7.2.6 to create site-specific namingh4               templates in NET$SEARCHPATH_LOCAL.NCL.  H               The net$configure.com and net$startup.com procedures checkD               for the presence of a site-specific search path scriptH               (NET$SEARCHPATH_LOCAL.NCL) on the node. If NET$SEARCHPATH_H               LOCAL.NCL is present on the node, it is invoked instead ofH               the standard script. A message similar to the following is               displayed:  O                  **************************************************************mL                  A site-specific searchpath NCL script has been found on theL                  system (SYS$SYSROOT:[SYSMGR]NET$SEARCHPATH_LOCAL.NCL;). TheH                  configuration procedure will use this script to set theK                  searchpath instead of using the standard searchpath script O                  that is created by NET$CONFIGURE (NET$SEARCHPATH_STARTUP.NCL).0O                  **************************************************************sP               %NET$CONFIGURE-I-SITESEARCHPATH, invoking site-specific searchpath+                  NCL script found on systeme  I                                               Managing Name Services 7-11A P  ,               Managing Name Services$         7.2 Name Service Search Path    E               The net$configure.com and net$startup.com procedures doeB               not modify the site-specific search path NCL script;F               rather, they invoke the site-specific search path scriptC               as it currently exists. Therefore, when using a site-aG               specific search path NCL script, you must modify it prior F               to invoking net$configure.com whenever you change any of5               the following name service information:v  =               o  The number of name services used on the node   @               o  The order of the name services used on the node  <               o  The specific name services used on the node  5         7.2.5 Using the Search Path to Ease Migrationn  F               A search path can be used to simplify migration from oneC               name service to another. The system administrator can F               create a search path designating the currently used nameH               service as the primary name service (to be searched first)D               and the new name service as the secondary name serviceF               (to be searched second after the primary name service is               searched).  G               As the secondary name service becomes populated with nodeEF               and addressing information, the system administrator canH               rerun net$configure.com and select Option 2 to reverse theE               positions of the name services in the search path. This H               causes the current secondary service to become primary, toD               be searched first for node and addressing information.  )         7.2.6 Setting Up Naming Templatesa  E               In each template, the user-supplied portion of the name F               (usually the node's terminating name or rightmost simpleF               name) is indicated with an asterisk (*). For example, ifH               the DECdns template is: "ABCDE:.xyz.*" and a user suppliesH               the name fin, then the following full name: ABCDE:.xyz.finI               is looked up in namespace ABCDE in the DECdns name service.n  E               You should specify only one asterisk per template. OnlykH               the first occurrence of an asterisk (*) in the template isE               substituted with the user-supplied name. Any additional A               asterisks are passed to the name service as part ofiC               the full name. When you specify a template without aneI               asterisk, the template string is passed to the name serviceu               unchanged.  #         7-12 Managing Name Servicese o         I                                                    Managing Name ServiceshI                                              7.2 Name Service Search Pathr    D               If the user-supplied name should be passed to the nameD               service as entered by the user, the template should be(               specified as follows: "*".  C               DECnet-Plus provides an NCL set command for modifying A               the naming templates associated with the naming andeB               backtranslation search paths. Do not use the NCL setE               command to modify aspects of the search path other than.#               the naming templates.a  C               The following NET$SEARCHPATH_LOCAL.NCL script createscF               typical naming and backtranslation search paths. In thisB               script ABCDE represents the namespace nickname. Your@               namespace nickname will appear in your NCL script:  =               SET NODE 0 SESSION CONTROL NAMING SEARCH PATH - E                       ([DIRECTORY SERVICE = LOCAL, TEMPLATE = "*"], -eJ                       [DIRECTORY SERVICE = LOCAL, TEMPLATE = "local:*"], -K                       [DIRECTORY SERVICE = LOCAL, TEMPLATE = "LOCAL:.*"], -aE                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "*"], -tK                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:*"], -7P                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:.xyz.*"], -`                       [DIRECTORY SERVICE = DECDNS_SYNONYM, TEMPLATE = "ABCDE:.DNA_NodeSynonym.*"                       ], -E                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*"], - Q                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*.xyz.ABCDE.com"])NC                       SET NODE 0 SESSION CONTROL BACK SEARCH PATH -hD                       ([DIRECTORY SERVICE = LOCAL, TEMPLATE = ""], -^                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:.DNA_BackTranslation"], -B                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = ""])           7.3 Domain Synonyms   D               Support for the Domain Name System (DNS/BIND) providesD               for the use of node synonyms. This allows for backwardH               compatibility with older applications that cannot use long               domain names.   H               There are two ways to configure node synonyms for use with               DNS/BIND:.  I               o  By constructing an appropriate set of naming search patho                  templates  *               o  By defining local aliases  I                                               Managing Name Services 7-13                     Managing Name Services         7.3 Domain Synonyms     E         7.3.1 Search Path Naming Template Support for Domain Synonymss  C               You can provide synonym support for entire domains by G               constructing an appropriate set of search path templates.uH               Note that excessively long search paths (search paths withE               many entries) can increase the time it takes to look upcH               node addresses. See Section 7.2 for general information on(               name service search paths.  F               Entering the following NCL command sets up a search path*               for a system using DNS/BIND:  S                $ mcr ncl set session control naming search path =                 -wS                    { [Directory Service = Domain, Template = "*"],                -rS                      [Directory Service = Domain, Template = "*.finbar.com"],     -rS                      [Directory Service = Domain, Template = "*.abc.finbar.com"], -aQ                      [Directory Service = Domain, Template = "*.xyz.finbar.com"]}   G               This NCL command results in the following DNS/BIND naming                templates:                   *e                 *.finbar.com                  *.abc.finbar.com                  *.xyz.finbar.com  >               When DECnet-Plus receives a connection from nodeD               koi.abc.finbar.com, it determines that koi is a usableI               synonym for this node, and DECnet-Plus will return the namehI               koi to applications that require Phase IV style node names.s  D               Using search path naming templates for synonym supportG               allows the user to enter any of the following node names:s?               koi, koi.abc, or koi.abc.finbar.com for node koi.t           7.3.2 Local Aliasesc  H               Another way to define a node synonym for a particular nodeC               is by adding DNS/BIND alias names to the local host's E               database. The following is an example using Digital TCP '               /IP Services for OpenVMS:   M               $ ucx set host koi.abc.finbar.com/address=aa.bb.cc.dd/alias=koiD  =               DECnet-Plus now returns the node synonym koi to B               applications that require Phase IV-style node names.  #         7-14 Managing Name Servicese a  g      I                                                    Managing Name ServicesnI                                              7.4 Node Synonym Directorieso    $         7.4 Node Synonym Directories  E               The default node synonym directory is .DNA_NodeSynonym. D               If you plan to use a node synonym directory other thanA               this default directory, you must define the logical F               name DECNET_MIGRATE_DIR_SYNONYM to the synonym directoryC               name you want to use in sys$manager:net$logicals.com. @               (If you do not have a sys$manager:net$logicals.com@               procedure on your system, you can create one using@               sys$manager:net$logicals.template.) This makes theH               definition permanent (that is, it will not be deleted when%               you reboot the system).n  :         7.4.1 Defining an Alternate Node Synonym Directory  B               Use the following format to define an alternate node                synonym directory:  F               $ define decnet_migrate_dir_synonym "alt-directory-name"  G               If you use a synonym directory name that includes special H               characters or three or more dots, the system might produceI               an error. To avoid this, enclose the synonym directory nameH%               in quotes. For example:t  K               $ define/system decnet_migrate_dir_synonym ".ch.noun.synonym"r  G               The net$configure procedure needs this logical name to benI               defined at all times if you wish to use a synonym directory I               other than .DNA_NodeSynonym. Be sure to add this definition F               to net$logicals.com to ensure that the definition of the2               synonym directory will be permanent.  *         7.4.2 When to Use the Logical Name  I               You can use the logical name described in Section 7.4.1 for D               either the BASIC or the ADVANCED configuration option.  E               You must define this logical name before you use any of #               following procedures:   "                  net$configure.com$                  decnet_register.exe#                  decnet_migrate.exei  I                                               Managing Name Services 7-15e f  e               Managing Name Services$         7.4 Node Synonym Directories    I               If synonym lookup fails in the namespace, the software does #               one of the following:d  E               o  The startup procedure defines SYS$NODE, SYS$CLUSTER_xI                  NODE, or both to be the first six characters of the lastaH                  simple name of the respective node full name or cluster                  full name.   G               o  The configuration procedure defines SYS$NODE to be theoI                  node synonym name that was entered during configuration.s  E               The system displays a message that it has redefined thep               logical names.  A         7.5 Using a DNS Version 1 Namespace with DECdns Version 2M  G               If you are already using a namespace created with Version E               1 of the VAX Distributed Name Service (DNS) (running onDE               DECnet Phase IV), you can continue to use the namespace F               when you upgrade your networking software to DECnet-PlusE               for OpenVMS. However, because of differences in the way C               that DNS Version 1 and DECdns Version 2 handle accesseD               control, you must prepare your DNS Version 1 namespaceF               for use by DECnet-Plus. DNS Version 1 and DECdns VersionD               2 interpret principal specifications in access control)               entries (ACEs) differently._  A               In DNS Version 1, servers recognize principals onlyvB               in the form nodename::username. In DECdns Version 2,@               servers recognize principals primarily in the formH               nodename.username. For DECdns Version 2 clerks and serversC               to interpret and process existing DNS Version 1-styleeI               access control entries in the namespace, you need to createrD               a backtranslation directory (.DNA_BackTranslation) andE               a node synonym directory (.DNA_NodeSynonym) in the roothF               directory of the namespace. You must then populate theseG               directories by registering all the nodes participating inh&               the Version 1 namespace.              #         7-16 Managing Name Serviceso    i      I                                                    Managing Name ServicesrI                 7.5 Using a DNS Version 1 Namespace with DECdns Version 2     C         7.5.1 Preparing a DNS Version 1 Namespace for Use by DECdns                Version 2m  G               To prepare a namespace created with DNS Version 1 for useo1               by DECnet-Plus, follow these steps:p  E               1. Install and configure DECnet-Plus for OpenVMS on anynI                  node in your namespace that is not currently functioningaC                  as a DNS Version 1 server. Configure the node as aVD                  DECdns Version 2 clerk. See Chapter 3 and Chapter 5H                  in this book if you plan to use the BASIC configurationD                  option, or the DECnet-Plus for OpenVMS ApplicationsE                  Installation and Advanced Configuration guide if you.?                  plan to use the ADVANCED configuration option.o  E               2. From any node running DNS Version 1 server software,rH                  use the DNS Version 1 control program (DNS$CONTROL) addE                  access command to grant the following DNS Version 1-eH                  style access on behalf of the SYSTEM account on the newD                  Version 2 clerk node that you configured in Step 1:  H                  o  Read, write, delete, test, and control access to the3                     root directory of the namespaceh  H                  o  Read, write, delete, test, and control access to theG                     clearinghouse that stores the master replica of thea"                     root directory  E                  For example, if the DECnet-Plus full name of the new H                  clerk is .pastry, and the master replica of the VersionF                  1 namespace is stored in the .paris_ch clearinghouse,2                  enter the following two commands:  O                  DNS> add access pastry::system directory . /rights=(r,w,d,t,c)c  [                  DNS> add access pastry::system clearinghouse .paris_ch /rights=(r,w,d,t,c)o  H                  You need to grant this access to ensure that the SYSTEMI                  account on the new Version 2 clerk has sufficient access.H                  to run the decnet_register utility. The Version 2 clerkC                  must also have permission to create and populate aiE                  backtranslation directory (.DNA_BackTranslation) andpF                  node synonym directory (.DNA_NodeSynonym) in the rootH                  directory of the namespace during the next step of this                  procedure.C  I                                               Managing Name Services 7-17m t  n               Managing Name ServicesA         7.5 Using a DNS Version 1 Namespace with DECdns Version 2     F                 ________________________ Note ________________________  B                 If the node you configured as a Version 2 clerk in@                 Step 1 is a new node, or is being assigned a newE                 DECnet Phase IV-compatible address, you should update E                 the DECnet node databases on all Version 1 servers in C                 the namespace to include the new address before you                  proceed.  F                 ______________________________________________________  H               3. Log in to the new Version 2 clerk node under the SYSTEMD                  account and invoke the sys$manager:decnet_register_6                  decdns.com utility. Do the following:  E                  a. Choose Option 3 on the decnet_register_decdns.comiA                     menu to create and populate a backtranslationdH                     directory (.DNA_BackTranslation). Choose Option 2 toG                     create a node synonym directory (.DNA_NodeSynonym).N  B                  b. Choose Option 2 on the decnet_register menu toC                     register the new Version 2 clerk node (the node C                     you are logged in to) and to register all other H                     DECnet Phase IV nodes in the namespace including allI                     nodes that are currently functioning as DNS Version 1                      servers.  E               Refer to the DECnet-Plus for OpenVMS Network ManagementeF               guide for complete information on how to use the decnet_I               register utility and the decnet_register_decdns.com utilitym%               to perform these steps.i  /         7.5.2 Using the DNS Version 1 Namespacef  B               When you have completed this step, the DNS Version 1F               namespace is ready for use by other nodes running DECdns<               Version 2 on DECnet-Plus for OpenVMS software.  I               Perform this procedure only once to prepare a DNS Version 1 H               namespace for use with DECnet-Plus. After the node synonymD               and backtranslation directories are populated, you canF               configure new DECdns clerks, new DECdns servers (for VAXC               only) into an existing namespace, or convert existingnE               DNS Version 1 servers to DECdns Version 2 format in theiG               normal manner. Refer to the DECnet-Plus DECdns ManagementtE               guide for information on how to convert a DNS Version 1 7               clearinghouse to DECdns Version 2 format.d  #         7-18 Managing Name Servicesa n  h      I                                                    Managing Name ServicesoI                                   7.6 Registering a Node in the Namespacer    /         7.6 Registering a Node in the Namespacen  F               The net$configure.com procedure creates an Export/ImportF               file to register your node in the appropriate namespace.E               If your node is already registered, the decnet_registere0               Export/Import file is not created.  '         7.6.1 Export/Import File Format   C               The decnet_register Export/Import file is a text file G               that has the following format where <synonym> is the node =               synonym name you selected during configuration:   C               sys$manager:decnet_register_import_file_<synonym>.TXT   )         7.6.2 Problems Registering a Nodes  D               If you encounter problems registering your node in theF               Local namespace or in the DECdns namespace, you will see3               information similar to the following:                  .a               .t               . X               Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT                  1) local:.elmer  8               Error - Node registration was unsuccessfulW                       Please correct any problems and re-register the node LOCAL:.elmer   F                 The specified node name is already in use as a synonym7                       Used by node: LOCAL:.WABBIT.ELMERn)                       Synonym:      elmer   U               You can choose to stop processing this command, continue executing thislX               command until completion or until the next error, or ignore further errors)               and continue to completion.h  +               Number of nodes registered: 0 +               Number of nodes modified:   0 *               Number of update failures: 1  ^               %NET$CONFIGURE-E-COULDNOTREG, could not automatically register node in the LOCAL                 directory service  I                                               Managing Name Services 7-19     c               Managing Name Services/         7.6 Registering a Node in the Namespacel    Y                    ********************************************************************** 6                                                WARNING  T                    This node could not be registered in one or more of the directoryW                    services you have chosen.  When this procedure completes you or your \                    network manager will have to manually register this node in the directory]                    service(s) for which the error occurred.  See the DECnet-Plus InstallationN]                    and Configuration guide for more details, or contact your network manager.M  Y                    Once the problem has been rectified, you or your namespace manager canO\                    use the following decnet_register command(s) to register your node in the4                    appropriate directory service(s):  6                       For the LOCAL directory service:C                       DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE - O                               SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT,  T                    Once the node has been successfully registered in the appropriateU                    directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change Y                    node name/namespace name) to complete the node's network configurationb                    and startup.t  Y                    **********************************************************************r  I               If net$configure.com cannot access the DECdns namespace you 7               have selected, it is most likely because:   >               o  The namespace is not available at the moment.  D               o  Your node does not have proper access to the DECdns                  namespace.   G               o  The namespace you are using is new and the directories +                  have not been created yet.n  C               When this happens, you will see the following messagedC               (this example uses ACME: as the namespace that is nota               accessible):  \                    *************************************************************************9                                                   WARNINGdV                    NET$CONFIGURE.COM cannot access the ACME: namespace, either becauseO                    the namespace is not available at the moment, your node does T                    not have proper access to the namespace, or because the namespaceV                    you are using is new and the directories have not been created yet.\                    Therefore, the decnet_register tool cannot attempt to look up or register6                    your node into the ACME: namespace.  #         7-20 Managing Name Services" b  i      I                                                    Managing Name ServicesyI                                   7.6 Registering a Node in the Namespace     \                    When the problem is rectified, please use the decnet_register import fileB                    to register your node into the ACME: namespace.  \                    *************************************************************************  G               If you receive this message because the namespace you areaF               using is new and the namespace directories have not beenD               created yet, use the decnet_register manage command toI               invoke decnet_register_decdns.com (located in SYS$MANAGER:)oG               to create the proper directories. For more details, referkF               to the DECnet-Plus for OpenVMS Network Management guide.  F               If you see the preceding warning messages, net$configureE               will display another message indicating how you or your F               namespace manager can attempt node registration once the/               problem is resolved. For example:   Y                    **********************************************************************u6                                                WARNING  T                    This node could not be registered in one or more of the directoryW                    services you have chosen.  When this procedure completes you or youre\                    network manager will have to manually register this node in the directory]                    service(s) for which the error occurred.  See the DECnet-Plus Installationn]                    and Configuration guide for more details, or contact your network manager.d  Y                    Once the problem has been rectified, you or your namespace manager can \                    use the following decnet_register command(s) to register your node in the4                    appropriate directory service(s):  7                       For the DECdns directory service:aD                       DECNET_REGISTER IMPORT DIRECTORY DECDNS FILE -?                           DECNET_REGISTER_IMPORT_FILE_ELMER.TXTi  6                       For the LOCAL directory service:C                       DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE - ?                           DECNET_REGISTER_IMPORT_FILE_ELMER.TXTe  T                    Once the node has been successfully registered in the appropriateU                    directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change Y                    node name/namespace name) to complete the node's network configuration                     and startup.c  Y                    **********************************************************************e  H               You may see the previous messages if the following exists:  F               o  You enter LOCAL for the primary directory service and@                  DECDNS for the secondary directory service and,  I                                               Managing Name Services 7-21                     Managing Name Services/         7.6 Registering a Node in the Namespacer    D               o  Your primary Local node full name does not have theD                  proper access necessary to look up or register your1                  secondary DECdns node full name.n  H                  If this is the case, you or your namespace manager needH                  to perform the following steps on the node that has theF                  DECdns server in order for your primary Local node to<                  obtain this access to the DECdns namespace:  D                  1. Make sure the .WorldRead_Group is created on theG                     DECdns server node. If the .WorldRead_Group has notsD                     been created yet, use the decnet_register manageI                     command to invoke decnet_register_decdns.com (locatedSH                     in sys$manager:) to create the .WorldRead_Group. ForF                     more details, refer to the DECnet-Plus for OpenVMS-                     Network Management guide.l  E                  2. Once you or your namespace manager knows that the A                     .WorldRead_Group has been created, invoke theiC                     DNS$CONTROL utility on the node with the DECdnst<                     server and enter the following commands:  %                     $ mcr dns$controlhK                     DNS> add group <ns>:.worldread_group member local:.*...t`                     DNS> add clear <ns>:.<ch_name> access <ns>:.worldread_group as group for r,t  H                     where <ns> is the DECdns namespace name to which youH                     want your LOCAL node to have access and <ch_name> isF                     the clearinghouse name of the DECdns namespace you                     are using.  G               These commands will give your primary Local full name therI               proper access it needs to look up information regarding theE9               secondary DECdns full name you have chosen.t  F                 ________________________ Note ________________________  C                 If you use DECDNS for the primary directory service D                 and LOCAL for the secondary directory service, these(                 steps are not necessary.  F                 ______________________________________________________      #         7-22 Managing Name Servicesd o  s                    I                                                                  Part III I         _________________________________________________________________)  I                                       Additional Installation Information             9               Part III contains the following appendixes:   A               o  Appendix A - Overview of the POLYCENTER Softwarei%                  Installation Utilityc  H               o  Appendix B - Installing DECnet-Plus for OpenVMS from an                  InfoServer   E               o  Appendix C - System Files Loaded During Installatione o                       I                                                                         A I         _________________________________________________________________e  I                              The POLYCENTER Software Installation Utilitye    C               The POLYCENTER Software Installation utility replacesVD               VMSINSTAL as the method of installing layered productsF               for OpenVMS such as the OSI applications for DECnet-PlusG               for OpenVMS, and X.25 for OpenVMS Alpha. It allows you todF               install several software products with a single command.  F                 ________________________ Note ________________________  B                 Before installing DECnet-Plus using the POLYCENTER@                 Software Installation utility for the first timeB                 on OpenVMS VAX Version 7.1, you should execute the&                 following DCL command:  M                 $ product register product vms/version=v7.1/source=sys$updaten  B                 This needs to be done only once in the life of theA                 OpenVMS system; it makes a permanent entry in theiE                 POLYCENTER Software Installation utility database, soeD                 it remains effective across system boots and for all)                 future software upgrades.   F                 If you do not perform this operation before installingD                 DECnet-Plus, the installation recommends terminationD                 due to the failure to locate the product "DEC VAXVMSC                 VMS Version 7.1." Answer YES to the question Do yourC                 want to terminate? and perform the product registere0                 command as in the above example.  F                 ______________________________________________________  B               Additional details for using the POLYCENTER SoftwareA               Installation utility to install, manage, and remove=B               software products on your system are provided in theC               OpenVMS System Management Utilities Reference Manual.l    I                          The POLYCENTER Software Installation Utility A-1. e  r      4         The POLYCENTER Software Installation Utility$         A.1 DCL Help with POLYCENTER    $         A.1 DCL Help with POLYCENTER  E               To obtain DCL Help for POLYCENTER, type the DCL command)I               help product, followed by the name of a POLYCENTER SoftwaretE               Installation utility command (for example: help product                install).g                                                                              8         A-2 The POLYCENTER Software Installation Utility           I                              The POLYCENTER Software Installation Utility I                                              A.1 DCL Help with POLYCENTERp    !         A.1.1 DCL Command Summarya  C               DCL Help for the PRODUCT commands listed in Table A-1dB               describes all the tasks you can perform from the DCL               interface.  ;               Table A-1 DCL PRODUCT Commands and Qualifiers I               ____________________________________________________________I               PRODUCT_Command_________________Qualifiers_________________e  <               CONFIGURE                       /CONFIGURATION3               Creates a product               /HELPt2               configuration file (PCF)        /LOG5               for one or more products in     /OUTPUT   +               reference format. Optionally,l,               uses the values in an existing(               PCF to create the new PCF.  :               COPY                            /DESTINATION5               Manipulates a product           /FORMATe3               distribution. You can use       /HELPn2               copy to create a sequential     /LOG5               copy from a reference copy,     /OUTPUT 8               a reference copy from a         /OWNER_UIC5               sequential copy, or to create   /SOURCEt  )               a copy without changing the                format.   6               EXTRACT RELEASE_NOTES           /DISPLAY2               Accesses the release notes for  /LOG5               the selected product or group   /OUTPUTi5               of products.                    /SOURCE   2               FIND                            /LOG5               Looks at the distribution       /OUTPUTu5               media and reports on the        /SOURCE   &               products it finds there.  I                                                  (continued on next page)r      I                          The POLYCENTER Software Installation Utility A-3            4         The POLYCENTER Software Installation Utility$         A.1 DCL Help with POLYCENTER    I               Table_A-1_(Cont.)_DCL_PRODUCT_Commands_and_Qualifiers______,  I               PRODUCT_Command_________________Qualifiers_________________   <               INSTALL                         /CONFIGURATION:               Installs one or more software   /DESTINATION3               products on your system.        /HELP 2                                               /LOG5                                               /OUTPUT 4                                               /PURGE5                                               /REMARK 5                                               /SOURCE 3                                               /TEST 3                                               /WORK   <               RECONFIGURE                     /CONFIGURATION3               Changes the active              /HELPh2               configuration choices for       /LOG5               a product.                      /OUTPUT 5                                               /REMARK 5                                               /SOURCEr  :               REGISTER PROCESSOR              /BASE_SYSTEM8               Adds a processor in a           /BOOTSTRAP:               computing facility. Used        /DESTINATION5               primarily within a DCL command  /GLOBALl3               procedure during system         /HELPg2               startup.                        /LOG8                                               /OPERATING5                                               /OUTPUT 5                                               /REMARK   :               REGISTER PRODUCT                /DESTINATION3               Registers a product in the      /HELP_2               product database.               /LOG5                                               /OUTPUTl5                                               /REMARK 5                                               /SOURCEh    I                                                  (continued on next page)d        8         A-4 The POLYCENTER Software Installation Utility l         I                              The POLYCENTER Software Installation UtilityiI                                              A.1 DCL Help with POLYCENTERr    I               Table_A-1_(Cont.)_DCL_PRODUCT_Commands_and_Qualifiers______   I               PRODUCT_Command_________________Qualifiers_________________   3               REGISTER VOLUME                 /HELP 2               For a volume containing         /LOG5               installed products, records a   /OUTPUTr  +               change in volume label in the                product database.v  3               REMOVE                          /HELPs2               Removes a software product      /LOG5               from your system and the        /OUTPUT*5               product database.               /REMARK 3                                               /WORK   4               SHOW FILE                       /BRIEF5               Displays information about      /DEVICEc8               files created during a          /DIRECTORY3               software product installation.  /FULLg6                                               /PRODUCT  5               SHOW HISTORY                    /ACTIONs5               Displays a log of actions,      /BEFOREi4               users, and remarks that apply   /BRIEF3               to a particular product.        /FULLi5                                               /REMARK 4                                               /SINCE4                                               /STATE3                                               /USER   I                                                  (continued on next page)R                        I                          The POLYCENTER Software Installation Utility A-5X           4         The POLYCENTER Software Installation Utility$         A.1 DCL Help with POLYCENTER    I               Table_A-1_(Cont.)_DCL_PRODUCT_Commands_and_Qualifiers______   I               PRODUCT_Command_________________Qualifiers_________________r  5               SHOW PRODUCT                    /ACTION 5               Displays information about      /BEFORE*4               the products installed on your  /BRIEF5               system.                         /DEVICE 8                                               /DIRECTORY3                                               /FILE.3                                               /FULLc3                                               /LINK 6                                               /PATCHED4                                               /SINCE7                                               /SOFTWAREh4                                               /STATE5                                               /STATUSe3                                               /USER*  3               UNREGISTER PROCESSOR            /HELP 2               Removes a processor from        /LOG5               a computing facility. Used      /OUTPUTt4               primarily within a DCL command  /PURGE5               procedure during system         /REMARKe  I               startup.___________________________________________________e  ;         A.2 Creating and Using a Product Configuration File   I               Some software products require you to make a set of choicesnC               when you install the product. For example, if you are F               installing a tool that checks spelling, you might chooseC               which languages you want to include. When you use the I               POLYCENTER Software Installation utility, you can configurer-               a product in one of three ways:   I               o  By responding to questions asked during the installatione                  procedure  F               o  By modifying your choices after you install a product  F               o  By creating a product configuration file (PCF) before(                  you install the product    8         A-6 The POLYCENTER Software Installation Utility a  d      I                              The POLYCENTER Software Installation UtilitygI                       A.2 Creating and Using a Product Configuration FileY    D               By saving your answers in a PCF and using the file forG               subsequent installations, you can reduce or eliminate themF               questions asked when you install a product. You can alsoD               create multiple PCFs for each product. This allows youE               to customize software installations for unique hardwarerH               situations or for different usage patterns within a group.  F               If you create a PCF as a separate operation, rather thanF               as part of the installation procedure, you can determineD               how your choices are recorded in the PCF. You have the                following options:  "               o  Save your answer.  F                  You can specify that your response to an installationD                  question (rather than the current default value) be#                  stored in the PCF.r  +               o  Use your answer only once.   A                  You can answer a question without recording yournD                  answer in the PCF. This is useful for responding toH                  questions that are specific to a single system (such asI                  a DECnet-Plus node name) or installation (such as a time                   setting).  D               o  Defer a question so that it is asked again during a%                  future installation.M  H                  For example, you might want an installer to verify thatH                  a particular response is still valid for the systems on<                  which each installation is being performed.  ;               o  Prevent a question from being asked again.L  F                  If you do not defer a question when you create a PCF,H                  the default response recorded in the PCF is used duringH                  future installations. The installer is not prompted forH                  the information. This reduces the length and complexity6                  of the actual installation procedure.          I                          The POLYCENTER Software Installation Utility A-7     v      4         The POLYCENTER Software Installation Utility;         A.2 Creating and Using a Product Configuration File     2         A.2.1 Responding to Installation Questions  I               The following are valid responses to questions asked during                an installation:  7               o  Enter your own value and press Return.p  8               o  Press Return to accept a default value.  G               o  Press the defer key F17 or ~D to ask the same questionr-                  during future installations.   H               o  Press F18 or ~W if you do not want to record the answer1                  as the default value in the PCF.o  H               o  Press the noexpand key F19 to accept default values for%                  a subset of options.   G               To get help on using the POLYCENTER Software Installation B               utility script, at the DCL prompt type the following               command:                 $ help product  ,         A.3 Verifying Pre-installation Tasks  H               The POLYCENTER Software Installation utility verifies thatE               any or all of the following are true, depending on youre               product:  ;               o  You are logged in to a privileged account.f  H                  It is good practice to install software from the systemI                  manager's account with your default device and directory #                  set to SYS$UPDATE.i  G               o  Quotas, system parameters, disk space (and memory) areC+                  adequate for installation.e  H                  The POLYCENTER Software Installation utility checks forH                  the quota values specified in Chapter 1. If it does notG                  find sufficient disk space, the installation procedures0                  provides the following options:  H                  -  You can restart the installation and specify anotherF                     disk to use as an alternate working device for the0                     temporary working directory.  8         A-8 The POLYCENTER Software Installation Utility y         I                              The POLYCENTER Software Installation UtilityoI                                      A.3 Verifying Pre-installation Tasksh    F                  -  You can terminate the installation and then createC                     more disk space on the system disk. The OpenVMSeD                     VAX Upgrade and Installation Manual, and OpenVMSI                     Alpha Upgrade and Installation Manual describe how to_G                     use tailoring utilities so you can delete files andn+                     create more disk space.   H                  If you lack sufficient free disk space for installationE                  or have no other disk to use as an alternate working_?                  device, the installation procedure terminates.o  D               o  The minimum version of the OpenVMS operating system8                  supported by this release is installed.  G               When the POLYCENTER Software Installation utility detects E               a problem in any of these areas, it asks if you want to F               continue the installation. If you want to continue, typeF               YES. If you want to stop the installation, press Return.           A.4 Resolving Conflicts   H               The POLYCENTER Software Installation utility resolves someH               conflicts automatically. For other types of conflicts, theH               POLYCENTER Software Installation utility provides feedbackG               on the nature of the conflict, letting you decide how youa               want to proceed.  A               For example, if the wrong version of DECnet-Plus is G               installed, the Software Integrator prompts you to install #               the required version.u  G               Similarly, if the correct version of OpenVMS is installed I               and you elect not to use the default values when installingsH               X.25, the Software Integrator warns you that you will needE               to use the RECONFIGURE option if you want to change theu,               version of OpenVMS to be used.  -         A.5 Determining Installation Progresss  A               As an installation procedure progresses, the systemd?               displays a percentage to indicate how much of the ;               installation has been completed. For example:R  O               Percent Done: 0%...10%...20%...30%...40%...50%...80%...90%...100%a  7               The following product has been installed:w(               DEC AXPVMS DECNET_OSI V7.1  I                          The POLYCENTER Software Installation Utility A-9t i  a      4         The POLYCENTER Software Installation Utility-         A.5 Determining Installation Progress     %               Or, as another example:h  O               Percent Done: 0%...10%...20%...30%...40%...50%...80%...90%...100%s  7               The following product has been installed: (               DEC VAXVMS DECNET_OSI V7.1  G               If you started the installation using the /LOG qualifier,e>               the system displays details of the installation.  (         A.6 Possible Installation Errors  D               If the installation procedure fails for any reason, anH               error message appears. For example, if the installation of8               X.25 fails, the following message appears:  L               %POLYCENTER Software Installation UtilityINSTAL-E-INSFAIL, TheP               ... installation of X.25 for OpenVMS Alpha Version 1.0 has failed.  G               An error can occur during the installation if one or morep0               of the following conditions exist:  ;               o  The operating system version is incorrect.h  @               o  The prerequisite software version is incorrect.  A               o  Quotas necessary for successful installation areY                  inadequate.  C               o  Process quotas required by the POLYCENTER SoftwareaE                  Installation utility are inadequate (see Chapter 1).A  >               o  The OpenVMS Help library is currently in use.  =               If the installation fails, you must restart thea%               installation procedure.h           A.7 Reporting Problems  D               If you encounter a problem while using DECnet-Plus forF               OpenVMS or X.25 for OpenVMS Alpha, report it to Digital.A               Depending on the nature of the problem and the type_D               of support you have, you can take one of the following               actions:  I               o  If your software contract or warranty agreement entitlesgD                  you to telephone support, call your Digital support                   representative.  9         A-10 The POLYCENTER Software Installation Utility  a  x      I                              The POLYCENTER Software Installation Utility I                                                    A.7 Reporting Problems     @               o  If the problem is related to the product's userD                  documentation, send comments and suggestions to theC                  electronic address at the beginning of this guide. B                  Include the section and page number of the error.  H               Review the Software Product Description (SPD) and WarrantyI               Addendum for an explanation of warranty. If you encounter acG               problem during the warranty period, report the problem as #               previously indicated.o                                                                        I                         The POLYCENTER Software Installation Utility A-11                          I                                                                         B I         _________________________________________________________________   I                     Installing DECnet-Plus for OpenVMS from an InfoServer     ?         B.1 Steps to Installing the Software from an InfoServer   I               The following steps show you how to access the distributionDD               kit via an InfoServer and install the software on your               system.s  F                 ________________________ Note ________________________  C                 The InfoServer does not use DECnet-Plus software to 7                 install software kits over the network.   F                 ______________________________________________________  B               1. Verify that the network hardware is installed and"                  working properly.  D               2. Log into the system manager account on your system.  E               3. Set your system's SCSNODE SYSGEN parameter to a non-                   blank value.   F                 ________________________ Note ________________________  B                 The InfoServer requires that the SCSNODE parameterB                 be set to a non-blank value even if your system is7                 running in a non-clustered environment.   F                 ______________________________________________________  E               4. Check with the InfoServer manager to verify that the G                  DECnet-Plus for OpenVMS distribution kit is available.oF                  If necessary, the InfoServer manager can refer to theH                  OpenVMS Layered Products Compact Disc User's Guide thatI                  came with the compact disc distribution kit for specific F                  details about the disc that contains the distribution                  kit.   I                 Installing DECnet-Plus for OpenVMS from an InfoServer B-1I R  O      =         Installing DECnet-Plus for OpenVMS from an InfoServern?         B.1 Steps to Installing the Software from an InfoServerL    ?               5. Get the distribution kit service name from the F                  InfoServer manager. For example, CDBIN is used in theA                  commands in this appendix as a kit service name.   D               6. Enter the following command to start the InfoServer0                  client software on your system:  5                  $ @sys$startup:ess$startup disk tapea  F               7. Assuming a service name of CDBIN, enter the followingH                  command to bind the service containing the distribution                  kit.   +                  $ mcr ess$ladcp bind cdbin_  F               8. Assuming a service name of CDBIN, enter the following<                  command to mount the kit device (optional):  :                  $ mount/override=identification dad$cdbin           B.2 Install Commands  I               To install DECnet-Plus from the CDBIN service, for example,                you would enter:  L               $ product install decnet_osi /source=dad$cdbin:[dnvosi071.kit]                                      A         B-2 Installing DECnet-Plus for OpenVMS from an InfoServer                          I                                                                         CsI         _________________________________________________________________   I                                   System Files Loaded During Installation     I               This appendix lists the system files that are placed on the I               system or copied to the system disk during the installationF               procedure.  B               The following table lists the files according to the3               directory into which they are copied.                                                             I                               System Files Loaded During Installation C-1            /         System Files Loaded During Installation     I         _________________________________________________________________ I         Directory/Files__________________________________________________-           [SYS$LDR]   <         LES$CHECK_LICENSE.EXE                LES$LES_V30.EXE  >         LES$NETMAN.EXE                       LES$NETMANLDR.EXE  :         LES$PROFILE.EXE                      NET$ALIAS.EXE  ;         NET$ALIAS.STB                        NET$DRIVER.EXE   E         NET$DRIVER.STB                       NET$LOOP_APPLICATION.EXEf  :         NET$MOPS0.EXE                        NET$MOPS0.STB  =         NET$OSDRIVER.EXE                     NET$OSDRIVER.STB   :         NET$OSVCM.EXE                        NET$OSVCM.STB  ?         NET$ROUTING_ES.EXE                   NET$ROUTING_ES.STB   D         NET$ROUTING_VCM.EXE                  NET$SESSION_CONTROL.EXE  ;         NET$SESSION_CONTROL.STB              NET$TPCONS.EXE   ;         NET$TPCONS.STB                       NET$TRACER.EXE   B         NET$TRANSPORT_NSP.EXE                NET$TRANSPORT_NSP.STB  B         NET$TRANSPORT_OSI.EXE                NET$TRANSPORT_OSI.STB  B         SYS$NAME_SERVICES.EXE                SYS$NAME_SERVICES.STB  <         SYS$NETWORK_SERVICES.STB             NET$MESSAGE.EXE  E         NET$ROUTING_IS.EXE                   SYS$NETWORK_SERVICES.EXE            [SYS$STARTUP]i  A         DNS$CLERK_STARTUP_V.COM              DNS$CLERK_STOP_V.COM   @         DTSS$STARTUP.COM                     NET$LES_STARTUP.COM  <         NET$ROUTING_STARTUP.COM              NET$STARTUP.COM           [SYSEXE]  :         ALIAS$SYMBOLS.STB                    CDI$TRACE.EXE  4         CDI_CACHE_DUMP.EXE                   CML.EXE  ;         CTF$DCP.EXE                          CTF$SERVER.EXEx  7         CTF$SYMBOLS.STB                      CTF$UI.EXEe  D         CTI$SYMBOLS.STB                      DECNET_LOC_REGISTER.EXE  D         DECNET_REGISTER.EXE                  DECNET_REGISTER_LNO.EXE  >         DNS$ADVER_V.EXE                      DNS$ANALYZE_V.EXE  3         C-2 System Files Loaded During Installations n  s      I                                   System Files Loaded During Installationo    I         _________________________________________________________________gI         Directory/Files__________________________________________________e  <         DNS$CONFIGURE.EXE                    DNS$CONTROL.EXE  6         DNSBROWSER.EXE                       DNSCP.BPT  :         DNSCP.MBF                            DSMDECDNS.EXE  B         DTSS$SERVICE.EXE                     DTSS$SET_TIMEZONE.EXE  <         ESIS$SYMBOLS.STB                     LES$ACP_V30.COM  >         LES$ACP_V30.EXE                      LES$FINDPTMAX.EXE  4         LES$STARTUP_V30.EXE                  NCL.EXE  8         NET$ACP.EXE                          NET$ACP.STB  :         NET$CCR.EXE                          NET$DEBUG.EXE  @         NET$EVENT_DISPATCHER.EXE             NET$LES_CONTROL.DAT  9         NET$LOAD.EXE                         NET$MGMT.EXEf  8         NET$MIRROR.EXE                       NET$MOP.EXE  @         NET$MOP.STB                          NET$QIO_SYMBOLS.STB  ;         NET$SERVER.COM                       NET$SERVER.EXEe  >         NET$SYMBOLS.STB                      NSPTP$SYMBOLS.STB  >         OSITP$SYMBOLS.STB                    OSVCM$SYMBOLS.STB  ?         SCL$SYMBOLS.STB                      TPCONS$SYMBOLS.STBe  4         CTF$CONFIG.EXE                       NCP.EXE            [SYSHLP.EXAMPLES.DNVOSI]  $         DNS_ADD_VALUE_TO_ATTRIBUTE.C  !         [SYSHLP.EXAMPLES.DNVPLUS]g  9         DNS_CREATE_OBJECT.C                  IPC_SERVER.Cr  @         DNS_READ_ATTRIBUTE.C                 IPC_BACKTRANSLATE.C  9         IPC_BUILD.COM                        IPC_CLIENT.Ce  6         IPC_COMMON.C                         IPC_DEF.H           [SYSHLP.EXAMPLES]r  6         CX.C                                 NSAPS.DAT  B         OSIT$CMD_EXECUTOR.COM                OSIT$CMD_EXECUTOR.MAR  @         OSIT$CMD_SOURCE.CLD                  OSIT$CMD_SOURCE.MAR  I                               System Files Loaded During Installation C-3a n         /         System Files Loaded During Installation     I         _________________________________________________________________nI         Directory/Files__________________________________________________C  :         OSIT$ECHO.FOR                        OSIT$RANDOM.C  G         OSIT$RECEIVER.PAS                    OSIT$RECORD_STRUCTURES.FORs  A         OSIT$STORAGE.FOR                     OSIT$TRANSMITTER.PASo  3         SETUP_NCL_KEYPAD.COM                 SUBX.CL  6         SX.C                                 VMS_OSI.H  =         XTIUTIL.C                            XTI_EXAMPLES.COM            [SYSHLP]  D         CTF$HELP.HLB                         DECNET_LOC_REGISTER.HLB  I         DECNET_MIGRATE.HLB                   DECNET_REGISTER_COMMANDS.HLBa  ;         DECNET_REGISTER_FORMS.HLB            DNS$CPHELP.HLB   <         DSMDECDNS.DECW$BOOK                  LES$SDAHELP.HLB  C         NCLHELP.HLB                          NET$CONFIGURE_HELP.HLBr  8         NET$MGMT_HELP.HLB                    NET$SDA.HLB  &         DECNET-PLUS-V7_1.RELEASE_NOTES                                3         C-4 System Files Loaded During Installationh e  l      I                                   System Files Loaded During Installationa                 [SYSLIB]  8         CDI$SHR.EXE                          CDI$SHR.STB  B         CML.OLB                              CTF$ALIAS_ANALYZE.EXE  @         CTF$CSMA-CD_TRACEPOINTS.DAT          CTF$CTI_ANALYZE.EXE  @         CTF$DECNET_TRACEPOINTS.DAT           CTF$DNA_ANALYZE.EXE  D         CTF$DUMP_ANALYZE.EXE                 CTF$ESEVENT_ANALYZE.EXE  E         CTF$IEEE8022_ANALYZE.EXE             CTF$IEEE8023_ANALYZE.EXEd  =         CTF$KEY.INIT                         CTF$KEY.TEMPLATEl  B         CTF$MOP_ANALYZE.EXE                  CTF$NSPTP_ANALYZE.EXE  D         CTF$NSP_ANALYZE.EXE                  CTF$NSP_TRACEPOINTS.DAT  B         CTF$OSITP_ANALYZE.EXE                CTF$OSVCM_ANALYZE.EXE  H         CTF$ROUTING_ANALYZE.EXE              CTF$ROUTING_TRACEPOINTS.DAT  C         CTF$SCL_ANALYZE.EXE                  CTF$TPCONS_ANALYZE.EXE   :         CTF$VOTS_ANALYZE.EXE                 DNS$RTL_V.EXE  9         DNSDEF_V.ADA                         DNSDEF_V.BASf  7         DNSDEF_V.FOR                         DNSDEF_V.Ht  9         DNSDEF_V.MAR                         DNSDEF_V.PASl  9         DNSDEF_V.PLI                         DNSDEF_V.R32t  9         DNSMSG_V.ADA                         DNSMSG_V.BAS   7         DNSMSG_V.FOR                         DNSMSG_V.H   9         DNSMSG_V.MAR                         DNSMSG_V.PASf  9         DNSMSG_V.PLI                         DNSMSG_V.R32   :         DSMDECDNS.DAT                        DSMDECDNS.UID  9         DTSS$RUNDOWN.EXE                     DTSS$SHR.EXE   A         DTSS$SHRD.EXE                        LES$ACP_CODE_V30.EXEd  8         LES$NETMANSHR.EXE                    LES$SDA.EXE  7         NCL$GLOBALSECTION.DAT                NCLSHR.EXE   H         NET$CMISE.EXE                        NET$EVD_RELAY_FORMATTER.EXE  >         NET$NISCS_LAA.EXE                    NET$NISCS_LAA.STB  C         NET$PROCESS_EMAA.EXE                 NET$ROUTING_ACPSHR.EXEr  8         NET$SDA.EXE                          NET_CMISE.H  >         NET_EXTERNALS.ADA                    NET_EXTERNALS.BAS  I                               System Files Loaded During Installation C-5o r  d      /         System Files Loaded During Installationn    I         _________________________________________________________________ I         Directory/Files__________________________________________________t  <         NET_EXTERNALS.FOR                    NET_EXTERNALS.H  >         NET_EXTERNALS.L32                    NET_EXTERNALS.MLB  >         NET_EXTERNALS.PAS                    NET_EXTERNALS.PLI  =         OSIT$LIBRARY.EXE                     OSIT$LIBRARY.OLB   5         OSIT.ADA                             OSIT.FORi  5         OSIT.H                               OSIT.L32.  5         OSIT.MAR                             OSIT.MLBT  5         OSIT.PAS                             OSIT.PEN   5         OSIT.PLI                             OSIT.R32   2         OSIT.SDI                             UTC.H  ;         XTI$DNETSHR.EXE                      XTI$OSISHR.EXE   <         XTI$UCXSHR.DECNET-PLUS               XTI.DECNET-PLUS           OSITMSG.H            [SYSMGR]  <         CTF$STARTUP.COM                      NET$AUTOGEN.COM  B         DECNET_DNS_REGISTER.COM              DECNET_DNS_TOWERS.COM  G         DECNET_LOC_REGISTER.COM              DECNET_REGISTER_DECDNS.COMt  >         DNS$CLERK_CLUSTER.NCL                DNS$CONFIGURE.COM  E         DTSS$CONFIG.COM                      DTSS$CONFIG_TEMPLATE.DAT   F         NET$CONFIGURE.COM                    NET$DNS_CLERK_STARTUP.NCL  E         NET$DTSS_CLERK_STARTUP.NCL           NET$EVENT_LOCAL.TEMPLATEg  =         NET$LOGICALS.TEMPLATE                NET$SHUTDOWN.COMe           [SYSMSG]  :         CTF$MESSAGES.EXE                     DNS$MSG_V.EXE  @         LES$ACP_MESSAGES_V30.EXE             LES$NM_MESSAGES.EXE           OSIT$VOTS_MSG.EXE            [SYSTEST]E  9         OSIT$IVP.CLD                         OSIT$IVP.EXEe  =         OSIT$IVPINIT.COM                     OSIT$IVPRESP.COMS  3         C-6 System Files Loaded During Installationn l  i      I                                   System Files Loaded During Installation     I         _________________________________________________________________ I         Directory/Files__________________________________________________            OSIT$IVP_SUPPORT.COM           [SYSUPD]           CTF.CLDa  C         DECNET_MIGRATE.EXE                   DECNET_MIGRATE_LSE.ENV.  D         DTSS$INSTALL_TIMEZONE_RULE.COM       DTSS$TIMEZONE_RULES.DAT  F         NCP_EMULATOR.TXT                     NET$CONFIGURE_UPGRADE.COM  A         NET$CONVERT_DATABASE.EXE             NET$PARSE_PREFIX.EXEs  A         NET$FIXUP_IDENTIFIERS.EXE            NET$PCSI_INSTALL.COMe  I         NET$REMOVE_EMU.COM___________________NET_ISHFILTER.EXE___________                                                     I                               System Files Loaded During Installation C-7                                  F      _________________________________________________________________  F                                                                  Index      E      A                                 CMIP Management Listener (CML) 7      _______________________________     defined,  6-12r8      ADVANCED configuration option,    Command procedureB         4-1, 7-15                        decnet_migrate.exe,  7-15C      Alternate node synonym              decnet_register.exe,  7-15s@         directory                        net$configure.com,  4-44        defining logicals, 7-15         ConfigurationC        format for defining, 7-15         changing basic components, 0        when used, 7-15                      6-18B      AUTOGEN utility                     changing fast components,/        running, 1-7                         5-6v?                                          choosing options,  4-2 =      B______________________________     cluster alias,  6-12eA      Backing up system disk              DECdns clerk-only systemt>        before running VMSINSTAL,            joining LAN DECdns=          1-9                                   namespace, 6-1 ?      Base components                     DECdns namespace,  7-4t=        configuring, 7-1                  flowchart,  3-5, 3-8rE           basic, 6-1                     list of tasks involved,  3-3rA      BASIC configuration option,         of base components,  7-1g7         4-1, 7-15                           basic,  6-1e9        invoking, 6-1                     of network,  4-1c?                                             basic,  6-1 to 6-18f=      C                                      fast,  5-1 to 5-6eB      _______________________________     proper sequence of steps,/      Characters                             3-3e;        valid for full name, 6-3,         requirements,  2-1 F          6-6                             search path information,  7-9@      Checklist                           selection weight,  6-132        installation, 2-2               Configuring?      Cluster alias                       a cluster alias,  6-12_E        configuring, 6-12                 application databases,  6-11 ?                                          DECnet over X.25,  6-8   F                                                                Index-1                   >         Configuring (cont'd)              DECnet-Plus (cont'd)  G          DECnet over X.25 (Alpha            configuration requirements,y1             system),  6-8                     2-1N=          DECnet over X.25 (VAX system)      installation, 1-1dE             ,  6-9                          license requirements, 1-3k:          NSP and OSI Transports,  6-11      node name, 6-3C          the search path,  7-9            decnet_migrate.exe,  7-15t9          time zone differential           decnet_registeri=             factors,  6-11                  export file, 7-19c=          using event dispatcher,  6-11      import file, 7-19OF         Conventions                         namespace management tool,1          of net$configure,  4-4               7-8_D         Creating                          decnet_register.exe,  7-151          DECdns namespace,  7-4           Default =          Local namespace,  7-2              node synonym, 6-6c4          new namespace,  7-3              DependencyB         Creating a namespace                for DECdns server, 1-4=          during initial configuration,      for gateways, 1-4 A             7-3                           Directory name services <                                             DECdns, 6-2, 7-2D         D______________________________     DNS/BIND, 6-2, 7-7, 7-13E         DCL                                 Local namespace, 6-2, 7-1s?          reply command,  1-9                node full name, 6-3hA          show device command,  1-6        Disk space requirementsgI          show memory command,  1-7          base components installation,t1         DCL help, A-2                         1-6 G          command summary,  A-3              DECdts server installation, 1         DECdns clerk-only system              1-6fB          joining LAN DECdns namespace       FTAM installation, 1-6=             configuring,  6-1               installation, 1-6iB         DECdns namespace                    OSAK installation, 1-6F          configuring,  7-4                  software installation, 1-6I          creating a new namespace,          Virtual terminal installation.4             7-3                               ,  1-6D          full name,  6-3                  Displaying information for>          valid characters,  6-3, 6-6         search path, 7-10:         DECnet over X.25                  Distribution kit9          configuring (Alpha system),        contents, 1-1n;             6-8                             inspecting, 1-1r<          configuring (VAX system),        Distribution media>             6-9                             mounting, 3-8, 3-9B         DECnet-Plus                       DNA address format,  6-77          configuration default values,    DNS version 1 G             4-5                             namespace preparation, 7-17f           Index-2I S  e              ?         DNS version 1 (cont'd)            Installation (cont'd)   A          using with DECdns Version 2,       installed files, 3-11_G             7-16                            list of tasks involved, 3-3tF         Domain synonym, 7-13                net$configure, how to run,1          node,  7-13                          4-4 F          search path naming template        OpenVMS for Alpha example,1             support,  7-14                    3-8nH                                             OpenVMS for Alpha flowchart,1         E______________________________       3-5 H         Error recovery, A-10                OpenVMS for VAX example, 3-9F         Export file, 7-19                   OpenVMS for VAX flowchart,1          decnet_register,  7-19               3-8_A                                             possible errors, A-10rG         F                                   Product Configuration File,S1         _______________________________       A-6 F         FAST configuration option           prompts and responses, A-8E          invoking,  5-1                     proper sequence of steps,E1         Files                                 3-3NB          installed,  3-11                   recommended order, 3-3D          system,  C-1                       reporting problems, A-10G         Full name                           required system parameters,.1          node,  6-3                           1-7 D          valid characters,  6-3, 6-6        resolving conflicts, A-9  G         I                                   system files loaded during,N1         _______________________________       C-1 B         Import file, 7-19                   time required for, 1-3@          decnet_register,  7-19             valid responses, A-8@         InfoServer                          verification of pre-F          bind command,  B-2                   installation tasks,  A-8?          installing software from,        Installation planning ;             B-1                              checklist, 2-2 I          mount command,  B-2              Installation procedure,  3-8 toL6          start command,  B-2                 3-11, A-8F         Installation                      Installation questions,  A-8@          checklist,  2-2                  Installed files,  3-11"          components included,  3-1I          DCL help,  A-2                   L______________________________ >          DECnet-Plus for OpenVMS          LAN DECdns namespace8             (Alpha),  3-3                   joining, 6-1-          DECnet-Plus for OpenVMS (VAX)    LNO H             ,  3-6                          replaced by Local Namespace,1          determining progress,  A-9           7-1           enabled keys,  A-8           from InfoServer,  B-1          how to run,  A-1   I                                                                   Index-3F s  a              -         Local aliases, 7-14               NCL_I         Local namespace                     creating site-specific search_@          creating,  7-2                       path script,  7-11;          managing,  7-2                   net$configure.comR<          replaces LNO,  7-1                 conventions, 4-4;                                             how to run, 4-4EG         M______________________________     privileges required to run, 1         Managing namespaces                   1-8C4          decnet_register tool,  7-8         starting9         Migration                              basic, 6-1 8          using search path,  7-12              fast, 5-1E         Modifying search path             Network configuration,  4-1V>           information,  7-10                basic, 6-1 to 6-18<         mount command                       fast, 5-1 to 5-6>          InfoServer,  B-2                 Node full name,  6-33                                           Node name <         N                                   DECnet-Plus, 6-3A         _______________________________     valid characters, 6-6 6         Name service                      Node synonym8          access features,  7-1              default, 6-68          primary,  7-8                      defined, 6-6G          search path,  7-8                  defining an alternate, 7-15U=          secondary,  7-8                    directories, 7-15 ?         Namespace                           local aliases, 7-14ND          DECdns,  7-4                       Phase IV-compatible, 6-63          directory path                   Node type ;             valid characters in,  6-3,      specifying, 6-5                 6-6I          local,  7-2                      O______________________________DB          management tool                  OpenVMS operating systemH             decnet_register,  7-8           checking the version number,1          nickname                             1-5-=             valid characters in,  6-3,      requirements, 1-3o                6-6+          node object                      P_I             valid characters in,  6-3,    ________________________________-                6-6                        PCF E          preparation                        See Product Configuration 8             DNS version 1,  7-17              File,  A-6.         Naming template                   PCSIC          setting up for search path,        see POLYCENTER SoftwareCC             7-12                              Installation utility, 1          support for domain synonyms,         A-1S             7-14           Index-4                             Phase IVI          compatible synonym,  6-6         S______________________________L1         POLYCENTER Software               ScriptsDF           Installation utility              creating for site-specific@          starting the DCL interface,          search path,  7-11;             3-8, 3-9                      Search path,  7-8N<          using,  A-1                        configuring, 7-9I         Post-installation tasks, A-10       creating site-specific scripth5           to A-11                             ,  7-11mH         Prerequisite                        displaying information, 7-10G          backing up system disk,  1-9       modifying information, 7-10 D          disk space,  1-5                   naming template support,2          informing users to log out,          7-14E             1-9                             primary name service, 7-8$G          required memory,  1-7              secondary name service, 7-8EH          setting system parameters,         setting up naming templates,2             1-7                               7-12D         Privileges                          using to ease migration,2          to run net$configure.com,            7-12:             1-8                           Selection weight=         Product Configuration File          configuring, 6-13 ;          creating,  A-6                   Simple name,  6-6L:          use,  A-6                        Software licenseH         PWIP interface, 1-4                 checking the version number,  1                                               1-5D=         Q______________________________     requirements, 1-3V  8         Quota                             SYSGEN utilityF          verifying disk space,  1-6         autoconfigure all command,2                                               6-109         R______________________________     invoking, 1-7GC         Registering a node                  setting parameters, 1-8 0          resolving problems,  7-19        SystemH         reply command, 1-9                  disk space requirements, 1-5E         Reporting installation              verifying disk space, 1-6 6           problems,  A-10                 System filesG         Routing                             loaded during installation, 1          DNA address format                   C-1 ;             characteristic,  6-7          System parametersE=         Routing information                 requirements, 1-7 D          specifying,  6-5                   requirements for cluster;                                               members,  1-8 7                                             values, 1-7   I                                                                   Index-5r d                   I         T______________________________   V_______________________________  :         TCP/IP                            Valid charactersH          DECnet and OSI applications        for namespace nickname, 6-3,1             over,  1-4                        6-6          Time zone3I          configuring differential         X______________________________ .             factors,  6-11                X.25  H                                             configuring DECnet over X.25B                                               (Alpha system),  6-8H                                             configuring DECnet over X.25@                                               (VAX system),  6-9                                                                       Index-6 