^ From:	MARVIN::HEALEY "Brendan Healey, PSI, 830 6306  19-Apr-1990 2002" 19-APR-1990 20:05:51.54 To:	SQGUK::WOOD  CC:	1 Subj:	VAX P.S.I. Installation guide (text format)                 VAX P.S.I.   )              (Packetnet System Interface)     $              Installation Procedures    "              Order No. AA-L069K-TE    E              SUPERSESSION/UPDATE INFORMATION:  This is a revised man- 2                                                ual    @              OPERATING SYSTEM AND VERSION:     VMS V5.1 or later    ;              SOFTWARE VERSION:                 VAX PSI V4.3                                 DIGITAL                 @                                             Revised January 1990        B              The information in this document is subject to changeA              without notice and should not be construed as a com- H              mitment by Digital Equipment Corporation. Digital EquipmentA              Corporation assumes no responsibility for any errors .              that may appear in this document.  A              The software described in this document is furnished B              under a license and may be used or copied only in ac-5              cordance with the terms of such license.   B              No responsibility is assumed for the use or reliabil-A              ity of software on equipment that is not supplied by A              Digital Equipment Corporation or its affiliated com-               panies.  B              Restricted Rights: Use, duplication, or disclosure byB              the U.S. Government is subject to restrictions as setI              forth in subparagraph (c)(1)(ii)  of the Rights in Technical E              Data and Computer Software clause at DFARS 252.227-7013.   >               Copyright 1990 by Digital Equipment Corporation/                             All Rights Reserved ,                                Printed in UK  E              The READER'S COMMENTS form on the last page of this doc- A              ument requests the user's critical evaluation to as- 4              sist in preparing future documentation.    K              The following are trademarks of Digital Equipment Corporation:   1              DDCMP           Packetnet     UNIBUS .              DEC             PDP           VAX5              DECnet          Q-bus         VAXcluster .              DECrouter       Q22-bus       VMS-              DECUS           RSTS          VT                DECwriter       RSX#              MASSBUS         ULTRIX 2              MicroVAX        ULTRIX-32     DIGITAL  E              This manual was produced by the Wide Area Communications 3              Environment group in Reading, England.                                    A           _______________________________________________________   A                                                          Contents                   How to Use This Manual               1   Introduction  A               1.1      VAX PSI Modes of Operation ........... 1-1   A               1.2      VAX PSI Software Kits ................ 1-4   8               1.3      What Happens When You Install andA                        Configure VAX PSI..................... 1-5   A               1.3.1      VAX PSI Native...................... 1-5   A               1.3.2      VAX PSI Multi-host.................. 1-6   A               1.3.3      VAX PSI Access...................... 1-6   A               1.3.4      VAX PSI Combination System.......... 1-7   A               1.4      The Installation Procedure ........... 1-7   A               1.5      VAX PSI and DECnet ................... 1-8   A               1.6      Installing VAX PSI on a Cluster ...... 1-8   ?               1.7      Use of Network Names for VAX PSI and VAX A                        PSI Access........................... 1-10   A               1.8      Profile Names ....................... 1-12   A                                                               iii                  '           2   Installation Preparations   A               2.1      VAX WAN Device Drivers ............... 2-1   @               2.2      VAX PSI Support of the License ManagementA                        Facility.............................. 2-2   A               2.3      Licensing VAX PSI .................... 2-3   A               2.4      VAX PSI Distribution Kits ............ 2-4   6               2.5      Information Required During theA                        Installation.......................... 2-5   7               2.6      Disk Space and SYSGEN Parameters A                        Required............................. 2-13   ;               2.6.1      Disk Space Required to Install VAX A                          PSI.................................2-13   >               2.6.2      SYSGEN Parameters Required to Run VAXA                          PSI.................................2-14   5           3   Installing Native or Multi-host VAX PSI   8               3.1      Installing VAX PSI Files from theA                        Distribution Volumes.................. 3-1   A               3.1.1      Release Notes....................... 3-5   A               3.1.2      Tailoring the Installation.......... 3-6   A               3.2      Tailoring VAX PSI ................... 3-13   A               3.2.1      Setting Up Devices................. 3-16   A               3.2.2      Configuring the Permanent Database. 3-24   :               3.2.3      Setting Up VAX PSI for Multi-hostA                          Working ............................3-30   A               3.3      Starting Up VAX PSI ................. 3-33              iv                 '           4   Installing VAX PSI Access   ?               4.1      Installing VAX PSI Access Files from the A                        Distribution Volumes.................. 4-1   A               4.1.1      Release Notes....................... 4-4   A               4.1.2      Tailoring the Installation.......... 4-5   A               4.2      Tailoring VAX PSI Access ............ 4-12   A               4.2.1      Creating LOAD_PSI043.COM........... 4-15   A               4.2.2      Configuring the X25-ACCESS Database 4-19   A               4.3      Starting Up VAX PSI Access .......... 4-22   5           5   Installing a VAX PSI Combination System   A               5.1      Installing the Distribution Kits ..... 5-1   A               5.2      Tailoring Your Combination System .... 5-2   A               5.2.1      Setting Up Devices.................. 5-6   A               5.2.2      Configuring the Permanent Database. 5-14   :               5.2.3      Setting Up VAX PSI for Multi-HostA                          Operation...........................5-22   A               5.3      Starting Up VAX PSI ................. 5-25   *           6   Changing Your VAX PSI System  A               6.1      Migrating Between VAX PSI Systems .... 6-2   A               6.2      Adding Further VAX PSI Systems ....... 6-4   A               6.3      Adding Extra Network Connections ..... 6-5   A               6.4      How to Change the Default Network .... 6-6   >               6.5      Installing the VAX PSI Utilities or PSIA                        MAIL for the First Time............... 6-6   A                                                                 v                  6           A  Example of a Native or Multi-host VAX PSI              Installation       5           B  Example of a VAX PSI Access Installation       :           C  Example of a VAX PSI Combination Installation      6           D  Contents of the VAX PSI Distribution Kits    ?               D.1      Contents of the VAX PSI Distribution Kit                         D-1  5               D.2      Contents of the VAX PSI Access A                        Distribution Kit ..................... D-8              Index                Figures   A               1-1    VAX PSI Modes of Operation ............. 1-3   A               1-2    VAX PSI on a VAXcluster ................ 1-9   @               1-3    An Example Installation, Showing the Use ofA                      Network Names ......................... 1-11                            vi e  y                       Tables  6               2-1    X25-PROTOCOL Database InformationA                      (Multi-host/Native Installation)........ 2-6P  (               2-2    X25-SERVER Database3                      Information (Multi-host/Native A                      Installation)........................... 2-8/  <               2-3    X25-ACCESS Database Information (AccessA                      Installation).......................... 2-11   ?               2-4    Disk Space Required to Install VAX PSI andOA                      VAX PSI Access......................... 2-13G  A               2-5    SYSGEN Parameter Values ............... 2-15   A               6-1    Migrating Between VAX PSI Systems ...... 6-2c  A               6-2    Adding Further VAX PSI Systems ......... 6-4t                                          A                                                               vii  C  o                          A           _______________________________________________________n  A                                            How to Use This Manuale                       Manual Objectivesb  D              This manual explains how to install VAX PSI and VAX PSIH              Access. The manual also explains how to build a CombinationE              system. Information about how to configure and test yourdE              VAX PSI system is contained in the VAX P.S.I. Management               Guide..               Intended Audiences  A              This manual provides information for system managerstA              and DIGITAL software specialists. The manual assumesaB              that readers understand and also have some experience              of:  <               _ Installation of software products on VAX/VMS  *               _ Local Area Networks (LANs)  )               _ Wide Area Networks (WANs)                  _ DECnet-VAX                  _ Packet switching  B                                                               viii h  s            )               _ DIGITAL's VAX PSI productp  F              The manual also assumes that readers have read the P.S.I.              Introduction.  )                                      NOTEc  :                         This product has been designed for:                         installation by DIGITAL's Software-                         Services Specialists.S      !           Structure of the Manual   F              This manual consists of six chapters and four appendixes.  F              Chapter 1 describes the VAX PSI products. Read this chap-?              ter before installing any of the VAX PSI products.   A              Chapter 2 gives the information you will need before C              you install the software. Read this chapter before in-_2              stalling any of the VAX PSI products.  G              Chapter 3 describes the procedures for installing a Native ,              or a Multi-host VAX PSI system.  B              Chapter 4 describes the procedures for installing VAX              PSI Access.  C              Chapter 5 describes how to build a Combination VAX PSII              system.  C              Chapter 6 describes how to change your VAX PSI system.   B              Appendix A gives an example of a Native or Multi-host"              VAX PSI installation.  D              Appendix B gives an example of a VAX PSI Access instal-              lation.  D              Appendix C gives an example of a Combination system in-              stallation.             ix    .            B              Appendix D describes the contents of the distribution+              kits for the VAX PSI products.S  E              The last page of the manual is a Reader's Comments form. F              If you have any suggestions or criticisms which you thinkC              would improve this manual, please fill in the form and."              return it to Digital.               Associated Manuals  D              The other manuals in the VAX PSI documentation set are:  D              VAX P.S.I. Introduction - This manual introduces PSDNs,C              the X.25 and X.29 interfaces, and the VAX PSI product.e  A              VAX P.S.I. X.25 Programmer's Guide - This manual ex- A              plains how to use the VAX PSI programming facilities-0              to communicate with remote systems.  A              VAX P.S.I. X.29 Programmer's Guide - This manual ex- B              plains how to use X.29 facilities provided by VAX PSI/              to communicate with a remote host.n  D              VAX P.S.I. Problem Solving Guide - This manual explainsA              how to detect and solve problems that may occur when               using VAX PSI.   A              VAX P.S.I. PAD and MAIL Utilities Manual - This man-.B              ual explains how to use commands specific to VAX PSI:B              SET HOST/X29, SET TERMINAL/X29, SHOW TERMINAL/X29 and              PSI MAIL.  D              VAX P.S.I. Management Guide  - This manual explains theC              utilities specific to VAX PSI, that enable the network '              manager to manage VAX PSI..  B              Public Network Information - This manual provides de-E              tails of the individual public networks on which DIGITAL.)              supports the use of VAX PSI..  A                                                                 x.                 B              Further reference information can be found in the VMS              manual set:  /              VMS Network Control Program Manual.  C              VMS Networking Manual - This manual describes the con-.A              cept of DIGITAL networks and explains how to config-tA              ure, control, and monitor DECnet-VAX and the VAX PSI               product.   C              For information on the rest of the VMS manual set, see /              the Overview of VMS Documentation..             Manual Conventions    @              <xxx>       This 1- to 3-character symbol indicates>                          that you press a key on the terminal.@                          For example: <RET> indicates the RETURN?                          key and <ESC> indicates the ESCAPE key   =              <CTRL/x>    This symbol indicates that you press 9                          the CTRL key at the same time as <                          you press another key; for example,7                          <CTRL/C>, <CTRL/Y>, and so on.o  7              Italics     indicate variable information.e  =              Red print   indicates commands and data that youi                          enter.                                  xi A  S                          A           ______________________________________________________1   A                                                      Introduction               (           1.1 VAX PSI Modes of Operation  7              VAX PSI supports three modes of operation:   #               _ Native mode VAX PSI   D                 Native mode provides a single system with direct ac-*                 cess to one or more PSDNs.  '               _ Multi-host mode VAX PSI   A                 Multi-host mode VAX PSI is an extension of Native &                 mode. Multi-host mode:  A                  - Provides a single system with direct access to 9                    one or more PSDNs (as in Native mode).E  C                  - Allows systems running VAX PSI Access and DECnet F                    to establish indirect connections to a PSDN through'                    the Multi-host node.n  #               _ Access mode VAX PSI   D                 Access mode allows a system to gain access to a PSDNC                 through a Multi-host node, or other connector node.   A              In addition, a Combination system may be built which F              combines Access mode with one or both of the other modes.  A           Introduction                                        1-1. .  .            A              The following terms are used throughout this manual:   B               _ Host - Any VAX/VMS system which has either VAX PSI  2                 or VAX PSI Access installed on it.  B               _ Connector node - A node that supports DECnet, con-  A                 nects to PSDNs and also provides indirect connec- A                 tions to PSDNs for other systems connected to the A                 node. VAX PSI Multi-host nodes and X25router 2000r*                 nodes are connector nodes.  D              Figure 1-1 shows the various modes of operation you can              use with VAX PSI.                                                    N           1-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures A  S            3              Figure 1-1  VAX PSI Modes of Operation.A              ____________________________________________________.    8              |~~\___     __                |~~\___/~~~~\<              \      ~\__/  ~~\             \            ~~~|<               \               |             |    PSDN 2   /~:                \   PSDN 1   /~              \            |:                 |           \               / 2A      2B \:                /            /               |__  _/~~~~\_/9                |__/~\_____/~                   \/       |M9                           \                    /        | ;                            >                /|/         |/| ;                            \               /              |CD                          +------------------+    +-----------------+D                          |  Combination   A |    |  Combination  B |D                          |  System          |    |  System         |D                          |                  |    |                 |G                          +------------------+    +-----------------+\|\ H                                           \       /                    \K                                            \ ___ /                     |~\_ L                                           |\\\_///|           /~~\_/~~~    \M                                           | \\ // |           |             \ N                                           | | X | |           \    PSDN 3    \N                                           | // \\ |            |             /M                                           |///~\\\|             ~\   /~~~~~~~ E                                            / ~~~ \                ~~~u3                                           /       \tD                         +------------------+     +-----------------+D                         |    Access      C |     |   Connector   D |D                         |    Node          |     |   Node          |D                         |                  |     |   (Multi-host)  |D                         +------------------+     +-----------------+6                                                     /_6                                                      /9                                                     / ___u;                                                      /   ~\n>                                               /~~~~~~      \__?                                              /                \g@                                             /       PSDN 4     |@                                             ~\                 /?                                               \____/~~~|     /~ =                                                         \__/~-  A              ____________________________________________________i  C              Figure 1-1 shows a VAXcluster connected to four PSDNs. C              Nodes A and B are combination systems (running VAX PSI B              Multi-host and VAX PSI Access), Node C is running VAX  A           Introduction                                        1-3  t  o            A              PSI Access and Node D is running VAX PSI Multi-host.rC              PSDN 2 is known to VAX PSI under two different networkc              names: 2A and 2B.                Node A can use:  -               _ PSDNs 1 and 2 in Native mode.t  5               _ PSDN 3 through Node B in Access mode.   5               _ PSDN 4 through Node D in Access mode.r  D               _ PSDN 2 through Node B in Access mode, under the net-                   work name 2B.9                Node B can use:  -               _ PSDNs 2 and 3 in Native mode.'  5               _ PSDN 1 through Node A in Access mode.e  5               _ PSDN 4 through Node D in Access mode.m  D               _ PSDN 2 through Node A in Access mode, under the net-                   work name 2A.                 Node C can use:  B               _ All the PSDNs through the nodes they are connected                   to.   B               _ PSDN 2 through Node A and PSDN 2 through Node B at                   the same time.                Node D can use:                 _ PSDN 4 only.  #           1.2 VAX PSI Software Kitsn  2              The software is supplied on two kits:  C               _ The VAX PSI V4.3 kit supplies the software for con-/  C                 figuring a Native mode or a Multi-host VAX PSI sys-P                 tem.  N           1-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures                 A               _ The VAX PSI Access V4.3 kit supplies the softwarer  C                 for configuring Access mode VAX PSI on VAX/VMS sys-i4                 tems that have DECnet-VAX installed.  B              If you want to install a Combination system, you will              need both kits.  B              A full description of the VAX PSI products, PSDNs andA              the X.25 and X.29 interfaces is given in the P.S.I. tE              Introduction. Read this manual before installing any of i"              the VAX PSI products.  D              Before installing the VAX PSI software, you must be fa-E              miliar with the information contained in the VMS Networkp$              Control Program Manual.  =           1.3 What Happens When You Install and Configure VAXv               PSIa  D              Sections 1.3.1 to 1.3.4 describe the databases that youD              create or modify when you install each mode of VAX PSI.             1.3.1 VAX PSI Native  A              Native mode provides a single system with direct ac- D              cess to one or more PSDNs. When you install Native modeB              VAX PSI on a node, the installation procedure sets up              three databases:e  C               _ The X25-PROTOCOL database. This defines the PSDN(s)m  C                 to which the node is connected and the subscription A                 characteristics that relate to each PSDN: for ex-RA                 ample, the protocol options, DTE address, window- !                 size, packetsize.   B               _ The X25-SERVER database. This defines the destina-  B                 tions on the local node that use VAX PSI to commu-B                 nicate. They need to be defined to ensure that in-A                 coming calls from the PSDN can be directed to the D                 appropriate destinations. Destinations are user pro-/                 cesses or objects such as MAIL.t  A           Introduction                                        1-5                  B               _ The X29-SERVER database. This defines the destina-  @                 tions on the local node for incoming X.29 calls.    "           1.3.2 VAX PSI Multi-host  C              Multi-host VAX PSI extends access to the PSDN to othereF              users of DECnet-VAX host systems that have VAX PSI Access              installed.   C              The installation procedure is the same for both Native D              and Multi-host VAX PSI. When you install Multi-host VAX-              PSI, the installation procedure:i  A               _ Creates the databases described in Section 1.3.1.e  B               _ Adds host destinations to the X25-SERVER database.  A              The host destinations enable incoming calls from thehA              PSDNs to be sent to destinations on the host systems 0              that have VAX PSI Access installed.             1.3.3 VAX PSI Access  C              When you install VAX PSI Access on a node, the instal- B              lation procedure sets up the X25-ACCESS database. YouB              specify which connector node is going to be the gate-8              way to the PSDN in the X25-ACCESS database.  B              VAX PSI Access allows users on host systems to accessF              PSDNs through one or more connector nodes. VAX PSI AccessB              uses a DECnet logical link to transmit X.25/X.29 mes-C              sages between the connector node and the VAX host run- !              ning VAX PSI Access.             N           1-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures f  )            *           1.3.4 VAX PSI Combination System  A              You set up a VAX PSI Combination system by first in-_A              stalling VAX PSI and then installing VAX PSI Access. 0              A Combination system allows you to:  E               _ Access one or more PSDNs directly by running VAX PSI.   =               _ Access other PSDNs by running VAX PSI Access.~  (           1.4 The Installation Procedure  2              To install VAX PSI or VAX PSI Access:  E               1. Complete all the installation preparations described_                 in Chapter 2.   E               2. Execute VMSINSTAL.COM to copy the VAX PSI files from >                 the distribution kit to the installation disk.  ;               3. Execute PSI_SET_UP.COM. This command file:   F                  _ Sets up the devices and creates the LOAD_PSI043.COM  8                    command file needed to start VAX PSI.  $                  _ Defines the PSDN.  C                  _ Sets up the X25-PROTOCOL database for Native and   (                    Multi-host VAX P.S.I.  B                  _ Sets up the X25-ACCESS database for X25 Access.  B                  _ Sets up Native mode VAX PSI with Multi-host ac-  A                    cess, and creates the X25-SERVER database, for ,                    Multi-host installations.  D               4. Execute STARTNET.COM to start up DECnet-VAX and VAX                 PSI.  B              The installation procedure prompts you with questionsF              that require a simple answer, such as Yes or No. DefaultsE              are indicated in square brackets. To accept the default,               press <RET>./  A           Introduction                                        1-7     ~            C              If at any stage during the installation you do not un- B              derstand a prompt or are uncertain about the informa-B              tion required, enter a question mark (?) in answer toB              the prompt. You will be provided with help about that              prompt.                1.5 VAX PSI and DECnet  A              All VAX PSI Multi-host and VAX PSI Access nodes must E              have DECnet-VAX installed to set up DECnet logical links E              between them. To use DECnet for communications, you will A              need to install a DECnet license. You should do this (              before you install VAX PSI.  -           1.6 Installing VAX PSI on a Cluster   A              To use VAX PSI on a VAXcluster, you must install VAX B              PSI on each node you require to use the software. OneB              way of doing this is to install VAX PSI Multi-host onD              systems that are connected to the PSDN, and install VAXK              PSI Access on the other VAX systems in the cluster. Figure 1-2_4              illustrates this type of configuration.                                    N           1-8  VAX P.S.I. (Packetnet System Interface) Installation Procedures                 0              Figure 1-2  VAX PSI on a VAXclusterJ              _____________________________________________________________      K                                                                        |~\_ L                                                               /~~\_/~~~    \M                                                               |             \ N                                                               \      PSDN    \N                                                                |             /N                                                               /  ~\   /~~~~~~~F                                                              /     ~~~=                                                           /\/s:                                                          /9                                                         /oF                          +------------------+    +-------------------+F                          |  VAX PSI         |    |  VAX PSI          |F                          |  Access          |    |  Multi-host       |F                          |                  |    |  (Connector node) |F                          +------------------+    +-------------------+3                                           \       /r2                                            \ ___ /3                                           |\\\_///| 3                                           | \\ // |X3                                           | | X | |X3                                           | // \\ |c3                                           |///~\\\|S2                                            / ~~~ \3                                           /       \SD                         +------------------+     +-----------------+D                         |    VAX PSI       |     |   VAX PSI       |D                         |    Access        |     |   Access        |D                         |                  |     |                 |D                         +------------------+     +-----------------+  A              ____________________________________________________   C              If you install a VAX PSI option, for example X.29 sup- E              port, on one of the systems in your VAXcluster, you must J              install the same option on all the systems in the VAXcluster.  C              Before you install VAX PSI or VAX PSI Access, you MUST3B              ensure that VAX PSI or VAX PSI Access are not alreadyD              running on any of the nodes in a cluster. When you haveA              finished installing the software on all the relevantc*              nodes, you can start VAX PSI.  A           Introduction                                        1-9t a  n            :           1.7 Use of Network Names for VAX PSI and VAX PSI               Access  2              You use network names to distinguish:  )               _ The PSDN you wish to use.   E               _ The route you want to use in order to access the PSDN   B                 (which connector node and which line the connector2                 node uses to connect to the PSDN).  C              Network names have to meet the following requirements:   D               _ You must have a different network name for each PSDN  #                 you want to access.-  B               _ If you have more than one connector node available  C                 to access the same PSDN, you must give each connec- 7                 tion to the PSDN a unique network name.   A               _ The network name contained in the Access database   A                 must be the same as the network name contained ine6                 the connector node permanent database.  C               _ The network name may comprise any combination of up   *                 to 16 letters and numbers.  B              In addition, if you have more than one line between aB              connector node and a PSDN, you can use different net-5              work names to distinguish between lines.   B              Figure 1-3 shows how network names are defined for an              installation.      O           1-10  VAX P.S.I. (Packetnet System Interface) Installation Procedures                  D              Figure 1-3  An Example Installation, Showing the Use of&                          Network NamesC              ______________________________________________________   3                      +----------+      +----------+ 3                      |          |      |          |n3                      | Access A |      | Access B | 3                      |          |      |          |.3                      +----------+      +----------+i-                           |                 |N-                           |                 |X?                         +---+    +---+    +---+    +---+    | |P?                    _----|   |----|   |----|   |----|   |----/ / >                   / ----|   |----|   |----|   |----|   |-----~8                   | |   +---+    +---+    +---+    +___+6                                    |                 |6                                    |                 |<                              +-----------+     +-----------+<                              | Connector |     | Connector |<                              |   Node    |     |   Node    |<                              |    A      |     |    B      |<                              +-----------+     +-----------+<                                 /       |           /    \ \=                                /        |          /      \ \ >                               /         |         /        \ \G                    /~~\__    /         /~~\__/~~~~|         \ \   /~~~\nI                 |~~      ~\ /         /            \         \-~~~     \_SL               /~           \        /~             |        /~           \__M               |   PSDN 1    \       |    PSDN 2    \       /    PSDN 3      \oM              /             /~       |               \      |                /0M              |             \        \              /       |                \ M              \   /~~\      |         \       --~~~~        /_       --~\____/aD               ~~~    ~~\__/~          \___/~~                \___/~~  A              ____________________________________________________   D              In Figure 1-3, PSDN 1 can be accessed only through con-C              nector node A, and hence requires only a single unique #              network name (PSDN 1).   E              PSDN 2 can be accessed through connector node A and con- F              nector node B. Therefore, separate (unique) network namesC              are required for Access nodes to differentiate betweenYB              the two routes. For example, you might choose network)              names "PSDN2A" and "PSDN2B".<  A           Introduction                                       1-11  -               B              PSDN3 can be accessed only through the two lines con-D              nected to connector node B. Therefore, the minimum num-E              ber of network names PSDN3 requires is one. You may want B              to distinguish between the two lines provided by con-B              nector node B (for example, if the lines have differ-D              ent speeds). To do this, you would give PSDN 3 two net-;              work names, for example "PSDN3A" and "PSDN3B".i               1.8 Profile NamesT  C              The following attributes are associated with each PSDNlD              connected to the VAX PSI Native node or connector node:                 _ A profile name  )               _ One or more DTE addresses   9               _ One or more devices connected to the PSDN   B              The profile name is unique for each PSDN and providesD              VAX PSI with network characteristics. The profile namesF              for public PSDNs appear in the Public Network Information              manual.  C              You must use the correct profile for your network. UseyC              of the incorrect profile invalidates DIGITAL's VAX PSI-              support.t                          O           1-12  VAX P.S.I. (Packetnet System Interface) Installation Proceduresu r                             A           ______________________________________________________2   A                                         Installation Preparations         .              Before starting the installation:  E               1. If your system requires a Device Driver from the VAX D                 WAN Device Drivers kit, make sure the VAX WAN Device>                 Drivers kit has been installed on your system.  C               2. Ensure that your system is licensed to run VAX PSI &                 and/or VAX PSI Access.  D               3. Check that your VAX PSI kit contains all of the me-                 dia.  D               4. Gather the information you will need during the in-L                 stallation by completing the relevant tables in Section 2.5.  C               5. Check that you have enough free disk space and the-)                 correct system resources.   B              Sections 2.1 to 2.6.1 describe how to do these tasks.  $           2.1 VAX WAN Device Drivers  A              If you are installing VAX PSI Native/Multi-host or a C              combination system, install the VAX WAN Device Drivers+D              kit before you install the VAX PSI software. Follow theD              instructions in the VAX WAN Device Drivers InstallationA              Guide. By installing the VAX WAN Device Drivers, you   A           Installation Preparations                           2-1                  D              ensure that the level 2 software and device drivers are&              installed on your system.  D              Note that some older device drivers are included in theD              VAX PSI kit itself. If you will only be using this typeA              of device driver, you do not need to install the VAX|A              WAN Device Drivers kit. Refer to the SPD for further '              details of device drivers.   @           2.2 VAX PSI Support of the License Management Facility  B              Before VAX PSI or VAX PSI Access can be run on a sys-D              tem, you must license the system by running the LicenseA              Management Facility (LMF) procedure. Once VAX PSI or G              VAX PSI Access is licensed on a system or on a node within B              a cluster, any user on that system or cluster can use              it.  A              If you do not license VAX PSI before you install it,rB              the following message will be displayed after the VAX0              PSI V4.3 files have been installed:  L                %PSI-W-NOLICENSE, P.S.I. has not been licensed to run on this                system   D              If you do not license VAX PSI Access before you installB              it, the following message will be displayed after the;              VAX PSI Access V4.3 files have been installed:u  N                %PSI-W-NOLICENSE, P.S.I.-Access has not been licensed to run on                this system  D              For both VAX PSI and VAX PSI Access, the procedure thenB              displays a series of instructions telling you what toA              do to complete the installation. If a license is re- C              quired for VAX PSI, the procedure displays the follow-r              ing instruction:   4                - Install the P.S.I. Product License.    N           2-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures a  P            B              If a license is required for VAX PSI Access, the pro-.              cedure displays this instruction:  ;                - Install the P.S.I.-Access Product License.                  2.3 Licensing VAX PSI   D              To license your system, you enter the information givenA              on the Product Authorization Key (PAK). The PAK con- C              tains all the information you need to enter during theh!              licensing procedure.   @              To start the license procedure, enter this command:  '                $ @SYS$UPDATE:VMSLICENSEn  C              You will then be prompted for the details contained in B              the P.S.I. or P.S.I.-Access PAK. Each question corre-,              sponds to a heading in the PAK.  E              If you are installing on a homogeneous cluster, you onlyaB              need to enter the above command on one node. Then, ifB              you are licensing VAX PSI Native or Multi-host, enterD              the following command on each of the other nodes in the              cluster:   $                $ LICENSE LOAD P.S.I.  C              If you are licensing VAX PSI Access, enter the follow- C              ing command on each of the other nodes in the cluster:   +                $ LICENSE LOAD P.S.I.-ACCESS   B              You can then install VAX PSI or VAX PSI Access on theA              other nodes in the cluster as required. Refer to the B              VMS License Management Utility Manual for further de-'              tails on using VMSLICENSE.     A           Installation Preparations                           2-3                  D              If you have not licensed VAX PSI or VAX PSI Access, andF              you try to start VAX PSI, the product will fail to start.D              An LMF error message will be displayed stating that theB              product is not licensed. You should therefore license              the product.   F              If you have a combination system which has not been fully?              licensed, you will only see one LMF error message.   I              You can check that both licenses are in the license database B              (which is cluster-wide) by issuing the following com-              mand:                  $ LICENSE LIST   D              You can check that the license has been loaded onto the5              system by issuing the following command:                   $ SHOW LICENSE     '           2.4 VAX PSI Distribution Kits   G              VAX PSI and VAX PSI Access can be installed onto a VAX/VMS C              system from either a TK50 cassette, a magnetic tape or A              a Compact Disc (CDROM). VAX PSI distribution volumes A              are labelled (PSI). VAX PSI Access distribution vol- (              umes are labelled (PSI_AC).                          N           2-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures S  1            :           2.5 Information Required During the Installation  B              You will need to supply information about your systemD              during the installation. Tables 2-1 to 2-3 list the in-#              formation you require.r  C              If you are installing VAX PSI Native or VAX PSI Multi-c/              host, complete Tables 2-1 and 2-2:   C               _ Table 2-1 contains the information entered into them  &                 X25-PROTOCOL database.  C               _ Table 2-2 contains the information entered into the                    X25-SERVER                 database.w  A              You will need a separate copy of each table for each               local DTE.   E              If you are installing VAX PSI Access, complete Table 2-3tA              which contains the information entered into the X25-n              ACCESS database.h  D              Obtain the information to complete the tables from your7              system manager and PTT representative. [1]"                           ________________C         [1] Your PTT representative may describe your logical chan-wD             nels allocation as a quantity.  VAX PSI requires a rangeD             of channels, so to determine the correct range, refer to2             the Public Network Information manual.  A           Installation Preparations                           2-5s i               A              Table 2-1  X25-PROTOCOL Database Information (Multi-T1                         host/Native_Installation)eC              ______________________________________________________ C              Information you will require for each network you use: C              ______________________________________________________   >              Item             Notes                 Your ValueC              ______________________________________________________     -              Network name     Choose your own_*                               unique name.-                               Example: SWED01n  )              Network profile  Recorded int,              name             Public Network)                               Information %                               manual.i&                               Example:'                               DATAPAK_Sa                                              N           2-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures s               A              Table 2-1 (Cont.)  X25-PROTOCOL Database Information @                                 (Multi-host/Native_Installation)A              ____________________________________________________l7              Information you will require for each DTE:aA              ____________________________________________________   ;              Item             Notes              Your ValuebA              ____________________________________________________     *              DTE address      Your DTE ad-+                               dress. Obtains+                               this from the +                               PTT. Example: ,                               24050198765432  (              Channels Range   Your range(                               of Logical-                               Channel Numbersa,                               (LCNs). Obtain+                               this from theh+                               PTT. Example:e%                               155-100.  ,              Line Name        Name of device-                               and line in thek+                               form dev-c-u.e-                               Example: DMB-0-d                               0   ,              Vector address   Vector address-                               for your device #                               type.t  )              CSR address      CSR address -                               for your device #                               type.cA              ____________________________________________________i    A           Installation Preparations                           2-7l n               ?              Table 2-2  X25-SERVER Database Information (Multi-s1                         host/Native Installation) A              ____________________________________________________ J              You must specify the following items during the installation:A              ____________________________________________________,  <              Item             Notes               Your ValueA              ____________________________________________________u    -              Destination      Choose your ownl*              name             unique name.*                               Example: HQ1  *              Destination      Node name of*              node name        Access node.-                               Example: BASEAC   *              Destination      Range = 0 to,              priority         255. Default =!                               200                                           N           2-8  VAX P.S.I. (Packetnet System Interface) Installation Procedures                 ?              Table 2-2 (Cont.)  X25-SERVER Database Information.@                                 (Multi-host/Native Installation)A              ____________________________________________________s@              Specifying the following items during the installa-              tion is optional:A              ____________________________________________________   9              Item             Notes            Your ValueeA              ____________________________________________________h    -              Call mask        Value between 2i-                               and 32 hexadec- *                               imal digits.-                               Example: FF00FEt  -              Call value       Value between 2V-                               and 32 hexadec-m*                               imal digits.-                               Example: FF5053t                                    A           Installation Preparations                           2-9o e               ?              Table 2-2 (Cont.)  X25-SERVER Database Information @                                 (Multi-host/Native Installation)A              ____________________________________________________ @              Specifying the following items during the installa-              tion is optional:A              ____________________________________________________g      d8              Item             Notes           Your ValueA              ____________________________________________________t    ,              Closed User      Name of closed(              Group (CUG)      user group+                               which has ac-m*                               cess to this,                               destination. 1+                               to 16 charac- ,                               ters. Example:"                               CUG1  ,              Sending address  Remote DTE ad-)                               dress which.+                               has access toi+                               this destina-t,                               tion. Example:+                               2405998887776I  ,              Subaddress       Accepted range-              Range            of subaddressess*                               indicated in,                               incoming call.,                               Example:_33-34B              _____________________________________________________            O           2-10  VAX P.S.I. (Packetnet System Interface) Installation Procedurese                 ?              Table 2-3  X25-ACCESS Database Information (AccessE%                         Installation)uA              ____________________________________________________lJ              You must specify the following items during the installation:A              ____________________________________________________t  <              Item             Notes               Your ValueA              ____________________________________________________   *              Network name     Unique name.+                               Has to be thed-                               same as the onet*                               given during,                               the Multi-host+                               installation.t-                               Example: SWED01   *              Connector node   Name of node,              name             routing you to,                               PSDN. Example:$                               ROUT01                                          A           Installation Preparations                          2-11  l  -            ?              Table 2-3 (Cont.)  X25-ACCESS Database Information 5                                 (Access_Installation)aA              ____________________________________________________ @              Specifying the following items during the installa-              tion is optional:A              ____________________________________________________a  9              Item             Notes            Your ValueaA              ____________________________________________________     ,              Username         As required by*                               destination.*                               Not required*                               by a VAX PSI*                               Access node.  ,              Password         As required by*                               destination.*                               Not required*                               by a VAX PSI*                               Access node.  ,              Account Name     As required by*                               destination.*                               Not required*                               by a VAX PSI*                               Access node.  ,              Object Id        As required by*                               destination.,                               VAX PSI Access(                               requires a*                               value of 36.E              ________________________________________________________           O           2-12  VAX P.S.I. (Packetnet System Interface) Installation Procedures                  7           2.6 Disk Space and SYSGEN Parameters Requiredm  B              To check that you have enough disk space and the cor-D              rect SYSGEN parameters to install and run VAX PSI, fol->              low the instructions in Sections 2.6.1 and 2.6.2.  6           2.6.1 Disk Space Required to Install VAX PSI  D              To check you have enough space on your target disk, en-              ter this command:    *                $ SHOW DEVICE SYS$SYSDEVICE  A              Make sure that there is enough space to install your C              system by consulting Table 2-4. (If you try to install_E              either of the VAX PSI products with too few free blocks, 3              the installation procedure will fail.)   >              Table 2-4  Disk Space Required to Install VAX PSI*                         and VAX PSI AccessE              ________________________________________________________h6                                              Native or@              Product Type                    Multi-host   AccessE              ________________________________________________________   ?              Basic Product                   3150          2650   ?              Basic Product with X.29 sup-    3700          3200h              port   ?              Basic Product with Utilities    3950          3450               support  ?              Basic Product with X.29 and     4500          4000               Utilities supportE              ________________________________________________________             A           Installation Preparations                          2-13                  9           2.6.2 SYSGEN Parameters Required to Run VAX PSIe  C              Your VAX PSI system requires the SYSGEN parameter val- D              ues detailed in Table 2-5. Alter the parameters by run-B              ning SYSGEN or permanently allocate the SYSGEN param-E              eters by editing MODPARAMS.DAT and running AUTOGEN. Both L              processes are described in the VMS manual, Guide to Maintaining              a System.                                                                  O           2-14  VAX P.S.I. (Packetnet System Interface) Installation Procedures  i  t            /              Table 2-5  SYSGEN Parameter Values_A              ____________________________________________________ "                            Minimum.              Resource      Amount        NotesA              ____________________________________________________     <              NPAGEDYN      85K bytes     For Multi-host only  8                            40K bytes     For Access only  8                            90K bytes     For Combination  1                            13K bytes     For X.29n  ;                            1K bytes      For each local DTE=?                                          (Multi-host and combi- 5                                          nation only)e  >                            1.5K bytes    For each virtual cir-1                                          cuit [1]t  >                            12K bytes     For each process run-3                                          ning Trace_  A              ____________________________________________________g  ?              NPAGEVIR      Same as       Change this to reflect_=                            NPAGEDYN      the maximum value ofI1                                          NPAGEDYN   A              ____________________________________________________   >              IRPCOUNT      2             For each concurrently?                                          active virtual circuittA              ____________________________________________________C?              [1] 1.5K bytes is the correct value if you use then=              default packetsize and windowsize. If you do not ?              use the defaults, calculate the amount of resource ,              required by using this formula:>                 2 * windowsize * (packetsize + 96) + 700 bytesA              ____________________________________________________   A           Installation Preparations                          2-15_ _  _            A              NPAGEDYN is the size of the variable length nonpagedwD              dynamic pool space following a system reboot. Alter theC              amount of space to reflect the number of bytes used by A              the data structures required by VAX PSI. If there is A              insufficient NPAGEDYN to load VAX PSI, the following               error appears:o  A              %PSI-F-INSFMEM, insufficient non-paged memory to run               VAX PSI  F              NPAGEVIR is the maximum size to which the variable length9              nonpaged dynamic pool space can be extended.h  B              IRPCOUNT reflects the I/O load the system is required              to handle.                                                     O           2-16  VAX P.S.I. (Packetnet System Interface) Installation Procedures                                A           ______________________________________________________3   A                           Installing Native or Multi-host VAX PSIe        C              This chapter explains how to install the VAX PSI soft- E              ware for Native mode and Multi-host mode systems. During B              the installation, you will need to provide the infor-A              mation you supplied in Tables 2-1 and 2-2 in Chapter               2 of this manual.  /              Before beginning the installation:   I               1. Work through the Installation Preparations in Chapter 2.   B               2. Log in to the system manager's account, or an ac-.                 count with similar privileges.  C               3. Check that the disk which will receive the VAX PSI D                 software is the default disk. Typically, this is theB                 system disk (with the logical name SYS$SYSDEVICE).  B               4. Check that you have a backup of your system disk.  <           3.1 Installing VAX PSI Files from the Distribution               Volumes   C              To start the installation procedure, enter the follow-u              ing command:   :                $ @SYS$UPDATE:VMSINSTAL PSI ddcu: OPTIONS N  A           Installing Native or Multi-host VAX PSI             3-1  n  t            ;              The format for the device name is ddcu: where:   C              dd is the device code, c is the controller letter, and 5              u is the unit number. For example, CSA1:                                                                           N           3-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures                 $              The procedure displays:      N                           VAX/VMS Software Product Installation Procedure V5.1  5                                   It is date at time.   >                Enter a question mark (?) at any time for help.  M                * Are you satisfied with the backup of your system disk [YES]?   B              Make sure you have a good backup copy of the disk, asD              the installation will write to the system disk. If yourC              system disk has not been backed up or you wish to make D              a fresh copy, answer NO. The procedure then exits with-F              out installing the VAX PSI software. When you have backedE              up your system disk, you can start the installation pro-d              cedure again.  7              If you answer YES, the procedure displays:.  A                Please mount the first volume of the set on device                   * Are you ready?   D              Load the distribution volume (PSI) in the drive. AnswerD              YES when you are ready to continue. If a console medium;              is not mounted, the following message appears:n  <                %SYSTEM-F-DEVNOTMOUNT, device is not mounted.  $              The procedure displays:  6                %MOUNT-I-MOUNTED, PSI mounted on device  8                The following products will be processed:                       VAX PSI   4.3  A                    Beginning installation of VAX PSI V4.3 at time   C                %VMSINSTAL-I-RESTORE, Restoring product saveset A...   A           Installing Native or Multi-host VAX PSI             3-3  G  p            <              You will then be asked about the Release Notes.                                                                                N           3-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures                            3.1.1 Release Notes   E              The procedure displays the options for printing and dis-oD              playing the Release Notes. You are recommended to printA              and read the Release Notes before continuing the in-u              stallation.  D              Release notes included with this kit are always copied               to SYS$HELP.q  0                Additional Release Notes Options:  '                1. Display release notes_  %                2. Print release notes_                  3. Both 1 and 2  #                4. None of the aboveP  !                Select option [2]:h  A              Select one of these options. DIGITAL recommends that_B              you choose Option 2. If you select Option 1, the fol-7              lowing file is displayed on your terminal:p  ?                  VMI$ROOT:[SYSUPD.PSI043]PSI043.RELEASE_NOTES;1P  A              The Release Notes are displayed on your terminal and 1              will start scrolling on your screen.   A              If you select Option 2, you are asked on which queue_-              you wish the file to be printed:   (                * Queue name [SYS$PRINT]:  8              Enter <RET> or specify another print queue.  A              If you select Option 3, you are asked on which queue A              you wish the file to be printed and then the Release A              Notes will be displayed on your terminal. If you se- H              lect Option 4, the release notes are copied to the SYS$HELP)              directory and not displayed.U  A           Installing Native or Multi-host VAX PSI             3-5  d  o            A              When the Release Notes have been queued to a printer D              and/or displayed on your terminal or moved to SYS$HELP,               the procedure asks:  >                * Do you want to continue the installation [N]?  D              If you enter <RET>, you can stop the procedure and readB              the Release Notes. If you do this, the following mes-              sage is displayed:_    0                VMSINSTAL procedure done at hh:mm  B              While reading the Release Notes, check for any issuesB              that are likely to affect the installation of the VAXA              PSI software. The VMSINSTAL procedure creates a file A              for the Release Notes called PSI043.RELEASE_NOTES ineA              the SYS$HELP: directory and the following message is               displayed:   J                %VMSINSTAL-I-RELMOVED, The products release notes have been.                successfully moved to SYS$HELP.  E              If you stop VMSINSTAL to read the Release Notes, restart =              the procedure by entering the following command:   6                $ @SYS$UPDATE:VMSINSTAL PSI device-name  *           3.1.2 Tailoring the Installation  C              If you do not stop VMSINSTAL, or if you have restarted B              the procedure, VMSINSTAL will continue to install the;              VAX PSI software. The procedure then displays:_  >                          VAX PSI V4.3 installation procedures.            N           3-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures    t            C              During the installation, the procedure checks the fol-               lowing:  C               1. That the operating system is VMS V5.1 or later. IfsB                 the operating system is an earlier version of VMS,B                 the procedure exits after displaying the following                 message:  L                   This product requires VMS version V5.1 or later to install  L                   %VMSINSTAL-E-INSFAIL, The installation of VAX PSI V4.3 has                   failed  D               2. That there is sufficient space on your disk for theB                 VAX PSI files. Refer to Section 2.6.1 in Chapter 2D                 for details of how many free blocks you need on yourA                 system to install VAX PSI. If there is not enoughXD                 space, the procedure exits after displaying the fol-                  lowing messages:  K                   %PSI-E-NOSPACE, this installation requires nnnn blocks ofu                   disk space. L                   %VMSINSTAL-E-INSFAIL, The installation of VAX PSI V4.3 has                   failed.a  D                 Make sure your system has sufficient free blocks be-5                 fore trying to install VAX PSI again.                             A           Installing Native or Multi-host VAX PSI             3-7e n  l            C              The procedure then asks if you want to install the VAX_A              PSI options. If you do, you must answer YES (the de- E              fault answer) to the question about the option you want.p    )                                      NOTE   9                         You cannot install the options at.:                         a later stage without reinstalling5                         the complete VAX PSI product.a  A              If you are installing VAX PSI on a VAXcluster with a A              common system root, every system in the cluster must D              be set up to support the same VAX PSI options. You mustA              therefore provide identical answers to the questions B              about options for each system. The procedure displays$              the following question:  0                * Do you want X.29 support [YES]?  ;              Answer NO if you do not want support for X.29.   %              The procedure then asks:C  5                * Do you want all the utilities [YES]?   C              Answer YES if you want all the utilities. DIGITAL rec-oC              ommends that you install all of the VAX PSI utilities. D              If you answer NO, you will be asked which utilities youB              want. If you do not want a particular utility, answer,              NO to the appropriate question.  I              If you do not have PSI_SECURITY.COM installed in SYS$MANAGER E              on your system, then the new PSIAUTHORIZE keypad is sup-               plied in.+              SYS$LIBRARY:PSIAUTHORIZE.INIT.   J              If you already have PSI_SECURITY.COM installed in SYS$MANAGERE              on your system, then the new PSIAUTHORIZE keypad is sup-               plied inuA              SYS$LIBRARY:PSIAUTHORIZE.TEMPLATE, and the followingu"              message is displayed:  N           3-8  VAX P.S.I. (Packetnet System Interface) Installation Procedures o  a                            Attention.                 ==========w  J                You have an existing PSI_SECURITY.COM file in SYS$MANAGER. G                If you choose not to have the VAX PSI security utility, iJ                by answering "NO" to the following question, the file will                 be deleted.  8                * Do you want the Security utility [YES]?  :                * Do you want the Accounting utility [YES]?  5                * Do you want the Trace utility [YES]?a  3                * Do you want the KDA utility [YES]?i  D              The procedure continues and displays the following mes-              sages:   N                There are no more questions to answer during this installation.  C                %VMSINSTAL-I-RESTORE, Restoring product saveset B... C                %VMSINSTAL-I-RESTORE, Restoring product saveset C... C                %VMSINSTAL-I-RESTORE, Restoring product saveset D... C                %VMSINSTAL-I-RESTORE, Restoring product saveset E...p  E              Saveset D is copied only if you have requested X.29 sup-iA              port. Saveset E is copied only if you have requested *              some or all of the utilities.  A              There may be a time delay of several minutes at this A              stage in the procedure. As you have now answered all D              the questions for this stage of the installation, thereA              is no need to watch the output. You will be requiredoA              to answer more questions after the "VMSINSTAL proce- 5              dure done at time" message is displayed.S  A              When the last saveset has been copied, the procedure C              copies the distribution files from the subdirectory ofiF              SYS$UPDATE to their respective directories. (See AppendixB              D for details of which files are installed into whichC              directories.) You may, if you wish, remove the distri-l8              bution media from the device at this stage.  A           Installing Native or Multi-host VAX PSI             3-9i :               B              If there are files from a previous VAX PSI or VAX PSIA              Access installation present on your disk, the proce-hB              dure deletes the obsolete files and displays the fol-              lowing message:  N                Removing obsolete files from any previous VAX PSI installation.  C              If you decide to cancel the installation of VAX PSI at B              any time by entering <CTRL/Y>, after a short time de--              lay, the following is displayed:t  D                %VMSINSTAL-F-CTRLY, Installation canceled via CTRL/Y.G                %VMSINSTAL-F-UNEXPECTED, Installation terminated due to                   unexpected event.  >                               VMSINSTAL procedure done at time  E              If you enter <CTRL/Y> after the information message thattE              the files are being moved to the target directories (see B              below), your system will have some new and (if previ-D              ously installed) some old VAX PSI files. Therefore, you*              should reinstall the product.  7              The procedure then displays the following:g  -                Installing VAX PSI V4.3 files.d  C              If you have a previous installation of VAX PSI on yourtA              system, a series of messages may be displayed. TheseeC              messages tell you which of the existing files will notDC              be updated. If you do not have a previous installationn:              of VAX PSI, these messages are not displayed.  7              The procedure then displays the following:   ,                VAX PSI V4.3 files installed.  F              After displaying the above messages, the procedure checks              that:  B               1. The VAX PSI product license has been installed onB                 the system. If the license has not been installed,  O           3-10  VAX P.S.I. (Packetnet System Interface) Installation Procedures     t            D                 then the procedure warns you with the following mes-                 sage:A  J                   %PSI-W-NOLICENSE, P.S.I. has not been licensed to run on                   this system   D               2. The MAXBUF SYSGEN parameter is the correct size. IfA                 the MAXBUF parameter value is too small, the pro- <                 cedure warns you with the following message:  N                   %PSI-W-SYSGEN, MAXBUF is too small, change from nnn to 1536.  C                 where nnn is the current value of the MAXBUF param-                  eter.   C                 Change the value of the MAXBUF SYSGEN parameter af- /                 ter you have installed VAX PSI.   D               3. No previous version of VAX PSI has been run on yourA                 system since the last system boot. If VAX PSI hasl?                 been run, the procedure displays the following:   O                   %PSI-W-PSIRUN, previous version of VAX PSI has been run since &                   the last system boot  )              The procedure then displays:t  K                To complete the installation, follow the instructions below:   L                - Execute the command procedure SYS$MANAGER:PSI_SET_UP.COM toM                  produce a LOAD_PSI043.COM and set up the permanent database.a  >              If a license is required, the procedure displays:  4                - Install the P.S.I. Product License.  A              Refer to Section 2.2 in Chapter 2 for details on howb,              to install the Product License.      A           Installing Native or Multi-host VAX PSI            3-11p e  e            B              If the SYSGEN parameters need updating, the procedure              displays:  8                - Update the specified SYSGEN parameters.  C              If the system needs rebooting, the procedure displays:n  #                - Reboot the system.   A              If the system does not require rebooting, the proce-               dure displays:o  I                - On a system which is running DECnet, execute the commandnH                  procedure SYS$MANAGER:STARTPSI.COM to bring up VAX PSI.E                  On a system which is not running DECnet, execute the G                  command procedure SYS$MANAGER:STARTNET.COM to bring up $                  DECnet and VAX PSI.    N                %VMSINSTAL-I-MOVEFILES, files will now be moved to their target                directories...s    G                          Installation of VAX PSI V4.3 completed at timei  )              The procedure then displays:P  L                Enter the products to be processed from the next distribution                volume set.                  * Products :u  A              Press <CTRL/Z> to stop entering products and move ons               to the next prompt.  C              If you mounted the distribution kit on the console de-s*              vice, the procedure displays:  >                * Do you want to mount the console volume [NO]?    O           3-12  VAX P.S.I. (Packetnet System Interface) Installation Procedures                  3              Answer YES and the procedure displays:a  (                Please mount it on CSA1:.  5              Replace the console volume in the drive.                  The procedure asks:                  * Are you ready?   A              Answer YES to this question. The procedure continues               with:  9                %MOUNT-I-MOUNTED, CONSOLE mounted on CSA1:t  =                              VMSINSTAL procedure done at timeE  F              After installing the software, execute the PSI_SET_UP.COM              procedure. E              Continue the installation procedure by entering the fol-.              lowing commands:l  (                $ SET DEFAULT SYS$MANAGER                $ @PSI_SET_UP  C              After running PSI_SET_UP.COM, update the SYSGEN param-i              etersB              (see Section 2.6.2 in Chapter 2) and reboot if neces-D              sary. To check the installation, refer to the VAX P.S.I              Management Guide.             3.2 Tailoring VAX PSIA  B              When you have reached this stage of the installation,B              you will have built a Native mode VAX PSI system. The              next steps are:  4               1. Set up devices - see Section 3.2.1.  J               2. Define the connection to the PSDN(s) - see Section 3.2.2.  A           Installing Native or Multi-host VAX PSI            3-13  D  o            D               3. If you want a Multi-host VAX PSI system, modify the?                 Native mode VAX PSI system - see Section 3.2.3.]  D              Before tailoring the VAX PSI system, make sure you haveD              the following information for each device that you will              use with VAX PSI:                 _ CSR addressA                 _ Vector address  E              You also need to know the subscription options that havetA              been taken out with each PSDN you are connecting to.s              These include:I                 _ DTE address(es)s  /               _ Logical Channel Number range(s)l  B              Refer to the completed Table 2-1 in Chapter 2 for theB              information you need to supply for your system. WhileB              running PSI_SET_UP.COM, you may enter a question mark8              (?) as a response to any question for help.  C              The documentation of the next part of the installationiC              has been divided into three sections (3.2.1 Setting UpwE              Devices, 3.2.2 Configuring the Permanent Database, 3.2.3NA              Setting Up VAX PSI for Multi-host Working). You willSC              be asked to refer to each section in turn and then re- ;              turn to the point where you left this section.c  :              The procedure displays the following message:  E                This command procedure assists in configuring VAX PSI.e  P                LOAD_PSI043.COM must be built before attempting to start VAX PSI.O                The load file from an earlier version of VAX PSI cannot be used.N  >                Do you wish to build LOAD_PSI043.COM now [YES]?  A              Answer YES if you want to build LOAD_PSI043.COM now.               Refer tolB              Section 3.2.1 for details of building LOAD_PSI043.COM$              and setting up devices.  O           3-14  VAX P.S.I. (Packetnet System Interface) Installation Procedures  v  s                           The procedure asks:  N                Do you wish to add network, line or DTE entries to the database                now [YES]?i  A              Answer YES if you want to add new information to the 6              database - see Section 3.2.2 for details.  %              The procedure then asks:   C                Do you wish to add VAX PSI Multi-host entries [YES]?   N              Answer YES if you require a Multi-host system - see Section 3.2.3              for details.i  C              Answer NO if you require a Native mode VAX PSI system, B              in which case you are now ready to load and start VAXC              PSI and should refer to the procedures in Section 3.3.P               The procedure asks:  4                Do you wish to load VAX PSI now [NO]?  B              Answer YES if you want to load VAX PSI. If you answerA              NO, VAX PSI will not be loaded. Refer to Section 3.3i4              for details of how to start up VAX PSI.  C              If VAX PSI is already running on your system, the fol-i!              lowing is displayed.   G                A version of VAX PSI is already running on this system.  J                In order to load the new configuration and device drivers, .                you need to reboot your system.  L                To check your installation after restarting VAX PSI, refer toN                the Configuration Testing chapter in the  VAX P.S.I. Management                Guide.b  A              If you do not need to reboot your system, and DECnetbB              is already running, then you should answer YES if you"              want to load VAX PSI.  A           Installing Native or Multi-host VAX PSI            3-15  l  n            )                                      NOTEI  8                         If you need to change the SYSGEN8                         parameters (see Section 2.6.2 in9                         Chapter 2), do so before attempt- 8                         ing to load VAX PSI or check the?                         installation. After making the changes, 8                         reboot the system. You will also9                         have to reboot if you have a pre-o:                         vious version of VAX PSI installed;                         and wish to reload VAX PSI or check )                         the installation.   D              If VAX PSI fails to load, the following message is dis-              played:  %                Failed to load VAX PSI   E              If VAX PSI fails to start, the following message is dis-               played:  '                Failed to set up VAX PSIb  B              For information on problem diagnosis and solving, re-9              fer to the VAX P.S.I. Problem Solving Guide.e  J              To check your installation refer to the VAX P.S.I. Management              Guide.e  B              Your Native or Multi-host VAX PSI system is now readyK              to be started. Follow the procedures described in Section 3.3.i  "           3.2.1 Setting Up Devices  B              This section describes how to set up the devices used-              to communicate with the PSDN(s).   A              You can exit from this procedure at any time by typ-iD              ing <CTRL/Z> in response to a request for input. If youA              exit by typing <CTRL/Z>, LOAD_PSI043.COM is not cre-               ated.  O           3-16  VAX P.S.I. (Packetnet System Interface) Installation Proceduresh y  m            :              The procedure displays the following message:  E                This command file assists in creating LOAD_PSI043.COM.p  A              LOAD_PSI043.COM is a command file used to set up thewD              VAX PSI supported devices using SYSGEN and start up the              ACP.T  %              The procedure then asks:   =                Do you want to set up a default network [YES]?   B              If you answer YES, the procedure asks you to supply a<              network name to serve as a system-wide default:  C                Default network name                   (network-id):   D              Enter the name of the network you want to set up as the-              default network for your system.e  A              If you answer NO, you will be given a further oppor-sB              tunity to specify a default network at a later stage.=              See the VAX P.S.I. Management Guide for details.n  )                                      NOTE   ;                         If there is only one network in then8                         database it is not automatically9                         used as the default. You must ei-s8                         ther specify that network in all;                         outgoing calls, or define that net- ,                         work as the default.  C              If you have a previous version of VAX PSI installed onR5              your system, the procedure now displays:   /                Checking old configuration data.a  B              Your previous installation detailed the following de-A              vice(s). You will be given the option to keep, alterEB              or delete each entry in turn, and then optionally add              new devices.   A           Installing Native or Multi-host VAX PSI            3-17     p            E              Details of existing devices are displayed as in the fol-               lowing example:  2                Configuration data for line DUP-0-0  1                Device CSR is             %O760050I  1                Device VECTOR is          %O000300e  ,                Device unibus adapter is  UB0  M                Do you want to Keep, Alter or Delete this entry (K, A, D) [K]?t  B              Answer K if you want to keep the entry, D if you wantC              to delete it, or A if you want to alter it. If you an-s8              swer K, the following message is displayed:  =                Device device-name added to new configuration.   A              If you answer D, the following message is displayed:h  J                Configuration data for device device-name has been deleted.  B              If you answer A, the procedure asks for the CSR, vec-F              tor and adapter in the same way as for defining new linesD              (see below). The defaults will be the same as those forB              the previous installation, and each may be altered as              necessary.i  I              The procedure will ask you about each entry in your database E              from the previous installation. When each entry has beenu)              checked, the procedure asks:   8                Do you want to configure more lines [NO]?  B              Answer YES if you want to add more lines to your con-<              figuration and then answer the questions below.  A              If you have no devices defined from previous instal-rD              lations, or this is the first time VAX PSI is being in-B              stalled on your system, answer the questions below in<              order to configure the devices for your system.  O           3-18  VAX P.S.I. (Packetnet System Interface) Installation Procedures  s  e                           The procedure asks:  %                Device type (dev-c-u):n  A              Enter the type of the first device to be configured. C              The permitted device types for Unibus systems are DMF,hD              DUP, KMX, and KMY. If you enter any other device types,$              the procedure displays:  *                Error, unknown device type.  <                Supported devices are DMF, DUP, KMX, and KMY.                  Examples:                         DMF-0b                       DUP-0                        KMX-0-1i                       KMY-1   B              The permitted device types for BI systems are DMB andA              DSB. If you enter any other device types, the proce-d              dure displays:   *                Error, unknown device type.  1                Supported devices are DMB and DSB.a                  Example:                          DMB-0t                       DSB-0a  A              The permitted device types for Qbus systems are DPV,:C              KMV, DIV and DSV. If you enter any other device types, $              the procedure displays:  *                Error, unknown device type.  ;                Supported devices are DPV, KMV, DIV and DSV.                   Examples:  A           Installing Native or Multi-host VAX PSI            3-19                                       DPV-0                      KMV-0e                     DIV-0-0c                     DSV-0-0d    C              The permitted device types for busless systems are DSTyC              and DSH. If you enter any other device types, the pro-t              cedure displays:l  *                Error, unknown device type.  1                Supported devices are DST and DSH.o                  Examples:                       DST-0E                     DSH-0S  C              If you have entered a wrong device type, the procedure )              will ask again for a device.o  B              If the device type is DMF, DMB, DSB, DSV, DIV, DSH or)              DST, the procedure displays:n  5                SYSGEN autoconfigures the device-name,s/                no further information required.   8                Do you want to configure more lines [NO]?  A              If you have more lines to configure, answer YES, and E              the procedure asks again for the device type. Otherwise, C              answer NO, and the procedure completes by asking about "              PSI MAIL (see below).  A              If the device type is DUP, KMX, KMY, DPV or KMV, theiB              procedure asks for the CSR address and vector address              of the device.   )                                      NOTE   8                         If you are installing VAX PSI on:                         a machine other than the MicroVAX,?                         the procedure also asks for the adaptero+                         type of the device.)  O           3-20  VAX P.S.I. (Packetnet System Interface) Installation Procedures                  B              The default values for these parameters are also dis-C              played. Enter the required addresses and adapter type,eC              or choose the defaults by pressing <RET>. For example,X"              for a KMX-0-0 device:  .                Default CSR address is %0764100*                CSR address (octal): 764120  )                Default VECTOR is %0000700g#                Vector (octal): 720):  %                Default ADAPTER is UB0 ,                Adapter (adapter-type): <RET>  B              The procedure now checks that the device has been setD              up correctly by displaying the values that you have se-B              lected, and also asks for confirmation that these are              correct.   2                Configuration data for line KMX-0-0  0                Device CSR is            %0764120  0                Device VECTOR is         %0000720  +                Device UNIBUS adapter is UB0o  7                Are these line parameters correct [YES]?n  A              If the line parameters are wrong, answer NO, and the A              procedure asks again for the device type. Otherwise, 3              answer YES and the procedure displays:   5                Device KMX-0-0 added to configuration.e  8                Do you want to configure more lines [NO]?  B              If you answer YES, the procedure asks again for a de-A              vice type. If you specify the same device again, the &              procedure warns you with:  ,                Error, duplicate device name.  A           Installing Native or Multi-host VAX PSI            3-21     L            5              Otherwise, the procedure continues with:V  F                The following NCP command may be used to configure the E                permanent database to support incoming X.29 terminals:t  4                NCP define module X29-server state on  :                Do you want the database defined now [YES]?  C              If you answer YES, X.29 support is enabled. Answer NO,f?              and support is unmodified from the previous state.   %              The procedure next asks:o  1                Do you want to use PSI MAIL [YES]?   B              The PSI MAIL utility allows VAX/VMS MAIL to send mailC              over a PSDN to other VAX PSI V3.0 or later systems. If A              you want to be able to use this utility, answer YES.s  B              If you answer NO to this question, the procedure con-0              tinues and creates LOAD_PSI043.COM.                Otherwise it asks:t  ?                Do you want support for incoming PSI MAIL [YES]?s  C              If you answer NO, you can still send PSI MAIL, but you               cannot receive it.   $              The procedure displays:  O                The PSI_MAIL object needs to run in an account with the right toI*                accept incoming X.25 calls.  A              If you answer YES, you must also define the usernameo?              and password for PSI MAIL. The procedure displays:f  "                Username [DECNET] ?                  Password ?                   Verification:  O           3-22  VAX P.S.I. (Packetnet System Interface) Installation Procedures     n            A              The username and password can be any that can accept D              incoming X.25 calls. Refer to the VAX P.S.I. ManagementA              Guide for details of setting up the system to accept B              X.25 calls. The default username is DECNET. (You willB              be asked to verify your password before being allowed              to continue.)  8              The procedure continues with the following:  P                The following NCP commands may be used to configure the permanent5                database to support incoming PSI MAIL:n  9                NCP define object psi_mail number 0 file -g?                    sys$system:psi$mail user USERNAME password -                     PASSWORD   B                NCP define module x25-server destination psi_mail -$                    object PSI_MAIL -?                    CALL MASK ffffffffffffffffffffffffffffffff - >                    CALL VALUE ff00000056332E30204D41494C2D3131  A              The call mask is applied to the user-data field, and)B              determines whether the incoming call is accepted. TheB              call value specifies the string used to test incoming              call data.o  %              The procedure then asks:o  :                Do you want the database defined now [YES]?  D              Answer YES if the NCP commands listed that will be usedD              to configure the database are correct. Answer NO if anyA              of the commands are incorrect, and then run PSI_SET_ B              UP.COM again, or enter the NCP commands as a separate1              operation to configure the database.   0              The following message is displayed:  K                Purging any previous PSI_MAIL definitions. Please ignore anyo                error messages.  A           Installing Native or Multi-host VAX PSI            3-23k e  y            A              There is a short delay while LOAD_PSI043.COM is cre-p/              ated. Then the procedure displays:-  :                Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COM  A              After this message is displayed, return to where yous              left Section 3.2.  C              If your default directory is not SYS$MANAGER, the pro-p              cedure displays:   N                The VAX PSI startup file should be moved into SYS$MANAGER to be1                used automatically by STARTNET.COM   F                Do you want LOAD_PSI043.COM moved to SYS$MANAGER [YES]?  C              If you answer YES, the procedure moves LOAD_PSI043.COMd              into theeB              SYS$MANAGER directory and displays the following mes-               sage before ending:  :                Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COM  D              If you answer NO, the procedure creates LOAD_PSI043.COMA              in your current directory, displays a message saying )              where the file is, and ends.o  B              Return to where you left Section 3.2 to continue your              installation.  2           3.2.2 Configuring the Permanent Database  C              You can exit from this PSI_DEFINE.COM procedure at any A              time by typing <CTRL/Z> in response to a request foriD              input. If you exit by typing <CTRL/Z>, some PSDN or DTEB              definitions may have been created. You can remove un-A              wanted PSDN and DTE definitions by using the follow-e              ing commands:  J                NCP purge module x25-protocol known dtes known networks all?                NCP purge module x25-protocol known networks all   O           3-24  VAX P.S.I. (Packetnet System Interface) Installation Procedures                  B              After the initial running of PSI_SET_UP.COM to defineI              the DTE(s), you may run this procedure again. Alternatively, B              you may use NCP DEFINE commands to define each entityC              in the database and thus configure the VAX PSI system.rD              See the VMS Network Control Program Manual for details.    $              The procedure displays:  B                This command procedure allows you to define one or C                more PSDN(s) and one or more DTE(s) associated with                  each network.  D              The SPD for VAX PSI lists the public networks supported%              at the time of printing.   D              Check with your Customer Support Representative for up-B              to-date information on new networks. You see the mes-              sage:  I                Do you want to define the X25-PROTOCOL database now [YES]?   G              Answer YES if you want to define the X25-PROTOCOL database D              to define the PSDN and DTE(s) associated with each net-              work.  %              The procedure continues:   I                You can use this procedure to purge the database to removeyI                all DTEs and all X.25 protocol information before updatingTI                the permanent database. You can also use this procedure toEJ                remove the line information from the database. Note that ifJ                the line permanent database is purged then all DECnet lines8                along with VAX PSI lines will be removed.  K                The following NCP commands will be used to purge the DTE and0'                X.25 permanent database:   ?                NCP purge module x25-protocol known networks alldJ                NCP purge module x25-protocol known dtes known networks all  H                The following NCP commands will be used to purge the line"                permanent database:  (                NCP purge known lines all  A           Installing Native or Multi-host VAX PSI            3-250                 >                Do you want the information in the X.25 and DTE.                permanent database purged [NO]?  C              If you wish to keep previous definitions for DTEs, an-eD              swer NO. If you answer YES, the following is displayed:  1                Purging the X.25 and DTE database.   %              The procedure then asks:s  I                Do you want the line information in the permanent databaseo                purged [NO]?   D              If you wish to keep previous definitions for lines, in-B              cluding DECnet lines, answer NO. Note that if you an-B              swer YES, all DECnet lines will be deleted along withD              VAX PSI lines. If you answer YES, the following is dis-              played:  )                Purging the line database.   $              The procedure displays:  M                PSDN and profile names are defined here. You can define one orbI                more PSDNs. For each PSDN you will be asked to provide themB                network name and the profile name for that network.                 The procedure asks:  &                Network name  (string):  D              Enter the network name that connects to the PSDN. ReferC              to Section 1.7 in Chapter 1 for details of network and               profile names.o  C                Profile name (string)                [NETWORK NAME]:T  E              Enter the profile name of the PSDN to which the DTE will A              connect. The default name is the same as the networkw              name.  O           3-26  VAX P.S.I. (Packetnet System Interface) Installation Procedures  c  r            C              The procedure then displays the command it will use toe+              update the permanent database.o  M                The following NCP command will be used to update the permanents                database:  C                NCP define module x25-protocol network network-id  - '                    profile profile-names  D                Do you want the information in the permanent database                updated [YES]?   E              If you answer NO to this question, the NCP commands willwA              not be executed. You may enter the commands yourselfmE              later if you wish. The procedure then continues and dis-oG              plays additional messages here, if it deletes any databasen              entries.   D              Answer YES if you want to update the database. The pro-3              cedure displays the following message:V  O                DTEs are defined here. You can define one or more DTEs connectedcM                to this network. For each DTE you will be asked to provide the %                following information:                    .  DTE address  :                 .  Range of channels to be used by the DTE  /                 .  Line associated with the DTEm  B              Refer to the completed Table 2-1 in Chapter 2 for the<              information you need to supply for your system.                 The procedure asks:  %                DTE address  (number):S  A              Enter your DTE address. For details on the format ofPC              this address, refer to the  Public Network Informationo              manual.  &                Channels range  (list):  A           Installing Native or Multi-host VAX PSI            3-27D 9  D            B              Enter the channels that the DTE will use for outgoingF              calls. Specify high-numbered channels before low-numberedA              channels. Each entry in the channels list can be ei- B              ther a single channel number or a channel range (with;              a hyphen separating the high and low numbers).   A              The entries in the list must be separated by commas.               For example:a  8                Channels range (list):1555,1544-1540,1536  A              The PSDN authorities allocate channel ranges at sub-,A              scription time. For details on the channel range al- L              located for your PSDN, refer to the  Public Network Information              manual.  $              The procedure now asks:  #                Line name (dev-c-u):m  F              Enter the name of the line that the DTE will use. SpecifyB              a line-id in the form dev-c[-u]. For all device typesC              except KMX, you need only specify line-id and the con-a)              troller number, for example:[                  KMV-0  B              For the KMX, you must specify the line-id, controller5              number and the unit number, for example:d                  KMX-0-1  $              The procedure displays:  N                The following NCP commands will be used to update the permanent                database:  J                NCP define line line-id  network network-id protocol lapb -                   state on    O           3-28  VAX P.S.I. (Packetnet System Interface) Installation Procedures     i            @                NCP define module x25-protocol dte dte-address  -(                    network network-id  -+                    channels  channel-list -0)                    line line-id  state one  %              The procedure then asks:   F                Do you want to update the permanent database now [YES]?  E              If you answer NO to this question, the NCP commands willeA              not be executed. You may enter the commands yourself E              later if you wish. The procedure then continues and dis-rF              plays additional messages here if it deletes any database              entries.   7              If you answer YES, the procedure displays:R                Updating database.   P              Do you want to define any more DTEs connected to this network [NO]?  C              Answer YES if more DTEs are required for this network. A              The procedure then repeats the questions to define asB              DTE. When you have finished defining all DTEs, answer              NO.  )              The procedure then displays:n  <                Do you want to define any more networks [NO]?  E              Answer YES if you want to define more networks. The pro-yC              cedure then repeats the questions to define DTE(s) fory              the next network.  A              When you have finished defining all networks, answerA              NO.  B              Return to where you left Section 3.2 to continue your              installation.    A           Installing Native or Multi-host VAX PSI            3-29e e               9           3.2.3 Setting Up VAX PSI for Multi-host Working   D              If you intend using VAX PSI as a Multi-host system, youA              need to set up X25-SERVER destinations for those in- A              coming calls destined for Access hosts. You can exitrB              from this procedure at any time by typing <CTRL/Z> in-              response to a request for input.o  C              Destinations will have been set up if you exit by typ-AC              ing <CTRL/Z> after the following message is displayed:   .                Updating the permanent database  A              You can delete the destinations by using the follow-               ing command:u  A                NCP purge module x25-server known destinations alll  :              The procedure displays the following message:  M                X25-Server destinations are set up here. These permit incoming N                calls received by this node to be redirected to the appropriateI                host. This procedure asks for a list of hosts with VAX PSI M                Access installed. This list of nodes will not include the nodec,                you are currently working on.  B              Refer to the completed Table 2-2 in Chapter 2 for the/              destination names for your system.   )              The procedure then displays:n  *                Destination name  (string):  A              Destinations are used by the Multi-host VAX PSI sys-eA              tem to identify the destination of the incoming call C              so that it can be redirected to the correct host node. A              Enter a destination name as a string of up to 16 al-d#              phanumeric characters.s  /                Destination node name  (string):p  O           3-30  VAX P.S.I. (Packetnet System Interface) Installation Proceduresl i  i            D              Destination node is the node where the object, requiredC              by the incoming call, resides. Enter a node name of upo,              to six alphanumeric characters.  ,                Destination priority   [200]:  D              Destination priority is the processing priority for theB              redirection of the incoming call to that destination.:              Priority is an integer in the range 0 to 255.  C              The rest of the parameters are optional. If you do not B              specify them, they will not be checked when an incom-              ing call arrives.  ,                Call mask (2-32 hex)  [None]:  C              The call mask is generally used with a call value, andeC              when applied to the user-data field determines whetheraE              the incoming call is accepted. Enter a hexadecimal value B              between 2 and 32 digits long. If you do not specify aB              mask, the destination accepts all calls with any user              data.  -                Call value (2-32 hex)  [None]:   B              Call value specifies the string used to test incomingC              call data. If the call mask accompanying the user-data D              fields matches the call value, the incoming call is ac-D              cepted. The call value for incoming calls should be set              to 01.o  ;                Closed User Group (1-16 characters)  [None]:i  A              Closed user group specifies which user group (CUG or 1              BCUG) has access to the destination.a  5                Sending address(1-15 decimal)  [None]:d        A           Installing Native or Multi-host VAX PSI            3-31d                 C              This specifies which remote DTE address(es) has accessiC              to the destination. If none is specified, all call re- C              quests from remote DTEs are accepted. Wildcards (* and ,              %) may be used in this address.  8                Subaddress range (decimal range)  [None]:  E              Subaddress is used to determine whether an incoming call,A              is to be accepted. If the subaddress of the incoming A              call is within the range specified, the call request A              is accepted. If no range is specified, call requestsrD              with any subaddress are accepted. Enter only one range,4              for example, 50-99 or 122 or 1010-1234.  6                Object identification (string)    [36]:  D              Set this parameter as required by the destination node.C              VAX PSI requires a value of 36 for this parameter (theT,              default value), so enter <RET>.  $              The procedure displays:  9                The destination will be set up as follows:   .                NCP> define module x25-server -+                     destination dest-name - $                     node dest-node -+                     [call mask call-mask] -b-                     [call value call-value] - &                     [group cug-name] -3                     [sending address dte-address] - 4                     [subaddress sub-address-range] -*                     [priority dest-prio] -&                     [object object-id]  A              Only the fields that you have specified will be dis-n              played.  $              The procedure displays:  @                Do you want to define this destination now [YES]?  O           3-32  VAX P.S.I. (Packetnet System Interface) Installation Procedurese p  t            A              If you answer NO, the procedure will not execute thesC              NCP command as displayed above. If you answer YES, thec               procedure displays:  /                Updating the permanent database.   @                Do you want to define any more destinations [NO]?  C              If you answer YES, the procedure will repeat the aboveaB              questions to allow further destinations to be set up.  C              When you have completed defining all destinations, an--              swer NO.]  B              Return to where you left Section 3.2 to continue your              installation.  !           3.3 Starting Up VAX PSI[  C              If DECnet is running on your system, issue the follow-t*              ing command to start VAX PSI:  +                $  @SYS$MANAGER:STARTPSI.COM   D              If STARTPSI.COM fails, after it has loaded VAX PSI suc-;              cessfully, the following message is displayed:t  '                Failed to set up VAX PSI   D              This means that the Security or Trace utilities, and/orG              lines and DTEs may have been set up incorrectly. ReinstallaA              VAX PSI, ensuring that the lines, DTEs and utilitiesP"              are set up correctly.  D              If DECnet is not running on your system, issue the fol-B              lowing command, which starts both DECnet and VAX PSI:  +                $  @SYS$MANAGER:STARTNET.COM       A           Installing Native or Multi-host VAX PSI            3-33                  A              If you try to start VAX PSI before DECnet is runningtC              with the STARTPSI command procedure, the following er-r=              ror message is displayed and the procedure ends:   H                DECnet must be running before attempting to start VAX PSI  )                                      NOTEh  9                         To restart DECnet and VAX PSI au- <                         tomatically when you reboot the sys-<                         tem, edit the STARTNET command given"                         above into5                         SYS$MANAGER:SYSTARTUP_V5.COM.n  A              If you wish to configure or modify your VAX PSI sys-w;              tem, refer to the VAX P.S.I. Management Guide.a  C              DIGITAL recommends that you check the installation and B              configuration of your VAX PSI system. Follow the pro-B              cedures described in the VAX P.S.I. Management Guide.  E              Finally, when you have installed and configured VAX PSI,eD              and checked that the system is installed properly, backA              up the updated system disk and save the distributions               kit for future use.                                O           3-34  VAX P.S.I. (Packetnet System Interface) Installation Proceduresi s  o                          A           ______________________________________________________4n  A                                         Installing VAX PSI Accessm        F              This chapter explains how to install VAX PSI Access soft-C              ware. During the installation you will need to provideqC              the information you supplied in Table 2-3 in Chapter 2f              of this manual.  /              Before beginning the installation:l  I               1. Work through the Installation Preparations in Chapter 2.c  B               2. Log in to the system manager's account, or an ac-.                 count with similar privileges.  C               3. Check that the disk which will receive the VAX PSI D                 Access software is the default disk. Typically, thisI                 is the system disk (with the logical name SYS$SYSDEVICE).t  6           4.1 Installing VAX PSI Access Files from the"               Distribution Volumes  C              To start the installation procedure, enter the follow-i              ing command:   =                $ @SYS$UPDATE:VMSINSTAL PSI_AC ddcu: OPTIONS Nt  ;              The format for the device name is ddcu, where:s    A           Installing VAX PSI Access                           4-1p s               C              dd is the device code, c is the controller letter, andd6              u is the unit number. For example, CSA1:.  $              The procedure displays:  M                          VAX/VMS Software Product Installation Procedure V5.1   4                                  It is date at time.  >                Enter a question mark (?) at any time for help.    M                * Are you satisfied with the backup of your system disk [YES]?a  B              Make sure you have a good backup copy of the disk, asD              the installation will write to the system disk. If yourB              system disk has not been backed up, answer NO to thisA              question. If you answer NO, the procedure exits, and D              the VAX PSI Access software will not be installed. WhenC              you have backed up your system disk, you can start then*              installation procedure again.  B                Please mount the first volume of the set on device.                  * Are you ready?   G              Load the distribution volume (PSI_AC) in the drive. AnswercD              YES when you are ready to continue. If a console medium;              is not mounted, the following message appears:e  <                %SYSTEM-F-DEVNOTMOUNT, device is not mounted.  $              The procedure displays:  :                %MOUNT-I-MOUNTED, PSI_AC mounted on device.  8                The following products will be processed:                  PSI_AC   V4.3  J                              Beginning installation of PSI_AC V4.3 at time  N           4-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures                 C                %VMSINSTAL-I-RESTORE, Restoring product saveset A...d  <              You will then be asked about the release notes.                                                                            A           Installing VAX PSI Access                           4-3                             4.1.1 Release Notese  E              The procedure displays the options for printing and dis- D              playing the Release Notes. You are recommended to printA              and read the Release Notes before continuing the in-               stallation.  P              Release notes included with this kit are always copied to SYS$HELP.  0                Additional Release Notes Options:  '                1. Display release notesl  %                2. Print release notese                  3. Both 1 and 2  #                4. None of the aboveo  !                Select option [2]:e  A              Select one of these options. DIGITAL recommends thattB              you choose Option 2. If you select Option 1, the fol-7              lowing file is displayed on your terminal:c  E                  VMI$ROOT:[SYSUPD.PSI_AC043]PSI_AC043.RELEASE_NOTES;1u  A              The Release Notes are displayed on your terminal ande1              will start scrolling on your screen.c  A              If you select Option 2, you are asked on which queue -              you wish the file to be printed:   (                * Queue name [SYS$PRINT]:  8              Enter <RET> or specify another print queue.  A              If you select Option 3, you are asked on which queueaA              you wish the file to be printed and then the ReleaselA              Notes will be displayed on your terminal. If you se- B              lect Option 4, the release notes will be moved to the2              SYS$HELP directory and not displayed.  N           4-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures e  d            A              When the Release Notes have been queued to a printer E              and/or displayed on your terminal or copied to SYS$HELP,                the procedure asks:  >                * Do you want to continue the installation [N]?  D              If you enter <RET>, you can stop the procedure and readB              the Release Notes. If you do this, the following mes-              sage is displayed:u  =                             VMSINSTAL procedure done at hh:mme  B              While reading the Release Notes, check for any issuesB              that are likely to affect the installation of the VAXA              PSI software. The VMSINSTAL procedure creates a fileoA              for the Release Notes called PSI_AC043.RELEASE_NOTES A              in the SYS$HELP: directory and the following messaget              is displayed:  J                %VMSINSTAL-I-RELMOVED, The products release notes have been.                successfully moved to SYS$HELP.  E              If you stop VMSINSTAL to read the Release Notes, restart =              the procedure by entering the following command:   ?                $ @SYS$UPDATE:VMSINSTAL PSI_AC device-identifier     *           4.1.2 Tailoring the Installation  C              If you do not stop VMSINSTAL, or if you have restartediB              the procedure, VMSINSTAL will continue to install the;              VAX PSI software. The procedure then displays:t  D                         VAX PSI Access V4.3 installation procedures.            A           Installing VAX PSI Access                           4-5n l               C              During the installation, the procedure checks the fol-a              lowing:  C               1. That the operating system is VMS V5.1 or later. If B                 the operating system is an earlier version of VMS,B                 the procedure exits after displaying the following                 messages:   L                   This product requires VMS version V5.1 or later to installO                   %VMSINSTAL-E-INSFAIL, the installation of VAX PSI Access V4.3e                   has failed.   B               2. If there are any files from a previous VAX PSI orA                 VAX PSI Access installation. If there is a set of B                 VAX PSI V4.3 files present on the disk, the proce-                 dure asks:  C                   Do you wish to install a combination system [NO]?   D                 Answer NO if you wish to install only VAX PSI Access.                 and the files will be deleted.  C                 Answer YES if you want to set up a Combination sys-mI                 tem, and then follow the instructions given in Chapter 5.e  C               3. That there is sufficient space on the disk for thelI                 VAX PSI Access files. Refer to Section 2.6.1 in Chapter 2rD                 for details of how many free blocks you need on yourA                 system to install VAX PSI Access. If there is notXB                 enough space, the procedure exits after displaying'                 the following messages:t  K                   %PSI-E-NOSPACE, this installation requires nnnn blocks of                    disk spaceO                   %VMSINSTAL-E-INSFAIL, the installation of VAX PSI Access V4.3                    has failed.   D                 Make sure your system has sufficient free blocks be-<                 fore trying to install VAX PSI Access again.    N           4-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures    w            C              The procedure then asks if you want to install the VAXiD              PSI Access options. If you do, you must answer YES (theA              default answer) to the question about the option you               want.  )                                      NOTE   9                         You cannot install the options at :                         a later stage without reinstalling5                         the complete VAX PSI product.h  A              If you are installing VAX PSI on a VAXcluster with acA              common system root, every system in the cluster mustmD              be set up to support the same VAX PSI options. You mustA              therefore provide identical answers to the questions B              about options for each system. The procedure displays$              the following question:  0                * Do you want X.29 support [YES]?  ;              Answer NO if you do not want support for X.29.n  5                * Do you want all the utilities [YES]?s  C              Answer YES if you want all the utilities. DIGITAL rec-eC              ommends that you install all of the VAX PSI utilities..D              If you answer NO, you will be asked which utilities youB              want. If you do not want a particular utility, answer,              NO to the appropriate question.  I              If you do not have PSI_SECURITY.COM installed in SYS$MANAGER D              on your system then the new PSIAUTHORIZE keypad is sup-              plied iny+              SYS$LIBRARY:PSIAUTHORIZE.INIT.   J              If you already have PSI_SECURITY.COM installed in SYS$MANAGERD              on your system then the new PSIAUTHORIZE keypad is sup-              plied inrA              SYS$LIBRARY:PSIAUTHORIZE.TEMPLATE, and the followingt"              message is displayed:  A           Installing VAX PSI Access                           4-7                                  Attention.                 ==========   J                You have an existing PSI_SECURITY.COM file in SYS$MANAGER. G                If you choose not to have the VAX PSI security utility,  J                by answering "NO" to the following question, the file will                 be deleted.  8                * Do you want the Security utility [YES]?  :                * Do you want the Accounting utility [YES]?  5                * Do you want the Trace utility [YES]?n  3                * Do you want the KDA utility [YES]?b  D              The procedure continues and displays the following mes-              sages.l  N                There are no more questions to answer during this installation.  C                %VMSINSTAL-I-RESTORE, Restoring product saveset B...SC                %VMSINSTAL-I-RESTORE, Restoring product saveset C...lC                %VMSINSTAL-I-RESTORE, Restoring product saveset D... C                %VMSINSTAL-I-RESTORE, Restoring product saveset E...V  E              Saveset D is copied only if you have requested X.29 sup- A              port. Saveset E is copied only if you have requestedp*              some or all of the utilities.  A              There may be a time delay of several minutes at thisaA              stage in the procedure. As you have now answered allsD              the questions for this stage of the installation, thereA              is no need to watch the output. You will be required A              to answer more questions after the "VMSINSTAL proce- 5              dure done at time" message is displayed.a  A              When the last saveset has been copied, the procedure C              copies the distribution files from SYS$UPDATE to theiroB              respective directories. See Appendix D for details ofA              which files are installed into which directories. IflA              you wish, you may remove the distribution media from_&              the device at this stage.  N           4-8  VAX P.S.I. (Packetnet System Interface) Installation Procedures e  c            B              If there are files from a previous VAX PSI or VAX PSIA              Access installation present on your disk, the proce-mB              dure deletes the obsolete files and displays the fol-              lowing message:  L                Removing obsolete files from a previous VAX PSI installation.  C              If you decide to cancel the installation of VAX PSI atdB              any time by entering <CTRL/Y>, after a short time de--              lay, the following is displayed:S  B              %VMSINSTAL-F-CTRLY, Installation canceled via CTRL/Y.O              %VMSINSTAL-F-UNEXPECTED, Installation terminated due to unexpectedW              event.   9                          VMSINSTAL procedure done at time   E              If you enter <CTRL/Y> after the information message that:E              the files are being moved to the target directories (see B              below), your system will have some new and (if previ-D              ously installed) some old VAX PSI files. Therefore, you*              should reinstall the product.  7              The procedure then displays the following:   4                Installing VAX PSI Access V4.3 files.  C              If you have a previous installation of VAX PSI on yourVA              system, a series of messages may be displayed. TheselC              messages tell you which of the existing files will not C              be updated. If you do not have a previous installation :              of VAX PSI, these messages are not displayed.  7              The procedure then displays the following:   3                VAX PSI Access V4.3 files installed.   E              After displaying the above message, the procedure checkse              that:    A           Installing VAX PSI Access                           4-9e e  e            F               1. The VAX PSI Access product license has been installedE                 on the system. If the license has not been installed,eC                 the procedure warns you with the following message:r  J                   %PSI-W-NOLICENSE, P.S.I.-ACCESS has not been licensed to$                   run on this system  H               2. The MAXBUF parameter is the correct size. If the MAXBUFA                 parameter value is too small, the procedure warnsh/                 you with the following message:   N                   %PSI-I-SYSGEN, MAXBUF is too small, change from nnn to 1536.  C                 where nnn is the current value of the MAXBUF param-d                 eter.i  B                 Change the value of the MAXBUF parameter after you.                 have installed VAX PSI Access.  E               3. No previous version of VAX PSI or VAX PSI Access hasSC                 been run on your system since the last system boot. C                 If VAX PSI or VAX PSI Access has been run, the pro-S.                 cedure displays the following:  O                   %PSI-W-PSIRUN, previous version of VAX PSI has been run sinceu&                   the last system boot  )              The procedure then displays:   K                To complete the installation, follow the instructions below:   L                - Execute the command procedure SYS$MANAGER:PSI_SET_UP.COM toM                  produce a LOAD_PSI043.COM and set up the permanent database.n  >              If a license is required, the procedure displays:  :                - Install the P.S.I.-ACCESS Product License        O           4-10  VAX P.S.I. (Packetnet System Interface) Installation Proceduresb k  o            A              Refer to Section 2.2 in Chapter 2 for details of howo,              to install the Product License.  B              If the SYSGEN parameters need updating, the procedure              displays:  7                - Update the specified SYSGEN parameters   C              If the system needs rebooting, the procedure displays:t  "                - Reboot the system  A              If the system does not require rebooting, the proce-a              dure displays:   I                - On a system which is running DECnet, execute the command-H                  procedure SYS$MANAGER:STARTPSI.COM to bring up VAX PSI.E                  On a system which is not running DECnet, execute thelG                  command procedure SYS$MANAGER:STARTNET.COM to bring upE$                  DECnet and VAX PSI.  N                %VMSINSTAL-I-MOVEFILES, files will now be moved to their target                directories...   A                     Installation of PSI_AC V4.3 completed at time   )              The procedure then displays:   L                Enter the products to be processed from the next distribution                volume set.                * Products :m  A              Press <CTRL/Z> to stop entering products and move one               to the next prompt.  C              If you mounted the distribution kit on the console de-h*              vice, the procedure displays:  >                * Do you want to mount the console volume [NO]?    A           Installing VAX PSI Access                          4-11     s            3              Answer YES and the procedure displays:D  '                Please mount it on CSA1:   5              Replace the console volume in the drive.L                 The procedure asks:                  *Are you ready?  A              Answer YES to this question. The procedure continuesi              with:  9                %MOUNT-I-MOUNTED, CONSOLE mounted on CSA1:   ?                                VMSINSTAL procedure done at timet  F              After installing the software, execute the PSI_SET_UP.COM              procedure.RE              Continue the installation procedure by entering the fol-I              lowing commands:   $                $ SET DEF SYS$MANAGER                  $ @PSI_SET_UP  C              After running PSI_SET_UP.COM, update the SYSGEN param- L              eters and reboot if necessary (see Section 2.6.2 in Chapter 2),A              and then refer to the VAX P.S.I. Management Guide toP$              check the installation.  &           4.2 Tailoring VAX PSI Access  B              When you have reached this stage of the installation,B              you will have built a VAX PSI Access system. The next              steps are:X  B               1. Create LOAD_PSI043.COM which is used to start VAX                 PSIi$                 - see Section 4.2.1.  O           4-12  VAX P.S.I. (Packetnet System Interface) Installation Procedureso a  t            F               2. Define the VAX PSI Access system - see Section 4.2.2.  B              Before tailoring the VAX PSI Access system, make sureD              you have the following information for each network you4              want to add to the X25-ACCESS database:  7               _ The network used by the connector node.%  C               _ The node-id of the connector node serving that net-M                   work.i  (              You will also need to know:  =               _ Whether you want to set up a default network.   .               _ Whether you want X.29 support.  B              Refer to the completed Table 2-3 in Chapter 2 for in-G              formation about your system. While running PSI_SET_UP.COM,eC              you may enter a question mark (?) as a response to anym              question for help.u  C              The documentation of the next part of the installationeO              has been divided into two sections (4.2.1 Creating LOADPSI043.COM, A              4.2.2 Configuring the X25-ACCESS Database). You will C              be asked to refer to each section in turn and then re- ;              turn to the point where you left this section.   :              The procedure displays the following message:  E                This command procedure assists in configuring VAX PSI.   P                LOAD_PSI043.COM must be built before attempting to start VAX PSI.N                The load file from an earlier version of VAX PSI cannot be used  >                Do you wish to build LOAD_PSI043.COM now [YES]?  A              Answer YES if you want to build LOAD_PSI043.COM now.a              Refer to C              Section 4.2.1 for details of building LOAD_PSI043.COM.S                 The procedure asks:  L                Do you wish to add network entries to the database now [YES]?  A           Installing VAX PSI Access                          4-13                  H              Answer YES if you want add new information to the database.0              Refer to Section 4.2.2 for details.  %              The procedure then asks:/  4                Do you wish to load VAX PSI now [NO]?  4              Answer YES if you want to load VAX PSI.  C              If VAX PSI is already running on your system, the fol- !              lowing is displayed.p  O                A version of VAX PSI is already running on this system. In ordertK                to load the new configuration and device drivers you need toa"                reboot your system.  L                To check your installation after restarting VAX PSI, refer toM                the Configuration Testing chapter in the VAX P.S.I. Managements                Guide.   A              If you do not need to reboot your system, and DECneteB              is running on your system, then you should answer YES)              if you want to load VAX PSI.a  )                                      NOTE   8                         If you need to change the SYSGEN9                         parameters, you must do so beforef:                         attempting to load VAX PSI or test:                         the installation. After making theE                         changes, reboot the system (see Section 2.6.2e9                         in Chapter 2). You will also haves8                         to reboot if you have a previous8                         version of VAX PSI installed and:                         wish to reload VAX PSI or test the%                         installation.e  D              If VAX PSI fails to load, the following message is dis-              played:  %                Failed to load VAX PSI   O           4-14  VAX P.S.I. (Packetnet System Interface) Installation ProceduresW L  N            E              If VAX PSI fails to start, the following message is dis-               played:  '                Failed to set up VAX PSI   E              This means that the Security or Trace utilities may havehC              been set up incorrectly. Reinstall VAX PSI Access, en- C              suring that the utilities are set up correctly. If VAX A              PSI loads successfully and if PSI_SET_UP.COM is run- 6              ning, the following message is displayed:  M                To check out your installation after starting VAX PSI refer to..                the VAX P.S.I. Management Guide  C              Your VAX PSI Access system is now ready to be started.c<              Follow the procedures described in Section 4.3.  (           4.2.1 Creating LOAD_PSI043.COM  A              You can exit from this procedure at any time by typ-UD              ing <CTRL/Z> in response to a request for input. If youE              exit by typing <CTRL/Z>, no LOAD_PSI043.COM file is cre- @              ated. The procedure displays the following message:    E                This command file assists in creating LOAD_PSI043.COM.S  K                LOAD_PSI043.COM is a command file used to SYSGEN the VAX PSIn5                supported devices and startup the ACP.t  %              The procedure then asks:-  =                Do you want to set up a default network [YES]?0  A              If your Local Area Network or DECnet network is con-kE              nected to several PSDNs, or to one PSDN but via a choicetA              of several Multi-host VAX PSI nodes, you may specify 5              one network for use as the default PSDN.e      A           Installing VAX PSI Access                          4-15G p  m            B              If you answer YES, the procedure asks you to supply a<              network name to serve as a system-wide default:  2                Default network name  (network-id):  D              Enter the name of the network you want to set up as the-              default network for your system.o  A              If you answer NO, you will be given a further oppor- B              tunity to specify a default network at a later stage.=              See the VAX P.S.I. Management Guide for details.   )                                      NOTE   ;                         If there is only one network in the 8                         database it is not automatically9                         used as the default. You must ei- 8                         ther specify that network in all;                         outgoing calls, or define that net- ,                         work as the default.  C              If you have requested X.29 support, the procedure con-o              tinues:  O                The following NCP command may be used to configure the permanentl;                database to support incoming X.29 terminals:   4                NCP define module X29-server state on  :                Do you want the database defined now [YES]?  C              If you answer YES, X.29 support is enabled. Answer NO, ?              and support is unmodified from the previous state.   %              The procedure next asks:i  1                Do you want to use PSI MAIL [YES]?   B              The PSI MAIL utility allows VAX/VMS MAIL to send mailC              over a PSDN to other VAX PSI V3.0 or later systems. IfOA              you want to be able to use this utility, answer YES.V  O           4-16  VAX P.S.I. (Packetnet System Interface) Installation Proceduresc                 B              If you answer NO to this question, the procedure con-0              tinues and creates LOAD_PSI043.COM.                Otherwise it asks:S  ?                Do you want support for incoming PSI MAIL [YES]?A  C              If you answer NO, you can still send PSI MAIL, but youe              cannot receive it.e  $              The procedure displays:  O                The PSI_MAIL object needs to run in an account with the right toa*                accept incoming X.25 calls.  A              If you answer YES, you must also define the usernamel?              and password for PSI MAIL. The procedure displays:   "                Username [DECNET] ?                  Password ?P                  Verification:  A              The username and password can be any that may accept D              incoming X.25 calls. Refer to the VAX P.S.I. ManagementA              Guide for details of setting up the system to acceptcB              X.25 calls. The default username is DECNET. (You willB              be asked to verify your password before being allowedC              to continue.) The procedure continues with the follow-               ing::  P                The following NCP commands may be used to configure the permanent5                database to support incoming PSI MAIL:   9                NCP define object psi_mail number 0 file -:C                    sys$system:psi$mail.com user USERNAME password -                     PASSWORDa  B                NCP define module x25-server destination psi_mail -$                    object PSI_MAIL -?                    CALL MASK ffffffffffffffffffffffffffffffff - >                    CALL VALUE ff00000056332E30204D41494C2D3131  A           Installing VAX PSI Access                          4-17e p               A              The call mask is applied to the user-data field, andeB              determines whether the incoming call is accepted. TheB              call value specifies the string used to test incoming0              call data. The procedure then asks:  :                Do you want the database defined now [YES]?  D              Answer YES if the NCP commands listed that will be usedD              to configure the database are correct. Answer NO if anyA              of the commands are incorrect, and then run PSI_SET_ B              UP.COM again, or enter the NCP commands as a separate1              operation to configure the database.   0              The following message is displayed:  K                Purging any previous PSI_MAIL definitions. Please ignore any1                error messages.  A              There is a short delay while LOAD_PSI043.COM is cre-o/              ated. Then the procedure displays:   :                Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COM  A              After this message is displayed, return to where youn              left Section 4.2.  C              If your default directory is not SYS$MANAGER, the pro-               cedure displays:   N                The VAX PSI startup file should be moved into SYS$MANAGER to be1                used automatically by STARTNET.COM   F                Do you want LOAD_PSI043.COM moved to SYS$MANAGER [YES]?  C              If you answer YES, the procedure moves LOAD_PSI043.COMs              into the B              SYS$MANAGER directory and displays the following mes-               sage before ending:  :                Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COM  O           4-18  VAX P.S.I. (Packetnet System Interface) Installation ProceduresA .  .            D              If you answer NO, the procedure creates LOAD_PSI043.COMA              in your current directory, displays a message sayingh)              where the file is, and ends.o  B              Return to where you left Section 4.2 to continue your              installation.  3           4.2.2 Configuring the X25-ACCESS Database   C              You can exit from this PSI_DEFINE.COM procedure at anygA              time by typing <CTRL/Z> in response to a request for C              input. If you exit by typing <CTRL/Z>, some X25-ACCESS(B              definitions may have been created. You can remove un-?              wanted definitions by using the following command:o  =                NCP purge module x25-access known networks all   B              After running PSI_SET_UP.COM initially to define yourB              database, you may either run this procedure again, orA              use NCP DEFINE commands to define each entity in the D              database and thus configure the VAX PSI system. See the<              VMS Network Control Program Manual for details.  ;              The procedure displays the following messages:d  I                You are assisted here in defining the X25-ACCESS database.   G                Do you want to define the X25-ACCESS database now [YES]?   B              Answer YES if you want to define (or update) the X25-              ACCESS database.a  $              The procedure displays:  H                This procedure can purge the database to remove all knownK                connector nodes information, before it updates the permanenta                database.  K                The following NCP command will be used to purge the databaseY  =                NCP purge module x25-access known networks all   A           Installing VAX PSI Access                          4-19  a  g            K                Do you want the information in the permanent database purged                 now [NO]?  A              If you answer NO, the information you supply will be D              added to the permanent database. If you answer YES, theB              information you supply will replace that already pre-B              sent in the permanent database and the following mes-              sage is displayed:e  #                Purging the database   D              You are then asked for the name of a PSDN to which yourC              connector node will be connected. Next, the node iden-[D              tification of that connector node is requested. You canD              define more than one network and you can enter the net-A              works in any order. During the PSI_SET_UP.COM proce- A              dure, you can set up one of these networks to be the A              default (see Section 4.2.1). The procedure displays:1  N                Your VAX PSI Access system uses a connector node to communicateO                with one or more PSDNs. You will be asked for a network name for N                the connection to the connector system and the DECnet node nameN                of that system. The network name you supply MUST be the same asM                the name of the network on the connector node that you wish to                 use.i                 The procedure asks:  *                Network name  (network-id):  D              Enter the name of the network to which you want to con-              nect.  A              If you define this network twice, the procedure willa              display:l  =                Network, network-id  has already been defined.         O           4-20  VAX P.S.I. (Packetnet System Interface) Installation Proceduresc s  r            B              If you need to use different network names to connectI              to the same PSDN, use the convention: name1,name2,.....nameneC              for the subsequent network name definition(s). For ex-rD              ample, if the original connection to the PSDN was iden-A              tified by the network name NETWORK, subsequent defi- K              nitions should take the form NETWORK1, NETWORK2,.....NETWORKn. C              See the VAX P.S.I. Management Guide for further expla-d'              nation of this convention.s  %              The procedure then asks:   *                Connector node   (node-id):  C              Enter the name or address number of the connector node C              which connects to the network you have specified. When B              you have entered this information, the procedure dis-              plays:   $                Network  = network-id(                Connector node  = node-id  6                Is the above information correct [YES]?  C              Answer YES to this question if the information is cor-.C              rect. If you answer NO, you must enter the informationp0              again. The procedure then displays:  M                The following NCP command will be used to update the permanente                databaseT  G                NCP define module x25-access network network name node -n                nodenamet  J                Adding entry to the X25-ACCESS database for network network  %              The procedure then asks:   >                Are there any more NETWORKS to be defined [NO]?  D              Answer NO to this question if you have no more networksB              to add to the X25-ACCESS database. If you answer YES,B              the procedure asks you for the network name and node-A              id, so you can add another network to the X25-ACCESSe  A           Installing VAX PSI Access                          4-21u n               A              database. You can define the same network twice pro-gF              vided two different network names and two different node-D              ids are defined. Refer to Chapter 1 for details of net-$              work and profile names.  C              When you have entered all the network information, re- C              turn to where you left Section 4.2 to continue the in-s              stallation.  (           4.3 Starting Up VAX PSI Access  C              If DECnet is running on your system, issue the follow-_1              ing command to start VAX PSI Access:     *                $ @SYS$MANAGER:STARTPSI.COM  E              If STARTPSI.COM fails after it has loaded VAX PSI Access1>              successfully, the following message is displayed:  .                Failed to set up VAX PSI Access  E              This means that the Security or Trace utilities may havetC              been set up incorrectly. Reinstall VAX PSI Access, en-f<              suring that the utilities are set up correctly.  D              If DECnet is not running on your system, issue the fol-B              lowing command, which starts both DECnet and VAX PSI:  *                $ @SYS$MANAGER:STARTNET.COM  B              If you try to start VAX PSI with the STARTPSI commandB              procedure before DECnet is running, the following er-=              ror message is displayed and the procedure ends:n  H                DECnet must be running before attempting to start VAX PSI  )                                      NOTES  <                         To restart DECnet and VAX PSI Access9                         automatically when you reboot theI  O           4-22  VAX P.S.I. (Packetnet System Interface) Installation Procedures  e  d            ;                         system, edit the above command intos5                         SYS$MANAGER:SYSTARTUP_V5.COM.t  A              If you wish to configure or modify your VAX PSI sys-,C              tem, refer to the VAX P.S.I. Management Guide. DIGITALPC              recommends that you check the installation and config- B              uration of your VAX PSI system. Follow the procedures:              described in the VAX P.S.I. Management Guide.  D              Finally, when you have installed and configured VAX PSIC              Access, and checked that the system is installed prop- D              erly, back up the updated system disk and save the dis-*              tribution kit for future use.                                                        A           Installing VAX PSI Access                          4-23t p  e                          A           ______________________________________________________5n  A                           Installing a VAX PSI Combination System         E              This chapter explains how to build a VAX PSI Combination 6              system. A Combination system is built by:  H               1. Installing the VAX PSI distribution kit on your VAX/VMS                 system./  B               2. Installing the VAX PSI Access distribution kit on(                 the same VAX/VMS system.  D               3. Running PSI_SET_UP.COM to configure and define your#                 Combination system.o  E               4. Checking that the installation and configuration hask                  been successful.  .           5.1 Installing the Distribution Kits  C              Run VMSINSTAL to install the VAX PSI distribution kit. E              Follow the instructions given in Chapter 3, Section 3.1.d  ;                    DO NOT RUN PSI_SET_UP.COM AT THIS STAGE.   C              Then run VMSINSTAL again to install the VAX PSI AccesseJ              distribution kit. Follow the instructions given in Chapter 4,D              Section 4.1, answering YES in response to the question:  @                Do you wish to install a combination system [NO]?  A           Installing a VAX PSI Combination System             5-1A S  a            F              After installing the software, execute the PSI_SET_UP.COM              procedure.eE              Continue the installation procedure by entering the fol-p              lowing commands:   (                $ SET DEFAULT SYS$MANAGER                  $ @PSI_SET_UP  C              After running PSI_SET_UP.COM, update the SYSGEN param-n              eters (see B              Section 2.6.2 in Chapter 2), reboot if necessary, andA              then check the installation. Details of how to checknI              the installation are documented in the VAX P.S.I. ManagementN              Guide.u  /           5.2 Tailoring Your Combination Systemn  B              When you have reached this stage of the installation,E              you will have built a Combination system. The next stepst              are:w  4               1. Set up devices - see Section 5.2.1.  J               2. Define the connection to the PSDN(s) - see Section 5.2.2.  G               3. Add support for Multi-host access - see Section 5.2.3.t  D              Before tailoring the VAX PSI system, make sure you haveC              the following information for each device in your con-n              figuration:                 _ CSR address                  _ VECTOR address  E              You also need to know the subscription options that havefA              been taken out with each PSDN you are connecting to.               These include:s                 _ DTE address(es)   /               _ Logical Channel Number range(s)a  N           5-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures n  h            E              You will need to know the following information for each @              network you want to add to the X25-ACCESS database:                  _ The network name  E               _ The node-id of the Multi-host VAX PSI system(s) serv-o                    ing that network  (              You will also need to know:  <               _ Whether you want to set up a default network  -               _ Whether you want X.29 support   B              Refer to Tables 2-1, 2-2 and 2-3 in Chapter 2 for theD              above information about your system. While running PSI_C              SET_UP.COM, you may enter a question mark (?) as a re-o-              sponse to any question for help.t  C              The documentation of the next part of the installationaC              has been divided into three sections (5.2.1 Setting Up E              Devices, 5.2.2 Configuring the Permanent Database, 5.2.3eA              Setting Up VAX PSI for Multi-host Working). You williC              be asked to refer to each section in turn and then re-.;              turn to the point where you left this section.f  :              The procedure displays the following message:  E                This command procedure assists in configuring VAX PSI.   P                LOAD_PSI043.COM must be built before attempting to start VAX PSI.O                The load file from an earlier version of VAX PSI cannot be used.   >                Do you wish to build LOAD_PSI043.COM now [YES]?  A              Answer YES if you want to build LOAD_PSI043.COM now.C              Refer todB              Section 5.2.1 for details of building LOAD_PSI043.COM$              and setting up devices.                 The procedure asks:  N                Do you wish to add network, line or DTE entries to the database                now [YES]?   A           Installing a VAX PSI Combination System             5-3  m  n            A              Answer YES if you want to add new information to thew6              database - see Section 5.2.2 for details.  %              The procedure then asks:S  C                Do you wish to add VAX PSI Multi-host entries [YES]?   N              Answer YES if you require a Multi-host system - see Section 5.2.3              for details.   C              Answer NO if you require a Native mode VAX PSI system,aB              in which case you are now ready to load and start VAX%              PSI. The procedure asks:i  4                Do you wish to load VAX PSI now [NO]?  4              Answer YES if you want to load VAX PSI.                                                N           5-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures t  t            C              If VAX PSI is already running on your system, the fol-r)              lowing message is displayed:n  O                A version of VAX PSI is already running on this system. In order K                to load the new configuration and device drivers you need to "                reboot your system.  P                To check out your installation after restarting VAX PSI, refer toN                the Configuration Testing chapter in the  VAX P.S.I. Management                Guide.E  A              If you do not need to reboot your system, and DECnetdB              is running on your system, then you should answer YES)              if you want to load VAX PSI.s  )                                      NOTEn  8                         If you need to change the SYSGEN9                         parameters, you must do so before :                         attempting to load VAX PSI or test:                         the installation. After making theE                         changes, reboot the system (see Section 2.6.2 9                         in Chapter 2). You will also have 8                         to reboot if you have a previous8                         version of VAX PSI installed and:                         wish to reload VAX PSI or test the%                         installation.D  D              If VAX PSI fails to load, the following message is dis-              played:  %                Failed to load VAX PSIs  E              If VAX PSI fails to start, the following message is dis-n              played:  '                Failed to set up VAX PSII  D              This means that the Security or Trace utilities, and/orG              lines and DTEs may have been set up incorrectly. Reinstall$A              VAX PSI, ensuring that the lines, DTEs and utilities "              are set up correctly.  A           Installing a VAX PSI Combination System             5-5     r            :              The procedure displays the following message:  M                To check out your installation after starting VAX PSI refer to /                the VAX P.S.I. Management Guide.l  H              Your Combination VAX PSI system is now ready to be started.<              Follow the procedures described in Section 5.3.  "           5.2.1 Setting Up Devices  B              This section describes how to set up the devices usedD              to communicate with the PSDN(s). You can exit from thisA              procedure at any time by typing <CTRL/Z> in response D              to a request for input. If you exit by typing <CTRL/Z>,0              no LOAD_PSI043.COM file is created.  :              The procedure displays the following message:  E                This command file assists in creating LOAD_PSI043.COM.i  K                LOAD_PSI043.COM is a command file used to SYSGEN the VAX PSIi5                supported devices and startup the ACP.   %              The procedure then asks:s  =                Do you want to set up a default network [YES]?   A              If your Local Area Network or DECnet network is con- D              nected to several PSDNs or to one PSDN but via a choiceA              of several connector nodes, you may specify one net-eC              work to be used as the default. (A default network may B              also be used if your system is connected to more than              one network.)  A              Answer YES if you want to set up a network name as aSD              system-wide default for your system. (If you answer NO,A              you will be given a further opportunity to specify aoA              default network at a later stage. See the VAX P.S.I.n+              Management Guide for details.)     N           5-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures a  X            C              The procedure then asks you to supply the default net-i              work name:x  2                Default network name  (network-id):  D              Enter the name of the network you want to set up as the-              default network for your system.$  A              Answer NO if you do not want to use the default net-               work.  C              If you have a previous version of VAX PSI on your sys- )              tem, the procedure displays:i  /                Checking old configuration data.l  B              Your previous installation detailed the following de-A              vice(s). You will be given the option to keep, alter B              or delete each entry in turn, and then optionally add              new devices.f  E              Details of existing devices are displayed as in the fol-.              lowing example:  2                Configuration data for line DUP-0-0  0                Device CSR is            %O7600500                Device VECTOR is         %O000300+                Device unibus adapter is UB0S  M                Do you want to Keep, Alter or Delete this entry (K, A, D) [K]?   B              Answer K if you want to keep the entry, D if you wantC              to delete it, or A if you want to alter it. If you an- 8              swer K, the following message is displayed:  =                Device device-name added to new configuration.e  A              If you answer D, the following message is displayed:u  J                Configuration data for device device-name has been deleted.  A           Installing a VAX PSI Combination System             5-7c I  a            B              If you answer A, the procedure asks for the CSR, vec-F              tor and adapter in the same way as for defining new linesD              (see below). The defaults will be the same as those forB              the previous installation, and each may be changed as              necessary.n  I              The procedure will ask you about each entry in your database E              from the previous installation. When each entry has beent)              checked, the procedure asks:l  8                Do you want to configure more lines [NO]?  B              Answer YES if you want to add more lines to your con-<              figuration and then answer the questions below.  A              If you have no devices defined from previous instal-nA              lations, or if this is the first time VAX PSI is be-eC              ing installed on your system, answer the questions be- C              low in order to configure the devices for your system.A                 The procedure asks:  %                Device type (dev-c-u):a  A              Enter the type of the first device to be configured.eC              The permitted device types for Unibus systems are DMF,oD              DUP, KMX, and KMY. If you enter any other device types,$              the procedure displays:  *                Error, unknown device type.  <                Supported devices are DMF, DUP, KMX, and KMY.                  Examples:                         DMF-0                        DUP-0.                       KMX-0-1A                       KMY-1d    N           5-8  VAX P.S.I. (Packetnet System Interface) Installation Procedures o  u            B              The permitted device types for BI systems are DMB andA              DSB. If you enter any other device types, the proce-               dure displays:e  *                Error, unknown device type.  1                Supported devices are DMB and DSB.                   Example:                          DMB-0a                       DSB-0   B              The permitted device types for Q-Bus systems are DPV,C              KMV, DIV and DSV. If you enter any other device types, $              the procedure displays:  *                Error, unknown device type.  ;                Supported devices are DPV, KMV, DIV and DSV.                   Examples:                       DPV-0m                     KMV-0a                     DIV-0-0a                     DSV-0-0I  C              The permitted device types for busless systems are DSTwC              and DSH. If you enter any other device types, the pro-               cedure displays:   *                Error, unknown device type.  1                Supported devices are DST and DSH.                   Example:A                       DST-0o                     DSH-0   C              If you have entered a wrong device type, the procedure )              will ask again for a device.r  A           Installing a VAX PSI Combination System             5-9     d            B              If the device type is DMF, DMB, DSV, DSB, DSH, DIV or)              DST, the procedure displays:o  L                SYSGEN autoconfigures the device-name, no further information                required.  6                Are there more lines to configure [NO]?  A              If you have more lines to configure, answer YES, andnE              the procedure asks again for the device type. Otherwise, C              answer NO, and the procedure completes by asking aboutc"              PSI MAIL (see below).  A              If the device type is DUP, KMX, KMY, DPV or KMV, theeB              procedure asks for the CSR address and vector address              of the device.   )                                      NOTE(  8                         If you are installing VAX PSI on8                         a machine other than a MicroVAX,@                         the procedure also asks for the adapter-+                         type of the device.e  B              The default values for these parameters are also dis-              played.  E              Enter the required addresses and adapter-type, or choose ,              the defaults by pressing <RET>.  /              For example, for a KMX-0-0 device:g  .                Default CSR address is %O7641001                       CSR address (octal): 764120n  )                Default VECTOR is %O000700r)                       Vector (octal): 720   %                Default ADAPTER is UB0 3                       Adapter (adapter-type): <RET>e  B              The procedure now checks that the device has been setD              up correctly by displaying the values that you have se-B              lected, and also asks for confirmation that these are              correct.l  O           5-10  VAX P.S.I. (Packetnet System Interface) Installation Proceduresi l               2                Configuration data for line KMX-0-0  0                Device CSR is            %O7641200                Device VECTOR is         %O000720+                Device UNIBUS adapter is UB0   7                Are these line parameters correct [YES]?   A              If the line parameters are wrong, answer NO, and thenA              procedure asks again for the device type. Otherwise,o3              answer YES and the procedure displays:   5                Device KMX-0-0 added to configuration.p  8                Do you want to configure more lines [NO]?  B              If you answer YES, the procedure asks again for a de-A              vice type. If you specify the same device again, the &              procedure warns you with:  ,                Error, duplicate device name.  B              Otherwise, the procedure continues with the question:  O                The following NCP command may be used to configure the permanent ;                database to support incoming X.29 terminals:   4                NCP define module X29-server state on  :                Do you want the database defined now [YES]?  C              If you answer YES, X.29 support is enabled. Answer NO, ?              and support is unmodified from the previous state.E  %              The procedure next asks:   1                Do you want to use PSI MAIL [YES]?   C              The PSI MAIL utility allows VMS MAIL to send mail overyB              a PSDN to other VAX PSI V3.0 or later systems. If you=              want to be able to use this utility, answer YES.   B              If you answer NO to this question, the procedure con-0              tinues and creates LOAD_PSI043.COM.  A           Installing a VAX PSI Combination System            5-11  e                             Otherwise it asks:r  ?                Do you want support for incoming PSI MAIL [YES]?t  C              If you answer NO, you can still send PSI MAIL, but you               cannot receive it.o  $              The procedure displays:  O                The PSI_MAIL object needs to run in an account with the right to *                accept incoming X.25 calls.  A              If you answer YES, you must also define the usernameo?              and password for PSI MAIL. The procedure displays:   "                Username [DECNET] ?                  Password ?e                  Verification:  A              The username and password can be any that may acceptxD              incoming X.25 calls. Refer to the VAX P.S.I. ManagementA              Guide for details of setting up the system to accept B              X.25 calls. The default username is DECNET. (You willB              be asked to verify your password before being allowed              to continue.)  8              The procedure continues with the following:  P                The following NCP commands may be used to configure the permanent5                database to support incoming PSI MAIL:   9                NCP define object psi_mail number 0 file - ?                    sys$system:psi$mail user USERNAME password -                     PASSWORD   B                NCP define module x25-server destination psi_mail -$                    object PSI_MAIL -?                    CALL MASK ffffffffffffffffffffffffffffffff - >                    CALL VALUE ff00000056332e30204d41494c2d3131  O           5-12  VAX P.S.I. (Packetnet System Interface) Installation Procedures  i  g            A              The call mask is applied to the user-data field, andrB              determines whether the incoming call is accepted. TheB              call value specifies the string used to test incoming              call data.r  %              The procedure then asks:s  :                Do you want the database defined now [YES]?  D              Answer YES if the NCP commands listed that will be usedD              to configure the database are correct. Answer NO if anyA              of the commands are incorrect, and then run PSI_SET_eB              UP.COM again, or enter the NCP commands as a separate1              operation to configure the database.s  0              The following message is displayed:  K                Purging any previous PSI_MAIL definitions. Please ignore anye                error messages.  A              There is a short delay while LOAD_PSI043.COM is cre--/              ated. Then the procedure displays:t  :                Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COM  A              After this message is displayed, return to where youf<              left Section 5.2 to continue your installation.  C              If your default directory is not SYS$MANAGER, the pro-               cedure displays:U  N                The VAX PSI startup file should be moved into SYS$MANAGER to be1                used automatically by STARTNET.COM-  F                Do you want LOAD_PSI043.COM moved to SYS$MANAGER [YES]?  C              If you answer YES, the procedure moves LOAD_PSI043.COM               into thevB              SYS$MANAGER directory and displays the following mes-               sage before ending:  A           Installing a VAX PSI Combination System            5-13i t  .            :                Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COM  D              If you answer NO, the procedure creates LOAD_PSI043.COMA              in your current directory, displays a message sayingP)              where the file is, and ends.n  B              Return to where you left Section 5.2 to continue your              installation.  2           5.2.2 Configuring the Permanent Database  C              This PSI_DEFINE.COM procedure allows you to set up the A              X.25 Access and Native/Multi-host information in theaA              permanent database. You can exit from this procedure D              at any time by typing <CTRL/Z> in response to a requestA              for input. If you exit by typing <CTRL/Z>, some PSDN 6              or DTE definitions may have been created.  D              You can remove unwanted PSDN and DTE definitions by us-(              ing the following commands:  J                NCP purge module x25-protocol known dtes known networks all  ?                NCP purge module x25-protocol known networks alln  =                NCP purge module x25-access known networks all   B              After running PSI_SET_UP.COM initially to define yourE              DTE(s), you may run this procedure again. Alternatively,SB              you may use NCP DEFINE commands to define each entityC              in the database and thus configure the VAX PSI system.[D              See the VMS Network Control Program Manual for details.  :              The procedure displays the following message:  I                You are assisted here in defining the X25-ACCESS database.   G                Do you want to define the X25-ACCESS database now [YES]?p  B              Answer YES if you want to define (or update) the X25-E              ACCESS database, and refer to Section 4.2.2 for details.   O           5-14  VAX P.S.I. (Packetnet System Interface) Installation Proceduresl                 $              The procedure displays:  H                This procedure can purge the database to remove all knownJ                connector node information, before it updates the permanent                database.  K                The following NCP command will be used to purge the databaser  =                NCP purge module x25-access known networks allp  K                Do you want the information in the permanent database purged                 now [NO]?  A              If you answer NO, the information you supply will be D              added to the permanent database. If you answer YES, theB              information you supply will replace that already pre-B              sent in the permanent database and the following mes-              sage is displayed:   #                Purging the databased  D              You are then asked for the name of a PSDN to which yourC              connector node will be connected. Next, the node iden- D              tification of that connector node is requested. You canD              define more than one network and you can enter the net-A              works in any order. During the PSI_SET_UP.COM proce- A              dure, you can set up one of these networks to be theSA              default (see Section 5.2.1). The procedure displays:t  N                Your VAX PSI Access system uses a connector node to communicateO                with one or more PSDNs. You will be asked for a network name forsN                the connection to the connector system and the DECnet node nameN                of that system. The network name you supply MUST be the same asM                the name of the network on the connector node that you wish tov                use.i                 The procedure asks:  *                Network name  (network-id):  D              Enter the name of the network to which you want to con-              nect.  A           Installing a VAX PSI Combination System            5-15d    f            A              If you define this network twice, the procedure wills              display:P  =                Network, network-id  has already been defined.t  B              If you need to use different network names to connectI              to the same PSDN, use the convention: name1,name2,.....namenoC              for the subsequent network name definition(s). For ex- D              ample, if the original connection to the PSDN was iden-A              tified by the network name NETWORK, subsequent defi-PK              nitions should take the form NETWORK1, NETWORK2,.....NETWORKn.bC              See the VAX P.S.I. Management Guide for further expla- '              nation of this convention.   %              The procedure then asks:O  +                Connector node    (node-id):n  C              Enter the name or address number of the connector node C              which connects to the network you have specified. WhenEB              you have entered this information, the procedure dis-              plays:   $                Network  = network-id(                Connector node  = node-id  6                Is the above information correct [YES]?  C              Answer YES to this question if the information is cor- C              rect. If you answer NO, you must enter the informationw0              again. The procedure then displays:  M                The following NCP command will be used to update the permanentr                database   E                NCP define module x25-access network network name nodem                    nodenameV  J                Adding entry to the X25-ACCESS database for network network    O           5-16  VAX P.S.I. (Packetnet System Interface) Installation Procedures     b            %              The procedure then asks:d  >                Are there any more NETWORKS to be defined [NO]?  D              Answer NO to this question if you have no more networksB              to add to the X25-ACCESS database. If you answer YES,B              the procedure asks you for the network name and node-A              id, so you can add another network to the X25-ACCESSAA              database. You can define the same network twice pro-dF              vided two different network names and two different node-D              ids are defined. Refer to Chapter 1 for details of net-$              work and profile names.  <              The next step is to set up the Native database.  $              The procedure displays:  N                This command procedure allows you to define one or more PSDN(s)A                and one or more DTEs associated with each network.c  D              The SPD for VAX PSI lists the public networks supportedF              at the time of printing. Check with your Customer SupportB              Representative for up-to-date information on new net-              works.   I                Do you want to define the X25-PROTOCOL database now [YES]?f  G              Answer YES if you want to define the X25-PROTOCOL databasenB              to define the PSDN(s) and DTE(s) associated with each.              network. The procedure continues:  I                You can use this procedure to purge the database to removesI                all DTEs and all X.25 protocol information before updatingoH                the permanent database. You can also use the procedure toJ                remove the line information from the database. Note that ifJ                the line permanent database is purged then all DECnet lines8                along with VAX PSI lines will be removed.  G                The following NCP commands will be used to purge the DTEa+                and X.25 permanent database:c  ?                NCP purge module x25-protocol known networks all J                NCP purge module x25-protocol known dtes known networks all  A           Installing a VAX PSI Combination System            5-17                  H                The following NCP commands will be used to purge the line"                permanent database:  (                NCP purge known lines all  I                Do you want the information in the X.25 and DTE permanent e$                database purged [NO]?  C              If you wish to keep previous definitions for DTEs, an- D              swer NO. If you answer YES, the following is displayed:  1                Purging the X.25 and DTE database.   %              The procedure then asks:a  I                Do you want the line information in the permanent database                 purged [NO]?e  D              If you wish to keep previous definitions for lines, in-B              cluding DECnet lines, answer NO. Note that if you an-B              swer YES, all DECnet lines will be deleted along withD              VAX PSI lines. If you answer YES, the following is dis-              played:  )                Purging the line database.   $              The procedure displays:  M                PSDN and profile names are defined here. You can define one or I                more PSDNs. For each PSDN you will be asked to provide thenB                network name and the profile name for that network.                 The procedure asks:  &                Network name  (string):  D              Enter the network name that connects to the PSDN. ReferC              to Section 1.7 in Chapter 1 for details of network and               profile names.n  A                Profile name          (string)     [NETWORK NAME]:u  O           5-18  VAX P.S.I. (Packetnet System Interface) Installation Procedures  m  s            E              Enter the profile name of the PSDN to which the DTE will A              connect. The default name is the same as the networko              name.  C              The procedure then displays the command it will use toY+              update the permanent database.S  M                The following NCP command will be used to update the permanent[                database:  C                NCP define module x25-protocol network network-id  - '                    profile profile-named  D                Do you want the information in the permanent database                updated [YES]?   E              If you answer NO, the NCP commands will not be executed.cC              You may enter the commands yourself later if you wish.eA              The procedure then continues and displays additional ?              messages here, if it deletes any database entries.u  ;              Answer YES if you want to update the database.2  :              The procedure displays the following message:  O                DTEs are defined here. You can define one or more DTEs connected M                to this network. For each DTE you will be asked to provide thet%                following information:                   . DTE address  8                . Range of channels to be used by the DTE  -                . Line associated with the DTEe  B              Refer to the completed Table 2-1 in Chapter 2 for theE              information you need to supply for your system. The pro-c              cedure asks:t  %                DTE address  (number):   A           Installing a VAX PSI Combination System            5-19Y c               A              Enter your DTE address. For details on the format of C              this address, refer to the  Public Network Information               manual.  &                Channels range  (list):  B              Enter the channels that the DTE will use for outgoingF              calls. Specify high-numbered channels before low-numberedA              channels. Each entry in the channels list can be ei-oB              ther a single channel number or a channel range (withC              a hyphen separating the high and low numbers). The en-nC              tries in the list must be separated by commas. For ex-t              ample:   8                Channels range (list):1555,1544-1540,1536  A              The PSDN authorities allocate channel ranges at sub- A              scription time. For details on the channel range al--L              located for your PSDN, refer to the  Public Network Information              manual.  $                Line name  (dev-c-u):  F              Enter the name of the line that the DTE will use. SpecifyB              a line-id in the form dev-c[-u]. For all device typesC              except KMX, you need only specify line-id and the con- )              troller number, for example:1                  KMV-0  C              For KMX, you must specify the line-id, controller num- 2              ber and the unit number, for example:                  KMX-0-1  $              The procedure displays:          O           5-20  VAX P.S.I. (Packetnet System Interface) Installation Procedures                  N                The following NCP commands will be used to update the permanent                database:  H                NCP define line line-id  network network-id protocol lapb                    state on   @                NCP define module x25-protocol dte dte-address  -'                    network network-id -E+                    channels  channel-list -i!                    line line-id -                     state ont  %              The procedure then asks:t  F                Do you want to update the permanent database now [YES]?  E              If you answer NO, the NCP commands will not be executed. C              You may enter the commands yourself later if you wish.wA              The procedure then continues and displays additional ?              messages here, if it deletes any database entries.   7              If you answer YES, the procedure displays:e  !                Updating database.m  D                Do you want to define any more DTEs connected to this                network [NO]?  E              Answer YES if more DTE definitions are required for thislA              network. The procedure then repeats the questions totD              define a DTE. When you have finished defining all DTEs,              answer NO.s  )              The procedure then displays:e  <                Do you want to define any more networks [NO]?  E              Answer YES if you want to define more networks. The pro-nC              cedure then repeats the questions to define DTE(s) forS              the next network.  A              When you have finished defining all networks, answere              NO.  A           Installing a VAX PSI Combination System            5-21r f  d            B              Return to where you left Section 5.2 to continue your              installation.    ;           5.2.3 Setting Up VAX PSI for Multi-Host Operation   B              The X25-SERVER destinations need to be set up for theD              incoming calls which are destined for Access hosts. YouH              can exit from this procedure at any time by typing <CTRL/Z>A              in response to a request for input. For example, you ;              can type <CTRL/Z> after the following message:-  .                Updating the permanent database  C              This will cause you to exit and the destinations to beeA              set up. You can delete the destinations by using the               following command:   B                NCP  purge module x25-server known destinations all  :              The procedure displays the following message:  D                X25-Server destinations are set up here. These permitK                incoming calls received by this node to be redirected to thehM                appropriate host. This procedure asks for a list of hosts withoL                VAX PSI Access installed. This list of nodes will not include5                the node you are currently working on.b  B              Refer to the completed Table 2-2 in Chapter 2 for the/              destination names for your system.n  )              The procedure then displays:l  *                Destination name  (string):  A              Destinations are used by the Multi-host VAX PSI sys- A              tem to identify the destination of the incoming call C              so that it can be redirected to the correct host node.sA              Enter a destination name as a string of up to 16 al- #              phanumeric characters.   O           5-22  VAX P.S.I. (Packetnet System Interface) Installation Procedures     t            /                Destination node name  (string):u  D              Destination node is the node where the object, requiredC              by the incoming call, resides. Enter a node name of up ,              to six alphanumeric characters.  .                Destination priority     [200]:  D              Destination priority is the processing priority for theB              redirection of the incoming call to that destination.A              Priority is an integer number in the range 0 to 255.   C              The rest of the parameters are optional. If you do not B              specify them, they will not be checked when an incom-              ing call arrives.  ,                Call mask (2-32 hex)  [None]:  B              The call mask is generally used in conjunction with aA              call value and, when applied to the user-data field,eD              determines whether the incoming call is accepted. EnterC              a hexadecimal value between 2 and 32 digits. If you doeB              not specify a mask, the destination accepts all calls               with any user data.  -                Call value (2-32 hex)  [None]:n  A              The call value specifies the string used to test in- B              coming call data. If the call mask with the call dataD              fields matches the call value, the incoming call is ac-B              cepted. The call value for incoming X.29 calls should              be set to 01.  ;                Closed User Group (1-16 characters)  [None]:a  A              Closed user group specifies which user group (CUG or 1              BCUG) has access to the destination.u  6                Sending address (1-15 decimal)  [None]:    A           Installing a VAX PSI Combination System            5-23d b  :            C              This specifies which remote DTE address(es) has access C              to the destination. If none is specified, all call re-fC              quests from remote DTEs are accepted. Wildcards (* and ,              %) may be used in this address.  8                Subaddress range (decimal range)  [None]:  E              Subaddress is used to determine whether an incoming callnA              is to be accepted. If the subaddress of the incomingeA              call is within the range specified, the call requestoA              is accepted. If no range is specified, call requestsoD              with any subaddress are accepted. Enter only one range,4              for example, 50-99 or 122 or 1010-1234.  6                Object identification (string)    [36]:  D              Set this parameter as required by the destination node.C              VAX PSI requires a value of 36 for this parameter (the ,              default value), so enter <RET>.  $              The procedure displays:  9                The destination will be set up as follows:s  .                NCP> define module x25-server -+                     destination dest-name -m$                     node dest-node -+                     [call mask call-mask] - -                     [call value call-value] -s&                     [group cug-name] -3                     [sending address dte-address] -o4                     [subaddress sub-address-range] -*                     [priority dest-prio] -&                     [object object-id]  A              Only the fields that you have specified will be dis-u              played.  $              The procedure displays:  @                Do you want to define this destination now [YES]?  O           5-24  VAX P.S.I. (Packetnet System Interface) Installation Procedures                  A              If you answer NO, the procedure will not execute theeC              NCP command as displayed above. If you answer YES, the                procedure displays:  /                Updating the permanent database.n  @                Do you want to define any more destinations [NO]?  C              If you answer YES, the procedure will repeat the abovenB              questions to allow further destinations to be set up.  C              When you have completed defining all destinations, an--              swer NO.]  B              Return to where you left Section 5.2 to continue your              installation.  !           5.3 Starting Up VAX PSI1  C              If DECnet is running on your system, issue the follow-lA              ing command to start the VAX PSI combination system:   *                $ @SYS$MANAGER:STARTPSI.COM  D              If STARTPSI.COM fails, after it has loaded VAX PSI suc-;              cessfully, the following message is displayed:   '                Failed to set up VAX PSIm  D              This means that the Security or Trace utilities, and/orG              lines and DTEs may have been set up incorrectly. Reinstall A              VAX PSI, ensuring that the lines, DTEs and utilities5"              are set up correctly.  D              If DECnet is not running on your system, issue the fol-=              lowing command to start both DECnet and VAX PSI:   *                $ @SYS$MANAGER:STARTNET.COM      A           Installing a VAX PSI Combination System            5-25  S               B              If you try to start VAX PSI with the STARTPSI commandB              procedure before DECnet is running, the following er-=              ror message is displayed and the procedure ends.   H                DECnet must be running before attempting to start VAX PSI  )                                      NOTEs  9                         To restart DECnet and VAX PSI au- <                         tomatically when you reboot the sys-<                         tem, edit the STARTNET command given"                         above into5                         SYS$MANAGER:SYSTARTUP_V5.COM.o  A              If you wish to configure or modify your VAX PSI sys-l;              tem, refer to the VAX P.S.I. Management Guide.e  C              DIGITAL recommends that you check the installation andrB              configuration of your VAX PSI system. Follow the pro-B              cedures described in the VAX P.S.I. Management Guide.  E              Finally, when you have installed and configured VAX PSI, F              and checked that the system is installed properly, backupB              the updated system disk and save the distribution kit              for future use.                                O           5-26  VAX P.S.I. (Packetnet System Interface) Installation ProceduresX I  r                          A           ______________________________________________________6   A                                      Changing Your VAX PSI System         D              The changes you might want to make to your VAX PSI sys-              tem are:   B               _ Migrate from one type of VAX PSI system to another  "                 (see Section 6.1).  N               _ Add further VAX PSI systems to your network (see Section 6.2).  B               _ Add extra network connections to your VAX PSI sys-  &                 tem (see Section 6.3).  =               _ Change the default network (see Section 6.4).r  A               _ Install PSI MAIL or the VAX PSI Utilities for the                    first time"                 (see Section 6.5).  B              When you make changes to your VAX PSI system, you mayB              need to change the security on your system. Alter theG              authorization commands in your DTE Access Control DatabasesC              by editing the PSI_SECURITY.COM command file. Refer tonI              the VAX P.S.I. Management Guide for details of this databasea.              and the VAX PSI Security utility.  A           Changing Your VAX PSI System                        6-1p s               /           6.1 Migrating Between VAX PSI SystemsD  B              To migrate between systems, follow the rules in Table              6-1.s  9              Table 6-1  Migrating Between VAX PSI SystemseA              ____________________________________________________a-              Migration Path        What to Do A              ____________________________________________________e  ;              Native -> Multi-host  Do one of the following:   <                                     _ Execute PSI_SET_UP.COM  =                                       to specify destinations <                                       for incoming calls di-?                                       rected to Access systems,D?                                       then restart VAX PSI (seet3                                       Section 3.3).d  =                                     _ Add destinations to theP  ?                                       X25-SERVER database using =                                       NCP (see the VAX P.S.I. 8                                       Management Guide).  =              Multi-host -> Native  Use NCP to remove destina--<                                    tions from the X25-SERVER;                                    database (see VAX P.S.I.p@                                    Management Guide). Remove the>                                    destinations to limit users=                                    of VAX PSI to those on thei>                                    local system and to prevent>                                    traffic to nodes other than2                                    the local node.  @              Access -> Multi-      Install and configure VAX PSI>              host/Native           Multi-host/Native. You must>                                    also subscribe to the PSDN.  @              Multi-host/Native ->  Install and configure VAX PSI*              Access                Access.  N           6-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures                 A              Table 6-1 (Cont.)  Migrating Between VAX PSI Systems5A              ____________________________________________________S-              Migration Path        What to Do A              ____________________________________________________   <              Multi-host/Native ->  Install and configure VAX;              Combination           PSI Access, choosing ther@                                    Combination option during the0                                    installation.  @              Access -> Combination Install and configure VAX PSI>                                    Multi-host/Native and rein-?                                    stall VAX PSI Access, choos-c=                                    ing the Combination optiond;                                    during the installation.eA              ____________________________________________________                                                       A           Changing Your VAX PSI System                        6-3e s  a            ,           6.2 Adding Further VAX PSI Systems  A              To add further VAX PSI systems to your network, fol- .              low the rules given in Table 6-2.  6              Table 6-2  Adding Further VAX PSI SystemsA              ____________________________________________________e-              Type of System Added  What to DoeA              ____________________________________________________     ?              VAX PSI Access        For each VAX PSI Access sys-g7                                    tem you want to add:s  @                                     1. Install VAX PSI Access on=                                       the system by following @                                       the procedure described in2                                       this manual.  <                                     2. Update the X25-SERVER=                                       database on each of thek;                                       Multi-host nodes with @                                       details of the new VAX PSI@                                       Access system. See the VAX=                                       P.S.I. Management Guide 2                                       for details.                                  N           6-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures b  n            A              Table_6-2_(Cont.)__Adding_Further_VAX_PSI_Systems___   A              Type_of_System_Added__What_to_Do____________________   <              VAX PSI Multi-host    To provide an alternative=                                    route to your PSDN through.=                                    another VAX PSI Multi-hosty*                                    system:  A                                     1. Install VAX PSI Multi-host >                                       on the system designated<                                       as the new or alterna-=                                       tive Multi-host node by =                                       following the procedure ?                                       described in this manual.b  <                                     2. Update the X25-ACCESS9                                       database on each oft=                                       the VAX PSI Access sys- >                                       tems. See the VAX P.S.I.>                                       Management Guide for de-,                                       tails.A              ____________________________________________________I  .           6.3 Adding Extra Network Connections  >              A new network connection is one of the following:                 _ A new line                 _ A new DTEr  -               _ A connection to a new network   B              To add one of these to your VAX PSI Native or VAX PSIE              Multi-host system, run PSI_SET_UP.COM. You must re-enter B              the information for all existing connections and thenB              include details of the new connection. PSI_SET_UP.COMA              will add the information about the new connection toR              the database.  A           Changing Your VAX PSI System                        6-5t    e            /           6.4 How to Change the Default NetworkL  A              If you have more than one PSDN connected to your VAXuB              PSI Native or Multi-host node, you may want to changeE              the default network. To do this you must modify the log- E              ical name, PSI$NETWORK, to point to the new default net-kB              work. To make this change permanent you should changeC              the definition of PSI$NETWORK in the SYS$MANAGER:LOAD_t              PSI043.COM file.   N              Note: This is the only time you should edit the SYS$MANAGER:LOAD_              PSI043.COM file.   >           6.5 Installing the VAX PSI Utilities or PSI MAIL for               the First Time  D              To install any of the VAX PSI Utilities or PSI MAIL forC              the first time, re-install your VAX PSI system and re- D              quest support for the utilities and/or PSI MAIL. Follow5              the procedures described in this manual.                                           N           6-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures    y                          A           ______________________________________________________Au  A            Example of a Native or Multi-host VAX PSI Installation         B              The following is an example of a Native or Multi-host              installation.  5           $ @sys$update:vmsinstal psi msa0: options nu  ?            VAX/VMS Software Product Installation Procedure V5.1r  %           It is 14-FEB-1989 at 14:45. 9           Enter a question mark (?) at any time for help.n  N           * Are you satisfied with the backup of your system disk [YES]? <RET>  3           The following products will be processed:a             VAX PSI V4.3:            Beginning installation of VAX PSI V4.3 at 14:45  ?           %VMSINSTAL-I-RESTORE, Restoring product saveset A ...e  L           Release notes included with this kit are always copied to SYS$HELP  +           Additional Release Notes Options:b  $            1.  Display release notes"            2.  Print release notes            3.  Both 1 and 2_             4.  None of the above  A       Example of a Native or Multi-host VAX PSI Installation  A-1_ _  _            $           * Select option [2]: <RET>)           * Queue name [SYS$PRINT]: <RET> J           Job PSI043 (queue SYS$PRINT_CRC, entry 964) started on LXY22_CRC7           * Do you want to continue the installation? n G           %VMSINSTAL-I-RELMOVED , The product's release notes have been )           successfully moved to SYS$HELP. :            Installation of VAX PSI V4.3 completed at 14:48  ,            VMSINSTAL procedure done at 14:48  +           $ @sys$update:vmsinstal psi msa0:n  ?            VAX/VMS Software Product Installation Procedure V5.1d  %           It is 20-FEB-1989 at 14:55. 9           Enter a question mark (?) at any time for help.   N           * Are you satisfied with the backup of your system disk [YES]? <RET>  3           The following products will be processed:t             VAX PSI V4.3  :            Beginning installation of VAX PSI V4.3 at 14:55  ?           %VMSINSTAL-I-RESTORE, Restoring product saveset A ... G           %VMSINSTAL-I-RELMOVED , The product's release notes have been )           successfully moved to SYS$HELP.o  0            VAX PSI V4.3 installation procedures.  1           * Do you want X.29 support [YES]? <RET>   6           * Do you want all the utilities [YES]? <RET>  I           There are no more questions to answer during this installation.i  ?           %VMSINSTAL-I-RESTORE, Restoring product saveset B ... ?           %VMSINSTAL-I-RESTORE, Restoring product saveset C ...e?           %VMSINSTAL-I-RESTORE, Restoring product saveset D ...e?           %VMSINSTAL-I-RESTORE, Restoring product saveset E ...   M               Removing obsolete files from any previous VAX PSI installation.   ,               Installing VAX PSI V4.3 files.  +               VAX PSI V4.3 files installed._  G           To  complete the installation, follow the instructions below:   L           -  Execute  the  command  procedure  SYS$MANAGER:PSI_SET_UP.COM toI              produce a LOAD_PSI043.COM and set up the permanent database.   N           A-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures                 N           -  On a system which is running DECnet execute the command procedure;              SYS$MANAGER:STARTPSI.COM, to bring up VAX PSI. I              On a system which is not running DECnet, execute the command O              procedure SYS$MANAGER:STARTNET.COM to bring up DECnet and VAX PSI.   B           %VMSINSTAL-I-MOVEFILES, Files will now be moved to their           target directories...   ;             Installation of VAX PSI V4.3 completed at 15:31   ,            VMSINSTAL procedure done at 15:32  '           $ @sys$manager:psi_set_up.com   @           This command procedure assists in configuring VAX PSI.  L           LOAD_PSI043.COM must be built before attempting to start  VAX PSI.J           The load file from an earlier version of VAX PSI cannot be used.  @           Do you wish to build load_psi043.com now  [YES]? <RET>  F           This  command  file  assists  in  creating  LOAD_PSI043.COM.  L           LOAD_PSI043.COM is a command file  used  to  SYSGEN  the  VAX  PSI0           supported devices and startup the ACP.  ?           Do you want to set up a default network  [YES]? <RET>u  @           Default network name                (network-id): net1  .           Device type         (dev-c-u): kmv-0  )           Default CSR address is %O760420 -           CSR address           (octal):<RET>n  $           Default VECTOR is %O000310.           Vector                (octal): %O300  -           Configuration data for line KMV-0-0   +           Device CSR is            %O760420 +           Device VECTOR is         %O000300n  N           Do you want to Keep, Alter or Delete this entry (K, A, D) [K]? <RET>  3           Device KMV-0-0 added to new configuratione  9           Do you want to configure more lines [NO]? <RET>   K           The following NCP command may be used to configure the  permanent 6           database to support incoming X.29 terminals:  /           NCP define module X29-server state on   ;           Do you want the database defined now [YES]? <RET>s  A       Example of a Native or Multi-host VAX PSI Installation  A-3_ _               2           Do you want to use PSI MAIL [YES]? <RET>@           Do you want support for incoming PSI MAIL [YES]? <RET>  J           The PSI_MAIL object needs to run in an account with the right to%           accept incoming X.25 calls.   2           Username    [DECNET]     (string): <RET>3           Password                 (string): decnets3           Verification             (string): decnet   L           The following NCP commands may be used to configure the  permanent1           database to support incoming  PSI MAIL:w  H           NCP define object psi_mail number 0 file sys$system:psi$mail -'           user DECNET password PASSWORD M           NCP define module x25-server destination psi_mail object psi_mail -o6           call mask ffffffffffffffffffffffffffffffff -5           call value ff00000056332e30204d41494c2d3131   ;           Do you want the database defined now [YES]? <RET>   L           Purging any  previous PSI_MAIL  definitions.   Please  ignore  any           error messages._  "           %NCP-I-SUCCESS,  Success           Object = PSI_MAILo1           %NML-I-RECDELET, Database entry deletedt"           %NCP-I-SUCCESS,  Success  1           %NML-I-RECDELET, Database entry deleted   5           Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COM   @           Do you wish to add network, line or DTE entries to the$           database now  [YES]? <RET>  L           This command procedure allows you to define one  or  more  PSDN(s)<           and one or more DTEs associated with each network.  J           Do you want to define the X25-PROTOCOL database now [YES]? <RET>  L           You can use this procedure to  purge the  database  to  remove allL           DTEs  and  all  X.25  protocol  information  before  updating  theL           permanent database.  You can also use this procedure to remove theL           line  information  from  the  database.  Note  that  if  the  lineL           permanent  database is purged then all DECnet lines along with VAX$           PSI lines will be removed.  L           The following NCP commands will be used to purge the DTE and  X.25           permanent database:   :           NCP purge module x25-protocol known networks allE           NCP purge module x25-protocol known dtes known networks ally  N           A-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures    t            L           The following  NCP  commands  will  be  used  to  purge  the  line           permanent database:U  #           NCP purge known lines allt  L           Do you want the information in the X.25 and DTE permanent database           purged [NO]? <RET>  D           Do you want the line information in the permanent database           purged  [NO]? <RET>   L           PSDN and profile names are defined here.  You can  define  one  orL           more  PSDNs.   For  each  PSDN  you  will  be asked to provide the=           network name and the profile name for that network.i  '           Network name   (string): net1 0           Profile name   (string) [net1]: sonnet  D           The following command will be used to update the permanent           database:0  7           NCP define module x25-protocol network net1 -a               profile sonnet?           Do you want the information in the permanent database             updated  [YES]?  <RET>  A           DTEs are defined here.  You can define one or more DTEs<D           connected to this network.  For each DTE you will be asked/           to provide the following information:o             o DTE address 3           o Range of channels to be used by the DTEa(           o Line associated with the DTE  0           DTE address    (number): 2342123456789,           Channels range   (list): 1250-1150(           Line name     (dev-c-u): kmv-0  ;           The following NCP commands will be used to update_!           the permanent database.   C           NCP define line kmv-0 network net1 protocol lapb state on_<           NCP define module x25-protocol dte 2342123456789 -               network net1 -"               channels 1250-1150 -               line kmv-0 -               state on  H           Do you want to update the permanent database now  [YES]? <RET>             Updating databases  A       Example of a Native or Multi-host VAX PSI Installation  A-5     s            ?           Do you want to define any more DTEs connected to thise           network [NO]? <RET>s  =           Do you want to define any more networks [NO]? <RET>d  D           Do you wish to add VAX PSI Multi-host entries [YES]? <RET>  L           X25-Server destinations are set up  here.  These  permit  incomingL           calls received by this node to be redirected  to  the  appropriateL           host. This procedure asks for a list of hosts with  VAX PSI AccessL           installed. This list of nodes will not include the  node  you  are           currently working on.e  A           Destination name       (string)                 : zaquaeA           Destination node name  (string)                 : zaqua A           Destination priority                     [200]  : <RET> A           Call mask              (2-32 hex)        [None] : <RET>tA           Call value             (2-32 hex)        [None] : <RET> A           Closed user group name (1-16 characters) [None] : <RET>rA           Sending address        (1-15 decimal)    [None] : <RET>nA           Subaddress range       (decimal range)   [None] : <RET> A           Object identification  (string)          [36]   : <RET>r  4           The destination will be set up as follows:  (           NCP>define module x25-server -            destination zaqua -            node zaqua -             priority 200 -s            object 36  B           Do you want to define this destination now  [YES]? <RET>  )           Updating the permanent database   B           Do you want to define any more destinations  [NO]? <RET>  5           Do you wish to load VAX PSI now [NO]? <RET>X  L           To check out your installation after starting VAX PSI refer to theH           Configuration Testing Chapter in the VAX PSI Management Guide.  N           A-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures    y                          A           ______________________________________________________BA  @                         Example of a VAX PSI Access Installation        J              The following is an example of a VAX PSI Access Installation.  8           $ @sys$update:vmsinstal psi_ac msa0: options n  E                  VAX/VMS Software Product Installation Procedure V5.1r  %           It is 21-FEB-1989 at 10:35.d9           Enter a question mark (?) at any time for help.D  A           * Are you satisfied with the backup of your system disk            [YES]? <RET>  3           The following products will be processed:              PSI_AC V4.3a9            Beginning installation of PSI_AC V4.3 at 10:35f  ?           %VMSINSTAL-I-RESTORE, Restoring product saveset A ...4  D           Release notes with this kit are always copied to SYS$HELP.  +           Additional Release Notes Options:   %             1.  Display release notes[#             2.  Print release notesw             3.  Both 1 and 2!             4.  None of the abovep  $           * Select option [2]: <RET>)           * Queue name [SYS$PRINT]: <RET> M           Job PSI_AC043 (queue SYS$PRINT_CRC, entry 965) started on LXY22_CRC 7           * Do you want to continue the installation? n G           %VMSINSTAL-I-RELMOVED , The product's release notes have been )           successfully moved to SYS$HELP. 9            Installation of PSI_AC V4.3 completed at 10:38e  A           Example of a VAX PSI Access Installation            B-1t e  o            ,            VMSINSTAL procedure done at 10:38  .           $ @sys$update:vmsinstal psi_ac msa0:  ?            VAX/VMS Software Product Installation Procedure V5.1t  %           It is 21-FEB-1989 at 10:45. 9           Enter a question mark (?) at any time for help.o  N           * Are you satisfied with the backup of your system disk [YES]? <RET>  3           The following products will be processed:              PSI_AC V4.3o9            Beginning installation of PSI_AC V4.3 at 10:45o  ?           %VMSINSTAL-I-RESTORE, Restoring product saveset A ...eG           %VMSINSTAL-I-RELMOVED , The product's release notes have been5)           successfully moved to SYS$HELP.   9              VAX PSI Access V4.3 installation procedures.g  1           * Do you want X.29 support [YES]? <RET>g  6           * Do you want all the utilities [YES]? <RET>  I           There are no more questions to answer during this installation.   ?           %VMSINSTAL-I-RESTORE, Restoring product saveset B ...s?           %VMSINSTAL-I-RESTORE, Restoring product saveset C ... ?           %VMSINSTAL-I-RESTORE, Restoring product saveset D ...i?           %VMSINSTAL-I-RESTORE, Restoring product saveset E ...   L           Removing any obsolete files from any previous VAX PSI installation  0            Installing VAX PSI Access V4.3 files.  /            VAX PSI Access V4.3 files installed.i  G           To  complete the installation, follow the instructions below:s  L           -  Execute  the  command  procedure  SYS$MANAGER:PSI_SET_UP.COM toI              produce a LOAD_PSI043.COM and set up the permanent database.s  N           -  On a system which is running DECnet execute the command procedure;              SYS$MANAGER:STARTPSI.COM, to bring up VAX PSI. I              On a system which is not running DECnet, execute the commandlO              procedure SYS$MANAGER:STARTNET.COM to bring up DECnet and VAX PSI.e  B           %VMSINSTAL-I-MOVEFILES, Files will now be moved to their           target directories...   N           B-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures    s            9            Installation of PSI_AC V4.3 completed at 11:06   ,            VMSINSTAL procedure done at 11:07  #           $ @sys$manager:psi_set_upn  @           This command procedure assists in configuring VAX PSI.  L           LOAD_PSI043.COM must be built before attempting to start  VAX PSI.J           The load file from an earlier version of VAX PSI cannot be used.  @           Do you wish to build load_psi043.com now  [YES]? <RET>  F           This  command  file  assists  in  creating  LOAD_PSI043.COM.  L           LOAD_PSI043.COM is a command file  used  to  SYSGEN  the  VAX  PSI0           supported devices and startup the ACP.  <           The system being configured is of an unknown type.  @           What type of bus does the system being configured have'           (UNIBUS,QBUS,BI,nobus)  nobusl  ?           Do you want to set up a default network  [YES]? <RET>m  @           Default network name                (network-id): net1  K           The following NCP command may be used to configure the  permanent 6           database to support incoming X.29 terminals:  /           NCP define module X29-server state onF  ;           Do you want the database defined now [YES]? <RET>e  3           Do you want to use  PSI MAIL [YES]? <RET> A           Do you want support for incoming  PSI MAIL [YES]? <RET>t  J           The PSI_MAIL object needs to run in an account with the right to%           accept incoming X.25 calls.   1           Username    [DECNET]     (string):<RET> 3           Password                 (string): DECNETn3           Verification             (string): DECNET   L           The following NCP commands may be used to configure the  permanent1           database to support incoming  PSI MAIL:.  H           NCP define object psi_mail number 0 file sys$system:psi$mail -'           user DECNET password PASSWORD M           NCP define module x25-server destination psi_mail object psi_mail -h6           call mask ffffffffffffffffffffffffffffffff -5           call value ff00000056332e30204d41494c2d3131   ;           Do you want the database defined now [YES]? <RET>   A           Example of a VAX PSI Access Installation            B-3e                 L           Purging any  previous PSI_MAIL  definitions.   Please  ignore  any           error messages.1  5           Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COMh  N           Do you wish to add network entries to the database now  [YES]? <RET>  D           You are assisted here in defining the X25-ACCESS database.  H           Do you want to define the X25-ACCESS database now [YES]? <RET>  L           This  procedure  can  purge  the  database  to  remove  all  knownL           connector  nodes  information  before  it  updates  the  permanent           database.e  G           The following NCP command will be used to purge the database:n  8           NCP PURGE MODULE X25-ACCESS KNOWN NETWORKS ALL  ?           Do you want the information in the permanent database             purged now [NO]? <RET>  L           Your VAX PSI Access system uses a  connector node  to  communicateL           with one or more PSDNs.  You will be asked for a network name  forL           the connection to the connector  system and  the node name of thatL           system.  The network name you supply  MUST  be  the  same  as  theB           network name on the connector node that you wish to use.  0           Network name        (network-id): net11           Connector node         (node-id): boris              Network    = net12"           Connector node   = boris  8           Is the above information correct  [YES]? <RET>  L           The following NCP command will be used  to  update  the  permanent           database:   >           NCP define module x25-access network net1 node boris  B           Adding entry to the X25-ACCESS database for network net1  @           Are there any more NETWORKS to be defined  [NO]? <RET>  5           Do you wish to load VAX PSI now [NO]? <RET>   L           To check out your installation after starting VAX PSI refer to theH           Configuration Testing Chapter in the VAX PSI Management Guide.  N           B-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures                               A           ______________________________________________________Ca  @                    Example of a VAX PSI Combination Installation        A              The following is an example of a VAX PSI Combinatione              installation.  :                $ @sys$update:vmsinstal psi msa0: options n  G                    VAX/VMS Software Product Installation Procedure V5.1   *                It is 20-FEB-1989 at 14:45.>                Enter a question mark (?) at any time for help.  A                * Are you satisfied with the backup of your systemm                 disk [YES]? <RET>  8                The following products will be processed:                  VAX PSI V4.3:?                 Beginning installation of VAX PSI V4.3 at 14:45   D                %VMSINSTAL-I-RESTORE, Restoring product saveset A ...  I                Release notes with this kit are always copied to SYS$HELP.   0                Additional Release Notes Options:  *                  1.  Display release notes(                  2.  Print release notes!                  3.  Both 1 and 2o&                  4.  None of the above  A           Example of a VAX PSI Combination Installation       C-1  .  i            )                * Select option [2]: <RET>e.                * Queue name [SYS$PRINT]: <RET>O                Job PSI043 (queue SYS$PRINT_CRC, entry 964) started on LXY22_CRCa<                * Do you want to continue the installation? nL                %VMSINSTAL-I-RELMOVED , The product's release notes have been.                successfully moved to SYS$HELP.F                        Installation of VAX PSI V4.3 completed at 14:48  1                 VMSINSTAL procedure done at 14:48   0                $ @sys$update:vmsinstal psi msa0:  I                      VAX/VMS Software Product Installation Procedure V5.1S  *                It is 20-FEB-1989 at 14:55.>                Enter a question mark (?) at any time for help.  A                * Are you satisfied with the backup of your system "                  disk [YES]? <RET>  8                The following products will be processed:                  VAX PSI V4.3   ?                 Beginning installation of VAX PSI V4.3 at 14:55e  D                %VMSINSTAL-I-RESTORE, Restoring product saveset A ...L                %VMSINSTAL-I-RELMOVED , The product's release notes have been.                successfully moved to SYS$HELP.  5                 VAX PSI V4.3 installation procedures.c  6                * Do you want X.29 support [YES]? <RET>  ;                * Do you want all the utilities [YES]? <RET>9  N                There are no more questions to answer during this installation.  D                %VMSINSTAL-I-RESTORE, Restoring product saveset B ...D                %VMSINSTAL-I-RESTORE, Restoring product saveset C ...D                %VMSINSTAL-I-RESTORE, Restoring product saveset D ...D                %VMSINSTAL-I-RESTORE, Restoring product saveset E ...  M                Removing obsolete files from any previous VAX PSI installationg  /                  Installing VAX PSI V4.3 files.l  -                 VAX PSI V4.3 files installed..  L                To  complete the installation, follow the instructions below:  Q                -  Execute  the  command  procedure  SYS$MANAGER:PSI_SET_UP.COM to N                   produce a LOAD_PSI043.COM and set up the permanent database.  N           C-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures u  n            I                -  On a system which is running DECnet execute the command J                   procedure SYS$MANAGER:STARTPSI.COM, to bring up VAX PSI.N                   On a system which is not running DECnet, execute the commandK                   procedure SYS$MANAGER:STARTNET.COM to bring up DECnet ando                   VAX PSI.  G                %VMSINSTAL-I-MOVEFILES, Files will now be moved to theira$                target directories...  ?                 Installation of VAX PSI V4.3 completed at 15:31   1                 VMSINSTAL procedure done at 15:32   1                @sys$update:vmsinstal psi_ac msa0:pD                 VAX/VMS Software Product Installation Procedure V5.1  *                It is 20-FEB-1989 at 16:03.>                Enter a question mark (?) at any time for help.  :                * Are you satisfied with the backup of your)                  system disk [YES]? <RET>o  8                The following products will be processed:                  PSI_AC V4.3  >                 Beginning installation of PSI_AC V4.3 at 16:04  D                %VMSINSTAL-I-RESTORE, Restoring product saveset A ...L                %VMSINSTAL-I-RELMOVED , The product's release notes have been.                successfully moved to SYS$HELP.  <                 VAX PSI Access V4.3 installation procedures.  F                * Do you want to install a combination system [NO]? Yes  6                * Do you want X.29 support [YES]? <RET>  ;                * Do you want all the utilities [YES]? <RET>X  N                There are no more questions to answer during this installation.  D                %VMSINSTAL-I-RESTORE, Restoring product saveset B ...D                %VMSINSTAL-I-RESTORE, Restoring product saveset C ...D                %VMSINSTAL-I-RESTORE, Restoring product saveset D ...D                %VMSINSTAL-I-RESTORE, Restoring product saveset E ...  M                Removing obsolete files from any previous VAX PSI installationd  5                 Installing VAX PSI Access V4.3 files.n  4                 VAX PSI Access V4.3 files installed.  L                To  complete the installation, follow the instructions below:  A           Example of a VAX PSI Combination Installation       C-3m    i            Q                -  Execute  the  command  procedure  SYS$MANAGER:PSI_SET_UP.COM to N                   produce a LOAD_PSI043.COM and set up the permanent database.  $                -  Reboot the system.  G                %VMSINSTAL-I-MOVEFILES, Files will now be moved to theira$                target directories...>                 Installation of PSI_AC V4.3 completed at 16:40  1                 VMSINSTAL procedure done at 16:40S  &                @sys$manager:psi_set_up  E                This command procedure assists in configuring VAX PSI.D  Q                LOAD_PSI043.COM must be built before attempting to start  VAX PSI.SO                The load file from an earlier version of VAX PSI cannot be used.   E                Do you wish to build load_psi043.com now  [YES]? <RET>>  K                This  command  file  assists  in  creating  LOAD_PSI043.COM.n  Q                LOAD_PSI043.COM is a command file  used  to  SYSGEN  the  VAX  PSI 5                supported devices and startup the ACP.i  E                Do you want to set up a default network  [YES]?  <RET>S  E                Default network name                (network-id): net1a  5                Device type         (dev-c-u): kmv-0-0   .                Default CSR address is %O7604202                CSR address           (octal):<RET>  )                Default VECTOR is %O000310r3                Vector                (octal): <RET>n  2                Configuration data for line KMV-0-0  0                Device CSR is            %O7604200                Device VECTOR is         %O000310  >                Do you want to Keep, Alter or Delete this entry#                (K, A, D) [K]? <RET>o  8                Device KMV-0-0 added to new configuration  >                Do you want to configure more lines [NO]? <RET>  P                The following NCP command may be used to configure the  permanent;                database to support incoming X.29 terminals:d  4                NCP define module X29-server state on  @                Do you want the database defined now [YES]? <RET>  N           C-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures                 8                Do you want to use  PSI MAIL [YES]? <RET>F                Do you want support for incoming  PSI MAIL [YES]? <RET>  O                The PSI_MAIL object needs to run in an account with the right toe*                accept incoming X.25 calls.  7                Username    [DECNET]     (string): <RET>_8                Password                 (string): decnet8                Verification             (string): decnet  Q                The following NCP commands may be used to configure the  permanent 6                database to support incoming  PSI MAIL:  M                NCP define object psi_mail number 0 file sys$system:psi$mail - ,                user DECNET password PASSWORDG                NCP define module x25-server destination psi_mail object F                psi_mail - call mask ffffffffffffffffffffffffffffffff -:                call value ff00000056332e30204d41494c2d3131  @                Do you want the database defined now [YES]? <RET>  Q                Purging any  previous PSI_MAIL  definitions.   Please  ignore  anyT                error messages.  '                %NCP-I-SUCCESS,  Successh                 Object = PSI_MAIL5                NML-I-RECDELET, Database entry deleted:'                %NCP-I-SUCCESS,  Successn  6                %NML-I-RECDELET, Database entry deleted  ;                 Created SYS$SYSROOT:[SYSMGR]LOAD_PSI043.COMe  E                Do you wish to add network, line or DTE entries to the.)                database now  [YES]? <RET>p  I                You are assisted here in defining the X25-ACCESS database.   M                Do you want to define the X25-ACCESS database now [YES]? <RET>   Q                This  procedure  can  purge  the  database  to  remove  all  knownDQ                connector  nodes  information  before  it  updates  the  permanentH                database.  L                The following NCP command will be used to purge the database:  =                NCP PURGE MODULE X25-ACCESS KNOWN NETWORKS ALLl  D                Do you want the information in the permanent database%                purged now [NO]? <RET>s  A           Example of a VAX PSI Combination Installation       C-5n i  f            Q                Your VAX PSI Access system uses a  connector node  to  communicate Q                with one or more PSDNs.  You will be asked for a network name  for Q                the connection to the connector  system and  the node name of that3Q                system.  The network name you supply  MUST  be  the  same  as  the G                network name on the connector node that you wish to use.e  5                Network name        (network-id): net2 6                Connector node         (node-id): bella                   Network    = net2'                Connector node   = bellao  =                Is the above information correct  [YES]? <RET>e  Q                The following NCP command will be used  to  update  the  permanent-                database:  C                NCP define module x25-access network net2 node bellas  G                Adding entry to the X25-ACCESS database for network net2t  E                Are there any more NETWORKS to be defined  [NO]? <RET>.  Q                This command procedure allows you to define one  or  more  PSDN(s) A                and one or more DTEs associated with each network.   O                Do you want to define the X25-PROTOCOL database now [YES]? <RET>o  Q                You can use this procedure to  purge the  database  to  remove allYQ                DTEs  and  all  X.25  protocol  information  before  updating  thepQ                permanent database.  You can also use this procedure to remove theIQ                line  information  from  the  database.  Note  that  if  the  linerQ                permanent  database is purged then all DECnet lines along with VAXI)                PSI lines will be removed.   Q                The following NCP commands will be used to purge the DTE and  X.25c"                permanent database:  ?                NCP purge module x25-protocol known networks allMJ                NCP purge module x25-protocol known dtes known networks all  Q                The following  NCP  commands  will  be  used  to  purge  the  line "                permanent database:  (                NCP purge known lines all  H                Do you want the information in the X.25 and DTE permanent)                database purged [NO]?<RET>s  N           C-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures .               I                Do you want the line information in the permanent databasek"                purged  [NO]? <RET>  Q                PSDN and profile names are defined here.  You can  define  one  or Q                more  PSDNs.   For  each  PSDN  you  will  be asked to provide theTB                network name and the profile name for that network.  ,                Network name   (string): net15                Profile name   (string) [net1]: sonnet   I                The following command will be used to update the permanent                 database:  <                NCP define module x25-protocol network net1 -!                    profile sonnet D                Do you want the information in the permanent database$                updated  [YES]? <RET>  F                DTEs are defined here.  You can define one or more DTEsI                connected to this network.  For each DTE you will be askeds4                to provide the following information:                  o DTE address8                o Range of channels to be used by the DTE-                o Line associated with the DTEl  5                DTE address    (number): 2342123456789 1                Channels range   (list): 1250-1150 -                Line name     (dev-c-u): kmv-0   @                The following NCP commands will be used to update&                the permanent database.  H                NCP define line kmv-0 network net1 protocol lapb state onA                NCP define module x25-protocol dte 2342123456789 - !                    network net1 -P'                    channels 1250-1150 -s                    line kmv-0 -e                    state onM  M                Do you want to update the permanent database now  [YES]? <RET>e                   Updating database  D                Do you want to define any more DTEs connected to this"                network [NO]? <RET>  B                Do you want to define any more networks [NO]? <RET>  I                Do you wish to add VAX PSI Multi-host entries [YES]? <RET>t  A           Example of a VAX PSI Combination Installation       C-7f    e            Q                X25-Server destinations are set up  here.  These  permit  incomingoQ                calls received by this node to be redirected  to  the  appropriateLQ                host. This procedure asks for a list of hosts with  VAX PSI AccessGQ                installed. This list of nodes will not include the  node  you  are $                currently working on.  F                Destination name       (string)                 : gretaF                Destination node name  (string)                 : gretaF                Destination priority                     [200]  : <RET>F                Call mask              (2-32 hex)        [None] : <RET>F                Call value             (2-32 hex)        [None] : <RET>F                Closed user group name (1-16 characters) [None] : <RET>F                Sending address        (1-15 decimal)    [None] : <RET>F                Subaddress range       (decimal range)   [None] : <RET>F                Object identification  (string)          [36]   : <RET>  9                The destination will be set up as follows:t  -                NCP>define module x25-server - #                 destination greta -s                 node greta -                 priority 200 -                 object 36s  G                Do you want to define this destination now  [YES]? <RET>   /                 Updating the permanent database   G                Do you want to define any more destinations  [NO]? <RET>d  O                To check out your installation after restarting VAX PSI refer to Q                the Configuration Testing Chapter in the VAX PSI Management Guide.                   N           C-8  VAX P.S.I. (Packetnet System Interface) Installation Procedures g  2                          A           ______________________________________________________D   @                        Contents of the VAX PSI Distribution Kits        B              During the installation, the VAX PSI software createsA              a file that contains the name of each file installedtE              during that particular installation. This file is calledrD              PSI$IVP.TXT and VAX PSI copies it to the SYS$UPDATE di-E              rectory. To see which files VAX PSI has installed, printl=              a copy of this file or view it on your terminal.f  H              When you install VAX PSI or VAX PSI Access on a VAXcluster,A              all files reside in the System Common Root area, ex->B              cept for the following which are copied to the System              Specific area:                  _ PSI$043.DAT   "               _ PSI$ACCESS_043.DAT                  _ PSI_SECURITY.COM  6           D.1 Contents of the VAX PSI Distribution Kit  A              This section contains an alphabetical listing of thea7              VAX PSI files installed in each directory.O  C              For all systems, the images listed below are copied to,/              the SYS$LOADABLE_IMAGES directory:b    A           Contents of the VAX PSI Distribution Kits           D-1i t  X                          NWDRIVER.EXED              PSI$L3CS.EXE5              PSI$L3NM.EXE               PSI$NMR.EXE              LES$DECNET.EXEh              LES$DECNET_ALT.EXEw              LES$DECNET_EVL.EXEe              PSI$GAP.EXE              LES$LES.EXE              PSI$043.DAT              PSI$DR.EXEl              PSI$DRX.EXE              PSI$L2.EXEs              PSI$L2NM.EXER              PSI$L2E.EXE              PSI$L2DM.EXE               PSI$L3.EXEr              PSI$NETPRF.EXEa  A              The following files are copied to the SYS$SYSTEM di-V              rectory:a                PSI$MAIL.COM                PSI$LES_CONTROL.DAT              LES$STARTUP.EXE              LES$ACP.EXE  B              The following files are copied to the SYS$MANAGER di-              rectory:                 PSI_CONFIG.COMc              PSI_DEFINE.COMe              PSI_SET_UP.COM               STARTPSI.COMy               PSI$CONFIG_HELP.COM$              PSI$GET_CONFIG_DATA.COM              PSI_MULTI_HOST.COM   B              The following files are copied to the SYS$LIBRARY di-              rectory:n  N           D-2  VAX P.S.I. (Packetnet System Interface) Installation Procedures e  r                          PSILIB.MLB               PSILIB.REQr              PSI_MAILSHR.EXE              PSI$ACPCODESHR.EXEw              PSI$ACPDATASHR.EXEm              LES$ACP_CODE.EXE:  B              The following files are copied to the SYS$LIBRARY di-C              rectory if the corresponding language (shown in brack-o              ets) is present:t  !              PSILIB.FOR (FORTRAN)               PSILIB.H   (C)               PSILIB.L32 (BLISS)u               PSILIB.PAS (PASCAL)                                                    A           Contents of the VAX PSI Distribution Kits           D-3O O  a            B              The following files are copied to the SYS$TEST direc-              tory:                PSI_ICP.COM              PSI$XTR.COM              PSI$XTR.EXE              PSI$XTS.EXE              PSI$PR.EXE               PSI$CTP.EXE              PSI$CTP.TLB              PSI$CTP_NETOBJ.COMm#              PSI$CTP_ADD_NETOBJ.COM #              PSI$CTP_REM_NETOBJ.COMa  D              The following file is copied to the SYS$HELP directory:  !              PSI043.RELEASE_NOTES   B              The following files are copied to the SYS$MESSAGE di-              rectory:a                PSI$MESSAGES.EXEN!              LES$ACP_MESSAGES.EXEn  C              The following files are copied to the SYS$EXAMPLES di-n              rectory:                 PSI$CHARGING.EXEm              PSI$CHARGING.MARe!              PSI$DLM_REDIRECT.MARe#              PSI$X25_SEND_BASIC.BASr              PSI$X25_SEND_C.C #              PSI$X25_SEND_COBOL.COBh%              PSI$X25_SEND_FORTRAN.FOR #              PSI$X25_SEND_MACRO.MAR $              PSI$X25_SEND_PASCAL.PAS&              PSI$X25_RECEIVE_BASIC.BAS               PSI$X25_RECEIVE_C.C&              PSI$X25_RECEIVE_COBOL.COB(              PSI$X25_RECEIVE_FORTRAN.FOR&              PSI$X25_RECEIVE_MACRO.MAR'              PSI$X25_RECEIVE_PASCAL.PASe  N           D-4  VAX P.S.I. (Packetnet System Interface) Installation Procedures    v            D              The following images are NOT installed if you are load-B              ing VAX PSI on a MicroVAX. These images are copied to/              the SYS$LOADABLE_IMAGES directory:T                PSI$KMXDIA.EXEe              PSI$KMXPDM.EXE               PSI$KMXPRO.EXE               PSI$KMYDIA.EXEx              PSI$KMYPDM.EXE               PSI$KMYPRO.EXEe              XNDRIVER.EXEa              XSDRIVER.EXEe              XWDRIVER.EXE   D              The following images are NOT installed if you are load-B              ing VAX PSI on a MicroVAX. These images are copied to$              the SYS$TEST directory:                UETPSIDUP.COM              UETPSIDUP.EXE  E              The following images are only installed if you are load- K              ing VAX PSI on a MicroVAX, and are copied to the SYS$LOADABLE_D              IMAGES directory:                PSI$KMVPRO.EXE               UEDRIVER.EXE               UVDRIVER.EXE   A              If you request X.29 support, the following is copiedb4              into the SYS$LOADABLE_IMAGES directory:                NVDRIVER.EXEn  B              If you request X.29 support, the following are copied+              into the SYS$SYSTEM directory:                 PSIPAD.EXEk              PSISETX29.EXE              PSISHOWX29.EXE   A              If you request X.29 support, the following is copied )              into the SYS$HELP directory:t  A           Contents of the VAX PSI Distribution Kits           D-5                                PSIPADHLP.HLB  A              If you request X.29 support, the following is copiedD,              into the SYS$MESSAGE directory:  !              PSI$PAD_MESSAGES.EXE   B              If you request X.29 support, the following are copied-              into the SYS$EXAMPLES directory:   (              PSI$X29_DESTINATION_COM.COM*              PSI$X29_DESTINATION_MACRO.MAR$              PSI$X29_DESTINATION_C.C+              PSI$X29_DESTINATION_PASCAL.PAS )              PSI$X29_NETPROCESS_MACRO.MARc-              PSI$X29_NV_UNIT_NUMBER_MACRO.MARc'              PSI$X29_OUTGOING_MACRO.MAR !              PSI$X29_OUTGOING_C.C (              PSI$X29_OUTGOING_PASCAL.PAS"              PSI$X29_TEMPLATES.MAR&              PSI$X29_USER_TEMPLATE.COM(              PSI$X29_SYSTEM_TEMPLATE.COM  D              If you request the VAX PSI utilities, the following are              copied into the+              SYS$LOADABLE_IMAGES directory:2                LES$TRACE.EXE              LES$TRACE_MBX.EXE  D              If you request the VAX PSI utilities, the following are              copied into the"              SYS$SYSTEM directory:                PSIACC.EXE)              PSIAUTHORIZE.EXE               PSIKDA.EXE               NETLTC.EXE:              NETTRACE.EXEc  D              If you request the VAX PSI utilities, the following are              copied into the#              SYS$LIBRARY directory:n  N           D-6  VAX P.S.I. (Packetnet System Interface) Installation Procedures e  -                          PSIAUTHORIZE.INIT$              NETTRACE$12_ANALYZE.EXE%              NETTRACE$12E_ANALYZE.EXE $              NETTRACE$13_ANALYZE.EXE%              NETTRACE$GAP_ANALYZE.EXE %              NETTRACE$GTW_ANALYZE.EXEe*              NETTRACE$13_DDX76_ANALYZE.EXE              NETTRACE$KEY.INIT%              NETTRACE$X29_ANALYZE.EXE                                                                 A           Contents of the VAX PSI Distribution Kits           D-7t s               D              If you request the VAX PSI utilities, the following are              copied into the               SYS$HELP directory:                 PSIAUTHORIZEHLP.HLB              TRACEHLP.HLB   C              If you request the VAX PSI utilities, the following is               copied into the#              SYS$MESSAGE directory:   "              NETTRACE_MESSAGES.EXE  D              If you request the VAX PSI utilities, the following are              copied into the#              SYS$MANAGER directory:f                PSI_SECURITY.COMl              PSIACCOUNTING.COM!              NETTRACE_INSTALL.COM "              NETTRACE_SECURITY.COM               PSI_TRACE_START.COM  A              LOAD_PSI043.COM is created by PSI_SET_UP.COM, and is>A              copied to the system specific SYS$MANAGER directory.m  C              PSIACCOUNTING.DAT is created when the Accounting util- D              ity is turned on in the system specific SYS$MANAGER di-              rectory.   =           D.2 Contents of the VAX PSI Access Distribution Kits  A              This section contains an alphabetical listing of thed>              VAX PSI Access files installed in each directory.  C              For all systems, the images listed below reside in thec+              SYS$LOADABLE_IMAGES directory:                 NWDRIVER.EXE-              PSI$L3CS.EXE               PSI$L3NM.EXE               PSI$NMR.EXE  N           D-8  VAX P.S.I. (Packetnet System Interface) Installation Procedures                               LES$DECNET.EXES              LES$DECNET_ALT.EXEI              LES$DECNET_EVL.EXEE              PSI$GAP.EXE              LES$LES.EXE              PSI$ACCESS_043.DAT               PSI$GTR.EXE                                                                    A           Contents of the VAX PSI Distribution Kits           D-9                  A              The following files are copied to the SYS$SYSTEM di-a              rectory:I                PSI$MAIL.COMC               PSI$LES_CONTROL.DAT              LES$STARTUP.EXE              LES$ACP.EXE    B              The following files are copied to the SYS$MANAGER di-              rectory:I                PSI_CONFIG.COM.               PSI$CONFIG_HELP.COM              PSI_SET_UP.COM               PSI_DEFINE.COMC$              PSI$GET_CONFIG_DATA.COM              STARTPSI.COMH  B              The following files are copied to the SYS$LIBRARY di-              rectory:r                PSILIB.MLBV              PSILIB.REQe              PSI_MAILSHR.EXE              PSI$ACPCODESHR.EXE               PSI$ACPDATASHR.EXEP              LES$ACP_CODE.EXEI  B              The following files are copied to the SYS$LIBRARY di-C              rectory if the corresponding language (shown in brack-f              ets) is present:A  !              PSILIB.FOR (FORTRAN)o              PSILIB.H   (C)n              PSILIB.L32 (BLISS)e               PSILIB.PAS (PASCAL)  B              The following files are copied to the SYS$TEST direc-              tory:  O           D-10  VAX P.S.I. (Packetnet System Interface) Installation Procedureso n  o                          PSI_ICP.COM              PSI$XTR.COM              PSI$XTR.EXE              PSI$XTS.EXE              PSI$PR.EXE               PSI$CTP.EXE              PSI$CTP.TLB              PSI$CTP_NETOBJ.COMX#              PSI$CTP_ADD_NETOBJ.COM #              PSI$CTP_REM_NETOBJ.COMI  D              The following file is copied to the SYS$HELP directory:  $              PSI_AC043.RELEASE_NOTES  B              The following files are copied to the SYS$MESSAGE di-              rectory:                 PSI$MESSAGES.EXE.!              LES$ACP_MESSAGES.EXEf  C              The following files are copied to the SYS$EXAMPLES di-a              rectory:S                PSI$CHARGING.EXEM              PSI$CHARGING.MARe!              PSI$DLM_REDIRECT.MARS#              PSI$X25_SEND_BASIC.BASy              PSI$X25_SEND_C.C.#              PSI$X25_SEND_COBOL.COB %              PSI$X25_SEND_FORTRAN.FOR #              PSI$X25_SEND_MACRO.MAR $              PSI$X25_SEND_PASCAL.PAS&              PSI$X25_RECEIVE_BASIC.BAS               PSI$X25_RECEIVE_C.C&              PSI$X25_RECEIVE_COBOL.COB(              PSI$X25_RECEIVE_FORTRAN.FOR&              PSI$X25_RECEIVE_MACRO.MAR'              PSI$X25_RECEIVE_PASCAL.PAS5    A           Contents of the VAX PSI Distribution Kits          D-11  P  X            E              For VAX PSI Access, the files for X.29 support and util-XB              ities are installed in the same areas as for VAX PSI.B              See Section D.1 for details of which files are copied              to which areas.  A              LOAD_PSI043.COM is created by PSI_SET_UP.COM, and iseA              copied to the system specific SYS$MANAGER directory.   C              PSIACCOUNTING.DAT is created when the Accounting util-PC              ity is turned on, and is copied to the system specific.#              SYS$MANAGER directory.                                                             O           D-12  VAX P.S.I. (Packetnet System Interface) Installation ProceduresV P  o                            A           _______________________________________________________U  A                                                             Indexg        ;           A                            Channels range, 2-7,I  4           Access mode VAX PSI, 2-5        3-27, 5-19<             installation, 4-1  to      Channels used by DTE,.                4-23                       3-27?           Accounting utility, 3-9,     Closed User Group, 2-10, 4              4-8                          3-31, 5-23?           Account name, 2-12           Combination system, 1-7,e-           ADAPTER, 3-21                   4-6 A             default, 3-21, 5-10          installing, 5-1  to 5-26X7           Adding extra network           tailoring, 5-2X9              connections, 6-5          Command files, 1-7n?           Adding VAX PSI systems,      Completing the installa- :              6-4                          tion, 3-11, 4-109             Access, 6-5                Configuration data 6             Multi-host, 6-5              checking, 5-7>                                        Configuring lines, 3-18@           C                            Configuring the permanent?                                           database, 3-24, 4-16,r.           Call mask, 2-9, 3-31,           5-14;              4-18, 5-13, 5-23          Configuring the X25- ?           Call value, 2-9, 3-31,          ACCESS database, 4-19.@              4-18, 5-13, 5-23          Connector node, 1-2, 1-6,:           Canceling the installa-         1-11, 4-21, 5-163              tion, 3-10, 4-9             name, 2-11 >           Changing the default         Controller letter, 3-2,-              network, 6-6                 4-2M*                                        CSR  A                                                           Index-1e                 :           CSR (Cont.)                  Disk space required@             address, 2-7, 3-14,          for basic product, 2-13?                3-18, 3-21, 5-2, 5-10     for utilities support, 0             default, 3-21, 5-10             2-13?           CUG                            for X.29 support, 2-13R>             see Closed User Group      Distribution kits, 1-5,-                                           2-4 8           D                              installing, 5-1;                                        Distribution volumes ;           Database                       mounting, 3-3, 4-2l>             configuring the            DTE address, 1-12, 2-7,?                permanent, 3-24,           3-14, 3-27, 5-3, 5-19$>                4-16, 5-14              DTE permanent database,4             configuring the X25-          3-26, 5-18(                ACCESS, 4-19            F             define, 3-22, 3-25,N8                4-16, 4-19              Free blocks, 2-13!             updating, 3-26, 4-19, (                5-4, 5-14               H"             X25-PROTOCOL, 1-5, 1-70             X25-SERVER, 1-5, 1-7       Host, 1-6(             X29-SERVER, 1-6            I           DECnet, 4-143           DECnet logical link, 1-6     Installation:=           DECnet-VAX, 1-6                Access mode, 4-1  to 0           Default network, 5-6              4-23=             changing, 6-6                canceling, 3-10, 4-9 @             name, 3-17, 4-16, 5-7        combination system, 5-1#             setting up, 3-17, 4-15, 3                5-6                          to 5-26 A           Destination                    Multi-host mode, 3-1  toS0             name, 2-8, 3-30, 5-22           3-34=             node, 5-23                   Native mode, 3-1  toC0             node name, 2-8, 3-30            3-34@             priority, 2-8, 3-31,       Installation preparations/                5-23                       , 2-1r>             set up, 3-32               Installation procedures:           Device code, 3-2, 4-2          introduction, 1-7@           Device name, 3-2, 4-1          starting, 3-1, 4-1, 5-11           Devices                      Installing ?             setting up, 3-16, 5-6        distribution kits, 5-1h@           Device type, 3-19, 5-8       Installing VAX PSI files,2           Disk space, 2-13, 3-7,          3-1, 4-1              4-6             Index-2L A  _            8           Installing VAX PSI on a      Migrating (Cont.);              VAXcluster, 1-8             from Multi-host to   7           K                                 Native, 6-3s>                                          from Native to Multi-5           KDA utility, 3-9, 4-8             host, 6-3L9           L                            Modes of operationL5                                          VAX PSI, 1-1 <           License Management           Mounting distribution;              Facility, 2-2                volumes, 3-3, 4-2i;           Licensing VAX PSI, 2-3       Multi-host operationT9             on a cluster, 2-3            setting up, 5-22 ?           Line and DTE, 3-27           Multi-host VAX PSI, 1-6,L-           Line database, 3-26             2-5 >           Line name, 2-7, 3-28,          installation, 3-1  to0              5-19                           3-343           Line parameters, 5-11          node, 5-15I  (           LMF                          N"             see License Management?                Facility                Native mode VAX PSI, 1-5 >           LOAD_PSI043.COM, 1-7,          installation, 3-1  to0              3-11, 3-14, 4-10, 4-13,        3-34@              4-17, 5-3                 NCP commands, 3-22, 3-23,A             creating, 3-17, 4-12,         3-24, 3-28, 3-30, 4-16, A                4-15, 5-6, 5-14            4-17, 5-12, 5-14, 5-15,c4           Logical Channel Number,         5-17, 5-18;              3-14, 5-3                 NCP DEFINE commands,s:           M                               3-25, 4-19, 5-14.                                        Network;           MAXBUF SYSGEN parameter,       default, 3-17, 5-6e:                                        Network connections4              3-11, 4-10                  adding, 6-5@           Media required for           Network name, 1-10, 1-11,@              installation, 2-4            2-6, 2-11, 3-17, 3-26,?           Migrating                       4-20, 5-6, 5-15, 5-18 6             from Access to               default, 4-16;                Combination, 6-3          requirements, 1-10 @             from Access to Multi-      Network profile name, 2-6(                host/Native, 6-3        O"             from Multi-host/Native=                to Access, 6-3          Object identification,M4             from Multi-host/Native        3-32, 5-24>                to Combination, 6-3     Object identifier, 2-12  A                                                           Index-3  r  o            <           Operation                    PSI_SET_UP.COM, 3-11,9             VAX PSI modes of, 1-1         4-10, 4-12, 5-1_>           Optional parameters,         PSI_VAX SET_UP.COM, 1-7(              3-31, 5-23                Q  ;           P                            Queue name, 3-5, 4-4   (           PAK                          R             see Product >                Authorization Key       Release notes, 3-5, 4-4(           Password, 2-12               S           Permanent database/             configuring, 3-24, 4-16,   SavesetsS<                5-12, 5-14                restoring, 3-9, 4-8=             updating, 3-27, 5-21       Security utility, 3-9,I-           Product Authorization           4-8 =              Key, 2-3                  Sending address, 2-10,S4             entering the PAK, 2-3         3-31, 5-23@           Profile name, 1-12, 3-26,    Setting up devices, 3-13,3              5-18                         3-16, 5-6 2           PSDN, 1-12                   Starting up<             connecting to, 1-7,          VAX PSI, 3-33, 5-25=                3-26, 4-20, 5-15          VAX PSI Access, 4-22o?             default, 4-15              STARTNET.COM, 1-7, 3-12, A           PSDN link, 1-6                  3-24, 3-33, 4-11, 4-18, 
           PSI..             see VAX PSI                   4-22@           PSI043.RELEASE_NOTES, 3-6    STARTPSI.COM, 3-12, 3-33,:           PSI-ACCESS Product              4-11, 4-22, 5-25>              License, 4-9              Subaddress range, 2-10,4           PSI MAIL, 3-22, 4-16,           3-32, 5-24?              5-11                      SYS$HELP directory, 3-6,9-             database, 3-23                4-5l=             incoming, 3-22, 4-17,      SYS$MANAGER directory, @                5-12                       3-11, 3-13, 4-10, 4-12>             password, 3-22, 4-17,      SYS$SYSDEVICE, 3-1, 4-1;                5-12                    SYS$UPDATE, 3-9, 4-8 8             username, 3-22, 4-17,      Sysgen parameters2                5-12                       required>           PSI_AC043.RELEASE_NOTES,       for Access only, 2-16>              4-5                         for Combination, 2-16A           PSI_SECURITY.COM, 3-8,         for each local DTE, 2-16 A              4-7, 6-1                    for each virtual circuit 2                                             , 2-16             Index-4     c            6           Sysgen parameters            VAX PSI (Cont.)5              required (Cont.)            loading, 5-4u@             for Multi-host only,         modes of operation, 1-1=                2-16                      Multi-host mode, 1-1-9             for trace, 2-16              Native mode, 1-1X5             for X.29, 2-16               options, 3-8d=           SYSGEN parameters              product license, 2-2rA              required, 2-14              starting up, 3-33, 4-22,-0           System disk, 3-1, 4-1             5-25?             backup, 3-3, 4-2             tailoring, 3-13, 4-12,e/                                             5-2 7           T                              utilities, 3-8 :                                        VAX PSI Access, 1-75           Trace utility, 3-9, 4-8        options, 4-7 =           U                              product license, 2-3 :                                          starting up, 4-227           Unibus adapter, 3-18, 5-7      utilities, 4-7,=           Unit number, 3-2, 4-2        VAX PSI and Multi-host 9           Updating the permanent          operation, 3-30 3              database, 3-27, 5-21      VAX PSI MAIL 5           Username, 2-12                 see PSI MAIL ?           Utilities                    VAX PSI Product License, 4             Accounting, 3-9, 4-8          3-11, 4-10>             KDA, 3-9, 4-8              VAX WAN Device Drivers,-             Security, 3-9, 4-8            2-1 3             Trace, 3-9, 4-8            VECTOR, 3-21 <           V                              address, 2-7, 3-14,A                                             3-18, 3-20, 5-2, 5-10 <           VAXcluster, 3-8, 4-7           default, 3-21, 5-109             installing VAX PSI on,     VMI$ROOT, 3-5, 4-4 ?                1-8                     VMSINSTAL.COM, 1-7, 3-1, 2             installing VAX PSI on a,      4-1, 5-1=                1-8                     VMS versions, 3-7, 4-6E  (           VAX PSI, 1-7                 X!             Access mode, 1-1, 1-61>             changing, 6-1              X.29 support, 3-8, 4-7,4             fails to load, 3-16,          4-16, 5-11;                4-14, 5-5               X25-ACCESS database,n3             fails to set up, 3-16,        4-19, 5-3 :                4-15, 5-25                configuring, 4-197             fails to start, 3-33,        defining, 5-1457                4-22, 5-5                 updating, 5-14              kits, 1-5   A                                                           Index-5                              X25-PROTOCOL database,              1-7             defining, 5-17"           X25-SERVER database, 1-7"           X25-SERVER destinations,              3-30, 5-22, 5-24                                                                                  Index-6 