           H                     DEC_TCP/IP_Services_for_OpenVMS_____________________2                     Installation and Configuration      ,                     Part Number: AA-LU49F-TE                         May 1994  >                     This manual describes the installation andH                     configuration of the DEC TCP/IP Services for OpenVMS#                     (UCX) software.   F                 _______________ Documentation Comments _______________  A                 If you have comments or suggestions for this book =                 or any of the DEC TCP/IP Services for OpenVMS >                 documents and you have access to the INTERNET,8                 mail your comments electronically to theD                 DEC TCP/IP Services for OpenVMS writing group within1                 Digital at the following address: 9                               doc_quality@lkg.mts.dec.com   F                 ______________________________________________________              C                     Revision Information:         This is a revised 9                                                   manual.   A                     Operating System:             OpenVMS VAX[TM] D                                                   Versions 5.5, 6.0,5                                                   6.1 A                                                   OpenVMS AXP[TM] C                                                   Versions 1.5, 6.1   I                     Software Version:             DEC TCP/IP Services for I                                                   OpenVMS VAX[TM] Version 5                                                   3.1 I                                                   DEC TCP/IP Services for I                                                   OpenVMS AXP[TM] Version 5                                                   3.1                    ?           The information in this document is subject to change D           without notice and should not be construed as a commitment=           by Digital Equipment Corporation. Digital Equipment C           Corporation assumes no responsibility for any errors that &           may appear in this document.  B           Possession, use, or copying of the software described inA           this publication is authorized only pursuant to a valid D           written license from Digital or an authorized sublicensor.  @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  :                        Digital Equipment Corporation 19941                               All Rights Reserved 0                                Printed in U.S.A.    ;           The following are trademarks of Digital Equipment B           Corporation:  ADVANTAGE-NETWORKS, Alpha AXP, AXP, DDCMP,D           DEC, DECnet, DECstation, DECUS, DECwindows, LAT, MicroVAX,E           OpenVMS, PATHWORKS, ULTRIX, UNIBUS, VAX, VAXBI, VAXcluster, B           VAXstation, VMS, VMScluster, VT, the Alpha AXP logo, and           the Digital logo.   3           The following are third-party trademarks:   E           HP and Hewlett-Packard are registered trademarks of Hewlett            Packard Company.  B           IBM is a registered trademarks of International Business           Machines Corporation.   :           OSF/1 is a registered trademark of Open Software           Foundation, Inc.  E           PostScript is a registered trademark of Adobe Systems, Inc.   ?           Sun, NFS, and PC-NFS are registered trademarks of Sun            Microsystems, Inc.  E           UNIX is a registered trademark of UNIX System Laboratories,            Inc.  @           All other trademarks and registered trademarks are the/           property of their respective holders.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................      v   '   1  Preparing to Install and Configure   0         1.1   Getting Ready for Installation andC               Configuration ................................    1-2 C         1.1.1     Global Pagelets and Sections .............    1-3 C         1.2   License Registration .........................    1-4 C         1.3   Installation and Configuration Checklists ....    1-4      2  Installation   C         2.1   The VMSINSTAL Procedure ......................    2-1 C         2.1.1     Conventions ..............................    2-1 C         2.1.2     Log Files ................................    2-2 C         2.1.3     Stopping .................................    2-2 C         2.1.4     If You Are Re-installing UCX .............    2-2 C         2.1.4.1     Renamed Files ..........................    2-3 C         2.1.5     Starting and Running the Procedure .......    2-3 C         2.2   Unsuccessful Installation ....................    2-6 9         2.3   Installing the Transport-Specific Shareable C               Image ........................................    2-7 C         2.3.1     Writing Your Own Transport ...............    2-8 <         2.3.2     Installing the Example Transport ShareableC                   Image ....................................    2-8 C         2.4   Next Steps ...................................   2-10                 C                                                                 iii                         3  Configuration  E           3.1   Step 1: Complete the Checklists. .............    3-2 E           3.2   Step 2: Assign the UIC. ......................    3-2 ;           3.3   Step 3: Increase the Nonpaged Dynamic Pool. E                 ..............................................    3-3 E           3.4   Step 4: Run the Configuration Procedure. .....    3-5 E           3.4.1     IVP: During Configuration ................    3-9 E           3.4.2     IVP: After Configuration .................    3-9 E           3.4.3     IVP: Errors ..............................    3-9 >           3.5   Step 5: Complete the Post-Configuration Steps.E                 ..............................................   3-11 8           3.5.1     Step 5a: Edit the System Startup andE                     Shutdown Procedures. .....................   3-11 <           3.5.2     Step 5b: Verify SYLOGIN.COM Protections.E                     ..........................................   3-11 E           3.5.3     Step 5c: Populate Relevant Databases. ....   3-12 8           3.5.4     Step 5d: Edit the DECwindows CommandE                     Procedure. ...............................   3-12 8           3.5.5     Step 5e: Refine and Complete the NFSE                     Server Configuration. ....................   3-12 8           3.5.6     Step 5f: Refine and Complete the NFSE                     Client Configuration. ....................   3-14 :           3.5.7     Step 5g: Make Available the NFS OnlineE                     Documentation. ...........................   3-14 :           3.5.8     Step 5h: Create Additional BIND ServerE                     Files. ...................................   3-15 <           3.6   Step 6: Startup or Shutdown the PWIP Driver.E                 ..............................................   3-15 :           3.7   Step 7: Configure the SRI $QIO ProgrammingE                 Interface. ...................................   3-16 E           3.8   Ongoing Steps: Tune the Network. .............   3-16        A  Examples   E           A.1   Installation .................................    A-1 E           A.2   Configuration ................................    A-4 E           A.2.1     Configuration: Client Components .........    A-4 E           A.2.2     Configuration: Routing ...................    A-9 E           A.2.3     Configuration: BIND Server ...............   A-10                iv                            B  Installed Files  I               B.1   UCX Drivers ..................................    B-1 I               B.2   Other UCX Files ..............................    B-1 I               B.3   Files Installed for PATHWORKS Systems ........    B-9   
         Index              Figures   ;               1         The DEC TCP/IP Services for OpenVMS I                         Documentation Set.........................    xii   A               1-3       Configuration Checklist: Core Environment I                         ..........................................    1-5   I               1-4       Configuration Checklist: Routing .........    1-5            Tables  I               1         Documentation Conventions ................     vi   I               2         Basic NFS Definitions ....................     xi   I               3-1       Correcting IVP Errors ....................   3-10   I               3-2       System Startup Files .....................   3-11   I               B-1       Drivers Copied to SYS$COMMON:[SYS$LDR] ...    B-1   I               B-2       Other UCX Files Installed ................    B-2   I               B-3       PATHWORKS Files ..........................    B-9                       I                                                                         v                              I         _________________________________________________________________   I                                                                   Preface       H               This manual explains the installation and configuration ofA               the DEC TCP/IP Services for OpenVMS (UCX) software.            Intended Audience   C               This manual is for OpenVMS system managers or network E               managers who install and configure networking software.            Product Licenses  E               To use the DEC TCP/IP Services for OpenVMS product, you 1               need one of two available licenses:   0               o  DEC TCP/IP Services for OpenVMS  6                  Provides all the software components.  .               o  DEC TCP/IP Client for OpenVMS  B                  Provides the same software components, excluding:  .                  -  Remote Boot Server (BOOTP)                    -  BIND Server   "                  -  NFS[TM] Server  %                  -  PC-NFS[TM] Server   B               You receive the complete documentation set with both               licenses.   D               A license is not required to use the software only forE               displaying DECwindows[TM] applications on remote hosts.   I                                                                         v                         Conventions   C           The documentation set for DEC TCP/IP Services for OpenVMS >           uses the documentation conventions shown in Table 1.  E           Table_1_Documentation_Conventions__________________________   E           Convention__Meaning________________________________________   ;           [ ]         In command syntax, indicates that the @                       enclosed values are optional. (Do not type$                       the brackets.)  E           ___________________________________________________________   @           { }         In command syntax, indicates that you must=                       specify either one, some, or all of the @                       enclosed values. (Do not type the braces.)  E           ___________________________________________________________   E           ...         In examples, indicates a missing portion, which B           or          is omitted because it is not relevant to the           .           example.           .            .   E           ___________________________________________________________   E           <>          Indicates the end of hardware-platform-specific "                       information.  E           ___________________________________________________________               THIS TYPE   Indicates:=           and         o  OpenVMS system output or user input.            THIS TYPE D                       o  Names of OpenVMS and UCX commands, options,'                          and utilities.   @                       o  Names of OpenVMS files and directories.  :                       o  Names of OpenVMS hosts and users.  A                       Example: On host CANARY, issue the UCX SHOW $                       PROXY command.  E                                              (continued on next page)        vi                   I               Table_1_(Cont.)_Documentation_Conventions__________________   I               Convention__Meaning________________________________________   C                           Example: To connect to host OSPREY, type:   0                           TELNET> CONNECT OSPREY  I               ___________________________________________________________   $               this type   Indicates:>               and         o  UNIX system output or user input.               this type D                           o  Names of UNIX commands, options, files,8                              directories, and utilities.  ;                           o  Names of UNIX hosts and users.   F                           Example: User lark on UNIX NFS Server thrushI                           exports the directory /warbler/song.bird for an 6                           OpenVMS NFS client to mount.  =                           Example: To copy a UNIX file, type:   4                           FTP> get /usr/waders/stork  /               this_type   Indicates a variable.   G                           Example: Specify the group identifier, /GIDn, 8                           on the ADD PROXY command line.  I                                                  (continued on next page)                           I                                                                       vii                    E           Table_1_(Cont.)_Documentation_Conventions__________________   E           Convention__Meaning________________________________________   B                       The following variables frequently appear inC                       command syntax and examples. They are used in 0                       the documentation to mean:  9                       host        Host name or IP address   +                       node        Node name   +                       user        User name   +                       file        File name   9                       directory   Directory specification   9                       path        UNIX or UNIX-style path /                                   specification   -                       domain      Domain name   -                       port        Port number   A                       n           Decimal number value or integer   3                       h           Hexadecimal value   E           ___________________________________________________________   B           IP          In examples, the IP addresses are fictitious-           addresses   and might not be valid.   E           ___________________________________________________________   ?           <Return>    In examples, indicates that you press the C                       Return key (shown only in examples that might '                       cause confusion).   E           ___________________________________________________________   A           <Ctrl/key>  Indicates that you simultaneously press the E           ____________Ctrl_key_and_the_illustrated_key.______________   E           ___________________________________________________________        viii                            Terminology   9               This manual uses the following terminology:   6               o  Abbreviations for the products' names  D                  -   DEC TCP/IP Services for OpenVMS is used to mean                     both:   C                     The DEC TCP/IP Services for the OpenVMS AXP[TM] ,                     Operating System product  C                     The DEC TCP/IP Services for the OpenVMS VAX[TM]e,                     Operating System product  H                  -  UCX is used to mean DEC TCP/IP Services for OpenVMS.  $               o  Software components  <                  -  Auxiliary Server is used to mean the UCX@                     implementation of the inetd function, system1                     security, and other features.t  H                  -  NFS means the UCX implementation of the Network FileE                     System (NFS) protocols, including NFS Server, NFSo;                     Client, and PC-NFS. (See also Table 2.)n  E                  -  IBM 3270TE means IBM 3270 model Terminal Emulator                      software.e  *               o  UNIX[TM] operating system  @                  UNIX refers to UNIX Version 4.3 of the BerkeleyD                  Software Distribution (BSD). The Digital ULTRIX[TM]I                  and DEC OSF/1[TM] Operating Systems are fully compatible_+                  with UNIX BSD Version 4.3.   !               o  Networking termsh  D                  -  Host and node both mean a system connected to an                     internet.r  C                  -  The term Internet means the network, as defined B                     by RFC 1208, consisting of large networks thatE                     use the TCP/IP protocol suite; provides universal H                     connectivity, reaching the Defense Advanced ProjectsE                     Research Agency (DARPA) Internet, MILNET, NSFnet, E                     CREN, and many worldwide universities, government G                     research labs, military installations, and business                       enterprises.  I                                                                        ix                    E                 The term internet means interconnected networks using A                 the TCP/IP protocols, functioning as one, virtualt                 network.  A              -  A VAXcluster[TM] system is made up of all VAX[TM]o                 systems.  @                 A VMScluster[TM] system can be made up of eitherC                 all AXP[TM] systems or a mix of VAX systems and AXPr                 systems.  *           Table 2 defines basic NFS terms.                                                                       xt    i              I               Table_2_Basic_NFS_Definitions______________________________i  I               Term__________Definition___________________________________   G               File system   Top-level directory (called the Master FileoG                             Directory (MFD) in OpenVMS file systems andcE                             the root in UNIX-style file systems), its I                             lower-level directories, and all the files inc.                             those directories.  E               Container     File system on an OpenVMS host that has a I               file system   UNIX-style directory structure and UNIX-style.<                             file attributes. Created by UCX.  :               UNIX-style    Same as container file system.               file systemD  A               OpenVMS file  File system with an OpenVMS directoryMB               system        structure and OpenVMS file attributes.  B               UNIX file     File system on a UNIX host with a UNIXI               system        directory structure and UNIX file attributes.   E               Proxy         Record in the Proxy Database that gives a I                             remote user access to local file systems or anE                             local user access to remote file systems.s  G               Disk          Physical device, or volume, on which a file +                             system resides.   G               Binding       Process that makes accessible to NFS Clientm"                             users:  ,                             o  OpenVMS disks  F                             o  The OpenVMS file system on a bound disk  5                             o  Container file systemsp  C               Exporting     Adding a file system name to the Export F                             Database, thus allowing an NFS Client user5                             to mount the file system.   F               Mounting      Process that makes physically remote files:                             available to NFS Client users.  ?                             Gives files a UNIX-style path name.o  C                             If the client and server are running on A                             different operating systems, mountingiG                             resolves the differences between their filel$                             systems.  H               Mount point   Directory tree point on the host running NFSH                             Server to be the Master File Directory (MFD)I                             of the NFS Client's mounted disk.          xi.I               ___________________________________________________________. .                      Associated Documents  C           You might find the following TCP/IP documentation useful:.  B           o  The DEC TCP/IP Services for OpenVMS Documentation Set              (see Figure 1)-  D           o  Internetworking with TCP/IP: Principles, Protocols, andC              Architecture, by Douglas Comer (order number ER-TCPIP-               TM-001)  A           o  Internal users only: Requests for Comment (RFCs) arer-              available in the following area:   1              decwrl::"/pub/net/info/etc/rfcn.txt"                                                                  xii                          I                                                                         1 I         _________________________________________________________________   H                                       Preparing to Install and Configure    H               The DEC TCP/IP Services for OpenVMS (UCX) installation and4               configuration consists of these tasks:  B               1. Checking out requirements and pre-requisites (see                  Section 1.1).  D               2. Gathering and recording the information you need to=                  install and configure UCX (see Section 1.3).   F               3. Running the installation procedure (see Chapter 2 and                  Appendix A)..  G               4. Running the configuration procedure (see Chapter 3 ands                  Appendix A).                                             I                                   Preparing to Install and Configure  1-1d                   8     1.1 Getting Ready for Installation and Configuration  @           Before you begin the installation and configuration ofA           the UCX software, ensure that your system meets all the B           requirements and that you have the information needed to1           answer the prompts. Follow these steps:d  %           1. Back up the system disk..  @              Digital recommends that you do a system disk backup,              before installing any software.  C              Use the backup procedures that are established at yourpB              site. For details on performing a system disk backup,B              see the section on the Backup Utility in the "OpenVMS'              System Management Subkit."   :           2. Check that you have the privileges to run the<              installation, configuration and IVP procedures.  @              Use the checklists to read about and check off each+              requirement (see Section 1.3).h  @           3. Ensure that your system meets the requirements for:                o  Software                o  Disk space                o  Quota   @              o  Memory for the BIND Server software (if you will                 configure it)T  3              o  Global pagelets and global sectionse                 o  Time needed for:  >                 -  Installation procedure - about five minutes  =                 -  Configuration procedure - about 15 minutes   =           Use the checklists to read about and check off each.(           requirement (see Section 1.3).  D           Figure 1-1 lists the requirements for disk space and quota           requirements.   *     1-2 Preparing to Install and Configure l  F              *         1.1.1 Global Pagelets and Sections  B               To check or change the number of global pagelets and+               sections, follow these steps:   I               1. Issue WRITE commands with the F$GETSYI lexical functions E                  to check the number of available global pagelets ande!                  global sections:   =                  $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")                   1234r=                  $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS").                  189  I               2. Increase the global pagelets and global sections. FollowR                  these steps:   2                  a. Edit SYS$SYSTEM:MODPARAMS.DAT.  E                     Add statements that increase the values of SYSGENeB                     parameters GBLPAGES and GBLSECTIONS (see GuideE                     to Setting Up an OpenVMS System or OpenVMS System (                     Generation Utility).  9                  b. Invoke the AUTOGEN command procedure.$  &                  c. Reboot the system.                                    I                                   Preparing to Install and Configure  1-3. .  .                   1.2 License Registration  A           Before you install on a newly licensed node or cluster, E           first register a License Product Authorization Key (License_E           PAK) using the License Management Facility (LMF). Without a 1           PAK, you can use only these components:   1           o  DECwindows TCP/IP Transport softwareo  '           o  PATHWORKS IP (PWIP) DriverE  D           The PAK might be shipped along with the kit if you orderedB           the license and media together. Otherwise, it is shippedB           separately to a location based on your license order. IfB           you are installing UCX as an update on a node or cluster>           already licensed for this software, you have already>           completed the License PAK registration requirements.  B           If you are installing pre-requisite or optional software?           along with UCX, review the PAK status and install the C           PAKs for any prerequisite or optional software before you            install UCX.  4           To register a license, follow these steps:  <           1. Log in to the system manager's account, SYSTEM.  +           2. Do one of the following steps:h  E              o  Run SYS$UPDATE:VMSLICENSE.COM and enter the data from !                 your License PAK.o  E              o  At the DCL prompt, issue the LICENSE REGISTER commandcB                 with the appropriate qualifiers that correspond to(                 License PAK information.  ?              o  To run UCX on multiple cluster nodes, perform a 0                 license load on the those nodes.  E           For complete information about LMF, see the OpenVMS Licenseo$           Management Utility Manual.  1     1.3 Installation and Configuration Checklists_  =           Before you start the installation and configurationa=           procedures, use the following checklists to record:v  <           o  Requirements for installation and configuration  A           o  Individual software components you want to configure_  *     1-4 Preparing to Install and Configure n  ,              F               o  Information you need to answer installation questions  F               o  Information you need to answer installation questions  G               o  Information you need to answer configuration questions   C               Figure 1-2 shows you the questions you need to answer E               to configure the OpenVMS system's internet interface or 7               interfaces. Record your information here.   H               Fill out the information you need for the core environment,               configuration. Use Figure 1-3.  B               Figure 1-4 shows the options for the dynamic routing&               software you can select.  F               Use Figure 1-5 to record the information you need to run               the IVP.                                                      I                                   Preparing to Install and Configure  1-5                          I                                                                         2 I         _________________________________________________________________   H                                                             Installation    D               The DEC TCP/IP Services for OpenVMS (UCX) installationI               copies the distribution files to the appropriate directory.e  I               Appendix B lists the names of the files that are installed._  #         2.1 The VMSINSTAL Procedure   @               VMSINSTAL, an OpenVMS layered product installation:               procedure, is an interactive procedure that:  :               o  Creates directories for the new software.  /               o  Copies the distribution files.   :               o  Prints and/or displays the Release Notes.  =               o  Copies the Release Notes file into SYS$HELP.                  o  Checks that:   >                  -  You are logged in to a privileged account.  ;                  -  Quotas for installation are sufficient.   -                  -  Users are all logged out.S  >               The UCX distribution media is either the OpenVMSF               Consolidated Software Distribution CD, a TK50 cartridge,!               or a magnetic tape.            2.1.1 Conventions   C               At the end of each question or prompt, either a colon G               (:) or a question mark (?) appears. Respond in one of thex               following ways:f  B               o  Type your response immediately after the colon or0                  question mark and press Return.  H               o  Press Return to choose a default value. Default values,I                  if they exist, appear in brackets ([ ]) after questions;   I                                                         Installation  2-1                    C           o  Type a question mark (?) to get help after a question. 7              After the help text, the question repeats.        2.1.2 Log Filest  D           To create a log of the VMSINSTAL session, use one of these           methods:  2           o  Run VMSINSTAL at a hardcopy terminal.  D           o  Before beginning the installation, log in a second time               to the same system:                $ SET HOST 0/LOGn  D              Run the installation at this second process. The system:              creates a log file in your working directory.       2.1.3 Stopping  =           To stop the installation at any time, press Ctrl/Y.a  E           The installation procedure deletes all the files created up "           to that point and exits.  &     2.1.4 If You Are Re-installing UCX  A           If another version of UCX exists on your system, follow_           these steps:  "           1. Shut down UCX. Issue:  '              $@SYS$MANAGER:UCX$SHUTDOWNs             2. Run VMSINSTAL.h  A           3. If UCX is active on other hosts of a cluster, do not_D              answer YES to the prompt that asks if you want to purgeD              the old version of UCX. You will need to manually purge              later.   ?              These directories contain previous versions of UCX_              files:_                   SYS$HELP                 SYS$LIBRARY                  SYS$MANAGER (                 SYS$COMMON:[SYSTEST.UCX]0                 SYS$COMMON:[SYSHLP.EXAMPLES.UCX]%                 SYS$SPECIFIC:[SYSEXE]_#                 SYS$COMMON:[SYSEXE]        2-2 Installation m  l                                   SYS$TEST  C               4. Re-configure all the application software that wast                  configured.  $               5. Reboot your system.           2.1.4.1 Renamed Fileso  D               During re-installation, the procedure checks to see ifB               old versions of the UCX$LPD_STARTUP.COM and UCX$LPD_D               SHUTDOWN.COM files exist. If so, the procedure renames               them.m  I               ___________________________________________________________pI               Old_Name________________New_Name___________________________i  9               UCX$LPD_STARTUP.COM     UCX$LPD_STARTUP.OLDm  I               UCX$LPD_SHUTDOWN.COM____UCX$LPD_SHUTDOWN.OLD_______________e  C               After the installation, edit the new files to add the C               necessary user printer queue information from the oldn               files.  0         2.1.5 Starting and Running the Procedure  G               Follow these steps to install the UCX software (using thea'               console is not required):   1               1. Ask users to log off the system.   :               2. Shut off the TCP/IP DECwindows Transport.  H                  (One method: Comment out the DECwindows startup commandF                  in your system startup file and restart your system.)  .               3. Log in to the SYSTEM account.  9               4. Set the default directory to SYS$UPDATE.   >               5. Start VMSINSTAL in one of the following ways:  I         _________________________________________________________________   3         Consolidated Distribution compact disc (CD)k  M               $ @VMSINSTAL UCX031 disc-drive:[ALPHA_UCX031.KITS] OPTIONS N <>   G               $ @VMSINSTAL UCX031 disc-drive:[UCX031.KITS] OPTIONS N <>   I                                                         Installation  2-3                               where:  C           disc-drive  Drive where the CD with the UCX save sets arel                       mounted.  C           OPTIONS N   Prompts you about displaying and printing the $                       Release Notes.  E     _________________________________________________________________t  +     TK50 cartridge or 9-track magnetic tapeo  0           $ @VMSINSTAL UCX031 ddcu: OPTIONS N <>             where:  ?           ddcu:       Device where you mounted the distribution ,                       media. The fields are:  &                       dd - device name)                       c - controller name %                       u - unit numbery  C           OPTIONS N   Prompts you about displaying and printing the $                       Release Notes.  E     _________________________________________________________________e                                         2-4 Installation m  _              (               6. Read the Release Notes.                    You can:o  $                  o  Read them online  F                  o  Print them, stop VMSINSTAL, read them, and restart3                     the procedure without OPTIONS Ne  I                  o  Read them after the installation. They are copied to:d  1                     SYS$HELP:UCX031.RELEASE_NOTES   &               7. Select purge options.  G                  If UCX is active on your system, either stand-alone orNE                  in a cluster, do not answer YES to purging. You will .                  need to manually purge later.  B               8. Answer the product authorization key (PAK) query.  G                  You can install the PAK either during the installationM/                  procedure or after you run it.M  F                  If you plan to use UCX only for displaying DECwindowsF                  applications using TCP/IP on remote hosts, you do not'                  need to install a PAK.                                     I                                                         Installation  2-5e s  s              !     2.2 Unsuccessful Installationc  B           Installation failure produces an error message. An error0           during installation can occur because:  7           o  The operating system version is incorrect.   <           o  The prerequisite software version is incorrect.  #           o  Quotas are inadequate.   +           o  Process quotas are inadequate.   :           o  The OpenVMS Help library is currently in use.  )           If VMSINSTAL reports a failure:m  3           1. Review the installation prerequisites.n  >           2. Check the error messages to identify the problem.  %           3. Run the procedure again.                                                    2-6 Installation r  s              =         2.3 Installing the Transport-Specific Shareable Imageo  D               To use the DECwindows TCP/IP transport with DEC TCP/IPH               Services for OpenVMS, install the transport-specific image8               so that the Transport Layer can access it.  F                 ________________________ Note ________________________  ;                 Do not redefine the logical name SYS$SHARE.   F                 ______________________________________________________  !               Follow these steps:   6               1. Log in to the system manager account.  B               2. Copy the image to the SYS$SHARE directory. Issue:  J                  $ COPY DECW_TRANSPORT_transport.EXE SYS$SHARE: /PROT=W:RE  B               3. Edit the the system startup procedure to include:  F                  $ INSTALL CREATE SYS$SHARE:DECW_TRANSPORT_transport -8                  _$ /OPEN /SHARED /HEADER_RES /PROTECTED  D                  If you write your own transport, see Section 2.3.1.  D               4. Copy SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE                  to *.COM.  I               5. Modify the DECW$SERVER_TRANSPORTS symbol to include youra(                  transport, for example:  H                  $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP,ROMPER"  ;                  The server uses DECW$SERVER_TRANSPORTS to:   9                  o  Determine which transports to attach.   =                  o  Determine which transports to initialize._  I                  o  Call the DECW$XPORT_ATTACH_TRANSPORT routine for eacho7                     transport identified by the symbol.S  F               6. Manually execute the install command you added to the*                  system startup procedure.  $               7. Restart DECwindows:  (                  $ @DECW$STARTUP RESTART  E               8. Customize security. See the OpenVMs DECwindows MOTIF                   User's Guide.  I                                                         Installation  2-7d    e              A              Use the transport name transport (instead of TCPIP).n  E           9. Create a DECterm [TM] window on your workstation. Issue:   I              $ SET DISPLAY /CREATE /NODE="your_node" /TRANSPORT=transport   D              your_node represents the node name of your workstation.  D           Now you can run a DECwindows application from your DECterm=           window with the application using your transport to #           establish the connection.t  $     2.3.1 Writing Your Own Transport  *           If you write your own transport:  C           o  Do not include the transport name supplied with UCX ine/              the DECW$SERVER_TRANSPORTS symbol.   E              (The  DEC TCP/IP Services for OpenVMS transport attacheswA              to Port 6000 and would conflict with your own TCP/IP               transport.)  ;           o  Follow the X11 Protocol convention for TCP/IP:   5              -  Server number 0 listens on Port 6000.   5              -  Server number 1 listens on Port 6001.e  5              -  Server number n listens on Port 600n.i  :     2.3.2 Installing the Example Transport Shareable Image  :           To use the example transport, do not include the8           TCP/IP transport name supplied with UCX in theA           DECW$SERVER_TRANSPORTS symbol. (This transport attachesoE           to Port 6000 and would conflict with the example transport.            )o             Follow these steps:i  2           1. Log in to the system manager account.  C           2. Copy the example transport to the SYS$SHARE directory:e  S              $  COPY DECW$EXAMPLES:DECW$TRANSPORT_EXAMPLE.EXE SYS$SHARE: /PROT=W:RE   D           3. Add the following line to the system startup procedure:  A              $  INSTALL CREATE SYS$SHARE:DECW$TRANSPORT_EXAMPLE - 5              _$  /OPEN /SHARED /HEADER_RES /PROTECTEDq       2-8 Installation d  o              G               4. Copy SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE to                   *.COM. .b  H               5. Modify the DECW$SERVER_TRANSPORTS symbol to include the0                  example transport, for example:  D                  $  DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,EXAMPLE"  F               6. Manually execute the install command you added to the*                  system startup procedure.  $               7. Restart DECwindows:  (                  $ @DECW$STARTUP RESTART  E               8. Customize security. See the OpenVMS DECwindows MOTIFE                  User's Guide.  A                  Use the transport name EXAMPLE instead of TCPIP.l  D               9. Create a DECterm window on your workstation. Issue:  K                  $ SET DISPLAY /CREATE /NODE="your_node" /TRANSPORT=EXAMPLEe  H               Using the example transport to establish a connection, you=               can use DECwindows to run a TCP/IP application.e                                      I                                                         Installation  2-9e                        2.4 Next Steps  ?           1. To continue using the system manager's account and B              restore the process symbol tables, log out and log in@              again. (VMSINSTAL deletes or changes entries in the<              process symbol tables during the installation.)  =           2. Run the configuration procedure (see Chapter 3).g                                                                               2-10 Installationn                         I                                                                         3 I         _________________________________________________________________   H                                                            Configuration    H               To prepare for and run the DEC TCP/IP Services for OpenVMS=               configuration procedure, following these steps:   I               1. Complete the configuration checklists (see Section 1.3).   0               2. Selecte UICs (see Section 3.2).  <               3. Increase the size of the nonpaged pool (see                  Section 3.3).  =               4. Run the configuration command procedure (seea                  Section 3.4).  E               Immediately after you exit the procedure, perform a few D               post-configuration tasks (see Section 3.5) to make theC               software available to local and remote network users.A                                        I                                                        Configuration  3-1, s  t              (     3.1 Step 1: Complete the Checklists.  ?           Gather the information you need for the configurationA?           procedure. Complete the configuration checklists (seen           Section 1.3), which:  .           o  List all the information you need  <           o  Provide space for you to record the information       3.2 Step 2: Assign the UIC.   D           Accounts for the services you will configure might already           exist. If they:n  A           o  Exist, the configuration procedure uses the existingt2              group User Identification Code (UIC).  ?           o  Do not exist, the default UIC group number for thet-              service accounts is 375 (octal).o  D           o  If this is a first-time configuration but the procedureE              detects that 375 is in use, it prompts you for a new UICa              group number.  C              -  Before you assign a new group number, check that itoA                 is not already in use. Issue (type the brackets):e  *                 $ RUN SYS$SYSTEM:AUTHORIZE6                 UAF> SHOW /BRIEF [your_group_number,*]F                 UAF> SHOW /IDENTIFIER /VALUE=UIC:[your_group_number,*]  E              -  To specify your own UIC group number instead of using A                 the default, assign the value TRUE to the logicaleC                 name UCX$ASK_GROUP_UIC. The configuration procedurec1                 then prompts you for a group UIC.f                       3-2 Configurationh V                 7         3.3 Step 3: Increase the Nonpaged Dynamic Pool.   G               Add at least 342,000 bytes of nonpaged dynamic pool. This 2               is the default maximum size for UCX.  !               Follow these steps:   .               1. Log in to the SYSTEM account.  F               2. Use the OpenVMS System Generation Utility (SYSGEN) by%                  running AUTOGEN.COM.   =                  For information about running AUTOGEN, type:   +                  $ @SYS$UPDATE:AUTOGEN HELPo  E               3. Identify the amount of additional nonpaged pool youre,                  system requires. Calculate:  W                  nonpaged pool = socket*1280+dbuf*1792+cbuf*256+mtusers*700+mrusers*700                     where  I                  ________________________________________________________wI                  Variable___Means________________________________________   G                  socket     Maximum number of sockets. (A socket system H                             call creates an endpoint for communication.)  ;                  dbuf       Maximum number of data buffers..  >                  cbuf       Maximum number of control buffers.  ;                  mtusers    Maximum number of TELNET users.   I                  mrusers____Maximum_number_of_Remote_Login_users.________d  F                  For more information, see the DEC TCP/IP Services for+                  OpenVMS Management manual.   (               4. Run AUTOGEN.COM. Issue:  Q                  $ @SYS$UPDATE:AUTOGEN [start-phase] [end-phase] [execution-type]o  H               5. Edit SYS$SYSTEM:MODPARAMS.DAT to modify, as calculated,6                  the NPAGEDYN and NPAGEVIR parameters.  H                  NPAGEVIR defines the maximum size to which NPAGEDYN can                  be increased.  G                  Unless you are sure that NPAGEVIR is large enough, add 4                  the same amount to both parameters.  I                                                        Configuration  3-3? o  t                            Example:   .              ! Add some nonpaged pool for UCX.              !               ADD_NPAGEDYN=342000               ADD_NPAGEVIR=342000  E           6. If you increase any of these values, increase the host'sr&              nonpaged pool size again.             7. Exit AUTOGEN.             8. Reboot.                                                                     3-4 Configurationo t  i              4         3.4 Step 4: Run the Configuration Procedure.  !               Follow these steps:p  I               1. Log in to the SYSTEM account or another account with the &                  following privileges:                       SYSPRV                     SYSNAM                     OPER                     DETACH                     BYPASS                     CMKRNL                     ALTPRI  E               2. Decide on the appropriate command syntax (Figure 3-1X4                  shows the options you can specify).                    where                                                    I                                                        Configuration  3-5r n               E              ________________________________________________________rE              Parameter_____Means_____________________________________   ?              ALL           Configures every component and every "                            service  ?              CLIENT        Configures all client components and]+                            related software   ?              SERVER        Configures all server components and +                            related software   D              WORKSTATION   Configures the BIND Resolver, the domain,D                            dynamic routing, the internet interfaces,E                            the time zone, Remote Login, Remote Shell,hD                            Remote Executive, FTP Client, FTP Server,=                            TELNET Client, TELNET Server, SMTPi  E              MINIMUM       Configures the internet interfaces, Remote_@                            Login, FTP Client, FTP Server, TELENT0                            Client, TELENT Server  @              ENABLE        Enables all the configured components  A              DISABLE       Disables all the configured componentsN  =              CLUSTER       Configures all selected componentst&                            clusterwide  B                            Exception: The only components that you@                            cannot configure clusterwide are BIND+                            Server and SMTP.   @                            If you configure at least one clusterA                            interface, the procedure automatically E              ______________enables_IP_forwarding.____________________   C              ________________________ Note ________________________   <              The procedure performs 2 levels of enabling and?              disabling: clusterwide and single node (except fordC              BIND Server and SMTP, which are configured and enabledi!              node-specific only).   ?              During a re-configuration, for every component you_=              select to configure, the menus show you if it is ?              currently enabled or disabled. This status matchesTA              the last enable or disable selection you made. If itKB              was clusterwide and now you are doing a node-specificA              configuration, the menu displays "enabled." However,:@              the prompts report that the component is "disabled"       3-6 Configuration     n              B                 and ask if you want to enable it. The component isE                 enabled at the clusterwide level, but not at the node_                 level.  F                 ______________________________________________________  6                  Example: The following example shows:  H                  o  The meaning of the prompts that result from 2 levelsE                     - clusterwide and node-specific - of enabling andcE                     disabling of components done by the configuration                      procedure.  A                  o  The flow of the menus. For example, after you C                     configure a client component, a prompt asks you_D                     if you want to configure that component's server                     software.   I                  ________________________________________________________n  R                   TCP/IP Services for OpenVMS CLIENT Components Configuration Menu  (                   Configuration options:  /                    1 - FTP              Enabled /                    2 - LPR/LPD          Enabledy/                    3 - NFS Client       EnabledU/                    4 - REXEC and RSH    Enabledu/                    5 - RLOGIN           Enabled /                    6 - SMTP             Enabled /                    7 - SNMP             Enabled./                    8 - TELNET           Enabledg  .                    A - Configure options 1 - 8                     E - Exit menu  7                  Enter configuration option: 1 <Return>s  )                  FTP CLIENT Configuratione  '                  Service is not enabledl  3                   FTP CLIENT configuration options:   2                    1 - Enable service on this node  4                    E - Exit FTP_CLIENT configuration  5                  Enter configuration option: <Return>   I                                                        Configuration  3-7  u  s              +              The FTP SERVER is not enabled.e  B              * Do you want to configure FTP SERVER [NO] ? <Return>  B              Example: The following command configures all the UCX*              software and then enables it.  1              $ @SYS$MANAGER:UCX$CONFIG ALL ENABLEa  E              ________________________________________________________O  !           3. Start the procedure.s  C              Depending on the exact command line you issue to start A              the procedure, it either automatically completes (nosE              questions for you to answer) and exits, or it displays a               menu.  E              For example, with no parameters on the command line, and B              with at least one interface configured, the procedure$              displays the main menu:  ?              With no configured interfaces, the procedure firsttD              prompts you to configure an interface and then displaysE              the main menu. Use the interface configuration checklist_@              to first record and then input the information (see6              Figure 1-2 ) for the interface checklist.  /           4. Type a selection and press Return.   D              If a default value is available, it appears in brackets              ([ ]).   /              To select a default, press Return.   D              If you started the configuration procedure with the ALLC              parameter, or if you now specify 1 - Core environment,eD              the procedure displays the Core Configuration Menu (see              Figure 3-3).   ;              The exact look of each sub-menu depends on the D              selections you make and, if you are re-installing, yourE              current configuration. Figure 3-4 shows how the menu for .              the server components might look.  A              Figure 3-5 shows 2 ways that the menu for the clientt#              components might look.D  @              To review and record your answers for the questionsD              asked during the configuration for dynamic routing, see              Figure 1-4.       3-8 Configuration                    E               5. Run the Internet Installation Verification ProcedureP                  (IVP).i  G                  Before you run the IVP be sure that UCX is started and F                  you have SYSPRV, OPER, NETMBX, and TMPMBX privileges.E                  You can also use SETPRV to set the other privileges.C  6                  The IVP performs the following tests:  B                  o  Verifies that the lower-layer software and theF                     Portmapper Service are correctly installed, if you?                     loaded the Product Authorization Key (PAK).   @                  o  Verifies that UCX is correctly installed forE                     DECwindows to display TCP/IP applications, if you )                     did not load the PAK.r  I                  o  Transfers device-socket packets, continuously varyingmG                     in size, between a sender and a receiver to comparei?                     the received packets with the sent packets.   G                  o  Tests the Portmapper Service with a pair of client-nE                     server programs. It reports the amount of time it 7                     took to run the test to SYS$OUTPUT.h  '         3.4.1 IVP: During ConfigurationS  F               Start the UCX software. Then select Option 6 at the main1               configuration menu (see Figure 3-6.   &         3.4.2 IVP: After Configuration  E               To run the IVP any time after exiting the configuration/               procedure, issue:m  !               $ @SYS$TEST:UCX$IVP            3.4.3 IVP: Errorst  C               All IVP errors are fatal. They ues the same format as0               system messages:                  %UCX-E-IDENT, text  &               Possible error messages:  4                  Internet (UCX$DEVICE) Device Assign%                  Local Host Not FoundR6                  Local Host Name Not in Hosts Database5                  Create and Bind Sender Device-Socketa7                  Create and Bind Receiver Device-Socket   I                                                        Configuration  3-9  m                 %              Connect on Device-Socket $              Listen on Device-Socket$              Accept on Device-Socket!              Sender Device-Socket #              Receiver Device-Socket               Invalid LengthS              Data Corruption+              Send Shutdown on Device-SocketR.              Receive Shutdown on Device-Socket'              Close Sender Device-SocketA)              Close Receiver Device-Socket *              Deassign Sender Device-Socket,              Deassign Receiver Device-Socket  E           Table 3-1 shows the possible causes for IVP errors and what /           you can do to try to fix the problem.O  E           Table_3-1_Correcting_IVP_Errors____________________________   E           Problem_________________Corrective_Action__________________   @           Network configuration   Shut down the UCX software andD           is incorrect.           rerun the configuration procedure.  A           Startup fails.          Check the SYSGEN parameters ando=                                   increase them if necessary.   <                                   Shut down and restart UCX.  <           The installation kit    Request a replacement kit.           is defective.m  ?           None of these actions   Submit a Software Performance /           corrects the problem.   Report (SPR).   A           The IVP fails because   Without a PAK, you can use only A           the PAK is missing.     the DECwindows TCP/IP Transporte+                                   software.e  <                                   If you want to run all theE           ________________________software,_purchase_a_UCX_PAK.______t             3-10 Configuration                   :         3.5 Step 5: Complete the Post-Configuration Steps.  G               After the configuration procedure, do the tasks described >               in the following sections, if applicable to your               environment.  G         3.5.1 Step 5a: Edit the System Startup and Shutdown Procedures.   E               For automatic startup of UCX, add the following line to_C               your system startup procedure, after the command lineiF               that starts the DECnet/OSI startup procedure (if you run               DECnet/OSI):  &               @SYS$MANAGER:UCX$STARTUP  I               Table 3-2 lists the names of the startup procedures for theo-               platforms on which UCX can run.S  I               Table_3-2_System_Startup_Files_____________________________   I               Platform:_______________File_to_Edit_______________________a  C               OpenVMS AXP Version     SYS$MANAGER:SYSTARTUP_VMS.COMe               1.5x  C               OpenVMS AXP Version     SYS$MANAGER:SYSTARTUP_VMS.COMs               6.1t  B               OpenVMS VAX Version     SYS$MANAGER:SYSTARTUP_V5.COM               5.5   C               OpenVMS VAX Version     SYS$MANAGER:SYSTARTUP_VMS.COM I               6.0,_6.1___________________________________________________o  I               For automatic shutdown of UCX upon system shutdown, add theo/               following line to SYSHUTDOWN.COM:o  '               @SYS$MANAGER:UCX$SHUTDOWNt  6         3.5.2 Step 5b: Verify SYLOGIN.COM Protections.  E               For the services to start after you log in, the OpenVMS I               systemwide log-in procedure SYS$MANAGER:SYLOGIN.COM must beo2               world-readable and world-executable.  6               To display its current privileges, type:  =               $ DIRECTORY SYS$MANAGER:SYLOGIN.COM /PROTECTIONU  I                                                       Configuration  3-11                    -           If protections are not W:RE, issue:   9           $ SET PROTECTION=(W:RE) SYS$MANAGER:SYLOGIN.COMt  /     3.5.3 Step 5c: Populate Relevant Databases.I  >           Add entries to the databases related to the servicesA           you configured (see the DEC TCP/IP Services for OpenVMSyD           Management and  DEC TCP/IP Services for OpenVMS Management%           Command Reference manuals).   ?           If UNIX hosts exist on your network, you can copy the 1           information in the following databases:              o  /etc/hostsu             o  /etc/networks             o  /etc/passwd             o  /etc/bootptab  >           For details, see the DEC TCP/IP Services for OpenVMSC           Management manual or the  DEC TCP/IP Services for OpenVMS .           Management Command Reference manual.  9     3.5.4 Step 5d: Edit the DECwindows Command Procedure.o             To useD           DECwindows for TCP/IP applications, add the following lineB           to the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM command           procedure:  :           $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"  @           If DECnet or DECnet/OSI runs on the same system, start           DECnet first.   D     3.5.5 Step 5e: Refine and Complete the NFS Server Configuration.  E           To make the Network File System (NFS) available to users on @           remote systems running NFS Client, follow these steps:  A           1. If you are unfamiliar with the management of the NFSd?              Server software, or this is the first time you areeC              running it on OpenVMS, see the DEC TCP/IP Services for_B              OpenVMS Concepts and Planning and DEC TCP/IP Services>              for OpenVMS Management manuals for conceptual and               management details.             2. Bind disk devices.t       3-12 Configuration i  )              C                  The following command illustrates binding the disk -                  devices to UNIX-style names:   .                  UCX> BIND DISK$USER3: "/usr3"  G                  You can add this command to the UCX$NFS_SET_FS commandu                  procedure.   %               3. Export file systems.P  =                  The following command illustrates exporting:   =                  UCX> ADD EXPORT "/usr3" /HOST="unix.xyz.com"Y                 4. Add proxies.n  4                  The following commands add proxies:  K                  UCX> ADD PROXY JONES /HOST="unix.xyz.com" /UID=271 /GID=15nB                  UCX> ADD PROXY UCX$NOBODY /HOST=* /UID=-2 /GID=-2@                  UCX> ADD PROXY UCX$NOBODY /HOST=* /UID=0 /GID=1  "               5. Monitor mounting.  F                  Watch the OPCOM Messages to confirm mounting (see the$                  following example:)  (                  $ REPLY /ENABLE=NETWORK0                  unix# mount openvms:/usr3 /usr3  2               6. Configure container file systems.  B                  The following commands configure a container file                  system:  =                  UCX> CREATE CONTAINER DISK$USER3:[CONTAINER] 9                  UCX> BIND DISK$USER3:[CONTAINER] "/cont" =                  UCX> ADD EXPORT "/cont" /HOST="unix.xyz.com"   %               7. Modify root mapping.   D                  The following command changes default root mapping:  +                  UCX> SET NFS /UID=0 /GID=1e  I                                                       Configuration  3-13w                   D     3.5.6 Step 5f: Refine and Complete the NFS Client Configuration.  9           To request the NFS Service, follow these steps:   A           1. If you are unfamiliar with the management of the NFS ?              Client software, or this is the first time you areeC              running it on OpenVMS, see the DEC TCP/IP Services forcB              OpenVMS Concepts and Planning and DEC TCP/IP Services>              for OpenVMS Management manuals for conceptual and               management details.             2. Add proxies.   C              The necessary proxies may already exist. To check, use $              the following commands:  G              UCX> ADD PROXY JONES /HOST="unix.xyz.com" /UID=271 /GID=15p>              UCX> ADD PROXY UCX$NOBODY /HOST=* /UID=-2 /GID=-2             3. Mount devices.l  D              The following command illustrates mounting the devices:  P              UCX> MOUNT DNFC10: /HOST="unix.xyz.com" /PATH="/usr/exports/public"  ?              You can add this to your system startup procedure.e             4. Access files.  A              The following command illustrates accessing files ase$              though they were local:  ,              $ TYPE DNFC10:[JONES]MYFILE.TXT  ?     3.5.7 Step 5g: Make Available the NFS Online Documentation.   >           For remote NFS Client users, UCX includes online NFSB           documentation. It describes how to remotely access filesB           that reside on a system running UCX and offering the NFS           Service.  C           To make this documentation available to remote NFS users:n  <           1. Copy the SYS$HELP:UCX$VMS_FILES.DOC to a public              directory.   :           2. Rename UCX$VMS_FILES.DOC to a UNIX file name.  A           3. Export the public directory so that remote users can               mount it.       3-14 Configuration                   ;         3.5.8 Step 5h: Create Additional BIND Server Files.   ?               If you selected to configure the BIND Server, the H               configuration procedure creates two files for it, NAMED.CA               and NAMED.LOCAL.  I               o  Depending on the type of server functions your host will_H                  perform, you might need to create additional files (seeF                  the DEC TCP/IP Services for OpenVMS Management manual                  for details.d  A               o  If you have not yet designed your BIND namespaceiC                  hierarchy, see the DEC TCP/IP Services for OpenVMSi=                  Concepts and Planning manual for guidelines.i  C               Example: Configuring as the primary server for domaini!               RHEA.LAB.UBIRD.EDU.   +               UCX> SET CONFIGURATION BIND - 8               _UCX> /PRIMARY=(DOMAIN:RHEA.LAB.UBIRD.EDU)  C               Example: Configuring as a secondary server for domaineE               JACANA.LAB.UBIRD.EDU and names the boot file JACANA.DB.i  :               Omitting the file name would default to file"               JACANA.LAB.UBIRD.DB.  +               UCX> SET CONFIGURATION BIND - W               _UCX> /SECONDARY=(DOMAIN:JACANA.LAB.UBIRD.EDU,FILE:JACANA.DB,HOST=MARSHY)   @               Example: Configuring as a secondary server for theD               reverse lookup domain for addresses that have the form               of 192.0.*.*.p  F               The boot file name defaults to 0_192_IN-ADDR_ARPA.DB and=               the host copies this file from the host WEBBED.m  +               UCX> SET CONFIGURATION BIND - F               _UCX> /SECONDARY=(DOMAIN=0.192.IN-ADDR.ARPA,HOST=WEBBED)  8         3.6 Step 6: Startup or Shutdown the PWIP Driver.  G               For PATHWORKS users to work with TCP/IP applications, UCXa/               includes the PWIP Driver and ACP.e  D               The PWIP Driver does not automatically start at system6               startup. To start the PWIP Driver, type:  1               $ @SYS$MANAGER:UCX$PWIP_STARTUP.COM   I                                                       Configuration  3-15e                   -           To shut down the PWIP Driver, type:   .           $ @SYS$MANAGER:UCX$PWIP_SHUTDOWN.COM  <           For information about PATHWORKS, see the PATHWORKS           documentation.A           For a list of PATHWORKS files that the UCX installationS,           procedure installs, see Table B-3.  =     3.7 Step 7: Configure the SRI $QIO Programming Interface.o  B           If you run or develop applications that use the Standard<           Research Institute (SRI) QIO API, load it with the           following command:  0           $ @SYS$MANAGER:UCX$LOAD_INETDRIVER.COM  (     3.8 Ongoing Steps: Tune the Network.  <           To improve network performance, modify, as needed:             o  UCX parametersi  7           o  The SYSGEN parameters CHANNELCNT and WSMAXe  B           Issue UCX management commands. For complete information,(           see the following UCX manuals:  ;           o  DEC TCP/IP Services for OpenVMS Management foroD              descriptions of management tasks and tuning performance  @           o   DEC TCP/IP Services for OpenVMS Management Command@              Reference for descriptions and syntax of management              commands                            3-16 Configuration _  _                    I                                                                         AeI         _________________________________________________________________o  H                                                                 Examples    H               This appendix show examples of an installation and several$               configuration scripts.           A.1 Installation                 This example:   H               o  Installs DEC TCP/IP Services for OpenVMS (UCX) VAX onto+                  an OpenVMS VAX V5.5 systems  D               o  Uses a 9-track magnetic tape mounted on drive MUA0:                 o  Assumes that:  A                  -  You checked the disk space and all other pre-mC                     installation requirements listed in Figure 1-1.   B                  -  You completed the installation tasks listed in                     Chapter 1.  H                  -  You filled out the interface configuration checklist$                     (see Figure 1-2.  H                  -  You ran VMSINSTAL prior to this with OPTIONS N untilH                     the prompt asking for your choice of a Release Notes                     option.n  2                  -  You printed the Release Notes.  D                  -  You aborted VMSINSTAL to read the Release Notes.  H                  -  You ran VMSINSTAL for a second time without options.  G               For a complete list of files copied by the procedure, seen               Appendix B.   I                                                             Examples  A-1e    h              -             $ SET DEFAULT SYS$UPDATE <Return>r;             $ @VMSINSTAL UCX031 MUA0:[UCX031.KITS] <Return>o  A            VAX/VMS Software Product Installation Procedure V5.5-2t  $           It is 1-MAY-1994 at 14:35.  9           Enter a question mark (?) at any time for help. H           %VMSINSTAL-W-ACTIVE, The following processes are still active:            _MUAO16:n            DECW$MWMy  ;           * Do you want to continue anyway [NO]? Y <Return> Q           * Are you satisfied with the backup of your system disk [YES]? <Return>e  3           The following products will be processed:o             UCX V3.1  6            Beginning installation of UCX V3.1 at 14:35  @           %VMSINSTAL-I-RESTORE, Restoring product save set A ...U           %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.e  T           * Do you want to purge files replaced by this installation [YES]? <Return>             Product:      UCX            Producer:     DEC            Version:      3.1e"           Release Date: MAY - 1994  Y           * Does this product have an authorization key registered and loaded? Y <Return>h  V           %UCX-I-DONEASK, No further questions will be asked during this installation.@           %VMSINSTAL-I-RESTORE, Restoring product save set B ...  D           Renaming file UCX$LPD_STARTUP.COM to UCX$LPD_STARTUP.OLD;0G           Please add any user printer queue information to the new file   F           Renaming file UCX$LPD_SHUTDOWN.COM to UCX$LPD_SHUTDOWN.OLD;0G           Please add any user printer queue information to the new filen  @           %VMSINSTAL-I-RESTORE, Restoring product save set C ...@           %VMSINSTAL-I-RESTORE, Restoring product save set D ...         A-2 Examples                   Z               ****************************************************************************C                This installation will add the following files . . . Z               ****************************************************************************/                                               . /                                               . /                                               . \               %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  V               %RENAME-I-RENAMED, SYS$COMMON:[SYSEXE]UCX$CONFIGURATION.DAT;1 renamed toK                                  SYS$COMMON:[SYSEXE]UCX$CONFIGURATION.OLD;2-  \               ******************************************************************************Y                  Instructions for Completing DEC TCP/IP Services for OpenVMS Installation \               ******************************************************************************  H                    All files have been copied from the installation kit.I                    If you are installing this product for the first time, H                    upgrading from a previous version, or you want to runI                    the IVP, then execute the following command procedure:_  -                    SYS$MANAGER:UCX$CONFIG.COM_  K                           If you would like this product to start when yourtD                    OpenVMS VAX system is started, modify your systemF                    startup command file (SYS$MANAGER:SYSTARTUP_V5.COM)H                    to invoke the DEC TCP/IP Services for OpenVMS startup                     command file:  .                    SYS$MANAGER:UCX$STARTUP.COM  Q                    NOTE: If you are reinstalling DEC TCP/IP Services for OpenVMS,f4                    then you must reboot your system.  R                    For information on the postinstallation steps, see this manual:T                    "DEC TCP/IP Services for OpenVMS Installation and Configuration."  S                       Registering DEC TCP/IP Services for OpenVMS privileged images   :                Installation of UCX V3.1 completed at 14:39  0                VMSINSTAL procedure done at 14:39               $t      I                                                             Examples  A-3e t  P                   A.2 Configuration   E           The UCX configuration procedure looks the same when you run E           it on OpenVMS AXP systems and OpenVMS VAX systems. However,iE           the following things are determined by the command line you C           use to start the procedure and, if you are reconfiguring,o%           your current configuration.s             o  Menus that appear  $           o  Questions you are asked  =           o  Display of the current configuration informationt  +           o  Flow from sub-menu to sub-menuP  :           o  Movement between client and server components  *     A.2.1 Configuration: Client Components             This example:   ;           o  Runs UCX$CONFIG.COM from an OpenVMS AXP system_  ;           o  Assumes that this is a first-time installation_  +           o  Specifies the CLIENT parameter   B           o  Shows how the procedure configures components one-by-@              one, each time asking you if you want to select it.  <           o  Shows how the procedure moves from component to7              component. The menu includes and displays:   (              -  FTP CLIENT Configuration  (              -  LPD CLIENT Configuration  (              -  NFS CLIENT Configuration  (              -  RSH SERVER Configuration  +              -  RLOGIN SERVER Configuration   *              -  REXEC SERVER Configuration  :              Shows how the procedure moves from the client7              configuration to the server configuration.        A-4 Examples                     I               ___________________________________________________________t    ,         $ @UCX$CONFIG CLIENT ENABLE <Return>  0           TCP/IP Network Configuration Procedure  @          This procedure helps you define the parameters required?          to run DEC TCP/IP Services for OpenVMS on this system.   6         The 'configure all client' option is selected.  9         The 'silent mode' ENABLE option is also selected.I  K          Checking TCP/IP Services for OpenVMS configuration database files.b  <          Creating SYS$COMMON:[SYSEXE]UCX$CONFIGURATION.DAT;1            FTP CLIENT Configuration            LPD CLIENT Configuration  -         Service is not defined in the SYSUAF.e3           Nonprivileged user access is not enabled.   =         By default DEC TCP/IP Services for OpenVMS configurescF         LPD such that nonprivileged users cannot modify queue entries.  7         Creating UCX$AUX identifier with a value of 375 =         Creating SYS$SPECIFIC:[UCX_LPD]UCX$PRINTCAP.DAT file.o  P          DEC TCP/IP for OpenVMS supports Line Printer Daemon Protocol (RFC 1179)$          LPD requires the following:%             - Name of the local queuem&             - Name of the remote queue%             - Name of the remote host 4             - Spooling directory for the local queue  N                 To add or delete printers in the UCX PRINTCAP database use the4                 $RUN SYS$SYSTEM:UCX$LPRSETUP command            NFS CLIENT Configuration  #         Creating UCX$NOBODY AccountS            RSH SERVER Configuration  I                                                             Examples  A-5e o  g              )     Service is not defined in the SYSUAF.S3     Service is defined in the UCX$SERVICE database.n       REXEC SERVER Configuration  )     Service is not defined in the SYSUAF. 3     Service is defined in the UCX$SERVICE database.a       RLOGIN SERVER Configurationr  3     Service is defined in the UCX$SERVICE database./       SMTP SERVER Configuratione  )     Service is not defined in the SYSUAF.v3     Service is defined in the UCX$SERVICE database. C     Configuration is not defined in the UCX$CONFIGURATION database.        SNMP SERVER Configurationu  )     Service is not defined in the SYSUAF. 3     Service is defined in the UCX$SERVICE database. C     Configuration is not defined in the UCX$CONFIGURATION database.X  >      To configure the SNMP agent, you must provide information<      for one or more communities. A community consists of an=      access type (which will be set to read), and one or more =      remote host internet addresses.  Enter <Return> when you *      have no more information to be added.  
      Example:        Community Type Addresses         public  read 0.0.0.0  "       examplecomm read 130.180.4.5          130.180.6.2          130.180.5.4  ?      WARNING - the community name is case sensitive.  Lowercase/-             names must be enclosed in quotes.   =     Do you want to provide the public community [Y]: <Return>t  :     Do you want to provide another community [N]: <Return>  ?      To configure the TCP/IP MOM you must provide the following       information:B(       - contact person(s) for the system       - location of the system1       - number of services as defined in RFC 1158        A-6 Examples c  a                        Example:            Larry Anonymous            42 Oak LaneA           Anytown, BQ, 99999  2         Enter contact person(s): WISE OWL <Return>C         Enter the location of the system: NIGHT_WATCH_2/S3 <Return>z  #         TELNET SERVER Configurationm  7         Service is defined in the UCX$SERVICE database.d  I          TCP/IP Services for OpenVMS CLIENT Components Configuration Menu             Configuration options:   &           1 - FTP              Enabled&           2 - LPR/LPD          Enabled&           3 - NFS Client       Enabled&           4 - REXEC and RSH    Enabled&           5 - RLOGIN           Enabled&           6 - SMTP             Enabled&           7 - SNMP             Enabled&           8 - TELNET           Enabled  %           A - Configure options 1 - 8            E - Exit menuo  ,         Enter configuration option: <Return>  E          DEC TCP/IP Services for OpenVMS requires a definition for atoF          least one interface.  There are no interfaces defined on this          system.  B          You must now reconfigure the core environment to do this.           INTERFACE Configuration   M          The Ethernet device(s) on your system are: ESA0:  * Not Configured *U  =           WARNING - the Internet host name is case sensitive.M9          Enclose lowercase host names in quotation marks.r  E          Start of configuration questions for Internet interface SE0..)          SE0 is the Ethernet device ESA0: $          SE0 has not been configured  7         * Do you want to configure SE0 [YES] ? <Return> *         Enter host name: "blujay" <Return>  I                                                             Examples  A-7P N  0              (      Host blujay exists in the database.  3     Enter Internet address [16.20.0.100] : <Return>NL     Enter Internet network mask for blujay [255.0.0.0]: 255.255.0.0 <Return>=     Enter broadcast mask for blujay [16.20.255.255]: <Return>e  8      The following parameters will be used to define the      Internet interface SE0:         Host name:         blujayn$       Internet address:  16.20.0.100$       Network mask:      255.255.0.0&       Broadcast mask:    16.20.255.255  +     * Is the above correct [YES] ? <Return>   >      End of configuration questions for Internet interface SE0  3      TCP/IP Services for OpenVMS Configuration Menu         Configuration options::         1 - Core environment       2 - Client componentsy       3 - Server componentsB  .       4 - Shutdown TCP/IP Services for OpenVMS;                     5 - Startup TCP/IP Services for OpenVMSA       6 - Run tests   !       A - Configure options 1 - 3v&       E - Exit configuration procedure       Enter configuration option:r     .d     .      .s  E           ___________________________________________________________l                 A-8 Examples                   $         A.2.2 Configuration: Routing  B               This section shows an example of the dynamic routing               configuration.  +               DYNAMIC ROUTING Configuration   7                Dynamic routing has not been configured.f  C                If you enable dynamic routing, this host will listenTD                for all dynamic routing information coming from other;                hosts to update its internal routing tables.r@                It will also supply its own Internet addresses to7                routing requests made from remote hosts.f  I               * Do you want to configure dynamic routing [YES] ? <Return>   D                If you enable the 'supply' option of dynamic routing,C                this host will supply dynamic routing information to D                other hosts on the network whether it is acting as an+                internetwork gateway or not.h  C               * Do you want this host to supply its dynamic routinge+                 information [NO] ? <Return>                                           I                                                             Examples  A-9  U                 $     A.2.3 Configuration: BIND Server  9           This section shows the local host's BIND Server            configuration.  3      TCP/IP Services for OpenVMS Configuration Menu   &       1 - Reconfigure Core Environment       2 - Configure NFS Server       3 - Configure NFS Client        4 - Configure PCNFS Server       5 - Configure Portmapper        6 - Configure Applications.       7 - Shutdown TCP/IP Services for OpenVMS-       8 - Startup TCP/IP Services for OpenVMS        9 - Run IVP   &       E - Exit Configuration Procedure  *     Enter configuration option: 6 <Return>  ?      TCP/IP Services for OpenVMS Application Configuration MenuT         [1] - Configure Telnet       [2] - Configure rlogin        [3] - Configure FTP Server       [4] - Configure SMTP       [5] - Configure rexec/rsh        [6] - Configure lpd/lprP       [7] - Configure SNMP       [8] - Configure BOOTP !       [9] - Configure Bind Server   !       [A] - Configure Options 1-7O       [M] - Return to Main Menu   ,      Enter configuration option:  9 <Return>  ;     Please enter host name for this system: BLUJAY <Return>r  ,     You have specified BLUJAY.EURO.SALES.COM!     Is this correct? [Y] <Return>U0      Creating SYS$SPECIFIC:[UCX$BIND]NAMED.LOCAL-      Creating SYS$SPECIFIC:[UCX$BIND]NAMED.CA !     Creating BIND Service Entriesn  3     Do you want the Bind Server enabled? Y <Return>        A-10 ExamplesI e  c                    I                                                                         BmI         _________________________________________________________________   H                                                          Installed Files    D               The DEC TCP/IP Services for OpenVMS (UCX) installationH               procedure copies all the distribution files built for your               operating system._  E               If you are re-installing UCX, the procedure renames the B               Configuration Database, in SYS$COMMON:[SYSEXE], from=               UCX$CONFIGURATION.DAT to UCX$CONFIGURATION.OLD.r           B.1 UCX Driverst  B               Table B-1 lists and describes the drivers in the UCX               software.s  I         Table_B-1_Drivers_Copied_to_SYS$COMMON:[SYS$LDR]_________________n  I         File_____________________Description_____________________________   7         UCX$BGDRIVER.EXE         Internet Device Driver   @         UCX$TNDRIVER.EXE         TELNET and Remote Login Drivers  2         UCX$DNFCDRIVER.EXE       NFS Client Driver  /         UCX$INETDRIVER.EXE       SRI QIO Drivert  2         UCX$INTERNET_            Internet software         SERVICES.EXE+-  2         UCX$INTERNET_SERVICES_   Internet software         V6.EXE+ I         +OpenVMS_VAX_specific____________________________________________   I         _________________________________________________________________f           B.2 Other UCX Files   C               Table B-2 lists and describes the remaining UCX files )               installed onto your system.o  I                                                      Installed Files  B-1d m  i              E     Table_B-2_Other_UCX_Files_Installed______________________________   E     File_____________________Description_____________________________   E     To_SYS$COMMON:[SYSEXE]___________________________________________   >     UCX$INETACP.EXE          Network ancillary control processD                              (NETACP) for the Internet device driver  :     UCX$INETACP.STB          Global symbol definitions for,                              UCX$INETACP.EXE  :     UCX$INTERNET_SERVICES_   Global symbol definitions for9     V6.STB+                  UCX$INTERNET_SERVICES_V6.EXE   :     UCX$INTERNET_SERVICES_   Global symbol definitions for=     V6_SEC.STB+              UCX$INTERNET_SERVICES_V6_SEC.EXEc  :     UCX$INTERNET_            Global symbol definitions for6     SERVICES.STB             UCX$INTERNET_SERVICES.EXE  :     UCX$INTERNET_SERVICES_   Global symbol definitions for:     SEC.STB                  UCX$INTERNET_SERVICES_SEC.EXE  ,     UCX$INET_ROUTING.EXE     Dynamic routing  D     UCX$INET_ROUTING.STB     Global symbol definitions for UCX$INET_(                              ROUTING.EXE  C     UCX$NET_GLOBALS.STB      Global symbol definitions for UCX$NET_ (                              GLOBALS.EXE  D     UCX$CONVERT.FDL          File definition used by UCX$CONVERT.COM  >     UCX$CONVERT.COM          Procedure for converting files to&                              STREAM_LF  (     UCX$BIND_SERVER.EXE      BIND Server  8     UCX$BIND_SERVER_         BIND Server's zone transfer     XFER.EXE  /     UCX$BOOTP.EXE            Remote Boot ServerP  =     UCX$DNFC_MOUNT.EXE       NFS Client Mount (MOUNT command)o  C     UCX$DNFC_DISMOUNT.EXE    NFS Client Dismount (DISMOUNT command)P  E     +OpenVMS_VAX-specific____________________________________________   E                                              (continued on next page)e       B-2 Installed FilesN L  R              I         Table_B-2_(Cont.)_Other_UCX_Files_Installed______________________   I         File_____________________Description_____________________________*  I         To_SYS$COMMON:[SYSEXE]___________________________________________   >         UCX$DNFCDRIVER.STB       Global symbol definitions for3                                  UCX$DNFCDRIVER.EXE   F         UCX$ENCODE.COM           Procedure to execute UUENCODE program  F         UCX$DECODE.COM           Procedure to execute UUDDCODE program  +         UCX$FTP.EXE              FTP Clientt  +         UCX$FTPC.EXE             FTP Server-  D         UCX$FTPD.EXE             FTP Control Command Server (daemon)  C         UCX$FTPSERVER.COM        Procedure that starts an FTP child (                                  process  /         UCX$LPD_RCV.EXE          Print receiver   /         UCX$LPD_SMB.EXE          Print symbiontP  -         UCX$LPRM.EXE             LPRM command   C         UCX$LPRSETUP.EXE         Setup utility for network printing*  ,         UCX$LPQ.EXE              LPQ command  1         UCX$NSLOOKUP.EXE         nslookup Utility   4         UCX$SERVER_NFS.EXE       NFS Server (daemon)  7         UCX$PCNFSD.EXE           PC-NFS Server (daemon)   -         UCX$PING.EXE             PING commandh  E         UCX$PORTMAPPER.EXE       Program that maps processes to portsN  4         UCX$RLOGIN.EXE           Remote Login Client  8         UCX$RPCINFO.EXE          SHOW PORTMAPPER command  -         UCX$RSH.EXE              Remote Shelly  .         UCX$SMTP_RECEIVER.EXE    SMTP receiver  I                                                  (continued on next page)c  I                                                      Installed Files  B-3  S  N              E     Table_B-2_(Cont.)_Other_UCX_Files_Installed______________________e  E     File_____________________Description_____________________________.  E     To_SYS$COMMON:[SYSEXE]___________________________________________   *     UCX$SMTP_SYMBIONT.EXE    SMTP symbiont  '     UCX$SNMP_AGENT.EXE       SNMP agentu  *     UCX$TELNET.EXE           TELNET Client  2     UCX$TELNETSYM.EXE        TELNET print symbiont  1     UCX$TFTP.EXE             TFTP Server (daemon)1  A     UCX$UCP.EXE              UCX Management control program (UCP)   -     UCX$UUENCODE.EXE         Encoder for SMTP   -     UCX$UUDECODE.EXE         Decoder for SMTP   ?     UCX$VERSIONS.EXE         Image for the SHOW VERSION command   E     _________________________________________________________________mE     To_SYS$COMMON:[SYSLIB]___________________________________________e  5     UCX$ACCESS_SHR.EXE       Database access routinesa  B     UCX$CFS_SHR.EXE          Container File System runtime library  :     UCX$INETDEF.ADA          Internet Ada definitions file  >     UCX$INETDEF.FOR          Internet FORTRAN definitions file  8     UCX$INETDEF.H            Internet C definitions file  <     UCX$INETDEF.MAR          Internet MACRO definitions file  =     UCX$INETDEF.PAS          Internet Pascal definitions file   ;     UCX$INETDEF.PL1          Internet PL/1 definitions fileo  <     UCX$INETDEF.R32          Internet BLISS definitions file  0     UCX$IPC_SHR.EXE          IPC runtime library  /     UCX$IPC.OLB              IPC object libraryp  B     UCX$LPD_SHR.EXE          Shared library for printing processes  0     UCX$SMTP_MAILSHR.EXE     SMTP shared library  E                                              (continued on next page)h       B-4 Installed Filess                   I         Table_B-2_(Cont.)_Other_UCX_Files_Installed______________________   I         File_____________________Description_____________________________i  I         To_SYS$COMMON:[SYSLIB]___________________________________________E  6         UCX$SMTP_PARSESHR.EXE    SMTP parsing routines  4         UCX$RPCXDR.H             Sun RPC header file  9         UCX$RPCXDR_SHR.EXE       Sun RPC routines library   I         __________________________________________________________________I         To_SYS$COMMON:[SYSHLP]___________________________________________N  .         UCX031.RELEASE_NOTES     Release Notes  D         UCX$UCP_HELP.HLB         Online help for management commands  >         UCX$VMS_FILES.DOC        Online information about fileC                                  restrictions for UNIX users of NFSE'                                  Servere  0         UCX$FTP_HELP.HLB         FTP online help  3         UCX$TELNET_HELP.HLB      TELNET online helpX           UCX$NSLOOKUP_HELP.HLBT  4                                  nslookuponline help  I         _________________________________________________________________ I         To_SYS$COMMON:[SYSHLP.EXAMPLES.UCX]______________________________O  @         UCX$INTERNET_SERVICES_   Internet software with security         V6_SEC.EXE+.  C         BUILD_UCX_SECURITY_      Example file to build the securityr'         DRIVER.COM               driver.  4         UCX$IOCTL_ROUTINE.C      Programming example  B         TN3270DEF.MAR            For IBM 3270TE; translation tableE                                  template that you edit to modify theh4                                  translation tables.  I         +OpenVMS_VAX-specific____________________________________________a  I                                                  (continued on next page)R  I                                                      Installed Files  B-5     a              E     Table_B-2_(Cont.)_Other_UCX_Files_Installed______________________   E     File_____________________Description_____________________________   E     To_SYS$COMMON:[SYSHLP.EXAMPLES.UCX]______________________________h  0     TRACEROUTE.EXE           Traceroute facility  4     UCX_TRACE.EXE            Protocol trace facility  :     UCX_SECURITY_DRIVER.MAR  Security driver source sample  0     UCX$TCP_CLIENT_IPC.C     Programming example  0     UCX$TCP_CLIENT_QIO.C     Programming example  0     UCX$TCP_CLIENT_QIO.MAR   Programming example  0     UCX$TCP_SERVER_IPC.C     Programming example  2     UCX$TCP_SERVER_IPC_      C programming example
     AUXS.C  0     UCX$TCP_SERVER_QIO.C     Programming example  0     UCX$TCP_SERVER_QIO.MAR   Programming example  2     UCX$TCP_SERVER_QIO_      C programming example
     AUXS.C  2     UCX$UDP_CLIENT_IPC.C     C programming example  2     UCX$UDP_CLIENT_QIO.C     C programming example  6     UCX$UDP_CLIENT_QIO.MAR   MACRO programming example  2     UCX$UDP_SERVER_IPC.C     C programming example  2     UCX$UDP_SERVER_QIO.C     C programming example  E     _________________________________________________________________ E     To_SYS$COMMON:[SYSMGR]___________________________________________0  :     UCX$BIND_STARTUP.COM     BIND Server startup procedure  ;     UCX$BIND_SHUTDOWN.COM    BIND Server shutdown procedures  A     UCX$BOOTP_STARTUP.COM    Remote boot server startup procedureu  B     UCX$BOOTP_SHUTDOWN.COM   Remote boot server shutdown procedure  E                                              (continued on next page)T       B-6 Installed Filesy m                 I         Table_B-2_(Cont.)_Other_UCX_Files_Installed______________________   I         File_____________________Description_____________________________   I         To_SYS$COMMON:[SYSMGR]___________________________________________r  8         UCX$CALLBACKS.COM        Configuration utilities  8         UCX$CONFIG.COM           Configuration procedure  7         UCX$FIXUP.COM            V1 configuration fixup3  =         UCX$FTPD_STARTUP.COM     FTP Server startup procedurev  >         UCX$FTPD_SHUTDOWN.COM    FTP Server shutdown procedure  ;         UCX$INET_STARTUP.COM     Internet startup procedure   <         UCX$INET_SHUTDOWN.COM    Internet shutdown procedure  D         UCX$LOAD_INETDRIVER.COM  Command file that loads the SRI QIO6                                  programming interface  G         UCX$REGISTER.COM         Command file that registers privilegedl+                                  UCX images   A         UCX$LPD_RCV_STARTUP.COM  Print receiver startup proceduren  ?         UCX$LPD_STARTUP.COM      Print Server startup procedurep  @         UCX$LPD_SHUTDOWN.COM     Print Server shutdown procedure  =         UCX$NFS_STARTUP.COM      NFS Server startup procedure   >         UCX$NFS_SHUTDOWN.COM     NFS Server shutdown procedure  @         UCX$PCNFSD_STARTUP.COM   PC-NFS Server startup procedure  A         UCX$PCNFSD_SHUTDOWN.COM  PC-NFS Server shutdown proceduree  >         UCX$PORTM_SHUTDOWN.COM   Portmapper shutdown procedure  =         UCX$PORTM_STARTUP.COM    Portmapper startup proceduree  I                                                  (continued on next page)n  I                                                      Installed Files  B-7h n  b              E     Table_B-2_(Cont.)_Other_UCX_Files_Installed______________________n  E     File_____________________Description_____________________________   E     To_SYS$COMMON:[SYSMGR]___________________________________________j  .     UCX$PRINTCAP.DAT         Printcap Database  C     UCX$REMOTE_TTY_          TELNET and Remote Login Server startupl&     STARTUP.COM              procedure  2     UCX$STARTUP.COM          UCX startup procedure  3     UCX$SHUTDOWN.COM         UCX shutdown proceduret  ;     UCX$RSHD_STARTUP.COM     Remote Shell startup procedure   ?     UCX$REXECD_STARTUP.COM   Remote Executive startup procedure   9     UCX$SMTP_STARTUP.COM     SMTP queue startup procedure5  :     UCX$SMTP_SHUTDOWN.COM    SMTP queue shutdown procedure  <     UCX$SMTP_RECV_           SMTP receiver startup procedure     STARTUP.COMO  3     UCX$SNMP_STARTUP.COM     SNMP startup procedures  4     UCX$SNMP_SHUTDOWN.COM    SNMP shutdown procedure  9     UCX$SNMP_CONFIG.COM      SNMP configuration procedureP  =     UCX$SNMPD_MIR.DAT        SNMP dictionary of MIB variablesS  8     UCX$SYMBOLS.COM          Configuration logical names  3     UCX$TFTP_STARTUP.COM     TFTP startup proceduree  4     UCX$TFTP_SHUTDOWN.COM    TFTP shutdown procedure  9     UCX$SMTP_CONFIG.COM      SMTP configuration procedure_  E                                              (continued on next page)          B-8 Installed FilesR i                 I         Table_B-2_(Cont.)_Other_UCX_Files_Installed______________________g  I         File_____________________Description_____________________________n  I         To_SYS$COMMON:[SYSMGR]___________________________________________c  @         UCX$TIMEZONE.COM         Internet timezone configuration*                                  procedure  C         UCX$UCP_STARTUP.COM      Management control program startup   I         _________________________________________________________________tI         To_SYS$COMMON:[SYSMSG]___________________________________________m  1         UCX$MSG.EXE              UCX message file   I         _________________________________________________________________ I         To_SYS$COMMON:[SYSTEST.UCX]______________________________________e  5         UCX$INET_IVP.EXE         Auxiliary Server IVPw  8         UCX$RPCIVP_CLIENT.EXE    RPC Client routines IVP  8         UCX$RPCIVP_SERVER.EXE    RPC Server routines IVP  I         _________________________________________________________________ I         To_SYS$COMMON:[SYSTEST]__________________________________________   I         UCX$IVP.COM______________UCX_IVP_________________________________e  1         B.3 Files Installed for PATHWORKS Systems   C               Table B-3 lists and describes the files for PATHWORKSo@               systems that are installed by the UCX installation               procedure.  I         Table_B-3_PATHWORKS_Files________________________________________f  I         File_________________________________Description_________________   @         SYS$COMMON:[SYS$LDR]UCX$PWIPDRIVER.EXPATHWORKS IP driver  =         SYS$COMMON:[SYSEXE]UCX$PWIPACP.EXE   PATHWORKS IP ACP   F         SYS$COMMON:[SYSEXE]UCX$PWIPDRIVER.STBGlobal symbol definitionsC                                              for UCX$PWIPDRIVER.EXE   I                                                  (continued on next page)g  I                                                      Installed Files  B-9                    E     Table_B-3_(Cont.)_PATHWORKS_Files________________________________n  E     File_________________________________Description_________________o  B     SYS$COMMON:[SYSEXE]UCX$PWIPSYM.STB   Global symbol definitions<                                          for UCX$PWIPSYM.EXE  D     SYS$COMMON:[SYSMGR]UCX$PWIP_         PATHWORKS IP driver startup     STARTUP.COMe  E     SYS$COMMON:[SYSMGR]UCX$PWIP_         PATHWORKS IP driver shutdownnE     SHUTDOWN.COM_____________________________________________________a                                                                       B-10 Installed Files                                 F      _________________________________________________________________  F                                                                  Index      =      A                                 Configuration (cont'd) ?      _______________________________     examples,  A-4 to A-10rD      API                                 preparing for,  1-2 to 1-5,/        SRI QIO, 3-16                        3-1   B      Application programming             privileges required,  3-5=         interface                        required tasks,  3-1.B        See API.                          requirements,  1-2 to 1-56                                             time,  1-2;      B______________________________     running,  3-5, 3-9_E      Berkeley Domain Name Service        running UCX$CONFIG.COM,  3-8_2                                        ConventionsC        See BIND.                         documentation,  vi to viiie  7      Berkeley Internet Name Domain          braces,  vin9        See BIND.                            brackets,  vit  	      BINDCF        Server                          D______________________________/           creating files for, 3-15     Database :      Braces                              populating,  3-12;        documentation convention, vi    DECW$PRIVATE_SERVER__8      Brackets                             SETUP.TEMPLATE=        documentation convention, vi      modifying,  2-7, 2-9i  =                                        DECW$SERVER_TRANSPORTSy8      C______________________________     modifying,  2-7  B      CHANNELCNT                          writing a transport,  2-8B        SYSGEN parameter                DECW$XPORT_ATTACH_TRANSPORT=           for tuning performance,        used by DECW$SERVER_ ;             3-16                            TRANSPORTS, 2-7_7      Checklist                         DECwindows,  2-5nF        installation, 1-4                 defining TCP Transport,  3-12F      Configuration,  3-1 to 3-16         requirements for installation1        example of BIND Server, A-10         , 1-4 9        example of core environment       restarting,  2-7 7          and client,  A-4                security,  2-7   F                                                                Index-1                   3     DECwindows (cont'd)                Installation >       transport for,  2-7 to 2-8        preparing for (cont'd)8       writing transport for,  2-8          backups,  1-2@     DNS                                    global pagelets,  1-2@       See BIND.                            global sections,  1-2A     Documentation                       requirements,  1-2 to 1-5f;       associated                           disk space,  1-2 6          titles listed,  xii               quota,  1-29       conventions,  vi to viii             software,  1-2C5          braces,  vi                       time,  1-2E8          brackets,  vi                  verifying,  3-10=       terminology,  ix to xii          Installation procedureC:     Domain Name Service                 create a log,  2-2<       See BIND.                         description of,  2-19     Driver                              directories,  2-2TD       for UCX                           interrupting VMSINSTAL,  2-2E          file names,  B-1               postinstallation tasks,  2-10iD       PATHWORKS systems (PWIP),         printing release notes,  2-5=          B-9                            re-installation,  2-2 D                                         reinstallation for clusters,.                                            2-2B     E______________________________     running VMSINSTAL,  2-3 to  .     Error                                  2-5@       during installation,  2-6         starting VMSINSTAL,  2-3E     Errors                              SYSTEM account required,  2-3XB       during IVP,  3-9 to 3-10          unsuccessful installation,.     Examples,  A-1 to A-10                 2-6D                                         using VMSINSTAL,  2-1 to 2-2C     G______________________________     VMSINSTAL conventions,  2-1rA     Global pagelet                     Installation procedure for @       changing,  1-2                     DECwindows,  2-7 to 2-8B     Global section                      installing transport,  2-7/       changing,  1-2                   Internet 5                                         Device DriverC:     I                                      installed,  B-1*     _______________________________    IVPD     Installation                        error messages,  3-9 to 3-107       drivers                           explained,  3-9RD          file names,  B-1               for Portmapper Service,  3-9A       example,  A-1 to A-3              privileges required,  3-9o6       files installed,  B-1 to B-10     running,  3-10C       of example transport,  2-8        running after configurationo9       PATHWORKS systems                    procedure, 3-9PB          file names,  B-9               running from configuration>       preparing for,  1-2                  procedure menu, 3-9       Index-2                             IVP (cont'd)I          SYSTEM account required,  2-3    P______________________________   8                                           PAK,  1-4, 2-5?         L______________________________     and DECwindows, 3-9D9         License                             and IVPs, 3-9O3          client,  v                       PATHWORKS 7          DECwindows,  v, 3-9                PWIP Driver$@          registration,  1-4                    configuring, 3-15G          registration of,  3-9                 files installed for, B-9 >          server,  v                            installed, 3-15?         LMF, 1-4                               requirements forUC                                                  installation,  1-4D5         N                                 Performancef8         _______________________________     tuning, 3-163         Name service                      Port 6000S  B          See BIND.                          used by transport, 2-84         NFS                               PortmapperC          Client                             verifying with IVP, 3-9 F             Driver                        Post-configuration,  3-11 to1                installed,  B-1               3-15e5             post-configuration tasks,       databases ?                3-14                            populating, 3-12i<          Server                             DECwindows, 3-12C             post-configuration tasks,       editing system shutdowno>                3-12                           procedure,  3-11B         NFS Server                          editing system startup>          online documentation for UNIX        procedure,  3-11/             users,  3-14                    NFS ;         Nonpaged dynamic pool                  Client, 3-14 ;          increasing,  3-3                      Server, 3-12 A         NPAGEDYN SYSGEN parameter           verifying SYLOGIN.COMn@          increasing,  3-3                     protections,  3-11:         NPAGEVIR SYSGEN parameter         Postinstallation=          increasing,  3-3                   BIND Server, 3-15_  4                                           PrivilegesF         O______________________________     installation requirements,  1         OpenVMS                               1-2iG          installation requirements,         required for configuration,_1             1-2                               3-5_A                                             required for IVP, 3-9N?                                           Process symbol tables ;                                             restoring, 2-10 4                                           Protection@                                             of SYLOGIN.COM, 3-11  I                                                                   Index-3                    4     PWIP Driver                        SRI Interface.       See PATHWORKS.                    Driver:                                            installed,  B-1  B     Q______________________________    Standard Research Institute  0     QIO Interface                       See SRI..       Driver                           Startup1          installed,  B-1                procedure_9                                            editing,  3-11 2     R                                  SYLOGIN.COMD     _______________________________     verifying protections,  3-11?     Re-installation                    SYS$SYSTEM:MODPARAMS.DAT ?       procedure,  2-2                   increasing NPAGEDYN and 8     Reinstallation                         NPAGEVIR, 3-3-       renamed files,  2-3              SYSGEN_C     Release Notes                       CHANNELCNT parameter,  3-16 B       printing,  2-5                    to increase nonpaged pool,.     Remote Login                           3-3>       Driver                            WSMAX parameter,  3-165          installed,  B-1               SYSTEM account_B     Requirement                         running installation from,.       license registration,  1-4           2-3     Requirements(       configuration,  1-2 to 1-5       TF          time,  1-2                    _______________________________-       installation,  1-2 to 1-5        TELNETC.          DECwindows,  1-4               Driver:          disk space,  1-2                  installed,  B-12          PATHWORKS,  1-4               Terminology=          quota,  1-2                    explained,  ix to xiii+          software,  1-2                TimeQ0          time,  1-2                     required=                                            to configure,  1-2C;     S______________________________        to install,  1-2 0     Security                           TransportE       for example transport,  2-9       example supplied with DEC TCPrD     Security for DECwindows,  2-7          /IP Services for OpenVMS,.     SET DISPLAY command,  2-8, 2-9         2-86     Shutdown                            for DECwindowsA       procedure                            writing your own,  2-8_@          editing,  3-11                 supplied with DEC TCP/IPD     SPR                                    Services for OpenVMS, 2-8>       reporting IVP error,  3-10        writing your own,  2-8=     SRI                                Transport installationoC       interface                         for DECwindows,  2-7 to 2-8             configuring,  3-16T       Index-4t e  i              4         Transport installation              See UIC.             (cont'd)I          modifying DECW$PRIVATE_          V_______________________________  3             SERVER_SETUP.TEMPLATE,        VMSINSTAL_<             2-7                             conventions, 2-1<          modifying DECW$SERVER_             description, 2-1?             TRANSPORTS,  2-7                running, 2-3 to 2-5 7                                           VMSINSTAL.COMMD         U______________________________     installing UCX with, 2-1  +         UCX$CONFIG.COM, 3-8               WNI          running,  3-5, 3-9               _______________________________./         UIC                               WSMAX$<          selecting,  3-2                    SYSGEN parameterF         User Identification Code               for tuning performance,5                                                  3-16   I                                           X______________________________O  -                                           X11CG                                             conventions for TCP/IP, 2-8_                                            I                                                                   Index-5 