               H                     HP_DECnet-Plus_for_OpenVMS__________________________2                     Installation and Configuration    ,                     Part Number: BA406-90007                         June 2006   G                     This book explains how to install and configure the G                     HP DECnet-Plus for OpenVMS software (including X.25 E                     for OpenVMS VAX and the optional OSI applications H                     software component). It also explains how to installG                     the HP X.25 for OpenVMS software on OpenVMS I64 and *                     OpenVMS Alpha systems.              H                     Revision/Update Information:  This manual supersedesI                                                   DECnet-Plus for OpenVMS B                                                   Installation andG                                                   Configuration (BA406- 8                                                   90001)  I                     Operating Systems:            OpenVMS I64 Version 8.3 G                                                   OpenVMS Alpha Version 5                                                   8.3   D                     Software Version:             HP DECnet-Plus for9                                                   OpenVMS =                                                   Version 8.3               +                     Hewlett-Packard Company )                     Palo Alto, California                    H                Copyright 2006 Hewlett-Packard Development Company, L.P.  C               Confidential computer software. Valid license from HP B               required for possession, use, or copying. ConsistentG               with FAR 12.211 and 12.212, Commercial Computer Software, E               Computer Software Documentation, and Technical Data for H               Commercial Items are licensed to the U.S. Government under3               vendor's standard commercial license.   C               The information contained herein is subject to change E               without notice. The only warranties for HP products and G               services are set forth in the express warranty statements E               accompanying such products and services. Nothing herein I               should be construed as constituting an additional warranty. I               HP shall not be liable for technical or editorial errors or )               omissions contained herein.   G               Intel and Itanium are trademarks or registered trademarks D               of Intel Corporation or its subsidiaries in the United)               States and other countries.   ?               UNIX is a registered trademark of The Open Group.                  Printed in the US                                  F      _________________________________________________________________  F                                                               Contents      F      Preface...................................................   xiii  /      Part I  Installing DECnet-Plus for OpenVMS     4      1  Preparing to Install DECnet-Plus for OpenVMS  F            1.1   Locating the Distribution Kit.................    1-1F            1.2   Accessing the Online Release Notes............    1-33            1.3   Time Required for Installation and F                  Configuration.................................    1-4F            1.4   Required Hardware.............................    1-4F            1.5   Prerequisite Software.........................    1-4F            1.5.1     Checking the Operating System Version.....    1-5F            1.5.2     DECnet and OSI Applications over TCP/IP...    1-5F            1.6   License Requirements..........................    1-5F            1.6.1     Checking Licenses.........................    1-6F            1.7   System Requirements...........................    1-7F            1.7.1     Disk Space................................    1-7F            1.7.2     Required Memory...........................    1-8F            1.7.3     Required System Parameters................    1-9<            1.7.3.1     SYSGEN Parameters for OpenVMS ClusterF                        Members.................................   1-123            1.7.4     Required Privileges and Rights F                      Identifiers...............................   1-12F            1.8   Backing Up the System Disk....................   1-13F            1.9   Notifying Users...............................   1-13              F                                                                    iii                   !         2  Pre-Installation Tasks   8               2.1   Information Required to Complete theI                     Installation Planning Checklist...............    2-1 I               2.2   Installation Planning Checklist...............    2-1   -         3  Installing DECnet-Plus for OpenVMS   I               3.1   Recommended Order for Installing Software.....    3-3 @               3.1.1     Installing DECnet-Plus on an OpenVMS I64I                         or OpenVMS Alpha System...................    3-3 @               3.1.2     Installing DECnet-Plus on an OpenVMS VAXI                         System....................................    3-6 I               3.2   PCSI Process Account Quotas...................    3-8 ?               3.3   Installing DECnet-Plus Using the POLYCENTER I                     Software Installation Utility.................    3-9 @               3.3.1     DECnet-Plus for OpenVMS I64 InstallationI                         Dialog....................................    3-9 B               3.3.2     DECnet-Plus for OpenVMS Alpha InstallationI                         Dialog....................................   3-11 @               3.3.3     DECnet-Plus for OpenVMS VAX InstallationI                         Dialog....................................   3-13 I               3.4   Rights Identifiers Added to the System........   3-15 I               3.5   Files Installed on the System.................   3-16 I               3.6   Rebooting the System..........................   3-17   4         Part II  Configuring DECnet-Plus for OpenVMS            4  Configuration Options  I               4.1   Choosing an Initial Configuration Option......    4-2 I               4.2   How to Run NET$CONFIGURE .....................    4-5 I               4.2.1     Local and Global Symbols..................    4-6 <               4.2.2     Running the Procedure from DifferentI                         Processes.................................    4-6                     
         iv                   .         5  Using the FAST Configuration Option  I               5.1   Invoking the FAST Configuration Option........    5-1 :               5.2   Modifying a Current DECnet-Plus SystemI                     Configuration.................................    5-5   =         6  Using the BASIC and ADVANCED Configuration Options   I               6.1   Invoking the Configuration Procedure..........    6-1 I               6.2   Opening Messages..............................    6-2 I               6.3   Specifying Phase IV Conversion Options........    6-4 8               6.4   Configuring Node and Session ControlI                     Information...................................    6-5 I               6.4.1     Specifying Directory Name Services........    6-6 I               6.4.1.1     The Local Namespace ....................    6-6 =               6.4.1.2     The HP DECnet-Plus Distributed Name I                           Service (DECdns)........................    6-7 I               6.4.1.3     The Domain Name System..................    6-7 I               6.4.1.4     The Name Service Search Path............    6-7 I               6.4.2     Specifying Node Full Names................    6-9 I               6.4.3     Specifying the Node Synonym...............   6-10 ;               6.4.4     Specifying the Naming Cache Timeout I                         Value.....................................   6-11 >               6.4.5     Specifying the Session Control AddressI                         Update Interval...........................   6-12 >               6.4.6     Specifying the Naming Cache CheckpointI                         Interval..................................   6-12 I               6.5   Configuring Routing Parameters................   6-13 I               6.5.1     Specifying the Node Type..................   6-13 I               6.5.2     Specifying Router Information.............   6-14 I               6.5.2.1     Routing Type............................   6-14 I               6.5.2.2     Maximum Path Splits.....................   6-14 >               6.5.2.3     Phase IV Maximum Address and MaximumI                           Area....................................   6-15 I               6.5.3     Specifying a DECnet Phase IV Address......   6-16 I               6.5.4     Specifying a Phase IV Prefix..............   6-16 I               6.5.5     Specifying End Node Information...........   6-17 I               6.5.5.1     Network Addresses.......................   6-17 I               6.5.5.2     DNA Address Format......................   6-20 @               6.5.5.3     Segregated Mode Routing and IntegratedI                           Mode Routing............................   6-20 I               6.5.6     Specifying the Default ES Hello Timer.....   6-22 I               6.5.7     Specifying the ES Cache Size..............   6-22 I               6.6   Configuring Devices...........................   6-22   I                                                                         v                    I               6.6.1     Configuring WANDD Device Support..........   6-23 ?               6.6.1.1     WANDD Device Configuration on OpenVMS I                           I64 and OpenVMS Alpha Systems...........   6-23 ?               6.6.1.2     WANDD Device Configuration on OpenVMS I                           VAX Systems.............................   6-24 I               6.6.2     The Configuration Procedure Device Scan...   6-25 B               6.6.3     Configuring Asynchronous Data Link SupportI                         (OpenVMS VAX Only)........................   6-26 I               6.6.3.1     Static Data Links.......................   6-27 I               6.6.3.2     Dynamic Data Links......................   6-28 A               6.6.3.3     Preparing the Terminal Lines for DECnet I                           Use.....................................   6-30 :               6.6.4     Configuring Data Links and RoutingI                         Circuits..................................   6-31 I               6.6.4.1     FDDI Large Packet Support...............   6-32 I               6.6.4.2     Circuit Cost and Routing Priority.......   6-32 A               6.6.4.3     Enabling Phase IV Addressing on Routing I                           Circuits................................   6-33 I               6.6.5     Configuring DECnet over X.25..............   6-34 I               6.7   Configuring Transports........................   6-39 ?               6.7.1     Specifying the Network Service Protocol I                         (NSP) Transport Configuration.............   6-40 I               6.7.1.1     Flow Control Policy.....................   6-41 4               6.7.2     Specifying the OSI TransportI                         Configuration.............................   6-42 ?               6.7.2.1     Enabling OSI Applications over TCP/IP I                           and DECnet over TCP/IP..................   6-43 7               6.7.3     Specifying Transport Congestion I                         Avoidance.................................   6-45 <               6.7.4     Configuring Slow-Speed NSP TransportI                         Connections...............................   6-46 8               6.7.5     Specifying the OSI Loopback TestI                         Application Account.......................   6-47 I               6.7.6     Configuring OSI Templates.................   6-47 I               6.7.6.1     Common Template Parameters..............   6-48 7               6.7.6.2     CLNS Network Service Template I                           Parameters..............................   6-52 7               6.7.6.3     CONS Network Service Template I                           Parameters..............................   6-53 ;               6.7.6.4     RFC 1006 Network Service Template I                           Parameters..............................   6-54 I               6.8   Configuring Time Zone Differential Factors....   6-54 I               6.9   Configuring the Event Dispatcher..............   6-55     
         vi                   I               6.9.1     Configuring Event Sinks...................   6-56 I               6.9.2     Outbound Streams..........................   6-58 I               6.9.3     Phase IV Relay............................   6-61 I               6.10  Configuring the Application Database..........   6-62 I               6.11  Configuring the MOP Client....................   6-65 I               6.12  Configuring the Cluster Alias.................   6-66 I               6.13  Summary Display...............................   6-68 I               6.14  Generating the NCL Scripts....................   6-69 I               6.15  Starting the Network..........................   6-70 I               6.16  Namespace Modification........................   6-71 :               6.17  Modifying a Current DECnet-Plus SystemI                     Configuration.................................   6-73   ,         7  Modifying a Current Configuration  I               7.1   Choosing a Configuration Option...............    7-1 I               7.2   Invoking the Configuration Procedure..........    7-3 I               7.3   Opening Messages..............................    7-4 I               7.4   The Main Options Menu.........................    7-6 I               7.5   Changing an Entire Configuration..............    7-7 I               7.6   Changing the Node Name/Namespace Name.........    7-8 I               7.6.1     Common Namespace Selection Processing.....   7-10 ?               7.6.2     Modifying Node Information on Satellite I                         Systems...................................   7-11 <               7.6.3     Changing a Node to Use DECdns as theI                         Primary Namespace.........................   7-11 B               7.6.4     Configuring a DECdns Clerk System to Use aI                         WAN DECdns Server.........................   7-15 =               7.6.5     Converting a DECdns Clerk System to a I                         DECdns Server System......................   7-17 >               7.6.6     Converting a DECdns Server to a DECdnsI                         Clerk System..............................   7-26 A               7.6.7     Reverting a DECdns Clerk System Back to a I                         DECdns Server System......................   7-28 B               7.6.8     Using the DECdns Namespace as Secondary onI                         a DECdns Server System....................   7-32 B               7.6.9     Configuring a DECdns Server System into anI                         Existing Namespace........................   7-36 >               7.6.9.1     Configuring a DECdns Server in a DNSI                           Version 1 Namespace.....................   7-37 I               7.7   Configuring Devices...........................   7-37 I               7.8   Configuring the NSP and OSI Transports........   7-38       I                                                                       vii                    A               7.9   Configuring the Time Zone Differential Factor I                     (DECdts)......................................   7-41 I               7.9.1     DECdts Overview...........................   7-41 :               7.9.2     Selecting the DECdts ConfigurationI                         Option....................................   7-43 I               7.9.3     Choosing a Time Zone Using Menus..........   7-44 I               7.9.4     Using Universal Coordinated Time (UTC)....   7-47 I               7.9.5     Defining Your Own Time Zone Rule..........   7-47 I               7.10  Configuring the Event Dispatcher..............   7-47 I               7.11  Configuring the Application Database..........   7-48 I               7.11.1    Deleting an Application...................   7-49 I               7.11.2    Adding an Application.....................   7-49 I               7.12  Configuring the MOP Client Database...........   7-55 I               7.12.1    Deleting a MOP Client.....................   7-56 I               7.12.2    Adding a MOP Client.......................   7-56 I               7.13  Configuring a Cluster Alias...................   7-58 I               7.13.1    Deleting an Alias.........................   7-58 I               7.13.2    Adding an Alias...........................   7-59 I               7.14  Replacing a MOP Client Configuration..........   7-59 I               7.15  Configuring Satellite Nodes...................   7-61 I               7.15.1    Autoconfiguring Phase IV Cluster Nodes....   7-63 :               7.15.2    Electing To Configure Cluster NodeI                         Scripts...................................   7-66 I               7.15.3    Electing to Configure the Local Node......   7-68 I               7.15.4    Exiting the Satellite Options Menu........   7-68 I               7.16  Configuring Cluster-Common Script Locations...   7-68 I               7.17  Summary Display...............................   7-74 I               7.18  Generating New NCL Startup Scripts............   7-75 I               7.19  Starting the Network..........................   7-76 I               7.20  Customizing the Network Configuration.........   7-77 I               7.20.1    Creating User-Defined Scripts.............   7-77   ?         Part III  Configuring X.25 Functionality on DECnet-Plus )                   for OpenVMS VAX Systems                                viii                   +         8  Configuring X.25 for OpenVMS VAX   I               8.1   Terminology...................................    8-1 I               8.2   Steps in Configuring X.25 for OpenVMS VAX.....    8-2 I               8.3   Planning the X.25 Configuration...............    8-2 ?               8.3.1     Configuring Client, Direct Connect, and I                         Connector Systems.........................    8-2 I               8.4   Using the Configuration Program...............    8-4 I               8.4.1     Invoking the Configuration Program........    8-4 I               8.4.2     Common Operations.........................    8-4 I               8.4.2.1     Entering Information....................    8-4 I               8.4.2.2     Moving Within a Section.................    8-5 I               8.4.3     Moving Between Sections...................    8-6 I               8.4.4     Keys Used in the Configuration Program....    8-6 I               8.4.5     Accessing the Options Menu................    8-8 I               8.4.6     Obtaining Help............................   8-10 I               8.4.6.1     Obtaining Help on the Program...........   8-10 I               8.4.6.2     Obtaining General Help..................   8-10 ?               8.4.6.3     Obtaining Help on a Specific Field or I                           Menu Choice.............................   8-10 I               8.4.7     Creating the Configuration File...........   8-10 I               8.4.8     Quitting from the Configuration Program...   8-11 I               8.4.9     Leaving the Program.......................   8-12 I               8.5   Configuration Sections........................   8-12 I               8.6   Required Configuration Data...................   8-18 I               8.7   Verifying the Configuration...................   8-43 I               8.7.1     Preparing to Run the CTP..................   8-43 I               8.7.2     Running the CTP...........................   8-45 I               8.7.2.1     Running the CTP Interactively...........   8-45 I               8.7.2.2     Running the CTP as a Network Object.....   8-45 I               8.8   Modifying the Configuration...................   8-45 I               8.9   Creating a New X.25 Configuration ............   8-46   ?         Part IV  Installing X.25 for OpenVMS on OpenVMS I64 and &                  OpenVMS Alpha Systems                    I                                                                        ix                    0         9  Preparing to Install X.25 for OpenVMS  I               9.1   Product Description...........................    9-1 I               9.2   Locating the Distribution Kit.................    9-1 I               9.3   Accessing the Online Release Notes............    9-3 6               9.4   Time Required for Installation andI                     Configuration.................................    9-3 I               9.5   Required Hardware.............................    9-4 I               9.6   Prerequisite Software.........................    9-4 I               9.7   License Requirements..........................    9-4 I               9.7.1     Checking Licenses.........................    9-5 I               9.8   System Requirements...........................    9-6 I               9.8.1     Disk Space................................    9-6 I               9.8.2     Required System Parameters................    9-7 6               9.8.3     Required Privileges and RightsI                         Identifiers...............................    9-7 I               9.9   Backing Up the System Disk....................    9-8 I               9.10  Notifying Users...............................    9-8   '         10  Installing X.25 for OpenVMS   I               10.1  Recommended Order for Installing Software.....   10-1 I               10.2  PCSI Process Account Quotas...................   10-2 I               10.3  Installing HP X.25 for OpenVMS Using PCSI.....   10-3 9               10.3.1    X.25 for OpenVMS I64 Installation I                         Dialog....................................   10-4 ;               10.3.2    X.25 for OpenVMS Alpha Installation I                         Dialog....................................   10-7 8               10.3.3    X.25 for OpenVMS De-InstallationI                         Example...................................  10-10 I               10.4  Files Installed on Your System................  10-11   :         11  X.25 Post-Installation and Configuration Tasks  I               11.1  Configuring X.25 for OpenVMS..................   11-1 I               11.2  Restart DECnet-Plus...........................   11-2 I               11.3  Rebooting the System..........................   11-3 I               11.4  De-installing X.25 for OpenVMS................   11-3               	         x                    ?         Part V  Installing OSI Applications for OpenVMS Systems   5         12  Preparing to Install the OSI Applications   I               12.1  Product Descriptions..........................   12-1 I               12.2  Locating the Distribution Kit.................   12-2 I               12.3  Accessing the Online Release Notes............   12-3 6               12.4  Time Required for Installation andI                     Configuration.................................   12-4 I               12.5  Required Hardware.............................   12-4 I               12.6  Prerequisite Software.........................   12-4 I               12.7  License Requirements..........................   12-5 I               12.7.1    Checking Licenses.........................   12-5 I               12.8  System Requirements...........................   12-5 I               12.8.1    Disk Space................................   12-5 I               12.8.2    Memory Requirements.......................   12-6 I               12.8.3    Required Privileges.......................   12-7 9               12.8.4    Process Quotas for OSAK$SERVER_V3 I                         Account...................................   12-8 I               12.9  Backing Up the System Disk....................   12-9 I               12.10 Notifying Users...............................   12-9   +         13  Installing the OSI Applications   I               13.1  PCSI Process Account Quotas...................   13-1 4               13.2  Starting Installation of the OSII                     Applications..................................   13-2 I               13.3  Installing the OSI Applications...............   13-2 5               13.4  Starting Up and Shutting Down OSI I                     Applications..................................   13-6 6               13.5  The OSAK Installation VerificationI                     Procedure.....................................   13-6 I               13.6  Running the OSIF$CONFIGURE.COM Procedure......   13-7 6               13.7  The FTAM Installation VerificationI                     Procedure.....................................   13-8 I               13.7.1    Preparing for the FTAM IVP................   13-8 I               13.7.2    Running the FTAM IVP......................   13-9 I               13.8  The VT Installation Verification Procedure....  13-11 I               13.9  Files Installed on Your System................  13-11 I               13.10 Sample OSI Application Installations..........  13-12 I               13.10.1   Sample OSAK Installation..................  13-12 I               13.10.2   Sample FTAM Installation..................  13-13 I               13.10.3   Sample Virtual Terminal Installation......  13-14     I                                                                        xi                    I               13.11 De-installing OSI Applications................  13-16 I               13.12 Sample OSI Application De-installations.......  13-16 I               13.12.1   Sample Virtual Terminal De-installation...  13-17 I               13.12.2   Sample FTAM De-installation...............  13-17 I               13.12.3   Sample OSAK De-installation...............  13-18   ,         14  Configuring the OSI Applications  I               14.1  FTAM and Virtual Terminal Terminology.........   14-1 I               14.2  About the OSI Application Entity Database.....   14-1 >               14.3  Getting Started Configuring Initiating andI                     Responding Entities...........................   14-2 I               14.3.1    Setting Up Responding Entities............   14-2 I               14.3.2    Setting Up Initiating Entities............   14-2 I               14.3.3    Example: Performing an FTAM File Copy.....   14-4 >               14.3.4    Example: Performing a Virtual TerminalI                         Login.....................................   14-5 I               14.4  About Responding Entities.....................   14-7 @               14.5  Configuring Addresses for Remote FTAM and VTI                     Applications..................................   14-7 I               14.5.1    Adding Address Format Entries.............  14-12 8               14.5.2    Adding Distinguished Name FormatI                         Entries...................................  14-12 I               14.5.3    Adding Pattern Format Entries.............  14-12 7               14.6  Registering Responders in the X.500 I                     Directory.....................................  14-13   0         Part VI  Supplemental Reference Material    >         A  System Files Loaded During DECnet-Plus Installation           B  Name Services  I               B.1   Modifying the Search Path Information.........    B-1 @               B.1.1     Creating a Site-Specific Search Path NCLI                         Script....................................    B-3 I               B.1.2     Using the Search Path to Ease Migration...    B-4 I               B.1.3     Setting Up Naming Templates...............    B-4 I               B.1.4     Domain Synonyms...........................    B-5 A               B.1.4.1     Search Path Naming Template Support for I                           Domain Synonyms.........................    B-5 I               B.1.4.2     Local Aliases...........................    B-6              xii                    I               B.2   Node Synonym Directories......................    B-6 :               B.2.1     Defining an Alternate Node SynonymI                         Directory.................................    B-7 I               B.2.2     When to Use the Logical Name..............    B-7 ?               B.3   Using a DNS Version 1 Namespace with DECdns I                     Version 2.....................................    B-8 ?               B.3.1     Preparing a DNS Version 1 Namespace for I                         Use by DECdns Version 2...................    B-8 I               B.3.2     Using the DNS Version 1 Namespace.........   B-10 I               B.4   Registering a Node in the Namespace...........   B-11 I               B.4.1     Export/Import File Format.................   B-11 I               B.4.2     Problems Registering a Node...............   B-11   3         C  Configuring OSI Transport Over X.25 CONS   >               C.1   OpenVMS I64 and Alpha Configuration of OSII                     Transport Over X.25 CONS......................    C-4 >               C.2   OpenVMS VAX Configuration of OSI TransportI                     Over X.25 CONS................................    C-7   9         D  Configuring Link State Routing Nodes Using the #            ISIS$CONFIGURE Procedure   I               D.1   Prerequisites.................................    D-1 I               D.2   Dialog Structure..............................    D-2 I               D.3   Outputs.......................................    D-2 I               D.4   Dialog........................................    D-3 I               D.4.1     LAN and Synchronous Circuit Dialogs.......    D-6 I               D.4.2     X.25 Routing Circuit Dialog...............    D-8 I               D.4.3     Reachable Address Dialog..................    D-9   
         Index              Tables  I               1         DECnet-Plus for OpenVMS Documentation.....     xv   I               1-1       DECnet-Plus Disk Space Requirements.......    1-8   A               1-2       Minimum System Parameters Required - Base I                         Software Installation.....................    1-9   I               1-3       ADD_ System Parameter Values..............   1-10   I               2-1       Installation Planning Checklist...........    2-2   I                                                                      xiii                    9               3-1       Process Quotas for the Installing I                         Account...................................    3-8   I               3-2       Rights Identifiers........................   3-15   9               4-1       Choosing an Initial Configuration I                         Option....................................    4-3   A               7-1       Choosing a Configuration Option to Modify I                         a Current Configuration...................    7-1   :               7-2       Application End-User SpecificationI                         Types.....................................   7-50   I               7-3       Application Numbers.......................   7-50   I               7-4       Satellite Configuration Options...........   7-62   I               8-1       X.25 Terminology..........................    8-1   ?               8-2       X.25 for OpenVMS VAX Configurations and I                         License Requirements......................    8-3   7               8-3       Available Keys Used by the X.25 I                         Configuration Program.....................    8-7   <               8-4       Configuration Sections Applicable to=                         Client, Direct Connect, and Connector I                         Systems...................................   8-13   A               8-5       Configuration Information: Lines and DTEs =                         (Direct Connect and Connector Systems I                         Only).....................................   8-18   ?               8-6       Configuration Information: PVCs (Direct I                         Connect and Connector Systems Only).......   8-22   A               8-7       Configuration Information: Groups (Direct I                         Connect and Connector Systems Only).......   8-22   <               8-8       Configuration Information: LLC2 DTEs=                         (Direct Connect and Connector Systems I                         Only).....................................   8-24   =               8-9       Configuration Information: Remote DTE I                         Classes (Client Systems Only).............   8-26   B               8-10      Configuration Information: X.29 and P.S.I.I                         Mail Support (All Systems) ...............   8-26   @               8-11      Configuration Information: Server ClientI                         Nodes (Connector Systems Only)............   8-27   ?               8-12      Configuration Information: Applications I                         (All Systems).............................   8-28   >               8-13      Configuration Information: Declaring aI                         Network Process (All Systems).............   8-28            xiv                    @               8-14      Configuration Information: Filters - for?                         Applications and Network Processes (All >                         Systems) and Server Clients (ConnectorI                         Systems Only) ............................   8-30   A               8-15      Configuration Information: Templates (All I                         Systems) .................................   8-32   ;               8-16      Configuration Information: Incoming I                         Security for Applications (All Systems)...   8-35   ;               8-17      Configuration Information: Outgoing 9                         Security for Local Processes (All I                         Systems)..................................   8-37   ;               8-18      Configuration Information: Incoming ;                         Security for Network Processes (All I                         Systems)..................................   8-39   ;               8-19      Configuration Information: Incoming >                         Security for Server Clients (ConnectorI                         Systems Only) ............................   8-40   ;               8-20      Configuration Information: Outgoing >                         Security for Client Systems (ConnectorI                         Systems Only) ............................   8-41   9               10-1      Process Quotas for the Installing I                         Account...................................   10-2   I               12-1      Minimum Disk Space Requirements...........   12-6   B               12-2      Required Global Pages, Global Pagelets andI                         Sections..................................   12-6   I               12-3      OSAK$SERVER_V3 Process Account Quotas.....   12-8   B               12-4      Account Quotas for Processes that use OSAKI                         Software..................................   12-9   9               13-1      Process Quotas for the Installing I                         Account...................................   13-1   I               14-1      Default Addresses.........................   14-7   I               14-2      X.500 Configuration Checklist.............   14-9   I               14-3      Address Format Worksheet..................  14-11   I               C-1       Sample X.25 Configuration Information.....    C-2   I               D-1       Routing Protocol Options..................    D-4   I                                                                        xv                              I         _________________________________________________________________   I                                                                   Preface       I               This book describes how to install and configure HP DECnet- F               Plus for OpenVMS using the three available configurationD               options (FAST, BASIC, and ADVANCED). It also discussesG               how to use the configuration procedure to modify existing C               DECnet-Plus for OpenVMS configurations. The book also 5               describes how to install and configure:   D               o  X.25 functionality on OpenVMS VAX systems (formally.                  known as VAX P.S.I. software)  B               o  X.25 for OpenVMS on OpenVMS I64 and OpenVMS Alpha                  systems  ?               o  The optional OSI layered applications software                   components:  2                  -  OSI Applications Kernel (OSAK)  @                  -  File Transfer, Access, and Management (FTAM)  )                  -  Virtual Terminal (VT)   F                 ________________________ Note ________________________  A                 DECnet-Plus for OpenVMS must be installed on your E                 system before you can install X.25, FTAM, VT, or OSAK                  software.   F                 ______________________________________________________          I                                                                      xiii                             Intended Audience   '               This book is written for:   (               o  OpenVMS system managers  0               o  DECnet-Plus software installers  .               o  Network planners and managers           Structure of This Book  (               This book has three parts:  C               Part I  Describes the prerequisite steps necessary to B                       install the DECnet-Plus for OpenVMS softwareE                       and the installation dialog used to install the                        software.   D               Part II Provides help to determine which configuration@                       option to use: FAST, BASIC or ADVANCED. ItG                       describes using each of the configuration options B                       to configure a new DECnet-Plus node. It alsoI                       discusses using the BASIC or ADVANCED configuration A                       option to modify an existing configuration.   E               Part IIIDescribes the steps necessary to configure X.25 B                       functionality on DECnet-Plus for OpenVMS VAXB                       systems. This functionality was previously a:                       separate product known as VAX P.S.I.  C               Part IV Describes the prerequisite steps necessary to I                       install the X.25 for OpenVMS software on an OpenVMS F                       I64 or OpenVMS Alpha system and the installationI                       dialog used to install the software. It also serves C                       as an introduction to the configuration tasks H                       discussed in the HP X.25 for OpenVMS Configuration                       manual.   C               Part V  Describes the prerequisite steps necessary to D                       install the optional OSI applications softwareD                       components and the installation dialog used toD                       install the software. It also describes how to=                       configure the FTAM and VT applications.   I               Part VI Reference appendixes useful to the installation and ,                       configuration process.           xiv                             Terminology   H               The following terms are used interchangeably in this book:  )               o  Transition and migration   -               o  DECnet Phase IV and Phase IV   (               o  End system and end node  /               o  Intermediate system and router   (               o  DECnet-Plus and Phase V           Guide to Documentation  G               DECnet-Plus for OpenVMS documentation is available in two                sets:   >               o  Documentation set for DECnet-Plus for OpenVMS  @               o  Supplemental X.25 for OpenVMS documentation set  H               Table 1 lists the documentation that supports this version6               of the DECnet-Plus for OpenVMS software.  I               Table_1_DECnet-Plus_for_OpenVMS_Documentation______________   I               Document___________________Contents________________________   I               DECnet-Plus_for_OpenVMS_Documentation_Set__________________   E               DECnet-Plus for OpenVMS    Describes the manuals in the E               Introduction and User's    documentation sets, outlines D               Guide                      the DECnet-Plus for OpenVMSI                                          features and tools, explains how I                                          to use and manage an end system, E                                          and provides a comprehensive H                                          glossary of DECnet terminology.  I                                                  (continued on next page)         I                                                                        xv                    I               Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______   I               Document___________________Contents________________________   I               DECnet-Plus_for_OpenVMS_Documentation_Set__________________   A               HP DECnet-Plus for         Describes changes to the I               OpenVMS Release Notes      software; installation, upgrade, G                                          and compatibility information; B                                          new and existing softwareC                                          problems and restrictions; G                                          and software and documentation 5                                          corrections.   E                                          Note: Print this file at the F                                          beginning of the installationI                                          procedure and read it before you I                                          install DECnet-Plus for OpenVMS.   C               DECnet-Plus Planning       Provides configuration and G               Guide                      planning guidelines, including H                                          namespace planning information,I                                          to help you transition a network D                                          from the DECnet Phase IV toE                                          DECnet Phase V architecture.   I                                                  (continued on next page)                                              xvi                    I               Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______   I               Document___________________Contents________________________   I               DECnet-Plus_for_OpenVMS_Documentation_Set__________________   D               HP DECnet-Plus for         Explains how to install andF               OpenVMS Installation       configure the DECnet-Plus forC               and Configuration          OpenVMS software using the D                                          three configuration optionsE                                          (FAST, BASIC, and ADVANCED). G                                          Also explains how to modify an @                                          existing configuration.  F                                          Explains how to configure theI                                          X.25 functionality included with H                                          the DECnet-Plus for OpenVMS VAXG                                          software (formerly provided by F                                          the VAX P.S.I. Access and VAX:                                          P.S.I. products).  D                                          Explains how to install theB                                          separate X.25 for OpenVMSC                                          software product available D                                          for OpenVMS I64 and OpenVMSI                                          Alpha systems. For configuration I                                          information, see the HP X.25 for F                                          OpenVMS Configuration manual.  D                                          Explains how to install andC                                          configure the optional OSI I                                          applications software components I                                          (OSI Applications Kernel (OSAK), C                                          OSI File Transfer, Access, G                                          and Management (FTAM), and OSI @                                          Virtual Terminal (VT)).  I                                                  (continued on next page)               I                                                                      xvii                    I               Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______   I               Document___________________Contents________________________   I               DECnet-Plus_for_OpenVMS_Documentation_Set__________________   F               HP DECnet-Plus for         Provides in-depth informationH               OpenVMS Network            about how to monitor and manageH               Management                 DECnet-Plus for OpenVMS systemsH                                          using various tools and NetworkI                                          Control Language (NCL) commands. C                                          Explains how to set up and B                                          use event dispatching andF                                          how to perform all day-to-dayG                                          management tasks for the local F                                          DECnet-Plus for OpenVMS node,E                                          including setting up OpenVMS E                                          clusters, managing security, I                                          downline loading, and monitoring 5                                          the network.   A               DECnet-Plus for OpenVMS    Provides quick-reference D               Network Management Quick   information about the toolsI               Reference Guide            that help you manage and monitor H                                          a DECnet-Plus network. Use thisF                                          guide with the HP DECnet-PlusG                                          for OpenVMS Network Management 0                                          manual.  F               HP DECnet-Plus for         Outlines command descriptionsE               OpenVMS Network Control    and examples for all Network H               Language Reference         Control Language (NCL) commandsD                                          that you execute to manage,B                                          monitor, and troubleshootA                                          the network. Begins with D                                          an orientation chapter thatC                                          contains information about E                                          how to execute NCL commands, F                                          followed by a command chapterF                                          for each module in the DECnet?                                          Phase V layered model.   I                                                  (continued on next page)     
         xviii                    I               Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______   I               Document___________________Contents________________________   I               DECnet-Plus_for_OpenVMS_Documentation_Set__________________   D               DECnet-Plus Problem        Explains how to isolate andD               Solving                    solve DECnet problems in anE                                          OpenVMS environment that can F                                          occur while the network is inH                                          operation. Includes informationF                                          about how to perform loopbackI                                          tests and how to use the DTS/DTR C                                          utility to solve problems.   @               HP DECnet-Plus for         Explains HP DECnet-PlusA               OpenVMS DECdns Management  Distributed Name Service E                                          (DECdns) concepts and how to D                                          manage a DECdns distributedH                                          namespace. Use this manual withH                                          the DECnet-Plus Planning Guide.  B               HP DECnet-Plus for         Introduces HP DECnet-PlusA               OpenVMS DECdts Management  Distributed Time Service H                                          (DECdts) concepts and describesG                                          how to manage the software and 7                                          system clocks.   E               DECnet-Plus DECdts         Contains DECdts time routine B               Programming                reference information andD                                          describes the time-provider9                                          interface (TPI).   E               DECnet-Plus OSAK           Explains how to use the OSAK B               Programming                (OSI Applications Kernel)F                                          interface to create OSI (OpenA                                          Systems Interconnection) G                                          applications for any supported :                                          operating system.  G               DECnet-Plus OSAK           Provides reference information G               Programming Reference      on using the OSAK interface to G                                          create OSI applications on any D                                          supported operating system.  I                                                  (continued on next page)   I                                                                       xix                    I               Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______   I               Document___________________Contents________________________   I               DECnet-Plus_for_OpenVMS_Documentation_Set__________________   G               DECnet-Plus OSAK SPI       Provides reference information E               Programming Reference      about using the OSAK session G                                          programming interface (SPI) to G                                          create OSI applications on any D                                          supported operating system.  G               DECnet-Plus FTAM and       Explains how to use and manage I               Virtual Terminal Use and   FTAM (File Transfer, Access, and H               Management                 Management) software for remoteI                                          file transfer and management and I                                          VT (Virtual Terminal) for remote H                                          login to OSI-compliant systems.  C               DECnet-Plus FTAM           Explains how to access the E               Programming                FTAM protocol through FTAM's E                                          API (application programming 4                                          interface).  C               DECnet-Plus for OpenVMS    Contains information about C               Programming                how to design and write an C                                          application that follows a E                                          client/server model and uses A                                          the OpenVMS Interprocess D                                          Communication ($IPC) systemH                                          service and the transparent andE                                          nontransparent communication D                                          with the queue Input/OutputH                                          ($QIO) system service. ExplainsD                                          how to write programs usingG                                          the OpenVMS system services to G                                          communicate with OSI transport G                                          services. Provides information D                                          about the Common ManagementI                                          Information Service (CMISE) API.   I                                                  (continued on next page)       
         xx                   I               Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______   I               Document___________________Contents________________________   I               DECnet-Plus_for_OpenVMS_Documentation_Set__________________   =               DECnet/OSI for VMS CTF     Explains how use the D               Use                        Common Trace Facility (CTF)H                                          troubleshooting tool to collectG                                          and analyze protocol data from =                                          networking software.   I                                                  (continued on next page)                                                                 I                                                                       xxi                    I               Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______   I               ___________________________________________________________   I               Supplemental_X.25_Documentation_Set________________________   C               HP X.25 for OpenVMS        Discusses how to configure G               Configuration              X.25 for OpenVMS on an OpenVMS E                                          I64 or OpenVMS Alpha system. E                                          For information about how to I                                          configure the X.25 functionality D                                          on OpenVMS VAX systems, seeG                                          the HP DECnet-Plus for OpenVMS G                                          Installation and Configuration 0                                          manual.  C               HP X.25 for OpenVMS        Explains how to manage and E               Management Guide           monitor an X.25 system using 7                                          network tools.   I               HP X.25 for OpenVMS        Explains the X.25 security model I               Security Guide             and the tasks required to set up B                                          and manage X.25 security.  D               HP X.25 for OpenVMS        Provides guidance on how toF               Problem Solving            solve problems that can occurD                                          while using an X.25 system.  @               HP X.25 for OpenVMS        Explains how to use andF               Utilities                  manage the X.25 Mail and X.29B                                          communications utilities.  A               HP X.25 for OpenVMS        Explains how to use X.25 I               Accounting                 accounting to obtain performance F                                          records and information about@                                          how X.25 is being used.  G               HP X.25 for OpenVMS        Explains how to write X.25 and I               Programming                X.29 programs to perform network 4                                          operations.  G               HP X.25 for OpenVMS        Provides reference information G               Programming Reference      for X.25 and X.29 programmers.   I               DECnet/OSI for VMS VAX     Provides information about using F               WANDD Programming          the programming interface forI               ___________________________the_WANDD_devices.______________   >               The following OpenVMS manuals provide additional               information:           xxii                   :               o  OpenVMS License Management Utility Manual  E               o  OpenVMS System Management Utilities Reference Manual            Reader's Comments   D               HP welcomes your comments on this manual or any of theF               DECnet-Plus documents. Please send comments to either of&               the following addresses:  +               Internet    openvmsdoc@hp.com   1               Mail        Hewlett-Packard Company >                           OSSG Documentation Group, ZKO3-4/U08,                           110 Spit Brook Rd./                           Nashua, NH 03062-2698   -         How To Order Additional Documentation   I               For information about how to order additional documentation H               and for online versions of most DECnet-Plus documentation,9               visit the following World Wide Web address:   /               http://www.hp.com/go/openvms/doc/            Conventions   >               The following conventions are used in this book.  I               ___________________________________________________________ I               Convention_______Meaning___________________________________   D               special type     Indicates a literal example of systemG                                output or user input. In text, indicates H                                command names, keywords, node names, fileH                                names, directories, utilities, and tools.  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 of D                                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.  I                                                                     xxiii                  I               ___________________________________________________________ I               Convention_______Meaning___________________________________   4               italic type      Indicates a variable.  G               bold             Indicates a new term defined in the text 8                                or important information.  G               <Return>         Indicates that you press the Return key.   G               Ctrl/x           Indicates that you press the Control 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.__________________________________                                                              xxiv                         I                                                                    Part I I         _________________________________________________________________   I                                        Installing DECnet-Plus for OpenVMS             B               Part I describes the prerequisite steps necessary toE               install the HP DECnet-Plus for OpenVMS software and the ?               installation dialog used to install the software.   1               It contains the following chapters:   I               o  Chapter 1 - Preparing to Install DECnet-Plus for OpenVMS   3               o  Chapter 2 - Pre-Installation Tasks   ?               o  Chapter 3 - Installing DECnet-Plus for OpenVMS                          I                                                                         1 I         _________________________________________________________________   I                              Preparing to Install DECnet-Plus for OpenVMS     F               This chapter describes the tasks you must perform beforeG               installing and configuring the HP DECnet-Plus for OpenVMS                software.   )         1.1 Locating the Distribution Kit   E               To obtain the directory location of the DECnet-Plus kit B               on the CD-ROM, refer to the OpenVMS Software ProductE               Library CD-ROM User's Guide that accompanies the CD-ROM                distribution kit.   :               Alternatively, complete the following steps:  H               1. To obtain the kit directory location of the DECnet-PlusG                  distribution files on the appropriate OpenVMS Software E                  Product Library CD-ROM (media CD-ROM), do one of the                   following:   H                  o  Use the CDMENU utility provided on the media CD-ROM.  F                  o  View the CD-ROM master index file on the media CD-                     ROM.  G                  For information about using the CDMENU utility and the C                  CD-ROM files on the media CD-ROM, see the Software E                  Product Library CD-ROM User's Guide that accompanies D                  the media CD-ROM distribution kit. The media CD-ROME                  user guide and CD-ROM master index file are provided G                  as online files in the [README] directory on the first                   media CD-ROM.  B               2. To determine if the appropriate CD-ROM is alreadyE                  mounted on your system, enter the following command:       I                          Preparing to Install DECnet-Plus for OpenVMS 1-1            4         Preparing to Install DECnet-Plus for OpenVMS)         1.1 Locating the Distribution Kit     &                  $ show device dka400:  F                 ________________________ Note ________________________  F                 The device DKA400 is used in examples in this documentC                 as the device where the appropriate CD-ROM has been                  mounted.  F                 ______________________________________________________  F               3. If the media CD-ROM containing the DECnet-Plus kit isG                  not mounted, insert the appropriate CD-ROM (write down H                  the volume label) into an available CD-ROM drive. EnterH                  the appropriate mount command to mount the media CD-ROM/                  (omit the /FOREIGN qualifier):   &                  $ mount dka400: label  E                  where label is the volume label of the media CD-ROM.   E               4. Define the logical name PCSI$SOURCE to reference the B                  appropriate kit directory on the Software ProductF                  Library Compact Disk. For example, if the DECnet-PlusC                  kit is located in the [DECNETPLUS083] directory on <                  device DKA400, enter the following command:  <                  $ define pcsi$source dka400:[decnetplus083]  D               5. To verify the DECnet-Plus kit name, use a directoryA                  command specifying the PCSI$SOURCE logical name:   /                  $ directory pcsi$source:*.pcsi   G               The distribution kit contains the following component kit                files:  )               o  Base components software   4                  -  DECnet-Plus for OpenVMS base kit  "               o  Optional software  ?                  -  OSI Applications Kernel kit (OSAK software)   I                  -  OSI File Transfer, Access, and Management application '                     kit (FTAM software)   :                  -  OSI Virtual Terminal kit (VT software)  8         1-2 Preparing to Install DECnet-Plus for OpenVMS           I                              Preparing to Install DECnet-Plus for OpenVMS I                                         1.1 Locating the Distribution Kit     6               For a more detailed list, see Chapter 3.  F                 ________________________ Note ________________________  ?                 Before installing any of the software, read the ?                 DECnet-Plus Planning Guide. This guide contains F                 installation planning information, including namespace&                 planning instructions.  F                 ______________________________________________________  .         1.2 Accessing the Online Release Notes  F               You should review the release notes for a description ofD               new features, differences between multiple versions ofE               DECnet-Plus, and changes in the installation procedure.   G               To access the release notes, issue the following command:   H               $ product extract release_notes decnet_osi  /file=filename  G               In the above example, it is assumed that the logical name D               PCSI$SOURCE properly references the directory locationE               of the DECnet-Plus kit. Details on how to determine the G               directory location of the DECnet-Plus kit are provided in                Section 1.1.  G               The product selected is displayed and you are prompted 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.   =               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 ________________________  A                 After DECnet-Plus is installed, the release notes D                 file is located in sys$help in the form decnet-plus-!                 v*.release_notes.   F                 ______________________________________________________  I                          Preparing to Install DECnet-Plus for OpenVMS 1-3            4         Preparing to Install DECnet-Plus for OpenVMS<         1.3 Time Required for Installation and Configuration    <         1.3 Time Required for Installation and Configuration  H               The time required to complete the DECnet-Plus installationD               and configuration procedures depends on the following:  E               o  Configuration option used (FAST, BASIC, or ADVANCED)   ,               o  Optional software installed  "               o  CPU on the system  D               The time required to install and configure DECnet-PlusC               can vary from 30 minutes to 2 hours, depending on the B               combination of choices you make from the above list.           1.4 Required Hardware   G               The DECnet-Plus for OpenVMS installation process requires %               the following hardware:                   o  A CD-ROM reader                 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.  B               Refer to the OpenVMS Operating System for I64, AlphaE               and VAX Software Product Description (SPD 25.01.xx) for I               hardware requirements and processor support for the DECnet-                Plus software.  !         1.5 Prerequisite Software   D               Before you can install and configure the software, theF               system must have the required operating system software.E               In addition, if you intend to use any optional software D               supported by DECnet-Plus for OpenVMS, you must use the<               supported versions of these software products.  E               For specific information about the required versions of G               prerequisite software, see the HP DECnet-Plus for OpenVMS +               Software Product Description.   8         1-4 Preparing to Install DECnet-Plus for OpenVMS           I                              Preparing to Install DECnet-Plus for OpenVMS I                                                 1.5 Prerequisite Software     3         1.5.1 Checking the Operating System Version   G               To determine the OpenVMS operating system version number, .               enter the following DCL command:  $               $ show system <Return>  5         1.5.2 DECnet and OSI Applications over TCP/IP   E               If you plan to use the DECnet-Plus over TCP/IP feature, F               then TCP/IP software is a prerequisite. Your system willF               be able to operate over TCP/IP if and only if the TCP/IPI               product used on your system supports the PATHWORKS Internet C               Protocol (PWIP) interface. For more information about B               required TCP/IP software, see the HP DECnet-Plus for$               OpenVMS Release Notes.  F                 ________________________ Note ________________________  C                 For more information on using DECnet over TCP/IP or A                 the OSI applications over TCP/IP, refer to the HP A                 DECnet-Plus for OpenVMS Network Management guide.   F                 ______________________________________________________            1.6 License Requirements  G               DECnet-Plus for OpenVMS uses three licenses. The specific B               license required on your system is determined by the:               functions you want to use and your CPU type:  H               o  Basic function license (DVNETEND) - provides end system                  support.   I               o  Extended function license (DVNETEXT) for OpenVMS I64 and E                  OpenVMS Alpha systems - provides end system support, B                  host-based routing support, DECdns server, DECdtsF                  server, cluster alias, and OSI applications gateways.  E               o  Extended function license (DVNETRTG) for OpenVMS VAX B                  systems - provides end system support, host-basedG                  routing support, DECdns server, DECdts server, cluster 6                  alias, and OSI applications gateways.  F                 __ License Requirements for OpenVMS for I64 Systems __  F                 HP DECnet-Plus for OpenVMS Version 8.3 for I64 systemsC                 requires the Foundation Operating Environment (FOE)   I                          Preparing to Install DECnet-Plus for OpenVMS 1-5            4         Preparing to Install DECnet-Plus for OpenVMS          1.6 License Requirements    A                 license. This license includes the basic function C                 license (DVNETEND). If you intend to configure your E                 system as a DECdns server, you must obtain a separate !                 DVNETEXT license.   F                 ______________________________________________________  E               At least one node of an OpenVMS Cluster system requires D               the appropriate extended function license (DVNETEXT or9               DVNETRTG) to use the cluster alias feature.   A               If you install the DECnet-Plus software without the G               appropriate extended function license and then attempt to I               configure your system as a DECdns server, the DECdns server I               will fail and the configuration utility (net$configure.com)                will exit.  H               In addition to the three DECnet-Plus for OpenVMS licenses,I               you may need additional licenses to use certain features of                DECnet-Plus.  D               o  In addition to the appropriate DECnet-Plus extendedI                  function license, the TELNET/VT gateway also requires an 8                  HP TCP/IP Services for OpenVMS license.  F               o  In addition to the DECnet-Plus base function license,I                  certain X.25 wide area network features on OpenVMS Alpha D                  and OpenVMS I64 systems require a separate X.25 forH                  OpenVMS license. For more information, see Section 9.7.  F               o  In addition to the DECnet-Plus base function license,G                  certain X.25 wide area network features on OpenVMS VAX G                  systems require an X.25 license. For more information, #                  see Section 8.3.1.            1.6.1 Checking Licenses   H               To determine if a DECnet-Plus license is registered, enter(               the following DCL command:  ,               $ show license dvnet* <Return>  G               If the system does not have the required licenses, obtain B               the Product Authorization Key (PAK) and register theG               license. For instructions on registering a license, refer ?               to the OpenVMS License Management Utility Manual.   8         1-6 Preparing to Install DECnet-Plus for OpenVMS           I                              Preparing to Install DECnet-Plus for OpenVMS I                                                   1.7 System Requirements              1.7 System Requirements   F               Before you install the DECnet-Plus for OpenVMS software,I               make sure that your system meets the requirements discussed (               in the following sections.           1.7.1 Disk Space  I               If this is the first time you are installing DECnet-Plus on I               a particular system, ensure that you have enough free space F               on the system disk. You need enough space to install theE               DECnet-Plus Base components and any options you select.   A               If you already have DECnet-Plus installed, you need G               considerably less free space for the installation because H               the earlier installation has already allocated most of the9               space that a subsequent installation needs.   H               Table 1-1 shows the amount of disk space needed to installE               the DECnet-Plus software components. Make sure you have H               enough free space to install the required software and the                optional software.                                              I                          Preparing to Install DECnet-Plus for OpenVMS 1-7            4         Preparing to Install DECnet-Plus for OpenVMS         1.7 System Requirements     I               Table_1-1_DECnet-Plus_Disk_Space_Requirements______________   7                                Blocks for    Blocks for I               Component________I64___________Alpha_________Blocks_for_VAX   A               Base components  160000         92000         77000   A               DECdts server      3500          1600          1800   A               DECdns            15000         15000          3000                server[1]   A               WANDD             10000          5000          5500   A               X.25 for          20000         10000         10000                OpenVMS   A               OSAK              12300          6600          6000   A               FTAM              42700         31800         12000   A               Virtual            9800          3300          2000                Terminal  A               Totals           273300        165300        117300 I               [1]Approximate_amount_-_actual_amount_depends_on_the_size__   I               of the namespace, the number of logs created, and so forth. I               The amount of required disk space could double when running H               tests, then return to original amount when duplicate files               are deleted.I               ___________________________________________________________   H               To find out how many free blocks exist on the system disk,*               enter the following command:  2               $ show device sys$sysdevice <Return>  I               If the number of required blocks exceeds the number of free >               blocks, you must clear space on the system disk.           1.7.2 Required Memory   I               The minimum amount of memory required is 512 MB for OpenVMS I               I64 systems, 64 MB for OpenVMS Alpha systems, and 24 MB for "               OpenVMS VAX systems.  E               To check the amount of memory on your system, enter the                 following command:  )               $ show memory/full <Return>   8         1-8 Preparing to Install DECnet-Plus for OpenVMS           I                              Preparing to Install DECnet-Plus for OpenVMS I                                                   1.7 System Requirements     (         1.7.3 Required System Parameters  H               This section provides information about system parameters,3               their values, and how to modify them.   H               Table 1-2 lists the minimum system parameters required for                the base software.  A               Table 1-2 Minimum System Parameters Required - Base I               __________Software_Installation____________________________   I               Parameter___________Minimum_Value__________________________   I               For_OpenVMS_I64_Systems:___________________________________   )               ARB_SUPPORT               3   )               MIN_CLISYMTBL           750   )               MIN_GBLPAGES         100000   )               MIN_GBLPAGFIL          1024   )               MIN_GBLSECTIONS         512   )               MIN_KSTACKPAGES           2   I               ___________________________________________________________ I               For_OpenVMS_Alpha_Systems:_________________________________   )               ARB_SUPPORT               3   )               MIN_CLISYMTBL           750   )               MIN_GBLPAGES         100000   )               MIN_GBLPAGFIL          1024   )               MIN_GBLSECTIONS         512   )               MIN_KSTACKPAGES           2   )               MIN_NPAGEDYN        2100000   I               ___________________________________________________________ I               For_OpenVMS_VAX_Systems:___________________________________   )               MIN_CLISYMTBL           500   )               MIN_GBLPAGES          50000   )               MIN_GBLPAGFIL          4096   )               MIN_GBLSECTIONS         400   I               MIN_VIRTUALPAGECNT____35000________________________________   I                          Preparing to Install DECnet-Plus for OpenVMS 1-9            4         Preparing to Install DECnet-Plus for OpenVMS         1.7 System Requirements     I               In addition to the minimum system parameter values, DECnet- H               Plus also requires several ADD_ parameter values to ensureG               adequate resources are available. These values are listed                in Table 1-3.   I               Table_1-3_ADD__System_Parameter_Values_____________________   I               Parameter___________Value__________________________________   I               For_OpenVMS_I64_Systems:___________________________________   )               ADD_GBLPAGES          75000   )               ADD_GBLPAGFIL           512   )               ADD_GBLSECTIONS         200   )               ADD_GH_EXEC_CODE        256   )               ADD_NPAGEDYN        3800000   I               ___________________________________________________________ I               For_OpenVMS_Alpha_Systems:_________________________________   )               ADD_GBLPAGES          55000   )               ADD_GBLPAGFIL           256   )               ADD_GBLSECTIONS         100   I               ___________________________________________________________ I               For_OpenVMS_VAX_Systems:___________________________________   )               ADD_GBLPAGES          55000   I               ADD_GBLSECTIONS_________100________________________________   G                 ______________________ Important ______________________   B                 For most DECnet installations, it is not necessaryE                 for you to add the preceding system parameters to the F                 modparams.dat file. These parameters are automaticallyD                 taken into consideration when DECnet is installed or                 upgraded.   A                 If necessary, prior to installing this release of E                 DECnet-Plus, you should edit modparams.dat and remove ?                 any entries that you may have made for previous C                 DECnet-Plus installations. Use the preceding tables B                 as a guide. Different versions of DECnet-Plus haveF                 had different parameter values; however, the parameterF                 list has remained consistent for most recent releases.  9         1-10 Preparing to Install DECnet-Plus for OpenVMS            I                              Preparing to Install DECnet-Plus for OpenVMS I                                                   1.7 System Requirements     D                 See the "Server Tuning" and "Client Tuning" sectionsA                 in the "DECdns Problem Solving" chapter of the HP D                 DECnet-Plus for OpenVMS DECdns Management manual forD                 examples of when it might still be necessary to makeF                 DECnet-related changes to modparams.dat. Note that anyC                 ADD_ values you place in modparams.dat are added to 6                 the standard ADD_ values in Table 1-3.  C                 DECnet and AUTOGEN use two files, newparams.dat and @                 clu$params.dat, to support this automatic system?                 parameter setting. The DECnet-Plus installation A                 procedure creates a newparams.dat file to provide =                 AUTOGEN with the DECnet-Plus system parameter C                 requirements. When AUTOGEN is run, it first renames C                 any existing clu$params.dat file to clu$params.old. >                 Then it takes the values found in all existingD                 newparams.dat files and creates a new clu$params.dat@                 file containing the results of its newparams.datE                 scan. AUTOGEN then renames the newparams.dat files to D                 newparams.done. During AUTOGEN, the parameters foundF                 in clu$params.dat are used in much the same fashion as2                 parameters found in modparams.dat.  F                 ______________________________________________________  F               To check any system parameter, invoke the SYSGEN utilityB               and enter the show command. For example, to view theI               current value for GBLSECTIONS, enter the following command:                  $ mcr sysgen&               SYSGEN> show gblsections  I               If any of the system parameters need to be modified, follow                these steps:  9               1. Edit the modparams.dat file by entering:   0                  $ edit sys$system:modparams.dat  H               2. Enter the values into the file in the following format:  $                  ADD_GBLSECTIONS=512                  .                  .                  .#                  ADD_GBLPAGFIL=1024   &               3. Exit from the editor.  I                         Preparing to Install DECnet-Plus for OpenVMS 1-11            4         Preparing to Install DECnet-Plus for OpenVMS         1.7 System Requirements     ?               4. Run AUTOGEN by entering the following command:   5                  $ @sys$update:autogen getdata reboot   G                 _______________________ Warning _______________________   ?                 In the unlikely event that the required minimum B                 system parameter requirements are no longer met byB                 the current system parameter settings, the networkD                 startup will fail. If the network fails to start forC                 this reason, the logical name NET$STARTUP_STATUS is C                 set to OFF-AUTOGENREQ. If this occurs you must edit F                 the modparams.dat file directly and set the parameters?                 to the values shown in Table 1-2 and Table 1-3.   F                 ______________________________________________________  =         1.7.3.1 SYSGEN Parameters for OpenVMS Cluster Members   C               When installing DECnet-Plus for OpenVMS on an OpenVMS A               Cluster, make sure that you apply any custom SYSGEN I               parameter values you may have added to all cluster members.   8         1.7.4 Required Privileges and Rights Identifiers  F               HP recommends that you install and configure DECnet-PlusB               from the SYSTEM account. If you are configuring fromF               another account, make sure the account has the followingC               privileges and rights identifiers in place before you                begin.  9               Required account privileges are as follows:                  o  CMKRNL                  o  NETMBX                  o  SYSPRV                  o  TMPMBX                  o  OPER                  o  SYSNAM                  o  WORLD  9         1-12 Preparing to Install DECnet-Plus for OpenVMS            I                              Preparing to Install DECnet-Plus for OpenVMS I                                                   1.7 System Requirements     F                 ________________________ Note ________________________  E                 The account cannot have the locked password (LOCKPWD)                  flag set.   F                 ______________________________________________________  9               Required rights identifiers are as follows:                  o  NET$MANAGE                  o  NET$SECURITY   &               o  NET$REGISTERDNSOBJECT  F                 ________________________ Note ________________________  E                 If your account has the BYPASS privilege, then you do ;                 not need to grant these rights identifiers.   F                 ______________________________________________________  C               To determine the default privileges of the installing B               account, log in and enter the following DCL command:  '               $ show process/privileges   &         1.8 Backing Up the System Disk  I               Use the OpenVMS BACKUP utility to make a copy of the system                disk.            1.9 Notifying Users   C               Inform users on the system that you plan to install a 1               product and that they must log out.   G               First, prevent nonprivileged users from logging in to the                system:   (               $ set logins/interactive=0  E               Next, use the reply/all command and be sure to indicate E               the exact time you plan to begin running the POLYCENTER 9               Software Installation utility. For example:   U               $ reply/all "Installing DECnet-Plus software at 18:00; Please log out."   I               If possible, give users an estimated time when they will be +               able to log in to the system.   I                         Preparing to Install DECnet-Plus for OpenVMS 1-13                          I                                                                         2 I         _________________________________________________________________   I                                                    Pre-Installation Tasks     H               Before installing the HP DECnet-Plus for OpenVMS software,B               complete the installation planning checklist in thisE               chapter. This ensures that you have the information you D               need to complete the installation and configuration inD               the minimum amount of time. In addition to identifyingC               necessary information and directing you to sources of G               help, the checklist also assists you in choosing optional                software.   F         2.1 Information Required to Complete the Installation Planning             Checklist   B               Determine the following information before you beginF               the installation and configuration procedure. Enter thisB               information on your installation planning checklist:  G               o  System's full name (you may have a DECdns full name, a F                  Local namespace full name, and a fully qualified host<                  name for the Domain Name System [DNS/BIND])                 o  Node synonym   G               o  Phase IV-compatible address to interface with Phase IV                   nodes                  o  Phase IV prefix                  o  Network address  +         2.2 Installation Planning Checklist   H               Complete the checklist in Table 2-1 before continuing with'               the installation process.       I                                                Pre-Installation Tasks 2-1                     Pre-Installation Tasks+         2.2 Installation Planning Checklist     I               Table_2-1_Installation_Planning_Checklist__________________   I               Question_____________________Yes__No___For_More_Information   4               Have you backed up your      <  > <  >               system disk?  '               If not, then do so before )               you start the installation.   I               ___________________________________________________________   F               Will the system get network  <  > <  > See Section 6.4.1F               addresses from a DECdns                and Section 6.4.2               name server?  !               If yes, what is the "               system's DECdns node                name (for example,               ACME:.BOSTON)?  I               ___________________________________________________________   F               Will the system store        <  > <  > See Section 6.4.1F               network addresses in a                 and Section 6.4.2               Local database?   !               If yes, what is the !               system's Local node                 name (for example,               LOCAL:.BOSTON)?   I               ___________________________________________________________   F               Is TCP/IP installed on the   <  > <  > See Section 6.4.1F               system? Will the system                and Section 6.4.2(               store network addresses in$               the DNS/BIND database?  !               If yes, what is the )               system's DNS/BIND name (for (               example, BOSTON.ACME.COM)?  I               ___________________________________________________________   F               What is the system's node              See Section 6.4.3#               synonym (for example,                BOSTON)?  I                                                  (continued on next page)   "         2-2 Pre-Installation Tasks           I                                                    Pre-Installation Tasks I                                       2.2 Installation Planning Checklist     I               Table_2-1_(Cont.)_Installation_Planning_Checklist__________   I               Question_____________________Yes__No___For_More_Information   I               ___________________________________________________________   F               Will the system communicate  <  > <  > See Section 6.5.3F               with Phase IV nodes?                   and Section 6.5.4  $               o  Phase IV-compatible&                  address (for example,                  2.38)  %               o  Phase IV Prefix (the !                  default is 49::)   I               ___________________________________________________________   H               Will the system              <  > <  > See Section 6.5.5.1'               autoconfigure its network                addresses?  #               If not, you will need                 network entity ti-                tles (for example,6               47:24:02-01-0A-04:08-00-2B-93-ED-99:00).  I               ___________________________________________________________   I               Do you want to install       <  > <  > Refer to the DECnet- I               DECdns server software?                Plus Planning Guide.   I               ___________________________________________________________   I               Do you want to install       <  > <  > Refer to the DECnet- I               DECdts server software?                Plus Planning Guide.   I               ___________________________________________________________   I                                                  (continued on next page)           I                                                Pre-Installation Tasks 2-3                     Pre-Installation Tasks+         2.2 Installation Planning Checklist     I               Table_2-1_(Cont.)_Installation_Planning_Checklist__________   I               Question_____________________Yes__No___For_More_Information   G               (For OpenVMS VAX only.) Do   <  > <  > Refer to Part III. &               you want to install X.25%               functionality and WANDD                software for VAX?   #               You must install this %               software if you want to '               use any of the following:   '               -  Non-LAN connections to                   the network  )               -  Routing over synchronous                   connections  #               -  X.25 software over "                  synchronous lines  '               -  LAN X.25 (LLC Class 2)   !               -  DECnet over X.25   I               ___________________________________________________________   I                                                  (continued on next page)                                 "         2-4 Pre-Installation Tasks           I                                                    Pre-Installation Tasks I                                       2.2 Installation Planning Checklist     I               Table_2-1_(Cont.)_Installation_Planning_Checklist__________   I               Question_____________________Yes__No___For_More_Information   F               (For OpenVMS I64 and         <  > <  > Refer to Part IV.%               OpenVMS Alpha only.) Do &               you want to install X.25               for OpenVMS?  #               You must install this %               software if you want to '               use any of the following:   $               -  X.25 communications'                  via a connector system                    (Client system)  $               -  X.25 communications(                  directly from the local'                  system (Direct Connect                   system)  '               -  X.25 communications on (                  behalf of other systems#                  (Connector system)   '               -  LAN X.25 (LLC Class 2)   !               -  DECnet over X.25   I               ___________________________________________________________   E               Do you want to install       <  > <  > Refer to Part V. %               DECnet-Plus for OpenVMS                OSAK software?  '               If you plan to use an OSI )               application such as FTAM or (               Virtual Terminal, you must$               install this software.  I               ___________________________________________________________   I                                                  (continued on next page)   I                                                Pre-Installation Tasks 2-5                     Pre-Installation Tasks+         2.2 Installation Planning Checklist     I               Table_2-1_(Cont.)_Installation_Planning_Checklist__________   I               Question_____________________Yes__No___For_More_Information   E               Do you want to install       <  > <  > Refer to Part V. %               DECnet-Plus for OpenVMS                FTAM software?  '               If you plan to copy files $               to and from other OSI-"               compliant systems or$               manage such files, you)               must install this software.   I               ___________________________________________________________   E               Do you want to install       <  > <  > Refer to Part V. %               DECnet-Plus for OpenVMS #               Virtual Terminal (VT)                software?   $               If you plan to support&               remote logins and access'               to remote applications on (               OSI-compliant systems, youI               must_install_this_software.________________________________                                       "         2-6 Pre-Installation Tasks                         I                                                                         3 I         _________________________________________________________________   I                                        Installing DECnet-Plus for OpenVMS     E               The HP DECnet-Plus for OpenVMS distribution software is I               provided on compact disc (CD-ROM). The software consists of '               the following components:   B               Components for OpenVMS I64 and OpenVMS Alpha Systems                  o  Base Components  4                  -  DECnet-Plus for OpenVMS base kit  !                  -  DECdns server   !                  -  DECdts server   D               o  X.25 for OpenVMS (separate kit; requires a separate                  license)   H                  -  Wide Area Network Device Drivers (WANDD) for OpenVMS)                     I64 and OpenVMS Alpha   H               o  Optional OSI applications software components (includedD                  with the base kit but must be installed separately)  2                  -  OSI Applications Kernel (OSAK)  D                  -  OSI File Transfer, Access, and Management (FTAM)  -                  -  OSI Virtual Terminal (VT)   0               Components for OpenVMS VAX Systems                  o  Base Components  4                  -  DECnet-Plus for OpenVMS base kit  D                  -  X.25 functionality for OpenVMS VAX (formerly VAX                     P.S.I.)   )                  -  WANDD for OpenVMS VAX   !                  -  DECdns server   !                  -  DECdts server   I                                    Installing DECnet-Plus for OpenVMS 3-1            *         Installing DECnet-Plus for OpenVMS      H               o  Optional OSI applications software components (includedD                  with the base kit but must be installed separately)                    -  OSAK                    -  FTAM                    -  VT                                                                          .         3-2 Installing DECnet-Plus for OpenVMS           I                                        Installing DECnet-Plus for OpenVMS       F                 ________________________ Note ________________________  D                 The DECnet-Plus base components, OSAK, FTAM, and VT,E                 are all packaged as separate installation kits on the D                 distribution CD-ROM. They are usually located in theB                 same directory. The X.25 for OpenVMS kit, however,B                 is a separately licensed product and as such is inA                 a different directory on the distribution CD-ROM. @                 Consult the documentation with your distribution?                 medium for the location of the kits you desire.   F                 ______________________________________________________  I               Use the POLYCENTER Software Installation utility to install A               the base components and any combination of optional E               components. See the OpenVMS System Management Utilities I               Reference Manual for information on using the DCL interface @               with the POLYCENTER Software Installation utility.  5         3.1 Recommended Order for Installing Software   D               The following sections describe the order in which youB               should install the DECnet-Plus for OpenVMS software.  G         3.1.1 Installing DECnet-Plus on an OpenVMS I64 or OpenVMS Alpha                System  @               If you choose to install all the software productsA               at the same time, install and configure the OpenVMS D               operating system and layered products in the followingF               order, referring to the appropriate documentation. For aE               quick reference, see Figure 3-1. After OpenVMS has been 5               installed, perform the following steps:   G               1. Locate the distribution kit. Access the online Release B                  Notes. Verify required hardware. See Sections 1.1                  through 1.4.   G               2. Verify that all prerequisite software and licenses are 5                  installed. See Sections 1.5 and 1.6.   G               3. Back up the system disk. Shut down all network-related I                  applications and tell users to log out. See Sections 1.8                   and 1.9.   B               4. Install DECnet-Plus for OpenVMS. See Section 3.3.  I                                    Installing DECnet-Plus for OpenVMS 3-3            *         Installing DECnet-Plus for OpenVMS5         3.1 Recommended Order for Installing Software     F               5. If necessary, set any required system parameters. See                  Section 1.7.   #               6. Reboot the system.   F               7. Install X.25 for OpenVMS and WANDD, if necessary. See*                  Chapter 9 and Chapter 10.  D               8. Configure DECnet-Plus for OpenVMS. See Chapter 4 toF                  determine which configuration option to choose: FAST,B                  BASIC, or ADVANCED. For a FAST configuration, seeE                  Chapter 5. For BASIC or ADVANCED configurations, see                   Chapter 6.   H               9. Configure X.25 for OpenVMS. See the HP X.25 for OpenVMS&                  Configuration manual.  D              10. Install and configure the optional OSI applicationsI                  software components (OSAK, FTAM, and VT). See Chapter 12                    and Chapter 13.                                                  .         3-4 Installing DECnet-Plus for OpenVMS           I                                        Installing DECnet-Plus for OpenVMS I                             3.1 Recommended Order for Installing Software                                                                                               I                                    Installing DECnet-Plus for OpenVMS 3-5            *         Installing DECnet-Plus for OpenVMS5         3.1 Recommended Order for Installing Software     =         3.1.2 Installing DECnet-Plus on an OpenVMS VAX System   @               If you choose to install all the software productsA               at the same time, install and configure the OpenVMS D               operating system and layered products in the followingF               order, referring to the appropriate documentation. For aE               quick reference, see Figure 3-2. After OpenVMS has been /               installed, perform the following:   G               1. Locate the distribution kit. Access the online Release B                  Notes. Verify required hardware. See Sections 1.1                  through 1.4.   G               2. Verify that all prerequisite software and licenses are 5                  installed. See Sections 1.5 and 1.6.   G               3. Back up the system disk. Shut down all network-related I                  applications and tell users to log out. See Sections 1.8                   and 1.9.   B               4. Install DECnet-Plus for OpenVMS. See Section 3.3.  F                 ________________________ Note ________________________  C                 If you want to install X.25 functionality (formerly C                 VAX P.S.I.), select the option now while installing (                 DECnet-Plus for OpenVMS.  F                 ______________________________________________________  F               5. If necessary, set any required system parameters. See                  Section 1.7.   #               6. Reboot the system.   D               7. Configure DECnet-Plus for OpenVMS. See Chapter 4 toF                  determine which configuration option to choose: FAST,B                  BASIC, or ADVANCED. For a FAST configuration, seeF                  Chapter 5. For a BASIC or ADVANCED configuration, see                  Chapter 6.   H               8. Configure X.25 functionality (formerly VAX P.S.I.). See                  Chapter 8.   D               9. Install and configure the optional OSI applicationsH                  software component (OSAK, FTAM, and VT). See Chapter 12                   and Chapter 13.  .         3-6 Installing DECnet-Plus for OpenVMS           I                                        Installing DECnet-Plus for OpenVMS I                             3.1 Recommended Order for Installing Software                                                                                               I                                    Installing DECnet-Plus for OpenVMS 3-7            *         Installing DECnet-Plus for OpenVMS'         3.2 PCSI Process Account Quotas     '         3.2 PCSI Process Account Quotas   H               The POLYCENTER Software Installation utility requires thatD               the installation account has, as a minimum, the quotas!               shown in Table 3-1.   I               Table_3-1_Process_Quotas_for_the_Installing_Account________   I               Quota_____Value____________________________________________                  ASTLM     24                 BIOLM     18                 BYTLM     32768                  DIOLM     18                 ENQLM     200   I               FILLM_____100______________________________________________   D               Use the OpenVMS Authorize utility to verify and changeE               process quotas for the installation account in the user G               authorization file (sysuaf.dat). (Some sites may restrict A               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               ___________________________________________________________ I               To..._______________Enter..._______________________________   <               Invoke the          $ run sys$system:authorize               Authorize utility   8               Show the account    UAF> show account-name               quotas  I               Modify the BYTLM    UAF> modify account-name /BYTLM = 32768                quota   +               Exit from the       UAF> exit                Authorize utility   I               Log_out_____________$_logout_______________________________   I               After you verify and change the quotas for the installation E               account, log out of the installation account and log in   .         3-8 Installing DECnet-Plus for OpenVMS           I                                        Installing DECnet-Plus for OpenVMS I                                           3.2 PCSI Process Account Quotas     H               again. The new quotas will take effect and you can proceed$               with the installation.  H               User account quotas are stored in the sysuaf.dat file. ForF               more information about modifying account quotas, see theH               description of the Authorize utility in the OpenVMS system.               management documentation subkit.  @         3.3 Installing DECnet-Plus Using the POLYCENTER Software              Installation Utility  E               This section describes the steps for installing DECnet- F               Plus software using the POLYCENTER Software InstallationF               utility. You must have SYSPRV privileges on the local or=               remote node where you want to run this utility.   F                 ________________________ Note ________________________  E                 Kits included on the OpenVMS Version 8.3 distribution 7                 media are signed using Secure Delivery.   F                 ______________________________________________________  =         3.3.1 DECnet-Plus for OpenVMS I64 Installation Dialog   <               To start the installation, follow these steps:  .               1. Log in to the SYSTEM account.  I               2. Mount the Software Products Library media CD-ROM, locate G                  the DECnet-Plus distribution directory, and define the E                  PCSI$SOURCE logical name to reference the directory. C                  See Section 1.1 for information about locating the "                  distribution kit.  -               3. Enter the following command:   .                  $ product install DECNET_PLUS  F                  For a description of all the features you can requestI                  when starting an installation (such as purging files and G                  using a product configuration file), refer to DCL help 1                  for the product install command.   F                  The actual kit location may change with new releases.C                  See Section 1.1 for information about locating the "                  distribution kit.  I                                    Installing DECnet-Plus for OpenVMS 3-9            *         Installing DECnet-Plus for OpenVMSU         3.3 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility     F               You are then prompted for installation information as inG               the following example. In this example, numbered callouts G               (1, 2, 3, . . . ) guide you through the sequence of steps )               that require your response.   4                Performing product kit validation .../                %PCSI-I-VALPASSED, validation of V                DKB200:[KITS]HP-I64VMS-DECNET_PLUS-V0803--1.PCSI$COMPRESSED;1 succeeded  7                The following product has been selected: I                    HP I64VMS DECNET_PLUS V8.3             Layered Product   7               1 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.  K                HP I64VMS DECNET_PLUS V8.3: DECnet-Plus V8.3 for OpenVMS I64   K                    Copyright 2006 Hewlett-Packard Development Company, L.P.   *                    Hewlett-Packard Company  O                    This product requires one of two PAKs: DVNETEND or DVNETEXT.   K               2 Do you want the defaults for all options? [YES] NO <return>   2                    HP I64VMS VMS V8.3  [Installed]  M                    * Configuration options for this referenced product cannot M                    * be changed now because the product is already installed. O                    * (You can use PRODUCT RECONFIGURE later to change options.)   2                    DECdns Server software [NO] YES  2                    DECdts Server software [NO] YES  D               3 Do you want to review the options? [NO] YES <return>  K                HP I64VMS DECNET_PLUS V8.3: DECnet-Plus V8.3 for OpenVMS I64 2                    HP I64VMS VMS V8.3  [Installed].                    DECdns Server software: YES.                    DECdts Server software: YES  D               4 Are you satisfied with these options? [YES] <return>  +                Execution phase starting ...   F                The following product will be installed to destination:Q                    HP I64VMS DECNET_PLUS V8.3             DISK$XBAI:[VMS$COMMON.]   /         3-10 Installing DECnet-Plus for OpenVMS            I                                        Installing DECnet-Plus for OpenVMS I  DECnet-Plus           Using the POLYCENTER Software Installation Utility     V                Portion done: 0%...10%...20%...30%...40%...50%...60%...80%...90%...100%  8                The following product has been installed:I                    HP I64VMS DECNET_PLUS V8.3             Layered Product                 $  I               1  At this point, you can stop the installation process. If I                  you want to continue, press Return. If you want to stop, *                  type NO and press Return.  H               2  This question allows you to select which optional partsG                  of the DECnet-Plus base components product you want to H                  install. If you want to take the installation defaults,B                  press Return. If you want to select each optionalI                  DECnet-Plus base component (for example, DECdns Server), H                  type NO and press Return. The procedure then displays a)                  list of choices for you.   C               3  This question allows you to review and change your G                  current selections. Type YES if you are satisfied with E                  the current selected options. Type NO if you want to                   make changes.  D               4  Responding NO to this question causes the procedure@                  to reprompt you to enter values for each of the@                  installation options. If you are satisfied withD                  the options, press Return to accept the default YES                  response.  ?         3.3.2 DECnet-Plus for OpenVMS Alpha Installation Dialog   <               To start the installation, follow these steps:  .               1. Log in to the SYSTEM account.  I               2. Mount the Software Products Library media CD-ROM, locate G                  the DECnet-Plus distribution directory, and define the E                  PCSI$SOURCE logical name to reference the directory. C                  See Section 1.1 for information about locating the "                  distribution kit.  -               3. Enter the following command:   -                  $ product install DECnet_OSI   F                  For a description of all the features you can requestI                  when starting an installation (such as purging files and G                  using a product configuration file), refer to DCL help 1                  for the product install command.   I                                   Installing DECnet-Plus for OpenVMS 3-11            *         Installing DECnet-Plus for OpenVMSU         3.3 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility     F                  The actual kit location may change with new releases.C                  See Section 1.1 for information about locating the "                  distribution kit.  F               You are then prompted for installation information as inG               the following example. In this example, numbered callouts G               (1, 2, 3, . . . ) guide you through the sequence of steps )               that require your response.   4                Performing product kit validation .../                %PCSI-I-VALPASSED, validation of V                DKB500:[KITS]DEC-AXPVMS-DECNET_OSI-V0803--1.PCSI$COMPRESSED;1 succeeded  7                The following product has been selected: I                    DEC AXPVMS DECNET_OSI V8.3             Layered Product   7               1 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.  K                DEC AXPVMS DECNET_OSI V8.3: DECnet-Plus V8.3 for OpenVMS AXP   K                    Copyright 2006 Hewlett-Packard Development Company, L.P.   *                    Hewlett-Packard Company  O                    This product requires one of two PAKs: DVNETEND or DVNETEXT.   K               2 Do you want the defaults for all options? [YES] NO <return>   @                Do you want to change any options? [YES] <return>  3                    DEC AXPVMS VMS V8.3  [Installed]   M                    * Configuration options for this referenced product cannot M                    * be changed now because the product is already installed. O                    * (You can use PRODUCT RECONFIGURE later to change options.)   2                    DECdns Server software [NO] YES  2                    DECdts Server software [NO] YES  @               3 Do you want to review the options? [NO] <return>  +                Execution phase starting ...   F                The following product will be installed to destination:Q                    DEC AXPVMS DECNET_OSI V8.3             DISK$XBAJ:[VMS$COMMON.]   P                Portion done: 0%...10%...20%...30%...40%...50%...80%...90%...100%  /         3-12 Installing DECnet-Plus for OpenVMS            I                                        Installing DECnet-Plus for OpenVMS I  DECnet-Plus           Using the POLYCENTER Software Installation Utility     8                The following product has been installed:I                    DEC AXPVMS DECNET_OSI V8.3             Layered Product                 $  I               1  At this point, you can stop the installation process. If I                  you want to continue, press Return. If you want to stop, ,                  type NO, then press Return.  H               2  This question allows you to select which optional partsG                  of the DECnet-Plus base components product you want to H                  install. If you want to take the installation defaults,B                  press Return. If you want to select each optionalI                  DECnet-Plus base component (for example, DECdns Server), H                  type NO and press Return. The procedure then displays a)                  list of choices for you.   C               3  This question allows you to review and change your G                  current selections. Type YES if you are satisfied with E                  the current selected options. Type NO if you want to                   make changes.  =         3.3.3 DECnet-Plus for OpenVMS VAX Installation Dialog   <               To start the installation, follow these steps:  .               1. Log in to the SYSTEM account.  I               2. Mount the Software Products Library media CD-ROM, locate G                  the DECnet-Plus distribution directory, and define the E                  PCSI$SOURCE logical name to reference the directory. C                  See Section 1.1 for information about locating the "                  distribution kit.  -               3. Enter the following command:   -                  $ product install DECnet_OSI   F                  For a description of all the features you can requestI                  when starting an installation (such as purging files and G                  using a product configuration file), refer to DCL help 1                  for the product install command.   F                  The actual kit location may change with new releases.C                  See Section 1.1 for information about locating the "                  distribution kit.  I                                   Installing DECnet-Plus for OpenVMS 3-13            *         Installing DECnet-Plus for OpenVMSU         3.3 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility     F               You are then prompted for installation information as inG               the following example. In this example, numbered callouts G               (1, 2, 3, . . . ) guide you through the sequence of steps )               that require your response.   7                The following product has been selected: B                    DEC VAXVMS DECnet_OSI V7.3      Layered Product  7               1 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.  K                DEC VAXVMS DECnet_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAX   K                    Copyright 2004 Hewlett-Packard Development Company, L.P.   *                    Hewlett-Packard Company  O                    This product requires one of two PAKS: DVNETEND or DVNETRTG.   K               2 Do you want the defaults for all options? [YES] NO <Return>   &                    DEC VAXVMS VMS V7.3  M                    * Configuration options for this referenced product cannot M                    * be changed now because the product is already installed. O                    * (You can use PRODUCT RECONFIGURE later to change options.)   @                    VAX P.S.I. or P.S.I. Access software [NO]: NO  8                    VAX Wide Area Device Drivers [NO]: NO  1                    DECdns Server software [NO] NO   1                    DECdts Server software [NO] NO   D               3 Do you want to review the options? [NO] YES <Return>K                DEC VAXVMS DECnet_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAX 2                    DEC VAXVMS VMS V7.3 [Installed];                    VAX P.S.I. or P.S.I. Access software: NO 3                    VAX Wide Area Device Drivers: NO -                    DECdns Server software: NO -                    DECdts Server software: NO   :                Are you satisfied with these options? [YES]  +                Execution phase starting ...   7                The following product will be installed: -                    DEC VAXVMS DECnet_OSI V7.3   /         3-14 Installing DECnet-Plus for OpenVMS            I                                        Installing DECnet-Plus for OpenVMS I  DECnet-Plus           Using the POLYCENTER Software Installation Utility     P                Portion Done: 0%...10%...20%...30%...40%...50%...80%...90%...100%  8                The following product has been installed:1                        DEC VAXVMS DECnet_OSI V7.3   I               1  At this point, you can stop the installation process. If I                  you want to continue, press Return. If you want to stop, ,                  type NO, then press Return.  H               2  This question allows you to select which optional partsG                  of the DECnet-Plus base components product you want to H                  install. If you want to take the installation defaults,B                  press Return. If you want to select each optionalF                  DECnet-Plus base component (for example, VAX P.S.I.),H                  type NO and press Return. The procedure then displays a)                  list of choices for you.   C               3  This question allows you to review and change your G                  current selections. Type YES if you are satisfied with E                  the current selected options. Type NO if you want to                   make changes.  2         3.4 Rights Identifiers Added to the System  I               During the final phase of the installation process, several F               rights identifiers are created in the rights identifiersI               database. If you are installing from the system console and F               have the Audit Server properly enabled, it alerts you asH               these rights are added. In addition, the NET$MANAGE rights:               identifier is granted to the SYSTEM account.  E               Table 3-2 lists the rights identifiers added during the G               installation. See the "Managing Network Security" chapter I               in the HP DECnet-Plus for OpenVMS Network Management manual B               for more information about these rights identifiers.  I               Table_3-2_Rights_Identifiers_______________________________   I               Rights_Identifier_____Description__________________________   ;               NET$DECLAREOBJECT     Declares an application   I                                                  (continued on next page)     I                                   Installing DECnet-Plus for OpenVMS 3-15            *         Installing DECnet-Plus for OpenVMS2         3.4 Rights Identifiers Added to the System    I               Table_3-2_(Cont.)_Rights_Identifiers_______________________   I               Rights_Identifier_____Description__________________________   B               NET$DECNETACCESS      Gives $IPC users access to theH                                     network in the absence of the NETMBX-                                     privilege   F               NET$DIAGNOSE          Permits use of network diagnostics  H               NET$EXAMINE           Permits display of the attributes of-                                     an entity   A               NET$MANAGE            Permits display, creation, or =                                     modification of an entity   =               NET$POSTEVENT         Permits posting of events   ;               NET$REGISTERDNSOBJECT Permits registration or E                                     deregistration of a DECdns object   C               NET$SECURITY          Permits setting a user name for F                                     session control or session control/                                     application   I               NET$TRACEALL          Permits tracing of entire messages on 0                                     a local node  I               NET$TRACEALLREMOTE    Permits tracing of entire messages on 1                                     a remote node   I               NET$TRACEHEADERS      Permits tracing of message headers on 0                                     a local node  I               NET$TRACEHEADERSREMOTEPermits tracing of message headers on I               ______________________a_remote_node________________________   )         3.5 Files Installed on the System   I               The DECnet-Plus installation procedure installs a number of G               files on your system. To list the files, enter one of the 7               following commands (see also Appendix A):   &               For OpenVMS I64 systems:  8               $ product show object /product=decnet_plus  8               For OpenVMS Alpha and OpenVMS VAX systems:  7               $ product show object /product=decnet_osi   /         3-16 Installing DECnet-Plus for OpenVMS            I                                        Installing DECnet-Plus for OpenVMS I                                                  3.6 Rebooting the System               3.6 Rebooting the System  F               After completing the installation of the DECnet-Plus forB               OpenVMS software, you must reboot your system beforeE               beginning the configuration process. Because the system D               has not been configured yet, you may see the following-               messages during system startup:   F               Copyright 2006 Hewlett-Packard Development Company, L.P.R               %NET$STARTUP-W-NONETCONFIG, this node has not been configured to run'                 DECnet-Plus for OpenVMS W                       use SYS$MANAGER:NET$CONFIGURE.COM if you wish to configure DECnet Z               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is OFF  F               Proceed to Chapter 4 for information about selecting the?               configuration option appropriate for your system.                                                           I                                   Installing DECnet-Plus for OpenVMS 3-17                          I                                                                   Part II I         _________________________________________________________________   I                                       Configuring DECnet-Plus for OpenVMS             D               Part II provides help to determine which configurationC               option to use: FAST, BASIC, or ADVANCED. It describes D               using each of the configuration options to configure aE               new DECnet-Plus node. It also discusses using the BASIC D               or ADVANCED configuration option to modify an existing               configuration.  1               It contains the following chapters:   2               o  Chapter 4 - Configuration Options  @               o  Chapter 5 - Using the FAST Configuration Option  G               o  Chapter 6 - Using the BASIC and ADVANCED Configuration                   Options  >               o  Chapter 7 - Modifying a Current Configuration                         I                                                                         4 I         _________________________________________________________________   I                                                     Configuration Options     G               This chapter explains the three configuration options you I               can use to configure your system for the HP DECnet-Plus for F               OpenVMS software. These configuration options enable youI               to configure the DECnet-Plus for OpenVMS base components so F               that the system becomes a DECnet-Plus node on a network.  H               The procedure you use to configure your system for DECnet-G               Plus is sys$manager:net$configure.com. You can use any of @               the following net$configure configuration options:  :               o  FAST configuration option (see Chapter 5)  D                  The FAST configuration option allows you to quicklyG                  upgrade a non-clustered system from DECnet Phase IV to                    DECnet Phase V.  ;               o  BASIC configuration option (see Chapter 6)   G                  The BASIC configuration option allows you to configure I                  your system for DECnet-Plus by answering a few questions 9                  and using the default answers on others.   >               o  ADVANCED configuration option (see Chapter 6)  @                  The ADVANCED configuration option allows you to?                  customize your system's network configuration.   D               This chapter presents additional information about the               following topics:   1               o  Selecting a configuration option   &               o  Running net$configure  I               See Section 1.7.4 for a list of account privileges you need #               to run net$configure.   I                                                 Configuration Options 4-1                     Configuration Options 4         4.1 Choosing an Initial Configuration Option    4         4.1 Choosing an Initial Configuration Option  G               If you installed the required software, you can configure F               your system using the net$configure configuration optionG               for the FAST configuration, using the net$configure basic H               configuration option for the BASIC configuration, or usingE               the net$configure advanced configuration option for the %               ADVANCED configuration.   @               Table 4-1 provides some guidelines for making your#               configuration choice.                                                                     !         4-2 Configuration Options            I                                                     Configuration Options I                              4.1 Choosing an Initial Configuration Option     I         Table_4-1_Choosing_an_Initial_Configuration_Option_______________   I         Option..._Choose_if...___________________________________________   G         FAST      You are upgrading from a DECnet Phase IV node and you B                   plan to use the existing Phase IV configuration.  8                   The node is not in an OpenVMS cluster.  E                   You are running the configuration procedure for the                    first time.   I         _________________________________________________________________   4         BASIC     The node is in an OpenVMS cluster.  3                   You are upgrading to DECnet-Plus.   @                   You need to access a DECdns server for network                   addresses.  A                   You have only one communications device, or you F                   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.   H                   You want to autoconfigure your network addresses only.  G                   You want to configure both the NSP and OSI transports @                   and only want to create default OSI templates.  I                   You want to enable DECnet over TCP/IP (RFC 1859) or OSI 6                   applications over TCP/IP (RFC 1006).  I                   You do not want to enable FDDI large packet support (if 1                   you have an FDDI-type circuit).   H                   You want to set the routing characteristic DNA AddressB                   Format to TRUE (to control the interpretation of'                   address structuring).   :                   You want to use integrated mode routing.  I         _________________________________________________________________   0         ADVANCED  Your configuration is complex.  E                   You need to customize your network's configuration.   I                   Your system has multiple communication devices, and you 6                   want them to run a mix of protocols.  I                                                  (continued on next page)   I                                                 Configuration Options 4-3                     Configuration Options 4         4.1 Choosing an Initial Configuration Option    I         Table_4-1_(Cont.)_Choosing_an_Initial_Configuration_Option_______   I         Option..._Choose_if...___________________________________________   H                   You want to configure a cluster with both DECnet Phase.                   IV and DECnet Phase V nodes.  C                   You want the option to give specific names to all /                   devices and routing circuits.   D                   You want the option of not configuring all of your*                   devices for DECnet-Plus.  G                   You want the option of manually entering your network                    addresses.  G                   You want to configure either the NSP transport or the *                   OSI transport (or both).  I                   You want the option to create additional OSI templates.   G                   You want the option of enabling/disabling DECnet over 9                   TCP/IP or OSI applications over TCP/IP.   C                   You want the option of enabling FDDI large packet =                   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).   E                   You want the option of using either integrated mode 5                   routing or segregated mode routing.   E                   You want the option to provide default accounts for I         __________FAL.___________________________________________________                   !         4-4 Configuration Options            I                                                     Configuration Options H                                             4.2 How to Run NET$CONFIGURE    $         4.2 How to Run NET$CONFIGURE  D               The net$configure procedure configures the DECnet-PlusD               software. This command creates or modifies the NetworkD               Control Language (NCL) startup scripts required to run'               DECnet-Plus on your node.   E               The net$configure procedure is an interactive procedure G               that displays a series of questions. After each question, H               the default response, if there is one, appears in bracketsF               ([ ]). At the end of each question, a colon (:) appears.3               Respond in one of the following ways:   H               o  To get help after a question, type a question mark (?).E                  After the help display, the same question reappears.   >               o  To select the default response, press Return.  D               o  To enter information, type it immediately after the;                  colon or question mark; then press Return.   -               o  Type Y for YES and N for NO.   :               o  To terminate the procedure, press Ctrl/Z.  F               To invoke net$configure with the BASIC option, enter the               following:  0               $ @sys$manager:net$configure basic  I               To invoke net$configure with the ADVANCED option, enter the                following:  3               $ @sys$manager:net$configure advanced   F               If you execute net$configure without specifying basic orD               advanced, the BASIC configuration option is invoked by               default.  F                 ________________________ Note ________________________  F                 If you are running the configuration procedure for theE                 first time on a system that was previously configured F                 for Phase IV and you do not specify basic or advanced,E                 the initial default is the FAST configuration option.   ?                 However, the FAST configuration option can only A                 be run once on a system, and after that the BASIC   I                                                 Configuration Options 4-5                     Configuration Options $         4.2 How to Run NET$CONFIGURE    >                 configuration option automatically becomes the                 default.  F                 ______________________________________________________  &         4.2.1 Local and Global Symbols  G               The net$configure procedure deletes all of your local and G               global symbols at the beginning of the procedure in order G               to free the symbol table. This action is required because G               net$configure creates and uses a large number of symbols. E               If the symbols were not deleted at the beginning of the D               procedure, net$configure could run out of symbol tableG               space to use while configuring the system. In most cases, E               the configuration procedure restores your symbols as it                exits.  <         4.2.2 Running the Procedure from Different Processes  A               Although net$configure can be run simultaneously on @               different nodes in a cluster, it should not be runG               simultaneously from different processes on the same node.                                               !         4-6 Configuration Options                          I                                                                         5 I         _________________________________________________________________   I                                       Using the FAST Configuration Option     H               This chapter describes how to configure the HP DECnet-PlusF               for OpenVMS base components using the FAST configurationI               option so that the system becomes a DECnet-Plus end node on $               a DECnet-Plus network.  F                 ________________________ Note ________________________  >                 If you have already run the FAST configuration@                 procedure once on your system, the configuration=                 procedure automatically defaults to the BASIC %                 configuration option.   F                 ______________________________________________________  2         5.1 Invoking the FAST Configuration Option  B               To invoke the net$configure procedure using the FAST@               configuration option, enter the following command:  4               $ @sys$manager:net$configure  <Return>  #               The procedure starts:   F               Copyright 2006 Hewlett-Packard Development Company, L.P.  M                       DECnet-Plus for OpenVMS network configuration procedure   V                   This procedure will help you create or modify the management scriptsV                   needed to operate DECnet on this machine. You may receive help aboutG                   most questions by answering with a question mark '?'.   I               %NET$CONFIGURE-I-SETUPNEW, setting up for new configuration J               %NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found  :                                  FAST CONFIGURATION OPTION  6                    *** Not supported on cluster nodes.  I                                   Using the FAST Configuration Option 5-1            +         Using the FAST Configuration Option 2         5.1 Invoking the FAST Configuration Option    Q                    You have the option of using the existing Phase IV information V                    to quickly configure DECnet-Plus. This provides full network accessW                    and uses a local file to hold naming information. Very few questions !                    will be asked.   [                    If you want to use the fast configuration option, answer YES to the next                     question.  W                    If you are running a DNS Server on this system, or plan to run a DNS T                    Server on this system, you *must* answer NO to the next question.Y                    If you want more flexibility when configuring DECnet-Plus, also answer                     NO.  P                    Answering NO will cause some additional questions to be asked+                    regarding configuration.   V               * Do you want the fast default configuration?          [YES] :  <Return>  B               Press Return to continue with the FAST configuration               option.   B               The procedure informs you that the Phase IV databaseB               conversion has completed. The procedure also createsI               several accounts for the standard DECnet-Plus applications. =               (Note that, in the interest of clarity, several I               AUDIT$SERVER-related OPCOM messages related to this account F               creation and modification process have been omitted from               this example.)  R               %NET$CONFIGURE-I-PHASEIVCOMPL, Phase IV database conversion complete  I               Determining DTSS timezone rules from OpenVMS information...   O               %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates [               %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration Z               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVERZ               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER\               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER  ?               The procedure continues by displaying the current F               system configuration and asking if you want to apply the               configuration:      /         5-2 Using the FAST Configuration Option            I                                       Using the FAST Configuration Option I                                5.1 Invoking the FAST Configuration Option     .                       Summary of Configuration                   Node Information:  ;                       Directory Services Chosen:      LOCAL ;                       Primary Directory Service:      LOCAL 4                       Node Synonym:           ASHFLD3                       Phase IV Address:       4.260 2                       Phase IV Prefix:        49::H                       Session Control Address Update Interval:        105                       Routing Node Type:      ENDNODE E                       Autoconfiguration of Network Addresses: Enabled 1                       Routing ESHello Timer:  600 1                       Routing ES Cache Size:  512   "                Device Information:  *                       Device: EWA (TULIP):3                               Data Link name: EWA-0 ;                               Routing Circuit Name:   EWA-0   %                Transport Information:   B                       NSP Transport:                    ConfiguredA                          Maximum number of logical links:     200 @                          Maximum Transmit and Receive Window: 20B                          Maximum Receive Buffers:             4000R                          Flow Control Policy:                 Segment Flow Control  3                       Congestion Avoidance Disabled   .                Event Dispatcher Configuration:  2                       Sinks:            local_sink4                       Outbound Streams: local_stream/                       Phase IV Relay:   Enabled   V               * Do you want to apply this configuration?             [YES] :  <Return>  G               Answer YES to apply this configuration. If you answer NO, G               the procedure defaults to the BASIC configuration option.   E               If you answer YES, the procedure displays the following                message:  L               %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts  G               The procedure then asks if you want to start the network:   U                * Do you want to start the network?                  [YES] :  <Return>   I                                   Using the FAST Configuration Option 5-3            +         Using the FAST Configuration Option 2         5.1 Invoking the FAST Configuration Option    F               Answer YES if you want to start the network and complete2               your system's network configuration.  F               If you want to postpone starting the network, answer NO.F               When you answer NO, the procedure displays the following               warning:  R               ********************************************************************J               You have decided not to start the network. NET$CONFIGURE.COMP               cannot complete your system's network configuration since it needsM               the network to be partially started in order to perform certain R               operations.  As a result, your system may be left in an inconsistentO               state if you try to startup the network manually or if you decide $               to reboot your system.  H               Once you are ready to start the network, please invoke theL               NET$CONFIGURE.COM procedure, choose menu Option 2 (Change nodeN               name/namespace name), and respond YES to starting the network soO               that the configuration procedure can finish your system's network                configuration.R               ********************************************************************  F               HP recommends that you answer YES and start the network.  H               If you choose to start the network, the procedure displaysE               information similar to the following (note that not all I               net$startup messages are shown and that OPCOM messages have                been omitted):  F               Copyright 2006 Hewlett-Packard Development Company, L.P.C               %NET-I-LOADED, executive image LES$LES_V30.EXE loaded A               %NET-I-LOADED, executive image NET$ALIAS.EXE loaded K               %NET-I-LOADED, executive image NET$SESSION_CONTROL.EXE loaded                   .                  .                  .@               %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script8                 SYS$SYSROOT:[SYSMGR]NET$NODE_STARTUP.NCL@               %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script:                 SYS$SYSROOT:[SYSMGR]NET$CSMACD_STARTUP.NCL                  .                  .                  .V               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is                 RUNNING-MAJOR   2               Directory Service: Phase IV database  /         5-4 Using the FAST Configuration Option            I                                       Using the FAST Configuration Option I                                5.1 Invoking the FAST Configuration Option     6               Exporting node name information using: *                 ASHFLD*               Number of nodes exported:  1  0               Directory Service: Local name file  H               Updating nodes listed in SYS$MANAGER:NET$PHASEIV_NODES.DAT                 ASHFLD,               Number of nodes registered:  1,               Number of nodes modified:    0  R               %NET$CONFIGURE-I-CONVERTNODEDB, converted the Phase IV node databaseV               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.ASHFLDJ               %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entriesF               Copyright 2006 Hewlett-Packard Development Company, L.P.?               %NET$STARTUP-I-STARTPROCESS, starting process EVD @               %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script9                 SYS$SYSROOT:[SYSMGR]NET$EVENT_STARTUP.NCL                   .                  .                  .V               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is                 RUNNING-ALL _               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed                $   B               You have just completed the initial configuration ofF               DECnet-Plus. It should now be operational as an end node               on the network.   G               See Figure 3-1 or Figure 3-2 to determine your next step. B               According to the flowcharts, you have just completed&               configuring DECnet-Plus.  @         5.2 Modifying a Current DECnet-Plus System Configuration  C               You can use the net$configure procedure to modify the G               current configuration. Depending on which menu option you E               select, net$configure either modifies the configuration I               automatically or produces modified NCL startup scripts that ?               you can use to modify the system's configuration.   =               See Chapter 7 for information about running the D               net$configure BASIC or ADVANCED options to modify your(               DECnet-Plus configuration.  I                                   Using the FAST Configuration Option 5-5                          I                                                                         6 I         _________________________________________________________________   I                        Using the BASIC and ADVANCED Configuration Options     F               This chapter describes the BASIC and ADVANCED options ofI               the net$configure.com procedure. Most sections begin with a G               general explanation of the configuration dialog discussed H               in the section. When the configuration dialog is common to<               both options, no special presentation is used.                 BASIC   E               If a portion of the configuration dialog description is H               unique to the BASIC option, the description is preceded by/               a BASIC subheading as shown here.                  ADVANCED  E               If a portion of the configuration dialog description is H               unique to the ADVANCED option, the description is preceded6               by an ADVANCED subheading as shown here.                  BASIC and ADVANCED  F               In certain rare cases, the BASIC and ADVANCED subheadingF               is used to denote that the description is common to both               options.  0         6.1 Invoking the Configuration Procedure  <               Begin by invoking the configuration procedure.                 BASIC   C               To invoke the net$configure procedure using the BASIC @               configuration option, enter the following command:  0               $ @sys$manager:net$configure basic                 ADVANCED  F               To invoke the net$configure procedure using the ADVANCED@               configuration option, enter the following command:  3               $ @sys$manager:net$configure advanced   I                    Using the BASIC and ADVANCED Configuration Options 6-1            :         Using the BASIC and ADVANCED Configuration Options         6.2 Opening Messages             6.2 Opening Messages  F               The procedure prints an opening message dependent on the.               configuration option you choose.                 BASIC   F               Copyright 2006 Hewlett-Packard Development Company, L.P.                     DECnet- >         Plus for OpenVMS BASIC network configuration procedure  R               This procedure will help you create or modify the management scriptsR               needed to operate DECnet on this machine. You may receive help aboutC               most questions by answering with a question mark '?'.   R               You have chosen the BASIC configuration option.  This option enablesS               you to quickly configure your system by answering a few questions and V               using most of the default answers.  If you would rather do some specificR               tailoring of your  system's network configuration, you should invokeK               NET$CONFIGURE.COM with the ADVANCED configuration option, ie: @                              @SYS$MANAGER:NET$CONFIGURE ADVANCED                 ADVANCED  F               Copyright 2006 Hewlett-Packard Development Company, L.P.                    DECnet-A         Plus for OpenVMS ADVANCED network configuration procedure   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                   BASIC and ADVANCED  D               If the procedure detects that the DECnet-Plus softwareH               has not been properly installed, it displays the following               warning:  >         6-2 Using the BASIC and ADVANCED Configuration Options           I                        Using the BASIC and ADVANCED Configuration Options I                                                      6.2 Opening Messages     Q                    The base DECnet system components are not yet properly loaded. N                    DECnet cannot be started until the DECnet software has beenK                    successfully installed and the system has been rebooted.   W                    NET$CONFIGURE may fail if you answer YES to the next question.  That S                    is because it may be necessary to start the network to establish V                    certain configurations.  Hewlett-Packard recommends that you reboot>                    before attempting to configure the network.  F               Next, the procedure asks if you want to proceed with the               configuration.  L               * Do you want to continue?                             [YES] :  >               Press Return to continue with the configuration.  D               The procedure now checks for the privileges and rightsF               identifiers required to run the net$configure procedure.G               For a list of required privileges and rights identifiers,                 see Section 1.7.4.  H               If the procedure finds insufficient process privileges, it8               displays the following messages and exits:  P               %NET$CONFIGURE-E-NOREQPRIV, privilege-list privileges are requiredU               %NET$CONFIGURE-E-NOPRIV, insufficient privileges to run this procedure.   H               If the procedure finds insufficient rights identifiers, it8               displays the following messages and exits:  T               NET$CONFIGURE-E-NOREQRIGHTSID, rights id rights-identifier not granted`               %NET$CONFIGURE-E-NORIGHTSID, insufficient rights identifiers to run this procedure  H               If you have the required privileges and rights identifiersA               and if this is the first time that you have run the E               configuration procedure, the procedure informs you that G               you are configuring your DECnet-Plus system for the first                time:   I               %NET$CONFIGURE-I-SETUPNEW, setting up for new configuration   W                    Now you will be asked a few questions.  If you need more information V                    to answer a question, you can type ? at the prompts, or consult theT                    DECnet-Plus for OpenVMS Installation and Configuration guide.  ToW                    configure DECnet, you need to know your node's full name and network X                    address(es).  Please review the Installation and Configuration guide,G                    and the checklists in particular, before continuing.   I                    Using the BASIC and ADVANCED Configuration Options 6-3            :         Using the BASIC and ADVANCED Configuration Options2         6.3 Specifying Phase IV Conversion Options    2         6.3 Specifying Phase IV Conversion Options  H               If a Phase IV database exists on the system, the procedureF               displays the following a message and asks if you want to#               convert the database:   J               %NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found  R                    A Phase IV database exists on your system.  You have the optionV                    of using the existing Phase IV database to generate the NCL scriptsT                    and configure the system.  If you do not want to use the existingR                    Phase IV database to generate the NCL scripts and configure theU                    system, then net$configure will configure the system based on your :                    answers to the configuration questions.  L               * Do you want to convert Phase IV databases?           [YES] :  H               If you answer NO, the net$configure procedure does not useI               the system's existing Phase IV database to generate the NCL G               startup scripts and proceeds to ask all the configuration 0               questions. Proceed to Section 6.4.  E               If you answer YES, the net$configure procedure uses the E               system's existing Phase IV database to generate the NCL E               startup scripts and configure the system. The procedure C               asks the following question to determine the Phase IV 2               prefix to use during the conversion:  M               * Enter Phase IV Prefix                                [49::] :   D               Usually, when a Phase IV database is found, a Phase IVC               local node name database is also found. The procedure E               continues by asking if you want to convert the Phase IV '               local node name database:   S                    You may convert your Phase IV node database to a local node name S                    database.  This will provide node name translation if you opt to Q                    use LOCAL in the list of directory services to be used on this U                    system.  This is unnecessary if you do not intend to include LOCAL 9                    in your directory service search list.   O               * Do you want to convert the Phase IV node name database? [YES] :   G               Answer YES if you want the configuration procedure to use E               the entries in the existing Phase IV node name database B               to generate a Phase V Local namespace database. (SeeD               Section 6.4.1 for information about directory servicesG               and the Local namespace.) Answer NO if you do not want to #               convert the database.   >         6-4 Using the BASIC and ADVANCED Configuration Options           I                        Using the BASIC and ADVANCED Configuration Options I                                6.3 Specifying Phase IV Conversion Options     H               The procedure converts the Phase IV databases immediately.H               However, the conversion of the Phase IV node name databaseA               is delayed until the namespace modification section E               (see Section 6.16). The procedure indicates that it has D               successfully converted the Phase IV databases with the                following message:  Q               %NET$CONFIGURE-I-PHASEIVCMPL, Phase IV database conversion complete   F                 ________________________ Note ________________________  A                 The conversion process enables all FDDI and CSMA- @                 CD stations found in the Phase IV configuration,9                 regardless of their previous line states.   F                 ______________________________________________________  <         6.4 Configuring Node and Session Control Information  B               The process for configuring node and session control:               information consists of the following items:  (               o  Directory name services                  o  Node full names                 o  Node synonym   .               o  Naming cache timeout interval  8               o  Session control address update interval  1               o  Naming cache checkpoint interval   G               If you have installed the DECdns Server option during the G               DECnet-Plus installation process, the procedure begins by H               informing you that the DECdns server startup file is beingF               renamed and that you must configure the node as a DECdnsI               clerk before you can configure the node as a DECdns server:   N                    A SYS$STARTUP:DNS$SERVER_STARTUP.COM file has been located.Q                    This file is being renamed because the node must be configured Q                    as a DNS clerk before it can be re-configured as a DNS server.   T                    After the node has been configured as a DNS clerk, you may chooseM                    to re-run NET$CONFIGURE Option 2 to rename the node into a                     DNS server.  I                    Using the BASIC and ADVANCED Configuration Options 6-5            :         Using the BASIC and ADVANCED Configuration Options<         6.4 Configuring Node and Session Control Information    F               Once you have configured the node as a DECdns clerk, seeH               Section 7.6.5 for an example of converting the node from a.               DECdns clerk to a DECdns server.  0         6.4.1 Specifying Directory Name Services  I               DECnet-Plus provides access to the node name and addressing F               information stored in one or more name services. DECnet-B               Plus supports the following directory name services:  G               o  Local namespace - A discrete, nondistributed namespace D                  that stores name and address information locally in                   database files.  H               o  DECdns - The HP DECnet-Plus Distributed Name Service, a2                  distributed, global name service.  H               o  Domain Name System - The Domain Name System (DNS/BIND),G                  a global name service for the storage of IP addresses.   C               The sections that follow give a short introduction to E               each of the name services. For more information on name @               services, refer to the DECnet-Plus Planning Guide.  #         6.4.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 H               nodes. The actual number of nodes that the Local namespaceE               can hold depends on the space available on your system.   I               The Local namespace is a discrete, nondistributed namespace F               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.  ?               DECnet-Plus recognizes that when a node full name E               begins with LOCAL:, information for that node is stored B               in a Local namespace. The following are typical nodeD               full names properly formatted for the Local namespace:1               LOCAL:.ma.ashfld and local:.ashfld.   @               Unlike DECdns, the Local namespace does not employB               backtranslation directories for address-to-node-name               translation.  >         6-6 Using the BASIC and ADVANCED Configuration Options           I                        Using the BASIC and ADVANCED Configuration Options I                      6.4 Configuring Node and Session Control Information     D         6.4.1.2 The HP DECnet-Plus Distributed Name Service (DECdns)  D               DECdns is a networkwide service that makes it possibleE               to use network resources without knowing their physical E               location. Users and applications can assign DECnet-Plus E               names to resources such as nodes. The creator of a name C               also supplies other relevant information, such as the I               resource's network address, for DECdns to store. Users then I               need to remember only the name, and DECdns acts as a lookup I               service, providing the rest of the data when necessary. The F               following are typical node full names properly formattedC               for the DECdns namespace: XYZ_CORP:.usa.ma.ashfld and (               CMP:.accounting.recv.paul.  &         6.4.1.3 The Domain Name System  H               The Domain Name System (DNS/BIND) is supported for storageF               of IP addresses. Refer to your BIND server documentationG               for specific installation and configuration instructions. F               For a list of supported vendors, see the DECnet-Plus forF               OpenVMS Software Product Description (SPD). Any properlyI               constructed DNS/BIND node name is supported by DECnet-Plus.   F               DECnet-Plus recognizes that when a node full name beginsD               with DOMAIN:, information for that node is stored in aI               DNS/BIND server. In most cases, the configuration procedure I               also accepts fully-qualified host names for the node's full F               name. The following are typical node full names properlyG               formatted for the DOMAIN namespace: DOMAIN:ashfld.ma.com.                 and ashfld.ma.com.  ,         6.4.1.4 The Name Service Search Path  A               The name service search path applies systemwide and E               allows DECnet-Plus to search a list of name services in G               a predetermined order when looking up names or addressing D               information. The search path includes naming templatesI               that tell DECnet-Plus how to interpret any abbreviated node %               names entered by users.   F               The ordering of the name services is very important. TheC               first name service listed is the primary name service C               to use on the system. The primary name service is the D               first choice used when looking up names and addressingE               information. The remaining name services listed are the 9               secondary name services used on the system.   I                    Using the BASIC and ADVANCED Configuration Options 6-7            :         Using the BASIC and ADVANCED Configuration Options<         6.4 Configuring Node and Session Control Information    G               The search path contains a list of name service keywords, A               each followed by a naming template that specifies a D               defaulting rule so users can enter shorter node names.  E               To create the node's name service search path, begin by I               entering an ordered list of the directory name services you F               want to use on the system. At the prompt, you can chooseH               the following name services for the system: LOCAL, DECDNS,B               and DOMAIN. If you enter more than one name service,5               separate the name services with commas.   Y               * Enter the directory services to use on the system [DECdns,Local,Domain] :   F               For example, entering DECDNS,LOCAL,DOMAIN at the prompt,"               means the following:  E               o  You want to use the name services DECdns, Local, and                   DNS/BIND.  4               o  The primary name service is DECdns.  G               o  The secondary name services are Local and DNS/BIND, in                   that order.  G                 ________________________ Notes ________________________   D                 If you intend to make this node a DECdns server, youA                 must first configure the node with only the Local @                 name service or as a clerk in an existing DECdnsF                 namespace. After completing the initial configuration,?                 reinvoke the net$configure procedure and select D                 Option 2 - Change Naming Information. At this point,D                 net$configure will give you the option of converting,                 the node to a DECdns server.  C                 All members in a cluster should have identical name E                 service search paths configured. This helps to ensure E                 that nodes are recognized in the various services you D                 have identified. For example, if you receive mail onD                 one node in the cluster, the "From" node name may beC                 LOCAL:.NODE::SMITH. If you attempt to reply to this F                 node from a node in the cluster that does not have theE                 Local namespace configured, the system would indicate +                 that there is no such node.   F                 ______________________________________________________  >         6-8 Using the BASIC and ADVANCED Configuration Options           I                        Using the BASIC and ADVANCED Configuration Options I                      6.4 Configuring Node and Session Control Information     (         6.4.2 Specifying Node Full Names  A               After requesting the ordered list of directory name G               services, the configuration procedure prompts you for one H               or more node full names. You can enter a DECdns full name,F               a Local namespace full name, a fully qualified host nameB               for the Domain Name System (DNS/BIND), or all three.  D               Use the following guidelines for selecting a node full               name:   H               o  For DECdns and Local, the node full name has the formatD                  NamespaceNickname:[.DirectoryPath].NodeObject. NoteE                  that the name must begin with the namespace nickname I                  and a colon (:). The nickname for the Local namespace is H                  always LOCAL: (or local:). The namespace nickname LOCALG                  is reserved for the Local namespace and cannot be used G                  for a DECdns namespace. The namespace nickname and the 4                  node object cannot be null strings.  I               o  For DECdns and Local, the directory path must begin with                   a dot (.).   D               o  The full name can be up to 512 characters long, theD                  namespace nickname can be up to 255 characters, andD                  the directory path and node object can be up to 255                  characters.  I               o  The full name can be any combination of letters, digits, H                  and certain punctuation characters from the ISO Latin-1I                  character set. Some other characters are allowed as long G                  as they are enclosed in quotation marks. For a list of F                  all allowable characters, refer to the HP DECnet-Plus6                  for OpenVMS DECdns Management manual.  D               o  For DNS/BIND, enter a fully qualified IP host name.  C               The following are some examples of suitable node full                names:  1                Local namespace -  LOCAL:.TomThumb 4                DECdns          -  ACME:.wabbit.Elmer7                Domain          -  elmer.wabbit.acme.edu   F                 ________________________ Note ________________________  @                 If you plan to use a Local namespace and you are?                 converting a Phase IV system to DECnet-Plus, HP   I                    Using the BASIC and ADVANCED Configuration Options 6-9            :         Using the BASIC and ADVANCED Configuration Options<         6.4 Configuring Node and Session Control Information    B                 recommends that you use the system's Phase IV node?                 name in the DECnet-Plus full name (for example,                  LOCAL:.PASTRY).   F                 ______________________________________________________  E               You should plan node full names carefully and make sure C               they are unique within the namespace. If your network D               administrator has not assigned a unique node full nameG               for your system, be sure to read the DECnet-Plus Planning B               Guide before you assign a node name for your system.  G               The prompts used by the configuration procedure depend on F               the directory name services you entered. For example, ifE               you enter LOCAL,DECDNS,DOMAIN at the directory services D               prompt, the configuration dialog asks for a Local fullG               name, a DECdns full name, and a fully qualified host name                for DNS/BIND.   P               * Enter the full name for directory service LOCAL   : LOCAL:.ELMER  V               * Enter the full name for directory service DECDNS  : ACME:.WABBIT.ELMER  Y               * Enter the fully qualified host name for DNS/BIND  : ELMER.WABBIT.ACME.EDU   )         6.4.3 Specifying the Node Synonym   B               The node synonym is an alphanumeric character stringF               between one and six characters long. The first characterI               must be an alphabetic character; after the first character, A               the string can contain either alphabetic or numeric                characters.   B               The node synonym is primarily a transition tool thatC               allows you to use a Phase IV-style node name for your F               DECnet-Plus node. Other users can then find your node byG               using this synonym rather than your full name. If you are E               transitioning from DECnet Phase IV, consider using your I               Phase IV node name as your synonym. The synonym is required F               for Phase IV applications that can only handle Phase IV-G               style node names. If your network has only DECnet-Plus or E               OSI (Open Systems Interconnection) systems, you may not "               need a node synonym.    ?         6-10 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                      6.4 Configuring Node and Session Control Information     E               The default node synonym is the first six characters of D               the system's last simple name. The last simple name isB               the string that follows the last period of your fullE               name. For example, if you specify XYZ_CORP:.sales.east_ G               coast.BrianMacKrill as a node full name, the default node                 synonym is BrianM.  H               If this system had previously been running DECnet Phase IVI               software, then you should use the old Phase IV node name as I               the synonym. If this system is joining a DECnet network for F               the first time, you can use any name for the synonym, asG               long as it meets the criteria listed above, and is unique !               within the network.   L               * What is the synonym name for this node?            [ELMER] :  >               For information on node synonym directories, see               Section B.2.  7         6.4.4 Specifying the Naming Cache Timeout Value   G               A naming cache is used to improve the performance of node F               name to address resolution. This naming cache supersedes@               the DECdns cache in older DECnet-Plus versions andB               is used when looking for addresses in the Domain andD               Local services, in addition to DECdns. Note that otherH               applications that directly use DECdns will continue to use;               the DECdns cache instead of the naming cache.   C               The naming cache includes a mechanism to time out old ?               entries. In this way, these entries are refreshed E               periodically to reflect the actual network environment.                  BASIC   I               The BASIC option sets the naming cache timeout value to the 5               default value of 30 days (30-00:00:00).                  ADVANCED  E               The ADVANCED option prompts for the naming cache value:   L               * Naming cache timeout value?                  [30-00:00:00] :  C               To choose the default value of 30 days, press Return. B               Otherwise, enter any legal OpenVMS delta time value.  I                   Using the BASIC and ADVANCED Configuration Options 6-11            :         Using the BASIC and ADVANCED Configuration Options<         6.4 Configuring Node and Session Control Information    D         6.4.5 Specifying the Session Control Address Update Interval  @               The session control address update interval is theF               time, in seconds, between updates of local tower address               information.                 BASIC   F               The BASIC option sets the session control address update:               interval to the default value of 10 seconds.                 ADVANCED  I               The ADVANCED option prompts for the session control address                update interval:  F               * Session Control Address Update Interval ?       [10] :  G               To choose the default value of ten seconds, press Return. E               Otherwise, enter an interval value in seconds and press                Return.   =         6.4.6 Specifying the Naming Cache Checkpoint Interval   C               Periodically, DECnet-Plus saves a snapshot of the in- F               memory naming cache to disk. This allows systems, duringG               startup, to have a naming cache that is already populated I               with entries, thereby preserving the contents of the naming *               cache across system reboots.                 BASIC   H               The BASIC option sets the naming cache checkpoint interval.               to the default value of 8 hours.                 ADVANCED  I               The ADVANCED option prompts for the naming cache checkpoint                interval:   L               * Naming cache checkpoint interval?               [08:00:00] :  G               To choose the default value of eight hours, press Return. B               Otherwise, enter any legal OpenVMS delta time value.  ?         6-12 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                        6.5 Configuring Routing Parameters     *         6.5 Configuring Routing Parameters  H               The process for configuring routing parameters consists of"               the following items:  /               o  Node type (end node or router)   #               o  Router information                     -  Router type   '                  -  Maximum path splits   ,                  -  Phase IV maximum address  )                  -  Phase IV maximum area   !               o  Phase IV address                   o  Phase IV prefix  %               o  End node information   %                  -  Network addresses   &                  -  DNA address format                     -  Routing mode  '               o  Default ES Hello Timer                  o  ES Cache Size  &         6.5.1 Specifying the Node Type  E               DECnet-Plus for OpenVMS allows an OpenVMS system to run A               integrated IS-IS, thus providing host-based routing B               functionality. Answer ROUTER if you want this systemE               to support the host-based routing functionality. If you H               answer ROUTER, you must have the extended function licenseF               (see Section 1.6) for the host-based routing software toD               function. Answer ENDNODE if this system will depend on-               other nodes to provide routing.   L               * What type of node (Endnode or Router)?           [ENDNODE] :  G               To configure an end node system, press Return. Otherwise, "               enter the node type.  I                   Using the BASIC and ADVANCED Configuration Options 6-13            :         Using the BASIC and ADVANCED Configuration Options*         6.5 Configuring Routing Parameters    +         6.5.2 Specifying Router Information   F               This section only applies if you chose to configure your!               system as a router.            6.5.2.1 Routing Type  A               A DECnet-Plus router can provide intra-area routing G               capability (known as level 1 routing) or inter-area level <               routing capability (known as level 2 routing).  L               * Type of routing node (L1 or L2)?                      [L1] :  E               To configure a level 1 router, press Return. Otherwise, 6               enter L2 for level 2 routing capability.  F                 ________________________ Note ________________________  B                 Immediately preceding this question, the procedureA                 displays an informational message explaining that E                 net$configure always generates a router that uses the (                 routing vector protocol:  J                 NET$CONFIGURE will assume that the MANUAL L1 ALGORITHM andL                 the MANUAL L2 ALGORITHM (if present) will be ROUTING VECTOR.  J                 If LINK STATE is to be designated as the preferred routing?                 algorithm at either level, the DCL command file I                 SYS$MANAGER:ISIS$CONFIGURE.COM must be invoked AFTER this M                 procedure to correctly configure the NET$ROUTING_STARTUP.NCL.   >                 For information about using the isis$configureB                 procedure to configure a router that uses the link7                 state routing protocol, see Appendix D.   F                 ______________________________________________________  #         6.5.2.2 Maximum Path Splits   D               A routing node may use multiple paths of equal cost toF               route traffic. The answer to this question specifies theH               maximum number of these paths between which the traffic is               split.                 BASIC   F               The BASIC option sets maximum path splits to the default               value of 2.   ?         6-14 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                        6.5 Configuring Routing Parameters                    ADVANCED  E               The ADVANCED option prompts for the maximum path splits                value:  L               * Maximum path splits                                    [2] :  H               To choose the default value of 2, press Return. Otherwise,.               enter a number between 1 and 32.  9         6.5.2.3 Phase IV Maximum Address and Maximum Area   C               The next two questions control which Phase IV packets E               are forwarded by a router. The Phase IV maximum address H               characteristic prohibits Phase IV packet forwarding to anyF               node with a higher address than the specified value. TheE               Phase IV maximum area characteristic prohibits Phase IV E               packet forwarding to any area with a higher area number A               than the specified value. The Phase IV maximum area G               question is asked only for level 2 routers. HP recommends C               that both defaults be taken to prevent any unintended                packet loss.                 BASIC   G               The BASIC option sets the Phase IV maximum address to the G               default value of 1023. If the system is a level 2 router, H               the BASIC option sets Phase IV maximum area to the default               value of 63.                 ADVANCED  B               The ADVANCED option prompts for the Phase IV maximum               address value:  L               * PhaseIV Maximum Address                             [1023] :  @               To choose the default value of 1023, press Return.;               Otherwise, enter a number between 1 and 1023.   I               If the router is a level 2 router, the ADVANCED option also :               prompts for the Phase IV maximum area value:  L               * PhaseIV Maximum Area                                  [63] :  I               To choose the default value of 63, press Return. Otherwise, .               enter a number between 1 and 63.  I                   Using the BASIC and ADVANCED Configuration Options 6-15            :         Using the BASIC and ADVANCED Configuration Options*         6.5 Configuring Routing Parameters    2         6.5.3 Specifying a DECnet Phase IV Address  B               If you want your system to communicate with Phase IVG               nodes, you must specify a Phase IV address and a Phase IV I               prefix. DECnet-Plus systems reference all network addresses B               (including Phase IV addresses) using the OSI NetworkD               Service Access Point (NSAP) address formats. The PhaseF               IV address and a Phase IV prefix are used to construct a$               complete NSAP address.  C               A DECnet Phase IV-compatible address is a DECnet-Plus I               address, in the form area-number.node-number, that conforms E               to the Phase IV area and node limits; that is, the area F               number is from 1 to 63, and the 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 not E               need a Phase IV-compatible address. Entering a Phase IV F               address of 0.0 at configuration time indicates that thisD               DECnet-Plus system does not have a Phase IV-compatibleD               address, and will not communicate with Phase IV nodes.  L               * Enter PhaseIV Address                              [15.27] :  I               Enter the Phase IV address you want to use, or enter 0.0 if A               you do not want to communicate with Phase IV nodes.   *         6.5.4 Specifying a Phase IV Prefix  E               All nodes within a single addressing domain contain the H               same initial domain part (IDP) in their network addresses.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 that0               contains some DECnet-Plus systems.  F                 ________________________ Note ________________________  C                 If you are using a Phase IV prefix other than 49::, >                 it must be assigned by an authorized standardsA                 organization, such as ANSI, or you must construct B                 a Phase IV prefix that you know is globally uniqueB                 (based on your telephone number, for instance). If@                 your organization has allocated its own Phase IVA                 prefix, you can enter that value instead of 49::. B                 The DECnet-Plus Planning Guide contains a detailed  ?         6-16 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                        6.5 Configuring Routing Parameters     A                 description of how to construct an IDP and how to =                 apply to a standards organization for an IDP.   F                 ______________________________________________________                 BASIC   F               The BASIC option sets the Phase IV prefix to its defaultF               value of 49::. If you do not enter a Phase IV-compatibleI               address, the BASIC option does not assign a Phase IV prefix                value.                 ADVANCED  H               If you entered a Phase IV-compatible address, the ADVANCED;               option prompts for the Phase IV prefix value:   M               * Enter Phase IV Prefix                                [49::] :   @               To choose the default value of 49::, press Return.1               Otherwise, enter a valid IDP value.   -         6.5.5 Specifying End Node Information   F               This section applies only if you chose to configure your$               system as an end node.  !         6.5.5.1 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- F               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. E               Rather than assign new addresses to all systems in both I               networks to reflect the new combined network, those systems F               that participate in both networks can have an address in               each network.   @               Network addresses are sometimes referred to in OSIC               terminology as network entity titles (NETs). NETs are F               network service access points (NSAPs) with a selector of               00.   I                   Using the BASIC and ADVANCED Configuration Options 6-17            :         Using the BASIC and ADVANCED Configuration Options*         6.5 Configuring Routing Parameters                   BASIC   E               The BASIC option autoconfigures one network address for                you.                 ADVANCED  F               The ADVANCED option prompts you for the method to create                network addresses:  L               * Autoconfigure network addresses?                     [YES] :  F               There are two ways to configure NETs: by autoconfiguring@               addresses or by manually configuring addresses. ToF               choose to autoconfigure network addresses, press Return.C               Otherwise, enter NO. The two methods are described in 1               detail in the following paragraphs.   /               Autoconfiguring Network Addresses   F               Answer YES to have your system autoconfigure its networkI               address. To use this option, you must be using only Phase V                (OSI) addressing.   E               If you have an OSI router from a supplier other than HP F               adjacent to your system, do not choose autoconfigurationG               unless you know that the router uses NETs with a selector @               of 00. This restriction applies even if you have aC               WANrouter as well as another supplier's OSI router on E               the same LAN. OSI routers that specify NETs differently C               can cause you to autoconfigure your network addresses E               incorrectly. If you have such a router, you must choose D               to manually configure your NETs by answering NO to the)               autoconfiguration question.                       ?         6-18 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                        6.5 Configuring Routing Parameters     &         Manually Configuring Addresses  E               If you answer NO, the procedure prompts you to manually E               enter network entity titles. If you configured a DECnet D               Phase IV-compatible address the procedure precedes theF               prompt with a message informing you that it is including/               that address in the list of NETs:   `               %NET$CONFIGURE-I-PHASEIVNETINCL, the Phase IV N.E.T. will be included: phaseiv-netI               * Enter Manual Network Entity Titles                   [ ]:   H               You can assign a maximum of three network addresses to theH               system, including the Phase IV-compatible network address.E               If you enter multiple addresses, separate the addresses                using commas.   F               To create a NET manually, you need to know your system's;               network IDP, network local area, and node ID.   ;               For example, given the following information:   .                  A network IDP of 41:45436192:+                  A network local area of 43 !                  A node ID of 258   0               The NET is constructed as follows:  E               IDP and selector    = 41:45436192:local-area:node-id:00 B               43 decimal          = 2B    hexadecimal (local area)1               (43 * 1024) + 258   = 44290 decimal 5               44290 decimal       = AD02  hexadecimal ?               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, or @                 hexadecimal format. Make sure you include the 009                 selector when you manually specify a NET.   F                 ______________________________________________________  H               For more information on how to construct DNA and OSI NETs,I               see the chapter on NSAPs in the DECnet-Plus Planning Guide.   I                   Using the BASIC and ADVANCED Configuration Options 6-19            :         Using the BASIC and ADVANCED Configuration Options*         6.5 Configuring Routing Parameters    "         6.5.5.2 DNA Address Format  C               The DIGITAL Network Architecture (DNA) Address Format >               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 or                removing NETs.                 BASIC   B               The BASIC option sets the routing characteristic DNA%               address format to TRUE.                  ADVANCED  H               The ADVANCED option prompts you for the DNA address format               setting:  L               * DNA Address Format                                  [TRUE] :  @               To choose the default value of TRUE, press Return.C               Otherwise, enter FALSE, and enter at least one manual 8               network entity title. See Section 6.5.5.1.  C         6.5.5.3 Segregated Mode Routing and Integrated Mode Routing   E               You have the option of using integrated mode routing or &               segregated mode routing.  F               Integrated mode routing - sends DECnet Phase IV messagesC               across the network using DECnet Phase V Network layer B               protocols. Routers receiving DECnet Phase IV packetsA               translate them to OSI CLNP format before forwarding E               them. Messages destined for DECnet Phase IV systems are I               translated to Phase IV format only on the last hop of their F               journey. Integrated mode routing allows routers to routeF               both DECnet Phase IV and Phase V traffic while storing aB               single network topology in their internal databases.  C               Under integrated mode, DECnet-Plus systems attempt to E               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.   B               o  No DECnet Phase V routers exist on the network to%                  forward the packets.   ?         6-20 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                        6.5 Configuring Routing Parameters     C               Segregated mode routing - handles DECnet Phase IV and H               Phase V as independent protocols. Routers do not translateG               messages between DECnet Phase IV and Phase V formats. The H               routers must maintain separate network topologies in theirA               internal databases to handle each type of protocol.   E               Under segregated mode, DECnet-Plus end systems transmit D               messages in the Phase IV address format if they have aI               DECnet Phase IV translatable destination address. All other D               messages are sent in DECnet Phase V format. If you useF               routers that do not support the technique of translatingG               DECnet Phase V addresses to DECnet Phase IV, you must 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- E               V or Phase-V-to-Phase-IV packet format conversions. Use F               segregated routing mode when the adjacent routers cannotG               perform Phase-IV-to-Phase-V or Phase-V-to-Phase-IV packet                conversions.  F                 ________________________ Note ________________________  D                 If your OpenVMS system is using a cluster alias, you)                 must use integrated mode.   F                 ______________________________________________________                 BASIC   C               The BASIC option selects the integrated routing mode.                  ADVANCED  B               The ADVANCED option prompts you for the routing mode               setting:  L               * Do you want to use segregated mode routing?           [NO] :  E               To choose the default value of integrated routing mode, E               press Return. Otherwise, enter YES to choose segregated                routing mode.     I                   Using the BASIC and ADVANCED Configuration Options 6-21            :         Using the BASIC and ADVANCED Configuration Options*         6.5 Configuring Routing Parameters    3         6.5.6 Specifying the Default ES Hello Timer   G               The default ES Hello timer value determines the interval, H               in seconds, that the end system (ES) uses when sending outF               its Hello messages. This interval multiplied by 3 is theG               amount of time the other end of a routing adjacency waits F               before determining that this system is no longer able to!               accept connections.                  BASIC   D               The BASIC option sets the ES Hello timer value to 600.                 ADVANCED  D               The ADVANCED option prompts you for the ES Hello timer               setting:  N               * Routing Default ES Hello Timer?                        [600] :  D               To select the default of 600, press Return. Otherwise,5               choose your own value and press Return.   *         6.5.7 Specifying the ES Cache Size  G               The routing ES Cache Size attribute specifies the maximum 0               number of entries in the ES cache.                 BASIC   C               The BASIC option sets the ES cache size value to 512.                  ADVANCED  C               The ADVANCED option prompts you for the ES cache size                setting:  M               * Routing ES Cache Size?                                [512] :   D               To select the default of 512, press Return. Otherwise,5               choose your own value and press Return.            6.6 Configuring Devices   G               The net$configure procedure checks for network devices on E               the system that are supported by net$configure and then                configures them.  ?         6-22 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     .         6.6.1 Configuring WANDD Device Support  E               The net$configure procedure begins device configuration H               by checking to see if the Wide Area Network Device DriversE               (WANDD) software has been installed but not configured. H               The WANDD software provides synchronous device support for               DECnet-Plus.  6               If it finds the WANDD configuration fileD               (sys$startup:wandd$configure.com), it displays a shortG               message and asks if you want to add WANDD devices to your                configuration:  N               You have installed wide area device support, but it has not been@               configured.  You may configure it now if you want.  O               * Do you want to configure Wide Area devices?             [YES] :   G               To add WANDD devices to your configuration, press Return. G               To skip over the WANDD device configuration, enter NO and                press Return.   I               If you select WANDD device configuration, the net$configure =               procedure invokes the WANDD configuration file, F               (sys$startup:wandd$configure.com). The next two sectionsH               describe the WANDD configuration dialog on OpenVMS I64 and?               OpenVMS Alpha systems and on OpenVMS VAX systems.   E         6.6.1.1 WANDD Device Configuration on OpenVMS I64 and OpenVMS                  Alpha Systems   H               If you select WANDD device configuration on an OpenVMS I64H               or OpenVMS Alpha system, the WANDD configuration procedureD               displays the following messages and asks the indicated               questions:  2                Configuring WANDD... ['?' for HELP]  O               %WANDD$CONFIGURE-I-WANDDNOTCONFIG, WANDD has not been configured. $               Configure WANDD? [YES]  I                 All installed autoconfigurable synchronous device drivers K                 will be configured.  However, the built-in serial port will L                 only be configured if you answer "YES" to the next question.  B               Configure built-in serial port as synchronous? [YES]8               Are you satisfied with your answers? [YES]  I                   Using the BASIC and ADVANCED Configuration Options 6-23            :         Using the BASIC and ADVANCED Configuration Options         6.6 Configuring Devices     @               By default, when the WANDD configuration procedureB               is called for the first time, the procedure does the               following:  G               1. Loads the appropriate synchronous device drivers which F                  enable connection to a wide area network via a serial                  port.  C               2. If the processor supports the built-in serial port C                  (TTA1), a question is displayed asking if you want E                  to configure the port for wide area network use. The D                  built-in serial port supports both asynchronous andF                  synchronous communications. If you elect to configureH                  the built-in port, it will be available for synchronous7                  wide area network communications only.   F                  The dialog displays the following text if the port is)                  present but unavailable:   H                    The built-in serial port is currently unavailable forL                    synchronous communications.  This is possibly because theP                    console has been configured to use it.  You are still able toP                    reserve this port for synchronous communications but be awareN                    that it will only be made available when the console is not$                    making use of it.  A         6.6.1.2 WANDD Device Configuration on OpenVMS VAX Systems   D               If you select WANDD device configuration on an OpenVMSH               VAX system, the WANDD configuration procedure displays theB               following messages and asks the indicated questions:  C                         This is the Configuration Procedure for the C                         ===========================================   E                        VAX Wan Device Drivers for DECnet-Plus for VMS D                        =============================================  P                 The Wide Area Network Datalinks and Drivers are  a  prerequisiteQ                 for  DECnet-Plus.  They  also  provide  synchronous  datalinks in C                 systems that do not use DECnet-Plus for networking.   Q                 Access to DECnet-Plus datalinks (created by NCL) is  possible via P                 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.   ?         6-24 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     0               Do you wish to use WANDRIVER [N] ?)               Will you use DEC HDLC [Y] ? D               Will you use LAPB/E (VAX P.S.I. requires LAPB/E) [Y] ?  T                 The DSV11 (Q-bus), DIV32 (Q-bus), DSB32 (BI-bus), DSF32 (MI-bus) andT                 DSW devices are soft-loadable. The WANDD startup procedure will load<                 the microcode for these devices if required.  R               Do you have any soft-loadable microcode devices on this system [N] ?@               Will you use the VAXft DSF32 device driver [N] ? Y  P                 The  VAXft  DSF32  software  supports the  pairing  of  physicalP                 controllers to  provide  a fault-tolerant  configuration. Such aP                 pairing  is  called  a  Failover Set. The  DSF32 device does notP                 automatically create the failover sets, so you will need to pairD                 controllers using the Failover Set Manager software.  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.   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.   5         6.6.2 The Configuration Procedure Device Scan   I               After adding the WANDD devices, the net$configure procedure 1               does a complete system device scan:   V               %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait  G               If no devices are found, the procedure displays a message H               and asks if you want to perform an autoconfigure operation7               to create a new set of available devices:   :               %NET$CONFIGURE-W-NODEVICES, no devices foundH               Should devices be autoconfigured?                  [YES] :  I                   Using the BASIC and ADVANCED Configuration Options 6-25            :         Using the BASIC and ADVANCED Configuration Options         6.6 Configuring Devices     F               If you want to have the procedure autoconfigure devices,H               press Return. If you enter NO, the configuration procedureD               continues without autoconfiguring devices. However, ifB               you do not autoconfigure devices, no devices will beF               available. On OpenVMS I64 and OpenVMS Alpha systems, theG               autoconfiguration is done using the command mcr sysman io I               auto. On OpenVMS VAX systems, the autoconfiguration is done =               using the command mcr sysgen autoconfigure all.   E         6.6.3 Configuring Asynchronous Data Link Support (OpenVMS VAX                Only)   F               Normally, the OpenVMS system controls lines connected toI               terminal ports, as in interactive logins. You can, however, F               switch the line so that the DECnet-Plus software can useG               the line for an asynchronous data link to another system. I               Asynchronous data links are implemented in software and can G               be run over any directly connected terminal line that the &               OpenVMS system supports.  G               The asynchronous protocol provides for a full-duplex data I               link and can be used for remote asynchronous communications D               over a telephone line using a modem. Asynchronous dataG               links are not supported for maintenance operations or for *               controller loopback testing.  F                 ________________________ Note ________________________  <                 For more information about asynchronous dataA                 link support on VAX systems, see the "Configuring C                 Asynchronous Data Links" appendix in the HP DECnet- ;                 Plus for OpenVMS Network Management manual.   F                 ______________________________________________________                 BASIC   G               The BASIC option does not offer the choice of configuring =               asynchronous devices. Proceed to Section 6.6.4.                  ADVANCED  D               The ADVANCED option asks whether you want to configure&               asynchronous data links:  I               * Do you want asynchronous datalink support?        [YES] :   H               Answer NO if you do not want to configure any asynchronous3               data links. Proceed to Section 6.6.4.   ?         6-26 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     @               If you answer YES, the procedure verifies that theC               asynchronous device driver (sys$ldr:asydriver.exe) is I               available. If the file is not found, the procedure displays A               a warning that you must install the WANDD software:   P                 ****************************************************************3                                             WARNING   O                 The WANDD software is not installed on the system.  If you want P                 asynchronous datalink support, make sure that the WANDD software;                 is installed and configured on your system. P                 ****************************************************************  E               The procedure allows you to continue. However, you must H               install the WANDD software or the data links you configure               will be unusable.   !         6.6.3.1 Static Data Links   H               A static asynchronous data link creates a permanent DECnetC               link to a single remote node. Two nodes are connected G               either by a dialup line or by a physical line attached to G               a terminal port at each end. Before the DECnet connection F               is made, the terminal line must be converted to a static<               asynchronous DDCMP line (see Section 6.6.3.3).  I               The procedure begins by asking if you want to configure any                 static data links:  M               * Do you want to configure static lines?                 [YES]:   B               Answer NO if you do not want to configure any staticB               asynchronous data links. Proceed to Section 6.6.3.2.  F               If you answer YES, the procedure asks you for the deviceG               names of the terminal lines that you want to configure as -               static asynchronous data links:   M               * Terminal device name (ex: TXA0,TXA2,...)?                 []:   E               Enter the OpenVMS device names of one or more available G               terminal lines. If you want to configure multiple devices E               enter two or more device names separated by commas. The G               configuration procedure displays the following dialog for $               each device you enter.  D               1. First, the procedure checks for the presence of theI                  device. If the procedure is unable to find the indicated   I                   Using the BASIC and ADVANCED Configuration Options 6-27            :         Using the BASIC and ADVANCED Configuration Options         6.6 Configuring Devices     H                  terminal device, it displays a warning message and asks)                  if you want to continue:   O                  %NET$CONFIGURE-W-NOSUCHDEV, no such device found - device-name O                  Do you want to continue configuring this line?          [YES]:   I                  Answer NO to quit the configuration of this line. Answer -                  YES if you want to continue.   F               2. If you answer YES, the procedure continues the deviceI                  configuration by asking you for the device's line speed:   O                  Line speed for TTA0?                                   [2400]:   E               3. Next, the procedure asks you about the modem control -                  requirements for the device:   O                  Will this line require full modem control?              [YES]:   G               When all devices in the device list have been configured, F               the procedure begins the dynamic data link configuration               section.  "         6.6.3.2 Dynamic Data Links  C               A dynamic asynchronous data link provides a temporary B               DECnet link. A dynamic asynchronous line is normallyD               switched on for network use only for the duration of aE               dialup connection between two nodes. When the telephone G               is hung up, the line reverts to being a terminal line. An G               advantage of dynamic data links is that you can establish G               connections to different remote nodes at different times.   E               When using a dynamic data link, you can use an explicit F               line or you can use a floating line. An explicit line isD               tied to a specific OpenVMS terminal device. A floatingF               line is not tied directly to a specific terminal device.E               Before the DECnet connection is made, the terminal line I               must be converted to a dynamic asynchronous DDCMP line (see                Section 6.6.3.3).   I               The procedure begins by asking if you want to configure any !               dynamic data links:   L               Do you want to configure dynamic lines?                 [YES]:  C               Answer NO if you do not want to configure any dynamic @               asynchronous data links. Answer YES if you want toG               configure either explicit or floating dynamic data links.   ?         6-28 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     )               Explicit Dynamic Data Links   H               The procedure then asks if you want to create any explicit               dynamic lines:  L               * Do you want to configure explicit dynamic lines?      [YES]:  D               Answer NO if you do not want to configure any explicitE               dynamic asynchronous data links. Proceed to the section 5               entitled "Floating Dynamic Data Links."   F               If you answer YES, the procedure uses the same questionsI               discussed in Section 6.6.3.1 to obtain the list of terminal E               device names, and then the line speed and modem control I               requirements of each device. When all devices in the device F               list have been configured, the procedure proceeds to the?               floating dynamic data link configuration section.   )               Floating Dynamic Data Links   H               The procedure next asks if you want to create any floating               dynamic lines:  L               * Do you want to configure floating dynamic lines?      [YES]:  D               Answer NO if you do not want to configure any floating@               dynamic asynchronous data links. If you answer NO,B               the procedure asks if you want to configure any more3               asynchronous data links at this time:   L               * Do you want to configure any more asynch lines?        [NO]:  C               Answer YES to return to the static asynchronous lines E               dialog (see Section 6.6.3.1). If you answer NO, proceed                to Section 6.6.4.   G               If you answer YES to the floating dynamic lines question, H               the procedure begins their configuration. Floating dynamicD               lines are configured in groups based on line speed andB               modem control requirements. First, the configurationA               procedure asks you the line speed and modem control G               requirements for the data link group using the line speed ?               and modem questions discussed in Section 6.6.3.1:   :               * Line speed for device-name?        [2400]:F               * Will this line require full modem control       [YES]:  I                   Using the BASIC and ADVANCED Configuration Options 6-29            :         Using the BASIC and ADVANCED Configuration Options         6.6 Configuring Devices     E               Next, the procedure asks you for the number of floating <               lines to configure with these characteristics:  L               * Number of floating speed bps control modem ctrl lines?  [1]:  A               Enter the number of floating data lines you want to B               configure with the indicated device characteristics.  F               The procedure then asks if you want to configure anotherD               set of floating dynamic lines with different speed and$               modem characteristics:  J               * Do you want to configure any more floating lines?   [YES]:  E               If you answer YES, the procedure asks another series of E               speed, modem control, and number questions for the next C               group of floating dynamic lines. Answer NO if you are :               finished configuring floating dynamic lines.  A               If you answer NO, the procedure asks if you want to F               configure any more asynchronous data links at this time:  L               * Do you want to configure any more asynch lines?        [NO]:  C               Answer YES to return to the static asynchronous lines E               dialog (see Section 6.6.3.1). If you answer NO, proceed                to Section 6.6.4.   ;         6.6.3.3 Preparing the Terminal Lines for DECnet Use   D               The configuration procedure configures all the networkF               entities to support asynchronous data links. However, itH               does not enable or disable the individual terminal devices               themselves.   I               To switch a terminal line to a DECnet line or a DECnet line G               back to a terminal line, use DCL set commands such as the                following:  I               o  To switch a terminal line to a static asynchronous line:   :                  $ set terminal/protocol=ddcmp device-name  @               o  To switch a terminal line to a floating dynamic#                  asynchronous line:   H                  $ set terminal/protocol=ddcmp/switch=decnet device-name  ?         6-30 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     A               o  To switch a terminal line to an explicit dynamic #                  asynchronous line:   O                  $ set terminal/protocol=ddcmp/switch=decnet/manual device-name   H               o  To switch a DECnet line back to OpenVMS terminal driver                  use:   <                  $ set terminal/protocol=noddcmp device-name  9         6.6.4 Configuring Data Links and Routing Circuits   I               You now need to supply names for the data links and routing /               circuits you have on your system.   E               For HDLC and synchronous links, you also need to select H               which protocol should be used on the link (HDLC, DDCMP, or               NONE).  E               o  DDCMP (Digital Data Communications Message Protocol) @                  provides synchronous point-to-point connectionsB                  and asynchronous static or dynamic point-to-point                  connections.   E               o  HDLC (High-Level Data Link protocol) conforms to ISO D                  standards. HDLC provides synchronous point-to-point                  connections.   C               o  NONE indicates that you do not want DECnet-Plus to F                  configure this line directly. You may still configureG                  this line for X.25 and then configure DECnet over X.25 F                  for the line (see Section 6.6.5 for information about4                  using DECnet over X.25 data links).                 BASIC   E               The BASIC option automatically configures all available I               network devices. It uses the default naming conventions for F               all data links and routing circuits. It also uses built-F               in defaults for the protocol on all HDLC and synchronous               links.                 ADVANCED  F               The ADVANCED option prompts you for the simple name thatI               you want to use for each data link and routing circuit. For I               HDLC and synchronous lines, the procedure precedes the link F               and routing circuit name questions with a question aboutH               which protocol should be used on the link (HDLC, DDCMP, or               NONE):  I                   Using the BASIC and ADVANCED Configuration Options 6-31            :         Using the BASIC and ADVANCED Configuration Options         6.6 Configuring Devices     L               * Data Link protocol for ZR-0-0 (SSCC)                [HDLC] :L               * Data Link name to use for ZR-0-0 (SSCC)?          [HDLC-0] :L               * Routing Circuit Name for Data Link 'HDLC-0'?      [HDLC-0] :  H               The "Data Link name" question can take on several slightlyG               different forms depending on the device being configured.   )         6.6.4.1 FDDI Large Packet Support   E               For each FDDI-type circuit on your system, you have the D               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 to G               fully utilize the bandwidth of FDDI. (A Phase V router on I               the LAN, preferably on the FDDI, is required before you can +               enable large packet support.)   F               If you choose not to enable FDDI large packet support onI               the circuit, the FDDI circuit uses the bandwidth of Carrier G               Sense, Multiple Access with Collision Detection (CSMA-CD)                instead.                 BASIC   G               The BASIC option automatically selects the CSMA-CD packet 9               size instead of the FDDI large packet size.                  ADVANCED  D               For each FDDI-type circuit on the system, the ADVANCED?               option displays the following message and prompt:   O               You have the option of enabling FDDI large packet support on this P               routing circuit. Note that a Phase V router on the LAN (preferablyQ               on the FDDI) is required in order to use FDDI large packet support.   P               * Use large packets on Routing Circuit FDDI-0?             [YES] :  D               If you want to enable FDDI large packet support, press+               Return. Otherwise, answer NO.   1         6.6.4.2 Circuit Cost and Routing Priority   H               The following applies only if your DECnet-Plus system is a               routing node.   B               For each data link and routing circuit pair entered,F               specify the circuit cost and router priority at level 1.G               If your node is a level 2 router, the procedure also asks ;               you for the level 2 cost and router priority.   ?         6-32 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     I               Cost indicates the cost of traffic on a particular circuit. G               Priority refers to the priority for becoming a designated 4               router on a LAN at level 1 or level 2.                 BASIC   F               The BASIC option assigns the level 1 and level 2 routing&               cost based on link type:  ?               o  Asynchronous data links are assigned a cost of )                  (38400/line-speed) + 48.   G               o  Synchronous and HDLC data links are assigned a cost of                   20.  ?               o  All other data links are assigned a cost of 8.   G               The level 1 and level 2 routing priorities are always set                to 64.                 ADVANCED  F               The ADVANCED option prompts you for the routing cost and#               priority information:   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] :  H               Press Return to take the defaults or enter you own values.  @         6.6.4.3 Enabling Phase IV Addressing on Routing Circuits  G               If you previously specified a Phase IV-compatible address D               for your node in order to communicate with other PhaseG               IV nodes (as in Section 6.5.3), you must specify for each G               circuit whether you want to enable Phase IV addressing on E               that circuit. If the node has multiple connections to a E               LAN, enable Phase IV addressing on only one circuit for                that LAN.                  BASIC   G               The BASIC option enables Phase IV addressing on the first B               broadcast circuit that the procedure encounters. TheH               device list is structured so that if both FDDI and CSMA-CDG               circuits are available, Phase IV addressing is allowed on G               the first FDDI circuit in preference to the first CSMA-CD                circuit.  I                   Using the BASIC and ADVANCED Configuration Options 6-33            :         Using the BASIC and ADVANCED Configuration Options         6.6 Configuring Devices     A               If you have multiple broadcast circuits and you are C               performing a Phase IV migration (that is, you elected E               to convert the Phase IV database (see Section 6.3), the I               procedure displays the following information about enabling ,               additional broadcast circuits:  U               NET$CONFIGURE has determined that you have multiple broadcast circuits. S               Your system has been configured to enable Phase IV addressing on only N               one of those circuits.  When Phase IV addressing is enabled, theP               datalink MAC address is set according to Phase IV addressing rules'               (i.e. AA-00-04-00-nn-nn).   M               It is undesirable (and invalid) for more than one circuit using O               Phase IV addressing to be connected to the same LAN.  However, if O               your circuits are on distinct and separate LANs, and the Phase IV M               style MAC address is desired on more circuits, you may edit the O               SYS$MANAGER:NET$ROUTING_STARTUP.NCL script prior to starting your L               network.  For example, you would change the following command:  M               SET NODE 0 ROUTING CIRCUIT SVA-1 ENABLE PHASEIV ADDRESS = FALSE   L               to this in order to enable Phase IV addressing on the circuit:  L               SET NODE 0 ROUTING CIRCUIT SVA-1 ENABLE PHASEIV ADDRESS = TRUE                 ADVANCED  H               The ADVANCED option prompts you whether you want to enable/               Phase IV addressing on a circuit:   Q               * Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] :   E               Entering YES allows Phase IV messages to be transmitted F               on that circuit. Answering NO indicates that no Phase IV;               messages will be transmitted on that circuit.   *         6.6.5 Configuring DECnet over X.25  B               If you have configured X.25 for OpenVMS on an I64 orE               OpenVMS Alpha system or the X.25 functionality provided H               by DECnet-Plus on an OpenVMS VAX system (formerly known asH               VAX P.S.I.), the configuration procedure now gives you theE               option of configuring DECnet-Plus to use any previously )               configured X.25 data links.   H               1. The procedure begins by displaying a message indicating7                  that X.25 software has been installed.   ?         6-34 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     @                  For an OpenVMS I64 or OpenVMS Alpha system, the>                  procedure displays the following information:  W                  X.25 for OpenVMS software has been installed on this system.  You have C                  the option of configuring DECnet to run over X.25.   F                  For an OpenVMS VAX system, the procedure displays the'                  following information:   O                  The VAX P.S.I. software has been installed on this system. You U                  have the option of configuring DECnet over P.S.I. (i.e., configuring 8                  DECnet over X.25 or data link mapping).  B               2. Next, the procedure asks if you want to configure)                  DECnet-Plus to use X.25:   O                  * Do you want to configure DECnet over X.25?            [NO] :   I                  Answer YES if you want to configure DECnet over X.25. If 7                  you answer NO, proceed to Section 6.7.   >               3. Routing supports four types of X.25 circuits:  H                  o  A dynamically assigned routing circuit operates overF                     a number of X.25 switched virtual circuits (SVCs),/                     both incoming and outgoing.   E                  o  A static incoming routing circuit operates over a H                     single incoming X.25 switched virtual circuit (SVC).  E                  o  A static outgoing routing circuit operates over a H                     single outgoing X.25 switched virtual circuit (SVC).  H                  o  A permanent routing circuit uses a permanent virtual4                     circuit (PVC) instead of an SVC.  B                  The procedure asks you which type of X.25 routing/                  circuit you want to configure:   -                       Types of X.25 circuits:   6                       [1] - X.25 Dynamic Assigned (DA)5                       [2] - X.25 Static Incoming (IN) 6                       [3] - X.25 Static Outgoing (OUT)0                       [4] - X.25 Permanent (PVC)  Q                  * Which type of X.25 circuit do you want to use?             : 4   C                  Enter the number for the type of circuit you want.   I                   Using the BASIC and ADVANCED Configuration Options 6-35            :         Using the BASIC and ADVANCED Configuration Options         6.6 Configuring Devices     E               4. The procedure asks for a name to use for the routing                   circuit:   O                  * Routing Circuit Name to use?                   [X25-PVC-0] :   H                  Specify the simple name you want to use for the routingH                  circuit. The default circuit names are derived from theE                  circuit type (X25-DA-x, X25-IN-x, X25-OUT-x, or X25- I                  PVC-x). You can use the default or you can supply a name /                  (for example, X25-STATICIN-0).   I               5. All X.25 routing circuits use an X.25 access template to 5                  make or accept a network connection.   H                  o  For a static outgoing (OUT) circuit, the X.25 accessD                     template must specify DTE class, destination DTEH                     address, and call data. The X.25 access template canG                     also specify other call characteristics to make the 0                     outbound network connection.  H                  o  For a static incoming (IN) routing circuit, the X.25G                     access template can specify call characteristics to :                     accept the inbound network connection.  H                  o  For a dynamically assigned (DA) routing circuit, theH                     X.25 access template must specify DTE class and callI                     data. The X.25 access template can also specify other G                     call characteristics to make the outbound or accept 4                     the inbound network connections.  B                  Use the appropriate X.25 configuration program to1                  configure X.25 access templates.   F                  The procedure asks for a template name to use for the                  circuit:   O                  * Template name?                                 [X25-PVC-0] :   F                  Specify the simple name of an X.25 access template. AH                  default name is provided or you may enter your own name)                  (for example, X25-DA-1).   G               6. Static incoming and dynamically assigned X.25 circuits E                  use an X.25 access filter to receive inbound network                   connections.   I                  o  For a static incoming circuit, the X.25 access filter H                     must specify inbound DTE class, sending DTE address,8                     call data value, and call data mask.  ?         6-36 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     G                  o  For a dynamically assigned circuit, the X.25 access D                     filter must specify inbound DTE class, call data.                     value, and call data mask.  B                  Use the appropriate X.25 configuration program to/                  configure X.25 access filters.   G                  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] :   F                  Specify the simple name of an X.25 access filter. YouF                  may accept the default or you may enter your own name)                  (for example, X25-IN-0).   H               7. If you chose to configure an X.25 dynamic assigned (DA)I                  circuit, the procedure asks if you want to configure any 5                  routing circuit reachable addresses:   O                  * Do you want to configure any reachable addresses?     [NO] :   D                  If you answer NO, the procedure omits the remaining=                  questions discussed here. Proceed to Step 8.   G                  If you want to configure any routing circuit reachable E                  address entities, answer YES. The procedure displays B                  a series of prompts to request a set of reachable                  addresses.   I                  a. The procedure prompts for the name you want to assign 7                     to this set of reachable addresses:   R                     * Reachable address name?                                    :  D                     Specify the simple name of the reachable addressC                     subentity that you want to create (for example, #                     ACCOUNTS_DEPT).   C                  b. The reachable address subentity name is used to D                     select the remote DTE address to where a routingD                     packet is sent. The selection is done by findingE                     a reachable address subentity that has an address G                     prefix matching the beginning of the remote NSAP in '                     the routing packet.   I                   Using the BASIC and ADVANCED Configuration Options 6-37            :         Using the BASIC and ADVANCED Configuration Options         6.6 Configuring Devices     G                     The procedure asks for the reachable address prefix 8                     for this set of reachable addresses:  Q                     * Reachable address prefix?                                 :   I                     Specify the address prefix for this reachable address H                     entity. The address prefix is a string of charactersH                     that is the valid beginning of an NSAP (for example,H                     41:45436192:). The address prefix matches all NSAPs.  C                  c. You can configure a reachable address subentity H                     with one or more DTE addresses. If more than one DTEI                     address is configured, then only one is selected each G                     time a packet is sent. All the remote DTE addresses E                     must be accessible by the DTE class configured in F                     the X25 Access template already configured for the8                     associated dynamic assigned circuit.  E                     The procedure asks for the reachable address data A                     terminal equipment (DTE) list for this set of (                     reachable addresses:  R                     * Reachable address dte list?                                :  E                     Specify the list of remote DTE addresses for this D                     reachable address entity. A DTE address consistsG                     of 1 to 15 decimal characters. The DTE addresses in H                     the list should be separated by commas (for example,                     2,3,4).   D                  d. The procedure then asks if you want to configure3                     additional reachable addresses:   R                     * Any more reachable addresses you wish to configure?   [NO] :  F                     If you want to configure another reachable addressI                     subentity for this circuit, answer YES. The procedure D                     returns you to the reachable address name prompt                     (Step 7a).  H               8. When you have entered the circuit, template, and filterG                  names and you have specified the appropriate reachable G                  address information, the procedure asks if you want to ;                  configure any other X.25 routing circuits.   P                  * Configure another X.25 routing circuit for DECnet?     [NO] :  ?         6-38 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                   6.6 Configuring Devices     A                  Press Return if you do not want to configure any ?                  other X.25 routing circuits. Answer YES if you D                  want to configure another X.25 routing circuit. TheD                  procedure returns you to Step 4. After you completeD                  the configuration of all X.25 routing circuits, theE                  configuration procedure continues with the transport                   section.   "         6.7 Configuring Transports  F               Next, the configuration procedure configures the NSP and               OSI transports.                  BASIC   D               The BASIC option configures the NSP and OSI transportsE               using default values. See Section 6.7.1 for the default E               values for the NSP transport. See Section 6.7.2 for the 3               default values for the OSI transport.                  ADVANCED  G               The ADVANCED option begins the transport configuration by /               displaying the following message:   Q                    You have the option of configuring the NSP and OSI Transports. T                    Configure the NSP Transport if you want the system to communicateW                    with DECnet Phase IV nodes.  Configure the OSI Transport if you want W                    the system to communicate with DECnet-Plus nodes; if you want to run T                    DECnet or OSI applications over TCP/IP; or if you plan to installG                    OSI Applications such as OSAK, FTAM, or VT software.   G                 _______________________ Warning _______________________   B                 If you do not configure one of the two transports,F                 the procedure issues a warning and asks you to confirm                 your decision:  E                 %NET$CONFIGURE-W-NOTRANSPORTS, no transports selected P                 * Are you sure?                                         [NO] : y  =                 If you answer YES, no transport configuration E                 information is generated. The configuration procedure ?                 creates empty NCL startup script files for both A                 transports. To create a usable configuration, you E                 will have to run the configuration procedure again to /                 create valid transport scripts.   F                 ______________________________________________________  I                   Using the BASIC and ADVANCED Configuration Options 6-39            :         Using the BASIC and ADVANCED Configuration Options"         6.7 Configuring Transports        E         6.7.1 Specifying the Network Service Protocol (NSP) Transport                Configuration                  BASIC   E               The BASIC option configures the NSP transport using the B               default values discussed in this section. Proceed to               Section 6.7.2.                 ADVANCED  H               The ADVANCED option begins the NSP transport configuration&               with following question:  L               * Configure the NSP Transport?                         [YES] :  C               Answer YES if you want the system to communicate with I               DECnet Phase IV nodes If you answer NO, the procedure still F               loads the NSP transport image. However, NSP transport isF               not configured or usable until you run the net$configureA               procedure and answer YES to the preceding question.   F                 ________________________ Note ________________________  C                 If you answer NO to this question and you specified ?                 a valid Phase IV address for the node (that is, @                 not 0.0), the procedure overrides your decision.D                 Instead, it uses the default values to configure theC                 NSP transport. The procedure displays the following 0                 message to indicate this action:  P                 %NET$CONFIGURE-I-NSPCONFIG, NSP will be configured since a Phase*                   IV address is being used  F                 ______________________________________________________  G               The procedure then displays a series of prompts for three G               interrelated settings of the NSP transport configuration:   M               *   Maximum number of logical links?                    [200] : M               *   Maximum transmit and receive window?                 [20] : M               *   Maximum receive buffers?                           [4000] :   H               The first question determines the maximum number of activeF               transport connections (logical links) allowed at any oneC               time to the NSP transport. Press Return to select the >               default value or enter a number from 1 to 65535.  ?         6-40 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                6.7 Configuring Transports     I               The second question determines the value of the transport's E               maximum window attribute. HP recommends setting a value G               of 20 for the maximum transmit and receive window option. H               Press Return to select the default value or enter a number               from 1 to 65535.  B               The third question prompts for the number of receiveG               buffers to preallocate. In a typical network environment, G               HP recommends setting a value for maximum receive buffers H               that is no more than the value you entered for the maximumI               window option multiplied by the value you specified for the .               maximum number of logical links.  G                 ________________________ Notes ________________________   E                 Selecting values for the maximum transmit and receive E                 window option or maximum receive buffers option other D                 than those recommended by HP can significantly alterB                 the behavior of your system and network and shouldF                 only be done after a thorough analysis of your network5                 traffic and application requirements.   B                 Selecting a high value for maximum receive buffersC                 may require considerable buffering capacity on your C                 node; therefore, non-paged pool should be allocated C                 accordingly. If your node does not have enough non- ?                 paged pool, you may want to set maximum receive F                 buffers to a smaller value than the recommended value.  F                 ______________________________________________________  D               For additional information about these parameters, seeG               the subsection about configuring the NSP transport in the I               "Managing Transport Services" section in the HP DECnet-Plus 4               for OpenVMS Network Management manual.  #         6.7.1.1 Flow Control Policy   F               The NSP transport configuration finishes with a questionB               about NSP's flow control policy. Flow control is theI               mechanism that determines when to send normal and expedited F               data messages. During connection establishment, each endF               of the connection uses this setting to determine when toI               expect data when acting as the receiver. It is not required F               that both ends of a connection use the same flow control               policy.   I                   Using the BASIC and ADVANCED Configuration Options 6-41            :         Using the BASIC and ADVANCED Configuration Options"         6.7 Configuring Transports                   BASIC   H               The BASIC option configures NSP with segment flow control.'               Proceed to Section 6.7.2.                  ADVANCED  F               The ADVANCED option prompts for the flow control policy:  K               *   NSP flow control policy (SEGMENT, NO)?        [SEGMENT] :   G               Enter SEGMENT to choose segment flow control. Enter NO to #               disable flow control.   8         6.7.2 Specifying the OSI Transport Configuration                 BASIC   E               The BASIC option configures the OSI transport using the A               default values discussed in this section (including C               enabling OSI applications over TCP/IP and DECnet over 0               TCP/IP). Proceed to Section 6.7.3.                 ADVANCED  H               The ADVANCED option begins the OSI transport configuration&               with following question:  M               * Configure the OSI Transport or run over TCP/IP?       [YES] :   C               Answer YES if you want the system to communicate with B               DECnet-Plus nodes, OSI nodes of other vendors, or ifA               you plan to install the OSAK, FTAM, or VT software. C               Also answer YES if you want to use DECnet over TCP/IP D               or OSI applications over TCP/IP. If you answer NO, theF               procedure still loads the OSI transport images. However,E               OSI transport is not configured or usable until you run I               the net$configure procedure and answer YES to the preceding2               question.   G               The procedure then displays a series of prompts for three G               interrelated settings of the OSI transport configuration:   M               *   Maximum number of logical links?                    [200] :cM               *   Maximum transmit and receive window?                 [20] : M               *   Maximum receive buffers?                           [4000] :.  H               The first question determines the maximum number of activeF               transport connections (logical links) allowed at any oneC               time to the OSI transport. Press Return to select then>               default value or enter a number from 1 to 65535.  ?         6-42 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options.I                                                6.7 Configuring Transports     I               The second question determines the value of the transport's E               maximum window attribute. HP recommends setting a value G               of 20 for the maximum transmit and receive window option. H               Press Return to select the default value or enter a number               from 1 to 65535.  B               The third question prompts for the number of receiveG               buffers to preallocate. In a typical network environment,dG               HP recommends setting a value for maximum receive buffersfH               that is no more than the value you entered for the maximumI               window option multiplied by the value you specified for the .               maximum number of logical links.  G                 ________________________ Notes ________________________   E                 Selecting values for the maximum transmit and receiveoE                 window option or maximum receive buffers option other D                 than those recommended by HP can significantly alterB                 the behavior of your system and network and shouldF                 only be done after a thorough analysis of your network5                 traffic and application requirements.   B                 Selecting a high value for maximum receive buffersC                 may require considerable buffering capacity on your C                 node; therefore, non-paged pool should be allocatedfC                 accordingly. If your node does not have enough non-t?                 paged pool, you may want to set maximum receivetF                 buffers to a smaller value than the recommended value.  F                 ______________________________________________________  D               For additional information about these parameters, seeG               the subsection about configuring the OSI transport in the.I               "Managing Transport Services" section in the HP DECnet-Plus 4               for OpenVMS Network Management manual.  E         6.7.2.1 Enabling OSI Applications over TCP/IP and DECnet over.                 TCP/IP  H               If you configure the OSI transport, you have the option ofF               allowing OSI applications and DECnet to use the servicesF               provided by HP TCP/IP Services for OpenVMS (or any otherA               vendor's TCP/IP product that supports the PATHWORKStF               Internet Protocol (PWIP) interface) to run OSI or DECnet1               applications over a TCP/IP network.   I                   Using the BASIC and ADVANCED Configuration Options 6-436 L  n      :         Using the BASIC and ADVANCED Configuration Options"         6.7 Configuring Transports    E               Enabling OSI applications over TCP/IP includes port 102.E               in the set of OSI transport RFC 1006 listener ports and.I               builds the appropriate RFC 1006 template. However, to fully.G               support OSI applications over TCP/IP you must also ensure.               the following:  F               o  HP TCP/IP Services for OpenVMS (or any other vendor'sD                  TCP/IP product that supports the PWIP interface) isD                  configured and running on both the local and remote                  system.  F               o  The remote node also has OSI applications over TCP/IP@                  enabled (that is, it is listening on port 102).  F               Enabling DECnet over TCP/IP includes port 399 in the setE               of OSI transport RFC 1006 listener ports and builds the H               appropriate RFC 1859 template (considered an RFC 1006-typeI               template). However, to fully support DECnet over TCP/IP you -               must also ensure the following:.  F               o  HP TCP/IP Services for OpenVMS (or any other vendor'sD                  TCP/IP product that supports the PWIP interface) isD                  configured and running on both the local and remote                  system.  D               o  The remote node also has DECnet over TCP/IP enabled8                  (that is, it is listening on port 399).                 BASIC.  G               The BASIC option enables OSI applications over TCP/IP andQ!               DECnet over TCP/IP.                  ADVANCED  F               The ADVANCED option begins by asking whether you want to2               enable OSI applications over TCP/IP:  N               *   Run OSI Applications over TCP/IP?                    [YES] :  @               Answer YES to this question if you want to run OSI'               applications over TCP/IP.a  H               Next, the procedure asks if you want to enable DECnet over               TCP/IP:.  M               *   Run DECnet over TCP/IP?                             [YES] :.  ?         6-44 Using the BASIC and ADVANCED Configuration Optionss e  f      I                        Using the BASIC and ADVANCED Configuration OptionstI                                                6.7 Configuring Transportsm    G               Answering YES to this question enables DECnet-Plus to runsG               over a TCP/IP network to any system that has enabled thish               same feature.o  C               *   Interface(s) for DECnet/OSI over TCP/IP ? [ALL] :.  C               Answering ALL to this question enables DECnet-Plus tomC               listen on ALL IP-configured interfaces. If you do notrD               wish to listen on all interfaces, then you can specifyH               the static IP address of the interface(s) on which DECnet-H               Plus should listen for inbound DECnet/OSI connections over               TCP/IP.                   BASIC and ADVANCED  C               If OSI applications over TCP/IP or DECnet over TCP/IP D               are configured, the net$configure procedure checks forF               the availability of the DOMAIN name service and the PWIP               driver.e  H               If the DOMAIN name service is not available, the procedure-               displays the following message:   W               NET$CONFIGURE-W-NODOMAIN, DECnet over IP requires DOMAIN in the directory                  services listn  I               If the PWIP driver is not available, the procedure displays-$               the following message:  [               NET$CONFIGURE-W-NOPWIP, DECnet over IP requires the PWIP driver to be enabled.  D               Both of these messages are warnings; the configurationI               continues. As long as the functionality is not required the.G               configuration need not be changed. If you need the DOMAIN.I               name service, run net$configure again and include DOMAIN in.F               the directory service list and enter a DOMAIN node name.  7         6.7.3 Specifying Transport Congestion AvoidanceN  F               One feature of both transports is the ability to use theE               Congestion Experienced field in the Connectionless-mode.G               Network Service (CLNS) routing header, and to implement anH               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 early.H               indication of congestion. When the transport receives dataE               that passed through a network path where the Congestion.H               Experienced bit is set, the transport reduces the transmit  I                   Using the BASIC and ADVANCED Configuration Options 6-45. .  .      :         Using the BASIC and ADVANCED Configuration Options"         6.7 Configuring Transports    F               rate of the sending end system to help alleviate network               congestion..  E               This feature works well in networks where all protocolsAB               support Congestion Avoidance mechanisms. However, itB               has been noted that in some heavily congested multi-G               protocol networks, this feature can negatively impact thed@               performance of DECnet compared to other protocols.  B               HP recognizes that most of its customers have multi-E               protocol networks. In this environment, not all network H               protocols have Congestion Avoidance mechanisms. Therefore,B               the default for this option is to disable Congestion               Avoidance.  A               If you operate in an environment where you can takeiI               advantage of Congestion Avoidance mechanisms, HP recommends *               that you enable the feature.                 BASIC   H               The BASIC option configures each transport with congestion!               avoidance disabled.C                 ADVANCED  H               The ADVANCED option asks the following question about your"               network environment:  M               * Is this system operating in a multi-protocol network? [YES] :.  >               If you take the default answer of YES, then bothF               transport's Congestion Avoidance characteristics are setE               to FALSE and this option is disabled. Answer NO to this)H               question to set the characteristics to TRUE and enable the               option..  >         6.7.4 Configuring Slow-Speed NSP Transport Connections  B               NSP connections over slow-speed point-to-point linesC               require adjustments to NSP's delay factor and maximum.A               window settings. The configuration utility asks theLF               following question if you have configured point-to-pointE               devices that have the potential to operate at very slowr               line speeds:  ]               * Are the point-to-point lines utilizing line speeds less than 9600 BPS? [NO] :   F               Answer YES if you have slow-speed point-to-point device.C               Otherwise, press Return to accept the default answer.   ?         6-46 Using the BASIC and ADVANCED Configuration Options.    f      I                        Using the BASIC and ADVANCED Configuration OptionsfI                                                6.7 Configuring Transports     B         6.7.5 Specifying the OSI Loopback Test Application Account  @               If the OSI transport is configured, a test programH               (sys$test:osit$ivp) is installed. You can use this programE               to verify OSI transport operation. For more informationiB               about the OSI test program, see the subsection aboutB               testing the OSI transport in the "Managing TransportI               Services" section in the HP DECnet-Plus for OpenVMS Network.                Management manual.                 BASICl  I               The BASIC option selects the user name SYSTEST for the test.               account.                 ADVANCED  D               The ADVANCED option asks for the user name to use when+               running the OSI test program:   N               * Username for OSI loopback test application to use? [SYSTEST] :  B               Press Return to accept the default user name for theE               application loopback test account or enter a user name.   '         6.7.6 Configuring OSI Templates6  @               If you configured the OSI transport, net$configureF               automatically creates the default OSI templates requiredG               by the OSAK and FTAM installation verification procedures I               (IVPs). The procedure displays a message stating that these 6               default OSI templates have been created:  O               %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates   ?               The default templates created are osit$loop_clns,gF               osit$loop_cons, osit$rfc1006, and, if DECnet over TCP/IPC               was chosen, osit$rfc1006plus. In addition, a template E               with the name DEFAULT is created when the OSI transport.G               entity is enabled. This template is used when no template                is specified.e                 BASIC   I               The BASIC option does not provide the opportunity to create6G               additional OSI templates. You will not be able to use OSI C               applications to make connections to other OSI systems.E               unless you use the ADVANCED option to create additional.H               OSI templates. You can do this at a later time. Proceed to               Section 6.8.  I                   Using the BASIC and ADVANCED Configuration Options 6-47g t  .      :         Using the BASIC and ADVANCED Configuration Options"         6.7 Configuring Transports                   ADVANCED  D               The ADVANCED option provides the opportunity to createF               additional OSI templates. The dialog begins by asking if6               you want to create additional templates:  Q               * Do you want to create additional OSI templates?       [NO] :  yes   I               If you answer YES, the procedure uses the prompts discussedhC               in this section to obtain the information required to.D               configure the OSI templates. If you answer NO, you canE               create additional templates at a later time. Proceed to                Section 6.8.  *         6.7.6.1 Common Template Parameters  H               The template questions begin with the parameters common to<               all templates for all transport service types:  H               1. The procedure asks for the type of template you want to                  create:  >                  o  Connectionless-mode Network Service (CLNS)  C                     There are two forms of CLNS: Internet/ES-IS and.H                     Null Internet. Both forms support only one transport#                     class: Class 4.   /                     -  CLNS with Internet/ES-IS7  G                        The communicating end systems may be on the same C                        subnetwork or on different subnetworks. This2H                        network service is provided by the implementationG                        of the ES-IS (end system to intermediate system) F                        Internet routing protocols, which route packetsD                        from the end system to an intermediate system?                        on the same subnetwork. The intermediate D                        system ensures that packets reach their finalH                        destination. Two end systems that implement ES-ISH                        on the same subnetwork may communicate without an7                        intervening intermediate system.   .                     -  CLNS with Null Internet  H                        The communicating end systems must be on the sameH                        802.3 local area network. This network service isF                        provided by the inactive subset of the InternetF                        protocol. No intermediate system is involved in.                        the network connection.  >                  o  Connection Oriented Network Service (CONS)  ?         6-48 Using the BASIC and ADVANCED Configuration Optionsa o  i      I                        Using the BASIC and ADVANCED Configuration Options I                                                6.7 Configuring Transportsr    =                     In DECnet-Plus, CONS is supported by X.25tD                     connections. CONS supports all transport classesD                     (class 0, 2, and 4). The underlying X.25 network;                     connection can be any of the following:2  F                     -  A connection between two systems attached to anH                        X.25 Packet Switching Data Network (PSDN), either:                        directly or via a connector system.  B                     -  A point-to-point connection between two endG                        systems using the LAPB protocol as the data link.                         protocol.  B                     -  A direct connection between two end systemsA                        attached to the same IEEE 802.3 local area 8                        network, using the LLC2 protocol.  H                  o  A connection between two systems using the X.25 overC                     TCP/IP (XOT) protocol as described in RFC 1613.   7                  o  RFC 1006 Network Service (RFC 1006).  C                     Indicates that the OSI transport should use theo@                     TCP/IP protocol stack. This service supports@                     transport classes 0 and 4. When using DECnetC                     applications over RFC 1006 connections, the OSIpG                     transport template osit$rfc1006 is used for inboundgA                     connections; the default template is used fort)                     outbound connections..  <                  Enter the template type you want to create:  I                  * Type of network service (CLNS/CONS/RFC1006)?  [CLNS] :.  G                  If you want to use Connectionless-mode Network ServiceEC                  (CLNS), press Return. Otherwise, enter the network C                  service for which you want to define the template.2  C               2. Depending on which network service you select, the.A                  procedure displays one of the following prompts:X  Q                  * Name of the OSI template?               [OSIT$CLNS_Default0] :.  Q                  * Name of the OSI template?               [OSIT$CONS_Default0] :n  T                  * Name of the OSI template?               [OSIT$RFC1006_Default0] :  I                  Enter the name you want to use for the OSI template (for G                  example, OSI_TEMPLATE_1) or press Return to accept the +                  default OSI template name..  I                   Using the BASIC and ADVANCED Configuration Options 6-49. .  .      :         Using the BASIC and ADVANCED Configuration Options"         6.7 Configuring Transports    F               3. Next, the procedure asks if the template will be usedG                  exclusively for inbound packets. Templates for inbound B                  connections provide OSI transport characteristicsH                  required for inbound transport connections. If no otherF                  template can be found with the inbound characteristicC                  set, OSI transport uses the template with the name C                  DEFAULT. For more information about how an inboundoI                  template is selected, see the description of the inbound1G                  characteristic of the osi transport template entity in8H                  the HP DECnet-Plus for OpenVMS Network Control Language"                  Reference manual.  G                  Indicate if this template will be used exclusively forr%                  inbound connections:   T                  * Will this template be used for inbound packets?           [YES] :  A                  If you want this template to be used for inbound E                  connections, enter YES. If you want this template to8<                  be used for outbound connections, enter NO.  H               4. DECnet-Plus supports three transport classes: 0, 2, andF                  4. The following list provides a short summary of the;                  services provided by each transport class:f  D                  o  Class 0 - The most basic transport service. ThisH                     service does not support flow control, multiplexing,4                     or error detection and recovery.  =                  o  Class 2 - Supports class 0 functions plus D                     multiplexing and flow control. The OSI transport>                     always uses the flow control capabilities.  C                  o  Class 4 - Supports class 2 functions plus error +                     detection and recovery..  F                  If you selected CONS as the network service type, theI                  default is 0, 2, 4. If you selected CLNS, the default isiG                  4. If you selected RFC1006, the default is 0, 2. Enter.G                  the numbers of the transport protocol classes you want.A                  to allow for connections that use this template:.  L                  * Transport Classes to support?                       [4] :  G                  For more information about transport protocol classes,.@                  refer to the HP DECnet-Plus for OpenVMS Network#                  Management manual.   ?         6-50 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options.I                                                6.7 Configuring Transports.    I               5. The following two questions are common to all templates. I                  However, the order in which they appear varies depending.-                  on the network service type.   F                 ________________________ Note ________________________  A                 For CLNS and RFC 1006 template definitions, entercB                 the information discussed in this step, proceed toE                 the appropriate service-specific subsection, and then 1                 return to Step 6 in this section.   C                 For CONS template definitions, proceed to the CONS- >                 specific subsection (Section 6.7.6.3) and thenD                 return to this step after entering the CONS-specific                 information.  F                 ______________________________________________________  F                  The configuration procedure asks if you want to allowC                  expedited data on transport connections using thisi                  template:  O                  * Allow use of expedited data?                         [YES] :2  I                  If you want to support the use of expedited data, answer                   YES..  F                  The configuration procedure asks if you want to allowH                  checksums on transport connections using this template:  O                  * Allow use of Checksums?                              [YES] :   H                  If you want to use the error correction feature, answer                  YES..  G               6. All template definitions end with a question asking if.9                  you want to create additional templates:   O                  * Do you want to create additional OSI templates?       [NO] :t  G                  This prompt allows you to create additional customized.E                  OSI templates. If you answer YES to this prompt, the.I                  template questions are repeated (starting with the "Name.F                  of the OSI template?" prompt discussed in Step 2). If7                  you answer NO, proceed to Section 6.8.c  I                   Using the BASIC and ADVANCED Configuration Options 6-51t .  .      :         Using the BASIC and ADVANCED Configuration Options"         6.7 Configuring Transports    8         6.7.6.2 CLNS Network Service Template Parameters  B               A CLNS OSI transport template can specify the use ofG               Internet/ES-IS routing protocols or Null Internet routingEI               protocol. The Null Internet protocol only operates over LAN.=               routing circuits (CSMA-CD and FDDI data links)..  G               A CLNS OSI transport template for use with Internet/ES-IS.H               routing protocols can use any routing circuits configured;E               the Routing module determines the most suitable circuit E               to use. A CLNS OSI transport template for use with Null I               Internet routing protocol can only use one routing circuit;3E               routing circuit selection is based on its inactive area                address.  A               Specify the CLNS routing protocol supported by this.               template:   H               * Use full CLNP or Null Internet?            [Full CLNP] :  F               Press Return to accept the default of full clnp or enter               null internet.  G                 _______________________ Warning _______________________i  B                 If you specify the Null Internet option and no LANC                 circuits are available, the configuration procedure.6                 terminates with the following message:  S                 %NET$CONFIGURE-E-ERRINRTGCIRC, error in accessing a default routinga                   circuit name  F                 ______________________________________________________  A               If you answer Null Internet, the procedure asks two1C               additional questions. The first question asks for the.I               routing circuit you want to use for this CLNS Null Internet.               template:3  W               * Which routing circuit is this Null Internet template for?  [CSMACD-0] :   G                 _______________________ Warning _______________________   F                 If you specify either a nonexistent routing circuit orF                 a non-LAN routing circuit, the configuration procedure6                 terminates with the following message:  ?         6-52 Using the BASIC and ADVANCED Configuration Optionst .  .      I                        Using the BASIC and ADVANCED Configuration Options.I                                                6.7 Configuring Transports     Q                 %NET$CONFIGURE-E-RTGCIRCNOTFND, routing circuit name circuit-nameu8                    not found in the routing circuit list  F                 ______________________________________________________  C               A CLNS OSI transport template that specifies the Null I               Internet routing protocol selects the routing circuit based B               on the inactive area address of the routing circuit.  H               If this templates supports Null Internet routing, you mustE               configure an inactive area address for the circuit. The E               inactive area address for the circuit must be different D               from 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 inactive.?               area set in routing for Null Internet to be used.n  D               Specify the CLNS inactive area address to use for this               template:   P               * Which CLNS Inactive Area to use?                   [49::FF-00] :  8         6.7.6.3 CONS Network Service Template Parameters  G               For CONS transport connections, you must specify the name H               of the X.25 Access template that transport should use whenB               making outgoing calls using this transport template.  C               Enter the name of the X.25 Access template to use for                outgoing calls:   L               * CONS template name?                        [OSI Transport] :  C               If the CONS template is used for inbound packets, younB               must specify the name of the X.25 Access filter thatF               transport should use when receiving incoming calls using&               this transport template.  A               Enter the name of the X.25 Access filter to use for.               incoming calls:   L               * CONS filter name?                          [OSI Transport] :  I                   Using the BASIC and ADVANCED Configuration Options 6-53            :         Using the BASIC and ADVANCED Configuration Options"         6.7 Configuring Transports    <         6.7.6.4 RFC 1006 Network Service Template Parameters  E               OSI applications over TCP/IP (RFC 1006) and DECnet over.C               TCP/IP (RFC 1859) connections use RFC 1006 templates.pB               For more information on configuring OSI applications?               over TCP/IP and DECnet-Plus over TCP/IP, refer to C               Section 6.7.2.1 and the "Managing Transport Services" ?               section in the HP DECnet-Plus for OpenVMS Network                 Management manual.  F               For RFC 1006 templates, you must define the local TCP/IPI               port number to use for outgoing transport connections usingo               this template.  E               Enter the port number to use for outgoing RFC 1006-type                connections:  L               * Local RFC1006 port number?                           [102] :  C               For OSI applications over TCP/IP, use 102 as the port.D               number. For DECnet over TCP/IP connections, use 399 as               the port number.  G               If the RFC 1006 template is used for inbound packets, you.H               must define the local TCP/IP port number to be used as theI               listener port for incoming transport connections using this.F               template. If the listener port number does not match theF               outgoing port number, this template will not be used for#               incoming connections.   E               Enter the port number to use for incoming RFC 1006-type                connections:  L               * RFC1006 listener port number?                        [102] :  C               For OSI applications over TCP/IP, use 102 as the portxD               number. For DECnet over TCP/IP connections, use 399 as               the port number.  6         6.8 Configuring Time Zone Differential Factors  @               The UTC (Coordinated Universal Time) is calculatedE               automatically by using the OpenVMS UTC. No messages are1               displayed.  ?         6-54 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                      6.9 Configuring the Event Dispatcher     ,         6.9 Configuring the Event Dispatcher                 BASIC   A               The procedure displays a message stating that it is C               providing the default Event Dispatcher configuration:   [               %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configurationg  &               Proceed to Section 6.10.                 ADVANCED  F               If you are configuring the Event Dispatcher on a clusterH               member, the procedure asks if you want the resultant eventF               NCL script file created in the cluster common directory:  J                   There is no EVENT startup script present on your system.P                   Would you like this script to be made common to all systems inP                   this cluster, or private to this system?  If you answer YES to@                   this question, the script will be made common.  L               * Create a cluster common EVENT startup script?        [YES] :  I               Answer YES to create an event NCL script file common to all.F               cluster members. Answer NO to create an event NCL scriptH               file unique to the cluster member on which you are running               net$configure.  E               The procedure begins the Event Dispatcher configurationtE               by asking if you want to customize the event dispatcherc               configuration:  H               * Do you want to customize the Event Dispatcher?    [NO] :  H               If you answer YES, proceed to Section 6.9.1. If you answerE               NO, the procedure displays a message stating that it is C               providing the default Event Dispatcher configuration:   [               %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configurationo  C               You have the option of blocking the display of eventsnD               targeted for this system's console. The procedure asks;               if you want to display events on the console:o  M               * Display events logged to the console of this machine? [YES] :t  G               Answer YES if you want to see the events targeted for theoH               console on this system. Answer NO if you want to block the9               display of events on your system's console.g  &               Proceed to Section 6.10.  I                   Using the BASIC and ADVANCED Configuration Options 6-55            :         Using the BASIC and ADVANCED Configuration Options,         6.9 Configuring the Event Dispatcher    %         6.9.1 Configuring Event Sinkso  A               The procedure begins the customization of the event E               dispatcher by asking if you want to configure any event F               sinks. Event sinks manage incoming event connections andI               maintain a set of filters (global, specific, and catch-all) H               that are applied to all data streams assigned to the sink.  >               Indicate if you want to configure a custom sink:  H               * Configure a Sink?                                [YES] :  F               If you want to create a customized sink, answer YES (forF               example, if you want to change where to send the output:C               a terminal, a printer, or a file). If you do not want F               to configure a customized sink, answer NO and proceed to               Section 6.9.2.  G               1. If you indicate that you want to create a custom sink,.<                  the procedure asks you for the sink's name:  K                  * Sink name?                                             :   A                  Specify the name of the sink you want to create.   G               2. Next, specify the maximum buffer size (in octets) that 4                  the sink can use to process events:  K                  * Maximum buffer size?                                   :   *                  Specify an integer value.  F               3. You have the option of associating a DECdns full nameG                  with the sink being created. To allow outbound streams4C                  to connect to this sink, you must specify either a G                  DECdns object name or an end-user name. If you specify G                  a DECdns object name it must match the sink object you G                  supply when you create any outbound streams using this                   sink.  I                  Next, the procedure asks you for the sink's object name:S  K                  * Object name?                                           :o  B                  If you will be using an object name when definingD                  outbound streams associated with this sink, specify(                  the sink's object name:  ?         6-56 Using the BASIC and ADVANCED Configuration Options-           I                        Using the BASIC and ADVANCED Configuration Options I                                      6.9 Configuring the Event Dispatcher     E               4. You have the option of associating a session control I                  end-user specification with the sink being created. This I                  is equivalent to specifying the addresses characteristic D                  of a session control application. To allow outboundI                  streams to connect to this sink, you must specify either_F                  a DECdns object name or an end-user specification. IfH                  you specify an end-user specification it must match theG                  sink end-user specification you supply when you createf6                  any outbound streams using this sink.  G                  If desired, specify the sink's end-user specification:   K                  * End user specification?                                :E  <                  Enter an end-user specification in the form7                  number=number, name=name, or uic=[uic- %                  identifier]username.X  E               5. If no other filter actions match an event, or if all I                  other filter actions for an event are set to ignore, the E                  actions specified for the catch-all filter are used.s  I                  Specify the action that the catch-all filter should use:s  K                  * Catch all filter action?                               :A  !                  The choices are:m  .                  o  BLOCK - Discard the event.  ,                  o  PASS - Report the event.  H               6. You have the option of entering an informational string&                  to describe the sink:  K                  * Description?                                           :_  ,                  Enter informational string.  F               7. You can specify that an entity's unique identifier be+                  displayed with each event.c  K                  * Display UIDs?                                          :e  G                  Answering YES displays the entity's unique identifier.   E               8. You can specify how the application is to accept the >                  events received by the sink. The choices are:  G                  o  CONSOLE - Events go the operator's console (OPCOM).t  3                  o  DEVICE - Events go to a device.   I                   Using the BASIC and ADVANCED Configuration Options 6-57  o  a      :         Using the BASIC and ADVANCED Configuration Options,         6.9 Configuring the Event Dispatcher    /                  o  FILE - Events go to a file.   >                  Enter your choice for the sink's client type:  K                  * Client type?                                           :c  E                  If you answer FILE to the "Client type?" prompt, thep=                  procedure asks you for the file name to use:t  L                  * File name?                                              :  H                  Enter the file specification you want to use to captureB                  events (for example, sys$manager:evd_events.log).  G                  If you answer DEVICE to the "Client type?" prompt, thee:                  procedure asks you for the device to use:  L                  * Device name?                                            :  H                  Enter the device you want to use to capture events (for!                  example, TWA1:).   7               The sink's configuration is now complete.k  D               Next, the procedure asks if you want to create another               sink:   I               * Configure another Sink?                            [NO] :s  H               If you do not want to configure another sink, press ReturnG               to proceed to Section 6.9.2. If want to configure another I               sink, enter YES and press Return. The procedure returns you H               to the "Sink name?" prompt discussed in Step 1 and repeats=               the prompts required to configure another sink.            6.9.2 Outbound Streams  D               The procedure continues the customization of the eventH               dispatcher by asking if you want to configure any outboundH               streams. Outbound streams represent an outgoing connectionI               to an event sink. An outbound stream manages the connection I               to the sink and it filters, processes, and transmits eventsd               to the sink.  I               Indicate if you want to configure a custom outbound stream:l  I               * Configure an Outbound Stream?                     [YES] :D  ?         6-58 Using the BASIC and ADVANCED Configuration Optionse S  c      I                        Using the BASIC and ADVANCED Configuration OptionssI                                      6.9 Configuring the Event Dispatcher     H               If you want to create a customized outbound stream, answerC               YES (for example, if you want to change where to send B               the event data stream). If you do not want to createD               a customized outbound stream, answer NO and proceed to               Section 6.9.3.  A               1. If you indicate that you want to create a customuI                  outbound stream, the procedure asks you for the outbound                   stream's name:o  L                  * Outbound Stream name?                                   :  D                  Specify the name of the outbound stream you want to                  create.  G               2. Next, specify the maximum buffer size (in octets) that ?                  the outbound stream can use to process events:   L                  * Maximum buffer size?                                    :  *                  Specify an integer value.  C               3. The connect retry timer operates continuously from B                  the time the outbound stream is enabled until theF                  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.   I                  Specify the number of seconds to wait between connections                  attempts:  L                  * Connect retry timer?                                    :  *                  Specify an integer value.  H               4. If you intend to have the outbound stream use the retryG                  timer value you provided in the previous question, you 5                  must enable the connect retry timer.e  G                  Specify if you want to enable the connect retry timer:o  L                  * Connect timer enabled?                                  :  H                  Answer YES to have the connect retry timer operational.)                  Answer NO to disable it.   I                   Using the BASIC and ADVANCED Configuration Options 6-59     o      :         Using the BASIC and ADVANCED Configuration Options,         6.9 Configuring the Event Dispatcher    F               5. The disconnect timer is the number of seconds to waitF                  before shutting down an idle connection. A value of 0H                  indicates that the no disconnect timer is used and thatB                  connections are never disconnected automatically.  F                  Specify the number of seconds to wait before shutting)                  down an idle connection:   L                  * Disconnect timer?                                       :  *                  Specify an integer value.  E               6. The catch-all filter specifies the action to take if C                  neither the specific filter setting nor the global G                  filter setting matches an event or if a filter setting D                  that matches an event is set to Ignore. The choices                  are:n  .                  o  BLOCK - Discard the event.  ,                  o  PASS - Report the event.  C                  Enter the action to take for the catch-all filter:   L                  * Catch all filter action?                                :  G               7. You have the option of specifying the DECdns full name E                  of the event sink. For an outbound stream to connect G                  with an event sink, you must specify the sink's DECdns H                  object name, the sink's node name/end-user pair, or theE                  sink's address tower. If you specify a DECdns object F                  name, it must match the object name you used when you(                  created the event sink.  M                  * Sink object?                                             :   E                  If desired, enter the full DECdns object name of the ;                  sink associated with this outbound stream..  H               8. You have the option of specifying a sink node/sink end-F                  user pair to identify the event sink. For an outboundG                  stream to connect with an event sink, you must specify I                  the sink's DECdns object name, the sink's node name/end- 8                  user pair, or the sink's address tower.  G                  If you are specifying a sink by its node name/end-usernI                  pair, enter the full node name (namespace name included) =                  of the sink associated with outbound stream:n  M                  * Sink node?                                               :   ?         6-60 Using the BASIC and ADVANCED Configuration Optionsn _  n      I                        Using the BASIC and ADVANCED Configuration Options_I                                      6.9 Configuring the Event DispatcherM    G                  If you are specifying a sink by its node name/end-user G                  pair, enter the Session Control end-user specification F                  of the sink associated with this outbound stream (for%                  example, number=82):   M                  * Sink end user?                                           :   7                  Enter an end-user specification in then;                  form number=number, name=name or uic=[uic-o%                  identifier]username.   G               9. You have the option of specifying a sink address tower F                  to identify the event sink. For an outbound stream toH                  connect with an event sink, you must specify the sink'sH                  DECdns object name, the sink's node name/end-user pair,-                  or the sink's address tower.   I                  If you are specifying a sink by its address tower, enter H                  the sink address tower of the sink associated with this!                  outbound stream:k  M                  * Sink address?                                            :   B               The outbound stream's configuration is now complete.  D               Next, the procedure asks if you want to create another               outbound stream:  J               * Configure another Outbound Stream?                  [NO] :  F               If you do not want to configure another outbound stream,D               press Return to proceed to the Phase IV Relay section.E               If you want to configure another outbound stream, enter D               YES and press Return. The procedure returns you to theD               "Outbound Stream name?" prompt discussed in Step 1 andH               repeats the prompts required to configure another outbound               stream.            6.9.3 Phase IV Relay  F               A Phase IV relay allows you to record and process eventsE               that occur on an OpenVMS system running DECnet Phase IVtE               software. The Phase IV Relay entity receives the eventsnH               from a Phase IV node, encapsulates them, and posts them in6               the DECnet-Plus system Event Dispatcher.  ?               Indicate if you want to include a Phase IV relay:   J               * Configure Phase IV Relay?                          [YES] :  I                   Using the BASIC and ADVANCED Configuration Options 6-61o n         :         Using the BASIC and ADVANCED Configuration Options,         6.9 Configuring the Event Dispatcher    6               Answer YES to create the Phase IV Relay.  1         6.10 Configuring the Application Database   E               This configuration section sets up the default accounts =               used by the following DECnet-Plus applications:   A               o  File access listener (FAL) - provides authorized H                  access to the file system of a DECnet node on behalf ofG                  processes executing on any DECnet node in the network. F                  FAL communicates with the initiating node by means of0                  the Data Access Protocol (DAP).  D               o  CMIP Management Listener (CML) - is the DECnet-PlusH                  management module that implements the Common ManagementG                  Information Protocol (CMIP). CML enables the system toD7                  respond to remote management commands.r  B               o  MAIL - allows users to send and receive messages.  D               o  VMScluster Performance Monitor (VPM) - supports theA                  OpenVMS Monitor utility command monitor cluster.s  H               o  MIRROR - supports particular forms of loopback testing.  F               o  PHONE - allows users on the same or different OpenVMS6                  systems to communicate interactively.                 BASIC   ?               The BASIC option includes the DECnet-Plus defaultsE               applications in the application database. The proceduretC               creates default user accounts for the CML, MAIL, VPM,cG               MIRROR, and PHONE applications (no account is created fortG               FAL). The procedure displays the following messages as it +               creates the default accounts:r  Z               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER[               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER Z               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER\               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER\               %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER  F                 ________________________ Note ________________________  E                 The procedure also assigns certain process privileges C                 and rights identifiers to each account. If you have A                 the audit server enabled during configuration, it   ?         6-62 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                 6.10 Configuring the Application Databasea    ?                 displays several OPCOM messages related to this                  process.  F                 ______________________________________________________  &               Proceed to Section 6.11.                 ADVANCED  C               The ADVANCED option allows you to control the defaultg7               accounts for all the DECnet applications.   D               If you are configuring a cluster member, the procedureI               asks if you want the resultant applications NCL script file 6               created in the cluster common directory:  P                   There is no APPLICATION startup script present on your system.P                   Would you like this script to be made common to all systems inP                   this cluster, or private to this system?  If you answer YES to@                   this question, the script will be made common.  R               * Create a cluster common APPLICATION startup script?        [YES] :  I               Answer YES to create an applications NCL script file common I               to all cluster members. Answer NO to create an applicationsaG               NCL script file unique to the cluster member on which you (               are running net$configure.  G               1. The procedure begins the applications configuration by C                  asking you for the default account to use for FAL:   Y                  * Do you want to use a default account for the 'FAL' application? [NO] :   G                  If you want an account set up and used for FAL, answerc                  YES.u  H                  If you answer YES, the procedure displays the following                  message:   ]                  %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account FAL$SERVERt  H               2. The procedure then asks if you want to set up a default!                  account for CML:   Z                  * Do you want to use a default account for the 'CML' application? [YES] :  G                  If you want an account set up and used for CML, answerr                  YES.   I                   Using the BASIC and ADVANCED Configuration Options 6-63            :         Using the BASIC and ADVANCED Configuration Options1         6.10 Configuring the Application Database     H                  If you answer YES, the procedure displays the following                  message:   ]                  %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER   I               3. Next, the procedure asks if you want to set up a default "                  account for MAIL:  [                  * Do you want to use a default account for the 'MAIL' application? [YES] :_  H                  If you want an account set up and used for MAIL, answer                  YES.   H                  If you answer YES, the procedure displays the following                  message:C  ^                  %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER  H               4. The procedure continues by asking if you want to set up+                  a default account for VPM:t  Z                  * Do you want to use a default account for the 'VPM' application? [YES] :  H                  Answer YES if the system is part of an OpenVMS Cluster.C                  Answer NO if the system is to be a non-cluster end                   system.  H                  If you answer YES, the procedure displays the following                  message:_  ]                  %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER_  I               5. Next, the procedure asks if you want to set up a defaulth4                  account for the MIRROR application:  ]                  * Do you want to use a default account for the 'MIRROR' application? [YES] :h  7                  If you want to use MIRROR, answer YES.f  H                  If you answer YES, the procedure displays the following                  message:   _                  %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER   I               6. Finally, the procedure asks if you want set up a default #                  account for PHONE:   \                  * Do you want to use a default account for the 'PHONE' application? [YES] :  G                  If you intend to use the OpenVMS PHONE utility, answer                   YES.   ?         6-64 Using the BASIC and ADVANCED Configuration Options  P  2      I                        Using the BASIC and ADVANCED Configuration OptionsiI                                 6.10 Configuring the Application Database     H                  If you answer YES, the procedure displays the following                  message:   _                  %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER   F                 ________________________ Note ________________________  E                 The procedure also assigns certain process privileges C                 and rights identifiers to each account. If you have A                 the audit server enabled during configuration, it ?                 displays several OPCOM messages related to thisg                 process.  F                 ______________________________________________________  '         6.11 Configuring the MOP Client   F               By default, MOP is not started by net$startup. To enableC               this system to service MOP requests, the NET$STARTUP_mD               MOP logical name must be defined to signal net$startupE               to load the MOP software. This logical name is normallyMD               defined in sys$startup:net$logicals.com. Based on yourF               input, the procedure modifies net$logicals.com by addingG               or removing the definition of the NET$STARTUP_MOP logicalrH               name. This section of the procedure also generates a shortD               NCL startup script file containing the NCL commands to/               create and enable the MOP entity.   8               The procedure asks if you want MOP loaded:  L               * Load MOP on this system?                             [YES] :  E               Answer YES to enable MOP service on this system. AnswerrF               NO to disable MOP service on this system. Note that yourG               answer will have no effect if the NET$STARTUP_MOP logicalo(               name is defined elsewhere.  D               If you are configuring a cluster member, the procedureH               asks if you want the resultant MOP NCL startup script file8               created in the cluster's common directory:  O                   There is no MOP_CLIENT startup script present on your system.oP                   Would you like this script to be made common to all systems inP                   this cluster, or private to this system?  If you answer YES to@                   this question, the script will be made common.  Q               * Create a cluster common MOP_CLIENT startup script?        [YES] :i  I                   Using the BASIC and ADVANCED Configuration Options 6-65            :         Using the BASIC and ADVANCED Configuration Options'         6.11 Configuring the MOP Client_    G               Answer YES to create a MOP NCL startup script file commonlC               to all cluster members. Answer NO to create a MOP NCLeG               startup script file unique to the cluster member on whichs,               you are running net$configure.  *         6.12 Configuring the Cluster Alias  H               All of the nodes or a subset of the nodes that are membersE               of an OpenVMS Cluster can be represented in the networkeG               as a single node by establishing an alias for the clustermH               members. The alias allows users access to common resourcesH               on the OpenVMS Cluster members without knowing which nodesG               are members of the alias. Refer to the HP DECnet-Plus for D               OpenVMS Network Management manual for more information8               about setting up an OpenVMS Cluster alias.  <               If the node is an OpenVMS Cluster member or ifE               net$configure finds an alias NCL startup script file oniE               the system, the procedure prompts you to enter the full_(               name of the cluster alias:  A               * Full name of Cluster Alias                      :   E               If you do not want the node to participate in a cluster ;               alias, press Return. Proceed to Section 6.13.   E               If you want the node to participate in a cluster alias, H               specify the full name that uniquely identifies the cluster:               alias node (for example, ACME:.WABBIT.HELP).  F                 ________________________ Note ________________________  F                 If you create a cluster alias, you must manually enterE                 the alias information into the appropriate namespace. C                 See the "Using an OpenVMS Cluster Alias" section inoA                 the HP DECnet-Plus for OpenVMS Network Managements,                 manual for more information.  F                 ______________________________________________________  I               If you entered a cluster alias, you must associate a unique D               address with the cluster alias. Do not use your node'sD               address for the cluster alias. If you are unsure whichH               address to enter, consult your network manager. Use eitherI               a DECnet Phase IV node address or Ethernet physical addresst               for the alias.  ?         6-66 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                        6.12 Configuring the Cluster Aliasl    H               The Phase IV node address has the format area-number.node-+               number (for example, 12.139).n  D               The Ethernet physical address has the format AA-00-04-C               00-xx-xx, where xx-xx is calculated from the Phase IV_G               node address. To determine the Ethernet physical address, !               proceed as follows:   A               1. Convert the Phase IV node address to its decimalr'                  equivalent as follows:   H                  (area-number * 1024) + node-number = decimal equivalentA                  (For example, (12 * 1024) + 139 = 12427 decimal)   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:C  K                  (12427 decimal = 308B hex, reversed = 8B30 hexnodeaddress)t  @               3. Incorporate the hexadecimal node address in the"                  following format:  +                  AA-00-04-00-hexnodeaddressa1                  (For example, AA-00-04-00-8B-30)a  D               Enter the unique address to associate with the cluster               alias:  V               * Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) : 12.139  C               If you entered a cluster alias full name, you need to G               specify the selection weight for this node. The selection A               weight determines the number of sequential incoming E               connects passed to this alias member node in the round- A               robin sequence before proceeding to the next member C               node in the sequence. A value of zero means this node E               is not eligible to receive incoming connections to this G               alias address. Selection weight apportions incoming aliasaI               connections according to the capacity of each alias member.rI               For example, nodes with greater capacity should have largerlD               values for the selection weight, while OpenVMS Cluster?               satellites should generally have a value of zero.o  @               Specify a nonzero selection weight if this node isG               connected locally to a dual-ported disk, or if it will be H               serving any multihost disks, such as RFxx or HSC-connectedI               disks, to other cluster members. Setting a selection weighteB               that is too low encourages needless connection delay  I                   Using the BASIC and ADVANCED Configuration Options 6-67i s         :         Using the BASIC and ADVANCED Configuration Options*         6.12 Configuring the Cluster Alias    E               because each incoming connection is treated in a round-cF               robin fashion. That is, as each new connection comes in,I               it must be passed to the next cluster member. HP recommendse&               values between 5 and 10.  A               Enter the selection weight for this cluster member:   L               * Selection weight for this cluster node [0 for satellites]  :           6.13 Summary Display  B               At this point, the procedure has asked all questionsI               related to the node's configuration. The procedure displays B               a summary of most of the information gathered by the#               net$configure dialog:   :                                   Summary of Configuration                  Node InformationhI                       Directory Services Chosen:      DECDNS,LOCAL,DOMAINp<                       Primary Directory Service:      DECDNS@                       DECdns Full name:       ACME:.WABBIT.ELMER:                       Local Full name:        LOCAL:.ELMER%                       Fully QualifiedtC                       Host name:              ELMER.WABBIT.ACME.EDUA3                       Node Synonym:           ELMER,3                       Phase IV Address:       15.27 2                       Phase IV Prefix:        49::E                       Session Control Address Update Interval:     10D5                       Routing Node Type:      ENDNODE E                       Autoconfiguration of Network Addresses: Enabled 1                       Routing ESHello Timer:  600t1                       Routing ES Cache Size:  512t  7                       Alias Name:     ACME:.WABBIT.HELP_  "                Device Information:+                       Device: ESA0 (DESVA):w6                               Data Link name: CSMACD-0>                               Routing Circuit Name:   CSMACD-0  %                Transport Information:       ?         6-68 Using the BASIC and ADVANCED Configuration Options_ _  _      I                        Using the BASIC and ADVANCED Configuration Options I                                                      6.13 Summary Display     H                       NSP Transport:                          ConfiguredD                         Maximum number of logical links:         200C                         Maximum Transmit and Receive Window:     20 E                         Maximum Receive Buffers:                 4000 U                         Flow Control Policy:                     Segment Flow ControlC  H                       OSI Transport:                          ConfiguredD                         Maximum number of logical links:         200C                         Maximum Transmit and Receive Window:     20eE                         Maximum Receive Buffers:                 4000rH                         OSI applications over TCP/IP:            EnabledH                         DECnet Applications over TCP/IP:         Enabled  3                       Congestion Avoidance Disabledw  .                Event Dispatcher Configuration:  2                       Sinks:            local_sink4                       Outbound Streams: local_stream/                       Phase IV Relay:   Enablede  '         6.14 Generating the NCL Scripts   G               After displaying the configuration summary, the procedure I               asks if you want to create the NCL startup scripts based on_*               the information you entered:  L               * Do you want to generate NCL configuration scripts?   [YES] :  H               Answer YES to accept the configuration you just specified.C               The procedure automatically generates a collection of_C               NCL startup scripts in the sys$manager directory (alltC               with the name net$function_startup.ncl. These scriptsnE               are invoked by the net$startup process when the networktB               is started. You can see each script being invoked byC               watching for the NET$STARTUP-I-EXECUTESCRIPT messagestI               during network startup. For more information about startingdI               up the network, see the "Defining Logical Names That ModifyTI               Network Operation" and "Managing a Node" sections in the HP @               DECnet-Plus for OpenVMS Network Management manual.  C               The procedure also performs a checksum process on themC               scripts so that it can be aware if any of the scriptsoH               have changed when you run net$configure again. It displaysB               a message indicating that the checksum process is in               progress:l  I                   Using the BASIC and ADVANCED Configuration Options 6-69r a         :         Using the BASIC and ADVANCED Configuration Options'         6.14 Generating the NCL Scriptsa    L               %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts  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                 ______________________________________________________  !         6.15 Starting the Networkf  H               To complete the configuration, the net$configure procedureF               must start the network. Although it can complete most ofE               the network configuration without an active network, it H               must start the network to complete the registration of the0               node in the various name services.  :               The procedure displays the following prompt:  K                * Do you want to start the network?                  [YES] :   F               Answer YES if you want to start the network and complete2               your system's network configuration.  F               If you want to postpone starting the network, answer NO.F               When you answer NO, the procedure displays the following               message:  R               ********************************************************************J               You have decided not to start the network. NET$CONFIGURE.COMP               cannot complete your system's network configuration since it needsM               the network to be partially started in order to perform certain R               operations.  As a result, your system may be left in an inconsistentO               state if you try to startup the network manually or if you decideu$               to reboot your system.  H               Once you are ready to start the network, please invoke theL               NET$CONFIGURE.COM procedure, choose menu Option 2 (Change nodeN               name/namespace name), and respond YES to starting the network soO               that the configuration procedure can finish your system's networko               configuration.R               ********************************************************************  (               Network Startup Incomplete  ?         6-70 Using the BASIC and ADVANCED Configuration Options            I                        Using the BASIC and ADVANCED Configuration Options I                                                 6.15 Starting the Networks    E               HP strongly recommends that you answer YES to start the                network.  I               When you choose to start the network, net$configure invokeseD               the sys$startup:net$startup.com procedure to start theE               network. The net$startup procedure displays informations'               similar to the following:   H                 Copyright 2006 Hewlett-Packard Development Company, L.P.C               %NET-I-LOADED, executive image LES$LES_V30.EXE loaded A               %NET-I-LOADED, executive image NET$ALIAS.EXE loaded K               %NET-I-LOADED, executive image NET$SESSION_CONTROL.EXE loadede                  .                  .                  .@               %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script:                  SYS$SYSROOT:[SYSMGR]NET$NODE_STARTUP.NCL;@               %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script<                  SYS$SYSROOT:[SYSMGR]NET$CSMACD_STARTUP.NCL;@               %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script:                  SYS$SYSROOT:[SYSMGR]NET$FDDI_STARTUP.NCL;                  .                  .                  .V               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is               RUNNING-MAJOR   H               Although the system parameters process has been automated,G               you may still see the following message if net$startup is F               not able to start the network due to insufficient system               resources:  V               %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is               OFF-AUTOGENREQ  #         6.16 Namespace Modificationh  G               Based on your answers about Phase IV database conversion, F               the directory service path, and the node's full name forF               each specified name service, the configuration procedureD               now performs a series of actions to register your nodeD               in the appropriate namespaces. The exact actions takenF               depend on the information you supplied, the existence ofG               former node identification information for your node, ands  I                   Using the BASIC and ADVANCED Configuration Options 6-71            :         Using the BASIC and ADVANCED Configuration Options#         6.16 Namespace Modificatione    G               the state of the network and any DECdns name servers usedq8               during the namespace modification process.  H               The following series of messages is for a Local namespace-?               only configuration (including a Phase IV databaseX?               conversion which includes the local node ASHFLD):s  2               Directory Service: Phase IV database  6               Exporting node name information using: *                 CONWAY               HEATHe               ASHFLD*               Number of nodes exported:  3  0               Directory Service: Local name file  H               Updating nodes listed in SYS$MANAGER:NET$PHASEIV_NODES.DAT                 CONWAY               HEATH                ASHFLD-               Number of nodes registered:   3i-               Number of nodes modified:     0   R               %NET$CONFIGURE-I-CONVERTNODEDB, converted the Phase IV node database  0               Directory Service: Local name file  /               Modifying the node: LOCAL:.ASHFLDE'               Modifying the node towers   V               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.ASHFLDJ               %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries  F                 ________________________ Note ________________________  ?                 For sets of namespace modification messages forkB                 different name service and network configurations,                  see Section 7.6.  F                 ______________________________________________________  G               After namespace information is updated, the net$configurenD               procedure calls net$startup a second time to start theD               event dispatcher, DECdts, the DECnet applications, andD               MOP (if enabled). It also enables the cluster alias atH               this time. During this phase of the startup, the procedureA               displays several messages similar to the following:l  ?         6-72 Using the BASIC and ADVANCED Configuration Options  h  E      I                        Using the BASIC and ADVANCED Configuration OptionscI                                               6.16 Namespace Modification.    :               Copyright 2006 Hewlett-Packard Company, L.P.?               %NET$STARTUP-I-STARTPROCESS, starting process EVD K               %RUN-S-PROC_ID, identification of created process is 00000117t<               %NET$STARTUP-I-EXECUTESCRIPT, executing script:                  SYS$SYSROOT:[SYSMGR]NET$EVENT_STARTUP.NCL                  .                  .                  .  A               (a series of event messages are displayed by OPCOM)a                    .                  .                  .@               %NET$STARTUP-I-STARTPROCESS, starting process DTSSK               %RUN-S-PROC_ID, identification of created process is 00000118 G               %DTSS-I-SETTDF DTSS$SERVICE set new timezone differential <               %NET$STARTUP-I-EXECUTESCRIPT, executing script@                  SYS$SYSROOT:[SYSMGR]NET$APPLICATION_STARTUP.NCLL               %NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded  E               Finally, net$configure indicates that the configuration0"               process is complete:  U               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration                  completede               $a  B               You have just completed the initial configuration of@               a DECnet-Plus for OpenVMS system. It should now be5               operational as a system on the network.   B               See Figure 3-1 and Figure 3-2 to determine your nextH               step. According to the flowcharts, you have just completed&               configuring DECnet-Plus.  A         6.17 Modifying a Current DECnet-Plus System Configuration   C               You can use the net$configure procedure to modify theyG               current configuration. Depending on which menu option yousE               select, net$configure either modifies the configuration I               automatically or produces modified NCL scripts that you can 7               use to modify the system's configuration.   =               See Chapter 7 for information about running the D               net$configure BASIC or ADVANCED options to modify your(               DECnet-Plus configuration.  I                   Using the BASIC and ADVANCED Configuration Options 6-73                          I                                                                         7 I         _________________________________________________________________   I                                         Modifying a Current Configurations    D               This chapter describes the steps necessary to modify a$               current configuration.    +         7.1 Choosing a Configuration Option   H               If your system has already been configured, you can modifyG               it with the net$configure basic configuration option (theuG               default) or with the net$configure advanced configuration_               option.   @               Table 7-1 provides some guidelines for making your#               configuration choice.t  C               After you have decided with option to use, proceed to                Section 7.2.  E         Table 7-1 Choosing a Configuration Option to Modify a Current0I         __________Configuration__________________________________________S  I         Option..._Choose_if...___________________________________________   4         BASIC     The node is in an OpenVMS Cluster.  A                   You are upgrading or reconfiguring DECnet-Plus._  @                   You need to access a DECdns server for network                   addresses.  A                   You have only one communications device, or you F                   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._  H                   You want to autoconfigure your network addresses only.  I                                                  (continued on next page)   I                                     Modifying a Current Configuration 7-1            )         Modifying a Current Configuration +         7.1 Choosing a Configuration Option_    E         Table 7-1 (Cont.) Choosing a Configuration Option to Modify auI         __________________Current_Configuration__________________________f  I         Option..._Choose_if...___________________________________________o  G                   You want to configure both the NSP and OSI transportsu@                   and only want to create default OSI templates.  I                   You want to enable DECnet over TCP/IP (RFC 1859) or OSI16                   applications over TCP/IP (RFC 1006).  I                   You do not want to enable FDDI large packet support (if_1                   you have an FDDI-type circuit).n  H                   You want to set the routing characteristic DNA addressB                   format to TRUE (to control the interpretation of'                   address structuring).   :                   You want to use integrated mode routing.  I                                                  (continued on next page)_                                                -         7-2 Modifying a Current Configuration_ _  _      I                                         Modifying a Current ConfigurationII                                       7.1 Choosing a Configuration Option     E         Table 7-1 (Cont.) Choosing a Configuration Option to Modify a I         __________________Current_Configuration__________________________   I         Option..._Choose_if...___________________________________________0  0         ADVANCED  Your configuration is complex.  E                   You need to customize your network's configuration.   I                   Your system has multiple communication devices, and youo6                   want them to run a mix of protocols.  D                   You want to configure an OpenVMS Cluster with both;                   DECnet Phase IV and DECnet Phase V nodes.r  C                   You want the option to give specific names to alli/                   devices and routing circuits.t  I                   You also want the option of not configuring all of your *                   devices for DECnet-Plus.  G                   You want the option of manually entering your network                    addresses.  G                   You want to configure either the NSP transport or theoH                   OSI transport (or both). You want the option to create+                   additional OSI templates.t  G                   You want the option of enabling/disabling DECnet over 9                   TCP/IP or OSI applications over TCP/IP.   C                   You want the option of enabling FDDI large packet =                   support (if you have an FDDI-type circuit).o  <                   You want the option of setting the routingD                   characteristic DNA address format to TRUE or FALSEI                   (to control the interpretation of address structuring).e  E                   You want the option of using either integrated mode 5                   routing or segregated mode routing.a  E                   You want the option to provide default accounts for I         __________FAL.___________________________________________________   0         7.2 Invoking the Configuration Procedure  <               Begin by invoking the configuration procedure.                 BASIC   G               To invoke the net$configure.com procedure using the BASIC @               configuration option, enter the following command:  0               $ @sys$manager:net$configure basic  I                                     Modifying a Current Configuration 7-3  n         )         Modifying a Current Configuration 0         7.2 Invoking the Configuration Procedure                   ADVANCED  A               To invoke the net$configure.com procedure using the I               ADVANCED configuration option, enter the following command:.  3               $ @sys$manager:net$configure advanced            7.3 Opening Messages  F               The procedure prints an opening message dependent on the-               configuration option you chose._                 BASIC_  F               Copyright 2006 Hewlett-Packard Development Company, L.P.                     DECnet-e>         Plus for OpenVMS BASIC network configuration procedure  R               This procedure will help you create or modify the management scriptsR               needed to operate DECnet on this machine. You may receive help aboutC               most questions by answering with a question mark '?'.   R               You have chosen the BASIC configuration option.  This option enablesS               you to quickly configure your system by answering a few questions andiV               using most of the default answers.  If you would rather do some specificR               tailoring of your  system's network configuration, you should invokeK               NET$CONFIGURE.COM with the ADVANCED configuration option, ie:s@                              @SYS$MANAGER:NET$CONFIGURE ADVANCED                 ADVANCED  F               Copyright 2006 Hewlett-Packard Development Company, L.P.                    DECnet-A         Plus for OpenVMS ADVANCED network configuration procedure   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 '?'.m  U               You have chosen the ADVANCED configuration option.  This option enablesaV               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   -         7-4 Modifying a Current Configuration     t      I                                         Modifying a Current ConfigurationeI                                                      7.3 Opening Messages                     BASIC and ADVANCED  F               Next, the procedure asks if you want to proceed with the               configuration.  L               * Do you want to continue?                             [YES] :  H               Answer YES if you want to continue. The procedure displaysI               the date that the checksum file for the NCL startup scripts                 was last modified:  L                  Configuration last run by SYSTEM on 18-SEP-2004 16:04:24.19  G               If previous configurations resulted in cluster-common NCL2I               startup script files, the procedure uses one or more of the H               following messages to tell you which cluster-common scriptE               files are in use (see Section 7.16 for more information 1               about cluster-common script files):_  Q               %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION scriptDK               %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT script_P               %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT script  E               If both cluster-common script files and system-specific G               script files exist, the procedure uses one or more of the_I               following messages to tell you which system-specific script C               files are overriding the cluster-common script files:r  Y               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific APPLICATION script overrides_+                 the cluster common settingsdS               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific EVENT script overridesl+                 the cluster common settingsoX               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific MOP_CLIENT script overrides+                 the cluster common settings   ?               The configuration procedure maintains a lock file F               (sys$common:[sysmgr]net$configure-lock.dat;1) to preventI               multiple users from running the procedure at the same time.rH               If another process is using the procedure, it displays the                following message:  S               %NET$CONFIGURE-I-WAITFORLOCK, the configuration database is in use by +                 another process, waiting...P  D               If the configuration procedure is unable to access theH               checksum file, or it can access the file but experiences aI               read error, the procedure displays one of the following twoh               messages:   I                                     Modifying a Current Configuration 7-5I a  D      )         Modifying a Current Configuration          7.3 Opening Messages    F               %NET$CONFIGURE-E-CKSOPENERR, error opening checksum fileF               %NET$CONFIGURE-E-CKSREADERR, error reading checksum file  H               If one of these error messages is displayed, the procedure@               exits. Determine the cause for the error and rerun               net$configure.  !         7.4 The Main Options Menu   G               The configuration procedure now displays the main options H               menu that you can use to modify the current configuration:  B                          Configuration Options for Node node-name:  2                        [0]     Exit this procedure  >                        [1]     Perform an entire configuration8                        [2]     Change naming information@                        [3]     Configure Devices on this machine3                        [4]     Configure TransportsnE                        [5]     Configure Timezone Differential Factora9                        [6]     Configure Event Dispatcheru=                        [7]     Configure Application database <                        [8]     Configure MOP Client database6                        [9]     Configure Cluster Alias?                        [10]    Replace MOP Client configuration 8                        [11]    Configure satellite nodesA                        [12]    Configure cluster script locationsn  H                * Which configuration option to perform?            [1] :  F                 ________________________ Note ________________________  >                 If this is the first time you are invoking the?                 net$configure procedure, or if you have deleted B                 the checksum file, the main menu is not displayed.D                 Instead, the procedure begins the full configuration.                 dialog discussed in Chapter 6.  F                 ______________________________________________________  H               Choose the option you want. Selecting an option allows youG               to modify either the entire configuration or a particular C               portion. Based on your menu selection, proceed to the 7               section indicated in the following table._  -         7-6 Modifying a Current Configuration            I                                         Modifying a Current ConfigurationcI                                                 7.4 The Main Options Menu   I               ___________________________________________________________                MenuI               Item__Option_____________________Proceed_to_..._____________  :               1     Perform an entire          Section 7.5!                     configurationw  :               2     Change naming information  Section 7.6  :               3     Configure Devices on this  Section 7.7                     machinen  :               4     Configure Transports       Section 7.8  :               5     Configure Timezone         Section 7.9'                     Differential Factor   ;               6     Configure Event            Section 7.10                      Dispatcher  ;               7     Configure Application      Section 7.11d                     database  ;               8     Configure MOP Client       Section 7.12                      database  ;               9     Configure Cluster Alias    Section 7.13   ;               10    Replace MOP Client         Section 7.14 !                     Configurations  ;               11    Configure satellite nodes  Section 7.15r  ;               12    Configure cluster script   Section 7.16 I               ______locations____________________________________________a  F                 ________________________ Note ________________________  C                 The procedure displays Options 11 or 12 only if thenB                 procedure is executing on a cluster member. OptionC                 12 is displayed only if you invoke the procedure in_D                 ADVANCED mode. See Section 7.15 and Section 7.16 for!                 more information._  F                 ______________________________________________________  ,         7.5 Changing an Entire Configuration  H               To make changes to the entire configuration, select option+               1 from the main options menu:m  J               * Which configuration option to perform?             [1] : 1  I                                     Modifying a Current Configuration 7-7_ _  _      )         Modifying a Current Configurations,         7.5 Changing an Entire Configuration    G               In most sections, the procedure displays the same prompts B               that were displayed during the initial configuration@               dialog. However, in some dialog sections there areH               differences. For this reason, you should see the following0               sections for the resulting dialog:  ;               1. Phase IV database conversion - Section 6.3   G               2. Node naming service and name information - Section 7.6   2               3. Routing information - Section 6.5  1               4. Device information - Section 6.6   4               5. Transport information - Section 7.8  <               6. Event Dispatcher information - Section 7.10  8               7. Applications information - Section 7.11  /               8. MOP information - Section 6.11   =               9. Configuration summary display - Section 7.17   5              10. NCL script generation - Section 7.18   /              11. Network startup - Section 7.19   <               Because it is highly likely that you will do aB               reconfiguration while the network is running using aC               previous configuration, you will probably not see the D               prompts related to starting the network. Therefore, toH               implement the new NCL scripts, you must reboot the system.  F               The system displays the same prompts that were displayedG               for the initial configuration. In most cases, the promptstG               now show the current configuration values as the default. I               If you do not want to change the current values, accept the I               default value. Refer to the sections indicated above for ann)               explanation of the prompts.   1         7.6 Changing the Node Name/Namespace Name   G               To change the directory name services used on the system, G               the system's full names or the fully qualified host name,aI               or the system's node synonym, select option 2 from the main                menu:   I               * Which configuration option to perform?            [1] : 2   -         7-8 Modifying a Current Configurationn h  l      I                                         Modifying a Current Configuration_I                                 7.6 Changing the Node Name/Namespace Namet    H               Although the basic dialog questions are identical to thoseI               documented in Section 6.4, there are many possible variants I               and many possible final configuration outcomes based on the H               answers you provide in this section and the current statusC               of your system. After a discussion of some processingcH               topics common to all configuration variants, the remainderF               of this section discusses several possible configuration=               modifications for name services and node names:   E               o  Changing the node from the Local-only namespace to aeI                  DECdns namespace as the primary with the Local namespaceC6                  as the secondary (see Section 7.6.3).  G               o  Changing the node as in the previous item except using B                  a DECdns server on a WAN instead of on a LAN (see                   Section 7.6.4).  I               o  Changing a DECdns clerk system to a DECdns server system %                  (see Section 7.6.5).M  G               o  Changing a DECdns server system back to a DECdns clerks,                  system (see Section 7.6.6).  F               o  Changing a DECdns clerk system with a previous DECdnsI                  server configuration back to a DECdns server system (see                    Section 7.6.7).  C               o  Modifying a DECdns server system to use the DECdns H                  namespace as a secondary namespace (see Section 7.6.8).  E               For each of the modifications in the previous list, the_G               net$configure procedure processing occurs in three steps:o  H               1. Configuration dialog processing - occurs as you provideH                  the configuration information. Based on the informationI                  you provide and the status of the current configuration,mE                  the procedure customizes the configuration dialog tot                  each task.   B               2. Namespace selection processing - occurs after allH                  configuration dialog processing has finished and beforeF                  the actual namespace configuration processing begins.D                  Based on the information you provide, the procedureB                  places the system in a condition suitable for theD                  namespace configuration processing. This processingI                  usually involves calling the dns$configure.com procedure H                  to configure the DNS clerk to use the new namespace. It5                  may also involve namespace creation.   I                                     Modifying a Current Configuration 7-9_ _  _      )         Modifying a Current Configuration 1         7.6 Changing the Node Name/Namespace Name     B               3. Namespace configuration processing - occurs afterC                  any necessary namespace selection processing. ThissG                  processing actually registers the new node informations.                  in the appropriate namespace.  3         7.6.1 Common Namespace Selection ProcessingE  A               When configuring a local system (versus a satellite E               system), all configuration changes made by using optionMC               2 are executed directly. For this reason, the network E               must be running. During namespace selection processing, G               net$configure always begins by verifying that the networkSF               is running. If the network is not running, the procedure8               asks you if you want to start the network:  L               * Do you want to start the network ?                    [YES]:  E               Answer YES to start the network and continue the node'slH               configuration. If you answer NO, or if the procedure failsG               in it's attempt to start the network, the procedure warnskI               you that you must elect to start the network or correct the H               problem that is causing the start attempt to fail and then                reinvoke option 2:  A               %NET$CONFIGURE-E-NETNOTSTARTED, network not started F               %NET$CONFIGURE-DNSNOTCONFIG, DNS could not be configured\                       **********************************************************************U                NET$CONFIGURE.COM cannot complete your system's network configuration.tS                As a result, your system may be left in an inconsistent state if youTR                try to startup the network manually or if you decide to reboot your                system.  T                When the problem is rectified and you are ready to start the network,U                please invoke the NET$CONFIGURE.COM procedure and choose menu option 2_R                (Change naming information) so that the configuration procedure canV                finish your system's network configuration before starting the network.U                **********************************************************************.  E               After displaying this warning, the procedure aborts theo?               transaction and returns to the main options menu:t  G               %NET$CONFIGURE-I-LASTTRANSABORT, last transaction abortedu  ;                       Configuration Options for Node ASHFLDk  1                       [0]     Exit this procedure_  .         7-10 Modifying a Current Configuration           I                                         Modifying a Current ConfigurationcI                                 7.6 Changing the Node Name/Namespace Nameh    =                       [1]     Perform an entire configurationu7                       [2]     Change naming information                   .                  .                  .H                * Which configuration option to perform?            [0] :  F                 ________________________ Note ________________________  ?                 The remaining tasks in this section assume thatl@                 the network is running or that net$configure can&                 successfully start it.  F                 ______________________________________________________  =         7.6.2 Modifying Node Information on Satellite Systemsd  F               During satellite node configurations (see Section 7.15),F               the procedure does only configuration dialog processing.@               Rather than actually manipulate the namespace, theB               procedure generates a node rename file (net$startup_G               rename.com) in the satellite's sys$manager: directory. ToaG               apply the node name change, you must reboot the satellite A               node. During startup, the net$startup.com procedure E               searches for the node rename file and executes the file                if located.w  G                 ______________________ Important ______________________   D                 When configuring a satellite node, you must register<                 the node before rebooting the satellite. TheB                 net$configure procedure does not register the node                 for you.  F                 ______________________________________________________  D         7.6.3 Changing a Node to Use DECdns as the Primary Namespace  D               This section describes how to add the DECdns namespaceF               as the primary namespace to a system formerly configured1               exclusively in the Local namespace.a  F                 ________________________ Note ________________________  B                 This task discussion assumes that no DECdns serverB                 software exists on the system being configured. IfC                 the DECdns server software exists on the system butt  I                                    Modifying a Current Configuration 7-11o p  M      )         Modifying a Current ConfigurationC1         7.6 Changing the Node Name/Namespace Named    D                 has never been configured, see Section 7.6.5. If theC                 DECdns server software exists on the system and hast3                 been configured, see Section 7.6.7.   F                 ______________________________________________________  -               Configuration Dialog ProcessingP  H               The following example shows a typical dialog to change theH               node from a Local namespace-only node to a node using bothI               the DECdns and Local namespaces (with DECdns as the primarys               name service):  N               * Which configuration option to perform?                 [1] : 2Y               * Enter the directory services to use on the system  [LOCAL] : decdns,localVW               * Enter the full name for directory service DECDNS           : hp:.ashfld Q               * Enter the full name for directory service LOCAL [LOCAL:.ASHFLD] :nL               * What is the synonym name for this node?           [ASHFLD] :L               * Naming cache timeout value?                  [30-00:00:00] :L               * Session Control Address Update Interval ?             [10] :L               * Naming cache checkpoint interval?               [08:00:00] :  ,               Namespace Selection Processing  F               Based on the answer provided during configuration dialogC               processing, the configuration procedure verifies that F               it can communicate with the server containing the DECdnsI               directory and then calls the dns$configure.com procedure toi5               configure the clerk for this namespace:   ]               sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.   4               Your default namespace nickname is HP.  X               Your default namespace NSCTS is AA-00-04-00-DE-11-A0-AA-F9-6F-56-DE-8E-00.  D               If the configuration procedure cannot communicate withD               the DECdns server containing the DECdns directory, the7               procedure displays the following message:   L               %NET$CONFIGURE-E-DNSNOSHOW, unable to show directory directory  0               Namespace Configuration Processing  G               Based on the answers provided during configuration dialog F               processing, the configuration procedure executes the newC               name service searchpath NCL script, renames the node, D               modifies the Local namespace entry, registers the nodeE               in the DECdns namespace, flushes the CDI cache, updatese  .         7-12 Modifying a Current Configuration           I                                         Modifying a Current Configuration I                                 7.6 Changing the Node Name/Namespace Namea    H               the node's address towers, and updates the backtranslation$               softlink for the node:  S               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to HP:.ASHFLDe  0               Directory Service: Local name file  /               Modifying the node: LOCAL:.ASHFLD '               Modifying the node towers   :               Finished obtaining address tower informationY               %NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import file   '               Directory Service: DECdns   Y               Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ASHFLD.TXT                      1) HP:.ASHFLDm  +               Number of nodes registered: 11+               Number of nodes modified:   0f  W               %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the_&               DECdns directory serviceJ               %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entriesX               %NET$CONFIGURE-I-CHECKPOINTWAIT, waiting for CDI to write the node name to"                 the CDI cache fileE               %NET$CONFIGURE-I-CHECKPOINTDONE, the node name has beenf:                 written to SYS$SYSTEM:DECNET$CDI_CACHE.DATM               %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for nodesW               %NET$CONFIGURE-E-BCKTRNUPDATED, updated backtranslation softlink for node   D               The procedure then displays the configuration summary,H               recalculates the NCL script file checksums, and redisplays$               the main options menu:  .                       Summary of Configuration                   Node Information:            I                                    Modifying a Current Configuration 7-13_ _  _      )         Modifying a Current Configurationy1         7.6 Changing the Node Name/Namespace Name     B                       Directory Services Chosen:      DECDNS,LOCAL<                       Primary Directory Service:      DECDNS@                       DECdns Full name:               HP:.ASHFLDC                       Local Full name:                LOCAL:.ASHFLD <                       Node Synonym:                   ASHFLD;                       Phase IV Address:               24.66u:                       Phase IV Prefix:                49::;                       DECdns Node Type:               ClerkiH                       Session Control Address Update Interval:        10=                       Routing Node Type:              ENDNODE E                       Autoconfiguration of Network Addresses: Enabled 9                       Routing ESHello Timer:          600d9                       Routing ES Cache Size:          512r                  .                  .                  .^               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NE               T$CONFIGUREh  ^               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration complete  ;                       Configuration Options for Node ASHFLDi  1                       [0]     Exit this procedures  =                       [1]     Perform an entire configurationO7                       [2]     Change naming informationu                  .                  .                  .H                * Which configuration option to perform?            [0] :                            .         7-14 Modifying a Current Configuration e  n      I                                         Modifying a Current ConfigurationcI                                 7.6 Changing the Node Name/Namespace Name_    F                 ________________________ Note ________________________  C                 If you are joining a Distributed Name Service (DNS) C                 Version 1.1 namespace, make sure you have access totC                 the remote server's sys$library:dns$ns_def_file.dat                  file.b  B                 Invoke the procedure sys$manager:dns$configure.comA                 and use Option 2 on the DECdns configuration menu1A                 to connect to a remote DNS Version 1 server. Make @                 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 programiA                 under a privileged account other than SYSTEM, theb>                 account still requires the appropriate access.  F                 ______________________________________________________  C         7.6.4 Configuring a DECdns Clerk System to Use a WAN DECdnsa               Server  B               This section discusses the same task as the previousA               section (adding a DECdns namespace name to a systembF               formerly configured exclusively in the Local namespace).I               However, it shows the extra processing that occurs when you H               join a namespace that is not available on your node's LAN.  -               Configuration Dialog ProcessingI  D               For the purposes of this discussion, the configurationA               dialog processing is assumed to be identical to the60               processing shown in Section 7.6.3.  ,               Namespace Selection Processing  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 DECdnseI               server on the LAN, it displays a list of all the namespacesD'               that do exist on the LAN:n  I                                    Modifying a Current Configuration 7-15p ,  P      )         Modifying a Current Configuration 1         7.6 Changing the Node Name/Namespace Namew    1               The namespace you specified was HP.u  V               %DNS-E-NOMATNS, The specified namespace is not being served on your LAN.<                       Please choose from the following list:                  [ 1]  APOLLOc                [ 2]  IAF                [ 3]  MIDAS_NSr  )                [ 0]  - Reject this list -   7                 Pick a number from the list: 0 <Return>n  C               When you see this display, type 0 and press Return to H               reject the list of namespaces currently known on your LAN.  I               The procedure then asks if you want to continue the processS%               using a WAN connection:   E                   Attempts to configure DECdns via a LAN have failed.D  G                   Type Y to attempt a WAN connection to a remote DECdns B                   server.  To stop DECdns Configuration and returnF                   control to the NET$CONFIGURE  utility, type N at the#                   following prompt:t  M               Do you want to connect to a remote DECdns server via a WAN [y]:A  E               Answer YES to connect to a remote server via a WAN. The H               procedure then prompts you for the remote server's networkF               service access point (NSAP), Phase IV-compatible addressE               (if it has one), or IP address. The NSAP is the network.D               entity title (NET) with a valid transport selector. ToG               find this information, contact the DECdns server's system G               administrator. The server system probably has a number ofpH               different NSAPs. You can use any of these NSAPs to connectF               to the server system, but you must enter the NSAP in the.               format in which it is displayed.  G                   Attempting to configure a clerk via a WAN connection.   X                Enter the NSAP or Phase IV compatible address or IP address of the server,                you want to connect to: 24.16  1               Getting server data, please wait...   E               If the procedure successfully connects with the server, D               the remainder of the namespace selection processing is)               identical to Section 7.6.3.y  .         7-16 Modifying a Current Configuration r  e      I                                         Modifying a Current ConfigurationsI                                 7.6 Changing the Node Name/Namespace Namea    C               If the procedure cannot connect to the remote server,tG               the procedure displays the following messages, aborts the >               transaction, and displays the main options menu:  N               Could not get information from server. Both Phase IV and Phase VW               connection attempts failed. Use the following information to help correctl               the problem.  8               Could not connect to remote Phase V server:               Could not connect to remote Phase IV server:  Q               The WAN configuration attempt failed.  Do you wish to retry? [y]: N >               %DNS-E-NOCONFIG, DECdns clerk is not configured.  G               %NET$CONFIGURE-I-LASTTRANSABORT, last transaction aborted   F               Correct the problem preventing the connection to the WAN1               server and run net$configure again.f  0               Namespace Configuration Processing  H               The namespace configuration processing is identical to theH               namespace configuration processing shown in Section 7.6.3.@               When performing the actual namespace configurationC               processing, it makes no difference whether the DECdnsm-               server is on a LAN or on a WAN.t  H         7.6.5 Converting a DECdns Clerk System to a DECdns Server System  I               This section describes how to convert a DECdns clerk systemo*               into a DECdns server system.  F                 ________________________ Note ________________________  B                 This description assumes that the DECdns namespaceB                 name that you specify in the dialog section is notC                 currently configured in your network and that it is C                 your intention to configure the first occurrence ofd.                 this namespace on your system.  F                 ______________________________________________________  -               Configuration Dialog Processing   F               To convert a DECdns clerk system to a DECdns server, youE               must install the DECdns server component using the PCSIsE               installation procedure (see Chapter 3). You can install C               the DECdns server before or after the initial network]               configuration.  I                                    Modifying a Current Configuration 7-17e t  s      )         Modifying a Current Configuration 1         7.6 Changing the Node Name/Namespace Namet    C               o  If you installed the DECdns server software beforeTE                  you did the initial configuration, the net$configurerI                  procedure renamed the sys$startup:dns$server_startup.comHC                  file to dns$server_startup.com-disabled during theeF                  initial configuration. The procedure informs you thatH                  this was done and asks if you want to change the system&                  into a DECdns server:  Z                       A SYS$STARTUP:DNS$SERVER_STARTUP.COM-DISABLED file has been located.X                       This indicates that the DECdns server software has been installed,R                       but this system was previously configured as a DECdns clerk.  U                       Answer YES to the next question if you want to rename this file W                       to DNS$SERVER_STARTUP.COM and configure the node as a DNS Server. Q                       If you take the default, this node will remain a DNS Clerk.   Q                  * Do you want to change this system into a DECdns server?  [NO]:D  ?                  Answer NO to leave your system configured as a >                  DECdns clerk system. Answer YES to rename theD                  sys$startup:dns$server_startup.com-disabled file toF                  sys$startup:dns$server_startup.com and configure your+                  system as a DECdns server.t  D               o  If you installed the DECdns server option after theD                  initial configuration, the procedure indicates thatB                  it has found a sys$startup:dns$server_startup.comD                  file and asks you if you want to rename the file to=                  sys$startup:dns$server_startup.com-disabled:t  Y                       A SYS$STARTUP:DNS$SERVER_STARTUP.COM file has been located.  If youlT                       do not want to configure this node as a DECdns server, you mayX                       now choose to rename that file to DNS$SERVER_STARTUP.COM-DISABLED.  X                       Answer YES to the next question if you want to configure this nodeT                       as a DECdns clerk.  If you take the default, this node will be4                       configured as a DECdns server.  U                  Do you want to rename DNS$SERVER_STARTUP.COM to .COM-DISABLED? [NO]:r  A                  Answer YES to rename the sys$startup:dns$server_ H                  startup.com file to sys$startup:dns$server_startup.com-@                  disabled and to leave your system configured as>                  a DECdns clerk system. Answer NO to leave the@                  sys$startup:dns$server_startup.com as is and to:                  configure your system as a DECdns server.  .         7-18 Modifying a Current Configuration c         I                                         Modifying a Current Configuration I                                 7.6 Changing the Node Name/Namespace Name     H               Whether you installed the DECdns server software before orG               after the initial configuration, if you elect to create a H               new DECdns server system, the procedure warns you that youF               must specify DECdns as the primary name service when you;               configure a DECdns server for the first time:   O                    Your node will be configured as a DNS Server.  Since you areeS                    configuring this DNS server for the first time, you must specifyh8                    DECdns as the primary naming service.  F               If you did not enter DECdns as the primary name service,H               the procedure displays the following warning and gives youG               a chance to re-enter the name service list with DECdns asg'               the primary name service:e  N                    You must specify DECdns as the primary naming service whileT                    configuring a DECdns server for the first time.  If you answer NOX                    to the next question, then NET$CONFIGURE will rename the SYS$STARTUP:U                    DNS$SERVER_STARTUP.COM file to .COM-DISABLED so that the node willtR                    not boot as a DNS server until it has been configured properly.  Q               * Do you want to re-enter your list of directory services?   [YES]:e  B               If you specify DECdns as the primary naming service,G               configuration dialog processing continues as shown in thehG               configuration dialog processing section of Section 7.6.3.   H               If you do not re-enter the list of directory services withI               DECdns as the first name service, the procedure renames the F               DECdns server startup file back to .com-disabled and the7               conversion to a DECdns server is aborted.   G               If you do not have a proper license for the DECdns servernB               software (DVNETEXT for OpenVMS I64 and OpenVMS AlphaI               systems or DVNETRTG for OpenVMS VAX systems), the procedure D               displays a message explaining that you need a license,D               renames the dns$server_startup.com file to dns$server_C               startup.com-disabled, and reprompts you for a list of !               directory services:r  T                    OpenVMS I64 and OpenVMS Alpha DECdns servers require the DVNETEXTR                    license.  This license is not yet loaded so this system will beY                    configured as a DECdns clerk.  To reconfigure this system as a server,VZ                    please load this license and run NET$CONFIGURE again choosing Option 2.  I                                    Modifying a Current Configuration 7-19D c  r      )         Modifying a Current Configurationw1         7.6 Changing the Node Name/Namespace Name:    ]               %RENAME-I-RENAMED, SYS$SYSROOT:[SYS$STARTUP]DNS$SERVER_STARTUP.COM;1 renamed toeH               SYS$SYSROOT:[SYS$STARTUP]DNS$SERVER_STARTUP.COM-DISABLED;1L               * Enter the directory services to use on the system  [LOCAL] :  F                 ________________________ Note ________________________  F                 For the purposes of this example, the DECdns full name:                 was specified using a null directory path:  Y                 * Enter the full name for directory service DECDNS           : HP:.ASHFLDo  F                 The net$configure procedure does not support automaticA                 creation of any directories in the directory patha@                 of the node's DECdns full name; only node objectD                 creations in the root directory ( . ) are supported.A                 If you need to specify a directory path, enter it C                 in the dialog. When the automatic node registrationr@                 fails, use the DECdns Control Program (DNSCP) toA                 create the directories in the directory path (seeaD                 the "Managing Directories" chapter in the HP DECnet-C                 Plus for OpenVMS DECdns Management manual) and thenrA                 use decnet_register to register the node (see thef@                 "Managing Name Service Searches and Information"A                 chapter in the HP DECnet-Plus for OpenVMS Networku#                 Management manual).   F                 ______________________________________________________  ,               Namespace Selection Processing  G               To configure a new namespace, the net$configure procedureiC               calls dns$configure.com twice: first to configure the C               system with the Local namespace as primary (this is a D               requirement for namespace creation), then to configure;               the system with the new namespace as primary:e  ]               sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.o  7               Your default namespace nickname is LOCAL.s  X               Your default namespace NSCTS is 08-00-2B-0D-C0-9D-5F-FA-A9-88-43-46-95-00.  1               The namespace you specified was HP.w  I               When dns$configure.com is called with the new namespace, it H               indicates that the namespace is not currently being servedF               on the LAN, displays a list of all the known namespaces,I               and asks you to choose a known namespace or reject the listp               entirely:   .         7-20 Modifying a Current Configuration x  a      I                                         Modifying a Current Configuration1I                                 7.6 Changing the Node Name/Namespace Namei    V               %DNS-E-NOMATNS, The specified namespace is not being served on your LAN.;                       please choose from the following list_                  [ 1]  AUTUMN_                [ 2]  DEC                [ 3]  DOMAINI  )                [ 0]  - Reject this list -   -                Pick a number from the list: 0X  D               When you see this display, enter 0 and press Return toE               reject the list of known namespaces. The procedure then$9               asks if you want to create a new namespace:   U                      If you are installing DECnet-Plus for OpenVMS for the first time P                      and you want to create a namespace, type Y.  If you want toH                      attempt a WAN connection to a remote DECdns server,>                      type N (default) at the following prompt:  I               Do you want to proceed with creating a new namespace [n]: y   G               If you answer NO, the dns$configure.com procedure returns I               an error to the net$configure procedure. The transaction is ?               aborted and the main options menu is redisplayed.   I               If you answer YES, the dns$configure.com procedure asks you F               for the clearinghouse name to use for the new namespace,H               starts the DECdns server process, and informs you that theB               default namespace has been set to the new namespace:  Q                      Your next input will determine the name of the clearinghouseCK                      in your namespace HP.  Enter the clearinghouse name as_?                      alphanumeric and/or underscore characters.   >               Enter a simple name for the clearinghouse: HP_CH                 Node 06               at 2003-03-28-17:40:35.901-04:00I675.395  0               Creating DECdns Server process ...K               %RUN-S-PROC_ID, identification of created process is 00000082y  4               Your default namespace nickname is HP.                 Node 06               at 2003-03-28-17:40:46.777-04:00I675.396  *         Namespace Configuration Processing  I                                    Modifying a Current Configuration 7-21            )         Modifying a Current Configurationo1         7.6 Changing the Node Name/Namespace Name     8               During namespace selection processing, theI               dns$configure.com procedure only creates the new namespace.-E               The net$configure procedure now populates the namespaceeA               with the initial groups and directories required ofeD               all namespaces (see the DECnet-Plus Planning Guide forD               more information about how DECnet-Plus uses the DECdns               namespace):P  M               %NET$CONFIGURE-I-NEWNAMESPACE, a new namespace has been createdn  U               %NET$CONFIGURE-I-ADDGROUP, adding .WorldRead_Group to the new namespace   7               Create the initial namespace directories.cH               Press Ctrl/Z at any question to cancel the initialization.  A               * Phase IV prefix value [afi:idi:predsp, Def=49::]:r<               * Maximum Phase IV area to use [1-63, Def=63]:  Z               The DECdns namespace groups and directories will now be created.  This mightQ               take up to 67 minutes or more, depending on the speed of the DECdns E               server system and the amount of traffic on the network.   3               Creating the HP:.DNA_Registrar group._=               Creating the HP:.DNA_BackTranslation directory. B               Creating the HP:.DNA_BackTranslation.%X49 directory.I               Creating the HP:.DNA_BackTranslation.%X49.%X0001 directory.iI               Creating the HP:.DNA_BackTranslation.%X49.%X0002 directory.                   .                  .                  .9               Creating the HP:.DNA_NodeSynonym directory.e@               Creating the HP:.DTSS_GlobalTimeServers directory.  I               DECdns namespace initialization for DECnet use is complete.a  G               The procedure then gives you a summary of further actionsOF               you must take to make the namespace fully functional andG               displays a summary of the directories it created (and anyt8               errors encountered during their creation):  U               If this is the first time you have initialized the namespace for DECnet 9               use, use SYS$SYSTEM:DECNET_REGISTER.EXE to:   (               * Press Return to continue  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.  .         7-22 Modifying a Current Configuration t         I                                         Modifying a Current ConfigurationoI                                 7.6 Changing the Node Name/Namespace Name     Z                 - Create any directories you need for node names that should be registeredZ                   immediately, according to your namespace design.  This includes the node/                   you are currently running on.   ]                 - Be sure to add backtranslation directories for any non Phase IV areas/IPDs.n\                   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.t  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 registrationn%                   command file above.i  Y                 - Change the currently registered names of other nodes from their defaultfZ                   names to their final full names when appropriate (for example, when they<                   are upgraded to run DECnet-Plus software).  @               Continue to use SYS$SYSTEM:DECNET_REGISTER.EXE to:  Y                 - Create any additional directories you need for node names, as new nodes 0                   are brought up on the network.  K                 - Register new nodes as they are brought up on the network.   L                 - Add members to the HP:.DNA_Registrar access control group.  (               * Press Return to continue  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:h  1                    Group:       HP:.DNA_Registrar 7                    Directory:   HP:.DNA_BackTranslation <                    Directory:   HP:.DNA_BackTranslation.%X49>                    Directories: HP:.DNA_BackTranslation.%X49.*3                    Directory:   HP:.DNA_NodeSynonym :                    Directory:   HP:.DTSS_GlobalTimeServers  (               * Press Return to continue  S               %NET$CONFIGURE-I-CREATEINITDIR, created initial namespace directories_  I                                    Modifying a Current Configuration 7-23_ _  _      )         Modifying a Current Configurationm1         7.6 Changing the Node Name/Namespace Name     C               Now that the new namespace is properly configured for E               DECnet-Plus use, the procedure registers your system in I               the new namespace using the information you supplied during .               configuration dialog processing:  '               Directory Service: DECdns   .               Registering the node: HP:.ASHFLD  S               %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered inn)                 the HP: directory servicer  G               Based on the answers provided during configuration dialog F               processing, the configuration procedure executes the newC               name service searchpath NCL script, renames the node, A               modifies the Local namespace entry, flushes the CDI G               cache, updates the node's address towers, and updates theo4               backtranslation softlink for the node:  H               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to                 HP:.ASHFLD  0               Directory Service: Local name file  /               Modifying the node: LOCAL:.ASHFLD '               Modifying the node towers   J               %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entriesM               %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for nodetW               %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for noder  D               The procedure then displays the configuration summary,H               recalculates the NCL script file checksums, and redisplays$               the main options menu:  .                       Summary of Configuration                 Node Information:                .         7-24 Modifying a Current Configuration           I                                         Modifying a Current Configuration I                                 7.6 Changing the Node Name/Namespace Name     5                       Node Type:              ENDNODE <                       Directory Services Chosen:      DECDNS<                       Primary Directory Service:      DECDNS8                       DECdns Full name:       HP:.ASHFLD4                       DECdns Node Type:       Server4                       Node Synonym:           ASHFLD4                       Phase IV Address:       24.1212                       Phase IV Prefix:        49::F                       Autoconfiguration of Network Addresses:  EnabledI                       Session Control Address Update Interval:         10e1                       Routing ESHello Timer:  600a1                       Routing ES Cache Size:  512                   .                  .                  .X               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified                  by NET$CONFIGUREU               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration                  completedt  ;                       Configuration Options for Node ASHFLDo  1                       [0]     Exit this procedure   =                       [1]     Perform an entire configuration 7                       [2]     Change naming informationp                                      I                                    Modifying a Current Configuration 7-25f t  g      )         Modifying a Current ConfigurationA1         7.6 Changing the Node Name/Namespace Name     F                 ________________________ Note ________________________  ?                 If the node registration fails, use the decnet_ A                 register tool to register the node (the procedure B                 does not create a decnet_register import file when,                 creating a local namespace):  >                 $ net_register = "$sys$system:decnet_register"J                 $ net_register register node HP:.ASHFLD directory DECDNS -Z                 _$ towers {SC3/NSP/phaseiv-address,SC3/TP4/phaseiv-address} SYNONYM ASHFLD  F                 ______________________________________________________  A         7.6.6 Converting a DECdns Server to a DECdns Clerk Systema  C               This section describes how to convert a DECdns server).               system to a DECdns clerk system.  -               Configuration Dialog Processinge  F               The procedure checks for the existence of a valid DECdnsI               server configuration (by searching for the sys$manager:dns_lG               files.txt file). If it finds the file and the file passes H               verification testing, the procedure displays the followingE               message and asks if you want to convert the server to at               clerk:  R                    The directory pointed to by SYS$MANAGER:DNS_FILES.TXT is valid.Q                    This indicates that the node has been previously configured as #                    a DECdns server.y  R                    Answer YES to the next question if you would like to rename theR                    the DNS$SERVER_STARTUP.COM file to .COM-DISABLED to change thisR                    node to a DECdns clerk.  If you take the default, the node will4                    be configured as a DECdns server.  V               Do you want to rename DNS$SERVER_STARTUP.COM to .COM-DISABLED.COM? [NO]:  :               Answer NO to leave your system configured as:               a DECdns server system. Answer YES to rename<               the sys$startup:dns$server_startup.com file toG               sys$startup:dns$server_startup.com-disabled and configure I               your system as a DECdns clerk. In both cases, configuration_G               dialog processing continues as shown in the configurationf9               dialog processing section of Section 7.6.3.v  .         7-26 Modifying a Current Configuration y  d      I                                         Modifying a Current Configuration I                                 7.6 Changing the Node Name/Namespace Namep    G                 ________________________ Notes ________________________A  >                 Except for renaming the dns$server_startup.comA                 file, the net$configure procedure does not delete A                 any configuration information associated with the E                 existing DECdns server configuration. Therefore, when A                 you follow the procedures given in Section 7.6.7, A                 the DECdns server is fully restored to its formerr                 configuration.  >                 The net$configure procedure does not shut down:                 the DECdns server. To shut down the server?                 without having to reboot the system, invoke thea>                 sys$startup:dns$server_shutdown.com procedure.  F                 ______________________________________________________  ,               Namespace Selection Processing  <               Assuming that no other changes are made duringB               configuration dialog processing, namespace selectionF               processing verifies that it can communicate with anotherH               DECdns server containing the same namespace and then callsF               the dns$configure procedure to reconfigure the clerk for               the namespace:  ]               sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.   4               Your default namespace nickname is HP.  X               Your default namespace NSCTS is AA-00-04-00-DE-11-A0-AA-F9-6F-56-DE-8E-00.  0               Namespace Configuration Processing  B               The procedure reruns the name service searchpath NCLI               script. Whenever a DECdns namespace is involved the processwF               renames the node, flushes the cache, updates the address?               towers, and updates the backtranslation softlink:e  S               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to HP:.ASHFLD J               %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entriesM               %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for nodedW               %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for nodel  D               The procedure then displays the configuration summary,H               recalculates the NCL script file checksums, and redisplays$               the main options menu:  I                                    Modifying a Current Configuration 7-27            )         Modifying a Current Configuration:1         7.6 Changing the Node Name/Namespace Namet    .                       Summary of Configuration                 Node Information:  5                       Node Type:              ENDNODE <                       Directory Services Chosen:      DECDNS<                       Primary Directory Service:      DECDNS8                       DECdns Full name:       HP:.ASHFLD3                       DECdns Node Type:       Clerk 4                       Node Synonym:           ASHFLD4                       Phase IV Address:       24.1212                       Phase IV Prefix:        49::F                       Autoconfiguration of Network Addresses:  EnabledI                       Session Control Address Update Interval:         10 1                       Routing ESHello Timer:  600 1                       Routing ES Cache Size:  512n                  .                  .                  .X               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified                  by NET$CONFIGUREU               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration                  completeds  ;                       Configuration Options for Node ASHFLDm  1                       [0]     Exit this proceduree  =                       [1]     Perform an entire configurationu7                       [2]     Change naming information   E         7.6.7 Reverting a DECdns Clerk System Back to a DECdns Servers               System  E               This section describes how to revert back to a previous C               DECdns server configuration after converting a DECdnsh5               server system to a DECdns clerk system.   -               Configuration Dialog Processingc  B               When you previously converted the system to a DECdnsC               clerk system, the net$configure procedure renamed thenD               sys$startup:dns$server_startup.com file to dns$server_G               startup.com-disabled during the conversion. The procedure D               informs you that this was done and asks if you want to:               change the system back into a DECdns server:  .         7-28 Modifying a Current Configuration P         I                                         Modifying a Current Configuration I                                 7.6 Changing the Node Name/Namespace Name     W                    A SYS$STARTUP:DNS$SERVER_STARTUP.COM-DISABLED file has been located.pU                    This indicates that the DECdns server software has been installed,eO                    but this system was previously configured as a DECdns clerk.   R                    Answer YES to the next question if you want to rename this fileT                    to DNS$SERVER_STARTUP.COM and configure the node as a DNS Server.N                    If you take the default, this node will remain a DNS Clerk.  N               * Do you want to change this system into a DECdns server?  [NO]:  I               Answer NO to leave your system configured as a DECdns clerkpF               system. Answer YES to rename the sys$startup:dns$server_B               startup.com-disabled file to sys$startup:dns$server_I               startup.com and reconfigure your system as a DECdns server.   B               If you choose to convert the system back to a DECdnsA               server, the procedure checks for the existence of atE               valid DECdns server configuration (by searching for thenC               sys$manager:dns_files.txt file). If it finds the file E               and the file passes verification testing, the procedureC-               displays the following message:r  R                    The directory pointed to by SYS$MANAGER:DNS_FILES.TXT is valid.Q                    This indicates that the node has been previously configured as #                    a DECdns server.   F               If the procedure does not find the configuration file orH               the file does not pass verification testing, the procedureG               treats this configuration as a new conversion to a DECdnseE               server. See the configuration dialog processing section G               in Section 7.6.5 for information about limitations on theTF               directory service list in this case (see the information4               directly following the bulleted list).  D               Assuming that the configuration file is found and thatF               it passes verification testing, the procedure begins theG               standard directory service/node name dialog by asking foriI               the directory services to use and, based on the answer, the                DECdns full name:   Y               * Enter the directory services to use on the system  [LOCAL] : decdns,localoW               * Enter the full name for directory service DECDNS           : hp:.ashfld   G               Because you have specified a DECdns name on a system thatSF               already has a DECdns server configuration, the procedureF               checks the server's clearinghouses to make sure that youG               are specifying a namespace already served by this system:   I                                    Modifying a Current Configuration 7-29r o  p      )         Modifying a Current Configurationo1         7.6 Changing the Node Name/Namespace Nameg    P                       NET$CONFIGURE is searching for pre-existing clearinghouses)                       on this DNS Server.u  .                       Clearinghouse: HP:.HP_CH  B               Note that this check requires that the net$configureG               procedure start the DECdns server using the newly renamed-I               sys$startup:dns$server_startup.com file. If you are running G               net$configure on the console and you have events enabled,oH               you should see one or more Clearinghouse Enabled events asF               the DECdns server enables the existing clearinghouses on               the server.   F               The net$configure procedure does not support creation ofF               more than one namespace on a system. If it cannot find aF               clearinghouse for the namespace you entered, it displays$               the following message:  T                       There is no clearinghouse on this DNS Server for the namespaceZ                       you specified in your DECdns fullname.  To proceed with this rename,T                       you may now provide a different DECdns fullname -- one that is5                       in a namespace displayed above.   N                       If you wish to use a namespace or clearinghouse name notR                       previously known to this DNS Server, then this rename cannotO                       proceed until you have manually ensured that the existingo5                       clearinghouse has been deleted.u  K               * Do you want to provide a different DECdns fullname?  [YES]:.  D               If you answer YES, the procedure returns to the DECdnsE               fullname prompt and, after you enter a DECdns full namerI               using the proper namespace, configuration dialog processingc               continues:  Q               * Enter the full name for directory service LOCAL [LOCAL:.ASHFLD] :uL               * What is the synonym name for this node?           [ASHFLD] :L               * Naming cache timeout value?                  [30-00:00:00] :L               * Session Control Address Update Interval ?             [10] :L               * Naming cache checkpoint interval?               [08:00:00] :  D               If you answer NO, the procedure displays the following6               message and aborts the rename operation:    .         7-30 Modifying a Current Configuration t         I                                         Modifying a Current ConfigurationPI                                 7.6 Changing the Node Name/Namespace Name]    Z                       Please refer to Section 9.6 of DECnet-Plus DECdns Management manual,R                       for instructions on Deleting a Clearinghouse before invokingD                       NET$CONFIGURE again to rename this DNS Server.  G               %NET$CONFIGURE-I-LASTTRANSABORT, last transaction aborted   &         Namespace Selection Processing  D               The procedure calls dns$configure.com twice: first, toA               ensure that the system is configured with the LocaleE               namespace as primary, then to configure the system withr.               the DECdns namespace as primary:  ]               sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.S  7               Your default namespace nickname is LOCAL.   X               Your default namespace NSCTS is 08-00-2B-0D-C0-9D-5F-FA-A9-88-43-46-95-00.  ]               sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.D  4               Your default namespace nickname is HP.  X               Your default namespace NSCTS is 00-00-F8-25-5A-72-D1-9D-2D-09-04-3C-A3-00.  0               Namespace Configuration Processing  G               Based on the answers provided during configuration dialogNF               processing, the configuration procedure executes the newC               name service searchpath NCL script, renames the node, A               modifies the Local namespace entry, flushes the CDI,G               cache, updates the node's address towers, and updates theL4               backtranslation softlink for the node:  S               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to HP:.ASHFLDa  0               Directory Service: Local name file  /               Modifying the node: LOCAL:.ASHFLD '               Modifying the node towerso  J               %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entriesU               %NET$CONFIGURE-I-CHECKPOINTWAIT, waiting for CDI to write the node nameo%                 to the CDI cache fileoP               %NET$CONFIGURE-I-CHECKPOINTDONE, the node name has been written to/                 SYS$SYSTEM:DECNET$CDI_CACHE.DAT M               %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node W               %NET$CONFIGURE-E-BCKTRNUPDATED, updated backtranslation softlink for nodep  I                                    Modifying a Current Configuration 7-31f h  y      )         Modifying a Current Configuratione1         7.6 Changing the Node Name/Namespace Name     D               The procedure then displays the configuration summary,H               recalculates the NCL script file checksums, and redisplays$               the main options menu:  .                       Summary of Configuration                 Node Information:  5                       Node Type:              ENDNODE_<                       Directory Services Chosen:      DECDNS<                       Primary Directory Service:      DECDNS8                       DECdns Full name:       HP:.ASHFLD4                       DECdns Node Type:       Server4                       Node Synonym:           ASHFLD4                       Phase IV Address:       24.1212                       Phase IV Prefix:        49::F                       Autoconfiguration of Network Addresses:  EnabledI                       Session Control Address Update Interval:         10 1                       Routing ESHello Timer:  600 1                       Routing ES Cache Size:  512                   .                  .                  .X               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified                  by NET$CONFIGUREU               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration.                 completed   ;                       Configuration Options for Node ASHFLDA  1                       [0]     Exit this procedureh  =                       [1]     Perform an entire configuration 7                       [2]     Change naming information   H         7.6.8 Using the DECdns Namespace as Secondary on a DECdns Server               System  H               This section describes how to configure a DECdns server toG               run with the primary directory service set to a namespacen                other than DECdns.  -               Configuration Dialog Processingf      .         7-32 Modifying a Current Configuration r  o      I                                         Modifying a Current ConfigurationuI                                 7.6 Changing the Node Name/Namespace Nameo    I               The following example shows the first portion of the dialognF               used to change the node from using DECdns as the primaryC               directory service to using the Local namespace as thenG               primary directory service (DOMAIN as primary is virtuallyI               identical):h  N               * Which configuration option to perform?                 [1] : 2`               * Enter the directory services to use on the system  [DECDNS,LOCAL] : local,decdns  C               At this point, the configuration procedure displays atI               message indicating that HP strongly recommends using DECdns A               as the primary directory service on DECdns servers:   L                    Hewlett-Packard recommends that you specify DECdns as theM                    primary naming service on a DECdns server, but the list of M                    directory services you entered does not start with DECdns.p  Q                    Answer NO to the following question if you want to ignore thisnR                    recommendation and proceed using the list of directory services$                    you just entered.  Q                    If you take the default, you will be prompted to re-enter yourHQ                    list of directory services so that you may enter DECdns as thef.                    first service in that list.  \               Do you want DECdns as the primary naming service on this DECdns server? [YES]:  H               If you answer YES, the procedure again prompts you for theF               directory services list. If you answer NO, your original9               order is accepted and the dialog continues:n  Q               * Enter the full name for directory service LOCAL [LOCAL:.ASHFLD] :uN               * Enter the full name for directory service DECDNS [HP:.ASHFLD]:  G               Because you have specified a DECdns name on a system thatyE               is already configured as a DECdns server, the procedure F               checks the server's clearinghouses to make sure that youG               are specifying a namespace already served by this system:i  P                       NET$CONFIGURE is searching for pre-existing clearinghouses)                       on this DNS Server.p  .                       Clearinghouse: HP:.HP_CH  F               The net$configure procedure does not support creation ofF               more than one namespace on a system. If it cannot find aF               clearinghouse for the namespace you entered, it displays$               the following message:  I                                    Modifying a Current Configuration 7-33            )         Modifying a Current Configurationt1         7.6 Changing the Node Name/Namespace Namea    T                       There is no clearinghouse on this DNS Server for the namespaceZ                       you specified in your DECdns fullname.  To proceed with this rename,T                       you may now provide a different DECdns fullname -- one that is5                       in a namespace displayed above.   N                       If you wish to use a namespace or clearinghouse name notR                       previously known to this DNS Server, then this rename cannotO                       proceed until you have manually ensured that the existing 5                       clearinghouse has been deleted.   K               * Do you want to provide a different DECdns fullname?  [YES]:.  D               If you answer YES, the procedure returns to the DECdnsD               fullname prompt and, after entering a DECdns full nameI               using the proper namespace, configuration dialog processing                continues:  N               * Enter the full name for directory service DECDNS [HP:.ASHFLD]:L               * What is the synonym name for this node?           [ASHFLD] :L               * Naming cache timeout value?                  [30-00:00:00] :L               * Session Control Address Update Interval ?             [10] :L               * Naming cache checkpoint interval?               [08:00:00] :  D               If you answer NO, the procedure displays the following6               message and aborts the rename operation:  Z                       Please refer to Section 9.6 of DECnet-Plus DECdns Management manual,R                       for instructions on Deleting a Clearinghouse before invokingD                       NET$CONFIGURE again to rename this DNS Server.  G               %NET$CONFIGURE-I-LASTTRANSABORT, last transaction abortedt  ,               Namespace Selection Processing  E               If you choose to configure the DECdns name service as aTE               secondary service, the configuration procedure modifies G               the DECdns namespace on the system to allow access by theoI               renamed server. It does this by adding access for the LOCAL F               or DOMAIN namespace based on which namespace is primary.;               The procedure displays the following message:C  P                       NET$CONFIGURE is searching for pre-existing clearinghousesK                       on this DNS Server in order to set up access control.     .         7-34 Modifying a Current Configuration g         I                                         Modifying a Current Configuration I                                 7.6 Changing the Node Name/Namespace Name     I               The procedure then calls the dns$configure.com procedure toIG               configure the DECdns clerk for the new primary namespace:e  ]               sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.   7               Your default namespace nickname is LOCAL.N  W               Your default namespace NSCTS is 08-00-2B-0D-C0-9D-5F-FA-A9-88-43-46-95-00a  I               If the net$configure procedure is not successful in settinghC               the new access information, it displays the following 1               message and aborts the transaction:t  P                       ERROR:  NET$CONFIGURE did not succeed in setting up accessQ                       control for pre-existing clearinghouses on this DNS Server.t  G               %NET$CONFIGURE-I-LASTTRANSABORT, last transaction abortedu  ;                       Configuration Options for Node ASHFLDa  1                       [0]     Exit this proceduree  =                       [1]     Perform an entire configuration 7                       [2]     Change naming information                   .                  .                  .  0               Namespace Configuration Processing  G               Based on the answers provided during configuration dialoguF               processing, the configuration procedure executes the newF               name searchpath NCL script, modifies the Local namespace=               entry, renames the node, and flushes the cache:e  0               Directory Service: Local name file  /               Modifying the node: LOCAL:.ASHFLDe'               Modifying the node towers   V               %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.ASHFLDJ               %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries  D               The procedure then displays the configuration summary,H               recalculates the NCL script file checksums, and redisplays$               the main options menu:  I                                    Modifying a Current Configuration 7-35t           )         Modifying a Current Configurationr1         7.6 Changing the Node Name/Namespace Names    .                       Summary of Configuration                   Node Information:  B                       Directory Services Chosen:      LOCAL,DECDNS;                       Primary Directory Service:      LOCAL @                       DECdns Full name:               HP:.ASHFLDC                       Local Full name:                LOCAL:.ASHFLDs<                       Node Synonym:                   ASHFLD<                       Phase IV Address:               24.900:                       Phase IV Prefix:                49::<                       DECdns Node Type:               ServerH                       Session Control Address Update Interval:        10=                       Routing Node Type:              ENDNODEEE                       Autoconfiguration of Network Addresses: Enabled 1                       Routing ESHello Timer:  600 1                       Routing ES Cache Size:  512l                  .                  .                  .X               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified                  by NET$CONFIGUREU               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configurationa                 completed   ;                       Configuration Options for Node ASHFLDM  1                       [0]     Exit this procedure   =                       [1]     Perform an entire configuration 7                       [2]     Change naming informationn                  .                  .                  .  A         7.6.9 Configuring a DECdns Server System into an Existingt               Namespace_  E               To configure additional DECdns servers into an existinggG               namespace, you must use the DECdns configuration program,oF               sys$system:dns$configure.exe. Be sure to refer to the HPI               DECnet-Plus for OpenVMS DECdns Management manual for DECdns E               access control information and for complete information I               about using the DECdns configuration program to configure ar7               DECdns server into an existing namespace.h  .         7-36 Modifying a Current Configuration n  l      I                                         Modifying a Current ConfigurationpI                                 7.6 Changing the Node Name/Namespace Namen    H         7.6.9.1 Configuring a DECdns Server in a DNS Version 1 Namespace  C               If you are already using a DNS Version 1 namespace (atF               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-hH               Plus (see Section B.3). For complete information on how toG               prepare a DNS Version 1 namespace for use by DECnet-Plus,eG               refer to the HP DECnet-Plus for OpenVMS DECdns Managementn;               manual for DECdns access control information.o  F                 ________________________ Note ________________________  F                 The DECdns configuration program allows you to convertE                 your DNS Version 1 clearinghouses to DECdns Version 2cE                 format. By doing so, you get the improved performancevB                 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 DECdnsD                 Version 2 format, HP strongly recommends that you doD                 not configure DECnet-Plus for OpenVMS on any of yourB                 DNS Version 1 server nodes until you have preparedD                 your DNS Version 1 namespace for use by DECnet-Plus.  F                 ______________________________________________________           7.7 Configuring DevicesN  I               To configure devices, select option 3 from the main optionss               menu:   I               * Which configuration option to perform?            [1] : 3   I               The dialog for a configuration modification is identical toeG               the initial dialog. See Section 6.6 for the entire devicecG               dialog. As with the initial configuration dialog, if X.25fI               or WANDD components are found and have not been configured, A               the procedure gives you a chance to configure them.e  F               Once you have completed the device dialog, the procedureA               displays a summary of the configuration and asks ifaC               you want to configure the new NCL scripts. Proceed tot0               Section 7.17 for more information.  I                                    Modifying a Current Configuration 7-37s e  o      )         Modifying a Current Configuration 2         7.8 Configuring the NSP and OSI Transports    2         7.8 Configuring the NSP and OSI Transports  H               To configure the NSP transport, the OSI transport, or bothE               transports, select option 4 from the main options menu:   J               * Which configuration option to perform?             [1] : 4                 BASICl  H               The BASIC option begins by asking if you want to configure                the NSP transport:  L               * Configure the NSP Transport?                         [YES] :  C               If you answer YES, the procedure displays the DEFAULT F               transport settings for the NSP transport and asks if youD               want to replace the existing transport values with the               default values:   P                       Since you are using the BASIC option, if you answer YES toO                       the next question, the NSP transport will be reconfiguredo9                       using the default values which are:n  E                       Maximum number of logical links:            200sE                       Maximum Transmit and Receive Window:         20 E                       Maximum Receive Buffers:                   4000dE                       Flow Control Policy:       Segment Flow Controlo  I                       If you intend to customize the transports, then uset2                       the ADVANCED option instead.  P               * Do you want to replace the existing NSP transport script? [NO] :  G               If you answer YES, the NSP transport is reconfigured withnH               the default values shown in the display. If you answer NO,6               the NSP configuration is left unchanged.  D               Next, the procedure asks the same question for the OSI               transport:  L               * Configure the OSI Transport or run over TCP/IP?      [YES] :  C               If you answer YES, the procedure displays the DEFAULTeF               transport settings for the OSI transport and asks if youD               want to replace the existing transport values with the               default values:   .         7-38 Modifying a Current Configuration t         I                                         Modifying a Current ConfigurationoI                                7.8 Configuring the NSP and OSI Transportse    P                       Since you are using the BASIC option, if you answer YES toO                       the next question, the OSI transport will be reconfigured 9                       using the default values which are:a  E                       Maximum number of logical links:            200iE                       Maximum Transmit and Receive Window:         20fE                       Maximum Receive Buffers:                   4000 E                       OSI applications over TCP/IP:           EnabledeE                       DECnet applications over TCP/IP:        Enabledt  I                       If you intend to customize the transports, then use 2                       the ADVANCED option instead.  P               * Do you want to replace the existing OSI transport script? [NO] :  G               If you answer YES, the OSI transport is reconfigured with H               the default values shown in the display. If you answer NO,6               the OSI configuration is left unchanged.  I               Once you have completed the transport dialog, the procedure A               displays a summary of the configuration and asks if C               you want to configure the new NCL scripts. Proceed to 0               Section 7.17 for more information.                 ADVANCED  A               The ADVANCED option begins by asking if you want to *               configure the NSP transport:  L               * Configure the NSP Transport?                         [YES] :  C               If you answer YES, the procedure displays the CURRENTnF               transport settings for the NSP transport and asks if you@               want to reconfigure the existing transport values:  D                       Answer YES to the next question if you wish toE                       change the current NSP transport configuration:n  E                       Maximum number of logical links:            200 E                       Maximum Transmit and Receive Window:         20,E                       Maximum Receive Buffers:                   4000ME                       Flow Control Policy:       Segment Flow Control   P               * Do you want to replace the existing NSP transport script? [NO] :  H               If you answer YES, you are prompted for the new values. IfE               you answer NO, the NSP configuration is left unchanged.   I                                    Modifying a Current Configuration 7-39_ _  _      )         Modifying a Current Configurations2         7.8 Configuring the NSP and OSI Transports    D               Next, the procedure asks the same question for the OSI               transport:  L               * Configure the OSI Transport or run over TCP/IP?      [YES] :  C               If you answer YES, the procedure displays the CURRENT F               transport settings for the OSI transport and asks if you@               want to reconfigure the existing transport values:  D                       Answer YES to the next question if you wish toE                       change the current NSP transport configuration:r  E                       Maximum number of logical links:            200eE                       Maximum Transmit and Receive Window:         20eE                       Maximum Receive Buffers:                   4000 E                       OSI applications over TCP/IP:           EnabledHE                       DECnet applications over TCP/IP:        Enabled   P               * Do you want to replace the existing OSI transport script? [NO] :  H               If you answer YES, you are prompted for the new values. IfE               you answer NO, the OSI configuration is left unchanged.   I               With the exception of the additional dialog shown here, the G               questions asked during a reconfiguration are identical to H               the initial configuration questions, including the sectionF               used to create additional OSI templates. If you elect toD               reconfigure either or both transports, see Section 6.7F               for the prompts used in this section and for informationI               about how to respond to the prompts. Note that the ADVANCEDaD               option of the reconfiguration dialog omits the opening<               message shown at the beginning of Section 6.7.  G                 _______________________ Warning _______________________   @                 If you select this option and then indicate thatA                 you don't want to configure either transport, thebB                 procedure issues a warning and asks you to confirm                 your decision:  E                 %NET$CONFIGURE-W-NOTRANSPORTS, no transports selected P                 * Are you sure?                                         [NO] : y  >                 If you answer YES, all transport configuration@                 information is lost. The configuration procedure?                 creates empty NCL startup script files for both A                 transports. To create a usable configuration, you   .         7-40 Modifying a Current Configuration e  n      I                                         Modifying a Current Configuration I                                7.8 Configuring the NSP and OSI Transports     D                 must run the configuration procedure again to create(                 valid transport scripts.  F                 ______________________________________________________  I               Once you have completed the transport dialog, the proceduresA               displays a summary of the configuration and asks ifoC               you want to configure the new NCL scripts. Proceed to 0               Section 7.17 for more information.  B         7.9 Configuring the Time Zone Differential Factor (DECdts)  H               To configure DECdts, select option 5 from the main options               menu:   I               * Which configuration option to perform?            [1] : 5            7.9.1 DECdts OverviewE  @               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. Time zones are still determined by theirnG               relationship to the prime meridian in Greenwich, England.OI               The local time in each time zone or locale is determined by H               its offset, or differential, from the Greenwich time zone.E               This value is commonly expressed as a time differential E               factor (TDF) of a positive or negative number of hours._  F               When you initially configure an OpenVMS system, you mustH               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 andlG               the applicable TDF, so that DECdts can calculate UTC fromsI               the system (local) time during the initial configuration ofeG               the DECdts software. The TZR also contains information oneH               any seasonal adjustments to the TDF that normally apply in%               the selected time zone.t  I               If you want to select the commonly accepted TZR for a given F               area and system, you can use the net$configure procedureF               menus to select the geographical location of the system.B               Based on your selection, the net$configure procedureB               automatically sets the TZR. After you configure yourG               system, it displays the local time even though the DECdtsgF               software uses UTC in the background. Because the default  I                                    Modifying a Current Configuration 7-41t a  t      )         Modifying a Current Configuration;B         7.9 Configuring the Time Zone Differential Factor (DECdts)    D               value of the DECdts management attribute Automatic TDFF               Change is set to TRUE, DECdts also changes the displayedH               local time automatically if there is a seasonal adjustment"               to the system's TDF.  I               Additionally, when you reconfigure the DECdts software, you F               are given the option of setting the system's time to UTC               time.   D               The following resources provide additional information?               about time management and use on OpenVMS systems:   I               o  HP DECnet-Plus for OpenVMS DECdts Management - discusses B                  what DECdts is and how it works, managing DECdts,I                  troubleshooting DECdts, and provides a command referenceN8                  for all commands used to manage DECdts.  D               o  HP OpenVMS System Manager's Utility Guide ("SettingF                  System Time" chapter) - discusses how time is managedG                  on OpenVMS systems that do not use DECdts. Much of the G                  information about how to configure DECdts is common to E                  DECdts and OpenVMS and is documented in this manual. I                  Specifically, this chapter discusses using the utc$time_sG                  setup command procedure to set your system's time zoneoG                  information. This procedure is used by the DECdts timeg.                  zone configuration procedure.  E               o  Compaq C Run-Time Library Utilities Reference ManualII                  (the "Creating Time Zone Conversion Information" sectioneF                  in the "Overview" chapter) - discusses using the ZoneE                  Information Compiler (ZIC) to create the binary timen;                  zone files required by OpenVMS and DECdts.   C               o  HP C Run-Time Library Reference Manual for OpenVMSoA                  Systems ("Date/Time Functions" chapter and tzsetpC                  function description in the "Reference Section") -cF                  describes how C programs can make use of the date andD                  time functions in the C run-time library. The tzsetD                  function description is useful in understanding theC                  syntax used in the SYS$TIMEZONE_RULE logical name.s          .         7-42 Modifying a Current Configuration c  o      I                                         Modifying a Current ConfigurationiI                7.9 Configuring the Time Zone Differential Factor (DECdts)e    7         7.9.2 Selecting the DECdts Configuration Option   D               After you invoke option 5, the net$configure procedure@               invokes the dtss$config procedure. The dtss$configE               procedure begins by displaying messages indicating that I               it is deassigning the four current SYS$TIMEZONE_xxx logical H               names and shutting down DECdts (the "Node 0 DTSS" messages@               come from the NCL commands used by the procedure):  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:00Iinfs                  Node 0 DTSS3                at 1995-08-04-18:36:23.960+00:00Iinf   F               The dtss$config procedure then invokes the dtss$install_E               timezone_rule procedure. This procedure is also invoked F               during the initial system configuration. However, duringG               initial configuration the procedure usually gets the timeoE               zone rule from the SYS$LOCALTIME system logical name so G               no menu is displayed. In a reconfiguration, the procedure G               is called with a parameter that forces it to override theCF               SYS$LOCALTIME system logical name and display an options               menu:   '                       Timezone Options:r  9                       [0]     Exit Timezone Configurationu  ;                       [1]     Choose a timezone using menusrB                       [2]     Use Universal Coordinated Time (UTC);                       [3]     Define 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.h  F                 ______________________________________________________  I                                    Modifying a Current Configuration 7-43u v  e      )         Modifying a Current Configuration B         7.9 Configuring the Time Zone Differential Factor (DECdts)    .         7.9.3 Choosing a Time Zone Using Menus  G               Option 1 of the Timezone Options menu invokes the OpenVMSoI               sys$manager:utc$time_setup procedure to allow you to choosesG               the time zone rule for the system by using a hierarchy ofSG               geographically-based menus. DECdts uses the time zone you E               select to determine the time zone rule it should use to F               automatically convert UTC to the local time whenever the                time is displayed.  G               To specify a time zone rule by choosing your geographicalfE               region, select option 1 from the timezone options menu:   F               * Enter an option number                           [1] :  C               The procedure displays a menu of continental regions:   /                 Configuring the Local Time Zone   \               TIME ZONE SPECIFICATION -- MAIN Time Zone Menu            "*" indicates a menu                   0* GMTW                 1* AFRICA          17) EST             33) IRAN            49) PORTUGAL-R                 2* AMERICA         18) EST5EDT         34) ISRAEL          50) PRCV                 3* ANTARCTICA      19* ETC             35) JAMAICA         51) PST8PDTR                 4* ARCTIC          20* EUROPE          36) JAPAN           52) ROCR                 5* ASIA            21) FACTORY         37) KWAJALEIN       53) ROKX                 6* ATLANTIC        22) GB-EIRE         38) LIBYA           54) SINGAPOREV                 7* AUSTRALIA       23) GB              39) MET             55* SYSTEMVU                 8* BRAZIL          24) GMT-0           40* MEXICO          56) TURKEY R                 9* CANADA          25) GMT             41* MIDEAST         57) UCTX                10) CET             26) GMT0            42) MST             58) UNIVERSALQ                11* CHILE           27) GMTPLUS0        43) MST7MDT         59* USrR                12) CST6CDT         28) GREENWICH       44) NAVAJO          60) UTCS                13) CUBA            29) HONGKONG        45) NZ-CHAT         61) W-SUnR                14) EET             30) HST             46) NZ              62) WETS                15) EGYPT           31) ICELAND         47* PACIFIC         63) ZULU A                16) EIRE            32* INDIAN          48) POLAND   R               Press "Return" to redisplay, enter "=" to search or "?" for help, orT               Select the number above that best represents the desired time zone: 59  \               US Time Zone Menu                                         "*" indicates a menu    .         7-44 Modifying a Current Configuration           I                                         Modifying a Current ConfigurationeI                7.9 Configuring the Time Zone Differential Factor (DECdts)_    0                 0* RETURN TO MAIN TIME ZONE MENUT                 1) ALASKA           5) EAST-INDIANA     9) MICHIGAN        13) SAMOAC                 2) ALEUTIAN         6) EASTERN         10) MOUNTAINsF                 3) ARIZONA          7) HAWAII          11) PACIFIC-NEWB                 4) CENTRAL          8) INDIANA-STARKE  12) PACIFIC  R               Press "Return" to redisplay, enter "=" to search or "?" for help, orS               Select the number above that best represents the desired time zone: 6   :               You selected US / EASTERN as your time zone.7               Is this correct? (Yes/No) [YES]: <Return>e  A               Enter the option (and, if necessary, the suboption)eF               corresponding to the region where the system resides. InF               the example, the system is in the eastern United States.F               After you make a selection, the following actions occur:  D               1. The utc$time_setup procedure sets the SYS$LOCALTIME?                  system logical name and returns control to the 6                  dtss$install_timezone_rule procedure.  D               2. Using the value in the SYS$LOCALTIME system logicalG                  name, the dtss$install_timezone_rule procedure creates C                  the dtss$utc_startup.com procedure. This procedureIH                  defines the four SYS$TIMEZONE_xxx system logical names.G                  The procedure is invoked each time the system reboots. I                  The dtss$install_timezone_rule procedure returns controlo.                  to the dtss$config procedure.  D               3. The dtss$config procedure invokes the newly-createdB                  dtss$utc_startup.com procedure to define the fourE                  SYS$TIMEZONE_xxx system logical names on the running                   system.  9               4. The procedure then sets the local clock.   H               5. Next, it executes the sys$startup:dtss$startup.com file!                  to start DECdts.a  H               6. After the DTSS entity is created, it sets the automaticE                  tdf change characteristic (after first disabling thei                  DTSS entity).  1               7. It then deletes the DTSS entity.y  -               8. Finally, it restarts DECdts.h  I                                    Modifying a Current Configuration 7-45o i  P      )         Modifying a Current ConfigurationaB         7.9 Configuring the Time Zone Differential Factor (DECdts)    <               These actions result in the following display:  B               DTSS$CONFIG-I-LOGS Defining system timezone logicalsF               DTSS-I-SETTDF DTSS$SERVICE set new timezone differential6               DTSS$CONFIG-I-SETLCL Setting Local ClockK               %RUN-S-PROC_ID, identification of created process is 00000059I                 Node 0 DTSSt2               at 1995-02-25-08:17:29.520-05:00Iinf                 Node 0 DTSS 2               at 1995-02-25-08:17:30.790-05:00Iinf                 Node 0 DTSSo4               at 1995-02-25-08:17:39.978-05:00I0.327                 Node 0 DTSS 4               at 1995-02-25-08:17:45.868-05:00I0.328                 Characteristicso  ,                  Automatic TDF Change = True                 Node 0 DTSSa4               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 0000006Bu                 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  F                 ________________________ Note ________________________  @                 If you are running on the console, several OPCOMF                 messages are displayed during this sequence displaying?                 entity status changes and clock synchronizationf                 events.c  F                 ______________________________________________________  F               This completes changes to the DECdts configuration usingG               option 1. The net$configure procedure returns to the mainu               options menu.   .         7-46 Modifying a Current Configuration e  a      I                                         Modifying a Current Configuration I                7.9 Configuring the Time Zone Differential Factor (DECdts)e    4         7.9.4 Using Universal Coordinated Time (UTC)  ?               If your system is located in the GMT time zone orP@               Antarctica, or if you do not want to make seasonalE               adjustments to the TDF, you may want to use UTC as your0E               system's local time. You can also configure all networkoH               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).a  F               To use UTC as your system's local time, select option 2:  I               * Enter an option number                            [1] : 2   A               The subsequent actions are identical to those shownoD               following the selection of a time zone in the previous               section.  F               This completes changes to the DECdts configuration usingG               option 2. The net$configure procedure returns to the mainm               options menu.r  .         7.9.5 Defining Your Own Time Zone Rule  H               The net$configure procedure no longer allows you to createF               a customized time zone rule. To create a customized timeH               zone rule, refer to the additional documentation resourcesF               referenced in Section 7.9.2. In particular, the Compaq CI               Run-Time Library Utilities Reference Manual discusses using9F               the Zone Information Compiler (ZIC) to create new binaryI               time zone files. Once you have created a new file and moved F               it to the appropriate place in the time zones directory,G               you can select the time zone in the same manner you wouldr)               select any other time zone.V  D               If you select option 3, the procedure displays a shortE               description of the process used to create a custom time                zone rule.  -         7.10 Configuring the Event Dispatcher   I               To configure the Event Dispatcher, select option 6 from the                 main options menu:  J               * Which configuration option to perform?             [0] : 6  I                                    Modifying a Current Configuration 7-47z o  o      )         Modifying a Current Configuration_-         7.10 Configuring the Event Dispatcher     D               The procedure asks if you want to replace the existing2               event dispatcher NCL startup script:  P               %NETCONFIGURE-I-EVDFND, Event dispatcher NCL script already existsH               * Replace Event Dispatcher NCL script file?         [NO] :  F               If you want to create a new Event Dispatcher NCL startupI               script file, answer YES. If you want to keep the previously H               generated Event Dispatcher NCL startup script file, answer               NO.                  BASIC:  D               If you answered YES, the BASIC option informs you thatC               the procedure automatically creates the default Events/               Dispatcher configuration for you:r  [               %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configurationo                 ADVANCED  D               If you answered YES, the ADVANCED option uses the same@               prompts used during the initial configuration. SeeF               Section 6.9 for the prompts used in this section and for>               information about how to respond to the prompts.                  BASIC and ADVANCED  F               Once you have completed the Event Dispatcher dialog, theC               procedure displays a summary of the configuration and H               asks if you want to configure the new NCL startup scripts.;               Proceed to Section 7.17 for more information.b  1         7.11 Configuring the Application Databaseh  B               When you configure the application database, you canE               either delete an existing application (including any ofeC               the default applications installed during the initialeC               configuration), or you can include a new application.   I               To configure the application database, select option 7 from $               the main options menu:  N               * Which configuration option to perform?                 [1] : 7  I               The procedure begins by asking if you want to add or deletef               an application:   L               * Do you want to ADD or DELETE an Application?         [ADD] :  .         7-48 Modifying a Current Configuration O  o      I                                         Modifying a Current Configuration I                                 7.11 Configuring the Application Database     H               Answer ADD to create a new application entity on the localC               node, allocate resources for it, and open the service G               interface. Answer DELETE to delete an existing entity and:+               reclaim associated resources.g  C               Next, the procedure asks for the applications's name:n  S               * What is the name of the Application?                        : NOTESR  <               If you are deleting an application, proceed toG               Section 7.11.1. If you are adding an application, proceed                 to Section 7.11.2.  B               Once you have completed the applications dialog, theI               procedure asks if you want to configure the new NCL startupoD               scripts. Proceed to Section 7.18 for more information.  F                 ________________________ Note ________________________  ?                 Each invocation of option 7 adds or deletes oneeB                 application. If you wish to add or delete multiple4                 applications, invoke option 7 again.  F                 ______________________________________________________  &         7.11.1 Deleting an Application  H               If you are deleting an application, the procedure displays#               the following prompt:o  L               * Are you sure you want to DELETE this application?      [NO]:  I               Answer YES if you want to delete the application. Answer NOuH               if you want to keep the application. If you answer NO, theI               procedure informs you it has canceled the delete operation:C  C               %NET$CONFIGURE-I-DELETECAN, delete operation canceled   $         7.11.2 Adding an Application  A               If you are adding an application, the configurationa@               procedure asks a series of questions to define the               application:  H               1. To add an application, the procedure must create one orG                  more addresses (also known as end-user specifications)hF                  for the application. Incoming connections provide theG                  application's address in the destination name field ofeF                  the connection request. Table 7-2 lists the supported  I                                    Modifying a Current Configuration 7-49  w         )         Modifying a Current Configuration 1         7.11 Configuring the Application Database     E                  types of end-user specifications (referred to in the .                  dialog as destination types).  I               Table_7-2_Application_End-User_Specification_Types_________l  I               Type________Description____________________________________f  I               NAME        The local name of the application (for example, H                           NOTES). The name must be 1 to 16 characters in!                           length.o  H               NUMBER      The unique number assigned to the application.E                           Application numbers must be in the range of)C                           1 to 255. Well-known applications such as4D                           MAIL and FAL have application numbers thatD                           are recognized throughout the network. SeeF                           Table 7-3 for application number preassignedI                           or reserved by HP. User-defined images can have H                           unique object numbers; numbers between 128 andH                           255 are reserved for this purpose. In Phase IVH                           terms, the application number was known as the6                           application's object number.  :               FULLNAME    The DECdns full name assigned to7                           the application (for example, H                           IAF:.SALES.BOSTON.APP3). The full name must beI                           1 to 512 characters in length and in the format I               ____________NamespaceNickname:[.DirectoryPath].NodeObject._m  I                  Table 7-3 lists the application numbers used or reserved                   by HP.t  I               Table_7-3_Application_Numbers______________________________n  I               Number____Mnemonic_Description_____________________________   -               0         Task     User programT  4               1-16               Reserved for HP use  I               17        FAL      File access listener for remote file andh.                                  record access  I                                                  (continued on next page)o  .         7-50 Modifying a Current Configuration           I                                         Modifying a Current Configuration I                                 7.11 Configuring the Application Database.    I               Table_7-3_(Cont.)_Application_Numbers______________________   I               Number____Mnemonic_Description_____________________________d  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)g  4               21-22              Reserved for HP use  E               23        REMACP   Network terminal handler (host side)t  I               24                 Network terminal handler (terminal side)o  0               25        MIRROR   Loopback mirror  /               26        EVL      Event receiveri  5               27        MAIL     OpenVMS Mail utility   4               28                 Reserved for HP use  I               29        PHONE    OpenVMS Phone utility and RSX-11M/M-PLUSe.                                  Phone utility  4               30                 Reserved for HP use  ,               31                 X.25 Server  4               32-35              Reserved for HP use  ,               36                 X.25 Client  4               37-41              Reserved for HP use  9               42        CTERM    Network terminal handlerw  4               43                 Reserved for HP use  G               44        DNSCLERK Used by DNS Server to receive connects 0                                  from DNS clerks  G               45        DNSCLERK Used by DNS Server to receive connectsi1                                  from DNS serversd  4               46-62              Reserved for HP use  <               63        DTR      DECnet Test Receiver object  4               64-85              Reserved for HP use  F               86                 Used by DNS$ADVER for remote-to-local0                                  cache transfers  4               87-127             Reserved for HP use  I                                                  (continued on next page)i  I                                    Modifying a Current Configuration 7-51r l  b      )         Modifying a Current Configuration 1         7.11 Configuring the Application Databaseu    I               Table_7-3_(Cont.)_Application_Numbers______________________   I               Number____Mnemonic_Description_____________________________   I               128-255____________Reserved_for_customer_use_______________d  I                  The procedure begins by asking you for the application's "                  destination type:  O                  * What is the destination type for 'notes'?           [NAME] :r  A                  Select NAME, NUMBER, FULLNAME, or UIC. The NOTESeD                  application is a well-known application with an HP-F                  reserved application number. Therefore, enter NUMBER.  I                  Next, based on the value you entered for the destination_H                  type, the procedure asks you for the required value for'                  that destination type:a  Z                  * What is the destination destination-type for 'notes'?                 :  E                  Enter the appropriate value based on the destinationo"                  type you entered.  I                  You have the option of specifying multiple addresses for I                  an application. The procedure asks if you want to assignu5                  another address to this application:e  O                  * Do you want to specify another application address?    [NO]:t  A                  If the application has more than one application @                  address, enter YES and the previous prompts are                  repeated.  G               2. The client name specifies the name of the local entityoD                  that you want activated upon receipt of the connectF                  request containing a destination name matching one of@                  the destination values you specified in Step 1.  O                  * What is the name of the Client for 'notes'?                :s  F               3. The image name specifies the file name of the programC                  you want invoked upon receipt of a Connect RequestaB                  containing a destination name matching one of the<                  destination values you specified in Step 1.  _                  * What is the Image name for 'notes'?             :sys$system:notes$server.exeo  G                  Specify the full file name of the application's image.T  .         7-52 Modifying a Current Configuration    s      I                                         Modifying a Current Configuration I                                 7.11 Configuring the Application Database     G               4. The answer to the following question specifies whether B                  or not the application should respond to incomingE                  connect requests directed to the alias node address. G                  FALSE indicates that the application should not accept I                  incoming connect requests that have been directed to theSH                  alias node address. TRUE indicates that the application-                  should accept such requests.s  O                  * Incoming Alias for 'notes' enabled?                 [TRUE] :n  '                  Specify TRUE or FALSE.r  G               5. The answer to the following question specifies whetherrC                  or not incoming proxy requests for the application.A                  are honored. FALSE indicates that incoming proxy I                  requests for the application are ignored. TRUE indicatesrE                  that incoming proxy requests are allowed. This valueo<                  overrides the global Session Control value.  O                  * Incoming Proxy for 'notes' enabled?                 [TRUE] :   '                  Specify TRUE or FALSE.e  G               6. The answer to the following question specifies whetherlI                  or not the application should use the alias node addressnG                  in its outgoing connect requests. FALSE indicates that I                  the application should not use the alias node address inuG                  its outgoing connect requests. TRUE indicates that thet?                  application should use the alias node address.   O                  * Outgoing Alias for 'notes' enabled?                 [TRUE] :   '                  Specify TRUE or FALSE.   G               7. The answer to the following question specifies whether H                  or not the application should use a proxy by default ifF                  the application does indicate whether to use a proxy.C                  FALSE indicates that, by default, this application E                  does not use an outgoing proxy. TRUE indicates that, E                  by default, this application uses an outgoing proxy.s  O                  * Outgoing Proxy for 'notes' enabled?                 [TRUE] :W  '                  Specify TRUE or FALSE.d  G               8. The answer to the following question specifies whether I                  or not the remote node name is passed to the application D                  in synonym form. If a synonym is not available, theC                  full name is always used. FALSE indicates that thee  I                                    Modifying a Current Configuration 7-53     s      )         Modifying a Current Configuration 1         7.11 Configuring the Application Database     G                  full name is passed to the application. TRUE indicates F                  that the node synonym, if available, is passed to the                  application.c  O                  * Require node synonym for 'notes' enabled?           [TRUE] :w  '                  Specify TRUE or FALSE.   F               9. The OSI TSEL is used for applications that do not useF                  the DNA Session Control protocol. The TSEL is roughlyF                  equivalent to a DNA Session Control address. The TSELH                  must be a hexadecimal number of 2 to 64 digits and must2                  contain an even number of digits.  O                  * What is the Incoming OSI TSEL for 'notes'?                 :   F                 ________________________ Note ________________________  A                 This function is currently not implemented. Pressd6                 Return to continue to the next prompt.  F                 ______________________________________________________  I              10. You have the option of creating an OpenVMS account under(I                  which the application should run. To create the account,fE                  begin by entering the user name that you want to useiH                  when creating the account. If you do not want to createE                  an account for the application, you can either enteriH                  NONE and press Return, or press the space bar and press                  Return.  O                  * What is the User Name for 'notes'?          [NOTES$SERVER] :   G                  If you decide to create an account for the applicationiI                  (by providing an account name in the previous question),iF                  you must provide a UIC for the account and assign anyG                  rights identifiers associated with the account. AnswerrE                  the following two questions to enter the UIC and any 8                  rights identifiers for the application:  O                  * What UIC should 'notes' use?         [[200,200]] : [376,377]uO                  * Rights identifiers for 'NOTES$SERVER'?         :net$examine,u4                   net$declareobject,net$decnetaccess  F                  If there are two or more rights identifiers, separate"                  them with commas.  .         7-54 Modifying a Current Configuration r  d      I                                         Modifying a Current Configuration I                                 7.11 Configuring the Application Database     H                  If you have entered account information in the previousH                  three questions, the procedure then creates the accountH                  for the application and displays the following message:  _                  %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account NOTES$SERVER   0         7.12 Configuring the MOP Client Database  H               To configure the MOP client database, select option 8 from$               the main options menu:  N               * Which configuration option to perform?                 [1] : 8  I               The procedure begins by asking if you want to add or delete                a MOP client:A  L               * Do you want to ADD or DELETE a MOP Client?           [ADD] :  G               Answer ADD to create a new MOP client entity on the localNC               node, allocate resources for it, and open the service G               interface. Answer DELETE to delete an existing entity andN+               reclaim associated resources.H  A               Next, the procedure asks for the MOP client's name:P  M               * Name of the MOP Client?                              : SUPERXS  A               Specify the simple name of the client (for example,W               SUPERX).  :               If you are deleting a MOP client, proceed toE               Section 7.12.1. If you are adding a MOP client, proceede                to Section 7.12.2.  @               Once you have completed the MOP client dialog, theI               procedure asks if you want to configure the new NCL startup D               scripts. Proceed to Section 7.18 for more information.  F                 ________________________ Note ________________________  C                 Each invocation of option 8 adds or deletes one MOP A                 client. If you wish to add or delete multiple MOPl/                 clients, invoke option 8 again.s  F                 ______________________________________________________  I                                    Modifying a Current Configuration 7-55            )         Modifying a Current Configurationi0         7.12 Configuring the MOP Client Database    $         7.12.1 Deleting a MOP Client  H               If you want to delete a MOP client, the procedure displays#               the following prompt:R  L               * Are you sure you want to DELETE this client?               :  H               Answer YES if you want to delete the MOP client. Answer NOG               if you want to keep the MOP client. If you answer NO, thesI               procedure informs you it has canceled the delete operation:d  C               %NET$CONFIGURE-I-DELETECAN, delete operation canceleds  "         7.12.2 Adding a MOP Client  I               If you are adding a MOP client, the configuration procedure B               asks a series of questions to define the MOP client:  G               1. The procedure begins by asking you for the MOP circuitDD                  to be used for all operations involving the client:  O                  * Circuit for 'superx'?                                      :c  ,                  Specify a MOP circuit name.  E               2. For LAN circuits, you must also specify a set of LAN +                  addresses for this client:o  O                  * Physical addresses for 'superx'?                           :   D                  Specify a set of LAN addresses separated by commas.  E               3. The next three questions describe the files that are D                  loaded onto the MOP client system during a downlineD                  load operation. The primary loader is assumed to beC                  the resident code on the system that activates therG                  client's network interface and prepares the system foreG                  downline loaded software. Depending on the system, you F                  may need to specify a secondary loader and a tertiaryD                  loader that are loaded before the system image. AllI                  file specifications are complete file specifications forn)                  files on the local node.e  O                  * Secondary Loader for 'superx'?                             :cO                  * Tertiary Loader for 'superx'?                              :SO                  * System Image for 'superx'?                                 :   B                  Specify the files you want loaded when the clientC                  requests the various images. If necessary, you cann:                  specify multiple files for each question.  .         7-56 Modifying a Current Configuration m         I                                         Modifying a Current Configuration I                                  7.12 Configuring the MOP Client Database     H               4. In addition to the system image file and its associatedG                  secondary and tertiary loaders, MOP has the capabilitytH                  to respond to downline load requests for special systemC                  images used for diagnostics and system management. F                  System management images can take the form of system-?                  specific management files or CMIP script files_E                  containing network management commands in CMIP form.aI                  All file specifications are complete file specifications -                  for files on the local node.n  O                  * Diagnostic Image for 'superx'?                             : O                  * Management Image for 'superx'?                             : O                  * Script File for 'superx'?                                  :r  B                  Specify the files you want loaded when the clientI                  requests diagnostic and management images. If necessary,yB                  you can specify multiple files for each question.  C               5. The next two questions control upline dump actions F                  involving the client system. You can specify the fileD                  on the local system used to contain the upline dumpH                  and the memory address in the client system at which to*                  begin the dump operation.  O                  * Dump File for 'superx'?                                    :oO                  * Dump Address for 'superx'?                             [0] :h  @                  Specify the dump file and the starting address.  I               6. You can specify a verification string you want sent in as6                  boot message to the specified client:  O                  * Verification for 'superx'?            [%X0000000000000000] :*  I               7. The next four questions define Phase IV information that F                  is passed to the client in a downline load operation.E                  Some client software needs this information. You canhE                  specify the Phase IV client address and name and theyG                  Phase IV host address and name. The client information*E                  defines the client's own Phase IV identity; the hostoG                  information identifies the client's load host Phase IVn                  identity.  O                  * Phase IV Client Address (aa.nnn) for 'superx'?             :tO                  * Phase IV Client Name for 'superx'?                      [] :gO                  * Phase IV Host Address for 'superx'?                        :rO                  * Phase IV Host Name for 'superx'?                        [] :r  I                                    Modifying a Current Configuration 7-57n t  t      )         Modifying a Current Configuration 0         7.12 Configuring the MOP Client Database    E                  Specify the Phase IV information appropriate for thet<                  software being loaded on the client system.  (         7.13 Configuring a Cluster Alias  I               To configure a cluster alias, select option 9 from the maino               options menu:e  N               * Which configuration option to perform?                 [1] : 9  I               The procedure begins by asking if you want to add or deletea               an alias:a  L               * Do you want to ADD or DELETE an alias?               [ADD] :  E               Answer ADD to create an alias on the local node; answers1               DELETE to delete an existing alias.l  F               Next, the procedure asks for the full name of the alias:  L               * Full name of Cluster Alias                                 :  >               Specify the full name of the alias (for example,!               IAF:.sales.boston).r  I               If you are deleting an alias, proceed to Section 7.13.1. If A               you are adding an alias, proceed to Section 7.13.2.   E               Once you have completed the alias dialog, the procedure E               displays a summary of the configuration and asks if youoG               want to configure the new NCL startup scripts. Proceed toa0               Section 7.17 for more information.            7.13.1 Deleting an Alias  F               If you are removing a node from the specified alias, the6               procedure displays the following prompt:  L               * Are you sure you want to DELETE this alias?            [NO]:  C               Answer YES if you want to remove the system from this H               alias. Answer NO if you want the system to remain a memberH               of this alias. If you answer NO, the procedure informs you3               it has canceled the delete operation:   C               %NET$CONFIGURE-I-DELETECAN, delete operation canceled   .         7-58 Modifying a Current Configuration t  o      I                                         Modifying a Current Configuration I                                          7.13 Configuring a Cluster Aliasb             7.13.2 Adding an Alias  I               If you are adding a node to a cluster alias, the dialog for F               a configuration modification is identical to the initialC               dialog. See Section 6.12 for the entire alias dialog.n  1         7.14 Replacing a MOP Client Configurationt  E               To replace a MOP Client Configuration, select option 10c)               from the main options menu:h  O               * Which configuration option to perform?                 [1] : 10   G                 _______________________ Warning _______________________   E                 Using this option deletes the existing MOP client NCL B                 startup script file. In the initial configuration,B                 this file contains two NCL commands: one to createC                 MOP and one to enable MOP. If you have modified theiB                 initial configuration by using option 8 to add MOPF                 client definitions, these definitions exist in the MOPF                 Client NCL startup script file. Therefore, choosing toD                 replace the existing MOP client file deletes all theC                 MOP client information you added by using option 8.y  >                 For information about how you can create a MOPA                 client database not subject to this deletion, seed                 Section 7.20.1.i  F                 ______________________________________________________  D               By default, MOP is not started by net$startup. To makeC               this system service MOP requests, the NET$STARTUP_MOP C               logical name must be defined to signal net$startup torD               load the MOP software. This symbol is normally definedG               in sys$startup:net$logicals.com. Based on your input, the G               procedure modifies net$logicals.com by adding or removing F               the definition of the NET$STARTUP_MOP logical name. ThisI               section of the procedure also generates a short NCL startup C               script file containing the NCL commands to create andt$               enable the MOP entity.  8               The procedure asks if you want MOP loaded:  L               * Load MOP on this system?                             [YES] :  I                                    Modifying a Current Configuration 7-59e e  m      )         Modifying a Current Configuration 1         7.14 Replacing a MOP Client Configuratione    E               Answer YES to enable MOP service on this system. AnswereF               NO to disable MOP service on this system. Note that yourG               answer will have no effect if the NET$STARTUP_MOP logical (               name is defined elsewhere.  C               Regardless of your answer, the procedure displays theuG               following message and asks it you want to replace the MOPn-               client NCL startup script file:a  Q               %NET$CONFIGURE-I-MOPCLIENTFND, MOP client NCL script already exists   P               * Replace MOP Client script file?                       [NO] : yes  F               Answer YES to create a new MOP Client NCL startup script+               file, otherwise press Return.   C               Once you have completed the MOP dialog, the procedureiE               displays a summary of the configuration and asks if youoG               want to configure the new NCL startup scripts. Proceed toi0               Section 7.17 for more information.                                                  .         7-60 Modifying a Current Configuration e  e      I                                         Modifying a Current Configuration I                                          7.15 Configuring Satellite Nodes     (         7.15 Configuring Satellite Nodes  @               This section of the dialog allows you to configureG               satellite nodes that are members of your system's OpenVMS F               Cluster. Before using this feature, you must first fullyC               configure the system on which you are now running thes&               net$configure procedure.  G                 _______________________ Caution _______________________   D                 If your cluster is running mixed versions of DECnet-?                 Plus, you cannot use this feature. Instead, you A                 must configure the nodes independently by runningi-                 net$configure on each system.   F                 ______________________________________________________                 BASICc  G               This option is not available when using the BASIC option.r                 ADVANCED  E               To configure satellite nodes, select option 11 from thee                main options menu:  O               * Which configuration option to perform?                 [1] : 11   /               The procedure displays a submenu:   ,                       Configuration Options:  1                       [0]     Return to main menui  B                       [1]     Autoconfigure Phase IV cluster nodes<                       [2]     Configure cluster node scripts2                       [3]     Configure local node  L               * Which configuration option to perform?                 [1] :  B               Table 7-4 gives a brief description of the satellite$               configuration options.      I                                    Modifying a Current Configuration 7-61e           )         Modifying a Current Configurationr(         7.15 Configuring Satellite Nodes    I               Table_7-4_Satellite_Configuration_Options__________________   I               Option___Description_______________________________________   F               1        Autoconfigure Phase IV cluster nodes - Use thisE                        option to perform the initial configuration ofiD                        a Phase IV cluster member. This option can beF                        used only for cluster members that have not yetF                        been configured (either by using this option orG                        by running net$configure directly on the clustert                        member).d  G               2        Configure cluster node scripts - Use this optioniI                        to set up the configuration utility to reference aCH                        satellite node in all future configuration tasks.D                        You can use this option to further refine theG                        configuration automatically created by option 1.   G               3        Configure local node - Use this option to deleteaC                        the satellite selection made in option 2 andsI                        return to configuring the local node in all futureeI               _________configuration_tasks.______________________________                                               .         7-62 Modifying a Current Configuration C  u      I                                         Modifying a Current Configuration I                                          7.15 Configuring Satellite NodesC    5         7.15.1 Autoconfiguring Phase IV Cluster Nodes   I               To autoconfigure a Phase IV cluster member, select option 1 .               from the satellite options menu:  N               * Which configuration option to perform?                 [1] : 1  F               If you select this option, the procedure creates a shortI               command file that invokes net$configure with the parameterseC               necessary to complete the initial configuration. This F               command file is invoked the next time that the satelliteI               system is rebooted. Most of the parameters are derived from G               the defaults within the net$configure procedure. However, D               you must supply a small number of parameters directly.  E               1. The procedure begins by asking you to enter the full F                  name of a cluster alias in which you want the cluster'                  member to participate:m  O                  * Fullname of cluster alias:                                 :u  H                  Supply the full node name of the cluster alias. If noneD                  is supplied, no cluster alias is configured for the(                  systems being upgraded.  D               2. If you entered a cluster alias name in the previousG                  question, the next two prompts ask for the address andd0                  selection weight for the alias:  S                  * Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx)  : S                  * Selection weight for this cluster node [0 for satellites]      :u  D                  Enter a Phase IV address or a MAC address. For moreE                  information about these two questions, see the alias (                  dialog in Section 6.12.  @               3. To configure the cluster satellite systems, theF                  configuration procedure needs to know the system rootF                  directories from which the satellites boot. Normally,F                  the system root directories are on sys$sysdevice. TheF                  device given in response to this question is searchedF                  for all system roots. Those found that do not containG                  a Phase V checksum database are assumed to be Phase IV F                  nodes and are candidates for autoconfiguration. EnterC                  the device containing the system roots for cluster                   members:   O                  * Device containing system roots            [SYS$SYSDEVICE:] :u  I                                    Modifying a Current Configuration 7-63h    o      )         Modifying a Current Configuratione(         7.15 Configuring Satellite Nodes    C                  The procedure displays the following message as it G                  scans the indicated system root device for system rootD                  directories:   P                  Scanning SYS$SYSDEVICE: for Phase IV system root directories...  @                  If it finds a directory it does some additionalD                  checking to verify that it has found a valid systemG                  root directory. If the directory is valid, it uses the I                  member's modparams.dat file to obtain the default values E                  for some of the following questions. If no roots are H                  found on the device supplied (or if all the roots foundI                  have already been autoconfigured), the procedure asks ifbH                  it should scan any additional devices for system roots:  R                  * Are there any more disk devices containing system roots? [NO] :  D                  Answer YES if any additional devices contain systemG                  root directories. Answer NO to return to the satellite.$                  configuration menu.  I                  a. If a system root is found and the system has not been G                     autoconfigured (that is, does not contain a DECnet-gF                     Plus checksum database), the procedure asks if you7                     want to upgrade the cluster member:e  U                     * Upgrade Phase IV cluster member FASTER?                 [Yes] :   E                     If you answer YES, net$configure creates the fileiG                     sys$specific:[sys$startup]net$autoconfigure.com. IfoI                     this file is present when the cluster member reboots, E                     it causes the cluster member to automatically runfE                     net$configure using the information you supply inrI                     this section. Answer NO if you do not want the system #                     autoconfigured.   A                     If the procedure finds a root that contains a C                     net$autoconfigure.com file but has not yet beenuE                     configured, it precedes the upgrade question withdF                     a message indicating that you have already created/                     the autoconfiguration file:   X                     %NET$CONFIGURE-I-ALREADYMARKED, FASTER is already marked for upgrade    .         7-64 Modifying a Current Configuration 6         I                                         Modifying a Current Configuration I                                          7.15 Configuring Satellite Nodese    D                  b. In you answered YES to the upgrade question, theH                     procedure needs to complete the information requiredE                     for the net$autoconfigure.com file. The procedure:D                     asks you for the node's full name. The full nameF                     can be a name in the Local, DECdns, or Domain nameI                     service. See Section 6.4.1 and Section 6.4.2 for moreiC                     information about name services and full names.i  >                     Enter the full name of the satellite node:  R                     * Enter the full name                           [HP:.FASTER] :  D                     Enter the node's full name. The nickname you useG                     determines the name service. If you fail to providetI                     the nickname (or namespace name if specifying a Local H                     or Domain full name), the procedure informs you that0                     you must enter the nickname:  P                     NET$CONFIGURE-E-NONAMESPACENAME, namespace nickname required  ?                  c. Next, enter the node synonym to use for the                      satellite:  R                     * What is the synonym name for this system?         [FASTER] :  H                     Enter the node's synonym. See Section 6.4.3 for more4                     information about node synonyms.  B                  The procedure resumes the scan of the system root@                  device. If any more system roots are found, theH                  procedure repeats the previous three questions for each-                  satellite system root found.   I                  Once the procedure completes the scan of system roots oncG                  the device you indicated, it asks you if there are anyd7                  other devices containing system roots:R  R                  * Are there any more disk devices containing system roots? [No] :  A                  Answer YES if you wish to specify another device H                  containing system roots. Answer NO if there are no more1                  devices containing system roots.o  F                 ________________________ Note ________________________  B                 This dialog forces all satellites to join a commonF                 alias. If the cluster supports more than one alias youC                 can select this option again and supply a differenta@                 cluster alias. In this manner, you can configure  I                                    Modifying a Current Configuration 7-65T _  R      )         Modifying a Current Configuration (         7.15 Configuring Satellite Nodes    B                 some of the satellite nodes in one alias and other2                 satellite nodes in a second alias.  F                 ______________________________________________________  D               After completing all requested autoconfigurations, the>               procedure returns to the satellite options menu.  9         7.15.2 Electing To Configure Cluster Node Scriptsd  H               Normally, the configuration procedure is used to configureA               the local node. You can use the procedure to modifywG               satellite nodes that have already been configured (eithersI               by using option 1 and rebooting the satellite or by runningiI               net$configure directly on the node). This option allows you I               to direct the configuration procedure to perform all future G               operations on a satellite node instead of the local node. H               Note that not all configuration options are available when+               configuring a satellite node.g  I               To direct the configuration procedure to perform all futureiF               operations on a satellite node, select option 2 from the%               satellite options menu:s  N               * Which configuration option to perform?                 [1] : 2  G               The procedure asks you for the name of the cluster member )               that you want to configure:V  S               * Cluster node name to be configured:                        : FASTERf  E               Enter the simple name of the cluster member you want toa               configure.  F                 ________________________ Note ________________________  @                 The net$configure procedure attempts to find theD                 system root for that cluster member (by scanning theE                 net$mop_client_startup.ncl startup script file on thetF                 local system) to supply defaults for the two questions                 that follow.  F                 ______________________________________________________  B               The next two questions determine the location of theF               satellite's system root. The first question asks for theC               disk device on which the cluster member's system root F               resides. The default is either sys$sysdevice or the root  .         7-66 Modifying a Current Configuration n  o      I                                         Modifying a Current ConfigurationiI                                          7.15 Configuring Satellite Nodes     I               device found for that system in the local system's net$mop_ -               client_startup.ncl script file.a  L               * Device for FASTER root:                    [SYS$SYSDEVICE] :  <               Enter the device containing the system's root.  H               Next, the procedure asks you for the system root directory*               from which the member loads:  Q               * Directory for FASTER root:                                 : SYS2   H               Enter the system root directory in the form SYSxxxx, where+               xxxx is a hexadecimal number.P  E               The procedure verifies that the cluster member has beenyA               configured (either through the autoconfigure option B               discussed in suboption 1 or by running net$configureC               directly on the satellite). If the autoconfigure file H               created by suboption 1 is found but no other configurationC               files are found, the procedure displays the following                message:  S                ******************************************************************** L                This cluster member has been flagged for autoconfiguration ofQ                OSI/DECnet Phase V, but has not yet executed the autoconfigurationCO                procedure.  In order to do this, the system must be rebooted, orT<                SYS$STARTUP:NET$STARTUP.COM must be executed.S                ********************************************************************   B               If the procedure finds no configuration files and noD               autoconfigure file, it displays the following message:  S                ********************************************************************xM                This cluster member has not yet been configured for OSI/DECnetaO                Phase V.  You may either select option [1] to autoconfigure thisX;                system, or run NET$CONFIGURE on this system. S                ********************************************************************t  C               If the proper configuration information is found, the E               procedure returns to the main options menu to allow youlB               to modify the cluster member's configuration. BeforeF               net$configure returns to the main options menu, it warnsD               you that all subsequent options will be applied to the+               cluster member you specified:   ?               %NET$CONFIGURE-I-VERCHECKSUM, verifying checksums   N               All configuration options will be applied to cluster node FASTER  I                                    Modifying a Current Configuration 7-67p e  s      )         Modifying a Current Configuration (         7.15 Configuring Satellite Nodes    I               Note that the following main menu options are not availableaD               when configuring satellite nodes: option 1 (Perform anH               entire configuration), option 3 (Configure Devices on thisE               machine), and option 5 (Configure Timezone Differentiale               Factor).  3         7.15.3 Electing to Configure the Local Node   D               If you select option 3, it clears the action of optionD               2; that is, all subsequent net$configure modificationsE               are made to the local system (as when net$configure wasw               started).(  I               To direct the configuration procedure to perform all futureaD               operations on the local node, select option 3 from the%               satellite options menu:   N               * Which configuration option to perform?                 [1] : 3  E               All subsequent configuration tasks now affect the local B               node. All options in the main options menu are again               available.  1         7.15.4 Exiting the Satellite Options Menu   C               To exit the satellite options menu, enter 0 and press I               Return. The procedure returns you to the main options menu.   8         7.16 Configuring Cluster-Common Script Locations  G               If you did not already elect to do so, this option allows D               you to make the event, application, and MOP client NCLB               startup scripts (net$event_startup, net$application_I               startup, and net$mop_client_startup) common for all clusteroG               nodes. That is, a single copy of each script is shared by G               all systems in the cluster. This ensures that all systemsoF               have the same event logging, application, and MOP client               configuration.  E               The configuration procedure does this by moving the NCLsG               startup scripts from the node's sys$specific directory tou(               it's sys$common directory.  F                 ________________________ Note ________________________  @                 The configuration procedure deletes the existingC                 system-specific NCL startup scripts in sys$specificdA                 only on the node where net$configure is currentlyl  .         7-68 Modifying a Current Configuration n  r      I                                         Modifying a Current Configuration.I                          7.16 Configuring Cluster-Common Script Locationsn    ?                 running. It does not delete the system-specificTA                 script files from the sys$specific directories ofuF                 the other cluster members. You must do this explicitlyF                 by selecting this option (either after using suboptionA                 2 of option 11 to select the cluster member or by E                 running net$configure directly on the cluster member) C                 on all cluster members where you want to delete the %                 sys$specific scripts.o  F                 ______________________________________________________                 BASIC   G               This option is not available when using the BASIC option.T                 ADVANCED  E               To select this option, you must have already configured E               the system using the ADVANCED configuration option, and B               net$configure must be executing on a cluster system.  F               To manage the location of the cluster-common NCL startupH               script files, select option 12 from the main options menu:  O               * Which configuration option to perform?                 [1] : 12   F               The remainder of this section contains an example of howC               this option can be used to manage the location of the H               scripts files for EVENT, APPLICATION, and MOP_CLIENT. ThisE               example assumes that you elect to create cluster-commonlD               script files for all three scripts. It is assumed thatE               you previous elected to create system-specific scripts.SG               These cluster-common scripts are created from the system-aI               specific scripts on the currently selected system. (To makesE               the dialogs in this section more clear, some additionalr?               formatting has been added to the example output.)n  .               1. Begin by selecting option 12.  R                  * Which configuration option to perform?                 [1] : 12  H               2. For each script, the procedure asks if you want to moveG                  the script and then displays a message indicating thats=                  the script has been moved if you answer YES:e  I                                    Modifying a Current Configuration 7-69o h  s      )         Modifying a Current Configuration 8         7.16 Configuring Cluster-Common Script Locations    Z                  * Move the APPLICATION startup script to the cluster common area? [YES] :_                  %NET$CONFIGURE-I-MOVESCRIPT, created cluster common APPLICATION startup scriptfI                    from SYS$SPECIFIC:[SYSMGR]NET$APPLICATION_STARTUP.NCL;   T                  * Move the EVENT startup script to the cluster common area? [YES] :Y                  %NET$CONFIGURE-I-MOVESCRIPT, created cluster common EVENT startup scriptnC                    from SYS$SPECIFIC:[SYSMGR]NET$EVENT_STARTUP.NCL;a  Y                  * Move the MOP_CLIENT startup script to the cluster common area? [YES] :h^                  %NET$CONFIGURE-I-MOVESCRIPT, created cluster common MOP_CLIENT startup scriptH                    from SYS$SPECIFIC:[SYSMGR]NET$MOP_CLIENT_STARTUP.NCL;  F                 ________________________ Note ________________________  B                 Although the example shows all three scripts beingB                 moved, you do not have to treat all scripts in the                 same manner.  F                 ______________________________________________________  D                  After moving the scripts, new checksums are createdC                  and the procedure returns to the main options menu I                  (after informing you that it is using the cluster-common                   scripts):  [                  %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modifiede#                    by NET$CONFIGUREg  X                  %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration                    completed  T                  %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION scriptN                  %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT scriptS                  %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT scripts  G               3. However, these cluster-common scripts will not be usedoD                  by the satellite system FASTER because it still hasI                  system-specific copies. To change this, select option 11 G                  to manage cluster nodes and then suboption 2 to manageo3                  the configuration for node FASTER:e  .                         Configuration Options:  4                          [0]     Exit this procedure  .         7-70 Modifying a Current Configuration    i      I                                         Modifying a Current ConfigurationeI                          7.16 Configuring Cluster-Common Script Locations     @                          [1]     Perform an entire configuration                     .i                     .                      .o:                          [11]    Configure satellite nodesC                          [12]    Configure cluster script locationst  R                  * Which configuration option to perform?                 [0] : 11  /                          Configuration Options:   4                          [0]     Return to main menu  E                          [1]     Autoconfigure Phase IV cluster nodesuC                          [2]     Full configuration of cluster nodec5                          [3]     Configure local node   Q                  * Which configuration option to perform?                 [0] : 2sV                  * Cluster node name to be configured:                        : FASTERO                  * Device for FASTER root:                    [SYS$SYSDEVICE] : U                  * Directory for FASTER root:                                 : SYS10m  H                  The configuration procedure informs you that FASTER hasH                  system-specific versions of these scripts that override,                  the cluster-common scripts:  \                  %NET$CONFIGURE-I-OVERRIDECOMMON, node specific APPLICATION script overrides.                    the cluster common settingsV                  %NET$CONFIGURE-I-OVERRIDECOMMON, node specific EVENT script overrides.                    the cluster common settings[                  %NET$CONFIGURE-I-OVERRIDECOMMON, node specific MOP_CLIENT script overrides .                    the cluster common settings  Q                  All configuration options will be applied to cluster node FASTER   G               4. Select option 12 to delete the system-specific scripts E                  so that FASTER will use the cluster-common versions:D  /                          Configuration Options:   4                          [0]     Exit this procedure  @                          [1]     Perform an entire configuration                     .o                     .m                     . :                          [11]    Configure satellite nodesC                          [12]    Configure cluster script locationsn  I                                    Modifying a Current Configuration 7-71u           )         Modifying a Current Configurationn8         7.16 Configuring Cluster-Common Script Locations    R                  * Which configuration option to perform?                 [0] : 12  F               5. The procedure asks you if each system-specific scriptH                  should be deleted and displays a message indicated thatD                  it is deleting the system-specific version when you                  answer YES:  S                  * Delete the local APPLICATION startup script?          [NO] : yes V                  %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of the-                    APPLICATION startup script   S                  * Delete the local EVENT startup script?                [NO] : yesrV                  %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of the'                    EVENT startup script   S                  * Delete the local MOP_CLIENT startup script?           [NO] : yes V                  %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of the,                    MOP_CLIENT startup script  @                  After deleting the system-specific scripts, newG                  checksums are created and the procedure returns to thenD                  main menu (after informing you that it is using the)                  cluster-common scripts):l  [                  %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modifiedr#                    by NET$CONFIGURE   X                  %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration                    completed  T                  %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION scriptN                  %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT scriptS                  %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT script   Q                  All configuration options will be applied to cluster node FASTERm  C               After the initial creation of cluster-common scripts, H               option 12 always allows you to alternate the status of theG               system-specific scripts. That is, if the system currentlyvH               has system-specific scripts, you are given the opportunityC               to delete them. If the system does not currently havepD               system-specific scripts, you are given the opportunity               to create them._  G               For example, if you now wanted to restore system-specificfG               scripts to node FASTER, again select option 12 (this timexH               to restore the system-specific scripts so that FASTER willH               use these scripts instead of the cluster-common versions):  .         7-72 Modifying a Current Configuration e  t      I                                         Modifying a Current ConfigurationeI                          7.16 Configuring Cluster-Common Script Locationsb    ,                       Configuration Options:  1                       [0]     Exit this procedurer  =                       [1]     Perform an entire configurationd                  .                  .                  .7                       [11]    Configure satellite nodes @                       [12]    Configure cluster script locations  O               * Which configuration option to perform?                 [0] : 12   X               * Override the cluster common default APPLICATION startup script? [NO] : yS               %NET$CONFIGURE-I-CREATEDOVERRIDE, created system specific copy of thec*                 APPLICATION startup script  R               * Override the cluster common default EVENT startup script? [NO] : yS               %NET$CONFIGURE-I-CREATEDOVERRIDE, created system specific copy of the $                 EVENT startup scriptW               * Override the cluster common default MOP_CLIENT startup script? [NO] : yeS               %NET$CONFIGURE-I-CREATEDOVERRIDE, created system specific copy of the )                 MOP_CLIENT startup scriptd  G               After creating the system-specific scripts, new checksums D               are created and the procedure returns to the main menuG               (after informing you that it is using the system-specific                scripts):u  X               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified                  by NET$CONFIGURE  U               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuratione                 completed   Y               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific APPLICATION script overrides +                 the cluster common settings S               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific EVENT script overrides +                 the cluster common settingslX               %NET$CONFIGURE-I-OVERRIDECOMMON, node specific MOP_CLIENT script overrides+                 the cluster common settings   H               If you choose not to delete the system-specific files, theI               procedure gives you the option to delete the cluster-common                files instead:  I                                    Modifying a Current Configuration 7-73.           )         Modifying a Current ConfigurationD8         7.16 Configuring Cluster-Common Script Locations    L               * Delete the local APPLICATION startup script?          [NO] :P               * Delete the cluster common APPLICATION script?         [NO] : yesS               %NET$CONFIGURE-I-DELETECOMMON, deleted the cluster common APPLICATIONf                 startup script  L               * Delete the local EVENT startup script?                [NO] :P               * Delete the cluster common EVENT script?               [NO] : yesM               %NET$CONFIGURE-I-DELETECOMMON, deleted the cluster common EVENTo                 startup script  L               * Delete the local MOP_CLIENT startup script?           [NO] :P               * Delete the cluster common MOP_CLIENT script?          [NO] : yesR               %NET$CONFIGURE-I-DELETECOMMON, deleted the cluster common MOP_CLIENT                 startup script  F               After deleting the cluster-common scripts, new checksumsE               are created and the procedure returns to the main menu:c  [               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by                  NET$CONFIGURE   _               %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completedn  N               All configuration options will be applied to cluster node FASTER           7.17 Summary Display  E               With the exceptions of options 5, 7, 8, 11, and 12, theUH               configuration procedure displays an updated summary of the#               node's configuration.V  G               In the case of option 1 (Perform an entire configuration) B               or option 2 (Change naming information), the displayI               includes an additional field entitled "DECdns Node Type" iniH               the Node Information section. This field shows you whetherG               the node has been configured as a DECdns server or clerk.tG               A portion of the display is shown below (for the complete )               display, see Section 6.13):t  :                                   Summary of Configuration          .         7-74 Modifying a Current Configuration    t      I                                         Modifying a Current ConfigurationvI                                                      7.17 Summary Display                     Node Information I                       Directory Services Chosen:      DECDNS,LOCAL,DOMAIN_<                       Primary Directory Service:      DECDNS@                       DECdns Full name:       ACME:.WABBIT.ELMER:                       Local Full name:        LOCAL:.ELMER%                       Fully QualifieddC                       Host name:              ELMER.WABBIT.ACME.EDUs3                       Node Synonym:           ELMER 3                       Phase IV Address:       15.27 2                       Phase IV Prefix:        49::4                       DECdns Node Type:       ServerE                       Session Control Address Update Interval:     10t5                       Routing Node Type:      ENDNODEpE                       Autoconfiguration of Network Addresses: Enableds1                       Routing ESHello Timer:  600 1                       Routing ES Cache Size:  512   7                       Alias Name:     ACME:.WABBIT.HELP                   .                  .                  .    /         7.18 Generating New NCL Startup Scriptsn  H               With the exception of options 2 and 12, the procedure asksG               if you want generate new NCL startup scripts based on thee,               new configuration information:  L               * Do you want to generate NCL configuration scripts?   [YES] :  A               Answer YES to accept the new configuration you just B               specified. The procedure automatically generates any@               required NCL scripts in the sys$manager directory.  F                 ________________________ Note ________________________  A                 Option 2 (Change naming information) does not ask B                 if you want to generate new NCL scripts. It always@                 generates new scripts. The naming operations are@                 complex and are performed throughout the dialog.?                 Therefore, if you need to retract a change, youtD                 must run the configuration dialog again with the old                 information.  F                 ______________________________________________________  I                                    Modifying a Current Configuration 7-75e t  u      )         Modifying a Current Configuration /         7.18 Generating New NCL Startup Scriptso      G               The procedure performs a checksum process on the modifiedrA               scripts to check if any of the scripts have changedeE               when you run net$configure again. It displays a messageoB               indicating that the checksum process is in progress:  O               %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scriptsi)                 modified by NET$CONFIGURED  H               If the procedure is unable to access the existing checksum=               file, it displays the following error messages:p  F               %NET$CONFIGURE-E-WRITECKERR, error writing checksum file                  .                  .                  .G               %NET$CONFIGURE-I-LASTTRANSABORT, last transaction abortedS  A               Exit the procedure (select option 0), determine whyrE               the configuration procedure was not able to write a new 5               checksum file, and retry the operation.   G               The LASTTRANSABORT message is also displayed whenever youeF               cancel an option. The configuration procedure returns toH               the main menu. Under these circumstances, you can continue/               with other configuration options./  !         7.19 Starting the Network   I               When modifying a configuration, the configuration procedure H               does not restart a running network. If you selected optionD               1 (Perform an entire configuration) and the network isH               not started, the procedure starts the network as discussedF               in Section 6.15. If you selected option 2 (Change namingD               information), the procedure also starts the network toH               enable it to make namespace modifications. See Section 7.6F               for more information about processing that occurs during%               option 2 modifications.N  D               In the case of all other options that affect the localH               node, if the network is running when you modify the node'sE               configuration, you can execute the modified NCL startup "               scripts in two ways:  #               o  Reboot the system.   .         7-76 Modifying a Current Configuration    L      I                                         Modifying a Current Configuration I                                                 7.19 Starting the Network     C               o  Disable the entity to which the script applies and -                  execute the modified script.i  B                  To execute the NCL script, use the format ncl> do*                  script-file. For example:  B                  ncl> do sys$manager:net$nsp_transport_startup.ncl  F                 ________________________ Note ________________________  >                 Although, the net$configure procedure does notB                 automatically execute the modified NCL scripts for?                 you, it does execute the search path NCL scripte-                 (net$searchpath_startup.ncl).   F                 ______________________________________________________  2         7.20 Customizing the Network Configuration  D               To customize your system beyond what the net$configureH               procedure provides, you must edit the NCL scripts producedG               by net$configure (refer to the HP DECnet-Plus for OpenVMS H               Network Management manual). HP recommends that you use theG               net$configure procedure for major modifications involving                an entire entity.n  ,         7.20.1 Creating User-Defined Scripts  H               You can use user-defined site-specific NCL scripts for theH               Event Dispatcher, MOP client, application, and search pathH               entities. (See Section B.1.1 for further information about=               creating the site-specific search path script.)n  H               The network startup procedure (net$startup.com) calls fourH               site-specific NCL scripts (if they exist) when the networkD               is started. These scripts must be in sys$manager. TheyH               are called immediately after their net$configure generatedF               counterparts are executed. The following table lists the-               scripts and their counterparts.a            I                                    Modifying a Current Configuration 7-77  x  i      )         Modifying a Current Configurationm2         7.20 Customizing the Network Configuration  I               ___________________________________________________________C7               User-Defined                    GeneratedrI               Site-Specific_Script____________Script_____________________o  C               net$event_local.ncl             net$event_startup.ncl   I               net$application_local.ncl       net$application_startup.nclm  H               net$mop_client_local.ncl        net$mop_client_startup.ncl  I               net$searchpath_local.ncl________net$searchpath_startup.ncl_i  H               Such user-defined scripts are user-maintained and thus areH               not overwritten or deleted by net$configure. HP recommendsC               that, whenever possible, you place your site-specific 8               changes in these user-defined NCL scripts.  F               HP provides a template for the net$event_local.ncl file.H               The template is located in the sys$manager: directory withE               the file name net$event_local.template. Simply copy thevG               file to net$event_local.ncl and make any changes for yourt               system.A  F                 ________________________ Note ________________________  B                 If you invoke net$configure to edit a standard NCLA                 script (net$entity_startup.ncl), the standard NCLu?                 script is superseded and renamed to net$entity_tD                 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 appropriatecC               net$entity_startup.ncl-old script back to net$entity_uD               startup.ncl. Be sure to incorporate any new changes asI               well. The net$configure procedure flags these modificationsi5               the next time it checksums the scripts.i          .         7-78 Modifying a Current Configuration                         I                                                                  Part III9I         _________________________________________________________________o  I             Configuring X.25 Functionality on DECnet-Plus for OpenVMS VAXnI                                                                   Systems             F               Part III describes the steps necessary to configure X.25H               functionality on DECnet-Plus for OpenVMS VAX systems. ThisF               functionality was previously a separate product known as               VAX P.S.I. e  I                    I                                                                         8aI         _________________________________________________________________r  I                                          Configuring X.25 for OpenVMS VAXa    H               This chapter describes how to configure X.25 functionalityH               on DECnet-Plus for OpenVMS VAX systems (this functionalityB               was formerly provided by a separate product known asE               VAX P.S.I.). The functionality formerly provided by VAX I               P.S.I. is now included with the DECnet-Plus for OpenVMS VAXt               software.e  F                 ________________________ Note ________________________  C                 You must elect to install this functionality during ?                 installation of the DECnet-Plus for OpenVMS VAX -                 software (see Section 3.1.2).   F                 ______________________________________________________           8.1 Terminology   E               The terminology used in the VAX P.S.I. product has been G               replaced by the terminology used in the documentation forlG               the separate X.25 for OpenVMS product used on OpenVMS I64aH               and OpenVMS Alpha systems. Table 8-1 shows the correlationA               between VAX P.S.I. terms and their X.25 for OpenVMS                counterparts.   I               Table_8-1_X.25_Terminology_________________________________   I               VAX_P.S.I.____________X.25_for_OpenVMS_____________________   8               VAX P.S.I.            X.25 for OpenVMS VAX  6               Access system         X.25 Client system  >               Native system         X.25 Direct Connect system  I                                                  (continued on next page)   I                                      Configuring X.25 for OpenVMS VAX 8-1            (         Configuring X.25 for OpenVMS VAX         8.1 Terminology     I               Table_8-1_(Cont.)_X.25_Terminology_________________________u  I               VAX_P.S.I.____________X.25_for_OpenVMS_____________________Y  9               Multihost system      X.25 Connector systemt  I               Gateway_system________X.25_Connector_system________________o  5         8.2 Steps in Configuring X.25 for OpenVMS VAXC  F               See Figure 8-1 and take the following steps to configure<               X.25 functionality on your OpenVMS VAX system:  F               1. Plan your configuration (see the DECnet-Plus Planning/                  Guide manual and Section 8.3).   C               2. Make a list of the information you need during thed:                  configuration program, using Section 8.6.  F               3. Run the X.25 configuration program (see Section 8.4).  B               4. Run the net$configure program (in either BASIC or:                  ADVANCED mode) to configure your network.  I               5. Carry out the postconfiguration tasks: starting X.25 and >                  testing your configuration (see Section 8.7).  +         8.3 Planning the X.25 Configurationw  B               This section introduces the aspects of your proposedD               configuration that you need to consider before you run(               the configuration program.  G         8.3.1 Configuring Client, Direct Connect, and Connector Systems)  @               There are three types of X.25 for OpenVMS systems:  2               o  Client (formerly known as Access)  :               o  Direct Connect (formerly known as Native)  8               o  Connector (formerly known as Multihost)  F                 ________________________ Note ________________________  F                 The older system type names are still used by the X.25D                 configuration utility. The newer terms are used here  ,         8-2 Configuring X.25 for OpenVMS VAX r  i      I                                          Configuring X.25 for OpenVMS VAXeI                                       8.3 Planning the X.25 Configuration     D                 for compatibility with the remainder of the X.25 for*                 OpenVMS documentation set.  F                 ______________________________________________________  ?               Refer to the DECnet-Plus for OpenVMS Introductiono@               and User's Guide manual for an explanation of X.25               fundamentals.   B               The types of systems you can configure depend on theD               licenses that you have installed. Table 8-2 summarizes2               the various possible configurations.  G               Table 8-2 X.25 for OpenVMS VAX Configurations and License I               __________Requirements_____________________________________   I               Licenses________Possible_X.25_Configurations_______________w  +               DECnet-Plus     Client systemS               only  3               X.25            Direct Connect system   $               DECnet-Plus     Client,               and X.25        Direct Connect'                               Connectorr7                               Client and Direct ConnecteI               ________________Client_and_Connector_______________________a                                  I                                      Configuring X.25 for OpenVMS VAX 8-3n           (         Configuring X.25 for OpenVMS VAX+         8.4 Using the Configuration Program       +         8.4 Using the Configuration Programe  I               To configure X.25 functionality on your OpenVMS VAX system,eD               you need to run the psi$configure.com command program.  =               This program allows you to set up the permanent I               configuration database for X.25 functionality on an OpenVMSr               VAX system.e  0         8.4.1 Invoking the Configuration Program  D               To start the X.25 configuration program, log in to anyG               account that has OPER and SYSPRV privileges and enter theg               command:  *               $ @sys$manager:psi$configure           8.4.2 Common Operationso  I               The configuration program consists of a number of sections,tC               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 thenF               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 youwD               select Yes, you go through the rest of the section. IfE               you select No, you go directly to the next new section,nG               although you can decide at a later stage to complete thati*               section (See Section 8.4.5).  $         8.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 menus=                  by using the arrow keys and pressing Return.   D               o  For other questions, you type data into a field and                  press Return.  E               When you have entered all the required information on aTI               screen, a new screen appears automatically. You cannot move C               forward until you have completed the required fields.p  ,         8-4 Configuring X.25 for OpenVMS VAX t  I      I                                          Configuring X.25 for OpenVMS VAXOI                                       8.4 Using the Configuration Programi    F                 ________________________ Note ________________________  D                 The configuration program indicates it is processingC                 input by flashing the message working in the bottomn/                 left-hand corner of the screen.   F                 ______________________________________________________  "               Horizontal Scrolling  G               Usually, when you type data into a field, you can see theeE               entire field on the screen. However, in some cases, thenC               maximum length of the data you are allowed to type iseE               too long to fit into the field shown on the screen; foriF               example, a node name, which may be up to 400 characters.H               In such cases, the field scrolls horizontally as you enter               data.t  G               Note that horizontal scrolling works only if the keyboardc                is in Insert mode.                 Data Entry Moden  I               By default, each data entry screen is invoked in OverstrikeeF               mode. In this mode, any characters entered overwrite anyH               characters currently displayed in the data entry field. IfI               required, a data entry screen can be placed in Insert mode.eD               In this mode, any characters entered are inserted intoH               the characters currently displayed; any previously enteredH               characters are moved to the right. To change from one modeI               to the other, press <Ctrl/A>. The current mode is displayed F               in the upper right-hand corner of the data entry screen.  '         8.4.2.2 Moving Within a Sectionu  H               To move backward within a section, press the <Prev Screen>D               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 8.4.5).e  F               If you have moved back to look at completed screens, youG               can move forward again by pressing the <Next Screen> key.sI               Do this until you reach an incomplete screen. Then completeaB               the required fields on that screen before moving on.  I                                      Configuring X.25 for OpenVMS VAX 8-5t l  a      (         Configuring X.25 for OpenVMS VAX+         8.4 Using the Configuration Programn    %         8.4.3 Moving Between SectionsB  I               The methods available for moving between sections depend on D               whether you are creating or modifying a configuration.  I               When creating a configuration, an Options Menu is displayed H               when you complete the last data entry screen in a section.B               This menu includes options that allow you to move toE               the next uncompleted section or to move to a previously_8               completed section (via the Sections Menu):  D               o  To move to the next uncompleted section, select the4                  option "Continue to a new section".  F               o  To move to a previously completed section, select the.                  option "Go to Sections Menu".  >               Full details of the Options Menu are provided in               Section 8.4.5.  D               When modifying a configuration, a specific section canF               be selected from the Sections Menu. The Sections Menu isH               displayed automatically after you select the option ModifyG               an existing configuration script, or can be accessed from F               the Options Menu of the current section by selecting theD               option "Go to Sections Menu" (refer to Section 8.4.5).  4         8.4.4 Keys Used in the Configuration Program  C               Table 8-3 lists the keys you can use when running the $               configuration program.  F               Note that if your terminal does not support cursor keys,F               you cannot move between fields, and therefore you cannot>               run the configuration program from the terminal.  G               To use the cursor keys, you must ensure that the terminal B               device type is set correctly so that it reflects the&               terminal being emulated.  A               To set the terminal device type, enter the command:D  -               $ SET TERM/DEVICE=terminal_type   F               where terminal_type is specified as VT300, VT200, and so               on.   ,         8-6 Configuring X.25 for OpenVMS VAX    m      I                                          Configuring X.25 for OpenVMS VAXmI                                       8.4 Using the Configuration Program     F                 ________________________ Note ________________________  A                 If you intend to run the configuration program in B                 a DECterm window, the terminal type must be set to8                 VT320. To set the correct terminal type:  5                 1. Select the Options pull-down menu.S  0                 2. Select the General... option.  D                 3. Select VT300 Mode, 7--Bit Control and Terminal ID                    VT320 ID.                   4. Select OK.o  F                 ______________________________________________________  E               Table 8-3 Available Keys Used by the X.25 Configuration.I               __________Program__________________________________________   $               DEC Terminal (VT200 orI               higher)_Keys__________________Function_____________________t                 Movement Keys   G               UP and DOWN arrow keys        Moves cursor between fields   G               LEFT and RIGHT arrow keys     Moves cursor within a field   E               <Prev Screen>                 Takes you to the previouseI                                             screen in the current sectionl  H               <Next Screen>                 Takes you to the next screenB                                             in the current section  H               <Ctrl/E>                      Moves cursor to end of input1                                             fieldt  D               <Ctrl/H>                      Moves cursor to start of7                                             input fieldn                 Edit Keys   E               <Return>, <Select> or         Enters or selects a value                <Enter>   I                                                  (continued on next page)_  I                                      Configuring X.25 for OpenVMS VAX 8-7            (         Configuring X.25 for OpenVMS VAX+         8.4 Using the Configuration Programt    ?               Table 8-3 (Cont.) Available Keys Used by the X.25 I               __________________Configuration_Program____________________A  $               DEC Terminal (VT200 orI               higher)_Keys__________________Function_____________________i  I               <Remove> or <Ctrl-U>          Deletes all characters from a 1                                             field   F               <Delete>                      Deletes previous character                 Action Keysi  H               <Help>                        Provides help on the current1                                             field   G               <F9>                          Return to Program Help menuU  5               <F10>                         Exit Help   0               <F8> or <Ctrl/Z>              Quit  I               <Ctrl/A>                      Toggle Insert/Overstrike Mode   I               <Ctrl/W>______________________Redraw_screen________________   (         8.4.5 Accessing the Options Menu  E               When you leave the last screen in a section, an Optionsh               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:  ,         8-8 Configuring X.25 for OpenVMS VAX           I                                          Configuring X.25 for OpenVMS VAXtI                                       8.4 Using the Configuration Programe    -                     Continue to a new sectiona                     Add a PVCh                      Modify a PVC                      Delete a PVC'                     Go to Sections menu]  /               These options are described here.   '               Continue to a new sectiono  F               Choose this option when you finish entering or modifyingC               information in the current section. The configurationoG               program then displays the first screen in the next unseeno               section.                 Add an X  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 youc;               back to the first data entry screen for PVCs.e                 Modify an X   I               Choose this option to modify some or all of the information.4               you provided previously about an item.  I               For example, if you choose this option from the PVC OptionsnF               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 fieldsE               contain the information you provided when you first setlF               up PVC1. You can modify any of this information. Use theI               <Next Screen> key and the <Prev Screen> key to move betweenr4               screens that you do not want to alter.                 Delete an Xv  C               Choose this option to delete an item in this section.r  I               For example, if you choose this option from the PVC OptionseD               menu, a list of all PVCs defined on your system so farC               appears on the screen. Select one of these (PVC2, foreD               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 there G               you can go on to the Options menu of a different section.e  I                                      Configuring X.25 for OpenVMS VAX 8-9c e  o      (         Configuring X.25 for OpenVMS VAX+         8.4 Using the Configuration Programs             8.4.6 Obtaining Help  I               You can get help at any time during the program by pressing                the <Help> key.g  -         8.4.6.1 Obtaining Help on the Program   I               You can get help on the configuration program (for example,iH               which keys you can use or how to navigate between screens)H               by pressing the <Help> key while you are on any other Help               screen.   &         8.4.6.2 Obtaining General Help  =               If you press the <Help> key while on any of the E               introductory screens, the screen is replaced by general G               information about that section. For example, pressing the G               <Help> key while on the PVC introduction screen brings upo*               general information on PVCs.  H               You can also reach this section help from the Options menu)               for any particular section.a  A         8.4.6.3 Obtaining Help on a Specific Field or Menu Choicen  B               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 tellF               you what sort of value is expected in that field or what9               the implications are of making that choice.h  G               If you press the <Help> key again, the screen is replacedIH               by additional information about that field or menu choice.H               Press the <F10> key to leave help and return to the screen?               from which you pressed the <Help> key originally.   -         8.4.7 Creating the Configuration Filer  F               The final section in the configuration program is CreateI               the NCL Script. You are asked if you want to create the NCLo               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 alluF                  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, goi  -         8-10 Configuring X.25 for OpenVMS VAXr i         I                                          Configuring X.25 for OpenVMS VAXaI                                       8.4 Using the Configuration Programe    H                  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.a  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.   =                  You can run the command file from within the @                  configuration program, or you can exit from theF                  configuration program and run the command file later.C                  Note that you cannot start the X.25 software untiloE                  you have run this command file. This is true even if G                  you have selected not to set up X.25 security for yourA                  system.  E                  If you edit the command procedure before running it,nG                  you must make corresponding changes to the NCL scripts >                  before attempting to start the X.25 software.  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 tooG               create the NCL scripts now?" You must correct the problemi5               before you answer YES to this question.   5         8.4.8 Quitting from the Configuration Program   G                 _______________________ Caution _______________________   C                 Quitting from the configuration program deletes all A                 information entered since the NCL script was lastu@                 created or since the configuration data was lastE                 saved. This action should therefore be performed onlyc>                 if you do not want to retain the entered data.  F                 ______________________________________________________  H               To quit from the configuration program without creating an               NCL script:                  1. Press <F8>.  G                  A warning message is displayed and you are prompted to,I                  confirm that you want to quit the configuration program.n  I                                     Configuring X.25 for OpenVMS VAX 8-11            (         Configuring X.25 for OpenVMS VAX+         8.4 Using the Configuration Programh    E               2. To quit the program, enter YES. The system prompt is                   redisplayed.t  D                  To return to the program, enter NO. The screen fromE                  which you chose to quit the configuration program isI                  redisplayed.   !         8.4.9 Leaving the Programh  <               Once the configuration program has created theE               configuration file containing the NCL scripts, the Main "               Menu is redisplayed.  H               To leave the configuration program, select the option Exit               this program.   "         8.5 Configuration Sections  C               The X.25 configuration program has many sections, buttD               not all sections are relevant to all types of systems.E               Table 8-4 shows the sections that apply to each type of                system.                                               -         8-12 Configuring X.25 for OpenVMS VAX     9      I                                          Configuring X.25 for OpenVMS VAXsI                                                8.5 Configuration Sectionst    D               Table 8-4 Configuration Sections Applicable to Client,I               __________Direct_Connect,_and_Connector_Systems____________c  5                                               Appliesn0                                     Applies   toB                                     to        Direct    Applies toI               Section_______________Client?___Connect?__Connector?_______   ;               Lines and DTEs[1]     No        Yes       Yese  ;               Set Up PVCs           No        Yes       Yes   ;               Set Up Groups         No        Yes       Yesi  ;               Set Up LLC2[1]        Yes       Yes       Yes   :               Set Up Remote DTE     Yes       No        No               Classeso  ;               Choose X.29 and       Yes       Yes       Yes !               P.S.I. Mail SupportX  ;               Set Up Server         No        No        Yes                Clients   ;               Set Up Applications   Yes       Yes       Yes   ;               Set Up Templates      Yes       Yes       Yes   ;               Declaring a Network   Yes       Yes       Yesl               Process   ;               Select X.25 Security  Yes       Yes       Yes                Option  ;               Set Up Incoming       Yes       Yes       Yesc               Security for               Applications  ;               Set Up Outgoing       Yes       Yes       Yesn                Security for Local               Processes   ;               Set Up Incoming       Yes       Yes       Yes "               Security for Network               Processes.  ;               Set Up Incoming       No        No        Yese!               Security for Servery               Clients   ;               Set Up Outgoing       No        No        Yes !               Security for Clients               Systems   ;               Create the NCL        Yes       Yes       Yesy               ScriptI               [1]You_must_set_up_at_least_one_synchronous_line_and_______   I               associated DTE or at leastioneiLLC2.DTE.or OpenVMS VAX 8-13)           (         Configuring X.25 for OpenVMS VAX"         8.5 Configuration Sections    I               ___________________________________________________________A  I               The X.25 configuration program automatically skips sectionsp7               that do not apply to your type of system.e                 Lines and DTEs  @               Choose a line on your system to configure for X.25I               communications. You must configure at least one synchronous =               line unless you intend to use LLC2 exclusively.                  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 thee3               need for call clearing or call setup.t  G               Complete this section if you have requested this facility =               from your packet switching data network (PSDN).                  Groups  F               If your DTE belongs to a closed user group (CUG), it canG               communicate freely with remote DTEs that are also memberstD               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 thise&               facility from your PSDN.                 LLC2 DTEsi  G               LLC2 is a data link protocol used on LANs, over which theo6               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.b                  Remote DTE Classes  I               Use this section to specify the connector systems that yourn!               client system uses.i  -         8-14 Configuring X.25 for OpenVMS VAX            I                                          Configuring X.25 for OpenVMS VAXoI                                                8.5 Configuration Sectionso    "               X.29 and P.S.I. Mail  =               This section allows you to add support for X.2981               communications and for P.S.I. Mail.e  I               You need X.29 support if your X.25 system is to communicatet,               with character-mode terminals.  G               P.S.I. Mail is an extension of OpenVMS Mail that lets youoF               send mail messages to and receive them from other P.S.I.)               Mail systems across a PSDN.                  Server Clients  D               You must create server clients to allow your connectorI               system to pass incoming calls to the correct client system. D               A server client identifies a client system or group ofF               client systems that use this connector system to receive               incoming calls.   A               In this section, you also set up filters for server C               clients. You must set up at least one filter for eachn@               server client. See Filters for more about filters.                 Filtersn  E               Filters are sets of characteristics that can be matchedv>               to fields in an incoming call request packet. If?               the characteristics in an incoming call match theuC               characteristics you set in a filter, then the call isfG               passed to the server client or the application associated                with that filter.e  C               You must supply a filter name and a priority for eachsI               filter. You may leave all the other parameters unspecified.e  C               The more parameters you specify in a filter, the moreiB               specific the filter. To handle unexpected calls, forA               example, you could create a filter with most of itspF               parameters unspecified and with a low priority to act as.               a catchall for unexpected calls.                 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.  I                                     Configuring X.25 for OpenVMS VAX 8-15            (         Configuring X.25 for OpenVMS VAX"         8.5 Configuration Sections    H               Do not specify any applications that do not receive calls.  H               In this section, you also set up filters for applications.G               You must set up at least one filter for each application.f1               See Filters for more about filters.T                 Templatesn  C               Your system uses a template to make outgoing calls. A G               template sets various parameters for each call made usingc               that template.  H               A template called default is created automatically on your               system.e  )               Declaring a Network Process   G               X.25 and X.29 programs on your system can issue $QIO(IO$_ @               ACPCONTROL) calls to declare themselves as network               processes. Each G               $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  StaticT  G                  In this case, $QIO(IO$_ACPCONTROL) names a filter thathH                  already exists on your system. Complete this section ifG                  you want to create static filters for use by $QIO(IO$_                   ACPCONTROL).                  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 to D                  exist when the program exits. Complete this sectionC                  if you want to name the dynamic filters created byo&                  $QIO(IO$_ACPCONTROL).  I               If your programs issue only $QIO(IO$_ACPCONTROL) calls thatnF               use unnamed dynamic filters, you do not need to complete               this section.   -         8-16 Configuring X.25 for OpenVMS VAXo h         I                                          Configuring X.25 for OpenVMS VAXYI                                                8.5 Configuration Sectionse                   Security  G               This section allows you to choose to set up X.25 securitynH               to prevent unauthorized use of your X.25 system. If you doF               not set up X.25 security, any remote DTE can make a callG               to your system (provided it matches one of your filters),eH               and any user on your system can make outgoing calls to anyI               remote DTE. If you choose to set up X.25 security, you willn7               see the following five security sections.   3               o  Incoming Security for ApplicationsC  H                  You see this section only if you have an X.25 system on4                  which you have set up applications.  G                  Complete this section if you want your applications to >                  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 systemi<                  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 declareo1                  themselves as network processes.   5               o  Incoming Security for Server Clients   I                  You see this section only if you have a connector systemo9                  on which you have set up server clients.c  I                  Complete this section if you want your system to be able-:                  to pass incoming calls to client systems.                  I                                     Configuring X.25 for OpenVMS VAX 8-17  e  n      (         Configuring X.25 for OpenVMS VAX"         8.5 Configuration Sections    5               o  Outgoing Security for Client Systems   B                  You see this section only if you have a connector                  system.  I                  Complete this section if you want your system to be able D                  to make outgoing calls on behalf of client systems.                 NCL Script  I               When you are satisfied that all the information you entered H               is complete and correct, the configuration program createsE               two NCL scripts using the information you provided. See 7               Section 8.4.7 for additional information.   '         8.6 Required Configuration Data?  F               This section details the information you need to provide/               during the configuration program.t  I               Tables 8-5 to 8-20 list all the information required duringw                the configuration.  F               Table 8-5 lists the information you need to complete theB               Lines and DTEs section of the configuration program.  I               Table 8-5 Configuration Information: Lines and DTEs (Direct I               __________Connect_and_Connector_Systems_Only)______________i  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________D  ;               Select device    -              You select  -A  E               Select line      -              Supplier    4.8 Kbits/s 5               speed                           of lineP  ?               DTE name         Max. 32        You supply  DTE-n )                                charactersn  ;               DTE address      Max. 15        PSDN sub-   -w7                                digits         scriptionc6                                               informa-2                                               tion  I                                                  (continued on next page)o  -         8-18 Configuring X.25 for OpenVMS VAXi i  n      I                                          Configuring X.25 for OpenVMS VAX I                                           8.6 Required Configuration Data     I               Table 8-5 (Cont.) Configuration Information: Lines and DTEsrE                                 (Direct Connect and Connector SystemssI               __________________Only)____________________________________s  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   ;               Logical channel  Numbers or     PSDN sub-   - 7               ranges           ranges of      scriptions6                                numbers        informa-2                                               tion  ;               Profile name     As supplied    PSDN/HP     -s$                                by HP  <               Flow control     Yes or No      You select  No               negotiation[1]  <               Extended         Yes or No      You select  No               packet sequence                numbering[1]  A               Minimum packet   Decimal        You supply  Profile C               size[2]          number         (subject    dependentu5                                               to PSDNC6                                               restric-4                                               tions)  A               Maximum packet   Decimal        You supply  Profile C               size[2]          number         (subject    dependentR5                                               to PSDNh6                                               restric-4                                               tions)  A               Default packet   Decimal        You supply  ProfileeC               size             number         (subject    dependentt5                                               to PSDNd6                                               restric-4                                               tions)  I               [1]You_need_to_make_this_choice_only_if_the_profile_you____   ,               entered supports the facility.G               [2]You need to enter values here only if you chose to usea'               packet-level negotiation.c  I                                                  (continued on next page)_  I                                     Configuring X.25 for OpenVMS VAX 8-19            (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Datae    I               Table 8-5 (Cont.) Configuration Information: Lines and DTEs,E                                 (Direct Connect and Connector SystemsnI               __________________Only)____________________________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   A               Minimum window   Decimal        You supply  Profile C               size (packet     number         (subject    dependent 5               level)[2]                       to PSDNt6                                               restric-4                                               tions)  A               Maximum window   Decimal        You supply  ProfilenC               size (packet     number         (subject    dependentc5               level)[2]                       to PSDN 6                                               restric-4                                               tions)  A               Default window   Decimal        You supply  Profile C               size (packet     number         (subject    dependent 5               level)                          to PSDNe6                                               restric-4                                               tions)  =               Interface        DTE or DCE     You select  DTEO               mode[3]a  <               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)  I               [1]You_need_to_make_this_choice_only_if_the_profile_you____i  ,               entered supports the facility.G               [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 you *               entered is ISO 8208 or NPSI.  I                                                  (continued on next page)   -         8-20 Configuring X.25 for OpenVMS VAXn o  h      I                                          Configuring X.25 for OpenVMS VAXaI                                           8.6 Required Configuration Data     I               Table 8-5 (Cont.) Configuration Information: Lines and DTEs E                                 (Direct Connect and Connector SystemssI               __________________Only)____________________________________g  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   F               DTE Class        Max. 32        You supply  Profile nameI               _________________characters________________________________                                                                       I                                     Configuring X.25 for OpenVMS VAX 8-21G -  A      (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Datap    F               Table 8-6 lists the information you need to complete the8               PVCs section of the configuration program.  G               Table 8-6 Configuration Information: PVCs (Direct Connect I               __________and_Connector_Systems_Only)______________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________E  ;               Select a DTE     -              You select  -s  ?               PVC name         Max. 32        You supply  PVC-n )                                charactersn  ;               Channel number   Decimal        PSDN sub-   -o7                                number         scription 6                                               informa-2                                               tion  E               PVC packet size  Decimal        PSDN sub-   Default DTE E                                number         scription   packet size 6                                               informa-2                                               tion  E               PVC window size  Decimal        PSDN sub-   Default DTEaE                                number         scription   window size_6                                               informa-I               ________________________________tion_______________________f  F               Table 8-7 lists the information you need to complete the:               Groups section of the configuration program.  I               Table 8-7 Configuration Information: Groups (Direct Connect I               __________and_Connector_Systems_Only)______________________n  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   A               Group name       Max. 32        You supply  GROUP-n )                                charactersg  I                                                  (continued on next page).  -         8-22 Configuring X.25 for OpenVMS VAXe d  e      I                                          Configuring X.25 for OpenVMS VAX$I                                           8.6 Required Configuration Datao    I               Table 8-7 (Cont.) Configuration Information: Groups (DirectmI               __________________Connect_and_Connector_Systems_Only)______   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________o  >               Group type       BCUG or CUG    PSDN sub-   BCUG7                                               scriptiona6                                               informa-2                                               tion  ;               DTE name[1]      -              You select  -   ;               CUG number[1]    Decimal        PSDN sub-   - 7                                number         scription 6                                               informa-2                                               tion  ;               Remote DTE       Max. 15        PSDN sub-   - 7               address[2]       digits         scriptionu6                                               informa-2                                               tionI               [1]You_may_specify_more_than_one_DTE/CUG_number_pair_for___   !               groups of type CUG.iF               [2]You need to supply this information only if the Group               type is BCUG. I               ___________________________________________________________e                                I                                     Configuring X.25 for OpenVMS VAX 8-23e           (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Data     F               Table 8-8 lists the information you need to complete the8               LLC2 section of the configuration program.  D               Table 8-8 Configuration Information: LLC2 DTEs (DirectI               __________Connect_and_Connector_Systems_Only)______________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________r  ;               Choose LAN       -              You select  -                device  ?               LLC2 DTE name    Max. 32        You supply  DTE-nn)                                characters   ;               LLC2 DTE         Max. 15        You supply  - %               address          digitst  ;               Logical channel  Numbers or     PSDN sub-   -m7               ranges           ranges of      scriptions6                                numbers        informa-2                                               tion  <               Local LSAP       2 hexadecimal  You supply  7E%                                digits.  ;               Remote MAC       LAN hardware   Remote      -c4               address          address        system  <               Remote LSAP      2 hexadecimal  Remote      7E4               address          digits         system  <               Flow control     Yes or No      You select  No               negotiatione  <               Extended         Yes or No      You select  No               packet sequencem               numbering   <               Minimum packet   Decimal        You supply  16%               size[1]          numbert  >               Maximum packet   Decimal        You supply  1024%               size[1]          number_  I               [1]You_need_to_supply_these_values_only_if_you_chose_to_uses  '               packet-level negotiation.   I                                                  (continued on next page)s  -         8-24 Configuring X.25 for OpenVMS VAX            I                                          Configuring X.25 for OpenVMS VAX I                                           8.6 Required Configuration Datao    D               Table 8-8 (Cont.) Configuration Information: LLC2 DTEsE                                 (Direct Connect and Connector SystemsEI               __________________Only)____________________________________g  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________e  =               Default packet   Decimal        You supply  128x%               size             numbere  ;               Level 3 minimum  Decimal        You supply  1e%               window size      numberc               (packet                level)[1]P  ;               Level 3 maximum  Decimal        You supply  7n%               window size      numbera               (packetn               level)[1]t  ;               Level 3 default  Decimal        You supply  2m%               window size      numberc               (packet 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_uses  '               packet-level negotiation. I               ___________________________________________________________i                            I                                     Configuring X.25 for OpenVMS VAX 8-258 0         (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Dataa    F               Table 8-9 lists the information you need to complete theF               Remote DTE Classes section of the configuration program.  E               Table 8-9 Configuration Information: Remote DTE ClasseseI               __________(Client_Systems_Only)____________________________i  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________h  A               Name             Max. 32        You supply  REMOTE-iA                                characters                 CLASS-n   ;               Gateway node     Max. 6         You supply  - I               names____________characters________________________________   G               Table 8-10 lists the information you need to complete the G               X.29 and P.S.I. Mail Support section of the configuration                program.  H               Table 8-10 Configuration Information: X.29 and P.S.I. MailI               ___________Support_(All_Systems)___________________________o  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   =               X.29 support     Yes or No      You select  Yes   =               P.S.I. Mail      Yes or No      You select  Yess               support   <               P.S.I. Mail      Max. 31        You supply  No)               account user     characters                name[1]hI               [1]_You_are_asked_for_this_information_only_if_you_request_T  "               P.S.I. Mail support.I               ___________________________________________________________d  G               Table 8-11 lists the information you need to complete thetB               Server Clients section of the configuration program.      -         8-26 Configuring X.25 for OpenVMS VAX     .      I                                          Configuring X.25 for OpenVMS VAXeI                                           8.6 Required Configuration Datas    G               Table 8-11 Configuration Information: Server Client Nodes I               ___________(Connector_Systems_Only)________________________m  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   B               Name             Max. 32        You supply  CLIENT-n)                                charactersa  ;               Node name        Max. 32        You supply  -u)                                characters   ;               Filter names     Max. 32        You supply  -SI               _________________characters________________________________2                                                            I                                     Configuring X.25 for OpenVMS VAX 8-27            (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Datak    G               Table 8-12 lists the information you need to complete the @               Applications section of the configuration program.  E               Table 8-12 Configuration Information: Applications (AlltI               ___________Systems)________________________________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________a  G               Name             Max. 32        You supply  APPLICATION-ni)                                charactersi  >               Type             X.25, X.29,    You select  X.25,                                or X.29 Login  ;               Command file     OpenVMS file   You supply  - #               to start         namek               application[1]  ;               User name for                   You supply  -                application[1]  ;               Filter names     Max. 32        You supply  -C)                                charactersFI               [1]You_are_not_asked_for_this_information_if_the___________   ,               application type is X.29 loginI               ___________________________________________________________t  G               Table 8-13 lists the information you need to complete therF               Declaring a Network Process section of the configuration               program.  G               Table 8-13 Configuration Information: Declaring a NetworkdI               ___________Process_(All_Systems)___________________________E  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________l  =               Dynamic          Yes or No      You supply  Yes                filters?  I                                                  (continued on next page)t  -         8-28 Configuring X.25 for OpenVMS VAX            I                                          Configuring X.25 for OpenVMS VAXgI                                           8.6 Required Configuration Datau    G               Table 8-13 (Cont.) Configuration Information: Declaring aeI               ___________________Network_Process_(All_Systems)___________r  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________s  ;               Dynamic filter   Max. 32        You supply  - )               names            charactersT  =               Static filters?  Yes or No      You supply  Yesa  ;               Filter names     Max. 32        You supply  -fI               _________________characters________________________________a                                                              I                                     Configuring X.25 for OpenVMS VAX 8-29r m         (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Datai    F               Table 8-14 lists the information you need to supply whenI               you create filters in the Applications, Declaring a Network G               Process, and Server Clients sections of the configurationn               program.  A               Table 8-14 Configuration Information: Filters - fortI                          Applications and Network Processes (All Systems)II               ___________and_Server_Clients_(Connector_Systems_Only)______  &                                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  1_%                                number   ;               Incoming DTE     Max. 15        You supply  -t%               address          digitst  ;               Call data value  Hexadecimal    You supply  - %                                digitsn  ;               Call data mask   Hexadecimal    You supply  -o%                                digits   ;               Subaddress       Range of       You supply  -r&               range            numbers  ;               DTE class        Max. 32        You supply  - )                                charactersi  ;               Sending DTE      Max. 15        You supply  -r%               address          digits   ;               Receiving DTE    Max. 15        You supply  -N%               address          digitsh  ;               Group name       Max. 32        You supply  - )                                characters*  ;               Originally       Max. 15        You supply  -c%               called address   digitsI  I                                                  (continued on next page)i  -         8-30 Configuring X.25 for OpenVMS VAXt l  t      I                                          Configuring X.25 for OpenVMS VAXsI                                           8.6 Required Configuration Datar    I               Table 8-14 (Cont.) Configuration Information: Filters - for.H                                  Applications and Network Processes (AllG                                  Systems) and Server Clients (ConnectorgI               ___________________Systems_Only)___________________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________*  G               Redirect reason  One of:        You supply  Not specifiede,                                Not specified#                                Busy +                                Out of orderV)                                Systematic   ;               Called address   Hexadecimal    You supply  - %               extension value  digitst  ;               Called address   Hexadecimal    You supply  - %               extension mask   digitsn  ;               Called NSAP      Hexadecimal    You supply  -eI               _________________digits____________________________________p                                            I                                     Configuring X.25 for OpenVMS VAX 8-31c d  v      (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Datae    G               Table 8-15 lists the information you need to complete the =               Templates section of the configuration program.l  B               Table 8-15 Configuration Information: Templates (AllI               ___________Systems)________________________________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________;  D               Name             Max. 32        You supply  TEMPLATE-n)                                charactersT  ;               DTE class        Max. 32        You supply  - )                                charactersA  ;               Call data        Hexadecimal    You supply  - %                                digitsu  ;               Packet size      Hexadecimal    You supply  - %                                digitss  ;               Window size      Decimal        You supply  -w%                                number   ;               Destination DTE  Max. 15        You supply  -C%               address          digits   G               Fast select      One of:        You supply  Not specified ,               option           Not specified*                                Fast select,                                With response&                                No fast%                                selecte  <               Reverse          Yes or No      You supply  No               charging  ;               Selected group   Max. 32        You supply  - )                                characters   I                                                  (continued on next page)u      -         8-32 Configuring X.25 for OpenVMS VAX  A  D      I                                          Configuring X.25 for OpenVMS VAXCI                                           8.6 Required Configuration Data     E               Table 8-15 (Cont.) Configuration Information: Templates I               ___________________(All_Systems)___________________________e  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________s  @               Throughput       A range of     You supply  {0..0}*               class request    values, the,                                max. and min.+                                to be choseno$                                from:*                                0, 75, 150,(                                300, 600,*                                1200, 2400,*                                4800, 9600,+                                19200, 48000d  ;               Network user     Max. 32        You supply  - )               identity         charactersv  ;               Local            Max. 32        You supply  -v)               facilities       charactersy  <               Charging         Yes or No      You supply  No               informationT  ;               RPOA sequence    Decimal        You supply  -S%                                numberU  ;               Local            Decimal        You supply  -_%               subaddress       number_  ;               Target address   Hexadecimal    You supply  -n%               extension        digitsn  <               NSAP mapping     Yes or No      You supply  No  ;               Calling address  Hexadecimal    You supply  -_%               extension        digits   ;               Transit delay    Decimal        You supply  - %               selection        number   ;               End-to-end       Decimal        You supply  -s%               delay            number   ;               Quality of       Max. 32        You supply  - )               service          characters   I                                                  (continued on next page)o  I                                     Configuring X.25 for OpenVMS VAX 8-33p n         (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Data     E               Table 8-15 (Cont.) Configuration Information: Templates I               ___________________(All_Systems)___________________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________T  G               Expedited data   One of:        You supply  Not specifiedN,               option           Not specified"                                UseI               _________________Do_not_use________________________________                                                                     -         8-34 Configuring X.25 for OpenVMS VAX  R  S      I                                          Configuring X.25 for OpenVMS VAXEI                                           8.6 Required Configuration DataP    C               Table 8-16 lists the information you need to completeNC               the Incoming Security for Applications section of thea$               configuration program.  I               Table 8-16 Configuration Information: Incoming Security for I               ___________Applications_(All_Systems)______________________T  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   ;               Select an        -              You supply  -                applicationn  ;               DTE addresses    Max. 15        You supply  -o(               of systems that  digits[1]               can call thisy               application                only if thet               remote systemi               is charged for               the call  ;               DTE addresses    Max. 15        You supply  -y(               of systems that  digits[1]               can call thiso               applicatione               irrespective of                who pays for               the call  I               [1]The_value_required_is_a_remote_address_prefix_(RAP).____m  E               This can be a full DTE address, or it can be an addressuD               prefix, which would stand for all DTEs with an address)               beginning with this prefix.g  I                                                  (continued on next page)o              I                                     Configuring X.25 for OpenVMS VAX 8-35            (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Data     D               Table 8-16 (Cont.) Configuration Information: IncomingI               ___________________Security_for_Applications_(All_Systems)_y  &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   >               DTE addresses    Max. 15        You supply  *[2](               of systems       digits[1]               that cannott               call thisn               application-I               [1]The_value_required_is_a_remote_address_prefix_(RAP).____i  E               This can be a full DTE address, or it can be an addresstD               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 access 4               are those that you specify explicitly.I               ___________________________________________________________v                                            -         8-36 Configuring X.25 for OpenVMS VAX            I                                          Configuring X.25 for OpenVMS VAX I                                           8.6 Required Configuration Data     C               Table 8-17 lists the information you need to complete F               the Outgoing Security for Local Processes section of the$               configuration program.  I               Table 8-17 Configuration Information: Outgoing Security fornI               ___________Local_Processes_(All_Systems)___________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default_________  ;               Enter a rights   -              You supply  -                identifier  ;               DTE addresses    Max. 15        You supply  -o(               of systems       digits[1]               that can bee               called by1               processes with               this rights(               identifier only                if they pay forl               the call  ;               DTE addresses    Max. 15        You supply  - (               of systems       digits[1]               that can be                called byR               processes with               this rightsd               identifier               irrespective of                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.   I                                                  (continued on next page)       I                                     Configuring X.25 for OpenVMS VAX 8-37o g  t      (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Data_    D               Table 8-17 (Cont.) Configuration Information: OutgoingB                                  Security for Local Processes (AllI               ___________________Systems)________________________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________E  ;               Names of PVCs    Max. 32        You supply  -o)               that can be      characters                accessed byc               processes with               this rightso               identifier[3]   >               DTE addresses    Max. 15        You supply  *[2](               of systems       digits[1]               that cannot                be called by               processes with               this rightso               identifier[3]p  >               Names of PVCs    Max. 32        You supply  *[2])               that cannot      characters                be accessed by               processes with               this rightsS               identifier[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.FF               [2]The wildcard character (*) means all unspecified DTEsG               or PVCs. If you enter the wildcard character to stand fortG               DTEs or PVCs that have Remote Charge or All access, there G               is no default for these values, and the only DTEs or PVCs D               that are not allowed access are those that you specify               explicitly.nE               [3]You are asked for this information only if PVCs haveo               been set up.I               ___________________________________________________________h    -         8-38 Configuring X.25 for OpenVMS VAX     l      I                                          Configuring X.25 for OpenVMS VAX I                                           8.6 Required Configuration Data     G               Table 8-18 lists the information you need to complete theuD               Incoming Security for Network Processes section of the$               configuration program.  I               Table 8-18 Configuration Information: Incoming Security foraI               ___________Network_Processes_(All_Systems)_________________   &                                Form in6               Information      which it       Where toI               required_________is_required____find_it_____Default________   ;               Select a filter  -              You supply  -   ;               DTE addresses    Max. 15        You supply  -t(               of systems       digits[1]               that can cally               access thisa               filter only if               remote systemh               is charged for               the call  ;               DTE addresses    Max. 15        You supply  - (               of systems       digits[1]               that can accessl               this filteri               irrespective ofn               who pays for               the call  >               DTE addresses    Max. 15        You supply  *[2](               of systems that  digits[1]               cannot accesso               this filterEI               [1]The_value_required_is_a_remote_address_prefix_(RAP).____   E               This can be a full DTE address, or it can be an addressCD               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 forpG               this value, and the only DTEs that are not allowed access'4               are those that you specify explicitly.I               ___________________________________________________________i  I                                     Configuring X.25 for OpenVMS VAX 8-39g m  p      (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Datat    C               Table 8-19 lists the information you need to completefE               the Incoming Security for Server Clients section of the $               configuration program.  I               Table 8-19 Configuration Information: Incoming Security for:I               ___________Server_Clients_(Connector_Systems_Only)_________   0                                          Form in@                                          which it       Where toI               Information_required_______is_required____find_it___DefaultA  C               Select a server client     -              You       -i>                                                         supply  C               DTE addresses of systems   Max. 15        You       -n>               that can call the client   digits[1]      supply%               systems associated with %               this server client only !               if remote system is "               charged for the call  C               DTE addresses of systems   Max. 15        You       -o>               that can call the client   digits[1]      supply                systems associated%               with this server cliente&               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 associatedN%               with this server clientII               [1]The_value_required_is_a_remote_address_prefix_(RAP).____E  E               This can be a full DTE address, or it can be an addressbD               prefix, which would stand for all DTEs with an address)               beginning with this prefix. G               [2]The wildcard character (*) means all unspecified DTEs.pH               If you enter the wildcard character to stand for DTEs thatG               have Remote Charge or All access, there is no default forcG               this value, and the only DTEs that are not allowed accessg4               are those that you specify explicitly.I               ___________________________________________________________i    -         8-40 Configuring X.25 for OpenVMS VAX, d  p      I                                          Configuring X.25 for OpenVMS VAX I                                           8.6 Required Configuration Data     C               Table 8-20 lists the information you need to complete E               the Outgoing Security for Client Systems section of the $               configuration program.  I               Table 8-20 Configuration Information: Outgoing Security for I               ___________Client_Systems_(Connector_Systems_Only)_________   0                                          Form in@                                          which it       Where toI               Information_required_______is_required____find_it___Default   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 onlyo'               if the remote systems pay                for the call  C               DTE addresses of systems   Max. 15        You       - >               that can be called         digits[1]      supply#               by this client systemi&               irrespective of who pays               for the call  C               Names of PVCs that can be  Max. 32        You       -o>               accessed by this client    characters     supply               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 addresshD               prefix, which would stand for all DTEs with an address)               beginning with this prefix.nE               [3]You are asked for this information only if PVCs haveD               been set up.  I                                                  (continued on next page)       I                                     Configuring X.25 for OpenVMS VAX 8-41A s         (         Configuring X.25 for OpenVMS VAX'         8.6 Required Configuration Data1    D               Table 8-20 (Cont.) Configuration Information: OutgoingG                                  Security for Client Systems (ConnectoroI               ___________________Systems_Only)___________________________   0                                          Form in@                                          which it       Where toI               Information_required_______is_required____find_it___Defaultt  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).____t  E               This can be a full DTE address, or it can be an addressbD               prefix, which would stand for all DTEs with an address)               beginning with this prefix.iF               [2]The wildcard character (*) means all unspecified DTEsG               or PVCs. If you enter the wildcard character to stand for_G               DTEs or PVCs that have Remote Charge or All access, there G               is no default for these values, and the only DTEs or PVCs D               that are not allowed access are those that you specify               explicitly. E               [3]You are asked for this information only if PVCs have                been set up.I               ___________________________________________________________r                                -         8-42 Configuring X.25 for OpenVMS VAXc n  9      I                                          Configuring X.25 for OpenVMS VAX I                                           8.7 Verifying the Configuration     '         8.7 Verifying the Configuration   E               This section explains how to run the X.25 configuration !               test program (CTP).   F                 ________________________ Note ________________________  D                 Before you can test the X.25 configuration, you mustA                 run the net$configure configuration procedure (ineF                 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/ReceiveA                 o  Receive Onlye                 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 youro                  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 au               remote DTE.n  &         8.7.1 Preparing to Run the CTP  D               This section describes the checks you must make before               running the CTP.  !               Privileges Requirede                 o  NETMBXr                 o  TMPMBX                  o  WORLD  I                                     Configuring X.25 for OpenVMS VAX 8-43  a  e      (         Configuring X.25 for OpenVMS VAX'         8.7 Verifying the Configuration                    o  CMKRNL                  o  DETACHc                 o  SYSPRV.  $               System Quotas Required                 o  ASTLM = 100                 o  BIOLM = 100                 o  BYTLM = 40000                 o  BIOLM = 100                 o  TQELM = 30                  X.25 Software.  B               o  The X.25 optional software 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.  4                  Direct Connect or Connector system:  :                  ncl> show x25 protocol dte dte-name state                    Client system:e  3                  ncl> show node connector-node-id - 6                  _ncl> x25 protocol dte dte-name state  C                  If the status of your DTE is not shown as RUNNING,dG                  wait for 2 minutes and try again. If your DTE is still F                  not RUNNING, refer to the HP X.25 for OpenVMS Problem                   Solving manual.                 Remote Systemt  E               o  The remote system must have VAX P.S.I. V4.3 or lateri(                  configured and running.  D               o  You must know the DTE address and subaddress of the                  remote system.   -         8-44 Configuring X.25 for OpenVMS VAX            I                                          Configuring X.25 for OpenVMS VAXrI                                           8.7 Verifying the Configuratione             8.7.2 Running the CTPg  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).  -         8.7.2.1 Running the CTP Interactivelyt  *               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.   A               o  If you run the CTP in Send/Receive mode, you cancF                  test your system's ability to communicate with a PSDN;                  (loopback testing) or with remote systems.i  E               o  If you run the CTP in Receive Only mode or Send OnlyoG                  mode, you can test your system's ability to make calls 9                  to or receive calls from remote systems.a  3         8.7.2.2 Running the CTP as a Network Object   *               Enter the following command:  4               $ mcr ncl @sys$test:psi$ctp_add_netobj  G               To run the CTP as a network object automatically when you G               start the X.25 software, 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  '         8.8 Modifying the Configuration   2               To modify an existing configuration:  3               o  Run psi$configure (Section 8.4.1).   <               o  At the main menu, choose Modify an existing&                  configuration script.  I                                     Configuring X.25 for OpenVMS VAX 8-45  t  p      (         Configuring X.25 for OpenVMS VAX'         8.8 Modifying the Configurations    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 program D                 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 whenE                 you modify an existing configuration, unless you quitfD                 the program (by pressing the <F8> key) before asking,                 it to create the NCL script.  F                 ______________________________________________________  -         8.9 Creating a New X.25 Configuration   H               To delete your existing configuration and create a new set               of NCL scripts:n  7               o  Run psi$configure.com (Section 8.4.1).s  D               o  At the main menu, choose Create a new configuration                  script.                              -         8-46 Configuring X.25 for OpenVMS VAXm a  S                    I                                                                   Part IV I         _________________________________________________________________   I              Installing X.25 for OpenVMS on OpenVMS I64 and OpenVMS AlphauI                                                                   Systemso            C               Part IV describes the prerequisite steps necessary tofH               install the HP X.25 for OpenVMS software on an OpenVMS I64F               or OpenVMS Alpha system and the installation dialog usedH               to install the software. It also serves as an introductionE               to the configuration tasks discussed in the HP X.25 for +               OpenVMS Configuration manual.   1               It contains the following chapters:d  B               o  Chapter 9 - Preparing to Install X.25 for OpenVMS  9               o  Chapter 10 - Installing X.25 for OpenVMSt  F               o  Chapter 11 - X.25 Post-installation and Configuration                  Tasks O  A                    I                                                                         9rI         _________________________________________________________________*  I                                     Preparing to Install X.25 for OpenVMSy             9.1 Product Description   D               The HP X.25 for OpenVMS software enables appropriatelyF               configured systems to connect to an X.25 packet switchedD               data network (PSDN) via an X.25 relay node on the sameF               local area network (LAN), via an X.25 connector node, orF               directly using a synchronous communications device. FullI               details of the features and facilities provided by X.25 forpG               OpenVMS are provided in the Software Product Description.eD               For more conceptual information on PSDNs, refer to theC               DECnet-Plus for OpenVMS Introduction and User's Guidei               manual.t  G               Throughout the rest of this section, the product X.25 for -               OpenVMS is referred to as X.25.I  )         9.2 Locating the Distribution Kit   E               To obtain the directory location of the X.25 or OpenVMS F               kit on the CD-ROM, refer to the OpenVMS Software ProductE               Library CD-ROM User's Guide that accompanies the CD-ROM                distribution kit.o  :               Alternatively, complete the following steps:  E               1. To obtain the kit directory location of the X.25 forfF                  OpenVMS distribution files on the appropriate OpenVMSG                  Software Product Library CD-ROM (media CD-ROM), do one*"                  of the following:  H                  o  Use the CDMENU utility provided on the media CD-ROM.  F                  o  View the CD-ROM master index file on the media CD-                     ROM.    I                                 Preparing to Install X.25 for OpenVMS 9-1l s  t      -         Preparing to Install X.25 for OpenVMS_)         9.2 Locating the Distribution Kito    G                  For information about using the CDMENU utility and theiC                  CD-ROM files on the media CD-ROM, see the SoftwarerF                  Product Library CD-ROM User's Guide which accompaniesD                  the media CD-ROM distribution kit. The media CD-ROME                  user guide and CD-ROM master index file are providedsG                  as online files in the [README] directory on the first                   media CD-ROM.  B               2. To determine if the appropriate CD-ROM is alreadyE                  mounted on your system, enter the following command:f  &                  $ show device dka400:  F                 ________________________ Note ________________________  F                 The device DKA400 is used in examples in this documentC                 as the device where the appropriate CD-ROM has been                  mounted.  F                 ______________________________________________________  H               3. If the media CD-ROM containing the X.25 for OpenVMS kitE                  is not mounted, insert the appropriate CD-ROM (writecG                  down the volume label) into an available CD-ROM drive.aG                  Enter the appropriate mount command to mount the median6                  CD-ROM (omit the /FOREIGN qualifier):  &                  $ mount dka400: label  E                  where label is the volume label of the media CD-ROM.   E               4. Define the logical name PCSI$SOURCE to reference the B                  appropriate kit directory on the Software ProductC                  Library Compact Disk. For example, if the X.25 for D                  OpenVMS kit is located in the [X25020] directory on<                  device DKA400, enter the following command:  5                  $ define pcsi$source dka400:[x25020]   I               5. To verify the X.25 for OpenVMS kit name, use a directory A                  command specifying the PCSI$SOURCE logical name:_  /                  $ directory pcsi$source:*.pcsi     1         9-2 Preparing to Install X.25 for OpenVMS            I                                     Preparing to Install X.25 for OpenVMS I                                    9.3 Accessing the Online Release Notesd    .         9.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:h  @               $ product extract release_notes x25 /file=filename  G               In the above example, it is assumed that the logical nameeG               PCSI$SOURCE properly references the directory location of E               the X.25 kit. Details on how to determine the directoryaC               location of the X.25 kit are provided in Section 9.2.o  G               The product selected is displayed and you are prompted too+               continue with the extraction.s  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.   =               If you do not use the /FILE qualifier to definet<               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 notesi;                 file is located in sys$help in the form of:a  &                    x25*release_notes.*(                    wandd*release_notes.*  F                 ______________________________________________________  <         9.4 Time Required for Installation and Configuration  @               The time required to complete the X.25 for OpenVMSF               installation and configuration procedures depends on theD               configuration option used (BASIC or ADVANCED), the CPU2               type, and your system configuration.  I               The time required to install and configure X.25 for OpenVMSuB               can vary from 15 minutes to 1 hour, depending on theE               combination of choices you make from the above options.i  I                                 Preparing to Install X.25 for OpenVMS 9-3, d  d      -         Preparing to Install X.25 for OpenVMSt         9.5 Required HardwareC             9.5 Required Hardwares  D               The X.25 for OpenVMS installation process requires the!               following hardware:                  o  A CD reader                 o  A terminalr  @               You can use either a hardcopy or video terminal toB               communicate with the operating system and respond to6               prompts from the installation procedure.  B               Refer to the OpenVMS Operating System for I64, AlphaA               and VAX Software Product Description (SPD 25.01.xx)mE               for hardware requirements and processor support for theoF               hardware requirements for the X.25 for OpenVMS software.  E               If you intend to access a PSDN directly, an appropriateyH               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.  !         9.6 Prerequisite SoftwareC  B               For information about the latest version of X.25 forG               OpenVMS and its software dependences, see the HP X.25 for 9               OpenVMS Software Product Description (SPD).c  I               During the installation of X.25, the process checks for theeI               required DECnet-Plus and WANDD software. If the DECnet-PlusmE               software is not present, you are prompted to install it F               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.r            9.7 License Requirements  D               Before you run X.25 on a newly licensed node, you mustI               first register a License Product Authorization Key (License C               PAK) using the License Management Facility (LMF). The B               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 node  1         9-4 Preparing to Install X.25 for OpenVMSe p         I                                     Preparing to Install X.25 for OpenVMSsI                                                  9.7 License Requirements     B               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 softwarepD               along with X.25, review the PAK status and install theG               PAKs for any prerequisite or optional software before you                install X.25.   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.  A               o  Use X.25 over a synchronous communications line.   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) for_                  OSI transport  C               o  DECnet routing over DEC HDLC (High-level Data Linke@                  Control) over a synchronous communications line  D               The X.25 product can be installed and used on a systemC               using the PAK associated with the retired X.25 ClientuE               product. If you are installing the X.25 product on suchnH               a system, remove the X.25 Client product before installing               the X.25 product.o  H               Full details of the licensing requirements are provided inE               the Software Product Description (SPD) on the media CD.i           9.7.1 Checking Licensese  F               To determine if an X.25 license is registered, enter the$               following DCL command:  *               $ show license x25* <Return>  G               If the system does not have the required licenses, obtainCB               the Product Authorization Key (PAK) and register theG               license. For instructions on registering a license, referp?               to the OpenVMS License Management Utility Manual._  I                                 Preparing to Install X.25 for OpenVMS 9-5o e  W      -         Preparing to Install X.25 for OpenVMSs         9.8 System Requirementsa             9.8 System Requirements   I               Before you install the X.25 for OpenVMS software, make suree@               that your system meets the following requirements.           9.8.1 Disk Space  ?               Installing X.25 and WANDD on your system requiresaD               approximately 30,000 blocks of free disk storage spaceE               (15,000 blocks for OpenVMS Alpha). This figure includesu<               space to store the Release Notes in sys$help:.  G               To determine the amount of free disk space on the current I               system disk, enter the following command at the DCL prompt:s  )               $ show device sys$sysdevicer  H               If necessary, create enough free disk space to accommodate'               the installation of X.25.D                                                    1         9-6 Preparing to Install X.25 for OpenVMSd x         I                                     Preparing to Install X.25 for OpenVMSiI                                                   9.8 System Requirements     (         9.8.2 Required System Parameters  B               The X.25 for OpenVMS software shares the same systemC               parameter requirements as the DECnet-Plus for OpenVMSAG               software. See Section 1.7.3 for a list of DECnet-Plus for *               OpenVMS system requirements.  8         9.8.3 Required Privileges and Rights Identifiers  C               HP recommends that you install and configure X.25 for0E               OpenVMS from the SYSTEM account. If you are configuring A               from another account, make sure the account has thenI               following privileges and rights identifiers in place beforen               you begin.  9               Required account privileges are as follows:s                 o  CMKRNLL                 o  NETMBX                  o  SYSPRV                  o  TMPMBXe                 o  OPER                  o  SYSNAMo                 o  WORLD  F                 ________________________ Note ________________________  E                 The account cannot have the locked password (LOCKPWD)t                 flag set.a  F                 ______________________________________________________  9               Required rights identifiers are as follows:e                 o  NET$MANAGE                  o  NET$SECURITYP  F                 ________________________ Note ________________________  E                 If your account has the BYPASS privilege, then you doi;                 not need to grant these rights identifiers.,  F                 ______________________________________________________  I                                 Preparing to Install X.25 for OpenVMS 9-7u a  o      -         Preparing to Install X.25 for OpenVMS          9.8 System RequirementsA    C               To determine the default privileges of the installing B               account, log in and enter the following DCL command:  '               $ show process/privilegesb  &         9.9 Backing Up the System Disk  I               Use the OpenVMS BACKUP utility to make a copy of the systemt               disk.            9.10 Notifying Users  C               Inform users on the system that you plan to install at1               product and that they must log out.   G               First, prevent nonprivileged users from logging in to thei               system:   (               $ set logins/interactive=0  E               Next, use the reply/all command and be sure to indicateeE               the exact time you plan to begin running the POLYCENTERo9               Software Installation utility. For example:i  N               $ reply/all "Installing X.25 software at 18:00; Please log out."  I               If possible, give users an estimated time when they will bee+               able to log in to the system.o                                  1         9-8 Preparing to Install X.25 for OpenVMS  h  r                    I                                                                        10nI         _________________________________________________________________p  I                                               Installing X.25 for OpenVMSn    G               This chapter describes the tasks necessary for installinglC               the HP X.25 for OpenVMS software on an OpenVMS I64 oriF               OpenVMS Alpha system. It also describes how to display aD               list of the files installed on your system during X.25               installation.r  6         10.1 Recommended Order for Installing Software  H               The following list describes the order in which you shouldF               install the DECnet-Plus for OpenVMS and X.25 for OpenVMS               software.h  @               If you choose to install all the software productsA               at the same time, install and configure the OpenVMStD               operating system and layered products in the followingF               order, referring to the appropriate documentation. For aF               quick reference, see Figure 10-1. After OpenVMS has been5               installed, perform the following steps:   G               1. Locate the distribution kit. Access the online Release 1                  Notes. Verify required hardware.a  .                  See Sections 9.2 through 9.5.  G               2. Verify that all prerequisite software and licenses are.                  installed._  *                  See Sections 9.6 and 9.7.  G               3. Back up the system disk. Shut down all network-relatedt8                  applications and tell users to log out.  +                  See Sections 9.9 and 9.10.i  1               4. Install DECnet-Plus for OpenVMS.e  !                  See Section 3.3.   B               5. If necessary, set any required system parameters.  !                  See Section 1.7.   I                                          Installing X.25 for OpenVMS 10-1            #         Installing X.25 for OpenVMS 6         10.1 Recommended Order for Installing Software    #               6. Reboot the system.e  B               7. Install X.25 for OpenVMS and WANDD, if necessary.  0                  See Chapter 9 and this chapter.  3               8. Configure DECnet-Plus for OpenVMS.   I                  See Chapter 4 to determine which configuration option toi2                  choose: FAST, BASIC, or ADVANCED.  G                  For a FAST configuration, see Chapter 5. For BASIC and 8                  ADVANCED configurations, see Chapter 6.  ,               9. Configure X.25 for OpenVMS.  F                  See the HP X.25 for OpenVMS Configuration manual. See0                  Chapter 11 for a quick summary.  F              10. Install and configure the OSI Applications (FTAM, VT,                  and OSAK).n  /                  See Chapter 12 and Chapter 13.   (         10.2 PCSI Process Account Quotas  A               The POLYCENTER Software Installation (PCSI) utility G               requires that the installation account has, as a minimum, -               the quotas shown in Table 10-1.y  I               Table_10-1_Process_Quotas_for_the_Installing_Account_______r  I               Quota_____Value____________________________________________                  ASTLM     24                 BIOLM     18                 BYTLM     32768                  DIOLM     18                 ENQLM     200   I               FILLM_____100______________________________________________e  D               Use the OpenVMS Authorize utility to verify and changeE               process quotas for the installation account in the user$G               authorization file (sysuaf.dat). (Some sites may restrict A               the use of the OpenVMS Authorize utility to certain_"               accounts or people.)  (         10-2 Installing X.25 for OpenVMS M  l      I                                               Installing X.25 for OpenVMS I                                          10.2 PCSI Process Account Quotase    H               For example, to verify and then change the BYTLM quota forH               the account-name installation account, enter the following               command sequence:y  I               ___________________________________________________________ I               To..._______________Enter..._______________________________.  <               Invoke the          $ run sys$system:authorize               Authorize utility   7               Show the account    UAF> showaccount-namee               quotas  I               Modify the BYTLM    UAF> modify account-name /BYTLM = 32768a               quota   +               Exit from the       UAF> exita               Authorize utility   I               Log_out_____________$_logout_______________________________   I               After you verify and change the quotas for the installation E               account, log out of the installation account and log in H               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         10.3 Installing HP X.25 for OpenVMS Using PCSI  B               This section describes the steps for installing X.25H               software using the POLYCENTER Software Installation (PCSI)F               utility. You must have SYSPRV privileges on the local or=               remote node where you want to run this utility.   B               This section also provides an annotated example thatC               shows the prompt and response sequence presented whensD               the POLYCENTER Software Installation utility is run to               de-install X.25.      I                                          Installing X.25 for OpenVMS 10-3e r  t      #         Installing X.25 for OpenVMSt6         10.3 Installing HP X.25 for OpenVMS Using PCSI    7         10.3.1 X.25 for OpenVMS I64 Installation Dialogt  G               This example shows a typical prompt and response sequenceSB               when installing both the X.25 software and the WANDDH               software on an OpenVMS I64 system. It assumes that OpenVMSI               and DECnet-Plus are already installed on the target system.   <               To start the installation, follow these steps:  .               1. Log in to the SYSTEM account.  B               2. Mount the Software Products Library media CD-ROM,G                  locate the X.25 distribution directory, and define the E                  PCSI$SOURCE logical name to reference the directory.cC                  See Section 9.2 for information about locating thee"                  distribution kit.  -               3. Enter the following command:r  ,                  $ product install x25,wandd  F                  For a description of all the features you can requestI                  when starting an installation (such as purging files andtG                  using a product configuration file), refer to DCL helpl1                  for the product install command.d  F                  The actual kit location may change with new releases.C                  See Section 9.2 for information about locating ther"                  distribution kit.  F               You are then prompted for installation information as inG               the following example. In this example, numbered calloutseG               (1, 2, 3, . . . ) guide you through the sequence of steps )               that require your response.   4                $ product install wandd,x25  <Return>  7                The following product has been selected:wA                    HP I64VMS WANDD V2.0           Layered Product ?                    HP I64VMS X25 V2.0           Layered ProductP  7               1 Do you want to continue? [YES] <Return>D  /                Configuration phase starting ...n  ]                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.  ;                HP I64VMS  WANDD V2.0: X.25 V2.0 for OpenVMSo&                   - WAN Device Drivers  K                    Copyright 2005 Hewlett-Packard Development Company, L.P.   (         10-4 Installing X.25 for OpenVMS a  m      I                                               Installing X.25 for OpenVMS I                            10.3 Installing HP X.25 for OpenVMS Using PCSIr    *                    Hewlett-Packard Company  H               2 Do you want the defaults for all options? [YES] <Return>  D               3 Do you want to review the options? [NO] Yes <Return>  :                HP I64VMS WANDD V2.0: X.25 V2.0 for OpenVMS'                    - WAN Device Driversh1                    HP I64VMS VMS V8.3 [Installed]n9                    HP I64VMS DECNET_PLUS V8.3 [Installed]l  ;               4 Are you satisfied with these options? [YES]   :                HP I64VMS  X.25 V2.0: X.25 V2.0 for OpenVMS  K                    Copyright 2005 Hewlett-Packard Development Company, L.P.p  *                    Hewlett-Packard Company  H               2 Do you want the defaults for all options? [YES] <Return>  D               5    This product uses the PAKs: <X25> or <X25-CLIENT>  V                    An X.25 License PAK should be loaded before continuing installation  D               3 Do you want to review the options? [NO] YES <Return>  9                HP I64VMS X.25 V2.0: X.25 V2.0 for OpenVMSi1                    HP I64VMS VMS V8.3 [Installed]i9                    HP I64VMS DECNET_PLUS V8.3 [Installed]e>                    HP I64VMS WANDD V2.0: X.25 V2.0 for OpenVMS+                        - WAN Device Driverst$                    X.29 Support: YES1                    X.25 Relay Client Support: YES 0                    X.25 over TCP/IP Support: YES)                    X.25 Mail Support: YESh2                    X.25 Mail Default Security: YES  ;               4 Are you satisfied with these options? [YES]   +                Execution phase starting ...   8                The following products will be installed:F                    HP I64VMS WANDD V2.0                Layered ProductF                    HP I64VMS X25 V2.0                  Layered Product  \                Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%  I                                          Installing X.25 for OpenVMS 10-5n g  e      #         Installing X.25 for OpenVMS 6         10.3 Installing HP X.25 for OpenVMS Using PCSI    :                The following products have been installed:F                    HP I64VMS WANDD V2.0                Layered ProductF                    HP I64VMS X25 V2.0                  Layered Product                $  3               Notes on Prompt and Response Sequence   I               1  At this point, you can stop the installation process. IftI                  you want to continue, press Return. If you want to stop, ,                  type NO, then press Return.  ?               2  To accept the default values for the availabler4                  installation options, press Return.  D                  To enter values other than the default values, typeD                  NO and press Return. In this case, the installationF                  procedure prompts you to enter values for each of the&                  installation options.  G               3  Responding YES to this question displays the currently I                  selected values for the installation options and prompts I                  you to verify that the selections are correct. If you do I                  not want to view and confirm the options selected, press :                  Return to accept the default NO response.  D               4  Responding NO to this question causes the procedure@                  to reprompt you to enter values for each of the@                  installation options. If you are satisfied withD                  the options, press Return to accept the default YES                  response.  C               5  The X.25 License PAK must be registered and loaded F                  before X.25 can be started. Details about registeringB                  the X.25 License PAK are given in Section 9.7. 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 beF                  run manually after loading the License PAK. The WANDDB                  software does not require a separate license PAK.            (         10-6 Installing X.25 for OpenVMS           I                                               Installing X.25 for OpenVMSeI                            10.3 Installing HP X.25 for OpenVMS Using PCSI     9         10.3.2 X.25 for OpenVMS Alpha Installation Dialoga  G               This example shows a typical prompt and response sequenceeB               when installing both the X.25 software and the WANDDB               software on an OpenVMS Alpha system. It assumes thatI               OpenVMS and DECnet-Plus are already installed on the target                system.P  <               To start the installation, follow these steps:  .               1. Log in to the SYSTEM account.  B               2. Mount the Software Products Library media CD-ROM,G                  locate the X.25 distribution directory, and define thelE                  PCSI$SOURCE logical name to reference the directory.sC                  See Section 9.2 for information about locating theu"                  distribution kit.  -               3. Enter the following command:n  ,                  $ product install x25,wandd  F                  For a description of all the features you can requestI                  when starting an installation (such as purging files andoG                  using a product configuration file), refer to DCL help 1                  for the product install command.   F                  The actual kit location may change with new releases.C                  See Section 9.2 for information about locating the "                  distribution kit.  F               You are then prompted for installation information as inG               the following example. In this example, numbered calloutsdG               (1, 2, 3, . . . ) guide you through the sequence of stepsr)               that require your response.l  *                $ product install wandd,x25  7                The following product has been selected:cB                    DEC AXPVMS WANDD V2.0           Layered Product@                    DEC AXPVMS X25 V2.0           Layered Product  7               1 Do you want to continue? [YES] <Return>   /                Configuration phase starting ...r  ]                You will be asked to choose options, if any, for each selected product and forR^                any products that may be installed to satisfy software dependency requirements.  <                DEC AXPVMS  WANDD V2.0: X.25 V2.0 for OpenVMS&                   - WAN Device Drivers  I                                          Installing X.25 for OpenVMS 10-7i S  S      #         Installing X.25 for OpenVMSM6         10.3 Installing HP X.25 for OpenVMS Using PCSI    K                    Copyright 2005 Hewlett-Packard Development Company, L.P.   *                    Hewlett-Packard Company  H               2 Do you want the defaults for all options? [YES] <Return>  D               3 Do you want to review the options? [NO] Yes <Return>  ;                DEC AXPVMS WANDD V2.0: X.25 V2.0 for OpenVMS '                    - WAN Device Drivers 2                    DEC AXPVMS VMS V8.3 [Installed]9                    DEC AXPVMS DECnet_OSI V8.3 [Installed]   ;               4 Are you satisfied with these options? [YES]c  ;                DEC AXPVMS  X.25 V2.0: X.25 V2.0 for OpenVMS   K                    Copyright 2005 Hewlett-Packard Development Company, L.P.o  *                    Hewlett-Packard Company  H               2 Do you want the defaults for all options? [YES] <Return>  D               5    This product uses the PAKs: <X25> or <X25-CLIENT>  V                    An X.25 License PAK should be loaded before continuing installation  D               3 Do you want to review the options? [NO] YES <Return>  :                DEC AXPVMS X.25 V2.0: X.25 V2.0 for OpenVMS2                    DEC AXPVMS VMS V8.3 [Installed]9                    DEC AXPVMS DECnet_OSI V8.3 [Installed] ?                    DEC AXPVMS WANDD V2.0: X.25 V2.0 for OpenVMS +                        - WAN Device Drivers_$                    X.29 Support: YES1                    X.25 Relay Client Support: YES 0                    X.25 over TCP/IP Support: YES)                    X.25 Mail Support: YESe2                    X.25 Mail Default Security: YES  ;               4 Are you satisfied with these options? [YES]a  +                Execution phase starting ...e  8                The following products will be installed:G                    DEC AXPVMS WANDD V2.0                Layered ProductcG                    DEC AXPVMS X25 V2.0                  Layered Producti  \                Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%  (         10-8 Installing X.25 for OpenVMS .  _      I                                               Installing X.25 for OpenVMS I                            10.3 Installing HP X.25 for OpenVMS Using PCSIo    :                The following products have been installed:G                    DEC AXPVMS WANDD V2.0                Layered ProductaG                    DEC AXPVMS X25 V2.0                  Layered Product                 $  3               Notes on Prompt and Response Sequence   I               1  At this point, you can stop the installation process. If_I                  you want to continue, press Return. If you want to stop,g,                  type NO, then press Return.  ?               2  To accept the default values for the available 4                  installation options, press Return.  D                  To enter values other than the default values, typeD                  NO and press Return. In this case, the installationF                  procedure prompts you to enter values for each of the&                  installation options.  G               3  Responding YES to this question displays the currently I                  selected values for the installation options and prompts I                  you to verify that the selections are correct. If you dorI                  not want to view and confirm the options selected, press :                  Return to accept the default NO response.  D               4  Responding NO to this question causes the procedure@                  to reprompt you to enter values for each of the@                  installation options. If you are satisfied withD                  the options, press Return to accept the default YES                  response.  C               5  The X.25 License PAK must be registered and loaded F                  before X.25 can be started. Details about registeringB                  the X.25 License PAK are given in Section 9.7. IfE                  the X.25 License PAK is not loaded before completingNE                  the installation, X25$STARTUP (which is normally run F                  automatically at the end of the installation) must beF                  run manually after loading the License PAK. The WANDDB                  software does not require a separate license PAK.            I                                          Installing X.25 for OpenVMS 10-9i a  r      #         Installing X.25 for OpenVMS 6         10.3 Installing HP X.25 for OpenVMS Using PCSI    7         10.3.3 X.25 for OpenVMS De-Installation Exampled  G               This example shows a typical prompt and response sequenceN&               when de-installing X.25.  $               1 $ product remove x25  7                The following product has been selected: F                    DEC AXPVMS X25 V2.0                 Layered Product  6                Do you want to continue? [YES] <Return>  W                %PCSI-I-NOREF, product HP AXPVMS DECnet_OSI V8.3 is no longer referenced U                -PCSI-I-NODEP, by another product as a software dependency requirementtO                -PCSI-I-REMLP, you can remove product DEC AXPVMS DECnet_OSI V8.3t>               2 Do you want to take this action? [NO] <Return>7               3 Do you want to continue? [YES] <Return>   S                %PCSI-I-NOREF, product DEC AXPVMS WANDD V2.0 is no longer referencedUU                -PCSI-I-NODEP, by another product as a software dependency requirementCJ                -PCSI-I-REMLP, you can remove product DEC AXPVMS WANDD V2.0B               4 Do you want to take this action? [NO] yes <Return>  6                The following products will be removed:V                    DEC AXPVMS WANDD V2.0                               Layered ProductV                    DEC AXPVMS X25 V2.0                                 Layered Product  \                Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%  8                The following products have been removed:W                    DEC AXPVMS WANDD V2.0                                Layered Product_W                    DEC AXPVMS X25 V2.0                                  Layered Producti                $  3               Notes on Prompt and Response Sequence(  G               1  This command invokes the de-installation procedure forl"                  X.25 for OpenVMS.  H               2  Whenever all the dependencies on a product are removed,C                  that product can also be removed. In this example,tC                  de-installing X.25 removes all the dependencies onTF                  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,F                  type YES and press Return. Otherwise, press Return toE                  accept the default NO response and leave DECnet-Plus H                  installed on your system. This example assumes that youB                  want to leave the DECnet-Plus software installed.  )         10-10 Installing X.25 for OpenVMSl n  h      I                                               Installing X.25 for OpenVMSlI                            10.3 Installing HP X.25 for OpenVMS Using PCSI     D               3  To continue with the de-installation, press Return.D                  To terminate the de-installation, type NO and pressI                  Return. Type NO only if you decide not to de-install theC                  product.   B               4  As is the case with the DECnet-Plus software, de-D                  installing X.25 removes all the dependencies on theE                  WANDD software. You are, therefore, prompted whether B                  to remove the WANDD software in addition to X.25.D                  To remove the specified product, type YES and pressI                  Return. Otherwise, press Return to accept the default NOyH                  response and leave the WANDD software installed on yourI                  system. This example assumes that you want to remove the A                  WANDD software in addition to the X.25 software.   +         10.4 Files Installed on Your Systemo  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                                              I                                         Installing X.25 for OpenVMS 10-11g e  d                    I                                                                        11_I         _________________________________________________________________   I                            X.25 Post-Installation and Configuration Tasks     G               This chapter describes the tasks to complete after the HPgH               X.25 for OpenVMS software has been installed on an OpenVMS*               I64 or OpenVMS Alpha system.  )         11.1 Configuring X.25 for OpenVMSo  G               After X.25 has been installed, you need to configure youre               system.o  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:a  3               1. Start the net$configure procedure.e  E               2. Select Perform the entire configuration. This option C                  steps you through a complete configuration of boths&                  DECnet-Plus and X.25.  A               3. Select the defaults for each of the questions by F                  pressing Return after each question. When you see theF                  question, Do you want to configure X.25? type YES and                  press Return.  F               4. Answer YES to the next several questions, then selectF                  either the X.25 BASIC or X.25 ADVANCED configuration.  H               5. Provide responses to the questions when prompted by theE                  X.25 configuration program. This sets up your system I                  using the information given to you by your X.25 provider 9                  (the X.25 Access service you are using).   I                       X.25 Post-Installation and Configuration Tasks 11-1A L         6         X.25 Post-Installation and Configuration Tasks)         11.1 Configuring X.25 for OpenVMSI    C               6. When you have entered all the information requiredIF                  to configure your X.25 system, the X.25 configurationH                  program saves all your information in a config.dat fileA                  (for example, sys$startup:x25$basic_config.dat).   @               7. After the X.25 configuration program saves yourF                  information, the X.25 portion of the configuration isI                  complete. The X.25 configuration program then returns toeI                  the net$configure procedure, which is still in progress.N  D               8. Enter the appropriate data link and routing circuitC                  names to use when they are requested (you can also 9                  accept the defaults by pressing Return).   E               9. When the net$configure procedure asks Do you want to G                  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 Returnu"                  for the default).  A              12. Enter the template name (or press Return for ther                  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 of theI               configuration. It then redisplays the Configuration OptionstH               menu. At this point, the procedure is complete and you can               exit.m  G               Full details on how to configure the product are provided >               in the HP X.25 for OpenVMS Configuration manual.            11.2 Restart DECnet-Plus  C               You must restart DECnet-Plus before starting the X.25rF               software. To restart DECnet, enter the following command               on each node:   (               $ @sys$startup:net$startup  ;         11-2 X.25 Post-Installation and Configuration Tasksn l         I                            X.25 Post-Installation and Configuration TasksyI                                                 11.3 Rebooting the System     !         11.3 Rebooting the Systemn  E               After you have completed the required post-installation '               tasks, reboot the system.h  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  +         11.4 De-installing X.25 for OpenVMSh  I               To de-install X.25 for OpenVMS, type the following command:S  "               $ product remove x25  E               Invoking this command automatically removes the productsG               files. Complete shutdown of X.25 does not occur until theiF               system is next rebooted. An annotated example of the de-F               installation prompt and response sequence is provided in               Section 10.3.3.n  B               To invoke the shutdown procedure manually, enter the8               following command from the SYSTEM account:  -               $ @sys$startup:x25$shutdown.comn  F                 ________________________ Note ________________________  C                 You do not have to remove X.25 before re-installingsD                 the same or a different version. If a version of theE                 product exists on the system where you are attemptingeF                 to install the same or another version of the product,@                 the PCSI utility warns you that a version of theA                 product is already installed. You can then chooset:                 whether to continue with the installation.  F                 ______________________________________________________        I                       X.25 Post-Installation and Configuration Tasks 11-3                          I                                                                    Part V I         _________________________________________________________________   I                           Installing OSI Applications for OpenVMS Systemse            B               Part V describes the prerequisite steps necessary toH               install the OSI applications software and the installationH               dialog used to install the software. It also describes how8               to configure the FTAM and VT applications.  1               It contains the following chapters:r  G               o  Chapter 12 - Preparing to Install the OSI Applicationsl  =               o  Chapter 13 - Installing the OSI Applicationsf  >               o  Chapter 14 - Configuring the OSI Applications  F                 ________________________ Note ________________________  C                 DECnet-Plus must be installed and configured beforev0                 installing the OSI applications.  F                 ______________________________________________________                         I                                                                        12cI         _________________________________________________________________d  I                                 Preparing to Install the OSI Applicationso    !         12.1 Product Descriptions                  OSAK  F               Open System Application Kernel (OSAK) is the DECnet-PlusF               implementation of the Open Systems Interconnection (OSI)B               upper layers. It provides OSI Session, Presentation,B               and Application services. These services are used byE               OSI applications such as FTAM, VT, X.400, and X.500. InfE               addition, by using the OSAK programming interfaces thatrI               provide access to OSI Session, Presentation and ApplicationtF               layers, users can develop applications that layer on the:               DECnet-Plus implementation of the OSI stack.                 FTAM  A               FTAM is an OSI product that implements the OSI Filer@               Transfer, Access, and Management standard ISO 8571G               developed by the International Organization for Standards F               (ISO). Using FTAM, you can copy, append, delete, rename,D               and inspect the file attributes of local files, remote               files, or both.e                 Virtual Terminal  =               DECnet-Plus Virtual Terminal is the DECnet-Plus B               implementation of the OSI Virtual Terminal standard.D               Virtual Terminal (VT) enables applications and systemsE               supporting different types of terminals to interoperatemE               with each other. Using VT, you can use your terminal tovH               access any other system running VT, regardless of the typeG               of system. You can also use the VT gateways for access toa'               and from non-OSI systems.       I                            Preparing to Install the OSI Applications 12-1            1         Preparing to Install the OSI Applicationst*         12.2 Locating the Distribution Kit    *         12.2 Locating the Distribution Kit  E               To obtain the directory location of the DECnet-Plus kit B               on the CD-ROM, refer to the OpenVMS Software ProductE               Library CD-ROM User's Guide that accompanies the CD-ROM                distribution kit.f  :               Alternatively, complete the following steps:  H               1. To obtain the kit directory location of the DECnet-PlusG                  distribution files on the appropriate OpenVMS SoftwareHE                  Product Library CD-ROM (media CD-ROM), do one of the0                  following:   H                  o  Use the CDMENU utility provided on the media CD-ROM.  F                  o  View the CD-ROM master index file on the media CD-                     ROM.  G                  For information about using the CDMENU utility and thenC                  CD-ROM files on the media CD-ROM, see the SoftwaretF                  Product Library CD-ROM User's Guide which accompaniesD                  the media CD-ROM distribution kit. The media CD-ROME                  user guide and CD-ROM master index file are provided G                  as online files in the [README] directory on the firstn                  media CD-ROM.  B               2. To determine if the appropriate CD-ROM is alreadyE                  mounted on your system, enter the following command:,  &                  $ show device dka400:  F                 ________________________ Note ________________________  F                 The device DKA400 is used in examples in this documentC                 as the device where the appropriate CD-ROM has beeng                 mounted.  F                 ______________________________________________________  F               3. If the media CD-ROM containing the DECnet-Plus kit isG                  not mounted, insert appropriate CD-ROM (write down therD                  volume label) into an available CD-ROM drive. EnterH                  the appropriate mount command to mount the media CD-ROM/                  (omit the /FOREIGN qualifier):f  &                  $ mount dka400: label  E                  where label is the volume label of the media CD-ROM.-  6         12-2 Preparing to Install the OSI Applications           I                                 Preparing to Install the OSI Applications I                                        12.2 Locating the Distribution Kita    E               4. Define the logical name PCSI$SOURCE to reference thesB                  appropriate kit directory on the Software ProductF                  Library Compact Disk. For example, if the DECnet-PlusC                  kit is located in the [DECNETPLUS083] directory onD<                  device DKA400, enter the following command:  <                  $ define pcsi$source dka400:[decnetplus083]  D               5. To verify the DECnet-Plus kit name, use a directoryA                  command specifying the PCSI$SOURCE logical name:e  /                  $ directory pcsi$source:*.pcsiW  /         12.3 Accessing the Online Release Notes   E               The release notes for the OSI applications are providedNB               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 multipleTI               versions, as well as changes to the installation procedure.   =               To access the release notes, issue the command:   P               $ product extract release_notes decnet_osi /file=filename <Return>  G               In the above example, it is assumed that the logical nameuD               PCSI$SOURCE properly references the directory locationE               of the DECnet-Plus kit. Details on how to determine the G               directory location of the DECnet-Plus kit are provided in                Section 12.2.   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.   F                 ________________________ Note ________________________  F                 After DECnet-Plus is installed, the release notes fileD                 is located in sys$help:decnet_plus-v*.release_notes.  F                 ______________________________________________________  I                            Preparing to Install the OSI Applications 12-3D C  M      1         Preparing to Install the OSI Applications =         12.4 Time Required for Installation and ConfigurationM    =         12.4 Time Required for Installation and Configurationp  @               The time required to install and configure the OSIB               applications depends on the CPU type and your systemE               configuration. In general, the procedure should require #               less than 15 minutes.o           12.5 Required Hardware  F               The OSI applications installation procedure requires the!               following hardware:w                  o  A CD-ROM reader                 o  A terminaly  D                  You can use either a hard copy or video terminal toE                  communicate with the operating system and respond toM9                  prompts from the installation procedure.   B               Refer to the OpenVMS Operating System for I64, AlphaE               and VAX Software Product Description (SPD 25.01.xx) for E               hardware requirements and processor support for the OSIa$               applications software.  "         12.6 Prerequisite Software  G               You must use the POLYCENTER Software Installation utility D               to install the OSI applications installation kit. ThisA               utility is provided as part of the operating systemp               software.   D               To install FTAM and VT, you must first install DECnet-I               Plus, and then install OSAK. For information about softwaree<               requirements for DECnet-Plus, see Section 1.5.  H               To run the VT/Telnet gateways, you must have the HP TCP/IP<               Services for OpenVMS installed on your system.  E               For specific information about the required versions of G               prerequisite software, see the HP DECnet-Plus for OpenVMS +               Software Product Description.o      6         12-4 Preparing to Install the OSI Applications    l      I                                 Preparing to Install the OSI Applications I                                                 12.7 License Requirementsn    !         12.7 License Requirementse  E               If you are installing prerequisite or optional softwarelD               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. ThisfG               PAK also allows you to install and run the base FTAM, VT,g$               and OSAK applications.  D               To use the FTAM and VT gateways, you need the extended2               function license. The PAK names are:  4               o  For I64 and Alpha systems: DVNETEXT  *               o  For VAX systems: DVNETRTG  G               For additional information about the DECnet-Plus licensesuC               (including the Foundation Operating Environment (FOE)eC               license on OpenVMS for I64 Systems), see Section 1.6.g            12.7.1 Checking Licenses  G               To determine whether a DECnet-Plus license is registered,n.               enter the following DCL command:  ,               $ show license dvnet* <Return>  G               If the system does not have the required licenses, obtaintB               the Product Authorization Key (PAK) and register theG               license. For instructions on registering a license, refere?               to the OpenVMS License Management Utility Manual.             12.8 System Requirements  H               Before you install the OSI application software, make sure@               that your system meets the following requirements.           12.8.1 Disk Space   A               Table 12-1 shows the approximate minimum disk space B               required to install the individual OSI applications.    I                            Preparing to Install the OSI Applications 12-5m -  e      1         Preparing to Install the OSI Applicationsa          12.8 System Requirements    I               Table_12-1_Minimum_Disk_Space_Requirements_________________r  4                             Blocks for    Blocks forI               Component_____I64___________Alpha_________Blocks_for_VAX___e  >               OSAK           12300          6600          6000  >               FTAM           42700         31800         12000  >               VT              9800          3300          2000  I               TOTAL_________64800_________41700_________20,000___________s  H               To determine the number of free disk blocks on the currentI               system disk, enter the following command at the DCL prompt:   2               $ show device sys$sysdevice <Return>  H               If necessary, create enough free disk space to accommodate7               the installation of the OSI applications.0  "         12.8.2 Memory Requirements  D               To install and run the OSI applications, you must haveH               sufficient free global memory. Table 12-2 shows the global"               memory requirements:  C               Table 12-2 Required Global Pages, Global Pagelets andoI               ___________Sections________________________________________n  I               Software_I64_______________Alpha_____________VAX___________e  F               OSAK     7056 global       3296 global       1344 global@                        pagelets          pagelets          pages  D                        11 global         6 global          13 globalC                        sections          sections          sectionss  F               FTAM     29440 global      5068 global       4402 global@                        pagelets          pagelets          pages  D                        38 global         24 global         19 globalC                        sections          sections          sectionsi  E               VT       5504 global       1136 global       422 globali@                        pagelets          pagelets          pages  D                        26 global         8 global          14 globalI               _________sections__________sections__________sections______C  F               You must first find out your available system resources,F               and then use the AUTOGEN utility if you need to increase  6         12-6 Preparing to Install the OSI Applications d         I                                 Preparing to Install the OSI ApplicationssI                                                  12.8 System Requirements_    C               the global pages, global pagelets, or global sections 4               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 globalfA                  sections. The following example shows how to getyC                  this information at your terminal (the default for                   sys$output):   H                  $ write sys$output f$getsyi("contig_gblpages") <Return>                  15848F                  $ write sys$output f$getsyi("free_gblsects") <Return>                  24n  I               2. Compare the values displayed with those required for theL"                  OSI applications:  E                  o  If the values displayed by the system are greateroF                     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.  "         12.8.3 Required Privileges  >               HP recommends that you install and configure OSI>               applications from the SYSTEM account. If you areE               configuring from another account, make sure the accountlE               has the following privileges in place before you begin.f  9               Required account privileges are as follows:                  For OSAK:t                 o  CMKRNL                  o  SETPRV                  For FTAM and VT:                 o  SETPRVs  C               To determine the default privileges of the installinguB               account, log in and enter the following DCL command:  '               $ show process/privilegess  I                            Preparing to Install the OSI Applications 12-7  N         1         Preparing to Install the OSI ApplicationsC          12.8 System Requirements    8         12.8.4 Process Quotas for OSAK$SERVER_V3 Account  C               The number of available global sections on the system I               limits the number of simultaneous connect requests that the H               OSAK software can support. OSAK buffers store each connectH               request in a global section until the intended applicationF               has either accepted or rejected it or does not accept anE               inbound connection within a given period, in which case G               the OSAK software rejects the connection on behalf of the                application.  G               Table 12-3 summarizes the required process account quotase-               for the OSAK$SERVER_V3 process.   I               Table_12-3_OSAK$SERVER_V3_Process_Account_Quotas___________   I               Quota_______Value__________________________________________c  >               ASTLM       2 units for each global section + 10  5               ENQLM       1 unit for each OSI processo  I               TQELM_______2_units_for_each_global_section_+_10___________o  F                 ________________________ Note ________________________  C                 The process running the OSAK software, OSAK$SERVER_ @                 V3, is started automatically by the installationE                 procedure. Therefore, the installing account requireso?                 the process quotas shown in Table 13-1, as does A                 the SYSTEM account if you start OSAK$SERVER_V3 ini"                 systartup_vms.com.  F                 ______________________________________________________  @               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                   = 50e  I               o  For TQELM: 20 global sections multiplied by 2 units + 10i                  = 50   6         12-8 Preparing to Install the OSI Applications r  o      I                                 Preparing to Install the OSI Applications I                                                  12.8 System Requirements     F               Table 12-4 summarizes the minimum process account quotas@               required for processes that use the OSAK software.  C               Table 12-4 Account Quotas for Processes that use OSAK2I               ___________Software________________________________________   I               Quota_______Value__________________________________________                  ASTLM       10                 ENQLM       2h  I               TQELM_______10_____________________________________________   F               Users of the OSI applications also need a minimum TMPMBX$               and NETMBX privileges.  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 Authorizeo4               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 ins6               again for the new quotas to take effect.  E               For more information on modifying account quotas, refer H               to the description of the Authorize utility in the OpenVMS5               system management documentation subkit.   '         12.9 Backing Up the System Diskr  I               Use the OpenVMS BACKUP utility to make a copy of the system                disk._           12.10 Notifying Users_  C               Inform users on the system that you plan to install ao1               product and that they must log out.p  G               First, prevent nonprivileged users from logging in to thet               system:1  (               $ set logins/interactive=0  I                            Preparing to Install the OSI Applications 12-9e e  o      1         Preparing to Install the OSI Applicationst         12.10 Notifying Usersl    I               Use the reply/all command and be sure to indicate the exactfD               time you plan to begin running the POLYCENTER Software0               Installation utility. For example:  Z               $ reply/all "Installing OSI applications software at 18:00; Please log out."  I               If possible, give users an estimated time when they will be +               able to log in to the system..                                                                          7         12-10 Preparing to Install the OSI Applicationst                         I                                                                        13rI         _________________________________________________________________,  I                                           Installing the OSI Applicationsu    D               This chapter describes how to install the optional OSI3               applications. These applications are:A  /               o  OSI Applications Kernel (OSAK)e  A               o  OSI File Transfer, Access, and Management (FTAM)S  *               o  OSI Virtual Terminal (VT)  F               It also includes how to list the files installed on yourB               system during the OSI applications installation. See4               Section 13.9 for the list of commands.  F                 ________________________ Note ________________________  @                 Install the OSI applications only after you have<                 installed DECnet-Plus for OpenVMS, rebooted,?                 and configured the DECnet-Plus for OpenVMS basea                 components.   F                 ______________________________________________________  (         13.1 PCSI Process Account Quotas  H               The POLYCENTER Software Installation utility requires thatH               the installation account have the minimum the quotas shown               in Table 13-1.  I               Table_13-1_Process_Quotas_for_the_Installing_Account_______C  I               Quota_____Value____________________________________________                  ASTLM     24                 BIOLM     18  I                                                  (continued on next page)o  I                                      Installing the OSI Applications 13-1l    h      '         Installing the OSI Applicationss(         13.1 PCSI Process Account Quotas    B               Table 13-1 (Cont.) Process Quotas for the InstallingI               ___________________Account_________________________________s  I               Quota_____Value____________________________________________d                 BYTLM     32768t                 DIOLM     18                 ENQLM     200   I               FILLM_____100______________________________________________   :         13.2 Starting Installation of the OSI Applications  H               Install the OSI applications using the POLYCENTER 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                 For FTAM and VT:  '               $ product install ftam,vt                  For FTAM only:  $               $ product install ftam                 For VT only:  "               $ product install vt  ,         13.3 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 onpH                  your system, be sure to shut down any FTAM, VT, or OSAKI                  processes currently running by executing the appropriatec%                  shutdown procedures.y  ,         13-2 Installing the OSI Applications o  a      I                                           Installing the OSI ApplicationsmI                                      13.3 Installing the OSI Applicationst    F                  You must shut down FTAM and VT first, before shutting                  down OSAK.g  ,                  o  $ @sys$startup:osif$stop  *                  o  $ @sys$startup:vt_stop  ,                  o  $ @sys$startup:osak$stop  1               2. De-install the OSI applications.y  I                  If you have previously installed the OSI applications on I                  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- I                  installing OSAK. See Section 13.11 for more information.w  +               3. Mount the software CD-ROM.   I               4. Mount the Software Products Library media CD-ROM, locate]G                  the DECnet-Plus distribution directory, and define thesE                  PCSI$SOURCE logical name to reference the directory.gD                  See Section 12.2 for information about locating the"                  distribution kit.  H               5. Decide which products to install. You must install OSAKG                  before installing FTAM or VT. You can install FTAM andf2                  VT either together or separately.  I                  See Section 13.2 for the OSAK, FTAM, and VT installation                   commands.  7               6. To install FTAM and VT together, type:t  *                  $ product install ftam,vt  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 13-3            '         Installing the OSI Applications ,         13.3 Installing the OSI Applications    F               7. The POLYCENTER Software Installation utility displaysG                  the selected products and requests confirmation. PressuE                  Return to continue, or enter NO to exit. The utility 0                  enters the configuration phase.  ;                  The following products have been selected: L                      DEC AXPVMS FTAM V3.2-P                  Layered ProductL                      DEC AXPVMS VT V2.1-K                    Layered Product  8                  Do you want to continue? [YES] <Return>  1                  Configuration phase starting ...r  _                  You will be asked to choose options, if any, for each selected product and forf`                  any products that may be installed to satisfy software dependency requirements.  F               8. The POLYCENTER Software Installation utility displaysE                  the pre-installation messages for FTAM including the_G                  copyright notice, license notice, and OSAK notice, andu.                  asks if you want to continue.  [                  DEC AXPVMS FTAM V3.2-P: DECnet-Plus for OpenVMS OSI File Transfer, Access,s&                  and Management (FTAM)  M                      Copyright 2004 Hewlett-Packard Development Company, L.P.r  \                      This product uses the PAKS: DVNETEND and the Gateway requires DVNETEXT.  H                  * This product does not have any configuration options.  W                      The DECnet-Plus OSAK software must be installed and started before                   running FTAM.  <                      Do you want to continue? [YES] <Return>  F               9. The POLYCENTER Software Installation utility displaysC                  the pre-installation messages for VT including theoC                  copyright notice, license notice, OSAK notice, andaB                  gateway notice, and asks if you want to continue.  O                  DEC AXPVMS VT V2.1-K: DECnet-Plus for OpenVMS Virtual Terminal_  M                      Copyright 2004 Hewlett-Packard Development Company, L.P.p  ]                      VT requires the PAK DVNETEND, and the VT Gateways require DVNETEXT also.   H                  * This product does not have any configuration options.  N                      OSAK must be installed and started before you can run VT.  <                      Do you want to continue? [YES] <Return>  ,         13-4 Installing the OSI Applications t  s      I                                           Installing the OSI Applications I                                      13.3 Installing the OSI Applicationss    [                      VT Gateways startup requires LAT and HP TCP/IP Services started first.l  <                      Do you want to continue? [YES] <Return>  D              10. 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 I                  FTAM IVP is not run during this installation and must beh                   run separately.  -                  Execution phase starting ...f  I                  The following products will be installed to destination:uL                      DEC AXPVMS FTAM V3.2-P                  DISK$OVMSSYSTEML                      DEC AXPVMS VT V2.1-K                    DISK$OVMSSYSTEM  R                  Portion Done: 0%...10%...20%...30%...40%...70%...80%...90%...100%  <                  The following products have been installed:L                      DEC AXPVMS FTAM V3.2-P                  Layered ProductL                      DEC AXPVMS VT V2.1-K                    Layered Product  V                  %PCSI-I-IVPEXECUTE, execute test procedure for DEC AXPVMS VT V2.1 ...J                  %PCSI-I-IVPSUCCESS, test procedure completed successfully  F              11. The POLYCENTER Software Installation utility displaysB                  the post-installation messages for FTAM and listsA                  required system resources, configuration and IVPlE                  tasks you must complete, release notes location, andc$                  completion message.  [                  DEC AXPVMS FTAM V3.2-P: DECnet-Plus for OpenVMS OSI File Transfer, Access,i&                  and Management (FTAM)  X                      The following messages are informational and indicate the amount of0                      each resource used by FTAM.  K                      This product requires the following SYSGEN parameters:h+                          GBLSECTIONS add 24   K                      This product requires the following SYSGEN parameters: *                          GBLPAGES add 5068  B                      After installing DECnet-Plus FTAM you must doQ                  "$ @SYS$STARTUP:OSIF$CONFIGURE.COM" to setup necessary accounts.l  M                      The DECnet-Plus FTAM IVP may be run at any time by doingp+                  "$ @SYS$TEST:OSIF$IVP.COM"   V                      To start FTAM on your system, do "@SYS$STARTUP:OSIF$STARTUP.COM".  I                                      Installing the OSI Applications 13-5     H      '         Installing the OSI Applicationsi,         13.3 Installing the OSI Applications    R                      Release notes are available in SYS$HELP:DECNET*.RELEASE_NOTES  H                      DECnet-Plus for OpenVMS FTAM Installation Completed  F              12. The POLYCENTER Software Installation utility displaysD                  the VT post-installation messages and lists release8                  notes location, and completion message.  O                  DEC AXPVMS VT V2.1-K: DECnet-Plus for OpenVMS Virtual Terminalm  Z                      Previous VT_SYSTART.COM changes are in SYS$STARTUP:VT_SYSTART.COM_OLD  J                      You can start VT by doing "@SYS$STARTUP:VT_START.COM"  R                      Release notes are available in SYS$HELP:DECNET*.RELEASE_NOTES  T                      DECnet-Plus for OpenVMS Virtual Terminal Installation Completed  ;         13.4 Starting Up and Shutting Down OSI Applicationsf  A               The installation procedure for each OSI applicationI;               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 startupMH               file (sys$manager:systartup_vms.com) and add the followingI               command lines to the file, beginning with the OSAK command:z  G               $ @sys$startup:osak$start.com ! OSAK startup command file I               $ @sys$startup:osif$startup.com ! FTAM startup command file C               $ @sys$startup:vt_start.com ! VT startup command file   I               See Section 13.3, Step 1, for instructions on shutting down #               the OSI applications.R  9         13.5 The OSAK Installation Verification Proceduret  G               The OSAK installation verification procedure (IVP) is runyI               automatically during the installation. However, you can runD?               it at any time by entering the following command:d  "               $ @sys$test:osak_ivp  B               If the IVP runs successfully, you see the following:  C               Starting OSAK Installation Verification Procedure ...rM               OSAK Installation Verification Procedure completed successfullys  ,         13-6 Installing the OSI Applications           I                                           Installing the OSI Applications I                         13.5 The OSAK Installation Verification Procedure$    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 called4I               osak$ivp.log in the default directory, sys$test. If the IVPvF               fails during installation, you can check the log file toG               help you identify the source of the problem. You can alsotF               forward the log file to HP 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 futureC               installations.  5         13.6 Running the OSIF$CONFIGURE.COM Procedure   I               Following the FTAM POLYCENTER Software Installation utility0E               installation, you should execute the osif$configure.como>               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 the F               accounts 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 system /               where the accounts already exist:   /               $ @sys$startup:osif$configure.comoR                 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] :e  T                 The OSIT$DEFAULT and OSIGTWY accounts are present.  The OSIT$DEFAULTW                 account is useful as an account to specify when running the DECnet-PluslY                 FTAM IVP.  The OSIGTWY account is the mechanism by which users may accesspW                 the DAP/FTAM Gateway.  For more information about this Gateway, see the .                 FTAM Use and Management Guide.  I                                      Installing the OSI Applications 13-7            '         Installing the OSI Applicationse5         13.6 Running the OSIF$CONFIGURE.COM Procedure*    0                 DECnet-Plus FTAM setup complete.  8                 Would you like to run the IVP [Yes] : No  9         13.7 The FTAM Installation Verification ProcedureP  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 usingCG               the underlying OSI layers of the local system through the I               Network layer. This testing verifies that your installation*F               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.T  C               The POLYCENTER Software Installation utility does not C               automatically run the IVP. You must do this manually.   5               The DCL commands tested by the IVP are:H  /               o  COPY/APPLICATION_PROTOCOL=FTAM1  4               o  DIRECTORY/APPLICATION_PROTOCOL=FTAM  1               o  DELETE/APPLICATION_PROTOCOL=FTAMH  1               o  RENAME/APPLICATION_PROTOCOL=FTAM   )         13.7.1 Preparing for the FTAM IVP4  %               Before you run the IVP:   I               1. Ensure that the OSI transport is running and enabled. It G                  should be running if you answered YES to the Configure E                  the OSI Transport? question during the net$configure                   procedure.o  G               2. If you are running the IVP for the first time, be sure G                  to run the osif$configure.com beforehand. Instructions H                  on running this procedure are in Section 13.6. The lastF                  question in the procedure asks if you want to run the:                  IVP. To do so, type YES and press Return.    ,         13-8 Installing the OSI Applications           I                                           Installing the OSI ApplicationssI                         13.7 The FTAM Installation Verification Procedure     #         13.7.2 Running the FTAM IVPA  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 A               reasonable choice since it is configured correctly.iF               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.r  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,sP                 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,rW                 SYS$TEST:OSIF$IVP.TMP, and the second new file, SYS$LOGIN:OSIF$IVP.CPY. T                 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:r  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 13-9c C  k      '         Installing the OSI Applicationso9         13.7 The FTAM Installation Verification Proceduret    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$DEFAULTtF               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: 0   .               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.RNMlO               %RENAME-I-RENAMED, :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:lP                  "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;1n                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...   @               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.TMPf  J               %COPY-S-COPIED, SYS$COMMON:[SYSTEST]OSIF$IVP.TMP;1 copied toU               :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:"OSIT$DEFAULT password"::dC               SYS$COMMON:[OSIT$DEFAULT]GTWYFILE.TMP;1 (403 records)h  J                 $ DIR 0"OSIGTWY password"::OSINOD"OSIT$DEFAULT password"::*                     SYS$LOGIN:GTWYFILE.TMP  -               Directory 0"OSIGTWY password"::   -         13-10 Installing the OSI Applications            I                                           Installing the OSI ApplicationshI                         13.7 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.   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         13.8 The VT Installation Verification Procedurei  E               The VT installation verification procedure (IVP) is runcI               automatically during the installation. However, you can runt?               it at any time by entering the following command:t                  $ @sys$test:vt_ivp  A               If the IVP ran successfully, you see the following:   %               VT_IVP: Test successfulp  #               %IVP-S-END, IVP ended   H               If the IVP finishes with errors, you see a message similar               to this:  '               VT_IVP: <Failure message>n  #               %IVP-S-END, IVP endedi  G               In both cases, the VT software produces a log file calledoH               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 HP to assist you when%               discussing the problem.r  +         13.9 Files Installed on Your Systemg  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.   I                                     Installing the OSI Applications 13-11     e      '         Installing the OSI Applications 2         13.10 Sample OSI Application Installations    2         13.10 Sample OSI Application Installations  ;               This section provides sample OSI applicationse               installations.  (         13.10.1 Sample OSAK Installation  !               $ prod install osakA  3               Performing product kit validation ... .               %PCSI-I-VALPASSED, validation ofI               VINVIN$DKB200:[000000.KITS.SIGN_KIT]HP-I64VMS-OSAK-V0300-U-d         1.PCSI$COMPRESSED;1t               succeedede  6               The following product has been selected:H                   HP I64VMS OSAK V3.0-U                  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.n  =               HP I64VMS OSAK V3.0-U: HP OSAK V3.0 for OpenVMS   %               Copyright 2006 Hewlett-n4         Packard Development Company, L.P. All rights               reserved.i  5                   Hewlett-Packard Development Companyl  E               * This product does not have any configuration options.a  I                   OSAKserver and OSAK network management will be stopped.l  9                   Do you want to continue? [YES] <Return>   *               Execution phase starting ...  E               The following product will be installed to destination:s&                   HP I64VMS OSAK V3.0-2         U                  DISK$TEST:[VMS$COMMON.]  O               Portion done: 0%...10%...20%...30%...60%...70%...80%...90%...100%C  7               The following product has been installed: H                   HP I64VMS OSAK V3.0-U                  Layered Product  -         13-12 Installing the OSI Applicationss           I                                           Installing the OSI Applications I                                13.10 Sample OSI Application Installations                    %PCSI-I-E         IVPEXECUTE, executing test procedure for HP I64VMS OSAK V3.0-c
         U ... G               %PCSI-I-IVPSUCCESS, test procedure completed successfully   =               HP I64VMS OSAK V3.0-U: HP OSAK V3.0 for OpenVMS   Y                   OSAKserver and OSAK network management processes have not been started.o  P                   To start OSAK and OSAKserver, do "@SYS$STARTUP:OSAK$START.COM"  (         13.10.2 Sample FTAM Installation  $               $ product install ftam  3               Performing product kit validation ... .               %PCSI-I-VALPASSED, validation ofI               VINVIN$DKB200:[000000.KITS.SIGN_KIT]HP-I64VMS-FTAM-V0401-A-N         1.PCSI$COMPRESSED;1                succeededv  6               The following product has been selected:H                   HP I64VMS FTAM V4.1-A                  Layered Product  5               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.n  ,               HP I64VMS FTAM V4.1-A: DECnet-7         Plus for OpenVMS OSI File Transfer, Access, andn               Management (FTAM)u  +                    Copyright 2006 Hewlett-,)         Packard Development Company, L.P.t  Y                   This product uses the PAKS: DVNETEND and the Gateway requires DVNETEXT.a  I                   * This product does not have any configuration options.u                     The DECnet-oG         Plus OSAK software must be installed and started before runninge                   FTAM.c  9                   Do you want to continue? [YES] <Return>r  *               Execution phase starting ...  I                                     Installing the OSI Applications 13-13p a  n      '         Installing the OSI Applications 2         13.10 Sample OSI Application Installations    E               The following product will be installed to destination:o&                   HP I64VMS FTAM V4.1-2         A                  DISK$TEST:[VMS$COMMON.]  U               Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...90%...100%n  7               The following product has been installed:aH                   HP I64VMS FTAM V4.1-A                  Layered Product  ,               HP I64VMS FTAM V4.1-A: DECnet-7         Plus for OpenVMS OSI File Transfer, Access, and_               Management (FTAM)_  Z                   The following messages are informational and indicate the amount of each(                   resource used by FTAM.  H                   This product requires the following SYSGEN parameters:(                       GBLSECTIONS add 24  H                   This product requires the following SYSGEN parameters:'                       GBLPAGES add 5068   ?                   After installing DECnet-Plus FTAM you must do Q                   "$@SYS$STARTUP:OSIF$CONFIGURE.COM" to setup necessary accounts.                      The DECnet-.5         Plus FTAM IVP may be run at any time by doingo+                   "$@SYS$TEST:OSIF$IVP.COM"   U                   To start FTAM on your system, do "$ @SYS$STARTUP:OSIF$STARTUP.COM".c  J                   Release notes are available in SYS$HELP:DECNET*.RELEASE_
         NOTESs  E                   DECnet-Plus for OpenVMS FTAM Installation Completeda  4         13.10.3 Sample Virtual Terminal Installation                 $ prod install vtL  3               Performing product kit validation ... .               %PCSI-I-VALPASSED, validation ofG               VINVIN$DKB200:[000000.KITS.SIGN_KIT]HP-I64VMS-VT-V0201-K-          1.PCSI$COMPRESSED;12               succeeded   6               The following product has been selected:H                   HP I64VMS VT V2.1-K                    Layered Product  5               Do you want to continue? [YES] <Return>   .               Configuration phase starting ...  -         13-14 Installing the OSI Applications  b  _      I                                           Installing the OSI ApplicationsaI                                13.10 Sample OSI Application Installationse    \               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.n  *               HP I64VMS VT V2.1-K: DECnet-)         Plus for OpenVMS Virtual Terminal   X                   Copyright (c) Digital Equipment Corporation 1994. All rights reserved.  Z                   VT requires the PAK DVNETEND, and the VT Gateways require DVNETEXT also.  E               * This product does not have any configuration options.p  K                   OSAK must be installed and started before you can run VT.d  9                   Do you want to continue? [YES] <Return>   Y                   VT Gateways startup requires LAT and DEC TCP/IP Services started first.   9                   Do you want to continue? [YES] <Return>E  *               Execution phase starting ...  E               The following product will be installed to destination:d$                   HP I64VMS VT V2.1-4         K                    DISK$TEST:[VMS$COMMON.]  C               Portion done: 0%...40%...60%...70%...80%...90%...100%   7               The following product has been installed: H                   HP I64VMS VT V2.1-K                    Layered Product                 %PCSI-I-H         IVPEXECUTE, executing test procedure for HP I64VMS VT V2.1-K ...G               %PCSI-I-IVPSUCCESS, test procedure completed successfully   *               HP I64VMS VT V2.1-K: DECnet-)         Plus for OpenVMS Virtual Terminal2  H                   Previous VT_SYSTART.COM changes are in SYS$STARTUP:VT_         SYSTART.COM_OLD   G                   You can start VT by doing "@SYS$STARTUP:VT_START.COM"N  J                   Release notes are available in SYS$HELP:DECNET*.RELEASE_
         NOTES                      DECnet-y@         Plus for OpenVMS Virtual Terminal Installation Completed  I                                     Installing the OSI Applications 13-15c e  n      '         Installing the OSI ApplicationsN,         13.11 De-installing OSI Applications    ,         13.11 De-installing OSI Applications  I               To de-install the OSI applications, you must be logged intoeE               an account with the same privileges required to installrG               the OSI applications. See Section 12.8.3 for this list of                privileges.R  F               You may optionally shut down the OSI applications beforeD               de-installing them. See Section 13.3 for instructions.  F               Note that you must de-install FTAM and VT before you de-               install OSAK.C  B               To de-install any of the OSI applications, enter the               command:  *               $ product remove application  /               application is FTAM, VT, or OSAK._  G               Invoking this command shuts down the application if it is_F               running and removes the product files. An example of theG               de-installation response sequence for each application is (               provided in Section 13.12.  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 onn@                 the system, the POLYCENTER Software InstallationA                 utility removes it automatically before beginningo!                 the installation.   F                 ______________________________________________________  5         13.12 Sample OSI Application De-installationst  ?               This section provides sample OSI applications de-u               installations.          -         13-16 Installing the OSI Applications. e  o      I                                           Installing the OSI ApplicationsiI                             13.12 Sample OSI Application De-installationsd    7         13.12.1 Sample Virtual Terminal De-installationo  !               $ product remove vt   6               The following product has been selected:H                   DEC AXPVMS VT V2.1-K                   Layered Product  5               Do you want to continue? [YES] <Return>a  E               The following product will be removed from destination: H                   DEC AXPVMS VT V2.1-K                   DISK$OVMSSYSTEM                 Portion Done: 0%B               %PCSI-I-PRCOUTPUT, output from subprocess follows...=               %%% VT_RESPONDER is running in process 0000050Dn)               %%% Process will be stoppedn<               %%% VT_LAT_GTWY is running in process 00000518)               %%% Process will be stopped <               %%% LAT_VT_GTWY is running in process 00000519)               %%% Process will be stoppeda?               %%% VT_TELNET_GTWY is running in process 0000029E )               %%% Process will be stopped ?               %%% TELNET_VT_GTWY is running in process 0000029FC)               %%% Process will be stopped                Portion Done: 20% >               Portion Done: 50%...60%...70%...80%...90%...100%  5               The following product has been removed:.H                   DEC AXPVMS VT V2.1-K                   Layered Product  +         13.12.2 Sample FTAM De-installationi  #               $ product remove ftami  6               The following product has been selected:G                   DEC AXPVMS FTAM V4.1-A                Layered Productm  5               Do you want to continue? [YES] <Return>   E               The following product will be removed from destination: H                   DEC AXPVMS FTAM V3.2-P                 DISK$OVMSSYSTEM  O               Portion Done: 0%...20%...40%...50%...60%...70%...80%...90%...100%U  5               The following product has been removed:iH               DEC AXPVMS FTAM V3.2-P                     Layered Product  I                                     Installing the OSI Applications 13-17t c  n      '         Installing the OSI Applicationsl5         13.12 Sample OSI Application De-installationst    +         13.12.3 Sample OSAK De-installationu  #               $ product remove osaka  6               The following product has been selected:H                   DEC AXPVMS OSAK V3.0-U                 Layered Product  5               Do you want to continue? [YES] <Return>e  E               The following product will be removed from destination:cH                   DEC AXPVMS OSAK V3.0-T                 DISK$OVMSSYSTEM  $               Portion Done: 0%...20%B               %PCSI-I-PRCOUTPUT, output from subprocess follows...?               %%% OSAK$SERVER_V3 is running in process 0000054Ad)               %%% Process will be stoppedi<               %%% OSAK$NETMAN is running in process 0000054B)               %%% Process will be stopped D               Portion Done: 40%...50%...60%...70%...80%...90%...100%  5               The following product has been removed: H                   DEC AXPVMS OSAK V3.0-T                 Layered Product                                              -         13-18 Installing the OSI Applications     L                    I                                                                        14xI         _________________________________________________________________s  I                                          Configuring the OSI Applications?    F               This chapter describes how to configure FTAM and Virtual1               Terminal (VT) on an OpenVMS system.   2         14.1 FTAM and Virtual Terminal Terminology  F               o  An initiator, or client, is the program on one systemH                  that initiates a request to a program on another system'                  and awaits a response.   C               o  A responder, or server, is the program on a system G                  providing a response to a request initiated on anotheri                  system.  E               o  A listener is a job running on the responding system C                  that fulfills incoming requests from an initiatingp                  system.  6         14.2 About the OSI Application Entity Database  D               The FTAM and VT applications require you to manage theC               OSI application entity database. This database storestD               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 andF               listeners and by users who specify these aliases in FTAM               and VT commands.    I                                     Configuring the OSI Applications 14-1g    n      (         Configuring the OSI Applications6         14.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, remotenB                  applications, and local initiator source address.  C               o  Distinguished Name - X.500 Directory Service fixeda                  entries.e  D               o  Pattern - X.500 Directory Service variable entries.  I               The isoapplications database can contain any combination of                these formats.  I               For detailed information on the Address, Distinguished Name H               and Pattern formats, refer to Chapter 9 in the DECnet-PlusB               FTAM and Virtual Terminal Use and Management manual.  B         14.3 Getting Started Configuring Initiating and Responding              Entitiesu  F               This section provides basic configuration task checklistB               items and examples for setting up the initiating and-               responding systems or entities.   H               Refer to the DECnet-Plus FTAM and Virtual Terminal Use andG               Management manual for detailed information about managinga0               initiating and responding systems.  G               If you are already familiar with configuring FTAM and VT, F               you can continue the configuration procedure starting at               Section 14.4.a  -         14.3.1 Setting Up Responding Entitiest  B               On OpenVMS, the FTAM and VT installation and startupE               procedures provide default FTAM and VT responders. WhenEF               the vt_start.com and osif$startup.com command proceduresB               are run, these responders are started automatically.  -         14.3.2 Setting Up Initiating Entitiest  <               A responding entity needs to be defined in theG               isoapplications database before you can access it. To get E               the information you need for an alias, you must contacttE               the person responsible for configuring and managing theoI               remote OSI system running FTAM or VT. The remote FTAM or VTaI               implementation may be a DECnet-Plus system or a system fromu               another vendor.c  -         14-2 Configuring the OSI Applicationse a  x      I                                          Configuring the OSI Applications I       14.3 Getting Started Configuring Initiating and Responding Entitiese    G               Set up the isoapplications database for a specific remotep0               FTAM or VT application as follows:  H               1. Determine the available transports between your DECnet-F                  Plus system and the remote OSI system and select one.  C               2. Collect the information needed to define an alias.hD                  Complete the Address Format Worksheet Form shown in'                  Table 14-3 as follows:r  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.t  I                  b. Specify whether the remote application is FTAM or VT.   E                  c. Obtain the AP-title and the AE-qualifier that theaH                     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 formatnG                     of this field depends upon which transport providerw"                     you are using.  A                     o  For OSI transport: Obtain the remote NSAP.   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.o  G                  f. Specify the transport provider you selected in Stepn                     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               3. Define the alias in the isoapplications database inE                  Address format with the information you collected in I                  the prior steps. You can edit this database using a text                   editor.  I                                     Configuring the OSI Applications 14-3            (         Configuring the OSI ApplicationsK         14.3 Getting Started Configuring Initiating and Responding Entitiese    B               Once the setup is complete, you can invoke initiator'               requests using the alias.   4         14.3.3 Example: Performing an FTAM File Copy  E               Use the task list from Section 14.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 no )               setup required on System-A.e  D               Using information collected in Section 14.3.2, performF               the following steps on initiating entity System-B from a!               privileged account:   H               1. Determine available transports and choose one. For this,                  example, use OSI transport.  -               2. Perform the following steps:f  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 onr/                     OpenVMS uses RMS.FTAM.OSIF.a  =                  e. Obtain the remote NSAP. For this example,f9                     the responder's OSI transport NSAP is +                     %X410004AA000400001321.   -         14-4 Configuring the OSI Applications            I                                          Configuring the OSI Applications I       14.3 Getting Started Configuring Initiating and Responding Entities     E                  f. Specify transport provider. For this example, use G                     OSI. Note that because OSI is the default provider,f5                     you can omit it for this example.   G                  g. Determine the transport template. For this example, I                     use default. Note that because default is the default ?                     template, you can omit it for this example.n  B               3. Define the alias in the isoapplications database:  9                  system_a_alias  :FTAM:::RMS.FTAM.OSIF. \rB                                          %X410004AA000400001321, \G                                          provider=osi,template=default:   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>  ;         14.3.4 Example: Performing a Virtual Terminal Loginx  E               Use the task list from Section 14.3.2 to configure youra9               system to perform a Virtual Terminal login.   I               In this example, you perform a VT set host/vtp from System-                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 accountt(               information from System-A:  .               username: system_a_user <Return>-               password: system_a_pwd <Return>   I               Use the default VT responder on responding entity System-A. 5               There is no setup required on System-A.   D               Using the information from Section 14.3.2, perform theB               following steps on initiating entity System-B from a!               privileged account:t  H               1. Determine available transports and choose one. For this'                  example, use RFC 1006.   I                                     Configuring the OSI Applications 14-5  s  w      (         Configuring the OSI ApplicationsK         14.3 Getting Started Configuring Initiating and Responding Entitiesi    -               2. Perform the following steps:p  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 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 OpenVMS .                     uses %x0001.%x0001.%x0002.  A                  e. Obtain the remote NSAP. For this example, thepG                     responder's RFC 1006 internet address is 16.20.8.42b/                     and the daemon port is 102.a  I                  f. Specify transport provider. For this example, use RFCp                     1006.   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.  B               3. Define the alias in the isoapplications database:  >                  system_a_alias  :VT:::%x0001.%x0001.%x0002. \9                                         16.20.8.42.102, \ 9                                         provider=rfc1006:   C               After the setup is complete, you can start the VT set                host/vtp command:A  5               $ set host/vtp system_a_alias  <Return>   0               Username:  SYSTEM_A_USER  <Return>/               Password:  system_a_pwd  <Return>           -         14-6 Configuring the OSI ApplicationsT N  e      I                                          Configuring the OSI ApplicationsoI                                            14.4 About Responding Entitiesr    &         14.4 About Responding Entities  I               As stated in Section 14.3.1, default FTAM and VT responders H               are provided on OpenVMS. The installation also supplies anI               initial isoapplications database with local aliases used by C               the FTAM and VT responders, gateways, and initiators.   G               Table 14-1 shows default addresses (PSEL, SSEL, TSEL) fora6               the FTAM and VT responders and gateways:  I               Table_14-1_Default_Addresses_______________________________p  I               Gateway/Responder_______Default_Address_____________________  3               FTAM Responder          RMS.FTAM.OSIF   :               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 and G               change the local addresses (PSEL, SSEL, TSEL) that the VTtE               responder and gateways use. For these operations, refer.F               to Chapter 10 and Chapter 11 in the DECnet-Plus FTAM and9               Virtual Terminal Use and Management manual.   F         14.5 Configuring Addresses for Remote FTAM and VT Applications  I               The primary job of configuring FTAM and VT on OpenVMS is toaH               add entries to the isoapplications database for the remoteG               FTAM and VT applications on your network. On OpenVMS, you I               add entries to the isoapplications database by using a textn               editor.e  D               Refer to Chapter 9 in the DECnet-Plus FTAM and Virtual?               Terminal Use and Management manual for a complete C               description of managing the isoapplications database.   I                                     Configuring the OSI Applications 14-7P a  :      (         Configuring the OSI ApplicationsF         14.5 Configuring Addresses for Remote FTAM and VT Applications    >               As mentioned in Section 14.2, every entry in theI               isoapplications database has one of three database formats:t                 o  Address formatt  *               o  Distinguished Name format                 o  Pattern formatv  A               If you have the DEC X.500 Directory Service product E               installed, you have the option of adding entries of thelC               Distinguished Name format and the Pattern format. YousE               have the option of adding entries of the Address formatl7               regardless of whether X.500 is installed.e  D               If you are not using X.500, complete an Address Format>               Worksheet as shown in Table 14-3 for each remoteI               application. If you are using X.500, complete the checklista               in Table 14-2.  A               To complete the Address Format Worksheet forms, seenH               Section 14.3.2 for instructions on collecting the relevant               information.                                            -         14-8 Configuring the OSI Applicationsd i         I                                          Configuring the OSI Applications I            14.5 Configuring Addresses for Remote FTAM and VT Applications     I               Table_14-2_X.500_Configuration_Checklist___________________   I               Question_______________________________________Yes__No_____   F               Do you want to register the local listeners    <  > <  >%               in the X.500 Directory?   :               If yes, you need an X.500 Distinguished Name6               to identify each of the local listeners.9               Specify a Distinguished Name for each localo               listener.n  S               o  X.500 Distinguished Names: ________________________________________  R                  _________________________________________________________________  I               ___________________________________________________________e  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.e  I               ___________________________________________________________i  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: ________________________________________________e  *               o  Application (FTAM or VT):  5                  ____________________________________   $               o  Distinguished Name:  9                  ________________________________________   )               o  Transport Template List:   6                  _____________________________________  I               ___________________________________________________________n  I                                                  (continued on next page)n  I                                     Configuring the OSI Applications 14-95 n  u      (         Configuring the OSI ApplicationsF         14.5 Configuring Addresses for Remote FTAM and VT Applications    I               Table_14-2_(Cont.)_X.500_Configuration_Checklist___________   I               Question_______________________________________Yes__No_____o  F               Do you want to add entries of the Pattern      <  > <  >               format?   5               If yes, you need to determine what yourc(               patterns should look like.  :               You may be able to get this information from7               your network administrator, or you may bey6               able to use the DEC X.500 Administration8               Utility (DXIM) to examine the structure of;               the X.500 Directory Information Tree for youri9               organization to determine what your Patterne'               format entries should be.   9               Complete the following information for eachi:               pattern entry. The Distinguished Name should5               be incomplete (contain at least one *).e  *               o  Application (FTAM or VT):  5                  ____________________________________   $               o  Distinguished Name:  9                  _________________________________________  )               o  Transport Template List:_  6                  _____________________________________  I               ___________________________________________________________   F               Do you want to add entries of the Address      <  > <  >               format?   ;               If yes, complete the form shown in Table 14-3nI               for_each_remote_application._______________________________I        .         14-10 Configuring the OSI Applications s  l      I                                          Configuring the OSI Applications I            14.5 Configuring Addresses for Remote FTAM and VT Applicationse    I         Table_14-3_Address_Format_Worksheet______________________________e           Configuration I         Information___________Answer/Entry_______________________________m  X         Alias name:           <                                                        >  X         Application (FTAM or  <                                                        >         VT):  X         AP-title:             <                                                        >      X         AE-qualifier:         <                                                        >    X         PSEL:                 <                                                        >    X         SSEL:                 <                                                        >    X         TSEL:                 <                                                        >      X         NSAPs:                <                                                        >    X         Transport provider    <                                                        >         names:  X         Transport template    <                                                        >         names:  I         _________________________________________________________________h                I                                    Configuring the OSI Applications 14-11a C  d      (         Configuring the OSI ApplicationsF         14.5 Configuring Addresses for Remote FTAM and VT Applications    ,         14.5.1 Adding Address Format Entries  @               Refer to Section 9.2.1 in the DECnet-Plus FTAM andG               Virtual Terminal Use and Management manual for a completehC               description of Address format entries. Entries of theo5               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 FormatiG               Worksheet to add the Address format entries. For example, @               an Address format entry for VT could look like the               following:  L               remote1 :VT:::psap.ssap.tsap.%x4145418715004108002B23569821, \I                                            provider=osi,template=default:s  C               Note that you can enter more than one NSAP per alias.r  7         14.5.2 Adding Distinguished Name Format EntriesP  @               Refer to Section 9.2.2 in the DECnet-Plus FTAM andG               Virtual Terminal Use and Management manual for a completehG               description of Distinguished Name entries. Entries of thei@               Distinguished Name format take the following form:  I               alias   :application:template_list:x500_distinguished_name:l  D               Use the information you completed in the configurationI               checklist to add the Distinguished Name format entries. FortG               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:  ,         14.5.3 Adding Pattern Format Entries  @               Refer to Section 9.2.3 in the DECnet-Plus FTAM andG               Virtual Terminal Use and Management manual for a complete C               description of Pattern format entries. Entries of the 5               Pattern format take the following form:   K               *   :application:template_list:incomplete_distinguished_name:y  .         14-12 Configuring the OSI Applications e  r      I                                          Configuring the OSI Applications I            14.5 Configuring Addresses for Remote FTAM and VT Applicationst    ;               You need only one Pattern format entry in theoD               isoapplications database for each application (FTAM orI               VT). Use the information you completed in the configuration :               checklist to add the Pattern format entries.  @               For example, the aliases passed to the FTAM and VTG               commands could correspond to the value of the common namedG               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:  :         14.6 Registering Responders in the X.500 Directory  G               If you have DEC X.500 Directory Service available to you, G               you have the option of storing the addresses of the local E               FTAM and VT responders in the X.500 Directory database.nD               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 yourfE               local FTAM responder on node srchr, assuming that srchrmG               already exists in the database as an application process:S  Z               dxim> create /c=us/o=local_org/ou=local_org_unit/cn=srchr/cn=ftam - <Return>I               _dxim> attributes objectclass=applicationentity, - <Return>e]               _dxim> presentationaddress="RMS"/"FTAM"/"OSIF"/NS+410004AA000400001321 <Return>                               I                                    Configuring the OSI Applications 14-13n    v                    I                                                                   Part VI I         _________________________________________________________________o  I                                           Supplemental Reference Material             H               Part VI contains supplemental reference information usefulB               to the installation and configuration procedures for               DECnet-Plus.  3               It contains the following appendixes:   D               o  Appendix A - System Files Loaded During DECnet-Plus                  Installation   D               o  Appendix B - Supplemental Name Services Information  F               o  Appendix C - Configuring OSI Transport Over X.25 CONS  H               o  Appendix D - Configuring Link State Routing Nodes Using-                  the ISIS$CONFIGURE Procedurel e  s                    I                                                                         A I         _________________________________________________________________   I                       System Files Loaded During DECnet-Plus InstallationA    I               This appendix lists the system files that are placed on the H               system or copied to the system disk during the DECnet-Plus%               installation procedure.e  B               The following table lists the files according to the3               directory into which they are copied._                                                            I                   System Files Loaded During DECnet-Plus Installation A-1r h  o      ;         System Files Loaded During DECnet-Plus Installationl    I         _________________________________________________________________eI         Directory/Files__________________________________________________6           [SYS$LDR]   <         LES$CHECK_LICENSE.EXE                LES$LES_V30.EXE  >         LES$NETMAN.EXE                       LES$NETMANLDR.EXE  :         LES$PROFILE.EXE                      NET$ALIAS.EXE  ;         NET$ALIAS.STB                        NET$DRIVER.EXE_  E         NET$DRIVER.STB                       NET$LOOP_APPLICATION.EXEt  :         NET$MOPS0.EXE                        NET$MOPS0.STB  =         NET$OSDRIVER.EXE                     NET$OSDRIVER.STBu  :         NET$OSVCM.EXE                        NET$OSVCM.STB  ?         NET$ROUTING_ES.EXE                   NET$ROUTING_ES.STB   D         NET$ROUTING_VCM.EXE                  NET$SESSION_CONTROL.EXE  ;         NET$SESSION_CONTROL.STB              NET$TPCONS.EXEo  ;         NET$TPCONS.STB                       NET$TRACER.EXEe  B         NET$TRANSPORT_NSP.EXE                NET$TRANSPORT_NSP.STB  B         NET$TRANSPORT_OSI.EXE                NET$TRANSPORT_OSI.STB  B         SYS$NAME_SERVICES.EXE                SYS$NAME_SERVICES.STB  <         SYS$NETWORK_SERVICES.STB             NET$MESSAGE.EXE  E         NET$ROUTING_IS.EXE                   SYS$NETWORK_SERVICES.EXEo           [SYS$STARTUP]   A         DNS$CLERK_STARTUP_V.COM              DNS$CLERK_STOP_V.COMl  @         DTSS$STARTUP.COM                     NET$LES_STARTUP.COM  <         NET$ROUTING_STARTUP.COM              NET$STARTUP.COM           [SYSEXE]  :         ALIAS$SYMBOLS.STB                    CDI$TRACE.EXE  4         CDI_CACHE_DUMP.EXE                   CML.EXE  ;         CTF$DCP.EXE                          CTF$SERVER.EXE   7         CTF$SYMBOLS.STB                      CTF$UI.EXEi  D         CTI$SYMBOLS.STB                      DECNET_LOC_REGISTER.EXE  D         DECNET_REGISTER.EXE                  DECNET_REGISTER_LNO.EXE  >         DNS$ADVER_V.EXE                      DNS$ANALYZE_V.EXE  ?         A-2 System Files Loaded During DECnet-Plus Installationg e         I                       System Files Loaded During DECnet-Plus Installation     I         _________________________________________________________________tI         Directory/Files___________________________________________________  <         DNS$CONFIGURE.EXE                    DNS$CONTROL.EXE  6         DNSBROWSER.EXE                       DNSCP.BPT  :         DNSCP.MBF                            DSMDECDNS.EXE  B         DTSS$SERVICE.EXE                     DTSS$SET_TIMEZONE.EXE  <         ESIS$SYMBOLS.STB                     LES$ACP_V30.COM  >         LES$ACP_V30.EXE                      LES$FINDPTMAX.EXE  4         LES$STARTUP_V30.EXE                  NCL.EXE  8         NET$ACP.EXE                          NET$ACP.STB  :         NET$CCR.EXE                          NET$DEBUG.EXE  @         NET$EVENT_DISPATCHER.EXE             NET$LES_CONTROL.DAT  9         NET$LOAD.EXE                         NET$MGMT.EXE   8         NET$MIRROR.EXE                       NET$MOP.EXE  @         NET$MOP.STB                          NET$QIO_SYMBOLS.STB  ;         NET$SERVER.COM                       NET$SERVER.EXEe  >         NET$SYMBOLS.STB                      NSPTP$SYMBOLS.STB  >         OSITP$SYMBOLS.STB                    OSVCM$SYMBOLS.STB  ?         SCL$SYMBOLS.STB                      TPCONS$SYMBOLS.STB   4         CTF$CONFIG.EXE                       NCP.EXE            [SYSHLP.EXAMPLES.DNVOSI]  $         DNS_ADD_VALUE_TO_ATTRIBUTE.C  !         [SYSHLP.EXAMPLES.DNVPLUS]   9         DNS_CREATE_OBJECT.C                  IPC_SERVER.Ce  @         DNS_READ_ATTRIBUTE.C                 IPC_BACKTRANSLATE.C  9         IPC_BUILD.COM                        IPC_CLIENT.Cr  6         IPC_COMMON.C                         IPC_DEF.H           [SYSHLP.EXAMPLES]   6         CX.C                                 NSAPS.DAT  B         OSIT$CMD_EXECUTOR.COM                OSIT$CMD_EXECUTOR.MAR  @         OSIT$CMD_SOURCE.CLD                  OSIT$CMD_SOURCE.MAR  I                   System Files Loaded During DECnet-Plus Installation A-3            ;         System Files Loaded During DECnet-Plus Installationo    I         _________________________________________________________________ I         Directory/Files__________________________________________________   :         OSIT$ECHO.FOR                        OSIT$RANDOM.C  G         OSIT$RECEIVER.PAS                    OSIT$RECORD_STRUCTURES.FOR   A         OSIT$STORAGE.FOR                     OSIT$TRANSMITTER.PAS*  3         SETUP_NCL_KEYPAD.COM                 SUBX.Cn  6         SX.C                                 VMS_OSI.H  =         XTIUTIL.C                            XTI_EXAMPLES.COM            [SYSHLP]  D         CTF$HELP.HLB                         DECNET_LOC_REGISTER.HLB  I         DECNET_MIGRATE.HLB                   DECNET_REGISTER_COMMANDS.HLBp  ;         DECNET_REGISTER_FORMS.HLB            DNS$CPHELP.HLBr  <         DSMDECDNS.DECW$BOOK                  LES$SDAHELP.HLB  C         NCLHELP.HLB                          NET$CONFIGURE_HELP.HLB   8         NET$MGMT_HELP.HLB                    NET$SDA.HLB  &         DECNET-PLUS-V8_2.RELEASE_NOTES                                ?         A-4 System Files Loaded During DECnet-Plus InstallationN U  I      I                       System Files Loaded During DECnet-Plus Installationl                 [SYSLIB]  8         CDI$SHR.EXE                          CDI$SHR.STB  B         CML.OLB                              CTF$ALIAS_ANALYZE.EXE  @         CTF$CSMA-CD_TRACEPOINTS.DAT          CTF$CTI_ANALYZE.EXE  @         CTF$DECNET_TRACEPOINTS.DAT           CTF$DNA_ANALYZE.EXE  D         CTF$DUMP_ANALYZE.EXE                 CTF$ESEVENT_ANALYZE.EXE  E         CTF$IEEE8022_ANALYZE.EXE             CTF$IEEE8023_ANALYZE.EXE   =         CTF$KEY.INIT                         CTF$KEY.TEMPLATEt  B         CTF$MOP_ANALYZE.EXE                  CTF$NSPTP_ANALYZE.EXE  D         CTF$NSP_ANALYZE.EXE                  CTF$NSP_TRACEPOINTS.DAT  B         CTF$OSITP_ANALYZE.EXE                CTF$OSVCM_ANALYZE.EXE  H         CTF$ROUTING_ANALYZE.EXE              CTF$ROUTING_TRACEPOINTS.DAT  C         CTF$SCL_ANALYZE.EXE                  CTF$TPCONS_ANALYZE.EXEf  :         CTF$VOTS_ANALYZE.EXE                 DNS$RTL_V.EXE  9         DNSDEF_V.ADA                         DNSDEF_V.BAS   7         DNSDEF_V.FOR                         DNSDEF_V.Hg  9         DNSDEF_V.MAR                         DNSDEF_V.PAS   9         DNSDEF_V.PLI                         DNSDEF_V.R32   9         DNSMSG_V.ADA                         DNSMSG_V.BASe  7         DNSMSG_V.FOR                         DNSMSG_V.Ht  9         DNSMSG_V.MAR                         DNSMSG_V.PASl  9         DNSMSG_V.PLI                         DNSMSG_V.R32h  :         DSMDECDNS.DAT                        DSMDECDNS.UID  9         DTSS$RUNDOWN.EXE                     DTSS$SHR.EXE   A         DTSS$SHRD.EXE                        LES$ACP_CODE_V30.EXE   8         LES$NETMANSHR.EXE                    LES$SDA.EXE  7         NCL$GLOBALSECTION.DAT                NCLSHR.EXEp  H         NET$CMISE.EXE                        NET$EVD_RELAY_FORMATTER.EXE  >         NET$NISCS_LAA.EXE                    NET$NISCS_LAA.STB  C         NET$PROCESS_EMAA.EXE                 NET$ROUTING_ACPSHR.EXEr  8         NET$SDA.EXE                          NET_CMISE.H  >         NET_EXTERNALS.ADA                    NET_EXTERNALS.BAS  I                   System Files Loaded During DECnet-Plus Installation A-5            ;         System Files Loaded During DECnet-Plus Installation     I         _________________________________________________________________tI         Directory/Files__________________________________________________e  <         NET_EXTERNALS.FOR                    NET_EXTERNALS.H  >         NET_EXTERNALS.L32                    NET_EXTERNALS.MLB  >         NET_EXTERNALS.PAS                    NET_EXTERNALS.PLI  =         OSIT$LIBRARY.EXE                     OSIT$LIBRARY.OLB   5         OSIT.ADA                             OSIT.FOR   5         OSIT.H                               OSIT.L32   5         OSIT.MAR                             OSIT.MLBe  5         OSIT.PAS                             OSIT.PENc  5         OSIT.PLI                             OSIT.R32r  2         OSIT.SDI                             UTC.H  ;         XTI$DNETSHR.EXE                      XTI$OSISHR.EXE   <         XTI$UCXSHR.DECNET-PLUS               XTI.DECNET-PLUS           OSITMSG.Hf           [SYSMGR]  <         CTF$STARTUP.COM                      NET$AUTOGEN.COM  B         DECNET_DNS_REGISTER.COM              DECNET_DNS_TOWERS.COM  G         DECNET_LOC_REGISTER.COM              DECNET_REGISTER_DECDNS.COM   >         DNS$CLERK_CLUSTER.NCL                DNS$CONFIGURE.COM  E         DTSS$CONFIG.COM                      DTSS$CONFIG_TEMPLATE.DATs  F         NET$CONFIGURE.COM                    NET$DNS_CLERK_STARTUP.NCL  E         NET$DTSS_CLERK_STARTUP.NCL           NET$EVENT_LOCAL.TEMPLATEf  =         NET$LOGICALS.TEMPLATE                NET$SHUTDOWN.COMm           [SYSMSG]  :         CTF$MESSAGES.EXE                     DNS$MSG_V.EXE  @         LES$ACP_MESSAGES_V30.EXE             LES$NM_MESSAGES.EXE           OSIT$VOTS_MSG.EXEf           [SYSTEST][  9         OSIT$IVP.CLD                         OSIT$IVP.EXEi  =         OSIT$IVPINIT.COM                     OSIT$IVPRESP.COMn  ?         A-6 System Files Loaded During DECnet-Plus InstallationP A  N      I                       System Files Loaded During DECnet-Plus Installationu    I         _________________________________________________________________hI         Directory/Files__________________________________________________            OSIT$IVP_SUPPORT.COM           [SYSUPD]           CTF.CLDa  C         DECNET_MIGRATE.EXE                   DECNET_MIGRATE_LSE.ENVm  D         DTSS$INSTALL_TIMEZONE_RULE.COM       DTSS$TIMEZONE_RULES.DAT  F         NCP_EMULATOR.TXT                     NET$CONFIGURE_UPGRADE.COM  A         NET$CONVERT_DATABASE.EXE             NET$PARSE_PREFIX.EXEW  A         NET$FIXUP_IDENTIFIERS.EXE            NET$PCSI_INSTALL.COM   I         NET$REMOVE_EMU.COM___________________NET_ISHFILTER.EXE___________                                                     I                   System Files Loaded During DECnet-Plus Installation A-7e                         I                                                                         BoI         _________________________________________________________________c  I                                                             Name Services     E               This appendix contains information not presented in theIH               chapters describing the configuration of DECnet-Plus. This5               chapter discusses the following topics:   7               o  Modifying the name service search path   )               o  Node synonym directories   2               o  Using Version 1 DECdns namespaces  1               o  Registering nodes in a namespaceC  G               For a complete description of name service tasks, see theEI               "Managing Name Service Searches and Information" chapter inEG               the HP DECnet-Plus for OpenVMS Network Management manual.t  1         B.1 Modifying the Search Path InformationP  E               See Section 6.4.1.4 for general information on the name_C               service search path and how to configure it using thelC               net$configure procedure. This section contains topics H               about the name service search path that provide additionalE               information on what the name service path is and how tot               configure it.e  F               HP recommends that you rerun net$configure.com to reviseB               the standard search path NCL script (net$searchpath_E               startup.ncl) whenever it is necessary to reorder access%F               to the name services on the node. To modify the standardC               search path startup script, run net$configure and useF;               Option 2 ("Change node name/namespace name").n  F                 ________________________ Note ________________________  F                 Whenever you directly edit an existing net$searchpath_?                 startup.ncl script, or when you use the NCL set B                 command to change the script (rather than changingF                 the script by rerunning net$configure), your edits are  I                                                         Name Services B-1                     Name Servicese1         B.1 Modifying the Search Path Information     A                 overwritten by any new net$searchpath_startup.ncl >                 scripts you subsequently generate by rerunningC                 net$configure. You can overcome this restriction byhD                 creating a site-specific search path NCL script file1                 as discussed in the next section.i  F                 ______________________________________________________                                                                                     B-2 Name Services            I                                                             Name Services I                                 B.1 Modifying the Search Path InformationC    =         B.1.1 Creating a Site-Specific Search Path NCL Scripti  E               HP recommends that you allow net$configure (and in some C               cases net$startup) to create and use the standard NCLt>               search path script (net$searchpath_startup.ncl).  H               However, if you need to make site-specific changes to yourF               search path NCL script and you do not want net$configureH               to overwrite these changes, you can create a site-specificD               search path NCL script by renaming the standard searchI               path script (net$searchpath_startup.ncl) to net$searchpath_o@               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 B.1.3 to create site-specific naming 4               templates in net$searchpath_local.ncl.  H               The net$configure and net$startup command 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                  **************************************************************nL                  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).aO                  ************************************************************** P               %NET$CONFIGURE-I-SITESEARCHPATH, invoking site-specific searchpath+                  NCL script found on systemr  E               The net$configure and net$startup command procedures doCB               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- G               specific search path NCL script, you must modify it prioreF               to invoking net$configure whenever you change any of the1               following name service information:   =               o  The number of name services used on the node   @               o  The order of the name services used on the node  <               o  The specific name services used on the node  I                                                         Name Services B-3t s  p               Name Servicest1         B.1 Modifying the Search Path InformationO    5         B.1.2 Using the Search Path to Ease Migration,  F               A search path can be used to simplify migration from oneC               name service to another. The system administrator can?F               create a search path designating the currently used nameH               service as the primary name service (to be searched first)D               and the new name service as the secondary name serviceG               (to be searched second, after the primary name service iss               searched).  G               As the secondary name service becomes populated with nodetF               and addressing information, the system administrator canD               rerun net$configure and select Option 2 to reverse theE               positions of the name services in the search path. ThiseH               causes the current secondary service to become primary, toD               be searched first for node and addressing information.  )         B.1.3 Setting Up Naming TemplatesC  E               In each template, the user-supplied portion of the name-F               (usually the node's terminating name or rightmost simpleF               name) is indicated with an asterisk (*). For example, ifH               the DECdns template is: "ABCDE:.xyz.*" and a user suppliesH               the name fin, then the following full name: ABCDE:.xyz.finI               is looked up in namespace ABCDE in the DECdns name service.   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 additional A               asterisks are passed to the name service as part of C               the full name. When you specify a template without an I               asterisk, the template string is passed to the name services               unchanged.  D               If you want the user-supplied name to be passed to theI               name service as entered by the user, the template should be (               specified as follows: "*".  C               DECnet-Plus provides an NCL set command for modifyingsA               the naming templates associated with the naming andoB               backtranslation search paths. Do not use the NCL setE               command to modify aspects of the search path other than #               the naming templates.              B-4 Name Services     ]      I                                                             Name ServicescI                                 B.1 Modifying the Search Path Information     C               The following net$searchpath_local.ncl script createsaF               typical naming and backtranslation search paths. In thisB               script ABCDE represents the namespace nickname. Your@               namespace nickname will appear in your NCL script:  =               SET NODE 0 SESSION CONTROL NAMING SEARCH PATH - E                       ([DIRECTORY SERVICE = LOCAL, TEMPLATE = "*"], - J                       [DIRECTORY SERVICE = LOCAL, TEMPLATE = "local:*"], -K                       [DIRECTORY SERVICE = LOCAL, TEMPLATE = "LOCAL:.*"], -UE                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "*"], - K                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:*"], -cP                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:.xyz.*"], -`                       [DIRECTORY SERVICE = DECDNS_SYNONYM, TEMPLATE = "ABCDE:.DNA_NodeSynonym.*"                       ], -E                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*"], -tQ                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*.xyz.ABCDE.com"])IC                       SET NODE 0 SESSION CONTROL BACK SEARCH PATH -oD                       ([DIRECTORY SERVICE = LOCAL, TEMPLATE = ""], -^                       [DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:.DNA_BackTranslation"], -B                       [DIRECTORY SERVICE = DOMAIN, TEMPLATE = ""])           B.1.4 Domain Synonymsm  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.d  H               There are two ways to configure node synonyms for use with               DNS/BIND:   I               o  By constructing an appropriate set of naming search path                   templates  *               o  By defining local aliases  G         B.1.4.1 Search Path Naming Template Support for Domain Synonymss  C               You can provide synonym support for entire domains byoG               constructing an appropriate set of search path templates.DH               Note that excessively long search paths (search paths withE               many entries) can increase the time it takes to look up                node addresses.     I                                                         Name Services B-5     T               Name Servicesl1         B.1 Modifying the Search Path Informationr    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 =                 -LS                    { [Directory Service = Domain, Template = "*"],                - S                      [Directory Service = Domain, Template = "*.finbar.com"],     -rS                      [Directory Service = Domain, Template = "*.abc.finbar.com"], -EQ                      [Directory Service = Domain, Template = "*.xyz.finbar.com"]}E  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 nametI               koi to applications that require Phase IV style node names.t  D               Using search path naming templates for synonym supportG               allows the user to enter any of the following node names:e?               koi, koi.abc, or koi.abc.finbar.com for node koi.            B.1.4.2 Local Aliases   H               Another way to define a node synonym for a particular nodeC               is by adding DNS/BIND alias names to the local host's C               database. The following is an example using HP TCP/IP #               Services for OpenVMS:i  O               $ tcpip set host koi.abc.finbar.com/address=aa.bb.cc.dd/alias=koi   F               DECnet-Plus returns the node synonym koi to applications5               that require Phase IV-style node names.   $         B.2 Node Synonym Directories  E               The default node synonym directory is .DNA_NodeSynonym.rD               If you plan to use a node synonym directory other thanF               this default directory, you must define the logical nameF               DECNET_MIGRATE_DIR_SYNONYM to the synonym directory nameF               you want to use in sys$manager:net$logicals.com. (If youF               do not have a net$logicals procedure on your system, youF               can create one using sys$manager:net$logicals.template.)           B-6 Name Services     e      I                                                             Name Services I                                              B.2 Node Synonym Directoriesu    G               This makes the definition permanent (that is, it will not 5               be deleted when you reboot the system).C  :         B.2.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 specialtH               characters or three or more dots, the system might produceI               an error. To avoid this, enclose the synonym directory name:%               in quotes. For example:t  K               $ define/system decnet_migrate_dir_synonym ".ch.noun.synonym"c  G               The net$configure procedure needs this logical name to beiI               defined at all times if you wish to use a synonym directory_I               other than .DNA_NodeSynonym. Be sure to add this definition F               to net$logicals.com to ensure that the definition of the2               synonym directory will be permanent.  *         B.2.2 When to Use the Logical Name  E               You can use the logical name described in Section B.2.1 I               with either the BASIC or the ADVANCED configuration option.g  I               You must define this logical name before you use any of the_#               following procedures:_  "                  net$configure.com$                  decnet_register.exe#                  decnet_migrate.exen  I               If synonym lookup fails in the namespace, the software does #               one of the following:f  E               o  The startup procedure defines SYS$NODE, SYS$CLUSTER_iI                  NODE, or both to be the first six characters of the lasteH                  simple name of the respective node full name or cluster                  full name.   G               o  The configuration procedure defines SYS$NODE to be thetI                  node synonym name that was entered during configuration.e  E               The system displays a message that it has redefined thes               logical names.  I                                                         Name Services B-7i                    Name Services A         B.3 Using a DNS Version 1 Namespace with DECdns Version 2B    A         B.3 Using a DNS Version 1 Namespace with DECdns Version 2e  G               If you are already using a namespace created with Version E               1 of the VAX Distributed Name Service (DNS) (running oneF               DECnet Phase IV), you can continue to use this namespaceF               when you upgrade your networking software to DECnet-PlusE               for OpenVMS. However, because of differences in the wayoC               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 onlysB               in the form nodename::username. In DECdns Version 2,@               servers recognize principals primarily in the formD               nodename.username. To have DECdns Version 2 clerks andH               servers interpret and process existing DNS Version 1-styleI               access control entries in the namespace, you need to createeD               a backtranslation directory (.DNA_BackTranslation) andE               a node synonym directory (.DNA_NodeSynonym) in the rootfF               directory of the namespace. You must then populate theseG               directories by registering all the nodes participating inM&               the Version 1 namespace.  C         B.3.1 Preparing a DNS Version 1 Namespace for Use by DECdnsf               Version 2   G               To prepare a namespace created with DNS Version 1 for use 1               by DECnet-Plus, follow these steps:e  E               1. Install and configure DECnet-Plus for OpenVMS on any I                  node in your namespace that is not currently functioning-C                  as a DNS Version 1 server. Configure the node as aaE                  DECdns Version 2 clerk. See Chapter 3 and Chapter 6._  E               2. From any node running DNS Version 1 server software,dH                  use the DNS Version 1 control program (DNS$CONTROL) addE                  access command to grant the following DNS Version 1-eH                  style access on behalf of the SYSTEM account on the newD                  Version 2 clerk node that you configured in Step 1:  H                  o  Read, write, delete, test, and control access to the3                     root directory of the namespace            B-8 Name ServicesC c  t      I                                                             Name ServicesMI                 B.3 Using a DNS Version 1 Namespace with DECdns Version 2e    H                  o  Read, write, delete, test, and control access to theG                     clearinghouse that stores the master replica of ther"                     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)e  [                  DNS> add access pastry::system clearinghouse .paris_ch /rights=(r,w,d,t,c)t  H                  You need to grant this access to ensure that the SYSTEMI                  account on the new Version 2 clerk has sufficient accessiH                  to run the decnet_register utility. The Version 2 clerkC                  must also have permission to create and populate aaE                  backtranslation directory (.DNA_BackTranslation) and F                  node synonym directory (.DNA_NodeSynonym) in the rootH                  directory of the namespace during the next step of this                  procedure.e  F                 ________________________ Note ________________________  B                 If the node you configured as a Version 2 clerk inF                 Step 1 is a new node, or if it is being assigned a newE                 DECnet Phase IV-compatible address, you should update$E                 the DECnet node databases on all Version 1 servers in_C                 the namespace to include the new address before yout                 proceed.  F                 ______________________________________________________  H               3. Log in to the new Version 2 clerk node under the SYSTEMD                  account and invoke the sys$manager:decnet_register_@                  decdns.com command procedure. Do the following:  F                  a. Choose Option 3 on the decnet_register_decdns menuF                     to create and populate a backtranslation directory+                     (.DNA_BackTranslation).   F                  b. Choose Option 2 to create a node synonym directory'                     (.DNA_NodeSynonym)._  B                  c. Choose Option 2 on the decnet_register menu toC                     register the new Version 2 clerk node (the noderC                     you are logged in to) and to register all otheryH                     DECnet Phase IV nodes in the namespace including all  I                                                         Name Services B-9_ _  _               Name ServicesfA         B.3 Using a DNS Version 1 Namespace with DECdns Version 2n    I                     nodes that are currently functioning as DNS Version 1g                     servers.  H               Refer to the HP DECnet-Plus for OpenVMS Network ManagementG               manual for complete information on how to use the decnet_tE               register utility and the decnet_register_decdns commande/               procedure to perform these steps.r  /         B.3.2 Using the DNS Version 1 Namespace   B               When you have completed this step, the DNS Version 1F               namespace is ready for use by other nodes running DECdns<               Version 2 on DECnet-Plus for OpenVMS software.  I               Perform this procedure only once to prepare a DNS Version 1 H               namespace for use with DECnet-Plus. After the node synonymD               and backtranslation directories are populated, you canF               configure new DECdns clerks, new DECdns servers (for VAXF               only) into an existing namespace (see Section 7.6.9), orF               convert existing DNS Version 1 servers to DECdns VersionH               2 format in the normal manner. Refer to the HP DECnet-PlusI               for OpenVMS DECdns Management manual for information on how H               to convert a DNS Version 1 clearinghouse to DECdns Version               2 format.                                                    B-10 Name Services    h      I                                                             Name Services-I                                   B.4 Registering a Node in the Namespacey    /         B.4 Registering a Node in the Namespace   B               The net$configure 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.  '         B.4.1 Export/Import File Format   C               The decnet_register Export/Import file is a text file G               that has the following format where <synonym> is the node_=               synonym name you selected during configuration:l  C               sys$manager:decnet_register_import_file_<synonym>.TXTs  )         B.4.2 Problems Registering a Nodel  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:                  .t               .2               . X               Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT                  1) local:.elmer  8               Error - Node registration was unsuccessfulW                       Please correct any problems and re-register the node LOCAL:.elmer   F                 The specified node name is already in use as a synonym7                       Used by node: LOCAL:.WABBIT.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._  +               Number of nodes registered: 0_+               Number of nodes modified:   0 *               Number of update failures: 1  ^               %NET$CONFIGURE-E-COULDNOTREG, could not automatically register node in the LOCAL                 directory service  Y                    ********************************************************************** 6                                                WARNING  I                                                        Name Services B-11                     Name Servicest/         B.4 Registering a Node in the Namespace     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[                    services for which the error occurred.  See the DECnet-Plus Installation2]                    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 Z                    use the following decnet_register commands to register your node in the2                    appropriate directory services:  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 appropriateS                    directory services, invoke option 2 of NET$CONFIGURE.COM (Change Y                    node name/namespace name) to complete the node's network configurationT                    and startup.   Y                    **********************************************************************   E               If net$configure cannot access the DECdns namespace you 7               have selected, it is most likely because:   >               o  The namespace is not available at the moment.  D               o  Your node does not have proper access to the DECdns                  namespace._  G               o  The namespace you are using is new and the directories +                  have not been created yet.e  C               When this happens, you will see the following messageyC               (this example uses ACME: as the namespace that is nots               accessible):  \                    *************************************************************************9                                                   WARNING V                    NET$CONFIGURE.COM cannot access the ACME: namespace, either becauseO                    the namespace is not available at the moment, your node doesPT                    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.  \                    *************************************************************************           B-12 Name Services r  a      I                                                             Name Services I                                   B.4 Registering a Node in the Namespace     C               If you receive this message because the namespace you E               are using is new and the namespace directories have not F               been created yet, use the decnet_register manage commandD               to invoke the decnet_register_decdns command procedureI               (located in sys$manager:) to create the proper directories. G               For more details, refer to the HP DECnet-Plus for OpenVMS (               Network Management manual.  F               If you see the preceding warning messages, net$configureE               will display another message indicating how you or your F               namespace manager can attempt node registration once the/               problem is resolved. For example:p  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 yourc\                    network manager will have to manually register this node in the directory[                    services for which the error occurred.  See the DECnet-Plus Installationi]                    and Configuration guide for more details, or contact your network manager.   Y                    Once the problem has been rectified, you or your namespace manager canaZ                    use the following decnet_register commands to register your node in the2                    appropriate directory services:  7                       For the DECdns directory service:vD                       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.TXT   T                    Once the node has been successfully registered in the appropriateS                    directory services, invoke option 2 of NET$CONFIGURE.COM (Change Y                    node name/namespace name) to complete the node's network configurations                    and startup.   Y                    **********************************************************************_  F               You may see the previous messages if you enter LOCAL forH               the primary directory service and DECDNS for the secondaryE               directory service and your primary Local node full name E               does not have the proper access necessary to look up or <               register your secondary DECdns node full name.  I                                                        Name Services B-13     n               Name Servicess/         B.4 Registering a Node in the Namespace     H               If this is the case, you or your namespace manager need toI               perform the following steps on the node that has the DECdns H               server in order for your primary Local node to obtain this-               access to the DECdns namespace:r  H               1. Make sure the .WorldRead_Group is created on the DECdnsB                  server node. If the .WorldRead_Group has not beenD                  created yet, use the decnet_register manage commandG                  to invoke the decnet_register_decdns command procedure D                  (located in sys$manager:) to create the .WorldRead_I                  Group. For more details, refer to the HP DECnet-Plus for 3                  OpenVMS Network Management manual.r  B               2. Once you or your namespace manager knows that the>                  .WorldRead_Group has been created, invoke theG                  DNS$CONTROL utility on the node with the DECdns servere2                  and enter the following commands:  "                  $ mcr dns$controlH                  DNS> add group <ns>:.worldread_group member local:.*.../                  DNS> add clear <ns>:.<ch_name> >                  access <ns>:.worldread_group as group for r,t  E                  where <ns> is the DECdns namespace name to which you E                  want your LOCAL node to have access and <ch_name> is G                  the clearinghouse name of the DECdns namespace you are                   using.d  H               These commands will give your primary Local node full nameI               the proper access it needs to look up information regardingn=               the secondary DECdns full name you have chosen.g  F                 ________________________ Note ________________________  C                 If you use DECDNS for the primary directory servicetD                 and LOCAL for the secondary directory service, these(                 steps are not necessary.  F                 ______________________________________________________                     B-14 Name Services n  d                    I                                                                         CaI         _________________________________________________________________   I                                  Configuring OSI Transport Over X.25 CONS     F               This appendix describes the steps necessary to configureF               the OSI transport to use the Connection-Oriented NetworkH               Service (CONS) provided by X.25 for OpenVMS. This appendix@               assumes that you are familiar with OSI application@               addressing, network service access points (NSAPs),B               and NSAP-to-X.25 address translation. For a completeC               explanation of these topics see the "Configuring X.25 I               Services" section in the HP DECnet-Plus for OpenVMS Network                 Management manual.  C               For most synchronous (WAN) devices, the net$configureeH               procedure configures the devices to use the HDLC protocol.B               This blocks X.25 access to the same devices. Use theG               advanced configuration procedure to override this defaultfF               by specifying none when prompted for the protocol to use               with the device.  D               The net$configure procedure always configures the CLNSH               stack. You cannot use this procedure to configure the CONSF               stack alone. In addition, you must manually add specificD               NCL commands to the user-specified NCL startup scriptsF               to complete the configuration, as shown in the following               examples.   H               DECnet-Plus uses the x25 access reachable address entitiesC               to map network service access points (NSAPs) to their I               corresponding DTE classes. Set the default configuration to I               perform X.121 mapping without address extension facilities,gI               as shown in this document. Use manual X.25 access reachable_I               addresses only for destinations with non-X.121-based NSAPs.   F                 ________________________ Note ________________________  B                 X.25 software provides controls to screen incoming?                 calls with the x25 access filter and x25 accesscD                 security filter entities. These mechanisms allow you  I                              Configuring OSI Transport Over X.25 CONS C-1. l         0         Configuring OSI Transport Over X.25 CONS      A                 to define access to the system based on call datatF                 such as source and destination addresses. The examplesB                 below do not use them. See the HP X.25 for OpenVMSA                 Management Guide and HP X.25 for OpenVMS Security_3                 Guide manuals for more information.   F                 ______________________________________________________  E               The following subsections show examples from procedures I               used to configure OpenVMS I64 and Alpha systems and OpenVMS D               VAX systems. The procedures were performed on pristineE               systems that include only the base operating system and I               the minimum appropriate licenses. The examples are based on G               a sample configuration discussed in the "Configuring X.25 I               Services" section in the HP DECnet-Plus for OpenVMS Network                 Management manual.  >               The sample configuration includes two end systemC               implementations ncosi and sybill connected to a local B               X.25 packet switch, which in turn is connected to anF               AT&T Accunet line in the US, as shown in Figure C-1. TheD               examples show the configuration process on node ncosi.  G               A summation of the pertinent configuration information ish$               provided in Table C-1.  I               Table_C-1_Sample_X.25_Configuration_Information_____________  I               Parameter_____________Initiator________Responder___________e  ;               Node name             ncosi            sybillu  <               X.25 profile          Accunet          Accunet  9               Accunet DNIC          3134             3134   6               Accunet               0                0"               international prefix  B               Accunet line          6171234500-99    6171234500-99               addressesd  =               X.25 network address  61712345         61712345   7               Local subaddress      40               10u  C               X.121 address         31346171234540   31346171234510   I                                                  (continued on next page)   4         C-2 Configuring OSI Transport Over X.25 CONS d         I                                  Configuring OSI Transport Over X.25 CONS       I               Table_C-1_(Cont.)_Sample_X.25_Configuration_Information____c  I               Parameter_____________Initiator________Responder___________   7               AFI                   36               36   I               NSAP__________________3631346171234540_3631346171234510____   F                 ________________________ Note ________________________  A                 The addresses shown in these examples differ from E                 the ones listed in Table C-1. DECnet-Plus for OpenVMS E                 requires an extra octet containing the NSAP length ini8                 digits to precede the actual NSAP value.  F                 ______________________________________________________                                                          I                              Configuring OSI Transport Over X.25 CONS C-3t a         0         Configuring OSI Transport Over X.25 CONSO         C.1 OpenVMS I64 and Alpha Configuration of OSI Transport Over X.25 CONS]    E         C.1 OpenVMS I64 and Alpha Configuration of OSI Transport Overn             X.25 CONS   C               Take the following steps to configure FTAM (and other G               OSI applications) with OSI Transport over X.25 CONS on an G               OpenVMS I64 or OpenVMS Alpha system. For more information I               on FTAM configuration, see the DECnet-Plus FTAM and Virtualp0               Terminal Use and Management guide.  >               1. Install the DECnet-Plus base kit, as follows:  J                  $ product install decnet_osi (decnet_plus on OpenVMS I64)  I               2. Configure DECnet-Plus with WAN drivers and an additional A                  OSI template for the CONS protocol stack. Do nota3                  configure WAN devices for routing.e  *                  $ @net$configure advanced  H                  Respond to the prompts as shown in this edited example:                     . . .hI         (Answer node, session control, and routing information questions)a@                  * Do you want to configure Wide Area devices? Y  6                    Configuring WANDD... ['?' for HELP]  R                  %WANDD$CONFIGURE-I-WANDDNOTCONFIG, WANDD has not been configured.  #                  Configure WANDD? Y A                  Configure built in serial port as synchronous? Y ;                  Are you satisfied with your answers? [YES]   =                    Available Synchronous Communication Ports:t  /                          1.  ZRA0   -  SSCC-0-0i  Y                  %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please waitd  D          . . .  (Configure any data links used for CLNS connections)=                  * Data Link protocol for ZR-0-0 (SSCC)? NONE ?                  * Do you want to configure DECnet over X.25? Nd6                  * Configure the NSP Transport? Y or N    4         C-4 Configuring OSI Transport Over X.25 CONS r         I                                  Configuring OSI Transport Over X.25 CONS I   C.1 OpenVMS I64 and Alpha Configuration of OSI Transport Over X.25 CONSo    C          . . .  (If needed, configure all NSP transport parameters)oD                  * Configure the OSI Transport or run over TCP/IP? YA                   . . .  (Configure all OSI transport parameters) D                  * Do you want to create additional OSI templates? YD                  * Type of network service (CLNS/CONS/RFC1006)? CONS1                  * Name of the OSI template? CONSeB                  * Will this template be used for inbound packets?6                  * Transport classes to support? 0,2,44                  * CONS template name? OSI Transport0                  * Allow use of expedited data ?*                  * Allow use of Checksums?D                  * Do you want to create additional OSI templates? NF                   . . .  (Continue with configuration until completed)  6               3. Install X.25 for OpenVMS, as follows:  '                  $ product install x.25   6               4. Configure and start X.25, as follows:  *                  $ @x25$configure advanced  H                  Respond to the prompts as shown in this edited example:  6                    Configuring WANDD... ['?' for HELP]  M                  %WANDD$CONFIGURE-I-WANDDCONFIG, WANDD is already configured.   )                    Current Configuration:c=                    1.  Autoconfigure device drivers   :   YES                               I                              Configuring OSI Transport Over X.25 CONS C-5  f  u      0         Configuring OSI Transport Over X.25 CONSO         C.1 OpenVMS I64 and Alpha Configuration of OSI Transport Over X.25 CONS     8                  Change your current configuration? [NO];                  Are you satisfied with your answers? [YES]lI                  The screen will be cleared.  Press RETURN to continue... 3                   . . .  (View Introduction screen) J                  Create a new configuration script (from Main Menu screen);                   . . .  (View CREATE Introduction screens) C                  Do you want to configure any Remote DTE Classes? NhB                  Do you want to configure any synchronous lines? Y@                  Select a synchronous line to configure: SCC-0-01                   . . .  (Enter the line's speed)A"                  Link Name: link-0                   DTE Name: dte-0'                  X.25 Address: 61712345 &                  Profile Name: ACCUNET(                  DTE Interface Type: DTE;                  Incoming Logical Channel Range: {[1..127]} ;                  Outgoing Logical Channel Range: {[1..127]}                    . . . F         (Change any DTE characteristics from profile values as needed):                  Do you want to use LLC2 communications? N9                  Do you want to use XOT communications? NA2                  Do you want to set up any PVCs? N<                  Do you want to create Closed User Groups? N,                  Do you want X.29 support? N.                  Do you want to use X.25 Mail?:                  Do you want to create any applications? NC                  Do you want to configure any X.25 Relay Clients? Ny<                  Do you want to set up additional filters? N>                  Do you want to set up additional templates? N>                  Do you want to specify reachable addresses? N?                  Do you want to configure any Server Clients? Nn?                  Allow all X.25 calls (from X.25 Security menu) 6                  Do you want to modify your answers? N  E               5. The configuration procedures in steps 2 and 4 do not C                  account for local X.25 address formats. Modify theAF                  configuration by adding the following NCL commands toG                  the sys$startup:x25$extra_set.ncl startup script file:g              4         C-6 Configuring OSI Transport Over X.25 CONS r  h      I                                  Configuring OSI Transport Over X.25 CONStI   C.1 OpenVMS I64 and Alpha Configuration of OSI Transport Over X.25 CONSc    8                  set lapb link link-0 sequence modulus 8                  !K                  ! Add ACCUNET profile characteristics to DTE Class accunet H                  set x25 access dte class accunet international prefix 0;                  set x25 access dte class accunet dnic 3134_A                  set x25 access dte class accunet strip dnic truei                  !H                  ! Add dte class characteristic to stock DTE Class x121dI                  set x25 access reachable address x121d dte class accunett                  !Y                  ! Add local subaddress characteristics to stock Template "OSI Transport"oL                  set x25 access template "OSI Transport" local subaddress 40  H               6. Install FTAM and the other OSI applications so that youG                  can use these applications with the OSI transport over "                  CONS, as follows:  1                  $ product install osak, ftam, vtt  ?               7. Configure FTAM, as follows (see Section 13.6):n  "                  $ @osif$configure  A               8. Add FTAM service aliases to the OSI applications 7                  database, as follows (see Chapter 14):h  :                  $ edit/edt sys$system:isoapplications.dat  D               9. Start OSAK and FTAM, as follows (see Section 13.4):  *                  $ @sys$startup:osak$start,                  $ @sys$startup:osif$startup  I              10. Manually enter the following NCL commands to provide theyC                  local NSAP information for OSI Transport entities:c  R                  ncl> add osi transport cons nsap addresses {/103631346171234540 }T                  ncl> set osi transport template cons local nsap /103631346171234540  E         C.2 OpenVMS VAX Configuration of OSI Transport Over X.25 CONSr  G               Take the following steps to configure FTAM (and other OSIuH               applications) with OSI Transport over X.25 CONS on OpenVMSF               VAX systems. For more information on FTAM configuration,C               see the DECnet-Plus FTAM and Virtual Terminal Use and                Management guide.   H               1. Install DECnet-Plus base kit with the X.25 software, as                  follows:   I                              Configuring OSI Transport Over X.25 CONS C-7     5      0         Configuring OSI Transport Over X.25 CONSE         C.2 OpenVMS VAX Configuration of OSI Transport Over X.25 CONSe    -                  $ product install decnet_osi   I               2. Configure DECnet-Plus with WAN drivers and an additional F                  OSI template for the CONS stack. Do not configure WAN%                  devices for routing.t  *                  $ @net$configure advanced  1                  Respond to the prompts as shown:                      . . . I         (Answer node, session control, and routing information questions)e@                  * Do you want to configure Wide Area devices? Y?                     This is the Configuration Procedure for thep?                     ===========================================   H                           VAX Wan Device Drivers for DECnet-Plus for VMSH                           ==============================================  S                    The Wide Area Network Datalinks and Drivers are  a  prerequisite T                    for  DECnet-Plus.  They  also  provide  synchronous  datalinks inF                    systems that do not use DECnet-Plus for networking.  0                  Do you wish to use WANDRIVER? Y)                  Will you use DEC HDLC? N '                  Will you use LAPB/E? Y R                  Do you have any soft-loadable microcode devices on this system? Y>                  Will you use the VAXft DSF32 device driver? NE                  Are you satisfied with the answers you have given? YpY                  %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait ?                  * Do you want asynchronous datalink support? N   D          . . .  (Configure any data links used for CLNS connections)@                  * Data Link protocol for DSV-0-0 (DSV-11)? NONE@                  * Data Link protocol for DSV-0-1 (DSV-11)? NONE?                  * Do you want to configure DECnet over X.25? N 6                  * Configure the NSP Transport? Y or N                4         C-8 Configuring OSI Transport Over X.25 CONS o  L      I                                  Configuring OSI Transport Over X.25 CONSVI             C.2 OpenVMS VAX Configuration of OSI Transport Over X.25 CONS_    C          . . .  (If needed, configure all NSP transport parameters)iD                  * Configure the OSI Transport or run over TCP/IP? YA                   . . .  (Configure all OSI transport parameters) D                  * Do you want to create additional OSI templates? YD                  * Type of network service (CLNS/CONS/RFC1006)? CONS1                  * Name of the OSI template? CONS2B                  * Will this template be used for inbound packets?6                  * Transport classes to support? 0,2,44                  * CONS template name? OSI Transport0                  * Allow use of expedited data ?*                  * Allow use of Checksums?D                  * Do you want to create additional OSI templates? NF                   . . .  (Continue with configuration until completed)  G               3. If you did not install the X.25 software (by selecting F                  the VAX P.S.I. or P.S.I. Access software and VAX WideH                  Area Device Drivers installation options), install them                  now.   C               4. Configure and start the X.25 software, as follows:   !                  $ @psi$configurei  1                  Respond to the prompts as shown:   @                  Create a new configuration (from the Main Menu);                   . . .  (View CREATE Introduction screens) +                  Configuration Type: Native B                  Do you want to configure any synchronous lines? Y1                   . . .  (Enter the line's speed)e+                  X.25 DTE Address: 61712345 3                  Logical Channel Ranges: [[1..127]]c&                  Profile Name: ACCUNET                   . . .o                      I                              Configuring OSI Transport Over X.25 CONS C-9            0         Configuring OSI Transport Over X.25 CONSE         C.2 OpenVMS VAX Configuration of OSI Transport Over X.25 CONSg    F         (Change any DTE characteristics from profile values as needed)#                  DTE Class: ACCUNET 2                  Do you wish to set up any PVCs? N@                  Do you wish to create any Closed User Groups? N:                  Do you wish to use LLC2 communications? N2                  Do you want to use P.S.I. Mail? N,                  Do you want X.29 support? N:                  Do you wish to set up any applications? N>                  Do you wish to set up additional templates? Y/                  Template Name: "OSI Transport"e#                  DTE Class: ACCUNETf&                  Call Data: %x03010100  D          . . .  (Except for the following fields, take the defaults))                  Charging Information: NOc%                  Local Subaddress: 40i"                  NSAP Mapping: YES]                  Do you want X.25 or X.29 programs to specify filter names in $QIO calls? YESlU                  Do you want IO$_ACPCONTROL calls issued by your programs to name any $                  dynamic filters? NOU                  Do you want IO$_ACPCONTROL calls issued by your programs to name anyt$                  static filters? YES-                  Filter Name: "OSI Transport" ,                  Call Data Value: %x03010100+                  Call Data Mask: %xFFFFFFFFv8                  Do you want to set up X.25 Security? NO=                  Do you wish to create an NCL script now? Yesa  A               5. The configuration procedures in steps 2 and 4 do ?                  not account for local X.25 address formats. InaD                  addition, when using X.25 for OpenVMS VAX, you mustD                  create the X.25 reachable address x121d. Modify theF                  configuration by adding the following NCL commands toF                  the sys$startup:psi$enable_decnet_clients.ncl startup                  script file:e                    5         C-10 Configuring OSI Transport Over X.25 CONSt o  o      I                                  Configuring OSI Transport Over X.25 CONS I             C.2 OpenVMS VAX Configuration of OSI Transport Over X.25 CONS                       !K                  ! Add ACCUNET profile characteristics to DTE Class accunet H                  set x25 access dte class accunet international prefix 0;                  set x25 access dte class accunet dnic 3134rA                  set x25 access dte class accunet strip dnic truef                  $! 7                  $! Create X.25 Reachable Address x121dgM                  create x25 access reachable address x121d address prefix /36eE                  set x25 access reachable address x121d mapping x.121sI                  set x25 access reachable address x121d dte class accunet O                  set x25 access reachable address x121d address extensions true   I               6. Install FTAM and the other OSI applications, as follows:e  1                  $ product install osak, ftam, vt   ?               7. Configure FTAM, as follows (see Section 13.6):   "                  $ @osif$configure  A               8. Add FTAM service aliases to the OSI applications 7                  database, as follows (see Chapter 14):y  :                  $ edit/edt sys$system:isoapplications.dat  D               9. Start OSAK and FTAM, as follows (see Section 13.4):  *                  $ @sys$startup:osak$start,                  $ @sys$startup:osif$startup  I              10. Manually enter the following NCL commands to provide thelC                  local NSAP information for OSI Transport entities:t  R                  ncl> add osi transport cons nsap addresses {/103631346171234540 }T                  ncl> set osi transport template cons local nsap /103631346171234540                    I                             Configuring OSI Transport Over X.25 CONS C-11  p  e                    I                                                                         D I         _________________________________________________________________I  I             Configuring Link State Routing Nodes Using the ISIS$CONFIGUREhI                                                                 Procedurew    C               This appendix describes how to use the isis$configureeI               procedure to configure routing. The net$configure procedure H               supports configuring host-based routing nodes that use theG               routing vector routing algorithm. If you want to create asF               host-based routing node that uses the link state routingC               algorithm, you must use the isis$configure procedure.            D.1 Prerequisites   G               The isis$configure procedure requires the following be inY4               place before you invoke the procedure:  D               o  The user account has SYSPRV and OPER privileges. HPI                  recommends that you invoke the procedure from the SYSTEMe                  account.u  C               o  The net$routing_startup.ncl script file created byeE                  the net$configure procedure must be available in thecF                  sys$manager: directory and must include configurationG                  information for all LAN routing circuits (both CSMA-CDsF                  and FDDI) that you want to include in your host-basedH                  routing configuration. Also, the associated net$csmacd_G                  startup.ncl and net$fddi_startup.ncl script files mustn                  be present.  D               o  WANDD software must be installed. This installationB                  creates the wandd$devices.dat in the sys$manager:=                  directory. This file is not required if yourfH                  configuration does not include any synchronous devices.            I  Link          State Routing Nodes Using the ISIS$CONFIGURE Procedure D-1            O         Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Proceduren         D.2 Dialog Structure             D.2 Dialog Structure  D               The isis$configure procedure begins by configuring theE               node's routing parameters. These parameters include thee               following:  =               o  Type of router required (Level 1 or Level 2)   >               o  Routing protocol to use at each routing level  @               o  Phase IV address (0.0 if no Phase IV address is                  required)  G               o  Zero or more Phase V area addresses (one or more if no "                  Phase IV address)  G               When the routing dialog completes, the procedure displays.B               a menu of routing circuit types. You must select andG               configure all desired routing circuits. This is true eveneG               though you configured these circuits using net$configure.sB               If you fail to configure a routing circuit using theE               isis$configure procedure, it will not be present in thet"               final configuration.  B               In addition to configuring the routing circuits, youG               must also create routing reachable addresses for any X.25i:               dynamically-assigned circuits you configure.  F               You will also be given the option of creating interphaseB               circuits for all synchronous, asynchronous, and X.25B               routing circuits. See the HP DECnet-Plus for OpenVMSB               Network Management manual for more information aboutF               interphase circuits. This manual describes the preferredB               method of creating these circuits if your network is               complex.           D.3 Outputs   G               The isis$configure procedure generates a new net$routing_ I               startup.ncl script. The existing net$csmacd_startup.ncl andiH               net$fddi_startup.ncl scripts are retained. The copy of theG               net$routing_startup.ncl file created by the net$configurei0               procedure is renamed to *.ncl-old.  A               If synchronous or asynchronous routing circuits are G               created, all necessary Modem Connect, DDCMP, and HDLC NCL D               commands are placed in the new net$routing_startup.nclD               script; any existing net$modem_startup.ncl, net$ddcmp_  S         D-2 Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure     d      I   Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure I                                                               D.3 Outputs     H               startup.ncl, and net$hdlc_startup.ncl files are renamed to               *.ncl-old.           D.4 Dialog  7               The dialog begins with an opening screen:M  K                           IS-IS Routing for OpenVMS configuration proceduretK                           -------------------------------------------------D  S                   This command procedure creates a script for use by IS-IS Routing.   Z                   The procedure  assumes  that you have performed a basic configuration of[                   your DECnet-Plus for OpenVMS system, and that you now have the following:_  V                        -  A basic routing script (SYS$MANAGER:NET$ROUTING_STARTUP.NCL)  P                        -  A CSMA-CD script (SYS$MANAGER:NET$CSMACD_STARTUP.NCL).  7                                                    NOTE Z                           If  you  are  setting up  X.25  circuits,  you must install X.25Z                           software  and use the X.25 configuration procedure to define theR                           templates and filters required by X.25 routing circuits.  Z                           If you  are  setting  up  synchronous circuits, you must install                            WANDD.  S                   This command procedure prompts you for the following information:   B                                           Press RETURN to continue  +               The opening screen continues:   N                        -  Type of system being configured (Level 1 or Level 2)  :                        -  Your Phase IV Address and Prefix  ;                        -  One or more Manual Area Addressesn  P                        -  Routing subentities - Circuits and Reachable Addresses2                           (Use the menu displayed)  I                   To obtain help for any question, enter ? as the answer.   ,                   Time is 10:20 29-OCT-2004.  (               _Press RETURN to continue:  I  Link          State Routing Nodes Using the ISIS$CONFIGURE Procedure D-3            O         Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure          D.4 Dialog    H               The dialog begins the routing configuration by asking whatH               type of router you want to configure (Level 1 or Level 2).  E               o  Level 1 routers route packets between systems in the I                  local area. Level 1 routing is carried out by both Level '                  1 and Level 2 routers.n  D               o  Level 2 routers route packets to other areas of theB                  network as well as within the local area. Level 2@                  routing is only carried out by Level 2 routers.  4               Enter the type of router you require:.  =               _Enter type of Router required (L1 or L2) [L1]:_  H               Next, the procedure asks for the routing protocols to use.E               Table D-1 discusses the possible configurations and thed)               reasons for selecting them._  I               Table_D-1_Routing_Protocol_Options_________________________   E               Level 1 Phase IV      If the entire routing domain uses 5               Level 2 Phase IV      Phase IV routing.   C               Level 1 Phase IV      If the local area uses Phase IV G               Level 2 Phase V       routing and Phase V routing is usedm2                                     between areas.  B               Level 1 Phase V       If the local area uses Phase VH               Level 2 Phase IV      routing and Phase IV routing is used2                                     between areas.  E               Level 1 Phase V       If the entire routing domain usesuI               Level_2_Phase_V_______Phase_V_routing._____________________e  1               Enter the routing protocols to use:   -                   Select the routing options:   8                   [1] Level 1 Phase IV, Level 2 Phase IV  7                   [2] Level 1 Phase IV, Level 2 Phase V   8                   [3] Level 1 Phase V,  Level 2 Phase IV  7                   [4] Level 1 Phase V,  Level 2 Phase V                  _Type [4]: ?  S         D-4 Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure            I   Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure I                                                                D.4 Dialog     G               The procedure asks for the node's Phase IV address. Enter H               the value 0.0 if you do not want this node to have a PhaseH               IV compatible address. Note that if you have chosen to runH               the Phase IV routing algorithm at any level you MUST enterG               a Phase IV address; if you have chosen to use the Phase V I               link state routing algorithm at all levels you CANNOT enter !               a Phase IV address.   7               Enter the node's Phase IV address or 0.0:   2               _Enter the Phase IV address [24.66]:  F               If you have indicated you want to use Phase V link stateD               routing at any level, you must enter at least one, andE               up to three, manual area addresses. If you have entered F               a Phase IV address, the procedure automatically convertsI               that address to a Phase V area address. Optionally, you can :               enter up to two more Phase V area addresses.  D               You must enter the Phase V area address in DNA format:  ,               aa:[ii...i]:[pp-....-pp-]ll-ll  G               where aa is the AFI, ii...i is the IDI (null for AFI 49),_C               pp-...-pp is the pre-DSP (usually null), and ll-ll is D               the local area (00-01 to 00-3F [1 - 63] used for PhaseG               IV compatible addresses). For example, 49::00-4F is valid H               Phase V area address using the private AFI value of 49 andF               the local area 79. For more information about the formatG               of area addresses and NSAPs, see the DECnet-Plus Planning                Guide manual.t  E               Enter a Phase V area address (press return when you arec/               finished entering the addresses):   *               _Enter Phase V area address:  B               The procedure now displays the routing circuit menu:  ,                   Routing configuration menu,                   --------------------------  0                   Configured node type: L2Router  )                   Please select an option   #                   [1]: LAN circuits   +                   [2]: Synchronous circuitss  $                   [3]: X.25 circuits  I  Link          State Routing Nodes Using the ISIS$CONFIGURE Procedure D-5o -         O         Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedurem         D.4 Dialog    *                   [4]: Reachable Addresses  /                   [5]: Generate script and exit   '                   [6]: Quit (no script)   ,                   [7]: Asynchronous circuits                 _Option [5]:  .               Enter your selection as follows:  I               1. Select 1 to configure CSMA-CD and FDDI routing circuits.   I               2. Select 2 to configure WANDD device (synchronous) routing_F                  circuits. The WANDD software must be installed if you$                  select this option.  =               3. Select 3 to configure X.25 routing circuits.a  F               4. Select 4 to configure reachable addresses if you haveH                  configure an X.25 dynamically-assigned routing circuit.  F               5. Select 5 to generate the NCL startup scripts and exit-                  the configuration procedure.   F               6. Select 6 to quit the configuration procedure and loseH                  all configuration data entered. The NCL startup scripts=                  created by net$configure are left untouched.   G               7. Select 7 to create asynchronous DDCMP routing circuitso(                  on OpenVMS VAX systems.  G               If you select one of the circuit configuration options or G               the reachable address configuration option, the procedure H               returns to this menu after configuring the requested item.F               You must select either 5 or 6 to exit the procedure. YouD               can select an option you already selected. If you haveH               already configured a routing entity, the procedure asks if1               you want to reconfigure the entity.   1         D.4.1 LAN and Synchronous Circuit Dialogs   C               If you select option 1 or 2, the procedure begins the D               individual LAN or synchronous routing circuit dialogs.H               Each dialog begins with a display of the devices available                for configuration:  S         D-6 Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedureo           I   Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure I                                                                D.4 Dialogs    V                  This section configures CSMA-CD and FDDI circuits for use by Routing.  2                   Select a device to be configured  D                         Device   Circuit Name       Data Link EntityD                         ------   ------------       ----------------  G                    [1]  FRA                         FDDI Station FDDI-0   +                    [2]  Return to main menu_                 _Option [2]:  B               For LAN circuits, the data link entity name is taken@               from the existing NCL startup scripts generated byI               net$configure. For all other circuits, the data link entityC>               name is created by the isis$configure procedure.  .               Select the circuit to configure.  I               After you select a circuit, the procedure asks for the nameo/               to use when creating the circuit:_  %               _Circuit name [FDDI-0]:y  I               Next, the procedure asks if you want the circuit enabled ono               system startup:r  6               _Enable circuit on system startup [yes]:  F               The procedure then asks if you want to take the defaults               for the circuit:  M               _Do you wish to accept the default circuit configuration [yes]:   :               The default configuration sets the following               characteristics:  ?               o  Data link protocol (synchronous circuits only)   %               o  Level 1 circuit cost   <               o  Level 1 router priority (LAN circuits only)  9               o  Level 2 circuit cost (if Level 2 router)   G               o  Level 2 router priority (LAN circuits only, if Level 2x                  router)  B               If you decide to manually configure the circuit, theI               procedure asks you for values for the same characteristics.   I  Link          State Routing Nodes Using the ISIS$CONFIGURE Procedure D-7            O         Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure          D.4 Dialog    )         D.4.2 X.25 Routing Circuit Dialoge  I               If you select option 3, the procedure begins the individual C               X.25 routing circuit dialog. The X.25 routing circuit H               dialog begins with the following introductory screen (it'sD               actually more than a screen, so scroll back to see the#               entire introduction):1  Z                   There are  four  types of X.25 routing circuits: static outgoing, staticZ                   incoming,  permanent,  and  dynamically  assigned.  Dynamically assignedO                   circuits are only supported on Level 2 Router configurations.   Z                   Static outgoing, and static incoming circuits operate over a single X.251                   switched virtual circuit (SVC).   Z                   A permanent  circuit  operates  over  a  single  X.25  permanent virtual                    circuit (PVC).  Z                   A dynamically  assigned  circuit operates over a number of X.25 switched*                   virtual circuits (SVCs).  [                   Use the  X.25 configuration program  to  configure  X25  Access templates_J                   and filters along with PVCs, following these guidelines:  O                       - Set the X25 Access template call data attribute to %X81cS                       - Set the X25 Access filter call data value attribute to %X81cS                       - Set the X25 Access filter call data mask attribute to %XFF.u  ;                   Select the type of X.25 circuit required:   %                   [1] Static Outgoing   %                   [2] Static Incoming                      [3] Permanentw  &                   [4] Dynamic Assigned  )                   [5] Return to main menu                  _Option [5]:  #               Enter your selection.a  I               After you select a circuit type, the procedure asks for thet4               name to use when creating the circuit:  (               _Circuit name [X25-OUT-0]:  S         D-8 Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure     o      I   Configuring Link State Routing Nodes Using the ISIS$CONFIGURE ProcedureOI                                                                D.4 Dialogl    E               For permanent circuits, the procedure asks for the nameDG               of the X.25 PVC you want to use when creating the routing-               circuit:  (               _X25 PVC name [X25-PVC-0]:  I               For static and dynamically-assigned circuits, the procedure I               asks for the name of the X.25 template you want to use wheno/               making or accepting a connection:i  4               _X25 Access template name [X25-OUT-0]:  H               For static incoming and dynamically-assigned circuits, theH               procedure asks for the name of the X.25 filter you want to.               use when accepting a connection:  1               _X25 Access filter name [X25-IN-0]:   C               The procedure asks if you want the circuit enabled on                system startup:   6               _Enable circuit on system startup [yes]:  I               For all circuit types except the dynamically-assigned type,IF               the procedure then asks if you want to take the defaults               for the circuit:  M               _Do you wish to accept the default circuit configuration [yes]:   :               The default configuration sets the following               characteristics:  %               o  Level 1 circuit cost   9               o  Level 2 circuit cost (if Level 2 router)   B               If you decide to manually configure the circuit, theI               procedure asks you for values for the same characteristics.   &         D.4.3 Reachable Address Dialog  I               If you select option 4, the procedure begins the individual H               reachable address dialog. The dialog begins with a displayI               of the circuits available for creating reachable addresses:m  I                   Select the circuit which connects to the routing domain.  1                         Name                 Type 1                         ----                 ----   3                    [1]  X25-DA-0             X25 DA   3                    [2]  X25-DA-1             X25 DAt  I  Link          State Routing Nodes Using the ISIS$CONFIGURE Procedure D-9e           O         Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure          D.4 Dialog    +                    [3]  Return to main menu                  _Circuit [3]:r  I               Select the circuit for which you want to create a reachable                address.  F               The procedure asks for the name to use when creating the                reachable address:  &               _Reachable Address name:  E               Next, the procedure asks for the address prefix to use. I               Enter the leading digits of an NSAP address, or a full NSAP_               address.  E               The address you enter is entered in a reachable-address H               table. This table tells the IS-IS router about non-DECnet-D               Plus systems that are reachable from the local domain.  H               When a Level 2 router receives a packet with a destinationE               address that matches an address prefix in its reachableaG               address table, the packet is forwarded to another Level 2l;               router, which can send it to its destination._  A               Enter the prefix in DNA format (see the DECnet-Plus %               Planning Guide manual):r  (               _Reachable Address prefix:  E               The procedure asks for the routing cost associated withx%               this reachable address:   +               _Reachable Address cost [20]:   D               Next, the procedure asks for the list of DTE addressesH               associated with this reachable address (separate addresses               using commas):  ,               _Destination DTE address list:          T         D-10 Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure c  o                            F      _________________________________________________________________  F                                                                  Index      F      A______________________________   B______________________________  =      Address Format Worksheet,         Backing up system disk D         14-11                            before installing software,;      ADVANCED configuration option,         1-13, 9-8, 12-9n6         4-1, B-7                       Base components:        invoking, 6-1, 7-4                configuring,  B-1B      Alternate node synonym            BASIC configuration option,2         directory                         4-1, B-7<        defining logicals, B-6            invoking,  6-1, 7-3        format for defining, B-7_F        when used, B-6                  C______________________________/      Application database              Changing B        configuring, 6-62, 7-48           X.25 configuration,  8-451      Application entities              Characters C        reconfiguring with site-          valid for full name,  6-9,i0          specific NCL scripts,              6-110          7-77                          Checklist;      Asynchronous data links             installation,  2-2iC        configuration, 6-26               X.500 configuration,  14-9l3        dynamic description, 6-28       Circuit cost :        static description, 6-27          specifying,  6-32+        switching terminal lines for,   CLNSu;          6-30                            configuring,  6-52 4      Autoconfiguring                   Cluster aliasA        network addresses, 6-18           configuring,  6-66, 7-58o?      Autoconfiguring a satellite       CMIP Management Listener          node, 7-630      AUTOGEN utility                     See CML2        running, 1-11                   CML account;                                          configuring,  6-62 8                                        Command procedure<                                          net$configure,  4-5<                                          psi$configure,  8-4  F                                                                Index-1 e  i              @         Command procedure (cont'd)        Configuration (cont'd)  H          psi$ctp,  8-45                     directory name services, 6-6H         Commands                            event dispatcher, 6-55, 7-47E          DCL                                flowchart, 3-5, 3-7, 8-4,_2             for starting FTAM,  13-6          10-2D             for starting OSAK,  13-6        host-based routing, 6-13G             for starting VT,  13-6          inactive area address, 6-53uG             for stopping FTAM,  13-6        list of tasks involved, 3-3xB             @sys$startup:osak$start.com     modifying, 7-1 to 7-77B                ,  13-6                      MOP client, 6-65, 7-59E         Configuration                       MOP client database, 7-55DH          application database,  6-62,       namespace modification, 6-71C             7-48                            NCL scripts, 6-69, 7-75 >          asynchronous data links,           net$configure, 4-1C             6-26                            network addresses, 6-17d?          autoconfiguring satellite          NSP transport, 6-40yC             nodes,  7-63                    of base components, B-1sE          changing                           of DECnet over X.25, 6-35c;             current configuration,          of network, 4-1oD                5-5, 6-73                       advanced, 6-1 to 6-73A             entire configuration,  7-7         basic, 6-1 to 6-73s?             the directory name                 fast, 5-1 to 5-5 A                services,  7-8               opening messages, 6-2 ?             the system's namespace,         OSI templates, 6-47 ?                7-8                          OSI transport, 6-42 H             the system's node name,         Phase IV conversion options,1                7-8                            6-4 5             the system's node synonym,      procedures=                7-8                             main menu, 7-6u@          choosing options,  4-2, 7-1           menu options, 7-6E          CLNS,  6-52                        reachable addresses, 6-37nE          cluster alias,  6-66, 7-58         reachable address prefix, 2          CONS,  6-53                          6-37=          customizing,  7-77                 requirements, 2-1 @          data links,  6-31                  RFC 1006, 6-43, 6-54B          DECdns clerk system                routing circuits, 6-31G             joining a WAN DECdns            routing parameters, 6-13 to 2                namespace,  7-15               6-22B          DECdns server system               routing protocol, 6-52F             joining existing DECdns         running net$configure, 4-5G                namespace,  7-36             satellite nodes, 7-61, 7-66yB          DECdts,  7-41                      selection weight, 6-67G          DECnet over X.25,  6-34, 11-1      starting the network, 6-70,d2          devices,  6-22, 7-37                 7-76G          device scan,  6-25                 summary display, 6-68, 7-74_           Index-2p                   =         Configuration (cont'd)            DECdns clerk systemfD          time zone differential             converting from a DECdns;             factors,  6-54                    server,  7-26eI          transports,  6-39 to 6-54,         converting to a DECdns serverh5             7-38                              ,  7-17n@          verifying,  6-68, 7-74             joining a WAN DECdns>          WANDD devices on Alpha system        namespace,  7-15I             ,  6-23                         reverting to a DECdns server, 2          WANDD devices on I64 system,         7-28:             6-23                          DECdns namespaceB          WANDD devices on VAX system,       adding to a Local-onlyB             6-24                              configuration,  7-11:          X.25 (OpenVMS I64/Alpha)           full name, 6-9@             See X.25 (OpenVMS               using as a secondary>                I64/Alpha),                    namespace,  7-32G                configuration                valid characters, 6-9, 6-11y>                                           DECdns server systemD          X.25 (OpenVMS VAX)                 converting from a DECdns  :             See X.25 (OpenVMS VAX),           clerk,  7-17I                configuration                converting to a DECdns clerk,a2          X.25 access template,  6-36          7-26C         Congestion avoidance, 6-45          joining existing DECdns   7         Connectionless-mode Network           namespacet@           Service                              configuring, 7-36I          See CLNS                           reverting from a DECdns clerko5         Connectionless Network Service        ,  7-28eE          See CLNS                           using DECdns namespace as >         Connection Oriented Network           secondary,  7-320           Service                         DECdts=                                             configuring, 7-41 <          See CONS                         DECnet over TCP/IP8         Conventions                         See RFC 1006:          of net$configure,  4-5           DECnet over X.25  D         D                                   configuring, 6-34, 6-35,2         _______________________________       11-15         Data links                        DECnet-Plus I          configuring,  6-31                 configuration default values,i1         DCL                                   4-5pF          reply command,  1-13, 9-8,         configuration options, 4-1G             12-9                            configuration requirements, 1          show device command,  1-8            2-1 =          show memory command,  1-8          installation, 1-1   B                                             installation time, 1-4E                                             license requirements, 1-5   I                                                                   Index-3                    A         DECnet-Plus (cont'd)              Disk space requirements 5          node name,  6-9                     (cont'd)iI          online release notes,  1-3         Virtual terminal installationo4          pre-installation                     ,  1-8:             accessing the release         Distribution kit4                notes,  1-3                  contents?          prerequisite software,  1-4           DECnet-Plus, 1-1sE          release notes,  1-3                   OSI applications, 12-2pD             extracting to a file,  1-3         X.25 for OpenVMS, 9-14             location,  1-3                  locating?          required hardware,  1-4               DECnet-Plus, 1-1 E         decnet_migrate, B-7                    OSI applications, 12-2 D         decnet_register, B-7                   X.25 for OpenVMS, 9-1<          export file,  B-11               Distribution mediaF          import file,  B-11                 mounting, 3-9, 3-11, 3-13,8         De-installation example               10-4, 10-7C          FTAM,  13-17                     DNA address format,  6-20 D          OSAK,  13-18                     DNA format for NETs,  6-197          OSI applications,  13-16         DNS version 1 F          VT,  13-17                         namespace preparation, B-8H          X.25 (OpenVMS I64/Alpha),          using with DECdns Version 2,1             10-10                             B-8_>         Devices                           Domain synonym,  B-55          configuring,  6-22, 7-37           node, B-5 G          reconfiguring,  7-37               search path naming template ;          scan for,  6-25                      support,  B-5 C         Directory name services           Dynamic asynchronous data 8          changing,  7-8                      links, 6-28          DECdns,  6-6, 6-7+          DNS/BIND,  6-6, 6-7, B-5         E I          Local namespace,  6-6            _______________________________M>          node full name,  6-9             End node information<          specifying,  6-6                   specifying, 6-177          specifying in user-defined       ES Cache Size A             script,  7-77                   routing default, 6-22 7         Disk space requirements           ESHello TimeroA          base components installation,      routing default, 6-22 :             1-8                           Event dispatcherC          DECdts server installation,        configuring, 6-55, 7-47TB             1-8                             outbound streams, 6-58@          FTAM installation,  1-8            Phase IV relay, 6-61D          installation,  1-8                 reconfiguring with site-C          OSAK installation,  1-8              specific NCL scripts, 2          software installation,  1-8          7-777                                             sinks, 6-56            Index-4                    C         Exiting                           Host-based routing,  6-13            from X.25 configurationI             program (OpenVMS VAX),        I______________________________y-             8-12                          IDP 9         Expedited data, 6-51                default, 6-16 ;         Export file, B-11                   standards, 6-16 ;          decnet_register,  B-11             supplying, 6-16m<         Extended addresses, 6-17          Import file,  B-11  A                                             decnet_register, B-11c?         F______________________________   Inactive area addressn  =         FAL account                         configuring, 6-53 =          configuring,  6-62               Initial Domain Part 9         FAST configuration option, 4-1      see IDP, 6-16 6          invoking,  5-1                   Initializing6         FDDI large packet support,          FTAM, 13-6<           6-32                              OSAKserver, 13-64         File Access Listener                VT, 13-66          See FAL                          Installation:         Files                               checklist, 2-2D          installed                          components included, 3-1C             DECnet-Plus,  3-16              DECnet-Plus for OpenVMS[;             OSI applications,  13-11          (Alpha),  3-3hI             X.25 for OpenVMS,  10-11        DECnet-Plus for OpenVMS (I64) 4          system,  A-1                         ,  3-3I         FTAM                                DECnet-Plus for OpenVMS (VAX) 4          starting, with network               ,  3-63             startup file,  13-6             examplehF          stopping,  13-6                       DECnet-Plus for OpenVMS?         Full name                                (Alpha),  3-11eF          node,  6-9                            DECnet-Plus for OpenVMS<          valid characters,  6-9, 6-11            (I64),  3-9F                                                DECnet-Plus for OpenVMS=         G______________________________          (VAX),  3-13_:         Generating NCL scripts, 6-69,          FTAM, 13-13:                                                OSAK, 13-12F           7-75                                 OSI applications, 13-128         Greenwich Mean Time (GMT)              VT, 13-14H          definition,  7-41                     X.25 for OpenVMS (Alpha),  5                                                  10-7hF         H______________________________        X.25 for OpenVMS (I64),  5         Hardware requirements                    10-4aE          DECnet-Plus,  1-4                  for Alpha flowchart, 10-2l;          OSI applications,  12-4            installed files @          X.25 for OpenVMS,  9-4                DECnet-Plus, 3-16F                                                OSI applications, 13-11  I                                                                   Index-5y                            InstallationI          installed files (cont'd)         L______________________________s  H             X.25 for OpenVMS,  10-11      Link state routing,  6-14, D-1=          list of tasks involved,  3-3     Local aliases,  B-6 4          net$configure, how to run,       Local time7             4-5                             configuringM;          OpenVMS for Alpha flowchart,          as UTC, 7-47dG             3-5                                using established rules, 5          OpenVMS for I64 flowchart,              7-44                3-5 I          OpenVMS for VAX flowchart,       M______________________________   >             3-7                           Manually configuringC          rebooting after,  3-17             network addresses, 6-19iD          recommended order,  10-1         Maximum path splits,  6-143             DECnet-Plus,  3-3             MigrationiB          required system parameters,        using search path, B-43             1-9                           Modifying D          rights identifiers added           your X.25 configuration,2             DECnet-Plus,  3-15                8-45?          system files loaded during,      Modifying search pathn=             A-1                              information, B-1 4          time required for                MOP clientC             DECnet-Plus,  1-4               configuring, 6-65, 7-59 =             OSI applications,  12-4       MOP client databasew=             X.25 for OpenVMS,  9-3          configuring, 7-55rD         Installation (VAX only)             reconfiguring with site-C          flowchart,  8-4                      specific NCL scripts,r2         Installation planning                 7-77<           checklist,  2-2                 Multihoming,  6-17         Installation procedure+          DECnet-Plus,  3-9 to 3-15        N I          OSI applications,  13-2 to       _______________________________ 6             13-6                          Name service8          X.25 for OpenVMS,  10-3 to         primary, 6-7<             10-9                            search path, 6-7:         Installed files                     secondary, 6-73          DECnet-Plus,  3-16               Namespaceh@          OSI applications,  13-11           directory path, 7-50H          X.25 for OpenVMS,  10-11              valid characters in, 6-9,5         Integrated mode routing, 6-20            6-11 ?         Intermediate system, 6-18           modification during B         isis$configure, D-1                   configuration,  6-71:         isoapplications database, 14-1      nickname, 7-50H                                                valid characters in, 6-9,5                                                  6-11h           Index-6  n  e              @         Namespace (cont'd)                net$configure (cont'd)  :          node object,  7-50                 option 4, 7-38:             valid characters in,  6-9,      option 5, 7-41:                6-11                         option 6, 7-47:          preparation                        option 7, 7-48:             DNS version 1,  B-8             option 8, 7-55:         Naming cache checkpoint             option 9, 7-58G           interval,  6-12                   privileges required to run,e2         Naming cache timeout value,           1-124           6-11                              startingA         Naming template                        advanced, 6-1, 7-4e>          setting up for search path,           basic, 6-1, 7-38             B-4                                fast, 5-1;          support for domain synonyms,     NET$DECLAREOBJECT_C             B-5                             rights identifier, 3-15o:         NCL                               NET$DECNETACCESSC          cluster-common scripts,  7-68      rights identifier, 3-16 6          creating site-specific search    NET$DIAGNOSEC             path script,  B-3               rights identifier, 3-16 5          generating scripts,  6-69,       NET$EXAMINEyC             7-75                            rights identifier, 3-16 4          site-specific scripts,  7-77     NET$MANAGEC          system-specific scripts,           rights identifier, 3-16o7             7-68                          NET$POSTEVENT C          user-defined scripts,  7-77        rights identifier, 3-16 ?         NET, 6-17                         NET$REGISTERDNSOBJECT C          autoconfiguring,  6-18             rights identifier, 3-16]6          DNA format,  6-19                NET$SECURITYC          example,  6-19                     rights identifier, 3-16lB          manually configuring,  6-19      net$startup,  6-70, 7-76H          transport selector field,        NET$STARTUP_MOP logical,  6-656             6-18, 6-19                    NET$TRACEALLC         net$configure, 4-1                  rights identifier, 3-16r<          configuring DECdts,  7-41        NET$TRACEALLREMOTEC          conventions,  4-5                  rights identifier, 3-16 :          how to run,  4-5                 NET$TRACEHEADERSC          main menu,  7-6                    rights identifier, 3-16c@          menu display,  7-1               NET$TRACEHEADERSREMOTEC          menu options,  7-6                 rights identifier, 3-16 1          option 1,  7-7                   Network.3          option 10,  7-59                   addressgD          option 11,  7-61                      autoconfiguring, 6-18D          option 12,  7-68                      manually configuring,5          option 2,  7-8                          6-19nE          option 3,  7-37                    configuring address, 6-17   I                                                                   Index-7  _  _              B         Network (cont'd)                  OpenVMS operating systemH          starting after modifying           checking the version number,1             configuration,  7-76              1-5_=          starting during initial            requirements, 1-4a.             configuration,  6-70          OSAKA         Network configuration, 4-1          software installation F          advanced,  6-1 to 6-73                process account quotas,5          basic,  6-1 to 6-73                     12-9p5          fast,  5-1 to 5-5                OSAK$SERVER G          link state routing,  D-1 to        calculating process account :             D-10                              quota,  12-84          modifying,  7-1 to 7-77          OSAKserver:         Network Control Language            stopping, 13-6:          See NCL                          OSI applicationsH         Network service type                application entity database,2          CLNS,  6-47, 6-52                    14-1C          CONS,  6-47, 6-53                  Authorize utility, 12-9 2          RFC 1006,  6-47, 6-54              CD-ROMA         Node full name, 6-9                    kit location, 12-2e?         Node name                           CD-ROM Reader, 12-4 I          DECnet-Plus,  6-9                  configuring OSI applications,f2          valid characters,  6-11              14-1@         Node synonym                        de-installing, 13-16H          default,  6-11                     disk space requirement, 12-5B          defined,  6-10                     files installed, 13-11A          defining an alternate,  B-7        global pagelets, 12-6 >          directories,  B-6                  global pages, 12-6A          local aliases,  B-6                global sections, 12-6 :          Phase IV-compatible,  6-10         hardware, 12-48         Node type                           installationE          specifying,  6-13                     installed files, 13-11 A         NSAP, 6-16                             kit location, 12-2dD         NSP transport                          notifying users, 12-9=          configuring,  6-40, 7-38              starting, 13-2oB          congestion avoidance,  6-45           time required, 12-4H          flow control policy,  6-41         installation procedure, 13-16          slow-speed connections,  6-46        to 13-11C                                             installation time, 12-4 B         O                                   installed files, 13-11E         _______________________________     isoapplications database,_2         OpenVMS Cluster performance           14-1>           monitor                           kit location, 12-2  F          See VPM                            license requirements, 12-5E                                             memory requirements, 12-6cA                                             notifying users, 12-9x           Index-8                    @         OSI applications (cont'd)         OSI transport (cont'd)  E          online release notes,  12-3        loopback test application <          post-installation tasks,             account,  6-47;             14-1 to 14-13                   templates, 6-47 &             configure OSI applicationsI                ,  14-1                    P______________________________ .          pre-installation                 PCSIH             accessing the release           process account quotas, 3-8,8                notes,  12-3                   10-2, 13-12             disk space requirements,      Phase IV9                12-5                         address, 6-16uD             notifying users,  12-9          compatible synonym, 6-108          prerequisite information           prefix, 6-16=             required hardware,  12-4      Phase IV addressingtI             required software,  12-4        enabling on routing circuits, 2          process account quotas,  12-8        6-33F          product description,  12-1       Phase IV conversion options,0          release notes,  12-3                6-4G             extracting to a file,         Phase IV routing information, 1                12-3                          6-15f6             location,  12-3               PrerequisiteC          required hardware,  12-4           backing up system disk,_=          required privileges,  12-7           1-13, 9-8, 12-9 6          required software,  12-4           disk space?          software product description,         DECnet-Plus, 1-7oE             12-1                               OSI applications, 12-5 D          software required,  12-4              X.25 for OpenVMS, 9-6G          time for installation,  12-4       informing users to log out, =          User Authorization File,             1-13, 9-8, 12-9 ;             12-9                            required memory ?          verification of                       DECnet-Plus, 1-8 E             FTAM,  13-8                        OSI applications, 12-6 ?             OSAK,  13-6                     required privilegesb@             VT,  13-11                         DECnet-Plus, 1-12E         osif$configure, 13-7                   OSI applications, 12-7wD         osif$startup, 14-2                     X.25 for OpenVMS, 9-7  >         OSI over TCP/IP                     rights identifiers  @          See RFC 1006                          DECnet-Plus, 1-12D         OSI router, non-DNA, 6-18              X.25 for OpenVMS, 9-74         OSI transport                       software?          configuring,  6-42, 7-38              DECnet-Plus, 1-4eE          configuring over X.25 CONS,           OSI applications, 12-4uD             C-1                                X.25 for OpenVMS, 9-4=          congestion avoidance,  6-45        system parametersi$          enabling over TCP/IP,  6-43  I                                                                   Index-9                    ;         Prerequisite                      RFC 1006 (cont'd) E          system parameters (cont'd)         configuring OSI templatesa  8             DECnet-Plus,  1-9                 for,  6-47<             X.25 for OpenVMS,  9-7        Rights identifiersE          TCP/IP software,  1-5              added during installation.@         Privileges                             DECnet-Plus, 3-15C          required for installation          NET$DECLAREOBJECT, 3-15DB             DECnet-Plus,  1-12              NET$DECNETACCESS, 3-16>             OSI applications,  12-7         NET$DIAGNOSE, 3-16=             X.25 for OpenVMS,  9-7          NET$EXAMINE, 3-16(<          required for X.25                  NET$MANAGE, 3-16?             configuration program           NET$POSTEVENT, 3-16vG             (OpenVMS VAX),  8-4             NET$REGISTERDNSOBJECT, 3-16 >          required for X.25 CTP,  8-43       NET$SECURITY, 3-16>          to run net$configure,  1-12        NET$TRACEALL, 3-16D         psi$configure, 8-4                  NET$TRACEALLREMOTE, 3-16B         PWIP interface, 1-5                 NET$TRACEHEADERS, 3-16H                                             NET$TRACEHEADERSREMOTE, 3-16E         Q______________________________     required for installatione@         Quitting                               DECnet-Plus, 1-12D          from X.25 configuration               X.25 for OpenVMS, 9-77                                           Router,  6-18e<             program (OpenVMS VAX),        Router type,  6-141             8-11                          Routingr>         Quota                               DNA address formatC          required for X.25 CTP,  8-44         characteristic,  6-20rA          verifying disk space,  1-8         integrated mode, 6-20   E                                             link state protocol, 6-14 A         R______________________________     segregated mode, 6-20n  :         Reachable address                 Routing circuits=          configuring,  6-37                 configuring, 6-31yI          prefix                             enabling Phase IV addressing,O2             configuring,  6-37                6-33=         Reconfiguration                   Routing information <          devices,  7-37                     specifying, 6-14:         Registering a node                Routing priority<          resolving problems,  B-11          specifying, 6-32:         Release Notes                     Routing protocol=          DECnet-Plus,  1-3                  configuring, 6-52 >          OSI applications,  12-3          RPOA sequence number6          X.25 for OpenVMS,  9-3             X.25, 8-33  &         reply command, 1-13, 9-8, 12-9         RFC 1006!          configuring,  6-43, 6-54            Index-10 o                 ;                                           Starting (cont'd)wF         S______________________________     X.25 configuration program  A         Satellite nodes                       (OpenVMS VAX),  8-4f9          autoconfiguring,  7-63           Startup scripts @          configuring,  7-61                 cluster-common, 7-68B          configuring from another           generating, 6-69, 7-75A             node,  7-66                     system-specific, 7-68r>         Scripts                             user-defined, 7-77H          cluster-common,  7-68            Static asynchronous data links3          creating for site-specific          , 6-27 2             search path,  B-3             Stopping6          NCL startup,  6-69, 7-75           FTAM, 13-6<          system-specific,  7-68             OSAKserver, 13-64          user-defined,  7-77                VT, 13-69         Search path, 6-7                  Summary displayoH          creating site-specific script      after initial configuration,2             ,  B-3                            6-68C          modifying information,  B-1        after modifying currentoB          naming template support,  B-5        configuration,  7-74D          primary name service,  6-7       Switching of terminal lineE          secondary name service,  6-7       DCL set terminal command, 2          setting up naming templates,         6-30B             B-4                             to a DECnet line, 6-30A          using to ease migration,  B-4    SYS$LIBRARY:DNS$NS_DEF_k;         Segregated mode routing, 6-20        FILE.DAT, 7-15 8         Selection weight                  SYSGEN utility:          configuring,  6-67                 invoking, 1-11D         Session control address update      setting parameters, 1-120           interval,  6-12                 SystemH         Simple name, 6-11                   configuring a namespace, 7-8H         Software license                    configuring a node name, 7-8G          checking the version number,       configuring a node synonym,s1             1-6, 9-5, 12-5                    7-8rC          requirements                       disk space requirementsr?             DECnet-Plus,  1-5                  DECnet-Plus, 1-7 E             OSI applications,  12-5            OSI applications, 12-5 D             X.25 for OpenVMS,  9-4             X.25 for OpenVMS, 9-6?         Software requirements               memory requirementsh?          DECnet-Plus,  1-4                     DECnet-Plus, 1-8aE          OSI applications,  12-4               OSI applications, 12-6rE          X.25 for OpenVMS,  9-4             verifying disk space, 1-8V6         Starting                          System filesG          FTAM,  13-6                        loaded during installation, 1          OSAKserver,  13-6                    A-1n          VT,  13-6  I                                                                  Index-11  _  _              :         System parameters                 Time zone,  7-41D          modifying values,  1-11            configuring differential<          requirements,  1-9                   factors,  6-540             DECnet-Plus,  1-9               rule@             X.25 for OpenVMS,  9-7             configuring, 7-41G          requirements for cluster              conventional for region,m5             members,  1-12                       7-41s@          values,  1-9                          customizing, 7-47;         System time                            format, 7-47g;          configuring,  7-41                    syntax, 7-47 -          configuring local,  7-44         TP0 =          configuring system                 configuring, 6-50_-             as UTC,  7-47                 TP2_=             using established rules,        configuring, 6-50 -                7-44                       TP4r=          configuring UTC as local,          configuring, 6-50 3             7-47                          Transport A                                             configuring NSP, 7-38 A         T______________________________     configuring OSI, 7-38iD         TCP/IP                            Transport protocol classes=          DECnet and OSI applications        configuring, 6-50 4             over,  1-5                    TransportsE                                             configuring, 6-39 to 6-54nA          using DECnet over                Type of network service   <             See RFC 1006                    CLNS, 6-47, 6-52<          using OSI applications over        CONS, 6-47, 6-53@             See RFC 1006                    RFC 1006, 6-47, 6-54-         TDF                               TZRn=          configuring,  7-41                 configuring, 7-41ID          definition,  7-41                  conventional for region,2         Testing                               7-41=          X.25,  8-43                        customizing, 7-47o<         Time                                definition, 7-418          configuring,  7-41                 format, 7-478          configuring local,  7-44           syntax, 7-47            configuring systemdI             as UTC,  7-47                 U______________________________   I             using established rules,      User-defined NCL scripts,  7-77_-                7-44                       UTC_<          configuring UTC as local,          definition, 7-41E             7-47                            relationship to GMT, 7-41             Time differential factor            See TDF           Index-12                   B                                           X.25 (OpenVMS I64/Alpha)C         V______________________________     AUTHORIZE utility, 10-2r:         Valid characters                    CD Reader, 9-42          for namespace nickname,  6-9,      CD-ROM@             6-11                               kit location, 9-1I         VAX P.S.I.                          configuring DECnet over X.25,u2          See X.25 (OpenVMS VAX)               11-1B                                             configuring X.25, 11-17         VMScluster performance monitor      DECnet-Plusl  ?          See VPM                               restarting, 11-2t?         VPM account                         de-installing, 11-3 G          configuring,  6-62                 disk space requirement, 9-6eF         VT                                  example installation, 10-3B          stopping,  13-6                    files installed, 10-119         vt_start, 14-2                      hardware, 9-4i8                                             installationE         W______________________________        installed files, 10-11c@         WANDD devices                          kit location, 9-1C          configuring,  6-23                    notifying users, 9-8rB          configuring (Alpha system),           prompt and responseH             6-23                                 sequence example,  10-3G          configuring (I64 system),             registering the license,C4             6-23                                 9-4H          configuring (VAX system),          installation procedure, 10-16             6-24                              to 10-11B         WAN DECdns namespace                installation time, 9-3B          joining,  7-15                     installed files, 10-11=         WANrouter, 6-18                     kit location, 9-1oH         Worksheet                           License Management Facility,1          Address Format,  14-11               9-4 I                                             license Product Authorization 7         X                                     Key,  9-4 E         _______________________________     license registration, 9-4 @         X.25                                notifying users, 9-8  E          Configuration Test Procedure       online release notes, 9-3i?             See X.25 (OpenVMS VAX),         POLYCENTER Software_C                CTP                            Installation utility,a1          configuring DECnet over X.25,        9-4cD             6-34                            post-installation tasks,:          Remote Address Prefix                11-1 to 11-3C             See X.25 (OpenVMS VAX),            configure X.25, 11-15D                RAP                             rebooting the system,5                                                  11-3bH                                                restart DECnet-Plus, 11-2B                                                starting X.25, 11-3  I                                                                  Index-13                    E         X.25 (OpenVMS I64/Alpha)          X.25 (OpenVMS VAX) (cont'd) ;           (cont'd)                          call data, 8-32a@          pre-installation                   call data mask, 8-30A             accessing the release           call data value, 8-30 D                notes,  9-3                  called address extension9             disk space requirements,           mask, 8-31 :                9-6                             value, 8-317             notifying users,  9-8           called NSAPt<          prerequisite information              filters, 8-31F             required hardware,  9-4         calling address extension,2             required software,  9-4           8-33:             synchronous interface           channel number9                card,  9-4                      PVCs, 8-22 :          process account quotas,  10-2      character-mode>          product description,  9-1             terminals, 8-15F          rebooting the system,  11-3        charging information, 8-33@          release notes,  9-3                client filters, 8-15:             extracting to a file,  9-3      client systems=             location,  9-3                     security, 8-41 9          required hardware,  9-4            configuration F          required licenses,  9-5               information you need to>          required software,  9-4                 supply,  8-18<          restarting DECnet-Plus,  11-2         planning, 8-2>          software product description,         verifying, 8-43A             9-1                             configuration programiC          software required,  9-4               data entry mode, 8-5 H          starting,  11-3                       entering information, 8-4A          System Support Addendum,  9-4         exiting from, 8-12e9          time for installation,  9-3           help, 8-10 G          User Authorization File,              help on specific fields, 5             10-2                                 8-10 H         X.25 (OpenVMS VAX)                     horizontal scrolling, 8-5?          application,  8-15, 8-28              insert mode, 8-5 <             command file,  8-15, 8-28          invoking, 8-4E             filters,  8-15                     keys used in, 8-4, 8-6_G             incoming calls to,  8-15           moving between sections,o4             name,  8-28                          8-6E             security,  8-35                    optional sections, 8-4 C             type,  8-28                        overstrike mode, 8-5_G             user name,  8-15, 8-28             privileges required, 8-4nB             X.25,  8-15                        quitting from, 8-11E             X.29,  8-15                        reviewing information,u4          applications,  8-13                     8-5E          BCUG,  8-13                           scrolling, horizontal, 4          call characteristics,  8-15             8-5           Index-14 2  o              E         X.25 (OpenVMS VAX)                X.25 (OpenVMS VAX) (cont'd) D          configuration program              extended packet sequence>             (cont'd)                          numbering,  8-19=             sections in,  8-4, 8-12         fast select, 8-32p>          configuring                        filter, 8-15, 8-30@             client systems,  8-2               application, 8-15C             connector systems,  8-2            call data mask, 8-30 D             direct connect systems,            call data value, 8-30G                8-2                             called address extensioni<          CTP,  8-43                              mask,  8-31G             as a network object,  8-45         called address extensione=             preparations,  8-43                  value,  8-31o@             privileges required,  8-43         called NSAP, 8-31>             quotas required,  8-44             DTE class, 8-30B             receive only mode,  8-45           dynamic, 8-16, 8-29:             running interactively,             group, 8-30D                8-45                            incoming DTE address,5             send/receive mode,  8-45             8-30dF             testing to remote system,          network processes, 8-16I                8-44                            originally called address,n5          CUG,  8-13, 8-14                        8-30 C             number,  8-23                      priority, 8-15, 8-30 E          declaring a network process,          receiving DTE address, 5             8-13, 8-16, 8-28                     8-30)D          destination DTE address               redirect reason, 8-30H             templates,  8-32                   sending DTE address, 8-30A          device,  8-18                         static, 8-16, 8-29eE          DTE address,  8-18                    subaddress range, 8-30eF             LLC2,  8-24                        unspecified parameters,5          DTE class,  8-21                        8-15 8             filters,  8-30                  flow control@             remote,  8-13, 8-14, 8-26          negotiation, 8-19C             templates,  8-32                group, 8-13, 8-14, 8-22i<          DTE name,  8-18                       filters, 8-309             LLC2,  8-24                        name, 8-22)G             PVCs,  8-22                        remote DTE address, 8-23u9          DTE status                            type, 8-23e0             checking,  8-44                 help<          dynamic filters,  8-16                general, 8-10<             name,  8-29                        leaving, 8-10F          end-to-end delay,  8-33            incoming DTE address, 8-30=          expedited data,  8-33              incoming security G          extended frame sequence               applications, 8-13, 8-35 D             numbering,  8-20                   server clients, 8-13,5                                                  8-40e  I                                                                  Index-15n                   E         X.25 (OpenVMS VAX) (cont'd)       X.25 (OpenVMS VAX) (cont'd)i  F          keys used in configuration         originally called address,2             program,  8-6                     8-30=          LAN device,  8-24                  outgoing securitylC          licenses                              client systems, 8-13 C             VAX,  8-3                          client Systems, 8-41dE          lines and DTEs,  8-13, 8-14,          local processes, 8-13, 5             8-18                                 8-37 =          line speed,  8-18                  P.S.I. Mail, 8-13 =          LLC2,  8-13, 8-14, 8-24            packet size, 8-19 9             DTEs,  8-14                        LLC2, 8-25 9          local facilities,  8-33               PVCs, 8-22 >          local processes                       templates, 8-329             security,  8-37                 profile, 8-19 ?          local subaddress,  8-33            psi$configure, 8-46 D          logical channel,  8-19             psi$configure, 8-4, 8-459             LLC2,  8-24                     psi$ctp, 8-45 D          LSAP                               psi$ctp_add_netobj, 8-45D             local,  8-24                    psi$ctp_rem_netobj, 8-45A             remote,  8-24                   PVC, 8-13, 8-14, 8-22oC          Mail,  8-15, 8-26                     channel number, 8-22a=             OpenVMS,  8-15                     DTE name, 8-22 9             P.S.I.,  8-13                      name, 8-22 @          NCL                                   packet size, 8-22C             scripts,  8-10, 8-13,              security, 8-38, 8-41f@                8-18, 8-37                      window size, 8-22F                failure to create,           $QIO(IO$_ACPCONTROL), 8-16D                   8-11                      quality of service, 8-33H          negotiation                        RAP, 8-35, 8-37, 8-39, 8-40,2             flow control,  8-19               8-41G          network process,  8-13, 8-16,      receiving DTE address, 8-30 A             8-28                            redirect reason, 8-30 6             filters,  8-16                  remote DTEF             security,  8-39                    class, 8-13, 8-14, 8-26D          network user identity,  8-33       remote MAC address, 8-24B          NSAP mapping,  8-33                reverse charging, 8-32F          options menu,  8-8                 RPOA sequence number, 8-33:             Add,  8-9                       security, 8-17F             adding information,  8-8           incoming, applications,;             changing information,  8-8           8-13, 8-35 H             Continue,  8-9                     incoming, server clients,;             Delete,  8-9                         8-13, 8-40sF             go to sections menu,  8-9          network processes, 8-39H             Modify,  8-9                       outgoing, client systems,;             sections menu,  8-8                  8-13, 8-41            Index-16                   <         X.25 (OpenVMS VAX)                X.25 (OpenVMS VAX)=          security (cont'd)                  template (cont'd)   G             outgoing, local processes,         transit delay selection,w5                8-13, 8-37                        8-33u@             PVCs,  8-38, 8-41                  window size, 8-32<          selected group,  8-32              terminology, 8-19          sending DTE address,  8-30         testing, 8-43iE          server clients,  8-13              throughput class request,i2             nodes,  8-27                      8-32D             security,  8-40                 transit delay selection,2             systems,  8-15                    8-33@          static filters,  8-16, 8-29        types of system, 8-2D          subaddress                         verifying configuration,2             range,  8-30                      8-437          SVC,  8-14                         window size 9          target address extension,             LLC2, 8-25 A             8-33                               packet level, 8-20_9          template,  8-13, 8-16, 8-32           PVCs, 8-22 >             call data,  8-32                   templates, 8-32C             calling address extension,      X.25 applications, 8-15_C                8-33                         X.29 applications, 8-15dE             charging information,           X.29 support, 8-13, 8-15, 2                8-33                           8-26>             `Default',  8-16              X.25 access template=             destination DTE address,        configuring, 6-36 3                8-32                       X.25 CONS E             DTE class,  8-32                configuring OSI transport 8             end-to-end delay,  8-33           over,  C-1D             expedited data,  8-33         X.25 routing circuit typesG             fast select,  8-32              dynamic assigned (DA), 6-35iA             local facilities,  8-33         permanent (PVC), 6-35,F             local subaddress,  8-33         static incoming (IN), 6-35G             network user identity,          static outgoing (OUT), 6-35 H                8-33                       X.500 Configuration checklist,1             NSAP mapping,  8-33              14-9              packet size,  8-32%             quality of service,  8-33 #             reverse charging,  8-32o!             RPOA sequence number,t                8-33f!             selected group,  8-32 %             target address extension,s                8-33 %             throughput class request,n                8-32c  I                                                                  Index-17 