               H                     DECnet-Plus_for_OpenVMS_____________________________:                     Applications Installation and Advanced!                     Configuration   -                     Order Number: AA-QPSVB-TE     !                     November 1996   G                     This book explains how to install and configure the G                     layered application products on the DECnet-Plus for %                     OpenVMS software.               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, E               DECNIS, DECserver, DECsystem, DECwindows, DIGITAL, DNA, H               InfoServer, OpenVMS, PATHWORKS, ULTRIX, VAX, VAX DOCUMENT,F               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 through X/Open Co.               Ltd.  D               All other trademarks and registered trademarks are the3               property of their respective holders.                  0                        F                                                                     -3          F      _________________________________________________________________  F                                                               Contents      F      Preface...................................................     xi  ?      Part I  ADVANCED Configuration for DECnet-Plus for OpenVMS     /      1  Using the ADVANCED Configuration Option   F            1.1   Invoking the ADVANCED Configuration Option....    1-1F            1.2   Directory Name Services.......................    1-4F            1.2.1     Node Full Name............................    1-5F            1.2.2     Node Synonym..............................    1-6F            1.2.3     Naming Cache Timeout Value................    1-6F            1.2.4     Session Control Address Update Interval...    1-7F            1.2.5     Naming Cache Checkpoint Interval..........    1-7F            1.2.6     Specifying the Node Type..................    1-77            1.2.7     Configuring Time Zone Differential F                      Factors...................................    1-7F            1.2.8     Specifying Routing Information............    1-85            1.2.9     Specifying a Phase IV-Compatible F                      Address...................................    1-8F            1.2.10    Specifying a Phase IV Prefix..............    1-9F            1.2.11    Specifying End Node Information...........    1-9F            1.2.11.1    Configuring Network Addresses...........    1-9F            1.2.11.2    DNA Address Format......................   1-11=            1.2.11.3    Segregated Mode Routing and Integrated F                        Mode Routing............................   1-11F            1.2.11.4    ESHello Timer...........................   1-13F            1.3   Configuring Devices...........................   1-13F            1.3.1     Configuring Asynchronous Connections......   1-13        F                                                                      v                   :               1.3.2     Configuring Data Links and RoutingI                         Circuits..................................   1-14 =               1.3.2.1     Specifying Circuit Cost and Routing I                           Priority................................   1-14 ?               1.3.3     Enabling Phase IV Addressing on Routing I                         Circuits..................................   1-14 I               1.3.4     FDDI Large Packet Support.................   1-14 I               1.3.5     Configuring an Alpha System...............   1-15 I               1.3.6     Configuring a VAX System..................   1-19 B               1.4   Configuring the Network Service Protocol (NSP)I                     Transport ....................................   1-21 I               1.5   Configuring the OSI Transport.................   1-22 I               1.5.1     Congestion Avoidance......................   1-24 8               1.5.2     Setting Up the OSI Loopback TestI                         Application Account.......................   1-25 I               1.5.3     Creating Additional OSI Templates.........   1-25 I               1.5.3.1     CLNS Network Service....................   1-26 I               1.5.3.2     CONS Network Service....................   1-27 I               1.5.3.3     RFC 1006 Network Service................   1-28 I               1.6   Configuring an Event Dispatcher ..............   1-29 I               1.7   Configuring an Application Database...........   1-29 I               1.8   Configuring a Cluster Alias ..................   1-30 I               1.9   Configuration Summary and Network Startup.....   1-32   !         2  Managing Name Services   I               2.1   Names Services Overview.......................    2-1 I               2.1.1     The Local Namespace ......................    2-1 I               2.1.1.1     Creating a Local Namespace..............    2-2 I               2.1.1.2     Managing the Local Namespace............    2-2 <               2.1.2     The DIGITAL Distributed Name ServiceI                         (DECdns)..................................    2-2 I               2.1.2.1     Creating a New Namespace................    2-3 I               2.1.2.2     Creating a DECdns Namespace.............    2-4 I               2.1.3     Domain Name System........................    2-7 I               2.1.4     Namespace Management......................    2-8 I               2.2   Name Service Search Path......................    2-8 I               2.2.1     Configuring the Search Path Information...    2-9 I               2.2.1.1     Naming Search Path in a Cluster.........   2-10 I               2.2.2     Displaying the Search Path Information....   2-10 I               2.2.3     Modifying the Search Path Information.....   2-10 @               2.2.4     Creating a Site-Specific Search Path NCLI                         Script....................................   2-11     
         vi                   I               2.2.5     Using the Search Path to Ease Migration...   2-12 I               2.2.6     Setting Up Naming Templates...............   2-12 I               2.3   Domain Synonyms...............................   2-13 ?               2.3.1     Search Path Naming Template Support for I                         Domain Synonyms...........................   2-14 I               2.3.2     Local Aliases.............................   2-14 I               2.4   Node Synonym Directories......................   2-15 :               2.4.1     Defining an Alternate Node SynonymI                         Directory.................................   2-15 I               2.4.2     When to Use the Logical Name..............   2-15 ?               2.5   Using a DNS Version 1 Namespace with DECdns I                     Version 2.....................................   2-16 ?               2.5.1     Preparing a DNS Version 1 Namespace for I                         Use by DECdns Version 2...................   2-17 I               2.5.2     Using the DNS Version 1 Namespace.........   2-18 I               2.6   Registering a Node in the Namespace...........   2-19 I               2.6.1     Export/Import File Format.................   2-19 I               2.6.2     Problems Registering a Node...............   2-19   ,         3  Modifying a Current Configuration  I               3.1   Steps for Changing the Configuration..........    3-1 I               3.2   Steps for Changing a Current Configuration....    3-3 I               3.3   Changing an Entire Configuration..............    3-6 I               3.4   Changing the Node Name/Namespace Name.........    3-7 I               3.4.1     Changing Directory Name Services..........    3-7 I               3.4.2     Changing Node Name or Namespace...........    3-8 I               3.4.3     Changing Node Synonym.....................    3-8 B               3.4.4     Configuring a DECdns Clerk System to Use aI                         WAN DECdns Server.........................   3-10 @               3.4.5     Configuring a DECdns Server System in anI                         Existing Namespace........................   3-12 >               3.4.5.1     Configuring a DECdns Server in a DNSI                           Version 1 Namespace.....................   3-12 I               3.5   Reconfiguring Devices.........................   3-13 I               3.6   Reconfiguring the NSP and OSI transports......   3-14 <               3.7   Reconfiguring the Time Zone DifferentialI                     Factor (DECdts)...............................   3-20 :               3.7.1     Selecting the DECdts ConfigurationI                         Option....................................   3-20           I                                                                       vii                    I               3.7.2     Configuring Your System's Local Time......   3-21 >               3.7.2.1     Configuring Your System's Local TimeI                           Using Menus (Menu Option 1).............   3-22 A               3.7.2.2     Configuring Your System's Local Time as I                           UTC (Menu Option 2).....................   3-25 B               3.7.2.3     Customizing Your System's Time Zone RuleI                           (Menu Option 3).........................   3-26 I               3.8   Reconfiguring the Event Dispatcher............   3-33 I               3.9   Reconfiguring the Application Database........   3-39 I               3.10  Reconfiguring the MOP Client Database.........   3-44 @               3.11  Reconfiguring Event, MOP Client, ApplicationI                     Entities, and the Naming Search Path..........   3-47 I               3.12  Reconfiguring the Cluster Alias...............   3-48 I               3.12.1    Specifying an Address.....................   3-49 I               3.12.2    Determining Selection Weight..............   3-50 I               3.13  Replace MOP Client Configuration..............   3-50 I               3.14  Configuring Satellite Nodes...................   3-51 I               3.15  Configuring Cluster Script Locations..........   3-54 I               3.16  Completing Configuration Changes..............   3-57   A         Part II  Configuring VAX P.S.I. and VAX P.S.I. Access for $                  OpenVMS VAX Systems    7         4  Configuring VAX P.S.I. and VAX P.S.I. Access   I               4.1   Steps in Configuring VAX P.S.I................    4-1 I               4.2   Planning Your VAX P.S.I. Configuration........    4-1 A               4.2.1     Configuring Access, Native, and Multihost I                         Systems...................................    4-1 I               4.2.2     The VAX P.S.I. Configuration Program......    4-4 @               4.2.3     Sections in the VAX P.S.I. ConfigurationI                         Program...................................    4-6 >               4.3   Recording the Information You Need for VAXI                     P.S.I. Configuration..........................   4-10 8               4.4   Running the VAX P.S.I. ConfigurationI                     Program.......................................   4-33 =               4.4.1     Starting the VAX P.S.I. Configuration I                         Program...................................   4-33 :               4.4.2     Using the VAX P.S.I. ConfigurationI                         Program...................................   4-34 I               4.4.2.1     Entering Information....................   4-34 I               4.4.2.2     Moving Within a Section.................   4-35 I               4.4.3     Options Menu..............................   4-35            viii                   I               4.4.4     Creating NCL Script.......................   4-37 I               4.4.5     Exiting the Program.......................   4-37 :               4.4.6     Requirement to Complete VAX P.S.I.I                         Configuration ............................   4-38 I               4.4.7     Getting Help..............................   4-38 B               4.4.7.1     Getting Help on a Specific Field or MenuI                           Choice..................................   4-38 I               4.4.7.2     Getting General Help....................   4-38 I               4.4.7.3     Getting Help on the Program.............   4-39 I               4.5   Testing VAX P.S.I.............................   4-39 I               4.5.1     Preparing to Run the CTP..................   4-40 I               4.5.2     Running the CTP...........................   4-41 I               4.5.2.1     Running the CTP Interactively...........   4-41 I               4.5.2.2     Running the CTP as a Network Object.....   4-41 I               4.6   Changing Your VAX P.S.I. Configuration........   4-42 I               4.7   Creating a New VAX P.S.I. Configuration ......   4-42   =         Part III  Installing and Configuring X.25 for OpenVMS                    Alpha Systems     5         5  Planning to Install X.25 for OpenVMS Alpha   I               5.1   Product Description...........................    5-1 I               5.2   Required Hardware.............................    5-1 I               5.3   Required Software.............................    5-2 I               5.4   Kit Location..................................    5-2 I               5.5   Time Required to Install......................    5-3   6         6  Preparing to Install X.25 for OpenVMS Alpha  I               6.1   Inspecting the Distribution Kit...............    6-1 I               6.2   Logging In to a Privileged Account............    6-1oI               6.3   Accessing the Online Release Notes............    6-2 I               6.4   Determining Process Account Quotas............    6-3nI               6.5   Determining Disk Space........................    6-4E                  I                                                                        ixi n  d              ,         7  Installing X.25 for OpenVMS Alpha  I               7.1   Registering the X.25 Software License.........    7-1:I               7.2   Installing X.25 Using the DCL Interface.......    7-4 I               7.3   Files Installed on Your System................    7-4A9               7.4   X.25 Installation and De-Installation I                     Sample........................................    7-4 I               7.4.1     X.25 Installation Example.................    7-55I               7.4.2     X.25 De-Installation Example..............    7-7o  9         8  X.25 Post-Installation and Configuration Tasksq  I               8.1   Configuring X.25..............................    8-1 I               8.2   Restart DECnet-Plus...........................    8-2_I               8.3   Rebooting the System..........................    8-3 I               8.4   De-installing X.25............................    8-3dI               8.5   Sample X.25 Configuration ....................    8-4n  @         Part IV  Installing OSI Applications for OpenVMS Systems  (         9  Planning for the Installation  I               9.1   Product Descriptions..........................    9-1rI               9.2   Required Hardware.............................    9-2oI               9.3   Required Software.............................    9-2nI               9.4   Kit Location..................................    9-2 I               9.5   Time Required to Install......................    9-3   5         10  Preparing to Install the OSI Applicationst  I               10.1  Inspecting the Distribution Kit...............   10-1oI               10.2  Logging In to a Privileged Account............   10-1 I               10.3  Accessing the Online Release Notes............   10-2 I               10.4  Memory Requirements...........................   10-3r=               10.4.1    Changing System Parameter Values with I                         AUTOGEN...................................   10-4nI               10.5  Process Quotas................................   10-4cI               10.6  Determining Disk Space........................   10-6 I               10.7  Notifying Users...............................   10-7             	         xe r  m              +         11  Installing the OSI Applicationsi  I               11.1  Prerequisite Steps............................   11-1t:               11.2  Register the OSI Applications SoftwareI                     License.......................................   11-1n8               11.3  Starting the Installation of the OSII                     Applications..................................   11-2tI               11.4  Installing the OSI Applications...............   11-2o5               11.5  Starting Up and Shutting Down OSIsI                     Applications..................................   11-6 6               11.6  The OSAK Installation VerificationI                     Procedure.....................................   11-6/I               11.7  Running the OSIF$CONFIGURE.COM Procedure......   11-7s6               11.8  The FTAM Installation VerificationI                     Procedure.....................................   11-8 I               11.8.1    Preparing for the FTAM IVP................   11-8 I               11.8.2    Running the FTAM IVP......................   11-9 I               11.9  The VT Installation Verification Procedure....  11-11 I               11.10 De-installing OSI Applications................  11-11 I               11.11 Files Installed on Your System................  11-12 I               11.12 Sample OSI Application Installations..........  11-12DI               11.12.1   Sample OSAK Installation..................  11-13vI               11.12.2   Sample Virtual Terminal Installation......  11-14.I               11.12.3   Sample FTAM Installation..................  11-15.I               11.13 Sample OSI Application De-installations.......  11-16.I               11.13.1   Sample Virtual Terminal De-installation...  11-16 I               11.13.2   Sample FTAM De-installation...............  11-17.I               11.13.3   Sample OSAK De-installation...............  11-18.  ,         12  Configuring the OSI Applications  I               12.1  FTAM and Virtual Terminal Terminology.........   12-1.I               12.2  About the OSI Application Entity Database.....   12-1.>               12.3  Getting Started Configuring Initiating andI                     Responding Entities...........................   12-2 I               12.3.1    Setting Up Responding Entities............   12-2 I               12.3.2    Setting Up Initiating Entities............   12-2 I               12.3.3    Example: Performing An FTAM File Copy.....   12-41>               12.3.4    Example: Performing A Virtual TerminalI                         Login.....................................   12-5 I               12.4  About Responding Entities.....................   12-6 @               12.5  Configuring Addresses for Remote FTAM and VTI                     Applications..................................   12-7 I               12.5.1    Adding Address Format Entries.............  12-12   I                                                                        xi                    8               12.5.2    Adding Distinguished Name FormatI                         Entries...................................  12-12.I               12.5.3    Adding Pattern Format Entries.............  12-12oI               12.6  Registering Responders To X.500 Directory.....  12-13i           Part V  Appendixes    /         A  Configuring Asynchronous Connections.  I               A.1   Asynchronous DECnet Connections...............    A-1.:               A.1.1     Establishing a Static AsynchronousI                         Connection................................    A-5n;               A.1.1.1     Terminating a Static Asynchronous I                           Connection..............................    A-8r7               A.1.1.2     Reasons for Failure of Static I                           Asynchronous Connections................    A-9 ;               A.1.2     Establishing a Dynamic Asynchronous2I                         Connection................................   A-10 9               A.1.2.1     Setting Up Dynamic Asynchronous I                           Connections.............................   A-11 ;               A.1.2.2     Switching on Dynamic Asynchronous.I                           Connections.............................   A-15.7               A.1.2.3     Managing Dynamic AsynchronouskI                           Resources...............................   A-19D<               A.1.2.4     Terminating a Dynamic AsynchronousI                           Connection..............................   A-19r8               A.1.2.5     Reasons for Failure of DynamicI                           Asynchronous Connections................   A-20   !         B  Configuring Transports   I               B.1   Overview......................................    B-1 I               B.2   Manually Configuring NSP......................    B-1 I               B.2.1     Transmit and Receive Window...............    B-3 :               B.3   Manually Configuring the OSI TransportI                     Service.......................................    B-3 I               B.3.1     Transmit and Receive Window...............    B-5                        xiia w  m              ;               B.3.2     Configuring the Connection-Oriented I                         Network Service...........................    B-6.A               B.3.2.1     Establishing Outbound Connections UsingaI                           CONS....................................    B-7a@               B.3.2.2     Establishing Inbound Connections UsingI                           CONS....................................    B-7 I               B.3.2.3     Manually Configuring Support for CONS...    B-8i0               B.3.3     Manually Configuring theI                         Connectionless-Mode Network Service.......   B-13 A               B.3.3.1     Establishing Outbound Connections Using I                           CLNS....................................   B-13 @               B.3.3.2     Establishing Inbound Connections UsingI                           CLNS....................................   B-14nI               B.3.3.3     Steps for Configuring CLNS..............   B-14n>               B.3.3.4     Providing Communications Between OSIB                           Transport Systems and VOTS Systems UsingI                           CLNS....................................   B-21 >               B.4   Manually Configuring OSI Transport NetworkI                     Applications..................................   B-22 8               B.4.1     Customizing End Selector for OSII                         Transport.................................   B-24 I               B.4.2     Enabling Use of CLNS Error Reports........   B-24 ?               B.5   Using DECnet over TCP/IP (RFC 1859) and OSI I                     over TCP/IP (RFC 1006)........................   B-24 I               B.5.1     Configuring RFC 1006 and/or RFC 1859......   B-25 9               B.5.2     Creating Additional OSI Transport I                         Templates for RFC 1006 and RFC 1859.......   B-26 I               B.5.3     Disabling DECnet-Plus over TCP/IP.........   B-26   
         Index.             Figuresi  6               4-1       Installation and ConfigurationI                         Flowchart.................................    4-3g  6               7-1       Installation and ConfigurationI                         Flowchart.................................    7-3   ?               A-1       Dynamic Switching of Asynchronous DDCMPhI                         Lines.....................................   A-15h      I                                                                      xiiin g  r                       Tables  I               3-1       Choosing Your Configuration Option........    3-2   I               3-2       Time Zone Rules...........................   3-29   I               3-3       Object Type Numbers.......................   3-41   =               4-1       VAX P.S.I. Configurations and License3I                         Requirements..............................    4-4   9               4-2       VAX P.S.I. Configuration Sections.A                         Required for Access, Native and MultihostaI                         Systems...................................    4-53  =               4-3       VAX P.S.I. Configuration Information:.<                         Lines and DTEs (Native and MultihostI                         Systems Only).............................   4-11n  B               4-4       VAX P.S.I. Configuration Information: PVCsI                         (Native and Multihost Systems Only).......   4-13a  =               4-5       VAX P.S.I. Configuration Information:.<                         Groups (Native and Multihost SystemsI                         Only).....................................   4-15   B               4-6       VAX P.S.I. Configuration Information: LLC2I                         (Native and Multihost Systems Only).......   4-16   =               4-7       VAX P.S.I. Configuration Information: :                         Remote DTE Classes (Access SystemsI                         Only).....................................   4-17   B               4-8       VAX P.S.I. Configuration Information: X.29I                         and P.S.I. Mail Support (All Systems) ....   4-18   =               4-9       VAX P.S.I. Configuration Information:3?                         Gateway Client Nodes (Multihost Systems.I                         Only).....................................   4-19.  =               4-10      VAX P.S.I. Configuration Information:nI                         Applications (All Systems)................   4-19.  =               4-11      VAX P.S.I. Configuration Information:a8                         Declaring a Network Process (AllI                         Systems)..................................   4-20n  =               4-12      VAX P.S.I. Configuration Information:e<                         Filters-for Applications and Network;                         Processes (All Systems) and gateway3I                         clients (Multihost Systems Only) .........   4-213  =               4-13      VAX P.S.I. Configuration Information:.I                         Templates (All Systems) ..................   4-23c           xiv                    =               4-14      VAX P.S.I. Configuration Information:A?                         Incoming Security for Applications (All.I                         Systems)..................................   4-26i  =               4-15      VAX P.S.I. Configuration Information:aB                         Outgoing Security for Local Processes (AllI                         Systems)..................................   4-28u  =               4-16      VAX P.S.I. Configuration Information: ?                         Incoming Security for Network Processes.I                         (All Systems).............................   4-30n  =               4-17      VAX P.S.I. Configuration Information:i=                         Incoming Security for Gateway ClientsnI                         (Multihost Systems Only) .................   4-31.  =               4-18      VAX P.S.I. Configuration Information:t<                         Outgoing Security for Client SystemsI                         (Multihost Systems Only) .................   4-32h  9               6-1       Process Quotas for the Installing.I                         Account...................................    6-3g  B               10-1      Required Global Pages, Global Pagelets andI                         Sections..................................   10-3i  9               10-2      Process Quotas for the InstallingiI                         Account...................................   10-4.  I               10-3      OSAK$SERVER_V3 Process Account Quotas.....   10-5.  B               10-4      Account Quotas for Processes that use OSAKI                         Software..................................   10-5.  I               10-5      Minimum Disk Space Requirements...........   10-7.  I               12-1      Default Addresses.........................   12-7   I               12-2      X.500 Configuration Checklist.............   12-9   I               12-3      Address Format Worksheet..................  12-11   B               B-1       Additional Routing Circuit CharacteristicsI                         for CLNS..................................   B-19   I                                                                        xv                              I         _________________________________________________________________n  I                                                                   Preface       A               This is the second book you should read in order tou1               successfully install and configure:   '               o  X.25 for OpenVMS Alphag  A               o  VAX P.S.I. and VAX P.S.I. Access for OpenVMS VAXg  2               o  OSI layered software applications  @                  -  File Transfer, Access, and Management (FTAM)  )                  -  Virtual Terminal (VT).  2                  -  OSI Applications Kernel (OSAK)  H               It also describes how to configure DECnet-Plus for OpenVMSE               using the ADVANCED configuration option and informationo"               about name services.  F                 ________________________ Note ________________________  D                 This book assumes you have already installed DECnet-?                 Plus which is a prerequisite for installing the.=                 applications discussed in this book. Refer tocF                 <REFERENCE>(DNPLUS_OVMS_INSTALL_BASIC) for information*                 on installing DECnet-Plus.  F                 ______________________________________________________           Intended Audiencee  '               This book is written for:   .               o  Network planners and managers  (               o  OpenVMS system managers  0               o  DECnet-Plus software installers  I                                                                        xi  :                          Structure of This Book  '               This book has five parts:.  H               Part I  Describes how to run an ADVANCED configuration forI                       DECnet-Plus for OpenVMS, as well as steps to change..                       a current configuration.  C               Part    Describes how to configure VAX P.S.I. and VAX E               II      P.S.I. Access for a DECnet-Plus for OpenVMS VAX-                       system.a  G               Part    Describes the pre-installation, installation, and.I               III     configuration steps necessary to install X.25 for a.;                       DECnet-Plus for OpenVMS Alpha system.t  G               Part    Describes the pre-installation, installation, andsF               IV      configuration steps necessary to install the OSI7                       applications: FTAM, VT, and OSAK.   I               Part V  Describes how to configure asynchronous connectionsP%                       and transports.            Terminologyc  H               The following terms are used interchangeably in this book.                 o  Alpha and AXP  )               o  Transition and migrationr  -               o  Phase IV and DECnet Phase IV   (               o  End system and end node  /               o  Intermediate system and routeri  (               o  DECnet-Plus and Phase V           Related DocumentsI  A               The following books provide additional information.s  7               o  <REFERENCE>(DNPLUS_OVMS_INSTALL_BASIC)o  H                  The first book to read in order to successfully installA                  DECnet-Plus for OpenVMS. It also includes how to D                  configure DECnet-Plus using the BASIC configuration5                  and information about name services.   .               o  <REFERENCE>(DNPLUS_OVMS_USER)           xii. 1  n              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.   -               o  <REFERENCE>(DNPLUS_PLANNING)   G                  Explains in detail the transition from DECnet Phase IV G                  to DECnet-Plus, providing configuration guidelines and                    planning tasks.  -               o  <REFERENCE>(DNPLUS_DNS_MGMT)i  -               o  <REFERENCE>(DNPLUS_DTS_MGMT)   2               o  <REFERENCE>(DNPLUS_OVMS_NET_MGMT)  5               o  X.25 for OpenVMS Configuration Guide.  1               o  <REFERENCE>(DNPLUS_FTAM_VT_MGMT)   :               o  OpenVMS License Management Utility Manual  4               o  OpenVMS System Management Utilities  H               For additional information on the DECnet-Plus products andG               services, access the DIGITAL OpenVMS World Wide Web site.F$               Use the following URL:  ,               http://www.openvms.digital.com           Reader's Comments   I               DIGITAL welcomes your comments on this manual or any of the I               DECnet-Plus documents. Send us your comments through any of %               the following channels:.  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   I                                                                      xiii  1                 -         How To Order Additional Documentation   G               Use the following table to order additional documentation =               or information. If you need help deciding which1C               documentation best meets your needs, call 800-DIGITAL.               (800-344-4825).                                                                                        xive s  l                       Conventions   >               The following conventions are used in this book.  I               ___________________________________________________________uI               Convention_______Meaning___________________________________t  D               special type     Indicates a literal example of systemG                                output or user input. In text, indicatesnH                                command names, keywords, node names, fileG                                names, directories, utilities and tools.x  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 of5D                                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 texte8                                or important information.  G               <Return>         Indicates that you press the Return key.   G               Ctrl/x           Indicates that you press the Control key B                                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.__________________________________           I                                                                        xv  o  c                    I                                                                    Part IcI         _________________________________________________________________.  I                        ADVANCED Configuration for DECnet-Plus for OpenVMS             F               Part I describes the steps necessary to use the ADVANCEDB               configuration option for DECnet-Plus for OpenVMS. It.               includes the following chapters:  D               o  Chapter 1 - Using the ADVANCED Configuration Option  3               o  Chapter 2 - Managing Name Services.  >               o  Chapter 3 - Modifying a Current Configuration c                       I                                                                         1iI         _________________________________________________________________.  I                                   Using the ADVANCED Configuration Option.    I               This chapter describes how to configure the DECnet-Plus for.F               OpenVMS base components using the ADVANCED configurationH               option so that the system becomes a DECnet-Plus end systemH               on a network. The ADVANCED configuration option allows you?               to customize your system's network configuration.   H               If you have already configured the DECnet-Plus for OpenVMSD               software and you want to modify the configuration, see               Chapter 3.  6         1.1 Invoking the ADVANCED Configuration Option  A               To invoke the net$configure.com procedure using theaI               ADVANCED configuration option, enter the following command:.  3               $ @sys$manager:net$configure advanced.  #               The procedure starts:C  Z               Copyright (c) Digital Equipment Corporation 1993, 1996. All rights reserved.  Q                  DECnet-Plus for OpenVMS ADVANCED network configuration procedureg  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 '?'.   U               You have chosen the ADVANCED configuration option.  This option enables V               you to do some specific tailoring of your system's network configurationV               by answering some specific questions.  If you do not want to do specificR               tailoring of your system's network configuration but instead want toR               quickly configure your system using most of the default answers, youV               should invoke NET$CONFIGURE.COM with the BASIC configuration option, ie:=                              @SYS$MANAGER:NET$CONFIGURE BASIC   L               * Do you want to continue?                             [YES] :  I                               Using the ADVANCED Configuration Option 1-1C 0  .      /         Using the ADVANCED Configuration Option 6         1.1 Invoking the ADVANCED Configuration Option    F               Press Return to continue with the net$configure ADVANCED#               configuration option.5                                                                                      3         1-2 Using the ADVANCED Configuration Option            I                                   Using the ADVANCED Configuration Option.I                            1.1 Invoking the ADVANCED Configuration Optionn    H               The following illustrates the main menu options from which               you can choose:   ,                       Configuration Options:  1                       [0]     Exit this procedure.  =                       [1]     Perform an entire configuration 7                       [2]     Change naming information ?                       [3]     Configure Devices on this machineo2                       [4]     Configure TransportsD                       [5]     Configure Timezone Differential Factor8                       [6]     Configure Event Dispatcher<                       [7]     Configure Application database;                       [8]     Configure MOP Client database.5                       [9]     Configure Cluster Alias >                       [10]    Replace MOP Client configuration7                       [11]    Configure satellite nodes @                       [12]    Configure cluster script locations  N               * Which configuration option to perform?                 [1] : 1  I               If you select Option 1, the procedure informs you that this.F               is the first time you are configuring your system to use&               DECnet-Plus for OpenVMS:  I               %NET$CONFIGURE-I-SETUPNEW, setting up for new configuration   H               If a Phase IV database exists on the system, the following               message displays:t  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.  Q               * Do you want to convert Phase IV databases?             [NO] : yesi  H               If you answer YES, the procedure prompts you for the PhaseB               IV prefix (see Section 1.2.10 for more information):  M               * Enter Phase IV Prefix                                [49::] :i  I                               Using the ADVANCED Configuration Option 1-31           /         Using the ADVANCED Configuration Optioni6         1.1 Invoking the ADVANCED Configuration Option    D               The net$configure procedure uses the system's existingI               Phase IV database to generate NCL scripts and configure the                system.   D               If you answer NO, the net$configure procedure does notE               use the system's existing Phase IV database to generateSC               NCL scripts and proceeds to ask all the configurationCA               questions. If you need more information to answer aSH               question, you can type a question mark (?) at the prompts.I               To configure DECnet, you need to know your node's full name /               and network address or addresses.l  #         1.2 Directory Name Services.  I               DECnet-Plus provides access to the node name and addressingCF               information stored in one or more name services. DECnet-B               Plus supports the following directory name services:  G               o  Local namespace - A discrete, nondistributed namespaceuD                  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.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 2.1.t  E               o  DECdns distributed namespace - DIGITAL's DistributedsC                  Name Service, DECdns is a distributed, global name.B                  service. For more information, see Section 2.1.2.  G               o  Domain Name System - The Domain Name System (DNS/BIND).C                  is supported for storage of IP addresses. For mores/                  information see Section 2.1.3.   A               If you choose to enter more than one directory name G               service for your system, enter them in order of priority. D               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 primary E               directory service is considered the first choice to use @               when looking up naming information for the system.    3         1-4 Using the ADVANCED Configuration Optionr e  .      I                                   Using the ADVANCED Configuration OptionaI                                               1.2 Directory Name Services.    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] :i  B               For example, if you enter LOCAL,DECDNS,DOMAIN at the/               prompt, this means the following:X  E               o  You want to use the name services DECdns, Local, ands                  DNS/BIND.  4               o  The primary name service is DECdns.  G               o  The secondary name services are Local and DNS/BIND, in                   that order.  F                 ________________________ Note ________________________  F                 If your node is also a DECdns server, the primary name'                 service must be DECdns.o  F                 ______________________________________________________           1.2.1 Node Full Name  G               Enter a node full name for each directory service chosen.dB               The node full name is the name of your system's nodeH               object in the directory service. It includes the namespaceF               nickname and the full list of directories leading to theD               node object name. Examples of node full names include:  1                Local namespace -  LOCAL:.TomThumb 4                DECdns          -  ACME:.wabbit.Elmer7                Domain          -  elmer.wabbit.acme.edue  F               For the Local namespace, the namespace nickname LOCAL isG               prepended to the full name and is terminated with a colon D               (:). 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. E               Note that the namespace nickname LOCAL is reserved, andeH               indicates that the Local namespace is used on this system.F               For example, if you enter "Local, DECdns, Domain" at theH               previous prompt, you will be asked for a DECdns full name,D               a Local full name, and a fully qualified host name for               DNS/BIND.   I                               Using the ADVANCED Configuration Option 1-5i           /         Using the ADVANCED Configuration Option #         1.2 Directory Name Servicesi    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.EDUn           1.2.2 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 numerice               characters.o  H               If this system had previously been running DECnet Phase IVI               software, then you should use the old Phase IV node name asnI               the synonym. If this system is joining a DECnet network fortF               the first time, you can use any name for the synonym, asG               long as it meets the criteria listed above, and is uniques!               within the network.D  L               * What is the synonym name for this node?            [ELMER] :  C               For more information on node synonym directories, seen               Section 2.4.  (         1.2.3 Naming Cache Timeout Value  G               A naming cache is used to improve the performance of node-I               name address resolution. This cache supersedes the existing H               DECdns cache and is used when looking for addresses in theI               Domain and Local services, in addition to DECdns. Note that I               other applications that directly use DECdns continue to usei               the DECdns cache.D  A               The naming cache includes a mechanism to "time out")C               old entries. In this way, these entries are refreshed C               periodically to accurately reflect the actual networkS               environment.  L               * Naming cache timeout value?                  [30-00:00:00] :  E               You have the option to set a value for the naming cache H               timeout interval. Enter any legal OpenVMS delta time value'               (the default is 30 days).t  3         1-6 Using the ADVANCED Configuration Optiont           I                                   Using the ADVANCED Configuration Option I                                               1.2 Directory Name Services     5         1.2.4 Session Control Address Update Interval   @               The session control address update interval is theF               time, in seconds, between updates of local tower address               information.  F               * Session Control Address Update Interval ?       [10] :  G               To choose a ten second interval, press Return. Otherwise, 7               enter your own interval and press Return.i  .         1.2.5 Naming Cache Checkpoint Interval  C               Periodically, DECnet-Plus saves a snapshot of the in-rF               memory naming cache to disk. This allows systems, duringG               startup, to have a naming cache that is already populatedlI               with entries, thereby preserving the contents of the naming *               cache across system reboots.  L               * Naming cache checkpoint interval?               [08:00:00] :  H               You have the option of setting the naming cache checkpointE               interval. Enter any legal OpenVMS delta time value (then"               default is 8 hours).  &         1.2.6 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 to E               run Integrated IS-IS, thus providing host-based routing >               functionality. The default is to be an end node.  L               * What type of node (Endnode or Router)?           [ENDNODE] :  8         1.2.7 Configuring Time Zone Differential Factors  @               The UTC (Coordinated Universal Time) is calculatedC               automatically by using the OpenVMS UTC. The procedure -               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.  I                               Using the ADVANCED Configuration Option 1-7     d      /         Using the ADVANCED Configuration Option #         1.2 Directory Name Servicesy    ,         1.2.8 Specifying Routing Information  G               This section only applies if your DECnet-Plus system is a                router.t  L               * Type of routing node (L1 or L2)?                      [L1] :  I               Enter L1 if your DECnet-Plus system will provide intra-areayF               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.  L               * Maximum path splits                                    [2] :  F               This specifies the maximum number of equal cost paths to               split between.  L               * PhaseIV Maximum Address                             [1023] :  G               Specifies the maximum node number within a Phase IV area.   L               * PhaseIV Maximum Area                                  [63] :  F               This question only applies if your DECnet-Plus system isF               a level 2 router. It indicates the maximum Phase IV area               number.   6         1.2.9 Specifying a Phase IV-Compatible Address  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 Phase $               IV-compatible address.  C               A DECnet Phase IV-compatible address is a DECnet-PlusEH               address (NSAP) that conforms to the Phase IV area and nodeG               limits; that is, the area number is from 1 to 63, and theu,               node number is from 1 to 1023.  H               If there are no Phase IV systems on your network or you doG               not want to communicate with Phase IV systems, you do notgE               need a Phase IV-compatible address. Entering a Phase IVoF               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.h  3         1-8 Using the ADVANCED Configuration OptionS V  E      I                                   Using the ADVANCED Configuration OptioncI                                               1.2 Directory Name Servicesn    +         1.2.10 Specifying a Phase IV Prefix   E               The default value for the Phase IV prefix is 49:: which G               represents the private network initial domain part (IDP). D               This is appropriate for a Phase IV DECnet network thatC               contains some DECnet-Plus systems. All nodes within aqD               single addressing domain contain the same IDP in their                network addresses.  D               If you are using a Phase IV prefix other than 49::, itG               must be assigned by an authorized standards organization,FH               such as ANSI, or you must construct a Phase IV prefix thatG               you know will be globally unique (based on your telephoneoG               number, for instance). If your organization has allocated G               its own Phase IV prefix, you can enter that value instead B               of 49::. The <REFERENCE>(DNPLUS_PLANNING) contains aE               detailed description of how to construct an IDP and howe>               to apply to a standards organization for an IDP.  .         1.2.11 Specifying End Node Information  H               This section applies only if your DECnet-Plus system is an               end node.   .         1.2.11.1 Configuring Network Addresses  G               Your system must have at least one unique network address B               in order to use DECnet-Plus communications features.F               DECnet-Plus systems can be multihomed; that is, they canF               have more than one network address. You can assign up to5               three network addresses to your system.   I               Having multiple addresses allows you to have both a DECnet-hF               Plus extended address and a Phase IV-compatible address,G               so you can communicate with both Phase IV and DECnet-Plus G               systems on the same network. It also allows you to belong H               to more than one OSI network. This feature is particularlyE               useful when you want to combine two (or more) networks.oE               Rather than assign new addresses to all systems in bothlI               networks to reflect the new combined network, those systemsnF               that participate in both networks can have an address in               each one.r  @               Network addresses are sometimes referred to in OSI?               terminology as network entity titles (NETs). NETss>               are network service access points (NSAPs) with aC               selector of 00. There are two ways to configure NETs:   I                               Using the ADVANCED Configuration Option 1-9t g         /         Using the ADVANCED Configuration Optiona#         1.2 Directory Name Serviceso    E               by autoconfiguring addresses or by manually configuringA               addresses.  F                 ________________________ Note ________________________  ?                 If you have an OSI router from a supplier otheraC                 than Digital Equipment Corporation adjacent to yourdB                 system, do not choose autoconfiguration unless youA                 know that the router uses NETs with a selector ofh?                 00. This restriction applies even if you have aoB                 Digital Equipment Corporation WANrouter as well asB                 another supplier's OSI router on the same LAN. OSIF                 routers that specify NETs differently can cause you toA                 autoconfigure your network addresses incorrectly.i=                 If you have such a router, you must choose to C                 manually configure your NETs by answering NO to the +                 autoconfiguration question.   F                 ______________________________________________________  1               Choice 1: Autoconfiguring Addresses   F                 ________________________ Note ________________________  B                 To use this option, you must be using only Phase V!                 (OSI) addressing.y  F                 ______________________________________________________  I               If you want to have your network address autoconfigured fornF               you, answer YES to the following question during network>               configuration when using the net$configure tool:  L               * Autoconfigure network addresses?                     [YES] :  6               Choice 2: Manually Configuring Addresses  H               You can assign a maximum of three network addresses to the<               system including the Phase IV network address.  F               To create a NET manually, you need to know your system's;               network IDP, network local area, and node ID.t  ;               For example, given the following information:r  .                  A network IDP of 41:45436192:+                  A network local area of 43l!                  A node ID of 258e  4         1-10 Using the ADVANCED Configuration Option    c      I                                   Using the ADVANCED Configuration Option I                                               1.2 Directory Name Servicesr    0               The NET is constructed as follows:  E               IDP and selector    = 41:45436192:local-area:node-id:00FB               43 decimal          = 2B    hexadecimal (local area)1               (43 * 1024) + 258   = 44290 decimal 5               44290 decimal       = AD02  hexadecimalm?               AD02 swapped        = 02AD  hexadecimal (node ID)   I               The resulting NET is 41:45436192:00-2B:AA-00-04-00-02-AD:00   F                 ________________________ Note ________________________  A                 NETs can be entered in OSI format, DNA format, ora@                 hexadecimal format. Make sure you include the 009                 selector when you manually specify a NET.r  F                 ______________________________________________________  B               For more information on how to construct DNA and OSIG               NETs, see the chapter on NSAPs in the <REFERENCE>(DNPLUS_                PLANNING).  #         1.2.11.2 DNA Address Formatr  E               You have the option of setting the value of the routingiC               characteristic "DNA Address Format" to either TRUE orD               FALSE.  L               * DNA Address Format                                  [TRUE] :  C               The DIGITAL Network Architecture (DNA) Address Formate>               attribute controls the interpretation of addressD               structuring. It does not control autoconfiguration. ToC               control autoconfiguration, you need to use the Manual C               Network Entity Titles attribute by manually adding orv               removing NETs.  D         1.2.11.3 Segregated Mode Routing and Integrated Mode Routing  E               You have the option of using integrated mode routing or I               segregated mode routing. If you answer NO to this question, 2               you will default to integrated mode.  L               * Do you want to use segregated mode routing?           [NO] :  D               Integrated mode routing works in the following way: ItE               sends DECnet Phase IV messages across the network using G               DECnet Phase V Network layer protocols. Routers receivingeG               DECnet Phase IV packets translate them to OSI CLNP format_H               before forwarding them. Messages destined for DECnet Phase  I                              Using the ADVANCED Configuration Option 1-11o f         /         Using the ADVANCED Configuration Optionb#         1.2 Directory Name Servicesl    F               IV systems are translated to Phase IV format only on theG               last hop of their journey. Integrated mode routing allowseG               routers to route both DECnet Phase IV and Phase V traffic G               while storing a single network topology in their internal                databases.  C               Under integrated mode, DECnet-Plus systems attempt toAE               send packets in DECnet Phase V format unless one of the                 following is true:  F               o  They are communicating directly to an adjacent DECnet!                  Phase IV system.w  B               o  No DECnet Phase V routers exist on the network to%                  forward the packets.o  C               Integrated mode routing is the only mode supported oncF               OpenVMS systems preceding DECnet/OSI for OpenVMS Version               6.0.  I               Segregated mode routing handles DECnet Phase IV and Phase VaI               as independent protocols. Routers do not translate messagesuF               between DECnet Phase IV and Phase V formats. The routersI               must maintain separate network topologies in their internal 8               databases to handle each type of protocol.  E               Under segregated mode, DECnet-Plus end systems transmitiD               messages in the Phase IV address format if they have aI               DECnet Phase IV translatable destination address. All othereI               messages are sent in DECnet Phase V format. If you use non-fH               DIGITAL routers that do not support DIGITAL's technique ofF               translating DECnet Phase V addresses to DECnet Phase IV,:               you may want to use segregated mode routing.  H               On OpenVMS systems, integrated mode is the default routingH               mode. Use integrated routing mode in an integrated routingI               environment where the routers can handle Phase-IV-to-Phase-dE               V or Phase-V-to-Phase-IV packet format conversions. UseyH               segregated routing mode when the adjacent router(s) cannotG               perform Phase-IV-to-Phase-V or Phase-V-to-Phase-IV packeti               conversions.  F                 ________________________ Note ________________________  D                 If your OpenVMS system is running cluster alias, you)                 must use integrated mode.   F                 ______________________________________________________  4         1-12 Using the ADVANCED Configuration Option    i      I                                   Using the ADVANCED Configuration OptionfI                                               1.2 Directory Name Servicesd             1.2.11.4 ESHello Timer  @               The default ESHello Timer attribute determines theF               interval, in seconds, when the end system (ES) sends outG               its hello. This interval multiplied by 3 is the amount of H               time the other end of a routing adjacency will wait beforeF               determining that this system is no longer able to accept               connections.  M               * Routing default ESHello Timer?                        [600] :i  D               To select the default of 600, press Return. Otherwise,5               choose your own value and press Return.o           1.3 Configuring Devices   G               The net$configure procedure checks for network devices on E               the system that are supported by net$configure and thenDI               configures them. If the procedure finds that you have WANDDnD               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  8               Answer YES if you want to configure WANDD.  F                 ________________________ Note ________________________  F                 If you answer NO to configuring wide area devices, youE                 will not see any information regarding X.25 or P.S.I.                  configurations.i  F                 ______________________________________________________  2         1.3.1 Configuring Asynchronous Connections  I               If you have installed and configured WANDD software on this F               system, you have the option of configuring it to support'               asynchronous connections.t  L               * Do you want asynchronous datalink support?            [NO] :  >               For more information on configuring asynchronous*               connections, see Appendix A.  I                              Using the ADVANCED Configuration Option 1-13     n      /         Using the ADVANCED Configuration Option          1.3 Configuring Devices     9         1.3.2 Configuring Data Links and Routing Circuits   I               You now need to supply names for the data links and routing B               circuits you have on your system. Specify the simpleF               name that you want to use for each data link and routing               circuit.  L               * Data Link name to use for ESA0 (DESVA)?         [CSMACD-0] :L               * Routing Circuit Name for Data Link 'CSMACD-0'?  [CSMACD-0] :  <         1.3.2.1 Specifying Circuit Cost and Routing Priority  I               The following applies only if your DECnet-Plus is a routingz               node.S  B               For each data link and routing circuit pair entered,F               specify the circuit cost and router priority at level 1.F               If your node is also a level 2 router, you will be asked3               for level 2 cost and router priority.V  I               Cost indicates the cost of traffic on a particular circuit.AG               Priority refers to the priority for becoming a designatedC4               router on a LAN at level 1 or level 2.  N               * Level 1 Cost for Routing Circuit 'CSMACD-0'?             [8] :N               * Level 1 Router Priority for Routing Circuit 'CSMACD-0'? [64] :N               * Level 2 Cost for Routing Circuit 'CSMACD-0'?             [8] :N               * Level 2 Router Priority for Routing Circuit 'CSMACD-0'? [64] :  >         1.3.3 Enabling Phase IV Addressing on Routing Circuits  G               If you previously specified a Phase IV-compatible address @               in order to communicate with Phase IV nodes (as inD               Section 1.2.6), entering YES to the following questionH               allows Phase IV messages to be transmitted on the circuit.B               Answering NO to this question means that no Phase IV:               messages will be transmitted on the circuit.  Q               * Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] :   '         1.3.4 FDDI Large Packet Support:  G               If you have an FDDI-type circuit on your system, you have H               the option of enabling FDDI large packet support. (A largeF               packet is 4 KB in size, where an Ethernet packet is 1500E               bytes in size.) FDDI large packet support allows you tosD               fully use the bandwidth of FDDI. (A DECnet-Plus routerG               on the LAN, preferably on the FDDI, is required to enableh$               large packet support.)  4         1-14 Using the ADVANCED Configuration Option i         I                                   Using the ADVANCED Configuration Option I                                                   1.3 Configuring Devicesh    F               If you choose not to enable FDDI large packet support onH               the system, the FDDI circuit uses the bandwidth of CarrierG               Sense, Multiple Access with Collision Detection (CSMA-CD)a               instead.  A               If there is an FDDI-type circuit on the system, the 7               procedure displays the following message:m  N               An FDDI-type circuit has been found on the system.  You have theO               option of enabling FDDI large packet support on the system.  Note N               that a DECnet-Plus router on the LAN (preferably on the FDDI) isA               required in order to use FDDI large packet support.w  L               * Enable FDDI large packet support?                     [NO] :  E               If you want to enable FDDI large packet support, answera               YES.  )         1.3.5 Configuring an Alpha Systemi  @               1. For an Alpha system, the procedure displays the'                  following information:o  O                  DEC X.25 software has been installed on this system.  You haveiC                  the option of configuring DECnet to run over X.25.h  O                  * Do you want to configure DECnet over X.25?            [NO] :d  F                  Answer YES if you want to configure DECnet over X.25.  F                  If you answer YES, you will see a list of choices for1                  the type of X.25 circuit to use:   -                       Types of X.25 circuits:r  6                       [1] - X.25 Dynamic Assigned (DA)5                       [2] - X.25 Static Incoming (IN)l6                       [3] - X.25 Static Outgoing (OUT)0                       [4] - X.25 Permanent (PVC)  Q                  * Which type of X.25 circuit do you want to use?             : 4a  E                  This prompt allows you to select the type of routing H                  circuit you want to use over X.25. The menu offers four                  choices:n  G                  o  A dynamically assigned routing circuit (menu optionaF                     1) operates over a number of X.25 switched virtual@                     circuits (SVCs), both incoming and outgoing.  I                              Using the ADVANCED Configuration Option 1-15  w         /         Using the ADVANCED Configuration Optionm         1.3 Configuring Devices     E                  o  A static incoming routing circuit (menu option 2)aI                     operates over a single incoming X.25 switched virtual "                     circuit (SVC).  E                  o  A static outgoing routing circuit (menu option 3)tI                     operates over a single outgoing X.25 switched virtual "                     circuit (SVC).  F                  o  A permanent routing circuit (menu option 4) uses aF                     permanent virtual circuit (PVC) instead of an SVC.  C                  Enter the number for the type of circuit you want.a  B               2. The procedure then asks for information about the!                  routing circuit.b  O                  * Routing Circuit Name to use?                   [X25-PVC-0] :   H                  Specify the simple name you want to use for the routingE                  circuit. You can use the default or you can supply ae/                  name (for example, X25-PSI-0).o  G               3. The procedure then asks for a template name to use fori0                  the circuit you just specified.  O                  * Template name?                                 [X25-PVC-0] :D  E                  Specify the simple name of an X25 Access template. ADH                  default name is provided or you may enter your own name)                  (for example, X25-DA-1).n  H                  All X.25 routing circuits use an X25 Access template to<                  either make or accept a network connection.  G                  o  For a static outgoing (OUT) circuit, the X25 AccesstD                     template must specify DTE class, destination DTEG                     address, and call data. The X25 Access template canoG                     also specify other call characteristics to make thea0                     outbound network connection.  G                  o  For a static incoming (IN) routing circuit, the X25iG                     Access template can specify call characteristics toy:                     accept the inbound network connection.  H                  o  For a dynamically assigned (DA) routing circuit, theG                     X25 Access template must specify DTE class and callEH                     data. The X25 Access template can also specify otherG                     call characteristics to make the outbound or accept 4                     the inbound network connections.  4         1-16 Using the ADVANCED Configuration Option _  _      I                                   Using the ADVANCED Configuration Option I                                                   1.3 Configuring Devices_    D                  Use the X.25 configuration program to configure X25"                  Access templates.  G               4. If you chose to configure an X.25 dynamically assigned F                  (DA) circuit or an X.25 static incoming (IN) circuit,6                  the procedure asks for a filter name.  O                  * Filter name?                                    [X25-DA-0] :   I                  Specify the simple name of an X25 Access filter. You mayyG                  accept the default or you may enter your own name (for $                  example, X25-IN-0).  G                  Static incoming and dynamically assigned X.25 circuits D                  use an X25 Access filter to receive inbound network                  connections.6  E                  For a static incoming circuit, the X25 Access filterdE                  must specify inbound DTE class, sending DTE address, 5                  call data value, and call data mask.   C                  For a dynamically assigned circuit, the X25 Access H                  filter must specify inbound DTE class, call data value,$                  and call data mask.  D                  Use the X.25 configuration program to configure X25                   Access filters.  I               5. If you choose to configure an X.25 dynamic assigned (DA) =                  circuit, the procedure displays this prompt:s  O                  * Do you want to configure any reachable addresses?     [NO] :4  G                  If you answer NO, the procedure skips to the question,_E                  "Configure another PSI routing circuit for DECnet?".e  ?                  If you want to configure any reachable addressmD                  subentities, answer YES. The procedure displays the"                  following prompt:  O                  * Reachable address name?                                    :o  A                  Specify the simple name of the reachable addresse@                  subentity that you want to create (for example,                   ACCOUNTS_DEPT).  B               6. The procedure then asks for the reachable address                  prefix:  O                  * Reachable address prefix                                   :S  I                              Using the ADVANCED Configuration Option 1-17U :         /         Using the ADVANCED Configuration Optiond         1.3 Configuring Devicesb    G                  The reachable address subentity name is used to selectsD                  the remote DTE address to where a routing packet isC                  sent. The selection is done by finding a reachableeF                  address subentity that has an address prefix matchingH                  the beginning of the remote NSAP in the routing packet.  F                  Specify the address prefix for this reachable addressE                  entity. The address prefix is a string of characters C                  that is a valid beginning of an NSAP (for example,yE                  41:45436192:). The address prefix matches all NSAPs.   E               7. The procedure then prompts for the reachable addresse4                  data terminal equipment (DTE) list:  O                  * Reachable address dte list?                                :   I                  You can configure a reachable address subentity with one G                  or more DTE addresses. If more than one DTE address is I                  configured, then only one is selected each time a packet I                  is sent. All the remote DTE addresses must be accessible G                  by the DTE class configured in the X25 Access templateoG                  already configured for the associated dynamic assignede                  circuit.   B                  Specify the list of remote DTE addresses for thisF                  reachable address entity. A DTE address consists of 1H                  to 15 decimal characters. The DTE addresses in the listD                  should be separated by commas (for example, 2,3,4).  D               8. The procedure then prompts for additional reachable                  addresses:e  O                  * Any more reachable addresses you wish to configure?   [NO] :N  C                  If you want to configure another reachable addressa8                  subentity for this circuit, answer YES.  H               9. When you have entered the circuit, template, and filterG                  names and you have specified the appropriate reachabledG                  address information, the procedure asks if you want top.                  configure any other circuits.  O                  * Configure another PSI routing circuit for DECnet?     [NO] :   F                  If you do not want to configure any other PSI routingC                  circuits, press Return for the default ([NO]). The G                  configuration procedure continues with the next serieseC                  of questions (such as FDDI large packet support orE*                  transports, for example).  4         1-18 Using the ADVANCED Configuration Option h         I                                   Using the ADVANCED Configuration OptionII                                                   1.3 Configuring DevicesE    A              10. If no devices are found on the Alpha system, then9                  procedure displays the following prompt:t  O                  * Should a SYSMAN IO AUTO be executed?                       :d  G                  If you answer YES, the net$configure procedure invokesoB                  the SYSMAN IO AUTO command to find devices on theB                  system. If you answer NO, there are no devices to                  configure.   &         1.3.6 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:  C                         This is the Configuration Procedure for the C                         ===========================================   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.   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  I                              Using the ADVANCED Configuration Option 1-19_           /         Using the ADVANCED Configuration Optione         1.3 Configuring Devicesn    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.  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 modifyN                 WANDD$STARTUP_SF.COM to include  Failover Set Manager commands!                 that you require.c  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:l  2                   [1] - X.25 Dynamic Assigned (DA)1                   [2] - X.25 Static Incoming (IN) 2                   [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 1.3.5 for the types of questions you will see andt/               possible responses you can enter.n  F               If no devices are found on the VAX system, the procedure,               displays the following prompt:  L               * Should a SYSGEN AUTOCONFIGURE ALL be executed?             :  4         1-20 Using the ADVANCED Configuration Option    c      I                                   Using the ADVANCED Configuration Option I                                                   1.3 Configuring Devices     D               If you answer YES, the net$configure procedure invokesE               the SYSGEN AUTOCONFIGURE ALL command to find devices on C               the system. If you answer NO, there are no devices to                configure.  D         1.4 Configuring the Network Service Protocol (NSP) Transport  H               If you want the system to communicate with DECnet Phase IV:               nodes, answer YES to the following question.  L               * Configure the NSP Transport?                         [YES] :  A               If you answer NO, the procedure still loads the NSP G               Transport image. However, NSP Transport is not configured E               or usable until you run the net$configure procedure andtH               answer YES to the question, "Configure the NSP Transport?"  A               To determine the maximum number of active transportFD               connections allowed at any one time to this transport,:               the procedure displays the following prompt:  L               * Maximum number of logical links?                     [200] :  @               You are then prompted to set the following values:  K               * Maximum transmit and receive window?                 [20] :u  K               * Maximum receive buffers?                           [4000] :   F               DIGITAL recommends setting a value of 20 for the maximumG               transmit and receive window option. The recommended value H               to set the maximum receive buffers is no more than maximumD               window multiplied by maximum transport connections forH               normal network operation in a typical network environment.  G               Selecting other values than these can significantly alteroH               the behavior of your system and network and should only beH               done after a thorough analysis of your network traffic and'               application requirements.I  @               High values of maximum receive buffers may requireF               considerable buffering capacity on your node; therefore,G               a non-paged pool should be allocated accordingly. If your G               node does not have enough non-paged pool, maximum receive C               buffers should be set to a smaller value than maximum5A               window multiplied by maximum transport connections.o  I                              Using the ADVANCED Configuration Option 1-21  s  c      /         Using the ADVANCED Configuration OptionnD         1.4 Configuring the Network Service Protocol (NSP) Transport    @               The transport receiver's window is determined by aC               combination of maximum transport connections, maximumvE               receive buffers, and maximum window. During the life of.H               the connection, the receiver quota fluctuates according toG               the value of maximum receive buffers divided by currently F               active connections. The credit window sent to the remoteG               transmitter may or may not be this quota value, dependinggI               on the value of maximum window. If maximum window is set to I               less than the determined receiver quota, this value is used G               instead for the credit granted to the remote transmitter.   G               The transmitter of a transport connection uses the creditiH               sent by the remote receiver as its transmit window, unlessH               its maximum window is a lower value. In that case, maximum8               window is used for the transmitter window.  )         1.5 Configuring the OSI Transport   D               If you want the system to communicate with DECnet-PlusB               nodes, OSI nodes of other vendors, or if you plan toH               install the OSAK, FTAM, or VT software, answer YES. If youH               want to use the DECnet over TCP/IP and/or OSI applications&               over TCP/IP, answer YES.  L               * Configure the OSI Transport?                         [YES] :  A               If you answer NO, the procedure still loads the OSI H               transport images. However, OSI transport is not configuredE               or usable until you run the net$configure procedure and 7               answer YES to the OSI transport question.   A               To determine the maximum number of active transportcD               connections allowed at any one time to this transport,:               the procedure displays the following prompt:  L               * Maximum number of logical links?                     [200] :  @               You are then prompted to set the following values:  K               * Maximum transmit and receive window?                 [20] :c  K               * Maximum receive buffers?                           [4000] :o  F               DIGITAL recommends setting a value of 20 for the maximumG               transmit and receive window option. The recommended valuesH               to set the maximum receive buffers is no more than maximumD               window multiplied by maximum transport connections forH               normal network operation in a typical network environment.  4         1-22 Using the ADVANCED Configuration Option e  y      I                                   Using the ADVANCED Configuration Option I                                         1.5 Configuring the OSI Transportt    G               Selecting other values than these can significantly alter H               the behavior of your system and network and should only beH               done after a thorough analysis of your network traffic and'               application requirements.e  @               High values of maximum receive buffers may requireF               considerable buffering capacity on your node; therefore,G               a non-paged pool should be allocated accordingly. If youroG               node does not have enough non-paged pool, maximum receive C               buffers should be set to a smaller value than maximumtA               window multiplied by maximum transport connections.a  @               The transport receiver's window is determined by aC               combination of maximum transport connections, maximummE               receive buffers, and maximum window. During the life ofeE               the connection, the receiver quota fluctuates according G               to the value of maximum receive buffers divided currently F               active connections. The credit window sent to the remoteG               transmitter may or may not be this quota value, dependingnI               on the value of maximum window. If maximum window is set toeI               less than the determined receiver quota, this value is usedsG               instead for the credit granted to the remote transmitter.5  G               The transmitter of a transport connection uses the creditfH               sent by the remote receiver as its transmit window, unlessH               its maximum window is a lower value. In that case, maximum8               window is used for the transmitter window.  $               You are then prompted:  L               * Run OSI Applications over TCP/IP?                    [YES] :  H               Answer YES to this question if you want to run any of yourI               OSI applications over TCP/IP. This causes the configuration D               utility to build the appropriate RFC 1006 template and5               establish a listener port for port 102.   K               * Run DECnet over TCP/IP?                             [YES] :n  C               Answering YES to this question enables DECnet-Plus toEF               run over a TCP/IP network to any system that has enabledE               this same feature. The configuration utility builds theeF               appropriate RFC 1859 template and establishes a listenerC               port for Port 399. (The default name for the RFC 1859 ,               template is osit$rfc1006plus.)  I                              Using the ADVANCED Configuration Option 1-23n y  m      /         Using the ADVANCED Configuration Optiond)         1.5 Configuring the OSI Transport     "         1.5.1 Congestion Avoidance  D               One feature of OSI transport is the ability to use theE               Congestion Experienced field in the Connectionless-mode G               Network Service (CLNS) routing header, and to implement a H               Congestion Avoidance scheme in heavily congested networks.F               The CLNS Congestion Experienced field is used by routersI               that support this feature (such as DECNIS) to give an earlyhH               indication of congestion. When OSI transport receives dataE               that passed through a network path where the Congestion H               Experienced bit is set, OSI transport reduces the transmitF               rate of the sending end system to help alleviate network               congestion.   E               This feature works well in networks where all protocols B               support Congestion Avoidance mechanisms. However, itB               has been noted that in some heavily congested multi-G               protocol networks, this feature can negatively impact theo@               performance of DECnet compared to other protocols.  G               DIGITAL recognizes that most of its customers have multi-fE               protocol networks. In this environment, not all networktH               protocols have Congestion Avoidance mechanisms. Therefore,=               the default of this characteristic is disabled.r  A               If you operate in an environment where you can takeeC               advantage of Congestion Avoidance mechanisms, DIGITAL ;               recommends that you enable the feature again.   I               You are asked a new question about multi-protocol networks:c  M               * Is this system operating in a multi-protocol network? [YES] :   A               If you take the default answer of YES, then the OSI E               transport Congestion Avoidance characteristic is set to                FALSE.  E               A NO answer to this question sets the characteristic toi               TRUE.t  G               To change transport Congestion Avoidance values, you must D               invoke net$configure in ADVANCED mode and use Option 4C               (Configure Transports) and answer NO to the question.l    4         1-24 Using the ADVANCED Configuration Option i  s      I                                   Using the ADVANCED Configuration OptionsI                                         1.5 Configuring the OSI Transportg    B         1.5.2 Setting Up the OSI Loopback Test Application Account  G               If you answered YES to the "Configure the OSI Transport?" D               question described earlier, the procedure displays the               following prompt:h  N               * Username for OSI loopback test application to use? [SYSTEST] :  B               Press Return to accept the default user name for theG               application loopback test account. The procedure displayscH               a message stating that the default OSI templates have been               created.  O               %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates   /         1.5.3 Creating Additional OSI Templates   I               If you configure OSI transport, net$configure automaticallygH               creates the default OSI templates required by the OSAK andC               FTAM installation and verification procedures (IVPs).o  Q               * Do you want to create additional OSI templates?       [NO] :  yesS  E               If you answer YES to the previous prompt, the procedureeD               displays prompts to obtain the information required toH               configure the OSI template; otherwise, the procedure skipsA               to the Event Dispatcher question (see Section 1.6).   F               * Type of network service (CLNS/CONS/RFC1006)?  [CLNS] :  D               If you want to use Connectionless-mode Network ServiceA               (CLNS), press Return. If you want to use Connection F               Oriented Network Service (CONS), enter CONS. If you wantD               to use DECnet over TCP/IP and/or OSI applications over#               TCP/IP enter RFC1006.t  H               For more information about types of network service, referF               to the <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide or type a.               question mark (?) at the prompt.  I               Depending on which network service you select, you will seeo+               one of the following prompts:   N               * Name of the OSI template?               [OSIT$CLNS_Default0] :  N               * Name of the OSI template?               [OSIT$CONS_Default0] :  Q               * Name of the OSI template?               [OSIT$RFC1006_Default0] :-  I                              Using the ADVANCED Configuration Option 1-25t a  l      /         Using the ADVANCED Configuration Option )         1.5 Configuring the OSI Transporte    F               Enter the name you want to use for the OSI template (forD               example, OSI_TEMPLATE_1) or press Return to accept the(               default OSI template name.  N               * Will this template be used for inbound packets?              :  >               If you want this template to be used for inboundE               connections, enter YES. If you want this template to be 6               used for outbound connections, enter NO.  I               * Transport Classes to support?                       [4] :a  B               Enter the number of the transport protocol class youD               want to use for this template. DECnet-Plus for OpenVMSB               supports three transport protocol classes: 0, 2, andD               4. If you select CONS as the network service type, theA               default is 0, 2, 4. If you select CLNS, the defaultMD               is 4. If you select RFC 1006, the default is 0, 2. YouA               can also configure multiple OSI templates. For moreaH               information about transport protocol classes, refer to theH               <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide or type a question%               mark (?) at the prompt.e  $         1.5.3.1 CLNS Network Service  F               If you select the network service CLNS, you will see the               following prompt:h  H               * Use full CLNP or Null Internet?            [Full CLNP] :  >               A CLNS OSI transport template can specify use ofG               Internet/ES-IS routing protocols or Null Internet routing I               protocol. The Null Internet protocol only operates over LANo               routing circuits.g  G               A CLNS OSI transport template for use with Internet/ES-ISnH               routing protocols can use any routing circuits configured;E               the Routing module determines the most suitable circuiteE               to use. A CLNS OSI transport template for use with NullDI               Internet routing protocol can only use one routing circuit;3E               routing circuit selection is based on its inactive area(               address.  D               If you want to create additional OSI templates and you@               answer Null Internet to the "Use full CLNP or NullE               Internet?" prompt, the procedure displays the following5               prompt:   4         1-26 Using the ADVANCED Configuration Option ]         I                                   Using the ADVANCED Configuration Option I                                         1.5 Configuring the OSI Transport     W               * Which routing circuit is this Null Internet template for?  [CSMACD-0] :.  D               Enter the routing circuit you want to use for the CLNSH               OSI transport template (for use with Null Internet routing               protocol).  P               * Which CLNS Inactive Area to use?                   [49::FF-00] :  C               A CLNS OSI transport template that specifies the NullNI               Internet routing protocol selects the routing circuit basedsB               on the inactive area address of the routing circuit.  D               If you plan to support Null Internet routing, you mustE               configure an inactive area address for the circuit. TheGE               inactive area address for the circuit must be differenttD               than any area addresses used by DECnet-Plus routers onF               the same LAN. If you plan to configure more than one LANH               routing circuit on this system, and you need Null InternetH               on each circuit, then each circuit should have a different$               inactive area address.  E               The CLNS inactive area must be the same as the inactiver?               area set in routing for Null Internet to be used.v  $         1.5.3.2 CONS Network Service  C               If you selected CONS as the network service type, the 6               procedure displays the following prompt:  L               * CONS template name?                                        :  ;               Enter the CONS template name you want to use.   F               The CONS template name must be the same as the name usedB               for the X25 Access template for you to make any CONS               connections.  H               If the CONS template is used for inbound packets, you will'               see the following prompt:   L               * CONS filter name?                                          :  I               Enter the CONS filter name you want to use. The CONS filtermH               name should be the same as the name being used for the X25G               Access filter. If it is not, you will not be able to makem#               any CONS connections.e  I                              Using the ADVANCED Configuration Option 1-27n    y      /         Using the ADVANCED Configuration Optiont)         1.5 Configuring the OSI Transporte    D               For the network services CLNS, CONS, and RFC 1006, the.               following prompts are displayed:  L               * Allow use of expedited data?                         [YES] :  F               If you want to support the use of expedited data, answer               YES.  L               * Allow use of Checksums?                              [YES] :  E               If you want to use the error correction feature, answero               YES.  (         1.5.3.3 RFC 1006 Network Service  F               If you select the network service RFC 1006, you will see#               the following prompt:   L               * Local RFC1006 port number?                           [102] :  G               Enter the outgoing port number to use when establishing arG               transport connection at the TCP level. For pure RFC 1006,rH               use 102 as the port number. If you want to use DECnet over1               TCP/IP, use 399 as the port number.   G               If the RFC 1006 template is used for inbound packets, you ,               will see the following prompt:  L               * RFC1006 listener port number?                        [102] :  G               Enter the incoming port number to use when establishing aoH               transport connection at the TCP level. This number must beI               the same as the local RFC 1006 port number for the templatet-               to be used for inbound traffic.i  L               * Do you want to create additional OSI templates?       [NO] :  H               This prompt allows you to create additional customized OSIG               templates. If you answer YES to this prompt, the templatesE               questions are repeated. If you answer NO, the procedurea8               proceeds to the Event Dispatcher question.  B               For more information on configuring DECnet-Plus overD               TCP/IP, and the OSI applications over TCP/IP, refer to               Section B.5.1.  4         1-28 Using the ADVANCED Configuration Option n  l      I                                   Using the ADVANCED Configuration OptionhH                                      1.6 Configuring an Event Dispatcher    +         1.6 Configuring an Event Dispatcherr  F               The Event Dispatcher is a utility to receive and displayC               event messages. You can either take the default Event F               Dispatcher configuration, or you can choose to customize1               the Event Dispatcher configuration.   J               * Do you want to customize the Event Dispatcher?      [NO] :  F               Answer YES if you want to customize the Event DispatcherD               configuration. Answer NO if you want the default Event,               Dispatcher configuration only.  D               If you answer YES, the procedure displays prompts thatG               allow you to customize the Event Dispatcher. The specific >               prompts are listed and explained in Section 3.8.  7               If you answer NO, the procedure displays:   [               %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration   F               If you chose the default Event Dispatcher configuration,C               you have the option of displaying the events that are G               logged to the console of this machine. If you do not want F               to see the events logged to the console of this machine,:               net$configure will block the events for you.  Q               * Display the events logged to the console of this machine? [YES] :   /         1.7 Configuring an Application Databasen  E               The following questions determine if you want to set up H               and use a default account for application objects. You canE               create default accounts for the following applications:o5               FAL, CML, MAIL, VPM, MIRROR, and PHONE.e  V               * Do you want to use a default account for the 'FAL' application? [NO] :  B               File access listener (FAL) is an image that providesF               authorized access to the file system of a DECnet node onE               behalf of processes executing on any DECnet node in the I               network. FAL communicates with the initiating node by means G               of the Data Access Protocol (DAP). If you want an account 1               set up or used for FAL, answer YES.a  W               * Do you want to use a default account for the 'CML' application? [YES] :v  I                              Using the ADVANCED Configuration Option 1-29i           /         Using the ADVANCED Configuration Optiont/         1.7 Configuring an Application Databasen    ?               CMIP Management Listener (CML) is the DECnet-Plus E               management module that implements the Common ManagementeH               Information Protocol (CMIP). It is a utility that providesH               access to CMIP. If you want an account set up and used for               CML, answer YES.  Z               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER  X               * Do you want to use a default account for the 'MAIL' application? [YES] :  F               If you want to use the OpenVMS MAIL utility, answer YES.  [               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVERo  W               * Do you want to use a default account for the 'VPM' application? [YES] :   C               If you want the system to be an OpenVMS Cluster node,nH               answer YES. The VMScluster Performance Monitor (VPM) needsF               an account on your system to support the OpenVMS MonitorI               utility command monitor cluster. Answer NO if the system is -               to be a non-cluster end system.   D               If you answer YES, you will see the following message:  Z               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER  Z               * Do you want to use a default account for the 'MIRROR' application? [YES] :  G               MIRROR is used for some forms of loopback testing. If your-               want to use MIRROR, answer YES.   \               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER  Y               * Do you want to use a default account for the 'PHONE' application? [YES] :   E               The PHONE utility allows users on the same or differentoI               OpenVMS systems to communicate interactively. If you intendt;               to use the OpenVMS PHONE utility, answer YES.i  \               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER  '         1.8 Configuring a Cluster Aliasy  E               The following steps describe how to configure a cluster                alias.  ?               1. If the node is an OpenVMS Cluster member or ifaG                  net$configure finds an alias NCL script on the system, F                  the procedure prompts you to enter the full name of a                  cluster alias.i  4         1-30 Using the ADVANCED Configuration Option    e      I                                   Using the ADVANCED Configuration Option H                                          1.8 Configuring a Cluster Alias    Y                  * Full name of Cluster Alias                         : ACME:.WABBIT.HELPd  H                  If you do not want the node to participate in a cluster%                  alias, press Return.   H                  If you want the node to participate in a cluster alias,C                  specify the full name that uniquely identifies the E                  cluster alias node (for example, ACME:.WABBIT.HELP).   E               2. If you entered a cluster alias full name in response C                  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   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-c:                  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:g  D                  a. Convert the Phase IV node address to its decimal*                     equivalent as follows:  K                     (area-number * 1024) + node-number = decimal equivalentiD                     (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 thel%                     following format:a  .                     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]  :E  I                              Using the ADVANCED Configuration Option 1-31t a  S      /         Using the ADVANCED Configuration Options'         1.8 Configuring a Cluster Alias     I                  The selection weight determines the number of sequential F                  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 valueeI                  of zero. Specify a nonzero selection weight if this nodeDE                  is connected locally to a dual-ported disk, or if ittE                  will be serving any multihost disks, such as RFxx orrG                  HSC-connected disks, to other cluster members. DIGITALg4                  recommends values between 0 and 10.  5         1.9 Configuration Summary and Network Startupi  G               The following describes the configuration summary and the                network startup.  -               1. The procedure then displays:   ;                                    Summary of Configuration$  !                  Node Informationa8                         Node Type:              L2ROUTERK                         Directory Services Chosen:      DECDNS,LOCAL,DOMAINn>                         Primary Directory Service:      DECDNSB                         DECdns Full name:       ACME:.WABBIT.ELMER<                         Local Full name:        LOCAL:.ELMER'                         Fully QualifiedrE                         Host name:              ELMER.WABBIT.ACME.EDU 5                         Node Synonym:           ELMERc5                         Phase IV Address:       15.27t4                         Phase IV Prefix:        49::H                         Autoconfiguration of Network Addresses: DisabledH                         Session Control Address Update Interval:      103                         Routing ESHello Timer:  600n            4         1-32 Using the ADVANCED Configuration Option t         I                                   Using the ADVANCED Configuration OptionsI                             1.9 Configuration Summary and Network Startupe    $                  Device Information:-                         Device: ESA0 (DESVA):a8                                 Data Link name: CSMACD-0@                                 Routing Circuit Name:   CSMACD-09                                 L1 circuit cost:        8r9                                 L2 circuit cost:        8(:                                 L1 router priority:     64:                                 L2 router priority:     64  '                  Transport Information:e  I                        NSP Transport:                          Configured F                           Maximum number of logical links:         200E                           Maximum Transmit and Receive Window:     20 G                           Maximum Receive Buffers:                 4000   H                        OSI Transport:                         ConfiguredF                           Maximum number of logical links:         200E                           Maximum Transmit and Receive Window:     20nG                           Maximum Receive Buffers:                 4000e  4                        Congestion Avoidance Disabled  0                  Event Dispatcher Configuration:  4                         Sinks:            local_sink6                         Outbound Streams: local_stream1                         Phase IV Relay:   Enabled.  O                  * Do you want to generate NCL configuration scripts?   [YES] :   @                  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 scriptsf  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                 ______________________________________________________  I                              Using the ADVANCED Configuration Option 1-33  e  t      /         Using the ADVANCED Configuration Option 5         1.9 Configuration Summary and Network Startup     =               2. The procedure displays the following prompt:i  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.eI                  When you answer NO, the procedure displays the followingn                  message:i  U                  ******************************************************************** M                  You have decided not to start the network. NET$CONFIGURE.COM S                  cannot complete your system's network configuration since it needsoP                  the network to be partially started in order to perform certainU                  operations.  As a result, your system may be left in an inconsistenttR                  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 the O                  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. U                  ********************************************************************e  +                  Network Startup Incompletet  E                  DIGITAL recommends that you answer YES and start theo                  network.O  D               3. When you choose to start the network, the procedure?                  displays information similar to the following:C  W                  Copyright (c) Digital Equipment Corporation 1996. All rights reserved.                   .                  .                  .Y                  %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is                   RUNNING-MAJOR  ^                  sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespac  9                  Your default namespace nickname is ACME.E  [                  Your default namespace NSCTS is 08-00-2B-0D-2E-89-23-5B-15-9E-F1-85-95-00.E                    Node 007                  at 1996-01-26-14:12:24.170-04:00I0.404w  4         1-34 Using the ADVANCED Configuration Option w         I                                   Using the ADVANCED Configuration Option[I                             1.9 Configuration Summary and Network Startuph    ^                  %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER  *                  Directory Service: DECdns  D               4. You can ignore the Error - Node name lookup failure(                  message during startup.  1                  Error - Node name lookup failurel(                       ACME:.WABBIT.ELMER  0                  Number of nodes reported on:  0  Z                  %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the)                  DECdns directory serviceu  3                  Directory Service: Local name file0  1                  Error - Node name lookup failure "                       LOCAL:.ELMER  0                  Number of nodes reported on:  0  Z                  %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   .                  Number of nodes registered: 1.                  Number of nodes modified:   0  Z                  %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the)                  DECdns directory serviceO  3                  Directory Service: Local name fileu  [                  Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT   .                  Number of nodes registered: 1.                  Number of nodes modified:   0  Z                  %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the(                  LOCAL directory service                    Node 0 7                  at 1996-01-26-14:13:25.980-04:00I0.411N  K                  %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to #                  ACME:.WABBIT.ELMERO  I                              Using the ADVANCED Configuration Option 1-35            /         Using the ADVANCED Configuration Optiont5         1.9 Configuration Summary and Network StartupD    L                  Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMER7                  at 1996-01-26-14:13:35.360-04:00I0.411i  P                  %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node  B                  Node 0 Session Control Backtranslation Softlink *7                  at 1996-01-26-14:13:43.360-04:00I0.412o  B                  Node 0 Session Control Backtranslation Softlink *7                  at 1996-01-26-14:13:43.370-04:00I0.412o  Z                  %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for nodeX                  %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration                  completed                  $  E                  You have just completed the initial configuration offC                  a DECnet-Plus for OpenVMS system. It should now belD                  operational on the network. You can now use the SET@                  HOST command to connect to other network nodes.                                                  4         1-36 Using the ADVANCED Configuration Option                         I                                                                         2sI         _________________________________________________________________   I                                                    Managing Name Services     G               If this is the first time you are configuring the DECnet- G               Plus for OpenVMS software on your system, the informationwF               in this chapter further explains some of the topics that<               appear as you run the configuration procedure.  #         2.1 Names Services Overview1  E               While configuring DECnet-Plus, the system administrator C               specifies one or more of the following directory nameMG               services to use on the node: the Local namespace, DECdns,d3               or Domain Name System (for DNS/BIND).   G               o  Local namespace - A discrete, nondistributed namespace D                  that stores name and address information locally inH                  database files. DECnet-Plus includes a Local namespace.  ?               o  DECdns - DIGITAL's Distributed Name Service, au2                  distributed, global name service.  G               o  Domain Name System - The Domain Name System (DNS/BIND),7                  supported for storage of IP addresses.T  A               For more information on name services, refer to the +               <REFERENCE>(DNPLUS_PLANNING).'  !         2.1.1 The Local Namespace   D               DECnet-Plus includes a Local namespace, independent ofC               DECdns, that is designed to scale to at least 100,000                nodes.  I               The Local namespace is a discrete, nondistributed namespaceiF               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 2-1I R                  Managing Name Services#         2.1 Names Services Overview     F               DECnet-Plus recognizes that when a node full name beginsI               with LOCAL:, information for that node is stored in a Localu               namespace.  @               Unlike DECdns, the Local namespace does not employB               backtranslation directories for address-to-node-name               translation.  *         2.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.@               The following are typical node full names properlyC               formatted for the Local namespace: LOCAL:.xyz.abc andf               local:.maximum.i  ,         2.1.1.2 Managing the Local Namespace  C               The DECdns distributed namespace is not a requirement F               for DECnet-Plus, and the Local namespace does not dependD               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 B               namespace. Instead, use decnet_register. The decnet_H               register tool is described in the <REFERENCE>(DNPLUS_OVMS_               NET_MGMT) guide.  ;         2.1.2 The DIGITAL Distributed Name Service (DECdns)T  D               DECdns is a networkwide service that makes it possibleE               to use network resources without knowing their physicallE               location. Users and applications can assign DECnet-PlustE               names to resources such as nodes. The creator of a name D               also supplies other relevant information for DECdns toG               store, such as the resource's network address. Users then I               need to remember only the name, and DECdns acts as a lookupoE               service, providing the rest of the data when necessary.c      "         2-2 Managing Name Services           I                                                    Managing Name ServicesaI                                               2.1 Names Services Overviewe    (         2.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 ifmF               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 this H               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.e  @               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,8               refer to the <REFERENCE>(DNPLUS_PLANNING).  G               To create a new namespace while configuring a DECnet-Plusl!               for OpenVMS system:   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 of I               the full name of every subsequent system in the network and F               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, &               servers, clerks, files).  :               DIGITAL recommends that you create namespaceB               directories before using the configuration procedureG               (net$configure.com) to create the namespace. Follow thesef4               steps to create namespace directories:  I               1. Invoke decnet_register and select option 10 ("Manage the %                  directory service").u  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 the '                  namespace directories.   I                                                Managing Name Services 2-3y    f               Managing Name Services#         2.1 Names Services Overviewo    E               3. When finished, invoke the configuration procedure toC*                  create the new namespace.  ?               For more information on decnet_register, refer to 0               <REFERENCE>(DNPLUS_OVMS_NET_MGMT).  +         2.1.2.2 Creating a DECdns Namespace   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>   F               If this is a new DECdns namespace, net$configure promptsG               you for more information once the configuration procedure E               completes and you have started the network. The startup ;               information will be similar to the following:   _               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-s               MAJORi  5               The namespace you specified was NEW_NS.r  V               %DNS-E-NOMATNS, The specified namespace is not being served on your LAN.;                       please choose from the following list                   [ 1]  BB_NS                [ 2]  DOMAIN                 [ 3]  LOCAL                [ 4]  X500   )                [ 0]  - Reject this list -   8                 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 thisrG               node ?" does not appear in the list. To continue, enter 0 2               and press Return to reject the list.  Q                      If you are installing DECnet-Plus for VMS for the first timeiP                      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:  S               Do you want to proceed with creating a new namespace [n]: y  <Return>   "         2-4 Managing Name Services e  v      I                                                    Managing Name ServicesiI                                               2.1 Names Services Overview     A               At this point, the configuration procedure needs todC               determine whether you intend to configure your systembD               as a clerk on a WAN (connect to an off-LAN server), orC               create a new namespace. Since you cannot create a newgH               namespace unless you have installed DECdns server softwareI               on the 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 namespacecE               and the appropriate directories. The procedure displayssI               information about the namespace, the directories, and othermG               network parameters, then tells you when the configuration_               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.   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 00000122o  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:.mrv042kM               %NET$CONFIGURE-I-NEWNAMESPACE, a new namespace has been createda  U               %NET$CONFIGURE-I-ADDGROUP, adding .WorldRead_Group to the new namespacem  7               Create the initial namespace directories.oH               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 2-5d S                  Managing Name Services#         2.1 Names Services Overview     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.u  7               Creating the NEW_NS:.DNA_Registrar group. A               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. Q               Creating the NEW_NS:.DNA_BackTranslation.%X470027.%X0002 directory.R=               Creating the NEW_NS:.DNA_NodeSynonym directory. D               Creating the NEW_NS:.DTSS_GlobalTimeServers directory.  I               DECdns namespace initialization for DECnet use is complete.   U               If this is the first time you have initialized the namespace for DECnetS9               use, use SYS$SYSTEM:DECNET_REGISTER.EXE to:   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.o  \                 - 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.c  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 defaulteZ                   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 nodesS0                   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.  "         2-6 Managing Name Services           I                                                    Managing Name Services I                                               2.1 Names Services Overviewr    F               Additionally, you can use the DECdns control utility to:  V                 -  Add specific access control to individual directories, objects, and                    soft links.  2                 -  Create replicas of directories.  )               The following were created:i  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 directories   1               Registering the node NEW_NS:.mrv042 #                 Type is DECnet-Plusr!                 Synonym is MRV042   W               %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in theE'               !NEW_NS directory serviceo                 Node 02               at 1995-04-06-15:50:29.390-04:00Iinf  W               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to new_ns:.mrv042v  ?                       .               .                       .D?                       .               .                       . ?                       .               .                       . ?                       .               .                       . ?                       .               .                       .N  L               %NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded_               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-_               ALL__               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed             2.1.3 Domain Name System  B               Refer to your BIND server documentation for specificE               installation and configuration instructions. For a list I               of supported vendors, refer to the <REFERENCE>(DNPLUS_OVMS_gE               INSTALL_BASIC) guide. Any properly constructed DNS/BIND 3               nodename is supported by DECnet-Plus.t  I                                                Managing Name Services 2-7                     Managing Name Services#         2.1 Names Services Overview     "         2.1.4 Namespace Management  G               DECnet-Plus includes an in-memory naming cache to improvec@               performance of name and address resolution for allG               supported name services. Refer to the <REFERENCE>(DNPLUS_e8               OVMS_NET_MGMT) guide for more information.  E               DECnet-Plus includes several features to ease namespace ?               management including decnet_register (a namespaceIF               management tool), several Network Control Language (NCL)C               commands, and Common Trace Facility (CTF) support for :               monitoring node name and address resolution.  C               The decnet_register tool, an executable image located B               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 LocaltH               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, and G               enables autoregistration. Refer to the section on decnet_ I               register in the <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide for                more information.   $         2.2 Name Service Search Path  A               The name service search path applies systemwide and-E               allows DECnet-Plus to search a list of name services inLG               a predetermined order when looking up names or addressingeD               information. The search path includes naming templatesI               that tell DECnet-Plus how to interpret any abbreviated node %               names entered by users.t  F               The ordering of the name services is very important. TheC               first name service listed is the primary name serviceoC               to use on the system. The primary name service is thecD               first choice used when looking up names and addressingE               information. The remaining name services listed are thed9               secondary name services used on the system.P  G               The search path contains a list of name service keywords,vA               each followed by a naming template that specifies aaF               "defaulting rule" so users can enter shorter node names.  "         2-8 Managing Name Services a         I                                                    Managing Name Services I                                              2.2 Name Service Search PathE    5         2.2.1 Configuring the Search Path Informatione  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, thelD               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 properlyeG               formatted DECnet-Plus node full names (in the case of the F               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 foraI               the name service to be searched first. The second and thirdiH               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 specified E               by the system administrator. For example, if the system F               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 name C               service access features. Invoke net$configure.com andeF               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 enternC               more than one name service, separate each name with aa               comma.  F               For example, entering DECDNS,LOCAL,DOMAIN at the prompt,"               means the following:  E               o  You want to use the name services DECdns, Local, andi                  DNS/BIND.  4               o  The primary name service is DECdns.  I                                                Managing Name Services 2-9e s                  Managing Name Services$         2.2 Name Service Search Path    D               o  The secondary name services are Local and DNS/BIND.  F                 ________________________ Note ________________________  F                 If your node is also a DECdns server, the primary name'                 service must be DECdns..  F                 ______________________________________________________  /         2.2.1.1 Naming Search Path in a Cluster   C               All members in a cluster should have identical namingyD               search paths configured. This will help to ensure thatC               nodes are recognized in the various services you haveg               identified.o  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 systeme8               would indicate that there is no such node.  4         2.2.2 Displaying the Search Path Information  =               The system maintains two separate search paths:   G               o  One search path supports forward translation or namings4                  (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 patho  3         2.2.3 Modifying the Search Path Informationt  D               DIGITAL recommends that you rerun net$configure.com toI               revise the standard search path NCL script (NET$SEARCHPATH_fE               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").   F                 ________________________ Note ________________________  F                 Whenever you directly edit an existing NET$SEARCHPATH_?                 STARTUP.NCL script, or when you use the NCL setrB                 command to change the script (rather than changing  #         2-10 Managing Name Servicest e  o      I                                                    Managing Name ServiceseI                                              2.2 Name Service Search Pathl    @                 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                 ______________________________________________________  =         2.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 yourE               search path NCL script and do not want net$configure to E               overwrite these changes, you can create a site-specific D               search path NCL script by renaming the standard searchI               path script (NET$SEARCHPATH_STARTUP.NCL) to NET$SEARCHPATH_ @               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 2.2.6 to create site-specific namingt4               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                  ************************************************************** L                  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).sO                  **************************************************************4P               %NET$CONFIGURE-I-SITESEARCHPATH, invoking site-specific searchpath+                  NCL script found on system   E               The net$configure.com and net$startup.com procedures doUB               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-pG               specific search path NCL script, you must modify it priorc  I                                               Managing Name Services 2-11t .                  Managing Name Services$         2.2 Name Service Search Path    F               to invoking net$configure.com whenever you change any of5               the following name service information:n  =               o  The number of name services used on the nodev  @               o  The order of the name services used on the node  <               o  The specific name services used on the node  5         2.2.5 Using the Search Path to Ease Migrationd  F               A search path can be used to simplify migration from oneC               name service to another. The system administrator canAF               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 nodeoF               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. ThistH               causes the current secondary service to become primary, toD               be searched first for node and addressing information.  )         2.2.6 Setting Up Naming Templates   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 suppliesG               the name fin, then the full name ABCDE:.xyz.fin is lookedn+               up in DECdns namespace ABCDE.   E               You should specify only one asterisk per template. Only H               the first occurrence of an asterisk (*) in the template isE               substituted with the user-supplied name. Any additionaleA               asterisks are passed to the name service as part oftC               the full name. When you specify a template without anlI               asterisk, the template string is passed to the name service                unchanged.  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: "*".  #         2-12 Managing Name Servicese a         I                                                    Managing Name ServicesaI                                              2.2 Name Service Search Pathd    C               DECnet-Plus provides an NCL set command for modifyingMA               the naming templates associated with the naming and B               backtranslation search paths. Do not use the NCL setI               command to modify aspects of the search path other than the F               naming templates. The following NET$SEARCHPATH_LOCAL.NCLF               script creates typical naming and backtranslation searchI               paths. In this script ABCDE represents the DECdns namespace G               nickname. Your namespace nickname will appear in your NCL                script:e  =               SET NODE 0 SESSION CONTROL NAMING SEARCH PATH -nE                       ([DIRECTORY SERVICE = LOCAL, TEMPLATE = "*"], -nJ                       [DIRECTORY SERVICE = LOCAL, TEMPLATE = "local:*"], -K                       [DIRECTORY SERVICE = LOCAL, TEMPLATE = "LOCAL:.*"], -eE                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "*"], - K                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:*"], - P                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:.xyz.*"], -`                       [DIRECTORY SERVICE = DECDNS_SYNONYM, TEMPLATE = "ABCDE:.DNA_NodeSynonym.*"                       ], -E                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*"], -IQ                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*.xyz.ABCDE.com"]) C                       SET NODE 0 SESSION CONTROL BACK SEARCH PATH - D                       ([DIRECTORY SERVICE = LOCAL, TEMPLATE = ""], -^                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:.DNA_BackTranslation"], -B                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = ""])           2.3 Domain SynonymsI  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 pathE                  templates  *               o  By defining local aliases          I                                               Managing Name Services 2-13     _               Managing Name Services         2.3 Domain Synonymsp    E         2.3.1 Search Path Naming Template Support for Domain Synonyms   C               You can provide synonym support for entire domains by G               constructing an appropriate set of search path templates. H               Note that excessively long search paths (search paths withE               many entries) can increase the time it takes to look up H               node addresses. See Section 2.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 =                 - S                    { [Directory Service = Domain, Template = "*"],                -rS                      [Directory Service = Domain, Template = "*.finbar.com"],     -iS                      [Directory Service = Domain, Template = "*.abc.finbar.com"], -sQ                      [Directory Service = Domain, Template = "*.xyz.finbar.com"]}   G               This NCL command results in the following DNS/BIND naming                templates:                   *                  *.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 name I               koi to applications that require Phase IV style node names.d  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.e           2.3.2 Local Aliases   C               Another way to define a node synonym for a particulareH               node is by adding DNS/BIND alias names to the local host'sH               database. The following is an example using DIGITAL TCP/IP#               Services for OpenVMS:i  M               $ ucx set host koi.abc.finbar.com/address=aa.bb.cc.dd/alias=koin  A               DECnet-Plus will now return the node synonym koi tosB               applications that require Phase IV-style node names.  #         2-14 Managing Name Servicesc i         I                                                    Managing Name Services I                                              2.4 Node Synonym Directories     $         2.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).e  :         2.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 specialCH               characters or three or more dots, the system might produceI               an error. To avoid this, enclose the synonym directory namea%               in quotes. For example:r  K               $ define/system decnet_migrate_dir_synonym ".ch.noun.synonym"e  G               The net$configure procedure needs this logical name to besI               defined at all times if you wish to use a synonym directoryfI               other than .DNA_NodeSynonym. Be sure to add this definitionnF               to net$logicals.com to ensure that the definition of the2               synonym directory will be permanent.  *         2.4.2 When to Use the Logical Name  H               You can use the logical name as described in Section 2.4.1H               for either the BASIC or the ADVANCED configuration option.  E               You must define this logical name before you use any oft#               following procedures:h  "                  net$configure.com$                  decnet_register.exe#                  decnet_migrate.exea  I                                               Managing Name Services 2-15n ,                  Managing Name Services$         2.4 Node Synonym Directories    I               If synonym lookup fails in the namespace, the software doesd#               one of the following:n  E               o  The startup procedure defines SYS$NODE, SYS$CLUSTER_oI                  NODE, or both to be the first six characters of the lastSH                  simple name of the respective node full name or cluster                  full name.o  G               o  The configuration procedure defines SYS$NODE to be thesI                  node synonym name that was entered during configuration.h  E               The system displays a message that it has redefined thei               logical names.  A         2.5 Using a DNS Version 1 Namespace with DECdns Version 2:  G               If you are already using a namespace created with VersioniE               1 of the VAX Distributed Name Service (DNS) (running onnE               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 access D               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 only B               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-styleaI               access control entries in the namespace, you need to createeD               a backtranslation directory (.DNA_BackTranslation) andE               a node synonym directory (.DNA_NodeSynonym) in the rooteF               directory of the namespace. You must then populate theseG               directories by registering all the nodes participating inr&               the Version 1 namespace.              #         2-16 Managing Name Serviceso f         I                                                    Managing Name ServicessI                 2.5 Using a DNS Version 1 Namespace with DECdns Version 2.    C         2.5.1 Preparing a DNS Version 1 Namespace for Use by DECdnsi               Version 2h  G               To prepare a namespace created with DNS Version 1 for user1               by DECnet-Plus, follow these steps:a  E               1. Install and configure DECnet-Plus for OpenVMS on anycI                  node in your namespace that is not currently functioningaC                  as a DNS Version 1 server. Configure the node as a I                  DECdns Version 2 clerk. Refer to the <REFERENCE>(DNPLUS_ G                  OVMS_INSTALL_BASIC) guide if you plan to use the BASIC F                  configuration option. If you plan to use the ADVANCED7                  configuration option, see Section 1.1.   E               2. From any node running DNS Version 1 server software, H                  use the DNS Version 1 control program (DNS$CONTROL) addE                  access command to grant the following DNS Version 1- H                  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 namespace   H                  o  Read, write, delete, test, and control access to theG                     clearinghouse that stores the master replica of the "                     root directory  E                  For example, if the DECnet-Plus full name of the newhH                  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)_  [                  DNS> add access pastry::system clearinghouse .paris_ch /rights=(r,w,d,t,c)   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 acE                  backtranslation directory (.DNA_BackTranslation) andnF                  node synonym directory (.DNA_NodeSynonym) in the rootH                  directory of the namespace during the next step of this                  procedure.a  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 new  I                                               Managing Name Services 2-17e a                  Managing Name ServicesA         2.5 Using a DNS Version 1 Namespace with DECdns Version 2     E                 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.comeA                     menu to create and populate a backtranslationnH                     directory (.DNA_BackTranslation). Choose Option 2 toG                     create a node synonym directory (.DNA_NodeSynonym).*  B                  b. Choose Option 2 on the decnet_register menu toC                     register the new Version 2 clerk node (the nodehC                     you are logged in to) and to register all otherhH                     DECnet Phase IV nodes in the namespace including allI                     nodes that are currently functioning as DNS Version 1y                     servers.  F               Refer to the <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide forD               complete information on how to use the decnet_registerC               utility and the decnet_register_decdns.com utility toi"               perform these steps.  /         2.5.2 Using the DNS Version 1 NamespaceS  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 1oH               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 (see Section 3.4.5),rA               or convert existing DNS Version 1 servers to DECdns A               Version 2 format in the normal manner. Refer to the G               <REFERENCE>(DNPLUS_DNS_MGMT) guide for information on how H               to convert a DNS Version 1 clearinghouse to DECdns Version               2 format.   #         2-18 Managing Name Servicese o  a      I                                                    Managing Name ServicesrI                                   2.6 Registering a Node in the Namespacet    /         2.6 Registering a Node in the Namespaceh  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_register 0               Export/Import file is not created.  '         2.6.1 Export/Import File Formate  C               The decnet_register Export/Import file is a text filedG               that has the following format where <synonym> is the nodem=               synonym name you selected during configuration:   C               sys$manager:decnet_register_import_file_<synonym>.TXTp  )         2.6.2 Problems Registering a Node   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:o                 .                .s               .rX               Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT                  1) local:.elmer  8               Error - Node registration was unsuccessfulJ                       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.ELMER )                       Synonym:      elmer   U               You can choose to stop processing this command, continue executing this X               command until completion or until the next error, or ignore further errors)               and continue to completion.s  +               Number of nodes registered: 0k+               Number of nodes modified:   0s*               Number of update failures: 1  ^               %NET$CONFIGURE-E-COULDNOTREG, could not automatically register node in the LOCAL                 directory service  Y                    **********************************************************************r6                                                WARNING  I                                               Managing Name Services 2-19                     Managing Name Services/         2.6 Registering a Node in the NamespaceE    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 InstallationO]                    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):  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 (ChangeNY                    node name/namespace name) to complete the node's network configuration                     and startup.r  Y                    **********************************************************************w  I               If net$configure.com cannot access the DECdns namespace you 7               have selected, it is most likely because:n  >               o  The namespace is not available at the moment.  D               o  Your node does not have proper access to the DECdns                  namespace.s  G               o  The namespace you are using is new and the directoriesn+                  have not been created yet.T  C               When this happens, you will see the following messageyC               (this example uses ACME: as the namespace that is notp               accessible):  \                    *************************************************************************9                                                   WARNINGuV                    NET$CONFIGURE.COM cannot access the ACME: namespace, either becauseO                    the namespace is not available at the moment, your node doesdT                    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.  \                    When the problem is rectified, please use the DECNET_REGISTER import fileB                    to register your node into the ACME: namespace.  \                    *************************************************************************  #         2-20 Managing Name Services            I                                                    Managing Name ServicesrI                                   2.6 Registering a Node in the Namespace     G               If you receive this message because the namespace you are F               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:) G               to create the proper directories. For more details, refer =               to the <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide.   F               If you see the preceding warning messages, net$configureE               will display another message indicating how you or yoursF               namespace manager can attempt node registration once the/               problem is resolved. For example:c  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 Installatione]                    and Configuration guide for more details, or contact your network manager.t  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: D                       DECNET_REGISTER IMPORT DIRECTORY DECDNS FILE -?                           DECNET_REGISTER_IMPORT_FILE_ELMER.TXT   6                       For the LOCAL directory service:C                       DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE - ?                           DECNET_REGISTER_IMPORT_FILE_ELMER.TXTn  T                    Once the node has been successfully registered in the appropriateU                    directory service(s), invoke option 2 of NET$CONFIGURE.COM (ChangesY                    node name/namespace name) to complete the node's network configurations                    and startup.   Y                    **********************************************************************.  G               You may see the previous messages if the following exist:"  F               o  You enter LOCAL for the primary directory service and@                  DECDNS for the secondary directory service and,  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.   I                                               Managing Name Services 2-21  e                  Managing Name Services/         2.6 Registering a Node in the Namespace     F                  If this is the case, you or your network 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 notnD                     been created yet, use the decnet_register manageI                     command to invoke decnet_register_decdns.com (located H                     in sys$manager:) to create the .WorldRead_Group. ForG                     more details, refer to the <REFERENCE>(DNPLUS_OVMS_ $                     NET_MGMT) guide.  E                  2. Once you or your namespace manager knows that the A                     .WorldRead_Group has been created, invoke the C                     dns$control utility on the node with the DECdns <                     server and enter the following commands:  %                     $ mcr dns$control J                     DNS>add group <ns>:.worldread_group member local:.*..._                     DNS>add clear <ns>:.<ch_name> access <ns>:.worldread_group as group for r,ts  F                     where ns is the DECdns namespace name to which youF                     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 the I               proper access it needs to look up information regarding the 9               secondary DECdns full name you have chosen.V  F                 ________________________ Note ________________________  C                 If you use DECDNS for the primary directory serviceVD                 and LOCAL for the secondary directory service, these(                 steps are not necessary.  F                 ______________________________________________________              #         2-22 Managing Name Servicesr a  s                    I                                                                         3eI         _________________________________________________________________a  I                                         Modifying a Current Configurationn    D               This chapter describes the steps necessary to modify a$               current configuration.  0         3.1 Steps for Changing the Configuration  H               If your system has already been configured, you can modifyG               it with the net$configure basic configuration option (the G               default) or with the net$configure advanced configuration                option.o  @               Table 3-1 provides some guidelines for making your#               configuration choice.C  B               If you prefer to use the BASIC configuration option,H               refer to the <REFERENCE>(DNPLUS_OVMS_INSTALL_BASIC) guide,G               Chapter 6. If you want to customize your system's networkOC               configuration with the ADVANCED configuration option,u&               continue to Section 3.2.                                    I                                     Modifying a Current Configuration 3-1R E  N      )         Modifying a Current Configuratione0         3.1 Steps for Changing the Configuration    I         Table_3-1_Choosing_Your_Configuration_Option_____________________a  I         Option..._Choose_if...___________________________________________V  G         FAST      You are upgrading from a DECnet Phase IV node and youpB                   plan to use the existing Phase IV configuration.  /                   The node is not in a cluster.e  E                   You are running the configuration procedure for thei                   first time.u  I         _________________________________________________________________a  +         BASIC     The node is in a cluster.y  A                   You are upgrading or reconfiguring DECnet-Plus.a  @                   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 you1F                   have multiple devices, all of which will be used for-                   DECnet-Plus communications.   G                   You want to use the default names for all devices and #                   routing circuits.s  H                   You want to autoconfigure your network addresses only.  G                   You want to configure both the NSP and OSI transportstI                   and only want to create default OSI templates. You want G                   to enable both DECnet over TCP/IP or OSI applicationsl                   over TCP/IP.  I                   You do not want to enable FDDI large packet support (ifn1                   you have an FDDI-type circuit).N  @                   You want to set the routing characteristic DNAE                   address format to TRUE (this attribute controls the 9                   interpretation of address structuring)._  :                   You want to use integrated mode routing.  I         _________________________________________________________________w  0         ADVANCED  Your configuration is complex.  E                   You need to customize your network's configuration.   -         3-2 Modifying a Current ConfigurationD n  e      I                                         Modifying a Current ConfigurationtI                                  3.1 Steps for Changing the Configuration     I         Table_3-1_(Cont.)_Choosing_Your_Configuration_Option_____________   I         Option..._Choose_if...____________________________________________  I                   Your system has multiple communication devices, and youh6                   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 allpH                   devices and routing circuits. You also want the optionI                   of not configuring all of your devices for DECnet-Plus.r  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 packetp=                   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).i  E                   You want the option of using either integrated moded5                   routing or segregated mode routing.s  E                   You want the option to provide default accounts forNI         __________FAL.___________________________________________________o  6         3.2 Steps for Changing a Current Configuration  F               Changing your DECnet-Plus for OpenVMS configuration with?               the ADVANCED option involves the following steps:a  ?               1. Run net$configure procedure using the ADVANCEDsA                  configuration option with the following command:m  6                  $ @sys$manager:net$configure advanced  I                                     Modifying a Current Configuration 3-3i 1  e      )         Modifying a Current Configurationm6         3.2 Steps for Changing a Current Configuration    &                  The procedure starts:  T                     DECnet-Plus for OpenVMS ADVANCED network configuration procedure  U                  This procedure will help you create or modify the management scripts U                  needed to operate DECnet on this machine. You may receive help aboutiF                  most questions by answering with a question mark '?'.  X                  You have chosen the ADVANCED configuration option.  This option enablesY                  you to do some specific tailoring of your system's network configurationIY                  by answering some specific questions.  If you do not want to do specifictX                  tailoring of your system's network  configuration but instead  want  toX                  quickly  configure your  system using most  of the default answers, youY                  should invoke net$configure.com with the BASIC configuration option, ie: =                              @SYS$MANAGER:NET$CONFIGURE BASIC   O                  * Do you want to continue?                             [YES] :   I               2. Answer YES if you want to continue. You will now see theD?                  date that the checksum file was last modified:e  S                     Checksum file updated last by SYSTEM on 18-SEP-1995 16:04:24.19   C                    %NETCONFIGURE-I-VERCHECKSUM, verifying checksums   F                 ________________________ Note ________________________  >                 If this is the first time you are invoking theC                 net$configure procedure, or if you have deleted the C                 checksum file, the following menu is not displayed. @                 Instead, the prompts shown in Section 6.1 of theC                 <REFERENCE>(DNPLUS_OVMS_INSTALL_BASIC) guide appear >                 for the BASIC option, and the prompts shown in@                 Section 1.1 in this book appear for the ADVANCED                 option.T  F                 ______________________________________________________  2                             Configuration Options:  5                           [0]     Exit this procedure*        -         3-4 Modifying a Current Configuration            I                                         Modifying a Current ConfigurationsI                            3.2 Steps for Changing a Current Configurationn    A                           [1]     Perform an entire configurationb;                           [2]     Change naming information C                           [3]     Configure Devices on this machineu6                           [4]     Configure TransportsH                           [5]     Configure Timezone Differential Factor<                           [6]     Configure Event Dispatcher@                           [7]     Configure Application database?                           [8]     Configure MOP Client databaseb9                           [9]     Configure Cluster Alias B                           [10]    Replace MOP Client configuration;                           [11]    Configure satellite nodescD                           [12]    Configure cluster script locations  K                   * Which configuration option to perform?            [1] :   G               3. Choose the option you want. Selecting an option allows_C                  you to modify either the entire configuration or a $                  particular portion.  F                 ________________________ Note ________________________  A                 To select Options 10 or 11, you must have alreadyrF                 configured the system using the ADVANCED configurationC                 option, and net$configure is executing on a cluster*B                 system. See Section 3.14 and Section 3.15 for more                 information.  F                 ______________________________________________________  G               4. After you have completed the configuration dialog, thee8                  system displays the following question:  L                  * Do you want to generate NCL configuration scripts [YES] :  F                  If you answer YES, the configuration program uses theI                  information you entered to generate modified NCL scriptsAF                  and, in some cases, automatically modify the system'sF                  configuration. The configuration program then returnsE                  to the Configuration Options menu. If you answer NO,NI                  the configuration procedure returns to the Configuration D                  Options menu and does not generate any modified NCL                  scripts.       I                                     Modifying a Current Configuration 3-5a           )         Modifying a Current Configurationt6         3.2 Steps for Changing a Current Configuration    C               You can use the net$configure procedure to modify the E               current configuration. Depending upon which menu option I               you select, net$configure either modifies the configurationeF               automatically or produces modified NCL scripts which you;               can use to modify the system's configuration.*  ?               You can execute modified NCL scripts in two ways:e  %               o  Rebooting the system   E               o  Disabling the entity to which the script applies and .                  executing the modified script  G               To execute the NCL script, use the format ncl> do script-o                file. For example:  ?               ncl> do sys$manager:net$nsp_transport_startup.ncl   F                 ________________________ Note ________________________  B                 The net$configure procedure does not automaticallyB                 execute the modified NCL scripts for you. However,:                 it will execute the search path NCL script-                 (NET$SEARCHPATH_STARTUP.NCL).,  F                 ______________________________________________________  D               To customize your system beyond what the net$configureH               procedure provides, you must edit the NCL scripts producedD               by net$configure.com (refer to the <REFERENCE>(DNPLUS_H               OVMS_NET_MGMT) guide). DIGITAL recommends that you use theG               net$configure procedure for major modifications involvingd               an entire entity.i  ,         3.3 Changing an Entire Configuration  E               To make changes to the entire configuration, proceed asy               follows:  H               * Which configuration option to perform?             [1] :                 Select Option 1.  F               The system displays the same prompts that were displayedI               for the initial configuration. The prompts show the currentiH               configuration values as the default. If you do not want toH               change the current values, accept the default value. ReferD               to Section 1.1 for an explanation of the prompts shownF               for a net$configure ADVANCED configuration. Refer to the  -         3-6 Modifying a Current Configuration     N      I                                         Modifying a Current ConfigurationrI                                      3.3 Changing an Entire ConfigurationL    F               <REFERENCE>(DNPLUS_OVMS_INSTALL_BASIC) guide, Chapter 6,I               for an explanation of the prompts shown for a net$configureo"               BASIC configuration.  H               At the end of the procedure, you see the following prompt:  J               * Do you want to generate NCL configuration scripts? [YES] :  C               If you answer YES, the configuration program uses the*G               information you entered to generate modified NCL scripts. D               If you answer NO, the configuration procedure does not#               generate NCL scripts.d  I               If you generate NCL scripts, the procedure displays anotherv               prompt:   G               * Do you want to start the network?               [YES] :p  I               Answer YES to start the network and to complete the networkyE               configuration. To implement the NCL scripts, reboot the                system.s  1         3.4 Changing the Node Name/Namespace Name   G               To change the directory name services used on the system,hG               the system's full names or the fully qualified host name,fF               the namespace that the system uses, or the system's node*               synonym, proceed as follows:  H               * Which configuration option to perform?            [1] :2  /               Select Option 2 and press Return.a  I               If you are using either the BASIC or ADVANCED configurationa8               option, you will see the following prompt:  [               * Enter the directory services to use for the system   [LOCAL,DECDNS,DOMAIN]:   .         3.4.1 Changing Directory Name Services  E               Enter the directory name services you want to use. (TheEE               first service you enter is considered your primary name F               service; the default is the name service you entered for*               the previous configuration.)  I               Depending on the directory services you choose, you may seeD3               one or more of the following prompts:o  I                                     Modifying a Current Configuration 3-7  >         )         Modifying a Current Configuration 1         3.4 Changing the Node Name/Namespace Namee    @               * Enter the full name for directory service LOCAL:A               * Enter the full name for directory service DECDNS: A               * Enter the fully qualified host name for DNS/BIND:   -         3.4.2 Changing Node Name or Namespacee  D               To change the node name or the namespace that it uses,<               enter the node's new full name. The format is:  9               NamespaceNickname:.DirectoryPath.NodeObject   C               For DECdns, the namespace nickname is the name that a G               DECdns manager assigns to a namespace when installing and H               configuring DECdns server software. If the namespace has aI               nickname, you must enter the nickname as part of the node's D               full name. However, not all namespaces have nicknames.H               Namespaces are required to have nicknames only if there is5               more than one namespace on the network.   G               If you use the Local namespace, the namespace nickname is_               LOCAL:._  #         3.4.3 Changing Node Synonym   =               Next you will be prompted for the node synonym:   L               * What is the synonym name for this node?           [YEWHO1] :  I               The synonym name is a Phase IV-compatible node name. It can H               be one to six alphanumeric characters long, must not startE               with a number, and must be unique within the namespace.hG               It is required for Phase IV nodes using the namespace andoF               DECnet-Plus nodes that need to communicate with Phase IV               nodes.  G               The following display shows the system response to a nodee               name change.                -         3-8 Modifying a Current ConfigurationL S         I                                         Modifying a Current Configuration I                                 3.4 Changing the Node Name/Namespace Name                    .e               .                . I                %NET$CONFIGURE-I-NODERENAMED, node successfully renamed tor*                PHASEV:.ENG.SSG.TEST.ELMER1>                Update Node 0 Session Control Tower Maintenance*                PHASEV:.ENG.SSG.TEST.ELMER16                 at 1995-04-13-14:44:14.821-04:00I0.532               .e               ._               ._N                %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node  .                       Summary of Configuration                   Node Information:J                       Directory services chosen:       DECDNS,LOCAL,DOMAIN=                       Primary directory service:       DECdnsiI                       DECdns full name:       PHASEV:.ENG.SSG.TEST.ELMER1_;                       Local full name:        LOCAL:.ELMER1 %                       Fully QualifiedrD                       Host name:              ELMER1.WABBIT.ACME.EDU4                       Node Synonym:           ELMER13                       Phase IV Address:       15.27C2                       Phase IV Prefix:        49::E                       Autoconfiguration of Network Addresses: EnabledoF                       Session Control Address Update Interval:      101                       Routing ESHello Timer:  600n  "                Device Information:+                       Device: ESA0 (DESVA): >                               Data Link name:         CSMACD-0>                               Routing Circuit Name:   CSMACD-0  %                Transport Information:gH                       NSP Transport:                          ConfiguredD                         Maximum number of logical links:         200C                         Maximum Transmit and Receive Window:     20PE                         Maximum Receive Buffers:                 4000u  H                       OSI Transport:                          ConfiguredD                         Maximum number of logical links:         200C                         Maximum Transmit and Receive Window:     20 E                         Maximum Receive Buffers:                 4000   3                       Congestion Avoidance Disabled_  I                                     Modifying a Current Configuration 3-9D o  c      )         Modifying a Current Configuration 1         3.4 Changing the Node Name/Namespace Name     .                Event Dispatcher Configuration:2                       Sinks:            local_sink4                       Outbound Streams: local_stream/                       Phase IV Relay:   enabledt  H               The configuration program uses the information you enteredE               to automatically modify the system's configuration. The_C               program then returns you to the Configuration Optionsa               menu.h  C         3.4.4 Configuring a DECdns Clerk System to Use a WAN DECdns                Server  B               If your node is a DECdns clerk and the net$configureD               procedure detects that the namespace you identified inE               the system's DECdns full name is not served by a DECdns I               server on the LAN, it displays a list of all the namespacesc6               that do exist on the LAN as shown below:  5                 The namespace you specified was IAF2.   W                %DNS-E-NOMATNS, The specified namespace is not being served on your LAN. <                       Please choose from the following list:                  [ 1]  APOLLOi                [ 2]  IAF                [ 3]  MIDAS_NSi  )                [ 0]  - Reject this list -r  ,                 Pick a number from the list:  C               When you see this display, type 0 and press Return toeH               reject the list of namespaces currently known on your LAN.  F               The procedure then asks if you want to continue with the(               WAN configuration process.  O                  Attempts to configure DECdns via a LAN connection have failed.)  F                  Type Y to attempt a WAN connection to a remote DECdnsA                  server.  To stop DECdns Configuration and return E                  control to the NET$CONFIGURE  utility, type N at the "                  following prompt:  N                Do you want to connect to a remote DECdns server via a WAN [y]:  .         3-10 Modifying a Current Configuration o  p      I                                         Modifying a Current ConfigurationgI                                 3.4 Changing the Node Name/Namespace Names    E               Answer YES to connect to a remote server via a WAN. The F               procedure then prompts you for the remote server's PhaseB               IV-compatible address (if it has one) or its networkI               service access point (NSAP). The NSAP is the network entityiG               title (NET) with a valid transport selector. To find this I               information, contact the server's system administrator. ThepI               server system probably has a number of different NSAPs. YoutI               can use any of these NSAPs to connect to the server system,aF               but you must enter the NSAP in the format in which it is               displayed.  G                   Attempting to configure a clerk via a WAN connection.i  J                Enter the NSAP or Phase IV compatible address of the server&                you want to connect to:  H               After you enter the server's address (for example, 4.456),1               your system connects to the server.s  B               You then receive a confirmation message listing yourE               namespace nickname and its namespace creation timestampu+               (NSCTS), as in the following:e  1               Getting server data, please wait...   ]               sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.t  9               Your default namespace nickname is XYZ_CORP.  W               Your default namespace NSCTS is 00-12-34-56-77-A0-A1-A2-A3-A4-A5-A6-A7-B0c  F                 ________________________ Note ________________________  C                 If you are joining a Distributed Name Service (DNS)EC                 Version 1.1 namespace, make sure you have access to_C                 the remote server's sys$library:dns$ns_def_file.dat                  file.m  B                 Invoke the procedure sys$manager:dns$configure.comA                 and use Option 2 on the DECdns configuration menugA                 to connect to a remote DNS Version 1 server. Maken@                 sure the SYSTEM account on your DECdns Version 2B                 clerk has DECnet_FAL access or proxy access to theB                 sys$library:dns$ns_def_file.dat file on the remoteD                 Version 1 server. These accounts need this access toB                 successfully copy the Version 1 server informationF                 contained in the sys$library:dns$ns_def_file.dat file.C                 If you are running the DECdns configuration programg  I                                    Modifying a Current Configuration 3-11u n  o      )         Modifying a Current Configurations1         3.4 Changing the Node Name/Namespace Name     A                 under a privileged account other than SYSTEM, the >                 account still requires the appropriate access.  F                 ______________________________________________________  G               If you cannot connect to the remote server, the proceduref-               displays the following message:   >               %DNS-E-NOCONFIG, DECdns clerk is not configured.  I         3.4.5 Configuring a DECdns Server System in an Existing Namespace8  E               To configure additional DECdns servers into an existingoG               namespace, you must use the DECdns configuration program,eC               sys$system:dns$configure.exe. Be sure to refer to thetB               <REFERENCE>(DNPLUS_DNS_MGMT) guide for DECdns accessD               control information and for complete information aboutC               using the DECdns configuration program to configure aS7               DECdns server into an existing namespace.y  H         3.4.5.1 Configuring a DECdns Server in a DNS Version 1 Namespace  C               If you are already using a DNS Version 1 namespace (a_F               namespace created with Version 1 of the Distributed NameF               Service), you can configure one or more DECdns Version 2F               servers into that namespace. Before you try to configureG               a DECdns server into a DNS Version 1 namespace, make sure E               that the namespace has been prepared for use by DECnet-_H               Plus (see Section 2.5). For complete information on how toG               prepare a DNS Version 1 namespace for use by DECnet-Plus,gH               refer to the <REFERENCE>(DNPLUS_DNS_MGMT) guide for DECdns)               access control information.   F                 ________________________ Note ________________________  F                 The DECdns configuration program allows you to convertE                 your DNS Version 1 clearinghouses to DECdns Version 2uE                 format. By doing so, you get the improved performance B                 offered by the DECdns Version 2 server while usingD                 your existing DNS Version 1 namespace. If you intendF                 to convert your DNS Version 1 clearinghouses to DECdnsB                 Version 2 format, DIGITAL strongly recommends thatC                 you do not configure DECnet-Plus for OpenVMS on anyoA                 of your DNS Version 1 server nodes until you haven@                 prepared your DNS Version 1 namespace for use by                 DECnet-Plus.  F                 ______________________________________________________  .         3-12 Modifying a Current Configuration           I                                         Modifying a Current Configuration I                                 3.4 Changing the Node Name/Namespace Namec        !         3.5 Reconfiguring Devices   E               To reconfigure the devices, proceed as follows from thet)               Configuration Options menu:   H               * Which configuration option to perform?            [1] :3  /               Select Option 3 and press Return.   D               Before proceeding with this menu option, the procedureH               determines whether the system has network devices that are)               supported by net$configure.e  V               %NET$CONFIGURE-I-SCANCONFIG  scanning device configuration - please wait  F               If no supported network devices are found or new devicesD               are found that were not detected the last time you ranG               the net$configure procedure on this system, the procedure >               displays the following prompt for Alpha systems:  L               * Should a SYSMAN IO AUTO be executed?                       :  A               For VAX systems, you will see the following prompt:   F               * Should a SYSGEN AUTOCONFIGURE ALL be executed?       :  D               If you answer YES, the net$configure procedure invokesH               the SYSMAN IO AUTO or the SYSGEN AUTOCONFIGURE ALL commandF               to find devices. If you answer NO, then there will be no;               devices to configure and the procedure exits.o  C               The BASIC configuration automatically configures your.E               devices and asks no further questions concerning deviceyF               configuration. If you choose the ADVANCED configuration,G               the procedure prompts you for data link names and routingw3               circuit names to use for each device.p  N               * Data Link name to use for ESA0 (DESVA)            [CSMACD-0] :  G               Specify the simple name you want to use for the data linkeI               device or accept the system-supplied default. If you do not F               want this device configured for DECnet-Plus, enter NONE.  N               * Routing Circuit Name for Data Link 'CSMACD-0'     [CSMACD-0] :  I                                    Modifying a Current Configuration 3-13            )         Modifying a Current Configuratione!         3.5 Reconfiguring Deviceso    E               Specify the simple name you want to use for the routingoD               circuit or accept the system-supplied default. DIGITALB               recommends that you use the default name even if you8               configure multiple lines of the same type.  L               * Level 1 Cost for Routing Circuit 'CSMACD-0'?           [8] :N               * Level 1 Router Priority for Routing Circuit 'CSMACD-0'? [64] :  C               If your DECnet-Plus system is a router, then you will B               be asked for this information for the routing levels               supported.  I               Cost indicates the cost of traffic on a particular circuit.yG               Priority refers to the priority for becoming a designated 4               router on a LAN at level 1 or level 2.  Q               * Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] :   G               If you previously specified a Phase IV-compatible addressh@               in order to communicate with Phase IV nodes (as inG               Section 1.2.6), entering YES to the question above allows A               Phase IV messages to be transmitted on the circuit. B               Answering NO to this question means that no Phase IV:               messages will be transmitted on the circuit.  F                 ________________________ Note ________________________  F                 Phase-IV addressing can be enabled on only one routingC                 circuit. If you are using large packet support with A                 FDDI, you must ensure that Phase-IV addressing is 3                 enabled on an FDDI routing circuit.y  F                 ______________________________________________________  4         3.6 Reconfiguring the NSP and OSI transports  E               To reconfigure the NSP, OSI transports, or both, select D               Option 4 from the Configuration Options menu and press               Return.i  J               * Which configuration option to perform?             [1] : 4  B               The BASIC configuration automatically configures the@               NSP and OSI transports. If you choose the ADVANCEDE               configuration option, the procedure asks if you want to 3               configure the NSP and OSI transports.   I               For more information on configuring NSP and OSI transports, "               see also Appendix B.  .         3-14 Modifying a Current Configuration w  l      I                                         Modifying a Current ConfigurationcI                              3.6 Reconfiguring the NSP and OSI transports     B               The following sections describe the prompts that are5               required to reconfigure the transports.t  L               * Configure the NSP Transport?                         [YES] :L               *   Maximum number of logical links ?                  [200] :L               *   Maximum Transmit and Receive Window ?               [20] :L               *   Maximum Receive Buffers  ?                        [4000] :L               * Configure the OSI Transport?                         [YES] :L               *   Maximum number of logical links ?                  [200] :L               *   Maximum Transmit and Receive Window ?               [20] :L               *   Maximum Receive Buffers  ?                        [4000] :L               *   Run OSI Applications over TCP/IP ?                 [YES] :L               *   Run DECnet over TCP/IP ?                           [YES] :M               * Is this system operating in a multi-protocol network? [YES] :hP               * Do you want to replace the existing NSP transport script? [NO] :[               * Are the point-to-point lines utilizing line speeds less than 9600 BPS? [NO] P               * Do you want to replace the existing OSI transport script? [NO] :  L               * Configure the NSP Transport?                         [YES] :  H               If you want to communicate with any DECnet Phase IV nodes,               answer YES.m  E               To determine the maximum number of active NSP transport H               connections allowed at any one time to this transport, the6               procedure displays the following prompt:  L               * Maximum number of logical links?                     [200] :  @               You are then prompted to set the following values:  L               * Maximum transmit and receive window?                  [20] :  L               * Maximum receive buffers?                            [4000] :  F               DIGITAL recommends setting a value of 20 for the maximumG               transmit and receive window option. The recommended value H               to set the maximum receive buffers is no more than maximumC               window multiplied by maximum transport connection for H               normal network operation in a typical network environment.  G               Selecting other values than these can significantly alter H               the behavior of your system and network and should only beH               done after a thorough analysis of your network traffic and'               application requirements.f  I                                    Modifying a Current Configuration 3-15o d  s      )         Modifying a Current Configuration 4         3.6 Reconfiguring the NSP and OSI transports    @               High values of maximum receive buffers may requireF               considerable buffering capacity on your node; therefore,G               a non-paged pool should be allocated accordingly. If yourIG               node does not have enough non-paged pool, maximum receive C               buffers should be set to a smaller value than maximum:A               window multiplied by maximum transport connections.W  @               The transport receiver's window is determined by aC               combination of maximum transport connections, maximum E               receive buffers, and maximum window. During the life ofiH               the connection, the receiver quota fluctuates according toG               the value of maximum receive buffers divided by currently F               active connections. The credit window sent to the remoteG               transmitter may or may not be this quota value, depending I               on the value of maximum window. If maximum window is set to I               less than the determined receiver quota, this value is used G               instead for the credit granted to the remote transmitter.   G               The transmitter of a transport connection uses the credit H               sent by the remote receiver as its transmit window, unlessH               its maximum window is a lower value. In that case, maximum8               window is used for the transmitter window.  L               * Configure the OSI Transport?                         [YES] :  D               If you want the system to communicate with DECnet-PlusC               nodes or if you plan to install the OSAK, FTAM, or VT F               software, answer YES. If you want to use the DECnet overE               TCP/IP and/or OSI applications over TCP/IP, answer YES.   A               If you answer NO, the procedure still loads the OSIcH               transport images. However, OSI transport is not configuredE               or usable until you run the net$configure procedure andN7               answer YES to the OSI transport question.N  E               To determine the maximum number of active OSI transport H               connections allowed at any one time to this transport, the6               procedure displays the following prompt:  L               * Maximum number of logical links?                     [200] :  @               You are then prompted to set the following values:  K               * Maximum transmit and receive window?                 [20] :a  K               * Maximum receive buffers?                           [4000] :   .         3-16 Modifying a Current Configuration           I                                         Modifying a Current ConfigurationoI                              3.6 Reconfiguring the NSP and OSI transportsd    F               DIGITAL recommends setting a value of 20 for the maximumG               transmit and receive window option. The recommended value H               to set the maximum receive buffers is no more than maximumD               window multiplied by maximum transport connections forH               normal network operation in a typical network environment.  G               Selecting other values than these can significantly alterSH               the behavior of your system and network and should only beH               done after a thorough analysis of your network traffic and'               application requirements.   @               High values of maximum receive buffers may requireF               considerable buffering capacity on your node; therefore,G               a non-paged pool should be allocated accordingly. If yourtG               node does not have enough non-paged pool, maximum receiveNC               buffers should be set to a smaller value than maximumeA               window multiplied by maximum transport connections.f  @               The transport receiver's window is determined by aC               combination of maximum transport connections, maximum E               receive buffers, and maximum window. During the life of H               the connection, the receiver quota fluctuates according toG               the value of maximum receive buffers divided by currentlyhF               active connections. The credit window sent to the remoteG               transmitter may or may not be this quota value, dependingeI               on the value of maximum window. If maximum window is set tonI               less than the determined receiver quota, this value is usedtG               instead for the credit granted to the remote transmitter.r  G               The transmitter of a transport connection uses the creditsH               sent by the remote receiver as its transmit window, unlessH               its maximum window is a lower value. In that case, maximum8               window is used for the transmitter window.  $               You are then prompted:  L               * Run OSI Applications over TCP/IP?                    [YES] :  H               Answer YES to this question if you want to run any of yourI               OSI applications over TCP/IP. This causes the configuration D               utility to build the appropriate RFC 1006 template and5               establish a listener port for port 102.E  L               * Run DECnet over TCP/IP?                              [YES] :  I                                    Modifying a Current Configuration 3-17o h  e      )         Modifying a Current Configurationo4         3.6 Reconfiguring the NSP and OSI transports    G               Answering YES to this question enables DECnet-Plus to runlG               over a TCP/IP network to any system that has enabled thisDH               same feature. The configuration utility builds appropriateH               RFC 1859 template and establishes a listener port for port               399.  B               You are then prompted about multi-protocol networks:  N               * Is this system operating in a multi-protocol network?  [YES] :  A               If you take the default answer of YES, then the OSI_G               transport and NSP Congestion Avoidance characteristic arecH               set to FALSE. Note that currently NSP does not support the-               Congestion Avoidance attribute.D  E               A NO answer to this question sets the characteristic toe               TRUE.n  B               If an NCL script already exists for an NSP transportF               and you answer YES to the "Configure the NSP Transport?"B               prompt, the procedure displays the following prompt:  P               * Do you want to replace the existing NSP transport script? [NO] :  G               If you reconfigure the NSP transport, you have the option E               of accepting the existing transport script or replacing F               it with a new one. Answer YES if you want to replace the,               existing NSP transport script.  [               * Are the point-to-point lines utilizing line speeds less than 9600 BPS? [NO]   F               You will be prompted only if you have any point-to-pointE               lines (i.e., any synchronous and/or asynchronous lines) I               configured. If you have any point-to-point lines running at H               low line speeds (lower than 9600 bits/s), answer YES. ThisG               places additional NSP NCL commands into the NSP transportsE               NCL script to accommodate the lower line speeds. If yourH               do not have any point-to-point lines being utilized at low%               line speeds, answer NO.   P               * Do you want to replace the existing OSI transport script? [NO] :  @               Answer YES if you want to replace the existing OSI               transport script.m  H               If you answer YES to the "Configure OSI Transport?" promptD               and you want to replace the existing OSI transport NCLA               script, the procedure displays the following prompt 3               (ADVANCED configuration option only):N  .         3-18 Modifying a Current Configuration    c      I                                         Modifying a Current ConfigurationmI                              3.6 Reconfiguring the NSP and OSI transportsD    N               * Username for OSI loopback test application to use? [SYSTEST] :  B               Press Return to accept the default user name for the0               application loopback test account.  %               The procedure displays:_  O               %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates   H               If you use the ADVANCED configuration option, you will see$               the following prompts:  L               * Do you want to create additional OSI templates?       [NO] :  H               This prompt allows you to create additional customized OSIF               templates. If you answer YES, the template questions are               repeated.e  7               If you answer NO, the procedure displays:n  9                                  Summary of Configuration                    Node Information:G                     Directory services chosen:      DECDNS,LOCAL,DOMAIN :                     Primary directory service:      DECDNS>                     DECdns Full Name:       ACME:.WABBIT.ELMER8                     Local Full name:        LOCAL:.ELMER#                     Fully QualifiedoA                     Host name:              ELMER.WABBIT.ACME.EDU 1                     Node Synonym:           ELMERr                       .       .l                       .       .   "                Device Information:(                    Device: ESA0 (DESVA):;                              Data Link name:       csmacd-0r;                              Routing Circuit Name: csmacd-0e  %                Transport Information:uH                       NSP Transport:                          ConfiguredD                         Maximum number of logical links:         200C                         Maximum Transmit and Receive Window:     20iE                         Maximum Receive Buffers:                 4000o    I                                    Modifying a Current Configuration 3-19u e  u      )         Modifying a Current Configurationr4         3.6 Reconfiguring the NSP and OSI transports    H                       OSI Transport:                          ConfiguredD                         Maximum number of logical links:         200C                         Maximum Transmit and Receive Window:     20 E                         Maximum Receive Buffers:                 4000   3                       Congestion Avoidance Disabledy.                              .               ..                              .               .L               * Do you want to generate NCL configuration scripts?   [YES] :  C               If you answer YES, the configuration program uses the F               information you have entered to create the Transport NCLD               scripts. The configuration program then returns to theC               Configuration Options menu. To implement the modifiedsE               NCL scripts, reboot the system or disable the transporta/               entities and execute the scripts.t  F               If you answer NO, the configuration procedure returns toF               the Configuration Options menu and does not generate NCL               scripts.  D         3.7 Reconfiguring the Time Zone Differential Factor (DECdts)  @               DECdts binary time values are based on CoordinatedB               Universal Time (UTC), an international time standardD               that has largely replaced Greenwich Mean Time (GMT) asD               a reference. For most measurement purposes, UTC is theI               equivalent of GMT. However, time zones are still determinedIG               by their relationship to the prime meridian in Greenwich,yD               England. The local time in each time zone or locale isA               determined by its offset, or differential, from theeF               Greenwich time zone. This value is commonly expressed asH               a time differential factor (TDF) of a positive or negative               number of hours.  7         3.7.1 Selecting the DECdts Configuration Optiono  @               To reconfigure DECdts, proceed as follows from the)               Configuration Options menu:s  H               * Which configuration option to perform?            [1] :5  /               Select Option 5 and press Return.     .         3-20 Modifying a Current Configuration g         I                                         Modifying a Current Configuration_I              3.7 Reconfiguring the Time Zone Differential Factor (DECdts)     "               The system displays:  F                DTSS$CONFIG-I-LOGS Deassigning system timezone logicals  >                DTSS$CONFIG-I-STOPDTS  Deleting the DTSS Entity                  Node 0 DTSS3                at 1995-08-04-18:36:19.740+00:00Iinf                   Node 0 DTSS3                at 1995-08-04-18:36:23.960+00:00Iinf   '                       Timezone Options:o  9                       [0]     Exit Timezone Configurationc  ;                       [1]     Choose a timezone using menus B                       [2]     Use Universal Coordinated Time (UTC)<                       [3]     Type in your own timezone rule  G               * Enter an option number                            [1] :   D               The following sections explain each of the DECdts menu               options.  F                 ________________________ Note ________________________  ?                 Changes made to DECdts take effect immediately.t  F                 ______________________________________________________  2         3.7.2 Configuring Your System's Local Time  C               When you are initially configuring a system, you must H               determine its geographical location and designate its timeF               zone rule (TZR), which is based on the location. The TZRI               contains the abbreviated name of the system's time zone and:G               the applicable TDF, so that DECdts can calculate UTC from0I               the system (local) time during the initial configuration of G               the DECdts software. The TZR also contains information on H               any seasonal adjustments to the TDF that normally apply in%               the selected time zone.E  C               If you want to select the commonly accepted TZR for asB               given area and system, you can use the net$configureD               procedure menus to select the geographical location ofD               the system. Based on your selection, the net$configureG               procedure automatically sets the TZR. After you configureeE               your system, it displays the local time even though theSE               DECdts software uses UTC in the background. Because then  I                                    Modifying a Current Configuration 3-21            )         Modifying a Current Configuration D         3.7 Reconfiguring the Time Zone Differential Factor (DECdts)    H               default value of the DECdts management attribute AutomaticI               TDF Change is TRUE, DECdts also changes the displayed local:I               time automatically if there is a seasonal adjustment to the                system's TDF.a  F               In rare instances, you may want to customize the TZR forF               your system, thereby modifying its TDF from the one thatD               normally applies in a given time zone or location. TheG               net$configure menus also provide a selection for enteringsF               a custom TZR for your system, although you must know theE               TZR syntax to enter it. See Section 3.7.2.3 for furtherm:               information on customizing the system's TZR.  I               After the initial system configuration, you can reconfigure C               the system's time zone rule (TZR) by selecting Option A               5 in the top-level net$configure menu. For example,aC               this may be necessary because you moved the system to D               a different location. To reconfigure the TZR, you mustH               know the system's geographical location, or in some cases,F               the time zone. If you do not know the system's time zoneF               and the configuration procedure requires you to enter itF               for your locale, refer to the world time zone map in theH               <REFERENCE>(DNPLUS_DTS_MGMT) guide. Additionally, when youG               reconfigure the DECdts software, you are given the optionlI               of setting the system's time to UTC time or customizing thee-               system's time to any time zone.r  F         3.7.2.1 Configuring Your System's Local Time Using Menus (Menu                 Option 1)   H               Option 1 of the Timezone Options menu allows you to chooseB               the geographical region and conventional TZR for theF               system. DECdts uses the TZR to automatically convert UTCF               to the local time whenever the time is displayed. To use+               Option 1, proceed as follows:   F               * Enter an option number                           [1] :  .               Press Return to select Option 1.  C               The procedure displays a menu of continental regions:         .         3-22 Modifying a Current Configuration           I                                         Modifying a Current Configuration I              3.7 Reconfiguring the Time Zone Differential Factor (DECdts)     /                        Timezone Region Options:m  A                       [0]     Return to the Timezone Options menu   $                       [1]     Europe+                       [2]     North America 5                       [3]     Central & South America-$                       [4]     Africa"                       [5]     Asia+                       [6]     South Pacificw(                       [7]     Antarctica  H               * Enter a timezone region number                        :2  E               Enter the option number for the region where the systemrI               resides and press Return, or return to the previous menu by                typing 0.f  F               If you select a region, the procedure displays a menu ofD               subregions within the region you select. The subregionF               you select determines the time zone rule for the system.E               For example, if you enter Option 2 (North America), the 4               procedure displays the following menu:  2                        Timezone Subregion Options:  :                      [0]     Return to Region Options menu                                    I                                    Modifying a Current Configuration 3-23            )         Modifying a Current ConfigurationCD         3.7 Reconfiguring the Time Zone Differential Factor (DECdts)    '                      [1]     US/Eastern ,                      [2]     US/East-Indiana'                      [3]     US/CentralA(                      [4]     US/Mountain'                      [5]     US/Pacifici&                      [6]     US/Alaska'                      [7]     US/Arizonae&                      [8]     US/Navajo(                      [9]     US/Michigan(                      [10]    US/Aleutian&                      [11]    US/Hawaii%                      [12]    US/Samoa 0                      [13]    Canada/Newfoundland,                      [14]    Canada/Atlantic+                      [15]    Canada/Easterne+                      [16]    Canada/Centrala5                      [17]    Canada/East-Saskatchewan ,                      [18]    Canada/Mountain+                      [19]    Canada/Pacificb)                      [20]    Canada/Yukon   G               * Enter a timezone subregion number                   : 1   C               Enter the option corresponding to the subregion where F               the system resides; in the example, the system is in theD               eastern United States. After you make a selection, theI               procedure executes and displays information on the NCL DTSS I               module subroutines that initialize the DECdts software withe               the new settings:D  B               DTSS$CONFIG-I-LOGS Defining system timezone logicals6               DTSS$CONFIG-I-SETLCL Setting Local ClockK               %RUN-S-PROC_ID, identification of created process is 00000059h                 Node 0 DTSSe2               at 1995-02-25-08:17:29.520-05:00Iinf                 Node 0 DTSS 2               at 1995-02-25-08:17:30.790-05:00Iinf  7               Node 0 Event Dispatcher Outbound Stream *d2               at 1995-02-25-08:17:30.950-04:00Iinf                 Node 0 DTSSd4               at 1995-02-25-08:17:39.978-05:00I0.327  .         3-24 Modifying a Current Configuration           I                                         Modifying a Current Configuration I              3.7 Reconfiguring the Time Zone Differential Factor (DECdts)i                   Node 0 DTSSr4               at 1995-02-25-08:17:45.868-05:00I0.328                 Characteristicss  ,                  Automatic TDF Change = True                 Node 0 DTSSq4               at 1995-02-25-08:17:51.898-05:00I0.328  ?               DTSS$CONFIG-I-STARTDTS Restarting the DTSS Entity K               %RUN-S-PROC_ID, identification of created process is 0000006B                  Node 0 DTSS 2               at 1995-02-25-08:18:06.138-05:00Iinf                 Node 0 DTSS 2               at 1995-02-25-08:18:07.488-05:00Iinf  7               Node 0 Event Dispatcher Outbound Stream *o2               at 1995-02-25-08:18:08.560-04:00Iinf  I               This completes changes to DECdts configuration using Optionu               1.  H         3.7.2.2 Configuring Your System's Local Time as UTC (Menu Option                 2)  ?               If your system is located in the GMT time zone ore>               Antarctica, and you do not want to make seasonalE               adjustments to the TDF, you may want to use UTC as yourbE               system's local time. You can also configure all networkgH               systems with UTC if you consider local time irrelevant forH               your applications. If you select UTC as the local time andE               later enter the NCL command show dtss current time, thea9               local time displayed has a TDF of 0 (zero).i  C               The following example shows how to select UTC for thes"               system's local time.  (                        Timezone Options:  9                       [0]     Exit Timezone Configuration   ;                       [1]     Choose a timezone using menus B                       [2]     Use Universal Coordinated Time (UTC)<                       [3]     Type in your own timezone rule  H               * Enter an option number                            [1] :2  I                                    Modifying a Current Configuration 3-25            )         Modifying a Current Configuration D         3.7 Reconfiguring the Time Zone Differential Factor (DECdts)    H         3.7.2.3 Customizing Your System's Time Zone Rule (Menu Option 3)  @               The net$configure procedure allows you to create aE               customized time zone rule (TZR) for your system, ratherh@               than selecting a location and having the procedureH               configure a TZR for you. When you create a customized TZR,G               you must supply the correct abbreviation for the system'ssA               time zone, the zone's offset from GMT, and optionalhF               seasonal time-change information. If you do not know theI               system's time zone or time zone abbreviation, see Table 3-2 G               in this book, and the world time zone map in the appendixN8               of the <REFERENCE>(DNPLUS_DTS_MGMT) guide.  F               The following example shows the TZR syntax and describesI               the TZR fields; you can also display similar information byaG               typing a question mark (?) after you choose Option 3 fromr(               the Timezone Options menu.  (                        Timezone Options:  9                       [0]     Exit Timezone Configuration   ;                       [1]     Choose a timezone using menusuB                       [2]     Use Universal Coordinated Time (UTC)<                       [3]     Type in your own timezone rule  M               * Enter an option number                                 [1] :3t                                    .         3-26 Modifying a Current Configuration .         I                                         Modifying a Current ConfigurationII              3.7 Reconfiguring the Time Zone Differential Factor (DECdts)V    :               STDoffset[DSToffset,start[/time],end[/time]]  C               STD         Specify three or more characters that aretC               DST         the designation for the standard (STD) oraF                           summer/daylight-saving time (DST) time zone.A                           The variable STD is required; if DST is E                           missing, then summer time does not apply in F                           this locale. Uppercase and lowercase lettersI                           are explicitly allowed. Any characters except a I                           numeral, comma (,), minus (-), plus (+), space, 4                           and ASCII NUL are allowed.  F               offset      Specifies the value to be added to the localC                           time to arrive at UTC. The offset has theBH                           format hh[:mm[:ss]]; the hour (hh) is requiredI                           and can be a single digit. The minutes (mm) and G                           seconds (ss) are optional. One or more digits I                           can be used; the value is always interpreted as I                           a decimal number. The hour must be between zeronF                           and 24; the minutes and seconds (if present)E                           between zero and 59. If preceded by a minus2E                           (-), the time zone is east of Greenwich; ifiH                           preceded by a (+) or not signed, it is west ofF                           Greenwich. Note that the signing conventionsE                           are based on POSIX rules, which reverse ISO .                           signing conventions.                                      I                                    Modifying a Current Configuration 3-27b o  o      )         Modifying a Current Configuration D         3.7 Reconfiguring the Time Zone Differential Factor (DECdts)      D               start       Indicate when to change to and from summerH               end         time. The variable start describes the date ofF                           the change to summer time, and end describesG                           the date of the change back to standard time.f;                           The start and end format follows:   F                              Jn - The Julian day n (1 < n < 365). LeapH                              days are not counted. That is, in all yearsI                              (including leap years) February 28 is day 59cG                              and March 1 is day 60. It is impossible tosH                              explicitly refer to the occasional February                               29.I                              n - The zero-based Julian day (0 < n < 365). I                              Leap days are counted, and it is possible to 2                              refer to February 29.G                              Mm.n.d - The nth d day of month m (1 < n <iF                              5, 0 < d < 6, 1 < m < 12). When n is 5 itG                              refers to the last d day of month m. Day 0s'                              is Sunday. E                              time - The time field describes the timerD                              when, in current time, the change to orG                              from summer time occurs. The variable timedF                              has the same format as offset except thatE                              no leading sign (- or +) is allowed. TheeH                              default, if time is not given, is 02:00:00.  G               As an example of a typical TZR, if the rule has the value D               EST5EDT4,M4.1.0,M10.5.0, it describes the rule for theD               eastern United States, which became effective in 1987.E               EST is the designation for Eastern Standard Time, which G               is 5 hours behind GMT. EDT is the designation for Eastern D               Daylight-Saving Time, which is 4 hours behind GMT. EDTF               starts on the first Sunday in April and ends on the lastG               Sunday in October. In both cases, because the time is not I               specified, the change to and from EDT occurs at the defaultD               time of 2:00 a.m.e  G               Since the TZR format is complex, you may want to refer to:I               Table 3-2 to copy the rule for your locale onto the command06               line, and then edit the rule as desired.        .         3-28 Modifying a Current Configuration z         I                                         Modifying a Current Configuration I              3.7 Reconfiguring the Time Zone Differential Factor (DECdts)     I               Table_3-2_Time_Zone_Rules__________________________________o  I               Region_Name______Time_Zone_Rule_____________Notes__________   I               Europe_____________________________________________________   ,               Eastern          EET-2EET_DST-2               European Time    3,M3.5.0/3,M9.5.0/3  #               Iceland          WET0   ,               Middle European  MET-1MET_DST-2               Time             2,M3.5.0/2,M9.5.0/2  ,               Poland           MET-1MET_DST-2                                2,M3.5.0/1,M9.5.0/1  ,               Turkey           EET-3EET_DST-2                                4,M3.5.0/1,M9.5.0/1  '               UK-Ireland       GMT0BST- 3                                1,M3.5.0/1,M10.5.0/1i  +               Western          WET0WET_DST- 2               European Time    1,M3.5.0/1,M9.5.0/1                                        I                                    Modifying a Current Configuration 3-29t s  f      )         Modifying a Current ConfigurationnD         3.7 Reconfiguring the Time Zone Differential Factor (DECdts)    I               Table_3-2_(Cont.)_Time_Zone_Rules__________________________   I               ___________________________________________________________   I               North_America______________________________________________   :               Canada/Atlantic  AST4ADT3,M4.1.0/2,M10.5.0/2  :               Canada/Central   CST6CDT5,M4.1.0/2,M10.5.0/2  :               Canada/Eastern   EST5EDT4,M4.1.0/2,M10.5.0/2  #               Canada/East-     CST6r               Saskatchewan  :               Canada/Mountain  MST7MDT6,M4.1.0/2,M10.5.0/2  @               Canada/NewfoundlaNST3:30NDT2:30,M4.1.0/2,M10.5.0/2  :               Canada/Pacific   PST8PDT7,M4.1.0/2,M10.5.0/2  :               Canada/Yukon     YST9YDT8,M4.1.0/2,M10.5.0/2  <               US/Alaska        AKST9AKDT8,M4.1.0/2,M10.5.0/2  =               US/Aleutian      HAST10HAST9,M4.1.0/2,M10.5.0/2   #               US/Arizona       MST7s  :               US/Central       CST6CDT5,M4.1.0/2,M10.5.0/2  :               US/Eastern       EST5EDT4,M4.1.0/2,M10.5.0/2  #               US/East-Indiana  EST5e  $               US/Hawaii        HST10  :               US/Michigan      EST5EDT4,M4.1.0/2,M10.5.0/2  :               US/Mountain      MST7MDT6,M4.1.0/2,M10.5.0/2  :               US/Navajo        MST7MDT6,M4.1.0/2,M10.5.0/2  :               US/Pacific       PST8PDT7,M4.1.0/2,M10.5.0/2  $               US/Samoa         SST11  .         3-30 Modifying a Current Configuration    .      I                                         Modifying a Current Configuration I              3.7 Reconfiguring the Time Zone Differential Factor (DECdts)     I               Table_3-2_(Cont.)_Time_Zone_Rules__________________________m  I               ___________________________________________________________o                 Central & SouthoI               America____________________________________________________a  :               Brazil/Acre      AST5ADT4,M10.4.6/2,M2.2.6/2  :               Brazil/DeNoronha FST2FDT1,M10.4.6/2,M2.2.6/2  :               Brazil/East      EST3EDT2,M10.4.6/2,M2.2.6/2  :               Brazil/West      WST4WDT3,M10.4.6/2,M2.2.6/2  A               Chile/Easter     EST6EDT5,M10.2.0/0,M3.2.0/0(EastergB                                                           Islands)  :               Chile/Regional   CST4CDT3,M10.2.0/0,M3.2.0/0  :               Cuba             CST5CDT4,M5.2.0/0,M10.2.0/0  :               Jamaica          EST5EDT4,M4.1.0/2,M10.5.0/2  #               Mexico/General   CST6   :               Mexico/BajaNorte PST8PDT7,M4.1.0/2,M10.5.0/2  #               Mexico/BajaSur   MST7   I               ___________________________________________________________tI               Africa_____________________________________________________s  ,               Egypt            EET-2EET_DST-.                                3,J152/2,J305/2  ,               Libya            EET-2EET_DST-.                                3,J121/2,J303/2              I                                    Modifying a Current Configuration 3-31d i  a      )         Modifying a Current Configuration D         3.7 Reconfiguring the Time Zone Differential Factor (DECdts)    I               Table_3-2_(Cont.)_Time_Zone_Rules__________________________   I               ___________________________________________________________e  I               Asia_______________________________________________________   $               Hong Kong        HKT-8  +               Iran             IST-3:30IDT-t5                                4:30,M3.5.0/2,M9.3.0/2   (               Israel           IST-3IDT-2                                4,M4.3.0/2,M8.4.6/2  $               Japan            JST-9  (               PRC              CST-8CDT-2                                9,M4.2.0/2,M9.2.0/3  $               ROC              CST-8  (               ROK              KST-9KDT-4                                10,M5.2.0/2,M10.2.0/3  $               Singapore        SST-8  I               ___________________________________________________________yI               South_Pacific______________________________________________   '               Australia/North  CST-9:30m  )               Australia/NSW    EST-10EST-h4                                11,M10.5.0/2,M3.1.0/3  I               Australia/QueenslEST-10                     (Standard Time)   D               Australia/QueenslEST-10EST-                 (NSW time)4                                11,M10.5.0/2,M3.1.0/3  +               Australia/South  CST-9:30CST- 7                                10:30,M10.4.0/2,M3.3.0/3g  )               Australia/TasmaniEST-10EST-t4                                11,M10.4.0/2,M3.3.0/3  )               Australia/VictoriEST-10EST- 4                                11,M10.4.0/2,M3.3.0/3  $               Australia/West   WST-8  +               New Zealand      NZST-12NZDT- 4                                13,M10.5.0/2,M3.1.0/3  .         3-32 Modifying a Current Configuration           I                                         Modifying a Current Configuration I              3.7 Reconfiguring the Time Zone Differential Factor (DECdts)     I               Table_3-2_(Cont.)_Time_Zone_Rules__________________________d  I               Region_Name______Time_Zone_Rule_____________Notes__________   I               Antarctica_________________________________________________a  I               Antarctica_______UTC0______________________________________   .         3.8 Reconfiguring the Event Dispatcher  H               1. To reconfigure the Event Dispatcher, proceed as follows5                  from the Configuration Options menu:i  M                  * Which configuration option to perform?             [0] : 6   2               2. Select Option 6 and press Return.  S                  %NETCONFIGURE-I-EVDFND, Event dispatcher NCL script already existstK                  * Replace Event Dispatcher NCL script file?         [NO] :C  H                  If you want to create a new Event Dispatcher NCL scriptE                  file, answer YES. If you want to keep the previouslyIG                  generated Event Dispatcher NCL script file, answer NO.i  G                  The BASIC configuration option automatically creates a I                  default Event Dispatcher configuration for you. You then )                  see the display summary.i  H               3. With the ADVANCED configuration, you have the option to?                  customize your Event Dispatcher configuration.S  K                  * Do you want to customize the Event Dispatcher?    [NO] :i  A                  If you answer NO, the procedure uses the default >                  configuration. You see the following message:  ^                  %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration  D                  You then see the following prompt (for the ADVANCED                   configuration):  L                  * Display events logged to the console of this machine?   :  >               4. If you answer YES to the "Customize the Event?                  Dispatcher?" question, the procedure displays:i  K                  * Configure a Sink?                                [YES] :   I                                    Modifying a Current Configuration 3-33            )         Modifying a Current Configuration .         3.8 Reconfiguring the Event Dispatcher    F                  If you want to customize information pertinent to theE                  sink, answer YES (for example, if you want to change.F                  where to send the output: a terminal, a printer, or aE                  file). If you answer YES, the procedure displays thet"                  following prompt:  K                  * Sink name?                                [local_sink] :t  E                  Specify the name of the sink you want to use for them6                  local node (for example, local_sink).  K                  * Maximum buffer size?                                   :p  C                  Specify the maximum number of octets that the sink ?                  allows to process events (for example, 16384).                                                             .         3-34 Modifying a Current Configuration    s      I                                         Modifying a Current Configuration I                                    3.8 Reconfiguring the Event Dispatcher     K                  * Object name?                                           :s  E                  Specify the DECdns full name of the object for which B                  the sink accepts incoming connections. Unless theG                  value of this characteristic is null, the sink employsfE                  the Session Control layer's Keep me Here function tou;                  maintain the object name in the namespace.   K                  * End user specification?                                :e  G                  Specify the DIGITAL Network Architecture (DNA) SessionoA                  Control local address for which the sink acceptso?                  incoming connections (for example, number=82).n  K                  * Catch all filter action?                               :a  C                  Specify the action to take if neither the specificnE                  filter setting nor the global filter setting matches,G                  an event, or if a filter setting that matches an event 3                  is set to ignore. The choices are:e  .                  o  BLOCK - Discard the event.  ,                  o  PASS - Report the event.  K                  * Description?                                           :   D                  Specify an informational string that can be used to#                  describe the sink.s  K                  * Display UIDs?                                          :u  G                  Answering YES displays the entity's unique identifier, ?                  which is generated when the entity is created.   K                  * Client type?                                           :   D                  Specify how the application is to accept the events7                  received by the sink. The choices are:t  G                  o  CONSOLE - Events go the operator's console (OPCOM).   3                  o  DEVICE - Events go to a device.   /                  o  FILE - Events go to a file.   E                  If you answer FILE to the "Client type?" prompt, thef9                  procedure displays the following prompt:f  L                  * File name?                                              :  H                  Enter the file specification you want to use to captureB                  events (for example, sys$manager:evd_events.log).  I                                    Modifying a Current Configuration 3-35n           )         Modifying a Current Configurationd.         3.8 Reconfiguring the Event Dispatcher    G                  If you answer DEVICE to the "Client type?" prompt, theU9                  procedure displays the following prompt:r  L                  * Device name?                                            :  H                  Enter the device you want to use to capture events (for!                  example, TWA1:).   L                  * Configure another Sink?                            [NO] :  D                  If you do not want to configure another sink, pressA                  Return to proceed to the next prompt. If want to D                  configure another sink, enter YES and press Return.I                  The procedure returns you to the "Sink name?" prompt and H                  repeats the prompts required to configure another sink.  I               5. If you want to configure an outbound stream, answer YES.   L                  * Configure an Outbound Stream?                     [YES] :  I                  Specify the outbound stream name that you want to manage ?                  with this command (for example, local_stream).   L                  * Outbound Stream name?                    [local_stream] :  F                  Specify the number of octets that the outbound streamE                  allows to process events. This value is derived fromiI                  (but is not necessarily equal to) the value specified in G                  the maximum buffer size argument of the create command &                  (for example, 16384).  L                  * Maximum buffer size?                                    :  I                  Specify the number of seconds to wait between connection H                  attempts. The connect retry timer operates continuouslyG                  from the time the outbound stream is enabled until the F                  stream is disabled or until the connect timer enabledG                  characteristic is set to FALSE. If the outbound stream I                  is already connected to the sink when the timer expires, C                  no connection is attempted at that time. The timer E                  resets and connection attempts continue whenever the                   timer expires.0  L                  * Connect retry timer?                                    :  H                  Answer YES to have the connect retry timer operational.)                  Answer NO to disable it.   L                  * Connect timer enabled?                                  :  .         3-36 Modifying a Current Configuration .         I                                         Modifying a Current Configuration I                                    3.8 Reconfiguring the Event Dispatcher     F                  Specify the number of seconds to wait before shuttingF                  down an idle connection. A 0 value indicates that theG                  disconnect timer is not operating and that connectionsi6                  are never disconnected automatically.  L                  * Disconnect timer?                                       :  C                  Specify the action to take if neither the specific E                  filter setting nor the global filter setting matchesfI                  an event or if a filter setting that matches an event isl0                  set to Ignore. The choices are:  .                  o  BLOCK - Discard the event.  ,                  o  PASS - Report the event.  L                  * Catch all filter action?                                :  @                  Specify the full DECdns object name of the sinkG                  associated with this outbound stream. This object nameu>                  is used to make the connection with the sink.  M                  * Sink object?                                             :s  B                  Specify the full node name (DECdns namespace nameG                  included) of the sink associated with outbound stream.   M                  * Sink node?                                               :   H                  Specify the sink Session Control end user specificationF                  of the sink associated with this outbound stream (for%                  example, number=82).   M                  * Sink end user?                                           :   F                  Specify the sink address tower of the sink associated+                  with this outbound stream._  M                  * Sink address?                                            :_  I                  If you do not want to configure another outbound stream,_H                  press Return to proceed to the next prompt. If you wantD                  to configure another outbound stream, enter YES andI                  press Return. The procedure returns you to the "Outbound I                  Stream name?" prompt and repeats the prompts required toT3                  configure another outbound stream.,  M                  * Configure another Outbound Stream?                  [NO] :   I                                    Modifying a Current Configuration 3-37            )         Modifying a Current Configuration .         3.8 Reconfiguring the Event Dispatcher    F               6. Answer YES to use the Phase IV Relay. This allows youF                  to record and process events that occur on an OpenVMSG                  system running DECnet-VAX Phase IV software. The Phase D                  IV Relay entity receives the events from a Phase IVG                  node, encapsulates them, and posts them in the DECnet- .                  Plus system Event Dispatcher.  M                  * Configure Phase IV Relay?                          [YES] :_  (                  The procedure displays:  ?                                        Summary of ConfigurationC  #                   Node Information: L                        Directory services chosen:        DECDNS,LOCAL,DOMAIN?                        Primary directory service:        DECDNS A                        DECdns full name:       ACME:.WABBIT.ELMERa;                        Local Full name:        LOCAL:.ELMER &                        Fully QualifiedD                        Host name:              ELMER.WABBIT.ACME.EDU4                        Node Synonym:           ELMER4                        Phase IV Address        15.273                        Phase IV Prefix:        49::MD                        Autoconfiguration of Network Address: EnabledG                        Session Control Address Update Interval:      10 2                        Routing ESHello Timer:  600  %                   Device Information: ,                        Device: XQA0 (DELQA):9                                 Data Link name:  CSMACD-0 A                                 Routing Circuit Name:    CSMACD-0   ;                        Device: ASYNC (floating async line):S<                                 Data Link name:  ASY_DDCMP-0D                                 Routing Circuit Name:    ASY_DDCMP-0  (                   Transport Information:L                           NSP Transport:                          ConfiguredG                            Maximum number of logical links:         200 F                            Maximum Transmit and Receive Window:     20H                            Maximum Receive Buffers:                 4000        .         3-38 Modifying a Current Configuration           I                                         Modifying a Current Configuration,I                                    3.8 Reconfiguring the Event Dispatcher     K                          OSI Transport:                          ConfiguredaG                            Maximum number of logical links:         200 F                            Maximum Transmit and Receive Window:     20H                            Maximum Receive Buffers:                 40006                          Congestion Avoidance Disabled  1                   Event Dispatcher Configuration:l4                         Sinks:            local_sink6                         Outbound Streams: local_stream1                         Phase IV Relay:   Enabled_  M                  * Do you want to generate NCL configuration scripts? [YES] :_  F                  If you answer YES, the configuration program uses theG                  information you entered to create the Event Dispatcher F                  NCL script. The configuration program then returns toG                  the Configuration Options menu. To implement the EventiH                  Dispatcher NCL script, reboot the system or disable the/                  entity and execute the script.c  I                  If you answer NO, the configuration procedure returns to_I                  the Configuration Options menu and does not generate NCL_                  scripts.   2         3.9 Reconfiguring the Application Database  I               To reconfigure the application database, proceed as follows 2               from the Configuration Options menu:  N               * Which configuration option to perform?                 [1] : 7  /               Select Option 7 and press Return.   L               * Do you want to ADD or DELETE an Application?         [ADD] :  F               Answer ADD to create the application entity on the localC               node, allocate resources for it, and open the service G               interface. Answer DELETE to delete the entity and reclaimSD               associated resources. Entering either ADD or DELETE inE               reply to this prompt displays the following prompt. The_;               NOTES application is used here as an example.   S               * What is the name of the Application?                        : NOTES/  A               When defining an application, you must identify the E               name of the object. DECnet object names are descriptive :               alphanumeric strings of up to 12 characters.  I                                    Modifying a Current Configuration 3-39            )         Modifying a Current Configuration 2         3.9 Reconfiguring the Application Database    ?               If you are deleting an application, the procedure1F               displays the following two prompts. If you are adding anD               application, the procedure skips the next two prompts.  L               * Are you sure you want to DELETE this application?      [NO]:  @               If you want to delete the application, answer YES.  L               * Do you want to generate NCL configuration scripts?   [YES] :  D               If you want to generate the NCL configuration scripts,               answer YES.e  F               If you are adding an application, the procedure displays#               the following prompt:   L               * What is the destination type for 'notes'?           [NAME] :  C               The destination type can be either NAME or NUMBER. To G               select NAME, press Return. To select NUMBER, enter NUMBERe               and press Return.r  F               If you select NAME, the procedure displays the following               prompt:i  K               * What is the destination name for 'notes'?                 :l  E               Your reply to this prompt can be either the application,I               name (for example, NOTES) or a destination object name (foreF               example, IAF:.SALES.BOSTON). The destination name is theI               DECdns full name of the node that provides the application.a  F               The application name can be from 1 to 16 characters. TheH               destination object name can be a maximum of 512 characters,               and is entered in this format:  9               NamespaceNickname:.DirectoryPath.NodeObjecto  G               If you enter NUMBER, the procedure displays the following                prompt:c  O               * What is the destination number for 'notes'?                : 33h  B               DECnet software uses object numbers as unique objectC               identifiers. Object numbers have a range of 1 to 255.eF               Generic objects such as MAIL and FAL have object numbersF               that are recognized throughout the network. User-definedH               images can have unique object numbers; numbers between 1284               and 255 are reserved for this purpose.  .         3-40 Modifying a Current Configuration y  e      I                                         Modifying a Current ConfigurationYI                                3.9 Reconfiguring the Application Database     G               For the NOTES application, enter 33 at this prompt. (This D               is the number that DIGITAL uses for this application.)  D               If you are adding a user-defined application, choose aF               number from 128 to 255. If you are adding an applicationD               defined by DIGITAL, select the appropriate number from               Table 3-3.  I               Table_3-3_Object_Type_Numbers______________________________t  I               Number____Mnemonic_Description_____________________________   -               0         Task     User program   9               1-16               Reserved for DIGITAL use   I               17        FAL      File access listener for remote file andt.                                  record access  F               18        HLD      Host loader for RSX-11S downline task1                                  loading requests   @               19        CML      CMIP Management Listener object  G               20                 RSTS/E media transfer program (NETCPY)   9               21-22              Reserved for DIGITAL use4  E               23        REMACP   Network terminal handler (host side)   I               24                 Network terminal handler (terminal side)   0               25        MIRROR   Loopback mirror  /               26        EVL      Event receiver   5               27        MAIL     OpenVMS Mail utilitye  9               28                 Reserved for DIGITAL uset  I               29        PHONE    OpenVMS Phone utility and RSX-11M/M-PLUSh.                                  Phone utility  9               30-41              Reserved for DIGITAL usei  9               42        CTERM    Network terminal handlers  9               43-62              Reserved for DIGITAL use   <               63        DTR      DECnet Test Receiver object  9               64-127             Reserved for DIGITAL usel  I               128-255____________Reserved_for_customer_use_______________i  L               * Do you want to specify another application address?    [NO]:  I                                    Modifying a Current Configuration 3-41  n  h      )         Modifying a Current Configuration 2         3.9 Reconfiguring the Application Database    H               If a node has more than one application address, enter YES4               and the previous prompts are repeated.  L               * What is the name of the Client for 'notes'?                :  H               Specify the name of the local user that you want activated@               upon receipt of the connect request containing the@               destination name matching one of the values in the+               destination names: attribute.   P               * What is the Image name for 'notes'? :Sys$system:notes$server.exe  C               Specify the file name of the program you want invokeddH               upon receipt of a Connect Request containing a destinationG               name matching one of the values in the destination names:                attribute.  L               * Incoming Alias for 'notes' enabled?                 [TRUE] :  H               Specify how the specified application responds to incomingE               connect requests directed to the alias node address. If I               you specify FALSE, the application does not accept incoming H               connect requests that have been directed to the alias node               address.  L               * Incoming Proxy for 'notes' enabled?                 [TRUE] :  F               Controls whether incoming proxy requests are honored. IfG               you specify FALSE, requests to invoke proxies on incominga#               requests are ignored.   L               * Outgoing Alias for 'notes' enabled?                 [TRUE] :  E               Specify whether a particular object uses the alias nodetI               identifier in its outgoing connect requests. If you specifymC               FALSE, the specified object cannot use the alias node 7               address in its outgoing connect requests.a  L               * Outgoing Proxy for 'notes' enabled?                 [TRUE] :  D               Specify the default action to execute when a user doesF               not explicitly specify whether to invoke a proxy. If you=               specify FALSE, there will be no default action.   L               * Require node synonym for 'notes' enabled?           [TRUE] :  .         3-42 Modifying a Current Configuration "  o      I                                         Modifying a Current Configuration.I                                3.9 Reconfiguring the Application DatabaseS    C               If you specify TRUE, then by default, the remote node E               name is passed to the application in synonym form. If awE               synonym is not available, the full name is used. If yousG               specify FALSE, the full name is passed to the applicationl               by default.   L               * What is the Incoming OSI TSEL for 'notes'?                 :  ?               Specify the transport service access point (TSAP) D               identifier for which the specified application accepts               connections.  F                 ________________________ Note ________________________  A                 This function is currently not implemented. Press 6                 Return to continue to the next prompt.  F                 ______________________________________________________  L               * What is the User Name for 'notes'?          [NOTES$SERVER] :  H               Enter the user name that you want to use when creating the>               account for the application you are configuring.  >               If you do not want to create an account for thatF               application, you can either enter NONE and press Return,6               or press the space bar and press Return.  F               If you decide to create an account for that application,1               the following two questions appear:t  L               * What UIC should 'notes' use?         [[200,200]] : [376,377]  I               Specify the UIC allocated upon creation of this applicationa               entity instance.  L               * Rights identifiers for 'NOTES$SERVER'?         :net$examine,1                net$declareobject,net$decnetaccess   C               Specify the rights identifiers (if any) needed by the G               application. If there are two or more rights identifiers, (               separate them with commas.  H               The procedure then creates the account for the applicationF               you want configured and displays the following messages:  \               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account NOTES$SERVERL               * Do you want to generate NCL configuration scripts?   [YES] :  I                                    Modifying a Current Configuration 3-43  l         )         Modifying a Current Configuration 2         3.9 Reconfiguring the Application Database    C               If you answer YES, the configuration program uses the I               information you entered to create an application NCL script-5               and displays the following information:e  X               %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts modified by               NET$CONFIGURE _               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completedt  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                 ______________________________________________________  I               The configuration program then returns to the Configuration D               Options menu. To implement the application NCL script,E               reboot the system or disable the entity and execute the                script.e  F               If you answer NO, the configuration procedure returns toF               the Configuration Options menu and does not generate NCL               scripts.  2         3.10 Reconfiguring the MOP Client Database  H               To reconfigure the MOP client database, proceed as follows2               from the Configuration Options menu:  N               * Which configuration option to perform?                 [1] : 8  /               Select Option 8 and press Return.   L               * Do you want to ADD or DELETE a MOP Client?           [ADD] :  C               Answer ADD to create an entity on the specified node,eH               allocate resources for it, and open the service interface.H               Answer DELETE to delete the entity from the specified node/               and reclaim associated resources..  M               * Name of the MOP Client?                              : SUPERXP  A               Specify the simple name of the client (for example,s               SUPERX).  .         3-44 Modifying a Current Configuration P  e      I                                         Modifying a Current ConfigurationoI                                3.10 Reconfiguring the MOP Client Databaseh    B               If you elect to delete the MOP client, the procedure,               displays the following prompt:  L               * Are you sure you want to DELETE this client?               :  <               If you want to delete this client, answer YES.  L               * Circuit for 'superx'?                                      :  E               Specify the name of the MOP circuit you want to use forr               this client.  L               * Physical addresses for 'superx'?                           :  D               Specify the set of LAN addresses for the client on the>               circuit specified by the CIRCUIT characteristic.  L               * Secondary Loader for 'superx'?                             :  H               Specify the files you want loaded when the client requestsG               a secondary loader during a downline load operation. FilerC               identifications are interpreted according to the filed)               system of the local system.   L               * Tertiary Loader for 'superx'?                              :  H               Specify the files you want loaded when the client requestsF               a tertiary loader during a downline load operation. FileC               identifications are interpreted according to the filea)               system of the local system.   L               * System Image for 'superx'?                                 :  H               Specify the files you want loaded when the client requestsC               a system image during a downline load operation. File C               identifications are interpreted according to the file )               system of the local system.i  L               * Diagnostic Image for 'superx'?                             :  H               Specify the files you want loaded when the client requestsG               a diagnostic image during a downline load operation. FilerC               identifications are interpreted according to the filei)               system of the local system.   L               * Management Image for 'superx'?                             :  I                                    Modifying a Current Configuration 3-45     M      )         Modifying a Current Configuration 2         3.10 Reconfiguring the MOP Client Database    H               Specify the files you want loaded when the client requestsG               a management image during a downline load operation. FileiC               identifications are interpreted according to the file )               system of the local system.   L               * Script File for 'superx'?                                  :  H               Specify the files you want loaded when the client requestsA               a CMIP initialization script during a downline loadrG               operation. File identifications are interpreted accordingn5               to the file system of the local system.a  L               * Dump File for 'superx'?                                    :  E               Specify the files to write to when the client is upline                dumped.   L               * Dump Address for 'superx'?                             [0] :  C               Specify the address of the files to write to when the &               client is upline dumped.  L               * Verification for 'superx'?            [%X0000000000000000] :  E               Specify the verification string you want sent in a booto.               message to the specified client.  L               * Phase IV Client Address (aa.nnn) for 'superx'?             :  E               Specify the Phase IV node address you want given to thetE               client system when it is loaded. This address is passediE               in a load characteristics message; whether it is neededa3               depends on the software being loaded.   L               * Phase IV Client Name for 'superx'?                      [] :  I               Specify the Phase IV node name you want given to the clienthE               system when it is loaded. This name is passed in a loadaF               characteristics message; whether it is needed depends on(               the software being loaded.  L               * Phase IV Host Address for 'superx'?                        :  F               Specify the Phase IV node address you want passed as theE               host node address when a client is loaded. This address H               is passed in a load characteristics message; whether it is:               needed depends on the software being loaded.  L               * Phase IV Host Name for 'superx'?                        [] :  .         3-46 Modifying a Current Configuration o  s      I                                         Modifying a Current ConfigurationwI                                3.10 Reconfiguring the MOP Client Databasei    H               Specify the Phase IV node name you want passed as the hostI               node name when a client is loaded. This name is passed in a H               load characteristics message; whether it is needed depends+               on the software being loaded.   L               * Do you want to generate NCL configuration scripts?   [YES] :  C               If you answer YES, the configuration program uses therC               information you have entered to create the MOP clientnG               NCL script. The configuration program then returns to theTI               Configuration Options menu. To implement the MOP client NCL I               script, reboot the system or disable the entity and execute                the script.   F               If you answer NO, the configuration procedure returns toF               the Configuration Options menu and does not generate NCL               scripts.  G         3.11 Reconfiguring Event, MOP Client, Application Entities, andE#              the Naming Search Pathe  H               You can use user-defined site-specific NCL scripts for theH               Event Dispatcher, MOP client, application, and search pathH               entities. (See Section 2.2.4 for further information about=               creating the site-specific search path script.)   H               The network startup procedure calls four site-specific NCLH               scripts (if they exist) when the network is started. TheseI               scripts must be in SYS$MANAGER. They are called immediately3I               after their DIGITAL-supplied counterparts are executed. The G               following table lists the scripts and their counterparts.   I               ___________________________________________________________ >               User-Defined                    DIGITAL-SuppliedI               Site-Specific_Script____________Script_____________________   C               NET$EVENT_LOCAL.NCL             NET$EVENT_STARTUP.NCLg  I               NET$APPLICATION_LOCAL.NCL       NET$APPLICATION_STARTUP.NCL   I               NET$MOP_CLIENT_LOCAL.NCL________NET$MOP_CLIENT_STARTUP.NCL_n  D               These scripts are user-defined and user-maintained andG               thus will not be overwritten or deleted by net$configure.tG               DIGITAL recommends that whenever possible, you place your F               site-specific changes in these user-defined NCL scripts.  I                                    Modifying a Current Configuration 3-47t a  o      )         Modifying a Current Configuration ^         3.11 Reconfiguring Event, MOP Client, Application Entities, and the Naming Search Path    F                 ________________________ Note ________________________  B                 If you invoke net$configure.com to edit a standardA                 NCL script (NET$entity_STARTUP.NCL), the standardsC                 NCL script is superseded and renamed to NET$entity_rD                 STARTUP.NCL-OLD (where entity is a particular entity                 name).  F                 ______________________________________________________  B               If you must make changes to the standard NCL scriptsF               and you want to retain your modifications after invokingH               net$configure, you can either manually edit the NCL scriptI               to replace the user modifications or rename the appropriatetC               NET$entity_STARTUP.NCL-OLD script back to NET$entity_LA               STARTUP.NCL. Be sure to incorporate any new changes B               as well. The net$configure.com procedure flags theseC               modifications the next time it checksums the scripts.9  ,         3.12 Reconfiguring the Cluster Alias  G               All or some nodes that are OpenVMS Cluster members can be I               represented in the network as a single node by establishingRE               an alias for the cluster. The alias allows users accessrH               to common resources on the OpenVMS Cluster without knowingI               which nodes are members of the cluster. It is not necessary F               for every member of the cluster to join the alias. ReferE               to the <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide for moresC               information about setting up a OpenVMS Cluster alias.C  C               To reconfigure the cluster alias, proceed as follows:t  N               * Which configuration option to perform?                 [1] : 9  /               Select Option 9 and press Return.S  L               * Do you want to ADD or DELETE an alias?               [ADD] :  I               Answer ADD to add the specified node to the cluster. AnswerfC               DELETE to remove the specified node from the cluster.p  L               * Full name of Cluster Alias                                 :  H               Specify the full name that uniquely identifies the cluster:               alias node (for example, IAF:.SALES.BOSTON).  .         3-48 Modifying a Current Configuration           I                                         Modifying a Current ConfigurationcI                                      3.12 Reconfiguring the Cluster Aliasv    H               If you are removing a node from the cluster, the procedure,               displays the following prompt:  L               * Are you sure you want to DELETE this alias?            [NO]:  H               If you answer YES to this prompt, the node is removed from               the cluster.  $         3.12.1 Specifying an Address  D               If you are adding a node to the cluster, the procedure,               displays the following prompt:  O               * Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) :   I               Specify either the DECnet Phase IV node address or Ethernet F               physical address of the alias. The Phase IV node addressB               has the format area-number.node-number (for example,G               63.171). The Ethernet physical address has the format AA- I               00-04-00-xx-xx, where xx-xx is calculated from the Phase IVgG               node address. To determine the Ethernet physical address,d!               proceed as follows:   A               1. Convert the Phase IV node address to its decimal '                  equivalent as follows:   H                  (area-number * 1024) + node-number = decimal equivalentA                  (For example, (63 * 1024) + 171 = 64683 decimal)t  D               2. Convert the decimal node address to its hexadecimalF                  equivalent and reverse the order of the bytes to form.                  the hexadecimal node address.  @                  (For example, 64683 decimal = FCAB hexadecimal,3                     reversed = ABFC hexnodeaddress)   @               3. Incorporate the hexadecimal node address in the"                  following format:  +                  AA-00-04-00-hexnodeaddress 1                  (For example, AA-00-04-00-AB-FC)m        I                                    Modifying a Current Configuration 3-49s           )         Modifying a Current Configuration ,         3.12 Reconfiguring the Cluster Alias    +         3.12.2 Determining Selection Weighto  F               The selection weight determines the number of sequentialC               incoming connects passed to this alias member node iniD               the round-robin sequence before proceeding to the nextE               member node in the sequence. A value of zero means this E               node is not eligible to receive incoming connections toeF               this alias address. Selection weight apportions incomingG               alias connections according to the capacity of each aliasr               member.   B               For example, nodes with greater capacity should haveF               larger values of selection weight, while OpenVMS ClusterG               satellites should generally have a value of zero. SpecifynB               a nonzero selection weight if this node is connectedE               locally to a dual-ported disk, or if it will be serving G               any multihost disks, such as RFxx or HSC-connected disks, C               to other cluster members. Values between 0 and 10 are                suggested.  L               * Selection weight for this cluster node [0 for satellites]  :  8               Enter a selection weight and press Return.  -         3.13 Replace MOP Client ConfigurationO  E               To replace a MOP Client Configuration, select Option 10d:               from the ADVANCED Configuration Option menu.  O               * Which configuration option to perform?                 [1] : 10s  -               The following question appears:c  L               * Load MOP on this system?                             [YES] :  E               By default, MOP is not started by NET$STARTUP. In order:D               to make this system service MOP requests, NET$STARTUP_?               MOP must be defined to signal NET$STARTUP to loadtB               the MOP software. This symbol is normally defined in+               SYS$STARTUP:NET$LOGICALS.COM.4  8               Answering YES to this question will modifyI               SYS$STARTUP:NET$LOGICALS.COM for you, to enable MOP serviceyG               on this system. Answering NO will remove the logical nametE               definition from SYS$STARTUP:NET$LOGICALS.COM. Note that H               this will have no effect if the NET$STARTUP_MOP is defined               elsewhere.  .         3-50 Modifying a Current Configuration G         I                                         Modifying a Current ConfigurationrI                                     3.13 Replace MOP Client Configuration_    8               If you answer YES, the following displays:  Q               %NET$CONFIGURE-I-MOPCLIENTFND, MOP client NCL script already existsr  P               * Replace MOP Client script file?                       [NO] : yes  D               Answer YES to create a new MOP Client NCL script file,%               otherwise press Return.   E               The procedure displays the Summary of Configuration and !               asks the following:p  L               * Do you want to generate NCL configuration scripts?   [YES] :  C               If you answer YES, the configuration program uses the F               information you entered to generate modified NCL scriptsC               and, in some cases, automatically modify the system's F               configuration. The configuration program then returns to-               the Configuration Options menu.o  F               If you answer NO, the configuration procedure returns toF               the Configuration Options menu and does not generate any#               modified NCL scripts.u  (         3.14 Configuring Satellite Nodes  F                 ________________________ Note ________________________  B                 CAUTION: If your cluster is running mixed versionsD                 of DECnet, you cannot use this feature. Instead, youA                 must configure the nodes independently by runninge-                 net$configure on each system.   F                 ______________________________________________________  E               To select this option, you must have already configured E               the system using the ADVANCED configuration option, and =               net$configure is executing on a cluster system.o  H               From the ADVANCED Configuration Option menu, select Option               11.   O               * Which configuration option to perform?                 [1] : 11p    I                                    Modifying a Current Configuration 3-51h c  n      )         Modifying a Current Configurationo(         3.14 Configuring Satellite Nodes                    A submenu appears:  ,                       Configuration Options:  1                       [0]     Return to main menu   B                       [1]     Autoconfigure Phase IV cluster nodes@                       [2]     Full configuration of cluster node2                       [3]     Configure local node  L               * Which configuration option to perform?                 [1] :  E               Autoconfigure Phase IV Cluster Nodes (Submenu Option 1)   B               If you select Option 1, it scans the system disk for@               evidence of satellite nodes that have not yet beenH               configured to run DECnet-Plus. If it finds one, it createsF               sys$specific:[sys$startup]net$autoconfigure.com, causingG               the cluster member to automatically configure DECnet-Plus D               the next time it reboots. The procedure prompts you to5               enter the full name of a cluster alias.   L               * Fullname of cluster alias:                                 :  H               Supply the full node name of the cluster alias. If none isF               supplied, no cluster alias is configured for the systems               being upgraded.e  L               * Device containing system roots            [SYS$SYSDEVICE:] :  H               Configuring cluster satellites involves finding the systemD               root from which the satellite boots. Normally, this isG               SYS$SYSDEVICE:, although it is possible to install system *               roots to a different volume.  G               The device given in response to this question is searchedrC               for all system roots. Those found that do not containiC               a checksum database are assumed to be Phase IV nodes,eB               and are candidates for being flagged for DECnet-Plus                autoconfiguration.  L               * Upgrade Phase IV cluster member FIGS?                [Yes] :  E               A system root was found that does not contain a DECnet- F               Plus checksum database, and is therefore assumed to be aD               Phase IV system. Answering YES to this question causesB               that cluster node to be flagged to run a DECnet-Plus3               autoconfiguration on its next reboot.   L               * What is the synonym name for this system?           [FIGS] :  .         3-52 Modifying a Current Configuration n  e      I                                         Modifying a Current Configuration I                                          3.14 Configuring Satellite Nodes     C               Full Configuration of Cluster Node (Submenu Option 2)l  N               * Which configuration option to perform?                 [1] : 2  E               If you select Option 2, it prompts for a cluster member A               name (and system root location). Once supplied, all @               net$configure modifications are made to the DECnetH               configuration for that cluster member. Note that this only7               allows a subset of configuration options.:  S               * Cluster node name to be configured:                        : TPZERO   C               This is simply the node name of the cluster member todE               configure. The net$configure procedure attempts to find B               the system root for that cluster member (by scanningD               NET$MOP_CLIENT_STARTUP.NCL) to supply defaults for the(               two questions that follow.  L               * Device for TPZERO root:                    [SYS$SYSDEVICE] :  F               In configuring a cluster member other than the system onI               which net$configure executes, you must specify the location C               of the member's system root. The location is the disk G               device on which the cluster member's system root resides.   C               The default answer to this is either SYS$SYSDEVICE orsF               the root device found for that system in NET$MOP_CLIENT_               STARTUP.NCLt  Q               * Directory for TPZERO root:                                 : SYS2   F               In configuring a cluster member other than the system onE               which net$configure executes, you must also specify the H               system root directory. The system root directory is of theI               form "SYSxxxx," where "xxxx" is the hexadecimal root number +               from which that member loads.o  F               Note that before net$configure returns to the main menu,E               it warns that all subsequent options will be applied tonH               the cluster node just specified. Notice also that Option 5I               (Configure Timezones) is not present when configuring other                cluster members.  ?               %NET$CONFIGURE-I-VERCHECKSUM, verifying checksumso  N               All configuration options will be applied to cluster node TPZERO  I                                    Modifying a Current Configuration 3-53r t  r      )         Modifying a Current Configurationh(         3.14 Configuring Satellite Nodes    5               Configure Local Node (Submenu Option 3)t  G               If you select Option 3, it clears the action of Option 2;eH               all subsequent net$configure modifications are made to the?               local system (as when net$configure was started).   N               * Which configuration option to perform?                 [1] : 3  1         3.15 Configuring Cluster Script Locationso  G               This option allows the system manager to make the network C               startup scripts for NET$APPLICATION_STARTUP, NET$MOP_ D               CLIENT_STARTUP, and NET$EVENT_STARTUP to be common forE               all cluster nodes. That is, a single copy of the script B               is shared by all systems in the cluster. This allowsC               a single configuration for those scripts to be common E               to all systems, ensuring that all systems have the same G               application, MOP client, and event logging configuration.   F               It does this by copying the script from the SYS$SPECIFICC               directory to the SYS$COMMON directory. Note that whens@               it does so, it does not delete the script from theE               SYS$SPECIFIC directories for the other cluster systems.uF               You must do this by rerunning the dialog for all cluster               members.  E               To select this option, you must have already configured E               the system using the ADVANCED configuration option, and =               net$configure is executing on a cluster system.N  H               From the ADVANCED Configuration Option menu, select Option               12.s  O               * Which configuration option to perform?                 [1] : 12m  G               For this example, the system manager selects Option 12 tohF               create cluster common scripts for APPLICATION, EVENT andG               MOP_CLIENT. These cluster common scripts are created fromiI               the latest configuration on the currently executing system.t            .         3-54 Modifying a Current Configuration           I                                         Modifying a Current ConfigurationyI                                 3.15 Configuring Cluster Script Locations(    W               * Move the APPLICATION startup script to the cluster common area? [YES] :t\               %NET$CONFIGURE-I-MOVESCRIPT, created cluster common APPLICATION startup scriptD               from SYS$SPECIFIC:[SYSMGR]NET$APPLICATION_STARTUP.NCL;Q               * Move the EVENT startup script to the cluster common area? [YES] :r[               %NET$CONFIGURE-I-MOVESCRIPT, created cluster common EVENT startup script frome9               SYS$SPECIFIC:[SYSMGR]NET$EVENT_STARTUP.NCL; V               * Move the MOP_CLIENT startup script to the cluster common area? [YES] :[               %NET$CONFIGURE-I-MOVESCRIPT, created cluster common MOP_CLIENT startup script C               from SYS$SPECIFIC:[SYSMGR]NET$MOP_CLIENT_STARTUP.NCL;e[               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified bys               NET$CONFIGUREi_               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed Q               %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION script K               %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT script P               %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT script  G               However, these cluster common scripts will not be used byrE               the system "TPZERO," because it still has local copies.<H               So, the system manager selects Option 10 to manage clusterI               nodes, and then suboption 2 to manage the configuration fore               node TPZERO.  +                      Configuration Options:t  1                       [0]     Exit this procedure   =                       [1]     Perform an entire configurationo7                       [2]     Change naming information:?                       [3]     Configure Devices on this machines2                       [4]     Configure TransportsD                       [5]     Configure Timezone Differential Factor8                       [6]     Configure Event Dispatcher<                       [7]     Configure Application database;                       [8]     Configure MOP Client database 5                       [9]     Configure Cluster Alias >                       [10]    Replace MOP Client configuration7                       [11]    Configure satellite nodes @                       [12]    Configure cluster script locations  O               * Which configuration option to perform?                 [0] : 11p  ,                       Configuration Options:  1                       [0]     Return to main menu   I                                    Modifying a Current Configuration 3-55h l  e      )         Modifying a Current Configuration 1         3.15 Configuring Cluster Script Locationst    B                       [1]     Autoconfigure Phase IV cluster nodes@                       [2]     Full configuration of cluster node2                       [3]     Configure local node  N               * Which configuration option to perform?                 [0] : 2S               * Cluster node name to be configured:                        : TPZEROlL               * Device for TPZERO root:                    [SYS$SYSDEVICE] :Q               * Directory for TPZERO root:                                 : SYS2 Y               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific APPLICATION script overridesf)               the cluster common settingsaW               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific EVENT script overrides the %               cluster common settingseX               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific MOP_CLIENT script overrides)               the cluster common settingsd  N               All configuration options will be applied to cluster node TPZERO  B               Upon doing so, we are informed that TPZERO has localH               versions of these scripts that override the cluster commonH               defaults. Selecting Option 11 allows the manager to deleteG               these local overrides so that TPZERO will use the cluster:               common versions.  ,                       Configuration Options:  1                       [0]     Exit this procedure   =                       [1]     Perform an entire configuration 7                       [2]     Change naming informationR?                       [3]     Configure Devices on this machinel2                       [4]     Configure Transports8                       [6]     Configure Event Dispatcher<                       [7]     Configure Application database;                       [8]     Configure MOP Client database 5                       [9]     Configure Cluster Aliasm>                       [10]    Replace MOP Client configuration7                       [11]    Configure satellite nodese@                       [12]    Configure cluster script locations              .         3-56 Modifying a Current Configuration           I                                         Modifying a Current ConfigurationaI                                 3.15 Configuring Cluster Script Locationsl    O               * Which configuration option to perform?                 [0] : 12oP               * Delete the local APPLICATION startup script?          [No] : yesS               %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of thee(               APPLICATION startup scriptP               * Delete the local EVENT startup script?                [No] : yesY               %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of the EVENTe               startup scriptP               * Delete the local MOP_CLIENT startup script?           [No] : yesS               %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of ther'               MOP_CLIENT startup scriptc[               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified byu               NET$CONFIGURE _               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completedOQ               %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION scriptcK               %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT script$P               %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT script  N               All configuration options will be applied to cluster node TPZERO  -         3.16 Completing Configuration ChangesR  D               After you have made all your selections, the procedure1               displays a summary of your changes:m  /                        Summary of ConfigurationO                   Node Information:I                       Directory Services Chosen:      DECDNS,LOCAL,DOMAIN <                       Primary directory service:      DECDNSH                       DECdns full name:       PHASEV:.ENG.SSG.TEST.ELMER:                       Local Full name:        LOCAL:.ELMER%                       Fully Qualified C                       Host name:              ELMER.WABBIT.ACME.EDU 3                       Node Synonym:           ELMERa3                       Phase IV Address:       15.27s2                       Phase IV Prefix:        49::C                       Autoconfiguration of Network Address: Enabled F                       Session Control Address Update Interval:      101                       Routing ESHello Timer:  600   7                       Alias Name:     ACME:.WABBIT.HELPr  "                Device Information:  +                       Device: XQA0 (DELQA):i  I                                    Modifying a Current Configuration 3-57  i  d      )         Modifying a Current Configurationu-         3.16 Completing Configuration Changes     '                Data Link name: CSMACD-0 >                               Routing Circuit Name:   CSMACD-0+                               .           .o+                               .           .f+                               .           .a  G               At the end of the summary, the procedure asks if you wantiF               to generate NCL configuration scripts (which now contain(               your updated information):  L               * Do you want to generate NCL configuration scripts?   [YES] :  C               If you answer YES, the configuration program uses theiE               information you entered to create the alias NCL script. I               The configuration program then returns to the Configuration I               Options menu. To implement the alias NCL script, reboot the B               system or disable the entity and execute the script.  F               If you answer NO, the configuration procedure returns toF               the Configuration Options menu and does not generate any               NCL scripts.                                                .         3-58 Modifying a Current Configuration                         I                                                                   Part IIgI         _________________________________________________________________m  I              Configuring VAX P.S.I. and VAX P.S.I. Access for OpenVMS VAX I                                                                   Systemso            D               Part II describes the steps necessary to configure VAXF               P.S.I. and VAX P.S.I Access on a DECnet-Plus for OpenVMS               VAX system.r o  p                    I                                                                         4uI         _________________________________________________________________e  I                              Configuring VAX P.S.I. and VAX P.S.I. Access     H               This chapter describes how to configure the VAX P.S.I. and)               VAX P.S.I. Access software.o  +         4.1 Steps in Configuring VAX P.S.I.e  F               See Figure 4-1 and take the following steps to configure%               your VAX P.S.I. system:o  E               1. Plan your configuration (see the <REFERENCE>(DNPLUS_ ,                  PLANNING) and Section 4.2).  C               2. Make a note of the information you need during thec:                  configuration program, using Section 4.3.  A               3. Run the configuration program (see Section 4.4).   D               4. Run the net$configure procedure (in either BASIC or:                  ADVANCED mode) to configure your network.  D               5. Carry out the postconfiguration tasks: starting VAXI                  P.S.I. and testing your configuration (see Section 4.5).   2         4.2 Planning Your VAX P.S.I. Configuration  B               This section introduces the aspects of your proposedD               configuration that you need to consider before you run(               the configuration program.  ?         4.2.1 Configuring Access, Native, and Multihost Systemsa  :               There are three types of VAX P.S.I. systems:                 o  Access                  o  Nativet                 o  Multihost  >               Refer to the <REFERENCE>(DNPLUS_PLANNING) for an0               explanation of VAX P.S.I. systems.  I                          Configuring VAX P.S.I. and VAX P.S.I. Access 4-1i Y  t      4         Configuring VAX P.S.I. and VAX P.S.I. Access2         4.2 Planning Your VAX P.S.I. Configuration    E               The type(s) you can configure depends on the license(s)eG               that you have installed. Table 4-1 summarizes the variousC&               possible configurations.                                                                                    8         4-2 Configuring VAX P.S.I. and VAX P.S.I. Access           I                              Configuring VAX P.S.I. and VAX P.S.I. Access I                                4.2 Planning Your VAX P.S.I. Configuration     A               Figure 4-1 Installation and Configuration Flowchart                                                                                         I                          Configuring VAX P.S.I. and VAX P.S.I. Access 4-3u r  m      4         Configuring VAX P.S.I. and VAX P.S.I. Access2         4.2 Planning Your VAX P.S.I. Configuration    =               Table 4-1 VAX P.S.I. Configurations and License I               __________Requirements_____________________________________   I               License(s)______Possible_VAX_P.S.I._Configurations_________   /               DECnet-VAX      VAX P.S.I. Access                only  /               Native only     VAX P.S.I. Native   /               DECnet-VAX and  VAX P.S.I. Access /               Native          VAX P.S.I. NativeY2                               VAX P.S.I. Multihost8                               VAX P.S.I. Access + NativeI               ________________VAX_P.S.I._Access_+_Multihost______________e  2         4.2.2 The VAX P.S.I. Configuration Program  E               The VAX P.S.I. configuration program has many sections, H               but not all sections are relevant to all types of systems.E               Table 4-2 shows the sections that apply to each type of                system.                                               8         4-4 Configuring VAX P.S.I. and VAX P.S.I. Access i  i      I                              Configuring VAX P.S.I. and VAX P.S.I. AccessxI                                4.2 Planning Your VAX P.S.I. Configuratione    F               Table 4-2 VAX P.S.I. Configuration Sections Required forI               __________Access,_Native_and_Multihost_Systems_____________s  9                                 Applies  Applies  Applies F                                 to       to       to       Required orI               Section___________Access?__Native?__MultihostOptional______t  ?               Set Up Lines and  No       Yes      Yes      O[1]e               DTEs  <               Set Up PVCs       No       Yes      Yes      O  <               Set Up Groups     No       Yes      Yes      O  ?               Set Up LLC2       Yes      Yes      Yes      O[1]   <               Set Up Remote     Yes      No       No       R               DTE Classesi  <               Choose X.29       Yes      Yes      Yes      O               and P.S.I. Mailf               Supportn  <               Set Up Gateway    No       No       Yes      R               Clientse  <               Set Up            Yes      Yes      Yes      O               Applications  <               Declaring a       Yes      Yes      Yes      O               Network Processt  <               Set Up Templates  Yes      Yes      Yes      O  <               Select X.25       Yes      Yes      Yes      O               Security Optionw  <               Set Up Incoming   Yes      Yes      Yes      O               Security for               Applications  <               Set Up Outgoing   Yes      Yes      Yes      O               Security for               Local Processesy  <               Set Up Incoming   Yes      Yes      Yes      O               Security               for Network                Processes   <               Set Up Incoming   No       No       Yes      O               Security for               Gateway Clients   <               Set Up Outgoing   No       No       Yes      O               Security for               Accessing.I               Systems    Configuring VAX P.S.I. and VAX P.S.I. Access 4-5r  <               Create the NCL    Yes      Yes      Yes      O               ScriptI               [1]You_must_set_up_at_least_one_synchronous_line_and_______   6               associated DTE or at least one LLC2 DTE.    e      4         Configuring VAX P.S.I. and VAX P.S.I. Access2         4.2 Planning Your VAX P.S.I. Configuration    I               ___________________________________________________________   F               The VAX P.S.I. configuration program automatically skips@               sections that do not apply to your type of system.  >         4.2.3 Sections in the VAX P.S.I. Configuration Program  F               This section explains the purpose of each section in the+               P.S.I. configuration program.                  Lines and DTEs  @               Choose a line on your system to configure for X.25I               communications. You must configure at least one synchronousn=               line unless you intend to use LLC2 exclusively.n                 PVCs  H               Your DTE can communicate with a remote DTE using either anH               SVC (switched virtual circuit) or a PVC (permanent virtualD               circuit). A PVC is a permanent association between two               specific DTEs.  E               Two DTEs connected by a PVC can communicate without theO3               need for call clearing or call setup.p  G               Complete this section if you have requested this facilityI               from your PSDN.m                 Groups  F               If your DTE belongs to a closed user group (CUG), it canG               communicate freely with remote DTEs that are also members[D               of that CUG. Its communications with other DTEs may beF               restricted, depending on your PSDN subscription options.  G               You must complete this section if you have requested thish&               facility from your PSDN.                 LLC2  G               LLC2 is a data link protocol used on LANs, over which the 6               X.25 Packet-Level Protocol (PLP) is run.  I               You must set up an LLC2 DTE for each remote system to which H               you want to connect on the LAN. You can set up one or more+               LLC2 DTEs per LAN connection.e                  Remote DTE Classes  F               Use this section to specify the connector system(s) that&               your Access system uses.  8         4-6 Configuring VAX P.S.I. and VAX P.S.I. Access s  c      I                              Configuring VAX P.S.I. and VAX P.S.I. AccessgI                                4.2 Planning Your VAX P.S.I. Configuration     "               X.29 and P.S.I. Mail  =               This section allows you to add support for X.2911               communications and for P.S.I. Mail.   C               You need X.29 support if your VAX P.S.I. system is to 8               communicate with character-mode terminals.  C               P.S.I. Mail is an extension of OpenVMS Mail that letsrG               you send mail messages to and receive them from other VAXv+               P.S.I. systems across a PSDN.                  Gateway Clients   E               You must create gateway clients to allow your multihost I               system to pass incoming calls to the correct client system.lE               A gateway client identifies a client system or group ofaF               client systems that use this multihost system to receive               incoming calls.c  D               In this section, you also set up filter(s) for gatewayC               clients. You must set up at least one filter for each A               gateway client. See filters for more about filters.g                 Filters3  E               Filters are sets of characteristics that can be matched.>               to fields in an incoming call request packet. If?               the characteristics in an incoming call match the C               characteristics you set in a filter, then the call is H               passed to the gateway client or the application associated               with that filter.]  C               You must supply a filter name and a priority for each I               filter. You may leave all the other parameters unspecified.   C               The more parameters you specify in a filter, the more F               specific is that filter. For example, you could create aG               filter with most of its parameters unspecified and with alG               low priority to act as a "catchall" for unexpected calls.d                 Applications  D               You must specify any X.25 or X.29 applications on yourF               system to allow incoming calls for those applications to               succeed.  F               You must supply the name of the command file that startsF               the application. You may also supply a user name for the               application.  H               Do not specify any applications that do not receive calls.  I                          Configuring VAX P.S.I. and VAX P.S.I. Access 4-7  h         4         Configuring VAX P.S.I. and VAX P.S.I. Access2         4.2 Planning Your VAX P.S.I. Configuration    <               In this section, you also set up filter(s) forH               applications. You must set up at least one filter for each>               application. See filters for more about filters.  )               Declaring a Network Processn  G               X.25 and X.29 programs on your system can issue $QIO(IO$_ @               ACPCONTROL) calls to declare themselves as network               processes. EachtG               $QIO(IO$_ACPCONTROL) specifies a filter used to determine 9               which calls are able to access the program.   H               The filter specified by $QIO(IO$_ACPCONTROL) can be one of               two types:                 o  Static   G                  In this case, $QIO(IO$_ACPCONTROL) names a filter that H                  already exists on your system. Complete this section ifG                  you want to create static filters for use by $QIO(IO$_                   ACPCONTROL).g                 o  Dynamic  G                  In this case, the filter characteristics are specified[E                  in the $QIO(IO$_ACPCONTROL) call. The filter created G                  in this way by the $QIO(IO$_ACPCONTROL) call ceases toeD                  exist when the program exits. Complete this sectionC                  if you want to name the dynamic filters created by &                  $QIO(IO$_ACPCONTROL).  I               If your programs issue only $QIO(IO$_ACPCONTROL) calls that F               use unnamed dynamic filters, you do not need to complete               this section.                  TemplatesE  C               Your system uses a template to make outgoing calls. A G               template sets various parameters for each call made usingh               that template.  E               A template called "default" is created automatically onU               your system.    8         4-8 Configuring VAX P.S.I. and VAX P.S.I. Access N  U      I                              Configuring VAX P.S.I. and VAX P.S.I. AccessII                                4.2 Planning Your VAX P.S.I. ConfigurationN                   Security  E               Set up security to prevent unauthorized use of your VAX =               P.S.I. system. There are six security sections:n                 o  X.25 Security  A                  This allows you to choose whether to set up X.25 I                  security. If you do not set up X.25 security, any remoteaH                  DTE can make a call to your system (provided it matchesF                  one of your filters), and any user on your system canI                  make outgoing calls to any remote DTE. If you choose notdF                  to set up X.25 security, you do not see the following(                  five security sections.  3               o  Incoming Security for Applications   A                  You see this section only if you have an Access, E                  Native, or Multihost system on which you have set up                   applications.  G                  Complete this section if you want your applications tof>                  be able to receive calls from remote systems.  6               o  Outgoing Security for Local Processes  G                  Complete this section if you want users on your system.<                  to be able to make calls to remote systems.  8               o  Incoming Security for Network Processes  H                  Complete this section if you have X.25 or X.29 programsA                  that issue $QIO(IO$_ACPCONTROL) calls to declareg1                  themselves as network processes.:  6               o  Incoming Security for Gateway Clients  I                  You see this section only if you have a Multihost system :                  on which you have set up gateway clients.  I                  Complete this section if you want your system to be ablek:                  to pass incoming calls to client systems.  8               o  Outgoing Security for Accessing Systems  B                  You see this section only if you have a Multihost                  system.  I                  Complete this section if you want your system to be able D                  to make outgoing calls on behalf of client systems.  I                          Configuring VAX P.S.I. and VAX P.S.I. Access 4-9  p  n      4         Configuring VAX P.S.I. and VAX P.S.I. Access2         4.2 Planning Your VAX P.S.I. Configuration                   NCL Script  I               When you are satisfied that all the information you enteredfH               is complete and correct, the configuration program createsA               two NCL scripts using the information you provided.d  C               When the NCL scripts have been created, you are asked D               if you want to run a command file called psi$security_               identifiers.com.  F               This file is created by the configuration program to addI               certain rights identifiers to the system rights database on H               your system. The rights to be added depend on the security,               information you have supplied.  H               You can run the command file from within the configurationG               procedure, or you can exit from the configuration program H               and run the command file later. Note that you cannot startF               VAX P.S.I. until you have run this command file. This isH               true even if you have selected not to set up X.25 security               for your system.  F               If you edit the command procedure before running it, youG               must make corresponding changes to the NCL scripts beforee,               attempting to start VAX P.S.I.  =         4.3 Recording the Information You Need for VAX P.S.I.              Configuration(  F               This section details the information you need to provide/               during the configuration program.o  I               Tables 4-3 to 4-18 list all the information required during                 the configuration.  F               Table 4-3 lists the information you need to complete theB               lines and DTEs section of the configuration program.                9         4-10 Configuring VAX P.S.I. and VAX P.S.I. Accessu i  t      I                              Configuring VAX P.S.I. and VAX P.S.I. AccesseI       4.3 Recording the Information You Need for VAX P.S.I. Configuration     G               Table 4-3 VAX P.S.I. Configuration Information: Lines andoI               __________DTEs_(Native_and_Multihost_Systems_Only)_________f  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________s  ;               Select device    -              You select  -   E               Select line      -              Supplier    4.8 Kbits/s 5               speed                           of line   ?               DTE name         Max. 32        You supply  DTE-nt)                                charactersV  ;               DTE address      Max. 15        PSDN sub-   -a7                                digits         scriptione6                                               informa-2                                               tion  ;               Logical channel  Number(s) or   PSDN sub-   - 7               range(s)         range(s) of    scription 6                                numbers        informa-2                                               tion  ;               Profile name     As supplied    PSDN/DIGITAL-4)                                by DIGITAL   <               Flow control     Yes or No      You select  No               negotiation[1]  <               Extended         Yes or No      You select  No               packet sequencei               numbering[1]  A               Minimum packet   Decimal        You supply  ProfileXC               size[2]          number         (subject    dependent 5                                               to PSDN 6                                               restric-4                                               tions)  I               [1]You_need_to_make_this_choice_only_if_the_profile_you____V  ,               entered supports the facility.G               [2]You need to enter values here only if you chose to uset'               packet-level negotiation.   I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-11. l  o      4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configuration     E               Table 4-3 (Cont.) VAX P.S.I. Configuration Information:AD                                 Lines and DTEs (Native and MultihostI               __________________Systems_Only)____________________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________c  A               Maximum packet   Decimal        You supply  ProfileIC               size[2]          number         (subject    dependent 5                                               to PSDN 6                                               restric-4                                               tions)  A               Default packet   Decimal        You supply  Profile C               size             number         (subject    dependentR5                                               to PSDNt6                                               restric-4                                               tions)  A               Minimum window   Decimal        You supply  Profile C               size (packet     number         (subject    dependent 5               level)[2]                       to PSDN 6                                               restric-4                                               tions)  A               Maximum window   Decimal        You supply  Profile C               size (packet     number         (subject    dependentw5               level)[2]                       to PSDNt6                                               restric-4                                               tions)  A               Default window   Decimal        You supply  ProfilerC               size (packet     number         (subject    dependent 5               level)                          to PSDN 6                                               restric-4                                               tions)  =               Interface        DTE or DCE     You select  DTE                mode[3]   I               [2]You_need_to_enter_values_here_only_if_you_chose_to_use__   '               packet-level negotiation. E               [3]You need to make this choice only if the profile youo*               entered is ISO 8208 or NPSI.  9         4-12 Configuring VAX P.S.I. and VAX P.S.I. Access            I                              Configuring VAX P.S.I. and VAX P.S.I. Access I       4.3 Recording the Information You Need for VAX P.S.I. Configuratione    E               Table 4-3 (Cont.) VAX P.S.I. Configuration Information:sD                                 Lines and DTEs (Native and MultihostI               __________________Systems_Only)____________________________r  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________u  <               Extended         Yes or No      You select  No               frame sequence               numbering[1]  A               Window size      Decimal        You supply  Profile C               (frame level)    number         (subject    dependent.5                                               to PSDN 6                                               restric-4                                               tions)  F               DTE Class        Max. 32        You supply  Profile name)                                characters I               [1]You_need_to_make_this_choice_only_if_the_profile_you____   ,               entered supports the facility.I               ___________________________________________________________e  F               Table 4-4 lists the information you need to complete the8               PVCs section of the configuration program.  B               Table 4-4 VAX P.S.I. Configuration Information: PVCsI               __________(Native_and_Multihost_Systems_Only)______________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   ;               Select a DTE     -              You select  -o  ?               PVC name         Max. 32        You supply  PVC-n )                                charactersa  ;               Channel number   Decimal        PSDN sub-   - 7                                number         scription 6                                               informa-2                                               tion  I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-13e n  N      4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configurationy    E               Table 4-4 (Cont.) VAX P.S.I. Configuration Information:pI               __________________PVCs_(Native_and_Multihost_Systems_Only)_   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________d  E               PVC packet size  Decimal        PSDN sub-   Default DTEgE                                number         scription   packet sizeP6                                               informa-2                                               tion  E               PVC window size  Decimal        PSDN sub-   Default DTErE                                number         scription   window size.6                                               informa-I               ________________________________tion_______________________i                                                          9         4-14 Configuring VAX P.S.I. and VAX P.S.I. Accessa s         I                              Configuring VAX P.S.I. and VAX P.S.I. Access I       4.3 Recording the Information You Need for VAX P.S.I. Configurationl    F               Table 4-5 lists the information you need to complete the:               Groups section of the configuration program.  D               Table 4-5 VAX P.S.I. Configuration Information: GroupsI               __________(Native_and_Multihost_Systems_Only)______________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   A               Group name       Max. 32        You supply  GROUP-n )                                characters   >               Group type       BCUG or CUG    PSDN sub-   BCUG7                                               scriptionl6                                               informa-2                                               tion  ;               DTE name[1]      -              You select  -r  ;               CUG number[1]    Decimal        PSDN sub-   -e7                                number         scription 6                                               informa-2                                               tion  ;               Remote DTE       Max. 15        PSDN sub-   -a7               address[2]       digits         scriptiony6                                               informa-2                                               tionI               [1]You_may_specify_more_than_one_DTE/CUG_number_pair_for___o  !               groups of type CUG. F               [2]You need to supply this information only if the Group               type is BCUG. I               ___________________________________________________________   F               Table 4-6 lists the information you need to complete the8               LLC2 section of the configuration program.              I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-15d X  S      4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configuration     B               Table 4-6 VAX P.S.I. Configuration Information: LLC2I               __________(Native_and_Multihost_Systems_Only)______________e  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   ;               Choose LAN       -              You select  -s               device  ?               DTE name         Max. 32        You supply  DTE-no)                                charactersd  ;               DTE address      Max. 15        You supply  -:%                                digits   ;               Logical channel  Number(s) or   PSDN sub-   - 7               range(s)         range(s) of    scriptione6                                numbers        informa-2                                               tion  <               Local LSAP       2 hexadecimal  You supply  7E%                                digits   ;               Remote MAC       LAN hardware   Remote      -l4               address          address        system  <               Remote LSAP      2 hexadecimal  Remote      7E4                                digits         system  <               Flow control     Yes or No      You select  No               negotiation_  <               Extended         Yes or No      You select  No               packet sequence                numberinga  <               Minimum packet   Decimal        You supply  16%               size[1]          number   >               Maximum packet   Decimal        You supply  1024%               size[1]          numbera  =               Default packet   Decimal        You supply  128 %               size             numberu  ;               Minimum window   Decimal        You supply  1 %               size (packet     numberd               level)[1]U  I               [1]You_need_to_supply_these_values_only_if_you_chose_to_usec  '               packet-level negotiation.a  9         4-16 Configuring VAX P.S.I. and VAX P.S.I. Accessi           I                              Configuring VAX P.S.I. and VAX P.S.I. Access I       4.3 Recording the Information You Need for VAX P.S.I. Configuration     E               Table 4-6 (Cont.) VAX P.S.I. Configuration Information:2I               __________________LLC2_(Native_and_Multihost_Systems_Only)_t  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________u  ;               Maximum window   Decimal        You supply  7 %               size (packet     numbert               level)[1]   ;               Default window   Decimal        You supply  2 %               size (packet     number                level)  F               DTE class        Max. 32        You supply  LLC2-CLASS-n)                                characters I               [1]You_need_to_supply_these_values_only_if_you_chose_to_usey  '               packet-level negotiation.bI               ___________________________________________________________i  F               Table 4-7 lists the information you need to complete theF               Remote DTE Classes section of the configuration program.  H               Table 4-7 VAX P.S.I. Configuration Information: Remote DTEI               __________Classes_(Access_Systems_Only)____________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________n  A               Name             Max. 32        You supply  REMOTE-oA                                characters                 CLASS-nt  ;               Gateway node     Max. 6         You supply  -yI               name(s)__________characters________________________________.  F               Table 4-8 lists the information you need to complete theG               X.29 and P.S.I. Mail Support section of the configuration                program.        I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-17  e  t      4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configuration     F               Table 4-8 VAX P.S.I. Configuration Information: X.29 andI               __________P.S.I._Mail_Support_(All_Systems)________________n  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________n  =               X.29 support     Yes or No      You select  Yesv  =               P.S.I. Mail      Yes or No      You select  Yesa               supporti  <               P.S.I. Mail      Max. 31        You supply  No)               account user     charactersa               name[1] I               [1]_You_are_asked_for_this_information_only_if_you_request_   "               P.S.I. Mail support.I               ___________________________________________________________                                                     9         4-18 Configuring VAX P.S.I. and VAX P.S.I. Accesso h  o      I                              Configuring VAX P.S.I. and VAX P.S.I. Access I       4.3 Recording the Information You Need for VAX P.S.I. Configuration.    F               Table 4-9 lists the information you need to complete theC               gateway clients section of the configuration program.h  E               Table 4-9 VAX P.S.I. Configuration Information: GatewaysI               __________Client_Nodes_(Multihost_Systems_Only)____________r  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________p  B               Name             Max. 32        You supply  CLIENT-n)                                characterst  ;               Node name        Max. 32        You supply  - )                                characters   ;               Filter name(s)   Max. 32        You supply  -hI               _________________characters________________________________I  G               Table 4-10 lists the information you need to complete theu@               Applications section of the configuration program.  >               Table 4-10 VAX P.S.I. Configuration Information:I               ___________Applications_(All_Systems)______________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   G               Name             Max. 32        You supply  APPLICATION-n )                                characterst  >               Type             X.25, X.29,    You select  X.25,                                or X.29 Login  ;               Command file     OpenVMS file   You supply  -2#               to start         name                application[1]  ;               User name for                   You supply  -                application[1]  ;               Filter name(s)   Max. 32        You supply  - )                                characters I               [1]You_are_not_asked_for_this_information_if_the___________o  ,               application type is X.29 loginI               ___________________________________________________________   I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-19  f         4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configuratione    G               Table 4-11 lists the information you need to complete theoF               Declaring a Network Process section of the configuration               program.  H               Table 4-11 VAX P.S.I. Configuration Information: DeclaringI               ___________a_Network_Process_(All_Systems)_________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________o  =               Dynamic          Yes or No      You supply  Yesn               filters?  ;               Dynamic filter   Max. 32        You supply  -u)               name(s)          charactersn  =               Static filters?  Yes or No      You supply  Yesd  ;               Filter name(s)   Max. 32        You supply  - I               _________________characters________________________________d                                                9         4-20 Configuring VAX P.S.I. and VAX P.S.I. Access            I                              Configuring VAX P.S.I. and VAX P.S.I. Access_I       4.3 Recording the Information You Need for VAX P.S.I. Configuration     F               Table 4-12 lists the information you need to supply whenI               you create filters in the gateway clients, Applications andcG               Declaring a Network Process sections of the configuration                program.  G               Table 4-12 VAX P.S.I. Configuration Information: Filters- D                          for Applications and Network Processes (AllH                          Systems) and gateway clients (Multihost SystemsI               ___________Only)___________________________________________i  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   B               Name             Max. 32        You supply  FILTER-n)                                characters   ;               Priority         Decimal        You supply  1e%                                number   G               Incoming DTE     Max. 15        You supply  Not specifiedi%               address          digits   G               Call data value  Hexadecimal    You supply  Not specifiedy%                                digits   G               Call data mask   Hexadecimal    You supply  Not specified %                                digits   G               Subaddress       Range of       You supply  Not specified &               range            numbers  G               DTE class        Max. 32        You supply  Not specified )                                characters   G               Sending DTE      Max. 15        You supply  Not specified %               address          digits   G               Receiving DTE    Max. 15        You supply  Not specified %               address          digits   G               Group            Max. 32        You supply  Not specifiedf)                                characterst  G               Originally       Max. 15        You supply  Not specified %               called address   digits   I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-21c           4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. ConfigurationV    F               Table 4-12 (Cont.) VAX P.S.I. Configuration Information:E                                  Filters-for Applications and NetworksD                                  Processes (All Systems) and gatewayI               ___________________clients_(Multihost_Systems_Only)________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   G               Redirect reason  One of:        You supply  Not specified ,                                Not specified#                                Busy +                                Out of ordere)                                Systematic   G               Called address   Hexadecimal    You supply  Not specified-%               extension value  digits   G               Called address   Hexadecimal    You supply  Not specified %               extension mask   digits   G               Called NSAP      Hexadecimal    You supply  Not specified_I               _________________digits____________________________________   G               Table 4-13 lists the information you need to complete the =               Templates section of the configuration program.                                       9         4-22 Configuring VAX P.S.I. and VAX P.S.I. Accessn u  i      I                              Configuring VAX P.S.I. and VAX P.S.I. Access_I       4.3 Recording the Information You Need for VAX P.S.I. Configurationo    H               Table 4-13 VAX P.S.I. Configuration Information: TemplatesI               ___________(All_Systems)___________________________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________m  D               Name             Max. 32        You supply  TEMPLATE-n)                                characters   G               DTE class        Max. 32        You supply  Not specified )                                characters.  G               Call data        Hexadecimal    You supply  Not specified.%                                digitse  G               Packet size      Hexadecimal    You supply  Not specified %                                digitsi  G               Window size      Decimal        You supply  Not specifiedl%                                number   G               Destination DTE  Max. 15        You supply  Not specifiedr%               address          digits_  G               Fast select      One of:        You supply  Not specifiedD,               option           Not specified*                                Fast select,                                With response&                                No fast%                                selecti  ?               Reverse          True or False  You supply  Falsea               charging  G               Selected group   Max. 32        You supply  Not specified )                                characters                 I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-23            4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configurationu    F               Table 4-13 (Cont.) VAX P.S.I. Configuration Information:I               ___________________Templates_(All_Systems)_________________h  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   @               Throughput       A range of     You supply  {0..0}*               class request    values, the,                                max. and min.+                                to be choseni$                                from:$                                    0$                                   75$                                  150$                                  300$                                  600$                                 1200$                                 2400$                                 4800$                                 9600$                                19200$                                48000  G               Network user     Max. 32        You supply  Not specified )               identity         characters   G               Local            Max. 32        You supply  Not specified )               facilities       characters   ?               Charging         True or False  You supply  Falsed               information   G               RPOA sequence    Decimal        You supply  Not specified %                                number   G               Local            Decimal        You supply  Not specifiedr%               subaddress       numberG  G               Target address   Hexadecimal    You supply  Not specified %               extension        digits   ?               NSAP mapping     True or False  You supply  False   G               Calling address  Hexadecimal    You supply  Not specified %               extension        digitst  9         4-24 Configuring VAX P.S.I. and VAX P.S.I. Accessn A  .      I                              Configuring VAX P.S.I. and VAX P.S.I. AccessdI       4.3 Recording the Information You Need for VAX P.S.I. ConfigurationP    F               Table 4-13 (Cont.) VAX P.S.I. Configuration Information:I               ___________________Templates_(All_Systems)_________________y  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default_________  G               Transit delay    Decimal        You supply  Not specifiedt%               selection        number   G               End-to-end       Decimal        You supply  Not specified %               delay            number   G               Quality of       Max. 32        You supply  Not specified )               service          characters   G               Expedited data   One of:        You supply  Not specified ,               option           Not specified"                                UseI               _________________Do_not_use________________________________h                                                  I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-25  l         4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configuration     C               Table 4-14 lists the information you need to completeoC               the Incoming Security for Applications section of thee$               configuration program.  G               Table 4-14 VAX P.S.I. Configuration Information: Incoming I               ___________Security_for_Applications_(All_Systems)_________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   ;               Select an        -              You supply  -                applicationm  ;               DTE addresses    Max. 15        You supply  -d(               of systems that  digits[1]               can call this_               application_               only if thet               remote system                is charged for               the call  ;               DTE addresses    Max. 15        You supply  -I(               of systems that  digits[1]               can call thisf               application                irrespective ofC               who pays for               the call  I               [1]The_value_required_is_a_remote_address_prefix_(RAP).____   E               This can be a full DTE address, or it can be an address D               prefix, which would stand for all DTEs with an address)               beginning with this prefix.u                  9         4-26 Configuring VAX P.S.I. and VAX P.S.I. Accesse           I                              Configuring VAX P.S.I. and VAX P.S.I. Access I       4.3 Recording the Information You Need for VAX P.S.I. Configuration     F               Table 4-14 (Cont.) VAX P.S.I. Configuration Information:H                                  Incoming Security for Applications (AllI               ___________________Systems)________________________________b  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________D  >               DTE addresses    Max. 15        You supply  *[2](               of systems       digits[1]               that cannot                call thisc               application_I               [1]The_value_required_is_a_remote_address_prefix_(RAP).____t  E               This can be a full DTE address, or it can be an addressrD               prefix, which would stand for all DTEs with an address)               beginning with this prefix. G               [2]The wildcard character (*) means all unspecified DTEs. H               If you enter the wildcard character to stand for DTEs thatG               have Remote Charge or All access, there is no default for G               this value, and the only DTEs that are not allowed accessd4               are those that you specify explicitly.I               ___________________________________________________________.                                          I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-27n h  n      4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configuration     C               Table 4-15 lists the information you need to complete F               the Outgoing Security for Local Processes section of the$               configuration program.  G               Table 4-15 VAX P.S.I. Configuration Information: OutgoingsI               ___________Security_for_Local_Processes_(All_Systems)______   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   ;               Enter a rights   -              You supply  -a               identifier  ;               DTE addresses    Max. 15        You supply  -_(               of systems       digits[1]               that can be                called by                processes with               this rights.               identifier only                if they pay forg               the call  ;               DTE addresses    Max. 15        You supply  -X(               of systems       digits[1]               that can bet               called byt               processes with               this rightsa               identifier               irrespective ofi               who pays for               the call  I               [1]The_value_required_is_a_remote_address_prefix_(RAP).____   E               This can be a full DTE address, or it can be an addressoD               prefix, which would stand for all DTEs with an address)               beginning with this prefix.x          9         4-28 Configuring VAX P.S.I. and VAX P.S.I. Accessa r         I                              Configuring VAX P.S.I. and VAX P.S.I. Access I       4.3 Recording the Information You Need for VAX P.S.I. Configurationo    F               Table 4-15 (Cont.) VAX P.S.I. Configuration Information:F                                  Outgoing Security for Local ProcessesI               ___________________(All_Systems)___________________________r  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   ;               Names of PVCs    Max. 32        You supply  - )               that can be      characters_               accessed bya               processes with               this rights                identifier[3]   >               DTE addresses    Max. 15        You supply  *[2](               of systems       digits[1]               that cannot                be called by               processes with               this rights                identifier[3]   >               Names of PVCs    Max. 32        You supply  *[2])               that cannot      characters                be accessed by               processes with               this rights                identifier[3]cI               [1]The_value_required_is_a_remote_address_prefix_(RAP)._____  E               This can be a full DTE address, or it can be an address D               prefix, which would stand for all DTEs with an address)               beginning with this prefix.dF               [2]The wildcard character (*) means all unspecified DTEsG               or PVCs. If you enter the wildcard character to stand forVG               DTEs or PVCs that have Remote Charge or All access, thereiG               is no default for these values, and the only DTEs or PVCseD               that are not allowed access are those that you specify               explicitly.rE               [3]You are asked for this information only if PVCs haves               been set up.I               ___________________________________________________________     I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-29i _  e      4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configuration     G               Table 4-16 lists the information you need to complete the D               Incoming Security for Network Processes section of the$               configuration program.  G               Table 4-16 VAX P.S.I. Configuration Information: Incoming_I               ___________Security_for_Network_Processes_(All_Systems)____   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________t  ;               Select a filter  -              You supply  -a  ;               DTE addresses    Max. 15        You supply  - (               of systems       digits[1]               that can call                access thisr               filter only if               remote systemg               is charged for               the call  ;               DTE addresses    Max. 15        You supply  -a(               of systems       digits[1]               that can accessa               this filters               irrespective ofO               who pays for               the call  >               DTE addresses    Max. 15        You supply  *[2](               of systems that  digits[1]               cannot accessd               this filter_I               [1]The_value_required_is_a_remote_address_prefix_(RAP).____   E               This can be a full DTE address, or it can be an address D               prefix, which would stand for all DTEs with an address)               beginning with this prefix.5G               [2]The wildcard character (*) means all unspecified DTEs. H               If you enter the wildcard character to stand for DTEs thatG               have Remote Charge or All access, there is no default forkG               this value, and the only DTEs that are not allowed access 4               are those that you specify explicitly.I               ___________________________________________________________   9         4-30 Configuring VAX P.S.I. and VAX P.S.I. Access  c  e      I                              Configuring VAX P.S.I. and VAX P.S.I. AccessMI       4.3 Recording the Information You Need for VAX P.S.I. Configurationg    C               Table 4-17 lists the information you need to completecF               the Incoming Security for Gateway Clients section of the$               configuration program.  G               Table 4-17 VAX P.S.I. Configuration Information: IncomingrH                          Security for Gateway Clients (Multihost SystemsI               ___________Only)___________________________________________d  0                                          Form in@                                          which it       Where toI               Information_required_______is_required____find_it___Defaultl  C               Select a gateway client    -              You       - >                                                         supply  C               DTE addresses of systems   Max. 15        You       - >               that can call the client   digits[1]      supply%               systems associated withn!               this gateway clienti#               only if remote systeme%               is charged for the call_  C               DTE addresses of systems   Max. 15        You       - >               that can call the client   digits[1]      supply%               systems associated withs!               this gateway clientO&               irrespective of who pays               for the call  F               DTE addresses of systems   Max. 15        You       *[2]>               that cannot call the       digits[1]      supply'               client systems associated &               with this gateway clientI               [1]The_value_required_is_a_remote_address_prefix_(RAP)._____  E               This can be a full DTE address, or it can be an address_D               prefix, which would stand for all DTEs with an address)               beginning with this prefix.fG               [2]The wildcard character (*) means all unspecified DTEs. H               If you enter the wildcard character to stand for DTEs thatG               have Remote Charge or All access, there is no default for G               this value, and the only DTEs that are not allowed access 4               are those that you specify explicitly.I               ____________________________________________________________  I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-31  o  t      4         Configuring VAX P.S.I. and VAX P.S.I. AccessK         4.3 Recording the Information You Need for VAX P.S.I. Configuration     G               Table 4-18 lists the information you need to complete theaD               Outgoing Security for accessing Systems section of the$               configuration program.  G               Table 4-18 VAX P.S.I. Configuration Information: OutgoinguG                          Security for Client Systems (Multihost Systems I               ___________Only)___________________________________________   0                                          Form in@                                          which it       Where toI               Information_required_______is_required____find_it___Defaulto  C               Client system              Max. 400       You       - >                                          characters     supply  C               Security name for client   Max. 32        You       - >               system                     characters     supply  C               DTE addresses of systems   Max. 15        You       - >               that can be called by      digits[1]      supply%               this client system onlyg'               if the remote systems pay2               for the call  C               DTE addresses of systems   Max. 15        You       - >               that can be called         digits[1]      supply#               by this client systemr&               irrespective of who pays               for the call  C               Names of PVCs that can be  Max. 32        You       - >               accessed by this client    characters     supply               system[3]l  I               [1]The_value_required_is_a_remote_address_prefix_(RAP).____n  E               This can be a full DTE address, or it can be an addresseD               prefix, which would stand for all DTEs with an address)               beginning with this prefix.uE               [3]You are asked for this information only if PVCs have                been set up.        9         4-32 Configuring VAX P.S.I. and VAX P.S.I. Access            I                              Configuring VAX P.S.I. and VAX P.S.I. Access I       4.3 Recording the Information You Need for VAX P.S.I. Configuration     F               Table 4-18 (Cont.) VAX P.S.I. Configuration Information:E                                  Outgoing Security for Client Systems I               ___________________(Multihost_Systems_Only)________________   0                                          Form in@                                          which it       Where toI               Information_required_______is_required____find_it___Default   F               DTE addresses of systems   Max. 15        You       *[2]>               that cannot be called by   digits[1]      supply#               this client system[3]   F               Names of PVCs that cannot  Max. 32        You       -[1]>               be accessed by this        characters     supply               client system[3]I               [1]The_value_required_is_a_remote_address_prefix_(RAP).____   E               This can be a full DTE address, or it can be an address D               prefix, which would stand for all DTEs with an address)               beginning with this prefix. F               [2]The wildcard character (*) means all unspecified DTEsG               or PVCs. If you enter the wildcard character to stand forSG               DTEs or PVCs that have Remote Charge or All access, therenG               is no default for these values, and the only DTEs or PVCsmD               that are not allowed access are those that you specify               explicitly.fE               [3]You are asked for this information only if PVCs have_               been set up.I               ___________________________________________________________i  8         4.4 Running the VAX P.S.I. Configuration Program  F               To configure your VAX P.S.I. system, you need to run the2               psi$configure.com command procedure.  I               This procedure allows you to set up the VAX P.S.I. system'so/               permanent configuration database.   ;         4.4.1 Starting the VAX P.S.I. Configuration Program   G               To start the program, log in to any account that has OPER :               and SYSPRV privileges and enter the command:  *               $ @sys$manager:psi$configure  I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-33_ _  _      4         Configuring VAX P.S.I. and VAX P.S.I. Access8         4.4 Running the VAX P.S.I. Configuration Program    8         4.4.2 Using the VAX P.S.I. Configuration Program  I               The configuration program consists of a number of sections, C               each corresponding to a logical group of information. G               Each section consists of one or more screens on which you E               can enter data. All sections (with the exception of thegF               X.29 and Mail support section) also have an introductory!               information screen.   E               Most sections are optional. These sections begin with a E               question of the form: "Do you want to set up X?" If you D               select Yes, you go through the rest of the section. IfE               you select No, you go directly to the next new section, G               although you can decide at a later stage to complete thatM*               section (See Section 4.4.3).  $         4.4.2.1 Entering Information  B               The program prompts you for information in two ways:  G               o  For some questions, you choose your answer from a menu =                  by using the arrow keys and pressing Return.   D               o  For other questions, you type data into a field and                  press Return.  "               Horizontal Scrolling  G               Usually, when you type data into a field, you can see theeE               entire field on the screen. However, in some cases, the C               maximum length of the data you are allowed to type is E               too long to fit into the field shown on the screen; for F               example, a node name, which may be up to 400 characters.H               In such cases, the field scrolls horizontally as you enter               data.P  G               Note that horizontal scrolling works only if the keyboardfE               is in Insert mode, not if it is in Overstrike mode. ThePG               words Insert or Overstrike appear in the upper right-handnH               corner of the screen to indicate which mode you are using.@               Press Ctrl/A to change from one mode to the other.  E               When you have entered all the required information on a I               screen, a new screen appears automatically. You cannot move C               forward until you have completed the required fields.   9         4-34 Configuring VAX P.S.I. and VAX P.S.I. Access            I                              Configuring VAX P.S.I. and VAX P.S.I. AccesssI                          4.4 Running the VAX P.S.I. Configuration ProgramE    F                 ________________________ Note ________________________  D                 The configuration program indicates it is processingC                 input by flashing the message working in the bottomT/                 left-hand corner of the screen.r  F                 ______________________________________________________  '         4.4.2.2 Moving Within a Section   F               To move backward within a section, press the Prev ScreenD               key. You are allowed to move backward within a sectionH               whether you have finished it or not. However, you can moveF               backward only as far as the first screen of the section.B               To reach another section, use the Sections Menu (see               Section 4.4.3).e  F               If you have moved back to look at completed screens, youH               can move forward again by pressing the Next Screen key. DoF               this until you reach an incomplete screen. Then completeB               the required fields on that screen before moving on.           4.4.3 Options Menu  E               When you leave the last screen in a section, an Options_               menu appears.   D               Generally, the Options menu for a section provides the                following choices:  (               o  Continue to new section                 o  Add an xh                 o  Modify an x                 o  Delete an x  $               o  Go to Sections menu  >               where x is the item you created in that section.  F               For example, the PVC Options menu provides the following               choices:  *               o  Continue to a new section                 o  Add a PVC                 o  Modify a PVC                  o  Delete a PVC   I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-35h c  b      4         Configuring VAX P.S.I. and VAX P.S.I. Access8         4.4 Running the VAX P.S.I. Configuration Program    $               o  Go to Sections menu  /               These options are described here.                  Continue  E               Choose this option when you finish entering or amendingDC               information in the current section. The configurationlG               program then displays the first screen in the next unseenr               section.                 AddX  E               Choose this option to add another item in this section.   F               For example, when you finish entering data for a PVC andI               you want to add another PVC, choosing this option takes you-;               back to the first data entry screen for PVCs.                  Modify  I               Choose this option to modify some or all of the informationt4               you provided previously about an item.  I               For example, if you choose this option from the PVC Options F               menu, the next screen lists all the PVCs defined so far.F               You select one of these (PVC1, for example), and then goF               back to the first data entry screen for PVCs. The fieldsH               contain the information you provided when you first set upH               PVC1. You can modify any of this information. Use the NextH               Screen key and the Prev Screen key to move between screens,               that you do not want to alter.                 Delete  C               Choose this option to delete an item in this section.C  I               For example, if you choose this option from the PVC OptionsrD               menu, a list of all PVCs defined on your system so farC               appears on the screen. Select one of these (PVC2, forTD               example), and you are asked for confirmation that this,               is the one you want to delete.  !               Go to Sections Menu   G               Choose this option to go to the Sections menu. From therehG               you can go on to the Options menu of a different section.p  9         4-36 Configuring VAX P.S.I. and VAX P.S.I. Accessd a  t      I                              Configuring VAX P.S.I. and VAX P.S.I. AccesssI                          4.4 Running the VAX P.S.I. Configuration Programr    !         4.4.4 Creating NCL Scriptw  F               The final section in the configuration program is CreateI               the NCL Script. You are asked if you want to create the NCL                script.   F               o  If you answer YES, the configuration program uses theH                  information you have entered to create two files of NCL                  commands.  G               o  If you answer NO, you see a Sections menu, showing alloF                  the completed sections. At this point, you can returnD                  to any of these sections and modify, add, or deleteG                  information. When you want to create an NCL script, gooH                  to the Sections menu from any of the Options menus, and.                  select Create the NCL Script.  D               o  After the NCL scripts are created, you are asked ifD                  you want to run a command file called psi$security_!                  identifiers.com.u  F                  This file is created by the configuration program, toD                  add certain rights identifiers to the system rightsG                  database on your system. The rights to be added depend ?                  on the security information you have supplied.t  =                  You can run the command file from within thedB                  configuration procedure, or you can exit from theF                  configuration program and run the command file later.E                  Note that you cannot start VAX P.S.I. until you haverE                  run this command file. This is true even if you have F                  selected not to set up X.25 security for your system.  E                  If you edit the command procedure before running it, G                  you must make corresponding changes to the NCL scriptsr6                  before attempting to start VAX P.S.I.  !         4.4.5 Exiting the Program   I               Once it has created the NCL scripts, the program returns to H               the main menu. You can then choose the Exit option to exit               the program.  D               If, for some reason, the program cannot create the NCLH               script, an error message appears at the foot of the screenC               and the cursor stays on the question, "Do you wish towG               create the NCL scripts now?" You must correct the problem 5               before you answer YES to this question._  I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-37            4         Configuring VAX P.S.I. and VAX P.S.I. Access8         4.4 Running the VAX P.S.I. Configuration Program    I               To quit the program, without creating a set of NCL scripts,rI               press the F8 key; however, this deletes all the informationa!               you entered so far.   >         4.4.6 Requirement to Complete VAX P.S.I. Configuration  D               You cannot leave the configuration program unfinished.I               That is, you cannot retain the data you entered if you exit_6               before you create a valid configuration.  C               If you quit prematurely by pressing F8, you receive a F               warning message, asking for confirmation. If you confirmG               that you want to quit, everything you have entered so far                is lost.           4.4.7 Getting Help  I               You can get help at any time during the program by pressings               the Help key.   ?         4.4.7.1 Getting Help on a Specific Field or Menu Choicey  @               If you press the Help key while the cursor is on aB               particular field or menu choice, three lines of textD               appear near the bottom of the screen. These lines tellG               you what sort of value is expected in that field, or what 9               the implications are of making that choice.   E               If you press the Help key again, the screen is replaced H               by additional information about that field or menu choice.F               Press the F10 key to leave help and return to the screen=               from which you pressed the Help key originally.   $         4.4.7.2 Getting General Help  H               If you press the Help key while on any of the introductoryD               screens, the screen is replaced by general informationD               about that section. For example, pressing the Help keyD               while on the PVC introduction screen brings up general"               information on PVCs.  H               You can also reach this section help from the Options menu)               for any particular section.l    9         4-38 Configuring VAX P.S.I. and VAX P.S.I. Accessn h  n      I                              Configuring VAX P.S.I. and VAX P.S.I. AccesspI                          4.4 Running the VAX P.S.I. Configuration Program_    +         4.4.7.3 Getting Help on the ProgramA  I               You can get help on the configuration program (for example,.F               which keys you can use, how to navigate between screens)F               by pressing the Help key while you are on any other Help               screen.o           4.5 Testing VAX P.S.I.  =               This section explains how to run the VAX P.S.I. )               configuration test program.l  F                 ________________________ Note ________________________  E                 Before you can test the VAX P.S.I. configuration, you_F                 must run the net$configure.com configuration procedureC                 (in either BASIC or ADVANCED mode) to configure the &                 system on the network.  F                 ______________________________________________________  G               You use the configuration test program (CTP) to check any E               synchronous DTEs (and associated PVCs) that your system ,               uses to make or receive calls.  <               You can operate the CTP in one of three modes:                 o  Send/Receiver                 o  Receive Only                  o  Send Only  D               In Send/Receive mode, you can do two types of testing:  F               o  Loopback testing, in which calls are sent to the PSDNG                  and then looped back to your system. The PSDN used for E                  the CTP must allow loopback from the network to youry                  system.  H               o  Testing to a remote DTE, in which calls are sent to and,                  received from a remote DTE.  I               In Receive Only and Send Only modes, you can only test to aa               remote DTE.   I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-39f (  )      4         Configuring VAX P.S.I. and VAX P.S.I. Access         4.5 Testing VAX P.S.I.    &         4.5.1 Preparing to Run the CTP  D               This section describes the checks you must make before               running the CTP.  !               Privileges Required                  o  NETMBX                  o  TMPMBXP                 o  WORLD                 o  CMKRNL                  o  DETACHi                 o  SYSPRV.  $               System Quotas Required                 o  ASTLM = 100                 o  BIOLM = 100                 o  BYTLM = 40000                 o  BIOLM = 100                 o  TQELM = 30n  !               VAX P.S.I. Software   B               o  VAX P.S.I. must be configured and running on your                  system.  B               o  The DTE you want to use to make and receive callsF                  must be up and running. To check, enter the following                  commands.  %                  Native or Multihost:M  :                  ncl> show x25 protocol dte dte-name state                    Access:  3                  ncl> show node connector-node-id - 6                  _ncl> x25 protocol dte dte-name state  H                  If the status of your DTE is not shown as RUNNING, waitF                  for 2 minutes and try again. If your DTE is still notB                  RUNNING, refer to the X.25 Problem Solving guide.  9         4-40 Configuring VAX P.S.I. and VAX P.S.I. Access  l  t      I                              Configuring VAX P.S.I. and VAX P.S.I. Access I                                                    4.5 Testing VAX P.S.I.                    Remote Systemi  E               o  The remote system must have VAX P.S.I. V4.3 or latert(                  configured and running.  D               o  You must know the DTE address and subaddress of the                  remote system.            4.5.2 Running the CTP   F               You can run the CTP either interactively or as a networkH               object. When the CTP is set up as a network object, it canH               only handle incoming calls (either from a remote system or>               calls that have been looped back from the PSDN).  -         4.5.2.1 Running the CTP Interactively   *               Enter the following command:  $               $ run sys$test:psi$ctp  H               After some introductory screens, you are asked if you wantH               to run the CTP in Send/Receive mode, Receive Only mode, or               Send Only mode.e  A               o  If you run the CTP in Send/Receive mode, you canPF                  test your system's ability to communicate with a PSDN;                  (loopback testing) or with remote systems.a  E               o  If you run the CTP in Receive Only mode or Send OnlyaG                  mode, you can test your system's ability to make callso9                  to or receive calls from remote systems.P  3         4.5.2.2 Running the CTP as a Network Objects  *               Enter the following command:  4               $ mcr ncl @sys$test:psi$ctp_add_netobj  C               To run the CTP as a network object automatically when D               you start VAX P.S.I., you should add the above line to               psi$startup.com.  H               To remove the CTP as a network object, enter the following               command:  4               $ mcr ncl @sys$test:psi$ctp_rem_netobj  I                         Configuring VAX P.S.I. and VAX P.S.I. Access 4-41     e      4         Configuring VAX P.S.I. and VAX P.S.I. Access2         4.6 Changing Your VAX P.S.I. Configuration    2         4.6 Changing Your VAX P.S.I. Configuration  2               To modify an existing configuration:  7               o  Run psi$configure.com (Section 4.4.1).   1               o  At the main menu, choose Modify.o  I               o  The next screen is the Sections Menu, from which you can I                  modify, add to, or delete any of the information entered                   previously.  F                 ________________________ Note ________________________  E                 When you run the configuration program to modify your A                 existing configuration, the configuration programdD                 retrieves the information you supplied the last time$                 you ran the program.  B                 If you manually changed the NCL script produced by@                 the configuration program, or if you dynamicallyB                 changed your configuration by issuing NCL commandsD                 interactively, this changed information is lost whenB                 you select Modify, unless you quit the program (byC                 pressing the F8 key) before asking it to create theo                 NCL script.a  F                 ______________________________________________________  3         4.7 Creating a New VAX P.S.I. Configurationt  H               To delete your existing configuration and create a new set               of NCL scripts:   7               o  Run psi$configure.com (Section 4.4.1).y  1               o  At the main menu, choose Create.a                9         4-42 Configuring VAX P.S.I. and VAX P.S.I. Accessn A  .                    I                                                                  Part IIIAI         _________________________________________________________________r  I                 Installing and Configuring X.25 for OpenVMS Alpha Systems_            D               Part III describes the prerequisite steps necessary toG               install and configure X.25 for OpenVMS Alpha. It includes %               the following chapters:r  6               o  Chapter 5 - Planning the Installation  H               o  Chapter 6 - Preparing to Install X.25 for OpenVMS Alpha  >               o  Chapter 7 - Installing X.25 for OpenVMS Alpha  4               o  Chapter 8 - Post-installation Tasks i                       I                                                                         5dI         _________________________________________________________________o  I                                Planning to Install X.25 for OpenVMS Alpha              5.1 Product Description   E               X.25 for OpenVMS Alpha enables appropriately configuredrH               systems to connect to an X.25 packet switched data networkB               (PSDN) via an X.25 relay node on the same local areaD               network (LAN), via an X.25 connector node, or directlyH               using a synchronous communications device. Full details ofF               the features and facilities provided by X.25 for OpenVMSE               Alpha are provided in the Software Product Description. D               For more conceptual information on PSDNs, refer to the,               <REFERENCE>(DNPLUS_OVMS_USER).  G               Throughout the rest of this section, the product X.25 fori3               OpenVMS Alpha is referred to as X.25.            5.2 Required Hardwarev  ?               To install X.25, you need the following hardware:i  =               o  A CD reader (if installing an Alpha version)   I               o  A CD reader, magnetic tape drive, or TK50 tape drive (if *                  installing a VAX version)                 o  A terminal   @               You can use either a hardcopy or video terminal toB               communicate with the operating system and respond to6               prompts from the installation procedure.  E               If you intend to access a PSDN directly, an appropriateoH               synchronous interface card is required. For details of theH               synchronous communications devices supported, refer to theI               System Support Addendum (SSA). The SSA is supplied with the F               X.25 Software Product Description (SPD) on the Media CD.  I                            Planning to Install X.25 for OpenVMS Alpha 5-1            2         Planning to Install X.25 for OpenVMS Alpha         5.3 Required Software              5.3 Required Software   F               X.25, Version 1.1-B, requires Version 7.1 of the OpenVMSG               operating system. Future X.25 releases may require highernC               versions of the operating system, as described in thehH               online release notes associated with each product release.  F               During the installation of X.25, a check is made for theI               required DECnet-Plus and WANDD software. If the DECnet-Plus E               software is not present, you are prompted to install itsF               before proceeding. If the WANDD software is not present,H               the X.25 installation procedure automatically installs it.F               Note that X.25 cannot be run without the DECnet-Plus for               OpenVMS software.t  I               You must install the following X.25 installation kits usingi;               the POLYCENTER Software Installation utility:   .               o  DEC-AXPVMS-X25-V0100-B-1.PCSI  0               o  DEC-AXPVMS-WANDD-V0100-B.1.PCSI           5.4 Kit Location  I               To obtain the directory location of the X.25 kit on the CD, G               refer to the OpenVMS Layered Products Compact Disc User's G               Guide that accompanies the CD distribution kit, or before B               starting installation, complete the following steps:  E               1. To determine whether the CD drive is already mountedt>                  (mount command), enter the following command:  *                  $ show device device-name  B               2. If it is not mounted, enter the appropriate mountG                  command to mount the CD (omit the /FOREIGN qualifier).n  E               3. To obtain the save-set name, use a directory commandnI                  specifying the directory file from the previous command:w  1                   $ directory dka400:[kits]*.pcsi   I               If you are installing from a magnetic tape or a TK50, refer E               to the appropriate user guide for further instructions.e  6         5-2 Planning to Install X.25 for OpenVMS Alpha    s      I                                Planning to Install X.25 for OpenVMS Alpha,I                                              5.5 Time Required to Installr    $         5.5 Time Required to Install  D               The time required to install X.25 depends on the mediaC               type, the CPU type, and your system configuration. IndH               general, the procedure should require less than 5 minutes.                                                                                I                            Planning to Install X.25 for OpenVMS Alpha 5-3r t  d                    I                                                                         6dI         _________________________________________________________________   I                               Preparing to Install X.25 for OpenVMS Alpha     D               This chapter details the tasks you need to complete or.               consider before installing X.25.  +         6.1 Inspecting the Distribution Kitr  E               The software bill of materials (BOM) included with yoursG               distribution kit shows the components of the kit. ComparesH               the items you received against the BOM. Report any damagedI               or missing components to DIGITAL before continuing with theg               installation.   .         6.2 Logging In to a Privileged Account  F               To install X.25, you must be logged into an account that>               has SETPRV or at least the following privileges:                 o  CMKRNLt                 o  WORLD                 o  SYSPRV   D               The POLYCENTER Software Installation utility turns off@               BYPASS privilege at the start of the installation.  C               To determine the default privileges of the installingtB               account, log in and enter the following DCL command:  '               $ show process/privilegesE  F               If the account lacks the SETPRV privilege, do one of the               following:  H               o  Ask your system manager to use the AUTHORIZE utility toH                  modify the default privileges of the account to include%                  the SETPRV privilegef  I                           Preparing to Install X.25 for OpenVMS Alpha 6-1  o  t      3         Preparing to Install X.25 for OpenVMS Alphae.         6.2 Logging In to a Privileged Account    H               o  Run the AUTHORIZE utility and make the changes yourself:                  if your account has the SYSPRV privilege:  )                  $ set default sys$systema                   $ run authorize=                  UAF> modify account-name/privileges=(setprv)                   UAF> exit  H               To activate the change in privileges, log out and then log               in again.d  .         6.3 Accessing the Online Release Notes  F               You should review the release notes for a description ofD               new features, differences between multiple versions of>               X.25, and changes in the installation procedure.  G               To access the release notes, issue the following command:f  G               $ product extract release_notes x25 /source=dka400:[kits]t&                         /file=filename  D               In the above example, the directory on the CD in which?               the installation kit is located is referred to as F               dka400:[kits]. You should substitute this directory nameI               with the actual directory location of the X.25 kit. Details H               on how to determine the directory location of the X.25 kit*               are provided in Section 5.4.  D               The product selected is displayed and you are prompted6               whether to continue with the extraction.  F               To extract the release notes, type YES and press Return.H               The release notes are written to the specified file, which'               you can display or print.b  =               If you do not use the /FILE qualifier to define <               the required location of the extracted releaseB               notes, the release notes are extracted into the fileB               DEFAULT.PCSI$RELEASE_NOTES in the current directory.  A               To cancel the extraction, type NO and press Return.   F                 ________________________ Note ________________________  E                 After X.25 and WANDD are installed, the release notes ;                 file is located in SYS$HELP in the form of:   &                    X25*RELEASE_NOTES.*  7         6-2 Preparing to Install X.25 for OpenVMS Alphai y  a      I                               Preparing to Install X.25 for OpenVMS Alpha I                                    6.3 Accessing the Online Release Notes     (                    WANDD*RELEASE_NOTES.*  F                 ______________________________________________________  .         6.4 Determining Process Account Quotas  H               The POLYCENTER Software Installation utility requires thatD               the installation account has, as a minimum, the quotas!               shown in Table 6-1.   I               Table_6-1_Process_Quotas_for_the_Installing_Account_________  I               Quota_____Value____________________________________________n                 ASTLM     24                 BIOLM     18                 BYTLM     32768s                 DIOLM     18                 ENQLM     200h  I               FILLM_____100______________________________________________   D               Use the OpenVMS Authorize utility to verify and changeE               process quotas for the installation account in the useroG               authorization file (SYSUAF.DAT). (Some sites may restricttA               the use of the OpenVMS Authorize utility to certain "               accounts or people.)  H               For example, to verify and then change the BYTLM quota forH               the account-name installation account, enter the following               command sequence:   I               ___________________________________________________________eI               To..._______________Enter..._______________________________   <               Invoke the          $ run sys$system:authorize               Authorize utilityt  7               Show the account    UAF> showaccount-name                quotas  I               Modify the BYTLM    UAF> modify account-name /BYTLM = 32768T               quotar  +               Exit from the       UAF> exit                Authorize utility   I                           Preparing to Install X.25 for OpenVMS Alpha 6-3            3         Preparing to Install X.25 for OpenVMS Alpha .         6.4 Determining Process Account Quotas  I               ___________________________________________________________0I               To..._______________Enter..._______________________________   I               Log_out_____________$_logout_______________________________   I               After you verify and change the quotas for the installationcE               account, log out of the installation account and log inoH               again. The new quotas will take effect and you can proceed$               with the installation.  H               User account quotas are stored in the file SYSUAF.DAT. ForF               more information about modifying account quotas, see theH               description of the Authorize utility in the OpenVMS system.               management documentation subkit.  "         6.5 Determining Disk Space  ?               Installing X.25 and WANDD on your system requiresuD               approximately 12000 blocks of free disk storage space.F               This figure includes space to store the Release Notes in               SYS$HELP.   G               To determine the number of free disk space on the current I               system disk, enter the following command at the DCL prompt:P  )               $ show device sys$sysdeviceu  H               If necessary, create enough free disk space to accommodate'               the installation of X.25.t                                  7         6-4 Preparing to Install X.25 for OpenVMS Alphai y                       I                                                                         7 I         _________________________________________________________________   I                                         Installing X.25 for OpenVMS Alphan    G               This chapter describes the tasks necessary for installing H               X.25. It also describes how to display a list of the files@               installed on your system during X.25 installation.  I               Refer to Figure 7-1 as a guideline when installing X.25 for G               OpenVMS Alpha. Section 7.4 provides annotated examples of F               typical prompt and response sequences that are displayed'               during X.25 installation.o  1         7.1 Registering the X.25 Software Licensen  D               Before you run X.25 on a newly licensed node, you mustI               first register a License Product Authorization Key (LicenseoC               PAK) using the License Management Facility (LMF). ThejB               License PAK may be shipped along with the kit if youF               ordered the license and media together; otherwise, it isD               shipped separately to a location based on your licenseF               order. If you are installing X.25 as an update on a nodeB               already licensed for this software, you have alreadyB               completed the License PAK registration requirements.  H               For information on using LMF, refer to the OpenVMS License(               Management Utility Manual.  E               If you are installing prerequisite or optional software D               along with X.25, review the PAK status and install theG               PAKs for any prerequisite or optional software before you                install X.25.c  I               You must register and load your license for X.25 to use the D               software. The X.25 license is required if you want to:  &               o  Use X.25 applications  +               o  Allow incoming X.29 logins   @               o  Use X.25 over a synchronous communications line  I                                     Installing X.25 for OpenVMS Alpha 7-1p r  t      )         Installing X.25 for OpenVMS Alphaa1         7.1 Registering the X.25 Software Licensee    6               A DECnet-Plus license allows the use of:  B               o  X.25 over LLC2 for DECnet routing over X.25 or toG                  provide Connection-Oriented Network Service (CONS) foro                  OSI transport  C               o  DECnet routing over DEC HDLC (High-level Data Link @                  Control) over a synchronous communications line  H               The X.25 product can now be installed and used on a systemD               using the PAK associated with the X.25 Client product.F               If you are installing the X.25 product on such a system,G               remove the X.25 Client product before installing the X.25                product.  H               Full details of the licensing requirements are provided inE               the Software Product Description (SPD) on the media CD.                                                         -         7-2 Installing X.25 for OpenVMS AlphaA .  .      I                                         Installing X.25 for OpenVMS Alpha I                                 7.1 Registering the X.25 Software License_    A               Figure 7-1 Installation and Configuration Flowchartu                                                                                        I                                     Installing X.25 for OpenVMS Alpha 7-3r e  S      )         Installing X.25 for OpenVMS Alpha 3         7.2 Installing X.25 Using the DCL Interfaceh    3         7.2 Installing X.25 Using the DCL Interfacet  H               For a description of all the features you can request whenG               starting an installation (such as purging files and usingTF               a product configuration file), refer to DCL help for the&               product install command.  ;               To install X.25, enter the following command:_  9               $ product install x25 /source=dka400:[kits]l  :               If you do not use the /SOURCE qualifier, the?               system attempts to read the installation kit fromn!               pcsi$source:[kits].c  D               In the above example, the directory on the CD in which?               the installation kit is located is referred to as F               dka400:[kits]. You should substitute this directory nameI               with the actual directory location of the X.25 kit. DetailssH               on how to determine the directory location of the X.25 kit*               are provided in Section 5.4.  *         7.3 Files Installed on Your System  H               The X.25 installation procedure installs a number of filesD               on your system. To list the files, enter the following               command:  0               $ product show object /product=x25  8         7.4 X.25 Installation and De-Installation Sample  H               This section provides two annotated examples that show theH               prompt and response sequence presented when the POLYCENTERC               Software Installation utility is run to install X.25.   B               This section also provides an annotated example thatC               shows the prompt and response sequence presented when D               the POLYCENTER Software Installation utility is run to               de-install X.25.  B               In all examples, numbered callouts (1, 2, 3, . . . )D               indicate parts of the prompt and response sequence forH               which additional explanatory notes are provided. The notes3               are given at the end of each example.   -         7-4 Installing X.25 for OpenVMS AlphaS    t      I                                         Installing X.25 for OpenVMS AlphalI                          7.4 X.25 Installation and De-Installation Sample     '         7.4.1 X.25 Installation Example.  G               This example shows a typical prompt and response sequence I               when installing both X.25 and WANDD for OpenVMS. It assumesyG               that OpenVMS and DECnet-Plus are already installed on ther               target system.  T               $ product install x25 /source=sys$login: /dest=sys$sysroot <Return>  1  6               The following product has been selected:H                   DEC AXPVMS X25 V1.0-B                  Layered Product  6               Do you want to continue? [YES]  <Return>  .               Configuration phase starting ...  \               You will be asked to choose options, if any, for each selected product and for]               any products that may be installed to satisfy software dependency requirements.   H               DEC AXPVMS X25 V1.0-B: X.25 V1.0-B for OpenVMS AXP Systems  7                   Copyright 1996 -- All rights reserveda  /                   Digital Equipment Corporation0  J               Do you want the defaults for all options? [YES]  <Return>  2  C                   This product uses the PAKs: <X25> or <X25-CLIENT>   U                   An X.25 License PAK should be loaded before continuing installatione  =                   Do you want to continue? [YES]  <Return>  3t  F                   Do you want to review the options? [NO]  <Return>  4  *               Execution phase starting ...  7               The following products will be installed: H                   DEC AXPVMS WANDD V1.0-B                Layered ProductH                   DEC AXPVMS X25 V1.0-B                  Layered Product  [               Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%   9               The following products have been installed: H                   DEC AXPVMS WANDD V1.0-B                Layered ProductH                   DEC AXPVMS X25 V1.0-B                  Layered Product               $   I                                     Installing X.25 for OpenVMS Alpha 7-5  d  o      )         Installing X.25 for OpenVMS Alphat8         7.4 X.25 Installation and De-Installation Sample    ;               Notes on Example Prompt and Response Sequence   D               1  This command invokes the installation procedure forF                  X.25. The SOURCE and DESTINATION qualifiers have beenH                  used to define the location of the source files and the>                  required location for the installed software.  ?               2  To accept the default values for the available @                  installation options, type YES or press Return.  H                  To enter values other than the default values, type NO.H                  In this case, the installation procedure prompts you toC                  enter values for each of the installation options._  C               3  The X.25 License PAK must be registered and loadedrF                  before X.25 can be started. Details about registeringB                  the X.25 License PAK are given in Section 7.1. IfE                  the X.25 License PAK is not loaded before completing E                  the installation, X25$STARTUP (which is normally run F                  automatically at the end of the installation) must be<                  run manually after loading the License PAK.  G               4  Responding YES to this question displays the currentlyiI                  selected values for the installation options and promptsrI                  you to verify that the selections are correct. If you doaH                  not want to view and confirm the options selected, type$                  NO or press Return.                                    -         7-6 Installing X.25 for OpenVMS Alphaf r  n      I                                         Installing X.25 for OpenVMS AlphaiI                          7.4 X.25 Installation and De-Installation Samples    *         7.4.2 X.25 De-Installation Example  G               This example shows a typical prompt and response sequence &               when de-installing X.25.  &               $ product remove x25   1  6               The following product has been selected:H                   DEC AXPVMS X25 V1.0-B                  Layered Product  5               Do you want to continue? [YES] <Return>T  W               %PCSI-I-NOREF, product DEC AXPVMS DECNET_OSI V7.1 is no longer referenced T               -PCSI-I-NODEP, by another product as a software dependency requirementN               -PCSI-I-REMLP, you can remove product DEC AXPVMS DECNET_OSI V7.1B               Do you want to take this action? [NO] no <Return>  28               Do you want to continue? [YES] <Return>  3  T               %PCSI-I-NOREF, product DEC AXPVMS WANDD V1.0-B is no longer referencedT               -PCSI-I-NODEP, by another product as a software dependency requirementK               -PCSI-I-REMLP, you can remove product DEC AXPVMS WANDD V1.0-B @               Do you want to take this action? [NO] yes <Return>  5               The following products will be removed: H                   DEC AXPVMS WANDD V1.0-B                Layered ProductH                   DEC AXPVMS X25 V1.0-B                  Layered Product  [               Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%   7               The following products have been removed:iH                   DEC AXPVMS WANDD V1.0-B                Layered ProductH                   DEC AXPVMS X25 V1.0-B                  Layered Product               $0  ;               Notes on Example Prompt and Response Sequence   G               1  This command invokes the de-installation procedure for                   X.25.  H               2  Whenever all the dependencies on a product are removed,C                  that product can also be removed. In this example,rC                  de-installing X.25 removes all the dependencies on F                  DECnet-Plus for OpenVMS. You are, therefore, promptedG                  whether to remove the specified version of DECnet-Plus F                  in addition to X.25. To remove the specified product,>                  type YES; otherwise, type NO or press Return.  I                                     Installing X.25 for OpenVMS Alpha 7-7a d  t      )         Installing X.25 for OpenVMS AlphaT8         7.4 X.25 Installation and De-Installation Sample    H               3  To continue with the de-installation, type YES or pressF                  Return in response to this question. To terminate theI                  de-installation, type NO. Type NO only if you decide notS+                  to de-install the product.                                                                                   -         7-8 Installing X.25 for OpenVMS Alphap n  o                    I                                                                         8eI         _________________________________________________________________   I                            X.25 Post-Installation and Configuration Tasksm    I               This chapter describes the tasks to complete after X.25 hasi               been installed.            8.1 Configuring X.25  G               After X.25 has been installed, you need to configure your                system.s  A               You can use the DECnet-Plus configuration procedure_B               (net$configure.com) to first configure X.25 and thenF               configure DECnet over X.25. You can use either the BASIC/               or ADVANCED configuration option.   B               The following steps summarize what you need to do to-               complete an X.25 configuration:   3               1. Start the net$configure procedure.   F               2. Select "Perform the entire configuration." This stepsG                  you through to the X.25 series of configuration steps.   A               3. Select the defaults for each of the questions by A                  pressing Return after each one. When you see theaD                  question, "Do you want to configure X.25?" type YES"                  and press Return.  F               4. Answer YES to the next several questions, then selectD                  either the X25 BASIC or X25 ADVANCED configuration.  D               5. Provide responses to the questions when prompted byE                  the configurator. This sets up your system using thetI                  information given to you by your X.25 provider (the X.25 /                  Access service you are using).m  F               6. When you have entered all the information required toH                  configure your X.25 system, the X.25 configurator savesH                  all your information in a CONFIG.DAT file (for example,3                  sys$startup:x25$basic_config.dat).M  I                        X.25 Post-Installation and Configuration Tasks 8-1_ _  _      6         X.25 Post-Installation and Configuration Tasks         8.1 Configuring X.25    D               7. After the X.25 configurator saves your information,C                  that portion of the configuration is complete. TheyD                  X.25 configurator then returns to the net$configure7                  procedure, which is still in progress.   D               8. Enter the appropriate data link and routing circuitI                  names to use as they are requested (you can also use thed.                  defaults by pressing Return).  G               9. When the net$configure procedure asks, "Do you want totH                  configure DECnet over X.25?" type YES and press Return.  A              10. Select the type of X.25 circuit you want to use.   G              11. Enter the routing circuit name to use (or press Return "                  for the default).  A              12. Enter the template name (or press Return for the                   default).  F              13. The net$configure procedure then continues with otherB                  configuration questions for different transports.  H               When you have provided answers to all of the configuration<               questions, the procedure displays a summary ofI               configuration. It then redisplays the Configuration Options H               menu. At this point, the procedure is complete and you can               exit.   G               For a sample X.25 and DECnet over X.25 configuration, see                Section 8.5.  G               Full details on how to configure the product are provided E               in the X.25 for OpenVMS Alpha Configuration Guide. This H               guide is available in a separate kit. Refer to the SPD forH               appropriate part numbers to use for ordering the X.25 kit.           8.2 Restart DECnet-Plus5  C               You must restart DECnet-Plus before starting the X.25 F               software. To restart DECnet, enter the following command               on each node:   (               $ @sys$startup:net$startup  :         8-2 X.25 Post-Installation and Configuration Tasks           I                            X.25 Post-Installation and Configuration Tasks2I                                                  8.3 Rebooting the Systeme              8.3 Rebooting the System  E               After you have completed the required post-installation '               tasks, reboot the system.g  D               X.25 software starts automatically when you reboot the.               system on which it is installed.  F               To start the X.25 software manually, enter the following.               command from the SYSTEM account:  ,               $ @sys$startup:x25$startup.com           8.4 De-installing X.25  =               To de-install X.25, type the following command:o  "               $ product remove x25  E               Invoking this command automatically removes the product G               files. Complete shutdown of X.25 does not occur until the F               system is next rebooted. An annotated example of the de-F               installation prompt and response sequence is provided in               Section 7.4.  B               To invoke the shutdown procedure manually, enter the8               following command from the SYSTEM account:  -               $ @sys$startup:x25$shutdown.coms  F                 ________________________ Note ________________________  C                 You do not have to remove X.25 before re-installing D                 the same or a different version. If a version of theE                 product exists on the system where you are attemptingSF                 to install the same or another version of the product,C                 the Software Integrator warns you that a version ofoE                 the product is already installed. You can then chooseS:                 whether to continue with the installation.  F                 ______________________________________________________        I                        X.25 Post-Installation and Configuration Tasks 8-3w    t      6         X.25 Post-Installation and Configuration Tasks%         8.5 Sample X.25 Configuration     %         8.5 Sample X.25 Configurationo  I               This section provides a sample configuration that you mightnF               see when you use net$configure.com to configure X.25 and.               then configure DECnet over X.25.                 $o'               $ @net$configure advancede`               Copyright (c) Digital Equipment Corporation 1993, 1994, 1995. All rights reserved.  V                       DECnet-Plus for OpenVMS ADVANCED network configuration procedure  W                    This procedure will help you create or modify the management scripts W                    needed to operate DECnet on this machine. You may receive help about H                    most questions by answering with a question mark '?'.  Z                    You have chosen the ADVANCED configuration option.  This option enables[                    you to do some specific tailoring of your system's network configuration [                    by answering some specific questions.  If you do not want to do specificlZ                    tailoring of your system's network  configuration but instead  want  toZ                    quickly  configure your  system using most  of the default answers, you[                    should invoke NET$CONFIGURE.COM with the BASIC configuration option, ie:m?                                @SYS$MANAGER:NET$CONFIGURE BASICs  L               * Do you want to continue?                             [YES] :R                    Checksum file updated last by SYSTEM on 17-JAN-1995 12:01:48.66  ?               %NET$CONFIGURE-I-VERCHECKSUM, verifying checksumsn  ,                       Configuration Options:  1                       [0]     Exit this procedure.  =                       [1]     Perform an entire configuratione=                       [2]     Change node name/namespace name ?                       [3]     Configure Devices on this machine 2                       [4]     Configure TransportsD                       [5]     Configure Timezone Differential Factor8                       [6]     Configure Event Dispatcher<                       [7]     Configure Application database;                       [8]     Configure MOP Client databaset5                       [9]     Configure Cluster Aliaso>                       [10]    Replace MOP Client configuration7                       [11]    Condigure satellite nodese@                       [12]    Configure cluster script locations  :         8-4 X.25 Post-Installation and Configuration Tasks c  n      I                            X.25 Post-Installation and Configuration TasksoH                                            8.5 Sample X.25 Configuration    L               * Which configuration option to perform?                 [1] :L               * Enter the directory services to use on the system [DECDNS] :Y               * Enter the full name for directory service DECDNS [bb_ns:.area39.arv011] :pL               * What is the synonym name for this node?           [ARV011] :L               * Enter PhaseIV Address                              [39.11] :L               * Enter Phase IV Prefix                           [47:0027:] :L               * Autoconfigure network addresses?                     [YES] :L               * DNA Address Format?                                 [TRUE] :L               * Do you want to use segregated mode routing?           [NO] :L               * Do you want to configure X.25?                       [YES] :  3                 Configuring WANDD... ['?' for HELP]   O               %WANDD$CONFIGURE-I-WANDDNOTCONFIG, WANDD has not been configured. $               Configure WANDD? [YES]8               Are you satisfied with your answers? [YES]F               %NET-I-LOADED, executive image X25$KERNEL_RTL.EXE loaded?               %NET-I-LOADED, executive image X25$MEL.EXE loaded >               %NET-I-LOADED, executive image X25$L2.EXE loadedK               %RUN-S-PROC_ID, identification of created process is 00000125l>               %NET-I-LOADED, executive image X25$L1.EXE loaded  @               %SYSMAN-I-OUTPUT, command execution on node ARV011L               %IOGEN-I-PREFIX, searching for ICBM with prefix DECW$GRAPHICS_M               %IOGEN-W-NOICBM, failed to find ICBM with prefix DECW$GRAPHICS_tB               %IOGEN-I-PREFIX, searching for ICBM with prefix SYS$B               %IOGEN-I-PREFIX, searching for ICBM with prefix X25$L               %IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKA08               %IOGEN-I-CONFIGURED, configured device ZEA8               %IOGEN-I-CONFIGURED, configured device ZEB  :                 Available Synchronous Communication Ports:  -                       1.  ZEA0   -  DNSES-0-0 -                       2.  ZEA1   -  DNSES-0-1 -                       3.  ZEB0   -  DNSES-1-0X-                       4.  ZEB1   -  DNSES-1-1   =               Use X25 BASIC or ADVANCED configurator? [BASIC].F               The screen will be cleared.  Press RETURN to continue...  F                                     X.25 for OpenVMS Alpha(TM) Systems8                                             Introduction    I                        X.25 Post-Installation and Configuration Tasks 8-5            6         X.25 Post-Installation and Configuration Tasks%         8.5 Sample X.25 Configuration     P               This program allows you to configure an X.25 for OpenVMS Alpha(TM)N               system. The program is divided into sections. Each section takesG               you through a series of configuration data entry screens.O7               The following sections can be configured:hD               1. X.25 Connection                     4. X.29 SupportA               2. PVCs                                5. X.25 Maild,               3. X.25 Incoming Call Security  T                     When you have provided all the information required, the program@                                         Press RETURN to continue  R                     Copyright (c)1993, 1994, 1995 by Digital Equipment Corporation  G                                      X.25 for OpenVMS Alpha(TM) Systemsu  G                                       Create a new configuration scriptDJ                                    Modify an existing configuration script  G                                      X.25 for OpenVMS Alpha(TM) Systemse>                                            Basic Configuration=                                            Configuration Type   M               You can configure your OpenVMS Alpha system to connect to PSDNseG               directly, or through a connector node, such as a gateway.   G               Select the type of X.25 connection you want to configure:n  )               X.25 over Wide Area Networka*               X.25 over Local Area Network               X.25 Clientv  H                                       X.25 for OpenVMS Alpha(TM) SystemsD                                          X.25 Over Wide Area Network  C               Enter the Network profile name and DTE details below.                  Profile Name:l                 X.25 Address:7  5               Select a synchronous line for this DTE:                       DNSES-0-0                    DNSES-0-1                    DNSES-1-0                    DNSES-1-1  :         8-6 X.25 Post-Installation and Configuration Tasks e  5      I                            X.25 Post-Installation and Configuration Tasks H                                            8.5 Sample X.25 Configuration    R                    Logical channels used for Switched Virtual Circuits and PermaneF                    Virtual Circuits are assigned in the following way:  F                                 <------------------------------------>P                         PVCs      Incoming           Two-way            OutgoingT                    |------------|----------|-------------------------|-------------|W                    1                SVCs               SVCs               SVCs     4095oT                    <------------>          <--------------------------------------->  T                   If you intend to configure PVCs, select SVC Logical Channel RangesH                   that leave enough channels free for the required PVCs.  A                   Incoming Logical Channel Range(s):  {[1..4095]} A                   Outgoing Logical Channel Range(s):  {[1..4095]}   3                                                PVCsy  N                   A PVC (Permanent Virtual Circuit) is a permanent associationL                   between two specific DTEs. Two DTEs connected by a PVC canO                   communicate without the need for call clearing or call setup.t  L                   Your subscription options will provide details of any PVCs!                   you can set up.   <                   Do you wish to set up any PVCs ?  No   Yes  ?                                          Incoming Call Security   N                   This section allows you to configure Incoming Call Security.R                   You can choose to allow all incoming calls, to allow no incomingN                   calls, or to restrict incoming access to particular systems.P                   If you choose to restrict incoming access you will be promptedM                   to enter the remote address prefixes (RAPs) of systems that5F                   will be permitted to make calls to the local system.L                   Separate entry screens are presented for RAPs with Remote-*                   Charge, and  All access.  !                   Do you want to:h=                                     Allow All Incoming Access <                                     Allow No Incoming Access<                                     Restrict Incoming Access  =                                     Allow All Incoming Access.<                                     Allow No Incoming Access<                                     Restrict Incoming Access  <                                     Allow No Incoming Access<                                     Restrict Incoming Access  I                        X.25 Post-Installation and Configuration Tasks 8-7_ _  _      6         X.25 Post-Installation and Configuration Tasks%         8.5 Sample X.25 Configurationt    9                                     Access: REMOTE CHARGEs  M                    Enter the Remote Address Prefixes (RAPs) of remote systems S                    associated with the specified network that are permitted to calloM                    the local system only if the remote DTE pays for the call.t  ?                    Do you want to add another RAP ?   Yes    Noo  ?                    Do you want to add another RAP ?   Yes    No   ?                    Do you want to add another RAP ?   Yes    Nog  ?                    Do you want to add another RAP ?   Yes    Not  L                    This section allows you to configure the local system for                    X.29 access.o  W                    X.29 access will allow users to access the local system remotely via T                    an X.25 network and to access remote systems via the X.25 network)                    from the local system.s  7                    Do you want X.29 support?   Yes   No   S                    Your system will be configured for X.29 access, which will allow P                    users to access the local system remotely via an X.25 networkM                    and to access remote systems via the X.25 network from theo                     local system.  P                    You can specify a Network User Identity (NUI) to identify the>                    party to charge for the outgoing X.29 call.  -                    X29 Network User Identity:   9                                                 X.25 Mail   Q                    X.25 mail is an addition to VMS mail which enables this systemiA                    to send and receive mail messages over a PSDN.   >                    Do you want to use X.25 MAIL ?     Yes   No  :                                                 NCL Script  R                     You have now entered all the information required to configureT                     your X.25 for OpenVMS Alpha system. If you do not want to modifyP                     your answers, an NCL script will be created and your answersD                     Do you want to modify your answers ?   No    Yes  7                     Please read the following messages:   K               The NCL script, sys$startup:x25$config.ncl, has been created.a  :         8-8 X.25 Post-Installation and Configuration Tasks t  s      I                            X.25 Post-Installation and Configuration TaskssH                                            8.5 Sample X.25 Configuration    Z               The NCL script, sys$startup:x25$enable_decnet_clients.ncl, has been created.                 Working ...o  ^               The current X25 configuration has been saved in sys$startup:x25$basic_config.dat  D                                   X.25 for OpenVMS Alpha(TM) Systems  D                                    Create a new configuration scriptG                                 Modify an existing configuration scriptr  F                                 ******* Configuration Complete *******  Z                       You must grant the rights identifier `x25_outgoing_all' to all usersL                       and processes that are allowed to make outgoing calls.  V               %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please waitN               * Enable FDDI large packet support?                     [NO] : yL               * Data Link name to use for EWA0 (TULIP)?         [CSMACD-0] :L               * Routing Circuit Name for Data Link 'CSMACD-0'?  [CSMACD-0] :L               * Data Link name to use for EWB0 (TULIP)?         [CSMACD-1] :L               * Routing Circuit Name for Data Link 'CSMACD-1'?  [CSMACD-1] :L               * Data Link name to use for FRA0 (DEFEA)?           [FDDI-0] :L               * Routing Circuit Name for Data Link 'FDDI-0'?      [FDDI-0] :L               * Data Link protocol for ZEA0 (DNSES)?                [HDLC] :L               * Data Link name to use for ZEA0 (DNSES)?           [HDLC-0] :L               * Routing Circuit Name for Data Link 'HDLC-0'?      [HDLC-0] :Q               * Data Link protocol for ZE-0-1 (DNSES)?              [HDLC] : none Q               * Data Link protocol for ZEB0 (DNSES)?                [HDLC] : nonenQ               * Data Link protocol for ZE-1-1 (DNSES)?              [HDLC] : noneoN               * Do you want to configure DECnet over X.25?            [NO] : y  )                   Types of X.25 circuits:   2                   [1] - X.25 Dynamic Assigned (DA)1                   [2] - X.25 Static Incoming (IN)l2                   [3] - X.25 Static Outgoing (OUT),                   [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 PSI routing circuit for DECnet?    [NO] :  I               Determining DTSS timezone rules from OpenVMS information...o  I                        X.25 Post-Installation and Configuration Tasks 8-9            6         X.25 Post-Installation and Configuration Tasks%         8.5 Sample X.25 Configuration     L               * Configure the NSP Transport?                         [YES] :L               * Configure the OSI Transport?                         [YES] :P               * Do you want to replace the existing NSP transport script? [NO] :P               * Do you want to replace the existing OSI transport script? [NO] :Q               %NET$CONFIGURE-I-EVDFND, Event Dispatcher NCL script already existshL               * Replace Event Dispatcher NCL script file?             [NO] :T               %NET$CONFIGURE-I-APPLICATIONFND, application NCL script already existsL               * Replace application script file?                      [NO] :Q               %NET$CONFIGURE-I-MOPCLIENTFND, MOP client NCL script already existsoL               * Replace MOP Client script file?                       [NO] :  <                                     Summary of Configuration                   Node Information:<                       Directory Services Chosen:      DECDNS<                       Primary Directory Service:      DECDNSB                       DECdns Full name:       bb_ns:.area39.arv0114                       Node Synonym:           ARV0113                       Phase IV Address:       39.11y6                       Phase IV Prefix:        47:0027:E                       Autoconfiguration of Network Addresses: Enabled   "                Device Information:+                       Device: EWA0 (TULIP):h6                               Data Link name: CSMACD-0>                               Routing Circuit Name:   CSMACD-0  +                       Device: EWB0 (TULIP):s6                               Data Link name: CSMACD-1>                               Routing Circuit Name:   CSMACD-1  +                       Device: FRA0 (DEFEA):o4                               Data Link name: FDDI-0<                               Routing Circuit Name:   FDDI-0  +                       Device: ZEA0 (DNSES): 4                               Data Link name: HDLC-0<                               Routing Circuit Name:   HDLC-0  (                       Device: X25-PVC-0:?                               Routing Circuit Name:   X25-PVC-0E        ;         8-10 X.25 Post-Installation and Configuration Tasks            I                            X.25 Post-Installation and Configuration Tasks H                                            8.5 Sample X.25 Configuration    $               Transport Information:H                       NSP Transport:                          ConfiguredD                         Maximum number of logical links:         200C                         Maximum Transmit and Receive Window:     20nE                         Maximum Receive Buffers:                 4000n  H                       OSI Transport:                          ConfiguredD                         Maximum number of logical links:         200C                         Maximum Transmit and Receive Window:     20 E                         Maximum Receive Buffers:                 4000   3                       Congestion Avoidance Disabled   .                Event Dispatcher Configuration:2                       Sinks:            local_sink4                       Outbound Streams: local_stream/                       Phase IV Relay:   Enablede  F         * Do you want to generate NCL configuration scripts?   [YES] :c         %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE g         %NET$CONFIGURE-I-NOTREPLACED, SYS$SYSROOT:[SYSMGR]NET$APPLICATION_STARTUP.NCL; was not replacedma         %NET$CONFIGURE-I-NOTREPLACED, SYS$SYSROOT:[SYSMGR]NET$EVENT_STARTUP.NCL; was not replaced[f         %NET$CONFIGURE-I-NOTREPLACED, SYS$SYSROOT:[SYSMGR]NET$MOP_CLIENT_STARTUP.NCL; was not replacedF         * Do you want to start the network?                    [YES] :T         Copyright (c) Digital Equipment Corporation 1993, 1995. All rights reserved.\         %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-ALL  W         sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.   1         Your default namespace nickname is BB_NS.   R         Your default namespace NSCTS is 08-00-2B-17-F4-BC-F5-B2-38-FB-C4-7B-96-00.D         %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries                 Node 02               at 1995-01-23-15:32:52.583-05:00Iinf  ]               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to bb_ns:.area39.arv011N  $               Node 0 Session Control2               at 1995-01-23-15:32:52.906-05:00Iinf  $               Node 0 Session Control2               at 1995-01-23-15:32:52.918-05:00Iinf  $               Node 0 Session Control2               at 1995-01-23-15:32:52.926-05:00Iinf  I                       X.25 Post-Installation and Configuration Tasks 8-11_    n      6         X.25 Post-Installation and Configuration Tasks%         8.5 Sample X.25 Configurationo    $               Node 0 Session Control2               at 1995-01-23-15:32:54.427-05:00Iinf  $               Node 0 Session Control2               at 1995-01-23-15:32:54.545-05:00Iinf                 Characteristics$  :                   Maintain Backward Soft Links      = True  '                                    SHOWE6                               DIRECTORY  BB_NS:.area39=                                      AT  23-JAN-1995:15:32:55 Y                                 DNS$CTS = 1993-02-06-16:50:34.908990700/08-00-2b-17-f4-bc,  '               Directory Service: DECdnsv  5               Node name:         BB_NS:.AREA39.ARV011 '               Phase IV synonym:  ARV011   9               Address tower protocol and selector values: 5                 Session:   DNA_SessionControlV3 (SC3)1                             00 133                 Transport: DNA_OSItransportV1 (TP4)                              DE C00                 Routing:   DNA_OSInetwork (CLNS)E                            47:0027:00-27:AA-00-04-00-0B-9C:21 (39.11)   5                 Session:   DNA_SessionControlV3 (SC3)                              00 13(                 Transport: DNA_NSP (NSP).                            (no selector value)0                 Routing:   DNA_OSInetwork (CLNS)E                            47:0027:00-27:AA-00-04-00-0B-9C:20 (39.11)e  5                 Session:   DNA_SessionControlV3 (SC3)d                             00 133                 Transport: DNA_OSItransportV1 (TP4)o                             DE C00                 Routing:   DNA_OSInetwork (CLNS)=                            47:0027:00-5E:08-00-2B-E4-54-1C:21o  5                 Session:   DNA_SessionControlV3 (SC3)5                             00 13(                 Transport: DNA_NSP (NSP).                            (no selector value)0                 Routing:   DNA_OSInetwork (CLNS)=                            47:0027:00-5E:08-00-2B-E4-54-1C:20o  ;         8-12 X.25 Post-Installation and Configuration Tasks            I                            X.25 Post-Installation and Configuration Tasks H                                            8.5 Sample X.25 Configuration    $               Synonym softlink name:/                   BB_NS:.DNA_NodeSynonym.ARV011   G               Reverse address mapping (backtranslation) softlink names: K                   BB_NS:.DNA_BackTranslation.%X470027.%X0027.%XAA0004000B9CCK                   BB_NS:.DNA_BackTranslation.%X470027.%X005E.%X08002BE4541Ce  -               Number of nodes reported on:  1r  \               %NET$CONFIGURE-I-NODEISREG, node is already registered in the DECdns directory               servicee                 Node 02               at 1995-01-23-15:32:56.524-05:00Iinf  ]               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to bb_ns:.area39.arv011e  K               Node 0 Session Control Tower Maintenance BB_NS:.AREA39.ARV011 2               at 1995-01-23-15:32:56.699-05:00Iinf  M               %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node   ?               Node 0 Session Control Backtranslation Softlink *D2               at 1995-01-23-15:32:56.823-05:00Iinf  ?               Node 0 Session Control Backtranslation Softlink *S2               at 1995-01-23-15:32:56.823-05:00Iinf  W               %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for nodeg_               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed   ,                       Configuration Options:  1                       [0]     Exit this procedurer  =                       [1]     Perform an entire configuration =                       [2]     Change node name/namespace name ?                       [3]     Configure Devices on this machine 2                       [4]     Configure TransportsD                       [5]     Configure Timezone Differential Factor8                       [6]     Configure Event Dispatcher<                       [7]     Configure Application database;                       [8]     Configure MOP Client databasen5                       [9]     Configure Cluster Alias >                       [10]    Replace MOP Client configuration7                       [11]    Configure satellite nodesn@                       [12]    Configure cluster script locations  L               * Which configuration option to perform?                 [0] :  I                       X.25 Post-Installation and Configuration Tasks 8-13i                         I                                                                   Part IVmI         _________________________________________________________________   I                           Installing OSI Applications for OpenVMS Systems             I               Part IV describes the steps necessary to plan, install, and F               configure the OSI applications for OpenVMS Alpha and VAX:               systems. It includes the following chapters:  :               o  Chapter 9 - Planning for the Installation  G               o  Chapter 10 - Preparing to Install the OSI Applicationsc  =               o  Chapter 11 - Installing the OSI Applicationsu  >               o  Chapter 12 - Configuring the OSI Applications  F                 ________________________ Note ________________________  C                 DECnet-Plus must be installed and configured before 0                 installing the OSI applications.  F                 ______________________________________________________                         I                                                                         9 I         _________________________________________________________________   I                                             Planning for the Installation               9.1 Product Descriptions                 FTAM  C               FTAM is an Open Systems Interconnection (OSI) productt@               that implements the OSI File Transfer, Access, andI               Management standard ISO 8571 developed by the InternationalcI               Organization for Standards (ISO). Using FTAM, you can copy,kH               append, delete, rename, and inspect the file attributes of1               local files, remote files, or both.                  Virtual Terminal  F               DECnet-Plus Virtual Terminal is DIGITAL's implementationI               of the OSI Virtual Terminal standard. Virtual Terminal (VT)iI               enables applications and systems supporting different types I               of terminals to interoperate with each other. Using VT, youtF               can use your terminal to access any other system runningH               VT, regardless of the type of system. You can also use theA               VT gateways for access to and from non-OSI systems.n                 OSAK  @               Open System Application Kernel (OSAK) is DIGITAL'sE               implementation of the OSI upper layers. It provides OSIXC               Session, Presentation and Application services. These A               services are used by OSI applications such as FTAM, B               VT, X.400, and X.500. In addition, by using the OSAKI               programming interfaces which provide access to OSI Session,YD               Presentation and Application layers, users can developH               applications that layer on DIGITAL's implementation of the               OSI stack.        I                                         Planning for the Installation 9-1s e         %         Planning for the Installationk         9.2 Required Hardwarey             9.2 Required Hardwareh  F               The OSI applications installation procedure requires the!               following hardware:   =               o  A CD reader (if installing an Alpha version)l  I               o  A CD reader, magnetic tape drive, or TK50 tape drive (if *                  installing a VAX version)                 o  A terminala  D                  You can use either a hard copy or video terminal toE                  communicate with the operating system and respond tol9                  prompts from the installation procedure.            9.3 Required Softwarem  G               You must use the POLYCENTER Software Installation utilityrD               to install the OSI applications installation kit. ThisA               utility is provided as part of the operating systemr               software.s  I               To install FTAM and VT, you must first install DECnet-Plus,t$               and then install OSAK.  F               To run the VT/Telnet gateways, you must have the DIGITALC               TCP/IP Services for OpenVMS installed on your system.            9.4 Kit Location  F               To obtain the directory location of the OSI applicationsB               kit on the CD, refer to the OpenVMS Layered Products?               Compact Disc User's Guide that accompanies the CDdI               distribution kit, or before starting installation, complete."               the following steps:  F               1. To determine whether the CD drive is already mounted,-                  enter the following command:c  3                  $ show device device-name <Return>   B               2. If it is not mounted, enter the appropriate MOUNT)                  command to mount the CD.g  E               3. To obtain the save-set name, use a DIRECTORY commandtF                  specifying the device name from the previous command.                  For example:e  )         9-2 Planning for the Installationa t  p      I                                             Planning for the Installation0I                                                          9.4 Kit Locationt    9                  $ directory DKA400:[kits]*.pcsi <Return>e  @               If you are installing from a TK50 or magnetic tapeD               drive, refer to the appropriate user guide for further               instructions.   $         9.5 Time Required to Install  ?               The time required to install the OSI applications-F               depends on the media type, the CPU type, and your systemE               configuration. In general, the procedure should require #               less than 15 minutes.t                                                                  I                                         Planning for the Installation 9-3                          I                                                                        10aI         _________________________________________________________________   I                                 Preparing to Install the OSI Applications     A               This chapter details the tasks you need to completem>               or consider before attempting to install the OSI               applications.   ,         10.1 Inspecting the Distribution Kit  E               The software bill of materials (BOM) included with your G               distribution kit shows the components of the kit. Compare H               the items you received against the BOM. Report any damagedI               or missing components to DIGITAL before continuing with ther               installation.e  /         10.2 Logging In to a Privileged Accountz  G               To install the OSI applications, you must be logged in toI;               an account that has the following privileges:                  For FTAM and VT:                 o  SETPRV                  For OSAK:                  o  CMKRNLr                 o  SETPRV   ;               Determine your account privileges as follows:n  C               1. Determine the default privileges of the installingr;                  account. Log in and enter the DCL command:   3                  $ show process/privileges <Return>c  F                  If the account lacks the SETPRV privilege, proceed to                  Step 2.  I                            Preparing to Install the OSI Applications 10-1            1         Preparing to Install the OSI Applicationsp/         10.2 Logging In to a Privileged Accountt    ,               2. Do either of the following:  H                  o  Ask your system manager to use the Authorize utilityF                     to modify the default privileges of the account to0                     include the SETPRV privilege  B                  o  Run the Authorize utility and make the changesG                     yourself, if your account has the SYSPRV privilege:   5                     $ set default sys$system <Return> ,                     $ run authorize <Return>I                     UAF> modify account-name/privileges=(SETPRV) <Return> &                     UAF> exit <Return>  G               3. To activate the change in privileges, log out and thenu                  log in again.  /         10.3 Accessing the Online Release Notes:  E               The release notes for the OSI applications are provided B               as part of the DECnet-Plus release notes. You shouldF               review these release notes prior to installation becauseG               they describe new features and differences among multiple I               versions, as well as changes to the installation procedure.i  =               To access the release notes, issue the command:   /               $ product extract release_notes -iH                   decnet_osi/source=DKA400:[kits]/file=filename <Return>  C               Note that in this example, the directory on the CD in E               which the installation kit is located is referred to as-F               DKA400:[kits]. You should substitute this directory nameI               with the actual directory location of your DECnet-Plus kit.   D               The product selected is displayed and you are prompted6               whether to continue with the extraction.  F               To extract the release notes, type YES and press Return.H               The release notes are written to the specified file, which'               you can display or print.   A               To cancel the extraction, type NO and press Return.a  F                 ________________________ Note ________________________  F                 After DECnet-Plus is installed, the release notes file                 is located in:  6         10-2 Preparing to Install the OSI Applications 2         I                                 Preparing to Install the OSI Applications I                                   10.3 Accessing the Online Release Notes     :                    SYS$HELP:DECNET_PLUS-V#_#.RELEASE_NOTES  D                 #_# is the version number of the DECnet-Plus version#                 you are installing.S  F                 ______________________________________________________            10.4 Memory Requirements  D               To install and run the OSI applications, you must haveH               sufficient free global memory. Table 10-1 shows the global"               memory requirements:  C               Table 10-1 Required Global Pages, Global Pagelets andNI               ___________Sections________________________________________n  I               Software_Alpha_______________VAX___________________________O  <               FTAM     5068 global         4402 global pages                        pagelets   =                        24 global sections  19 global sections   ;               VT       1136 global         422 global pagesA                        pageletsa  =                        8 global sections   14 global sections_  <               OSAK     3296 global         1344 global pages                        pagelets   I               _________6_global_sections___13_global_sections____________-  F               You must first find out your available system resources,F               and then use the AUTOGEN utility if you need to increaseC               the global pages, global pagelets, or global sectionse4               system parameters. Do this as follows:  I               1. Use the WRITE command with the F$GETSYI lexical function:C                  to find the number of free global pages and global-A                  sections. The following example shows how to getlC                  this information at your terminal (the default for                   SYS$OUTPUT):a  H                  $ write sys$output f$getsyi("contig_gblpages") <Return>                  15848F                  $ write sys$output f$getsyi("free_gblsects") <Return>                  24   I                            Preparing to Install the OSI Applications 10-3l           1         Preparing to Install the OSI Applications           10.4 Memory Requirements    I               2. Compare the values displayed with those required for the "                  OSI applications.  E                  o  If the values displayed by the system are greater F                     than the values required for the OSI applications,B                     you do not need to change the system parameter                     settings.   H                  o  If one of the values is less than the value requiredF                     for OSI applications, you must increase the systemH                     parameter setting using the AUTOGEN utility. Proceed(                     to the next section.  <         10.4.1 Changing System Parameter Values with AUTOGEN  @               Use the AUTOGEN command procedure to change systemB               parameters. AUTOGEN automatically adjusts values forF               parameters that are associated with the values you reset               manually.n  I               For more information about using the AUTOGEN utility, refer >               to your OpenVMS system management documentation.           10.5 Process Quotas0  H               The POLYCENTER Software Installation utility requires thatH               the installation account has as a minimum the quotas shown               in Table 10-2.  I               Table_10-2_Process_Quotas_for_the_Installing_Account_______   I               Quota_____Value____________________________________________o                 ASTLM     24                 BIOLM     18                 BYTLM     32768:                 DIOLM     18                 ENQLM     200)  I               FILLM_____100______________________________________________   C               The number of available global sections on the systemtE               limits the number of simultaneous connect requests thatXD               the OSAK software can support. OSAK buffers store eachD               connect request in a global section until the intendedE               application has either accepted or rejected it, or does   6         10-4 Preparing to Install the OSI Applications o  i      I                                 Preparing to Install the OSI Applications0I                                                       10.5 Process Quotas2    E               not accept an inbound connection within a given period, D               in which case the OSAK software rejects the connectionC               on behalf of the application. The process running the E               OSAK software, OSAK$SERVER_V3, is started automaticallyIF               by the installation procedure. Therefore, the installingF               account requires the process quotas shown in Table 10-2,G               as does the SYSTEM account if you start OSAK$SERVER_V3 inT                SYSTARTUP_VMS.COM.  G               Table 10-3 summarizes the required process account quotass-               for the OSAK$SERVER_V3 process.-  I               Table_10-3_OSAK$SERVER_V3_Process_Account_Quotas___________n  I               Quota_______Value__________________________________________   >               ASTLM       2 units for each global section + 10  5               ENQLM       1 unit for each OSI processT  I               TQELM_______2_units_for_each_global_section_+_10___________   @               OSAK$SERVER_V3 Process Account Calculation Example  F               The following calculations determine the correct process:               account quota values for 20 global sections:  I               o  For ASTLM: 20 global sections multiplied by 2 units + 10                   = 50   I               o  For TQELM: 20 global sections multiplied by 2 units + 10e                  = 50   F               Table 10-4 summarizes the minimum process account quotas@               required for processes that use the OSAK software.  C               Table 10-4 Account Quotas for Processes that use OSAK I               ___________Software________________________________________i  I               Quota_______Value__________________________________________                  ASTLM       10                 ENQLM       2   I               TQELM_______10_____________________________________________   F               Users of the OSI applications also need a minimum TMPMBX$               and NETMBX privileges.  I                            Preparing to Install the OSI Applications 10-5_ _  _      1         Preparing to Install the OSI Applications          10.5 Process QuotasO    D               Use the OpenVMS Authorize utility to verify and changeI               process quotas and user privileges for the installation and H               user accounts in the user authorization file (SYSUAF.DAT).G               (Some sites may restrict the use of the OpenVMS Authorize 4               utility to certain accounts or users.)  D               After you have changed the quotas for the installationE               account, log out of the installation account and log ino6               again for the new quotas to take effect.  E               For more information on modifying account quotas, refertH               to the description of the Authorize utility in the OpenVMS5               system management documentation subkit._  #         10.6 Determining Disk Space_  A               Table 10-5 shows the approximate minimum disk space B               required to install the individual OSI applications.                                                      6         10-6 Preparing to Install the OSI Applications l  o      I                                 Preparing to Install the OSI ApplicationsTI                                               10.6 Determining Disk Spacep    I               Table_10-5_Minimum_Disk_Space_Requirements_________________S  I               Software________Alpha___________VAX________________________r  ;               FTAM            28,000 blocks   12,000 blockse  :               VT              4,000 blocks    2,000 blocks  :               OSAK            6,900 blocks    6,000 blocks  I               TOTAL___________38,900_blocks___20,000_blocks______________a  H               To determine the number of free disk blocks on the currentI               system disk, enter the following command at the DCL prompt:y  2               $ show device sys$sysdevice <Return>  H               If necessary, create enough free disk space to accommodate7               the installation of the OSI applications.h  A               Chapter 7 describes options the POLYCENTER Software E               Installation utility provides, if there is insufficient G               disk space to complete the OSI applications installation.l           10.7 Notifying Users  I               You may want to notify the users on the system that you arevH               installing the OSI applications. Log in to an account that"               has OPER privileges.                 The command is:   M               $ reply/all/bell "Now installing the OSI applications" <Return>                         I                            Preparing to Install the OSI Applications 10-7a a                       I                                                                        11 I         _________________________________________________________________n  I                                           Installing the OSI Applicationse    D               This chapter describes how to install the optional OSI3               applications. These applications are:                  o  FTAMe  &               o  Virtual Terminal (VT)                 o  OSAKd  F               It also includes how to list the files installed on yourB               system during the OSI applications installation. See5               Section 11.11 for the list of commands.   H               You install these optional components using the POLYCENTERF               Software Installation utility. For information about howH               to run the this utility, refer to <REFERENCE>(DNPLUS_OVMS_)               INSTALL_BASIC), Appendix A.l           11.1 Prerequisite Stepsk  H               Install the OSI applications only after you have installedC               DECnet-Plus for OpenVMS, rebooted, and configured theo6               DECnet-Plus for OpenVMS base components.  ;         11.2 Register the OSI Applications Software License,  E               If you are installing prerequisite or optional softwaretD               along with OSI applications, review the PAK status andH               install the PAKs for any prerequisite or optional software6               before you install the OSI applications.  G               The DVNETEND PAK is required to install DECnet-Plus. ThisiG               PAK also allows you to install and run the base FTAM, VT, $               and OSAK applications.  D               To use the FTAM and VT gateways, you need the extended2               function license. The PAK names are:  $               o  For Alpha: DVNETEXT  I                                      Installing the OSI Applications 11-1     c      '         Installing the OSI Applications ;         11.2 Register the OSI Applications Software License     "               o  For VAX: DVNETRTG  >         11.3 Starting the Installation of the OSI Applications  C               You install the OSI applications using the POLYCENTER 2               Software Installation DCL interface.  H               For a description of all the features you can request whenG               starting an installation (such as purging files and using F               a product configuration file), refer to DCL help for the&               product install command.  H               To install the OSI applications, choose from the following               commands.                  For OSAK only:  :               $ product install osak /source=DKA400:[kits]                 For FTAM and VT:  =               $ product install ftam,vt /source=DKA400:[kits]                  For FTAM only:  :               $ product install ftam /source=DKA400:[kits]                 For VT only:  8               $ product install vt /source=DKA400:[kits]  H               If you do not use the /SOURCE qualifier, the default is to:               read the installation kit from PCSI$SOURCE:.  E               Note that in the above example, the directory on the CD H               in which the installation kit is located is referred to asH               DKA400:[kits]. You should replace this directory name withI               your actual directory location of the OSI applications kit.0  F               Details on determining the directory location of the OSI;               applications kit are provided in Section 9.4.n  ,         11.4 Installing the OSI Applications  B               To install the OSI applications, log into the SYSTEM6               account and perform the following steps:  I               1. If you have previously installed the OSI applications onIH                  your system, be sure to shut down any FTAM, VT, or OSAKI                  processes currently running by executing the appropriaten(                  shutdown procedures(s).  ,         11-2 Installing the OSI Applications           I                                           Installing the OSI ApplicationseI                                      11.4 Installing the OSI Applicationst    F                  You must shut down FTAM and VT first, before shutting                  down OSAK.   ,                  o  $ @sys$startup:osif$stop  *                  o  $ @sys$startup:vt_stop  ,                  o  $ @sys$startup:osak$stop  1               2. De-install the OSI applications.   I                  If you have previously installed the OSI applications onlI                  your system, then de-install the applications, using the (                  product remove command:  6                  $ product remove application <Return>  2                  application is FTAM, VT, or OSAK.  E                  Note that you must de-install FTAM and VT before de- !                  installing OSAK.   +               3. Mount the software CD-ROM.g  F                 ________________________ Note ________________________  B                 Refer to the OpenVMS Layered Products Compact DiscF                 User's Guide for instructions on mounting and removing                 a compact disc.e  F                 ______________________________________________________  H               4. Decide which products to install. You must install OSAKG                  before installing FTAM or VT. You can install FTAM and 2                  VT either together or separately.  I                  See Section 11.3 for the FTAM, VT, and OSAK installation                   commands.  7               5. To install FTAM and VT together, type:d  M                  $ product install ftam,vt/source=device:[directory] <Return>w  G                  device:[directory] is the location of the files on theh$                  distribution media.  F                 ________________________ Note ________________________  =                 The following code examples are from an Alpha C                 installation. A VAX installation varies slightly in <                 the PAK name and in disk space requirements.  F                 ______________________________________________________  I                                      Installing the OSI Applications 11-3            '         Installing the OSI Applications ,         11.4 Installing the OSI Applications      F               6. The POLYCENTER Software Installation utility displaysG                  the selected products and requests confirmation. Pressi9                  Return to continue, or enter NO to exit.   ;                  The following products have been selected:n%                  DEC AXPVMS FTAM V3.2_#                  DEC AXPVMS VT V2.1   8                  Do you want to continue? [YES] <Return>  F               7. The POLYCENTER Software Installation utility displaysE                  the pre-installation messages for FTAM including the G                  copyright notice, license notice, and OSAK notice, and .                  asks if you want to continue.  U                  *** DEC AXPVMS FTAM V3.2: DECnet-Plus for OpenVMS OSI File Transfer,s.                  Access, and Management (FTAM)  [                      Copyright (c) Digital Equipment Corporation 1995. All rights reserved._  \                      This product uses the PAKS: DVNETEND and the Gateway requires DVNETEXT.  W                      The DECnet-Plus OSAK software must be installed and started beforeh/                   continuing this installation. <                      Do you want to continue? [YES] <Return>  F               8. The POLYCENTER Software Installation utility displaysC                  the pre-installation messages for VT including the_C                  copyright notice, license notice, OSAK notice, andbB                  gateway notice, and asks if you want to continue.  Q                  *** DEC AXPVMS VT V2.1: DECnet-Plus for OpenVMS Virtual Terminal   [                      Copyright (c) Digital Equipment Corporation 1994. All rights reserved.s  ]                      VT requires the PAK DVNETEND, and the VT Gateways require DVNETEXT also.   \                      OSAK must be installed and started before continuing this installation.  <                      Do you want to continue? [YES] <Return>  \                      VT Gateways startup requires LAT and DEC TCP/IP Services started first.<                      Do you want to continue? [YES] <Return>  D               9. The POLYCENTER Software Installation utility entersH                  the execution phase, in which it installs the products,D                  executes the startup command files, and runs the VTI                  installation verification procedure (IVP). Note that the   ,         11-4 Installing the OSI Applications           I                                           Installing the OSI ApplicationslI                                      11.4 Installing the OSI Applicationsu    G                  FTAM IVP is not run during this installation, and must #                  be run separately.S  <                  %PCSIUI-I-DONEASK, execution phase starting:                  The following products will be installed:%                  DEC AXPVMS FTAM V3.2i#                  DEC AXPVMS VT V2.1 X                  %PCSI-I-VOLINFO, estimated space information for volume DISK$OVMSSYSTEMM                  -PCSI-I-VOLSPC, 31060 required; 484479 available; 453419 netpR                  Portion Done: 0%...10%...20%...30%...40%...70%...80%...90%...100%<                  The following products have been installed:%                  DEC AXPVMS FTAM V3.2d#                  DEC AXPVMS VT V2.1t=                  %PCSI-I-EXETSTSTART, start of test procedureeR                  %PCSI-I-EXETSTOK, end of test procedure; completed with no errors  F              10. The POLYCENTER Software Installation utility displaysB                  the post-installation messages for FTAM and listsA                  required system resources, configuration and IVP E                  tasks you must complete, release notes location, and $                  completion message.  U                  *** DEC AXPVMS FTAM V3.2: DECnet-Plus for OpenVMS OSI File Transfer, .                  Access, and Management (FTAM)  Q                      Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:e6                          @SYS$STARTUP:OSIF$STARTUP.COMM                      Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:03                          @SYS$STARTUP:OSIF$STOP.COM   X                      The following messages are informational and indicate the amount of,                  each resource used by FTAM.  K                      This product requires the following SYSGEN parameters: +                          GBLSECTIONS add 24_  K                      This product requires the following SYSGEN parameters:v*                          GBLPAGES add 5068  B                      After installing DECnet-Plus FTAM you must doQ                  "$ @SYS$STARTUP:OSIF$CONFIGURE.COM" to setup necessary accounts.o  M                      The DECnet-Plus FTAM IVP may be run at any time by doinga+                  "$ @SYS$TEST:OSIF$IVP.COM"   R                      Release notes are available in SYS$HELP:DECNET*.RELEASE_NOTES  H                      DECnet-Plus for OpenVMS FTAM Installation Completed  I                                      Installing the OSI Applications 11-5     e      '         Installing the OSI Applications ,         11.4 Installing the OSI Applications    F              11. The POLYCENTER Software Installation utility displaysD                  the VT post-installation messages and lists release8                  notes location, and completion message.  Q                  *** DEC AXPVMS VT V2.1: DECnet-Plus for OpenVMS Virtual Terminal   Q                      Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:E2                          @SYS$STARTUP:VT_START.COMM                      Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: 1                          @SYS$MANAGER:VT_STOP.COM   Z                      Previous VT_SYSTART.COM changes are in SYS$STARTUP:VT_SYSTART.COM_OLD  R                      Release notes are available in SYS$HELP:DECNET*.RELEASE_NOTES  T                      DECnet-Plus for OpenVMS Virtual Terminal Installation Completed  ;         11.5 Starting Up and Shutting Down OSI Applications_  A               The installation procedure for each OSI applicationE;               executes the startup procedure automatically.t  F               To enable automatic restart of the applications once youI               have installed them on your system, edit the system startupsH               file (sys$manager:systartup_vms.com) and add the followingI               command lines to the file, beginning with the OSAK command:   G               $ @sys$startup:osak$start.com ! OSAK startup command fileuI               $ @sys$startup:osif$startup.com ! FTAM startup command fileAC               $ @sys$startup:vt_start.com ! VT startup command fileS  I               See Section 11.4, Step 1, for instructions on shutting down_#               the OSI applications._  9         11.6 The OSAK Installation Verification ProcedureN  G               The OSAK installation verification procedure (IVP) is run_I               automatically during the installation. However, you can runi?               it at any time by entering the following command:   "               $ @sys$test:osak_ivp  B               If the IVP runs successfully, you see the following:  C               Starting OSAK Installation Verification Procedure ...sM               OSAK Installation Verification Procedure completed successfullyt  ,         11-6 Installing the OSI Applications           I                                           Installing the OSI Applications I                         11.6 The OSAK Installation Verification Proceduret    H               If the IVP finishes with errors, you see a message similar               to this:  L               OSAK Installation Verification Procedure completed with errors  I               In both cases, the OSAK software produces a log file calledoE               OSAK$IVP.LOG in the default directory, SYS$TEST. If theeG               IVP fails during installation, you can check the log filemE               to help you identify the source of the problem. You cancE               also forward the log file to DIGITAL to assist you when %               discussing the problem.   E               When you have finished running the IVP and you are sure C               that the OSAK software is properly installed, back up C               the system disk. Save the distribution kit for futureI               installations.  5         11.7 Running the OSIF$CONFIGURE.COM Procedurec  I               Following the FTAM POLYCENTER Software Installation utility_E               installation, you should execute the osif$configure.com_>               procedure located in SYS$STARTUP. This procedureB               first verifies the existence of the OSIT$DEFAULT andE               OSIGTWY accounts, then asks whether you want to run the 8               installation verification procedure (IVP).  H               If the procedure finds that either of the OSIT$DEFAULT andI               OSIGTWY accounts are not present, the procedure creates thehH               account(s) and prompts for user input. The IVP question isG               asked whether or not it was necessary to create accounts.   G               Following is an example of running the script on a systemp/               where the accounts already exist:   /               $ @sys$startup:osif$configure.comrR                 This setup procedure will verify the existence of the OSIT$DEFAULTR                 and OSIGTWY accounts.  If these accounts are not present, you willP                 be asked some questions about UIC and default device, as well asR                 being required to choose passwords from a computer generated list.  C                 Do you wish to continue with this procedure [Yes] :a  T                 The OSIT$DEFAULT and OSIGTWY accounts are present.  The OSIT$DEFAULTW                 account is useful as an account to specify when running the DECnet-Plus Y                 FTAM IVP.  The OSIGTWY account is the mechanism by which users may access_W                 the DAP/FTAM Gateway.  For more information about this Gateway, see thet.                 FTAM Use and Management Guide.  I                                      Installing the OSI Applications 11-7h    l      '         Installing the OSI Applications 5         11.7 Running the OSIF$CONFIGURE.COM ProcedureO    0                 DECnet-Plus FTAM setup complete.  8                 Would you like to run the IVP [Yes] : No  9         11.8 The FTAM Installation Verification Procedure   F               You can verify the FTAM installation by running the FTAMF               installation verification procedure (IVP). The IVP is anE               internal test of the FTAM initiator and responder usingfG               the underlying OSI layers of the local system through thelI               Network layer. This testing verifies that your installationcF               can set up and accept an application association and itsF               underlying presentation and session connections. The IVPF               tests the FTAM DCL commands on the local system and also-               exercises the DAP-FTAM Gateway.n  C               The POLYCENTER Software Installation utility does notiC               automatically run the IVP. You must do this manually.r  5               The DCL commands tested by the IVP are:o  /               o  COPY/APPLICATION_PROTOCOL=FTAM   4               o  DIRECTORY/APPLICATION_PROTOCOL=FTAM  1               o  DELETE/APPLICATION_PROTOCOL=FTAMd  1               o  RENAME/APPLICATION_PROTOCOL=FTAMi  )         11.8.1 Preparing for the FTAM IVP   %               Before you run the IVP:   F               1. Ensure that the OSI transport is running and enabled.I                  It will be running if you answered YES to the "ConfigurecI                  Transport?" question during the net$configure procedure.   G               2. If you are running the IVP for the first time, be sure G                  to run the OSIF$CONFIGURE.COM beforehand. InstructionspH                  on running this procedure are in Section 11.7. The lastF                  question in the procedure asks if you want to run the<                  IVP. To do so, type YES and press <Return>.      ,         11-8 Installing the OSI Applications g         I                                           Installing the OSI ApplicationsfI                         11.8 The FTAM Installation Verification Proceduret    #         11.8.2 Running the FTAM IVPo  B               You can issue the IVP commands from any directory onD               the system. The IVP prompts you for an account and theC               corresponding password. The OSIT$DEFAULT account is a=F               reasonable choice since it will be configured correctly.F               However, you may specify any valid account and password.  &               $ @sys$test:osif$ivp.com  D                 DECnet-Plus FTAM Installation Verification Procedure  +                 It is 20-APR-1995 at 10:50.l  L                 The DECnet-Plus FTAM IVP assigns the LOCAL_FTAM alias to be:  F                         :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:  Y                 The DECnet-Plus FTAM IVP copies a small data file, SYS$TEST:OSIF$IVP.TMP,iP                 to LOCAL_FTAM::OSIFILE.TMP. The IVP requests a directory listingR                 of the new file, before copying it back to SYS$LOGIN:OSIF$IVP.CPY.I                 Next, the IVP requests a difference of the original file, W                 SYS$TEST:OSIF$IVP.TMP, and the second new file, SYS$LOGIN:OSIF$IVP.CPY.MT                 The LOCAL_FTAM::OSIFILE.TMP file, that was originally copied is thenP                 renamed to LOCAL_FTAM::OSIFILE.RNM. The IVP then deletes the two                 new files.  L                 To perform these actions, a valid username and password withF                 the following privileges must be supplied by the user:  >                         NETMBX, TMPMBX, SYSNAM, SYSLCK, PRMMBX  H               Please enter the USERNAME for use by the IVP: osit$default  ;               Please enter the PASSWORD for use by the IVP:   L                 $ COPY /APPLICATION_PROTOCOL=FTAM /LOG SYS$TEST:OSIF$IVP.TMP@                   LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.TMP  J               %COPY-S-COPIED, SYS$COMMON:[SYSTEST]OSIF$IVP.TMP;1 copied toU               :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:"OSIT$DEFAULT password":: B               SYS$COMMON:[OSIT$DEFAULT]OSIFILE.TMP;1 (403 records)  8                 $ DIRECTORY /APPLICATION_PROTOCOL=FTAM -@                   LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.TMP  H               Directory :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:::(                  "OSIT$DEFAULT password"  4               SYS$COMMON:[OSIT$DEFAULT]OSIFILE.TMP;1                 Total of 1 file.  I                                      Installing the OSI Applications 11-9_ _  N      '         Installing the OSI Applications 9         11.8 The FTAM Installation Verification Procedure     8                 $ COPY /APPLICATION_PROTOCOL=FTAM /LOG -B                   LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.TMP -(                   SYS$LOGIN:OSIF$IVP.CPY  Y               %COPY-S-COPIED, :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:"OSIT$DEFAULTbF               password"::SYS$COMMON:[OSIT$DEFAULT]OSIFILE.TMP;1 copied<                to DKA100:[SMITH]OSIF$IVP.CPY;8 (403 records)  I                 $ DIFFERENCE SYS$TEST:OSIF$IVP.TMP SYS$LOGIN:OSIF$IVP.CPY.4               Number of difference sections found: 03               Number of difference records found: 0s  .               DIFFERENCES /IGNORE=()/MERGED=1-4                  SYS$COMMON:[SYSTEST]OSIF$IVP.TMP;1--                  DKA100:[SMITH]OSIF$IVP.CPY;8   4                 $ DELETE/LOG SYS$LOGIN:OSIF$IVP.CPY;  :                 $ RENAME /APPLICATION_PROTOCOL=FTAM /LOG -B                   LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.TMP -                   OSIFILE.RNM O               %RENAME-I-RENAMED, :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:_P                  "OSIT$DEFAULT password"::SYS$COMMON:[OSIT$DEFAULT]OSIFILE.TMP;1'                  renamed to OSIFILE.RNM   :                 $ DELETE /APPLICATION_PROTOCOL=FTAM /LOG -@                   LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.RNMN               %DELETE-I-FILDEL, :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:M               "OSIT$DEFAULT password"::SYS$COMMON:[OSIT$DEFAULT]OSIFILE.RNM;1,                deleted (0 blocks)  \               Would you like to test the DAP Gateway (this requires the OSIGTWY password)? Y  E                 Checking SYS$SYSTEM:ISOAPPLICATIONS.DAT for OSINOD...t  @               Please enter the PASSWORD for the OSIGTWY account:  L                 $ COPY /APPLICATION_PROTOCOL=FTAM /LOG SYS$TEST:OSIF$IVP.TMPA                   LOCAL_FTAM"OSIT$DEFAULT password"::GTWYFILE.TMPc  J               %COPY-S-COPIED, SYS$COMMON:[SYSTEST]OSIF$IVP.TMP;1 copied toU               :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:"OSIT$DEFAULT password":: C               SYS$COMMON:[OSIT$DEFAULT]GTWYFILE.TMP;1 (403 records)C  J                 $ DIR 0"OSIGTWY password"::OSINOD"OSIT$DEFAULT password"::*                     SYS$LOGIN:GTWYFILE.TMP  -               Directory 0"OSIGTWY password"::   -         11-10 Installing the OSI Applicationsm    i      I                                           Installing the OSI Applications I                         11.8 The FTAM Installation Verification Procedure     X               OSINOD"OSIT$DEFAULT OSIT$DEFAULT"::SYS$COMMON:[OSIT$DEFAULT]GTWYFILE.TMP;1Z                                         24  20-APR-1995 10:53:47.00  (RWED,RWED,RWED,RWED)  )               Total of 1 file, 24 blocks.a  E                 $ DELETE /LOG 0"OSIT$DEFAULT password"::GTWYFILE.TMP;..               %DELETE-I-FILDEL, 0"OSIT$DEFAULTT               password"::SYS$COMMON:[OSIT$DEFAULT]GTWYFILE.TMP;1 deleted (24 blocks)  D                 DECnet-Plus FTAM Installation Verification Procedure0                 completed successfully at 10:53.  7         11.9 The VT Installation Verification Procedure   E               The VT installation verification procedure (IVP) is run I               automatically during the installation. However, you can runC?               it at any time by entering the following command:                   $ @sys$test:vt_ivp  A               If the IVP ran successfully, you see the following:   %               VT_IVP: Test successful   #               %IVP-S-END, IVP ended   H               If the IVP finishes with errors, you see a message similar               to this:  '               VT_IVP: <Failure message>4  #               %IVP-S-END, IVP ended   G               In both cases, the VT software produces a log file calledaH               VT_IVP.LOG in the SYS$SCRATCH directory. You can check theF               log file to help you identify the source of the problem.H               You can also forward the log file to DIGITAL to assist you*               when discussing the problem.  ,         11.10 De-installing OSI Applications  I               To de-install the OSI applications, you must be logged intoME               an account with the same privileges required to installoE               the OSI applications. See Section 10.2 for this list ofq               privileges.3  F               You may optionally shut down the OSI applications beforeD               de-installing them. See Section 11.4 for instructions.  I                                     Installing the OSI Applications 11-11M T  .      '         Installing the OSI Applications ,         11.10 De-installing OSI Applications    F               Note that you must de-install FTAM and VT before you de-               install OSAK.a  B               To de-install any of the OSI applications, enter the               command:  *               $ product remove application  /               application is FTAM, VT, or OSAK.s  G               Invoking this command shuts down the application if it isgF               running and removes the product files. An example of theG               de-installation response sequence for each application is (               provided in Section 11.13.  F                 ________________________ Note ________________________  >                 You do not have to remove a product before re-F                 installing the same version, or installing a different?                 version. If the product is already installed onr@                 the system, the POLYCENTER Software InstallationA                 utility removes it automatically before beginnings!                 the installation.   F                 ______________________________________________________  ,         11.11 Files Installed on Your System  D               The OSI applications installation procedure installs aF               number of files on your system. To list the files, enter$               the following command:  8               $ product show object /product=application  /               application is FTAM, VT, or OSAK.   2         11.12 Sample OSI Application Installations  ;               This section provides sample OSI applicationsT               installations.          -         11-12 Installing the OSI Applications            I                                           Installing the OSI Applications I                                11.12 Sample OSI Application Installationst    (         11.12.1 Sample OSAK Installation  =               $ prod install osak/source=sys$sysdevice:[kits]i  6               The following product has been selected:"               DEC AXPVMS OSAK T3.0  5               Do you want to continue? [YES] <Return>s  E               *** DEC AXPVMS OSAK T3.0: DEC OSAK V3.0 for OpenVMS AXPn  V                   Copyright  Digital Equipment Corporation 1994. All rights reserved.  /                   Digital Equipment Corporatione  U                   Do you want all the default values for this product? [YES] <Return>   I                   OSAKserver and OSAK network management will be stopped.A9                   Do you want to continue? [YES] <Return>b  ?                   Do you want to view the values? [NO] <Return>-  9               %PCSIUI-I-DONEASK, execution phase starting 6               The following product will be installed:"               DEC AXPVMS OSAK T3.0               %PCSI-I-G         VOLINFO, estimated space information for volume DISK$OVMSSYSTEMtI               -PCSI-I-VOLSPC, 6785 required; 350277 available; 343492 net O               Portion Done: 0%...10%...20%...30%...60%...70%...80%...90%...100% 7               The following product has been installed:f"               DEC AXPVMS OSAK T3.0:               %PCSI-I-EXETSTSTART, start of test procedure               %PCSI-I-A         EXETSTOK, end of test procedure; completed with no errorst  E               *** DEC AXPVMS OSAK T3.0: DEC OSAK V3.0 for OpenVMS AXPa  U                   OSAKserver and OSAK network management processes have been started.o  F                   Insert the following lines in SYS$MANAGER:SYSTARTUP_         VMS.COM:/                       $ @sys$startup:osak$start       I                                     Installing the OSI Applications 11-13  o  i      '         Installing the OSI Applications 2         11.12 Sample OSI Application Installations    4         11.12.2 Sample Virtual Terminal Installation  ;               $ prod install vt/source=sys$sysdevice:[kits]w  6               The following product has been selected:                DEC AXPVMS VT V2.1  5               Do you want to continue? [YES] <Return>s  -               *** DEC AXPVMS VT V2.1: DECnet-t)         Plus for OpenVMS Virtual Terminal   X                   Copyright (c) Digital Equipment Corporation 1995. All rights reserved.  Z                   VT requires the PAK DVNETEND, and the VT Gateways require DVNETEXT also.  Y                   OSAK must be installed and started before continuing this installation.o  9                   Do you want to continue? [YES] <Return>t  Y                   VT Gateways startup requires LAT and DEC TCP/IP Services started first.t9                   Do you want to continue? [YES] <Return>a  9               %PCSIUI-I-DONEASK, execution phase startingo6               The following product will be installed:                DEC AXPVMS VT V2.1               %PCSI-I-G         VOLINFO, estimated space information for volume DISK$OVMSSYSTEMvI               -PCSI-I-VOLSPC, 3506 required; 343419 available; 339913 netoI               Portion Done: 0%...10%...20%...50%...60%...80%...90%...100% 7               The following product has been installed:i                DEC AXPVMS VT V2.1:               %PCSI-I-EXETSTSTART, start of test procedure               %PCSI-I-A         EXETSTOK, end of test procedure; completed with no errorsu  -               *** DEC AXPVMS VT V2.1: DECnet-r)         Plus for OpenVMS Virtual Terminal   F                   Insert the following lines in SYS$MANAGER:SYSTARTUP_         VMS.COM:/                       @SYS$STARTUP:VT_START.COM J                   Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:.                       @SYS$MANAGER:VT_STOP.COM  H                   Previous VT_SYSTART.COM changes are in SYS$STARTUP:VT_         SYSTART.COM_OLDn  J                   Release notes are available in SYS$HELP:DECNET*.RELEASE_
         NOTESa  -         11-14 Installing the OSI Applications  l  n      I                                           Installing the OSI ApplicationsnI                                11.12 Sample OSI Application Installations                        DECnet-e@         Plus for OpenVMS Virtual Terminal Installation Completed  (         11.12.3 Sample FTAM Installation  I               $ product install ftam/source=sys$sysdevice:[kits] <Return>e  6               The following product has been selected:"               DEC AXPVMS FTAM V3.2  6               Do you want to continue? [YES]  <Return>  /               *** DEC AXPVMS FTAM V3.2: DECnet- +         Plus for OpenVMS OSI File Transfer,.3                       Access, and Management (FTAM)   X                   Copyright (c) Digital Equipment Corporation 1995. All rights reserved.  Y                   This product uses the PAKS: DVNETEND and the Gateway requires DVNETEXT.                      The DECnet-G?         Plus OSAK software must be installed and started before ,                continuing this installation.:                   Do you want to continue? [YES]  <Return>  9               %PCSIUI-I-DONEASK, execution phase startingF6               The following product will be installed:"               DEC AXPVMS FTAM V3.2               %PCSI-I-G         VOLINFO, estimated space information for volume DISK$OVMSSYSTEMc               -PCSI-I-<         VOLSPC, 27584 required; 423237 available; 395653 netO               Portion Done: 0%...10%...20%...30%...40%...50%...80%...90%...100% 7               The following product has been installed: "               DEC AXPVMS FTAM V3.2  /               *** DEC AXPVMS FTAM V3.2: DECnet- +         Plus for OpenVMS OSI File Transfer,r+               Access, and Management (FTAM)a  F                   Insert the following lines in SYS$MANAGER:SYSTARTUP_         VMS.COM:3                       @SYS$STARTUP:OSIF$STARTUP.COMLJ                   Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:0                       @SYS$STARTUP:OSIF$STOP.COM  U                   The following messages are informational and indicate the amount ofi)               each resource used by FTAM.n  I                                     Installing the OSI Applications 11-15            '         Installing the OSI ApplicationsM2         11.12 Sample OSI Application Installations    H                   This product requires the following SYSGEN parameters:(                       GBLSECTIONS add 24  H                   This product requires the following SYSGEN parameters:'                       GBLPAGES add 5068I  ?                   After installing DECnet-Plus FTAM you must do N               "$ @SYS$STARTUP:OSIF$CONFIGURE.COM" to setup necessary accounts.                     The DECnet-o5         Plus FTAM IVP may be run at any time by doing (               "$ @SYS$TEST:OSIF$IVP.COM"  J                   Release notes are available in SYS$HELP:DECNET*.RELEASE_
         NOTES   E                   DECnet-Plus for OpenVMS FTAM Installation CompletedI  5         11.13 Sample OSI Application De-installations   ?               This section provides sample OSI applications de-                installations.  7         11.13.1 Sample Virtual Terminal De-installationT  !               $ product remove vtc  6               The following product has been selected:                DEC AXPVMS VT V2.1  5               Do you want to continue? [YES] <Return> 4               The following product will be removed:                DEC AXPVMS VT V2.1               %PCSI-I-G         VOLINFO, estimated space information for volume DISK$OVMSSYSTEM                -PCSI-I-VOLSPC, -y                  -         11-16 Installing the OSI Applicationsf p  m      I                                           Installing the OSI Applications I                             11.13 Sample OSI Application De-installationsT    3         3436 required; 310692 available; 314128 net                Portion Done: 0%B               %PCSI-I-PRCOUTPUT, output from subprocess follows...=               %%% VT_RESPONDER is running in process 0000050D )               %%% Process will be stoppede<               %%% VT_LAT_GTWY is running in process 00000518)               %%% Process will be stopped.<               %%% LAT_VT_GTWY is running in process 00000519)               %%% Process will be stoppedT?               %%% VT_TELNET_GTWY is running in process 0000029E )               %%% Process will be stopped ?               %%% TELNET_VT_GTWY is running in process 0000029F )               %%% Process will be stoppedl               Portion Done: 20% >               Portion Done: 50%...60%...70%...80%...90%...100%5               The following product has been removed:r                DEC AXPVMS VT V2.1  +         11.13.2 Sample FTAM De-installation   #               $ product remove ftam   6               The following product has been selected:"               DEC AXPVMS FTAM V3.2  5               Do you want to continue? [YES] <Return>P4               The following product will be removed:"               DEC AXPVMS FTAM V3.2               %PCSI-I-G         VOLINFO, estimated space information for volume DISK$OVMSSYSTEMp               -PCSI-I-VOLSPC, -.4         27578 required; 314199 available; 341777 netO               Portion Done: 0%...20%...40%...50%...60%...70%...80%...90%...100% 5               The following product has been removed: "               DEC AXPVMS FTAM V3.2                    I                                     Installing the OSI Applications 11-17c :         '         Installing the OSI Applications 5         11.13 Sample OSI Application De-installations     +         11.13.3 Sample OSAK De-installation   #               $ product remove osakl  6               The following product has been selected:"               DEC AXPVMS OSAK T3.0  5               Do you want to continue? [YES] <Return>                  PCSI-E-CB         CONREMUNR, optionally remove product DEC AXPVMS DECNET_OSIG                 T6.3-K3_B that is no longer required by another product <               Do you want to take this action? [NO] <Return>5               Do you want to continue? [YES] <Return>I4               The following product will be removed:"               DEC AXPVMS OSAK T3.0               %PCSI-I-G         VOLINFO, estimated space information for volume DISK$OVMSSYSTEMu               -PCSI-I-VOLSPC, -:3         6735 required; 344094 available; 350829 net $               Portion Done: 0%...20%B               %PCSI-I-PRCOUTPUT, output from subprocess follows...?               %%% OSAK$SERVER_V3 is running in process 0000054A )               %%% Process will be stopped <               %%% OSAK$NETMAN is running in process 0000054B)               %%% Process will be stoppedoD               Portion Done: 40%...50%...60%...70%...80%...90%...100%5               The following product has been removed:_"               DEC AXPVMS OSAK T3.0                                -         11-18 Installing the OSI Applicationst S  L                    I                                                                        12TI         _________________________________________________________________R  I                                          Configuring the OSI Applicationso    F               This chapter describes how to configure FTAM and Virtual1               Terminal (VT) on an OpenVMS system.G  2         12.1 FTAM and Virtual Terminal Terminology  F               o  An initiator, or client, is the program on one systemI                  that initiates a request to a program on another system, '                  and awaits a response.G  C               o  A responder, or server, is the program on a systemoG                  providing a response to a request initiated on anotherS                  system.  E               o  A listener is a job running on the responding systemaC                  that fulfills incoming requests from an initiating3                  system.  6         12.2 About the OSI Application Entity Database  D               The FTAM and VT applications require you to manage theC               OSI application entity database. This database storesaD               addressing information for aliases that represent FTAM0               and VT applications and listeners.  7               On OpenVMS, the location of this file is:   ,               sys$system:isoapplications.dat  H               The entries in the isoapplications database define aliasesC               and contain information about local listeners, remote D               responders, and source addresses for local initiators.F               The aliases are used by local FTAM and VT initiators andG               listeners, and by users who specify these aliases in FTAMP               and VT commands.    I                                     Configuring the OSI Applications 12-1  p  e      (         Configuring the OSI Applications6         12.2 About the OSI Application Entity Database    B               There are three types of formats you can use in this1               isoapplications database. They are:a  A               o  Address - Information on local listeners, remotedB                  applications, and local initiator source address.  C               o  Distinguished Name - X.500 Directory Service fixeds                  entries.   D               o  Pattern - X.500 Directory Service variable entries.  I               The isoapplications database can contain any combination ofF               these formats.  D               For detailed information on the Address, Distinguished=               Name and Pattern formats, refer to Chapter 9 in /               <REFERENCE>(DNPLUS_FTAM_VT_MGMT).   B         12.3 Getting Started Configuring Initiating and Responding              Entitiesr  F               This section provides basic configuration task checklistB               items and examples for setting up the initiating and-               responding systems or entities.o  D               Refer to <REFERENCE>(DNPLUS_FTAM_VT_MGMT) for detailedB               information about managing initiating and responding               systems.  G               If you are already familiar with configuring FTAM and VT,nH               then you can continue the configuration procedure starting               at Section 12.4.  -         12.3.1 Setting Up Responding EntitiesI  B               On OpenVMS, the FTAM and VT installation and startupE               procedures provide default FTAM and VT responders. When F               the vt_start.com and osif$startup.com command proceduresB               are run, these responders are started automatically.  -         12.3.2 Setting Up Initiating Entities   <               A responding entity needs to be defined in theG               isoapplications database before you can access it. To getnE               the information you need for an alias, you must contactcE               the person responsible for configuring and managing theeI               remote OSI system running FTAM or VT. The remote FTAM or VT H               implementation may be from DIGITAL or from another vendor.  -         12-2 Configuring the OSI Applications  o  r      I                                          Configuring the OSI Applications I       12.3 Getting Started Configuring Initiating and Responding Entities     G               Set up the isoapplications database for a specific remoteo0               FTAM or VT application as follows:  H               1. Determine the available transports between your DIGITALA                  system and the remote OSI system and select one.t  C               2. Collect the information needed to define an alias.sD                  Complete the Address Format Worksheet Form shown in'                  Table 12-3 as follows::  G                  a. Choose an alias name for the remote responder. This H                     name is local to your system and can be any name you                     choose.   I                  b. Specify whether the remote application is FTAM or VT.n  E                  c. Obtain the AP-title and the AE-qualifier that the H                     remote application requires, if any. If they are not7                     required, leave these fields blank.c  H                  d. Obtain the SAP selectors (PSEL, SSEL, TSEL) that the0                     remote application requires.  I                  e. Obtain the NSAP of the remote application. The format G                     of this field depends upon which transport providere"                     you are using.  A                     o  For OSI transport: Obtain the remote NSAP.y  G                     o  For RFC 1006: Obtain the remote Internet address 0                        and RFC 1006 daemon port.  G                     o  For CONS over X.25: Obtain the remote X.25 NSAP.u  G                  f. Specify the transport provider you selected in stepo                     1.  F                  g. Determine the local transport template you want to                     use.  F                     o  For OSI transport: Default template is default.  F                     o  For RFC 1006: Default template is osit$rfc1006.  ?                     o  For CONS over X.25: Use a CONS template.d  F               3. Define the alias in isoapplications in Address formatG                  with the information you collected in the prior steps.o@                  You can edit this database using a text editor.  B               Once the setup is complete, you can invoke initiator'               requests using the alias.T  I                                     Configuring the OSI Applications 12-3n f  s      (         Configuring the OSI ApplicationsK         12.3 Getting Started Configuring Initiating and Responding Entities     4         12.3.3 Example: Performing An FTAM File Copy  E               Use the task list from Section 12.3.2 to configure your$2               system to perform an FTAM file copy.  H               In this example, you copy remote file system_a_filename on>               System-A, to file system_b_filename on System-B.  D               System-A is the responding entity, and System-B is theB               initiating entity. System-A and System-B are OpenVMS               systems.  H               Use the OSI provider and the following account information               on System-A:  .               username: system_a_user <Return>-               password: system_a_pwd <Return>   E               Use the default FTAM responder on System-A. There is nol)               setup required on System-A.c  D               Using information collected in Section 12.3.2, performF               the following steps on initiating entity System-B from a!               privileged account:m  H               1. Determine available transports and choose one. For this,                  example, use OSI transport.  -               2. Perform the following steps:e  D                  a. Choose an alias. For this example, use system_a_                     alias.  D                  b. Specify FTAM or VT. For this example, the remote(                     application is FTAM.  B                  c. Obtain the AP-title and AE-qualifier. For this@                     example, the responder does not require this                      information.  C                  d. Obtain the SAP selectors. The FTAM responder ont/                     OpenVMS uses RMS.FTAM.OSIF..  =                  e. Obtain the remote NSAP. For this example, 9                     the responder's OSI transport NSAP isT+                     %X410004AA000400001321.   E                  f. Specify transport provider. For this example, userG                     OSI. Note that because OSI is the default provider,O5                     you can omit it for this example.e  -         12-4 Configuring the OSI Applications  M  O      I                                          Configuring the OSI ApplicationseI       12.3 Getting Started Configuring Initiating and Responding EntitiesM    G                  g. Determine the transport template. For this example,nI                     use default. Note that because default is the defaulte?                     template, you can omit it for this example.   5               3. Define the alias in isoapplications:   9                  system_a_alias  :FTAM:::RMS.FTAM.OSIF. \IB                                          %X410004AA000400001321, \G                                          provider=osi,template=default:O  F               After the setup is complete, you can start the FTAM copy               command:  0               $ copy/application=ftam - <Return>V               system_a_alias"system_a_user system_a_pwd"::system_a_filename - <Return>(               system_b_filename <Return>  ;         12.3.4 Example: Performing A Virtual Terminal LoginE  E               Use the task list from Section 12.3.2 to configure your.9               system to perform a Virtual Terminal login.   I               In this example, you perform a VT set host/vtp from System-r               B to System-A.  D               System-A is the responding entity, and System-B is theB               initiating entity. System-A and System-B are OpenVMS               systems.  A               Use the RFC 1006 provider and the following account (               information from System-A:  .               username: system_a_user <Return>-               password: system_a_pwd <Return>d  I               Use the default VT responder on responding entity System-A.S5               There is no setup required on System-A.v  D               Using the information from Section 12.3.2, perform theB               following steps on initiating entity System-B from a!               privileged account:%  H               1. Determine available transports and choose one. For this'                  example, use RFC 1006.   -               2. Perform the following steps:   D                  a. Choose an alias. For this example, use system_a_                     alias.  I                                     Configuring the OSI Applications 12-5            (         Configuring the OSI ApplicationsK         12.3 Getting Started Configuring Initiating and Responding Entities     D                  b. Specify FTAM or VT. For this example, the remote&                     application is VT.  B                  c. Obtain the AP-title and AE-qualifier. For this@                     example, the responder does not require this                      information.  I                  d. Obtain the SAP selectors. The VT responder on OpenVMSo.                     uses %x0001.%x0001.%x0002.  A                  e. Obtain the remote NSAP. For this example, thedG                     responder's RFC 1006 internet address is 16.20.8.42m/                     and the daemon port is 102.   I                  f. Specify transport provider. For this example, use RFC                      1006.N  G                  g. Determine the transport template. For this example, D                     use osit$rfc1006. Note that because osit$rfc1006E                     is the default template, you can omit it for thisa                     example.  5               3. Define the alias in isoapplications:p  >                  system_a_alias  :VT:::%x0001.%x0001.%x0002. \9                                         16.20.8.42.102, \o9                                         provider=rfc1006:i  C               After the setup is complete, you can start the VT set                host/vtp command:   5               $ set host/vtp system_a_alias  <Return>   0               Username:  SYSTEM_A_USER  <Return>/               Password:  system_a_pwd  <Return>   &         12.4 About Responding Entities  I               As stated in Section 12.3.1, default FTAM and VT responderstH               are provided on OpenVMS. The installation also supplies anI               initial isoapplications file with local aliases used by then?               FTAM and VT responders, gateways, and initiators.l  G               Table 12-1 shows default addresses (PSEL, SSEL, TSEL) forp6               the FTAM and VT responders and gateways:  -         12-6 Configuring the OSI Applicationso o         I                                          Configuring the OSI Applications I                                            12.4 About Responding Entitiesc    I               Table_12-1_Default_Addresses_______________________________5  I               Gateway/Responder_______Default_Address____________________   3               FTAM Responder          RMS.FTAM.OSIFs  :               VT Responder            %x0001.%x0001.%x0002  :               VT/LAT Gateway          %x0001.%x0001.%x0003  I               VT/TELNET_Gateway_______%x0001.%x0001.%x0004_______________   >               Each of these responders and gateways can acceptE               connections through all of the transports that FTAM and A               VT support: OSI transport, RFC 1006, and X.25/CONS.   G               You can set up your own responder for FTAM in addition to G               or instead of the default one. You cannot set up your own G               responder for VT; however, you can change the aliases anduG               change the local addresses (PSEL, SSEL, TSEL) that the VTiH               responder and gateways use. For these operations, refer toF               <REFERENCE>(DNPLUS_FTAM_VT_MGMT), Chapter 10 and Chapter               11.P  F         12.5 Configuring Addresses for Remote FTAM and VT Applications  I               The primary job of configuring FTAM and VT on OpenVMS is to H               add entries to the isoapplications database for the remoteG               FTAM and VT applications on your network. On OpenVMS, you D               add entries to isoapplications by using a text editor.  D               Refer to Chapter 9 in <REFERENCE>(DNPLUS_FTAM_VT_MGMT)H               for a complete description of managing the isoapplications               database.l  :               As mentioned in Section 12.2, every entry in7               isoapplications has one of three formats:w                 o  Address format   *               o  Distinguished Name format                 o  Pattern formatE  A               If you have the DEC X.500 Directory Service producttE               installed, you have the option of adding entries of therC               Distinguished Name format and the Pattern format. You E               have the option of adding entries of the Address formatA7               regardless of whether X.500 is installed.d  I                                     Configuring the OSI Applications 12-7            (         Configuring the OSI ApplicationsF         12.5 Configuring Addresses for Remote FTAM and VT Applications    D               If you are not using X.500, complete an Address FormatI               Worksheet in Table 12-3 for each remote application. If you D               are using X.500, complete the checklist in Table 12-2.  A               To complete the Address Format Worksheet forms, see.A               Section 12.3.2 for collecting relevant information.                                                                               -         12-8 Configuring the OSI Applicationsi i  t      I                                          Configuring the OSI Applications I            12.5 Configuring Addresses for Remote FTAM and VT Applications_    I               Table_12-2_X.500_Configuration_Checklist___________________t  I               Question_______________________________________Yes__No_____r  F               Do you want to register the local listeners    <  > <  >%               in the X.500 Directory?T  :               If yes, you need an X.500 Distinguished Name6               to identify each of the local listeners.9               Specify a Distinguished Name for each local                listener.   U               o  X.500 Distinguished Name(s): _______________________________________p  R                  _________________________________________________________________  I               ___________________________________________________________   F               Do you want to add entries to                  <  > <  >               isoapplications?  :               If yes, then continue on with this checklist7               to add entries of the Distinguished Name, +               Pattern, and Address formats.a  I               ___________________________________________________________n  F               Do you want to add entries of the              <  > <  >(               Distinguished Name format?  8               If yes, complete the following information*               for each remote application:  M               o  Alias name: ________________________________________________,  *               o  Application (FTAM or VT):  5                  ____________________________________e  $               o  Distinguished Name:  9                  ________________________________________s  )               o  Transport Template List:a  6                  _____________________________________  I               ___________________________________________________________t  I                                     Configuring the OSI Applications 12-9  h         (         Configuring the OSI ApplicationsF         12.5 Configuring Addresses for Remote FTAM and VT Applications    I               Table_12-2_(Cont.)_X.500_Configuration_Checklist___________,  I               Question_______________________________________Yes__No_____   F               Do you want to add entries of the Pattern      <  > <  >               format?r  5               If yes, you need to determine what youra*               pattern(s) should look like.  :               You may be able to get this information from7               your network administrator, or you may be 6               able to use the DEC X.500 Administration8               Utility (DXIM) to examine the structure of;               the X.500 Directory Information Tree for your 9               organization to determine what your Patterne'               format entries should be.   9               Complete the following information for eachd:               pattern entry. The Distinguished Name should5               be incomplete (contain at least one *).a  *               o  Application (FTAM or VT):  5                  ____________________________________   $               o  Distinguished Name:  9                  ________________________________________i  )               o  Transport Template List:   6                  _____________________________________  I               ___________________________________________________________a  F               Do you want to add entries of the Address      <  > <  >               format?   7               If yes, complete a form in Table 12-3 for I               each_remote_application.___________________________________         .         12-10 Configuring the OSI Applications e  n      I                                          Configuring the OSI ApplicationsfI            12.5 Configuring Addresses for Remote FTAM and VT Applicationsa    I         Table_12-3_Address_Format_Worksheet______________________________g           Configuration I         Information___________Answer/Entry_______________________________   X         Alias name:           <                                                        >  X         Application (FTAM or  <                                                        >         VT):  X         AP-title:             <                                                        >      X         AE-qualifier:         <                                                        >    X         PSEL:                 <                                                        >    X         SSEL:                 <                                                        >    X         TSEL:                 <                                                        >      X         NSAP(s):              <                                                        >    X         Transport provider    <                                                        >         name(s):  X         Transport template    <                                                        >         name(s):  I         _________________________________________________________________a                I                                    Configuring the OSI Applications 12-11            (         Configuring the OSI ApplicationsF         12.5 Configuring Addresses for Remote FTAM and VT Applications    ,         12.5.1 Adding Address Format Entries  H               Refer to Section 9.2.1 in <REFERENCE>(DNPLUS_FTAM_VT_MGMT)C               for a complete description of Address format entries.eD               Entries of the Address format take the following form:  H               alias   :application:ap-title:ae-qualifier:psel.ssel.tsel.P                                                          nsap,transport_options;T                                                          nsap,transport_options; ...P                                                          nsap,transport_options:  E               Use the information you completed in the Address FormateG               Worksheet to add the Address format entries. For example,t@               an Address format entry for VT could look like the               following:  L               remote1 :VT:::psap.ssap.tsap.%x4145418715004108002B23569821, \I                                            provider=osi,template=default:   C               Note that you can enter more than one NSAP per alias.r  7         12.5.2 Adding Distinguished Name Format Entries   H               Refer to Section 9.2.2 in <REFERENCE>(DNPLUS_FTAM_VT_MGMT)G               for a complete description of Distinguished Name entries. I               Entries of the Distinguished Name format take the following                form:   I               alias   :application:template_list:x500_distinguished_name:i  D               Use the information you completed in the configurationI               checklist to add the Distinguished Name format entries. For G               example, a Distinguished Name format entry for FTAM could &               look like the following:  X               remote2 :FTAM:template=default:/c=us/o=org/ou=org_unit/cn=remote2/cn=ftam:  ,         12.5.3 Adding Pattern Format Entries  H               Refer to Section 9.2.3 in <REFERENCE>(DNPLUS_FTAM_VT_MGMT)C               for a complete description of Pattern format entries.fD               Entries of the Pattern format take the following form:  K               *   :application:template_list:incomplete_distinguished_name:u  G               You need only one Pattern format entry in isoapplicationsnH               for each application (FTAM or VT). Use the information youI               completed in the configuration checklist to add the Patternt               format entries.-  .         12-12 Configuring the OSI Applications           I                                          Configuring the OSI ApplicationseI            12.5 Configuring Addresses for Remote FTAM and VT Applicationse    @               For example, the aliases passed to the FTAM and VTG               commands could correspond to the value of the common name G               attribute of the application process entries in the X.500 F               directory. In this case, you might use the following two&               isoapplications entries:  J               *   :VT:template=default:/c=us/o=org/ou=org_unit/cn=*/cn=vt:N               *   :FTAM:template=default:/c=us/o=org/ou=org_unit/cn=*/cn=ftam:  6         12.6 Registering Responders To X.500 Directory  G               If you have DEC X.500 Directory Service available to you,rG               you have the option of storing the addresses of the local E               FTAM and VT responders in the X.500 Directory database. D               Use the information you completed in the configuration:               checklist to register your local responders.  @               For example, you could use the following DEC X.500E               Administration Facility (DXIM) command to register yourtE               local FTAM responder on node srchr, assuming that srchr G               already exists in the database as an application process.   Z               dxim> create /c=us/o=local_org/ou=local_org_unit/cn=srchr/cn=ftam - <Return>I               _dxim> attributes objectclass=applicationentity, - <Return>a]               _dxim> presentationaddress="RMS"/"FTAM"/"OSIF"/NS+410004AA000400001321 <Return>                                         I                                    Configuring the OSI Applications 12-13p e  f                    I                                                                    Part V I         _________________________________________________________________   I                                                                Appendixes             ;               Part V includes the following two appendixes:g  B               o  Appendix A - Configuring Asynchronous Connections  C               o  Appendix B - Configuring NSP and the OSI Transporta                  Service                         I                                                                         A I         _________________________________________________________________   I                                      Configuring Asynchronous Connectionsy    C               This appendix describes how to configure asynchronousnG               connections, which give you the option of connecting youryF               OpenVMS system to another system by means of a low-cost,G               low-speed asynchronous line. Asynchronous connections areSF               implemented in software and can be run over any directlyG               connected terminal line that the OpenVMS system supports.o  B               The asynchronous protocol provides for a full-duplex@               connection and can be used for remote asynchronousA               communications over a telephone line using a modem. H               Asynchronous connections are not supported for maintenance<               operations or for controller loopback testing.  +         A.1 Asynchronous DECnet Connections   F               Normally, the OpenVMS system controls lines connected toI               terminal ports, as in interactive logins. You can, however,tE               switch the line so the DECnet-Plus software can use theTH               line for an asynchronous connection to another system. YouI               can establish two types of asynchronous DECnet connections:   B               o  A static asynchronous connection, which creates aI                  permanent DECnet link to a single remote node. Two nodesTG                  are connected by either a dialup line or by a physical E                  line attached to a terminal port at each end. Before G                  the DECnet connection is made, the terminal lines must F                  be converted to static asynchronous DDCMP lines. (See                   Section A.1.1.)  D               o  A dynamic asynchronous connection, which provides aC                  temporary DECnet link. A dynamic asynchronous line E                  is normally switched on for network use only for thesC                  duration of a dialup connection between two nodes. C                  When the telephone is hung up, the line reverts to A                  being a terminal line. You can establish dynamic   I                                  Configuring Asynchronous Connections A-1            ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connectionse    C                  connections to different remote nodes at differenteE                  times. When using a dynamic connection, you can have>E                  the terminal line switched automatically to a DECnettF                  line, or you can switch it to a DECnet line manually.%                  (See Section A.1.2.)   A               The asynchronous software is optional. You can load >               and configure it by using the net$configure.com,@               net$startup.com, and wandd$startup.com procedures.                                                                        0         A-2 Configuring Asynchronous Connections g  w      I                                      Configuring Asynchronous Connections I                                       A.1 Asynchronous DECnet Connections     F                 ________________________ Note ________________________  ;                 The net$configure.com, net$startup.com, and_A                 wandd$startup.com procedures automatically set up_8                 static asynchronous connections for you.  B                 The information in Section A.1.1 is necessary onlyD                 if you want to set up a configuration outside of the9                 configuration provided by the procedures._  ;                 The net$configure.com, net$startup.com, andwC                 wandd$startup.com procedures load all the necessarytD                 images and NCL files to preconfigure your system forE                 dynamic asynchronous connections. The user making theTF                 dynamic connection needs only to log in and invoke the                 dynamic switch.   E                 Most of the information in Section A.1.2 is necessary B                 only if you want to set up a configuration outside@                 of the configuration provided by the procedures.F                 Section A.1.2.2 provides information about the dynamic                 switch.   F                 ______________________________________________________  A               The asynchronous software consists of three pieces:t                 o  asydriver                 o  asyswitch                 o  asydynswitchT  I               To switch a terminal line to a DECnet line or a DECnet linenG               back to a terminal line, you use DCL set commands such aso               the following:  :               o  To switch a DECnet line back to ttdriver:  7                  $ set terminal/nonetwork terminal-port   H               o  To switch a terminal line to a static asynchronous line                  (asydriver):r  5                  $ set terminal/network terminal-port   I               o  To switch a terminal line to a dynamic asynchronous line                   (asydriver):   5                  $ set terminal/network/switch=decneth  I                                  Configuring Asynchronous Connections A-3r           ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connections     >               o  To switch a terminal line to a dynamic manual/                  asynchronous line (asydriver):p  <                  $ set terminal/network/switch=decnet/manual  ?               Switching the line is only one step in setting up G               asynchronous communications. You must also configure yourdF               DECnet lines, links, and circuits. Setting up a link andF               circuit for asynchronous connections is the same as whenG               you set up a synchronous link and circuit. The differencefF               occurs when you configure your line in the Modem ConnectE               module. The communications port attribute for the modem 4               connect line has special significance.  F               To set up a dynamic asynchronous connection, you need toG               preconfigure the protocol stack. This means that you needFF               to map a routing circuit to a DDCMP logical station. TheD               logical station, in turn, uses a line created with theG               Modem Connect module that specifies a communications portrH               with either a "floating" line or an explicit line for yourD               dynamic connection. A "floating" line is not tied to aF               specific terminal device, while an explicit line is tiedI               to a specific device. You must configure the protocol stack F               (at both ends of the link when using two DECnet-Plus forG               OpenVMS systems) before you set host to the remote system_F               and switch the dynamic asynchronous line into operation.                                      0         A-4 Configuring Asynchronous Connections           I                                      Configuring Asynchronous ConnectionswI                                       A.1 Asynchronous DECnet Connections     F                 ________________________ Note ________________________  B                 Non OpenVMS systems that support OSI standards canD                 make asynchronous DECnet-Plus connections to OpenVMSC                 systems. The asynchronous connection can be betweeniA                 two routers, a router and an end node, or two end                  nodes.  F                 ______________________________________________________  ;         A.1.1 Establishing a Static Asynchronous Connection_  D               A static asynchronous DECnet connection is a permanentG               connection between two nodes. This type of connection cant)               be made in one of two ways:_  F               o  The nodes can be connected by a physical line (a nullI                  modem cable) attached to a terminal port at each system.oE                  No modems are required. You can communicate with the *                  other system at any time.  D               o  The connection can be made over a dialup line usingC                  modems at both ends of the line. For example, your C                  OpenVMS system can establish a static asynchronous C                  connection to a remote node over a telephone line.   C               Follow the steps outlined in this section to manuallyhA               establish a static asynchronous connection. For the F               connection to be successful, the node with which you areH               creating a DECnet link must also establish an asynchronousH               DECnet connection with your node. (The line speeds at each6               end of the connection must be the same.)  F                 ________________________ Note ________________________  =                 If you use the net$configure.com procedure tol?                 set up your static asynchronous lines, then thesE                 net$startup.com and wandd$startup.com procedures loadn:                 asydriver and configure the lines for you.  F                 ______________________________________________________  E               1. Log in to the SYSTEM account on your OpenVMS system._  G               2. DECnet must be running on both nodes for the remaining_F                  steps. If not already done, you and the remote systemB                  manager must start up the network by entering the#                  following command:   I                                  Configuring Asynchronous Connections A-5b 1         ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connections     +                  $ @sys$startup:net$startup   9               3. Load the asynchronous driver, asydriver.O  B                  Enter the following commands at your terminal (orB                  include them in the sys$manager:systartup_vms.com?                  command procedure before you boot the system):   (                  $ run sys$system:sysgen@                  SYSGEN> connect asy0/noadapter/driver=asydriver                  SYSGEN> exit   B                  The asynchronous driver must be loaded before any5                  asynchronous connection can be made.:  I               4. Next, install the asynchronous shareable images required H                  for a static asynchronous connection. Use the following                  command:   H                  $ install add sys$library:asyswitch.exe/open/head/share  E               5. To change a terminal line into a static asynchronous H                  DECnet line, use the DCL command set terminal terminal-A                  port-name with the appropriate qualifiers, where H                  terminal-port-name represents the device where you wantD                  to connect the static asynchronous DECnet line (seeF                  examples a and b.) If you have more than one terminalD                  attached to your OpenVMS system, you must specify aG                  set terminal command for each terminal line used for a_7                  static asynchronous DECnet connection.   F                  a. Nondialup line: The following command converts theE                     terminal line connected to the port into a DECnetu/                     line with no modem control:s  C                     $ set terminal/permanent/nomodem/notype_ahead -e2                     _$ /network terminal-port-name  H                     The terminal-port-name, for instance, could be tta0.  C                  b. Dialup line: The following command converts the E                     terminal line connected to the port (which can be H                     used as a dialup line) into a DECnet line with modem                     control:  I                     $ set terminal/permanent/notype_ahead/network/modem - >                     _$ /noautobaud/nohangup terminal-port-name  H                     The terminal-port-name, for instance, could be ttb0.  0         A-6 Configuring Asynchronous Connections r  .      I                                      Configuring Asynchronous Connections I                                       A.1 Asynchronous DECnet Connections4    D                  You can change the line speed by resetting the lineD                  to non-network mode with the set terminal/nonetworkD                  command. After you do this, switch the line back toH                  network mode with the set terminal/network command. YouG                  cannot use the set command to change the line speed ortH                  any other parameters while the line is in network mode.  H                  You can ensure that these set terminal commands executeB                  automatically each time the network is started inF                  the future. Modify your sys$manager:systartup_vms.comG                  command procedure to include all required set terminal @                  commands after the network starts up but beforeG                  executing the commands in the next step that configured(                  the modem connect line.  @               6. Next, configure your line. If the configurationF                  procedures have not already created the Modem ConnectH                  module, create it manually before configuring the line.H                  Use the following example to set up the necessary modem"                  connect entities.  %                  $ run sys$system:ncl   ?                  ncl> create modem connect line static_asynch - <                  _ncl> communications port async_port_name 1  G                  ncl> set modem connect line static_asynch speed 2400 2a  =                  ncl> enable modem connect line static_asynchn  <                  1  For an asynchronous line or circuit, theE                     communications port attribute, (async_port_name),g+                     has one of two formats:a  (                     o  devcu as in txa0:  +                     o  dev-c-u as in tx-0-0   8                     where dev-c-u is defined as follows:  I                     dev  The first two letters of the asynchronous device >                          name (possible values are tt and tx).  C                     c    A decimal number (0 or a positive integer)pD                          designating a device's hardware controller.G                          If the third letter of the device name is A, c6I                          equals 0. If the third letter of the device name 5                          is B, c equals 1, and so on.   I                                  Configuring Asynchronous Connections A-7T a  V      ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connectionsn      H                     u    The unit number of the device name; u is always:                          equal to 0 or a positive integer.  H                     For example, dev-c-u would be tx-0-0 for unit txa0:.  C                  2  The line speeds at both sides of the connectionh'                     should be the same.a  H               7. Next, configure your data link and routing circuit. ForI                  information about configuring your data link and routingaG                  circuit, see the chapters on managing network security>I                  and network management tasks in <REFERENCE>(DNPLUS_OVMS_                   NET_MGMT).   C               8. For security over a dialup connection, run NCL andaE                  establish optional routing initialization passwords. I                  For more information about using verifiers, refer to the_9                  <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide.   <         A.1.1.1 Terminating a Static Asynchronous Connection  H               Use the following steps to terminate a static asynchronous               connection:   E               1. Use NCL to disable (turn off) and delete the routingoF                  circuit and the static asynchronous line, as follows:  %                  $ run sys$system:ncl   >                  ncl> disable modem connect line static_asynch  8                  ncl> disable ddcmp link static_asynch -4                  _ncl> logical station static_asynch  6                  ncl> disable ddcmp link static_asynch  ;                  ncl> disable routing circuit static_asynchc  =                  ncl> delete modem connect line static_asynch   7                  ncl> delete ddcmp link static_asynch - 4                  _ncl> logical station static_asynch  5                  ncl> delete ddcmp link static_asynch   :                  ncl> delete routing circuit static_asynch                  ncl> exit  0         A-8 Configuring Asynchronous Connections o         I                                      Configuring Asynchronous ConnectionssI                                       A.1 Asynchronous DECnet Connectionsm    F               2. The following command switches your asynchronous line)                  back to a terminal line:r  P                  $ set terminal/permanent/nonetwork/typeahead terminal_port_name  F         A.1.1.2 Reasons for Failure of Static Asynchronous Connections  D               If the initial set terminal command fails, check that:  "               o  WANDD started up.  H               o  The asydriver loaded (the asy0 device must be present).  )               o  The asyswitch installed.s  G               If the logical station is in the on-starting state, checki               that:t  G               o  The line speeds at both ends of the connection are setm#                  to the same value.   F               o  The modem control characteristic of the modem connect<                  line at both ends of the link are the same.  ;               o  The routing circuits configured correctly.s  H               o  The parity is correct. Asynchronous DECnet requires theG                  parity on the asynchronous line be set to none and theuE                  terminal line be set to use 8-bit characters. If you I                  are using a system other than OpenVMS, the terminal linen3                  must be set to the correct parity.f  @               If your terminal line cannot be set up as a staticB               asynchronous DDCMP line, check whether the following               condition exists:   C               o  If data is stored in a type-ahead buffer, the lineoE                  appears as a terminal line even if a startup commandoF                  procedure attempts to set it up as a DDCMP line. ThisI                  generally occurs when the remote node is running and its H                  asynchronous DDCMP line is on. The DDCMP start messagesF                  being transmitted are stored in the type-ahead bufferI                  associated with your terminal line. Before you can start G                  up your line in DDCMP mode, terminate the process thatl)                  owns your terminal line.n  I               To verify that the asynchronous line is connected properly,m"               check the following:  G               o  For local connections, verify that the cable is a nulls                  modem cable.   I                                  Configuring Asynchronous Connections A-9n           ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connections_    B               o  For modem connections, verify that the cable is aD                  straight-through cable and that if the modem is putH                  in analog loopback, the circuit comes up with the local+                  node as the adjacent node.   D               o  For both types of connections, verify that the port@                  is operational by resetting it to terminal-typeG                  characteristics and plugging in a terminal and loggingr                  in.  G               If your connection is timing out or losing DDCMP packets,tG               you might not have a sufficient number of receive buffers A               set up on the DDCMP link for the asynchronous line.T  I               For more information about solving problems in your DECnet- F               Plus network, refer to the <REFERENCE>(DNPLUS_PROB_SOLV)               guide.  <         A.1.2 Establishing a Dynamic Asynchronous Connection  E               A dynamic asynchronous DECnet connection is a temporaryuI               connection between two nodes, usually over a telephone linecH               through the use of modems. You can switch the line at eachE               end of the connection from a terminal line to a dynamicoI               asynchronous DECnet line. A dynamic asynchronous connectionaH               is usually maintained only for the duration of a telephone               call.e  G               Dynamic switching of terminal lines to asynchronous DDCMPLF               lines can occur between DECnet-Plus systems or between aG               DECnet-Plus system and a non DECnet-Plus system. AssumingiF               that both the remote node and the local node are OpenVMSE               operating systems, the system manager at each node must A               have loaded the asynchronous driver, asydriver, and H               installed the shareable images asyswitch and asydynswitch.I               (If the local node is a personal computer, there is no needhE               to load asydriver and install asydynswitch.) The systemnE               manager at the remote node must have enabled the use of H               virtual terminals on the system. First, the system managerG               must have enabled virtual terminals by issuing the sysgensH               connect command. The system manager must also have enabledD               virtual terminals on the system. The terminal devices,F               which you plan to use for dynamic connections, should be4               set up with the /disconnect qualifier.  1         A-10 Configuring Asynchronous Connectionso s  n      I                                      Configuring Asynchronous ConnectionscI                                       A.1 Asynchronous DECnet Connectionst    F                 ________________________ Note ________________________  B                 Any OpenVMS node that supports DECnet asynchronous?                 connections can initiate a dynamic asynchronouse.                 connection to an OpenVMS node.  F                 ______________________________________________________  G               Setting up a dynamic asynchronous connection involves twoa%               distinct sets of steps.o  ?               1. At some point, you must configure your dynamic @                  asynchronous line. See Section A.1.2.1 for more(                  information about this.  F               2. You dynamically switch the line to a DECnet line. SeeA                  Section A.1.2.2 for more information about this.t  ;         A.1.2.1 Setting Up Dynamic Asynchronous Connectionst  E               Use the following steps to manually set up your dynamicfE               asynchronous line any time prior to the dynamic switch.nH               This example assumes the local OpenVMS node is originatingC               the connection and switching the terminal line on for F               DECnet use. The connection must be to an OpenVMS node onE               which you have an account with net$decnetaccess rights.i  C               To set up a dynamic asynchronous connection, you must_C               execute the instructions discussed in this section atdF               both the local and remote OpenVMS systems. If the remoteH               system is a system other than OpenVMS, refer to the remoteG               system's documentation for information about setting up a .               dynamic asynchronous connection.  F                 ________________________ Note ________________________  =                 If you use the net$configure.com procedure toy@                 set up your dynamic asynchronous lines, then theE                 net$startup.com and wandd$startup.com procedures loaddA                 the asydriver, install the asynchronous shareablee8                 images, and configure the lines for you.  F                 ______________________________________________________  C               1. Log in to the SYSTEM account on your OpenVMS node.s  I                                 Configuring Asynchronous Connections A-11  e  i      ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet ConnectionsS    G               2. DECnet must be running on both nodes for the remainingaF                  steps. If not already done, you and the remote systemB                  manager must start up the network by entering the#                  following command:   +                  $ @sys$startup:net$startupn  9               3. Load the asynchronous driver, asydriver.m  B                  Enter the following commands at your terminal (orB                  include them in the sys$manager:systartup_vms.com?                  command procedure before you boot the system):_  (                  $ run sys$system:sysgen@                  SYSGEN> connect asy0/noadapter/driver=asydriver                  SYSGEN> exitc  F                  The asynchronous driver must be loaded before you can2                  make any asynchronous connection.  I               4. Next, install the asynchronous shareable images. Use the_#                  following command:   H                  $ install add sys$library:asyswitch.exe/open/head/share  U                  $ install add sys$library:asydynswitch.exe/open/head/share/protectedf  A                  The following commands enable the use of virtualrH                  terminals for the terminal line that is to be switched,G                  and set the disconnect characteristic for the terminalcC                  line. (The virtual terminal capability permits thesE                  process to continue running if the physical terminal@5                  you are using becomes disconnected.)s  (                  $ run sys$system:sysgen?                  SYSGEN> connect vta0/noadapter/driver=ttdriver                   SYSGEN> exits  X                  $ set terminal/eight_bit/permanent/modem/disconnect terminal-port-name:  D                  terminal-port-name is the name of the terminal portE                  on the remote node to which the dynamic asynchronous @                  connection is made. The terminal-port-name, for)                  instance, could be txa3.n  F               5. After you load asydriver and install the asynchronousH                  shareable images, you need to preconfigure the protocolD                  stack for the dynamic asynchronous line. A protocolI                  stack for a dynamic asynchronous connection is a routing G                  circuit that is mapped to a ddcmp logical station. Thee  1         A-12 Configuring Asynchronous Connections            I                                      Configuring Asynchronous ConnectionsaI                                       A.1 Asynchronous DECnet Connectionsc    H                  ddcmp logical station uses a modem connect line createdD                  with the communications port attribute specified asI                  either async or async-terminal_name (for example: async- F                  tx-0-3). You must configure the protocol stack beforeH                  you switch the dynamic asynchronous line into operationH                  by means of the DCL set terminal command. The following.                  steps explain how to do this.  I                  If the configuration procedures have not already creatednD                  the Modem Connect module, create it manually beforeG                  configuring the line. Use the following example to set 9                  up the necessary modem connect entities:n  %                  $ run sys$system:ncll  @                  ncl> create modem connect line dynamic_asynch -<                  _ncl> communications port async_port_name 1  F                  ncl> set modem connect line dynamic_asynch speed 2400  >                  ncl> enable modem connect line dynamic_asynch  H                  1  In dynamic asynchronous connections, you can specifyG                     the communications port attribute (async_port_name) F                     in one of two ways when creating the modem connect                      line entity:  F                     o  async - When you specify async, a unique numberD                        is given to the modem connect line as an "-n"D                        extension to the async name each time a modemH                        connect line with a communications port attributeE                        of ASYNC is created. This creates a "floating" A                        modem connect line, which is not tied to a E                        specific terminal device or unit. For example:   F                        ncl> create modem connect line dynamic_asynch -6                        _ncl> communications port async  I                        If you now display information about the port, you F                        will see that the line has a new communications9                        port name of async-n. For example:   V                        ncl> show modem connect line dynamic_asynch communications port  F                     o  async-dev-c-u - Specifying async-dev-c-u allowsC                        you to set up a dynamic protocol tower on ana%                        explicit line.   I                                 Configuring Asynchronous Connections A-13  U  t      ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connections     H                        For a dynamic line or circuit, the communications3                        port has one of two formats:a  +                        o  devcu as in txa0:   .                        o  dev-c-u as in tx-0-0  ;                        where dev-c-u is defined as follows:c  E                        dev  The first two letters of the asynchronous H                             device name (possible values are tt and tx).  F                        c    A decimal number (0 or a positive integer)G                             designating a device's hardware controller. H                             If the third letter of the device name is A,I                             c equals 0. If the third letter of the device =                             name is B, c equals 1, and so on.   D                        u    The unit number of the device name; u isD                             always equal to 0 or a positive integer.  F                        ncl> create modem connect line dynamic_asynch -=                        _ncl> communications port async-tx-0-3   E                  If you request a specific device, txa3 (with the set G                  terminal command; see Section A.1.2.2, step 13), for afE                  dynamic asynchronous connection, the asydriver firstcB                  searches for an available modem connect line withD                  a communications port attribute of async-tx-0-3. IfE                  this search fails, the asydriver then searches for arI                  "floating" modem connect line with a communications portnF                  attribute of async-n. If asydriver finds a "floating"G                  line, it uses it. For the duration of this connection,iH                  the communications port attribute is modified to async-B                  tx-0-3 so you can tell which terminal devices areC                  actively running dynamic asynchronous connections.   B                  If asydriver does not find a "floating" line, theA                  dynamic switch fails. Either you have set up thetF                  protocol stack incorrectly, or else all modem connect"                  lines are in use.  H               6. Next, configure your data link and routing circuit. ForI                  information about configuring your data link and routinglG                  circuit, see the chapters on managing network security H                  and network management tasks in the <REFERENCE>(DNPLUS_&                  OVMS_NET_MGMT) guide.  1         A-14 Configuring Asynchronous Connections$ n  s      I                                      Configuring Asynchronous Connections I                                       A.1 Asynchronous DECnet Connections_    C               7. For security over a dialup connection, run NCL and E                  establish optional routing initialization passwords.tI                  For more information about using verifiers, refer to the 9                  <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide.   =         A.1.2.2 Switching on Dynamic Asynchronous Connections   G               This section explains how to dynamically switch your linee                for communication.  G               Figure A-1 shows a typical configuration in which dynamicoI               asynchronous switching occurs over a dialup line. The localnH               node in Figure A-1 is a standalone VAXstation 3100 system;H               the remote node is a VAX 8800. After the user at the localH               node dials in to the remote node, he or she can switch theH               lines connected to terminal ports tta2 and txb1 to dynamic!               asynchronous DDCMP.l  @         Figure A-1 Dynamic Switching of Asynchronous DDCMP Lines          D               1. The following steps can be performed by any OpenVMS                  user.  H               2. Log in to your local OpenVMS system. This login createsC                  a process (identified by Process_L in Figure A-1).t  1               3. Enter the following DCL command:   3                  $ set host/dte terminal-port-name:n  F                  terminal-port-name is the name of your local terminalI                  port that is connected to the modem. If both systems usenF                  modems with autodial capabilities (for example, DF03,H                  DF112, or DF224 modems), you can optionally include theE                  /dial qualifier on the set host/dte command to causecF                  automatic dialing of the modem on the remote node, as                  follows:.        I                                 Configuring Asynchronous Connections A-15n           ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connectionse    F                  $ set host/dte/dial=number:number terminal-port-name:  A               4. If you do not specify the /dial qualifier in theaF                  previous step, dial the remote system manually. AfterI                  the dialup connection is made and you receive the remotetF                  system welcome message, log in to your account on theI                  remote node. In this case, you supply your user name and A                  password to the remote OpenVMS operating system.t  G               5. If you are not using automatic dialing, dial in to the &                  remote node manually.  G               6. Once the dialup connection is made and you receive thetF                  remote OpenVMS system welcome message, log in to yourG                  account on the remote node. This process is identifiedc,                  by Process_R in Figure A-1.  F               7. You can initiate the dynamic switch by specifying the:                  following DCL command on the remote node:  5                  $ set terminal/network/switch=decnet   G                  The set terminal command is an OpenVMS DCL command. If F                  you are on a node other than an OpenVMS node, specify9                  the equivalent function for your system.s  C               8. When the SET image on the remote system recognizeseE                  the /NETWORK and /switch=decnet qualifiers, it calls G                  the shareable image asydynswitch (see Figure A-1). The I                  asydynswitch image verifies the link and sends an escapeiG                  sequence to the terminal emulator on the local system. I                  The escape sequence notifies the local terminal emulator I                  that the line connected to the remote system is becoming -                  a dynamic asynchronous line.u  H               9. When the terminal emulator at the local system receivesE                  the escape sequence, it calls the asydynswitch image_G                  (see Figure A-1) on the local system. The asydynswitchAI                  image verifies the line on the local system and switchesc3                  it to an asynchronous DECnet line.n  F              10. When the switch occurs on the local system, asydriver?                  first searches for an explicitly named dynamictA                  asynchronous line. For example, if the switch isn?                  on device tta1:, it searches for a line with a B                  communications port attribute of async-tt-0-1. IfC                  asydriver cannot find that line, it searches for aeD                  "floating" line (created with a communications port  1         A-16 Configuring Asynchronous Connections  t  a      I                                      Configuring Asynchronous ConnectionsnI                                       A.1 Asynchronous DECnet Connectionsa    I                  attribute of async). Because a protocol stack previouslyyE                  had been preconfigured over this line, the data linkd9                  protocol now attempts to start the link.n  B              11. The local system then sends a ddcmp start messageE                  (see Figure A-1) to the remote system that initiatedoD                  the dynamic switch. When asydynswitch on the remoteC                  system detects the start message, it activates the E                  preconfigured local protocol stack. (For information.E                  about the protocol stack, see Section A.1.2.1, stepsn                  5-7.)  C                  The remote system first searches for an explicitlycF                  named dynamic asynchronous line. When it searches forF                  an explicitly named dynamic line, it searches for oneD                  that refers to the physical terminal over which theD                  original switch was made. In Figure A-1, the remoteF                  system searches for a line associated with port txb1.E                  Therefore, it looks for a line with a communicationsnI                  port attribute of async-tx-1-1. If it does not find one, F                  it uses a "floating" async-n line. If this fails, the&                  dynamic switch fails.  A              12. Since both ends of the link have a preconfigurednC                  protocol stack, the DECnet link comes up over both G                  circuits. Any preconfigured security checks also occury                  at this time.  B                  The following message indicates that the terminalE                  emulator on the local system has exited and that the 2                  DECnet link is being established:  B                  %REM-S-END - control returned to local-nodename::                  $  F                  To check whether the communications link has come up,C                  specify the following command on the local system:e  %                  $ run sys$system:nclo  U                  ncl> show routing circuit dynamic_asynch adjacency adjacent-node all                   ncl> exit  G                  If there is an adjacency, you can start to communicate D                  with the remote system over the asynchronous DECnet                  connection.  I                                 Configuring Asynchronous Connections A-17            ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connectionsr    D              13. As an alternative to switching the terminal line toE                  a DECnet line automatically, you can switch the linecF                  manually. If you originate a dynamic connection to anF                  OpenVMS node from a system other than OpenVMS, manualE                  switching is required; from an OpenVMS system, it iseE                  optional. If you are originating the connection fromdB                  a node other than OpenVMS, follow system-specificI                  procedures to log in to the remote OpenVMS node by means '                  of terminal emulation._  I                  Once you are logged in to the remote node, two steps areM/                  required for manual switching:g  B                  a. Using your account on the remote OpenVMS node,I                     specify the set terminal command described in Step 7, G                     but add the /manual qualifier. For more informationa0                     see Section A.1.2.1, Step 5.  ?                     $ set terminal/network/switch=decnet/manualn  C                     You will receive the following message from the I                     remote node indicating the remote system is switchingo+                     its line to DECnet use:t  U                     %SET-I-SWINPRG The line you are currently logged over is becomingm0                                    a DECnet line  I                  b. You should exit from the terminal emulator and switch:F                     your line manually to a DECnet line. The procedureI                     depends on the specific operating system on which your"                     are logged in.  C                     The following example shows how an OpenVMS user,C                     originating a dynamic connection exits from the C                     terminal emulator and turns on the DECnet line.y  A                     1. Exit from the terminal emulator: Press andaF                        hold down the Control key while you press the \>                        (backslash) key on your OpenVMS system.  A                     2. Enter the following command to switch your ?                        terminal line to a DECnet line manually:   3                        $ set terminal/network tta0:t  I                        tta0 is the name of the terminal port on the local@                        node.  1         A-18 Configuring Asynchronous Connectionss s  e      I                                      Configuring Asynchronous Connections I                                       A.1 Asynchronous DECnet Connectionsn    A                     3. Next, you must manually turn on the lines,oD                        data links, and routing circuits connected toC                        your terminal port. See Steps 5 through 7 inoE                        Section A.1.1 for information about setting upd5                        your static asynchronous link.   G                        Asynchronous DECnet is then started on the localo$                        OpenVMS node.  7         A.1.2.3 Managing Dynamic Asynchronous Resources   B               You can define the following system logical names inG               sys$manager:net$logicals.com to manage the resources used 3               by a dynamic asynchronous connection:i  %               o  asy$dynamic_maxlines   E                  Specifies the maximum number of dynamic asynchronous F                  modem connect lines that can be active on a system atE                  any one time. You can specify values in the range of E                  0-65534 lines. The default is 16 lines. For example:   8                  $ define/system asy$dynamic_maxlines 16  )               o  asy$dynamic_line_timeoutu  G                  Specifies the amount of time in seconds that a dynamichG                  asynchronous line waits before deciding that a dynamiciE                  connection has broken. When the dynamic asynchronousi@                  line decides that a link is broken, the line isD                  automatically switched back to a terminal line. YouI                  can specify values in the range of 10-65535 seconds. Thea5                  default is 300 seconds. For example:o  =                  $ define/system asy$dynamic_line_timeout 300   =         A.1.2.4 Terminating a Dynamic Asynchronous Connection   =               Take the following steps to terminate a dynamic &               asynchronous connection:  F               1. Disable the modem connect line and then re-enable it.                  For example:   %                  $ run sys$system:ncln  ?                  ncl> disable modem connect line dynamic_asynchr  =                  ncl> enable modem connect line terminal_linew                  ncl> exit  I                                 Configuring Asynchronous Connections A-19o p  f      ,         Configuring Asynchronous Connections+         A.1 Asynchronous DECnet Connections     G               2. Switch your asynchronous line back to a terminal line.   P                  $ set terminal/permanent/nonetwork/typeahead terminal_port_name  H               The dynamic asynchronous connection can also terminate, ifF               the time specified by the logical name asy$dynamic_line_G               timeout expires. The link is considered idle if it has no I               input or output for the timeout interval. When this occurs,mI               the link is broken and the line automatically switches fromtI               a DECnet line back to a terminal line. For more information B               about asy$dynamic_line_timeout, see Section A.1.2.3.  G         A.1.2.5 Reasons for Failure of Dynamic Asynchronous Connections_  E               If you are using dynamic switching and the asynchronousi8               DECnet connection is not made, check that:  .               o  DECnet-Plus has been started.  (               o  WANDD has been started.  B               o  The asydriver has been loaded (the asy0 device is                  present).  2               o  The asyswitch has been installed.  5               o  The asydynswitch has been installed.c  H               o  The modem connect lines have been configured correctly.  E               o  Virtual terminals must be enabled both on the remote G                  node and, in particular, for the terminal at which youvI                  are logged in. The terminal line at the remote node muste3                  have the attribute disconnect set.   H               o  After you enter a set terminal command with the /manualH                  qualifier, you must specify NCL commands to turn on theG                  DECnet line within approximately 2 minutes or the line *                  returns to terminal mode.  G               If the logical station is in the on-starting state, check                that:   E               o  The routing circuits have been configured correctly.   G               o  The routing initialization passwords on each node mustsI                  be set correctly. (Refer to the <REFERENCE>(DNPLUS_OVMS_d"                  NET_MGMT) guide.)  1         A-20 Configuring Asynchronous Connectionst -         I                                      Configuring Asynchronous Connections I                                       A.1 Asynchronous DECnet Connections     H               o  The parity is correct. Asynchronous DECnet requires theF                  parity on the asynchronous line to be set to none andH                  the terminal line to be set up to use 8-bit characters.F                  If you are using a non OpenVMS system, you must checkE                  that the terminal line is set to the correct parity.t  I               For more information about solving problems in your DECnet- F               Plus network, refer to the <REFERENCE>(DNPLUS_PROB_SOLV)               guide.                                                                        I                                 Configuring Asynchronous Connections A-21o c  e                    I                                                                         B I         _________________________________________________________________o  I                                                    Configuring Transports              B.1 Overview  D               To configure NSP Transport, OSI Transport, DECnet overC               TCP/IP, or OSI over TCP/IP on your system, invoke the F               sys$manager:net$configure using the ADVANCED option, andC               select Option 4 ("Configure Transports"). Section 1.4 C               and Section 1.5 in this manual describe in detail therD               questions net$configure asks in order to configure theG               transports. DIGITAL recommends that you do not modify the E               NSP and OSI startup scripts that net$configure creates.rH               (These scripts in SYS$MANAGER are named NET$NSP_TRANSPORT_E               STARTUP.NCL and NET$OSI_TRANSPORT_STARTUP.NCL.) DIGITALoF               also recommends that you accept the default settings for%               the various attributes.   C               This appendix describes the NCL commands that you can C               use to manually create and modify these transports if F               necessary. Refer to <REFERENCE>(DNPLUS_NCL_REF) for more5               information about transport attributes.o  $         B.2 Manually Configuring NSP  A               This section describes how to configure the NetworkoF               Services Protocol (NSP). The following example shows theG               commands to create the nsp entity on your system. DIGITALhF               recommends that you accept the default settings (used inF               the example) for the various attributes and change theseG               only if you need to. Refer to the <REFERENCE>(DNPLUS_NCL_ ?               ref) for more information about these attributes.               I                                                Configuring Transports B-1s                    Configuring Transports$         B.2 Manually Configuring NSP                   ncl> create nspa  >               ncl> set nsp delay factor 2, delay weight 3, - 1T               _ncl> maximum remote nsaps 200, maximum transport connections 200, - 2:               _ncl> maximum window 20, nsap selector 32, -*               _ncl> retransmit threshold 5               ncl> enable nsp   >               1  The effect of delay factor is to increase theE                  retransmission time by increasing the average round-sF                  trip delay time, thus allowing for additional network                  delay.o  B                  The value of the weighting factor is given by theE                  delay weight characteristic. Basically, delay weighteI                  determines how quickly the retransmission timer responds$F                  to variations in actual round-trip delay times. A lowD                  value of delay weight means that the retransmissionD                  timer responds quickly to each sample of round-tripG                  delay time; a delay weight of 0 means that an estimate G                  is nearly the same as the last actual sample of round- F                  trip delay. A high value for delay weight reduces theI                  impact of recent variations in network delay; the higherIH                  the value, the closer each estimate of round-trip delay4                  is to the average of all estimates.  D                  The default values of delay factor and delay weightH                  should be suitable for most networks. However, considerH                  increasing these values if there are wide variations in8                  round-trip delay times on your network.  G               2  You can save memory resources by reducing the value ofhF                  maximum remote nsaps. However, you do not have accessF                  to the information provided by this entity's countersE                  and status attributes (except through information ineH                  event logs). The maximum NSAPs must be greater than the.                  maximum transport connection.  I               For some NSP characteristics, such as maximum remote nsaps,iD               or maximum transport connections, you can raise valuesG               at any time, but you cannot lower the value without firste               disabling NSP.      "         B-2 Configuring Transports o         I                                                    Configuring TransportsoI                                              B.2 Manually Configuring NSPn    ?               The following is an example of how to set up NSP:.                 ncl> create nspe+               ncl> set nsp maximum window 8e<               ncl> set nsp maximum transport connections 2007               ncl> set nsp maximum receive buffers 2000c               ncl> enable nspfM               ncl> create session control transport service nsp protocol %x04h  )         B.2.1 Transmit and Receive Window   E               NSP receiver's window is controlled by a combination ofsI               Maximum Transport Connections, Maximum Receive Buffers, ande               Maximum Window.n  B               The receiver initial quota is determined by dividingG               Maximum Receive Buffers by Maximum Transport Connections. C               During the life of the connection, the receiver quota D               fluctuates, using the value of Maximum Receive BuffersH               divided by Currently Active Connections. The credit windowI               sent to the remote transmitter may or may not be this quota I               value, depending on the value of Maximum Window. If Maximum G               Window is set to less than the determined receiver quota, F               this value is used instead for the credit granted to the!               remote transmitter.t  G               The transmitter on an NSP connection uses the credit senttC               by the remote receiver as its transmit window, unless D               Maximum Window is a lower value. In that case, Maximum8               Window is used for the transmitter window.  G               By controlling the transmitter's and receiver's window as.H               above a dynamic balance of system resource consumption andA               network performance may be achieved and maintained.m  :         B.3 Manually Configuring the OSI Transport Service  G               This section describes how to configure the OSI transport I               service. The following example shows the commands to createeI               the osi transport entity on your system. DIGITAL recommendstH               that you accept the default settings (used in the example)E               for the various attributes and change these only if youoH               need to. Refer to the <REFERENCE>(dnplus_ncl_ref) for more1               information about these attributes.   I                                                Configuring Transports B-3d m  s               Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    <               The characteristics specified in the followingB               command example are those that apply to all types ofB               network service. For details of osi transport entityF               characteristics that are specific to Connection-OrientedC               Network Service (CONS) or Connectionless-Mode NetworksA               Service (CLNS), see Section B.3.2 or Section B.3.3.a  '               ncl> create osi transport   G               ncl> set osi transport delay factor 4, delay weight 5,- 1 L               _ncl> maximum receive buffers 96, maximum remote nsaps 64, - 2G               _ncl> maximum transport connections 33, maximum window 20c  '               ncl> enable osi transport   >               1  The effect of delay factor is to increase theE                  retransmission time by increasing the average round- F                  trip delay time, thus allowing for additional network                  delay.f  B                  The value of the weighting factor is given by theE                  delay weight characteristic. Basically, delay weightnI                  determines how quickly the retransmission timer respondsoF                  to variations in actual round-trip delay times. A lowD                  value of delay weight means that the retransmissionI                  timer responds very quickly to each sample of round-trip G                  delay time; a delay weight of 0 means that an estimate G                  is nearly the same as the last actual sample of round- F                  trip delay. A high value for delay weight reduces theI                  impact of recent variations in network delay; the higher H                  the value, the closer each estimate of round-trip delay4                  is to the average of all estimates.  D                  The default values of delay factor and delay weightH                  should be suitable for most networks. However, considerE                  increasing its value if there are wide variations ina8                  round-trip delay times on your network.  D                  For a complete discussion of delay factor and delayG                  weight and how to calculate round-trip delay, refer toi3                  <REFERENCE>(DNPLUS_OVMS_NET_MGMT).   G               2  You can save memory resources by reducing the value of H                  maximum remote nsaps. However, you will not have accessF                  to the information provided by this entity's countersE                  and status attributes (except through information inrF                  event logs). The maximum remote NSAPs cannot be lower8                  than the maximum transport connections.  "         B-4 Configuring Transports           I                                                    Configuring TransportseI                        B.3 Manually Configuring the OSI Transport Service     F               You must disable the osi transport entity before you can0               modify any of its characteristics.  )         B.3.1 Transmit and Receive Windowl  @               OSI transport receiver's window is controlled by aC               combination of Maximum Transport Connections, MaximumtG               Receive Buffers, and Maximum Window. The receiver initial E               quota is determined by dividing Maximum Receive BuffersaB               by Maximum Transport Connections. During the life ofF               the connection, the receiver quota fluctuates, using theC               value of Maximum Receive Buffers divided by Currently F               Active Connections. The credit window sent to the remoteG               transmitter may or may not be this quota value, depending I               on the value of Maximum Window. If Maximum Window is set to I               less than the determined receiver quota, this value is used G               instead for the credit granted to the remote transmitter.S  E               The transmitter on an OSI transport connection uses theuH               credit sent by the remote receiver as its transmit window,C               unless Maximum Window is a lower value. In that case, @               Maximum Window is used for the transmitter window.  G               By controlling the transmitter's and receiver's window as H               above a dynamic balance of system resource consumption andA               network performance may be achieved and maintained.n  I               The following NCL script creates and sets up OSI transport,yG               including the Connection-Oriented Network Service (CONS),s@               and the Connectionless-mode Network Service (CLNS)               services.                             I                                                Configuring Transports B-5n c  x               Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    (         ncl> create node 0 osi transport=         ncl> create node 0 osi transport application osit$ivp ^         ncl> set node 0 osi transport application osit$ivp file name sys$test:osit$ivpresp.comN         ncl> set node 0 osi transport application osit$ivp user name "systest"Z         ncl> set node 0 osi transport application osit$ivp called tsels {%X564f5453495650}@         ncl> create node 0 osi transport template osit$loop_clnsU         ncl> set node 0 osi transport template osit$loop_clns network service clns, -          _ncl> classes {4}, -$         _ncl> expedited data true, -          _ncl> checksums false, -         _ncl> inbound false, -         _ncl> loopback true   @         ncl> create node 0 osi transport template osit$loop_consU         ncl> set node 0 osi transport template osit$loop_cons network service cons, -           _ncl> classes {4,2,0}, -$         _ncl> expedited data true, -          _ncl> checksums false, -         _ncl> inbound false, -         _ncl> loopback true   >         ncl> create node 0 osi transport template osit$rfc1006V         ncl> set node 0 osi transport template osit$rfc1006 network service RFC1006, -         _ncl> classes {0}, -         _ncl> inbound true  B         ncl> create node 0 osi transport template osit$rfc1006plusZ         ncl> set node 0 osi transport template osit$rfc1006plus network service RFC1006, -         _ncl> classes {2}, -(         _ncl> RFC1006 port number 399, -         _ncl> inbound true  D         ncl> set osi transport RFC1006 listener ports = { 102, 399 }(         ncl> enable node 0 osi transport  A         B.3.2 Configuring the Connection-Oriented Network Servicet  B               The following sections describe how to configure theC               Connection-Oriented Network Service (CONS). CONS is ayF               network service that operates according to a connection-H               oriented model. Before data can be exchanged, a connectionC               must first be established. X.25 provides this type ofn               service.    "         B-6 Configuring Transports s  e      I                                                    Configuring TransportsyI                        B.3 Manually Configuring the OSI Transport Service     <         B.3.2.1 Establishing Outbound Connections Using CONS  E               To establish an outbound transport connection that usesnA               CONS as its network service, an application makes au7               connection request in which it specifies:   C               o  The OSI transport address of the destination host.   I               o  The OSI transport service access point identifier (TSAP- D                  ID) of the remote application. A TSAP-ID identifiesC                  a TSAP. A TSAP is a unique identifier for a singleq                   transport user.  C               o  Optionally, other transport connection parameters.   4               The OSI transport address consists of:  E               o  The name of the OSI transport template to be used insC                  setting up the transport connection. The specifiedrE                  OSI transport template must have its network servicei,                  characteristic set to cons.  ?               o  A network address that uniquely identifies theVA                  destination host. The network address for a CONSg-                  connection is a DTE address.   C               OSI transport either creates a new network connection D               (using either X.25 or X25 Access), or uses an existingA               outbound network connection (provided the transport D               connection is class 2 or class 4). If a new connectionF               is to be created, X.25 uses the DTE address from the OSIH               transport address and the X25 Access template specified inH               the OSI transport template to set up a network connection.  ;         B.3.2.2 Establishing Inbound Connections Using CONSg  ;               To establish an inbound transport connection:o  C               1. OSI transport must be listening to one or more X25                    Access filters.  I                  X.25 or X25 Access passes calls from these filters up too                  OSI transport.   F               2. OSI transport must have an OSI transport template forE                  CONS connections with its inbound characteristic set_G                  to TRUE. This OSI transport template must also specify E                  an X25 Access template with the same name (includingcH                  matching case) as the X25 Access filter on which a call                  arrives.s  I                                                Configuring Transports B-7D t  ,               Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    >               3. If a suitable OSI transport template for CONSE                  connections is found, it is used to accept the call,rC                  using the X25 Access template specified in the OSI $                  transport template.  H               4. The incoming transport connection can then be received.B                  If an application is found to receive the inboundB                  request, the application can accept or reject the                  request.   H               5. If the application accepts the inbound request, the OSIH                  transport template for CONS connections is used for the                  accept.  G               For incoming connections to applications that are invoked F               by passive TSAP association, you must also configure oneI               or more OSI transport application entities to represent the G               passive association between a TSAP-ID and an application.eF               Refer to the <REFERENCE>(DNPLUS_OVMS_NET_MGMT) guide for>               information about managing application entities.  5         B.3.2.3 Manually Configuring Support for CONSv  G               To configure CONS support, each element in the set of therE               CONS filters attribute of the OSI transport entity mustoF               have a corresponding X25 Access filter of the same name.I               By default, the CONS filters attribute of the OSI transportr-               entity is set to OSI transport.g  I               Similarly, the CONS template attribute of the OSI transportfI               template subentity must contain a name that is a PSI filter D               and is contained in the set of CONS filters of the OSIF               transport entity. The default value of the CONS templateE               attribute of an OSI transport template subentity is OSIy               transport.  I               The following steps list the commands required to configure I               CONS. The characteristics added or set up for OSI transport I               in this example are relevant to CONS. In addition, consideriG               setting some of the more general characteristics shown iny               Section B.3.  F               For the variables, substitute values appropriate to yourC               configuration. DIGITAL recommends that you accept the D               default settings (used in the example) for the variousG               attributes. Change them only if you need to. Refer to thed  "         B-8 Configuring Transports    e      I                                                    Configuring Transports I                        B.3 Manually Configuring the OSI Transport Service     D               <REFERENCE>(dnplus_ncl_ref) guide for more information%               about these attributes.e  B               1. The following example shows how to create the OSIF                  transport module, set its characteristics, and enable                  it.  *                  ncl> create osi transport  D                  ncl> add osi transport cons filters {filter-name} 1  B                  ncl> set osi transport disconnect holdback 0, - 2V                  _ncl> maximum multiplexing 65535, maximum network connections 65535 3  *                  ncl> enable osi transport  H                  1  Specifies the names of one or more X.25 filters usedI                     to listen for incoming transport connection requests.uE                     If you do not specify any X.25 filters, a defaultt8                     filter called OSI transport is used.  H                  2  Set a high value for disconnect holdback if you wantI                     to keep idle network connections. This saves the cost I                     of re-establishing network connections. You should beiH                     aware, however, that this is unnecessarily costly if8                     the network connection remains idle.  I                     Set disconnect holdback to 0 if you want to lose idle <                     network connections as soon as possible.  G                     disconnect holdback is supported only for transport -                     protocol classes 2 and 4.   F                  3  Sets the value of maximum multiplexing. IncreasingF                     the value saves on the cost of network connectionsA                     but reduces the throughput for each transport >                     connection that uses a multiplexed network                     connection.o  H                     maximum multiplexing is supported only for transport-                     protocol classes 2 and 4.   I                     If you set maximum network connections too low, localdE                     transport users might be unable to make transporttG                     connection requests, particularly if all the activeiA                     network connections are inbound. For example,cD                     if the limit is 7 and there are 7 active networkH                     connections, all inbound, then local transport usersG                     will be unable to make transport connections unlessmD                     you either increase the value of maximum network  I                                                Configuring Transports B-9e    n               Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    D                     connections or one of the network connections is.                     released by a remote host.  B               2. The following example shows how to create the OSI%                  transport templates:   C                  ncl> create osi transport template template-name 1   @                  ncl> set osi transport template template-name -5                  _ncl> acknowledgment delay time 1, - 8                  _ncl> checksums false, classes {4}, - 2U                  _ncl> cons template osi transport, cr timeout 30, er timeout 30, - 3p  T                  _ncl> inbound true, initial retransmit time 15, loopback false, - 4C                  _ncl> keepalive time 60, maximum nsdu size 2048, - E                  _ncl> network service cons, retransmit threshold 8 5)  A                  ncl> enable osi transport template template-nameo  E                  1  OSI transport templates are used by OSI transportoG                     to supply connection parameters not provided by the 9                     requesting OSI transport application.   D                     An OSI transport template name must contain onlyH                     alphanumeric characters, underscores (_), hyphens (-H                     ), or dollar ($) signs. OSI transport template names?                     should not be more than 16 characters long.   @                     You can configure two types of OSI transport3                     templates for CONS connections:c  4                     o  For outbound connections only  G                        You can configure as many outbound OSI transportc-                        templates as you want.o  @                     o  For both outbound and inbound connections  I                        You should configure a single outbound-inbound OSIlI                        transport template for each X25 Access filter used>8                        by inbound transport connections.  D                  2  Including checksums reduces data throughput. UseE                     checksums only if you have reason to believe thata:                     data will be corrupted by the network.  D                  3  The default value for cr timeout is adequate forC                     most networks. However, consider increasing the I                     value if you find that a high proportion of transport <                     connection requests are being timed out.  #         B-10 Configuring Transports  g  m      I                                                    Configuring TransportshI                        B.3 Manually Configuring the OSI Transport Servicea    H                  4  When true, inbound specifies that this OSI transportI                     template for CONS connections can be used for inboundt4                     as well as outbound connections.  G                     The default initial retransmit time value should beeI                     suitable for most networks. It is set to a relatively C                     high value to reflect the fact that a transport D                     connection request Transport layer protocol dataE                     unit (TPDU) usually has a longer round-trip delaydF                     than a data TPDU. Consider increasing the value ifF                     transport connection requests frequently time out.  G                     You can set up different OSI transport templates toiG                     provide different values of this characteristic for D                     networks with significantly different round-tripH                     delay. For example, round-trip delay on an X.25 PSDNA                     is usually much greater than on an 802.3 LAN.   A                  5  network service cons indicates that transport A                     connections set up using a specified template E                     will use CONS. An OSI transport template for CONSoA                     connections configured with the net$configure E                     procedure have this characteristic set correctly.MH                     However, if you create a CONS OSI transport templateG                     directly, you must set this characteristic, becauseyI                     the default is CLNS. The default value for retransmit C                     threshold should be suitable for most networks. G                     However, consider increasing the value for networks ;                     with a high probability of losing data.   I               3. The following example creates the X25 Access module, and                   enables it:  '                  ncl> create x25 access '                  ncl> enable x25 accessu  I               4. The following example shows how to create the x25 access 6                  template and set its characteristics:  @                  ncl> create x25 access template template-name 1  =                  ncl> set x25 access template template-name -aG                  _ncl> call data hex-string, dte class dte-class-name 2e  H                  1  Outbound transport connections that use X.25 networkB                     connections use X25 Access templates to supplyE                     most of the parameters for setting up the networksB                     connection. Inbound transport connections that  I                                               Configuring Transports B-11i w                  Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    D                     use X.25 connections use X25 Access templates to<                     negotiate network connection parameters.  I                     Each OSI transport template for CONS connections thatpE                     you configure names an X25 Access template in itsrF                     cons template characteristic. You must, therefore,G                     configure each of the X25 Access templates named in F                     your OSI transport templates for CONS connections.  G                  2  When you create an X25 Access template for use withgG                     CONS, set the value of the call data characteristic F                     to %X03010100. The destination host will recognizeD                     this value as indicating that the call should be#                     passed to CONS.d  I               5. The following example shows how to create the x25 accessn                  filter:  <                  ncl> create x25 access filter filter-name 1  9                  ncl> set x25 access filter filter-name ->F                  _ncl> call data mask mask, call data value value, - 27                  _ncl> inbound dte class dte-class-name   A                  1  If your system is to accept inbound transport G                     connections over X.25 network connections, you needtG                     to configure one or more X25 Access filters. An X25eI                     Access filter listens for incoming network connection0I                     requests and passes these requests to the appropriate-C                     destination. One or more X25 Access filters are D                     required for each X25 Access DTE class that CONS!                     wants to use.e  D                     Each outbound-inbound OSI transport template forE                     CONS connections that you configure specifies thetG                     name of an X25 Access template in its cons templateoI                     characteristic. This X25 Access template will be used E                     to accept an inbound network connection. The name G                     of this X25 Access template must be the same as the H                     name of an X25 Access filter that is used to receive0                     inbound network connections.  I                  2  When you create an X25 Access filter for use by CONS,O5                     set call data mask to %Xffffffff.   I                     When you create an X25 Access filter for use by CONS,e6                     set call data value to %X03010100.  #         B-12 Configuring Transports. 2  r      I                                                    Configuring TransportsrI                        B.3 Manually Configuring the OSI Transport Serviceu    B         B.3.3 Manually Configuring the Connectionless-Mode Network               Service   B               The following sections describe how to configure theC               Connectionless-Mode Network Service (CLNS). CLNS is a C               network service that operates according to a datagram @               model. Each message is routed and delivered to itsF               destination independently of any other. When using CLNS,A               only TP4 is available in the default configuration.   <         B.3.3.1 Establishing Outbound Connections Using CLNS  E               To establish an outbound transport connection that uses A               CLNS as its network service, an application makes ah7               connection request in which it specifies:   C               o  The OSI transport address of the destination host.O  E               o  The TSAP-ID of the responding application. A TSAP-IDnG                  identifies a TSAP. A TSAP is a unique identifier for a '                  single transport user.   C               o  Optionally, other transport connection parameters.s  4               The OSI transport address consists of:  @               o  The name of the OSI transport template for CLNSC                  connections to be used in setting up the transportaA                  connection. The specified OSI transport templatecC                  for CLNS connections must have its network service ,                  characteristic set to clns.  D               o  An address that uniquely identifies the destination*                  host. The address can be:  I                  -  An NSAP (for a transport connection using CLNS/ES-IS)n  H                  -  A LAN address (for a transport connection using CLNS'                     with Null Internet)n  E               The Routing module selects a routing circuit to be usedoG               for the underlying network connection; the basis for thismE               selection is the area address part of the NSAP address.X    I                                               Configuring Transports B-13t                    Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    ;         B.3.3.2 Establishing Inbound Connections Using CLNSR  D               To establish an inbound transport connection that uses               CLNS:i  @               1. The Routing module passes an incoming transportE                  connection to OSI transport. OSI transport must have H                  an OSI transport template for CLNS connections with itsE                  inbound characteristic set to TRUE. If the transportiA                  connection uses Null Internet, the OSI transportIF                  template for CLNS connections must also have its clnsE                  inactive area address characteristic set to the samepI                  area address as the inactive area address characteristic I                  of the routing circuit on which the transport connection                   arrived.   >               2. If a suitable OSI transport template for CLNSI                  connections is found, an application is found to process E                  the connection. The application can either accept or '                  reject the connection.o  C               3. If the application accepts the connection, the OSIiC                  transport template for CLNS connections is used tos'                  accept the connection.i  *         B.3.3.3 Steps for Configuring CLNS  F               The following steps show the commands to configure CLNS.E               The characteristic added or set up for OSI transport inEE               this example is relevant to CLNS. In addition, consider G               setting some of the more general characteristics shown inp               Section B.3.  F               For the variables, substitute values appropriate to yourC               configuration. DIGITAL recommends that you accept the D               default settings (used in the example) for the variousG               attributes. Change them only if you need to. Refer to the D               <REFERENCE>(DNPLUS_ncl_ref) guide for more information%               about these attributes.   G               1. The following example creates the OSI transport moduleP                   and enables it:      #         B-14 Configuring TransportsO           I                                                    Configuring Transports I                        B.3 Manually Configuring the OSI Transport Servicen    *                  ncl> create osi transport  :                  ncl> set osi transport nsap selector 33 1*                  ncl> enable osi transport  I                  1  nsap selector is used for transport connections usingi                     CLNS/ES-IS.o  B               2. The following example shows how to create the OSI@                  transport template and set its characteristics:  C                  ncl> create osi transport template template-name 1c  2                  ncl> set osi transport template -5                  _ncl> acknowledgment delay time 1, -nW                  _ncl> checksums false, classes {4}, clns inactive area address {}, - 2   W                  _ncl> inbound true, initial retransmit time 15, keepalive time 60, - 3 X                  _ncl> loopback false, network service clns, retransmit threshold 8, - 4C                  _ncl> security empty, use clns error reports false   3                  ncl> enable osi transport templatea  E                  1  OSI transport templates are used by OSI transportiG                     to supply connection parameters not provided by then9                     requesting OSI transport application.r  D                     An OSI transport template name must contain onlyH                     alphanumeric characters, underscores (_), hyphens (-H                     ), or dollar ($) signs. OSI transport template names?                     should not be more than 16 characters long.f  @                     You can configure two types of OSI transport3                     templates for CLNS connections:   >                     o  For outbound transport connections only  G                        You can configure as many outbound OSI transport B                        templates for CLNS connections as you want.  >                     o  For both outbound and inbound transport"                        connections  E                        A CLNS OSI transport template is configured totI                        use either the CLNS/ES-IS or Null Internet Routingr                         Protocol.  C                        If you configure Null Internet OSI transport I                        templates, you must configure one outbound-inboundnD                        OSI transport template for each inactive area$                        address used.  I                                               Configuring Transports B-15                     Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    C                  2  Including checksums reduces data throughput, sonG                     you should use checksums only if you have reason touG                     believe that data will be corrupted by the network.c  G                  3  The default initial retransmit time value should beoI                     suitable for most networks. It is set to a relativelymE                     high value because a transport connection requestfE                     TPDU usually has a longer round-trip delay than aFI                     data TPDU. Consider increasing the value if transportn<                     connection requests frequently time out.  E                  4  The default value for retransmit threshold shouldcD                     be suitable for most networks. However, considerA                     increasing the value for networks with a high /                     probability of losing data.   B               3. The following example shows how to set up routingF                  for end systems using the Connectionless-mode Network                  Service.   1                  ncl> create routing type endnode   I                  ncl> set routing dna address format true, lifetime 63, -oE                  _ncl> manual network entity titles {}, probe rate 20e  $                  ncl> enable routing  D               4. The following example shows how to set up a routingF                  circuit for end systems using the Connectionless-mode!                  Network Service.>  ?                  ncl> create routing circuit hdlc-0 type hdlc 1   C                  ncl> set routing circuit hdlc-0 data link entity -cC                  _ncl> hdlc link hdlc-0 logical station hdlc-0, - 2s:                  _ncl> manual data link sdu size 1492, - 3/                  _ncl> template template-name 4   3                  ncl> enable routing circuit hdlc-0   ;                  1  You need to configure routing circuits:   I                     o  For CLNS connections over a LAN. You can configure D                        a routing circuit for each LAN device on yourD                        system. Each LAN routing circuit supports theE                        CLNS/ES-IS Routing Protocol; it can optionally 2                        also support Null Internet.  #         B-16 Configuring Transportsn b  o      I                                                    Configuring TransportsfI                        B.3 Manually Configuring the OSI Transport Service     G                     o  For CLNS connections over synchronous links. YouuG                        can configure two types of synchronous circuits:m                          -  HDLC                          -  DDCMPi  A                     o  For CLNS connections over an X.25 network.i  C                        You can configure four types of X.25 routingo                        circuit:   I                        -  Static outgoing (for outbound connections only)   H                        -  Static incoming (for inbound connections only)  I                        -  Dynamic assigned (for both outbound and inbounde&                           connections)  B                        -  Permanent (for both outbound and inbound&                           connections)  C                     The following table lists the supported routingr&                     circuits for CLNS.  I                     _____________________________________________________sI                     Circuit____________________Description_______________n  B                     csma-cd                    LAN routing circuit  G                     hdlc                       Synchronous HDLC circuiti  H                     ddcmp                      Synchronous DDCMP circuit  C                     x.25 static incoming       X.25 inward switchedo>                                                virtual circuit  D                     x.25 static outgoing       X.25 outward switched>                                                virtual circuit  D                     x.25 da                    Dynamic assigned X.25>                                                virtual circuit  E                     x.25 permanent             Permanent X.25 virtualPI                     ___________________________circuit___________________i  H                  2  The data link entity characteristic is valid for all                     circuits.i  F                     For broadcast circuits, this characteristic is set                     to:w  0                     csma-cd station station-name  E                     where station-name is the generic name of the LAN 4                     adapter (for example, csmacd-0).  I                                               Configuring Transports B-17                     Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    E                     For hdlc circuits, this characteristic is set to:d  D                     hdlc link link-name logical station station-name  C                     where link-name is the generic name of the linkCF                     (for example, hdlc-0) and the logical station (for%                     example, hdlc-0).   F                     For ddcmp circuits, this characteristic is set to:  E                     ddcmp link link-name logical station station-name   C                     where link-name is the generic name of the link G                     (for example, ddcmp-0) and the logical station (fore&                     example, ddcmp-0).  E                     For x.25 circuits, this characteristic is set to:a                       x25 access  I                  3  The manual data link sdu size characteristic is valid %                     for all circuits.   B                  4  The template characteristic is ignored for LAN>                     circuits and valid for all other circuits.  G                  Table B-1 lists additional characteristics to considerxE                  when setting up a routing circuit with CLNS. It alsoaE                  shows the circuits for which the characteristics aren                  valid.s                              #         B-18 Configuring Transportsu h  e      I                                                    Configuring Transports I                        B.3 Manually Configuring the OSI Transport Service     F               Table B-1 Additional Routing Circuit Characteristics forI               __________CLNS_____________________________________________X  I               Characteristic_____________Valid_Circuit_Type______________m  0               idle timer                 x.25 da  0               inactive area address      csma-cd  =               initial minimum timer      x.25 static incoming =                                          x.25 static outgoing 0                                          x.25 da  0               manual routers             csma-cd  =               maximum call attempts      x.25 static outgoingn  0               maximum svc adjacencies    x.25 da  =               recall timer               x.25 static outgoings  0               reserved adjacency         x.25 da  0               reserve timer              x.25 da  =               x25 filters                x.25 static incomingaI               ___________________________x.25_da_________________________e  +                  For inactive area address:   B                  Each LAN circuit that supports Null Internet must;                  specify a different inactive area address.   H                  For circuits using only CLNS/ES-IS, this characteristic=                  is an empty set (this is the default value).1  +                  For initial minimum timer:   D                  On X.25 static incoming or outgoing circuits, if noH                  adjacency has been established when this timer expires,(                  the circuit is cleared.  I               5. The following example configures a reachable address for )                  an X.25 routing circuit.   F                 ________________________ Note ________________________  E                 You have to configure a reachable address only if you D                 have configured one or more dynamic assigned routing                 circuits.   F                 ______________________________________________________  I                                               Configuring Transports B-19                     Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    5                  ncl> create routing circuit hdlc-0 -2>                  _ncl> reachable address reachable-address - 16                  _ncl> address prefix address-prefix 2  2                  ncl> set routing circuit hdlc-0 -2                  _ncl> dte addresses dte-addresses  5                  ncl> enable routing circuit hdlc-0 -k(                  _ncl> reachable address  D                  1  If you configure a dynamic assigned X.25 routingE                     circuit, you must configure one or more reachableoD                     addresses to be used to manage the circuit. EachD                     reachable address specifies a mapping of an NSAP-                     address to a DTE address..  B                  2  Specify the address prefix when you create theF                     entity. You cannot modify this characteristic with$                     the set command.  H               6. The following example creates the X25 Access module and                  enables it:  '                  ncl> create x25 accessu'                  ncl> enable x25 accesse  I               7. The following example shows how to create the x25 access46                  template and set its characteristics:  @                  ncl> create x25 access template template-name 1  =                  ncl> set x25 access template template-name - =                  _ncl> destination dte address dte-address, - /                  _ncl> dte class dte-class-namei  F                  1  A routing circuit that invokes outbound X.25 callsE                     uses an X25 Access template to supply most of thePI                     parameters for setting up the call. A routing circuit G                     that receives inbound X.25 calls uses an X25 Accessl:                     template to negotiate call parameters.  I                     Each X.25 routing circuit that you configure names anIG                     X25 Access template in its template characteristic.sG                     You must therefore configure each of the X25 AccesstB                     templates named in your X.25 routing circuits.  #         B-20 Configuring Transportsc a  r      I                                                    Configuring TransportssI                        B.3 Manually Configuring the OSI Transport Service     E               8. The following example creates the x25 access filter:-  <                  ncl> create x25 access filter filter-name 1  9                  ncl> set x25 access filter filter-name - ;                  _ncl> inbound dte class dte-class-name,  -o6                  _ncl> sending dte address dte-address  .                  ncl> enable x25 access filter  F                  1  A routing circuit that receives inbound X.25 callsC                     requires one or more X25 Access filters. An X25pG                     Access filter listens for incoming calls and passes 8                     them to the appropriate destination.  F                     Each X.25 static-incoming or X.25 dynamic-assignedD                     routing circuit that you configure specifies theH                     name of one or more X25 Access filters in its filterF                     characteristic. You must, therefore, configure the1                     specified X25 Access filters.r  H                     When setting up a filter for use with an x.25 staticG                     incoming or x.25 da circuits, specify the followingo-                     X25 Access filter values:a  *                     o  call data mask %xff  +                     o  call data value %x81t  F         B.3.3.4 Providing Communications Between OSI Transport Systems+                 and VOTS Systems Using CLNS   H               If you need communication between a VOTS system and an OSIE               transport system using the full Internet CLNS protocol,tI               you must use an intermediate system (router). OSI transporteE               implements only the Internet protocol. An OSI Transport G               system has no way of finding another end system that doesoE               not support ES-IS without using an intermediate system.h  F               If a DEC WANrouter is used as an intermediate system, itI               must be configured as a link state router (see the previous                section).o  I               If the VOTS system and the DEC WANrouter reside on the sameSE               LAN subnetwork and the VOTS system is configured with alI               DNA-compatible NSAP address, the DEC WANrouter need only be -               configured as a level 1 router.   I                                               Configuring Transports B-21                     Configuring Transports:         B.3 Manually Configuring the OSI Transport Service    D               If the VOTS system does not have a DNA-compatible NSAPI               address, or if the VOTS system and the DEC WANrouter do not G               reside on the same LAN subnetwork, the DEC WANrouter must 0               be configured as a level 2 router.  C               When using a level 1 router, you must create a manual E               adjacency on the router for the VOTS system. When usingMC               a level 2 router, you must create a reachable addressnF               on the router for the VOTS system. See the DEC WANrouterG               configuration and management guides for details about how F               to configure manual adjacencies and reachable addresses.  H               OSI transport systems and VOTS systems on the same LAN canH               communicate without an intermediate system, using the Null%               Internet CLNS protocol.a  C         B.4 Manually Configuring OSI Transport Network Applications   E               This section describes how to configure applications toeG               receive connection requests from remote hosts. One of theeI               attributes of a transport connection request is a transportaG               service access point identifier (TSAP-ID), which uniquelyaH               identifies the transport application on the remote host to;               which the connection request is to be passed.   I               An application that expects to receive a connection requestpE               must therefore associate itself with a particular TSAP- D               ID, so the transport service knows which application a<               particular connection request is intended for.  F               There are two ways in which an application can associateB               itself with a TSAP-ID: active association or passive               association.  E               Active association is entirely under the control of theaG               transport user, and requires no support from you. PassiveaI               association, on the other hand, requires that you configure F               the osi transport application entities that describe the<               association between TSAP-IDs and applications.  E               In active association, the transport application issues D               a $qio(io$_acpcontrol) system service call in which itF               requests an association with a specified TSAP-ID. When aE               connection request arrives with that TSAP-ID, a mailboxoE               message containing details of the connection request is H               sent to the associated application, which can then process<               the request, either accepting or rejecting it.  #         B-22 Configuring Transportsm t  o      I                                                    Configuring Transports I               B.4 Manually Configuring OSI Transport Network Applications     F               OSI transport dynamically creates the osi transport portI               entity so that the active association is available by meansu$               of network management.  @               In passive association, you create a osi transport@               application entity, whose characteristics specify:                 o  A TSAP-ID.n  6               o  The name of an image or command file.  E               o  The user name of an account under which the image orl(                  command file is to run.  C               When a connection request arrives with a TSAP-ID thatFD               is associated with a osi transport application entity,B               the transport service creates a new process in whichE               it runs loginout.exe. loginout.exe validates any accesslI               control information and invokes DCL to execute the image or G               command file associated with that TSAP-ID. Details of the H               connection request are passed in the logical name sys$net.  A               The following command example shows the commands tos@               configure an osi transport application entity. ForB               the variables, substitute values appropriate to yourI               configuration. DIGITAL, however, recommends that you accept H               the default settings (used in the example) for the variousG               attributes and change these only if you need to. Refer tosH               the <REFERENCE>(DNPLUS_NCL_REF) for more information about               these attributes.   '               ncl> create osi transport '               ncl> enable osi transporth  D               ncl> create osi transport application application-name  C               ncl> set osi transport application application-name - 7               _ncl> called tsels set-of-hex-string, - 19A               _ncl> file name file-spec, user name user-account 2   3               ncl> enable osi transport application   F               1  called tsels specifies the set of TSAP-IDs with which1                  this entity is to be associated.g  E               2  file name specifies the name of the command or imagerA                  file to be executed when a connection request istG                  received with a TSAP-ID that matches one of the values 4                  of the called tsels characteristic.  I                                               Configuring Transports B-23                     Configuring TransportsC         B.4 Manually Configuring OSI Transport Network Applicationsr    E                  user name specifies the user account under which thes'                  application is to run.c  8         B.4.1 Customizing End Selector for OSI Transport  ?               The network service access points (NSAP) selector E               determines which transport service is used by a network E               connection. The default NSAP selector for DIGITAL's OSI F               transport implementations is 33 (decimal). Other vendorsG               might use different NSAP selectors and might require thatr'               the NSAP selectors match.   E               You can only change the NSAP selector for OSI transport F               when OSI transport is disabled. Valid NSAP selectors areF               in the range from 2 to 255, with the exception of 32. InI               order to maintain interoperability between DNA Phase IV and B               DECnet-Plus, you cannot use NSP's NSAP selector, 32.  G               The command to change the NSAP selector for OSI transport_               is:p  (               ncl> disable osi transportF               ncl> set osi transport nsap selector new_selector_number  '               ncl> enable osi transporti  0         B.4.2 Enabling Use of CLNS Error Reports  H               OSI transport can recognize the unavailability of a remoteG               node during connection establishment using CLNS (Routing)                error reports.  >               This feature is disabled for all templates (used?               by DNA Session Control), but you can enable it by B               editing the OSI transport NCL initialization script,F               sys$manager:net$osi_transport_startup.ncl, and using the;               following command to set the default to true:   S               ncl> set osi transport template default use clns error reports = true   H         B.5 Using DECnet over TCP/IP (RFC 1859) and OSI over TCP/IP (RFC             1006)   C               DECnet-Plus for OpenVMS allows you to run DNA and OSItD               applications over an IP network backbone. Applications<               include those supplied by DIGITAL, third-party:               applications, and user-written applications.  #         B-24 Configuring Transports            I                                                    Configuring TransportsrI    B.5 Using DECnet over TCP/IP (RFC 1859) and OSI over TCP/IP (RFC 1006)     ?               RFC 1006 and RFC 1859 (formerly known as RFC 1006 E               Extension) are standards of the Internet community. RFC F               1006 defines how to implement ISO 8073 Class 0 on top ofG               TCP. Hosts that implement RFC 1006 are expected to listen                on TCP port 102.  H               RFC 1859 defines how to implement ISO 8073 Transport ClassE               2 Non-use of Explicit Flow Control on top of TCP. HostsnH               that implement RFC 1859 are expected to listen on TCP port               399.  >               The DECnet over TCP/IP feature (RFC 1859) allowsG               traditional DECnet applications (such as MAIL, CTERM, andtI               FAL) to accept IP names and addresses. The OSI applications D               over TCP/IP feature (RFC 1006) allows OSI applicationsE               (such as FTAM and VT) to accept IP names and addresses.e  2         B.5.1 Configuring RFC 1006 and/or RFC 1859  >               If you want to use DECnet over TCP/IP and/or OSIE               applications over TCP/IP, invoke net$configure.com with B               the ADVANCED option, and select Option 4 ("Configure@               Transports") to configure (or reconfigure) the OSID               transport. You can then create a new OSI transport NCLG               script (or replace the old script). You must also include B               Domain in your Session Control naming search path byC               selecting Option 2 to rename your node using a Domain D               secondary node name. This is described in Section 2.2.  D               For the changes to take effect, either disable the OSID               transport entity (if it exists) and invoke the new OSI9               transport NCL script, or reboot the system.n  (               ncl> disable osi transport?               ncl> do sys$manager:net$osi_transport_startup.ncl   H               When configuring RFC 1006, RFC 1859, or both, each elementI               in the set of RFC 1006 listener ports attribute corresponds-H               to a TCP listener port. By default, net$configure sets theG               OSI transport RFC 1006 listener ports attribute to { 102,mG               399 }. Port 102 is required for RFC 1006, and port 399 isy$               required for RFC 1859.      I                                               Configuring Transports B-25t c  c               Configuring TransportsN         B.5 Using DECnet over TCP/IP (RFC 1859) and OSI over TCP/IP (RFC 1006)    F         B.5.2 Creating Additional OSI Transport Templates for RFC 1006               and RFC 1859  E               To create RFC 1006 or RFC 1859 templates in addition to D               the default templates, use Option 4 under the ADVANCEDH               configuration option. When the net$configure.com procedureF               asks you if you want to create additional OSI templates,F               answer yes. Then select RFC 1006 as the network service.  E               The RFC 1006 port number attribute of the OSI transport.G               template subentity must contain a TCP port number that is H               one of the chosen RFC 1006 or RFC 1859 listener ports. TheE               default value for the RFC 1006 port number attribute is G               102. If you create an OSI transport template subentity torF               use with DECnet over TCP/IP (RFC 1859), then set the RFCA               1006 port number attribute of that template to 399.   /         B.5.3 Disabling DECnet-Plus over TCP/IPr  H               DECnet-Plus only attempts to locate TCP/IP if the RFC 1006I               listener ports attribute set of the OSI transport entity isa               not empty.  C               To disable RFC 1006 and RFC 1859, issue the following                command:  >               ncl> set osi transport rfc1006 listener ports {}                                    #         B-26 Configuring Transports                                  F      _________________________________________________________________  F                                                                  Index      ?      A                                 Asynchronous connections <      _______________________________     configuration,  A-1;      Active association                  configuring,  1-13 B        network applications, B-22        dynamic description,  A-1A        TSAP, B-22                        static description,  A-1 C      Address Format Worksheet,           terminating dynamic,  A-19 F         12-11                          Asynchronous driver,  A-6, A-128      ADVANCED configuration option,    Asynchronous lineB         2-15                             communications port,  A-7<        invoking, 1-1                   Asynchronous software:      Alternate node synonym               components,  A-36         directory                      AutoconfiguringA        defining logicals, 2-15           network addresses,  1-10 ?        format for defining, 2-15       Autodial protocol,  A-15i:        when used, 2-15                 Automatic switching@      Application database                of terminal line,  A-16          configuring, 3-39F      Application entities              B______________________________6        reconfiguring with site-        Base components:          specific NCL scripts,           configuring,  2-1:          3-47                               advanced,  1-1B      application entity,  B-8, B-23    BASIC configuration option,.        configuring, B-23                  2-15        creating, B-232F      asy$dynamic_line_timeout          C______________________________,         logical name, A-19             Cable9      asy$dynamic_maxlines logical        null modem,  A-5uB         name, A-19                     called tsels characteristicD      asydriver asynchronous driver,      network applications,  B-23/         A-10, A-20                     Changingg>      asydynswitch image,  A-16           configuration of base  ;                                             components, 3-5   F                                                                Index-1    e              B         Changing (cont'd)                 CMIP Management Listener  3          VAX P.S.I. configuration,          See CMLd5             4-42                          CML account =         Characters                          configuring, 1-29.;          valid for full name,  1-6        Command procedure D         Checklist                           decnet_migrate.exe, 2-15E          X.500 configuration,  12-9         decnet_register.exe, 2-15nC         Checksum, B-10                      psi$configure.com, 4-33i9         checksums characteristic            PSI$CTP, 4-41nH          CLNS,  B-16                        systartup_vms.com, A-6, A-122          CONS,  B-10                      Commands/         Circuit                             DCL F          configuring,  B-16                    for starting FTAM, 11-6F         Circuit cost                           for starting OSAK, 11-6D          specifying,  1-14                     for starting VT, 11-6F         circuit entity                         for stopping FTAM, 11-6J          characteristics,  B-16                @sys$startup:osak$start.com8          creating,  B-16                         ,  11-6@         CLNS                                SYSMAN IO AUTO, 1-19=          and VOTS,  B-21                  communications portnB          checksums characteristic,          asynchronous line, A-7B             B-16                            synchronous line, A-137          configuring,  1-26, B-13,        ConfigurationnF             B-14                            application database, 3-399          error reports                      changing, 3-5iA             enabling,  B-24                    the directory name ?          inbound connections,  B-14              services,  3-7 F          initial retransmit time               the system's namespace,4             characteristic,  B-16                3-7F          outbound connections,  B-13           the system's node name,4          retransmit threshold                    3-7I             characteristic,  B-16              the system's node synonym, 4          routing circuit                         3-7A             characteristics,  B-18          choosing options, 3-1 E          supported circuit types,           cluster alias, 1-31, 3-48 D             B-17                            DECdns clerk-only systemA          X.25,  B-17                           joining LAN DECdnst@          X.25 filter entity,  B-21               namespace,  1-1A          X.25 routing circuit                  joining WAN DECdns.A             configuring,  B-19                   namespace,  3-10nA          X.25 template entity,  B-20        DECdns namespace, 2-4e@         Cluster alias                       DECdns server systemF          configuring,  1-31, 3-48              joining existing DECdnsA                                                  namespace,  3-12 8                                             DECdts, 3-20           Index-2l d  s              5         Configuration (cont'd)            ConfiguringaC          devices,  3-13                     OSI transport templates 6          event dispatcher,  1-29, 3-33        (cont'd)9          flowchart,  4-3, 7-3                  CONS, B-10pI          inactive area address,  1-27       reachable addresses for CLNS,t2          modifying,  3-1 to 3-58              B-20:          MOP client database,  3-44         RFC 1006, 1-28@          network addresses,  1-9            the search path, 2-9B          NSP transport,  1-21               time zone differential;          of base components,  2-1             factors,  1-7 8             advanced,  1-1                  X.25 filters9          of DECnet over X.25,  1-15,           CONS, B-12a>             8-4                             X25 Access filters9          of network,  1-1 to 1-36              CONS, B-21s@          of X.25,  8-4                      X25 Access templates9          OSI transport,  1-22                  CLNS, B-20r9          procedure                             CONS, B-11 B             main menu,  3-5               Configuring asynchronous>             menu options,  3-5               connections, 1-13G          reachable address prefix,        Configuring data links,  1-14 F             1-18                          Configuring DECnet over X.25>          reachable addresses,  1-17         Alpha system, 1-15D          routing protocol,  1-26          Configuring devices,  1-13G          search path information,  2-9    Configuring routing circuits,e1          selection weight,  1-32             1-14oE          steps to changing,  3-1          Connection Oriented Networks4          transports,  3-14                   Service$          X.25 access template,  1-164         Configuring                         See CONS  H          applications,  B-23              Connectionless Network Service4          asynchronous connections,          See CLNSE             A-1                           Connectionless-mode Networkn4          circuits,  B-16                     Service4          CLNS,  1-26, B-13, B-14            See CLNS4          CLNS and VOTS,  B-21             CONS,  B-6E          CONS,  1-27, B-6, B-8              checksums characteristic,r2          DECnet over X.25 VAX system,         B-10A             1-19                            configuring, B-6, B-8 F          network applications,  B-22        cr timeout characteristic,2          NSP                                  B-10G             transport service,  B-1         filters characteristic, B-9 H          OSI transport,  B-9                inbound characteristic, B-10D             service,  B-3                   inbound connections, B-7C          OSI transport templates            initial retransmit timeeC             CLNS,  B-15                       characteristic,  B-11o  I                                                                   Index-3c    w              ;         CONS (cont'd)                     Creating (cont'd)l  ?          OSI transport templates            OSI transport, B-14iE             configuring,  B-10              osi transport entity, B-3iC          outbound connections,  B-7         OSI transport template,l8          retransmit threshold                 B-10, B-15F             characteristic,  B-11           X.25 filter for CLNS, B-21F          summary of management tasks,       X.25 filter for CONS, B-12H             B-6                             X.25 template for CLNS, B-20H          X.25 access template entity,       X.25 template for CONS, B-11@             B-11                          Current base component:         cons filters characteristic,         configuration9           B-10                              changing, 3-5s  !         cr timeout characteristiccI          CONS,  B-10                      D______________________________ 4         create command                    Data links=          nsp,  B-1                          configuring, 1-14a5          osi transport,  B-4, B-9         DCL commandeC          osi transport application,         set host/dte in networke?             B-23                              operations,  A-15oC          osi transport for CLNS,  B-14      set terminal in networkhD          osi transport template for           operations,  A-6, A-12A             CLNS,  B-15                   De-installation example 5          osi transport template for         X.25, 7-4eB             CONS,  B-10                   DECdns clerk-only systemH          routing circuit for CLNS,          joining LAN DECdns namespace?             B-16                               configuring, 1-1BH          routing, for CLNS,  B-16           joining WAN DECdns namespace@          x25 access filter for CLNS,           configuring, 3-10:             B-21                          DECdns full nameA          x25 access filter for CONS,        valid characters, 1-6 :             B-12                          DECdns namespace<          x25 access for CLNS,  B-20         configuring, 2-4E          x25 access for CONS,  B-11         creating a new namespace,i1          x25 access template for CLNS,        2-3 >             B-20                          DECdns server systemC          x25 access template for CONS,      joining existing DECdnsi7             B-11                              namespace @         Creating                               configuring, 3-120          DECdns namespace,  2-4           DECdts=          Local namespace,  2-2              configuring, 3-2058          namespace                        DECnet over IP8             during initial                  see RFC 10067                configuration,  2-3          see RFC1006.          NSP entity,  B-1n           Index-4P l  o              D         DECnet over X.25                  Displaying information for>          configuring,  1-15, 8-1             search path, 2-10C          configuring (Alpha system),      DNA address format,  1-11 D             1-15                          DNA format for NETs,  1-107          configuring (VAX system),        DNS version 1oG             1-19                            namespace preparation, 2-17rH          example configuration,  8-4        using with DECdns Version 2,2         DECnet-Plus for OpenVMS               2-160          dynamic asynchronous             Domain?             connection,  A-16               node synonyms, 2-13eG         decnet_migrate.exe, 2-15            synonyms search path namingnE         decnet_register                       template support,  2-14t0          export file,  2-19               DriverE          import file,  2-19                 asynchronous driver, A-6,C2          namespace management tool,           A-12>             2-8                           Dynamic asynchronous<         decnet_register.exe, 2-15            connection, A-1B         delay factor characteristic,        automatic switching ofB           B-4                                 terminal line,  A-16D         Delay factor characteristic         establishing, A-10, A-11G          NSP,  B-2                          establishing automatically,)2         delay weight characteristic,          A-11H           B-4                               manual switching of terminal9          NSP,  B-2                            line,  A-18 I         delete command                      preconfiguring protocol stack :          ddcmp link,  A-8                     ,  A-4, A-12E          modem connect line,  A-8           reasons for failure, A-20 G          routing circuit,  A-8              switching of terminal line,l2         Devices                               A-10G          configuring,  1-13, 3-13           switching on the line, A-15.=          reconfiguring,  3-13               terminating, A-19o9         Dialup line                         timeout, A-19MD          using for dynamic                Dynamic asynchronous modem:             asynchronous connections,        connect lines@             A-10                            maximum number, A-19H          using for static asynchronous    Dynamic Asynchronous Resources:             connection,  A-5, A-6           managing, A-19;         Directory Name Services           Dynamic switching/D          changing,  3-7                     procedure for line, A-10         disable commandn          ddcmp link,  A-8p"          modem connect line,  A-8,             A-19    I                                                                   Index-5i (  r              G                                           Example de-installation,  7-7n1         E______________________________   Exiting I         Emulator                            from VAX P.S.I. configurationn<          terminal,  A-15                      program,  4-37?         enable command                    Expedited data,  1-28r<          modem connect line,  A-19        Export file,  2-19A          nsp,  B-1                          decnet_register, 2-19 B          osi transport,  B-4, B-9         Extended addresses,  1-9  #          osi transport application, I             B-23                          F______________________________   5          osi transport for CLNS,  B-14    FAL accountd=          osi transport template for         configuring, 1-29gD             CLNS,  B-15                   FDDI large packet support,1          osi transport template for          1-14r>             CONS,  B-10                   File Access Listener3          routing circuit for CLNS,          See FAL B             B-16                          file name characteristicF          routing, for CLNS,  B-16           network applications, B-237          x25 access filter for CLNS,      filter entitydC             B-21                            creating for CLNS, B-218C          x25 access filter for CONS,        creating for CONS, B-12iD             B-12                            modifying for CLNS, B-21D          x25 access for CLNS,  B-20         modifying for CONS, B-12.          x25 access for CONS,  B-11       FTAMB          x25 access template for CLNS,      starting, with networkA             B-20                              startup file,  11-66:          x25 access template for CONS,      stopping, 11-63             B-11                          Full nametA         Enabling the nsp entity, B-1        valid characters, 1-6 "         Enabling the osi transportI           entity,  B-4                    G______________________________rC         End node information              Greenwich Mean Time (GMT)D<          specifying,  1-9                   definition, 3-20         End selectors, B-24 +         ESHello Timer                     HlI          routing default,  1-13           _______________________________l.         Event dispatcher                  HelpI          configuring,  1-29, 3-33           how VAX P.S.I. program works, 2         Event entities                        4-39!          reconfiguring with site- !             specific NCL scripts,>             3-47           Index-6o                   -                                           LNOTH         I______________________________     replaced by Local Namespace,  1         IDP                                   2-1 >          default,  1-9                    Local aliases,  2-149          standards,  1-9                  Local namespace 9          supplying,  1-9                    creating, 2-2i=         Import file, 2-19                   replaces LNO, 2-1u4          decnet_register,  2-19           Local time7         Inactive area address               configuring ;          configuring,  1-27                    as UTC, 3-25kG         inbound characteristic                 using established rules, 5          CONS,  B-10                             3-22E  #         Inbound connection request, I           B-22                            M______________________________ 6         Initial Domain Part               MAIL account=          see IDP,  1-9                      configuring, 1-30 =         initial retransmit time           Managing namespacesdE           characteristic                    decnet_register tool, 2-8aF          CLNS,  B-16                      Manual switching of terminal7          CONS,  B-11                         line, A-18n>         Initializing                      Manually configuringC          FTAM,  11-6                        network addresses, 1-10_>          OSAKserver,  11-6                maximum remote nsaps@         Installation                         characteristic, B-44          de-installation example,  7-7      NSP, B-23          for Alpha flowchart,  7-3        MigrationcC         Installation (VAX only)             using search path, 2-12 8          flowchart,  4-3                  MIRROR account=         Intermediate system, 1-10           configuring, 1-309  ;         IP                                Modem,  A-6, A-10l  :          using DECnet over                  autodial, A-15;             see RFC1006                     null cable, A-5 7                                           Modem Connect E         L______________________________     asynchronous connections,a1         LAN DECdns namespace                  A-4 3          joining,  1-1                    Modifying ;                                             nsp entity, B-1 E         License PAK                         osi transport entity, B-4r  H          see License Product                OSI transport template, B-10F             Authorization Key               X.25 filter for CLNS, B-21F         Link                                X.25 filter for CONS, B-12H          terminating dynamic                X.25 template for CLNS, B-20H             asynchronous,  A-19             X.25 template for CONS, B-11I                                             your VAX P.S.I. configuration,5                                               ,  4-42$  I                                                                   Index-76 -                 6         Modifying search path             NET (cont'd)F           information,  2-10                manually configuring, 1-10E         MOP client database                 transport selector field, 2          configuring,  3-44                   1-10;         MOP client entity                 net$configure.comcG          reconfiguring with site-           configuring DECdts portion,a2             specific NCL scripts,             3-20:             3-47                            main menu, 3-5=         Multihoming, 1-9                    menu display, 3-1U  =                                             menu options, 3-5s9         N______________________________     starting, 1-1oE         Name service                      net$startup startup script, 6          access features,  2-1               A-5, A-111          primary,  2-8                    Network 3          search path,  2-8                  addressrD          secondary,  2-8                       autoconfiguring, 1-10D         Namespace                              manually configuring,5          DECdns,  2-4                            1-10aD          directorypath,  3-8, 3-40          configuring address, 1-9=             valid characters in,  1-6     Network application,D          local,  2-2                        active association, B-22H          management tool                    called tsels characteristic,2             decnet_register,  2-8             B-23=          nickname,  3-8, 3-40               configuring, B-228E             valid characters in,  1-6       file name characteristic, 2          nodeobject,  3-8, 3-40               B-23E             valid characters in,  1-6       passive association, B-237E          preparation                        user name characteristic,t2             DNS version 1,  2-17              B-24H         Naming template                   Network configuration,  1-1 to1          setting up for search path,         1-36 B             2-12                            modifying, 3-1 to 3-58B          support for domain synonyms,     Network Control Language3             2-14                            See NCLe>         NCL                               Network service type<          creating site-specific search      CLNS, 1-25, 1-26<             path script,  2-11              CONS, 1-25, 1-27F          modified scripts                   RFC 1006, 1-28, B-25, B-269             executing,  3-5                 RFC1006, 1-25e3          site-specific scripts,  3-47     Node name A          user-defined scripts,  3-47        valid characters, 1-6vA         NET, 1-9                          Node synonym,  1-8, 3-8 ?          autoconfiguring,  1-10             local aliases, 2-14a          DNA format,  1-10          example,  1-10k           Index-8                    C         Node type                         OSI applications (cont'd)n1          specifying,  1-7                   CDROM D         Nondialup line                         EFT kit location, 9-2I          using for static asynchronous      configuring OSI applications, 2             connection,  A-6                  12-1@         NSAP, 1-9                           de-installing, 11-11H          address for CLNS,  B-13            disk space requirement, 10-6<          selector,  B-24                    distribution kit?             customizing,  B-24                 inspection, 10-1,A         NSP                                 EFT kit location, 9-2oB          creating,  B-1                     files installed, 11-12A          delay factor characteristic,       global pagelets, 10-3 >             B-2                             global pages, 10-3A          delay weight characteristic,       global sections, 10-3g9             B-2                             hardware, 9-2 8          enabling,  B-1                     installationF          maximum remote nsaps                  /DESTINATION qualifier,5             characteristic,  B-2                 11-2wD          modifying,  B-1                       EFT kit location, 9-2E         NSP transport                          installed files, 11-12 D          configuring,  1-21, 3-14              notifying users, 10-7F         Null modem cable, A-5                  /SOURCE qualifier, 11-2=                                                starting, 11-2wA         O______________________________        time required, 9-3 H         OpenVMS Cluster performance         installation procedure, 11-16           monitor                             to 11-12B          See VPM                            installation time, 9-3B         OpenVMS system                      installed files, 11-12=          asynchronous connection to         kit location, 9-2 E                                             memory requirements, 10-3 A             non VMS system,  A-5            notifying users, 10-7hF         OSAK                                online release notes, 10-2?          software installation              POLYCENTER Software C             process account quotas,           Installation Utility, 1                10-5                           9-2 D         OSAK$SERVER                         post-installation tasks,;          calculating process account          12-1 to 12-13 I             quota,  10-5                       configure OSI applications 8         OSAKserver                               ,  12-1<          stopping,  11-6                    pre-installationD         OSI applications                       accessing the release=          Authorize utility,  10-5                notes,  10-2 G          AUTOGEN utility,  10-4                disk space requirements,L5          bill of materials,  10-1                10-6.E          CD Reader,  9-2                       distribution kit, 10-1.  I                                                                   Index-9t l                 >         OSI applications                  osi transport entity9          pre-installation (cont'd)          creating, B-3i9             log in to privileged            enabling, B-4-:                account,  10-1               modifying, B-4  "             notifying users,  10-7I          prerequisite information         P______________________________   =             required hardware,  9-2       Passive association F             required software,  9-2         network applications, B-23;             synchronous interface           TSAP, B-8, B-23 2                card,  9-2                 Phase IV8          process account quotas,  10-4      address, 1-9F          product description,  9-1          compatible node name, 1-8,1          release notes,  10-2                 3-8 7             extracting to a file,           prefix, 1-9t=                10-2                       Phase IV addressing I             location,  10-2                 enabling on routing circuits,o2          required hardware,  9-2              1-147          required privileges,  10-1       PHONE accountg=          required software,  9-2            configuring, 1-30 .          software product description,    Port:             9-1                             terminal, A-153          software required,  9-2          Privilege H          system parameters                  required for VAX P.S.I. CTP,2             changing manually,  10-4          4-402          System Support Addendum,  9-2    Protocol:          time for installation,  9-3        autodial, A-15!          User Authorization File, I             10-5                          Q______________________________a2         OSI router, non-DNA, 1-10         QuittingI         osi transport                       from VAX P.S.I. configurationi<          example script,  B-5                 program,  4-38/         OSI transport                     QuotaLH          address,  B-7                      required for VAX P.S.I. CTP,2             for CLNS,  B-13                   4-40&          configuring,  1-22, 3-14, B-9          template,  B-7uI             configuring for CLNS,         R______________________________n  B                B-15                       Reachable address,  B-19=             configuring for CONS,           configuring, 1-17 F                B-10                         configuring for CLNS, B-202             creating,  B-10, B-15           prefix@             for CLNS connections,              configuring, 1-189                B-13                       Reconfiguration 9             modifying,  B-10                devices, 3-13              name,  B-10, B-15            Index-10 e  o                       Registering a nodeI          resolving problems,  2-19        S______________________________ 1         retransmit threshold              Scripts1F           characteristic                    creating for site-specific@          CLNS,  B-16                          search path,  2-11;          CONS,  B-11                      Search path,  2-8 <         RFC 1006                            configuring, 2-9I          configuring,  1-28, B-25           creating site-specific script-5          running OSI applications over        ,  2-11 H             IP backbone,  B-24              displaying information, 2-10G          using,  B-26                       modifying information, 2-10 D         RFC 1006 Extension                  naming template support,2          configuring,  B-25                   2-14E          running DECnet applications        primary name service, 2-8 G             over IP backbone,  B-24         secondary name service, 2-8 H         RFC 1859                            setting up naming templates,2          using,  B-26                         2-12D         Router, 1-10                        using to ease migration,2         Routing                               2-12H          circuit characteristics          Segregated mode routing,  1-11:             CLNS,  B-18                   Selection weight=          segregated mode,  1-11             configuring, 1-32 5         Routing circuits                  set commandlD          configuring,  1-14                 modem connect line, A-7,2          enabling Phase IV addressing,        A-134             1-14                            nsp, B-1C         Routing information                 osi transport, B-4, B-9 F          specifying,  1-8                   osi transport application,2         Routing module, B-16                  B-23F          reachable address,  B-19           osi transport template for9         Routing priority                      CLNS,  B-15 F          specifying,  1-14                  osi transport template for         Routing protocol9          configuring,  1-26                   CONS,  B-10 E         RPOA sequence number                routing CIRCUIT for CLNS, 2          VAX P.S.I.,  4-24                    B-16C         Running the configuration           routing, for CLNS, B-16mG           program                           x25 access filter for CLNS,t2          VAX P.S.I.,  4-33                    B-21G             privileges required,  4-33      x25 access filter for CONS, 2                                               B-12I                                             x25 access template for CLNS,x2                                               B-20I                                             x25 access template for CONS, 2                                               B-11  I                                                                  Index-11_ _  _              9         set host/dte command              System (cont'd)iG          using over the network,  A-15      configuring a node synonym,11         set terminal command, A-6             3-7 D          using over the network,  A-12      non VMS system connectedG         Starting                              asynchronously to OpenVMSN:          FTAM,  11-6                          system,  A-58          OSAKserver,  11-6                System manager?          VAX P.S.I. configuration           establishing staticiF             program,  4-33                    asynchronous connection,2         Startup script                        A-125          net$startup,  A-5, A-11          System time =         Static asynchronous connection      configuring, 3-201C           ,  A-1                            configuring local, 3-222>          establishing automatically,        configuring system;             A-5                                as UTC, 3-25 G          establishing manually,  A-6,          using established rules,a5             A-12                                 3-22 E          procedure for establishing,        configuring UTC as local,t2             A-5                               3-25"          reasons for failure,  A-9+          terminating,  A-8                T_I         Stopping                          _______________________________T0          FTAM,  11-6                      TCP/IPB          OSAKserver,  11-6                  running DECnet and OSIB          VT,  11-6                            applications over IP=         Switching of terminal line            backbone,  B-24r-          automatic,  A-16                 TDF1=          DCL set terminal command,          configuring, 3-20n<             A-3                             definition, 3-208          manual,  A-18                    Telephone line7          to a DECnet line,  A-3             dialup, A-5 9         Synchronous line                  template entity_C          communications port,  A-13         in OSI transport module =         SYS$LIBRARY:DNS$NS_DEF_                creating, B-15 A           FILE.DAT,  3-12                   in X.25 access module F         SYSGEN utility                         creating for CLNS, B-20F          autoconfigure all command,            creating for CONS, B-11G             1-20                               modifying for CLNS, B-20 G         SYSMAN IO AUTO command, 1-19           modifying for CONS, B-1112         systartup_vms.com command         TerminalH           procedure,  A-6, A-12             automatic switching of line,2         System                                A-16E          configuring a namespace,  3-7      manual switching of line, 2          configuring a node name,  3-7        A-186                                             port, A-15           Index-12    o              <         Terminal (cont'd)                 Transport (cont'd)  A          virtual,  A-12                     configuring NSP, 3-14lA         Terminal emulator, A-15             configuring OSI, 3-14oD         Terminal line                     Transport protocol classes=          asynchronous,  A-1                 configuring, 1-26 .         Terminating                       TSAPD          dynamic asynchronous link,         active association, B-22<             A-19                            identifier, B-22E         Testing                             passive association, B-2329          VAX P.S.I.,  4-39                  TSAP-ID, B-22 A         Time                              Type of network service <          configuring,  3-20                 CLNS, 1-25, 1-26<          configuring local,  3-22           CONS, 1-25, 1-27F          configuring system                 RFC 1006, 1-28, B-25, B-269             as UTC,  3-25                   RFC1006, 1-25 -             using established rules,      TZR-=                3-22                         configuring, 3-20 D          configuring UTC as local,          conventional for region,2             3-25                              3-21=         Time differential factor            customizing, 3-26 <          See TDF                            definition, 3-208         Time zone, 3-21                     format, 3-268          configuring differential           syntax, 3-26  +             factors,  1-7                 U I          rule,  3-29                      _______________________________ B             configuring,  3-20            user name characteristicF             conventional for region,        network applications, B-24I                3-21                       User-defined NCL scripts,  3-47 -             conventional rules            UTC,<                listed by region,  3-29      definition, 3-20E             customizing,  3-26              relationship to GMT, 3-206               format,  3-26 I             syntax,  3-26                 V______________________________-:         TP0                               Valid charactersG          configuring,  1-26                 for namespace nickname, 1-6u4         TP2                               VAX P.S.I.4          configuring,  1-26                 see X.25=         TP4                                 accessing systems =          configuring,  1-26                    security, 4-32 B         Transport                           application, 4-7, 4-19F          application                           command file, 4-7, 4-19;             identifying,  B-22                 filters, 4-7_E          configuring,  B-3                     incoming calls to, 4-7 9          configuring for CONS,  B-9            name, 4-19s"          configuring for NSP,  B-1  I                                                                  Index-13                    4         VAX P.S.I.                        VAX P.S.I.A          application (cont'd)               configuration programn6             security,  4-26                   (cont'd)E             type,  4-19                        reviewing information,r5             user name,  4-7, 4-19                4-35 E             X.25,  4-7                         scrolling, horizontal,c5             X.29,  4-7                           4-34 F          BCUG,  4-5                            sections, 4-4, 4-5, 4-6D          call characteristics,  4-7            sections required for=          call data,  4-23                         access, 4-5e@          call data mask,  4-21                    multihost, 4-5=          call data value,  4-21                   native, 4-5sH          called address extension           Configuration Test Procedure=             mask,  4-22                        See VAX P.S.I.-             value,  4-225          called NSAP                              CTP 7             filters,  4-22                  configuring B          calling address extension,            access systems, 4-1E             4-24                               multihost systems, 4-1-B          channel number                        native systems, 4-15             PVCs,  4-13                     CTP, 4-39iH          character-mode                        as a network object, 4-41A             terminals,  4-7                    preparations, 4-40 H          charging information,  4-24           privileges required, 4-40D          client filters,  4-7                  quotas required, 4-40F          configuration                         Receive Only mode, 4-41E             information required for,          running interactively, 5                4-6                               4-412F             information you need to            Send/Receive mode, 4-41H                supply,  4-10                   testing to remote system,5             planning,  4-1                       4-41 9          configuration program              CUG, 4-5, 4-6 ;             description,  4-4                  number, 4-15nH             entering information,           declaring a network process,<                4-34                           4-5, 4-8, 4-20C             exiting from,  4-37             destination DTE address >             horizontal scrolling,              templates, 4-238                4-34                         device, 4-11=             insert mode,  4-34              DTE address, 4-11 9             keys used in,  4-34                LLC2, 4-16,;             main menu,  4-37                DTE class, 4-13l<             optional sections,  4-34           filters, 4-21?             overstrike mode,  4-34             remote, 4-5, 4-6 ;             quitting from,  4-38               Remote, 4-17 >                                                templates, 4-23           Index-14                   4         VAX P.S.I. (cont'd)               VAX P.S.I.D          DTE name,  4-11                    gateway clients (cont'd)=             LLC2,  4-16                        security, 4-31T;             PVCs,  4-13                        systems, 4-7 A          DTE status                         group, 4-5, 4-6, 4-15 <             Checking,  4-40                    filters, 4-219          dynamic filters,  4-8                 name, 4-15 G             name,  4-20                        remote DTE address, 4-15_9          end-to-end delay,  4-25               type, 4-15s6          expedited data,  4-25              help, 4-38<          extended frame sequence               general, 4-38<             numbering,  4-13                   leaving, 4-38G          extended packet sequence              on specific fields, 4-38 F             numbering,  4-11                incoming DTE address, 4-21=          fast select,  4-23                 incoming security F          filter,  4-7, 4-21                    applications, 4-5, 4-26D             application,  4-7                  gateway clients, 4-31C             call data mask,  4-21              Gateway Clients, 4-5r<             call data value,  4-21          LAN device, 4-169             called address extension        licenses, 4-2S<                mask,  4-22                  line speed, 4-11E             called address extension        lines and DTEs, 4-5, 4-6,t2                value,  4-22                   4-11@             called NSAP,  4-22              LLC2, 4-5, 4-6, 4-168             DTE class,  4-21                   DTEs, 4-6B             dynamic,  4-8, 4-20             local facilities, 4-24;             group,  4-21                    local processes =             incoming DTE address,              security, 4-28cB                4-21                         local subaddress, 4-24A             network processes,  4-8         logical channel, 4-11i9             originally called address,         LLC2, 4-16 0                4-21                         LSAP:             priority,  4-7, 4-21               local, 4-16;             receiving DTE address,             remote, 4-16i;                4-21                         Mail, 4-7, 4-18 ;             redirect reason,  4-21             OpenVMS, 4-7 :             sending DTE address,  4-21         P.S.I., 4-5/             static,  4-8, 4-20              NCL H             subaddress range,  4-21            scripts, 4-5, 4-10, 4-28,5             unspecified parameters,              4-37oD                4-7                                failure to create,8          flow control                               4-377             negotiation,  4-11              negotiation A          gateway clients,  4-7                 flow control, 4-11                nodes,  4-19  I                                                                  Index-15-                   =         VAX P.S.I. (cont'd)               VAX P.S.I. (cont'd)i  H          network process,  4-5, 4-8,        RAP, 4-26, 4-28, 4-30, 4-31,2             4-20                              4-32G             filters,  4-8                   receiving DTE address, 4-21 A             security,  4-30                 redirect reason, 4-21,A          network user identity,  4-24       Remote Address Prefix56          NSAP mapping,  4-24                   See RAP6          options menu,  4-35                remote DTED             Add,  4-36                         class, 4-5, 4-6, 4-17D             adding information,  4-35       remote MAC address, 4-16B             changing information,           reverse charging, 4-23F                4-35                         RPOA sequence number, 4-24E             Continue,  4-36                 running the Configuration <             Delete,  4-36                     program,  4-33H             go to sections menu,  4-36         privileges required, 4-33I             Modify,  4-36                   sections in the configuration <             sections menu,  4-35              program,  4-349          originally called address,         security, 4-92F             4-21                               incoming, applications,:          outgoing security                       4-5, 4-26I             accessing systems,  4-5            incoming, gateway clients,n5             Client Systems,  4-32                4-31 I             local processes,  4-5,             incoming, Gateway Clients,i4                4-28                              4-5F          P.S.I. Mail,  4-5                     network processes, 4-30B          packet size,  4-11                    outgoing, accessing>             LLC2,  4-16                          systems,  4-5H             PVCs,  4-14                        outgoing, Client systems,5             templates,  4-23                     4-32_I          profile,  4-11                        outgoing, local processes,r!          psi$configure.com,  4-42i:          psi$configure.com,  4-33                4-5, 4-28?          PSI$CTP,  4-41                        PVCs, 4-29, 4-32 @          PSI$CTP_ADD_NETOBJ,  4-41          selected group, 4-23E          PSI$CTP_REM_NETOBJ,  4-41          sending DTE address, 4-21gE          PVC,  4-5, 4-6, 4-13               static filters, 4-8, 4-20 6             channel number,  4-13           subaddress:             DTE name,  4-13                    range, 4-214             name,  4-13                     SVC, 4-6E             packet size,  4-14              target address extension,u2             security,  4-29, 4-32             4-24D             window size,  4-14              template, 4-5, 4-8, 4-23>          $QIO(IO$_ACPCONTROL),  4-8            call data, 4-23I          quality of service,  4-25             calling address extension, 5                                                  4-24o           Index-16                   :         VAX P.S.I.                        Virtual terminal7          template (cont'd)                  using, A-12g  H             charging information,         VMScluster performance monitor  3                4-24                         See VPMo.             `Default',  4-8               VOTSD             destination DTE address,        communicating with, B-215                4-23                       VPM accountd=             DTE class,  4-23                configuring, 1-30 ,             end-to-end delay,  4-25       VT:             expedited data,  4-25           stopping, 11-6               fast select,  4-23I             local facilities,  4-24       W______________________________r>             local subaddress,  4-24       WAN DECdns namespace9             network user identity,          joining, 3-10 :                4-24                       WANrouter,  1-103             NSAP mapping,  4-24           WorksheetiA             packet size,  4-23              Address Format, 12-11b%             quality of service,  4-25L+             reverse charging,  4-23       X I             RPOA sequence number,         _______________________________B.                4-24                       X.25G             selected group,  4-23           AUTHORIZE utility, 6-1, 6-3 B             target address extension,       bill of materials, 6-1:                4-24                         CD Reader, 5-11             throughput class request,       CDROM D                4-23                            EFT kit location, 5-26             transit delay selection,        CLNS, B-17I                4-24                         configuring DECnet over X.25, 1             window size,  4-23                8-1 H          testing,  4-39                     configuring DECnet over X.25C          throughput class request,            (Alpha system),  1-15eH             4-23                            configuring DECnet over X.25A          transit delay selection,             (VAX system),  1-19 A             4-24                            configuring X.25, 8-1 >          types of system,  4-1              de-installing, 8-37          window size                        DECnet-Plus >             LLC2,  4-16                        restarting, 8-2G             packet level,  4-12             disk space requirement, 6-4 <             PVCs,  4-14                     distribution kit>             templates,  4-23                   inspection, 6-1A          X.25 applications,  4-7            EFT kit location, 5-2,E          X.29 applications,  4-7            example installation, 7-43@          X.29 support,  4-5, 4-7, 4-18      files installed, 7-49                                             hardware, 5-138                                             installation  I                                                                  Index-17                    .         X.25                              X.25E          installation (cont'd)              pre-requisite informationf6             EFT kit location,  5-2            (cont'd)D             installed files,  7-4              synchronous interface;             prompt and response                  card,  5-1PG                sequence example,  7-4       process account quotas, 6-3 D             registering the license,        product description, 5-1E                7-1                          rebooting the system, 8-3m>             /SOURCE qualifier,  7-4         release notes, 6-2H             starting,  7-4                     extracting to a file, 6-2<             time required,  5-3                location, 6-2B             using the DCL interface,        required hardware, 5-1B                7-4                          required licenses, 7-1D          installation procedure,  7-1       required privileges, 6-1B             to 7-8                          required software, 5-2G          installation time,  5-3            restarting DECnet-Plus, 8-2YI          installed files,  7-4              software product description,c1          kit location,  5-2                   5-1 B          License Management Facility,       software required, 5-29             7-1                             starting, 8-3mH          license Product Authorization      System Support Addendum, 5-1F             Key,  7-1                       time for installation, 5-3H          license registration,  7-1         User Authorization File, 6-3>          online release notes,  6-2       X.25 access template=          POLYCENTER Software                configuring, 1-16 <             Installation utility,         X.25 configuration8             5-2                             example, 8-4A          post-installation tasks,  8-1    X.25 filter,  B-9, B-10oF             to 8-3                          configuring for CONS, B-12C             configure X.25,  8-1            creating for CLNS, B-21 C             rebooting the system,  8-3      creating for CONS, B-12r?             restart DECnet-Plus,  8-2       default filter, B-9 D             starting X.25,  8-3             modifying for CLNS, B-21D          pre-installation                   modifying for CONS, B-12?             accessing the release           osi transport, B-12 >                notes,  6-2                X.25 routing circuitB             disk space requirements,        configuring CLNS, B-19D                6-4                        X.25 routing circuit typesG             distribution kit,  6-1          dynamic assigned (DA), 1-15 A             log in to privileged            permanent (PVC), 1-16 F                                             static incoming (IN), 1-16G                account,  6-1                static outgoing (OUT), 1-16 7          pre-requisite information        X.25 templaterC             required hardware,  5-1         creating for CLNS, B-20 C             required software,  5-2         creating for CONS, B-11T           Index-18                            X.25 template (cont'd)  "          modifying for CLNS,  B-20"          modifying for CONS,  B-11&         X.500 Configuration checklist,           12-9         X25 Access filter9$          configuring for CONS,  B-21         X25 Access templates$          configuring for CLNS,  B-20$          configuring for CONS,  B-11                                                                    I                                                                  Index-19v