                                   C                      DIGITAL_PATHWORKS_for_OpenVMS_________________ @                      Server Installation and Configuration Guide                         AA-R6G1A-TE                           August 1997  E                      This guide explains how to install and configure C                      all of the components of DIGITAL PATHWORKS for E                      OpenVMS (Advanced Server) software including the E                      Advanced Server, the NetWare server, the license 5                      server, and the Upgrade utility.           G                      Revision/Update Information: This guide supersedes G                                                   PATHWORKS for OpenVMS E                                                   Server Installation D                                                   and Upgrade Guide,>                                                   AA-LB63G-TE.  F                      Operating System:            DIGITAL OpenVMS V7.1  F                      Software Version:            DIGITAL PATHWORKS V6G                                                   for OpenVMS (Advanced 9                                                   Server) C                                                   DIGITAL PATHWORKS C                                                   V1.0G for OpenVMS ;                                                   (NetWare)   2                      Digital Equipment Corporation+                      Maynard, Massachusetts                  E            __________________________________________________________ #            First Printing, May 1988             Revised, August 1997   A            Digital Equipment Corporation makes no representations B            that the use of its products in the manner described inC            this publication will not infringe on existing or future C            patent rights, nor do the descriptions contained in this C            publication imply the granting of licenses to make, use, ?            or sell equipment or software in accordance with the             description.   C            Possession, use, or copying of the software described in B            this publication is authorized only pursuant to a validC            written license from Digital Equipment Corporation or an "            authorized sublicensor.  ;            This software is proprietary to and embodies the C            confidential technology of Digital Equipment Corporation             and other parties.   A             Digital Equipment Corporation 1988, 1997. All Rights             Reserved.  <            The following are trademarks of Digital EquipmentD            Corporation: Alpha, DEC, DEClaser, DECnet-Plus, DECprint,C            DIGITAL, LA50, LN03, LN03 PLUS, OpenVMS, PATHWORKS, VAX,              and the DIGITAL logo.  4            The following are third-party trademarks:  5            AT&T is a registered trademark of American /            Telephone and Telegraph Corporation. -            Apple and Macintosh are registered -            trademarks of Apple Computer, Inc.             Epson is a @            registered trademark of Seiko Epson Kabushiki Kaisha.5            Hewlett-Packard, HP, LaserJet, and PCL are <            registered trademarks of Hewlett-Packard Company.>            IBM, OS/2, and ProPrinter are registered trademarks:            of International Business Machines Corporation.@            Intel is a registered trademark of Intel Corporation.5            Microsoft, MS-DOS, Windows, and Windows 95 3            are registered trademarks and Windows NT 3            is a trademark of Microsoft Corporation.             NetWare?            and Novell are registered trademarks of Novell, Inc.             PostScript is@            a registered trademark of Adobe Systems Incorporated.E            SilentWriter is a registered trademark of NEC Corporation. 0            UNIX is a registered trademark in the6            United States and other countries, licensed2            exclusively through X/Open Company Ltd.5            Xerox is a trademark of Xerox Corporation. ;            X/Open is a trademark of X/Open Company Limited.   A            All other trademarks and registered trademarks are the 0            property of their respective holders.  E            This document was prepared using VAX DOCUMENT Version 2.1.                                C    ________________________________________________________________   C                                                            Contents     C    Preface..................................................     xi     6    1  Before You Install DIGITAL PATHWORKS for OpenVMS  C          About DIGITAL PATHWORKS for OpenVMS Servers........    1-1 C          Installing DIGITAL DECprint Software...............    1-2 C          About Licensing....................................    1-3 C          License requirements...............................    1-3 C          About the license server...........................    1-3 C          For more licensing information.....................    1-4 C          Reading the Release Notes..........................    1-4 C          About the release notes............................    1-4 C          How to access the release notes....................    1-5 C          Using the Summary Checklist........................    1-6 C          What You Need......................................    1-7 C          Hardware requirements..............................    1-7 C          Software Requirements..............................    1-7 C          PATHWORKS Advanced Server client software..........    1-7 C          NetWare client software............................    1-8 C          Memory requirements................................    1-8 C          Preinstallation Tasks..............................    1-8 C          Step 1: Check the part listing.....................    1-9 C          Step 2: Check the network hardware.................   1-10 C          Step 3: Check the required software................   1-10 C          Step 4: Log in to the SYSTEM account...............   1-10 C          Step 5: Back up the system.........................   1-10 C          Step 6: Print and read the Release Notes...........   1-11 C          Step 7: Check disk space requirements..............   1-11 C          Step 8: Check system parameters....................   1-12 C          Step 9: Check the queue manager....................   1-15 C          Step 10: Check Time Zone and TDF...................   1-16 C          Step 11: Check DECnet status.......................   1-16   C                                                                 iii                  E            Step 12: Check TCP/IP status.......................   1-18 E            OpenVMS Cluster Considerations.....................   1-18 E            Step 13: Check OpenVMS cluster configuration.......   1-18 E            Next Step..........................................   1-19     0      2  Installing DIGITAL PATHWORKS for OpenVMS  E            About the Installation Procedure...................    2-1 E            What is VMSINSTAL?.................................    2-1 E            VMSINSTAL installation kit.........................    2-2 E            What VMSINSTAL does................................    2-2 E            Determining What Software to Install...............    2-2 E            Installing the Server..............................    2-4 E            Before you start VMSINSTAL.........................    2-4 E            How to start VMSINSTAL.............................    2-6 E            How installation questions work....................    2-8 E            How to interrupt the installation..................    2-8 E            How to respond to prompts..........................    2-8 E            Next Steps.........................................   2-18 E            What to do next....................................   2-18 E            Install optional server administration tools.......   2-19   5      3  Configuring the DIGITAL PATHWORKS for OpenVMS           (Advanced Server) Server  <            About the PATHWORKS Advanced Server ConfigurationE            Procedure..........................................    3-1 E            What is the configuration procedure?...............    3-2 E            What the configuration procedure does..............    3-2 9            Before You Start the PATHWORKS Advanced Server E            Configuration Procedure............................    3-3 5            How to Start the PATHWORKS Advanced Server E            Configuration Procedure............................    3-9 6            How to Respond to PATHWORKS Advanced ServerE            Configuration Prompts..............................    3-9 2            How to Change PATHWORKS Advanced ServerE            Configuration Default Settings.....................   3-13 :            Selecting the PATHWORKS Advanced Server NetworkE            Device.............................................   3-16 E            Next Steps.........................................   3-17               iv                  8         4  Configuring the DIGITAL PATHWORKS for OpenVMS            (NetWare) Server   H               About the NetWare Configuration Procedure..........    4-1H               What is the configuration procedure?...............    4-1H               What the configuration procedure does..............    4-2H               When to configure the server.......................    4-2H               NetWare Configuration Information..................    4-2H               About network numbers..............................    4-3H               Types of network numbers...........................    4-3H               Types of external networks.........................    4-4H               Number and types of networks you can configure.....    4-4H               About Token Ring and FDDI Support..................    4-4H               Running the NetWare Configuration Procedure........    4-5H               When to run the configuration procedure............    4-5H               How to run the configuration procedure.............    4-5H               How configuration questions work...................    4-6H               How to get online help.............................    4-6H               How to interrupt the configuration.................    4-6H               How to respond to prompts..........................    4-6H               How to confirm your answers........................   4-12H               Reconfiguring the NetWare Server...................   4-12H               How to reconfigure the server......................   4-12H               New configuration value location...................   4-13  A         5  Configuring and Starting the Standalone License Server   :               Before You Begin to Configure the StandaloneH               License Server.....................................    5-2H               Configuring the Standalone License Server..........    5-27               Configuring the PATHWORKS Advanced Server H               Transports.........................................    5-39               How to Respond to PATHWORKS Advanced Server H               Configuration Prompts..............................    5-4H               Configuring the NetWare Transport..................    5-6H               How to Respond to NetWare Configuration Prompts....    5-7H               How to Start the Standalone License Server.........   5-11H               How to start the license server manually...........   5-12H               How to start the license server automatically......   5-12;               How to start the license server in an OpenVMS H               cluster............................................   5-13        H                                                                        v                 ;      6  After You Install the DIGITAL PATHWORKS for OpenVMS          Servers   E            Before You Begin Postinstallation Tasks............    6-2 E            Have you done?.....................................    6-2 E            Verifying the Server Installation..................    6-2 E            How to run the IVP.................................    6-2 :            Starting the DIGITAL PATHWORKS for OpenVMS FileE            Servers............................................    6-4 E            When to start the server...........................    6-4 E            What the startup procedure does....................    6-4 E            Troubleshooting the startup........................    6-5 E            Starting the File Servers..........................    6-5 E            Ways to start the server...........................    6-5 5            How to start the PATHWORKS Advanced Server E            manually...........................................    6-5 7            How to define LAN Manager server commands at E            login..............................................    6-6 E            How to start the NetWare server manually...........    6-6 E            How to define NetWare server commands at login.....    6-6 E            How to start the server automatically..............    6-7 E            How to start the server in an OpenVMS cluster......    6-7 E            Stopping the Server................................    6-8 E            When to stop the server............................    6-8 E            How to stop the server.............................    6-9 E            How to stop the server on system shutdown..........    6-9 E            Enabling External Authentication...................    6-9 E            Enabling External Authentication for VAX Systems...   6-10 E            Enabling External Authentication for a User........   6-11 E            Establishing User Host Mapping.....................   6-12 E            Synchronizing Passwords............................   6-13 E            External Authentication Over a Network.............   6-13 E            Configuring Externally Authenticated Clients.......   6-14 E            Setting up Shares..................................   6-14   (      7  Implementing a Wide Area Network  E            Implementing a Wide Area Network Using TCP/IP......    7-1 E            Planning and Setup.................................    7-2 E            LMHOSTS Directory..................................    7-2 E            LMHOSTS Syntax.....................................    7-2 E            Managing the LMHOSTS File..........................    7-4 E            LMHOSTS Log File...................................    7-4           vi                  H               Using a WINS Server in a Wide Area Network.........    7-4    1         8  Removing DIGITAL PATHWORKS for OpenVMS   H               Reasons for Removing the Server....................    8-1H               Why remove the server?.............................    8-1H               Removing the Server................................    8-2H               About the deinstallation command procedure.........    8-2H               How to run the deinstallation procedure............    8-2H               How to respond to prompts..........................    8-3:               Sample PATHWORKS Advanced Server and NetWareH               Removal Procedures.................................    8-46               Sample PATHWORKS Advanced Server removalH               procedure..........................................    8-4H               Sample NetWare removal procedure...................    8-5  >         A  Summary Checklist of Installation and Upgrade Tasks  <         B  Sample PATHWORKS Advanced Server Installation and"            Configuration Procedure  ;               Sample PATHWORKS Advanced Server Installation H               Procedure..........................................    B-1<               Sample PATHWORKS Advanced Server ConfigurationH               Procedure..........................................    B-4  ?         C  Sample NetWare Server Installation and Configuration             Procedure  H               Sample NetWare Server Installation Procedure.......    C-1H               Sample NetWare Server Configuration Procedure......    C-4  >         D  Sample PATHWORKS Advanced Server and NetWare Server)            Installation and Configurationi  ;               Sample Combined PATHWORKS Advanced Server and H               NetWare Server Installation Procedure..............    D-1;               Sample Combined PATHWORKS Advanced Server andIH               NetWare Configuration Procedures...................    D-5          H                                                                      vii s               9      E  Sample Standalone License Server Installation and          Configuration Proceduref  8            Sample Standalone License Server InstallationE            Procedure..........................................    E-1 9            Sample PATHWORKS Advanced Server Configuration E            Procedure for the Standalone License Server........    E-3 9            Sample NetWare Configuration Procedure for the E            Standalone License Server..........................    E-4   $      F  Upgrade Utility Installation  E            Installing the Upgrade Utility.....................    F-1 E            Sample Upgrade Utility Installation Procedure......    F-2         G  Files Installed   8            Files Common to PATHWORKS Advanced Server andE            NetWare............................................    G-1 =            Files Created During the PATHWORKS Advanced Server E            Installation.......................................   G-11aE            Files Created During the NetWare Installation......   G-15_5            PATHWORKS Advanced Server and NetWare DisktE            Structure..........................................   G-17g  <      H  PATHWORKS Advanced Server and NetWare Server Logical
         Namesf    $      I  NetWare Server Logical Names  E            How NetWare Logical Names Are Created..............    I-1 E            Types of NetWare Logical Names.....................    I-1 E            Common NetWare Logical Names.......................    I-2 E            Private NetWare Logical Names......................    I-3s  
      Index                	      viii  c  i                     Figuresi  H               G-1       Server On-Disk Structure Diagram.........   G-18           Tables  H               1-1       Preinstallation Checklist................    1-9  H               1-2       keep.....................................   1-17  H               2-1       Installation Options.....................    2-3  H               2-2       Installation Prompts.....................    2-9  ?               3-1       PATHWORKS Advanced Server ConfigurationeH                         Prompts..................................   3-10  ?               3-2       PATHWORKS Advanced Server ConfigurationPH                         Settings.................................   3-15  H               3-3       OpenVMS Network Device Logicals..........   3-17  H               4-1       NetWare Configuration Network Numbers....    4-3  H               4-2       External Network Types...................    4-4  ;               4-3       Types of Physical Network Media andsH                         NetWare Frame Types They Support.........    4-5  H               4-4       Configuration Prompts....................    4-6  H               5-1       PWRK$CONFIG Configuration Prompts........    5-4  H               5-2       PWVN$CONFIG Configuration Prompts........    5-7  H               8-1       PWRK$DEINSTAL Prompts....................    8-3  H               8-2       PWVN$DEINSTAL Prompts....................    8-4  H               A-1       Installation and Upgrade Checklist.......    A-1  A               G-1       Files Common to PATHWORKS Advanced Server,H                         and NetWare Server.......................    G-2  H               G-2       PATHWORKS Advanced Server Files..........   G-11  H               G-3       NetWare Files............................   G-15  :               H-1       DIGITAL PATHWORKS V6.0 for OpenVMSH                         (Advanced Server) Logical Names..........    H-1  H               I-1       Types of NetWare Logical Names...........    I-2  H               I-2       Common NetWare Logical Names.............    I-2  H               I-3       Private NetWare Logical Names............    I-3  H                                                                       ix                           H         ________________________________________________________________  H                                                                  Preface               About This Guide  E               This guide explains how to install and configure one or 6               more of the following PATHWORKS servers:  E               o  DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server).                  file server  C               o  DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare) fileq                  server.  4               o  PATHWORKS standalone license server           Audience  :               This guide is written for the network serverA               administrator. It assumes that the administrator is.@               familiar with the following aspects of the OpenVMS               operating system:   /               o  Digital Command Language (DCL).  2               o  A text editor, such as EDT or EVE  ,               o  VMSINSTAL command procedure  ?               This guide also assumes that the administrator iswC               familiar with the networking concepts appropriate forwB               the applicable DIGITAL PATHWORKS for OpenVMS server.          H                                                                       xi a  .                  Organization of This GuideM  C            The following list can help you find information in thise            guide:.  B            Chapter 1   Describes prerequisites to the installation!                        procedure.   <            Chapter 2   Describes the installation procedure.  D            Chapter 3   Describes the configuration procedure for the1                        PATHWORKS Advanced Server..  D            Chapter 4   Describes the configuration procedure for the&                        NetWare server.  D            Chapter 5   Describes the configuration procedure for the1                        standalone license server.   =            Chapter 6   Describes postinstallation tasks, such ?                        as running the Installation Verification1D                        Procedure and starting the server independent<                        of the installation and configuration"                        procedures.  B            Chapter 7   Describes how to set up Wide Area Networks.  D            Chapter 8   Describes how to remove DIGITAL PATHWORKS for0                        OpenVMS from your system.  =            Appendix A  Provides a summary of installation ando=                        configuration tasks. You can photocopy.B                        Appendix A and use it as a checklist as you'                        read this guide.t  D            Appendix B  Shows a sample installation and configurationC                        procedure for the PATHWORKS Advanced Server.N  D            Appendix C  Shows a sample installation and configuration8                        procedure for the NetWare server.  D            Appendix D  Shows a sample installation and configuration>                        procedure for a system running both the@                        PATHWORKS Advanced Server and the NetWare                        server.  D            Appendix E  Shows a sample installation and configurationC                        procedure for the standalone license server.         xii n  l              E               Appendix F  Explains how to install the Upgrade utility.H                           without installing any servers; shows a sample>                           installation of the Upgrade utility.  A               Appendix G  Lists the files that are installed withr8                           DIGITAL PATHWORKS for OpenVMS.  A               Appendix H  Lists the logical names created for the A                           Advanced Server and the NetWare server.P  A               Appendix I  Lists the logical names created for the .                           NetWare server only.                 Index            Related Documentsd  B               The following manuals provide more information about-               topics discussed in this guide:P  H               __________________________________________________________H               Document_Title________Description_________________________  F               DECprint Supervisor   Describes how to load the DECprintD               for OpenVMS Software  Supervisor software, install theF               Installation Guide    printing system, and test printing/                                     operations..  C               OpenVMS System        Describes the VMSINSTAL command E               Manager's Manual      procedure, UIC group numbers, and G                                     how to back up your OpenVMS system, E                                     requeue print and batch jobs, andT<                                     run the AUTOGEN utility.  A               OpenVMS System        Describes how to back up your 3               Management Utilities  OpenVMS system..               Reference Manual  ?               DIGITAL PATHWORKS     Explains how to upgrade the G               for OpenVMS           PATHWORKS for OpenVMS (LAN Manager) A               (Advanced Server)     software to DIGITAL PATHWORKS F               Server Migration      V6.0 for OpenVMS (Advanced Server)-               Guide                 software..  H                                                                     xiii .  .          E            __________________________________________________________4E            Document_Title________Description_________________________   E            DIGITAL PATHWORKS     Explains how to manage and customize B            for OpenVMS           the DIGITAL PATHWORKS for OpenVMS<            (Advanced             (Advanced Server) software.            Server) Server             Administrator's            Guide  E            DIGITAL PATHWORKS     Provides command syntax descriptions.<            for OpenVMS           for all ADMINISTER commandsA            (Advanced Server)     available with DIGITAL PATHWORKS C            Commands Reference    for OpenVMS (Advanced Server), andm:            Manual                Net command equivalences.  9            DIGITAL PATHWORKS     Provides an overview and <            for OpenVMS           introduction to the DIGITAL@            (Advanced Server)     PATHWORKS for OpenVMS (Advanced@            Concepts and          Server) software and associated?            Planning Guide        networking concepts for systemr>                                  administrators and operators.  <            PATHWORKS             Describes how to manage the@            for OpenVMS           PATHWORKS for OpenVMS (NetWare)*            (NetWare) System      software.            Administration Guide.  =            DIGITAL PATHWORKS     Describes the license serverKE            for OpenVMS Guide to  software and how to manage PATHWORKS.*            Managing PATHWORKS    licenses.E            Licenses__________________________________________________o        Conventions  D            The following conventions are used in the Advanced Server            documentation set.-  E            __________________________________________________________-E            Convention____Meaning_____________________________________   @            <Ctrl/x>      While you hold down the Ctrl key, pressA                          another key or a pointing device button.             xiv               H               __________________________________________________________H               Convention____Meaning_____________________________________  D               Italic        Indicates a place holder for informationD                             or parameters that you must provide. ForF                             example, if the procedure asks you to typeG                             file name, you must type the actual name of #                             a file.A  C                             Italic also indicates new terms and the.E                             titles of other documentation referenced..  D               monospace     Indicates the actual commands, words, orG                             characters that you type in a dialog box or.A                             at a command prompt or system output..  G               Note:         Provides information of special importance..  B               Caution:      Provides information to avoid damaging1                             software or hardware..  E               Warning:      Provides information that is essential tor,                             people's safety.  C               /             A forward slash in command descriptions G                             indicates that a command qualifier follows.a  G                . . .        A horizontal ellipsis following an entry inrH                             a command line indicates that the entry or aD                             similar entry can be repeated any numberB                             of times. An ellipsis following a fileF                             name indicates that additional parameters,B                             values, or information can be entered.  G               .             A vertical ellipsis in an example indicatesA;               .             that not all the data is shown. H               ._________________________________________________________                  H                                                                       xv .  .                  H                                                                        1H         ________________________________________________________________  H                         Before You Install DIGITAL PATHWORKS for OpenVMS      G               This chapter describes the hardware and software you mustmH               have and the tasks you need to complete before you install,               DIGITAL PATHWORKS for OpenVMS.  >               This chapter consists of the following sections:  <               o  About DIGITAL PATHWORKS for OpenVMS Servers                  o  About Licensing  *               o  Reading the Release Notes                 o  What You Need  &               o  Preinstallation Tasks  /               o  OpenVMS Cluster Considerations                  o  Next Step  H         ________________________________________________________________  3         About DIGITAL PATHWORKS for OpenVMS Serversp  @               The DIGITAL PATHWORKS for OpenVMS kit contains theE               software required to run the following server software:.  F               o  DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server),:                  the PATHWORKS Advanced Server file server  C               o  DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare), thet$                  NetWare file server  4               o  PATHWORKS standalone license server  H                     Before You Install DIGITAL PATHWORKS for OpenVMS 1-1           0      About DIGITAL PATHWORKS for OpenVMS Servers    @            In addition, the kit includes an Upgrade utility that=            helps you to migrate from PATHWORKS LAN Manager to8%            PATHWORKS Advanced Server.l  B            The VMSINSTAL procedure allows you to install either ofE            the file servers, both of the file servers, the standaloned@            license server, or only the PATHWORKS Advanced Server            Upgrade utility.A  E            If you have PATHWORKS for OpenVMS (LAN Manager) installed,.B            you must install the new PATHWORKS Advanced Server. YouD            can choose to install just the Upgrade utility initially,C            and install the PATHWORKS Advanced Server later. See thelA            DIGITAL PATHWORKS for OpenVMS (Advanced Server) Serverp0            Migration Guide for more information.  C            If you have any version of DIGITAL PATHWORKS for OpenVMS @            (NetWare) installed, you must install the new NetWare            server.  B            The license server is installed when you install eitherB            PATHWORKS Advanced Server or the NetWare server. If youB            choose not to install either file server, you can still1            install the standalone license server.f  E      ________________________________________________________________   )      Installing DIGITAL DECprint Software   E            DIGITAL DECprint Supervisor for OpenVMS, which is includedIC            in your software kit, is a printing system that providesl@            queue management and printing features for PostScript            printers.  E            If you plan to use DIGITAL DECprint Supervisor for OpenVMSfC            on your system, Digital Equipment Corporation recommends.C            that you install it before installing PATHWORKS AdvancedhB            Server. You must reboot the system after installing theC            DECprint software. You can perform the reboot as part ofnB            the DECprint Supervisor installation procedure or afterD            you install, but before you configure, PATHWORKS Advanced            Server.      9      1-2 Before You Install DIGITAL PATHWORKS for OpenVMSN a  .      H                                                          About Licensing  H         ________________________________________________________________           About Licensing1               LICENSE REQUIREMENTSA               The DIGITAL PATHWORKS for OpenVMS (Advanced Server)eH               requires that clients accessing file and print services beE               appropriately licensed. To conform to this requirement,r0               one of the following must be true:  E               o  The client must have acquired a client-based licensetB                  before connecting to a PATHWORKS Advanced Server.  G               o  The PATHWORKS Advanced Server must have a server-based.D                  license available to assign to an unlicensed clientE                  attempting to use services of the PATHWORKS Advancedc                  Server.  E               In both cases, the license required to access PATHWORKS.E               Advanced Server services is the PATHWORKS Client-Access &               license: PWLMXXXCA06.00.  G               If you are upgrading from PATHWORKS LAN Manager, refer to H               the DIGITAL PATHWORKS for OpenVMS (Advanced Server) ServerD               Migration Guide for information about upgrading client               license requests.O            ABOUT THE LICENSE SERVERE               The PATHWORKS license server is a software program that0E               you can run on your OpenVMS system to grant licenses to                clients.  2               The license server can be installed:  H               o  Separately from the file server (called the "standalone!                  license server")r  C               o  In conjunction with the file server (automaticallyt=                  included with your file server installation)   E               In either case, you can configure the license server tom               support:  $               o  LAN Manager clients                  o  NetWare clients  H                     Before You Install DIGITAL PATHWORKS for OpenVMS 1-3 .               About Licensing    D            Digital Equipment Corporation recommends that you installD            the license server on a designated OpenVMS system withoutE            the PATHWORKS file server, to ensure smooth and continuous B            operation of the license server. Therefore, the DIGITAL>            PATHWORKS for OpenVMS kit allows you to install theE            standalone license server separately from the file server. >            Alternatively, you can run the license server on anE            OpenVMS cluster with PATHWORKS file servers, where cluster.)            failover provides reliability.   C            Each LAN needs only one active PATHWORKS license server.e>            (The same license server can support both PATHWORKSB            LAN Manager and PATHWORKS Advanced Server clients.) TheC            license product authorization keys (PAKs) must be loaded @            on the system that runs the PATHWORKS license server.  @            In an OpenVMS cluster, the PAKs must be loaded into a#            shared license database.   E      FOR MORE_LICENSING_INFORMATION___________________________________            For more information E            about_._._.___________Refer_to_._._.______________________i  C            Loading licenses      OpenVMS License Management Utilitye'                                  Manual   D            Managing PATHWORKS    DIGITAL PATHWORKS for OpenVMS GuideE            licenses______________to_Managing_PATHWORKS_Licenses______D      E      ________________________________________________________________         Reading the Release Notes          ABOUT THE RELEASE NOTES=            The DIGITAL PATHWORKS for OpenVMS installation kite.            includes two sets of release notes:  B            o  DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server)               Release Notes       9      1-4 Before You Install DIGITAL PATHWORKS for OpenVMSu    L      H                                                Reading the Release Notes    F               o  DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare) Release                  Notes  E               Digital Equipment Corporation recommends that you print H               and read the appropriate release notes before starting the               installation.                  Note  E               The installation procedure moves the release notes into H               the SYS$HELP: area, where you can always locate them after7               server installation for future reference.s  '         HOW TO ACCESS THE RELEASE NOTES H               Use the following table to decide how to print the release               notes:  H               __________________________________________________________               If you wantvH               to_._._.______Then_._._.__________________________________  -               Print the     Do the following: D               DIGITAL       1. Load the installation kit on a drive.               PATHWORKSlF               Advanced      2. Enter the following commands, replacingF               Server           device with the name of the device (andF               Release          if the device is a disk, also designateB               Notes            the directory) where you loaded the0               before the       installation kit:0               installation  $ MOUNT device: PWRK  C                             $ BACKUP/SELECT=PWRK060.RELEASE_NOTES -R:                             _$ device:PWRK060.A/SAVE_SET *9                             $ PRINT PWRK060.RELEASE_NOTESn                      H                     Before You Install DIGITAL PATHWORKS for OpenVMS 1-5    n            Reading the Release Notes  E            __________________________________________________________l            If you wantE            to_._._.______Then_._._.__________________________________e  *            Print the     Do the following:A            NetWare       1. Load the installation kit on a drive.f            ReleaseC            Notes         2. Enter the following commands, replacingaA            before the       device with the name of the device oneB            installation     which you loaded the installation kit:  .                          $ MOUNT device: PWRKNA                          $ BACKUP/SELECT=PWVNV10G.RELEASE_NOTES - 7                          _$ device:PWRK060.A/SAVE_SET * 7                          $ PRINT PWVNV10G.RELEASE_NOTES   *            Print the     Do the following:A            release       1. Load the installation kit on a drive.a            notesD            during the    2. Enter the following command to start the3            installation     installation procedure:   <                          $ @VMSINSTAL PWRK060 device_name: -%                          _$ OPTIONS Na  B                          The installation procedure prompts you toC                          either print or display the release notes.eB                          In any case, the release notes are alwaysE            ______________copied_to_the_SYS$HELP:_area._______________h    E      ________________________________________________________________s         Using the Summary Checklist  @            Appendix A of this guide provides an installation andA            configuration summary checklist. You can photocopy the_B            summary checklist and use it to track the completion ofE            the installation and configuration tasks described in thisl            guide.             9      1-6 Before You Install DIGITAL PATHWORKS for OpenVMS            H                                                            What You Need  H         ________________________________________________________________           What You Need                HARDWARE REQUIREMENTS @               Make sure that the network (including cables, PCs,C               servers, and other hardware) is connected. For a listuD               of the hardware that the server supports, refer to theG               Software Product Description (SPD) that is appropriate tom               your file server.l           SOFTWARE REQUIREMENTSKH               To install DIGITAL PATHWORKS for OpenVMS successfully, youE               must have the following software properly installed and (               configured on your system:                 o  OpenVMS V7.1r                 o  DECnet   C                  DECnet is installed automatically with the OpenVMS "                  operating system.  "               o  TCP/IP (optional)  D                  DIGITAL TCP/IP Services for OpenVMS and a number ofF                  third-party TCP/IP products on OpenVMS can be used to$                  provide IP support.  H                  See the DIGITAL PATHWORKS for OpenVMS (Advanced Server)E                  Release Notes for a list of supported TCP/IP vendorse-                  and product version numbers.   1         PATHWORKS ADVANCED SERVER CLIENT SOFTWAREDF               DIGITAL PATHWORKS for OpenVMS (Advanced Server) supports>               connections from the following types of clients:                 o  Windows NTt                 o  Windows 95   '               o  Windows for Workgroupsd  .               o  PATHWORKS for DOS and Windows  )               o  PATHWORKS for Windows 95L                 o  PATHWORKS 32e  H                     Before You Install DIGITAL PATHWORKS for OpenVMS 1-7    d            What You Need          NETWARE CLIENT SOFTWARE;            DIGITAL PATHWORKS for OpenVMS (NetWare) supports ;            connections from the following types of clients:   B            o  PATHWORKS for DOS and Windows, Version 5.0 or higher  9            o  NetWare clients using NETX shell (V3.x,2.x)   4            o  NetWare clients using VLMS (V3.12,4.x)        MEMORY REQUIREMENTS@            The minimum amount of physical memory required to run?            PATHWORKS Advanced Server on Alpha systems is 64 MB.     E      ________________________________________________________________n        Preinstallation Tasks  9            Use the checklist in Table 1-1 to complete the_A            preinstallation tasks that are described later in thiss            section.n                                              9      1-8 Before You Install DIGITAL PATHWORKS for OpenVMS_ _  _      H                                                    Preinstallation Tasks    H               Table_1-1_Preinstallation_Checklist_______________________  /               <   >1.   Check the part listing.   H               <   >2.   Make sure that the network hardware is installed&                         and connected.  ?               <   >3.   Make sure that the required software is "                         installed.  5               <   >4.   Log in to the SYSTEM account.   1               <   >5.   Back up the system disks.   /               <   >6.   Read the release notes.s  G               <   >7.   Make sure that you have adequate disk space fora%                         installation.   0               <   >8.   Check system parameters.  0               <   >9.   Check the queue manager.  :               <   >10.  Check the time zone configuration.  D               <   >11.  Make sure that DECnet is running, if you are>                         planning to use PATHWORKS over DECnet.  D               <   >12.  Make sure that TCP/IP is running, if you are>                         planning to use PATHWORKS over TCP/IP.  G               <   >13.  Check the OpenVMS cluster configuration, if you H               __________are_installing_PATHWORKS_on_a_cluster.__________  G               Before you install DIGITAL PATHWORKS for OpenVMS, perform                these tasks:  &         STEP 1: CHECK THE PART LISTINGE               The software part listing specifies the contents of themE               kit you receive. Check the contents of your kit againstlC               that information. If parts are missing or your kit isiA               damaged, contact your Digital Equipment Corporationa               representative.b    H                     Before You Install DIGITAL PATHWORKS for OpenVMS 1-9                 Preinstallation Tasks    '      STEP 2: CHECK THE NETWORK HARDWARE >            DIGITAL PATHWORKS for OpenVMS runs on OpenVMS AlphaD            systems that meet the software requirements. The PC local'            area network (LAN) requires:s  D            o  A supported network controller board in the server and               in each client  >            o  The cables to connect each client to the network  (      STEP 3: CHECK THE REQUIRED SOFTWARE=            DIGITAL PATHWORKS for OpenVMS requires the OpenVMS >            operating system, Version 7.1 or higher. If you areB            going to use the PATHWORKS Advanced Server over DECnet,B            the license server over DECnet, the mail server, or IPXD            tunneling, you also need the DECnet network transport. IfC            you are going to use the TCP/IP transport, you must havepB            a TCP/IP transport product, as described in the DIGITALA            PATHWORKS for OpenVMS (Advanced Server) Release Notes.s  )      STEP 4: LOG IN TO THE SYSTEM ACCOUNT C            Before you install DIGITAL PATHWORKS for OpenVMS, log indD            to the SYSTEM account, which has sufficient privileges to,            start the installation procedure.  +            To log in to the SYSTEM account:_  4            1. At the Username: prompt, enter SYSTEM:                 Username: SYSTEM  <            2. At the Password: prompt, enter the password to?               the SYSTEM account. The password you enter is note               displayed.        STEP 5: BACK UP THE SYSTEMpB            To safeguard against the loss of valuable data, Digital@            Equipment Corporation recommends that you back up all>            disks on your system before you install any layered            product.W  E            To do a system backup, use the OpenVMS BACKUP command. ForD@            information about the BACKUP command, see the OpenVMS?            System Management Utilities Reference Manual and thei+            OpenVMS System Manager's Manual.   :      1-10 Before You Install DIGITAL PATHWORKS for OpenVMS P  W      H                                                    Preinstallation Tasks    0         STEP 6: PRINT AND READ THE RELEASE NOTESH               If you have not already read the release notes, you shouldC               do so before installing the software. See the section =               Reading the Release Notes for more information.     -         STEP 7: CHECK DISK SPACE REQUIREMENTSrC               On your OpenVMS Alpha system, the following amount ofnG               free disk space on the system disk is required during the H               installation procedure. (The disk space requirements shownC               include provision for the integrated license server.)   H               __________________________________________________________               With theseH               components_._._.______You_need_this_number_of_blocks_._._.  +               PATHWORKS Advanced    104,600W               Server only   *               NetWare server only   39,600  +               PATHWORKS Advanced    110,600                 Server and NetWare               server  +               Standalone license    104,600_               server  H               Upgrade_utility_only__27,100______________________________  D               To check the number of free blocks on the system disk,               enter:  )               $ SHOW DEVICE SYS$SYSDEVICE                  Result  F               The OpenVMS system displays information about the system8               disk, including the number of free blocks:  F               Device     Device     Error    Volume    Free  Trans MntF                Name      Status     Count     Label   Blocks Count CntF               DUA0:      Mounted        0  AXP062     724856   280   1    H                    Before You Install DIGITAL PATHWORKS for OpenVMS 1-11 t               Preinstallation Tasks    $      STEP 8: CHECK SYSTEM PARAMETERSE            Make sure that the following OpenVMS system parameters areI            set properly.              Note   ?            If these parameters are not set properly, you cannotgC            configure the server after you complete the installation_            procedure.               GBLPAGES parameter   A            The minimum value of this parameter on an Alpha systeme'            must be at least 7500 pages.l  C            To ensure that your system has enough free global pages:   "            1. Enter the following:  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")                 Result  C               The value of the GBLPAGES parameter is displayed. Forn               example:                 7500  ?            2. If the value is less than required, edit the file.@               SYS$SYSTEM:MODPARAMS.DAT and add a line similar to               the following:  !               ADD_GBLPAGES = 7500A               GBLSECTIONS parameter  C            The minimum value of this parameter differs depending on.-            which servers are to be installed:   E            __________________________________________________________             For the standaloneo            license server only,             or the NetWare D            server only, the      If the PATHWORKS Advanced Server isC            value must be at      to be installed, the value must be E            least_._._.___________at_least_._._.______________________O  E            50____________________75__________________________________   <            To ensure that your system has enough free global            sections:  :      1-12 Before You Install DIGITAL PATHWORKS for OpenVMS l  r      H                                                    Preinstallation Tasks    %               1. Enter the following:f  =                  $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")i                    Result   E                  The value of the GBLSECTIONS parameter is displayed.                   For example:                     75i  B               2. If the value is less than required, edit the fileC                  SYS$SYSTEM:MODPARAMS.DAT and add a line similar too                  the following:t  %                  ADD_GBLSECTIONS = 75y  #               PROCSECTCNT parametere  F               The minimum value of this parameter differs depending on0               which servers are to be installed:  H               __________________________________________________________                For the standalone"               license server only,               or the NetWareG               server only, the      If the PATHWORKS Advanced Server isrF               value must be at      to be installed, the value must beH               least_._._.___________at_least_._._.______________________  H               32____________________40__________________________________  >               To ensure that the value of the system parameter&               PROCSECTCNT is adequate:  %               1. Enter the following:k  ;                  $ WRITE SYS$OUTPUT F$GETSYI("PROCSECTCNT")t                    Result.  E                  The value of the PROCSECTCNT parameter is displayed.                   For example:                     40S  B               2. If the value is less than required, edit the fileC                  SYS$SYSTEM:MODPARAMS.DAT and add a line similar to_                  the following:a  %                  MIN_PROCSECTCNT = 40m  H                    Before You Install DIGITAL PATHWORKS for OpenVMS 1-13 A  O            Preinstallation Tasks                SCSNODE parameter  C            This parameter must be defined as your system's computer_C            name. If you are running DECnet, the SCSNODE name shouldt/            be the same as the DECnet node name.S  C            To check whether the system parameter SCSNODE is defined *            as your system's computer name:  ?            1. Enter the following command at the system prompt:   4               $ WRITE SYS$OUTPUT F$GETSYI("SCSNODE")                 Result  *               One of the following occurs:  <               o  If SCSNODE is defined, the computer name isB                  displayed. For example, if your system's computer                   name is HYDRAC:  $                    NAME = "HYDRAC  "  D               o  If SCSNODE is not defined, the computer name is not(                  displayed. For example:  $                    NAME = "        "  6            2. If SCSNODE is not defined, edit the file@               SYS$SYSTEM:MODPARAMS.DAT and define the parameter.D               For example, if your system's computer name is HYDRAC,C               edit the file so that it contains the following line:s                  SCSNODE = "HYDRAC"  @               If you edit the file SYS$SYSTEM:MODPARAMS.DAT, you@               must run the OpenVMS command procedure AUTOGEN andA               reboot the system either now or at some time before_2               configuring the server. For example:  =               $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACKa  "               For more information  D               For information about running AUTOGEN, see the OpenVMS&               System Manager's Manual.  A            The SCSNODE parameter's preinstallation status affects B            what happens after you install and configure the server-            and reboot the system, as follows:   :      1-14 Before You Install DIGITAL PATHWORKS for OpenVMS l  i      H                                                    Preinstallation Tasks  H         ________________________________________________________________         If SCSNODE    And H         is_._._.______you_._._._____Then_the_server_._._._______________  3         Not defined   Do not        Does not start.                        define itl  +         Already       Do not        Starts._         defined       define it_  B         Not defined   Define it     Starts, but the OpenVMS systemB                                     renames print and batch queuesE                                     to include the new computer name.eC                                     Therefore, you must requeue anynC                                     existing print or batch jobs toaE                                     the new queues. You may also haveiB                                     to rebuild the queue database.C                                     For information on these system E                                     management tasks, see the OpenVMS H         ____________________________System_Manager's_Manual.____________  '         STEP 9: CHECK THE QUEUE MANAGERoC               It is not necessary to have the queue manager runningrB               during installation, but it must be running when youH               configure the server. You can enter the SHOW QUEUE/MANAGERD               command to check whether the queue manager is running:  "               $ SHOW QUEUE/MANAGER                 Result  B               If the queue manager is running, your OpenVMS system:               displays a message similar to the following:  C               Queue manager SYS$QUEUE_MANAGER, running, on HYDRAC::.  B               If the queue manager is not running, you can use the,               following command to start it:  #               $ START/QUEUE/MANAGERf            H                    Before You Install DIGITAL PATHWORKS for OpenVMS 1-15                 Preinstallation Tasks    %      STEP 10: CHECK TIME ZONE AND TDFo?            You check the time zone and time differential factoreA            settings on your system by running the OpenVMS commandt=            procedure SYS$MANAGER:UTC$TIME_SETUP.COM. From the C            SYSTEM account, enter the following command to begin the             procedure:_  ,            $ @SYS$MANAGER:UTC$TIME_SETUP.COM  D            For more information on running the command procedure andB            resetting time zone and TDF, see the section on setting@            time zone information in the OpenVMS System Manager's            Manual:Essentials.e  !      STEP 11: CHECK DECNET STATUS @            It is not necessary to have DECnet running during theA            installation, but DECnet must be running on the system C            before you can configure the server, if you are planning D            to enable the DECnet transport. DECnet is required in the$            following configurations:  <            o  If you plan to use the Mail Server over DECnet  3            o  If clients will need to use eXcursiony  B            o  If you are configuring the server as a Backup Domain               Controller  &      CHECKING DECNET (PHASE IV) STATUSD            If you use DECnet (Phase IV), enter the following commandC            to see whether it is running on the system where you are 3            planning to install the server software:S                          :      1-16 Before You Install DIGITAL PATHWORKS for OpenVMS e         H                                                    Preinstallation Tasks    %               $ MCR NCP SHOW EXECUTORA    H               Table_1-2_keep____________________________________________                 If DECnete               (Phase IV)H               is_._._._____Then_._._.___________________________________  B               Running      The system displays State = on as shown!                            below:9  L                            Node Volatile Summary as of  16-SEP-1996 12:16:36  :                            Executor node = 12.691 (COBRAZ)  /                            State           = onDH                            Identification  = DECnet for OpenVMS AXP V7.1  G               Not running  You can enter the following command to start                             it:  2                            $ @SYS$MANAGER:STARTNET  H               __________________________________________________________  #         CHECKING DECNET-PLUS STATUSaG               If you use DECnet-Plus (formerly DECnet/OSI for OpenVMS),eF               enter the following command to see whether it is runningH               on the system where you are planning to install the server               software:i  /               $ SHOW LOGICAL NET$STARTUP_STATUSa  H         ________________________________________________________________         If DECnet H         is_._._._____Then_._._._________________________________________  )         Running      The system displays:   5                      "NET$STARTUP_STATUS" = "RUNNING- ,                      ALL" (LNM$SYSTEM_TABLE)  E         Not running  You can enter the following command to start it:   /                      $ @SYS$STARTUP:NET$STARTUPh  H         ________________________________________________________________  H                    Before You Install DIGITAL PATHWORKS for OpenVMS 1-17 n  l            Preinstallation Tasks    !      STEP 12: CHECK TCP/IP STATUS A            If you are planning to use PATHWORKS over TCP/IP, make @            sure that TCP/IP is running and that the PATHWORKS IPA            driver has been loaded. See the documentation for yourlD            TCP/IP product for information on how to check the status@            of TCP/IP and the PATHWORKS IP driver on your system.      E      ________________________________________________________________h  #      OpenVMS Cluster Considerations     1      STEP 13: CHECK OPENVMS CLUSTER CONFIGURATION.@            You can run DIGITAL PATHWORKS for OpenVMS on multipleC            OpenVMS cluster members (server nodes). To do so, follow.            these steps:.  B            1. On each system disk on which you want to run DIGITAL.               PATHWORKS for OpenVMS, complete:  4               o  The tasks described in this chapter  =               o  The VMSINSTAL command procedure described in                   Chapter 2  >            2. On each cluster member that you want to use as a=               PATHWORKS server, run the configuration commandyB               procedure (PWRK$CONFIG). This ensures that each node5               has enough resources to run the server.               Noteo  ?            An OpenVMS cluster cannot support both PATHWORKS LAN 1            Manager and PATHWORKS Advanced Server.9  C            An OpenVMS cluster can include both VAX and Alpha memberNE            nodes. However, in order to enable external authenticationV?            on a VAX node, you must perform additional steps, as B            described in Enabling External Authentication , in this            guide.w      :      1-18 Before You Install DIGITAL PATHWORKS for OpenVMS           H                                                                Next Step  H         ________________________________________________________________           Next Step   B               To install DIGITAL PATHWORKS for OpenVMS, proceed to               Chapter 2.                                                                                H                    Before You Install DIGITAL PATHWORKS for OpenVMS 1-19 o                     H                                                                        2H         ________________________________________________________________  H                                 Installing DIGITAL PATHWORKS for OpenVMS      ?               This chapter describes how to install the DIGITALMC               PATHWORKS for OpenVMS software. You must follow theseiG               procedures regardless of whether you are upgrading from a E               previous version of the server or installing the server,!               for the first time.r  D               Before you begin the installation procedure, make sureF               that you have completed the preinstallation tasks listed               in Chapter 1.   >               This chapter consists of the following sections:  1               o  About the Installation Proceduret  5               o  Determining What Software to Installd  &               o  Installing the Server                 o  Next Steps   H         ________________________________________________________________  (         About the Installation Procedure           WHAT IS VMSINSTAL?H               VMSINSTAL is the standard command procedure for installingA               software on the OpenVMS operating system. VMSINSTALPG               consists of a series of questions (prompts). Your answers G               to these questions provide VMSINSTAL with the informationEB               needed for installing DIGITAL PATHWORKS for OpenVMS.          H                             Installing DIGITAL PATHWORKS for OpenVMS 2-1 o         %      About the Installation Procedureo          VMSINSTAL INSTALLATION KIT B            The VMSINSTAL installation kit includes several OpenVMSC            BACKUP save sets. The save set PWRK060.A always containse8            the file KITINSTAL.COM and the release notes.          WHAT VMSINSTAL DOES&            When you use VMSINSTAL, it:  C            1. Creates DIGITAL PATHWORKS for OpenVMS accounts on the_(               file server, if necessary.  :            2. Restores the files from the save sets in the               installation kit.b  E            3. Creates DECnet objects, if you are running DECnet Phase                IV.   .            4. Installs PATHWORKS DCL commands.  A            5. Creates DIGITAL PATHWORKS for OpenVMS logical namesd               definition files.   %            6. Deletes obsolete files.0  B            7. Places the files in the directories that you specify#               during the procedure.   ;            8. Verifies that the software has been installed,B               successfully. (See Verifying the Server Installation<               for information on how to run the InstallationD               Verification Procedure after installing the software.)  E      ________________________________________________________________V  )      Determining What Software to Install   C            DIGITAL PATHWORKS for OpenVMS (Advanced Server) includes C            PATHWORKS Advanced Server and PATHWORKS NetWare options. D            The software you install depends upon the clients in your            configuration.s  B            o  If your configuration includes PATHWORKS LAN Manager<               clients or retail LAN Manager clients, install1               PATHWORKS Advanced Server software.s  1      2-2 Installing DIGITAL PATHWORKS for OpenVMS     n      H                                     Determining What Software to Install    A               o  If your configuration includes PATHWORKS NetWaresB                  clients or retail NetWare clients and you want toC                  use your PATHWORKS server to support them, installp,                  PATHWORKS NetWare software.  B               o  If your configuration includes both PATHWORKS LAND                  Manager or retail LAN Manager clients and PATHWORKSH                  NetWare clients or retail NetWare clients, and you wantD                  to use your PATHWORKS server to support the NetWareG                  as well as LAN Manager clients, install both PATHWORKSo@                  Advanced Server and PATHWORKS NetWare software.  F               Depending upon the software on your existing system, youE               can install the license server only. If you install the B               NetWare server only, the license server is included.B               If you install the Advanced Server only, or AdvancedH               Server and NetWare server, the license server is included.F               Table 2-1, Installation Options, indicates which options               you can choose.a                 Note  D               If you are running the NetWare server and the AdvancedG               Server, you must upgrade both servers. If you are runningsD               V4.x, you must upgrade to V5.0 before installing V6.0.  H         Table_2-1_Installation_Options__________________________________  F                                 License   Advanced            AdvancedH         Existing      Upgrade   Server    Server    NetWare   Server andH         System________Only______Only______Only______Only______NetWare___  A         LAN Manager   Yes       No        Yes       No[1]     Yesp         server
         V5.0x   A         NetWare       No        No        No[2]     Yes       Yes          server         V1.0F and.         earliere  H         [1]You_must_upgrade_to_Advanced_Server._________________________  /         [2]You must upgrade the NetWare server.e  H                                                 (continued on next page)  H                             Installing DIGITAL PATHWORKS for OpenVMS 2-3 _  _      )      Determining What Software to Install     E      Table_2-1_(Cont.)_Installation_Options__________________________   C                              License   Advanced            AdvancedvE      Existing      Upgrade   Server    Server    NetWare   Server andtE      System________Only______Only______Only______Only______NetWare____  >      LAN Manager   Yes       No        No[2]     No[1]     Yes      server_      V5.0x and      NetWare      serverh
      V1.0F or       earlier  =      PATHWORKS     No        No        No        No        No.
      V4.x foro      OpenVMS[3]   E      [1]You_must_upgrade_to_Advanced_Server._________________________R  ,      [2]You must upgrade the NetWare server.;      [3]You must upgrade to PATHWORKS V5 for OpenVMS first.eE      ________________________________________________________________n    E      ________________________________________________________________         Installing the Server          BEFORE YOU START VMSINSTAL C            Before you start the VMSINSTAL command procedure, answerI#            the following questions:   -            1. What is the product identifier?   D               The product identifier tells VMSINSTAL which save setsA               to copy from the media to a disk on the system. ThehB               product identifier for DIGITAL PATHWORKS for OpenVMS               is:T                 PWRK060m  A            2. What is the name of the device on which you want ton               mount the media?  1      2-4 Installing DIGITAL PATHWORKS for OpenVMS     R      H                                                    Installing the Server    A                  The device name depends on the type of media and G                  computer you have. For example, if you want to mount a'E                  CD-ROM on the CD-ROM drive of your Alphastation 400, 1                  the device name might be DKA400.d  F               3. Do you want to access the online release notes during,                  the installation procedure?  C                  You can tell VMSINSTAL to ask you whether you want$D                  to display or print the online release notes duringE                  installation. Because the release notes may describefA                  important changes to the installation procedure,DG                  Digital Equipment Corporation recommends that you readAE                  them. Procedures for obtaining the release notes ared(                  described in Chapter 1.  F               4. Do you want to install the standalone license server?  B                  If the system is designated to run the standaloneC                  license server, you can install the license serveroH                  software only. Digital Equipment Corporation recommendsH                  that you run the license server on a designated license                  server system.   C                  The installation procedure gives you the option to D                  install the standalone license server software fromE                  the DIGITAL PATHWORKS for OpenVMS kit. In this case,PG                  the DIGITAL PATHWORKS for OpenVMS file servers are not_D                  installed. If any PATHWORKS file server software isE                  installed, you cannot install the standalone licensee                  server.  E               5. Do you want to install DIGITAL PATHWORKS for OpenVMSo3                  (Advanced Server) server software?_  ?                  If you have V5.0 of PATHWORKS for OpenVMS (LANtC                  Manager) installed, you must install V6.0. See thesG                  DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 6                  Migration Guide for more information.  ?                  If you have V4.x of PATHWORKS for OpenVMS, you A                  must upgrade to V5.0 before installing V6.0. For A                  instructions on upgrading from V4.x to V5.0, seetE                  the PATHWORKS for OpenVMS Server Migration Guide for                   OpenVMS V5.  G               6. Do you want to install the DIGITAL PATHWORKS V1.0F for_3                  OpenVMS (NetWare) server software?_  H                             Installing DIGITAL PATHWORKS for OpenVMS 2-5 r  o            Installing the Server    E               If you have a previous version of PATHWORKS for OpenVMS 3               (NetWare), you must upgrade to V1.0G.E  >            7. Do you want to install just the Upgrade utility?  A               To migrate to the Advanced Server, you must upgrade B               your LAN Manager databases. If you choose to installD               just the Upgrade utility, you can install the Advanced@               Server later, after you upgrade your databases. IfC               you install the Advanced Server software, the Upgradee(               utility is also installed.  B            8. Do you want to preserve the PATHWORKS V5 for OpenVMS:               (LAN Manager) environment, and if so, where?  >            9. What is the User Identification Code (UIC) group               number?o  <               The DIGITAL PATHWORKS for OpenVMS installationA               procedure creates an OpenVMS account, PWRK$DEFAULT,nB               if necessary. The default selection displayed in the;               installation dialog is determined as follows:i  E               _______________________________________________________PE               If_._._.______________The_default_is_._._._____________e  B               You are installing    The first available unused UICD               DIGITAL PATHWORKS     group number, starting with 360.!               for OpenVMS for the                first time  A               An account named      The same group number as thatt@               PCFS$ACCOUNT already  associated with the existing9               exists                account PCFS$ACCOUNT.u  <               An account named      The same group number as=               PWRK$DEFAULT already  the existing PWRK$DEFAULT ?               exists                and PWRK$GUEST accounts, in E               ______________________preference_to_PCFS$ACCOUNT.______u        HOW TO START VMSINSTALa            To start VMSINSTAL:  B            1. Ensure that you are logged in to the SYSTEM account.  B            2. Load the installation kit media onto a drive. (It isA               not necessary to mount the drive, but it must be onnD               line so that the installation procedure can mount it.)  1      2-6 Installing DIGITAL PATHWORKS for OpenVMS            H                                                    Installing the Server    G               3. Enter the following command to check the status of the_F                  device on which you have loaded the installation kit,F                  replacing device_name with the name of the applicable                  device:  *                  $ SHOW DEVICE device_name                    For example:   '                  $ SHOW DEVICE $1$DUS0:   M                  Device             Device  Error  Volume  Free    Trans  Mnt M                   Name              Status  Count  Label   Blocks  Count  Cnt M                  $1$DUS0: (HSC001)  Mounted     0  HUBSYS  347718    628    4   E                  If the device status is Offline, enter the followingdF                  command to place the device online, replacing device_3                  name with the name of your device:_  3                  $ SET DEVICE/AVAILABLE device_name   <               4. Change the default directory to SYS$UPDATE:  )                  $ SET DEFAULT SYS$UPDATE   @               5. Start VMSINSTAL and specify the PWRK060 product>                  identifier, the media device, and whether youC                  want access to the online release notes during theT(                  installation procedure:  H         ________________________________________________________________H         If_you_._._.______________Then_enter_._._.______________________  H         Want access to the        @VMSINSTAL PWRK060 device_name OPTIONS#         release notes during the  N          installation procedure  @         Do not want access        @VMSINSTAL PWRK060 device_name         to the release notes         during the installation H         procedure_______________________________________________________        H                             Installing DIGITAL PATHWORKS for OpenVMS 2-7                 Installing the Server    $      HOW INSTALLATION QUESTIONS WORK<            An asterisk (*) at the beginning of a line in the@            installation procedure identifies a question you must            answer.  >            Usually, a question has a default answer, which the@            procedure displays within square brackets ([]) at the            end of the question.o  <            To accept a default, press <Return>. For example:  =            * Are you satisfied with the backup of your system             disk [YES]? <Return>L  &      HOW TO INTERRUPT THE INSTALLATIONE            To interrupt the installation procedure, press <Ctrl/Y> atrC            any time. Then you can restart the installation from the             beginning.         HOW TO RESPOND TO PROMPTS<            Table 2-2 tells you how to respond to the prompts            VMSINSTAL displays.              Noter  B            Table 2-2 shows only the prompts VMSINSTAL displays; itC            does not show any informational messages. For a complete =            sample installation script, see Appendix D, SampleoD            PATHWORKS Advanced Server and NetWare Server Installation            and Configuration.                               1      2-8 Installing DIGITAL PATHWORKS for OpenVMSp M  l      H                                                    Installing the Server    H         Table_2-2_Installation_Prompts__________________________________  *                            If you want the1         At this            installation procedureAH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Are you            Continue                     <Return>         satisfied with         the backup off         your system disk         [YES]?  :                            Exit                         NO  9         Select option      Display the release notes    1_C         [2]:[1]            on the screen                To stop theT  F                                                         display at anyC                                                         time, press A                                                         <Ctrl/C>.   @                            Print the release notes      <Return>  C                                                         The release_E                                                         notes file istC                                                         sent to therE                                                         default printnH                                                         queue SYS$PRINT.E                                                         You can enter C                                                         the name ofeE                                                         another printu>                                                         queue.  H         [1]This_prompt_is_displayed_only_if_you_specify_OPTIONS_N_when__  H         you start the VMSINSTAL command procedure or if there are active          processes on the system.  H                                                 (continued on next page)            H                             Installing DIGITAL PATHWORKS for OpenVMS 2-9 _  _            Installing the Server    E      Table_2-2_(Cont.)_Installation_Prompts__________________________A  '                         If you want thet.      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____i  6                         Print the release notes      3@                         and display them on the      To send theE                         screen                       release notes to   B                                                      another printE                                                      queue, enter theTD                                                      name of anotherA                                                      print queue.c  @                                                      To stop theC                                                      screen display A                                                      at any time,hD                                                      press <Ctrl/C>.  6                         Continue without             4@                         displaying or printing       The release>                         the release notes            notes are  B                                                      automatically>                                                      copied to>                                                      SYS$HELP.  =      Do you want        Install one or more          <Return>g      to install the     servers       Upgrade utility      only [NO]?[2]  8                         Install only the Upgrade     YES                         utilityn  E      [2]This_prompt_is_displayed_only_if_your_system_is_currently____e  ;      running the previous version of PATHWORKS for OpenVMS._  E                                              (continued on next page)o        2      2-10 Installing DIGITAL PATHWORKS for OpenVMS (  a      H                                                    Installing the Server    H         Table_2-2_(Cont.)_Installation_Prompts__________________________  *                            If you want the1         At this            installation procedurenH         prompt_._._._______to_._._._____________________Enter_._._._____  ;         Do you want to     Continue                     YESl         continue the         installation         [NO]?[1]  @                            Exit                         <Return>  ;         Do you want        Install the Advanced         YESs!         to install         Serverl         the DIGITALy         PATHWORKS          for OpenVMSH         (Advancedp         Server) [NO]?   @                            Omit the Advanced Server     <Return>  @         Do you want to     Retain the V5 (LAN           <Return>/         preserve the V5    Manager) environment .         (LAN Manager)      so that you can use2         environment        the rollback procedures2         [YES]?[2]          described in the Server*                            Migration Guide  :                            Not retain the V5            NO&                            environment    H         [1]This_prompt_is_displayed_only_if_you_specify_OPTIONS_N_when__  H         you start the VMSINSTAL command procedure or if there are active          processes on the system.D         [2]This prompt is displayed only if your system is currently>         running the previous version of PATHWORKS for OpenVMS.  H                                                 (continued on next page)      H                            Installing DIGITAL PATHWORKS for OpenVMS 2-11 f  u            Installing the Server    E      Table_2-2_(Cont.)_Installation_Prompts__________________________   '                         If you want theu.      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____   =      Enter the          Preserve the environment     <Return>c0      directory to       in the default directory      preserve the       shown       V5 environmenty!      [SYS$SYSDEVICE:[000000]]:[3]_  @                         Preserve the V5              A differentB                         environment on another       device and/or?                         device and/or in another     directory. !                         directory   8      Do you want        Install the NetWare server   YES      to install the       NetWare serverd
      [NO]?  =                         Omit the NetWare server      <Return>n  E      [3]This_prompt_is_displayed_only_if_you_chose_to_preserve_the___T  8      PATHWORKS V5 for OpenVMS (LAN Manager) environment.  E                                              (continued on next page)_                                2      2-12 Installing DIGITAL PATHWORKS for OpenVMS v  e      H                                                    Installing the Server    H         Table_2-2_(Cont.)_Installation_Prompts__________________________  *                            If you want the1         At this            installation procedureeH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Do you want        Install the standalone       <Return>C         to install         license server               This option_D         the PATHWORKS                                   installs theF         license server                                  license serverE         [YES]?[4]                                       and transport_  H                                                         software withoutA                                                         a DIGITALtE                                                         PATHWORKS forqD                                                         OpenVMS fileE                                                         server. Refer D                                                         to Chapter 5@                                                         for moreD                                                         information.  :                            Install a PATHWORKS file     NOC                            server with the license      This option B                            server                       causes the  D                                                         installationA                                                         procedure A                                                         to repeatuD                                                         the previousG                                                         questions aboutiF                                                         installing theE                                                         file servers,iC                                                         so that youaF                                                         can select oneD                                                         or both file@                                                         servers.  @         Is the selection   Use the selection            <Return>         correct [YES]?  H         [4]This_prompt_is_displayed_only_if_you_chose_to_install_neither  =         the PATHWORKS Advanced Server nor the NetWare server.n  H                                                 (continued on next page)  H                            Installing DIGITAL PATHWORKS for OpenVMS 2-13                 Installing the Server    E      Table_2-2_(Cont.)_Installation_Prompts__________________________   '                         If you want theo.      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____T  7                         Change the selection         NOe  =                         Terminate the installation   <Ctrl/Y>   =      Will you allow a   Shut down the system         <Return> .      system shutdown    as part of the product.      after this         installation procedure      product iso      installed [YES]?A  7                         Complete the installation    NO)D                         procedure without shutting   System shutdown@                         down the system              is required  D                                                      for the productE                                                      installation. IfmC                                                      you answer NO, B                                                      you must shutD                                                      down the systemC                                                      manually after E                                                      the installationnA                                                      procedure ise>                                                      finished.  =      Do you want to     Reboot the system            <Return>n2      do an automatic    automatically after system       system reboot      shutdown      [YES]?   7                         Reboot the system manually   NO   =      Do you want        Run the Installation         <Return> .      to run the         Verification Procedure1      IVP after the      (IVP) automatically aftery2      installation is    the installation procedure!      finished [YES]?    completesc  E                                              (continued on next page)   2      2-14 Installing DIGITAL PATHWORKS for OpenVMS p  d      H                                                    Installing the Server    H         Table_2-2_(Cont.)_Installation_Prompts__________________________  *                            If you want the1         At this            installation procedure H         prompt_._._._______to_._._._____________________Enter_._._._____  :                            Not run the IVP              NO  ?                                                         You cannC                                                         run the IVP F                                                         independent ofH                                                         the installationB                                                         procedure.D                                                         For detailedF                                                         information onG                                                         running the IVP F                                                         independently,F                                                         see How to runC                                                         the IVP, inhB                                                         Chapter 6.  @         Do you want        Purge all files it           <Return>#         to purge files     replacesW         replaced by this         installation         [YES]?  :                            Not purge any files it       NO#                            replacesi  @         Do you want to     Delete the files and         <Return>4         continue with      continue the installation         the installation         [YES]?[5]   :                            Leave the files intact and   NO5                            terminate the installation   H         [5]This_question_is_displayed_only_if_there_are_PATHWORKS_files_  '         in system-specific directories.d  H                                                 (continued on next page)    H                            Installing DIGITAL PATHWORKS for OpenVMS 2-15                 Installing the Server    E      Table_2-2_(Cont.)_Installation_Prompts__________________________0  '                         If you want thee.      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____   =      Do you want        Shut down the license        <Return>1/      to shut down       server and continue thes$      the PATHWORKS      installation      license serverm      [YES]?[6]  7                         Keep the server running      NOi)                         and terminate the $                         installation  =      Do you want        Shut down the server and     <Return>:1      to shut down       continue the installation       the PATHWORKS      Advanced Server      [YES]?[6]  7                         Keep the server running      NOe)                         and terminate theh$                         installation  =      Do you want        Shut down the server and     <Return>_1      to shut down       continue the installation       the PATHWORKS      NetWare serverr      [YES]?[6]  7                         Keep the server running      NOL)                         and terminate thes$                         installation  E      [6]This_question_is_displayed_only_if_a_server_is_running.______d  E                                              (continued on next page)             2      2-16 Installing DIGITAL PATHWORKS for OpenVMS _  _      H                                                    Installing the Server    H         Table_2-2_(Cont.)_Installation_Prompts__________________________  *                            If you want the1         At this            installation procedure H         prompt_._._._______to_._._._____________________Enter_._._._____  @         Enter default      Associate the newly          <Return>*         UIC group          created OpenVMS0         number for         accounts PWRK$DEFAULT.         PWRK$DEFAULT and   and PWRK$GUEST with+         PWRK$GUEST[nnn]:   the default user 4                            identification code (UIC)-                            group number (nnn)N  E                            Associate the newly          A three-digit C                            created accounts with        UIC number. D                            the UIC group number you     For detailedC                            specify                      informationL  G                                                         about UIC grouptD                                                         numbers, seeC                                                         the OpenVMSAH                                                         System Manager's?                                                         Manual.   @         NetWare SYS        Keep the same SYS volume     <Return>#         volume             location          location"         [device:[PWVN$SYSVOL]]:[7]  C                            Specify a different          A different F                            SYS volume location for      disk device orB                            NetWare                      directory.  H         [7]This_question_is_displayed_only_if_NetWare_is_being__________           installed.  H                                                 (continued on next page)            H                            Installing DIGITAL PATHWORKS for OpenVMS 2-17 e  o            Installing the Server    E      Table_2-2_(Cont.)_Installation_Prompts__________________________h  '                         If you want the .      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____   =      Do you want        Copy new files onto the      <Return> +      to copy new        existing SYS volumeR      files onto       the existing       NetWare SYS      volume [YES]?[8]   7                         Leave the existing SYS       NOe'                         volume as it is   E      [8]This_question_is_displayed_only_if_NetWare_is_being_installed   )      and there is an existing SYS volume. E      ________________________________________________________________     E      ________________________________________________________________         Next Steps           WHAT TO DO NEXT:            To continue, depending on which servers you are/            installing, do one of the following:   E      ________________________________________________________________a@                                              Which tells you howE      If_you_are_._._.____Proceed_to_._._.____to_._._.________________n  D      Installing the      Chapter 3           Configure the PATHWORKS=      PATHWORKS Advanced                      Advanced Server.l      ServerP  B      Installing the      Chapter 4           Configure the NetWare4      NetWare server                          server.        2      2-18 Installing DIGITAL PATHWORKS for OpenVMS           H                                                               Next Steps  H         ________________________________________________________________C                                                 Which tells you how H         If_you_are_._._.____Proceed_to_._._.____to_._._.________________  H         Installing the      Chapter 5           Configure the standalone?         standalone license                      license server.          server  G         Upgrading from      DIGITAL PATHWORKS   Use the Upgrade utility B         PATHWORKS V5        for OpenVMS         to create and edit@         for OpenVMS (LAN    (Advanced Server)   upgrade reports.,         Manager)            Server Migration!                             Guide   E         Upgrading from      PATHWORKS V5        Install the PATHWORKS C         PATHWORKS V4 for    for OpenVMS         V5 for OpenVMS (LAN @         OpenVMS             Installation and    Manager) server.H         ____________________Upgrade_____________________________________  4         INSTALL OPTIONAL SERVER ADMINISTRATION TOOLSA               After you install and configure the server, you can E               install client-based server management tools that allow C               you to manage the server from Windows 95, Windows for C               Workgroups, and Windows NT clients. After you installi@               and configure the PATHWORKS Advanced Server, theseE               tools are available in the pwutil share in the svrtoolsoH               subdirectory (SYS$UPDATE:PWRK$PWUTIL.SAV). For informationG               on installing client-based server management tools, refer =               to the README.TXT file supplied with the tools.   D               After you configure the server, you may need to rebootE               the system for the configuration to take effect. If youaF               have installed the optional server administration tools,F               this system reboot activates the server and the optional&               software simultaneously.                      H                            Installing DIGITAL PATHWORKS for OpenVMS 2-19                       H                                                                        3H         ________________________________________________________________  H          Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server)H                                                                   Server      C               This chapter describes how to configure the PATHWORKSaE               Advanced Server and consists of the following sections:A  B               o  About the PATHWORKS Advanced Server Configuration                  Procedure  ?               o  Before You Start the PATHWORKS Advanced Serverd(                  Configuration Procedure  ;               o  How to Start the PATHWORKS Advanced Server (                  Configuration Procedure  <               o  How to Respond to PATHWORKS Advanced Server&                  Configuration Prompts  F               o  How to Change PATHWORKS Advanced Server Configuration!                  Default Settings   G               o  Selecting the PATHWORKS Advanced Server Network Deviceo                 o  Next Steps   H         ________________________________________________________________  C         About the PATHWORKS Advanced Server Configuration Procedure                   H  the          DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-1 h  e      @      About the PATHWORKS Advanced Server Configuration Procedure    )      WHAT IS THE CONFIGURATION PROCEDURE? >            The PATHWORKS Advanced Server initial configurationB            procedure, PWRK$CONFIG.COM, is installed by the DIGITAL8            PATHWORKS for OpenVMS installation procedure.  =            Like the installation procedure, the configuration B            procedure asks you a series of questions (by displayingE            prompts). The procedure uses your answers to configure thee%            PATHWORKS Advanced Server.   *      WHAT THE CONFIGURATION PROCEDURE DOES3            PWRK$CONFIG is a command procedure that:   6            o  Creates the PATHWORKS on-disk structure.  A            o  Creates the PATHWORKS Advanced Server user accountseA               and shares databases (that is, access control listsr               (ACLs)).  E            o  Allows you to enter the Configuration Manager to modify E               system configuration parameters, such as the transports C               the server will run and the maximum number of clients <               that can connect to the server simultaneously.  ?            o  Allows you to modify server configuration default B               settings such as server role, domain name, and which#               services are enabled._  C            o  Allows you to set or change the Administrator account                password.e  :            o  Gives you the option of starting the server.  A            After you install the server, you must run PWRK$CONFIG B            before you can start the server. In an OpenVMS cluster,B            you must run PWRK$CONFIG on each individual node before>            you can start the server. (Although the nodes in anA            OpenVMS cluster function as a single unit in a domain, E            you need to treat them as individual units for purposes of             configuration.)              For more information   C            Read the information on the Configuration Manager in the (            Server Administrator's Guide.  O      3-2 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server            H   Before You Start the PATHWORKS Advanced Server Configuration Procedure  H         ________________________________________________________________  D         Before You Start the PATHWORKS Advanced Server Configuration         Procedure.  H               Before you start the PWRK$CONFIG command procedure, answer&               the following questions:  E               1. On what OpenVMS disk device do you want to store the 0                  following PATHWORKS data files?  1                  o  Configuration parameter files   -                  o  License server data files                     o  Log files   '                  o  Printer spool files   %                  o  Server data files   0                  o  Virtual memory section files  H                  By default, the configuration procedure copies the dataF                  files to the disk device SYS$SYSDEVICE:. However, youF                  can specify any existing OpenVMS disk device that has;                  at least 12,000 free blocks of disk space.                     Note   E                  The server frequently accesses the data files copiedrG                  to the specified disk device, which generates input torH                  and output from the disk. Having these operations occurG                  on the system disk can degrade the performance of bothhF                  the OpenVMS system and the server. Therefore, DigitalD                  Equipment Corporation recommends that you specify a8                  disk device other than the system disk.  F                  On an OpenVMS cluster with multiple system disks, allF                  nodes on which you plan to run PATHWORKS must use theF                  same disk device to store and access PATHWORKS files.  ?               2. Do you want to change the system configuration_                   parameters now?  H                  If you respond "yes" to the prompt to change the systemF                  configuration parameters, you enter the ConfigurationE                  Manager. The Configuration Manager is a utility that F                  allows you to modify server configuration parameters,G                  such as the maximum number of clients that can connecte  H  the          DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-3    s      K      Before You Start the PATHWORKS Advanced Server Configuration Procedure     C               to the server and which network transports the server                uses.   "               For more information  D               For detailed information about using the ConfigurationA               Manager, refer to the Configuration Manager chapterhD               in the DIGITAL PATHWORKS for OpenVMS (Advanced Server)@               Server Administrator's Guide. For more informationB               about transports, refer to Network Protocols chapterD               in the DIGITAL PATHWORKS for OpenVMS (Advanced Server)+               Server Administrator's Guide.   <               Whether or not you choose to change the systemD               configuration at this time, you can change it later byC               entering the ADMINISTER/CONFIG command at the OpenVMS                system prompt:  !               $ ADMINISTER/CONFIGt                 Note  @               If you are configuring a server as a Backup Domain@               Controller (BDC), during the initial configuration@               you must select at least one transport for the BDC=               that will also be run by its PDC. Otherwise theo&               configuration will fail.  >               If you are configuring a BDC to join an existingA               domain, and the PDC of the domain is on a different D               IP subnet, with both BDC and PDC configured to use the5               TCP/IP transport, you have two options:t  D               -  Configure both the BDC and PDC to use a WINS ServerC                  for NetBIOS name registration and resolution. This 4                  is the most straightforward method.  E               -  Configure the BDC and PDC to use LMHOSTS for NetBIOS @                  name resolution. If you choose this option, you>                  must ensure that the entry for the PDC exists>                  in the LMHOSTS file on the BDC before you runB                  PWRK$CONFIG.COM. If there is no entry for the PDCB                  in the LMHOSTS file on the BDC when you configureE                  the BDC, the BDC will fail to find the PDC and hence 2                  fail to join the existing domain.  O      3-4 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Servere n  ,      H   Before You Start the PATHWORKS Advanced Server Configuration Procedure    =                     The LMHOSTS file, or in the case of a new C                     installation, an LMHOSTS template file, will be B                     available in the PWRK$LANMAN: directory on theE                     server. For more information on adding entries tol4                     the LMHOSTS FILE, see Chapter 7.  A                     For more information on configuring PATHWORKS C                     Advanced Server to use WINS or LMHOSTS, see the @                     Configuration Manager section in the DIGITALB                     PATHWORKS for OpenVMS (Advanced Server) Server*                     Administrator's Guide.  F               3. Do you want to change any of the server configuration<                  default settings? These settings determine:  3                  o  Whether the license server runs   E                     The license server is a software program that youID                     can run on your OpenVMS system to grant licensesC                     to clients. Any client that wants to use server_A                     resources must have a valid license. Each LAN G                     needs only one PATHWORKS license server. The clientoE                     license product authorization keys (PAKs) must be H                     loaded on the system that runs the PATHWORKS license                     server.W  E                     In an OpenVMS cluster, the PAKs must be loaded on D                     all nodes that run the PATHWORKS license server.E                     This is best accomplished by adding the PAKs to ao,                     shared license database.  @                     By default, the license server does not run.  (                     For more information  B                     For detailed information on managing PATHWORKSA                     licenses, see the Guide to Managing PATHWORKSt                     Licenses.   7                  o  Whether the Timesource service runsw  D                     The Timesource service allows your server to actB                     as a time server. Other servers on the networkF                     can synchronize with the time server to coordinateG                     network events (for example, running batch programsrF                     on all computers the same time each day). Each LAN/                     needs only one time server.n  D                     By default, the Timesource service does not run.  H  the          DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-5 C  .      K      Before You Start the PATHWORKS Advanced Server Configuration Procedureo    1               o  Whether the Alerter service runsc  D                  The Alerter service sends messages called alerts toD                  servers and clients that run the Messenger service.  6                  By default, the Alerter service runs.  >               o  Names of the users who receive alert messages  ;                  By default, alert messages are sent to thet'                  Administrator account.f  9               o  Whether the Netlogon service is enabled.n  @                  In a domain, the Netlogon service distributes aB                  domain-wide user accounts database to all servers@                  running Netlogon. The service allows for single?                  domain-wide logon that enables users to access 7                  resources on any server in the domain.   7                  By default, the Netlogon service runs.   6               o  PATHWORKS Advanced Server domain name  =                  This is the PATHWORKS Advanced Server domain ?                  in which your server is located. A domain is arC                  subdivision of clients and servers on the network.   @                  The default Advanced Server domain is LANGROUP.  #               o  Role of the server   A                  This is the server's role in the domain. You can @                  designate a PATHWORKS Advanced Server as eitherD                  the Primary Domain Controller or as a Backup DomainD                  Controller. In an OpenVMS cluster, all nodes on the1                  cluster must have the same role.g  8               o  PATHWORKS Advanced Server computer name  D                  This is the unique name that identifies your serverB                  in a PATHWORKS Advanced Server domain. You defineC                  this name or accept the default value when you runa-                  the configuration procedure.   E                  By default, the Advanced Server computer name is thei.                  server's DECnet network name.  (               o  PATHWORKS cluster alias  O      3-6 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server  s  g      H   Before You Start the PATHWORKS Advanced Server Configuration Procedure    E                     If your server is a member of an OpenVMS cluster, D                     this is the network name that all servers in theE                     cluster use. The alias lets remote nodes (such astG                     clients) treat the entire cluster as though it were_C                     a single server. For example, a client user can_H                     specify the PATHWORKS alias to connect to any serverD                     in the cluster; the user does not know (and doesC                     not need to know) to which server the client is_                     connected.  E                     The default PATHWORKS cluster alias is the DECnet "                     cluster alias.  +                  o  Server announce commentl  E                     This is the comment the PATHWORKS Advanced ServerAC                     sends out when it announces its presence on theIH                     network. This comment may also be shown when you useH                     an interface to display a list of available servers.  C                     The default server announce comment is "DIGITAL @                     PATHWORKS V6 for OpenVMS (Advanced Server)."  %                  For more information_  G                  Unless otherwise specified, you can find more detailed F                  information on any of the services or concepts listedE                  above in the DIGITAL PATHWORKS for OpenVMS (Advanced 6                  Server) Server Administrator's Guide.  D                  For detailed information on changing default serverD                  configuration settings, see How to Change PATHWORKSD                  Advanced Server Configuration Default Settings , in                  this chapter.  <               4. What is the Administrator account password?  B                  The configuration procedure prompts you to define=                  a password for the PATHWORKS Advanced ServerME                  Administrator account, from which you administer thenE                  server. Passwords are case-sensitive and can contain_G                  up to 14 alphanumeric characters as well as any of theIG                  following special characters: ! # $ % & () - . ^ _ ` {a                  } ~  H  the          DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-7 g  h      K      Before You Start the PATHWORKS Advanced Server Configuration Procedurei                   Note  A               If your server will be a primary domain controller, 9               enter the password to the domain's existings$               Administrator account.  .            5. Do you want to start the server?  >               The configuration procedure asks you if you want>               to start the server. If you do not want to start?               the server at this time, you can do so later fromt@               the command line after the configuration procedure               completes.                 Note  >               Do not start the server during the configuration9               procedure if any of the following are true:   E               o  You still need to run the PATHWORKS V5 (LAN Manager)                   server.  C                  The configuration procedure shuts down the server.   C               o  You may need to run the PATHWORKS V5 (LAN Manager)_-                  server again for any reason._  ?                  File access problems may occur if you stop thecD                  PATHWORKS Advanced Server and restart the PATHWORKS)                  V5 (LAN Manager) server.a  B               o  You are installing the server on multiple OpenVMS!                  cluster members.n  C                  Before you start the server on any OpenVMS clusternA                  member, Digital Equipment Corporation recommendsoA                  that you configure DIGITAL PATHWORKS for OpenVMSiA                  on each cluster member that you want to use as adE                  server. You can then use the SYSMAN utility to startHE                  the server simultaneously on all cluster members. IfiD                  you choose to start the server individually on eachB                  cluster member, make sure that you do so from the4                  SYSTEM account on each server node.  "               For more information  E               For detailed information on alternate ways to start the_A               server, see Starting the File Servers in Chapter 6.d  O      3-8 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Serverr e  r      H       How to Start the PATHWORKS Advanced Server Configuration Procedure  H         ________________________________________________________________  @         How to Start the PATHWORKS Advanced Server Configuration         Proceduret  E               After the installation procedure completes, the OpenVMSd?               system prompt ($) is displayed. If the system wast.               rebooted following installation:  E               1. Ensure that you are logged in to the SYSTEM account.s  ?               2. Start the configuration procedure by entering:   *                  $ @SYS$UPDATE:PWRK$CONFIG    H         ________________________________________________________________  A         How to Respond to PATHWORKS Advanced Server Configurationd         Promptsr  D               Table 3-1 tells you how to respond to the prompts that#               PWRK$CONFIG displays.                  Note  G               Table 3-1 shows only the prompts PWRK$CONFIG displays; itaF               does not show any informational messages. For a completeA               sample configuration script, see Appendix B, SampleeF               PATHWORKS Advanced Server Installation and Configuration               Procedure.                              H  the          DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-9 _         F      How to Respond to PATHWORKS Advanced Server Configuration Prompts    E      Table_3-1_PATHWORKS_Advanced_Server_Configuration_Prompts_______e  '                         If you want thee/      At this            configuration procedureoE      prompt_._._._______to_._._._____________________Enter_._._._____   =      Do you want to     Shut down the server or,     <Return>a1      continue with      if your server is part of /      configuration      an OpenVMS cluster, allo.      [YES]:[1]          servers in the cluster  7                         Abort the configuration      NO !                         procedure   =      Enter disk         Copy the PATHWORKS on-       <Return> -      device name        disk structure to the ,      where PATHWORKS    default OpenVMS disk(      data files         device displayed1      will be stored     If you ran PWRK$CONFIG or /      [default_device]:  PWVN$CONFIG previously,_  2                         the default disk device is1                         the one you specified thee0                         last time you configured#                         the server.O  @                         Copy the PATHWORKS on-disk   device_name/                         structure to an OpenVMSe2                         disk device different from-                         the default displayed   =                         Keep the existing            <Return>v-                         Administrator account                           password  E      [1]This_prompt_is_displayed_only_if_the_server_is_running.______o  E                                              (continued on next page)u              P      3-10 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server ,  u      H        How to Respond to PATHWORKS Advanced Server Configuration Prompts    A         Table 3-1 (Cont.) PATHWORKS Advanced Server Configuration H         __________________Prompts_______________________________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Do you want        Enter the Configuration      <Return>D         to change          Manager tool                 For detailedC         the server                                      information G         configuration                                   about using the E         parameters now?                                 ConfigurationdF         [YES]:                                          Manager, refer  F                                                         to the DIGITALA                                                         PATHWORKSmC                                                         for OpenVMScA                                                         (AdvancedtF                                                         Server) ServerG                                                         Administrator'su>                                                         Guide.  :                            Not enter the                NO0                            Configuration Manager  @         Enter item         Accept the configuration     <Return>/         number, or         parameters displayed          RETURN to usep         these values         [DONE]:   H                                                 (continued on next page)                          H  the         DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-11           F      How to Respond to PATHWORKS Advanced Server Configuration Prompts    >      Table 3-1 (Cont.) PATHWORKS Advanced Server ConfigurationE      __________________Prompts_______________________________________e  '                         If you want ther/      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____   ?                         Change the default           The number D                         configuration settings       associated withB                         displayed                    a setting youD                                                      want to change.  A                                                      For detailedn@                                                      information@                                                      on changingB                                                      these defaultB                                                      configurationB                                                      settings, seeB                                                      How to Change>                                                      PATHWORKSD                                                      Advanced ServerB                                                      ConfigurationE                                                      Default Settingsd>                                                      , in this=                                                      chapter.e  =      Enter              Associate a password with    passwordTC      Administrator      the Administrator account    If your serverfD      network account                                 will be part ofD      password:                                       a domain, enter  D                                                      the password toA                                                      the domain'sS=                                                      existingeB                                                      Administrator=                                                      account.   =      Re-enter to                                     password       verify password:n  E                                              (continued on next page)i        P      3-12 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server           H        How to Respond to PATHWORKS Advanced Server Configuration Prompts    A         Table 3-1 (Cont.) PATHWORKS Advanced Server ConfigurationoH         __________________Prompts_______________________________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____    ;         Do you want        Prompt you to enter a        YESo4         to enter a new     new Administrator account#         Administrator      passwordp         account password         [NO]:[2]  @         Do you want to     Start the server             <Return>2         start DIGITAL      automatically after the1         PATHWORKS V6 for   installation procedureE$         OpenVMS on node    completes         node_name nowe         [YES]:[3]o  :                            Not start the server         NOH         [2]This_prompt_is_displayed_if_you_ran_PWRK$CONFIG_previously.__  B         [3]This prompt is displayed only if the PATHWORKS Advanced@         Server can be started without first executing AUTOGEN or         rebooting the system.SH         ________________________________________________________________  H         ________________________________________________________________  E         How to Change PATHWORKS Advanced Server Configuration Default          Settings  E               After you change system configuration parameters duringSE               the configuration procedure, you exit the Configuration G               Manager. The configuration procedure then displays a listeH               of server configuration default settings and a prompt that0               lets you change them; for example:            H  the         DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-13 t  o      K      How to Change PATHWORKS Advanced Server Configuration Default Settings     L        PATHWORKS V6.0 for OpenVMS is presently configured to run as follows:  +         1.  Run the license server:      NO +         2.  Enable Timesource service:   NOi,         3.  Enable Alerter service:      YES6         3a. Alert user names:            Administrator)         4.  Enable Netlogon service:  YESd-         5.  Advanced Server domain:  LANGROUP *         6.  Advanced Server role:  PRIMARY1         7.  Advanced Server computer name: COBRAZs9         7a. PATHWORKS OpenVMS cluster alias: COBRAZ_ALIASsT         8.  Server announce comment:    PATHWORKS V6.0 for OpenVMS (Advanced Server)=      Enter item number, or RETURN to use these values [DONE]:e  B            To change a server configuration default setting, enterA            the number of the setting you want to change. A prompth?            is then displayed that lets you change that setting.a@            Table 3-2 describes possible values for each setting.  B            To save the settings after you complete your changes orB            to accept the settings displayed, press <Return> to useE            the default answer DONE. For information on completing theeE            rest of the configuration procedure, see How to Respond tocD            PATHWORKS Advanced Server Configuration Prompts , in this            chapter.               Notev  B            Item 3a is displayed only if your response to item 3 is            YES.               For more informatione  B            For a description of each server configuration setting,=            see Before You Start the PATHWORKS Advanced Servers5            Configuration Procedure , in this chapter.                   P      3-14 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server    e      H   How to Change PATHWORKS Advanced Server Configuration Default Settings    H         Table_3-2_PATHWORKS_Advanced_Server_Configuration_Settings______  H         Setting_________________________Possible_Values_________________  D         1. Run the license server:      Enter YES to run the licenseH                                         server, or press <Return> to use7                                         the default NO.u  ?         2. Enable Timesource service:   Enter YES to enable the D                                         Timesource service, or pressG                                         <Return> to use the default NO.a  G         3. Enable Alerter service:      Enter NO to disable the AlerterrE                                         service, or press <Return> toe<                                         use the default YES.  F         3a. Alert user names:[1]        Enter the names of users, eachG                                         containing up to 20 characters,TG                                         who can receive alert messages,tF                                         and separate them with commas.  H         4. Enable Netlogon service:     Enter NO to disable the NetlogonE                                         service, or press <Return> toh<                                         use the default YES.  G         5. Advanced Server domain:      Enter a domain name of up to 15 E                                         characters, or press <Return> G                                         to use the default. The defaultoD                                         domain name is LANGROUP. YouH                                         must supply a unique domain name8                                         within your LAN.  B         6. Advanced Server role:        Enter PRIMARY to designateA                                         the server as the primaryrC                                         domain controller or BACKUPOD                                         to designate the server as aA                                         backup domain controller.t  H         [1]Displayed_only_if_Alerter_service_is_enabled.________________  H                                                 (continued on next page)        H  the         DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-15 e  n      K      How to Change PATHWORKS Advanced Server Configuration Default SettingsH    >      Table 3-2 (Cont.) PATHWORKS Advanced Server ConfigurationE      __________________Settings______________________________________   E      Setting_________________________Possible_Values_________________c  @      7. Advanced Server computer     Enter a computer name of up?      name:                           to 15 characters, or presssA                                      <Return> to use the default.rB                                      The default displayed is yourC                                      system's DECnet name. However, @                                      if your system's DECnet andD                                      NETBIOS names are different andA                                      the NETBIOS name is the nodeHB                                      name, enter the NETBIOS name.  D      7a. PATHWORKS OpenVMS cluster   Enter a PATHWORKS cluster aliasE      alias:[2]                       for the OpenVMS cluster to which B                                      your server belongs, or pressE                                      <Return> to use the default, thea;                                      OpenVMS cluster alias.s  ?      8. Server announce comment:     Enter the text of up to 48oA                                      characters that you want thee?                                      server to send out when it B                                      announces its presence on theB                                      network, or press <Return> to5                                      use the default. E      [2]Displayed_only_in_an_OpenVMS_cluster.________________________d  E      ________________________________________________________________     E      ________________________________________________________________   ;      Selecting the PATHWORKS Advanced Server Network Device   A            The configuration procedure selects the network device B            depending on the transport you specify when you run theE            procedure. If the server has more than one network device,nD            and you do not want to use the device selected, or if theD            server has a network device that is not recognized by theA            PATHWORKS Advanced Server, you can manually select theiB            network device to use with the transport you specified.    P      3-16 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server    e      H                   Selecting the PATHWORKS Advanced Server Network Device    @               Table 3-3 lists OpenVMS logical names that you can>               use to control the network device over which theD               PATHWORKS server operates. You must add these logicalsH               to SYS$MANAGER:SYLOGICALS.COM to have them available after               rebooting.    H               Table_3-3_OpenVMS_Network_Device_Logicals_________________  H               Logical_Name____________________Transport_________________  4               NETBIOS$DEVICE                  DECnet  4               PWRK$KNBDAEMON_DEVICE           TCP/IP  H               PWRK$NETBEUI_DEVICE_____________NetBEUI___________________  G               For example, to select device EWA0: for DECnet transport,oF               enter the following command before you start the server:  2               $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:  H         ________________________________________________________________           Next Steps  G               You can start the PATHWORKS Advanced Server automatically A               as part of the configuration procedure. However, if_D               you are installing the NetWare server as well, you canA               complete the NetWare configuration procedure before D               rebooting the system and starting the servers. NetWare6               configuration is described in Chapter 4.  F               If you are upgrading from PATHWORKS LAN Manager, performF               the upgrade procedures described in the Server Migration               Guide.  H               If you are ready to start the server, see Chapter 6, AfterG               You Install the DIGITAL PATHWORKS for OpenVMS Servers for                instructions.e          H  the         DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-17    w                  H                                                                        4H         ________________________________________________________________  H           Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server      H               This chapter describes how to configure the NetWare server5               and consists of the following sections:c  :               o  About the NetWare Configuration Procedure  2               o  NetWare Configuration Information  <               o  Running the NetWare Configuration Procedure  1               o  Reconfiguring the NetWare Serverd  =               For an example of a complete configuration, seeu@               Appendix C, Sample NetWare Server Installation and&               Configuration Procedure.  H         ________________________________________________________________  1         About the NetWare Configuration Procedureo  ,         WHAT IS THE CONFIGURATION PROCEDURE?2               The NetWare configuration procedure,E               SYS$UPDATE:PWVN$CONFIG.COM, is installed by the DIGITAL D               PATHWORKS for OpenVMS installation procedure. Like theF               installation procedure, the configuration procedure asksE               you a series of questions. The procedure then uses your F               answers to configure the PATHWORKS for OpenVMS (NetWare)               file server.                H       Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-1 h  p      .      About the NetWare Configuration Procedure    *      WHAT THE CONFIGURATION PROCEDURE DOES'            The configuration procedure:   6            o  Creates the PATHWORKS on-disk structure.  B            o  Allows you to specify a NetWare file server name andE               checks the file server name you provide for conformance.)               with NetWare naming syntax.   A            o  Allows you to specify an alternate location for the_*               NetWare configuration files.  B            o  Allows you to configure the NetWare Virtual Terminal               (NVT).  A            o  Allows you to run the license server on the system.E  B            o  Allows you to configure up to eight NetWare networksC               and verifies that the network numbers you provide are 2               valid (8-digit) hexadecimal numbers.  >            o  Writes your answers into configuration files and.               logical name command procedures.  >               For the logical names and their definitions, see?               Appendix H, PATHWORKS Advanced Server and NetWare A               Server Logical Names and Appendix I, NetWare Server                Logical Names.  !      WHEN TO CONFIGURE THE SERVER E            You must configure the NetWare server after you install it D            and before you start it for the first time. In an OpenVMSC            cluster, you must configure the server on each node that )            will run the PATHWORKS server.   E      ________________________________________________________________   &      NetWare Configuration Information              G      4-2 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server     f      H                                        NetWare Configuration Information             ABOUT NETWORK NUMBERSuH               A network number (address) is a unique 8-digit hexadecimalG               number used by the NetWare operating system to identify aT               network.  H               When you configure the server, the configuration procedureC               asks you to specify network numbers for your internalR2               network (LAN) and external networks.            TYPES OF NETWORK NUMBERSH               Table 4-1 describes the two types of configuration network               numbers.    H               Table_4-1_NetWare_Configuration_Network_Numbers___________  H               Number________Description_________________________________  F               Internal      The internal network number is the 8-digitF               network       hexadecimal number that you assign to yourG               number        file server. This number must be unique for 6                             each file server on a LAN.  C                             If you do not enter an internal network ?                             number, the configuration procedure F                             calculates one from the DECnet node numberD                             for the OpenVMS system. If the system isD                             not running DECnet, the default value is%                             00000DEC.   C               External      Also called the IPX network number, theTF               network       external network number is a unique numberH               number        that is used by the file server to route IPX$                             packets.  E                             All the file servers on one LAN share the A                             same network number. This number is a D                             hexadecimal number that corresponds to aH               ______________physical_network_interface_and_a_frame_type.            H       Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-3 s  r      &      NetWare Configuration Information          TYPES OF EXTERNAL NETWORKS B            Table 4-2 describes the two types of external networks,            tunnel and local.    E            Table_4-2_External_Network_Types__________________________n  E            Type__________Description_________________________________   @            Tunnel        Also called an IPX DECnet tunnel in the?            network       PWVN$CONFIG.COM procedure, a tunnel isv@                          a point-to-point connection between twoB                          servers on different networks. The tunnelB                          connects two or more IPX networks over anB                          existing DECnet network that carries onlyD                          DECnet traffic. This is often used for Wide+                          Area connectivity._  D                          Each tunnel network must be identified by aC                          number different from the internal networktA                          number and unique among NetWare external @                          network numbers in the LAN environment.  D            Local         A local network is a group of file servers,C            network       workstations, and peripheral devices, suchyB                          as printers, that share the same physical7                          network media in a local area.6  @                          You can have only one local network perE            ______________physical_network_interface._________________   3      NUMBER AND TYPES OF NETWORKS YOU CAN CONFIGUREmE            You can configure a maximum of eight external networks for D            any one NetWare server. The external networks can contain@            any combination of local networks and tunnels up to a            total of eight.  &      ABOUT TOKEN RING AND FDDI SUPPORT9            If you have Token Ring or FDDI interfaces, the_A            configuration procedure detects them and allows you to A            configure them for the NetWare server. Table 4-3 shows @            the physical network media that are supported and the@            frame types they support. Frame types define how dataC            is encapsulated at the data-link level of the OSI model.aA            The frame type you select during configuration must bea  G      4-4 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server  e         H                                        NetWare Configuration Information    G               compatible with the physical network media in use in your $               current configuration.    C               Table 4-3 Types of Physical Network Media and NetWare H               __________Frame_Types_They_Support________________________  0                                       IEEE-802.2H               Media_______DIX_SNAP____(SAP_E0)____RAW-802.3_____________  ?               Token Ring  Supported   Supported   Not Supported.  ?               FDDI        Supported   Supported   Not Supportedt  H               Ethernet____Supported___Supported___Supported_____________    H         ________________________________________________________________  3         Running the NetWare Configuration Proceduree    /         WHEN TO RUN THE CONFIGURATION PROCEDUREfF               You need to run the configuration procedure if you have:  C               o  Turned the system into an OpenVMS cluster. In thisuG                  case, you must run the configuration procedure on eachrE                  node in the cluster that will be running the NetWareu                  server.  ?               o  Altered the external network by adding networkt9                  interface cards or changing frame types.   .         HOW TO RUN THE CONFIGURATION PROCEDURE1               To run the configuration procedure:   -               1. Enter the following command:   *                  $ @SYS$UPDATE:PWVN$CONFIG  G               2. Respond to the configuration questions as shown in How 8                  to respond to prompts, in this chapter.      H       Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-5 A  O      0      Running the NetWare Configuration Procedure    %      HOW CONFIGURATION QUESTIONS WORK <            An asterisk (*) at the beginning of a line in theA            configuration procedure identifies a question you mustr*            answer to configure the server.  >            Usually, a question has a default answer, which the@            procedure displays within square brackets ([]) at theD            end of the question. To accept a default, press <Return>.        HOW TO GET ONLINE HELP C            To get online help on a specific configuration question, 8            enter a question mark (?) after the question.    '      HOW TO INTERRUPT THE CONFIGURATIONaE            You can interrupt the configuration procedure at any time.rD            To interrupt the configuration procedure, press <Ctrl/Y>.        HOW TO RESPOND TO PROMPTS<            Table 4-4 tells you how to respond to the prompts             PWVN$CONFIG displays.              Notet  =            Table 4-4 shows only the prompts; it does not show <            any informational messages. For a complete sample?            configuration script, see Appendix C, Sample NetWarei;            Server Installation and Configuration Procedure.   E      Table_4-4_Configuration_Prompts_________________________________   '                         If you want the /      At this            configuration procedureaE      prompt_._._._______to_._._._____________________Enter_._._._____r  =      Do you want to     Shut down the server or,     <Return> 1      continue with      if your server is part of /      configuration      an OpenVMS cluster, all .      [YES]:[1]          servers in the cluster  E      [1]This_prompt_is_displayed_only_if_you_started_the_server______h        previously.  E                                              (continued on next page)   G      4-6 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server            H                              Running the NetWare Configuration Procedure    H         Table_4-4_(Cont.)_Configuration_Prompts_________________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  :                            Abort the configuration      NO$                            procedure  @         Enter disk         Copy the PATHWORKS on-       <Return>0         device name        disk structure to the/         where PATHWORKS    default OpenVMS diskr+         data files         device displayedh4         will be stored     If you ran PWRK$CONFIG or2         [default_device]:  PWVN$CONFIG previously,  5                            the default disk device is_4                            the one you specified the3                            last time you configured_&                            the server.  C                            Copy the PATHWORKS on-disk   device_namet2                            structure to an OpenVMS5                            disk device different from 0                            the default displayed  @         Name of DIGITAL    Use the default server       <Return>         PATHWORKS          name          for OpenVMSs         (NetWare) file         server [server-          name]:  F                            Use another server name      Server name to;                                                         uset      H                                                 (continued on next page)            H       Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-7           0      Running the NetWare Configuration Procedure    E      Table_4-4_(Cont.)_Configuration_Prompts_________________________   '                         If you want theS/      At this            configuration procedurenE      prompt_._._._______to_._._._____________________Enter_._._._____         System-specific      directory#      [SYS$SPECIFIC:[PWVN$PRIVATE]]:o  =                         Use the default device and   <Return>s!                         directory   ?                         Use another device or        Device and A                         directory                    directory to_8                                                      use  =      Do you want to     Not allow clients using      <Return> *      configure NVT      the Novell Virtual)      on this system     Terminal protocolg
      [NO]?  8                         Allow clients using the      YES/                         Novell Virtual Terminal                           protocol  =      Do you want to     Not run the license server   <Return>       run a License      Server on this       system [NO]?   8                         Run the license server       YES  =      Internal           Use the default internal     <Return>P&      network number     network number      (hexadecimal)      [network_
      number]:t  E                                              (continued on next page)H          G      4-8 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Servern h  A      H                              Running the NetWare Configuration Procedure    H         Table_4-4_(Cont.)_Configuration_Prompts_________________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  G                            Use another internal         Correct network_>                            network number               number  @         Maximum SPX        Use no more than 50          <Return>"         sockets [50]:      sockets  H                            Use a greater number of      50, 200, 500, or<                            sockets                      1000  @         Network            Allow you to enter a new     <Return>0         Configuration      network configuration         Action (ADD)         [ADD]:[2]O  /                            To proceed, at least_.                            one network must be0                            configured. A maximum3                            of eight networks can be &                            configured.  @         Network Type       Configure a new local        <Return>"         (LOCAL,            network         TUNNEL,NONE)         [L]:[3]b  9                            Configure a new tunnel       Te"                            network  <                            Not configure a new          NONE"                            network  H         [2]This_prompt_is_displayed_only_if_there_are_no_NetWare________  $         networks configured already.E         [3]This prompt is displayed only if you are configuring a new          network.  H                                                 (continued on next page)  H       Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-9    7      0      Running the NetWare Configuration Procedure    E      Table_4-4_(Cont.)_Configuration_Prompts__________________________  '                         If you want the /      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____w  =      Choose a Network   Configure a new network      <Return>h+      controller from    based on controllero      above listing      [controller]:[3]   9                         Not configure a new          NONE D                         network                      When you select  E                                                      NONE, the dialogo?                                                      returns toa@                                                      the NetworkB                                                      ConfigurationB                                                      Action prompt  =      Enter 5 for        Use the default frame type   <Return>W"      Ethernet_II        (DIX/SNAP)      (DIX), 6 forP      802.2 (Sap E0),      or 7 for RAW-      802.3 [5]:[3]  6                         Use the IEEE-802.2 frame     6                         type  6                         Use the RAW-802.3 type       7  E      Network Number     Use the unique network       n, a hexadecimal B      [0]:[3]            number                       value greater;                                                      than 0O  =      Network            Store the displayed          <Return>e)      Configuration      configuration andW0      Action             finish the configuration!      (ADD,DELETE,       procedure       MODIFY,NONE)h      [NONE]:  E      [3]This_prompt_is_displayed_only_if_you_are_configuring_a_new___r  
      network.   E                                              (continued on next page)   H      4-10 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server a  r      H                              Running the NetWare Configuration Procedure    H         Table_4-4_(Cont.)_Configuration_Prompts_________________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  ;                            Add a new network            ADDd  >                            Delete a network             DELETE  >                            Modify the configuration     MODIFY1                            of an existing network   @         Do you want        Reboot the system            <Return>2         to reboot the      automatically after the2         system now         configuration procedure$         [YES][4]:          completes  :                            Not reboot the system        NO  2                            After the configuration3                            procedure completes, youc1                            must reboot the systemt3                            before you can start the *                            NetWare server.  @         Do you want to     Start the server             <Return>2         start DIGITAL      automatically after the2         PATHWORKS          configuration procedure$         for OpenVMS        completes         (NetWare) nowf         [YES]:  :                            Not start the server         NO  @         Is this            Retain the settings          <Return>$         configuration      displayed         satisfactory         [YES]?  :                            Change the configuration     NOH         [4]This_prompt_is_displayed_only_if_it_is_necessary_to_reboot___  D         the system to reload the streams execlet or the PCFS driver.H         ________________________________________________________________  H      Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-11 r  o      0      Running the NetWare Configuration Procedure           HOW TO CONFIRM YOUR ANSWERS9            After you have answered all the questions, theeE            configuration procedure displays a summary of your choicesi3            and prompts you to confirm your choices.b              It then asks you:  6            * Is this configuration satisfactory [YES]?  E            __________________________________________________________nE            If_you_are_._._.___Then_._._._____________________________o  ;            Satisfied with     Press <Return> to answer YES.h            the configuration            summary  D            Not satisfied      Answer NO to change any of the values.E            with the           The configuration procedure prompts you0-            configuration      for each value.eE            summary___________________________________________________t  D            When you are done with the configuration procedure, startC            the server, as described in Chapter 6, After You Install.5            the DIGITAL PATHWORKS for OpenVMS Servers.     E      ________________________________________________________________u  %      Reconfiguring the NetWare Servere    "      HOW TO RECONFIGURE THE SERVER?            You can reconfigure the server at any time after thee3            installation. To reconfigure the server:H  -            1. Stop the server and transports.   .            2. Run the configuration procedure.  .            3. Start the server and transports.  C            For information about starting and stopping the servers, E            see Chapter 6, After You Install the DIGITAL PATHWORKS for_            OpenVMS Servers._  H      4-12 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server    A      H                                         Reconfiguring the NetWare Server    (         NEW CONFIGURATION VALUE LOCATIONC               When you enter new configuration values, some of them G               are stored as new logical name definitions in the logicaleG               name command procedure. The new definitions supersede theEF               previous definitions. However, the previous logical nameG               definitions remain in the files, thus providing a history_+               of the configuration changes.o                                                                            H      Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-13 e  t                  H                                                                        5H         ________________________________________________________________  H                   Configuring and Starting the Standalone License Server      E               The PATHWORKS license server is a software program thatdE               you can run on your OpenVMS system to grant licenses tol               clients.  1               You can install the license server:_  0               o  Separately from the file server  4               o  In conjunction with the file server  E               In either case, you can configure the license server tot               support:  $               o  LAN Manager clients                  o  NetWare clients  G               Digital Equipment Corporation recommends that you installIG               the license server on a designated OpenVMS system withoutpH               the PATHWORKS file server, to ensure smooth and continuousE               operation of the license server. Therefore, the DIGITALiA               PATHWORKS for OpenVMS kit allows you to install theFH               standalone license server separately from the file server.A               Alternatively, you can run the license server on an H               OpenVMS cluster with PATHWORKS file servers, where cluster,               failover provides reliability.  B               Typically, each LAN needs only one PATHWORKS license?               server. (The same license server can support both A               PATHWORKS LAN Manager and PATHWORKS Advanced Servera@               clients.) The client license product authorizationD               keys (PAKs) must be loaded on the system that runs the'               PATHWORKS license server.2  C               In an OpenVMS cluster, the PAKs must be loaded into a_B               shared license database. For detailed information onD               managing PATHWORKS licenses, see the Guide to Managing!               PATHWORKS Licenses.r  H               Configuring and Starting the Standalone License Server 5-1 _  _            C            This chapter describes how to configure and start up therC            standalone license server, and consists of the following             sections:  B            o  Before You Begin to Configure the Standalone License               Server  7            o  Configuring the Standalone License Server   B            o  Configuring the PATHWORKS Advanced Server Transports  9            o  How to Respond to PATHWORKS Advanced Servere#               Configuration Promptst  /            o  Configuring the NetWare Transporti  =            o  How to Respond to NetWare Configuration PromptsE  8            o  How to Start the Standalone License Server  E      ________________________________________________________________   @      Before You Begin to Configure the Standalone License Server  =            You install the standalone license server from thetB            same software kit that you use to install the PATHWORKSB            file server. The procedures are described in Chapter 2,4            Installing DIGITAL PATHWORKS for OpenVMS.    E      ________________________________________________________________i  .      Configuring the Standalone License Server  >            You must configure the standalone license server toB            provide license information to clients in the PATHWORKSE            LAN. Therefore, you select the appropriate transports used($            by the PATHWORKS clients.  C            For PATHWORKS Advanced Server clients, you can configureL>            the license server to use the following transports:              o  DECnet              o  NetBEUIt  ?      5-2 Configuring and Starting the Standalone License Server     Y      H                                Configuring the Standalone License Server                   o  TCP/IPr                 Note  C               TCP/IP requires a TCP/IP transport product. SuggestedeC               products are listed in the DIGITAL PATHWORKS V6.0 forN6               OpenVMS (Advanced Server) Release Notes.  F               To configure the standalone license server to use one orG               more of these transports, use the PWRK$CONFIG.COM command C               procedure, as described in "Configuring the PATHWORKSe9               Advanced Server Transports " in this guide.   =               For NetWare clients, you can also configure the C               license server to use the IPX transport. To configure_?               the standalone license server to use IPX, use thewA               PWVN$CONFIG.COM command procedure, described in thev;               "Configuring the NetWare Transport " section.l  H         ________________________________________________________________  <         Configuring the PATHWORKS Advanced Server Transports  F               The following section describes how to use the PATHWORKSB               Advanced Server's configuration command procedure toA               configure the transports for the standalone licensee               server.P  E               After the installation procedure completes, the OpenVMS_?               system prompt ($) is displayed. If the system was .               rebooted following installation:  E               1. Ensure that you are logged in to the SYSTEM account.   ?               2. Start the configuration procedure by entering:   *                  $ @SYS$UPDATE:PWRK$CONFIG  6               3. Respond to the configuration prompts.            H               Configuring and Starting the Standalone License Server 5-3 s         F      How to Respond to PATHWORKS Advanced Server Configuration Prompts  E      ________________________________________________________________   >      How to Respond to PATHWORKS Advanced Server Configuration      Prompts  A            Table 5-1 tells you how to respond to the prompts thaty             PWRK$CONFIG displays.              Note.  <            Table 5-1 shows only the prompts that PWRK$CONFIGE            displays; it does not show any informational messages. For B            a complete sample configuration script, see Appendix E,<            Sample Standalone License Server Installation and#            Configuration Procedure.   E      Table_5-1_PWRK$CONFIG_Configuration_Prompts_____________________e  '                         If you want the /      At this            configuration procedureaE      prompt_._._._______to_._._._____________________Enter_._._._____   =      Enter disk         Copy the PATHWORKS on-       <Return> -      device name        disk structure to theo,      where PATHWORKS    default OpenVMS disk(      data files         device displayed/      will be stored     (If you ran PWRK$CONFIG 2      [default_device]:  or PWVN$CONFIG previously,  2                         the default disk device is1                         the one you specified ther0                         last time you configured#                         the server)e  @                         Copy the PATHWORKS on-disk   device_name/                         structure to an OpenVMSd2                         disk device different from-                         the default displayed   E                                              (continued on next page)r            ?      5-4 Configuring and Starting the Standalone License ServerD o  a      H        How to Respond to PATHWORKS Advanced Server Configuration Prompts    H         Table_5-1_(Cont.)_PWRK$CONFIG_Configuration_Prompts_____________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Do you want to     Allow licenses to be         <Return>-         serve PATHWORKS    served over DECnet          licenses         over DECnet          [YES]:[1,2]   :                            Not allow licenses to be     NO-                            served over DECnetw  ;         Do you want to     Allow licenses to be         YES .         serve PATHWORKS    served over NetBEUI         licenses         over NetBEUI         [NO]:[1,2]  @                            Not allow licenses to be     <Return>.                            served over NetBEUI  ;         Do you want to     Allow licenses to be         YES -         serve PATHWORKS    served over TCP/IP          licenses overi         TCP/IP [NO]:[1]   @                            Not allow licenses to be     <Return>-                            served over TCP/IPa  H         [1]Default_answers_may_differ_if_you_have_run_the_PWRK$CONFIG___           procedure previously. G         [2]This prompt appears only if the PATHWORKS license server was !         not previously installed.   H                                                 (continued on next page)            H               Configuring and Starting the Standalone License Server 5-5 e         F      How to Respond to PATHWORKS Advanced Server Configuration Prompts    E      Table_5-1_(Cont.)_PWRK$CONFIG_Configuration_Prompts______________  '                         If you want thes/      At this            configuration procedurexE      prompt_._._._______to_._._._____________________Enter_._._._____   =      Do you want        Start the server             <Return>e/      to start the       automatically after the /      PATHWORKS          configuration procedure:!      license server     completesC      now [YES]:n  7                         Complete the configuration   NO 2                         procedure without startingE      ___________________the_server___________________________________a      E      ________________________________________________________________d  &      Configuring the NetWare Transport  A            The following section describes how to use the NetWare ?            configuration command procedure to configure the IPX >            transport so that the standalone license server can7            support NetWare client license verification.P  B            After the installation procedure completes, the OpenVMS=            system prompt ($)  is displayed. If the system was +            rebooted following installation:   B            1. Ensure that you are logged in to the SYSTEM account.  <            2. Start the configuration procedure by entering:  '               $ @SYS$UPDATE:PWVN$CONFIGl  D            3. Respond to the configuration prompts. For descriptions9               of the types of information required in the A               configuration procedure, see Chapter 4, Configuring A               the DIGITAL PATHWORKS for OpenVMS (NetWare) Server.         ?      5-6 Configuring and Starting the Standalone License Server            H                          How to Respond to NetWare Configuration Prompts  H         ________________________________________________________________  7         How to Respond to NetWare Configuration Prompts   ?               Table 5-2 tells you how to respond to the promptsIB               that PWVN$CONFIG displays. For a complete example ofC               the configuration dialog, refer to Appendix E, Sample F               Standalone License Server Installation and Configuration               Procedure.  H         Table_5-2_PWVN$CONFIG_Configuration_Prompts_____________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Enter disk         Copy the PATHWORKS on-       <Return>0         device name        disk structure to the/         where PATHWORKS    default OpenVMS disk:+         data files         device displayedy2         will be stored     (If you ran PWRK$CONFIG5         [default_device]:  or PWVN$CONFIG previously,n  5                            the default disk device isK4                            the one you specified the3                            last time you configuredn&                            the server)  C                            Copy the PATHWORKS on-disk   device_name 2                            structure to an OpenVMS5                            disk device different from_0                            the default displayed           System-specificn         directory &         [SYS$SPECIFIC:[PWVN$PRIVATE]]:  @                            Use the default device and   <Return>$                            directory  B                            Use another device or        Device andD                            directory                    directory to<                                                         use.  H                                                 (continued on next page)  H               Configuring and Starting the Standalone License Server 5-7 c  i      4      How to Respond to NetWare Configuration Prompts    E      Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________   '                         If you want the /      At this            configuration procedureuE      prompt_._._._______to_._._._____________________Enter_._._._____A    =      Do you want to     Allow licenses to be         <Return>a'      serve PATHWORKS    served over IPX       licenses over      IPX [YES]?     7                         Not allow licenses to be     NOe'                         served over IPX   =      Internal           Use the default internal     <Return> &      network number     network number      (hexadecimal)      [network_
      number]:o  D                         Use another internal         Correct network;                         network number               numbera  =      Maximum SPX        Use no more than 50          <Return>_      sockets [50]:      sockets_  E                         Use a greater number of      50, 200, 500, ore9                         sockets                      1000n  =      Network            Allow you to enter a new     <Return>r-      Configuration      network configuration       Action (ADD)n      [ADD]:[1]  E      [1]This_prompt_is_displayed_only_if_there_are_no_NetWare________r  >      networks configured already. At least one network must beA      configured in order to complete the configuration procedure._  E                                              (continued on next page)h      ?      5-8 Configuring and Starting the Standalone License Server  s  R      H                          How to Respond to NetWare Configuration Prompts    H         Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  4                            At least one network must1                            be configured in ordere0                            to proceed. A maximum3                            of eight networks can be &                            configured.  @         Network Type       Configure a new local        <Return>"         (LOCAL,            network         TUNNEL,NONE)         [L]:[2]t  9                            Configure a new tunnel       T "                            network  <                            Not configure a new          NONE"                            network  @         Choose a Network   Configure a new network      <Return>.         controller from    based on controller         above listingf         [controller]:[2]  <                            Not configure a new          NONEG                            network                      When you select   H                                                         NONE, the dialogB                                                         returns toC                                                         the NetworkdE                                                         ConfigurationmE                                                         Action prompto  H         [2]This_prompt_is_displayed_only_if_you_are_configuring_a_new___           network.  H                                                 (continued on next page)      H               Configuring and Starting the Standalone License Server 5-9 n  u      4      How to Respond to NetWare Configuration Prompts    E      Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________   '                         If you want the_/      At this            configuration procedure_E      prompt_._._._______to_._._._____________________Enter_._._._____s  =      Enter 5 for        Use the default frame type   <Return>o"      Ethernet_II        (DIX/SNAP)      (DIX), 6 for       802.2 (Sap E0),      or 7 for Raw-      802.3:[5]:[2]  6                         Use the IEEE-802.2 frame     6                         type  6                         Use the Raw-802.3 frame      7                         type  E      Network Number     Use the unique network       n, a hexadecimal B      [0]:[2]            number                       value greater;                                                      than 0o  =      Network            Store the displayed          <Return>o)      Configuration      configuration and 0      Action             finish the configuration!      (ADD,DELETE,       procedurep      MODIFY,NONE)n      [NONE]:  8                         Add a new network            ADD  ;                         Delete a network             DELETEs  ;                         Modify the configuration     MODIFYv.                         of an existing network  =      Do you want        Reboot the system            <Return>t/      to reboot the      automatically after the /      system now         configuration proceduree!      [YES][3]:          completese  E      [2]This_prompt_is_displayed_only_if_you_are_configuring_a_new___   
      network.AB      [3]This prompt is displayed only if it is necessary to rebootA      the system to reload the streams execlet or the PCFS driver.   E                                              (continued on next page)   @      5-10 Configuring and Starting the Standalone License Server           H                          How to Respond to NetWare Configuration Prompts    H         Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  :                            Not reboot the system        NO  /                            (Note that after thee2                            configuration procedure5                            completes, you must reboota4                            the system before you can+                            start PATHWORKS)   @         Do you want        Start the server             <Return>2         to start the       automatically after the2         PATHWORKS          configuration procedure$         license server     completes         now [YES]:  :                            Not start the server         NO  @         Is this            Continue with the            <Return>2         configuration      configuration procedure         satisfactory         [YES]?  :                            Prompt you for another       NO0                            Network ConfigurationH         ___________________Action_______________________________________  H         ________________________________________________________________  2         How to Start the Standalone License Server  F               You can start the license server in any of the following               ways:   H               o  During the configuration procedure, as described in theF                  "Configuring the Standalone License Server " section.  0               o  Manually from the command line.  4               o  Automatically each time you reboot.  H              Configuring and Starting the Standalone License Server 5-11           /      How to Start the Standalone License Servern    -      HOW TO START THE LICENSE SERVER MANUALLY =            If you did not start the license server during theeC            configuration procedure, you can start it manually using "            the following commands:  E            __________________________________________________________PE            To_serve_._._.________Enter_._._._________________________e  <            Advanced Server       $ @SYS$STARTUP:PWRK$STARTUP            licenses   <            NetWare licenses      $ @SYS$STARTUP:PWVN$STARTUP  <            NetWare and           $ @SYS$STARTUP:PWRK$STARTUP<            Advanced Server       $ @SYS$STARTUP:PWVN$STARTUPE            licenses__________________________________________________               Example  &            $ @SYS$STARTUP:PWVN$STARTUP              Resulth  A            The license server starts, and messages similar to theC#            following are displayed:d  &            $ @SYS$STARTUP:PWVN$STARTUP  9            PATHWORKS license server will use DECnet, IPX._7            PATHWORKS mail notification will use DECnet.f?            Process NETBIOS created with identification 0000012C *            Starting IPX Daemon (NPSD)...OKF            Process PWRK$LICENSE_S created with identification 00000135            $  2      HOW TO START THE LICENSE SERVER AUTOMATICALLYD            To make sure that the license server starts automatically2            each time you boot your OpenVMS system:  +            1. Edit the system startup file,a,               SYS$STARTUP:SYSTARTUP_VMS.COM.  C            2. Add the appropriate startup commands, as shown in thecB               following example. Add the command to the file belowD               all lines that start network transports. The followingB               example shows how to edit the file to serve both LAN+               Manager and NetWare licenses.s  @      5-12 Configuring and Starting the Standalone License Server e  r      H                               How to Start the Standalone License Server                      Example  [                  $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNETs                    .                  .                  .  ,                  $ @SYS$STARTUP:PWRK$STARTUP,                  $ @SYS$STARTUP:PWVN$STARTUP  =         HOW TO START THE LICENSE SERVER IN AN OPENVMS CLUSTERgC               If you installed and configured the PATHWORKS licensenE               server on multiple members of the same OpenVMS cluster, A               Digital Equipment Corporation suggests that you usenA               the SYSMAN utility to start the server manually and >               simultaneously on all cluster members. To do so:  G               1. Make sure that you are logged in to the SYSTEM account C                  on one of the server nodes in the OpenVMS cluster.   6               2. Start the SYSMAN utility by entering:  (                  $ RUN SYS$SYSTEM:SYSMAN  D               3. Define all the cluster members on which you want toE                  start the standalone license server. For example, if F                  you want to start the license server on nodes HYDRAA,$                  HYDRAB, and HYDRAC:  F                  SYSMAN> SET ENVIRONMENT/NODE=(HYDRAA, HYDRAB, HYDRAC)  F               4. Start the license server on the nodes you defined. At6                  the SYSMAN> prompt, do the following:  H                  _______________________________________________________H                  To_serve_._._.___Enter_._._.___________________________  F                  Advanced         SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP                  Server                   licensesP  F                  NetWare          SYSMAN> DO @SYS$STARTUP:PWVN$STARTUP                  licenseso  H              Configuring and Starting the Standalone License Server 5-13 t  i      /      How to Start the Standalone License Server.  E               _______________________________________________________wE               To_serve_._._.___Enter_._._.___________________________K  C               NetWare and      SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP C               Advanced         SYSMAN> DO @SYS$STARTUP:PWVN$STARTUP                ServerE               licenses_______________________________________________c                                                                              @      5-14 Configuring and Starting the Standalone License Server                       H                                                                        6H         ________________________________________________________________  H              After You Install the DIGITAL PATHWORKS for OpenVMS Servers      D               This chapter describes tasks you can perform after you"               install the servers.  >               This chapter consists of the following sections:  8               o  Before You Begin Postinstallation Tasks  2               o  Verifying the Server Installation  *               o  Starting the File Servers  1               o  Enabling External Authentication   "               o  Setting up Shares                                          H          After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-1    P      ,      Before You Begin Postinstallation Tasks  E      ________________________________________________________________   ,      Before You Begin Postinstallation Tasks      E      HAVE YOU_DONE?___________________________________________________E            If_you_are_._._.______Make_sure_that_you_have_._._._______h  ;            Installing the        Completed the installationiC            DIGITAL PATHWORKS     procedures described in Chapter 2, A            for OpenVMS Advanced  Installing DIGITAL PATHWORKS for )            Server                OpenVMS.   <                                  Completed the configuration>                                  procedures appropriate to the<                                  servers you have installed.  @            Upgrading the LAN     Completed the upgrade procedureC            Manager server to     described in DIGITAL PATHWORKS fornA            PATHWORKS Advanced    OpenVMS (Advanced Server) Servers1            Server                Migration Guide.   <            Upgrading the         Completed the configurationB            NetWare server from   procedure described in Chapter 4,B            a previous version.   Configuring the DIGITAL PATHWORKSE            ______________________for_OpenVMS_(NetWare)_Server._______o  E      ________________________________________________________________r  &      Verifying the Server Installation          HOW TO RUN THE IVP D            If you did not run the IVP when you installed the DIGITALB            PATHWORKS kit, you can run it now to make sure that the)            server installed successfully.o                  D      6-2 After You Install the DIGITAL PATHWORKS for OpenVMS Servers    6      H                                        Verifying the Server Installation    H               Verifying the DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced"               Server) Installation  C               To run the IVP for DIGITAL PATHWORKS V6.0 for OpenVMSr'               (Advanced Server), enter:   "               $ @SYS$TEST:PWRK$IVP  H         ________________________________________________________________         If the          installa-   Then the IVPH         tion_._._.__displays_._._.________And_you_should_._._.__________  H         Succeeded   The message           Start the server, as describedH                     %PWRK-I-NORMAL,       in Starting the File Servers ,:                     IVP completed         in this chapter.                      successfully  D         Failed      An error message,     Reinstall the software, asD                     followed by -PWRK-    described in Chapter 2, in5                     E-IVPFAIL, IVP has    this guide.OH         ____________failed______________________________________________  ?               Verifying the DIGITAL PATHWORKS V1.0F for OpenVMS $               (NetWare) Installation  D               To run the IVP for DIGITAL PATHWORKS V1.0F for OpenVMS               (NetWare), enter:   "               $ @SYS$TEST:PWVN$IVP  H         ________________________________________________________________         If the          installa-   Then the IVPH         tion_._._.__displays_._._.________And_you_should_._._.__________  H         Succeeded   The message           Start the server, as describedH                     %PWVN-I-NORMAL,       in Starting the File Servers ,:                     IVP completed         in this chapter.                      successfully  D         Failed      An error message,     Reinstall the software, asH                     followed by -PWVN-    described in Chapter 2 in this0                     E-IVPFAIL, IVP has    guide.H         ____________failed______________________________________________  H          After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-3 t  S      <      Starting the DIGITAL PATHWORKS for OpenVMS File Servers  E      ________________________________________________________________i  <      Starting the DIGITAL PATHWORKS for OpenVMS File Servers            WHEN TO START THE SERVERoD            You must configure the server before you can start it forE            the first time. After running the configuration procedure, 9            you can start and stop the server at any time.P  $      WHAT THE STARTUP PROCEDURE DOES!            The startup procedure:l  1            1. Checks for the required privileges.e  D            2. Checks for enough available processes (for the NetWare               server only).   C            3. Looks for the logical names files and, if it does not :               find the files, exits the startup procedure.  D            4. Verifies that the server has been configured, and ends               if it has not.  E            5. Makes sure that the value for VIRTUALPAGECNT is greater 8               than 20,000 (for the NetWare server only).              6. Loads drivers.              7. Loads streams.              8. Installs images.  1            9. Starts transport support processes.u  ,            10.Starts each of the components:  "               o  License Registrar  B               o  Novell Virtual Terminal (NVT) (if configured) for#                  the NetWare servere                 o  File server  E               o  Print servers (if configured) for the NetWare server   /               o  License server (if configured)h  D      6-4 After You Install the DIGITAL PATHWORKS for OpenVMS Servers s  R      H                  Starting the DIGITAL PATHWORKS for OpenVMS File Servers    #         TROUBLESHOOTING THE STARTUPI@               PATHWORKS processes are detached processes. During>               startup, all detached processes must execute the?               site-specific system login procedure (by default,e'               SYS$MANAGER:SYLOGIN.COM).   G               If your PATHWORKS startup does not complete successfully,eB               check the SYLOGIN.COM procedure. Make sure that onlyD               commands that should be executed by detached processes4               are executed during PATHWORKS startup.  C               In SYSLOGIN.COM, you can use the DCL lexical functionNH               F$MODE or F$GETJPI to conditionalize DCL commands, such asE               $SET TERM/INQUIRE, that should be executed only by non- F               detached processes, so that they are not executed duringH               PATHWORKS startup. See the OpenVMS DCL Dictionary for more               information.    H         ________________________________________________________________  !         Starting the File Serversa              WAYS TO START THE SERVER'               You can start the server:n  D               o  During the configuration procedure, as described inE                  Chapter 2, Installing DIGITAL PATHWORKS for OpenVMS.   0               o  Manually from the command line.  4               o  Automatically each time you reboot.  ;         HOW TO START THE PATHWORKS ADVANCED SERVER MANUALLY G               If you did not start the PATHWORKS Advanced Server during_B               the configuration procedure, you can start it now by               entering:   )               $ @SYS$STARTUP:PWRK$STARTUPo          H          After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-5 r  9            Starting the File Servers                ResultP  E            The PATHWORKS Advanced Server starts, and messages similar_*            to the following are displayed:  1            PATHWORKS file server will use DECnet.d7            PATHWORKS mail notification will use DECnet._?            Process NETBIOS created with identification 0000009AmF            Process PWRK$LICENSE_R created with identification 0000009DL            The PATHWORKS V6.0 server is configured to support 20 PC clients.C            Process PWRK$MASTER created with identification 000000A2 K            The master process will now start all other PATHWORKS processes.   7      HOW TO DEFINE LAN MANAGER SERVER COMMANDS AT LOGINtD            You can define server commands automatically when you logB            in to the privileged account that you use to manage the%            PATHWORKS Advanced Server.   A            To define server commands at login, edit the LOGIN.COM D            file of the privileged account to add the following line:  .            $ @SYS$STARTUP:PWRK$DEFINE_COMMANDS  -      HOW TO START THE NETWARE SERVER MANUALLYd?            If you did not start the DIGITAL PATHWORKS V1.0F fora<            OpenVMS (NetWare) server during the configuration7            procedure, you can start it now by entering:f  &            $ @SYS$STARTUP:PWVN$STARTUP  3      HOW TO DEFINE NETWARE SERVER COMMANDS AT LOGINeD            You can define server commands automatically when you logB            in to the privileged account that you use to manage the            NetWare server.  A            To define server commands at login, edit the LOGIN.COMpD            file of the privileged account to add the following line:  '            $ @SYS$STARTUP:PWVN$COMMANDSr            D      6-6 After You Install the DIGITAL PATHWORKS for OpenVMS Servers 5         H                                                Starting the File Servers    -         HOW TO START THE SERVER AUTOMATICALLYiD               To make sure that the server starts automatically each0               time you boot your OpenVMS system:  .               1. Edit the system startup file,/                  SYS$STARTUP:SYSTARTUP_VMS.COM._  ;               2. For the PATHWORKS Advanced Server, add the D                  @SYS$STARTUP:PWRK$STARTUP command to the file below9                  all lines that start network transports.i                    Example  R         $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET  	         . 	         . 	         .s  #         $ @SYS$STARTUP:PWRK$STARTUP   0               3. For the NetWare server, add theD                  @SYS$STARTUP:PWVN$STARTUP command to the file below9                  all lines that start network transports.l                    Example  R         $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET  	         .i	         . 	         .r  #         $ @SYS$STARTUP:PWVN$STARTUPa  5         HOW TO START THE SERVER IN AN OPENVMS CLUSTER C               If you installed and configured DIGITAL PATHWORKS for F               OpenVMS on multiple members of the same OpenVMS cluster,C               Digital Equipment Corporation recommends that you use_A               the SYSMAN utility to start the server manually andt4               simultaneously on all cluster members.  F               To start the servers at the same time, make sure you areH               logged into the SYSTEM account on one of the server nodes,)               then run SYSMAN as follows:o  H          After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-7 .               Starting the File Servers  E      ________________________________________________________________cE      Enter_this_command...___________To...___________________________e  >      $ RUN SYS$SYSTEM:SYSMAN         Start the SYSMAN utility.  ?      SYSMAN> SET ENVIRONMENT         Define the OpenVMS cluster B      /NODE=(HYDRA,HYDRAB,HYDRAC)     members on which to start the@                                      server. For example, HYDRA,4                                      HYDRAB, HYDRAC.  A      SYSMAN> DO                      Start the PATHWORKS AdvancedAC      @SYS$STARTUP:PWRK$STARTUP       Server server on all the nodes @                                      you defined in the previous-                                      command.U  D      SYSMAN> DO                      Start the NetWare server on allA      @SYS$STARTUP:PWVN$STARTUP       the nodes you defined in the_6                                      previous command.  E      SYSMAN>_EXIT____________________Exit_the_SYSMAN_utility.________t              Notes  >             If you are using the STARTUP feature of the SYSMANC            utility to start PATHWORKS, you must pass a P1 parameteri            of "". For example,  C            SYSMAN STARTUP ADD FILE PWRK$STARTUP.COM/PARAMETER=P1:""I  =            For more information on using the SYSMAN utility's D            STARTUP feature, see the OpenVMS System Manager's Manual:            Essentials.  E      ________________________________________________________________         Stopping the Server        WHEN TO STOP THE SERVERD            You can stop the server at any time for any reason, which%            can include the following:   /            o  When you change server parameters2  3            o  As part of an orderly system shutdownc    D      6-8 After You Install the DIGITAL PATHWORKS for OpenVMS Servers           H                                                      Stopping the Server             HOW TO STOP THE SERVERA               To stop the server, enter the following command, as                appropriate:  ;               To stop the PATHWORKS Advanced Server, enter:   *               $ @SYS$STARTUP:PWRK$SHUTDOWN  0               To stop the NetWare server, enter:  *               $ @SYS$STARTUP:PWVN$SHUTDOWN  1         HOW TO STOP THE SERVER ON SYSTEM SHUTDOWN.H               To stop the servers as part of an orderly system shutdown,B               add the shutdown command to the site-specific system!               shutdown procedure.     H         ________________________________________________________________  (         Enabling External Authentication  B               The OpenVMS operating system versions 7.1 and higherD               provide support for external authentication. PATHWORKSH               Advanced Server takes advantage of external authenticationE               to allow Advanced Server users to log in to the OpenVMS F               operating system using the Advanced Server user name and               password.t  A               External authentication provides automatic password >               synchronization between an OpenVMS account and aD               corresponding NT account. With external authenticationF               enabled, users who have both OpenVMS and Advanced ServerF               user accounts can avoid having to maintain two different               passwords.  H               To provide external authentication for a user, perform theF               following procedures. Each procedure is described in the#               section listed below.w            H          After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-9           %      Enabling External Authentication_  E            __________________________________________________________UE            Step___Procedure___________Section________________________   7            1.     Enable external     Enabling ExternalWD                   authentication      Authentication for VAX Systems$                   for the system, if                   necessary.  7            2.     Set the OpenVMS     Enabling External_?                   user account to     Authentication for a User                     allow external!                   authentication.   D            3.     Establish host      Establishing User Host Mapping!                   mapping betweenS                   the PATHWORKS !                   Advanced Servers                   user account!                   and the OpenVMS "                   operating systemE            _______user_account.______________________________________n  5      ENABLING EXTERNAL AUTHENTICATION FOR VAX SYSTEMS E            On Alpha systems, external authentication is automatically_<            enabled when the PATHWORKS Advanced Server starts>            up. However, when the server is running on a mixed-E            architecture OpenVMS cluster (that is, a cluster with bothrA            VAX and Alpha members), you must perform the following B            additional steps on VAX members to ensure that external?            authentication is enabled across the entire cluster.f  A            1. Copy the following files to the VAX member's systemr7               disk from the Alpha member's system disk:   E               _______________________________________________________ C               Copy this File from the   To this Location on the VAXSE               Alpha_System______________System_______________________   @               SYS$STARTUP:PWRK$ACME_    SYS$COMMON:[SYS$STARTUP]               STARTUP.COMi  ;               SYS$LIBRARY:PWRK$ACME_    SYS$COMMON:[SYSLIB]_E               MODULE_VAX.EXE__________________________________________      E      6-10 After You Install the DIGITAL PATHWORKS for OpenVMS Serversm t  t      H                                         Enabling External Authentication    G               2. Run the PWRK$ACME_STARTUP command procedure on the VAX                   machine:   5                  $ @SYS$STARTUP:PWRK$ACME_STARTUP.COMd  G               3. Define the following logicals in the VAX local startup F                  file, where the scs_node is the SCS node name that is.                  running the PATHWORKS server:  =                  $ DEFINE/SYSTEM/EXE SYS$ACME_SERVER scs_nodeI  F                 ________________________Note  ________________________  @                 You may include steps 2 and 3 as commands in the<                 system startup procedure for the VAX system.  E                 _____________________________________________________   B               Failure to enable external authentication on the VAXF               member of an OpenVMS cluster can result in unpredictable,               login failures on the cluster.  3         ENABLING EXTERNAL AUTHENTICATION FOR A USERlH               To enable the optional external authentication feature forG               a user, set the EXTAUTH flag in the user's SYSUAF record.tG               When set, the EXTAUTH flag denotes that the user is to be G               externally authenticated at OpenVMS logon. You can modifyV4               this flag using the AUTHORIZE utility.  A               For example, to create a user account with externalyC               authentication enabled, enter the following commands,e>               where [nnn,nnn] is the UIC for the user account:                 $ MCR AUTHORIZE H               UAF> ADD username /FLAG=(EXTAUTH,NODISUSER) /UIC=[nnn,nnn]  B               To modify an existing user account to allow external;               authentication, enter the following commands:                  $MCR AUTHORIZE2               UAF> MODIFY username /FLAG=(EXTAUTH)        H         After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-11 -  O      %      Enabling External Authentication                 Note   C            By default, the EXTAUTH flag in the AUTHORIZE utility is             not set.n  E            Refer to the OpenVMS System Management Utilities Referencew?            Manual for more information on the AUTHORIZE utility-            EXTAUTH flag.  #      ESTABLISHING USER HOST MAPPING_C            After you enable external authentication for a user, youh@            must establish the host mapping for the corresponding?            PATHWORKS Advanced Server user account. Host mappingVC            identifies an Advanced Server user with an OpenVMS user.   C            Host mapping can serve two purposes. It can be used both_D            to enable external authentication and to enforce resourceC            access restrictions. Default host mapping is provided by_E            the system. Explicit host mapping, done to enable externalsC            authentication or to enhance OpenVMS security, overrides             the default mapping.   B            To establish the host mapping for an existing PATHWORKS?            Advanced Server user, use the ADMINISTER command ADDo            HOSTMAP, as follows:o  A            $ADMINISTER ADD HOSTMAP pw-user-name OpenVMS-user-name   A            After you complete these steps, the user identified as_B            externally authenticated can use the PATHWORKS Advanced@            Server user name and password to log in to OpenVMS atC            the login prompt. If the verification is successful, the_D            appropriate OpenVMS user name and profile is obtained and            used.  @            For more information about user account host mapping,?            refer to the DIGITAL PATHWORKS for OpenVMS (Advanced 0            Server) Server Administrator's Guide.              E      6-12 After You Install the DIGITAL PATHWORKS for OpenVMS Serverse           H                                         Enabling External Authentication             SYNCHRONIZING PASSWORDSlA               The password of an externally authenticated OpenVMStD               user is automatically synchronized with the hostmappedG               PATHWORKS Advanced Server user, regardless of the role of :               the PATHWORKS Advanced Server in the domain.  F               When the user changes the OpenVMS password using the SETE               PASSWORD command, if external authentication is set for G               the user, OpenVMS forwards the password change request to E               the PATHWORKS Advanced Server. When the password changesD               request is successfully processed, OpenVMS updates the$               OpenVMS user password.  A               When the user changes the PATHWORKS Advanced ServeriD               password using the NET PASSWORD command, or the serverG               administrator changes it with the ADMINISTER SET PASSWORDsB               command, the PATHWORKS Advanced Server processes the'               password change as usual.r                 Note  B               Password synchronization may fail due to differencesD               in the sets of valid characters allowed by OpenVMS andH               PATHWORKS Advanced Server. Keep this in mind when changingD               the password of an externally authenticated hostmapped               user.   @               Password synchronization is enabled by default for=               externally authenticated OpenVMS users. You cantD               selectively disable it. Refer to the section "ManagingE               System Access" in the OpenVMS Guide to System Security,dE               for more information on how to selectively disable thisA               feature.  .         EXTERNAL AUTHENTICATION OVER A NETWORK?               External authentication cannot occur if a networkeF               connection is required and the network is down. However,F               privileged users can enter the /LOCAL_PASSWORD qualifierA               after the OpenVMS user name at the login prompt, toe>               specify local authentication. Be sure to specify?               the OpenVMS user name and password when using the_(               /LOCAL_PASSWORD qualifier.      H         After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-13           %      Enabling External Authenticationr    B            Because using the /LOCAL_PASSWORD qualifier effectively;            overrides the security policy established by theaA            system manager, it is allowed only under the following             conditions:  A            o  When the user's account has SYSPRV as an authorizeda?               privilege. This allows the system manager to gaing<               access to the system when the network is down.  @            o  When Bit 1 is set in the SYS$SINGLE_SIGNON logicalE               name, which allows nonprivileged users who are normallyr9               externally authenticated to log in locally.R  @            Refer to the OpenVMS Utility Routines Manual for moreA            information about the /LOCAL_PASSWORD qualifier to the             LOGINOUT command.  1      CONFIGURING EXTERNALLY AUTHENTICATED CLIENTSwC            By default, the PATHWORKS Advanced Server supports up toiD            10 simultaneous external authentication requests. You canD            modify this maximum to suit the server requirements using@            the Configuration Manager. To start the Configuration0            Manager, enter the following command:  %            $ ADMINISTER/CONFIGURATIONS  <            The basic server parameters include the number of;            simultaneous activations for users with externala9            authentication (also called "Single Sign-on").h  =            For more information about using the Configuration >            Manager, refer to the DIGITAL PATHWORKS for OpenVMS:            (Advanced Server) Server Administrator's Guide.  E      ________________________________________________________________H        Setting up Shares  A            After installing and configuring your servers, you can @            set up directory shares to enable users to share fileE            resources and print shares to enable them to share printer             queues.      E      6-14 After You Install the DIGITAL PATHWORKS for OpenVMS Servers     u      H                                                        Setting up Shares    C               You can photocopy and use the Shares Worksheet in the F               Worksheets Appendix of the DIGITAL PATHWORKS for OpenVMSE               (Advanced Server) Concepts and Planning Guide to record =               the decisions you make as you plan your shares.r  F               Read the following chapters of the DIGITAL PATHWORKS forH               OpenVMS (Advanced Server) Server Administrator's Guide for/               information on setting up shares:   G               o  Managing Directory and File Sharing for information on 9                  setting up and managing directory shares.  G               o  Managing Shared Printers for information on setting upC*                  and managing print shares                                                              H         After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-15 r  r                  H                                                                        7H         ________________________________________________________________  H                                         Implementing a Wide Area Network      F               This chapter describes how to set up a wide area network?               (WAN) using the TCP/IP transport supported by the 1               PATHWORKS Advanced Server software.(  >               This chapter consists of the following sections:  >               o  Implementing a Wide Area Network Using TCP/IP  ;               o  Using a WINS Server in a Wide Area Network     H         ________________________________________________________________  5         Implementing a Wide Area Network Using TCP/IPl  E               The DIGITAL PATHWORKS for OpenVMS software provides thesC               ability to set up a wide area network with the TCP/IPtF               transport through the use of the LMHOSTS file. This fileF               contains a list of domain controllers and member serversC               that are not in the same TCP/IP subnet as the primary F               domain controller. The LMHOSTS file allows the PATHWORKSF               Advanced Server to participate in a Windows NT wide area               network as well.  G               Unlike a Windows NT Server, DIGITAL PATHWORKS for OpenVMSnD               does not support remote LMHOSTS files (called into theA               Windows NT LMHOSTS file using #INCLUDE). To includeVB               the same host names as an existing LMHOSTS file on aG               Windows NT server, copy the LMHOSTS file to the PATHWORKS H               Advanced Server, then manually insert the entries into the5               PATHWORKS Advanced Server LMHOSTS file.         H                                     Implementing a Wide Area Network 7-1           2      Implementing a Wide Area Network Using TCP/IP          PLANNING AND SETUP >            To implement a TCP/IP wide area network, modify theC            LMHOSTS file, which consists of a list of the host namesSD            and TCP/IP addresses of the domain controllers and member@            servers in the wide area network that are in the same            domain.  C            When you include a node in the LMHOSTS file, the primaryeB            domain controller copies the user account database ontoE            that node and keeps it up to date. If you omit a node, its 8            user account database may become out of date.  ?            You can modify the LMHOSTS file at any time. As longtA            as the LMHOSTS file exists, users can establish TCP/IPM8            connections to any server listed in the file.        LMHOSTS DIRECTORY=            You implement a wide area network by supplying theO>            following file on all DIGITAL PATHWORKS for OpenVMS:            Advanced Servers that are in different subnets:  '            PWRK$LMROOT:[LANMAN]LMHOSTS.p              Note   2            The LMHOSTS file has no file extension.        LMHOSTS SYNTAXlD            In the LMHOSTS file, create a list of nodes by specifying,            the following line for each node:  1            address nodename #PRE #DOM:domain_name               Where:h  E            o  address is an Internet address of form x.x.x.x, where x 0               is a decimal number from 0 to 255.  >            o  nodename is a name from 1 to 16 characters long,A               and may include a control character. (The format ofS?               a control character is \0Xnn or \nn, where n is aS!               hexadecimal digit.)       )      7-2 Implementing a Wide Area Network            H                            Implementing a Wide Area Network Using TCP/IP    D                  To preserve the case of the characters, enclose theF                  node name in double quotation marks. If the node nameE                  is not enclosed in quotes, the alphabetic characters D                  are set to uppercase before the node name is loadedF                  into cache (see parameter #PRE) or used for matching.  A                  If the node name includes a control character in C                  the last byte, you should include blank characters C                  to explicitly control the placement of the controla@                  character. When the node name has fewer than 16D                  characters, it is padded out with blank characters.  '                  Examples of Node Namese                    1. hydra1  !                  2. "hydra1\0X03"c  *                  3. "hydra1         \0X03"  H                  In Example 1, the node name is interpreted as uppercaseC                  (HYDRA1) and will be padded with blank characters.h  B                  In Example 2, the node name is not interpreted asD                  uppercase, and will be padded with blank characters(                  for bytes 8 through 16.  B                  In Example 3, the node name is not interpreted asG                  uppercase, and no padding needs to be inserted becausetG                  blank spaces are already included in order to make theb5                  control character reside in byte 16.u  F               o  #PRE is an optional tag that indicates that the entry4                  should be preloaded into the cache.  C               o  #DOM:domainname is an optional tag that associateshC                  the entry with the LAN Manager domain specified by F                  domainname. It is required when the entry is a domainC                  controller. This affects how the logon and browser H                  services behave in routed environments. It is also usedG                  in user account management and in trust relationships.p  G               For example, the following entry might be included in the_               LMHOSTS file:X  4               12.13.14.15 server #PRE #DOM:PATHWORKS  H                                     Implementing a Wide Area Network 7-3           2      Implementing a Wide Area Network Using TCP/IP    B            This entry results in NETBIOS name SERVER with InternetC            address 12.13.14.15 being preloaded into the cache. BotheA            the NETBIOS name SERVER and the NETBIOS name PATHWORKSnC            (the name of the domain) will be available for matching.a          MANAGING THE LMHOSTS FILEB            To change the list of available nodes, you can edit theB            file at any time. Domain names are resolved by checking(            the LMHOSTS file dynamically.  C            To disable wide area networking capabilities, rename theo7            LMHOSTS file to any name other than LMHOSTS._  A            When you modify or disable the LMHOSTS file, it is notMB            necessary to restart the PATHWORKS Advanced Server. The+            change is effective immediately.[        LMHOSTS LOG FILEOA            If errors occur when the LMHOSTS file is accessed, the65            errors are recorded in the following file:   8            PWRK$LMROOT:[LOGS]PWRK$KNBDAEMON_nodename.LOG  E            This file is open and being written to while the PATHWORKSCA            Advanced Server is running. To close the log file, you 3            must stop the PATHWORKS Advanced Server..  @            To prevent the log file from becoming too large, eachE            error is logged only once: the first time it occurs. If an B            error is found in the log file, it is not logged again.  E      ________________________________________________________________   /      Using a WINS Server in a Wide Area Network_  D            You can configure the PATHWORKS Advanced Server as a WINSA            client. This allows the PATHWORKS server to use a WINS E            server for NETBIOS name registration, resolution, renewal, <            and release in a wide area network configuration.          )      7-4 Implementing a Wide Area Networkn s         H                               Using a WINS Server in a Wide Area Network    B               For more information on how to use the ConfigurationG               Manager to configure the PATHWORKS Advanced Server to useXH               WINS, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced3               Server) Server Administrator's Guide.                                                                                   H                                     Implementing a Wide Area Network 7-5 e  c                  H                                                                        8H         ________________________________________________________________  H                                   Removing DIGITAL PATHWORKS for OpenVMS      H               This chapter describes how to remove DIGITAL PATHWORKS for/               OpenVMS servers from your system.h  >               This chapter consists of the following sections:  0               o  Reasons for Removing the Server  $               o  Removing the Server  E               o  Sample PATHWORKS Advanced Server and NetWare Removale                  Procedurest  H         ________________________________________________________________  '         Reasons for Removing the Server              WHY REMOVE THE SERVER?A               If the IVP indicates that the software installationRH               procedure failed, you must reinstall the DIGITAL PATHWORKS#               for OpenVMS software.e                 Note  H               If your system has enough free disk space, you can installF               the server again without deinstalling PATHWORKS servers.E               If you do not have enough disk space, however, you must F               remove DIGITAL PATHWORKS for OpenVMS before reinstalling               it.e  "               For more information  E               For detailed information about disk space requirements,dF               see Step 7: Check disk space requirements, in Chapter 1.  H                               Removing DIGITAL PATHWORKS for OpenVMS 8-1                 Removing the Server  E      ________________________________________________________________         Removing the Server      /      ABOUT THE DEINSTALLATION COMMAND PROCEDUREo>            You remove a server using a command procedure that:  >            o  Is installed with DIGITAL PATHWORKS for OpenVMS.  2            o  Shuts down the server automatically.  D            o  Prompts you to enter information necessary to complete$               the removal procedure.  ?            o  Removes all DIGITAL PATHWORKS for OpenVMS images,a?               support files, and logical names that are created C               during the installation procedure. Optionally removesa'               the PATHWORKS data files.A  =            o  Removes the PATHWORKS Advanced Server accounts.t  ;            o  Removes the NETBIOS$ACCESS OpenVMS identifierI=               if PATHWORKS V5.x for OpenVMS was not installed                previously.   /            o  Removes PATHWORKS DECnet objects.R  ,      HOW TO RUN THE DEINSTALLATION PROCEDUREC            To start the deinstallation procedure and remove DIGITALi(            PATHWORKS for OpenVMS server:  B            1. Ensure that you are logged in to the SYSTEM account.  9            2. Start the deinstallation command procedure:   E      ________________________________________________________________ ;      To remove DIGITAL PATHWORKS V6.0     To remove DIGITAL E      for OpenVMS (Advanced Server),       PATHWORKS V1.0F for OpenVMSrE      enter:_______________________________(NetWare),_enter:__________o  E      $_@SYS$UPDATE:PWRK$DEINSTAL__________$_@SYS$UPDATE:PWVN$DEINSTALt      /      8-2 Removing DIGITAL PATHWORKS for OpenVMS     h      H                                                      Removing the Server    !         HOW TO RESPOND TO PROMPTSrC               Table 8-1 tells you how to respond to the prompts theW@               PATHWORKS Advanced Server deinstallation procedure               displays.s    H         Table_8-1_PWRK$DEINSTAL_Prompts_________________________________  M                                 If you want the removal           Enter . . .rH         At_this_prompt_._._.____procedure_to_._._.______________________  E         Are you sure you        Continue                          YESh         want to deinstall          DIGITAL PATHWORKS V6         for OpenVMS (Advancedn         Server)[no]:  J                                 Exit                              <Return>  J         Do you want to          Save the PATHWORKS Advanced       <Return>9         delete the PATHWORKS    Server on-disk structure, 2         Advanced Server data    including the User:         files [no]:             Authorization file and the*                                 Share file  E                                 Remove the PATHWORKS              YES 7                                 Advanced Server on-disk =                                 structure, including the User :                                 Authorization file and theH         ________________________Share_file______________________________  ?               Table 8-2 tells you how to respond to the prompts ?               the DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare)h0               deinstallation procedure displays.                      H                               Removing DIGITAL PATHWORKS for OpenVMS 8-3 q  i            Removing the Server    E      Table_8-2_PWVN$DEINSTAL_Prompts_________________________________i  J                              If you want the removal           Enter . . .E      At_this_prompt_._._.____procedure_to_._._.______________________r  B      Are you sure you want   Continue                          YES      to deinstall DIGITALw      PATHWORKS V1.0G for      OpenVMS (NetWare)
      [no]:  G                              Exit                              <Return>o  G      Do you want to delete   Save the NetWare on-disk          <Return> 5      the NetWare data        structure, including thea0      files [no]:             configuration Files  B                              Remove the NetWare on-disk        YES5                              structure, including theB0                              configuration files  G      Do you want to delete   Save the NetWare SYS volume       <Return>n      the NetWare SYS      Volume [no]:t  E      ________________________Remove_the_NetWare_SYS_volume_____YES___a  E      ________________________________________________________________   D      Sample PATHWORKS Advanced Server and NetWare Removal Procedures      7      SAMPLE PATHWORKS ADVANCED SERVER REMOVAL PROCEDUREiB            This is a sample of the removal procedure for PATHWORKSE            Advanced Server from a system that is also running DIGITAL 1            PATHWORKS V1.0x for OpenVMS (NetWare).G  &            $ @SYS$UPDATE:PWRK$DEINSTAL  L            This procedure shuts down all PATHWORKS V6.0 for OpenVMS servers,O            and deletes all PATHWORKS V6.0 for OpenVMS (Advanced Server) images.t      /      8-4 Removing DIGITAL PATHWORKS for OpenVMS            H          Sample PATHWORKS Advanced Server and NetWare Removal Procedures    K               Are you sure you want to deinstall PATHWORKS V6.0 for OpenVMS1'               (Advanced Server) [no]: Y J               Do you want to delete the Advanced Server data files [no]: Y  P               PATHWORKS V1.0x for OpenVMS (NetWare) is installed on this system.X               There are many images that are common between Advanced Server and NetWare.Q               These images will not be deleted unless you also deinstall NetWare.   >               Shutting down the currently running server(s)...M               Deleting PATHWORKS V6.0 for OpenVMS (Advanced Server) images... 4               Deleting Advanced Server data files...E               Deassigning PATHWORKS V6.0 for OpenVMS logical names... N               PATHWORKS V6.0 for OpenVMS (Advanced Server) is now deinstalled.  (         SAMPLE NETWARE REMOVAL PROCEDUREC               This is a sample of the removal procedure for DIGITALC.               PATHWORKS for OpenVMS (NetWare).  )               $ @SYS$UPDATE:PWVN$DEINSTAL P               This procedure shuts down all PATHWORKS V1.0G for OpenVMS servers,K               and deletes all PATHWORKS V1.0G for OpenVMS (NetWare) images.   L               Are you sure you want to deinstall PATHWORKS V1.0G for OpenVMS               (NetWare) [no]: Y B               Do you want to delete the NetWare SYS Volume [no]: Y  @               Stopping PATHWORKS for OpenVMS (NetWare) Server...  %               Process NETBIOS stoppedP,               Process PWRK$LICENSE_R stopped+               Stopping IPX Daemon (NPSD)...   =               Deleting PATHWORKS for OpenVMS common images... A               Deleting PATHWORKS for OpenVMS NETBIOS component... F               Deleting PATHWORKS V1.0G for OpenVMS (NetWare) images...,               Deleting NetWare data files...,               Deleting NetWare SYS Volume...B               Removing PWRK$DEFAULT and PWRK$GUEST VMS accounts...A               Removing PATHWORKS V1.0G for OpenVMS identifiers...eD               Removing PATHWORKS V1.0G for OpenVMS DECnet objects...F               Deassigning PATHWORKS V1.0G for OpenVMS logical names...G               PATHWORKS V1.0G for OpenVMS (NetWare) is now deinstalled.T      H                               Removing DIGITAL PATHWORKS for OpenVMS 8-5 o  t                  H                                                                        AH         ________________________________________________________________  H                      Summary Checklist of Installation and Upgrade Tasks      H               Table A-1 summarizes the tasks that you need to perform toG               install and configure your PATHWORKS Advanced Server. YounG               can photocopy this table and use it as a checklist as youK=               read about and complete the tasks in this book.r  H         Table_A-1_Installation_and_Upgrade_Checklist____________________    H                                                 (continued on next page)                                                    H                  Summary Checklist of Installation and Upgrade Tasks A-1 d  r      8      Summary Checklist of Installation and Upgrade Tasks    E      Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________   9      <   >1.   Prepare for the installation by completinge<                all preinstallation tasks on the checklist in@                Preinstallation Tasks in Chapter 1, including the                following:   C                a. Make sure that you have the required hardware and                    software.   E                b. Log in to the SYSTEM account and back up the systemY                   disks.  >                c. Make sure that you have enough disk space to&                   install the servers.  @                d. Make sure that the system parameters GBLPAGES,?                   GBLSECTIONS, PROCSECTCNT, and SCSNODE are seth                   properly.   A                e. Make sure that the queue manager is running andt=                   that the time zone is configured correctly.H  ?                f. Verify that DECnet and TCP/IP, if needed, arel                   running.  D                g. Check OpenVMS cluster configuration, if installing                   on a cluster.l  >      <   >2.   Start the installation procedure and respond to?                installation prompts. You may choose to install:n  %                o  The Advanced Server   $                o  The NetWare server  C                o  The Upgrade utility only (if you chose to install E                   neither the Advanced Server nor the NetWare server)   >                o  The license server only (if you chose not toB                   install the Advanced Server, the NetWare server,*                   and the Upgrade utility)  E                                              (continued on next page)   <      A-2 Summary Checklist of Installation and Upgrade Tasks           H                      Summary Checklist of Installation and Upgrade Tasks    H         Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________  B         <   >3.   Start the configuration procedure and respond to(                   configuration prompts.  D         <   >4.   If you are upgrading from PATHWORKS V5 for OpenVMSF                   (LAN Manager), complete the upgrade procedure. ReferH                   to the DIGITAL PATHWORKS for OpenVMS (Advanced Server)F                   Server Migration Guide for information about how to:  5                   a. Determine the role of the server   '                   b. Upgrade the server   -                   c. Upgrade OpenVMS clusters2  +                   d. Create upgrade reports   -                   e. Upgrade users and groupst  #                   f. Upgrade sharese  %                   g. Upgrade securitya  <                   h. Upgrade server configuration parameters  E         <   >5.   Run the Installation Verification Procedure (if youb?                   did not do so when you installed the server).u  A         <   >6.   Start the server (if you did not do so when youe)                   configured the server).p  @         <   >7.   Install Windows NT server administration toolsH         __________(optional).___________________________________________                      H                  Summary Checklist of Installation and Upgrade Tasks A-3                       H                                                                        BH         ________________________________________________________________  H          Sample PATHWORKS Advanced Server Installation and ConfigurationH                                                                Procedure      G               This appendix shows sample installation and configurationsH               procedures for the PATHWORKS Advanced Server on an OpenVMS               cluster.    H         ________________________________________________________________  ?         Sample PATHWORKS Advanced Server Installation ProcedureR  F               The following example shows a sample installation dialog0               for the PATHWORKS Advanced Server.    >         $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK]B           OpenVMS AXP Software Product Installation Procedure V6.2#         It is 16-MAY-1997 at 15:29. 7         Enter a question mark (?) at any time for help. F         * Are you satisfied with the backup of your system disk [YES]?  1         The following products will be processed:e           PWRK V6.0e5          Beginning installation of PWRK V6.0 at 15:29D  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.   +          PATHWORKS for OpenVMS InstallationL  6             Please select which components to install:  6          PATHWORKS V6.0  for OpenVMS (Advanced Server).          PATHWORKS V1.0G for OpenVMS (NetWare)  T         * Do you want to install the PATHWORKS for OpenVMS (Advanced Server) [NO]? Y9         * Do you want to install the NetWare server [NO]?e  H  PATHWORKS  Advanced Server Installation and Configuration Procedure B-1 o  a      <      Sample PATHWORKS Advanced Server Installation Procedure    0      The following components will be installed:  2       PATHWORKS V6.0 for OpenVMS (Advanced Server)  A      If the selection is correct, the installation will continue. D      If the selection is not correct, you can change your selection.<      Press CTRL/Y if you want to terminate the installation.  &      * Is the selection correct [YES]?  
          NOTE_
          ----_M          Because this kit provides a new streams execlet for NetBEUI, TCP/IP,rL          IPX, and SPX, you MUST reboot all nodes in the cluster that are nowM          running or have run PATHWORKS to complete installation of PATHWORKS.rJ          If you do not reboot the nodes at this time, you must remember to5          reboot them later before starting PATHWORKS.   H          To complete the installation of this product, you should rebootJ          the system.  If it is not convenient to reboot at this time, then,          enter NO to the following question.  C          If you enter NO, the installation procedure will continue.   P      * Will you allow a system shutdown after this product is installed [YES]? NK      * Do you want to run the IVP after the installation is finished [YES]? F      * Do you want to purge files replaced by this installation [YES]?6      %PWRK-I-FREEBLKS, Checking for 104600 free blocks  E                    User Accounts and User Identification Codes (UICs) E                    --------------------------------------------------_  O          PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account,TO          PWRK$DEFAULT, and  a guest account, PWRK$GUEST.  The default UIC groupTE          number for both these new accounts depends on the following:   N          o If you are installing the server for the first time, the default is@            the first unused UIC group number, starting with 360.  O          o If there is an existing account PCFS$ACCOUNT, the default is the UIC 5            group number associated with PCFS$ACCOUNT._  R          o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, the defaultQ            is the UIC group number associated with PWRK$DEFAULT or PWRK$GUEST, in R            preference to PCFS$ACCOUNT.  However, the default UIC group number willB            not be used to change the UIC of any existing accounts.  M          For more information about UIC group numbers, see the OpenVMS System           Manager's Manual.  R      B-2 Sample PATHWORKS Advanced Server Installation and Configuration Procedure s  e      H                  Sample PATHWORKS Advanced Server Installation Procedure    O         * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]:   =                        Optional DECprint Supervisor Available =                        --------------------------------------.  J             The PATHWORKS for OpenVMS distribution media includes two kitsC             for the DECprint Supervisor for OpenVMS: VAX and Alpha._K             DECprint Supervisor for OpenVMS is a family of layered products L             that runs on OpenVMS VAX and Alpha to provide access through theL             OpenVMS queueing system to selected PostScript printers.  To useI             DECprint Supervisor for OpenVMS, you must install the kit for.O             either VAX or Alpha accordingly. You do not need a separate license P             to use DECprint Supervisor for OpenVMS with Advanced Server clients.  #         * Press RETURN to continue:i  B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.  S         %PWRK-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST V         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$DEFAULT.5         %UAF-I-ADDMSG, user record successfully added a         %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights databaseET         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST.5         %UAF-I-ADDMSG, user record successfully added _         %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights databasel>         %VMSINSTAL-I-RESTORE, Restoring product save set C ...>         %VMSINSTAL-I-RESTORE, Restoring product save set E ...M         %PWRK-I-SKIPSET, Skipping product save set G (Alpha NetWare only) ...AM         %PWRK-I-SKIPSET, Skipping product save set H (NetWare SYS Volume) ...,I         %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAILT:         %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands=         %PWRK-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COM M         %PWRK-I-SPECIFY, Specifying target directories for the provided files 1         %PWRK-I-OBSOLETE, Deleting obsolete filesh  4                                           Next Steps4                                           ----------  R             To continue the installation procedure, enter the following command to?             execute the server configuration command procedure:   %             $ @SYS$UPDATE:PWRK$CONFIGc  N             For information about the configuration command procedure, see theM             PATHWORKS (Advanced Server) Installation and Configuration Guide.O  H  PATHWORKS  Advanced Server Installation and Configuration Procedure B-3           <      Sample PATHWORKS Advanced Server Installation Procedure    S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...W  2       Starting Installation Verification Procedure6       for PATHWORKS V6.0 for OpenVMS (Advanced Server)  /      %PWRK-I-NORMAL, IVP completed successfully 2       Installation of PWRK V6.0 completed at 15:36  C          Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY   K          Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA,  '       VMSINSTAL procedure done at 15:36   E      ________________________________________________________________r  =      Sample PATHWORKS Advanced Server Configuration Proceduree  D            The following example shows a sample configuration dialog-            for the PATHWORKS Advanced Server.           $ @SYS$UPDATE:PWRK$CONFIGI      PATHWORKS V6.0 for OpenVMS (Advanced Server) Configuration ProcedureR  I          PATHWORKS stores and accesses the following types of data files:2  (          o Configuration parameter files$          o License server data files          o Log files          o Printer spool files'          o Virtual memory section files_  K          You can specify any existing OpenVMS disk device that has at least C          12000 free blocks of disk space to store these data files.f  J          Note: the server frequently accesses the data files stored on theL          disk.  If these files are stored on the system disk, it can degradeO          the performance of both the OpenVMS system and the server.  Therefore,dO          Digital recommends that you specify a disk other than the system disk.         Press RETURN to continue:  N          If this OpenVMS cluster has multiple system disks, make sure that all2          nodes on which you plan to run PATHWORKS:  R      B-4 Sample PATHWORKS Advanced Server Installation and Configuration Procedure V  m      H                 Sample PATHWORKS Advanced Server Configuration Procedure    P             o Use the same disk device to store and access PATHWORKS data files.  Q             o Share the same SYSUAF.DAT file. In each system disk's startup file,HN               define a system logical name that points all nodes to the shared+               SYSUAF.DAT file. For example:n  O               $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.datf  F               The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM  H         Enter disk device name where PATHWORKS data files will be stored$         [SYS$SYSDEVICE:]: DISK$PWRK::         Creating PATHWORKS directory tree on DISK$PWRK:...2         Creating Advanced Server directory tree...A         Copying client files to Advanced Server directory tree...rW         Creating PATHWORKS Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT ...   Q             Changing the server configuration parameters will allow you to modifydO             this server's client capacity and select the transports to be used.   -             COBRAZ is currently configured to '                 + support 20 PC clientsd8                 + use the following transport(s): DECnet  S             If you want this server to be the primary domain controller, you should T             configure it to use all the transports used by any of the backup servers             in the domain.  P             If you want this server to be a backup domain controller, you shouldS             configure it to have at least one transport in common with the domain'saN             primary domain controller, otherwise this configuration will fail.  P             If you do not change the configuration parameters now, you may do so)             later by typing ADMIN/CONFIG.   O         Do you want to change the server configuration parameters now? [YES]: NO  4         Reading current configuration parameters ...  O           PATHWORKS V6.0 for OpenVMS is presently configured to run as follows:y          H  PATHWORKS  Advanced Server Installation and Configuration Procedure B-5           =      Sample PATHWORKS Advanced Server Configuration Procedure     +         1.  Run the license server:      NOr+         2.  Enable Timesource service:   NOe,         3.  Enable Alerter service:      YES6         3a. Alert user names:            Administrator)         4.  Enable Netlogon service:  YESm-         5.  Advanced Server domain:  LANGROUPS*         6.  Advanced Server role:  PRIMARY1         7.  Advanced Server computer name: COBRAZ)9         7a. PATHWORKS OpenVMS cluster alias: COBRAZ_ALIAS T         8.  Server announce comment:    PATHWORKS V6.0 for OpenVMS (Advanced Server)=      Enter item number, or RETURN to use these values [DONE]:G        Saving parameters ....      Checking the access control list file ...'      Successfully created new ACL storeiB      Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB. ...$      New sharefile has been created.      ADMIN$ added       IPC$ added       PWUTIL addede  E          The Advanced Server Administrator network account is used to B          administer the server.  The Administrator network account<          is mapped by default to the OpenVMS SYSTEM account.  O          If this server is to join an Advanced Server domain, the AdministratorsD          network account password should be the same as the password@          to the domain's existing Administrator network account.  F          The network account password can be up to 14 characters long.  2      Enter Administrator network account password:  !      Re-enter to verify password:   ;      Changing password for Administrator network account..._!      Checking system resources...   L      The current system configuration for COBRAZ will support 20 PC clients.+      PATHWORKS is configured to use DECnet.C  Q          To automatically start PATHWORKS V6.0 for OpenVMS at system startup, youoQ          should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file.d  !       $ @SYS$STARTUP:PWRK$STARTUP>  R      B-6 Sample PATHWORKS Advanced Server Installation and Configuration Procedure s         H                 Sample PATHWORKS Advanced Server Configuration Procedure    Q             Note: Add this line below the lines that start all network transportsd             (such as DECnet).   Q             Before starting PATHWORKS V6.0 for OpenVMS on this system, be sure toYQ             execute @SYS$UPDATE:PWRK$CONFIG on each node that will run PATHWORKS.   Q         Do you want to start PATHWORKS V6.0 for OpenVMS on node COBRAZ now [yes]:tI         %PWRK-F-REBOOT, system must be rebooted before starting PATHWORKS                                                                           H  PATHWORKS  Advanced Server Installation and Configuration Procedure B-7 m  o                  H                                                                        CH         ________________________________________________________________  H           Sample NetWare Server Installation and Configuration Procedure      G               This appendix shows sample installation and configurationtF               procedures for the NetWare server on an OpenVMS cluster.    H         ________________________________________________________________  4         Sample NetWare Server Installation Procedure  H         The following example shows a sample installation dialog for the         NetWare server.o    >         $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK]B           OpenVMS AXP Software Product Installation Procedure V6.2#         It is 16-MAY-1997 at 15:50. 7         Enter a question mark (?) at any time for help.CF         * Are you satisfied with the backup of your system disk [YES]?  1         The following products will be processed:T           PWRK V6.0l5          Beginning installation of PWRK V6.0 at 15:50_  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.g  +          PATHWORKS for OpenVMS Installation   6             Please select which components to install:  6          PATHWORKS V6.0  for OpenVMS (Advanced Server).          PATHWORKS V1.0G for OpenVMS (NetWare)  R         * Do you want to install the PATHWORKS for OpenVMS (Advanced Server) [NO]?;         * Do you want to install the NetWare server [NO]? Y   3         The following components will be installed:   H       Sample NetWare Server Installation and Configuration Procedure C-1 d  o      1      Sample NetWare Server Installation Procedure     +       PATHWORKS V1.0G for OpenVMS (NetWare)   A      If the selection is correct, the installation will continue.hD      If the selection is not correct, you can change your selection.<      Press CTRL/Y if you want to terminate the installation.  &      * Is the selection correct [YES]?  
          NOTE 
          ----gM          Because this kit provides a new streams execlet for NetBEUI, TCP/IP,nL          IPX, and SPX, you MUST reboot all nodes in the cluster that are nowM          running or have run PATHWORKS to complete installation of PATHWORKS.dJ          If you do not reboot the nodes at this time, you must remember to5          reboot them later before starting PATHWORKS._  H          To complete the installation of this product, you should rebootJ          the system.  If it is not convenient to reboot at this time, then,          enter NO to the following question.  C          If you enter NO, the installation procedure will continue.o  P      * Will you allow a system shutdown after this product is installed [YES]? NK      * Do you want to run the IVP after the installation is finished [YES]?_F      * Do you want to purge files replaced by this installation [YES]?5      %PWRK-I-FREEBLKS, Checking for 39600 free blocksl  E                    User Accounts and User Identification Codes (UICs)AE                    --------------------------------------------------Y  O          PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account, O          PWRK$DEFAULT, and  a guest account, PWRK$GUEST.  The default UIC groupaE          number for both these new accounts depends on the following:   N          o If you are installing the server for the first time, the default is@            the first unused UIC group number, starting with 360.  O          o If there is an existing account PCFS$ACCOUNT, the default is the UICN5            group number associated with PCFS$ACCOUNT.d  R          o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, the defaultQ            is the UIC group number associated with PWRK$DEFAULT or PWRK$GUEST, indR            preference to PCFS$ACCOUNT.  However, the default UIC group number willB            not be used to change the UIC of any existing accounts.  M          For more information about UIC group numbers, see the OpenVMS Systeme          Manager's Manual.  L      * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]:  G      C-2 Sample NetWare Server Installation and Configuration Procedure  A  O      H                             Sample NetWare Server Installation Procedure    O             The PATHWORKS for OpenVMS (NetWare) product comes with a SYS volumeuQ             containing client files used by the file server.  These files require*N             a minimum of 34000 free disk blocks.  However, if the disk cluster@             size is greater than 3, more space will be required.  O             The file server uses the SYS volume location you specify as the top R             level directory for the SYS volume.  SYS volume subdirectories includeQ             SYSTEM, MAIL, PUBLIC, and LOGIN.  Client utilities such as SYSCON and I             FILER are placed in these subdirectories during installation.t  Q             Note: the server frequently accesses the data files stored on the SYS Q             volume.  If these files are stored on the system disk, it can degrade R             the performance of both the OpenVMS system and the server.  Therefore,R             Digital recommends that you specify a disk other than the system disk.  D         * NetWare SYS volume location [SYS$SYSDEVICE:[PWVN$SYSVOL]]:         PWRK$DISK:[PWVN$SYSVOL]h  B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.  S         %PWRK-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST-V         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$DEFAULT.5         %UAF-I-ADDMSG, user record successfully addedna         %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights databasefT         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST.5         %UAF-I-ADDMSG, user record successfully addedt_         %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights databaseI>         %VMSINSTAL-I-RESTORE, Restoring product save set C ...U         %PWRK-I-SKIPSET, Skipping product save set E (Alpha Advanced Server only) ... >         %VMSINSTAL-I-RESTORE, Restoring product save set G ...N         %PWRK-I-RESTORE, Restoring product save set H (NetWare SYS Volume) ...Z         %PWRK-I-PURGING, Purging PATHWORKS for OpenVMS (NetWare) files moved to SYS VolumeZ         %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PWVN].I         %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAILn:         %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands=         %PWRK-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COM M         %PWRK-I-SPECIFY, Specifying target directories for the provided files 1         %PWRK-I-OBSOLETE, Deleting obsolete filesa  4                                           Next Steps4                                           ----------  R             To continue the installation procedure, enter the following command to?             execute the server configuration command procedure:   H       Sample NetWare Server Installation and Configuration Procedure C-3 a         1      Sample NetWare Server Installation Procedures    "          $ @SYS$UPDATE:PWVN$CONFIG  K          For information about the configuration command procedure, see theoJ          PATHWORKS (Advanced Server) Installation and Configuration Guide.  S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...t  2       Starting Installation Verification Procedure/       for PATHWORKS V1.0G for OpenVMS (NetWare)l  /      %PWVN-I-NORMAL, IVP completed successfullyn2       Installation of PWRK V6.0 completed at 15:55  C          Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORYT  K          Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATAS  '       VMSINSTAL procedure done at 15:56   E      ________________________________________________________________   2      Sample NetWare Server Configuration Procedure  D            The following example shows a sample configuration dialog"            for the NetWare server.          $ @SYS$UPDATE:PWVN$CONFIG  M             *****************************************************************RM             * PATHWORKS V1.0G for OpenVMS (NetWare) Configuration Procedure *nM             *****************************************************************(M             *                                                               *(M             *                  Copyright (C) 1992, 1997 by                  *SM             *     Digital Equipment Corporation, Maynard, Massachusetts     *sM             *                           and                                 *-M             *                   Novell, Incorporated                        *-M             *                   All rights reserved.                        * M             *                                                               * M             *****************************************************************   L          This procedure will help you to set up and configure your PATHWORKS,          for OpenVMS (NetWare) installation.    G      C-4 Sample NetWare Server Installation and Configuration ProcedureK A  n      H                            Sample NetWare Server Configuration Procedure    M             If you need help with any question asked by this procedure, reply 5             to the question with a question mark (?).S  #         * Press RETURN to continue:d  C             Defining PATHWORKS for OpenVMS (NetWare) logical names.a  L             PATHWORKS stores and accesses the following types of data files:  +             o Configuration parameter files '             o License server data files1             o Log filesi!             o Printer spool filesI*             o Virtual memory section files  N             You can specify any existing OpenVMS disk device that has at leastF             12000 free blocks of disk space to store these data files.  M             Note: the server frequently accesses the data files stored on the O             disk.  If these files are stored on the system disk, it can degrade R             the performance of both the OpenVMS system and the server.  Therefore,R             Digital recommends that you specify a disk other than the system disk.  #         * Press RETURN to continue:p  Q             If this OpenVMS cluster has multiple system disks, make sure that allr5             nodes on which you plan to run PATHWORKS:r  P             o Use the same disk device to store and access PATHWORKS data files.  Q             o Share the same SYSUAF.DAT file. In each system disk's startup file,kN               define a system logical name that points all nodes to the shared+               SYSUAF.DAT file. For example:s  O               $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dato  F               The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM  J         * Enter disk device name where PATHWORKS data files will be stored$         [SYS$SYSDEVICE:]: DISK$PWRK::         Creating PATHWORKS directory tree on DISK$PWRK:...*         Creating NetWare directory tree...  W             Scanning for supported Ethernet/TokenRing/FDDI controllers.  Please wait...i  U             PATHWORKS for OpenVMS (NetWare) has never been configured on this system.n  #         * Press RETURN to continue:a  H       Sample NetWare Server Installation and Configuration Procedure C-5           2      Sample NetWare Server Configuration Procedure    :                      +-----------------------------------+:                      | Current Configuration Information |:                      +-----------------------------------+;                      Type Control-Y to abort configuration.i  -       Server name                : COBRAZ_PNW '       NVT Server name            : NONEt>       System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]%       Run License Server         : NO +       Internal Network Number    : 000032B3e%       Maximum SPX sockets        : 50          Network Type    :r       Connection      :        DLPI type       :M       Network Number  :   &       Reboot system when done    : YES&       Perform Bindup             : N/A&       Start Server when done     : N/A  -         There are no networks configured yet.e         * Press RETURN to continue:  K          PATHWORKS for OpenVMS (NetWare) File Server name must be unique onl           all known IPX networks.  H      * Name of PATHWORKS for OpenVMS (NetWare) file server [COBRAZ_PNW]:  O          The PATHWORKS for OpenVMS (NetWare) product requires a system-specific K          directory  to  hold configuration information for the file server, L          and print server.  It needs to be on a disk with at least 3000 free          disk blocks.   @      * System-specific directory  [SYS$SPECIFIC:[PWVN$PRIVATE]]:  N          Novell Virtual Terminal (NVT) allows NetWare clients to log into thisO          node using terminal emulation software that supports the NVT protocol.   8      * Do you want to configure NVT on this system [NO]?  K          PATHWORKS for OpenVMS (NetWare) client licenses are granted by thenK          License Server.  In order to run a License Server, you must have aS'          loaded PAK of client licenses.s  G      C-6 Sample NetWare Server Installation and Configuration Procedureo u  B      H                            Sample NetWare Server Configuration Procedure    R             In an OpenVMS cluster, all members either do or do not run the licenseI             server, even though only one member actively serves licenses.sM             However, if this member fails and stops serving licenses, another ,             member takes over automatically.  B         * Do you want to run a License Server on this system [NO]?  L             This is the internal network number used by the file server.  ItS             should be unique on your network (i.e. there should be no other NetWareS@             File Server with this same internal network number).  O             If you are running DECnet, the default value is your DECnet address ;             converted to hex and padded with leading zeros.f             e.g.:NK                 node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864"   Q             If you are not running DECnet, the default value is "00000DEC" (whichr;             just happens to be a valid hexadecimal number).v  ;         * Internal network number (hexadecimal) [000032B3]:e  Q             Maximum SPX sockets is the maximum number of SPX sockets available todQ             processes using the IPX/SPX stack provided with PATHWORKS for OpenVMS P             (NetWare).  If you plan to only use PATHWORKS for OpenVMS (NetWare),R             then you need not set SPX sockets any larger than max NVT connections.R             If, however, you are planning on using other products that use the IPXO             stack, then you should consult the documentation for those products N             when configuring this parameter.  Valid values for SPX sockets areL             50, 200, 500 and 1000 (but no smaller than max NVT connections).  P             If you change this parameter, you must reboot for it to take effect.  #         * Maximum SPX sockets [50]:Y            Network Type    :          Connection      :          DLPI type       :          Network Number  :  0            There are no networks configured yet.  H             At least one network must be configured in order to proceed.  3         * Network Configuration Action (ADD) [ADD]:e&             Configuring a new network.  H       Sample NetWare Server Installation and Configuration Procedure C-7 O  V      2      Sample NetWare Server Configuration Procedure    @          There are two types of networks that can be configured.I          "LOCAL" networks are networks that have direct connections to an Q          physical Network controller.  There can only be as many "LOCAL" networks B          as there are physical Network controllers on this system.N          "TUNNEL" networks connect to another node also running the IPX DECnetS          Tunnel. The total number of "TUNNEL" networks is eight, minus however many T          "LOCAL" networks are configured (i.e. if 2 "LOCAL" networks are configured,N          then there can be up to 6 "TUNNEL" networks").  There can only be one;          "TUNNEL" network for each remote DECnet node name.t@       "NONE" returns you to Network Configuration Action prompt.  ,      * Network Type (LOCAL,TUNNEL,NONE) [L]:  1      Currently available Network controller list:a  )           EZA(Ethernet),  FAA(FDDI), NONE L           "NONE" will return you to the Network Configuration Action prompt.  <      * Choose a Network controller from above listing [EZA]:  C            Input values for selecting a frame-type (DLPI-type) are:l  C                              DIX/SNAP    IEEE-802.2       Raw-802.3eE                   Media:                  (Sap E0)      (Old: Novell)eF                    -----      --------    ----------     -------------0              Token Ring:       (1)           (2)0                    FDDI:       (3)           (4)<                Ethernet:       (5)           (6)         (7)  9       Select a frame type for this >>>ETHERNET<<< device.t  P      *   Enter 5 if Ethernet_II(DIX), 6 if 802.2(Sap E0), or 7 if Raw-802.3 [5]:  N          Each configured network must have a unique Network Number.  This is aP          hexadecimal (0-9,A-F) number that can be up to 8 digits long.  For moreP          information on choosing a Network Number, see the PATHWORKS for OpenVMS-          (NetWare) Server Installation Guide.sK          "NONE" will return you to the Network Configuration Action prompt.   "      * Network Number [0]: 2100001                              #1d                            ---       Network Type    :   Local        Connection      :   EZAn$       DLPI type       :   ETH_II_DIX"       Network Number  :   02100001  G      C-8 Sample NetWare Server Installation and Configuration Proceduret .         H                            Sample NetWare Server Configuration Procedure    >             A maximum of eight (8) networks can be configured.  L             If the above networks are configured correctly, then enter NONE.  G         * Network Configuration Action (ADD,DELETE,MODIFY,NONE) [NONE]:r  Q             This configuration procedure can reboot the system automatically when R             it completes.  If you do not answer YES, you must reboot the system byQ             hand before starting the PATHWORKS for OpenVMS (NetWare) file server.d  5         * Do you want to reboot the system now [YES]?t  =                         +-----------------------------------+e=                         | Current Configuration Information |i=                         +-----------------------------------+s>                         Type Control-Y to abort configuration.  0          Server name                : COBRAZ_PNW*          NVT Server name            : NONEA          System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]k(          Run License Server         : NO.          Internal Network Number    : 000032B3(          Maximum SPX sockets        : 50                                  #1!                               ---V"          Network Type    :   Local           Connection      :   EZA'          DLPI type       :   ETH_II_DIX %          Network Number  :   02100001   )          Reboot system when done    : YESl)          Perform Bindup             : N/Ag)          Start Server when done     : N/A                       H       Sample NetWare Server Installation and Configuration Procedure C-9 x  i      2      Sample NetWare Server Configuration Procedure    0      * Is this configuration satisfactory [YES]?1      Writing PWVN$CONF_DIR:PWVN$NWCONFIG.CFG file 2      Writing PWVN$CONF_DIR:PWVN$NPSCONFIG.CFG file5      Writing PWVN$CONF_DIR:PWVN$CONF_SYMBOLS.COM fileiB      Writing Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$MSGS.DATP      Writing Sconsole Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$SCONSOLE.HELPI      Writing Config Help file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$CONFIG.HELPVT      Writing NetWare printer config file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$NWPRINT.CFGB      Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM fileE      Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM file O      Setting file ownership in SYS$SYSDEVICE:[PWVN$SYSVOL] to user PWRK$DEFAULTHF      Ignore any "SYSTEM-W-ACCONFLICT, file access conflict." warnings.  O          To start PATHWORKS for OpenVMS (NetWare), issue the following command:   2                      @SYS$STARTUP:PWVN$STARTUP.COM  D          DIGITAL recommends that the above command be placed in yourJ          site-specific system startup file in the SYS$MANAGER directory toJ          automatically start PATHWORKS for OpenVMS (NetWare) each time the          system is re-booted.   O          IMPORTANT:  Some sites use OpenVMS disk quotas.  If your site does so, K          then  you may need to use the DISKQUOTA utility and enter a record ?          for the PATHWORKS for OpenVMS (NetWare) Guest Account.o  N          IMPORTANT:  By default the PATHWORKS for OpenVMS (NetWare) SUPERVISORJ          account does not have a password.  It is suggested that after theM          file server is running that you change the SUPERVISOR password. NotehN          that this must be done from a PC client logged in to this file server)          using the client utility SYSCON.Y  J          The configuration of PATHWORKS for OpenVMS (NetWare) is complete.                        H      C-10 Sample NetWare Server Installation and Configuration Procedure t  o                  H                                                                        DH         ________________________________________________________________  H         Sample PATHWORKS Advanced Server and NetWare Server InstallationH                                                        and Configuration      D               This appendix shows a sample installation and a sampleC               configuration procedure on an OpenVMS cluster for theGE               PATHWORKS Advanced Server and NetWare servers combined.L    H         ________________________________________________________________  D         Sample Combined PATHWORKS Advanced Server and NetWare Server         Installation Procedure  F               The following example shows a sample installation dialog@               for both the PATHWORKS Advanced Server and NetWare               servers.  >         $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK]A          OpenVMS AXP Software Product Installation Procedure V6.2ER         It is 16-MAY-1997 at 14:56.Enter a question mark (?) at any time for help.F         * Are you satisfied with the backup of your system disk [YES]?  1         The following products will be processed:e           PWRK V6.0o5          Beginning installation of PWRK V6.0 at 14:56   >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.o  +          PATHWORKS for OpenVMS Installation   6             Please select which components to install:  6          PATHWORKS V6.0  for OpenVMS (Advanced Server).          PATHWORKS V1.0G for OpenVMS (NetWare)  T         * Do you want to install the PATHWORKS for OpenVMS (Advanced Server) [NO]? Y;         * Do you want to install the NetWare server [NO]? Yu  H  Advanced   Server and NetWare Server Installation and Configuration D-1 l  o      X      Sample Combined PATHWORKS Advanced Server and NetWare Server Installation Procedure    0      The following components will be installed:  2       PATHWORKS V6.0 for OpenVMS (Advanced Server)+       PATHWORKS V1.0G for OpenVMS (NetWare)m  A      If the selection is correct, the installation will continue.:D      If the selection is not correct, you can change your selection.<      Press CTRL/Y if you want to terminate the installation.  &      * Is the selection correct [YES]?K      * Do you want to run the IVP after the installation is finished [YES]?_F      * Do you want to purge files replaced by this installation [YES]?6      %PWRK-I-FREEBLKS, Checking for 110600 free blocks  E                    User Accounts and User Identification Codes (UICs)PE                    --------------------------------------------------*  O          PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account,fO          PWRK$DEFAULT, and  a guest account, PWRK$GUEST.  The default UIC group*E          number for both these new accounts depends on the following:   N          o If you are installing the server for the first time, the default is@            the first unused UIC group number, starting with 360.  O          o If there is an existing account PCFS$ACCOUNT, the default is the UICn5            group number associated with PCFS$ACCOUNT.   R          o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, the defaultQ            is the UIC group number associated with PWRK$DEFAULT or PWRK$GUEST, in R            preference to PCFS$ACCOUNT.  However, the default UIC group number willB            not be used to change the UIC of any existing accounts.  M          For more information about UIC group numbers, see the OpenVMS System(          Manager's Manual.  L      * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]:  L          The PATHWORKS for OpenVMS (NetWare) product comes with a SYS volumeN          containing client files used by the file server.  These files requireK          a minimum of 34000 free disk blocks.  However, if the disk clusters=          size is greater than 3, more space will be required.e  L          The file server uses the SYS volume location you specify as the topO          level directory for the SYS volume.  SYS volume subdirectories include N          SYSTEM, MAIL, PUBLIC, and LOGIN.  Client utilities such as SYSCON andF          FILER are placed in these subdirectories during installation.  [      D-2 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configurationr b  k      H  PATHWORKS     Advanced Server and NetWare Server Installation Procedure    Q             Note: the server frequently accesses the data files stored on the SYSrQ             volume.  If these files are stored on the system disk, it can degradenR             the performance of both the OpenVMS system and the server.  Therefore,R             Digital recommends that you specify a disk other than the system disk.  D         * NetWare SYS volume location [SYS$SYSDEVICE:[PWVN$SYSVOL]]:         DISK$PWRK:[PWVN$SYSVOL]i  =                        Optional DECprint Supervisor Available =                        --------------------------------------   J             The PATHWORKS for OpenVMS distribution media includes two kitsC             for the DECprint Supervisor for OpenVMS: VAX and Alpha.rK             DECprint Supervisor for OpenVMS is a family of layered productssL             that runs on OpenVMS VAX and Alpha to provide access through theL             OpenVMS queueing system to selected PostScript printers.  To useI             DECprint Supervisor for OpenVMS, you must install the kit for]O             either VAX or Alpha accordingly. You do not need a separate license P             to use DECprint Supervisor for OpenVMS with Advanced Server clients.  #         * Press RETURN to continue:t  B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.  S         %PWRK-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUESTCV         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$DEFAULT.5         %UAF-I-ADDMSG, user record successfully added a         %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights database-T         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST.5         %UAF-I-ADDMSG, user record successfully addedm_         %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights databasei>         %VMSINSTAL-I-RESTORE, Restoring product save set C ...>         %VMSINSTAL-I-RESTORE, Restoring product save set E ...>         %VMSINSTAL-I-RESTORE, Restoring product save set G ...N         %PWRK-I-RESTORE, Restoring product save set H (NetWare SYS Volume) ...Z         %PWRK-I-PURGING, Purging PATHWORKS for OpenVMS (NetWare) files moved to SYS VolumeZ         %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PWVN].I         %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAILn:         %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands=         %PWRK-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COM(M         %PWRK-I-SPECIFY, Specifying target directories for the provided filesi1         %PWRK-I-OBSOLETE, Deleting obsolete files     H  Advanced   Server and NetWare Server Installation and Configuration D-3 s  l      X      Sample Combined PATHWORKS Advanced Server and NetWare Server Installation Procedure    1                                        Next Steps 1                                        ----------r  P          To continue the installation procedure, enter the following commands to=          execute the server configuration command procedures:i  "          $ @SYS$UPDATE:PWRK$CONFIG"          $ @SYS$UPDATE:PWVN$CONFIG  L          For information about the configuration command procedures, see theJ          PATHWORKS (Advanced Server) Installation and Configuration Guide.  S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   2       Starting Installation Verification Procedure6       for PATHWORKS V6.0 for OpenVMS (Advanced Server)  /      %PWRK-I-NORMAL, IVP completed successfully   2       Starting Installation Verification Procedure/       for PATHWORKS V1.0G for OpenVMS (NetWare)e  /      %PWVN-I-NORMAL, IVP completed successfullyL2       Installation of PWRK V6.0 completed at 15:05  C          Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY   K          Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA   '       VMSINSTAL procedure done at 15:05a                              [      D-4 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuratione o  x      H  Combined PATHWORKS Advanced Server and NetWare Configuration Procedures  H         ________________________________________________________________  =         Sample Combined PATHWORKS Advanced Server and NetWare           Configuration Procedures  F               The following example shows sample configuration dialogsD               for the PATHWORKS Advanced Server and NetWare servers.  !         $ @SYS$UPDATE:PWRK$CONFIG L         PATHWORKS V6.0 for OpenVMS (Advanced Server) Configuration Procedure  L             PATHWORKS stores and accesses the following types of data files:  +             o Configuration parameter filesn'             o License server data files              o Log filese!             o Printer spool filesh*             o Virtual memory section files  N             You can specify any existing OpenVMS disk device that has at leastF             12000 free blocks of disk space to store these data files.  M             Note: the server frequently accesses the data files stored on theaO             disk.  If these files are stored on the system disk, it can degradePR             the performance of both the OpenVMS system and the server.  Therefore,R             Digital recommends that you specify a disk other than the system disk.  !         Press RETURN to continue:t  Q             If this OpenVMS cluster has multiple system disks, make sure that allo5             nodes on which you plan to run PATHWORKS:e  P             o Use the same disk device to store and access PATHWORKS data files.  Q             o Share the same SYSUAF.DAT file. In each system disk's startup file,aN               define a system logical name that points all nodes to the shared+               SYSUAF.DAT file. For example:   O               $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat   F               The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM  H         Enter disk device name where PATHWORKS data files will be stored$         [SYS$SYSDEVICE:]: DISK$PWRK::         Creating PATHWORKS directory tree on DISK$PWRK:...2         Creating Advanced Server directory tree...A         Copying client files to Advanced Server directory tree...wW         Creating PATHWORKS Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT ...e  H  Advanced   Server and NetWare Server Installation and Configuration D-5 N  o      S      Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedures     N          Changing the server configuration parameters will allow you to modifyL          this server's client capacity and select the transports to be used.  *          COBRAZ is currently configured to$              + support 20 PC clients5              + use the following transport(s): DECnetE  P          If you want this server to be the primary domain controller, you shouldQ          configure it to use all the transports used by any of the backup servers-          in the domain.:  M          If you want this server to be a backup domain controller, you should P          configure it to have at least one transport in common with the domain'sK          primary domain controller, otherwise this configuration will fail.   M          If you do not change the configuration parameters now, you may do so &          later by typing ADMIN/CONFIG.  L      Do you want to change the server configuration parameters now? [YES]: N  1      Reading current configuration parameters ...,  L        PATHWORKS V6.0 for OpenVMS is presently configured to run as follows:  +         1.  Run the license server:      NOC+         2.  Enable Timesource service:   NOk,         3.  Enable Alerter service:      YES6         3a. Alert user names:            Administrator)         4.  Enable Netlogon service:  YES -         5.  Advanced Server domain:  LANGROUP *         6.  Advanced Server role:  PRIMARY1         7.  Advanced Server computer name: COBRAZo9         7a. PATHWORKS OpenVMS cluster alias: COBRAZ_ALIASlT         8.  Server announce comment:    PATHWORKS V6.0 for OpenVMS (Advanced Server)=      Enter item number, or RETURN to use these values [DONE]:         Saving parameters ....      Checking the access control list file ...'      Successfully created new ACL store B      Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB. ...$      New sharefile has been created.      ADMIN$ addeds      IPC$ added       PWUTIL addedy  E          The Advanced Server Administrator network account is used tolB          administer the server.  The Administrator network account<          is mapped by default to the OpenVMS SYSTEM account.  [      D-6 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration- -  -      H  Combined PATHWORKS Advanced Server and NetWare Configuration Procedures    R             If this server is to join an Advanced Server domain, the AdministratorG             network account password should be the same as the password[C             to the domain's existing Administrator network account.t  I             The network account password can be up to 14 characters long.   5         Enter Administrator network account password:   $         Re-enter to verify password:  >         Changing password for Administrator network account...$         Checking system resources...  O         The current system configuration for COBRAZ will support 20 PC clients.m.         PATHWORKS is configured to use DECnet.  T             To automatically start PATHWORKS V6.0 for OpenVMS at system startup, youT             should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file.  $          $ @SYS$STARTUP:PWRK$STARTUP  Q             Note: Add this line below the lines that start all network transportsi             (such as DECnet).I  Q             Before starting PATHWORKS V6.0 for OpenVMS on this system, be sure toaQ             execute @SYS$UPDATE:PWRK$CONFIG on each node that will run PATHWORKS.e  S         Do you want to start PATHWORKS V6.0 for OpenVMS on node COBRAZ now [yes]: YF.         PATHWORKS file server will use DECnet.4         PATHWORKS mail notification will use DECnet.<         Process NETBIOS created with identification 202000ABC         Process PWRK$LICENSE_R created with identification 202000AE$I         The PATHWORKS V6.0 server is configured to support 20 PC clients.W@         Process PWRK$MASTER created with identification 202000B3H         The master process will now start all other PATHWORKS processes.                    H  Advanced   Server and NetWare Server Installation and Configuration D-7 P  M      S      Sample Combined PATHWORKS Advanced Server and NetWare Configuration Proceduresc          $ @SYS$UPDATE:PWVN$CONFIG  M             *****************************************************************)M             * PATHWORKS V1.0G for OpenVMS (NetWare) Configuration Procedure *eM             ***************************************************************** M             *                                                               *rM             *                  Copyright (C) 1992, 1997 by                  *OM             *     Digital Equipment Corporation, Maynard, Massachusetts     *.M             *                           and                                 *gM             *                   Novell, Incorporated                        *eM             *                   All rights reserved.                        * M             *                                                               * M             *****************************************************************i  L          This procedure will help you to set up and configure your PATHWORKS,          for OpenVMS (NetWare) installation.  J          If you need help with any question asked by this procedure, reply2          to the question with a question mark (?).         * Press RETURN to continue:  @          Defining PATHWORKS for OpenVMS (NetWare) logical names.  I          PATHWORKS stores and accesses the following types of data files:t  (          o Configuration parameter files$          o License server data files          o Log files          o Printer spool files'          o Virtual memory section files_  K          You can specify any existing OpenVMS disk device that has at leastrC          12000 free blocks of disk space to store these data files.n  J          Note: the server frequently accesses the data files stored on theL          disk.  If these files are stored on the system disk, it can degradeO          the performance of both the OpenVMS system and the server.  Therefore,cO          Digital recommends that you specify a disk other than the system disk.o         * Press RETURN to continue:  N          If this OpenVMS cluster has multiple system disks, make sure that all2          nodes on which you plan to run PATHWORKS:  M          o Use the same disk device to store and access PATHWORKS data files.S  [      D-8 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configurationl e  t      H  Combined PATHWORKS Advanced Server and NetWare Configuration Procedures    Q             o Share the same SYSUAF.DAT file. In each system disk's startup file,fN               define a system logical name that points all nodes to the shared+               SYSUAF.DAT file. For example:S  O               $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.date  F               The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM  J             The PATHWORKS directory tree already exists on SYS$SYSDEVICE:.K             If you specify a different disk device, the PATHWORKS directoryt1             tree will be moved to the new device.e  J         * Enter disk device name where PATHWORKS data files will be stored$         [SYS$SYSDEVICE:]: DISK$PWRK:*         Creating NetWare directory tree...  W             Scanning for supported Ethernet/TokenRing/FDDI controllers.  Please wait...e  U             PATHWORKS for OpenVMS (NetWare) has never been configured on this system.h  #         * Press RETURN to continue:d  =                         +-----------------------------------+a=                         | Current Configuration Information | =                         +-----------------------------------+i>                         Type Control-Y to abort configuration.  0          Server name                : COBRAZ_PNW*          NVT Server name            : NONEA          System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]S(          Run License Server         : NO.          Internal Network Number    : 000032B3(          Maximum SPX sockets        : 50            Network Type    :          Connection      :          DLPI type       :          Network Number  :  )          Perform Bindup             : N/At)          Start Server when done     : YES   0            There are no networks configured yet.  #         * Press RETURN to continue:c  H  Advanced   Server and NetWare Server Installation and Configuration D-9 r  s      S      Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedurese    K          PATHWORKS for OpenVMS (NetWare) File Server name must be unique on            all known IPX networks.  H      * Name of PATHWORKS for OpenVMS (NetWare) file server [COBRAZ_PNW]:  O          The PATHWORKS for OpenVMS (NetWare) product requires a system-specificdK          directory  to  hold configuration information for the file server,mL          and print server.  It needs to be on a disk with at least 3000 free          disk blocks.   @      * System-specific directory  [SYS$SPECIFIC:[PWVN$PRIVATE]]:  N          Novell Virtual Terminal (NVT) allows NetWare clients to log into thisO          node using terminal emulation software that supports the NVT protocol.l  8      * Do you want to configure NVT on this system [NO]?  K          PATHWORKS for OpenVMS (NetWare) client licenses are granted by the K          License Server.  In order to run a License Server, you must have at'          loaded PAK of client licenses.d  O          In an OpenVMS cluster, all members either do or do not run the licenseSF          server, even though only one member actively serves licenses.J          However, if this member fails and stops serving licenses, another)          member takes over automatically.   N          If you choose to run the license server, then the LAN Manager startupM          command procedure will also start the license server.  If you chooseaL          not to run the license server, then the LAN Manager startup command:          procedure will also not start the license server.  ?      * Do you want to run a License Server on this system [NO]?i  I          This is the internal network number used by the file server.  It P          should be unique on your network (i.e. there should be no other NetWare=          File Server with this same internal network number).a  L          If you are running DECnet, the default value is your DECnet address8          converted to hex and padded with leading zeros.          e.g.:H              node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864"  N          If you are not running DECnet, the default value is "00000DEC" (which8          just happens to be a valid hexadecimal number).  8      * Internal network number (hexadecimal) [000032B3]:  \      D-10 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration           H  Combined PATHWORKS Advanced Server and NetWare Configuration Procedures    Q             Maximum SPX sockets is the maximum number of SPX sockets available toKQ             processes using the IPX/SPX stack provided with PATHWORKS for OpenVMSnP             (NetWare).  If you plan to only use PATHWORKS for OpenVMS (NetWare),R             then you need not set SPX sockets any larger than max NVT connections.R             If, however, you are planning on using other products that use the IPXO             stack, then you should consult the documentation for those products N             when configuring this parameter.  Valid values for SPX sockets areL             50, 200, 500 and 1000 (but no smaller than max NVT connections).  P             If you change this parameter, you must reboot for it to take effect.  #         * Maximum SPX sockets [50]:.            Network Type    :          Connection      :          DLPI type       :          Network Number  :  0            There are no networks configured yet.  H             At least one network must be configured in order to proceed.  3         * Network Configuration Action (ADD) [ADD]:n&             Configuring a new network.  C             There are two types of networks that can be configured. L             "LOCAL" networks are networks that have direct connections to anT             physical Network controller.  There can only be as many "LOCAL" networksE             as there are physical Network controllers on this system.tQ             "TUNNEL" networks connect to another node also running the IPX DECneteV             Tunnel. The total number of "TUNNEL" networks is eight, minus however manyW             "LOCAL" networks are configured (i.e. if 2 "LOCAL" networks are configured,tQ             then there can be up to 6 "TUNNEL" networks").  There can only be onet>             "TUNNEL" network for each remote DECnet node name.C          "NONE" returns you to Network Configuration Action prompt.r  /         * Network Type (LOCAL,TUNNEL,NONE) [L]:u  4         Currently available Network controller list:  ,              EZA(Ethernet),  FAA(FDDI), NONEO              "NONE" will return you to the Network Configuration Action prompt.   ?         * Choose a Network controller from above listing [EZA]:6  F               Input values for selecting a frame-type (DLPI-type) are:  H  Advanced  Server and NetWare Server Installation and Configuration D-11 H  K      S      Sample Combined PATHWORKS Advanced Server and NetWare Configuration Proceduresn    C                              DIX/SNAP    IEEE-802.2       Raw-802.3rE                   Media:                  (Sap E0)      (Old: Novell)iF                   ------      --------    ----------     -------------0              Token Ring:       (1)           (2)0                    FDDI:       (3)           (4)@                Ethernet:       (5)           (6)             (7)  9       Select a frame type for this >>>ETHERNET<<< device.d  P      *   Enter 5 if Ethernet_II(DIX), 6 if 802.2(Sap E0), or 7 if Raw-802.3 [5]:  N          Each configured network must have a unique Network Number.  This is aP          hexadecimal (0-9,A-F) number that can be up to 8 digits long.  For moreP          information on choosing a Network Number, see the PATHWORKS for OpenVMS-          (NetWare) Server Installation Guide.OK          "NONE" will return you to the Network Configuration Action prompt.   "      * Network Number [0]: 2100001                              #1                             ---       Network Type    :   Locale       Connection      :   EZA $       DLPI type       :   ETH_II_DIX"       Network Number  :   02100001  ;          A maximum of eight (8) networks can be configured.e  I          If the above networks are configured correctly, then enter NONE.c  D      * Network Configuration Action (ADD,DELETE,MODIFY,NONE) [NONE]:  T          This configuration procedure can start PATHWORKS for OpenVMS (NetWare) whenS          it completes.  If you do not answer YES, then BINDUP will not be run, event%          if you have chosen to do so.   F      * Do you want to start PATHWORKS for OpenVMS (NetWare) now [YES]?  :                      +-----------------------------------+:                      | Current Configuration Information |:                      +-----------------------------------+;                      Type Control-Y to abort configuration.P      \      D-12 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration e         H  Combined PATHWORKS Advanced Server and NetWare Configuration Procedures    0          Server name                : COBRAZ_PNW*          NVT Server name            : NONEA          System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE] (          Run License Server         : NO.          Internal Network Number    : 000032B3(          Maximum SPX sockets        : 50                                  #1!                               ---W"          Network Type    :   Local           Connection      :   EZA'          DLPI type       :   ETH_II_DIXe%          Network Number  :   02100001R  )          Perform Bindup             : N/AN)          Start Server when done     : YESd  3         * Is this configuration satisfactory [YES]? 4         Writing PWVN$CONF_DIR:PWVN$NWCONFIG.CFG file5         Writing PWVN$CONF_DIR:PWVN$NPSCONFIG.CFG fileC8         Writing PWVN$CONF_DIR:PWVN$CONF_SYMBOLS.COM fileE         Writing Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$MSGS.DATpS         Writing Sconsole Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$SCONSOLE.HELPtL         Writing Config Help file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$CONFIG.HELPW         Writing NetWare printer config file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$NWPRINT.CFGnE         Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM file H         Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM fileR         Setting file ownership in SYS$SYSDEVICE:[PWVN$SYSVOL] to user PWRK$DEFAULTI         Ignore any "SYSTEM-W-ACCONFLICT, file access conflict." warnings.sH         Defining logical names for PATHWORKS V1.0G for OpenVMS (NetWare).         Begin verifying minimum resources...OK1         Complete verifying minimum resources...OKt+         PATHWORKS file server will use IPX.s4         PATHWORKS mail notification will use DECnet.'         Process NETBIOS already createdo.         Process PWRK$LICENSE_R already created%         Starting IPX Daemon (NPSD)...v  :         Starting PATHWORKS for OpenVMS (NetWare) Server...            H  Advanced  Server and NetWare Server Installation and Configuration D-13 n  r      S      Sample Combined PATHWORKS Advanced Server and NetWare Configuration ProceduresR          OK       Purging old server logs...Y       Purging old config files...8      IPX/DECnet Tunnel Daemon (STU)           : INACTIVE6      IPX Daemon (NPSD)                        : ACTIVE6      PATHWORKS for OpenVMS (NetWare) Server   : ACTIVE8      Print Services                           : INACTIVE8      NVT Daemon (NVT)                         : INACTIVE  K          PATHWORKS for OpenVMS (NetWare) has been started with the command:h  2                      @SYS$STARTUP:PWVN$STARTUP.COM  D          DIGITAL recommends that the above command be placed in yourJ          site-specific system startup file in the SYS$MANAGER directory toJ          automatically start PATHWORKS for OpenVMS (NetWare) each time the          system is re-booted.b  O          IMPORTANT:  Some sites use OpenVMS disk quotas.  If your site does so,eK          then  you may need to use the DISKQUOTA utility and enter a record ?          for the PATHWORKS for OpenVMS (NetWare) Guest Account.   N          IMPORTANT:  By default the PATHWORKS for OpenVMS (NetWare) SUPERVISORJ          account does not have a password.  It is suggested that after theM          file server is running that you change the SUPERVISOR password. Note N          that this must be done from a PC client logged in to this file server)          using the client utility SYSCON.d  J          The configuration of PATHWORKS for OpenVMS (NetWare) is complete.                                \      D-14 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration s  o                  H                                                                        EH         ________________________________________________________________  H          Sample Standalone License Server Installation and ConfigurationH                                                                Procedure      G               This appendix shows sample installation and configuration)F               procedures for a standalone license server on an OpenVMS               cluster.    H         ________________________________________________________________  ?         Sample Standalone License Server Installation ProcedureO  F               The following example shows a sample installation dialog0               for the standalone license server.  >         $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK]B           OpenVMS AXP Software Product Installation Procedure V6.2#         It is 16-MAY-1997 at 16:08.i7         Enter a question mark (?) at any time for help.SF         * Are you satisfied with the backup of your system disk [YES]?  1         The following products will be processed:            PWRK V6.0 5          Beginning installation of PWRK V6.0 at 16:08n  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.   +          PATHWORKS for OpenVMS Installation*  6             Please select which components to install:  6          PATHWORKS V6.0  for OpenVMS (Advanced Server).          PATHWORKS V1.0G for OpenVMS (NetWare)  R         * Do you want to install the PATHWORKS for OpenVMS (Advanced Server) [NO]?9         * Do you want to install the NetWare server [NO]?1D         * Do you want to install the PATHWORKS license server [YES]?  H  Standalone  License Server Installation and Configuration Procedure E-1           <      Sample Standalone License Server Installation Procedure    0      The following components will be installed:  #       PATHWORKS V6.0 license servers  A      If the selection is correct, the installation will continue. D      If the selection is not correct, you can change your selection.<      Press CTRL/Y if you want to terminate the installation.  &      * Is the selection correct [YES]?  
          NOTE 
          ---- M          Because this kit provides a new streams execlet for NetBEUI, TCP/IP,aL          IPX, and SPX, you MUST reboot all nodes in the cluster that are nowM          running or have run PATHWORKS to complete installation of PATHWORKS.OJ          If you do not reboot the nodes at this time, you must remember to5          reboot them later before starting PATHWORKS.o  H          To complete the installation of this product, you should rebootJ          the system.  If it is not convenient to reboot at this time, then,          enter NO to the following question.  C          If you enter NO, the installation procedure will continue.c  P      * Will you allow a system shutdown after this product is installed [YES]? NK      * Do you want to run the IVP after the installation is finished [YES]?oF      * Do you want to purge files replaced by this installation [YES]?6      %PWRK-I-FREEBLKS, Checking for 104600 free blocks  ?          All questions have been answered.  The installation of -          PATHWORKS for OpenVMS will continue.   ;      %VMSINSTAL-I-RESTORE, Restoring product save set C ...s;      %VMSINSTAL-I-RESTORE, Restoring product save set E ...KJ      %PWRK-I-SKIPSET, Skipping product save set G (Alpha NetWare only) ...J      %PWRK-I-SKIPSET, Skipping product save set H (NetWare SYS Volume) ...F      %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL7      %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands :      %PWRK-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COMJ      %PWRK-I-SPECIFY, Specifying target directories for the provided files.      %PWRK-I-OBSOLETE, Deleting obsolete files  1                                        Next Stepsc1                                        ----------   P          To continue the installation procedure, enter the following commands to=          execute the server configuration command procedures:   R      E-2 Sample Standalone License Server Installation and Configuration Procedure    e      H                  Sample Standalone License Server Installation Procedure    %             $ @SYS$UPDATE:PWRK$CONFIGS%             $ @SYS$UPDATE:PWVN$CONFIGa  O             For information about the configuration command procedures, see theRM             PATHWORKS (Advanced Server) Installation and Configuration Guide.t  V         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  5          Starting Installation Verification Procedure-9          for PATHWORKS V6.0 for OpenVMS (Advanced Server)o  2         %PWRK-I-NORMAL, IVP completed successfully5          Installation of PWRK V6.0 completed at 16:15r  F             Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  N             Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA  *          VMSINSTAL procedure done at 16:15  H         ________________________________________________________________  H         Sample PATHWORKS Advanced Server Configuration Procedure for the!         Standalone License Server   A               The following is a sample PATHWORKS Advanced ServerBH               configuration procedure for the standalone license server.  !         $ @SYS$UPDATE:PWRK$CONFIGuL         PATHWORKS V6.0 for OpenVMS (Advanced Server) Configuration Procedure  L             PATHWORKS stores and accesses the following types of data files:  +             o Configuration parameter filesu'             o License server data filesS             o Log filesl!             o Printer spool files *             o Virtual memory section files  N             You can specify any existing OpenVMS disk device that has at leastF             12000 free blocks of disk space to store these data files.        H  Standalone  License Server Installation and Configuration Procedure E-3 p  t      _      Sample PATHWORKS Advanced Server Configuration Procedure for the Standalone License Serverc    J          Note: the server frequently accesses the data files stored on theL          disk.  If these files are stored on the system disk, it can degradeO          the performance of both the OpenVMS system and the server.  Therefore,fO          Digital recommends that you specify a disk other than the system disk.         Press RETURN to continue:  N          If this OpenVMS cluster has multiple system disks, make sure that all2          nodes on which you plan to run PATHWORKS:  M          o Use the same disk device to store and access PATHWORKS data files.,  N          o Share the same SYSUAF.DAT file. In each system disk's startup file,K            define a system logical name that points all nodes to the shareda(            SYSUAF.DAT file. For example:  L            $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat  C            The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM   E      Enter disk device name where PATHWORKS data files will be storedo!      [SYS$SYSDEVICE:]: DISK$PWRK:n7      Creating PATHWORKS directory tree on DISK$PWRK:...o  T        The PATHWORKS license server can serve PATHWORKS licenses for Advanced ServerN        clients over DECnet, NetBEUI, and TCP/IP, and NetWare clients over IPX.Q        The Advanced Server and NetWare file servers do not need to be running for %        the license server to operate.a  L        If you want to serve PATHWORKS licenses for NetWare clients over IPX,:        you must later execute @SYS$UPDATE:PWVN$CONFIG.COM.  ?      Do you want to serve PATHWORKS licenses over DECnet [yes]: ?      Do you want to serve PATHWORKS licenses over NetBEUI [no]:j>      Do you want to serve PATHWORKS licenses over TCP/IP [no]:  A      Do you want to start the PATHWORKS license server now [yes]:RF      %PWRK-F-REBOOT, system must be rebooted before starting PATHWORKS  E      ________________________________________________________________   >      Sample NetWare Configuration Procedure for the Standalone      License Servera  D            The following is a sample NetWare configuration procedure-            for the standalone license server.   R      E-4 Sample Standalone License Server Installation and Configuration Procedure e  P      H  NetWare       Configuration Procedure for the Standalone License Server    !         $ @SYS$UPDATE:PWVN$CONFIGu  P                *****************************************************************P                * PATHWORKS V1.0G for OpenVMS (NetWare) Configuration Procedure *P                *****************************************************************P                *                                                               *P                *                  Copyright (C) 1992, 1997 by                  *P                *     Digital Equipment Corporation, Maynard, Massachusetts     *P                *                           and                                 *P                *                   Novell, Incorporated                        *P                *                   All rights reserved.                        *P                *                                                               *P                *****************************************************************  O             This procedure will help you to set up and configure your PATHWORKSw/             for OpenVMS (NetWare) installation.N  M             If you need help with any question asked by this procedure, replyu5             to the question with a question mark (?).i  #         * Press RETURN to continue:e  C             Defining PATHWORKS for OpenVMS (NetWare) logical names.   L             PATHWORKS stores and accesses the following types of data files:  +             o Configuration parameter filesC'             o License server data fileso             o Log filesn!             o Printer spool filesr*             o Virtual memory section files  N             You can specify any existing OpenVMS disk device that has at leastF             12000 free blocks of disk space to store these data files.  M             Note: the server frequently accesses the data files stored on the[O             disk.  If these files are stored on the system disk, it can degrade R             the performance of both the OpenVMS system and the server.  Therefore,R             Digital recommends that you specify a disk other than the system disk.  #         * Press RETURN to continue:   Q             If this OpenVMS cluster has multiple system disks, make sure that allS5             nodes on which you plan to run PATHWORKS:   P             o Use the same disk device to store and access PATHWORKS data files.  H  Standalone  License Server Installation and Configuration Procedure E-5 r  :      M      Sample NetWare Configuration Procedure for the Standalone License ServerE    N          o Share the same SYSUAF.DAT file. In each system disk's startup file,K            define a system logical name that points all nodes to the sharedr(            SYSUAF.DAT file. For example:  L            $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat  C            The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM   G          The PATHWORKS directory tree already exists on SYS$SYSDEVICE:.tH          If you specify a different disk device, the PATHWORKS directory.          tree will be moved to the new device.  G      * Enter disk device name where PATHWORKS data files will be stored !      [SYS$SYSDEVICE:]: DISK$PWRK:   T          Scanning for supported Ethernet/TokenRing/FDDI controllers.  Please wait...  R          PATHWORKS for OpenVMS (NetWare) has never been configured on this system.         * Press RETURN to continue:  :                      +-----------------------------------+:                      | Current Configuration Information |:                      +-----------------------------------+;                      Type Control-Y to abort configuration.o  >       System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]&       Serve licenses over IPX    : YES+       Internal Network Number    : 000032B3-%       Maximum SPX sockets        : 50t         Network Type    :|       Connection      :-       DLPI type       :-       Network Number  :   &       Reboot system when done    : YES&       Start Server when done     : N/A  -         There are no networks configured yet.C         * Press RETURN to continue:  O          The PATHWORKS for OpenVMS (NetWare) product requires a system-specificeK          directory  to  hold configuration information for the file server,EL          and print server.  It needs to be on a disk with at least 3000 free          disk blocks.   R      E-6 Sample Standalone License Server Installation and Configuration Procedure           H  NetWare       Configuration Procedure for the Standalone License Server    C         * System-specific directory  [SYS$SPECIFIC:[PWVN$PRIVATE]]:   N             PATHWORKS for OpenVMS (NetWare) client licenses are granted by theN             License Server, provided the License Server is configured to serveQ             licenses over IPX.  In order to run a License Server, you must have aN*             loaded PAK of client licenses.  A         * Do you want to serve PATHWORKS licenses over IPX [YES]?I  L             This is the internal network number used by the file server.  ItS             should be unique on your network (i.e. there should be no other NetWareE@             File Server with this same internal network number).  O             If you are running DECnet, the default value is your DECnet addressP;             converted to hex and padded with leading zeros.O             e.g.:WK                 node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864"P  Q             If you are not running DECnet, the default value is "00000DEC" (whichL;             just happens to be a valid hexadecimal number).C  ;         * Internal network number (hexadecimal) [000032B3]:n  Q             Maximum SPX sockets is the maximum number of SPX sockets available torQ             processes using the IPX/SPX stack provided with PATHWORKS for OpenVMSeP             (NetWare).  If you plan to only use PATHWORKS for OpenVMS (NetWare),P             the default value of 50 is acceptable. If, however, you are planningS             on using other products that use the IPX stack, then you should consult(Q             the documentation for those products when configuring this parameter.nC             Valid values for SPX sockets are 50, 200, 500 and 1000.v  P             If you change this parameter, you must reboot for it to take effect.  #         * Maximum SPX sockets [50]:             Network Type    :          Connection      :          DLPI type       :          Network Number  :  0            There are no networks configured yet.  H             At least one network must be configured in order to proceed.  3         * Network Configuration Action (ADD) [ADD]: &             Configuring a new network.  H  Standalone  License Server Installation and Configuration Procedure E-7 S  T      M      Sample NetWare Configuration Procedure for the Standalone License Server     @          There are two types of networks that can be configured.I          "LOCAL" networks are networks that have direct connections to an Q          physical Network controller.  There can only be as many "LOCAL" networksqB          as there are physical Network controllers on this system.N          "TUNNEL" networks connect to another node also running the IPX DECnetS          Tunnel. The total number of "TUNNEL" networks is eight, minus however manyMT          "LOCAL" networks are configured (i.e. if 2 "LOCAL" networks are configured,N          then there can be up to 6 "TUNNEL" networks").  There can only be one;          "TUNNEL" network for each remote DECnet node name.t@       "NONE" returns you to Network Configuration Action prompt.  ,      * Network Type (LOCAL,TUNNEL,NONE) [L]:  1      Currently available Network controller list:   )           EZA(Ethernet),  FAA(FDDI), NONEAL           "NONE" will return you to the Network Configuration Action prompt.  <      * Choose a Network controller from above listing [EZA]:  C            Input values for selecting a frame-type (DLPI-type) are:_  C                              DIX/SNAP    IEEE-802.2       Raw-802.3nE                   Media:                  (Sap E0)      (Old: Novell) E                   -----      --------    ----------     ------------- 0              Token Ring:       (1)           (2)0                    FDDI:       (3)           (4)@                Ethernet:       (5)           (6)             (7)  9       Select a frame type for this >>>ETHERNET<<< device.p  P      *   Enter 5 if Ethernet_II(DIX), 6 if 802.2(Sap E0), or 7 if Raw-802.3 [5]:  N          Each configured network must have a unique Network Number.  This is aP          hexadecimal (0-9,A-F) number that can be up to 8 digits long.  For moreP          information on choosing a Network Number, see the PATHWORKS for OpenVMS-          (NetWare) Server Installation Guide.rK          "NONE" will return you to the Network Configuration Action prompt.y  "      * Network Number [0]: 2100001                              #1s                            ---       Network Type    :   LocalR       Connection      :   EZAS$       DLPI type       :   ETH_II_DIX"       Network Number  :   02100001  R      E-8 Sample Standalone License Server Installation and Configuration Procedure O  V      H  NetWare       Configuration Procedure for the Standalone License Server    >             A maximum of eight (8) networks can be configured.  L             If the above networks are configured correctly, then enter NONE.  G         * Network Configuration Action (ADD,DELETE,MODIFY,NONE) [NONE]:e  Q             This configuration procedure can reboot the system automatically when R             it completes.  If you do not answer YES, you must reboot the system byQ             hand before starting the PATHWORKS for OpenVMS (NetWare) file server.   5         * Do you want to reboot the system now [YES]?H  =                         +-----------------------------------+h=                         | Current Configuration Information |r=                         +-----------------------------------+w>                         Type Control-Y to abort configuration.  A          System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE] )          Serve licenses over IPX    : YESE.          Internal Network Number    : 000032B3(          Maximum SPX sockets        : 50                                  #1!                               ---T"          Network Type    :   Local           Connection      :   EZA'          DLPI type       :   ETH_II_DIXr%          Network Number  :   02100001   )          Reboot system when done    : YES,)          Start Server when done     : N/Af  3         * Is this configuration satisfactory [YES]? 5         Writing PWVN$CONF_DIR:PWVN$NPSCONFIG.CFG file 8         Writing PWVN$CONF_DIR:PWVN$CONF_SYMBOLS.COM fileE         Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM fileeH         Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM file  R             To start PATHWORKS for OpenVMS (NetWare), issue the following command:  5                         @SYS$STARTUP:PWVN$STARTUP.COM   G             DIGITAL recommends that the above command be placed in your M             site-specific system startup file in the SYS$MANAGER directory topM             automatically start PATHWORKS for OpenVMS (NetWare) each time the               system is re-booted.  M             The configuration of PATHWORKS for OpenVMS (NetWare) is complete.o  H  Standalone  License Server Installation and Configuration Procedure E-9    e                  H                                                                        FH         ________________________________________________________________  H                                             Upgrade Utility Installation      F               This appendix shows a sample installation of the Upgrade               utility.    H         ________________________________________________________________  &         Installing the Upgrade Utility  C               As a first step in upgrading a system that is running2D               a previously released version of DIGITAL PATHWORKS forB               OpenVMS, you can install the Upgrade utility withoutA               installing the server. Doing this allows you to runSE               your V5 servers while performing the upgrade procedure, B               avoiding any interruption of services to your users.  B               If you install the Upgrade utility only, the on-diskD               structure and datafile format are not changed, and the?               PATHWORKS Version 5 executables are not replaced.c  E               When you execute the installation procedure on a system G               that is running PATHWORKS Version 5, the procedure offersPG               you the option of installing the Upgrade utility only. ToOC               install the Upgrade utility only, select this option.a                 Note  G               When you install the Upgrade utility only, you cannot run G               the Installation Verification Procedure (IVP); therefore, F               the prompt asking whether you want to run the IVP is not0               displayed during the installation.          H                                         Upgrade Utility Installation F-1 r  o      2      Sample Upgrade Utility Installation Procedure  E      ________________________________________________________________u  2      Sample Upgrade Utility Installation Procedure  =            The following example shows a sample procedure forg4            installation of the Upgrade utility only.  ;      $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK]p?        OpenVMS AXP Software Product Installation Procedure E7.1        It is 22-MAY-1997 at 15:14.4      Enter a question mark (?) at any time for help.E      * Are you satisfied with the backup of your system disk [YES]? yl  .      The following products will be processed:        PWRK V6.02       Beginning installation of PWRK V6.0 at 15:14  ;      %VMSINSTAL-I-RESTORE, Restoring product save set A ... P      %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  (       PATHWORKS for OpenVMS Installation  C       You have the option to install only the PATHWORKS for OpenVMSsA       Advanced Server upgrade utility, which upgrades your servertC       environment from V5 to V6.  If you choose to install only the C       upgrade utility, no file server components will be installed.d  G       The upgrade utility allows you to continue to run your V5 servers:I       while you perform the upgrade.  You may install the Advanced Serverf6       after your server environment has been upgraded.  E       However, if you choose not to install the upgrade utility only, F       the installation will proceed with the regular kit installation.I       You may invoke the upgrade utility after the installation by typing]!       @SYS$UPDATE:PWRK$V6UPGRADE.p  L       The following question allows you to install only the upgrade utility:  >      * Do you want to install the upgrade utility only [NO]? YC      %PWRK-I-VERSION, Checking for OpenVMS version 7.1, or later... F      * Do you want to purge files replaced by this installation [YES]?5      %PWRK-I-FREEBLKS, Checking for 27100 free blocksd;      %VMSINSTAL-I-RESTORE, Restoring product save set C ...e  0                                        Next Step0                                        ---------  %      F-2 Upgrade Utility Installationi s  f      H                            Sample Upgrade Utility Installation Procedure    H             To upgrade the server, enter the following command to invoke'             the server upgrade utility:s  %          $ @SYS$UPDATE:PWRK$V6UPGRADEt  H             For information about the upgrade utility, see the PATHWORKS5             (Advanced Server) Server Migration Guide.B  V         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...5          Installation of PWRK V6.0 completed at 15:15e  F             Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  N             Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA  *          VMSINSTAL procedure done at 15:16                                                          H                                         Upgrade Utility Installation F-3 e  a                  H                                                                        GH         ________________________________________________________________  H                                                          Files Installed      C               This appendix lists the files that are created during C               the installation procedure and includes the following                information:  C               o  Table G-1 lists files common to both the PATHWORKS 5                  Advanced Server and NetWare servers.h  F               o  Table G-2 lists the files installed for the PATHWORKS&                  Advanced Server only.  D               o  Table G-3 lists the files installed for the NetWare                  server only.r  C               This appendix also shows the on-disk structure of the ;               PATHWORKS Advanced Server and NetWare server.   H         ________________________________________________________________  =         Files Common to PATHWORKS Advanced Server and NetWareu  >               Table G-1 describes the files created during theC               installation of either the PATHWORKS Advanced Server,e*               the NetWare server, or both.                        H                                                      Files Installed G-1 e  S      :      Files Common to PATHWORKS Advanced Server and NetWare    D      Table G-1 Files Common to PATHWORKS Advanced Server and NetWareE      __________Server________________________________________________   E      File_________________________________Description________________o  E      DCPS$EXAMPLES:PWRK$BORDER.LUP        DECprint Supervisor printer ;                                           layup for borderss  E      DCPS$EXAMPLES:PWRK$NOBORDER.LUP      DECprint Supervisor printern>                                           layup for no borders  E      DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_    DECprint Supervisor printer @      BORDER.LUP                           layup for borders with1                                           Windowsf  E      DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_    DECprint Supervisor printereC      NOBORDER.LUP                         layup for no borders withm1                                           Windowsp  >      SYS$HELP:PCDISKHLP.HLB               DOS File Maintenance>                                           utility help library  >      SYS$HELP:PWRK$ADMIN_LIC.HLB          License Manager help1                                           libraryh  ?      SYS$HELP:PWRK060.RELEASE_NOTES       DIGITAL PATHWORKS forDC                                           OpenVMS (Advanced Server)t7                                           Release Notes   ?      SYS$HELP:PWVNV10G.RELEASE_NOTES      DIGITAL PATHWORKS foreC                                           OpenVMS (NetWare) Releasea/                                           Notes   <      SYS$LIBRARY:NETBIOSSHR.EXE           NETBIOS for DECnet9                                           shareable imagec  >      SYS$LIBRARY:PCDISKSHR.EXE            DOS File MaintenanceA                                           utility shareable images  E      SYS$LIBRARY:PCSA_MAILSHR.EXE         Mail notification shareable /                                           image.  D      SYS$LIBRARY:PWRK$CMTLIBSHR.EXE       Configurator, Monitor, andA                                           Tuner shareable library   D      SYS$LIBRARY:PWRK$CMTSHR.EXE          Configurator, Monitor, and?                                           Tuner shareable image   E                                              (continued on next page)t        G-2 Files Installed           H                    Files Common to PATHWORKS Advanced Server and NetWare    G         Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server andiH         __________________NetWare_Server________________________________  H         File_________________________________Description________________  F         SYS$LIBRARY:PWRK$CSSHR_V7.EXE        Common services shareable2                                              image  A         SYS$LIBRARY:PWRK$DEVCTL_DL1100.TLB   DEClaser 1100 deviceW<                                              control library  A         SYS$LIBRARY:PWRK$DEVCTL_DL2100.TLB   DEClaser 2100 deviced<                                              control library  B         SYS$LIBRARY:PWRK$DEVCTL_DL2100P.TLB  DEClaser 2100P device<                                              control library  A         SYS$LIBRARY:PWRK$DEVCTL_DL2200.TLB   DEClaser 2200 device <                                              control library  B         SYS$LIBRARY:PWRK$DEVCTL_DL2200P.TLB  DEClaser 2200P device<                                              control library  A         SYS$LIBRARY:PWRK$DEVCTL_DL3200.TLB   DEClaser 3200 deviceP<                                              control library  B         SYS$LIBRARY:PWRK$DEVCTL_FX1050.TLB   FX1050 device control4                                              library  A         SYS$LIBRARY:PWRK$DEVCTL_FX850.TLB    FX850 device control 4                                              library  G         SYS$LIBRARY:PWRK$DEVCTL_HP_          HP LaserJet device controle4         LASERJET.TLB                         library  A         SYS$LIBRARY:PWRK$DEVCTL_LA210.TLB    LA210 device controlo4                                              library  A         SYS$LIBRARY:PWRK$DEVCTL_LA324.TLB    LA324 device control"4                                              library  H         SYS$LIBRARY:PWRK$DEVCTL_LA50.TLB     LA50 device control library  H         SYS$LIBRARY:PWRK$DEVCTL_LA75.TLB     LA75 device control library  A         SYS$LIBRARY:PWRK$DEVCTL_LJ250.TLB    LJ250 device controlm4                                              library  H         SYS$LIBRARY:PWRK$DEVCTL_LN03.TLB     LN03 device control library  H                                                 (continued on next page)  H                                                      Files Installed G-3           :      Files Common to PATHWORKS Advanced Server and NetWare    D      Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server andE      __________________NetWare_Server________________________________2  E      File_________________________________Description________________r  B      SYS$LIBRARY:PWRK$DEVCTL_LN03P.TLB    LN03 PLUS device control1                                           library   C      SYS$LIBRARY:PWRK$DEVCTL_             Proprinter device control 1      PROPRINTER.TLB                       library   E      SYS$LIBRARY:PWRK$DEVCTL_             Silentwriter device control 1      SILENTWRITER.TLB                     library   <      SYS$LIBRARY:PWRK$FSLIB_ODS2.EXE      ODS2 addon library  C      SYS$LIBRARY:PWRK$LICENSE_LIBSHR.EXE  License shareable libraryl  <      SYS$LIBRARY:PWRK$LICENSE_            License management9      MGMTSHR.EXE                          shareable image   E      SYS$LIBRARY:PWRK$PCMALTSHR.EXE       Alternative PATHWORKS cacheoA                                           manager shareable imageo  A      SYS$LIBRARY:PWRK$PCMSHR.EXE          PATHWORKS cache managero9                                           shareable imagec  B      SYS$LIBRARY:PWRK$PRINTER_            Printer information file      INFORMATION.DAT  E      SYS$LIBRARY:PWRK$SDA.EXE             PATHWORKS extension for ther>                                           System Dump Analyzer  A      SYS$LIBRARY:PWRK$STREAMSSHR_V7.EXE   Streams shareable imageo  B      SYS$LIBRARY:PWRK$VVTERMCAP.DAT       License manager terminal>                                           capability data file  D      SYS$LIBRARY:PWRK$WINLIBSHR.EXE       Advanced Server character-=                                           cell user interfaceI9                                           shareable imageo  D      SYS$LIBRARY:PWRK$XTILIBSHR.EXE       X/Open Transport Interface;                                           shareable library   D      SYS$LIBRARY:PWRK$XTINETBIOSSHR.EXE   X/Open Transport InterfaceE                                           shareable image for NETBIOS   E                                              (continued on next page)-        G-4 Files Installed           H                    Files Common to PATHWORKS Advanced Server and NetWare    G         Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and H         __________________NetWare_Server________________________________  H         File_________________________________Description________________  G         SYS$LIBRARY:PWRK$XTINSPNBSHR.EXE     X/Open Transport InterfaceaG                                              shareable image for DECnet   G         SYS$LIBRARY:XTI.H                    X/Open Transport InterfaceR8                                              header file  G         SYS$LOADABLE_                        Data structure definitionsr;         IMAGES:PCFSDRIVERDEF.STB             for PCFSDRIVER   D         SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Streams system loadable2         V7.EXE                               image  =         SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Symbol table for B         V7.STB                               PWRK$STREAMSOS_V7.EXE  B         SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  DECnet I/O and double;         V7.EXE                               mapping driver   =         SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  Symbol table foroB         V7.STB                               SYS$PCFSDRIVER_V7.EXE  E         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Cluster Interconnect I/O 3         V7.EXE                               driverm  =         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Symbol table forsA         V7.STB                               SYS$PCIDRIVER_V7.EXEr  C         SYS$MANAGER:PWRK$DEFINE_             Command procedure thatyE         COMMANDS.COM[1]                      defines foreign commands-D                                              for PATHWORKS utilities  C         SYS$MANAGER:PWRK$SHOWSYS.COM         Command procedure that-F                                              shows status of PATHWORKS9                                              V5 processesP  C         SYS$MANAGER:PWVN$COMMANDS.COM        Command procedure that E                                              defines foreign commandssB                                              for NetWare utilities  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__           or command procedure.   H                                                 (continued on next page)  H                                                      Files Installed G-5           :      Files Common to PATHWORKS Advanced Server and NetWare    D      Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server andE      __________________NetWare_Server_________________________________  E      File_________________________________Description________________E  @      SYS$MANAGER:PWVN$COPY_CRASH.COM      Command procedure thatD                                           copies a system crash dump  ?      SYS$MESSAGE:PWRK$MSG.EXE             DIGITAL PATHWORKS for >                                           OpenVMS message file  @      SYS$STARTUP:PWRK$CHECK_PARAMS.COM    Command procedure thatA                                           checks system resources   @      SYS$STARTUP:PWRK$COMMON_             Command procedure thatA      LOGICALS.COM                         defines common logicalsr  A      SYS$STARTUP:PWRK$COMMON_             Common shutdown command 3      SHUTDOWN.COM                         procedure   @      SYS$STARTUP:PWRK$COMMON_STARTUP.COM  Common startup command3                                           procedure   D      SYS$STARTUP:PWRK$GATHER_INFO.COM     Gathers information into aB                                           save set for engineering3                                           debugging_  A      SYS$STARTUP:PWRK$LICENSE_R_          Startup for the Licensea3      START.COM                            Registrari  A      SYS$STARTUP:PWRK$LICENSE_S_          Startup for the licenses0      START.COM                            server  A      SYS$STARTUP:PWRK$LICENSE_            License server shutdowni;      SHUTDOWN.COM                         command procedureo  @      SYS$STARTUP:PWRK$LICENSE_            License server startup;      STARTUP.COM                          command procedure   @      SYS$STARTUP:PWRK$LOGICALS.COM        Command procedure that?                                           defines logical names   D      SYS$STARTUP:PWRK$SHUTDOWN.COM        Shutdown command procedure  C      SYS$STARTUP:PWRK$STARTUP.COM         Startup command procedure   E                                              (continued on next page)         G-6 Files Installed t  i      H                    Files Common to PATHWORKS Advanced Server and NetWare    G         Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server andlH         __________________NetWare_Server________________________________  H         File_________________________________Description________________  C         SYS$STARTUP:PWVN$COMMON_             Command procedure thattE         LOGICALS.COM                         defines NetWare cluster-rA                                              common logical namesl  C         SYS$STARTUP:PWVN$LOGICALS.COM        Command procedure that_D                                              defines NetWare logical2                                              names  H         SYS$STARTUP:PWVN$NPSD_START.COM      Command procedure that runsG                                              the NetWare Protocol Suite 3                                              Daemone  E         SYS$STARTUP:PWVN$SHUTDOWN.COM        NetWare shutdown commanda6                                              procedure  D         SYS$STARTUP:PWVN$STARTUP.COM         NetWare startup command6                                              procedure  H         SYS$STARTUP:PWVN$TUNNEL_START.COM    Command procedure that runsF                                              the NetWare DECnet tunnel  ?         SYS$SYSTEM:NETBIOS.EXE               NETBIOS for DECneti  A         SYS$SYSTEM:PCDISK.EXE                DOS File Maintenancen4                                              utility  B         SYS$SYSTEM:PCSA$MAIL_SERVER.EXE      PATHWORKS mail server  D         SYS$SYSTEM:PCSA_CLAIM_NAME.EXE       PCSA claim name utility  C         SYS$SYSTEM:PCX$SERVER.COM            Command procedure that G                                              starts the PC DECwindows Xl3                                              servero  @         SYS$SYSTEM:PWRK$EVTREPORT.EXE        Event logger report6                                              generator  B         SYS$SYSTEM:PWRK$KNBDAEMON.EXE        Kernel NETBIOS daemon4                                              process  H                                                 (continued on next page)  H                                                      Files Installed G-7 r         :      Files Common to PATHWORKS Advanced Server and NetWare    D      Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server andE      __________________NetWare_Server________________________________b  E      File_________________________________Description________________   E      SYS$SYSTEM:PWRK$LICENSE_             License count units utility       COUNTUNITS.EXE[1]  >      SYS$SYSTEM:PWRK$LICENSE_MANAGER.EXE  License manager user3                                           interfaceP  ;      SYS$SYSTEM:PWRK$LICENSE_             License registraro      REGISTRAR.EXE  8      SYS$SYSTEM:PWRK$LICENSE_SERVER.EXE   License server  C      SYS$SYSTEM:PWRK$LOADSTREAMS_V7.EXE   Loader for streams systemr8                                           loadable image  B      SYS$SYSTEM:PWRK$MASTER.EXE           Master process and event0                                           logger  ;      SYS$SYSTEM:PWRK$MONITOR.EXE          PATHWORKS Monitor   @      SYS$SYSTEM:PWRK$NBDAEMON.EXE         NETBIOS daemon process  E      SYS$SYSTEM:PWRK$NBSHOW.EXE[1]        NetBEUI show status utility_  >      SYS$SYSTEM:PWRK$PWMON.EXE[1]         PATHWORKS host-based9                                           monitor utility   <      SYS$SYSTEM:PWRK$SETSHO.EXE           PATHWORKS Set/Show<                                           Parameters utility  A      SYS$SYSTEM:PWRK$SHOWQUOTA.EXE        Show Disk Quota utility_  =      SYS$SYSTEM:PWRK$START.EXE            Utility that starts A                                           detached master processh  <      SYS$SYSTEM:PWRK$STOP.EXE             Utility that stops=                                           PATHWORKS processes   ?      SYS$SYSTEM:PWRK$VERIFY.EXE           Utility that verifiesmB                                           configuration parameters  D      SYS$SYSTEM:PWVN$DROUTER.EXE          NetWare utility that dumps;                                           the router tables   E      [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.  E                                              (continued on next page)         G-8 Files Installed e  n      H                    Files Common to PATHWORKS Advanced Server and NetWare    G         Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server andrH         __________________NetWare_Server________________________________  H         File_________________________________Description________________  G         SYS$SYSTEM:PWVN$GETLAN.EXE           NetWare utility that shows @                                              this node's network  H         SYS$SYSTEM:PWVN$MERGE.EXE            NetWare utility that merges@                                              configuration files  C         SYS$SYSTEM:PWVN$NPSD.EXE             NetWare Protocol Suite :                                              Daemon (NPSD)  D         SYS$SYSTEM:PWVN$NWCP.EXE             NetWare control program  H         SYS$SYSTEM:PWVN$RROUTER.EXE          NetWare utility that resets>                                              the router tables  ?         SYS$SYSTEM:PWVN$SAPD.EXE             Netware SAP Daemone  B         SYS$SYSTEM:PWVN$STUACP.EXE           NetWare DECnet tunnel  F         SYS$TEST:PWRK$IVP.COM                PATHWORKS Advanced ServerF                                              Installation Verification<                                              Procedure (IVP)  F         SYS$TEST:PWRK$IVP.DAT                PATHWORKS Advanced ServerF                                              Installation Verification@                                              Procedure data file  A         SYS$TEST:PWVN$IVP.COM                NetWare Installation C                                              Verification Procedure 2                                              (IVP)  A         SYS$TEST:PWVN$IVP.DAT                NetWare InstallationpC                                              Verification proceduree6                                              data file  C         SYS$UPDATE:PWL$SERVER_STATE.DAT[2]   NetWare license servern7                                              state file   C         SYS$UPDATE:PWRK$COMMANDS.CLD         PATHWORKS command line 8                                              definitions  H         [2]This_file_is_installed_only_if_DIGITAL_PATHWORKS_V1.0G_for___  G         OpenVMS (NetWare) is being installed and you are upgrading fromS.         PATHWORKS V1.0C for OpenVMS (NetWare).  H                                                 (continued on next page)  H                                                      Files Installed G-9           :      Files Common to PATHWORKS Advanced Server and NetWare    D      Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server andE      __________________NetWare_Server________________________________   E      File_________________________________Description________________d  @      SYS$UPDATE:PWRK$COMMON.SAV[3]        Backup saveset for theB                                           initial PATHWORKS common8                                           directory tree  >      SYS$UPDATE:PWRK$COMMON_CONFIG.COM    Common configuration;                                           command procedure   @      SYS$UPDATE:PWRK$CONFIG.COM           One-time configuration;                                           command procedure   @      SYS$UPDATE:PWRK$DEFINE_FORMS.COM[3]  Command procedure thatC                                           defines printer forms for$3                                           PATHWORKSd  D      SYS$UPDATE:PWRK$DEINSTAL.COM         DIGITAL PATHWORKS V6.0 forC                                           OpenVMS (Advanced Server) C                                           removal command procedureI  E      SYS$UPDATE:PWRK$GETPARAM.COM         Command procedure that gets E                                           a parameter from LANMAN.INIV  @      SYS$UPDATE:PWRK$INSTALL_             Command procedure that@      COMMANDS.COM                         installs PATHWORKS DCL2                                           commands  8      SYS$UPDATE:PWRK$LICENSE_CONFIG.COM   License server?                                           configuration command 3                                           procedure   @      SYS$UPDATE:PWRK$SETINI.COM           Command procedure that<                                           updates LANMAN.INI4                                           parameters  E      SYS$UPDATE:PWRK$SETPARAM.COM         Command procedure that setsYC                                           a parameter in LANMAN.INI   @      SYS$UPDATE:PWRK$VERSIONS.COM         Command procedure that?                                           shows PATHWORKS image 2                                           versions  E      [3]This_file_is_deleted_after_you_configure_the_server._________R  E                                              (continued on next page)I        G-10 Files Installed  2  d      H                    Files Common to PATHWORKS Advanced Server and NetWare    G         Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and H         __________________NetWare_Server________________________________  H         File_________________________________Description________________  B         SYS$UPDATE:PWVN$CONFIG.COM           NetWare configuration>                                              command procedure  D         SYS$UPDATE:PWVN$DEINSTAL.COM         NetWare product removal>                                              command procedure  C         SYS$UPDATE:PWVN$RESIZE_STACK.COM     Command procedure thatiC                                              configures the NetWare H         _____________________________________transports_________________    H         ________________________________________________________________  G         Files Created During the PATHWORKS Advanced Server Installation   H               Table G-2 describes the files created during the PATHWORKS+               Advanced Server installation.E  H         Table_G-2_PATHWORKS_Advanced_Server_Files_______________________  H         File_________________________________Description________________  G         SYS$HELP:PWRK$ADMIN_CFG.HLB          Configuration Manager tool 9                                              help library   E         SYS$HELP:PWRK$MANAGER.HLB            ADMINISTER commands helpe4                                              library  G         SYS$HELP:PWRK$SHOWINI.HLB[1]         Show LANMAN.INI ParametersiA                                              utility help library   A         SYS$HELP:PWRK$V6UPGRADE.HLB          Upgrade utility help 4                                              library  D         SYS$LIBRARY:PWRK$ACME_MODULE_        External authentication8         ALPHA.EXE                            ALPHA image  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__           or command procedure.r  H                                                 (continued on next page)  H                                                     Files Installed G-11 $  L      D      Files Created During the PATHWORKS Advanced Server Installation    E      Table_G-2_(Cont.)_PATHWORKS_Advanced_Server_Files_______________/  E      File_________________________________Description________________a  E      SYS$LIBRARY:PWRK$ACME_MODULE_        External authentication VAXo/      VAX.EXE                              imaged  C      SYS$LIBRARY:PWRK$CMT_LM.EXE          Advanced Server interfacee>                                           to the Configurator,<                                           Monitor, and Tuner  C      SYS$LIBRARY:PWRK$LMAPISHR.EXE        Advanced Server shareable_/                                           image   C      SYS$LIBRARY:PWRK$LMRPCAPISHR.EXE     Advanced Server shareablea/                                           imagea  C      SYS$LIBRARY:PWRK$LMRPCSHR.EXE        Advanced Server shareable /                                           image   C      SYS$LIBRARY:PWRK$LMRPCXNPSHR.EXE     Advanced Server shareable /                                           image   C      SYS$LIBRARY:PWRK$LMTASKSHR.EXE       Advanced Server shareableD/                                           imageb  C      SYS$LIBRARY:PWRK$MGTLIBSHR.EXE       Advanced Server shareableO/                                           image   A      SYS$LIBRARY:PWRK$NBLIB_DECNET.EXE    Advanced Server network =                                           interface to DECnetb  A      SYS$LIBRARY:PWRK$NBLIB_NETBEUI.EXE   Advanced Server network >                                           interface to NetBEUI  A      SYS$LIBRARY:PWRK$NBLIB_TCPIP.EXE     Advanced Server network =                                           interface to TCP/IP   D      SYS$STARTUP:PCSA$MAIL_STARTUP.COM    "pcsamail" command for TCPB                                           /IP clients invoking the?                                           PATHWORKS mail serverY  D      SYS$STARTUP:PWRK$ACME_STARTUP.COM    Single signon startup file  >      SYS$STARTUP:PWRK$LMBROWSER_          Browser startup file      START.COM  E                                              (continued on next page)K        G-12 Files Installedp e  e      H          Files Created During the PATHWORKS Advanced Server Installation    H         Table_G-2_(Cont.)_PATHWORKS_Advanced_Server_Files_______________  H         File_________________________________Description________________  H         SYS$STARTUP:PWRK$LMDMN_START.COM     Command procedure that runsG                                              the Advanced Server daemons  C         SYS$STARTUP:PWRK$LMMCP_START.COM     Command procedure thatuE                                              runs the Advanced Servere7                                              controller   H         SYS$STARTUP:PWRK$LMSRV_START.COM     Command procedure that runs@                                              the Advanced Server  C         SYS$STARTUP:PWRK$PCSA_SHUTDOWN.COM   PATHWORKS for VMS V4.x_G                                              shutdown command procedure_  E         SYS$SYSTEM:PWRK$ADMIN.COM            Remote Net Admin command 6                                              procedure  F         SYS$SYSTEM:PWRK$ADMIN.EXE            Character-oriented, menu-G                                              driven Net Admin interface   A         SYS$SYSTEM:PWRK$ADMIN_CFG.EXE        Server configuration 4                                              utility  B         SYS$SYSTEM:PWRK$ADMIN_LIC.EXE        License configuration4                                              utility  B         SYS$SYSTEM:PWRK$BANNER.EXE           Utility that collectsC                                              system information and E                                              inserts it at top of logP2                                              files  D         SYS$SYSTEM:PWRK$CHGROUP.EXE[1]       Standalone utility thatH                                              manages the Advanced Server<                                              groups database  D         SYS$SYSTEM:PWRK$CHUSER.EXE[1]        Standalone utility thatH                                              manages the Advanced ServerC                                              user accounts database   D         SYS$SYSTEM:PWRK$LMBROWSER.EXE        Advanced Server browser2                                              image  C         SYS$SYSTEM:PWRK$LMDMN.EXE            Advanced Server daemonP  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__           or command procedure.   H                                                 (continued on next page)  H                                                     Files Installed G-13 P  $      D      Files Created During the PATHWORKS Advanced Server Installation    E      Table_G-2_(Cont.)_PATHWORKS_Advanced_Server_Files_______________   E      File_________________________________Description________________   D      SYS$SYSTEM:PWRK$LMMCP.EXE            Advanced Server controller  A      SYS$SYSTEM:PWRK$LMSHARE.EXE[1]       Standalone utility thatdE                                           manages the Advanced Server_9                                           shares database_  9      SYS$SYSTEM:PWRK$LMSRV.EXE            Advanced ServerW  7      SYS$SYSTEM:PWRK$MANAGER.EXE          ADMIN utilityI  A      SYS$SYSTEM:PWRK$MODAL.EXE[1]         Standalone utility that E                                           manages the Advanced Server$9                                           modals database   D      SYS$SYSTEM:PWRK$SHOWINI.EXE[1]       Show LANMAN.INI Parameters1                                           utility   =      SYS$SYSTEM:PWRK$START_PRINTERS.EXE   Utility that starts D                                           printer queues and printer6                                           destinations  @      SYS$UPDATE:PWRK$LANMAN.SAV[2]        Backup saveset for theA                                           initial Advanced Servere8                                           directory tree  E      SYS$UPDATE:PWRK$LMCONFIG.COM         Command procedure that sets A                                           up the initial Advanced ?                                           Server directory treeC  <      SYS$UPDATE:PWRK$PWUTIL.SAV[2]        Backup saveset for@                                           PATHWORKS client-based3                                           utilities   <      SYS$UPDATE:PWRK$ROLLBACK.COM         Used to restore V5?                                           PATHWORKS environmentE  E      SYS$UPDATE:PWRK$V6UPGRADE.COM        Command procedure that runs =                                           the Upgrade utility   9      SYS$UPDATE:PWRK$V6UPGRADE.EXE        Upgrade utility E      [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.<      [2]This file is deleted after you configure the server.E      ________________________________________________________________         G-14 Files Installed     o      H                            Files Created During the NetWare Installation  H         ________________________________________________________________  5         Files Created During the NetWare Installatione  F               Table G-3 describes the files created during the NetWare               installation._      H         Table_G-3_NetWare_Files_________________________________________  H         File_________________________________Description________________  H         PWVN$EXAMPLES:EXAMPLE.C              NetWare API program example1                                              in C   C         PWVN$EXAMPLES:EXAMPLE.COM            Command procedure that G                                              builds the example programR  D         PWVN$EXAMPLES:EXAMPLE.OPT            Linker option file thatF                                              links the program example  F         PWVN$EXAMPLES:GETOPT.C               Simple getopt routine for0                                              VMS  B         PWVN$EXAMPLES:GETOPT.H               Simple getopt routine8                                              header file  G         SYS$LIBRARY:NWAPI.H                  NetWare API library headerN1                                              file   G         SYS$LIBRARY:NWERRORS.H               NetWare errors header file   B         SYS$LIBRARY:PWVN$CACHE.EXE           NetWare cache manager<                                              shareable image  C         SYS$LIBRARY:PWVN$NWAPISHR.EXE        NetWare APIs shareableO2                                              image  H         SYS$STARTUP:PWVN$NSSP_START.COM      Startup for symbiont server  H         SYS$STARTUP:PWVN$NVT_START.COM       Command procedure that runs;                                              the NVT daemon   H         SYS$STARTUP:PWVN$NWCP_START.COM      Command procedure that runsH                                              the NetWare control program  H                                                 (continued on next page)  H                                                     Files Installed G-15           2      Files Created During the NetWare Installation    E      Table_G-3_(Cont.)_NetWare_Files_________________________________   E      File_________________________________Description________________n  E      SYS$STARTUP:PWVN$PSPAWNER_START.COM  Command procedure that runsNB                                           the NetWare print server1                                           spawner_  E      SYS$STARTUP:PWVN$SERVER_START.COM    Command procedure that runs_<                                           the NetWare server  ?      SYS$SYSTEM:PWVN$BANNER.EXE           Utility that collects @                                           system information andB                                           inserts it at the top of3                                           log filesn  >      SYS$SYSTEM:PWVN$BINDDOWN.EXE         NetWare utility thatB                                           downloads or uploads the1                                           bindery   >      SYS$SYSTEM:PWVN$CLIENT.EXE           Client print utility  E      SYS$SYSTEM:PWVN$DOSLOGIN.EXE         NetWare utility that does a B                                           login test from the host  =      SYS$SYSTEM:PWVN$NETWARE.EXE          NetWare file server   9      SYS$SYSTEM:PWVN$NSSP.EXE             Symbiont server   B      SYS$SYSTEM:PWVN$NVTD.EXE             NetWare Virtual Terminal6                                           (NVT) daemon  >      SYS$SYSTEM:PWVN$PSERVER.EXE          NetWare print server  >      SYS$SYSTEM:PWVN$PSPAWNER.EXE         NetWare print server1                                           spawnere  @      SYS$SYSTEM:PWVN$SCONSOLE.EXE         NetWare system console  D      SYS$SYSTEM:PWVN$SLIST.EXE            NetWare utility that lists1                                           servers   8      SYS$SYSTEM:PWVN$SMB.EXE              Print symbiont  D      SYS$SYSTEM:PWVN$TLIST.EXE            NetWare utility that lists8                                           trustee rights  D      SYS$SYSTEM:PWVN$ULIST.EXE            NetWare utility that lists/                                           users.  E                                              (continued on next page)         G-16 Files InstalledY P  E      H                            Files Created During the NetWare Installation    H         Table_G-3_(Cont.)_NetWare_Files_________________________________  H         File_________________________________Description________________  C         SYS$UPDATE:PWRK$NETWARE.SAV[1]       Backup saveset for theeF                                              initial NetWare directory1                                              tree   C         SYS$UPDATE:PWRK$NWCONFIG.COM         Command procedure thatWH                                              sets up the initial NetWare;                                              directory treea  D         SYS$UPDATE:PWVN$CLD.CLD              Command definition fileH         [1]This_file_is_deleted_after_you_configure_the_server._________  H         ________________________________________________________________  H         ________________________________________________________________  <         PATHWORKS Advanced Server and NetWare Disk Structure  H               Figure G-1 shows the PATHWORKS Advanced Server and NetWareH               on-disk structure. Note that only part of the substructure               is shown.   D               The LANMAN subdirectory is created only if you installB               and configure PATHWORKS Advanced Server. The NETWAREG               subdirectory is created only if you install and configureA               NetWare.                                H                                                     Files Installed G-17 A  n      9      PATHWORKS Advanced Server and NetWare Disk Structureo    6            Figure G-1 Server On-Disk Structure Diagram    4            pwrk$commonroot, pwrk$lmroot, pwrk$nwroot              |              |___lanmanN              |     :              |     :---accounts               |     :---addon               |     :---datafiles              |     :---logs               |     :---shareso              |     :---upgrade              |              |___license              |              |___logsf              |              |___print              |              |___NetWare              |              |___section              |              |___spool              |              |___temp                                           G-18 Files InstalledS D  :                  H                                                                        HH         ________________________________________________________________  H               PATHWORKS Advanced Server and NetWare Server Logical Names      D               Table H-1 describes the logical names that are createdG               when you configure or start either the PATHWORKS Advanced '               Server or NetWare server.(  F         Table H-1 DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server)H         __________Logical_Names_________________________________________  H         Logical_name__________Description_______________________________  F         PWRK$ADDON_LIBRARY    Location of file system shareable images  ?         PWRK$COMMON           Top level directory for PATHWORKS_  D         PWRK$COMMONROOT[1]    Root of the PATHWORKS common directory"                               tree  +         PWRK$KNBDAEMON_       TCP/IP deviceP         DEVICE  2         PWRK$LANMAN[2]        Advanced Server area  4         PWRK$LICENSE          PATHWORKS license area  =         PWRK$LMDATAFILES      Advanced Server data files area   @         PWRK$LMDEBUG          Area where trace files are written  9         PWRK$LMDOMAINS        Advanced Server domain area_  ;         PWRK$LMLOGS[2]        Advanced Server log file area_  H         PWRK$LMROOT[1]        Root of the Advanced Server directory tree  :         PWRK$LMUPGRADE[2]     Advanced Server upgrade area  H         [1]This_logical_name_requires_that_you_specify_the_directory____           with it.A         [2]This logical name is defined for Advanced Server only.   H                                                 (continued on next page)  H           PATHWORKS Advanced Server and NetWare Server Logical Names H-1           ?      PATHWORKS Advanced Server and NetWare Server Logical NamesP    C      Table H-1 (Cont.) DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced E      __________________Server)_Logical_Names_________________________]  E      Logical_name__________Description_______________________________   8      PWRK$LOADSTREAMS      Logical for LoadStreams image  /      PWRK$LOGS             Common log file area   )      PWRK$NETBEUI_DEVICE   NetBEUI device   1      PWRK$NETWARE          Top level NetWare area   =      PWRK$NWROOT[1]        Root of the NetWare directory treeA  )      PWRK$PARAMS           Parameter areac  =      PWRK$PERFDATA         PATHWORKS monitor performance datau$                            directory  ?      PWRK$PRINT            PATHWORKS printer database directory   ,      PWRK$SECTION          Section file area  %      PWRK$SPOOL            Spool areanE      [1]This_logical_name_requires_that_you_specify_the_directory____)  
      with it.eE      _________________________________________________________________                                C      H-2 PATHWORKS Advanced Server and NetWare Server Logical Names  o                     H                                                                        IH         ________________________________________________________________  H                                             NetWare Server Logical Names      H               This appendix describes the logical names that are createdB               only for the PATHWORKS for OpenVMS (NetWare) server.    H         ________________________________________________________________  -         How NetWare Logical Names Are CreatedP      D               The installation procedure generates logical names forB               server directories and parameters. The configurationH               procedure modifies these names when you modify parameters.      H         ________________________________________________________________  &         Types of NetWare Logical Names  G               The configuration procedure, PWVN$CONFIG.COM, calls other E               command procedures to generate logical names. Table I-1IG               lists these command procedures and describes the types of *               logical names they generate.                      H                                         NetWare Server Logical Names I-1    e      #      Types of NetWare Logical NamesB    E      Table_I-1_Types_of_NetWare_Logical_Names________________________   '                                 Type ofSE      Command_Procedure__________Name______Description________________   B      SYS$COMMON:[SYS$STARTUP]   Common    Shared by all configured>      - PWVN$COMMON_                       NetWare servers on a2      LOGICALS.COM                         cluster.  >      SYS$SPECIFIC:[SYS$STARTUP] Private   Relevant only to the=      - PWVN$PRIVATE_                      NetWare server on a E      LOGICALS.COM_________________________particular_node.___________       E      ________________________________________________________________n  !      Common NetWare Logical NamesO  B            Table I-2 describes common logical names defined by the.            PWVN$COMMON_LOGICALS.COM procedure.  E      Table_I-2_Common_NetWare_Logical_Names__________________________s  E      Logical_Name____________Description_____________________________s  D      PWVN$CONFIGURED_LIST    A list of the nodes that are configured+                              on the cluster   E      PWVN$EXAMPLES           The directory location for example filesc  A      PWVN$GUEST_ACCOUNT      The name of the GUEST account on theo(                              file server  C      PWVN$GUEST_UIC          The User Identification Code (UIC) forSA                              the GUEST account on the file server   @      PWVN$LANGUAGE           The language (Version 1.0x supports*                              English only)  E      PWVN$SYSVOL_DIR         The root directory for the PATHWORKS for 9                              OpenVMS (NetWare) SYS Volumem  %      PWVN$UPGRADE            Obsolete   E                                              (continued on next page).  %      I-2 NetWare Server Logical Names            H                                             Common NetWare Logical Names    H         Table_I-2_(Cont.)_Common_NetWare_Logical_Names__________________  H         Logical_Name____________Description_____________________________  C         PWVN$IPX_SOCKETS[1]     The number of available IPX sockets   C         PWVN$SPX_SOCKETS[1]     The number of available SPX sockets   G         PWVN$NVT_USERS[1]       The maximum number of users who can logHH                                 in through Novell Virtual Terminal (NVT)H         [1]This_logical_name_is_added_by_the_configuration_procedure.___  H         ________________________________________________________________  H         ________________________________________________________________  %         Private NetWare Logical Names   F               Table I-3 describes private logical names defined by the2               PWVN$PRIVATE_LOGICALS.COM procedure.    H         Table_I-3_Private_NetWare_Logical_Names_________________________  H         Logical_Name_______Definition___________________________________  @         PWVN$CONF_DIR      The directory location for the server.                            configuration files  G         PWVN$ENET_DEVS     The names of the Ethernet controller devices -                            used by the server   G         PWVN$LOGFILES      The directory location for the PATHWORKS for 6                            OpenVMS (NetWare) log files  G         PWVN$NVT           A flag that indicates whether Novell Virtual_E                            Terminal (NVT) is configured on the serverS  6         PWVN$SERVER_NAME   The name of the file server  E         PWVN$TUNNEL        A flag that indicates whether tunneling isaH         ___________________enabled______________________________________      H                                         NetWare Server Logical Names I-3 S  S                          E      ________________________________________________________________a  E                                                                 Index     1      A                                    Cluster >      ___________________________           see OpenVMS cluster>      Administrator account                Common logical names?        password on, 3-7                    description of,  I-2l7      Advanced Server                      Computer name A        computer name defined,              SCSNODE parameter and, 2          3-6                                  1-14A        domain name defined, 3-6           Configuration, Advanced 2        on-disk structure, G-17              Server?      Advanced Server                       description of,  3-4C@         deinstallation procedure          Configuration Manager,;        sample, 8-4                          Advanced Server 8      Alerter service                       running afterE        description of, 3-6                    configuration procedure 4      alias,  3-7                              ,  3-4A      Automatic shutdown                   Configuration procedureDD        of file server, 6-9                 for Advanced Server, term  ;      B                                        defined,  3-1:D      ___________________________           for NetWare, term defined4      BACKUP command,  1-10                    ,  4-1  A                                            getting help for,  4-6s=      C__________________________           interrupting,  4-6 <      Checklist                             preparing for theC        summary, A-1                           Advanced Server,  3-3_D      Client-based server                   preparing for the NetWare4         administration tools,                 ,  4-5>         2-19                               prerequisites,  3-3=      Client software                       questions in,  4-6gA        LAN Manager, 1-7                    responding to prompts, ;        NetWare, 1-8                           3-9, 4-6, 5-4_8                                            running,  4-5  E                                                               Index-1s p  n            B      Configuration procedure              Deinstallation procedure?         (cont'd)                           description of,  8-2 ?        sample script for NetWare           guidelines for,  8-1tA          ,  C-4                            responding to prompts,l1        sample script for                      8-3 9          PATHWORKS Advanced                starting,  8-2 :          Server,  B-4                     Device name, 2-44        sample script for                  Disk space=          PATHWORKS Advanced                determining,  1-11 B          Server and NetWare,              Disk space requirements,0          D-5                                1-11  +        sample script for                  ENE          standalone license               ___________________________ B          server,  E-1, E-3                External network numbersB        starting, 3-9                       configuration and,  4-3@        starting server during,            External network typesB          3-8, 3-13, 4-11, 5-6,             configuration and,  4-4  +          5-11                             F E        storage of old values in,          ___________________________a/          4-13                             FilesWC                                            created by installation, 1      D__________________________              G-1 5      Data loss                            File servere<        preventing, 1-10                    configuring,  4-1?      DECnet (Phase IV)                     reconfiguring,  4-12 9        checking status, 1-16               starting,  6-4 9      DECnet-Plus                           stopping,  6-8   +        checking status, 1-17              GlE      DECnet transport,  1-7               ____________________________<        running during                     GBLPAGES parameterA          configuration,  1-16              checking and defining, 2        status of, 1-16                        1-12      DECprint SupervisorE         software, 1-2                     H__________________________ @        installing, 1-2                    Hardware requirements,5      Default answers                        1-7, 1-10e.        for configuration                  Help<          procedure,  4-6                   for configuration=        for installation                       procedure,  4-6           procedure,  2-8      Default settings         changing, 3-13         Index-2 n               >                                             IPX DECnet tunnels@         I__________________________           term defined,  4-4/         Installation                        IVPS>          files created by,  G-1               restriction whenC          logical names created by,               installing Upgrade B             H-1                                  utility only, F-1;         Installation kit                      running after B          contents of,  2-2                       installation, 6-2D         Installation procedure                running automatically,5          description of,  2-1                    2-14           interrupting,  2-8EG          logical names and,  I-1            K__________________________ 8          prerequisites,  2-4                Kit contents<          questions in,  2-8                   checking,  1-9          responding to prompts,S-             2-8                             LtG          sample script for NetWare          ___________________________S/             ,  C-1                          LANtE          sample script for                    number of networks on as<             PATHWORKS Advanced                   server, 4-4:             Server,  B-1                    License serverE          sample script for                    installation procedure, 4             PATHWORKS Advanced                   5-1@             Server and NetWare,               term defined,  3-5;             D-1                             Licensing,  1-3 3          sample script for                  LMHOSTS_F             standalone license                configuring to use,  7-5:             server,  E-1                    Local networksE          sample script for Upgrade            configuration and,  4-4 9                                             Logical names :             utility,  F-2                     common,  I-2F          standalone license server            created by installation,4             ,  5-1                               H-1?          starting,  2-6                       creation of,  I-1$  ;         Installation Verification             private,  I-3 >           Procedure                           redefined,  4-13E          See IVP                              startup procedure,  6-4_<         Internal network numbers              types of,  I-1             configuration and,  4-3         IP subnets!          BDC and PDC on different              subnets,  3-4t  H                                                                  Index-3    t            B                                           OpenVMS cluster (cont'd)D      M__________________________           shutting down servers on,  1      Memory requirements,  1-8                4-6 E                                            starting server in,  5-13, 1      N__________________________              6-7 :      NetBIOS name resolution              Operating system>        using LMHOSTS for, 3-4,              requirements,  1-7A          7-1                              Optional software, 2-19r  +        using WINS server for,             P E          3-4, 7-4                         ___________________________ 6      Netlogon service,  3-6               Part listing9      NetWare deinstallation                checking,  1-9 A         procedure                         PATHWORKS cluster alias =        sample, 8-5                         term defined,  3-7nA      Network numbers                      Postinstallation tasks, /        configuration and, 4-3               6-1N>      Network transport                     configuration,  4-2@         requirements, 1-7                 Preinstallation tasks,4                                             1-9, 2-4>      O__________________________           checklist for,  1-8?      OpenVMS cluster                      Private logical names_?        checking configuration,             description of,  I-3 ?          1-9                              PROCSECTCNT parameter A        cluster alias, 3-16                 checking and defining,e2        configuring nodes in,                  1-13A          3-2, 4-2, 4-5                    Product identifier, 2-4(  ?        disk device for PATHWORKS          PWRK$CONFIG procedureS  <          files,  3-3                       See Configuration7        installation in, 1-18,                 proceduret  A          3-8                              PWRK$DEINSTAL procedureo  =        loading client license              See Deinstallation 7          PAKs on,  5-1                        procedureCB        loading PAKs on, 1-4               PWVN$COMMON_LOGICALS.COM5        PATHWORKS cluster alias              procedure D          for,  3-7                         logical names created by,1        running license server                 I-2HC          on,  1-4, 5-1                    PWVN$CONFIG.COM procedurea?        sample configuration on,            description of,  4-2fB          E-3                               logical names and,  I-1          sample installation on,          E-1        server role in, 3-6        Index-4 O  ]            @         PWVN$PRIVATE_LOGICALS.COM           Server startup,  6-5G           procedure                         SHOW QUEUE/MANAGER command,e3          logical names created by,             1-15i>             I-3                             Shutdown procedureC         PWVN$STARTUP.COM                      for file server,  6-9oB          description of,  6-4               Software requirements,8         PWVN$STARTUP.COM procedure             1-7, 1-10F          logical names and,  I-1            Standalone license server,  7                                                1-4, 5-1_E         Q__________________________         Standalone license serverl  F         Queue manager                          configuration procedure:          running during                       sample,  E-1E             configuration,  1-15            Standalone license serverE<          starting,  1-15                       startup, 5-11F                                             Starting up the standaloneC         R__________________________            license server, 5-11 G         Release notes, 1-11, 2-5,           START/QUEUE/MANAGER commando5           2-9                                  , 1-15b3          in SYS$HELP: area,  1-5            STARTUPfE          printing,  1-4                       in SYSMAN utility,  6-8l=         Required hardware, 1-7              Startup procedure C         Required software, 1-7                for file server,  6-4_7         Requirements                        SYLOGIN.COMSD          disk space,  1-11                    conditionalizing,  6-5:          hardware,  1-7, 1-10               SYSMAN utilityA          memory,  1-8                         using STARTUP,  6-8_:          software,  1-7, 1-10               SYSTEM accountB                                               logging in to,  1-10@                                             System backup,  1-107         S__________________________         System disk   C         SCSNODE parameter                     input/output on,  3-3_>          defining,  1-14                      space needed forC         Server                                   installation, 1-11 =          starting during                    System parametersnD             configuration,  3-8,              checking and defining,5             3-13, 4-11, 5-6, 5-11                1-12_;         Server administration tools         System shutdowncG          installing,  2-19                    file server shutdown and,a4         Server announce comment                  6-9:          term defined,  3-7                 System startupF         Server commands                       defining server commands8          defining at system                      at, 6-6C             startup,  6-6                     troubleshooting,  6-5   H                                                                  Index-5 _  e                  System startup fileE        editing, 5-12, 6-7                 V___________________________  3                                           VMSINSTALS?      T__________________________           description of,  2-1N  =      Task summary,  A-1                    kit contents,  2-2   =      TCP/IP,  1-7                         VMSINSTAL procedure ;        status of, 1-18                     See Installation 7      Timesource service                       procedure_        description of, 3-5+      Time zone                            W_E        checking setting, 1-16             ___________________________r?      Transports,  3-4                     Wide area domain, 7-1 ;        selecting duringconfigu-           Windows NT servercA          ration,  3-4                       administration tools,_0      Tunnel networks                        2-19<        configuration and, 4-4              installing,  2-19.                                           WINSC      U__________________________           configuring to use,  7-5         Upgrade utility,  F-1                                                  Index-6