                                                   PATHWORKSC                      for_OpenVMS___________________________________ :                      Server Installation and Upgrade Guide                         AA-LB63G-TE    "                      February 1995              ?                      Revision/Update Information: This document F                                                   supersedes PATHWORKSB                                                   for OpenVMS (LANA                                                   Manager) Server E                                                   Installation Guide, B                                                   AA-LB63F-TE, andG                                                   PATHWORKS for OpenVMS B                                                   (NetWare) ServerE                                                   Installation Guide, >                                                   AA-PWCGA-TH.  G                      Operating System:            OpenVMS VAX, Versions ?                                                   5.5-2 and 6.1 @                                                   OpenVMS Alpha,=                                                   Version 6.1   D                      Software Version:            PATHWORKS 5.0C forG                                                   OpenVMS (LAN Manager) D                                                   PATHWORKS 1.0C forC                                                   OpenVMS (NetWare)   2                      Digital Equipment Corporation+                      Maynard, Massachusetts                  E            __________________________________________________________ $            First Published, May 1988!            Revised, February 1995   @            The information in this document is subject to changeE            without notice and should not be construed as a commitment >            by Digital Equipment Corporation. Digital EquipmentD            Corporation assumes no responsibility for any errors that'            may appear in this document.   E            The software described in this document is furnished under A            a license and may be used or copied only in accordance *            with the terms of such license.  B            No responsibility is assumed for the use or reliabilityC            of software on equipment that is not supplied by Digital =            Equipment Corporation or its affiliated companies.   D            Restricted Rights: Use, duplication, or disclosure by theE            U.S. Government is subject to restrictions as set forth in C            subparagraph (c)(1)(ii)  of the Rights in Technical Data >            and Computer Software clause at DFARS 252.227-7013.  6             Digital Equipment Corporation 1988, 1995.              All Rights Reserved.   <            The following are trademarks of Digital Equipment            Corporation:   =            Alpha AXP, Bookreader, DEClaser, DECnet, DECprint, B            Digital, LA50, LN03, LN03 PLUS, MicroVAX, ObjectBroker,:            OpenVMS, PATHWORKS, VAX, VAXserver, VAXstation,,            VMScluster, and the DIGITAL logo.  4            The following are third-party trademarks:  @            PostScript is a registered trademark of Adobe SystemsB            Incorporated. HP and LaserJet are registered trademarks>            of Hewlett-Packard Company. Proprinter and OS/2 areC            registered trademarks of International Business Machines E            Corporation. Windows is a trademark and MS-DOS and Windows A            NT are registered trademarks of Microsoft Corporation. E            SilentWriter is a registered trademark of NEC Corporation. <            NetBIOS is a trademark of Micor Computer Systems,E            Incorporated. NetWare and Novell are registered trademarks #            of Novell, Incorporated.   A            All other trademarks and registered trademarks are the 0            property of their respective holders.  0            This document is available on CD-ROM.  A            This document was prepared using VAX DOCUMENT, Version             2.1.                                C    ________________________________________________________________   C                                                            Contents     C    Preface..................................................     xi     .    1  Before You Install PATHWORKS for OpenVMS  C          About PATHWORKS for OpenVMS Servers................    1-1 C          About Licensing....................................    1-2 C          License requirements...............................    1-2 C          Types of licenses..................................    1-2 C          About the License Server...........................    1-3 C          For more licensing information.....................    1-4 C          Reading the Release Notes..........................    1-5 C          About the release notes............................    1-5 C          How to access the release notes....................    1-5 C          What You Need......................................    1-6 C          Hardware requirements..............................    1-6 C          Software requirements..............................    1-7 C          LAN Manager client software........................    1-8 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-9 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: Check disk space requirements..............   1-11 C          Step 7: Check system parameters....................   1-12 C          Step 8: Check the queue manager....................   1-16 C          Step 9: Check DECnet status........................   1-17 C          VMScluster Considerations..........................   1-18 C          Step 10: Check VMScluster configuration............   1-18 C          Next Step..........................................   1-19   C                                                                 iii                  (      2  Installing 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            Installing the Server..............................    2-3 E            Before you start VMSINSTAL.........................    2-3 E            How to start VMSINSTAL.............................    2-4 E            How installation questions work....................    2-6 E            How to interrupt the installation..................    2-6 E            How to respond to prompts..........................    2-6 E            Next Steps.........................................   2-15 E            What to do next....................................   2-15 E            Edit the system startup file.......................   2-16 E            Install optional software..........................   2-17   8      3  Configuring the PATHWORKS V5.0C for OpenVMS (LAN         Manager) Server   5            About the LAN Manager Server Configuration E            Procedure..........................................    3-1 E            What is the configuration procedure?...............    3-1 E            What the configuration procedure does..............    3-2 9            Before You Start the LAN Manager Configuration E            Procedure..........................................    3-3 5            How to Start the LAN Manager Configuration E            Procedure..........................................   3-11 6            How to Respond to LAN Manager ConfigurationE            Prompts............................................   3-11 :            How to Change LAN Manager Configuration DefaultE            Settings...........................................   3-16 E            Selecting the LAN Manager Network Device...........   3-19 E            Next Steps.........................................   3-20   =      4  Configuring the PATHWORKS V1.0C for OpenVMS (NetWare)          Server  E            About the NetWare Configuration Procedure..........    4-1 E            What is the configuration procedure?...............    4-1 E            What the configuration procedure does..............    4-2 E            When to configure the server.......................    4-2 E            About NetWare Configuration Information............    4-2           iv                  H               About network numbers..............................    4-3H               Types of network numbers...........................    4-3H               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               Before you begin...................................    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-13H               Reconfiguring the NetWare Server...................   4-14H               How to reconfigure the server......................   4-14H               New configuration value location...................   4-15    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-2H               Configuring the LAN Manager Transports.............    5-39               How to Respond to LAN Manager Configuration H               Prompts............................................    5-4H               Configuring the NetWare Transport..................    5-7H               How to Respond to NetWare Configuration Prompts....    5-8H               How to Start the Standalone License Server.........   5-13H               How to start the license server manually...........   5-13H               How to start the license server automatically......   5-14H               How to start the license server in a VMScluster....   5-15  =         6  Creating PATHWORKS V5.0C for OpenVMS (LAN Manager)             Upgrade Reports  H               Before You Begin...................................    6-2H               Have you done?.....................................    6-2H               About Upgrade Reports..............................    6-2H               What is an upgrade report?.........................    6-2H               Types of reports...................................    6-2H               About the Users report.............................    6-3H               About the Groups report............................    6-4H               About the File and Print Services report...........    6-5  H                                                                        v                 E            Sample reports.....................................    6-5 E            Using the Upgrade Utility..........................    6-5 E            Before you start the utility.......................    6-6 E            How to start the utility...........................    6-7 E            How to navigate the utility........................   6-11 E            How to get online help.............................   6-11 E            Creating Upgrade Reports...........................   6-12 E            How to create an upgrade report....................   6-12 E            Where to find report files.........................   6-14 E            Editing Upgrade Reports............................   6-15 E            When and how to edit a Users report................   6-15 E            When and how to edit a Groups report...............   6-19 9            When and how to edit a File and Print Services E            report.............................................   6-20 E            Next Steps.........................................   6-21 E            What to do next....................................   6-22     >      7  Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)  E            Before You Begin...................................    7-2 E            Have you done?.....................................    7-2 E            About Upgrading Your Server........................    7-2 E            Why upgrade your server?...........................    7-2 E            What the upgrade procedure does....................    7-3 E            Types of upgrades..................................    7-5 E            Performing a Complete Upgrade with Reports.........    7-6 E            How to perform a complete upgrade with reports.....    7-6 E            Performing a Custom Upgrade with Reports...........    7-8 E            How to perform a custom upgrade with reports.......    7-8 E            Performing a Complete Upgrade Without Reports......   7-14 4            How to perform a complete upgrade withoutE            reports............................................   7-14 E            Performing a Custom Upgrade Without Reports........   7-22 E            How to perform a custom upgrade without reports....   7-22 E            Performing Additional Upgrade Tasks................   7-34 E            What to do next....................................   7-34 E            Upgrading OpenVMS Security.........................   7-34 E            Why upgrade security?..............................   7-34 E            How to upgrade security............................   7-35 E            Performing a UAS Merge Procedure...................   7-35 E            What the UAS merge procedure does..................   7-35 E            What is a UAS Merge report?........................   7-36 E            When to create a UAS Merge report..................   7-36         vi                  H               How to create a UAS Merge report...................   7-37H               When and how to edit the UAS Merge report..........   7-38H               How to perform a UAS merge procedure...............   7-40H               Upgrading Disk Services............................   7-47H               Why upgrade disk services?.........................   7-48H               How to upgrade disk services.......................   7-48H               Next Steps.........................................   7-50H               What to do next....................................   7-50    >         8  After You Install the PATHWORKS for OpenVMS Servers  H               Before You Begin...................................    8-2H               Have you done?.....................................    8-2H               Verifying the Server Installation..................    8-2H               How to run the IVP.................................    8-2H               Starting the PATHWORKS for OpenVMS File Servers....    8-4H               When to start the server...........................    8-4H               What the startup procedure does....................    8-4H               Starting the File Servers..........................    8-5H               Ways to start the server...........................    8-5H               How to start the LAN manager server manually.......    8-5:               How to define LAN Manager server commands atH               login..............................................    8-5H               How to start the NetWare server manually...........    8-6H               How to define NetWare server commands at login.....    8-6H               How to start the server automatically..............    8-6H               How to start the server in a VMScluster............    8-7H               Stopping the Server................................    8-9H               When to stop the server............................    8-9H               How to stop the server.............................    8-9H               How to stop the server on system shutdown..........    8-9           9  Installing the XQP+  H               Features of the XQP+...............................    9-2H               XQP+ features......................................    9-2H               Performing the XQP+ Installation...................    9-2H               Before you install the XQP+........................    9-3H               How to start the XQP+ installation.................    9-3H               How to respond to prompts..........................    9-4H               Removing the XQP+..................................   9-11H               How to remove the XQP+.............................   9-11H               Sample XQP+ Installations..........................   9-13  H                                                                      vii                 E            System not part of a VMScluster....................   9-13 E            System that is part of a VMScluster................   9-15u    '      10  Removing PATHWORKS for OpenVMS_  E            Reasons for Removing the Server....................   10-1bE            Why remove the server?.............................   10-1iE            Removing the Server................................   10-2tE            About the deinstallation command procedure.........   10-2 E            How to run the deinstallation procedure............   10-2sE            How to respond to prompts..........................   10-3o1            Sample LAN Manager and NetWare RemovaliE            Procedures.........................................   10-4 E            Sample LAN Manager removal procedure...............   10-5 E            Sample NetWare removal procedure...................   10-5   2      A  Sample LAN Manager Server Installation and         Configuration Proceduret  E            Sample LAN Manager Server Installation Procedure...    A-1s2            Sample LAN Manager Server ConfigurationE            Procedure..........................................    A-5   <      B  Sample NetWare Server Installation and Configuration         Procedure   E            Sample NetWare Server Installation Procedure.......    B-1CE            Sample NetWare Server Configuration Procedure......    B-5   6      C  Sample Combined LAN Manager and NetWare Server0         Installation and Configuration Procedure  9            Sample Combined LAN Manager and NetWare Server E            Installation Procedure.............................    C-1,2            Sample Combined LAN Manager and NetWareE            Configuration Procedure............................    C-6e                	      viiir    a            <         D  Sample Standalone License Server Installation and"            Configuration Procedure  ;               Sample Standalone License Server Installation H               Procedure..........................................    D-1@               Sample LAN Manager Configuration Procedure for theH               Standalone License Server..........................    D-4<               Sample NetWare Configuration Procedure for theH               Standalone License Server..........................    D-5  4         E  Sample LAN Manager Server Upgrade Reports  H               Sample Users Report................................    E-1H               Sample Groups Report...............................    E-3H               Sample File and Print Services Report..............    E-5H               Sample UAS Merge Report............................    E-6           F  Files Installed  H               Files Common to LAN Manager and NetWare............    F-12               Files Created During the LAN ManagerH               Installation.......................................   F-12H               Files Created During the NetWare Installation......   F-16H               LAN Manager and NetWare Disk Structure.............   F-18  @         G  Logical Names for the LAN Manager and NetWare Servers    4         H  Logical Names for the NetWare Server Only  H               How NetWare Logical Names Are Created..............    H-1H               Types of NetWare Logical Names.....................    H-1H               Common NetWare Logical Names.......................    H-2H               Private NetWare Logical Names......................    H-3           Glossary                  H                                                                       ix .  .            
      Index          Tables.  E            1         Installation and Upgrade Checklist.......    xvin  E            1-1       Preinstallation Checklist................    1-9.  E            2-1       Installation Prompts.....................    2-7e  E            2-2       Optional Software........................   2-18.  E            3-1       LAN Manager Configuration Prompts........   3-12.  E            3-2       LAN Manager Configuration Settings.......   3-18.  E            4-1       NetWare Configuration Network Numbers....    4-3.  E            4-2       Types of NetWare Interfaces..............    4-5.  E            4-3       Configuration Prompts....................    4-7.  E            5-1       PWRK$CONFIG Configuration Prompts........    5-41  E            5-2       PWVN$CONFIG Configuration Prompts........    5-8   E            6-1       Report File Names........................   6-14   E            6-2       Editing the Users Report.................   6-15   E            6-3       Editing the Groups Report................   6-19S  8            6-4       Editing the File and Print ServicesE                      Report...................................   6-21   E            7-1       Editing a UAS Merge Report...............   7-39   E            9-1       Features of the XQP+.....................    9-2   E            9-2       XQP+ Installation Prompts................    9-4   E            10-1      PWRK$DEINSTAL Prompts....................   10-3I  E            10-2      PWVN$DEINSTAL Prompts....................   10-4N  E            F-1       Common Files.............................    F-1a  E            F-2       LAN Manager Files........................   F-13o  E            F-3       NetWare Files............................   F-16v  >            G-1       PATHWORKS V5.0C for OpenVMS (LAN Manager)E                      Logical Names............................    G-1   E            H-1       Types of NetWare Logical Names...........    H-2o  E            H-2       Common NetWare Logical Names.............    H-2   E            H-3       Private NetWare Logical Names............    H-3p        x .  .                      H         ________________________________________________________________  H                                                                  Preface               Purposes  )               This guide explains how to:   C               o  Install and configure one or more of the following '                  PATHWORKS[TM] servers:o  B                  -  PATHWORKS V5.0C for OpenVMS (LAN Manager) file                     server  E                  -  PATHWORKS V1.0C for OpenVMS (NetWare) file server   7                  -  PATHWORKS standalone license server.  H               o  Upgrade existing databases for users, groups, services,G                  and access rights so that they work with PATHWORKS for                   OpenVMS..           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  H               This guide also assumes that the administrator is familiarF               with the networking concepts appropriate for the type of+               PATHWORKS for OpenVMS server.A  H                                                                       xi t  e                  Organization.  C            The following list can help you find information in this.            guide:   B            Chapter 1   Describes prerequisites to the installation!                        procedure..  <            Chapter 2   Describes the installation procedure.  D            Chapter 3   Describes the configuration procedure for the*                        LAN Manager server.  D            Chapter 4   Describes the configuration procedure for the&                        NetWare server.  D            Chapter 5   Describes the configuration procedure for the1                        standalone license server..  D            Chapter 6   Describes how to use the upgrade procedure toC                        create and edit upgrade reports that you canrA                        use as input data files during the upgrade.!                        procedure.   D            Chapter 7   Describes how to use the upgrade procedure toC                        convert existing databases so that they work *                        with the V5 server.  =            Chapter 8   Describes postinstallation tasks, suchn?                        as running the Installation VerificationtD                        Procedure and starting the server independent<                        of the installation and configuration"                        procedures.  D            Chapter 9   Describes how to install and remove the XQP+.  D            Chapter 10  Describes how to remove PATHWORKS for OpenVMS(                        from your system.  D            Appendix A  Shows a sample installation and configuration<                        procedure for the LAN Manager server.  D            Appendix B  Shows a sample installation and configuration8                        procedure for the NetWare server.  D            Appendix C  Shows a sample installation and configurationB                        procedure for a system running both the LAN3                        Manager and NetWare servers..        xii 4                 G               Appendix D  Shows a sample installation and configurationoF                           procedure for the standalone license server.  7               Appendix E  Shows sample upgrade reports.   A               Appendix F  Lists the files that are installed with-0                           PATHWORKS for OpenVMS.  E               Appendix G  Lists the logical names created for the LAN 6                           Manager and NetWare servers.  A               Appendix H  Lists the logical names created for the .                           NetWare server only.  F               Glossary    Explains some of the terminology specific to<                           the PATHWORKS for OpenVMS servers.                 Index.           Related Documentst  B               The following manuals provide more information about-               topics discussed in this guide:.  F               DECprint Supervisor   Describes how to load the DECprintD               for OpenVMS Software  Supervisor software, install theF               Installation Guide    printing system, and test printing/                                     operations.   @               Guide to Managing     Describes the license serverH               PATHWORKS Licenses    software and how to manage PATHWORKS-                                     licenses..  F               LAN Manager Remote    Describes the Remote Boot service,F               Boot Guide            and displays a complete diagram ofA                                     the RPL on-disk substructure..  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, and.<                                     run the AUTOGEN utility.  A               OpenVMS System        Describes how to back up youre3               Management Utilities  OpenVMS system.                Reference Manual  H                                                                     xiii                   <            PATHWORKS V5.0C       Describes how to manage theA            for OpenVMS (LAN      PATHWORKS V5.0C for OpenVMS (LAN 3            Manager) Server       Manager) software..            Administrator's            Guide  <            PATHWORKS V1.0C       Describes how to manage the<            for OpenVMS           PATHWORKS V1.0C for OpenVMS4            (NetWare) System      (NetWare) software.            Administration Guidev        Conventions  5            This guide uses the following conventions:.  E            __________________________________________________________.E            Convention____Meaning_____________________________________.  @            <Ctrl/x>      While you hold down the Ctrl key, pressA                          another key or a pointing device button.e  @            <Return>      Press the key that executes commands orC                          terminates a sequence. This key is labeleduD                          <Return>, <Enter>, or << -  >, depending on'                          your keyboard.   <            enter         Type all required text, spaces, and@                          punctuation marks; then press <Return>,?                          <Enter>, or << -  >, depending on your2"                          keyboard.  D            UPPERCASE     Uppercase letters indicate OpenVMS commandsC                          and qualifiers. You can enter commands and.C                          qualifiers in any combination of uppercaseS>                          or lowercase, unless otherwise noted.  B            lowercase     Lowercase italic letters indicate OpenVMSC            italic        command parameters. You must enter a valueoB                          for the parameter, unless it is optional.  B                          In examples of dialog between you and theE            teal blue typesystem, teal blue type indicates information ?                          that you enter. In online (Bookreader) E                          files, this information appears in boldface.o        xiv .  .          H               __________________________________________________________H               Convention____Meaning_____________________________________  C               /             A forward slash in command descriptions7G                             indicates that a command qualifier follows.8  G                . . .        A horizontal ellipsis following an entry in H                             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 indicates.;               .             that not all the data is shown..               .   @               Note          Notes provide information of special'                             importance.h  C               Caution       Cautions provide information to preventtH               ______________damage_to_software_or_hardware._____________           Terminology.  >               In this guide, the following terms have specific               definitions:  H               __________________________________________________________H               The_term_._._.________Refers_to_the_._._._________________  A               server                type of PATHWORKS for OpenVMS C                                     software that is running on the +                                     system.   E               file server           LAN Manager server or the NetWare.+                                     server.a  =               license server        PATHWORKS license server.t  F               client                personal computer that connects toH               ______________________the_file_server_or_license_server.__        H                                                                       xv h  e            .      Summary of Installation and Upgrade Tasks  >            Table 1 summarizes the tasks you need to perform to@            install and upgrade your OpenVMS server. You can copyA            this list and use it as a checklist when you read this             book.  E            Table_1_Installation_and_Upgrade_Checklist________________.  2            <   >1.   Prepare for the installation:  E                      a. Make sure that you have the required hardware %                         and software.4  5                      b. Log in to the SYSTEM account..  3                      c. Back up the OpenVMS system..  D                      d. Make sure that you have enough disk space toB                         install the PATHWORKS for OpenVMS servers.  <                      e. Make sure that the system parameters?                         GBLPAGES, GBLSECTIONS, PROCSECTCNT, and 1                         SCSNODE are set properly.t  D                      f. Make sure that the queue manager is running.  D            <   >2.   Start the installation procedure and respond to*                      installation prompts.  @            <   >3.   Install the DECprint Supervisor (optional).  C            <   >4.   Install the eXtended Qio Processor Plus (XQP+,                       optional).   E            <   >5.   Start the configuration procedure and respond to +                      configuration prompts..  E                                              (continued on next page)a                  xvi .  .            H               Table_1_(Cont.)_Installation_and_Upgrade_Checklist________  D               <   >6.   If you are upgrading from PATHWORKS V4.x for>                         OpenVMS, use the upgrade procedure to:  2                         a. Create upgrade reports.  4                         b. Upgrade users and groups.  ;                         c. Upgrade file and print services.u  <                         d. Upgrade security for file shares.  2                         e. Delete temporary files.  C                         f. Upgrade security on OpenVMS directories,r@                            subdirectories, and files (optional).  E                         g. Change the server's role in the domain andmD                            merge the local server's users and groupsE                            databases with those of the primary domainS&                            controller.  D               <   >7.   If you are upgrading from PATHWORKS V4.x for7                         OpenVMS, upgrade disk services..  C               <   >8.   Run the Installation Verification Procedure D                         (if you did not do so when you installed the                          server).  G               <   >9.   Start the server (if you did not do so when you H               __________configured_the_server)._________________________                          H                                                                     xvii .  .                  H                                                                        1H         ________________________________________________________________  H                                 Before You Install PATHWORKS for OpenVMS      G               This chapter describes the hardware and software you musteH               have and the tasks you need to complete before you install$               PATHWORKS for OpenVMS.  >               This chapter consists of the following sections:  4               o  About PATHWORKS for OpenVMS Servers                  o  About Licensing  *               o  Reading the Release Notes                 o  What You Need  &               o  Preinstallation Tasks  *               o  VMScluster Considerations                 o  Next Step  H         ________________________________________________________________  +         About PATHWORKS for OpenVMS Serversl  A               The PATHWORKS for OpenVMS kit contains the softwarel<               required to run the following server software:  C               o  PATHWORKS V5.0C for OpenVMS (LAN Manager), the LANf$                  Manager file server  H               o  PATHWORKS V1.0C for OpenVMS (NetWare), the NetWare file                  server   4               o  PATHWORKS standalone license server  H                             Before You Install PATHWORKS for OpenVMS 1-1           (      About PATHWORKS for OpenVMS Servers    ?            The VMSINSTAL procedure allows you to install either @            of the file servers, both of the file servers, or the%            standalone license server.   B            If you have PATHWORKS V5.0 for OpenVMS (LAN Manager) or@            later installed, you must install the new LAN Manager            server.  E            If you have any version of PATHWORKS for OpenVMS (NetWare) >            installed, you must install the new NetWare server.  E            If you have neither LAN Manager nor NetWare installed, you D            can install the standalone license server. Otherwise, theC            license server is installed when you install either file.            server.    E      ________________________________________________________________         About Licensing          LICENSE REQUIREMENTS.B            Any client that wants to use PATHWORKS server resources%            must have a valid license.         TYPES OF LICENSES5            There are two types of PATHWORKS licenses:g  E            __________________________________________________________gE            Type_____________Description______________________________.  D            Individual       A license issued to a client workstationB            client license   to enable users of that workstation to@            (CCS or FPA)     access any PATHWORKS services in theB                             network for a single network operatingC                             system, such as LAN Manager or NetWare.   D            Concurrent       A license that can be used for access toC            server license   a PATHWORKS server when client licenses E            (FPS)____________are_not_available._______________________         1      1-2 Before You Install PATHWORKS for OpenVMS1           H                                                          About Licensing              ABOUT THE LICENSE SERVERE               The PATHWORKS license server is a software program that.E               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")_  C               o  In conjunction with the file server (automatically =                  included with your file server installation)h  E               In either case, you can configure the license server too               support:  )               o  LAN Manager clients only   %               o  NetWare clients onlyp  0               o  LAN Manager and NetWare clients  D               Digital recommends that you install the license serverB               on a designated OpenVMS system without the PATHWORKSG               file server, to ensure smooth and continuous operation of F               the license server. Therefore, the PATHWORKS for OpenVMSE               kit allows you to install the standalone license serveriE               separately from the file server. Alternatively, you cansH               run the license server on a VMScluster with PATHWORKS fileC               servers, where cluster failover provides reliability.   F               Each LAN needs only one active PATHWORKS license server.G               The client license product authorization keys (PAKs) must E               be loaded on the system that runs the PATHWORKS license                server.n  C               In a VMScluster, the PAKs must be loaded on all nodes A               that run the PATHWORKS license server. This is best A               accomplished by adding the PAKS to a shared license.               database.i          H                             Before You Install PATHWORKS for OpenVMS 1-3 r               About Licensing    E      FOR MORE_LICENSING_INFORMATION__________________________________2            For more informationcE            about...______________Refer_to..._________________________f  ?            Loading licenses      VMS License Management Utilitya'                                  Manuale  E            Managing PATHWORKS    Guide to Managing PATHWORKS LicensesrE            licenses__________________________________________________                                                                         1      1-4 Before You Install PATHWORKS for OpenVMS  c  t      H                                                Reading the Release Notes  H         ________________________________________________________________  !         Reading the Release Notesh               ABOUT THE RELEASE NOTES E               The PATHWORKS for OpenVMS installation kit includes two $               sets of release notes:  H               o  PATHWORKS V5.0C for OpenVMS (LAN Manager) Release Notes  D               o  PATHWORKS V1.0C for OpenVMS (NetWare) Release Notes  H               Digital recommends that you print and read the appropriate=               release notes before starting the installation.   '         HOW TO ACCESS THE RELEASE NOTESnH               Use the following table to decide how to print the release               notes:  H               __________________________________________________________               If you wantcH               to_print...___Then..._____________________________________  -               The LAN       Do the following:aD               Manager       1. Load the installation kit on a drive.               Release F               Notes         2. Enter the following commands, replacingD               before the       device with the name of the device onE               installation     which you loaded the installation kit:   0                             $ MOUNT device: PWRKG                             $ BACKUP/SELECT=PWRKV50C050.RELEASE_NOTES -a>                             _$ device:PWRKV50C050.A/SAVE_SET *=                             $ PRINT PWRKV50C050.RELEASE_NOTESh                    H                             Before You Install PATHWORKS for OpenVMS 1-5 x               Reading the Release Notes  E            __________________________________________________________             If you wantE            to_print...___Then..._____________________________________e  *            The NetWare   Do the following:A            Release       1. Load the installation kit on a drive.h            NotesC            before the    2. Enter the following commands, replacing A            installation     device with the name of the device ontB                             which you loaded the installation kit:  .                          $ MOUNT device: PWRKND                          $ BACKUP/SELECT=PWVNV10C010.RELEASE_NOTES -;                          _$ device:PWRKV50C050.A/SAVE_SET *d:                          $ PRINT PWVNV10C010.RELEASE_NOTES  *            The release   Do the following:A            notes         1. Load the installation kit on a drive.t            during thePD            installation  2. Enter the following command to start the3                             installation procedure:e  @                          $ @VMSINSTAL PWRKV50C050 device_name: -%                          _$ OPTIONS N   B                          The installation procedure prompts you toC                          either print or display the release notes.uB                          In any case, the release notes are alwaysE            ______________copied_to_the_SYS$HELP:_area._______________     E      ________________________________________________________________         What You Need            HARDWARE REQUIREMENTS=            Make sure that the network (including cables, PCs, @            servers, and other hardware) is connected. For a listA            of the hardware that the server supports, refer to the D            Software Product Description (SPD) that is appropriate to            your file server.      1      1-6 Before You Install PATHWORKS for OpenVMSS A         H                                                            What You Need             SOFTWARE REQUIREMENTST@               To install PATHWORKS for OpenVMS successfully, youE               must have the following software properly installed and (               configured on your system:  5               o  Supported operating system software:u  H                  _______________________________________________________                  On thisH                  system_._._.__You_need_this_operating_system_._._._____  F                  VAX           OpenVMS VAX, Version 5.5-2 or higher[1]  F                  Alpha         OpenVMS Alpha, Version 1.5 or higher[1]H                  [1]PATHWORKS_installs_on_both_the_OpenVMS_VAX_V6.0_____  F                  and Alpha V1.5 operating systems but PATHWORKS is notH                  supported_on_these_operating_system_versions.__________  "               o  DECnet (optional)  G                  DECnet is installed with the OpenVMS operating system.p  "               o  TCP/IP (optional)  G                  PATHWORKS for OpenVMS provides transparent support for H                  TCP/IP. The following TCP/IP network transport products#                  support PATHWORKS:   8                  -  DEC TCP/IP Services V3.1 for OpenVMS  0                  -  TGV MultiNet V3.3 Revision A  B                  TCP/IP is a separately installable product. OtherH                  third-party TCP/IP products may also support PATHWORKS.  @                  See the PATHWORKS for OpenVMS Release Notes for(                  additional information.  A               o  NetBEUI is installed with PATHWORKS for OpenVMS.lC                  Therefore, having NetBEUI installed on your systema6                  is not a preinstallation requirement.      H                             Before You Install PATHWORKS for OpenVMS 1-7 i  r            What You Need           LAN MANAGER CLIENT SOFTWAREC            You can use the following client software with PATHWORKS %            for OpenVMS (LAN Manager):_  B            o  PATHWORKS for DOS and Windows, Version 5.0 or higher  6            o  PATHWORKS for DOS, Version 4.0 or higher  7            o  PATHWORKS for OS/2, Version 2.0 or higher   D            o  LAN Manager 2.2 workstation software for DOS, Windows,               and OS/2  D            o  Microsoft Windows NT workstation software, Version 3.1  C            o  Microsoft Windows for Workgroups, Version 3.1 or 3.11         NETWARE CLIENT SOFTWAREC            You can use the following client software with PATHWORKSr!            for OpenVMS (NetWare):   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 REQUIREMENTSE            The following minimum amount of main memory is required to %            run PATHWORKS for OpenVMS:t  E            ___________________________________________________________E            On_this_system_._._.__You_need_at_least_._._._____________g  5            OpenVMS VAX           16 MB of main memoryv  E            OpenVMS_Alpha_________32_MB_of_main_memory_________________  E      _________________________________________________________________        Preinstallation Tasks  9            Use the checklist in Table 1-1 to complete theH;            preinstallation tasks that are described in thisa            section.   1      1-8 Before You Install 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.T  1               <   >5.   Back up the system disks.   G               <   >6.   Make sure that you have adequate disk space fort%                         installation.   0               <   >7.   Check system parameters.  0               <   >8.   Check the queue manager.  D               <   >9.   Make sure that DECnet is running, if you are>                         planning to use PATHWORKS over DECnet.  B               <   >10.  Check VMScluster configuration, if you areH               __________installing_PATHWORKS_on_a_VMScluster.___________  E               Before you install PATHWORKS for OpenVMS, perform these !               installation tasks:   &         STEP 1: CHECK THE PART LISTINGE               The software part listing specifies the contents of the E               kit you receive. Check the contents of your kit against F               that information. If your kit is damaged or if parts are;               missing, contact your Digital representative.t  *         STEP 2: CHECK THE NETWORK HARDWAREC               PATHWORKS for OpenVMS runs on any OpenVMS system thatlH               meets the software requirements. The PC local area network               (LAN) requires:+  G               o  A supported network controller board in the server andi                  in each client   A               o  The cables to connect each client to the network   H                             Before You Install PATHWORKS for OpenVMS 1-9 .               Preinstallation Tasks    (      STEP 3: CHECK THE REQUIRED SOFTWAREC            PATHWORKS for OpenVMS requires the OpenVMS VAX operatingx@            system, Version 5.5-2 or higher, or the OpenVMS AlphaD            operating system, Version 1.5 or higher. If you are goingD            to use the LAN Manager server over DECnet, or the licenseD            server over DECnet, or the mail server, IPX tunneling, orE            clustering, you also need the DECnet network transport. IfpC            you are going to use the TCP/IP transport, you must haveSD            a TCP/IP transport product, as described in the PATHWORKS3            for OpenVMS (LAN Manager) Release Notes.e    )      STEP 4: LOG IN TO THE SYSTEM ACCOUNT B            Before you install PATHWORKS for OpenVMS, log in to theC            SYSTEM account, which has sufficient privileges to start &            the installation procedure.  +            To log in to the SYSTEM account:K  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 not                displayed.        STEP 5: BACK UP THE SYSTEM B            To safeguard against the loss of valuable data, Digital?            recommends that you back up all disks on your system 2            before you install any layered product.  E            To do a system backup, use the OpenVMS BACKUP command. For @            information about the BACKUP command, see the OpenVMS?            System Management Utilities Reference Manual and the +            OpenVMS System Manager's Manual.a                  2      1-10 Before You Install PATHWORKS for OpenVMS h  w      H                                                    Preinstallation Tasks    -         STEP 6: CHECK DISK SPACE REQUIREMENTSpH               The following amount of free disk space on the system disk<               is required during the installation procedure:  H               __________________________________________________________G               On this          With these com-  You need at least . . .sH               system_._._._____ponents_._._.____blocks__________________  6               OpenVMS VAX      LAN Manager      40,000#                                only   6                                NetWare only     20,000  6                                LAN Manager and  44,000&                                NetWare  6                                Standalone       16,000-                                license serverf  H               __________________________________________________________  6               OpenVMS Alpha    LAN Manager      60,000#                                only   6                                NetWare only     32,000  6                                LAN Manager and  66,000&                                NetWare  6                                Standalone       26,000H               _________________license_server___________________________  D               To check the number of free blocks on the system disk,               enter:  )               $ SHOW DEVICE SYS$SYSDEVICEw                 Result  F               The OpenVMS system displays information about the system8               disk, including the number of free blocks:  H               Device         Device   Error    Volume    Free  Trans MntH                Name          Status   Count     Label   Blocks Count CntG               DUA0:          Mounted      0  VAXVMSV055  43062   196  1f  H                            Before You Install PATHWORKS for OpenVMS 1-11 _  _            Preinstallation Tasks    $      STEP 7: CHECK SYSTEM PARAMETERSE            Make sure that the following OpenVMS system parameters are             set properly.              NoteS  ?            If these parameters are not set properly, you cannotgC            configure the server after you complete the installation_            procedure._              GBLPAGES parameter_  E            The minimum value of this parameter depends on the type ofl            system:  E            __________________________________________________________             For a VAX system,D            the value must be at  For an Alpha system, the value mustE            least_._._.___________be_at_least_._._.___________________A  E            3500_pages____________7500_pages__________________________b  C            To ensure that your system has enough free global pages:e  "            1. Enter the following:  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")                 Result  C               The value of the GBLPAGES parameter is displayed. For                example:                 7500  ?            2. If the value is less than required, edit the filee@               SYS$SYSTEM:MODPARAMS.DAT and add a line similar to               the following:  !               ADD_GBLPAGES = 7500.          2      1-12 Before You Install PATHWORKS for OpenVMS           H                                                    Preinstallation Tasks    #               GBLSECTIONS parametero  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 NetWareC               server only, the      If the LAN Manager server is toiF               value must be at      be installed, the value must be atH               least_._._.___________least_._._._________________________  H               50____________________75__________________________________  ?               To ensure that your system has enough free globals               sections:a  %               1. Enter the following:a  =                  $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")                     Result   E                  The value of the GBLSECTIONS parameter is displayed.o                  For example:                     75e  B               2. If the value is less than required, edit the fileC                  SYS$SYSTEM:MODPARAMS.DAT and add a line similar toa                  the following:A  %                  ADD_GBLSECTIONS = 75   #               PROCSECTCNT parameterK  F               The minimum value of this parameter differs depending on0               which servers are to be installed:            H                            Before You Install PATHWORKS for OpenVMS 1-13                 Preinstallation Tasks  E            __________________________________________________________R            For the standalone_            license server only,             or the NetWareo@            server only, the      If the LAN Manager server is toC            value must be at      be installed, the value must be attE            least_._._.___________least_._._._________________________   E            32____________________40___________________________________  ;            To ensure that the value of the system parameter #            PROCSECTCNT is adequate:   "            1. Enter the following:  8               $ WRITE SYS$OUTPUT F$GETSYI("PROCSECTCNT")                 Result  B               The value of the PROCSECTCNT parameter is displayed.               For example:                 40  ?            2. If the value is less than required, edit the fileO@               SYS$SYSTEM:MODPARAMS.DAT and add a line similar to               the following:  "               MIN_PROCSECTCNT = 40              SCSNODE parameter  C            This parameter must be defined as your system's computerSC            name. If you are running DECnet, the SCSNODE name should /            be the same as the DECnet node name.e  C            To check whether the system parameter SCSNODE is definedH*            as your system's computer name:  @            1. Enter the following commands at the system prompt:  (               $ NAME=F$GETSYI("SCSNODE")                $ SHOW SYMBOL NAME      2      1-14 Before You Install PATHWORKS for OpenVMS .  _      H                                                    Preinstallation Tasks                      Result   -                  One of the following occurs:   ?                  o  If SCSNODE is defined, the computer name isiE                     displayed. For example, if your system's computern#                     name is HYDRAC:n  '                       NAME = "HYDRAC  "a  G                  o  If SCSNODE is not defined, the computer name is not +                     displayed. For example:E  '                       NAME = "        "   9               2. If SCSNODE is not defined, edit the file C                  SYS$SYSTEM:MODPARAMS.DAT and define the parameter. G                  For example, if your system's computer name is HYDRAC, F                  edit the file so that it contains the following line:  #                  SCSNODE = "HYDRAC"   D               The SCSNODE parameter's preinstallation status affectsE               what happens after you install and configure the server 0               and reboot the system, as follows:  H         ________________________________________________________________         If SCSNODE    And H         is_._._.______you_._._._____Then_the_server_._._._______________  3         Not defined   Do not        Does not start.:                       define itU  +         Already       Do not        Starts.C         defined       define itT  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 anysC                                     existing print or batch jobs to E                                     the new queues. You may also haveMB                                     to rebuild the queue database.C                                     For information on these system E                                     management tasks, see the OpenVMStH         ____________________________System_Manager's_Manual.____________  H                            Before You Install PATHWORKS for OpenVMS 1-15    _            Preinstallation Tasks                Note_  E            When you finish editing the file SYS$SYSTEM:MODPARAMS.DAT, A            you must run the OpenVMS command procedure AUTOGEN andrE            reboot the system before you configure the server. You canaC            run AUTOGEN after you install (but before you configure)r#            the server. For example:p  :            $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK  @            If you plan to install optional software (such as theC            XQP+ or DECprint Supervisor for OpenVMS), you can rebootOB            the system as part of an installation procedure or as aD            postinstallation task. For example, after you install theA            XQP+, you must reboot the system. Therefore, you could A            install the XQP+, run the AUTOGEN, and then reboot the -            system after you install the XQP+._              For more informationh  A            For information about running AUTOGEN, see the OpenVMS_#            System Manager's Manual.   $      STEP 8: CHECK THE QUEUE MANAGERD            Enter the SHOW SYSTEM command to make sure that the queue            manager is running:              $ SHOW SYSTEM              Result   =            Your OpenVMS system displays all currently running B            processes. If the queue manager is running, the display4            includes a line similar to the following:  R      0000004C QUEUE_MANAGER   HIB      8       51   0 00:00:01.55       524    509  A            If the queue manager is not running, use the followingo            command to start it:                $ START/QUEUE/MANAGER        2      1-16 Before You Install PATHWORKS for OpenVMS T  R      H                                                    Preinstallation Tasks    #         STEP 9: CHECK DECNET STATUS H               Enter the following command to see if DECnet is running onF               the system on which you are performing the installation:  %               $ MCR NCP SHOW EXECUTORS  H               __________________________________________________________               If DECnet H               is...______Then...________________________________________  G               Running    The system displays State = on as shown below:m  I                          Node Volatile Summary as of  1-JUL-1994 12:16:36V  7                          Executor node = 9.000 (BRUTUS)G  -                          State           = onlH                          Identification  = DECnet-VAX V5.4-1, VMS V5.4-2,                          Active links    = 2  A               Not        Enter the following command to start it:i0               running    $ @SYS$MANAGER:STARTNET  E                          This is only required if you plan to use theoB                          Mail Server over DECnet, or eXcursion, orH               ___________Remote_PCSA_Manager_commands.__________________                                      H                            Before You Install PATHWORKS for OpenVMS 1-17 o  g            VMScluster Considerations  E      ________________________________________________________________d        VMScluster Considerations      ,      STEP 10: CHECK VMSCLUSTER CONFIGURATIONC            You can run PATHWORKS for OpenVMS on multiple VMSclusterM,            members (server nodes). To do so:  D            1. On each system disk on which you want to run 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 command_?               procedure. This ensures that each node has enoughi*               resources to run the server.  @               Running the configuration procedure on a clusteredE               server is slightly different from running the procedurelC               on a nonclustered server. For example, on a clustered B               server the procedure asks you to specify a PATHWORKS               VMScluster alias._  A            3. Ordinarily, a VMScluster uses only one system disk, A               no matter how many members. However, a cluster thati?               contains both VAX and Alpha processors (a "mixed- A               architecture VMScluster") must use two system disks D               (one on each processor type). If you run PATHWORKS forB               OpenVMS on multiple system disks, make sure that allC               VMScluster members that you use as PATHWORKS servers:   =               o  Use the same disk device to store and access %                  PATHWORKS data files   /               o  Share the same SYSUAF.DAT file   ?                  To do so, define a system logical name in each C                  system disk's startup file that points all cluster D                  members to the shared SYSUAF.DAT file. For example,A                  to define the logical name SYSUAF that points to E                  the SYSUAF.DAT located at DKB0:[SYS0.SYSEXE] on node                   HYDRAC, enter:   2      1-18 Before You Install PATHWORKS for OpenVMS t  e      H                                                VMScluster Considerations    ;                     $ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF -i:                     _$ HYDRAC$DKB0:[SYS0.SYSEXE]SYSUAF.DAT  6                  o  Share the same RIGHTSLIST.DAT file  B                     To do so, define a system logical name in eachF                     system disk's startup file that points all clusterH                     members to the shared RIGHTSLIST.DAT file. To defineB                     the logical name RIGHTSLIST that points to theH                     RIGHTSLIST.DAT file located at DKB0:[SYS0.SYSEXE] on'                     node HYDRAC, enter:   ?                     $ DEFINE/SYSTEM/EXECUTIVE_MODE RIGHTSLIST -.>                     _$ HYDRAC$DKB0:[SYS0.SYSEXE]RIGHTSLIST.DAT  B               4. If you are installing PATHWORKS V1.0C for OpenVMSB                  (NetWare) on a mixed architecture VMScluster, the@                  default location of the SYS volume given in theC                  installation procedure points to the same location H                  for all nodes. Not taking the default leads to multipleG                  copies of the SYS volume, which can needlessly consumerD                  large amounts of disk space and result in incorrectG                  operation of the server. If you are installing in thistH                  environment, you must specify the same location for the)                  SYS volume on all nodes.     H         ________________________________________________________________           Next Steph  E               To install PATHWORKS for OpenVMS, proceed to Chapter 2..                          H                            Before You Install PATHWORKS for OpenVMS 1-19 :                     H                                                                        2H         ________________________________________________________________  H                                         Installing PATHWORKS for OpenVMS      A               This chapter describes how to install the PATHWORKShD               for OpenVMS software. You must follow these proceduresE               regardless of whether you are upgrading from a previousnD               version of the server or installing the server for the               first time.   D               Before you begin the installation procedure, make sureF               that you have completed the preinstallation tasks listed               in Chapter 1.S  >               This chapter consists of the following sections:  1               o  About the Installation ProcedureK  &               o  Installing the Server                 o  Next Stepsc  H         ________________________________________________________________  (         About the Installation Procedure             WHAT IS VMSINSTAL?H               VMSINSTAL is the standard command procedure for installingA               software on the OpenVMS operating system. VMSINSTAL_G               consists of a series of questions (prompts). Your answers F               to these questions provide VMSINSTAL with information it5               needs to install PATHWORKS for OpenVMS.L            H                                     Installing PATHWORKS for OpenVMS 2-1           %      About the Installation Procedure           VMSINSTAL INSTALLATION KIT @            The VMSINSTAL installation kit includes the following$            OpenVMS BACKUP save sets:  E            __________________________________________________________             PATHWORKS SaveoE            Set_____________Contents__________________________________0  ;            PWRKV50C050.A   KITINSTAL.COM, and release notes   7            PWRKV50C050.B   Common files for VAX systems_  9            PWRKV50C050.C   Common files for Alpha systems   <            PWRKV50C050.D   LAN Manager files for VAX systems  >            PWRKV50C050.E   LAN Manager files for Alpha systems  8            PWRKV50C050.F   NetWare files for VAX systems  :            PWRKV50C050.G   NetWare files for Alpha systems  E            PWRKV50C050.H___NetWare_client_files______________________r        WHAT VMSINSTAL DOES&            When you use VMSINSTAL, it:  @            1. Creates PATHWORKS for OpenVMS accounts on the file#               server, if necessary.1  :            2. Restores the files from the save sets in the               installation kit.   E            3. Creates DECnet objects, if you are running DECnet Phase                IV.t  .            4. Installs PATHWORKS DCL commands.  D            5. Creates PATHWORKS for OpenVMS logical names definition               files.  %            6. Deletes obsolete files.t  B            7. Places the files in the directories that you specify#               during the procedure.   ;            8. Verifies that the software has been installedyB               successfully. (See Verifying the Server Installation<               for information on how to run the InstallationD               Verification Procedure after installing the software.)  )      2-2 Installing PATHWORKS for OpenVMSt .  _      H                                                    Installing the Server  H         ________________________________________________________________           Installing the Serverh      "         BEFORE YOU START VMSINSTALF               Before you start the VMSINSTAL command procedure, answer&               the following questions:  0               1. What is the product identifier?  G                  The product identifier tells VMSINSTAL which save setslD                  to copy from the media to a disk on the system. TheA                  product identifier for PATHWORKS for OpenVMS is:                     PWRKV50C050  D               2. What is the name of the device on which you want to!                  mount the media?i  A                  The device name depends on the type of media andhG                  computer you have. For example, if you want to mount acE                  TK50 on the tape drive of your VAXstation 4000 Model_4                  60, then the device name is MKA500.  F               3. Do you want to access the online release notes during,                  the installation procedure?  A                  You can tell VMSINSTAL to ask you if you want toeA                  display or print the online release notes during_E                  installation. Because the release notes may describe_A                  important changes to the installation procedure,rF                  Digital recommends that you read them. Procedures forH                  obtaining the release notes are 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 serverhC                  software only. Digital recommends that you run theSF                  license server on a designated license server system.  C                  The installation procedure gives you the option toEH                  install the standalone license server software from theG                  PATHWORKS for OpenVMS kit. In this case, the PATHWORKS C                  for OpenVMS file servers are not installed. If anynH                  PATHWORKS file server software is installed, you cannot7                  install the standalone license server.   H                                     Installing PATHWORKS for OpenVMS 2-3 e  r            Installing the Server    ?            5. Do you want to install PATHWORKS for OpenVMS (LANb'               Manager) server software?   E               If you have a previous version of PATHWORKS for OpenVMS 7               (LAN Manager), you must upgrade to V5.0C._  D            6. Do you want to install the PATHWORKS V1.0C for OpenVMS(               (NetWare) server software?  E               If you have a previous version of PATHWORKS for OpenVMST3               (NetWare), you must upgrade to V1.0C.   >            7. What is the User Identification Code (UIC) group               number?   >               The PATHWORKS for OpenVMS installation procedureE               creates two OpenVMS accounts if necessary: PWRK$DEFAULTnD               and PWRK$GUEST. The default selection displayed in the;               installation dialog is determined as follows:   E               _______________________________________________________ E               If_._._.______________The_default_is_._._._____________e  B               You are installing    The first available unused UICD               PATHWORKS for         group number, starting with 360.               OpenVMS for theo               first time  A               An account named      The same group number as that @               PCFS$ACCOUNT already  associated with the existing9               exists                account PCFS$ACCOUNT.   <               An account named      The same group number as=               PWRK$DEFAULT or       the existing PWRK$DEFAULT >               PWRK$GUEST already    or PWRK$GUEST accounts, inE               exists________________preference_to_PCFS$ACCOUNT.______         HOW TO START VMSINSTALC            To start VMSINSTAL:  B            1. Ensure that you are logged in to the SYSTEM account.  ?            2. Load the installation kit media onto a drive. (It A               is not necessary to mount the drive, but it must beCB               online, so the installation procedure can mount it.)  )      2-4 Installing PATHWORKS for OpenVMS            H                                                    Installing the Server    G               3. Enter the following command to check the status of theEF                  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:f  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    4i  E                  If the device status is Offline, enter the followinghF                  command to place the device online, replacing device_3                  name with the name of your device:i  3                  $ SET DEVICE/AVAILABLE device_name   <               4. Change the default directory to SYS$UPDATE:  )                  $ SET DEFAULT SYS$UPDATEs  D               5. Start VMSINSTAL and specify the PWRKV50C050 product>                  identifier, the media device, and whether youC                  want access to the online release notes during thee(                  installation procedure:  H         ________________________________________________________________H         If_you_._._.______________Then_enter_._._.______________________  D         Want access to the        @VMSINSTAL PWRKV50C050 device_name+         release notes during the  OPTIONS NW         installation procedure  D         Do not want access        @VMSINSTAL PWRKV50C050 device_name         to the release notes         during the installation H         procedure_______________________________________________________        H                                     Installing PATHWORKS for OpenVMS 2-5 $  A            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.   <            To accept a default, press <Return>. For example:  =            * Are you satisfied with the backup of your system             disk [YES]? <Return>f  &      HOW TO INTERRUPT THE INSTALLATIONE            To interrupt the installation procedure, press <Ctrl/Y> atQC            any time. Then you can restart the installation from theh            beginning.         HOW TO RESPOND TO PROMPTS<            Table 2-1 tells you how to respond to the prompts            VMSINSTAL displays.              Note   B            Table 2-1 shows only the prompts VMSINSTAL displays; itC            does not show any informational messages. For a completeE=            sample installation script, see Appendix C, Sample C            Combined LAN Manager and NetWare Server Installation and #            Configuration Procedure.                               )      2-6 Installing PATHWORKS for OpenVMSf O  V      H                                                    Installing the Server    H         Table_2-1_Installation_Prompts__________________________________  *                            If you want the1         At this            installation procedurerH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Are you            Continue                     <Return>         satisfied with         the backup of_         your system disk         [YES]?  :                            Exit                         NO  9         Select option      Display the release notes    1iC         [2]:[1]            on the screen                To stop thee  F                                                         display at anyC                                                         time, pressMA                                                         <Ctrl/C>.   @                            Print the release notes      <Return>  C                                                         The release E                                                         notes file is C                                                         sent to the_E                                                         default print H                                                         queue SYS$PRINT.E                                                         You can enter_C                                                         the name ofsE                                                         another print >                                                         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 PATHWORKS for OpenVMS 2-7 t               Installing the Server    E      Table_2-1_(Cont.)_Installation_Prompts__________________________.  '                         If you want the .      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____   6                         Print the release notes      3@                         and display them on the      To send theE                         screen                       release notes toR  B                                                      another printE                                                      queue, enter themD                                                      name of anotherA                                                      print queue."  @                                                      To stop theC                                                      screen displaytA                                                      at any time, D                                                      press <Ctrl/C>.  6                         Continue without             4@                         displaying or printing       The release>                         the release notes            notes are  B                                                      automatically>                                                      copied to>                                                      SYS$HELP.  8      Do you want to     Continue                     YES      continue the       installationH
      [NO]?[1]   =                         Exit                         <Return>   8      Do you want to     Install the LAN Manager      YES      install the LAN    server      Manager serverE
      [NO]?  E      [1]This_prompt_is_displayed_only_if_you_specify_OPTIONS_N_when__T  E      you start the VMSINSTAL command procedure or if there are active       processes on the system.e  E                                              (continued on next page)a  )      2-8 Installing PATHWORKS for OpenVMSb    t      H                                                    Installing the Server    H         Table_2-1_(Cont.)_Installation_Prompts__________________________  *                            If you want the1         At this            installation procedureEH         prompt_._._._______to_._._._____________________Enter_._._._____  @                            Omit the LAN Manager         <Return>!                            server   ;         Do you want        Install the NetWare server   YES          to install the         NetWare server
         [NO]?   @                            Omit the NetWare server      <Return>  @         Do you want        Install the standalone       <Return>C         to install         license server               This optionlD         the PATHWORKS                                   installs theF         license server                                  license serverE         [YES]?[2]                                       and transporto  H                                                         software withoutG                                                         a PATHWORKS foreD                                                         OpenVMS fileE                                                         server. ReferrD                                                         to Chapter 5@                                                         for moreD                                                         information.  H         [2]This_prompt_is_displayed_only_if_you_chose_not_to_install____  ;         both the LAN Manager server and the NetWare server.t  H                                                 (continued on next page)                    H                                     Installing PATHWORKS for OpenVMS 2-9    e            Installing the Server    E      Table_2-1_(Cont.)_Installation_Prompts__________________________b  '                         If you want the .      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____h  7                         Install a PATHWORKS file     NO @                         server with the license      This option?                         server                       causes the_  A                                                      installation >                                                      procedure>                                                      to repeatA                                                      the previous D                                                      questions aboutC                                                      installing thetB                                                      file servers,@                                                      so that youC                                                      can select onerA                                                      or both fileN=                                                      servers.S  =      Is the selection   Use the selection            <Return>_      correct [YES]?_  7                         Change the selection         NO_  =                         Terminate the installation   <Ctrl/Y>0  =      Will you allow a   Shut down the system         <Return>0.      system shutdown    as part of the product.      after this         installation procedure      product isP      installed      [YES]?[3]  E      [3]This_prompt_is_displayed_only_if_it_is_necessary_to_reboot___a  =      the system to reload the streams execlet or PCFS driver.e  E                                              (continued on next page)         *      2-10 Installing PATHWORKS for OpenVMS _  _      H                                                    Installing the Server    H         Table_2-1_(Cont.)_Installation_Prompts__________________________  *                            If you want the1         At this            installation procedure H         prompt_._._._______to_._._._____________________Enter_._._._____  :                            Complete the installation    NOG                            procedure without shutting   System shutdown C                            down the system              is requirede  G                                                         for the producttH                                                         installation. IfF                                                         you answer NO,E                                                         you must shuthG                                                         down the systemsF                                                         manually afterH                                                         the installationD                                                         procedure isA                                                         finished.E  @         Do you want        Run the Installation         <Return>1         to run the         Verification Procedurel4         IVP after the      (IVP) automatically after5         installation is    the installation proceduree$         finished [YES]?    completes  H                                                 (continued on next page)                                    H                                    Installing PATHWORKS for OpenVMS 2-11 a  s            Installing the Server    E      Table_2-1_(Cont.)_Installation_Prompts__________________________c  '                         If you want the .      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____   7                         Not run the IVP              NOe  <                                                      You can@                                                      run the IVPC                                                      independent ofaE                                                      the installationn?                                                      procedure.dA                                                      For detailedoC                                                      information oncD                                                      running the IVPC                                                      independently,o@                                                      see "How toA                                                      run the IVP"sD                                                      under Verifying?                                                      the ServersA                                                      Installation B                                                      in Chapter 8.  =      Do you want        Purge all files it           <Return>R       to purge files     replaces      replaced by this       installationS      [YES]?   7                         Not purge any files it       NO                           replaces  =      Do you want to     Delete the files and         <Return> 1      continue with      continue the installationT      the installation       [YES][4]?  E      [4]This_question_is_displayed_only_if_there_are_PATHWORKS_files_R  $      in system-specific directories.  E                                              (continued on next page)     *      2-12 Installing PATHWORKS for OpenVMS ,  u      H                                                    Installing the Server    H         Table_2-1_(Cont.)_Installation_Prompts__________________________  *                            If you want the1         At this            installation procedure H         prompt_._._._______to_._._._____________________Enter_._._._____  :                            Not delete the files and     NO5                            terminate the installationw  @         Do you want        Shutdown the server and      <Return>4         to shutdown        continue the installation         the PATHWORKSd         license server         [YES][5]?   :                            Not shutdown the server      NO,                            and terminate the'                            installation   @         Do you want to     Shutdown the server and      <Return>4         shutdown the       continue the installation         PATHWORKS LANM         Manager server         [YES][5]?   :                            Not shutdown the server      NO,                            and terminate the'                            installations  @         Do you want        Shutdown the server and      <Return>4         to shutdown        continue the installation         the PATHWORKSx         NetWare server         [YES][5]?E  :                            Not shutdown the server      NO,                            and terminate the'                            installation   H         [5]This_question_is_displayed_only_if_the_server_is_still_______           running.  H                                                 (continued on next page)  H                                    Installing PATHWORKS for OpenVMS 2-13 i               Installing the Server    E      Table_2-1_(Cont.)_Installation_Prompts__________________________   '                         If you want the .      At this            installation procedureE      prompt_._._._______to_._._._____________________Enter_._._._____     =      Enter default      Associate the newly          <Return> '      UIC group number   created OpenVMSo-      for PWRK$DEFAULT   accounts PWRK$DEFAULT +      and PWRK$GUEST     and PWRK$GUEST with (      [nnn]:             the default user1                         identification code (UIC)D*                         group number (nnn)  B                         Associate the newly          A three-digit@                         created accounts with        UIC number.A                         the UIC group number you     For detailed @                         specify                      information  D                                                      about UIC groupA                                                      numbers, see/@                                                      the OpenVMSE                                                      System Manager's <                                                      Manual.  =      NetWare SYS        Keep the same SYS volume     <Return>y       volume             location
      locationl      [device:[PWVN$SYSVOL]]:[6]   @                         Specify a different          A differentC                         SYS volume location for      disk device or_?                         NetWare                      directory.   E      [6]This_question_is_displayed_only_if_NetWare_is_being__________u        installed.W  E                                              (continued on next page)S          *      2-14 Installing PATHWORKS for OpenVMS t         H                                                    Installing the Server    H         Table_2-1_(Cont.)_Installation_Prompts__________________________  *                            If you want the1         At this            installation procedureOH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Do you want        Copy new files onto the      <Return>.         to copy new        existing SYS volume         files onto         the existing         NetWare SYSd         volume [YES]?[7]  :                            Leave the existing SYS       NO*                            volume as it is  H         [7]This_question_is_displayed_only_if_NetWare_is_being_installed  ,         and there is an existing SYS volume.H         ________________________________________________________________    H         ________________________________________________________________           Next Steps             WHAT TO DO NEXTW"               Before you continue:  >               o  Edit the system startup file to enable server                  utilities.N  @               o  Install any desired optional software (refer to?                  "Install optional software" at the end of thisa                  chapter).  F               o  Depending on which servers you are installing, do one"                  of the following:            H                                    Installing PATHWORKS for OpenVMS 2-15 a  n            Next Stepsf  E      ________________________________________________________________l@                                              Which tells you howE      If_you_are_._._.____Proceed_to_._._.____to_._._.________________e  >      Installing the LAN  Chapter 3           Configure the LAN<      Manager server                          Manager server.  B      Installing the      Chapter 4           Configure the NetWare4      NetWare server                          server.  E      Installing the      Chapter 5           Configure the standalone <      standalone license                      license server.      servers  <      Upgrading the LAN   Chapter 6,          Use the upgradeD      Manager server      Creating PATHWORKS  procedure to create andB      from PATHWORKS      V5.0C for OpenVMS   edit upgrade reports.&      V4.x for OpenVMS    (LAN Manager)E      ____________________Upgrade_Reports_____________________________   !      EDIT THE SYSTEM STARTUP FILEt@            To enable server utilities (such as the Configuration?            utility and the LAN Manager Upgrade utility) without E            starting the server, add the following lines to the system             startup file:  E      ________________________________________________________________       For the LAN Manager      server or the standaloneNE      license_server,_add:_______For_the_NetWare_server,_add:_________e  E      $_@SYS$STARTUP:PWRK$LOGICAL$_@SYS$STARTUP:PWVN$LOGICALS_________   =            These lines run command procedures that define therE            appropriate logical names, and should be deleted after you D            add lines to start up the PATHWORKS servers, as described            in Chapter 8.  ?            The name of the system startup file depends on whichs:            version of OpenVMS is installed on your system:            *      2-16 Installing PATHWORKS for OpenVMS           H                                                               Next Steps  H               __________________________________________________________               On this H               system_._._._________The_file_is_called_._._._____________  ?               OpenVMS VAX V5.5-2   SYS$STARTUP:SYSTARTUP_V5.COME  @               OpenVMS VAX V6.0     SYS$STARTUP:SYSTARTUP_VMS.COM               and higher or                 OpenVMS Alpha V1.5H               and_higher________________________________________________  !         INSTALL OPTIONAL SOFTWARE F               Before you configure the server, Digital recommends thatG               you install any desired optional software included in the (               PATHWORKS for OpenVMS kit.                                                              H                                    Installing PATHWORKS for OpenVMS 2-17                 Next Steps     C               ________________________Note ________________________   <               If you choose to install any optional software=               now, redefine system parameters as described inn>               the section "Step 7: Check system parameters" in>               Chapter 1, before you run AUTOGEN and reboot the               system.a  C               _____________________________________________________y  ?            Table 2-2 lists and describes each optional software ;            product and tells you where to find installation             information.   E      Table_2-2_Optional_Software_____________________________________   E      Product__________Description___________Installation_Information_e  E      eXtended Qio     An OpenVMS file       Chapter 9, Installing thei@      Processor Plus   system that improves  XQP+, in this guide.$      (XQP+)           concurrency in%                       your computer'su"                       input/output#                       subsystem ande(                       improves directory*                       caching by including*                       new features such as(                       multithreading and(                       asynchronous cache                       writes  ?      DECprint         A printing system     DECprint Supervisor @      Supervisor       that provides queue   for OpenVMS Software?                       management and        Installation Guide,_@                       printing features     which is included in>                       for PostScript        your software kit.E      _________________printers_______________________________________   E            After you configure the server, you may need to reboot the C            system for the configuration to take effect. If you have D            installed optional software, this system reboot activates?            the server and the optional software simultaneously.       *      2-18 Installing PATHWORKS for OpenVMS l  t                  H                                                                        3H         ________________________________________________________________  H         Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server      E               This chapter describes how to configure the LAN Manager <               server and consists of the following sections:  E               o  About the LAN Manager Server Configuration Procedure   E               o  How to Start the LAN Manager Configuration Procedure   D               o  How to Respond to LAN Manager Configuration Prompts  @               o  How to Change LAN Manager Configuration Default                  Settingsh                 o  Next Steps   H         ________________________________________________________________  <         About the LAN Manager Server Configuration Procedure    ,         WHAT IS THE CONFIGURATION PROCEDURE?C               The LAN Manager configuration procedure, PWRK$CONFIG, D               is installed by the PATHWORKS for OpenVMS installation               procedure.  @               Like the installation procedure, the configurationE               procedure asks you a series of questions (prompts). The.D               procedure uses your answers to configure the PATHWORKS5               V5.0C for OpenVMS (LAN Manager) server.T              H     Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-1           9      About the LAN Manager Server Configuration Procedure     *      WHAT THE CONFIGURATION PROCEDURE DOES?            The configuration procedure PWRK$CONFIG is a command             procedure that:  6            o  Creates the PATHWORKS on-disk structure.  >            o  Creates the LAN Manager user accounts and shares               databases.  E            o  Allows you to set or change the ADMIN account password.   A            o  Gives you the option to modify server configuration E               settings, such as which services you want to enable and E               the LAN Manager domains that are visible to the server.o  @            o  Gives you the option of entering the Configuration7               utility to modify aspects of the server's B               configuration, such as the maximum number of clients<               that can connect to the server simultaneously.  D            o  Gives you the option of entering the upgrade procedureD               to perform the upgrade procedure if PATHWORKS V4.x for$               OpenVMS was installed.  :            o  Gives you the option of starting the server.  A            After you install the server, you must run PWRK$CONFIGe@            before you can start the server. In a VMScluster, youE            must run PWRK$CONFIG on each node before you can start then            server on that node.t  C               ________________________Note ________________________   A               After you start the server, you can run PWRK$CONFIGC@               again, to move the PATHWORKS data files to anotherA               disk device. If you have more than one system disk,lA               for example in a VMScluster with both VAX and Alpha_<               processors, for each system disk, you must run=               PWRK$CONFIG on at least one node that uses thatt=               system disk in order to move the PATHWORKS dataw$               files to another disk.  C               _____________________________________________________d    I      3-2 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server            H                 Before You Start the LAN Manager Configuration Procedure  H         ________________________________________________________________  @         Before You Start the LAN Manager Configuration Procedure  H               Before you start the PWRK$CONFIG command procedure, answer&               the following questions:  E               1. What is the name of the OpenVMS disk device that yourE                  want to store the following PATHWORKS data files on?i  1                  o  Configuration parameter filest  -                  o  License server data filesV                    o  Log filesV  '                  o  Printer spool files   3                  o  Remote Program Load (RPL) files   ;                  o  User Authentication Service (UAS) 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.s  F                 ________________________Note  ________________________  D                 The server frequently accesses the data files copied=                 to the specified disk device, which generates @                 input to and output from the disk. If this inputA                 /output occurs on the system disk, it can degrade >                 the performance of both the OpenVMS system andB                 the server. Therefore, Digital recommends that youA                 specify a disk device other than the system disk.   E                 _____________________________________________________   4               2. What is the ADMIN account password?  D                  The configuration procedure prompts you to define aF                  password for the LAN Manager account ADMIN, which youG                  use to administer the server. The password you specify H                  can contain up to 14 alphanumeric characters as well asF                  any of the following special characters: ! # $ % & ()                   - . ^ _ ` { } ~  H     Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-3           =      Before You Start the LAN Manager Configuration Procedure     C               ________________________Note ________________________a  @               If your server will be part of a domain, enter the>               password to the domain's existing ADMIN account.  C               _____________________________________________________n  =            3. Do you want to change any of the default serveri?               configuration settings? These settings determine:d  0               o  Whether the license server runs  B                  The license server is a software program that youA                  can run on your OpenVMS system to grant licensesr@                  to clients. Any client that wants to use server>                  resources must have a valid license. Each LAND                  needs only one PATHWORKS license server. The clientB                  license product authorization keys (PAKs) must beE                  loaded on the system that runs the PATHWORKS license_                  server.  @                  In a VMScluster, the PAKs must be loaded on allB                  nodes that run the PATHWORKS license server. ThisD                  is best accomplished by adding the PAKS to a shared"                  license database.  =                  By default, the license server does not run.   %                  For more informationO  ?                  For detailed information on managing PATHWORKS >                  licenses, see the Guide to Managing PATHWORKS                  Licenses.  B               o  Whether the server runs in backward compatibility                  modee  B                  Backward compatibility mode lets both V4.x and V5D                  PATHWORKS clients connect to the V5 server, so thatC                  you can upgrade clients at your convenience over ad7                  period of time instead of all at once.   D                  Run the server in backward compatibility mode untilC                  you have upgraded all clients and all client usershA                  have logged in to the server once. This lets the >                  server synchronize the users' LAN Manager and#                  OpenVMS passwords.t  I      3-4 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server     n      H                 Before You Start the LAN Manager Configuration Procedure    F                 ________________________Note  ________________________  <                 If an OpenVMS account password contains more<                 characters than LAN Manager allows (14), the/                 password synchronization fails._  E                 _____________________________________________________   C                     By default, the server does not run in backwardeB                     compatibility mode. Refer to the PATHWORKS forF                     OpenVMS (LAN Manager) Server Administrator's GuideE                     for more information about backward compatibility                      mode.n  >                  o  Whether the Remote Boot service is enabled  H                     The Remote Boot service enables clients to boot fromA                     a share instead of from their own hard disks.   F                 ________________________Note  ________________________  ?                 If you enable the Remote Boot service, you must A                 configure your server to load the NetBEUI network                  transport.  E                 _____________________________________________________   E                     By default, the Remote Boot service does not run.   (                     For more information  B                     For detailed information about the Remote BootC                     service, see the LAN Manager Remote Boot Guide.   7                  o  Whether the Timesource service runs   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 programsxF                     on all computers the same time each day). Each LAN/                     needs only one time server.   D                     By default, the Timesource service does not run.  4                  o  Whether the Alerter service runs  H     Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-5           =      Before You Start the LAN Manager Configuration Procedure     D                  The Alerter service sends messages called alerts toD                  servers and clients that run the Messenger service.  C               ________________________Note ________________________   ?               The V5 server does not run the Messenger service.   C               _____________________________________________________i  6                  By default, the Alerter service runs.  >               o  Names of the users who receive alert messages  A                  By default, alert messages are sent to the ADMIN_                  account._  *               o  LAN Manager computer name  D                  This is the unique name that identifies your server)                  in a LAN Manager domain.   A                  By default, the LAN Manager computer name is theo.                  server's DECnet network name.  (               o  LAN Manager domain name  D                  This is the LAN Manager domain in which your serverE                  is located. A domain is a subdivision of clients and (                  servers on the network.  <                  The default LAN Manager domain is LANGROUP.  *               o  Other LAN Manager domains  @                  These are the names of other domains visible toD                  the server. For example, if you use an interface toD                  display a list of available servers on the LAN, theD                  interface displays the servers located in the otherB                  domains you specify, as well as those in your own!                  server's domain.a  =                  By default, no other LAN Manager domains are                   defined.n  *               o  LAN Manager security mode  <                  The security mode can be based on passwordsA                  associated with LAN Manager user accounts (user-sA                  level security) or based on passwords associatedA;                  with shared network resources (share-levelV                  security).e  I      3-6 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server     I      H                 Before You Start the LAN Manager Configuration Procedure    G                     The default LAN Manager security mode is user-level                      security.r  +                  o  Server announce comment   H                     This is the comment the LAN Manager server sends outG                     when it announces its presence on the network. ThisNG                     comment may also be shown when you use an interface ;                     to display a list of available servers.S  E                     The default server announce comment is "PATHWORKSh5                     V5.0C for OpenVMS (LAN Manager)".                                                                   H     Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-7 e  s      =      Before You Start the LAN Manager Configuration Procedurei    +               o  PATHWORKS VMScluster aliasn  ?                  If your server is a VMScluster member, this is A                  the network name that all servers in the cluster C                  use. The alias lets remote nodes (such as clients) D                  treat the entire cluster as though it were a singleC                  server. For example, a client user can specify theS@                  PATHWORKS alias to connect to any server in theC                  cluster; the user does not know (and does not need B                  to know) to which server the client is connected.  E                  The default PATHWORKS VMScluster alias is the DECneto                  cluster alias.t  "               For more information  D               Unless otherwise specified, you can find more detailedC               information on any of the services or concepts listed E               above in the PATHWORKS for OpenVMS (LAN Manager) ServerK$               Administrator's Guide.  A               For detailed information on changing default server_D               configuration settings, see "How to Change LAN Manager?               Configuration Default Settings " in this chapter.r  ;            4. Do you want to run the Configuration utility?e  C               The configuration procedure asks you whether you wante/               to run the Configuration utility._  @               The Configuration utility is a character-oriented,C               menu-driven interface that lets you modify aspects ofdD               the server's configuration, such as the maximum numberA               of clients that can connect to the server and which C               network transports the server uses. Refer to SoftwareiE               requirements for more information about the transports.n  @               If you do not run the Configuration utility duringA               the configuration procedure, you can do so later byoC               entering the ADMINISTER/CONFIG command at the OpenVMS                system prompt:  !               $ ADMINISTER/CONFIG     I      3-8 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Servers           H                 Before You Start the LAN Manager Configuration Procedure    F                 ________________________Note  ________________________  >                 The configuration procedure displays a message>                 stating how many clients your system's currentD                 configuration can support. If this number is too lowD                 for the needs of your network, run the Configuration;                 utility during the configuration procedure._  E                 _____________________________________________________y  %                  For more informationo  D                  For detailed information on using the ConfigurationF                  utility, access the utility's online help by choosing4                  the Help button on utility screens.  :               5. Do you want to run the upgrade procedure?  E                  The upgrade procedure is a character-oriented, menu-3F                  driven interface that lets you upgrade PATHWORKS V4.xG                  for OpenVMS users, groups, services, and access rightseH                  so that they work with the LAN Manager features offered*                  by PATHWORKS for OpenVMS.  F                  The LAN Manager server supports many more LAN ManagerA                  features than previous versions. Use the upgrade F                  procedure to upgrade server security to a LAN Manager;                  security model so that existing users can:h  B                  o  Take advantage of the new LAN Manager features  6                  o  Access upgraded services and files  A                  You can run the upgrade procedure as part of theAD                  configuration procedure or independently, after theG                  configuration procedure completes. However, you cannotrG                  run the upgrade procedure while the LAN Manager server E                  is running. If you start the upgrade procedure whilelG                  the server is running, a prompt is displayed that asksr9                  you whether you want to stop the server.s  %                  For more informationS  F                  For detailed information about the upgrade procedure,D                  see Chapter 6, Creating PATHWORKS V5.0C for OpenVMSH                  (LAN Manager) Upgrade Reports, and Chapter 7, Upgrading>                  to PATHWORKS V5.0C for OpenVMS (LAN Manager).  1               6. Do you want to start the server?   H     Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-9 r         =      Before You Start the LAN Manager Configuration Procedure     >               The configuration procedure asks you if you want>               to start the server. If you do not want to start?               the server at that time, you can do so later from @               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:   7               o  You still need to run the V4.x server.n  B                  You do not need to stop the V4.x server while you>                  configure and upgrade the LAN Manager server.@                  However, when you start the V5 server, the V4.x,                  server stops automatically.  B               o  You may need to run the V4.x server again for any                  reason.  C                  File access problems may occur if you stop the LAN <                  Manager server and restart the V4.x server.  E               o  You are installing the server on multiple VMScluster                   members._  >                  Before you start the server on any VMScluster>                  member, Digital recommends that you configureB                  PATHWORKS for OpenVMS on each cluster member thatB                  you want to use as a server. You can then use theB                  SYSMAN utility to start the server simultaneouslyC                  on all cluster members. If you choose to start the A                  server individually on each cluster member, makeoD                  sure that you do so from the 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 8.n        J      3-10 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server _  _      H                     How to Start the LAN Manager Configuration Procedure  H         ________________________________________________________________  <         How to Start the LAN Manager Configuration Procedure  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. Change the default directory to SYS$UPDATE:  )                  $ SET DEFAULT SYS$UPDATE   ?               3. Start the configuration procedure by entering:                     $ @PWRK$CONFIGs  H         ________________________________________________________________  ;         How to Respond to LAN Manager Configuration Promptse  D               Table 3-1 tells you how to respond to the prompts that#               PWRK$CONFIG displays.2                 Note  G               Table 3-1 shows only the prompts PWRK$CONFIG displays; it_F               does not show any informational messages. For a completeE               sample configuration script, see Appendix A, Sample LAN F               Manager Server Installation and Configuration Procedure.                              H    Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-11    n      8      How to Respond to LAN Manager Configuration Prompts    E      Table_3-1_LAN_Manager_Configuration_Prompts_____________________s  '                         If you want the_/      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____c  =      Do you want to     Shut down the server or,     <Return>p1      continue with      if your server is part ofu1      configuration      a VMScluster, all serverse&      [yes]:[1]          in the cluster  7                         Abort the configuration      NO !                         procedure   =      Enter disk         Copy the PATHWORKS on-       <Return>~-      device name        disk structure to then,      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 then0                         last time you configured#                         the server.n  .                         If you run PWRK$CONFIG/                         or PWVN$CONFIG again ont0                         another system disk in a0                         VMScluster, and move the/                         location of the on-diskt.                         structure, the default.                         disk device is the new/                         location of the on-disk "                         structure.  E      [1]This_prompt_is_only_displayed_if_you_started_the_server______e        previously.  E                                              (continued on next page)         J      3-12 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server .         H                      How to Respond to LAN Manager Configuration Prompts    H         Table_3-1_(Cont.)_LAN_Manager_Configuration_Prompts_____________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  C                            Copy the PATHWORKS on-disk   device_namen2                            structure to an OpenVMS5                            disk device different from 0                            the default displayed  ;         Do you want        Move the PATHWORKS on-disk   YESc4         to move the        structure to the new disk!         PATHWORKS          devicet         data files         from device          current_device         to devicen         new_device         [no]:[2]  @                            Leave the PATHWORKS on-      <Return>D                            disk structure on the        You are onceF                            current disk device          again prompted  B                                                         to specify@                                                         the diskD                                                         device whereD                                                         you want theE                                                         PATHWORKS on-eF                                                         disk structure@                                                         located.  H         [2]This_prompt_is_only_displayed_if_you_ran_PWRK$CONFIG_or______  F         PWVN$CONFIG previously and chose to move the PATHWORKS on-disk)         structure to another disk device.   H                                                 (continued on next page)            H    Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-13           8      How to Respond to LAN Manager Configuration Prompts    E      Table_3-1_(Cont.)_LAN_Manager_Configuration_Prompts_____________c  '                         If you want theo/      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____   8      Do you want        Prompt you to enter a new    YES.      to enter a         ADMIN account password      new ADMIN      account password 
      [no]:[3]r  =                         Keep the existing ADMIN      <Return> (                         account password  =      Enter ADMIN        Associate a password with    password C      network account    the ADMIN account            If your servereD      password:                                       will be part of  D                                                      a domain, enterA                                                      the passwordnD                                                      to the domain'sC                                                      existing ADMINo=                                                      account.   =      Re-enter to                                     passwordi      verify password:   E      [3]This_prompt_is_only_displayed_if_you_ran_PWRK$CONFIG_________   C      previously. The procedure asks for the Administrator's accountfC      password if you have joined a domain with a Windows NT server.t  E                                              (continued on next page)p                      J      3-14 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server c  r      H                      How to Respond to LAN Manager Configuration Prompts    H         Table_3-1_(Cont.)_LAN_Manager_Configuration_Prompts_____________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  B         Enter item         Change the default           The numberG         number, or         configuration settings       associated with E         RETURN to use      displayed                    a setting you G         these values                                    want to change.eD         [done]:                                         For detailed  C                                                         information C                                                         on changingsE                                                         these defaulteE                                                         configurationrE                                                         settings, see E                                                         the followinguE                                                         section, "HowrA                                                         to ChangeiC                                                         LAN ManagereE                                                         ConfigurationAH                                                         Default Settings:                                                         ".  @                            Use the default              <Return>1                            configuration settings $                            displayed  ;         Do you want        Enter the server             YESoD         to change          Configuration utility        For detailedC         the system                                      information D         configuration                                   on using theE         now [no]:                                       Configurationt  G                                                         utility, access E                                                         the utility's D                                                         online help.  @                            Not enter the server         <Return>0                            Configuration utility  H                                                 (continued on next page)    H    Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-15 w  h      8      How to Respond to LAN Manager Configuration Prompts    E      Table_3-1_(Cont.)_LAN_Manager_Configuration_Prompts_____________o  '                         If you want the5/      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____A    =      Do you want        Enter the upgrade            <Return> A      to upgrade         procedure, which you can     For detailed @      PATHWORKS V4.x     use to create reports to     information=      databases to V5    prepare for upgrade, and     on usingt@      now [yes][4]:      to perform a complete or     the upgrade?                         custom upgrade               procedure,   E                                                      creating upgrade A                                                      reports, and B                                                      upgrading the@                                                      server, seeB                                                      Chapter 6 and?                                                      Chapter 7.   7                         Not enter the upgrade        NOr!                         procedurer  =      Do you want to     Start the server             <Return>t/      start PATHWORKS    automatically after the .      V5.0C for          installation procedure!      OpenVMS on node    completes       node_name now      [yes][5]:  7                         Not start the server         NO E      [4]This_prompt_is_only_displayed_if_you_have_PATHWORKS_V4.x_for_         OpenVMS installed.aC      [5]This prompt is not displayed if you must execute AUTOGEN ort7      reboot the system before PATHWORKS can be started.tE      ________________________________________________________________i  E      ________________________________________________________________t  =      How to Change LAN Manager Configuration Default Settingso      J      3-16 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server r         H                 How to Change LAN Manager Configuration Default Settings    F               After the configuration procedure asks you to define theD               LAN Manager ADMIN account password, it displays a listG               of the default server configuration settings and a promptg(               that lets you change them:  P           PATHWORKS V5.0C for OpenVMS is presently configured to run as follows:  -            1.  Run the license server:     NON-            2.  PATHWORKS V4 compatibility: NO.-            3.  Enable Remote Boot service: NO -            4.  Enable Timesource service:  NOn.            5.  Enable Alerter service:     YES0            5a. Alert user names:           ADMIN1            6.  LAN Manager computer name:  HYDRACr3            7.  LAN Manager domain name:    LANGROUPy)            8.  Other LAN Manager domains: /            9.  LAN Manager security mode:  USERtT            10. Server announce comment:    PATHWORKS V5.0C for OpenVMS (LAN Manager)0            11. PATHWORKS VMScluster alias: HYDRA  @         Enter item number, or RETURN to use these values [done]:  F                 ________________________Note  ________________________  @                 Item 5a is only displayed if item 5 is YES. Item@                 11 is only displayed if your server is part of a                 VMScluster.t  E                 _____________________________________________________   "               For more information  E               For a description of each server configuration setting,tA               see "Before You Start the LAN Manager Configurations2               Procedure " earlier in this chapter.  D               To change default server configuration settings, enterD               the number of the setting you want to change. A promptF               is displayed that lets you change the setting. Table 3-29               describes possible values for each setting.e  H               To save any settings you change, press <Return> to use theE               default answer DONE. For more information on completing H               the installation procedure, see the previous section, "How@               to Respond to LAN Manager Configuration Prompts ."  H    Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-17 t  t      =      How to Change LAN Manager Configuration Default Settingsc    E      Table_3-2_LAN_Manager_Configuration_Settings____________________r  E      Setting_________________________Possible_Values_________________l  A      1. Run the license server:      Enter YES to run the licensetE                                      server, or press <Return> to use 4                                      the default NO.  C      2. PATHWORKS V4 compatibility:  Enter YES to run the server in A                                      backward compatibility mode, A                                      or press <Return> to use the 0                                      default NO.  C      3. Enable Remote Boot service:  Enter YES to enable the RemotefD                                      Boot service, or press <Return>;                                      to use the default NO.   <      4. Enable Timesource service:   Enter YES to enable theA                                      Timesource service, or pressnD                                      <Return> to use the default NO.  D      5. Enable Alerter service:      Enter NO to disable the AlerterB                                      service, or press <Return> to9                                      use the default YES.   C      5a. Alert user names:[1]        Enter the names of users, eachuD                                      containing up to 20 characters,D                                      who can receive alert messages,C                                      and separate them with commas.a  @      6. LAN Manager computer name:   Enter a computer name of up?                                      to 15 characters, or pressnA                                      <Return> to use the default.pB                                      The default displayed is yourC                                      system's DECnet name. However,n@                                      if your system's DECnet andD                                      NETBIOS names are different andA                                      the NETBIOS name is the node B                                      name, enter the NETBIOS name.  D      7. LAN Manager domain name:     Enter a domain name of up to 15E                                      characters, or press <Return> to 5                                      use the default.   E      [1]Only_displayed_if_alerter_service_is_enabled.________________   E                                              (continued on next page)   J      3-18 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server a  d      H                 How to Change LAN Manager Configuration Default Settings    H         Table_3-2_(Cont.)_LAN_Manager_Configuration_Settings____________  H         Setting_________________________Possible_Values_________________  G         8. Other LAN Manager domains:   Enter up to four other domains,_@                                         each containing up to 15E                                         characters, and separate them 4                                         with commas.  E         9. LAN Manager security mode:   Enter SHARE to specify share- @                                         level security, or pressC                                         <Return> to use the defaultgC                                         USER and specify user-levelU1                                         security.u  E         10. Server announce comment:    Enter the comment of up to 48 D                                         characters that you want theB                                         server to send out when itE                                         announces its presence on the E                                         network, or press <Return> to 8                                         use the default.  A         11. PATHWORKS VMScluster        Enter the PATHWORKS aliaseC         alias:[2]                       for the VMScluster to which E                                         your server belongs, or pressdD                                         <Return> to use the default.H         [2]Only_displayed_in_a_VMScluster.______________________________  H         ________________________________________________________________  H         ________________________________________________________________  0         Selecting the LAN Manager Network Device  D               The configuration procedure selects the network deviceE               depending on the transport you specify when you run the H               procedure. If the server has more than one network device,C               and you do not want to use the device selected, or if G               the server has a network device that is not recognized by G               the PATHWORKS server, you can manually select the network =               device to use with the transport you specified.         H    Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server 3-19    w      -      Selecting the LAN Manager Network Devicee    >            The following OpenVMS logical names are provided soA            that you can control the network device over which thec%            PATHWORKS server operates:t  E            __________________________________________________________ E            Logical_Name__________Transport___________________________F  '            NETBIOS$DEVICE        DECnete  '            PWRK$KNBDAEMON_       TCP/IP             DEVICEe  E            PWRK$NETBEUI_DEVICE___NetBEUI_____________________________   D            For example, to select device EWA0: for DECnet transport,C            enter the following command before you start the server:   /            $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:_    E      ________________________________________________________________         Next Steps   =            You can start the PATHWORKS V5.0C for OpenVMS (LANgE            Manager) server automatically as part of the configuration @            procedure. However, if you are installing the NetWareE            server as well, you can complete the NetWare configurationtA            procedure before rebooting the system and starting the D            servers. NetWare configuration is described in Chapter 4.  @            If you are upgrading from PATHWORKS V4.x for OpenVMS,A            be sure to perform the upgrade procedures described in #            Chapter 6 and Chapter 7.   B            If you are ready to start the server, see Chapter 8 for            instructions.                J      3-20 Configuring the PATHWORKS V5.0C for OpenVMS (LAN Manager) Server                       H                                                                        4H         ________________________________________________________________  H             Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server      H               This chapter describes how to configure the NetWare server5               and consists of the following sections:   :               o  About the NetWare Configuration Procedure  8               o  About NetWare Configuration Information  <               o  Running the NetWare Configuration Procedure  1               o  Reconfiguring the NetWare Server   =               For an example of a complete configuration, see                Appendix B.   H         ________________________________________________________________  1         About the NetWare Configuration Procedure   ,         WHAT IS THE CONFIGURATION PROCEDURE?2               The NetWare configuration procedure,G               SYS$UPDATE:PWVN$CONFIG.COM, is installed by the PATHWORKSPG               for OpenVMS installation procedure. Like the installation F               procedure, the configuration procedure asks you a seriesC               of questions. The procedure then uses your answers toeH               configure the PATHWORKS for OpenVMS (NetWare) file server.                    H         Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server 4-1           .      About the NetWare Configuration Procedure    *      WHAT THE CONFIGURATION PROCEDURE DOES'            The configuration procedure:   6            1. Creates the PATHWORKS on-disk structure.  B            2. Allows you to specify a NetWare file server name andE               checks the file server name you provide for conformancee)               with NetWare naming syntax.   A            3. Allows you to specify an alternate location for thea*               NetWare configuration files.  B            4. Allows you to configure the NetWare Virtual Terminal               (NVT).  A            5. Allows you to run the license server on the system.   B            6. Allows you to configure up to eight NetWare networksC               and verifies that the network numbers you provide are 2               valid (8-digit) hexadecimal numbers.  >            7. Writes your answers into configuration files and.               logical name command procedures.  >               For the logical names and their definitions, see(               Appendix G and Appendix H.  !      WHEN TO CONFIGURE THE SERVEROB            You must configure the NetWare server after you install>            it and before you start it for the first time. In aA            VMScluster, you must configure the server on each node .            that will run the PATHWORKS server.  E      ________________________________________________________________   ,      About NetWare Configuration Information                  E      4-2 Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server_ f  r      H                                  About NetWare Configuration Information             ABOUT NETWORK NUMBERSpH               A network number (address) is a unique 8-digit hexadecimalG               number used by the NetWare operating system to identify au               network.  H               When you configure the server, the configuration procedure@               asks you to specify network numbers for your localE               area network (LAN). Additionally, if you plan to enablenF               tunneling, you must specify another number for each node+               at the far end of the tunnel.n            TYPES OF NETWORK NUMBERSF               Table 4-1 describes three types of configuration network               numbers.    H               Table_4-1_NetWare_Configuration_Network_Numbers___________  H               Number________Description_________________________________  A               External      Also called the IPX network number orhH               network       network address, the external network numberF               number        is a unique number (for example, 00633905)G                             that designates the network address for thee(                             file server.  H                             Each file server, workstation, and device onH                             one LAN shares the same network number. ThisE                             number is a hexadecimal number that often G                             corresponds to the Ethernet segment number.   E               Tunnel        Also called the IPX network number in theeA               network       PWVN$CONFIG.COM procedure, the tunnelyB               number        network number is a unique number thatD                             designates the IPX DECnet tunnel network$                             address.  G                             The tunnel network number must be different D                             from the internal network number and allD                             other NetWare network numbers in the LAN(                             environment.  H                                                 (continued on next page)    H         Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server 4-3           ,      About NetWare Configuration Information    E            Table_4-1_(Cont.)_NetWare_Configuration_Network_Numbers___   E            Number________Description_________________________________   C            Internal      The internal network number is a unique 8-oD            network       digit hexadecimal number that you assign toE            number        your file server. This number must be unique_7                          for each file server on a LAN.e  @                          If you do not enter an internal network<                          number, the configuration procedureC                          calculates one from the DECnet node numberrA                          for the OpenVMS system. If the system ismA                          not running DECnet, the default value isaE            ______________00000DEC.___________________________________   3      NUMBER AND TYPES OF NETWORKS YOU CAN CONFIGURE E            You can configure up to eight networks for any one NetWare A            server. The eight networks can contain up to two local +            networks and IPX DECnet tunnels.   D            A local network is a group of file servers, workstations,A            and peripheral devices such as printers that share the .            same Ethernet wire in a local area.  >            An IPX DECnet tunnel is a point-to-point connection@            between two servers on different networks. The tunnelD            connects two or more IPX networks over an existing DECnet4            network that carries only DECnet traffic.  &      ABOUT TOKEN RING AND FDDI SUPPORT9            If you have Token Ring or FDDI interfaces, the_A            configuration procedure detects them and allows you todA            configure them for the NetWare server. Table 4-2 showsNE            the interfaces that are supported and the frame types they_            support._                  E      4-4 Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server_ _  _      H                                  About NetWare Configuration Information    H               Table_4-2_Types_of_NetWare_Interfaces_____________________  H               Media_______DIX_SNAP_________IEEE-802.2_(SAP_E0)__________  4               Token Ring  Supported        Supported  4               FDDI        Supported        Supported  H               Ethernet____Supported________Supported____________________    H         ________________________________________________________________  3         Running the NetWare Configuration Procedure     /         WHEN TO RUN THE CONFIGURATION PROCEDURE F               You need to run the configuration procedure if you have:  G               o  Turned the system into a VMScluster. In this case, you4E                  must run the configuration procedure on each node incE                  the cluster that will be running the NetWare server.   H               o  Upgraded your VAX system (for example, upgraded an 8820@                  to a 6640) to account for new Ethernet devices.           BEFORE YOU BEGINC               Set the default directory to SYS$UPDATE:, as follows:R  &               $ SET DEFAULT SYS$UPDATE  .         HOW TO RUN THE CONFIGURATION PROCEDURE1               To run the configuration procedure:s  -               1. Enter the following command:_                    $ @PWVN$CONFIG   H               2. Respond to the configuration questions as shown in "How(                  to respond to prompts."          H         Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server 4-5 _  _      0      Running the NetWare Configuration Procedure    %      HOW CONFIGURATION QUESTIONS WORKf<            An asterisk (*) at the beginning of a line in theA            configuration procedure identifies a question you must *            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 HELPlC            To get online help on a specific configuration question,g8            enter a question mark (?) after the question.    '      HOW TO INTERRUPT THE CONFIGURATION E            You can interrupt the configuration procedure at any time. D            To interrupt the configuration procedure, press <Ctrl/Y>.        HOW TO RESPOND TO PROMPTS<            Table 4-3 tells you how to respond to the prompts             PWVN$CONFIG displays.  C               ________________________Note ________________________g  @               Table 4-3 shows only the prompts; it does not show?               any informational messages. For a complete sample B               configuration script, see Appendix B, Sample NetWare>               Server Installation and Configuration Procedure.  C               _____________________________________________________r                              E      4-6 Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server            H                              Running the NetWare Configuration Procedure    H         Table_4-3_Configuration_Prompts_________________________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Do you want to     Shut down the server or,     <Return>4         continue with      if your server is part of4         configuration      a VMScluster, all servers)         [yes]:[1]          in the clusterE  :                            Abort the configuration      NO$                            procedure  @         Enter disk         Copy the PATHWORKS on-       <Return>0         device name        disk structure to the/         where PATHWORKS    default OpenVMS disk +         data files         device displayed 4         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.  1                            If you run PWRK$CONFIG 2                            or PWVN$CONFIG again on3                            another system disk in a 3                            VMScluster, and move then2                            location of the on-disk1                            structure, the default 1                            disk device is the new 2                            location of the on-disk%                            structure.:  H         [1]This_prompt_is_displayed_only_if_you_started_the_server______           previously.t  H                                                 (continued on next page)        H         Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server 4-7           0      Running the NetWare Configuration Procedure    E      Table_4-3_(Cont.)_Configuration_Prompts_________________________d  '                         If you want thea/      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____   @                         Copy the PATHWORKS on-disk   device_name/                         structure to an OpenVMS 2                         disk device different from-                         the default displayed   8      Do you want        Move the PATHWORKS on-disk   YES1      to move the        structure to the new diskc      PATHWORKS          device      data files       from device      current_device       to device      new_devicee
      [no]:[2]r  =                         Leave the PATHWORKS on-      <Return>hA                         disk structure on the        You are onceyC                         current disk device          again prompted   ?                                                      to specify =                                                      the diskaA                                                      device wherewA                                                      you want thenB                                                      PATHWORKS on-C                                                      disk structurel=                                                      located.K  E      [2]This_prompt_is_displayed_only_if_you_ran_PWRK$CONFIG_or______h  C      PWVN$CONFIG previously and chose to move the PATHWORKS on-diskr&      structure to another disk device.  E                                              (continued on next page)s            E      4-8 Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server_ _  _      H                              Running the NetWare Configuration Procedure    H         Table_4-3_(Cont.)_Configuration_Prompts_________________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  @         Name of            Use the default server       <Return>         PATHWORKS          namei         for OpenVMS          (NetWare) file         server [server-d         name]:  F                            Use another server name      Correct server<                                                         name           System-specificS         directory(&         [SYS$SPECIFIC:[PWVN$PRIVATE]]:  @                            Use the default device and   <Return>$                            directory  B                            Use another device or        Device andD                            directory                    directory to;                                                         use   @         Do you want to     Not allow clients using      <Return>-         configure NVT      the Novell Virtual ,         on this system     Terminal protocol
         [NO]?   ;                            Allow clients using the      YES 2                            Novell Virtual Terminal#                            protocolr  @         Do you want to     Not run the license server   <Return>         run a LicenseD         Server on this         system [NO]?  H                                                 (continued on next page)      H         Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server 4-9 t  t      0      Running the NetWare Configuration Procedure    E      Table_4-3_(Cont.)_Configuration_Prompts_________________________y  '                         If you want the /      At this            configuration procedureaE      prompt_._._._______to_._._._____________________Enter_._._._____d  8                         Run the license server       YES  =      Internal           Use the default internal     <Return> &      network number     network number      (hexadecimal)      [network_
      number]:d  D                         Use another internal         Correct network;                         network number               numbern  =      Maximum SPX        Use no more than 50          <Return>       sockets [50]:      sockets   E                         Use a greater number of      50, 200, 500, or_9                         sockets                      1000H  =      Network            Allow you to enter a new     <Return>s-      Configuration      network configuration       Action (ADD)       [ADD]:[3]  1                         At least one network mustt.                         be configured in order-                         to proceed. A maximum 0                         of eight networks can be#                         configured.n  =      Network Type       Configure a new local        <Return>       (LOCAL,            network       TUNNEL,NONE)B      [L]:[4]  E      [3]This_prompt_is_displayed_only_if_there_are_no_NetWare________   !      networks configured already.cB      [4]This prompt is displayed only if you are configuring a new
      network.o  E                                              (continued on next page)a  F      4-10 Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server e  e      H                              Running the NetWare Configuration Procedure    H         Table_4-3_(Cont.)_Configuration_Prompts_________________________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  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]:[4]  <                            Not configure a new          NONEG                            network                      When you selecte  H                                                         NONE, the dialogB                                                         returns toC                                                         the NetworkiE                                                         ConfigurationrE                                                         Action prompt   @         Enter 5 for        Use the default frame type   <Return>%         Ethernet_II        (DIX/SNAP)u         (DIX), or 6 for          802.2 (Sap E0).i         [5]:[4]e  9                            Use the IEEE-802.2 frame     6N                            typeu  H         Network Number     Use the unique network       n, a hexadecimalE         [0]:[4]            number                       value greaters>                                                         than 0  H         [4]This_prompt_is_displayed_only_if_you_are_configuring_a_new___           network.  H                                                 (continued on next page)  H        Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server 4-11           0      Running the NetWare Configuration Procedure    E      Table_4-3_(Cont.)_Configuration_Prompts_________________________r  '                         If you want the /      At this            configuration proceduregE      prompt_._._._______to_._._._____________________Enter_._._._____u  =      Network            Finish the configuration     <Return> !      Configuration      procedure       Actionl      (ADD,DELETE,a      MODIFY,NONE)i      [NONE]:  8                         Add a new network            ADD  ;                         Delete a network             DELETE   ;                         Modify the configuration     MODIFY .                         of an existing network  =      Do you want        Reboot the system            <Return>W/      to reboot the      automatically after the /      system now         configuration procedure_!      [YES][5]:          completes   7                         Not reboot the system        NO   /                         After the configurationa0                         procedure completes, you.                         must reboot the system0                         before you can start the'                         NetWare server.   =      Do you want to     Start the server             <Return>o/      start PATHWORKS    automatically after the /      for OpenVMS        configuration procedure !      (NetWare) now      completesi      [YES]:a  7                         Not start the server         NOdE      [5]This_prompt_is_displayed_only_if_it_is_necessary_to_reboot___c  A      the system to reload the streams execlet or the PCFS driver.NE      ________________________________________________________________   F      4-12 Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server X  C      H                              Running the NetWare Configuration Procedure    #         HOW TO CONFIRM YOUR ANSWERS <               After you have answered all the questions, theH               configuration procedure displays a summary of your answers6               and prompts you to confirm your choices.                                                                                  H        Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server 4-13           0      Running the NetWare Configuration Procedure                It then asks you:  6            * Is this configuration satisfactory [YES]?  E            __________________________________________________________aE            If_you_are...______Then...________________________________   ;            Satisfied with     Press <Return> to answer YES.m            the configuration            summary  D            Not satisfied      Answer NO to change any of the values.E            with the           The configuration procedure prompts you -            configuration      for each value.uE            summary___________________________________________________r  D            When you are done with the configuration procedure, start1            the server, as described in Chapter 8.u    E      _________________________________________________________________  %      Reconfiguring the NetWare ServerO    "      HOW TO RECONFIGURE THE SERVER?            You can reconfigure the server at any time after the 3            installation. To reconfigure the server:a  -            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,n            see Chapter 8.                 F      4-14 Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server f  n      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 logicalaG               name command procedure. The new definitions supersede the F               previous definitions. However, the previous logical nameG               definitions remain in the files, thus providing a history +               of the configuration changes..                                                                            H        Configuring the PATHWORKS V1.0C for OpenVMS (NetWare) Server 4-15 e  f                  H                                                                        5H         ________________________________________________________________  H                   Configuring and Starting the Standalone License Server      E               The PATHWORKS license server is a software program that_E               you can run on your OpenVMS system to grant licenses to                clients.  1               You can install the license server:O  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 to                support:  )               o  LAN Manager clients only   0               o  LAN Manager and NetWare clients  %               o  NetWare clients onlyo  D               Digital recommends that you install the license serverB               on a designated OpenVMS system without the PATHWORKSD               file server, to ensure smooth and continuous operationC               of the license server. Alternatively, you can run theNF               license server on a cluster with PATHWORKS file servers,E               where cluster failover provides reliability. Therefore,$E               the PATHWORKS for OpenVMS kit allows you to install thenH               standalone license server separately from the file server.  B               Typically, each LAN needs only one PATHWORKS licenseC               server. The client license product authorization keys ?               (PAKs) must be loaded on the system that runs the)'               PATHWORKS license server.   C               In a VMScluster, the PAKs must be loaded on all nodes A               that run the PATHWORKS license server. This is besthA               accomplished by adding the PAKS to a shared licensen  H               Configuring and Starting the Standalone License Server 5-1 l  p            C            database. For detailed information on managing PATHWORKSaB            licenses, see the Guide to Managing PATHWORKS Licenses.  C            This chapter describes how to configure and start up the C            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   8            o  How to Start the Standalone License Server    E      ________________________________________________________________y  @      Before You Begin to Configure the Standalone License Server  B            You install the standalone license server from the sameB            software kit that you use to install the PATHWORKS file=            server. The procedures are described in Chapter 2._      E      ________________________________________________________________u  .      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 usedo$            by the PATHWORKS clients.  A            For LAN Manager clients, you can configure the license_2            server to use the following transports:              o  DECnet              o  NetBEUI               o  TCP/IP[1]o              ___________________:            [1]        Requires a TCP/IP transport product.D                       Suggested products are listed in the PATHWORKS  D                       V5.0C for OpenVMS (LAN Manager) Release Notes.  ?      5-2 Configuring and Starting the Standalone License Servern           H                                Configuring the Standalone License Server    F               To configure the standalone license server to use one orG               more of these transports, use the PWRK$CONFIG.COM command E               procedure, as described in "Configuring the LAN Manager                Transports ."i  =               For NetWare clients, you can also configure the C               license server to use the IPX transport. To configureo?               the standalone license server to use IPX, use thei=               PWVN$CONFIG.COM command procedure, described in 3               "Configuring the NetWare Transport ."       H         ________________________________________________________________  .         Configuring the LAN Manager Transports  @               The following section describes how to use the LAND               Manager's configuration command procedure to configure?               the transports for the standalone license server.v  E               After the installation procedure completes, the OpenVMS ?               system prompt ($) is displayed. If the system wasp.               rebooted following installation:  E               1. Ensure that you are logged in to the SYSTEM account.n  <               2. Change the default directory to SYS$UPDATE:  )                  $ SET DEFAULT SYS$UPDATE   ?               3. Start the configuration procedure by entering:_                    $ @PWRK$CONFIG   6               4. Respond to the configuration prompts.                  H               Configuring and Starting the Standalone License Server 5-3 i  r      8      How to Respond to LAN Manager Configuration Prompts  E      ________________________________________________________________   8      How to Respond to LAN Manager Configuration Prompts  <            Table 5-1 tells you how to respond to the prompts             PWRK$CONFIG displays.              Note   D            Table 5-1 shows only the prompts PWRK$CONFIG displays; itC            does not show any informational messages. For a complete >            sample configuration script, see Appendix D, SampleC            Standalone License Server Installation and Configuration             Procedure.   E      Table_5-1_PWRK$CONFIG_Configuration_Prompts_____________________   '                         If you want the /      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____   =      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,k  2                         the default disk device is1                         the one you specified theC0                         last time you configured#                         the server.   .                         If you run PWRK$CONFIG/                         or PWVN$CONFIG again onr0                         another system disk in a0                         VMScluster, and move the/                         location of the on-diskm.                         structure, the default.                         disk device is the new/                         location of the on-diskK"                         structure.  E                                              (continued on next page)     ?      5-4 Configuring and Starting the Standalone License Server            H                      How to Respond to LAN Manager Configuration Prompts    H         Table_5-1_(Cont.)_PWRK$CONFIG_Configuration_Prompts_____________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  C                            Copy the PATHWORKS on-disk   device_name 2                            structure to an OpenVMS5                            disk device different fromR0                            the default displayed  ;         Do you want        Move the PATHWORKS on-disk   YES]4         to move the        structure to the new disk!         PATHWORKS          device          data files         from device          current_device         to devicew         new_device         [no]:[1]  @                            Leave the PATHWORKS on-      <Return>D                            disk structure on the        You are onceF                            current disk device          again prompted  B                                                         to specify@                                                         the diskD                                                         device whereD                                                         you want theE                                                         PATHWORKS on- F                                                         disk structure@                                                         located.  H         [1]This_prompt_is_displayed_only_if_you_ran_PWRK$CONFIG_or______  F         PWVN$CONFIG previously and chose to move the PATHWORKS on-disk)         structure to another disk device.m  H                                                 (continued on next page)            H               Configuring and Starting the Standalone License Server 5-5 2         8      How to Respond to LAN Manager Configuration Prompts    E      Table_5-1_(Cont.)_PWRK$CONFIG_Configuration_Prompts_____________   '                         If you want the /      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____i  =      Do you want to     Allow licenses to be         <Return> *      serve PATHWORKS    served over DECnet      licenses over      DECnet [yes]:[2]   7                         Not allow licenses to be     NOn*                         served over DECnet  8      Do you want to     Allow licenses to be         YES+      serve PATHWORKS    served over NetBEUI       licenses over      NetBEUI [no]:[2]h  =                         Not allow licenses to be     <Return>t+                         served over NetBEUI   8      Do you want to     Allow licenses to be         YES*      serve PATHWORKS    served over TCP/IP      licenses over      TCP/IP [no]:[2]  =                         Not allow licenses to be     <Return>a*                         served over TCP/IP  =      Do you want        Start the server             <Return> /      to start the       automatically after thee/      PATHWORKS          configuration procedure_!      license server     completes       now [yes]:   E      [2]Default_answers_may_differ_if_you_have_run_the_PWRK$CONFIG___         procedure previously.  E                                              (continued on next page)         ?      5-6 Configuring and Starting the Standalone License Servero r  o      H                      How to Respond to LAN Manager Configuration Prompts    H         Table_5-1_(Cont.)_PWRK$CONFIG_Configuration_Prompts_____________  *                            If you want the2         At this            configuration procedureH         prompt_._._._______to_._._._____________________Enter_._._._____  :                            Complete the configuration   NO5                            procedure without starting H         ___________________the_server___________________________________      H         ________________________________________________________________  )         Configuring the NetWare Transport   D               The following section describes how to use the NetWareB               configuration command procedure to configure the IPXA               transport so that the standalone license server can :               support NetWare client license verification.  E               After the installation procedure completes, the OpenVMSe?               system prompt ($) is displayed. If the system was0.               rebooted following installation:  E               1. Ensure that you are logged in to the SYSTEM account.   <               2. Change the default directory to SYS$UPDATE:  )                  $ SET DEFAULT SYS$UPDATEW  ?               3. Start the configuration procedure by entering:i                    $ @PWVN$CONFIGo  G               4. Respond to the configuration prompts. For descriptions <                  of the types of information required in the8                  configuration procedure, see Chapter 4.              H               Configuring and Starting the Standalone License Server 5-7    C      4      How to Respond to NetWare Configuration Prompts  E      ________________________________________________________________   4      How to Respond to NetWare Configuration Prompts  A            Table 5-2 tells you how to respond to the prompts thatc>            PWVN$CONFIG displays. For a complete example of the5            configuration dialog, refer to Appendix D.   E      Table_5-2_PWVN$CONFIG_Configuration_Prompts_____________________   '                         If you want the_/      At this            configuration procedure E      prompt_._._._______to_._._._____________________Enter_._._._____   =      Enter disk         Copy the PATHWORKS on-       <Return>p-      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,S  2                         the default disk device is1                         the one you specified theo0                         last time you configured#                         the server.   .                         If you run PWRK$CONFIG/                         or PWVN$CONFIG again on 0                         another system disk in a0                         VMScluster, and move the/                         location of the on-disk1.                         structure, the default.                         disk device is the new/                         location of the on-diskI"                         structure.  @                         Copy the PATHWORKS on-disk   device_name/                         structure to an OpenVMS 2                         disk device different from-                         the default displayed   E                                              (continued on next page).        ?      5-8 Configuring and Starting the Standalone License Servera C  i      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_._._._____  ;         Do you want        Move the PATHWORKS on-disk   YESs4         to move the        structure to the new disk!         PATHWORKS          deviceg         data files         from device          current_device         to device          new_device         [no]:[2]  @                            Leave the PATHWORKS on-      <Return>D                            disk structure on the        You are onceF                            current disk device          again prompted  B                                                         to specify@                                                         the diskD                                                         device whereD                                                         you want theE                                                         PATHWORKS on-eF                                                         disk structure@                                                         located.           System-specificA         directoryp&         [SYS$SPECIFIC:[PWVN$PRIVATE]]:  @                            Use the default device and   <Return>$                            directory  B                            Use another device or        Device andD                            directory                    directory to<                                                         use.  H         [2]This_prompt_is_only_displayed_if_you_ran_PWRK$CONFIG_or______  F         PWVN$CONFIG previously and chose to move the PATHWORKS on-disk)         structure to another disk device.e  H                                                 (continued on next page)  H               Configuring and Starting the Standalone License Server 5-9 e  r      4      How to Respond to NetWare Configuration Prompts    E      Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts______________  '                         If you want the_/      At this            configuration procedurerE      prompt_._._._______to_._._._____________________Enter_._._._____i  =      Do you want to     Allow licenses to be         <Return>u'      serve PATHWORKS    served over IPXs      licenses over      IPX [YES]?   7                         Not allow licenses to be     NO '                         served over IPX   =      Internal           Use the default internal     <Return> &      network number     network number      (hexadecimal)      [network_
      number]:   D                         Use another internal         Correct network;                         network number               number   =      Maximum SPX        Use no more than 50          <Return>v      sockets [50]:      sockets   E                         Use a greater number of      50, 200, 500, ore9                         sockets                      1000n  =      Network            Allow you to enter a new     <Return> -      Configuration      network configuration,      Action (ADD)r      [ADD]:[3]  1                         At least one network musth.                         be configured in order-                         to proceed. A maximum 0                         of eight networks can be#                         configured.T  E      [3]This_prompt_is_only_displayed_if_there_are_no_NetWare________a  >      networks configured already. At least one network must beA      configured in order to complete the configuration procedure.   E                                              (continued on next page)h  @      5-10 Configuring and Starting the Standalone License Server p  h      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_._._._____  @         Network Type       Configure a new local        <Return>"         (LOCAL,            network         TUNNEL,NONE)         [L]:[4]n  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 listingY         [controller]:[4]  <                            Not configure a new          NONEG                            network                      When you selecte  H                                                         NONE, the dialogB                                                         returns toC                                                         the Network E                                                         Configuration E                                                         Action prompt   @         Enter 5 for        Use the default frame type   <Return>%         Ethernet_II        (DIX/SNAP)          (DIX), or 6 fort         802.2 (Sap E0).          [5]:[4]E  9                            Use the IEEE-802.2 frame     6                             type   H         Network Number     Use the unique network       n, a hexadecimalE         [0]:[4]            number                       value greater >                                                         than 0  H         [4]This_prompt_is_only_displayed_if_you_are_configuring_a_new___           network.  H                                                 (continued on next page)  H              Configuring and Starting the Standalone License Server 5-11 n  r      4      How to Respond to NetWare Configuration Prompts    E      Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________.  '                         If you want theu/      At this            configuration procedureeE      prompt_._._._______to_._._._____________________Enter_._._._____o  =      Network            Finish the configuration     <Return>.!      Configuration      procedure       Action       (ADD,DELETE,N      MODIFY,NONE)       [NONE]:  8                         Add a new network            ADD  ;                         Delete a network             DELETE   ;                         Modify the configuration     MODIFY .                         of an existing network  =      Do you want        Reboot the system            <Return>n/      to reboot the      automatically after thet/      system now         configuration procedure !      [YES][5]:          completesy  7                         Not reboot the system        NOs  /                         After the configurationl0                         procedure completes, you.                         must reboot the system,                         before you can start"                         PATHWORKS.  =      Do you want        Start the server             <Return> /      to start the       automatically after the /      PATHWORKS          configuration procedurer!      license server     completese      now [YES]:i  7                         Not start the server         NOn  E      [5]This_prompt_is_only_displayed_if_it_is_necessary_to_reboot____  A      the system to reload the streams execlet or the PCFS driver.   E                                              (continued on next page)   @      5-12 Configuring and Starting the Standalone License Server s  l      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_._._._____  @         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:p  D               o  During the configuration procedure, as described in>                  "Configuring the Standalone License Server ."  0               o  Manually from the command line.  4               o  Automatically each time you reboot.  0         HOW TO START THE LICENSE SERVER MANUALLY@               If you did not start the license server during theF               configuration procedure, you can start it manually using%               the following commands:o  H               __________________________________________________________H               To_serve...______Enter..._________________________________  :               LAN Manager      $ @SYS$STARTUP:PWRK$STARTUP               licenses  :               NetWare          $ @SYS$STARTUP:PWVN$STARTUP               licenses  H              Configuring and Starting the Standalone License Server 5-13           /      How to Start the Standalone License Servere  E            ___________________________________________________________E            To_serve...______Enter..._________________________________n  7            NetWare and      $ @SYS$STARTUP:PWRK$STARTUP 7            LAN Manager      $ @SYS$STARTUP:PWVN$STARTUP E            licenses__________________________________________________                   Example  &            $ @SYS$STARTUP:PWVN$STARTUP              Resultk  A            The license server starts, and messages similar to them#            following are displayed:          $ @sys$startup:pwvn$startup  3      PATHWORKS license server will use DECnet, IPX.e1      PATHWORKS mail notification will use DECnet. 9      Process NETBIOS created with identification 0000012C $      Starting IPX Daemon (NPSD)...OK@      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.   E               _______________________________________________________                On this E               system_._._._________The_file_is_called_._._.__________   ?               OpenVMS VAX V5.5-2   SYS$STARTUP:SYSTARTUP_V5.COM_  @               OpenVMS VAX V6.0     SYS$STARTUP:SYSTARTUP_VMS.COM               or higher; ore               Alpha V1.5 or E               higher_________________________________________________   C            2. Add the appropriate startup commands, as shown in thefB               following example. Add the command to the file belowD               all lines that start network transports. The following  @      5-14 Configuring and Starting the Standalone License Server           H                               How to Start the Standalone License Server    E                  example shows how to edit the file to serve both LAN .                  Manager and NetWare licenses.                    Example  R         $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET  	         . 	         .o	         .t  #         $ @SYS$STARTUP:PWRK$STARTUPe#         $ @SYS$STARTUP:PWVN$STARTUPt  7         HOW TO START THE LICENSE SERVER IN A VMSCLUSTERSC               If you installed and configured the PATHWORKS license H               server on multiple members of the same VMScluster, DigitalC               suggests that you use the SYSMAN utility to start the H               server manually and simultaneously on all cluster members.               To do so:P  G               1. Ensure that you are logged in to the SYSTEM account onn;                  one of the server nodes in the VMScluster.   G               2. Define all the VMScluster members on which you want to E                  start the standalone license server. For example, ifrF                  you want to start the license server on nodes HYDRAA,$                  HYDRAB, and HYDRAC:  L                  $ MCR SYSMAN SET ENVIRONMENT /NODE=(HYDRAA, HYDRAB, HYDRAC)  C               3. Start the license server on the nodes you defined:i  H         ________________________________________________________________H         To_serve...______Enter..._______________________________________  B         LAN Manager      $ MCR SYSMAN DO @SYS$STARTUP:PWRK$STARTUP         licenses  B         NetWare          $ MCR SYSMAN DO @SYS$STARTUP:PWVN$STARTUP         licenses  B         NetWare and      $ MCR SYSMAN DO @SYS$STARTUP:PWRK$STARTUPB         LAN Manager      $ MCR SYSMAN DO @SYS$STARTUP:PWVN$STARTUPH         licenses________________________________________________________  H              Configuring and Starting the Standalone License Server 5-15 _  _                  H                                                                        6H         ________________________________________________________________  H               Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) UpgradeH                                                                  Reports      A               This chapter describes how to use the PATHWORKS forpB               OpenVMS upgrade procedure to create and edit upgrade               reports.  B               You can use these reports as input data files to theC               upgrade procedure. This ensures a smooth and complete E               upgrade of existing users, groups, services, and access F               rights from PATHWORKS V4.x for OpenVMS so that they work)               with PATHWORKS for OpenVMS.$  D               For complete information on the upgrade procedure, seeF               Chapter 7, Upgrading to PATHWORKS V5.0C for OpenVMS (LAN               Manager).   >               This chapter consists of the following sections:  !               o  Before You Begind  &               o  About Upgrade Reports  *               o  Using the Upgrade Utility  )               o  Creating Upgrade Reports_  (               o  Editing Upgrade Reports                 o  Next Stepsa              H   Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-1    P            Before You Beginm  E      ________________________________________________________________D        Before You Begin$            HAVE YOU DONE?sE            Before you continue, make sure that you have completed the E            installation procedure, as described in Chapter 2, and theo>            configuration procedure, as described in Chapter 3.    E      ________________________________________________________________k        About Upgrade Reports            WHAT IS AN UPGRADE REPORT? ?            An upgrade report is a file that you create with they0            upgrade procedure. An upgrade report:  C            o  Lists elements of the current server database (users,cC               groups, services) that the upgrade procedure will and                will not upgrade.r  ?            o  Points out aspects of the current server database C               that do not comply with LAN Manager restrictions (foroA               example, file service names that exceed LAN Manager                limits).  C            You can edit an upgrade report to change information and E            correct conflicts. You can then use the report as an inputcD            data file during the upgrade procedure to ensure a smooth             and complete upgrade.        TYPES OF REPORTSy,            Types of upgrade reports include:              o  Usersr              o  Groups  %            o  File and print servicesr    K      6-2 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports            H                                                    About Upgrade Reports             ABOUT THE USERS REPORT(               The Users report displays:  F               o  Current PATHWORKS V4.x for OpenVMS user accounts thatB                  the upgrade procedure will upgrade to LAN Manager                  accounts   F                  By default, the upgrade procedure upgrades an account1                  if any of the following is true:   H                  -  The resource identifier PCFS$USER is associated with                      the account.  H                  -  The user is a member of an existing PATHWORKS group.  D                  -  The user's login directory contains at least oneD                     file with a DOS access control list entry (ACE),F                     indicating that the file was created from a client                      workstation.  ?               o  Current OpenVMS user accounts that the upgrade C                  procedure will not upgrade to LAN Manager accounts                   by default   H                  By default, the upgrade procedure does not upgrade userF                  accounts that meet none of the criteria listed above.G                  You can display and edit the Users report to make sure D                  that the accounts of PATHWORKS users that fall into,                  this category are upgraded.  @               o  LAN Manager user accounts on the primary domainD                  controller (if your local server is not the primary#                  domain controller)R  A                  This part of the display lets you see which user D                  accounts on the local server have duplicates on the+                  primary domain controller.   D                  If an account on the local server has the same userE                  name as an account on the primary domain controller, F                  the upgrade procedure upgrades the PATHWORKS V4.x forF                  OpenVMS account to a LAN Manager account on the local                  server.  D                  After the upgrade procedure completes and the localG                  server is part of the domain, however, the LAN ManageruD                  account on the primary domain controller supersedesH                  the one on the local server. Depending on whether these  H   Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-3 _  _            About Upgrade Reports    E               accounts belong to different users or to the same user,T.               one of the following must occur:  E               _______________________________________________________NE               If_._._.______________Then_._._._______________________   ?               The accounts belong   The user must log on to thewE               to the same user      domain with the correct user name B                                     and password to take advantageD                                     of the logon validation feature.D                                     (This is the password associatedC                                     with the account on the primary 7                                     domain controller.)   @               The accounts belong   Before you begin the upgrade@               to different users    procedure, you must edit the>                                     Users report to rename theE               ______________________account_on_the_local_server._____o              For more informationo  @            For detailed information on editing the Users report,C            see "When and how to edit a Users report" in the sectioni9            Editing Upgrade Reports later in this chapter.o        ABOUT THE GROUPS REPORT&            The Groups report displays:  ?            o  Current PATHWORKS groups, OpenVMS UIC groups, and >               OpenVMS resource identifiers on the local serverD               that the upgrade procedure will upgrade to LAN Manager               groups.H  =               The upgrade procedure upgrades any UIC group or_C               resource identifier that includes at least one member A               who is considered a PATHWORKS user according to theiD               criteria described in the previous section, "About the               Users report".  B            o  The members of each UIC group or resource identifier               listed.o  B            o  LAN Manager groups on the primary domain controller.  E               These groups are displayed only if your local server is 0               not the primary domain controller.  K      6-4 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reportsn u  a      H                                                    About Upgrade Reports    H               o  A warning message if the number of groups listed in theF                  report exceeds the number LAN Manager allows for each                  domain (256).    0         ABOUT THE FILE AND PRINT SERVICES REPORTG               This report displays all file and print services, OpenVMS F               user accounts, and OpenVMS print queues that the upgradeF               procedure will upgrade to LAN Manager shares. The reportD               displays each service, account, or queue on one of two               lists:  H               __________________________________________________________               If the service,                account, or H               queue_._._.___________Then_the_report_displays_it_on_._._.  E               Follows LAN Manager   The list of shares that users canwG               naming conventions    access with both Basic and Enhanced:0               (a share name that    Redirectors.               contains eight               characters or                fewer followed               by an extensiono!               that contains three "               characters or fewer)  E               Does not follow       The list of shares that users canuF               LAN Manager naming    access with only the Digital BasicH               conventions___________Redirector._________________________           SAMPLE REPORTSA               See Appendix E for complete sample upgrade reports.u    H         ________________________________________________________________  !         Using the Upgrade Utility.              H   Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-5 n               Using the Upgrade Utility    !      BEFORE YOU START THE UTILITYE?            Before you start the upgrade procedure, follow these             steps:   ?            1. Make sure that you know the name of the domain in B               which your server resides. If your server is not theD               primary domain controller, make sure that you know the=               primary's name and that the primary is running.   "               For more information  ?               For detailed information about domains and domain =               controllers, see the PATHWORKS for OpenVMS (LAN 4               Manager) Server Administrator's Guide.  3            2. Log in to the OpenVMS SYSTEM account.b  @            3. Use the PWRK$SHOWSYS command procedure to find out,               whether the server is running:                 $ @PWRK$SHOWSYS                  Result  =               If the server is running, the command procedure A               displays all currently running PATHWORKS processes.n               For example:  O      VAX/VMS V5.5-2  on node AMUN   8-NOV-1994 12:21:38.31   Uptime  0 02:34:51_R        Pid    Process Name    State  Pri      I/O       CPU       Page flts Ph.MemR      00000137 NETBIOS         HIB      5     1629   0 00:00:04.20       481    187R      000001AA PWRK$ADMIN_0    LEF     12       55   0 00:00:03.34       331    183R      00000145 PWRK$LICENSE_R  HIB     10       59   0 00:00:04.29       997     65R      000001BD PWRK$LMDMN      HIB     11      541   0 00:00:16.36      3720    989R      0000011F PWRK$MASTER     HIB      8      525   0 00:00:10.85      1327    117R      000001A7 PWRK$MONITOR    HIB      4       83   0 00:00:05.59      1465    396R      0000013C PWRK$NBDAEMON   HIB     10       29   0 00:00:01.37       300    133  :               The processes that may be displayed include:            K      6-6 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports     N      H                                                Using the Upgrade Utility                        NETBIOS                  PWRK$ADMIN_0_                  PWRK$LICENSE_R "                  PWRK$LICENSE_S[1]                  PWRK$LMDMN                   PWRK$LMMCPe                  PWRK$LMRIPL[2]                   PWRK$LMSRV                   PWRK$MASTER!                  PWRK$NBDAEMON[3] "                  PWRK$KNBDAEMON[4]H                  [1]This_process_runs_only_if_you_start_the_license_____  ;                  server during the configuration procedure. G                  [2]This process runs only if you start the Remote Boots<                  service during the configuration procedure.A                  [3]This process runs only if you use the NetBEUIl                  transport. @                  [4]This process runs only if you use the TCP/IP                  transport.E  F                  If the server is not running, none of these processes                  are displayed.   H               4. If the server is running, use the PWRK$SHUTDOWN command&                  procedure to stop it:  -                  $ @SYS$STARTUP:PWRK$SHUTDOWNn  C                  If you do not stop the server, the upgrade commandS,                  procedure stops it for you.  B               You are now ready to start the upgrade procedure, as,               described in the next section.            HOW TO START THE UTILITY-               To start the upgrade procedure:S  <               1. Change the default directory to SYS$UPDATE:  )                  $ SET DEFAULT SYS$UPDATE   -               2. At the system prompt, enter:A                     $ @PWRK$UPGRADE  H   Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-7 i  a            Using the Upgrade Utility                   Result  A               If you did not stop the running server earlier, thei7               upgrade procedure displays the following:t  I      This procedure shuts down the currently running PATHWORKS V5 server.s0      Do you want to continue with upgrade [yes]:  6            3. Press <Return> to continue with upgrade.                 Result  ;               The upgrade procedure displays the configured &               transports. For example:  5      Shutting down the currently running server(s)... <      PATHWORKS is configured to use DECnet, NetBEUI, TCP/IP.  N      If you are upgrading a server in an existing domain that has a designatedM      primary domain controller, the upgrade procedure communicates with it to.7      enumerate users and groups in the existing domain.S  K      If you are not upgrading a server in an existing domain, press Return.   ;      Are you upgrading a server in an existing domain [no]:_  B            4. Enter YES to upgrade a server in an existing domain.                 Result  @               If you have more than one transport configured andC               you are upgrading a server in an existing domain, theg7               upgrade procedure displays the following:   L      The upgrade procedure uses only one of the transports configured on theK      server.  Choose a transport, and make sure that the designated primary 1      domain controller is running that transport.   =      Which transport do you want to use for upgrade [DECnet]:E  B            5. Enter the name of the transport that you want to useA               for the upgrade or press Return to use the default.A                 Result  B               If you are upgrading a server in an existing domain,A               the upgrade procedure starts the transport you have ?               chosen. The upgrade procedure then starts the LAN A               Manager upgrade utility. If you are upgrading in an ?               existing domain, the upgrade utility displays theb               following prompt:   K      6-8 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports            H                                                Using the Upgrade Utility    =                  Enter the name of the Domain [PF2 for Help]:t  B               6. Enter the name of the domain in which your server                  resides.r                    Result   G                  If you are upgrading the server in an existing domain,ME                  the upgrade procedure displays the following prompt:e  G         Enter the Primary Domain Controller's node name [PF2 for Help]:_  "               7. Do the following:  H         ________________________________________________________________A         If your local                             And the upgrade H         server_is_._._.______Then_._._.___________procedure_._._._______  C         The primary domain   Press <Return>       Displays the MainOH         controller or a                           menu; you have startedH         standalone server                         the upgrade procedure.  E         Part of a domain,    Enter the name of    Prompts you for theoH         but not the          the remote server    user name and passwordA         primary domain       that is or will be   of a privileged_F         controller           the primary domain   account (see below).'                              controller   !                              Note +                              Make sure thatR/                              the primary domains*                              controller is*                              available and(                              running the.                              network transport.                              that you selected'                              to use for +                              upgrade. If its.                              is not, a message.                              is displayed that*                              says that the+                              primary domain .                              controller is notH         _____________________listening._________________________________  B               8. When you enter the name of the remote server, theA                  upgrade procedure displays the following prompt:R  H   Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-9 n  p            Using the Upgrade Utility    8               Enter a user name for a privileged account%               [ADMIN | PF2 for Help]:e  B               Press <Return> to use the default ADMIN or enter the@               name of another LAN Manager account that has admin5               privileges on the domain you specified.V                 Result  D               The upgrade procedure displays a prompt similar to the               following:  +               Enter ADMIN account password:c  C            9. Enter the password, and then re-enter it as prompted._                 Result  A               The upgrade procedure logs you on to the domain and %               displays the Main menu:                                                   L      6-10 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports l  n      H                                                Using the Upgrade Utility    #         HOW TO NAVIGATE THE UTILITY 9               To navigate and exit the upgrade procedure:s  H               __________________________________________________________H               If_you_want_to_._._.__Then_._._.__________________________  E               Choose a menu option  Use the up and down arrow keys tonC                                     highlight the option, and pressc-                                     <Return>.   <               Return to the         Do one of the following:G               previous menu         o  Highlight the Return to Previous   G                                        Menu option, and press <Return>.   6                                     o  Press <Ctrl/Z>.  <               Exit the upgrade      Do one of the following:G               procedure             o  Highlight the Exit option on the   E                                        Main menu, and press <Return>.   G                                     o  Press <Ctrl/Z> at the Main menu.pH               __________________________________________________________           HOW TO GET ONLINE HELPG               To display context-sensitive online help when you use thee                upgrade procedure:  H               __________________________________________________________               If you wantiH               help_._._.____________Then_._._.__________________________  E               About a menu option   Use the up and down arrow keys tolC                                     highlight the option, and press *                                     <PF2>.  H               At_a_prompt___________Press_<PF2>.________________________              H  Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-11                 Creating Upgrade Reportsd  E      ________________________________________________________________         Creating Upgrade Reportsu      $      HOW TO CREATE AN UPGRADE REPORT'            To create an upgrade report:s  A            1. From the upgrade procedure Main menu, choose Createt               Upgrade Reports.                 Result  ;               The Create Upgrade Reports menu is displayed:e  A            2. From the Create Upgrade Reports menu, choose Users,r>               Groups, or File and Print Services. (Because youB               can use one report as input to another, create these%               reports in that order.)s                 Result  $               The upgrade procedure:  B               o  Displays the Users report, Groups report, or File2                  and Print Services report screen.  @               o  For a User or a File and Print Services report,>                  creates the report and displays the following                  prompt:  /                  Do you want to view the reporte?                  Enter Y or N, or press Return for the default: E                                                                     Y   D               o  For a Groups report, displays the following prompt:  D      Do you want to use a Users report as input to the Groups report3      Enter Y or N, or press Return for the default:eC                                                                   Np  B            3. If you are creating a Groups report, specify whetherE               you want to use the Users report you created and edited ?               previously as input to the creation of the Groups_               report:_  L      6-12 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports _         H                                                 Creating Upgrade Reports  H         ________________________________________________________________)                               Enter . . .aH         If_you_._._.___________________And_the_upgrade_procedure_._._.__  ?         Want to use the       Y        Prompts you to enter theoB         Users report                   name of the report or pressB                                        <Return> to use the defaultC                                        PWRK$UPG$USERS.RPT, and then C                                        creates a Groups report that G                                        reflects changes you made to the_4                                        Users report.  D         Do not want to use    <Return> Creates a Groups report basedC         the Users report               on existing groups and grouptH         _______________________________membership.______________________                    ResultA  F                  The upgrade procedure creates the report and asks you8                  whether you want to display the report:  /                  Do you want to view the reporto?                  Enter Y or N, or press Return for the default: E                                                                     Yc  @               4. Specify whether you want to display the report:                                        H  Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-13    t            Creating Upgrade Reportsn  E      ________________________________________________________________f!                       Enter . . .iE      If_you_._._.______________And_the_upgrade_procedure_._._._______r  C      Do not want      N        Does not display the report. BecauselD      to display the            the upgrade procedure saves the file,@      report                    you can display and edit the fileD                                after you exit the upgrade procedure.A                                For report file locations, see theiA                                next section "Where to find reportr&                                files".  D      Want to display  <Return> Displays a prompt that asks you which6      the report                editor you want to use.  @                                Enter LSE, TECO, or TPU, or pressC                                <Return> to use the default EDT. ThedD                                upgrade procedure displays the report8                                in the editor you choose.  E                                When you are finished with the report,_B                                exit the editor to save any changesB                                you made to the report, or quit theA                                editor to exit without saving yourhE      __________________________changes.______________________________o        WHERE TO FIND REPORT FILES C            Report files are stored in the PWRK$LMUPGRADE directory. @            Table 6-1 lists the file names of each report you can-            create with the upgrade procedure.a  E            Table_6-1_Report_File_Names_______________________________f  E            Report_Type________File_Name______________________________   0            Users              PWRK$UPG$USERS.RPT  0            Groups             PWRK$UPG$GROUP.RPT  0            File and Print     PWRK$UPG$SHARE.RPTE            Services___________________________________________________          L      6-14 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports    l      H                                                  Editing Upgrade Reports  H         ________________________________________________________________           Editing Upgrade ReportsB      +         WHEN AND HOW TO EDIT A USERS REPORT B               Table 6-2 describes circumstances in which you mightG               edit the Users report. For each situation, the table alsorG               describes how to edit the report and provides an example.o  H         Table_6-2_Editing_the_Users_Report______________________________  H         When_._._.________Then_._._.________Example_from_Users_Report___  H                                                 (continued on next page)                                                            H  Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-15    3            Editing Upgrade Reports    E      Table_6-2_(Cont.)_Editing_the_Users_Report______________________   E      When_._._.________Then_._._.________Example_from_Users_Report___e  C      A user name       Define a new,     A user named Ken Cardinalet>      on the local      unique user       has an account on theD      server has a      name for the      local server. The CARDINALEC      match on the      account on        account has a match on thePC      primary domain    the local         primary domain controller. D      controller, but   server; to        However, the account on theB      the accounts      do this, type =   primary domain controllerB      are not for the   newname after     is for another user named3      same user         the existing      Cardinale. ?                        name in the       If left unchanged, the A                        appropriate       CARDINALE account on theKB                        section of the    primary domain controller<                        report.           would supersede the  A                                          CARDINALE account on theeD                                          local server. Therefore, anB                                          account for Ken Cardinale?                                          would not exist on the C                                          primary domain controller.R  >                                          To make sure that theB                                          upgrade procedure createsA                                          a new account KCARDINALER>                                          on the primary domain?                                          controller, rename the_A                                          CARDINALE account on thenB                                          local server's user list:  J                                          !OpenVMS users to be added as LAN  7                                          !Manager usersh  B                                          VERRILLI        !VERRILLI@                                          JORDAN          !JORDANF                                          HICKSCOURANT    !HICKSCOURANT  O                                          CARDINALE = KCARDINALE      !CARDINALEu  D                                          BRODMERKLE      !BRODMERKLEA                                          BRISTOW         !BRISTOWI?                                          BJORK           !BJORK @                                          BERUBE          !BERUBEB                                          BELLUSCI        !BELLUSCIC                                          BELLIVEAU       !BELLIVEAUa  L      6-16 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade ReportsE                                              (continued on next page)  .         H                                                  Editing Upgrade Reports    H         Table_6-2_(Cont.)_Editing_the_Users_Report______________________  H         When_._._.________Then_._._.________Example_from_Users_Report___  E         You want to       Type an           To prevent the upgrade ofcG         prevent the       exclamation       HICKSCOURANT and BELLIVEAU,eH         upgrade of        point (!) in      edit the appropriate sectionD         existing          front of each     of the report so that it<         OpenVMS           user that you     looks like this:M         users who are     do not want       !OpenVMS users to be added as LANn#         upgraded by       upgraded.):         default                             !Manager users  F                                              VERRILLI        !VERRILLID                                              JORDAN          !JORDANJ                                             !HICKSCOURANT    !HICKSCOURANT  G                                              CARDINALE       !CARDINALEsH                                              BRODMERKLE      !BRODMERKLEE                                              BRISTOW         !BRISTOW C                                              BJORK           !BJORKnD                                              BERUBE          !BERUBEF                                              BELLUSCI        !BELLUSCIG                                             !BELLIVEAU       !BELLIVEAUi  H                                                 (continued on next page)                                      H  Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-17 p  d            Editing Upgrade Reports    E      Table_6-2_(Cont.)_Editing_the_Users_Report______________________d  E      When_._._.________Then_._._.________Example_from_Users_Report___   A      You want to       Remove the        To ensure the upgrade of E      ensure the        exclamation       SYSTEST and SYSTEM, edit the C      upgrade of        point (!)         appropriate section of theaE      existing users    from in front     report so that it looks likeg.      who are not       of each user      this:J      upgraded by       that you want     !OpenVMS users NOT to be added as       default           upgraded.  ;                                          !LAN Manager usersi  L                                          !VPM$SERVER     !VPM$SERVER DEFAULT  B                                          !SYSTEST_CLIG   !SYSTEST--                                          UETP B                                           SYSTEST        !SYSTEST--                                          UETPeH                                           SYSTEM         !SYSTEM MANAGER  C                                          !PWRK$GUEST     !PATHWORKS.C                                          !PWRK$DEFAULT   !PATHWORKS_N                                          !PHONE$SERVER   !PHONE$SERVER DEFAULT  B                                          !PCSA$RMI       !PCSA$RMI>                                          !PCFS$ACCOUNT   !PCFSL                                          !NML$SERVER     !NML$SERVER DEFAULT  N                                          !MIRRO$SERVER   !MIRRO$SERVER DEFAULT  M                                          !MAIL$SERVER    !MAIL$SERVER DEFAULT   G                                          !FIELD          !FIELD SERVICEo  E      ____________________________________!DEFAULT________!___________                 L      6-18 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports    n      H                                                  Editing Upgrade Reports    ,         WHEN AND HOW TO EDIT A GROUPS REPORTG               Table 6-3 describes circumstances in which you might edit C               the Groups report. For each situation, the table also G               describes how to edit the report and provides an example.                  Note  A               If you want to use the Users report as input to the D               creation of the Groups report, make sure that you haveE               finished editing the Users report before you create and %               edit the Groups report.   H         Table_6-3_Editing_the_Groups_Report_____________________________  H         When_._._.________Then_._._.________Example_from_Groups_Report__  C         You want to       Rename the        To merge the members of F         merge the         group on the      the group EDITING (BERUBE,G         members of        local server      HICKSCOURANT, and VERRILLI) D         a group on        so that it        on the local server withD         the local         has the same      the members of the groupC         server with       name as the       EDITORS (BRODMERKLE and B         the members of    group on the      JORDAN) on the primaryE         a group on the    primary domain    domain controller, renametD         primary domain    controller; to    the group EDITING on theG         controller, but   do this type, =   local server's groups list:dS         the groups do     newname after     EDITING = EDITORS   !PCFS Group EDITING 0         not have the      the existing      NoteD         same name         name in the       If you do not rename theF                           appropriate       group EDITING, the upgradeE                           section of the    procedure creates a group A                           report.           on the primary domainU  F                                             controller called EDITING,C                                             of which only the users_E                                             BERUBE, HICKSCOURANT, and.A                                             VERRILLI are members.a  H                                                 (continued on next page)            H  Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-19                 Editing Upgrade Reports    E      Table_6-3_(Cont.)_Editing_the_Groups_Report_____________________t  E      When_._._.________Then_._._.________Example_from_Groups_Report__i  B      You want to       Type an           To prevent the upgrade ofC      prevent the       exclamation       the OpenVMS group EDITING,lE      upgrade of an     point (!)  in     edit the appropriate sectionnA      existing group    front of the      of the report so that itr9      or resource       group (and its    looks like this:eJ      identifier that   members) that     !EDITING      !PCFS Group EDITING&      is upgraded by    you do not want1      default           upgraded.         !USERS=(n  7                                          !       BERUBE =                                          !       HICKSCOURANT_9                                          !       VERRILLI +                                          !).  -                                          Note B                                          If you do not upgrade allE                                          existing groups and resource B                                          identifiers, the security=                                          phase of the upgradeOE      ____________________________________procedure_may_be_incomplete.     :      WHEN AND HOW TO EDIT A FILE AND PRINT SERVICES REPORTD            Table 6-4 describes circumstances in which you might editB            the File and Print Services report. For each situation,>            the table also describes how to edit the report and            provides an example.                             L      6-20 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports y  e      H                                                  Editing Upgrade Reports    H         Table_6-4_Editing_the_File_and_Print_Services_Report____________  G                                             Example from File and Print H         When_._._.________Then_._._.________Services_Report_____________  E         You want to       Type an           To prevent the upgrade of F         prevent the       exclamation       the file service PCCOMMON,H         upgrade of        point (!)         edit the appropriate sectionD         a service,        in front of       of the report so that it<         account, or       the service,      looks like this:N         queue to a LAN    OpenVMS           !Accessible from the basic and the%         Manager share     account, or @                           queue that you    !enhanced redirector%                           do not wante4                           upgraded.          WINWORD5                                             !PCCOMMON 2                                              EXCEL2                                              ASCII  A         You want to       Define a new,     To make sure that theeA         change the name   unique name for   OpenVMS printer queue E         of a service,     the service,      POSTSCRIPT is upgraded toVG         account, or       account, or       the LAN Manager print share F         queue so that     queue; to do      POST, edit the appropriateD         it can be         this, type =      section of the report soD         used with both    newname after     that it looks like this:Q         redirectors       the existing      !Accessible from the basic redirector %                           name in ther8                           appropriate       WORD_PERFECT7                           section of the    PUBLIC_TEXTd7                           report.           PUBLIC_DATAS=                                             POSTSCRIPT = POSTtH         ____________________________________LOTUS_123___________________      H         ________________________________________________________________           Next Steps            H  Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports 6-21 o  x            Next Stepst          WHAT TO DO NEXT>            To perform the upgrade procedure itself, proceed to            Chapter 7.                                                                                     L      6-22 Creating PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade Reports r  r                  H                                                                        7H         ________________________________________________________________  H                   Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)      H               This chapter describes how to use the upgrade procedure toE               upgrade users, groups, services, and access rights from_F               a previous version of PATHWORKS for OpenVMS to PATHWORKS.               V5.0C for OpenVMS (LAN Manager).  H               The upgrade procedure is a character-oriented, menu-driven&               utility that lets users:  4               o  Access upgraded services and files.  B               o  Take advantage of the V5 server's new LAN Manager                  features.  >               This chapter consists of the following sections:  !               o  Before You Begin   ,               o  About Upgrading Your Server  ;               o  Performing a Complete Upgrade with Reportsl  9               o  Performing a Custom Upgrade with Reports   >               o  Performing a Complete Upgrade Without Reports  <               o  Performing a Custom Upgrade Without Reports  +               o  Upgrading OpenVMS Securityn  1               o  Performing a UAS Merge Procedure   (               o  Upgrading Disk Services                 o  Next Steps   H               Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-1 i  d            Before You Begin   E      ________________________________________________________________         Before You Begino            HAVE YOU DONE? A            Before you continue, make sure that you have evaluated B            whether you need to create upgrade reports. If so, makeE            sure that you have created and edited the upgrade reports,d%            as described in Chapter 6.     E      ________________________________________________________________e         About Upgrading Your Server            WHY UPGRADE YOUR SERVER?sA            The LAN Manager server supports the following featuresiE            that previous versions of the PATHWORKS for OpenVMS server             do not:  B            o  Domains - Subdivisions of servers and clients on the               network that:R  B               -  Let each user work with a specific set of servers!                  and other users.P  >               -  Provide a simple way to control access to the                  network.   4               -  Make network administration easier.  D            o  Logon validation - the ability to let a user log on toC               a network domain once, then connect to shared networkTC               resources without specifying a user name and passwordw               again   @            o  User-level security - security based on a password:               associated with the LAN Manager user account  A            o  Share-level security - security based on a password_:               associated with each shared network resource  ?      7-2 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)            H                                              About Upgrading Your Server    A               o  Hidden servers - servers that are protected fromrE                  intruders, because they are omitted from any list ofT/                  servers that users can display_  E               o  Remote server management - the ability to manage thesE                  server remotely with either a window or command-line E                  interface from an OpenVMS V5 server, an OS/2 server, F                  an OS/2 client, or a DOS client on which the Enhanced(                  Redirector is installed  C               At the file access level, the V5 server also lets you E               integrate the security model of the LAN Manager network H               operating system with that of the host OpenVMS system. YouG               can specify whether you want host-based security enforcednD               for all files or only for those files not created with               PATHWORKS.  "               For more information  F               For detailed information about these and other features,@               see the PATHWORKS for OpenVMS (LAN Manager) Server$               Administrator's Guide.  '         WHAT THE UPGRADE PROCEDURE DOES 7               The upgrade procedure does the following:   H               1. The procedure upgrades users and groups by using one of                  the following:t  1                  o  Data file reports you specify   D                  o  Default criteria based on the existing PATHWORKSB                     V4.x for OpenVMS users and groups database, asC                     described in About Upgrade Reports in Chapter 6u  B               2. If you specified a primary domain controller whenA                  you entered the upgrade procedure, the procedure F                  adds the upgraded user accounts to the primary domain                  controller.  E                  Because the new user accounts created on the primary H                  domain controller do not include passwords, you must do&                  one of the following:  F                  o  Use one of the available administrative interfacesD                     to modify the user accounts so that they include                     passwords.  H               Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-3 R                About Upgrading Your Server    E               o  Run the LAN Manager server in backward compatibility B                  mode until all client users have logged on to theD                  upgraded server. As client users log on, their userA                  accounts are modified automatically so that they ,                  include the passwords used.  "               For more information  E               For detailed information about available administrative ;               interfaces and running the server in backwardSD               compatibility mode, see the PATHWORKS for OpenVMS (LAN4               Manager) Server Administrator's Guide.  >            3. For each PATHWORKS group, OpenVMS UIC group, andB               OpenVMS resource ID that is upgraded, the procedure:  ;               o  Creates a corresponding LAN Manager group..  D               o  Adds users to the group based on the previous group                  membership.  B               o  If you specified a primary domain controller when>                  you entered the upgrade procedure, adds a LAN@                  Manager group to the primary domain controller.  B            4. For each file and print service you want to upgrade,D               the procedure creates a corresponding LAN Manager file               or print share.n  >            5. The procedure upgrades existing PATHWORKS accessC               permissions (assigned to all system, application, and @               common file shares) from an OpenVMS security modelC               to a LAN Manager security model. For all directories, C               subdirectories, and files, the upgrade procedure maps ?               OpenVMS permissions to LAN Manager permissions as E               closely as possible so that user access is not changed.   D            6. If you instruct it to do so, the procedure deletes all9               temporary files created during the upgrade.             ?      7-4 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)            H                                              About Upgrading Your Server             TYPES OF UPGRADES E               If you are upgrading the OpenVMS server from a previousnF               version, you must perform either a complete upgrade or a               custom upgrade.M  E               This table describes the differences between a complete +               upgrade and a custom upgrade:R  H         ________________________________________________________________H         With_a_complete_upgrade_._._.___With_a_custom_upgrade_._._._____  E         Once you start, you must        You complete different phasesaG         complete it, or press <Ctrl/Y>  of the upgrade procedure one ateG         to stop it, then start again.   a time. You may want to perform D         When you press <Ctrl/Y>, you    a custom upgrade if your LAND         exit the upgrade procedure,     is large or has a customizedE         and the OpenVMS system prompt   configuration, and you do not G         ($) is displayed.               have time to perform a complete$0                                         upgrade.  G         You need to choose only one     You must choose several upgrade A         upgrade procedure menu option.  procedure menu options toYB                                         complete all phases of the:                                         upgrade procedure.  >         You respond to all prompts      You respond to promptsE         before the upgrade procedure    throughout the actual upgradeD2         actually starts so that you     procedure.#         can let the upgrade proceedVH         unattended._____________________________________________________                 Note  G               With a custom upgrade, you can also specify multiple disk F               device names that contain file shares for which you want"               to upgrade security.  C               You can perform either a complete upgrade or a customA?               upgrade with or without upgrade reports. However, H               regardless of which type of upgrade you choose to perform,E               Digital recommends that you use upgrade reports unless:   G               o  Your LAN's existing user, group, and service databases %                  are extremely small.   H               Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-5 P  E             About Upgrading Your Server    A            o  No conditions exist that would prevent a smooth and.C               complete upgrade, as described in Chapter 6, Creatinge?               PATHWORKS V5.0C for OpenVMS (LAN Manager) Upgrade                Reports.  B            Therefore, before you can upgrade your server, you mustD            decide which of the following upgrade procedures you want            to perform:  +            o  Complete upgrade with reportso  )            o  Custom upgrade with reports_  .            o  Complete upgrade without reports  ,            o  Custom upgrade without reports  B            These upgrade procedures are described in the following$            sections of this chapter.  E      ________________________________________________________________   /      Performing a Complete Upgrade with ReportsL  3      HOW TO PERFORM A COMPLETE UPGRADE WITH REPORTSe?            To perform a complete upgrade using upgrade reports:h  C            1. From the upgrade procedure Main menu, choose CompleteT               Upgrade.  ?            2. Press <Return> at the following prompt to use the                default Y:  G               Do you want to use reports as input to the upgrade phaseso?               Enter Y or N, or press Return to use the default:oG                                                                       Ye  A            3. In response to the following prompt, specify a data A               file for user upgrade, or press <Return> to use thee)               default PWRK$UPG$USERS.RPT:   C      Specify the Users report file for the user upgrade on the next 8      line [PWRK$LMUPGRADE:PWRK$UPG$USERS.RPT is default]    ?      7-6 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)d i         H                               Performing a Complete Upgrade with Reports                      Result   8                  The upgrade procedure upgrades existingG                  PATHWORKS/OpenVMS users to LAN Manager users according 2                  to the information in the report.  D               4. In response to the following prompt, specify a dataE                  file for group upgrade, or press <Return> to use the ,                  default PWRK$UPG$GROUP.RPT:  C         Specify the Groups report for the group upgrade on the next_;         line [PWRK$LMUPGRADE:PWRK$UPG$GROUP.RPT is default]o                    ResultY  G                  The upgrade procedure upgrades groups according to thet+                  information in the report.E  D               5. In response to the following prompt, specify a dataC                  file for file and print services upgrade, or pressh@                  <Return> to use the default PWRK$UPG$SHARE.RPT:  B         Specify the File and Print Services report for the serviceO         upgrade on the next line [PWRK$LMUPGRADE:PWRK$UPG$SHARE.RPT is default]                     Result   G                  The upgrade procedure upgrades existing file and print C                  services, OpenVMS user accounts, and OpenVMS print F                  queues to LAN Manager file and print shares according2                  to the information in the report.  1               6. Respond to the following prompt:t  A                  Do you want to minimize output to the status boxsK                  This may speed up the time it takes to upgrade the system.uB                  Enter Y or N, or press Return to use the default:J                                                                          N              H               Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-7 s  r      /      Performing a Complete Upgrade with Reports   E               _______________________________________________________ E               If_you_._._.__________Enter_._._.______________________   ,               Do not want to        <Return>               minimize theC               number of messages    This may slow down the upgrade. B               displayed in the      However, if the upgrade fails,B               status box during     more troubleshooting clues are@               upgrade               displayed in the status box.  %               Want to minimize the  Y_                number of messagesB               displayed in the      This may speed up the upgrade.B               status box during     However, if the upgrade fails,C               upgrade               fewer troubleshooting clues area@                                     displayed in the status box.  ?                                     In either case, choose Viewi?                                     Log File from the Main menu <                                     to display more detailed?                                     information. For still morerB                                     detailed explanations of theseA                                     log file messages, along with @                                     troubleshooting suggestions,?                                     see the appropriate chapteroA                                     in PATHWORKS for OpenVMS (LANhE               ______________________Manager)_Server_Messages.________s      E      ________________________________________________________________   -      Performing a Custom Upgrade with Reportsr    1      HOW TO PERFORM A CUSTOM UPGRADE WITH REPORTSd=            To perform a custom upgrade using upgrade reports:   A            1. From the upgrade procedure Main menu, choose Custom                Upgrade.  D            2. From the Custom Upgrade Options menu, choose Users and               Groups.       ?      7-8 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)  O  P      H                                 Performing a Custom Upgrade with Reports    1               3. Enter Y at the following prompt:   F         Do you want to use a Users report as input to the user upgrade6         Enter Y or N, or press Return for the default:F                                                                      N  D               4. In response to the following prompt, specify a dataD                  file for user upgrade, or press <Return> to use the,                  default PWRK$UPG$USERS.RPT:  F         Specify the Users report file for the user upgrade on the next;         line [PWRK$LMUPGRADE:PWRK$UPG$USERS.RPT is default]                     Result   8                  The upgrade procedure upgrades existingG                  PATHWORKS/OpenVMS users to LAN Manager users according 2                  to the information in the report.  D               5. In response to the following prompt, specify a dataD                  file for group upgrade or press <Return> to use the,                  default PWRK$UPG$GROUP.RPT:  C         Specify the Groups report for the group upgrade on the nexta;         line [PWRK$LMUPGRADE:PWRK$UPG$GROUP.RPT is default]A                    ResultW  G                  The upgrade procedure upgrades groups according to thep+                  information in the report.-                              H               Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-9           -      Performing a Custom Upgrade with ReportsM    B            6. Press <Return> to display the Custom Upgrade OptionsB               menu, choose File and Print Services, and enter Y at#               the following prompt:u  :               Do you want to use a File and Print Services4               report as input to the service upgradeD               Enter Y or N, or press Return for the default:       N  A            7. In response to the following prompt, specify a datat@               file for file and print services upgrade, or press=               <Return> to use the default PWRK$UPG$SHARE.RPT:   ?      Specify the File and Print Services report for the service L      upgrade on the next line [PWRK$LMUPGRADE:PWRK$UPG$SHARE.RPT is default]                 Result  D               The upgrade procedure upgrades existing file and print@               services, OpenVMS user accounts, and OpenVMS printC               queues to LAN Manager file and print shares according /               to the information in the report.o  B            8. Press <Return> to display the Custom Upgrade Options'               menu and choose Security.t  .            9. Respond to the following prompt:  >               Do you want to minimize output to the status boxH               This may speed up the time it takes to upgrade the system.?               Enter Y or N, or press Return to use the default:iG                                                                       N                             @      7-10 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)           H                                 Performing a Custom Upgrade with Reports  H                  _______________________________________________________H                  If_you_._._.__________Enter_._._.______________________  /                  Do not want to        <Return>a                  minimize the F                  number of messages    This may slow down the upgrade.E                  displayed in the      However, if the upgrade fails, E                  status box during     more troubleshooting clues areoC                  upgrade               displayed in the status box.u  (                  Want to minimize the  Y#                  number of messages E                  displayed in the      This may speed up the upgrade.gE                  status box during     However, if the upgrade fails, F                  upgrade               fewer troubleshooting clues areC                                        displayed in the status box.   B                                        In either case, choose ViewB                                        Log File from the Main menu?                                        to display more detailed B                                        information. For still moreE                                        detailed explanations of these D                                        log file messages, along withC                                        troubleshooting suggestions,lB                                        see the appropriate chapterD                                        in PATHWORKS for OpenVMS (LANH                  ______________________Manager)_Server_Messages.________  1               10.Respond to the following prompt:   <                  Do you want to create a list of devices for&                  the security upgrade.F                  Enter Y or N, or press Return to use the default:   N  C                  You may want to create a list of disk devices thatMB                  contain file shares for which you want to upgradeC                  security. For example, if your server is part of asF                  VMScluster, you can specify the names of disk devicesC                  located on any VMScluster member that you use as a "                  PATHWORKS server.            H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-11           -      Performing a Custom Upgrade with Reports                    Note  @               To save time, you can start the Upgrade utility inA               multiple terminal sessions and perform simultaneoustA               Security upgrades. For example, if you have 40 diskhC               devices in a VMScluster that are part of the securityr@               upgrade, you can start the Upgrade utility in fourD               terminal sessions and create a list of 10 disk devices@               in each. This way, the security upgrade takes one-=               fourth the time it would if you did it with onec               terminal session.   E               _______________________________________________________ E               If_you_._._.____________________Enter_._._.____________3  /               Want to create a list of disk   Y                device names  6               Do not want to create a list    <Return>E               of_disk_devices_names__________________________________   A            11.If you chose to create a list of disk device names:   B               a. In response to the following prompt, enter a file@                  name for the list, or press <Return> to use the/                  default PWRK$UPG$SECURITY.DAT:a  <      Specify a file specification for the file being createdF      [PWRK$LMROOT:[LANMAN.DATAFILES]PWRK$UPG$SECURITY.DAT is default]:  @               b. In response to the following prompt, enter LSE,C                  TECO, or TPU, or press <Return> to use the defaultd                  EDT:   F                  Select an editor (LSE TECO TPU or EDT) default [EDT]:                    Resultg  D                  The upgrade procedure displays the following in the#                  editor you choose:   D      !+++++++++++ Security Upgrade Device Data File ++++++++++++++++9      !Please enter a list of devices separated by spaces.N9      !Enter the device names as they appear on the systemr?      !no logicals and no colons ( For example:  DKA100 DKA200 )t  @      7-12 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) a         H                                 Performing a Custom Upgrade with Reports    D                  c. At the bottom of the file, enter the disk deviceE                     names you want to specify, and separate them witheC                     spaces. Do not specify logical names or included                     colons.u                       Exampleg  G         !+++++++++++ Security Upgrade Device Data File ++++++++++++++++i<         !Please enter a list of devices separated by spaces.<         !Enter the device names as they appear on the systemB         !no logicals and no colons ( For example:  DKA100 DKA200 )  #         MKA200 MKA300 MKA400 MKA500          MKA600 MAK700O  G                  d. Exit the editor to save the changes you made to the ;                     file and to begin the security upgrade.   F               12.When the security upgrade is complete, press <Return>C                  to display the Custom Upgrade Options menu and, ifmC                  you have completed all other phases of the upgradeh3                  procedure, choose Cleanup Upgrade.                     Caution  B                  If you have not completed all other phases of theD                  upgrade procedure, performing the cleanup phase mayG                  remove temporary files needed to complete the upgrade.o  E               13.In response to the following prompt, specify whethertF                  you want to delete temporary files created during the;                  upgrade (for example, PWRK$UPG$USERS.DAT):Y  =                  Do you want to delete ALL upgrade data filesp2                  in PWRK$LMROOT:[LANMAN.DATAFILES]B                  Enter Y or N, or press Return for the default:  Y                  H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-13           2      Performing a Complete Upgrade Without Reports  E      ________________________________________________________________o  2      Performing a Complete Upgrade Without Reports      6      HOW TO PERFORM A COMPLETE UPGRADE WITHOUT REPORTS>            To perform a complete upgrade without using upgrade            reports:   C            1. From the upgrade procedure Main menu, choose Completeo               Upgrade.  .            2. Enter N at the following prompt:  G               Do you want to use reports as input to the upgrade phases_B               Enter Y or N, or press Return to use the default:  Y  .            3. Respond to the following prompt:  4               Do you want to upgrade users to shares?               Enter Y or N, or press Return for the default:  Yt  E               _______________________________________________________AE               If_you_._._.________Enter_._._.________________________   *               Want to create      <Return>               a corresponding                share for each               OpenVMS/LANe               Manager user               account on the               server  #               Do not want         N                to create a &               corresponding       NoteC               file share for      If you do not create a file share >               each OpenVMS/LAN    for each OpenVMS/LAN ManagerB               Manager user        account on the server, users canA               account on the      no longer access their personal E               server______________OpenVMS_logon_directories._________         @      7-14 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)           H                            Performing a Complete Upgrade Without Reports    1               4. Respond to the following prompt:   <                  Do you want to upgrade OpenVMS print queues,                  to LAN Manager print sharesB                  Enter Y or N, or press Return for the default:  N  H                  _______________________________________________________H                  If_you_._._.________Enter_._._.________________________  &                  Want to create      Y                   a corresponding"                  LAN Manager print                  share for eache                  OpenVMS print                  queue  -                  Do not want to      <Return>l                   create any more)                  print shares        NotenG                                      If you do not create a print sharerB                                      for each OpenVMS print queue,H                                      users can no longer access existingH                  ____________________printer_services.__________________  1               5. Respond to the following prompt:e  8         Do you want to minimize output to the status boxB         This may speed up the time it takes to upgrade the system.<         Enter Y or N, or press Return to use the default:  N                                H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-15 d  i      2      Performing a Complete Upgrade Without Reports  E               _______________________________________________________eE               If_you_._._.__________Enter_._._.______________________o  ,               Do not want to        <Return>               minimize theC               number of messages    This may slow down the upgrade. B               displayed in the      However, if the upgrade fails,B               status box during     more troubleshooting clues are@               upgrade               displayed in the status box.  %               Want to minimize the  Y                 number of messagesB               displayed in the      This may speed up the upgrade.B               status box during     However, if the upgrade fails,C               upgrade               fewer troubleshooting clues areo@                                     displayed in the status box.  ?                                     In either case, choose Viewt?                                     Log File from the Main menu$<                                     to display more detailed?                                     information. For still morenB                                     detailed explanations of theseA                                     log file messages, along witha@                                     troubleshooting suggestions,?                                     see the appropriate chapter A                                     in PATHWORKS for OpenVMS (LAN E               ______________________Manager)_Server_Messages.________   <            6. If your local server is not the primary domain:               controller, respond to the following prompt:  -               Ignore same name user conflicts ?               Enter Y or N, or press Return for the default:  Y   >               A same-name conflict occurs when a PATHWORKS forE               OpenVMS user name on the local server matches exactly afE               LAN Manager user name on the primary domain controller.                   @      7-16 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) s  s      H                            Performing a Complete Upgrade Without Reports        H         ________________________________________________________________         If          Enter . . . H         you_._._.______________And_the_upgrade_procedure_._._.__________           Want to     <Return>H         ignore                 _________________________________________H         same-name              For_._._._________Does_this_._._.________  D         conflicts              Matching          Lets the account on  C                                accounts          the primary domain E                                                  controller supersede E                                                  the account with the G                                                  same name on the local F                                                  server. The user mustF                                                  then use the passwordB                                                  to the account onC                                                  the primary domainh<                                                  controller.  H                                Accounts on the   Displays the User MergeF                                local server      screen to resolve the@                                that have names   name conflicts.)                                similar toU-                                (but not exactr*                                matches of).                                accounts on the-                                primary domain )                                controllern  A                                All other         Creates matchingaH                                accounts on       accounts on the primaryH                                the_local_server__domain_controller._____                    H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-17 p  t      2      Performing a Complete Upgrade Without Reports  E      ________________________________________________________________       If          Enter . . .E      you_._._.______________And_the_upgrade_procedure_._._.__________         Want to     NE      resolve                _________________________________________RE      same-name              For_._._._________Does_this_._._.________   E      conflicts              Accounts on the   Displays the User Merge   C                             local server      screen to resolve thea=                             that have names   name conflicts.a)                             similar to or ,                             exact matches of+                             accounts on thec*                             primary domain&                             controller  >                             All other         Creates matchingE                             accounts on       accounts on the primaryUE                             the_local_server__domain_controller._____   E      ________________________________________________________________   C               As shown in the following figure, the box on the left A               of the User Merge screen displays an account on theeB               local server that has a same-name conflict (only oneC               account is displayed at a time). The box on the rightoA               lists the accounts on the primary domain controller 7               that have the same or similar user names.   C               Select the user name on the primary domain controllern@               that you want to associate with the account on theB               local server, and press <Return>. The account on theE               primary domain controller supersedes the account on the @               local server. (The user must then use the password?               associated with the account on the primary domaincD               controller.) Repeat this action for each local account               displayed.  <            7. If your local server is not the primary domain:               controller, respond to the following prompt:  .               Ignore same name group conflicts>               Enter Y or N, or press Return for the default: Y  @      7-18 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) r         H                            Performing a Complete Upgrade Without Reports    A                  A same-name conflict occurs when a PATHWORKS for C                  OpenVMS UIC group name on the local server matcheshG                  exactly a LAN Manager group name on the primary domainn                  controller.                                                                                  H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-19 C  r      2      Performing a Complete Upgrade Without Reports  E      _________________________________________________________________      If          Enter . . .E      you_._._.______________And_the_upgrade_procedure_._._.__________.        Want to     <Return> E      ignore                 _________________________________________mE      same-name              For_._._._________Does_this_._._.________   @      conflicts              Matching groups   Merges the members  A                                               of the group on thetC                                               local server with thehB                                               members of the groupA                                               of the same name on @                                               the primary domain9                                               controller.g  @                             Groups on the     Displays the GroupE                             local server      Merge screen to resolve A                             that have names   the name conflicts. &                             similar to*                             (but not exact'                             matches of) )                             groups on the *                             primary domain&                             controller  @                             All other groups  Creates a matchingB                             on the local      group on the primaryE                             server____________domain_controller._____t                                @      7-20 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) _  _      H                            Performing a Complete Upgrade Without Reports               Want to     N H         resolve                _________________________________________H         same-name              For_._._._________Does_this_._._.________  C         conflicts              Groups on the     Displays the Groupd  H                                local server      Merge screen to resolveD                                that have names   the name conflicts.,                                similar to or/                                exact matches ofl,                                groups on the-                                primary domain )                                controller5  H                                All other groups  Creates matching groupsF                                on the local      on the primary domainH                                server____________controller.____________  H         ________________________________________________________________  F                  As shown in the following figure, the box on the leftH                  of the Group Merge screen displays a group on the localH                  server that has a same-name conflict (only one group isE                  displayed at a time). The box on the right lists the F                  groups on the primary domain controller that have the-                  same or similar group names.   G                  Select the group name on the primary domain controlleryG                  that you want to associate with the group on the localtD                  server, and press <Return>. Members of the group onF                  the local server are made members of the group on theG                  primary domain controller whose name you chose. Repeato<                  this action for each local group displayed.                 Note  E               After you complete the steps described in this section,sC               the upgrade procedure continues through its differentaD               phases, including the file and print services upgrade,G               the security upgrade, and the deletion of temporary files )               created during the upgrade.r      H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-21 l         0      Performing a Custom Upgrade Without Reports  E      ________________________________________________________________   0      Performing a Custom Upgrade Without Reports      4      HOW TO PERFORM A CUSTOM UPGRADE WITHOUT REPORTSE            To perform a custom upgrade without using upgrade reports:!  A            1. From the upgrade procedure Main menu, choose Custom                Upgrade.  D            2. From the Custom Upgrade Options menu, choose Users and               Groups.1  ?            3. Press <Return> at the following prompt to use the                default N:  C      Do you want to use a Users report as input to the user upgrade 6      Enter Y or N, or press Return for the default:  N                 Result  =               The upgrade procedure creates a data file named E               PWRK$UPG$USERS.DAT that lists the users to be upgraded.o  .            4. Respond to the following prompt:  D      Do you want to write all OpenVMS users to the user upgrade list6      Enter Y or N, or press Return for the default:  N  E      ________________________________________________________________ #                         Enter . . . E      If_._._.____________________And_the_upgrade_procedure_._._._____0  ?      You do not want    <Return> Adds a user to the list if the A      to add all                  resource identifier PCFS$USER isyB      OpenVMS users               associated with the user account;D      to the list                 the user is a member of an existingD                                  PATHWORKS group; or the user's homeE                                  directory contains at least one file E                                  with a DOS access control list entrydD                                  (ACE), indicating that the file wasC                                  created from a client workstation.d  C      You want to add    Y        Overrides the default criteria forlD      all OpenVMS users           user upgrade listed above, and addsE      to_the_list_________________all_OpenVMS_users_to_the_list.______,  @      7-22 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) g  e      H                              Performing a Custom Upgrade Without Reports    1               5. Respond to the following prompt:   :                  Do you want to view the upgrade user listB                  Enter Y or N, or press Return for the default:  N  H         ________________________________________________________________#                         Enter . . .mH         If_you_._._._______________And_the_upgrade_procedure_._._.______  H         Want to         Y          Displays a prompt that asks you which:         display the                editor you want to use.         listD                                    Enter LSE, TECO, or TPU, or pressG                                    <Return> to use the default EDT. TheeH                                    upgrade procedure displays the report<                                    in the editor you choose.  A                                    When you are finished with thetF                                    report, exit the editor to save anyE                                    changes you made to the data file,_E                                    or quit the editor to exit without_7                                    saving your changes.   =         Do not want to  <Return>   Does not display the list.          display the H         list____________________________________________________________  ?               6. If your local server is not the primary domain =                  controller, respond to the following prompt:a  0                  Ignore same name user conflictsB                  Enter Y or N, or press Return for the default:  Y  A                  A same-name conflict occurs when a PATHWORKS for H                  OpenVMS user name on the local server matches exactly aH                  LAN Manager user name on the primary domain controller.                  H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-23    r      0      Performing a Custom Upgrade Without Reports        E      ________________________________________________________________p      If          Enter . . .E      you_._._.______________And_the_upgrade_procedure_._._.__________         Want to     <Return>fE      ignore                 __________________________________________E      same-name              For_._._._________Does_this_._._._________  A      conflicts              Matching          Lets the account on   @                             accounts          the primary domainB                                               controller supersedeB                                               the account with theD                                               same name on the localC                                               server. The user musthC                                               then use the passwordu?                                               to the account ons@                                               the primary domain9                                               controller.w  E                             Accounts on the   Displays the User Merge C                             local server      screen to resolve the =                             that have names   name conflicts. &                             similar to*                             (but not exact'                             matches of)o+                             accounts on the *                             primary domain&                             controller  >                             All other         Creates matchingE                             accounts on       accounts on the primary E                             the_local_server__domain_controller._____                     @      7-24 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) r         H                              Performing a Custom Upgrade Without Reports  H         ________________________________________________________________         If          Enter . . . H         you_._._.______________And_the_upgrade_procedure_._._.__________           Want to     N,H         resolve                _________________________________________H         same-name              For_._._._________Does_this_._._.________  H         conflicts              Accounts on the   Displays the User Merge  F                                local server      screen to resolve the@                                that have names   name conflicts.,                                similar to or/                                exact matches ofe.                                accounts on the-                                primary domaina)                                controllerl  A                                All other         Creates matchingpH                                accounts on       accounts on the primaryH                                the_local_server__domain_controller._____  H         ________________________________________________________________  F                  As shown in the following figure, the box on the leftD                  of the User Merge screen displays an account on theE                  local server that has a same-name conflict (only onecF                  account is displayed at a time). The box on the rightD                  lists the accounts on the primary domain controller:                  that have the same or similar user names.  F                  Select the user name on the primary domain controllerC                  that you want to associate with the account on the E                  local server, and press <Return>. The account on the_H                  primary domain controller supersedes the account on theC                  local server. (The user must then use the password>B                  associated with the account on the primary domainG                  controller.) Repeat this action for each local account_                  displayed.   ?               7. If your local server is not the primary domain =                  controller, respond to the following prompt:   1                  Ignore same name group conflictseC                  Enter Y or N, or press Return for the default:   Yw  H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-25 a         0      Performing a Custom Upgrade Without Reports    >               A same-name conflict occurs when a PATHWORKS for@               OpenVMS UIC group name on the local server matchesD               exactly a LAN Manager group name on the primary domain               controller.                                                                                   @      7-26 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)           H                              Performing a Custom Upgrade Without Reports  H         ________________________________________________________________         If          Enter . . .(H         you_._._.______________And_the_upgrade_procedure_._._.__________           Want to     <Return>H         ignore                 _________________________________________H         same-name              For_._._._________Does_this_._._.________  C         conflicts              Matching groups   Merges the memberst  D                                                  of the group on theF                                                  local server with theE                                                  members of the group D                                                  of the same name onC                                                  the primary domain <                                                  controller.  C                                Groups on the     Displays the Group_H                                local server      Merge screen to resolveD                                that have names   the name conflicts.)                                similar to -                                (but not exact *                                matches of),                                groups on the-                                primary domain )                                controller   C                                All other groups  Creates a matchingaE                                on the local      group on the primary H                                server____________domain_controller._____                                H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-27           0      Performing a Custom Upgrade Without Reports            Want to     NE      resolve                _________________________________________ E      same-name              For_._._._________Does_this_._._.________a  @      conflicts              Groups on the     Displays the Group  E                             local server      Merge screen to resolvehA                             that have names   the name conflicts.v)                             similar to or ,                             exact matches of)                             groups on then*                             primary domain&                             controller  E                             All other groups  Creates matching groupssC                             on the local      on the primary domain E                             server____________controller.____________a  E      ________________________________________________________________a  C               As shown in the following figure, the box on the leftiE               of the Group Merge screen displays a group on the localoE               server that has a same-name conflict (only one group is B               displayed at a time). The box on the right lists theC               groups on the primary domain controller that have the *               same or similar group names.  D               Select the group name on the primary domain controllerD               that you want to associate with the group on the localA               server, and press <Return>. Members of the group onrC               the local server are made members of the group on the D               primary domain controller whose name you chose. Repeat9               this action for each local group displayed.M  B            8. Press <Return> to display the Custom Upgrade Options=               menu, choose File and Print Services, and press_A               <Return> at the following prompt to use the default.               N:  :               Do you want to use a File and Print Services4               report as input to the service upgradeA               Enter Y or N, or press Return for the default:    N_    @      7-28 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) g  p      H                              Performing a Custom Upgrade Without Reports    1               9. Respond to the following prompt:   7                  Do you want to upgrade users to shares D                  Enter Y or N, or press Return for the default:    Y  H                  _______________________________________________________H                  If_you_._._.________Enter_._._.________________________  -                  Want to create      <Return>                    a corresponding                  share for eachr                  PATHWORKS for                  OpenVMS (LANt                  Manager) user                  account on thei                  server   &                  Do not want         N                  to create a)                  corresponding       Note F                  file share for      If you do not create a file shareA                  each OpenVMS/LAN    for each OpenVMS/LAN Manager H                  Manager user        account on the server, users can noF                  account on the      longer access their personal fileH                  server______________services.__________________________  1               10.Respond to the following prompt:                                     H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-29           0      Performing a Custom Upgrade Without Reports    9               Do you want to upgrade OpenVMS print queues_)               to LAN Manager print sharesnA               Enter Y or N, or press Return for the default:    Nl  E               _______________________________________________________ E               If_you_._._.________Enter_._._.________________________r  #               Want to create      Ye               a corresponding                LAN Manager print                share for each               OpenVMS print                queuer  *               Do not want to      <Return>               create any morer&               print shares        NoteD                                   If you do not create a print share?                                   for each OpenVMS print queue,_E                                   users can no longer access existingAE               ____________________printer_services.__________________o  B            11.Press <Return> to display the Custom Upgrade Options(               menu, and choose Security.  .            12.Respond to the following prompt:  5      Do you want to minimize output to the status boxg?      This may speed up the time it takes to upgrade the system. :      Enter Y or N, or press Return to use the default:   N                              @      7-30 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) h  e      H                              Performing a Custom Upgrade Without Reports  H                  _______________________________________________________H                  If_you_._._.__________Enter_._._.______________________  /                  Do not want to        <Return>                   minimize the F                  number of messages    This may slow down the upgrade.E                  displayed in the      However, if the upgrade fails,fE                  status box during     more troubleshooting clues arerC                  upgrade               displayed in the status box.r  (                  Want to minimize the  Y#                  number of messagesgE                  displayed in the      This may speed up the upgrade.PE                  status box during     However, if the upgrade fails,_F                  upgrade               fewer troubleshooting clues areC                                        displayed in the status box.W  B                                        In either case, choose ViewB                                        Log File from the Main menu?                                        to display more detailedtB                                        information. For still moreE                                        detailed explanations of these D                                        log file messages, along withC                                        troubleshooting suggestions,tB                                        see the appropriate chapterD                                        in PATHWORKS for OpenVMS (LANH                  ______________________Manager)_Server_Messages.________  1               13.Respond to the following prompt:M  <                  Do you want to create a list of devices for&                  the security upgrade.F                  Enter Y or N, or press Return to use the default:   N  C                  You may want to create a list of disk devices thataB                  contain file shares for which you want to upgradeC                  security. For example, if your server is part of adF                  VMScluster, you can specify the names of disk devicesC                  located on any VMScluster member that you use as am"                  PATHWORKS server.            H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-31 r  o      0      Performing a Custom Upgrade Without Reports                   Note  @               To save time, you can start the Upgrade utility inA               multiple terminal sessions and perform simultaneousfA               Security upgrades. For example, if you have 40 diskrC               devices in a VMScluster that are part of the security @               upgrade, you can start the Upgrade utility in fourD               terminal sessions and create a list of 10 disk devices@               in each. This way, the security upgrade takes one-=               fourth the time it would if you did it with one                terminal session.l  E               _______________________________________________________iE               If_you_._._.____________________Enter_._._.____________   /               Want to create a list of disk   Y_               device names  6               Do not want to create a list    <Return>E               of_disk_devices_names__________________________________   A            14.If you chose to create a list of disk device names:   B               a. In response to the following prompt, enter a file@                  name for the list, or press <Return> to use the/                  default PWRK$UPG$SECURITY.DAT:f  <      Specify a file specification for the file being createdF      [PWRK$LMROOT:[LANMAN.DATAFILES]PWRK$UPG$SECURITY.DAT is default]:  @               b. In response to the following prompt, enter LSE,C                  TECO, or TPU, or press <Return> to use the default                   EDT:   F                  Select an editor (LSE TECO TPU or EDT) default [EDT]:                    Result   D                  The upgrade procedure displays the following in the#                  editor you choose:n  D      !+++++++++++ Security Upgrade Device Data File ++++++++++++++++9      !Please enter a list of devices separated by spaces._9      !Enter the device names as they appear on the systemn?      !no logicals and no colons ( For example:  DKA100 DKA200 )h  @      7-32 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) s         H                              Performing a Custom Upgrade Without Reports    D                  c. At the bottom of the file, enter the disk deviceE                     names you want to specify, and separate them with C                     spaces. Do not specify logical names or include                      colons.t                       ExampleL  G         !+++++++++++ Security Upgrade Device Data File ++++++++++++++++p<         !Please enter a list of devices separated by spaces.<         !Enter the device names as they appear on the systemB         !no logicals and no colons ( For example:  DKA100 DKA200 )  #         MKA200 MKA300 MKA400 MKA500          MKA600 MKA700_  G                  d. Exit the editor to save the changes you made to the_;                     file and to begin the security upgrade.a  E               15.Press <Return> to display the Custom Upgrade OptionsnH                  menu and, if you have completed all other phases of the;                  upgrade procedure, choose Cleanup Upgrade.                     Caution  B                  If you have not completed all other phases of theD                  upgrade procedure, performing the cleanup phase mayG                  remove temporary files needed to complete the upgrade.   E               16.In response to the following prompt, specify whether F                  you want to delete temporary files created during the;                  upgrade (for example, PWRK$UPG$USERS.DAT):   =                  Do you want to delete ALL upgrade data files 2                  in PWRK$LMROOT:[LANMAN.DATAFILES]C                  Enter Y or N, or press Return for the default:   Ys                    H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-33           (      Performing Additional Upgrade Tasks  E      ________________________________________________________________   (      Performing Additional Upgrade Tasks            WHAT TO DO NEXTD            After you perform a complete upgrade or a custom upgrade,D            you may want to perform the additional upgrade tasks thatC            are described in the remaining sections of this chapter,d            which include:O  (            o  Upgrading OpenVMS Security  .            o  Performing a UAS Merge Procedure  %            o  Upgrading Disk Services_    E      ________________________________________________________________         Upgrading OpenVMS Security_          WHY UPGRADE SECURITY?C            You can use the upgrade procedure to upgrade permissions B            assigned to OpenVMS directories that were not PATHWORKS>            V4.x for OpenVMS file services and, therefore, were@            not upgraded to LAN Manager shares. After you upgradeD            these directories from an OpenVMS security model to a LANE            Manager security model, you must also create a LAN Manager D            share for the directory (also know as a shared directory)-            for upgraded clients to access it.               For more information   E            For information about creating shared directories, see thelE            PATHWORKS for OpenVMS (LAN Manager) Server Administrator's             Guide.               @      7-34 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)    e      H                                               Upgrading OpenVMS Security             HOW TO UPGRADE SECURITY >               To upgrade security for an OpenVMS directory (or7               subdirectory) and the files stored there:s  H               1. From the upgrade procedure Main menu, choose Additional#                  Upgrade Utilities.u                    Result   D                  The Additional Upgrade Utilities menu is displayed.  C               2. From the Additional Upgrade Utilities menu, choose %                  Additional Security.s  E               3. When prompted, enter the path name for the directorytF                  you want to upgrade. The name should be in the format<                  disk:[directory.subdirectory]. For example:  +                  Enter the path to upgrade:e$                   DUA1:[MACK.PUBLIC]                    Resultw  B                  The access permissions on the specified directoryD                  and all the files stored there are upgraded from anH                  OpenVMS security model to a LAN Manager security model.F                  Permissions are mapped as closely as possible so thatE                  user access from a client is the same as user accessi2                  from an OpenVMS terminal session.  H         ________________________________________________________________  (         Performing a UAS Merge Procedure  )         WHAT THE UAS MERGE PROCEDURE DOES E               The User Authentication Subsystem (UAS) merge procedure F               changes your server from a standalone server to a backup1               domain controller or member server.o  D               If you have changed user and group information on yourE               local server since you performed the upgrade procedure,WF               the UAS merge procedure also updates that information on,               the primary domain controller.    H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-35 _         %      Performing a UAS Merge Procedure_                Notet  A            You need to perform a UAS merge procedure only if your =            local server is not going to be the primary domain_            controller.         WHAT IS A UAS MERGE REPORT?B            A UAS Merge report, PWRK$UPG$UAS_SA.RPT, is a data fileB            you can create, edit, and use as input to the UAS merge)            procedure. A UAS Merge report:   E            o  Lists LAN Manager users and groups on the local server. E               For each user and group listed, the report says whether @               there is a match on the primary domain controller.  ?            o  Lists LAN Manager users and groups on the primary                 domain controller.  C            o  Points out conflicts between the local server and theD(               primary domain controller.  ?            o  Lets you change information to correct conflicts.   D            The UAS merge procedure reads the UAS Merge report, notesC            all users and groups on the local server without matchesc>            on the primary domain controller, and creates theseA            users and groups on the primary domain controller. Seey=            Appendix E for a complete sample UAS merge report.   &      WHEN TO CREATE A UAS MERGE REPORTD            Create a UAS Merge report if time passes between when youA            perform the upgrade procedure and when you perform the_C            UAS merge procedure, because in the interim you may have @            created new LAN Manager users and groups on the local?            server that are not duplicated on the primary domain             controller.  E            You do not need to create a UAS Merge report if you create E            a Users report and a Groups report, use them as input data C            files during the upgrade procedure, and then immediately E            perform a UAS merge procedure. In this case, the UAS merge B            procedure does not update user and group information onA            the primary domain controller because no user or group ?            information has changed on the local server; it only E            changes the server's role from standalone server to backupt.            domain controller or member server.  @      7-36 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) c         H                                         Performing a UAS Merge Procedure    (         HOW TO CREATE A UAS MERGE REPORT+               To create a UAS Merge report:a  H               1. From the upgrade procedure Main menu, choose Additional#                  Upgrade Utilities.   G               2. From the Additional Upgrade Utilities menu, choose UASo                  Merge.                     Resultt  <                  The Standalone UAS Merge menu is displayed.  F               3. From the Standalone UAS Merge menu, choose Standalone"                  UAS Merge Report.                    Resultp  '                  The upgrade procedure:t  '                  o  Creates the report.e  D                  o  Asks you whether you want to display the report:  2                     Do you want to view the reportB                     Enter Y or N, or press Return for the default:H                                                                        Y                                    H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-37    n      %      Performing a UAS Merge Procedure>    =            4. Specify whether you want to display the report:   E      ________________________________________________________________e                       Enter . . .E      If_you_._._._____________And_the_upgrade_procedure_._._.________   C      Want to         <Return> Displays a prompt that asks you whichg5      display the              editor you want to use.u      reportW?                               Enter LSE, TECO, or TPU, or pressmB                               <Return> to use the default EDT. TheC                               upgrade procedure displays the report 7                               in the editor you choose._  D                               When you are finished with the report,E                               exit the editor to save any changes you D                               made to the report, or quit the editorB                               to exit without saving your changes.  B      Do not want to  N        Does not display the report. BecauseC      display the              the upgrade procedure saves the file, E      report                   you can display and edit the file after E      _________________________you_exit_the_upgrade_procedure.________   .      WHEN AND HOW TO EDIT THE UAS MERGE REPORTD            Table 7-1 describes circumstances in which you might editC            the UAS Merge report. For each situation, the table alsooD            describes how to edit the report and provides an example.                                  @      7-38 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)           H                                         Performing a UAS Merge Procedure    H         Table_7-1_Editing_a_UAS_Merge_Report____________________________  B                                             Example from UAS MergeH         When_._._.________Then_._._.________report______________________  C         A user name       Define a new,     A user named John Burke_G         on the local      unique user       has an account on the local_E         server has a      name for the      server. The BURKE accountoF         match on the      account on the    has a match on the primaryG         primary domain    local server;     domain controller. However,tF         controller, but   to do this,       the account on the primaryD         the accounts      make sure that    domain controller is forE         are not for the   no exclamation    another user named Burke.VH         same user         point (!)         If left unchanged, the BURKEB                           precedes the      account on the primaryC                           existing user     domain controller wouldtG                           name and type =   supersede the BURKE account F                           newname after     on the local server duringD                           the name in       the UAS merge procedure.E                           the appropriate   Therefore, an account forlC                           section of the    John Burke would not beSB                           report.           created on the primary  >                                             domain controller.  F                                             To make sure the UAS mergeC                                             procedure creates a new A                                             account JBURKE on themF                                             primary domain controller,D                                             rename the account BURKEF                                             on the local server's user1                                             list:d  :                                             BURKE = JBURKE  H                                                 (continued on next page)                  H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-39 f  e      %      Performing a UAS Merge Procedure     E      Table_7-1_(Cont.)_Editing_a_UAS_Merge_Report____________________   ?                                          Example from UAS Merge E      When_._._.________Then_._._.________report______________________   @      You want to       Rename the        To merge the members ofB      merge the         group on the      the group ARTISTS (BURKE,@      members of        local server      SVENSSON, and TRACY) on>      a group on        so that it        the local server withA      the local         has the same      the members of the group B      server with       name as the       GRAPHICS (DEPATSY, HOGAN,D      the members of    group on the      and PERKINS) on the primaryB      a group on the    primary domain    domain controller, renameA      primary domain    controller; to    the group ARTISTS on the D      controller, but   do this, type =   local server's groups list:O      the groups do     newname after     ARTISTS = GRAPHICS !PCFS Group ARTISTS -      not have the      the existing      NotehA      same name         name in the       If you do not rename the ?                        appropriate       group ARTISTS, the UAShB                        section of the    merge procedure creates aD                        report.           group on the primary domain  C                                          controller called ARTISTS,m@                                          of which only the usersC                                          BURKE, SVENSSON, and TRACYgE      ____________________________________are_members.________________s  )      HOW TO PERFORM A UAS MERGE PROCEDUREs,            To perform a UAS merge procedure:  E            1. From the upgrade procedure Main menu, choose Additional                 Upgrade Utilities.  D            2. From the Additional Upgrade Utilities menu, choose UAS               Merge.  C            3. From the Standalone UAS Merge menu, choose Standalone                UAS Merge.  B            4. In response to the following prompt, specify whether;               you want to use a data file for the UAS merget               procedure:      @      7-40 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) _  _      H                                         Performing a UAS Merge Procedure    @                  Do you want to use a data file for this upgradeB                  Enter Y or N, or press Return for the default:  N  A                  o  If you created a UAS Merge report and want toe*                     specify the data file:                       a. Enter Y.l  E                     b. In response to the following prompt, specify anH                        file name for the data file, or press <Return> to;                        use the default PWRK$UPG$UAS_SA.RPT:T  L         Specify the input data file for the Standalone UAS Merge on the next<         line [PWRK$LMUPGRADE:PWRK$UPG$UAS_SA.RPT is default]                          Resulth  G                        The UAS merge procedure merges the user databasetC                        of the local server with that of the primarySH                        domain controller according to the information in"                        the report.  8                  o  If you want to specify no data file:  ;                     a. Press <Return> to use the default N.c                          Result   E                        The UAS merge procedure displays a prompt thateF                        asks whether you want to resolve same-name user!                        conflicts.   E                        A same-name conflict occurs when a LAN Manager D                        user name on the local server matches exactlyD                        a LAN Manager user name on the primary domain"                        controller.  7                     b. Respond to the following prompt:   6                        Ignore same name user conflictsJ                        Enter Y or N, or press Return for the default:    Y        H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-41 e         %      Performing a UAS Merge Procedure   E      ________________________________________________________________s                       Enter . . .E      If_you_._._._____________And_the_upgrade_procedure_._._.________A        Want to ignore  <Return>tE      same-name                _______________________________________eE      conflicts                For_._._._________Does_this_._._.______   C                               Matching          Lets the account onoB                               accounts          the primary domainD                                                 controller supersede@                                                 the account with@                                                 the same name onA                                                 the local server.gB                                                 The user must then@                                                 use the passwordA                                                 to the account on$B                                                 the primary domain;                                                 controller.]  <                               Accounts on the   Displays theE                               local server      Standalone User MergeoE                               that have names   screen to resolve theU?                               similar to        name conflicts._,                               (but not exact)                               matches of)E-                               accounts on ther,                               primary domain(                               controller  @                               All other         Creates matching?                               accounts on       accounts on thep>                               the local server  primary domainE                               __________________controller.___________                        @      7-42 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) W  U      H                                         Performing a UAS Merge Procedure  H         ________________________________________________________________#                         Enter . . .iH         If_you_._._._____________And_the_upgrade_procedure_._._.________           Want to         NtH         resolve same-            _______________________________________H         name conflicts           For_._._._________Does_this_._._.______  ?                                  Accounts on the   Displays theuH                                  local server      Standalone User MergeH                                  that have names   screen to resolve theB                                  similar to or     name conflicts.1                                  exact matches of 0                                  accounts on the/                                  primary domain +                                  controller   C                                  All other         Creates matchingVB                                  accounts on       accounts on theA                                  the local server  primary domainoH                                  __________________controller.__________  H         ________________________________________________________________                                              H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-43           %      Performing a UAS Merge Procedure     >                     The box on the left of the Standalone UserA                     Merge screen displays an account on the local B                     server that has a same-name conflict (only oneC                     account is displayed at a time). The box on the B                     right lists the accounts on the primary domainA                     controller that have the same or similar user                      names.  >                     Select the user name on the primary domainB                     controller that you want to associate with theC                     account on the local server and press <Return>.o@                     The account on the primary domain controller?                     supersedes the account on the local server.U=                     Repeat this action for each local account                      displayed.  B                  c. If your local server is not the primary domain@                     controller, respond to the following prompt:  4                     Ignore same name group conflictsE                     Enter Y or N, or press Return for the default:  Yr  B                     A same-name conflict occurs when a LAN ManagerB                     group name on the local server matches exactlyB                     a LAN Manager group name on the primary domain                     controller.5                                      @      7-44 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) o  a      H                                         Performing a UAS Merge Procedure  H         ________________________________________________________________         If          Enter . . .,H         you_._._.______________And_the_upgrade_procedure_._._.__________           Want to     <Return>H         ignore                 _________________________________________H         same-name              For_._._._________Does_this_._._.________  C         conflicts              Matching groups   Merges the membersh  D                                                  of the group on theF                                                  local server with theE                                                  members of the group D                                                  of the same name onC                                                  the primary domaine<                                                  controller.  H                                Groups on the     Displays the StandaloneC                                local server      Group Merge screeniD                                that have names   to resolve the name;                                similar to        conflicts.O-                                (but not exacte*                                matches of),                                groups on the-                                primary domaint)                                controllerd  C                                All other groups  Creates a matchingaE                                on the local      group on the primary H                                server____________domain_controller._____                                H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-45 r  a      %      Performing a UAS Merge ProcedureS  E      ________________________________________________________________       If          Enter . . .E      you_._._.______________And_the_upgrade_procedure_._._.__________         Want to     NE      resolve                _________________________________________tE      same-name              For_._._._________Does_this_._._.________o  E      conflicts              Groups on the     Displays the StandaloneO  @                             local server      Group Merge screenA                             that have names   to resolve the name 8                             similar to or     conflicts.,                             exact matches of)                             groups on the *                             primary domain&                             controller  E                             All other groups  Creates matching groupslC                             on the local      on the primary domain E                             server____________controller.____________   E      ________________________________________________________________   E                     The box on the left of the Standalone Group Merget?                     screen displays a group on the local servereA                     that has a same-name conflict (only one group A                     is displayed at a time). The box on the right E                     lists the groups on the primary domain controller >                     that have the same or similar group names.  ?                     Select the group name on the primary domainoB                     controller that you want to associate with theB                     group on the local server, and press <Return>.@                     Members of the group on the local server areC                     made members of the group on the primary domain_@                     controller whose name you chose. Repeat this:                     action for each local group displayed.  .            5. Respond to the following prompt:            @      7-46 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) s  h      H                                         Performing a UAS Merge Procedure    I         Please enter the node name of this system [HYDRAC | PF2 for Help]   H                  _______________________________________________________H                  To_specify_._._.______Do_this_._._.____________________  6                  The default name      Press <Return>.                  displayed[1]   H                  A different name      Type the name and press <Return>.H                  [1]The_default_name_displayed_is_your_system's_DECnet__  C                  name. However, if your system's DECnet and NETBIOSdE                  names are different and the NETBIOS name is the nodepH                  name,_make_sure_that_you_specify_the_NETBIOS_name._____  @               6. In response to the following prompt, change theD                  server's role from that of a standalone server (oneD                  that does not participate in a domain) to that of aC                  backup domain controller (0) or member server (1):C  R         Enter the new workstation role [0 for backup, 1 for member, PF2 for Help]:  /                  o  A backup domain controller:_  A                     -  Receives user account information from the 1                        primary domain controller.r  7                     -  Validates user's logon requests._  F                     -  Can be promoted to primary domain controller if)                        the primary fails.n  E                  o  A member server receives user account informationa7                     from the primary domain controller.   H         ________________________________________________________________           Upgrading Disk Servicesn              H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-47                 Upgrading Disk Services          WHY UPGRADE DISK SERVICES? @            PATHWORKS V4.x for OpenVMS uses local area disk (LAD)=            container files to offer disk services to clients.eE            However, the LAN Manager server uses file allocation tableaA            (FAT) container files to offer disk shares to clients.o  D            Installing the LAN Manager server does not interfere withB            the operation of the V4.x disk server. However, the LANB            Manager FAT file system provides features that the V4.x             disk server does not.  D            For example, the V4.x disk server offers read-only accessB            to disk services over a local area network, but the LANC            Manager FAT file system offers read/write access to disk 9            shares over both local and wide area networks.   E            You upgrade disk services by dismounting them and mounting A            them again as disk shares that use the LAN Manager FAT B            file system. Because LAD and FAT container file formatsE            are similar, you can continue to use the PCDISK utility to 9            maintain the contents of a FAT container file.               For more information   B            For more detailed information about FAT container filesA            and the FAT file system, see the PATHWORKS for OpenVMS 6            (LAN Manager) Server Administrator's Guide.  !      HOW TO UPGRADE DISK SERVICES               Note   ?            You do not use the upgrade procedure to upgrade disk             services.  $            To upgrade disk services:  B            1. Ensure that you are logged in to the SYSTEM account.  B            2. While the V4.x disk server is still running, use theC               ADMINISTER/PCSA command DISMOUNT DISK to dismount the 0               disk service (LAD container file).                 Note  A               Make sure that no clients are connected to the disksA               service before you dismount it. When you dismount ao;               disk service, all connections are terminated.c  @      7-48 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) h         H                                                  Upgrading Disk Services                      Example  H                  To dismount the disk service PLANS, enter the following&                  at the system prompt:  H                  $ ADMINISTER/PCSA DISMOUNT DISK PLANS /PERMANENT /PURGE                    Resultt  G                  A message similar to the following is displayed, which G                  contains the exact location of the LAD container file.m.                  Make a note of this location.  N         %PCSA-I-DISKDISMOUNTED, SYS$SYSDEVICE:[PCSA.LAD]PLANS.DSK;1 dismounted  2               3. Enter the Server Admin interface:  '                  $ ADMINISTER/PATHWORKSh                    Result   9                  The Server Admin login box is displayed:   B               4. Enter the required login information. Press <Tab>D                  or the down arrow key to advance to the next field;H                  press the up arrow key to return to the previous field.H                  Alternatively, you can point and click on a field using                  a mouse.                     a. User id:  F                     Enter the user name for a LAN Manager account thatD                     has administrative privileges. ADMIN is the userG                     name for the default administrative account that isd>                     created during the installation procedure.                    b. Password:e  E                     Enter the password associated with the user name.                     c. Domain:7  A                     Enter the name of your local server's domain.   F               5. Choose the OK button to complete the login procedure.                    Result   9                  The Server Admin Main menu is displayed.   %                  For more informationf  ?                  For general information about the Server AdminnG                  interface, see the PATHWORKS for OpenVMS (LAN Manager) G                  Server Administrator's Guide. For detailed informationr  H              Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager) 7-49 <  u            Upgrading Disk Services    =               on using the Server Admin interface, access thef&               interface's online help.  @            6. From the Server Admin Main menu, choose Utilities.  <            7. From the Utilities submenu, choose FAT Volume.                 Result  >               The FAT File Operations dialog box is displayed.  A            8. Use the FAT File Operations dialog box to mount thecD               FAT container file as a disk share. Make sure that youC               specify the directory and the LAD container file name A               of the disk service you dismounted. In the previous >               example, these were SYS$SYSDEVICE:[PCSA.LAD] and&               PLANS.DSK, respectively.  "               For more information  D               For detailed information on creating the FAT containerC               file and mounting it as a disk share, choose the Help ;               button on the FAT File Operations dialog box.   E      ________________________________________________________________         Next Stepsr        WHAT TO DO NEXT:            To verify the installation and start the server<            independent of the installation and configuration+            procedure, proceed to Chapter 8.u                          @      7-50 Upgrading to PATHWORKS V5.0C for OpenVMS (LAN Manager)                       H                                                                        8H         ________________________________________________________________  H                      After You Install the PATHWORKS for OpenVMS Servers      D               This chapter describes tasks you can perform after you"               install the servers.  >               This chapter consists of the following sections:  !               o  Before You Begins  2               o  Verifying the Server Installation  *               o  Starting the File Servers                                                  H                  After You Install the PATHWORKS for OpenVMS Servers 8-1                 Before You Begin   E      ________________________________________________________________         Before You Begin       E      HAVE YOU_DONE?__________________________________________________ E            If_you_are_._._.______Make_sure_that_you_have_._._._______               Installing thet>            PATHWORKS for         1. Completed the installation;            OpenVMS server for       procedures described in .            the first time           Chapter 2.  ?                                  2. Completed the configurationoA                                     procedures appropriate to the ?                                     servers you have installed.   @            Upgrading the LAN     Completed the upgrade procedure;            Manager server from   described in Chapter 6 andf+            a previous version.   Chapter 7.   <            Upgrading the         Completed the configurationB            NetWare server from   procedure described in Chapter 4.E            a_previous_version._______________________________________     E      ________________________________________________________________m  &      Verifying the Server Installation          HOW TO RUN THE IVP_<            If you did not run the IVP when you installed theA            PATHWORKS kit you can run it now to make sure that the )            server installed successfully.M    B            Verifying the PATHWORKS V5.0C for OpenVMS (LAN Manager)            Installation   >            To run the IVP for PATHWORKS V5.0C for OpenVMS (LAN            Manager), enter:.              $ @SYS$TEST:PWRK$IVP   <      8-2 After You Install the PATHWORKS for OpenVMS Servers _  _      H                                        Verifying the Server Installation                   Result  H         ________________________________________________________________         If the          installa-   Then the IVPH         tion_._._.__displays_._._.________And_you_should_._._.__________  H         Succeeded   The message           Start the server, as describedG                     %PWRK-I-NORMAL,       in "Starting the File Serverst,                     IVP completed         ".                      successfully  D         Failed      An error message,     Reinstall the software, asA                     followed by -PWRK-    described in Chapter 2. &                     E-IVPFAIL, IVP hasH         ____________failed______________________________________________  A               Verifying the PATHWORKS V1.0C for OpenVMS (NetWare)_               Installation  G               To run the IVP for PATHWORKS V1.0C for OpenVMS (NetWare),                enter:  "               $ @SYS$TEST:PWVN$IVP                 Result  H         ________________________________________________________________         If the          installa-   Then the IVPH         tion_._._.__displays_._._.________And_you_should_._._.__________  H         Succeeded   The message           Start the server, as describedG                     %PWVN-I-NORMAL,       in "Starting the File Serverst,                     IVP completed         ".                      successfully  D         Failed      An error message,     Reinstall the software, asA                     followed by -PWVN-    described in Chapter 2. &                     E-IVPFAIL, IVP hasH         ____________failed______________________________________________        H                  After You Install the PATHWORKS for OpenVMS Servers 8-3           4      Starting the PATHWORKS for OpenVMS File Servers  E      ________________________________________________________________p  4      Starting the PATHWORKS for OpenVMS File Servers            WHEN TO START THE SERVER D            You must configure the server before you can start it forE            the first time. After running the configuration procedure,r9            you can start and stop the server at any time.   $      WHAT THE STARTUP PROCEDURE DOES!            The startup procedure:e  1            1. Checks for the required privileges.   D            2. Checks for enough available processes (for the NetWare               server only).   C            3. Looks for the logical names files and, if it does notS:               find the files, exits the startup procedure.  D            4. Verifies that the server has been configured, and ends               if it has not.  B            5. Makes sure that the value for VIRTPAGECNT is greater8               than 20,000 (for the NetWare server only).              6. Loads drivers.              7. Loads streams.              8. Installs images.  $            9. Starts the transports.  ,            10.Starts each of the components:  "               o  License registrar  B               o  Novell Virtual Terminal (NVT) (if configured) for#                  the NetWare server                  o  File server  .               o  Print servers (if configured)  /               o  License server (if configured)   <      8-4 After You Install the PATHWORKS for OpenVMS Servers n         H                                                Starting the File Servers  H         ________________________________________________________________  !         Starting the File Servers                 WAYS TO START THE SERVER'               You can start the server:   D               o  During the configuration procedure, as described in                  Chapter 2.s  0               o  Manually from the command line.  4               o  Automatically each time you reboot.  4         HOW TO START THE LAN MANAGER SERVER MANUALLYD               If you did not start the LAN Manager server during theH               configuration procedure, you can start it now by entering:  )               $ @SYS$STARTUP:PWRK$STARTUP                  Result  H               The LAN Manager server starts, and messages similar to the&               following are displayed:  =               PATHWORKS file server will use DECnet, NetBEUI.n:               PATHWORKS mail notification will use DECnet.B               Process NETBIOS created with identification 00000137H               Process PWRK$NBDAEMON created with identification 0000013CI               Process PWRK$LICENSE_R created with identification 00000145 P               The PATHWORKS V5.0C server is configured to support 20 PC clients.F               Process PWRK$MASTER created with identification 0000011FN               The master process will now start all other PATHWORKS processes.  :         HOW TO DEFINE LAN MANAGER SERVER COMMANDS AT LOGING               You can define server commands automatically when you log E               in to the privileged account that you use to manage thec!               LAN Manager server.   D               To define server commands at login, edit the LOGIN.COMG               file of the privileged account to add the following line:   2               $  @SYS$STARTUP:PWRK$DEFINE_COMMANDS  H                  After You Install the PATHWORKS for OpenVMS Servers 8-5 e  r            Starting the File Servers    -      HOW TO START THE NETWARE SERVER MANUALLY_?            If you did not start the PATHWORKS V1.0C for OpenVMSfC            (NetWare) server during the configuration procedure, your(            can start it now by entering:  &            $ @SYS$STARTUP:PWVN$STARTUP  3      HOW TO DEFINE NETWARE SERVER COMMANDS AT LOGINTD            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.COM D            file of the privileged account to add the following line:  (            $  @SYS$STARTUP:PWVN$COMMANDS  *      HOW TO START THE SERVER AUTOMATICALLYA            To make sure that the server starts automatically each -            time you boot your OpenVMS system:   +            1. Edit the system startup file.h  E               _______________________________________________________                On thislE               system_._._._________The_file_is_called_._._.__________O  ?               OpenVMS VAX V5.5-2   SYS$STARTUP:SYSTARTUP_V5.COM   @               OpenVMS VAX V6.0     SYS$STARTUP:SYSTARTUP_VMS.COM               or higher; orH               Alpha V1.5 or E               higher_________________________________________________   1            2. For the LAN Manager server, add the_A               @SYS$STARTUP:PWRK$STARTUP command to the file belowe6               all lines that start network transports.                 ExampleT  O      $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET_        .      .      .         $ @SYS$STARTUP:PWRK$STARTUP  <      8-6 After You Install the PATHWORKS for OpenVMS Servers e  a      H                                                Starting the File Servers    0               3. For the NetWare server, add theD                  @SYS$STARTUP:PWVN$STARTUP command to the file below9                  all lines that start network transports.t                    Example  R         $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET  	         . 	         .h	         .t  #         $ @SYS$STARTUP:PWVN$STARTUP   /         HOW TO START THE SERVER IN A VMSCLUSTERiC               If you installed and configured PATHWORKS for OpenVMSaA               on multiple members of the same VMScluster, Digital E               recommends that you use the SYSMAN utility to start the H               server manually and 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:_  H               __________________________________________________________               Enter thisH               command...____________To..._______________________________  %               $ RUN SYS$SYSTEM:SYSMAN   <                                     Start the SYSMAN utility  @               SYSMAN> SET ENVIRONMENT/NODE=(HYDRA,HYDRAB,HYDRAC)  D                                     Define the VMScluster members onB                                     which to start the server. ForB                                     example, HYDRA, HYDRAB, HYDRAC  2               SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP  C                                     Start the LAN Manager server onFD                                     all the nodes you defined in the5                                     previous command.v    H                  After You Install the PATHWORKS for OpenVMS Servers 8-7 ,  t            Starting the File Servers  E            __________________________________________________________a            Enter thissE            command...____________To..._______________________________t      /            SYSMAN> DO @SYS$STARTUP:PWVN$STARTUP   D                                  Start the NetWare server on all theB                                  nodes you defined in the previous)                                  command.o              SYSMAN> EXITi  E            ______________________Exit_the_SYSMAN_utility_____________i                                                              <      8-8 After You Install the PATHWORKS for OpenVMS Servers e  S      H                                                      Stopping the Server  H         ________________________________________________________________           Stopping the Server                WHEN TO STOP THE SERVER G               You can stop the server at any time for any reason, which2(               can include the following:  2               o  When you change server parameters  6               o  As part of an orderly system shutdown           HOW TO STOP THE SERVER>               To stop the server, enter the following command:  H               __________________________________________________________               To stop the LANi               Manager server,tH               enter:________________To_stop_the_NetWare_server,_enter:__  H               $_@SYS$STARTUP:PWRK$SH$T@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,C               add the shutdown command to the system shutdown file.S                                      H                  After You Install the PATHWORKS for OpenVMS Servers 8-9 n  s                  H                                                                        9H         ________________________________________________________________  H                                                      Installing the XQP+      D               This chapter describes how to install the eXtended QioF               Processor Plus (XQP+). The XQP+ improves the performanceF               of your computer's file system by including new featuresC               such as multithreading and asynchronous cache writes.   A               If you are using OpenVMS VAX Version 6.1 or OpenVMS D               Alpha Version 6.1 or higher, the XQP+ has already been@               installed. If not, the XQP+ kit is included in theD               PATHWORKS for OpenVMS kit. It can be installed only on$               an OpenVMS VAX system.  >               This chapter consists of the following sections:  %               o  Features of the XQP+r  1               o  Performing the XQP+ Installationu  "               o  Removing the XQP+  *               o  Sample XQP+ Installations  "               For more information  E               For additional information about the XQP+, see the XQP+ G               online release notes. After you install the XQP+ kit, the -               release notes are available as:   4               SYS$HELP:VAXPWF11X01_060.RELEASE_NOTES              H                                                  Installing the XQP+ 9-1    F            Features of the XQP+S  E      ________________________________________________________________L        Features of the XQP+             XQP+ FEATURES8            Table 9-1 describes the features of the XQP+.  E            Table_9-1_Features_of_the_XQP+____________________________a  E            Feature_______________Description_________________________,  D            Multithreading        Lets the server perform up to eight?                                  concurrent OpenVMS file system ,                                  operations.  =            Improved concurrency  Lets the OpenVMS file system C                                  increase the number of file create D                                  operations that can be processed in6                                  parallel to one disk.  B            Asynchronous cache    Lets the server return control toE            writes                the client before completing certain E                                  OpenVMS file system operations. This E                                  improves the response time needed toa>                                  access files from the server.  C            Multiblock bitmap     Reduces time spent allocating diskAE            reads_________________space._______________________________  E            After you install the XQP+, no further action is necessaryEE            for the LAN Manager server to use the performance features A            of the XQP+. Although all applications on your OpenVMSoE            system use the XQP+, only applications designed to use therC            XQP+ (such as the LAN Manager server) can take advantage             of these features.   E      _________________________________________________________________  %      Performing the XQP+ Installation_                9-2 Installing the XQP+ s  l      H                                         Performing the XQP+ Installation    #         BEFORE YOU INSTALL THE XQP+ ;               Do the following before you install the XQP+:t  F               1. Be aware that, if your VMScluster has multiple systemF                  disks, you must install the XQP+ on each system disk.  C               2. Make sure that OpenVMS VAX Version 5.5-2 or 6.0 is C                  installed on your system. Once installed, the XQP+8*                  replaces the current XQP.                    Note_  G                  In a VMScluster, OpenVMS VAX Version 5.5-2 and Version B                  6.0 systems that run their respective versions ofF                  the XQP+ can coexist. However, make sure that all the5                  systems in the cluster run the XQP+.S  A               3. Make sure that your current XQP executable file, @                  F11BXQP.EXE, resides in the SYS$COMMON:[SYSEXE]H                  directory (not in the SYS$SPECIFIC:[SYSEXE] directory).  D               4. Do a system backup with the OpenVMS BACKUP command.  *         HOW TO START THE XQP+ INSTALLATION-               To start the XQP+ installation:i  E               1. Ensure that you are logged in to the SYSTEM account.   G               2. Use the SHOW DEVICE command to make sure that at leastrH                  1000 blocks of free space are available on your OpenVMSB                  system disk, as required by the XQP+ installation                  procedure._  <               3. Change the default directory to SYS$UPDATE:  )                  $ SET DEFAULT SYS$UPDATE_  C               4. Start VMSINSTAL and specify the product identifierVH                  VAXPWF11X01_060 and the name of the device on which youE                  want to mount the media. For example, if you want tosG                  mount a TK50 on the tape drive of your VAXstation 4000.:                  Model 60, then the device name is MKA500.  4                  $ @VMSINSTAL VAXPWF11X01_060 MKA500  H                                                  Installing the XQP+ 9-3 8  A      %      Performing the XQP+ Installationr          HOW TO RESPOND TO PROMPTS<            Table 9-2 tells you how to respond to the prompts            VMSINSTAL displays.              Note_  B            Table 9-2 shows only the prompts VMSINSTAL displays; itC            does not show any informational messages. For a completenE            sample installation script, see "Sample XQP+ Installations #            " later in this section.   E      Table_9-2_XQP+_Installation_Prompts_____________________________   %                       If you want the "      At this          installationE      prompt_._._._____procedure_to_._._.______Enter_._._.____________   6      Are you          Continue                <Return>      satisfied with       the backup of      your system      disk [YES]?  0                       Exit                    NO  6      Continue the     Continue                <Return>      Installation?	      [Y]?   0                       Abort the               NO"                       installation      E                                              (continued on next page)                           9-4 Installing the XQP+ _  _      H                                         Performing the XQP+ Installation    H         Table_9-2_(Cont.)_XQP+_Installation_Prompts_____________________  (                          If you want the%         At this          installationOH         prompt_._._._____procedure_to_._._.______Enter_._._.____________  9         Are you going    Do the following        <Return>a5         to install       to enable               Note A         the XQP+         multithreading,         The installation2E         on all the       improved concurrency,   procedure sets these_B         nodes in your    and asynchronous        system parametersD         VMScluster       cache writes on an      only on the node atF         [YES]?[1]        OpenVMS VAX V5.5-2      which you perform theC                          system:                 installation. MakeaF                          ______________________  sure that you set theH                          Set the                 VMSD2 and ACP_WRITEBACKG                          system pa-      To . . .parameters to the sameuH                          rameter_._._._________  values on all the nodes  G                          VMSD2           8       in the VMScluster. For   F                          ACP_WRITEBACK   1       example, if you pressH                          ______________________  <Return> at this prompt  C                                                  to use the default H                                                  YES, make sure that theH                                                  VMSD2 and ACP_WRITEBACKH                                                  parameters are set to 8H                                                  and 1, respectively, onF                                                  all the nodes in your<                                                  VMScluster.  H         [1]This_prompt_is_displayed_only_if_your_system_is_part_of_a____           cluster.  H                                                 (continued on next page)                H                                                  Installing the XQP+ 9-5 i  e      %      Performing the XQP+ Installationf    E      Table_9-2_(Cont.)_XQP+_Installation_Prompts_____________________n  %                       If you want the "      At this          installationE      prompt_._._._____procedure_to_._._.______Enter_._._._____________  0                       Do the following        NO2                       to disable              Note>                       multithreading and      The installationB                       improved concurrency,   procedure sets these?                       and to enable           system parameters A                       asynchronous cache      only on the node atLC                       writes on an OpenVMS    which you perform theN@                       VAX V5.5-2 system:      installation. MakeC                       ______________________  sure that you set theRE                       Set the                 VMSD2 and ACP_WRITEBACKvD                       system pa-      To . . .parameters to the sameE                       rameter_._._._________  values on all the nodesI  D                       VMSD2           32769   in the VMScluster. For  C                       ACP_WRITEBACK   1       example, if you enter @                       ______________________  NO at this prompt,  @                                               make sure that theE                                               VMSD2 and ACP_WRITEBACK0@                                               parameters are set=                                               to 32769 and 1,t>                                               respectively, onC                                               all the nodes in your 9                                               VMScluster.h  E                                              (continued on next page)e                              9-6 Installing the XQP+ l  n      H                                         Performing the XQP+ Installation    H         Table_9-2_(Cont.)_XQP+_Installation_Prompts_____________________  (                          If you want the%         At this          installation H         prompt_._._._____procedure_to_._._.______Enter_._._.____________  9                          Do the following        <Return>o5                          to enable               NoteiA                          multithreading,         The installation E                          improved concurrency,   procedure sets theseSB                          and asynchronous        system parametersD                          cache writes on an      only on the node atF                          OpenVMS VAX V6.0        which you perform theC                          system:                 installation. MakefF                          ______________________  sure that you set theC                          Set the                 XQPCTLD1, XQPCTL2, B                          system pa-      To . . .and ACP_WRITEBACKG                          rameter_._._._________  parameters to the sames  H                          XQPCTLD1        8       values on all the nodes  G                          XQPCTL2         1       in the VMScluster. For_F                          ACP_WRITEBACK   1       example, if you pressH                          ______________________  <Return> at this promptC                                                  to use the default H                                                  YES, make sure that theC                                                  XQPCTLD1, XQPCTL2,_B                                                  and ACP_WRITEBACKC                                                  parameters are set @                                                  to 8, 1, and 1,A                                                  respectively, on@F                                                  all the nodes in your<                                                  VMScluster.  H                                                 (continued on next page)                    H                                                  Installing the XQP+ 9-7           %      Performing the XQP+ Installations    E      Table_9-2_(Cont.)_XQP+_Installation_Prompts_____________________E  %                       If you want the "      At this          installationE      prompt_._._._____procedure_to_._._.______Enter_._._.____________R  0                       Do the following        NO2                       to disable              Note>                       multithreading and      The installationB                       improved concurrency,   procedure sets these?                       and to enable           system parametersrA                       asynchronous cache      only on the node ateC                       writes on an OpenVMS    which you perform thes@                       VAX V6.0 system:        installation. MakeC                       ______________________  sure that you set the @                       Set the                 XQPCTLD1, XQPCTL2,?                       system pa-      To . . .and ACP_WRITEBACKSD                       rameter_._._._________  parameters to the same  E                       XQPCTLD1        0       values on all the nodes   D                       XQPCTL2         0       in the VMScluster. ForC                       ACP_WRITEBACK   1       example, if you enter @                       ______________________  NO at this prompt,@                                               make sure that the@                                               XQPCTLD1, XQPCTL2,?                                               and ACP_WRITEBACK @                                               parameters are set=                                               to 0, 0, and 1,,>                                               respectively, onC                                               all the nodes in yourr9                                               VMScluster._  6      Do you want to   Delete all previous     <Return>+      purge files      versions of the files )      replaced         associated with the       by this          XQP+      installationn      [YES]?v  E                                              (continued on next page)I              9-8 Installing the XQP+ i  h      H                                         Performing the XQP+ Installation    H         Table_9-2_(Cont.)_XQP+_Installation_Prompts_____________________  (                          If you want the%         At this          installationrH         prompt_._._._____procedure_to_._._.______Enter_._._.____________  3                          Save all previous       NOT.                          versions of the files,                          associated with the                          XQP+o  F                                                  Regardless of how youH                                                  respond to this prompt,A                                                  the installationn;                                                  procedure:_  F                                                  o  Saves the originalC                                                     XQP executable,rG                                                     F11BXQP_OLD.EXE, inTH                                                     SYS$COMMON:[SYSEXE].  >                                                  o  Copies theC                                                     PWF11X$DEINSTALSE                                                     command procedureaE                                                     to the SYS$UPDATE B                                                     directory. TheC                                                     PWF11X$DEINSTAL_F                                                     command procedure:  H                                                     -  Removes the XQP+.  C                                                     -  Restores therD                                                        original XQP.  C                                                  o  Copies the XQP+ ?                                                     executable,1C                                                     F11BXQP.EXE, to H                                                     SYS$COMMON:[SYSEXE].  H                                                 (continued on next page)          H                                                  Installing the XQP+ 9-9 o  g      %      Performing the XQP+ Installatione    E      Table_9-2_(Cont.)_XQP+_Installation_Prompts_____________________   %                       If you want the "      At this          installationE      prompt_._._._____procedure_to_._._.______Enter_._._.____________n  6      Will you         Perform an orderly      <Return>+      allow a system   system shutdown after &      shutdown after   the installation      this product     completesP      is installedL      [YES]?   0                       Not shut down           NOA                       the system after        You must reboot theeD                       the installation        system before the XQP+;                       completes               is activated.T    6      How many         Start the orderly       <Return>%      minutes          system shutdownt'      for system       immediately after &      shutdown         the installation      [0]:[2]          completes   C                       Start the orderly       n (number of minutes) %                       system shutdown !                       n number of #                       minutes after &                       the installation                       completes     E      [2]This_prompt_is_displayed_only_if_you_choose_to_shut_down_the_         system.  E                                              (continued on next page)e                    9-10 Installing the XQP+h    t      H                                         Performing the XQP+ Installation    H         Table_9-2_(Cont.)_XQP+_Installation_Prompts_____________________  (                          If you want the%         At this          installationdH         prompt_._._._____procedure_to_._._.______Enter_._._.____________  9         Do you want      Boot the system         <Return>d,         to do an         automatically after+         automatic        the orderly systemA+         system reboot    shutdown completesi         [YES]?[2,3]   3                          Not boot the system     NOaB                          automatically after     In this case, youE                          the orderly system      must boot the systems:                          shutdown completes      manually.  H         [2]This_prompt_is_displayed_only_if_you_choose_to_shut_down_the_           system._=         [3]XQP+ is not invoked until your system is rebooted.tH         ________________________________________________________________  H         ________________________________________________________________           Removing the XQP+              HOW TO REMOVE THE XQP+E               If you want to remove the XQP+ and restore the originaltE               XQP, you can use the PWF11X$DEINSTAL command procedure,P/               which is installed with the XQP+.u  >               To remove the XQP+ and restore the original XQP:  E               1. Ensure that you are logged in to the SYSTEM account.e  <               2. Change the default directory to SYS$UPDATE:  )                  $ SET DEFAULT SYS$UPDATEn  =               3. Start the PWF11X$DEINSTAL command procedure:e  #                  $ @PWF11X$DEINSTAL   H                                                 Installing the XQP+ 9-11 l  e            Removing the XQP+                   Result  @               The XQP+ removal procedure displays the following:  #          ** Restoring previous XQP.   G          ** A system reboot is now required to complete this procedure. M          ** If the installation occurred on a cluster a cluster reboot shouldA          ** be performed. J          ** This should be performed at the earliest possible opportunity.  B            4. In response to the following prompt, specify whetherD               you want to reboot your system now. Note that you must9               reboot before the original XQP is restored.   (               Start Shutdown now (Y/N) :  E               _______________________________________________________                If you want toE               reboot_._._.__________Then_enter_._._._________________.  %               Now                   Yi  E               Later_________________N________________________________n                 Note  B               Before you reboot, reset to their default values any?               system parameters that the installation procedure                changed:  E               _______________________________________________________FE               On_this_system_._._.__The_default_values_are_._._._____s  +               OpenVMS V5.5-2        VMSD2=0m3                                     ACP_WRITEBACK=1O  .               OpenVMS V6.0          XQPCTLD1=0-                                     XQPCTL2=0lE               ______________________ACP_WRITEBACK=1__________________                 9-12 Installing the XQP+o h  a      H                                                Sample XQP+ Installations  H         ________________________________________________________________  !         Sample XQP+ Installationsp      '         SYSTEM NOT PART OF A VMSCLUSTER F               This is a sample of the XQP+ installation procedure on a6               system that is not part of a VMScluster:            $ SET DEFAULT SYS$UPDATE+         $ @VMSINSTAL VAXPWF11X01_060 MKA500w  F                 VAX/VMS Software Product Installation Procedure V5.5-2  #         It is 29-JUL-1993 at 14:44.   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:              VAXPWF11X01_ V6.0   D                 Beginning installation of VAXPWF11X01_ V6.0 at 14:44  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.r  Q               o Depending on your system, this installation procedure will changeiH                 the following system parameters to the following values:  7                   System         Parameter        Value 7                   ------         ---------        -----n3                   Standalone or  VMSD2            8l3                   XQP+ only      ACP_WRITEBACK    1l                   VMScluster  7                   VMScluster     VMSD2            32769y                   with XQP+e3                   and original   ACP_WRITEBACK    1                    XQP nodes   ;               o The original XQP will be saved in the file:   2                         SYS$SYSTEM:F11BXQP_OLD.EXE  H                                                 Installing the XQP+ 9-13 s  t            Sample XQP+ Installations    G            o The following deinstallation procedure will be provided to @              allow you to back out the changes made by this kit:  3                      SYS$UPDATE:PWF11X$DEINSTAL.COM   E            o To activate the new XQP a reboot is required. During the D              installation a question will ask if it is convenient toB              shutdown the system. If you enter NO the installationG              will continue as normal but will not shutdown your system.   '      * Continue the Installation?  [Y]?   B        The installation procedure will change the following system*        parameters to the following values:  #                Parameter      Valuer#                ---------      -----                 VMSD2          8a                ACP_WRITEBACK  1   4        You must add these settings to MODPARAMS.DAT.  F      * Do you want to purge files replaced by this installation [YES]?  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.   R      * Will you allow a system shutdown after this product is installed [YES]? YES0      * How many minutes for system shutdown [0]::      * Do you want to do an automatic system reboot [YES]?L      %VAXPWF11X01_-I-QEND, This installation procedure will not ask any more      questions;      %VMSINSTAL-I-RESTORE, Restoring product save set B ... S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   A              Installation of VAXPWF11X01_ V6.0 completed at 14:45                   9-14 Installing the XQP+t p  m      H                                                Sample XQP+ Installations    +         SYSTEM THAT IS PART OF A VMSCLUSTERoF               This is a sample of the XQP+ installation procedure on a2               system that is part of a VMScluster:              $ SET DEFAULT SYS$UPDATE+         $ @VMSINSTAL VAXPWF11X01_060 MKA500   A            VAX/VMS Software Product Installation Procedure V5.5-2e  #         It is 29-JUL-1993 at 20:40.a  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             VAXPWF11X01_ V6.0_  ?            Beginning installation of VAXPWF11X01_ V6.0 at 20:40   >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.   Q               o Depending on your system, this installation procedure will changetH                 the following system parameters to the following values:  7                   System         Parameter        Value 7                   ------         ---------        -----r3                   Standalone or  VMSD2            8o3                   XQP+ only      ACP_WRITEBACK    19                   VMScluster  7                   VMScluster     VMSD2            32769t                   with XQP+ 3                   and original   ACP_WRITEBACK    1_                   XQP nodes   ;               o The original XQP will be saved in the file:t  +                  SYS$SYSTEM:F11BXQP_OLD.EXE_  J               o The following deinstallation procedure will be provided toC                 allow you to back out the changes made by this kit:i  6                         SYS$UPDATE:PWF11X$DEINSTAL.COM  H                                                 Installing the XQP+ 9-15 s               Sample XQP+ Installations    E            o To activate the new XQP a reboot is required. During the D              installation a question will ask if it is convenient toB              shutdown the system. If you enter NO the installationG              will continue as normal but will not shutdown your system._    '      * Continue the Installation?  [Y]?   ?        The installation procedure has detected that this system #        is a member of a VMScluster.P  Q      * Are you going to install the XQP+ on all the nodes in your VMScluster [Y]?   B        The installation procedure will change the following system*        parameters to the following values:  #                Parameter      Value #                ---------      -----                 VMSD2          8                 ACP_WRITEBACK  1_  4        You must add these settings to MODPARAMS.DAT.  D        This procedure only sets these values on this node. You must:  R             o set the system parameters manually on other nodes in your VMSclusterO             o update MODPARAMS.DAT on other nodes in your VMScluster to reflect                these changes.  F      * Do you want to purge files replaced by this installation [YES]?  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.   M      * Will you allow a system shutdown after this product is installed [YES] L      %VAXPWF11X01_-I-QEND, This installation procedure will not ask any more      questions;      %VMSINSTAL-I-RESTORE, Restoring product save set B ...)S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... :       Installation of VAXPWF11X01_ V6.0 completed at 20:41          9-16 Installing the XQP+_ _  _                  H                                                                       10H         ________________________________________________________________  H                                           Removing PATHWORKS for OpenVMS      H               This chapter describes how to remove PATHWORKS for OpenVMS'               servers from your system.o  >               This chapter consists of the following sections:  0               o  Reasons for Removing the Server  $               o  Removing the Server    H         ________________________________________________________________  '         Reasons for Removing the ServerQ             WHY REMOVE THE SERVER?H               You may want to remove PATHWORKS servers from your OpenVMSD               system if the IVP did not verify that the installationD               succeeded and you want to install the server again butG               there is not enough disk space, or if you want to installCF               an earlier version of the software. However, if you wantF               to continue to run PATHWORKS V4.x for OpenVMS, it is not8               necessary to remove PATHWORKS for OpenVMS.  F                 ________________________Note  ________________________  ?                 You can reinstall PATHWORKS for OpenVMS without A                 performing a removal procedure if your system has '                 enough free disk space.   E                 _____________________________________________________   "               For more information  E               For detailed information about disk space requirements,aG               see "Step 6: Check disk space requirements" in Chapter 1.o  H                                      Removing PATHWORKS for OpenVMS 10-1    +            Removing the Server  E      ________________________________________________________________e        Removing the Server      /      ABOUT THE DEINSTALLATION COMMAND PROCEDURE >            You remove a server using a command procedure that:  6            o  Is installed with PATHWORKS for OpenVMS.  2            o  Shuts down the server automatically.  D            o  Prompts you to enter information necessary to complete$               the removal procedure.  C            o  Removes all PATHWORKS for OpenVMS files, directories, ;               and logical names that are created during thee%               installation procedure.P  9            o  Removes the PATHWORKS for OpenVMS accounts.l  ;            o  Removes the NETBIOS$ACCESS OpenVMS identifier =               if PATHWORKS V4.x for OpenVMS was not installed                previously.n  /            o  Removes PATHWORKS DECnet objects.p  ,      HOW TO RUN THE DEINSTALLATION PROCEDUREE            To start the deinstallation procedure and remove PATHWORKS             for OpenVMS server:  B            1. Ensure that you are logged in to the SYSTEM account.  9            2. Change the default directory to SYS$UPDATE:Y  &               $ SET DEFAULT SYS$UPDATE  9            3. Start the deinstallation command procedure:   E               _______________________________________________________ !               To remove PATHWORKSn               V5.0C for OpenVMS A               (LAN Manager),        To remove PATHWORKS V1.0C for E               enter:________________OpenVMS_(NetWare),_enter:________   E               $_@PWRK$DEINSTAL______$_@PWVN$DEINSTAL_________________   (      10-2 Removing PATHWORKS for OpenVMS           H                                                      Removing the Server    !         HOW TO RESPOND TO PROMPTS D               Table 10-1 tells you how to respond to the prompts theF               PATHWORKS V5.0C for OpenVMS (LAN Manager) deinstallation!               procedure displays.     H         Table_10-1_PWRK$DEINSTAL_Prompts________________________________  M                                 If you want the removal           Enter . . . H         At_this_prompt_._._.____procedure_to_._._.______________________  E         Are you sure you        Continue                          YES          want to deinstalls         PATHWORKS V5.0C for          OpenVMS (LAN Manager)I
         [no]:   J                                 Exit                              <Return>  J         Do you want to delete   Save the LAN Manager on-disk      <Return>=         the LAN Manager data    structure, including the User_:         files [no]:             Authorization file and the*                                 Share file  E                                 Remove the LAN Manager on-disk    YESe=                                 structure, including the Usero:                                 Authorization file and the*                                 Share file  J         Do you want to delete   Save NETBIOS and the PATHWORKS    <Return>1         NETBIOS [no]:[1]        mail server files   E                                 Remove NETBIOS and the            YES ;                                 PATHWORKS mail server files H         [1]This_prompt_is_only_displayed_if_you_have_PATHWORKS_V4.x_for_  D         OpenVMS or PATHWORKS V1.x for OpenVMS (MacIntosh) installed.H         ________________________________________________________________  D               Table 10-2 tells you how to respond to the prompts theB               PATHWORKS V1.0C for OpenVMS (NetWare) deinstallation!               procedure displays._      H                                      Removing PATHWORKS for OpenVMS 10-3 e  n            Removing the Server    E      Table_10-2_PWVN$DEINSTAL_Prompts________________________________   J                              If you want the removal           Enter . . .E      At_this_prompt_._._.____procedure_to_._._.______________________o  B      Are you sure you        Continue                          YES      want to deinstall      PATHWORKS V1.0C for      OpenVMS (NetWare)
      [no]:  G                              Exit                              <Return>r  G      Do you want to delete   Save the NetWare on-disk          <Return>u5      the NetWare data        structure, including the 0      files [no]:             configuration Files  B                              Remove the NetWare on-disk        YES5                              structure, including thee0                              configuration files  G      Do you want to delete   Save the NetWare SYS volume       <Return>h      the NetWare SYS      Volume [no]:   B                              Remove the NetWare SYS volume     YES  G      Do you want to delete   Save NETBIOS and the PATHWORKS    <Return>_.      NETBIOS [no]:[1]        mail server files  B                              Remove NETBIOS and the            YES8                              PATHWORKS mail server filesE      [1]This_prompt_is_only_displayed_if_you_have_PATHWORKS_V4.x_for_L  A      OpenVMS or PATHWORKS V1.x for OpenVMS (MacIntosh) installed.uE      ________________________________________________________________   E      ________________________________________________________________   6      Sample LAN Manager and NetWare Removal Procedures          (      10-4 Removing PATHWORKS for OpenVMS           H                        Sample LAN Manager and NetWare Removal Procedures    ,         SAMPLE LAN MANAGER REMOVAL PROCEDUREA               This is a sample removal procedure in which all LAN E               Manager image files are removed but not the data files:o    &               $ SET DEFAULT SYS$UPDATE               $ @PWRK$DEINSTALZ               This procedure deletes all PATHWORKS V5.0C for OpenVMS (LAN Manager) images.  L               Are you sure you want to deinstall PATHWORKS V5.0C for OpenVMS#               (LAN Manager) [no]: yr  F               Do you want to delete the LAN Manager data files [no]: n  =               Deleting PATHWORKS for OpenVMS common images...tJ               Deleting PATHWORKS V5.0C for OpenVMS (Lan Manager) images...D               Removing PATHWORKS V5.0C for OpenVMS DECnet objects...F               Deassigning PATHWORKS V5.0C for OpenVMS logical names...K               PATHWORKS V5.0C for OpenVMS (Lan Manager) is now deinstalled.e               $_  (         SAMPLE NETWARE REMOVAL PROCEDUREE               This is a sample removal procedure in which all NetWare_=               image files are removed but not the data files:b  &               $ SET DEFAULT SYS$UPDATE               $ @PWVN$DEINSTALV               This procedure deletes all PATHWORKS V1.0C for OpenVMS (NetWare) images.  L               Are you sure you want to deinstall PATHWORKS V1.0C for OpenVMS               (NetWare) [no]: y   5                                               CAUTION 5                                               -------   U               If you delete the NetWare data files, the PATHWORKS license server will V               not serve NetWare licenses until you re-execute @SYS$UPDATE:PWVN$CONFIG.  B               Do you want to delete the NetWare data files [no]: nA               Do you want to delete the NetWare SYS Volume [no]:)_          H                                      Removing PATHWORKS for OpenVMS 10-5           6      Sample LAN Manager and NetWare Removal Procedures    :            Deleting PATHWORKS for OpenVMS common images...C            Deleting PATHWORKS V1.0C for OpenVMS (NetWare) images...YA            Removing PATHWORKS V1.0C for OpenVMS DECnet objects... C            Deassigning PATHWORKS V1.0C for OpenVMS logical names... D            PATHWORKS V1.0C for OpenVMS (NetWare) is now deinstalled.            $                                                                              (      10-6 Removing PATHWORKS for OpenVMS p  e                  H                                                                        AH         ________________________________________________________________  H                 Sample LAN Manager Server Installation and ConfigurationH                                                                Procedure      C               The following examples show a sample installation andmA               configuration procedure for the LAN Manager server.P    H         ________________________________________________________________  8         Sample LAN Manager Server Installation Procedure  F               The following example shows a sample installation dialog)               for the LAN Manager server.V               $ @sys$update:vmsinstal   A          OpenVMS VAX Software Product Installation Procedure V6.1   #         It is 17-NOV-1994 at 17:00.   7         Enter a question mark (?) at any time for help. F         * Are you satisfied with the backup of your system disk [YES]?A         * Where will the distribution volumes be mounted: dkb300:   R         Enter the products to be processed from the first distribution volume set.         * Products: pwrkv50c050a<         * Enter installation options you wish to use (none):1         The following products will be processed:            PWRKV50C V5.0n  9          Beginning installation of PWRKV50C V5.0 at 17:00l  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.m  +          PATHWORKS for OpenVMS Installation*  H   Sample LAN Manager Server Installation and Configuration Procedure A-1 a         5      Sample LAN Manager Server Installation Proceduree    3          Please select which components to install:   /       PATHWORKS V5.0C for OpenVMS (LAN Manager) +       PATHWORKS V1.0C for OpenVMS (NetWare)   <      * Do you want to install the LAN Manager server [NO]? y8      * Do you want to install the NetWare server [NO]? n:      %PWRKV50C-I-OLDVERPCSA, PATHWORKS for VMS (PCSA V4.2)5      -PWRKV50C-I-OLDVERPCSA, was previously installedn  0      The following components will be installed:  /       PATHWORKS V5.0C for OpenVMS (LAN Manager)n  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]?H      %PWRKV50C-I-VERSION, Checking for OpenVMS version 5.5-2 or later...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]?9      %PWRKV50C-I-FREEBLKS, Checking for 44000 free blocks1  E                    User Accounts and User Identification Codes (UICs)tE                    --------------------------------------------------Q  O          PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account,hO          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 UICi5            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, inIR            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 Systemh          Manager's Manual.  L      * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]:  A                     Optional DECprint Supervisor (DCPS) Available A                     ---------------------------------------------   K      A-2 Sample LAN Manager Server Installation and Configuration Procedure     M      H                         Sample LAN Manager Server Installation Procedure    N             The PATHWORKS for OpenVMS distribution media includes two kits forR             the DECprint Supervisor (DCPS) for OpenVMS: DCPSVAX011 and DCPSAXP011.T             DCPS is a family of layered products that runs on OpenVMS VAX and AXP toU             provide access through the OpenVMS queueing system to selected PostScript R             printers.  To use DCPS on OpenVMS VAX, you must install the DCPSVAX011R             kit.  To use DCPS on OpenVMS AXP, you must install the DCPSAXP011 kit.T             You do not need a separate license to use DCPS with LAN Manager clients.  F                        Optional eXtended Qio Processor (XQP) AvailableF                        -----------------------------------------------  O             The PATHWORKS for OpenVMS distribution media includes a performancenT             update kit, VAXPWF11X01_060.  The performance update kit contains an XQPS             for the OpenVMS file system that will improve the server's performance. Q             To use this enhanced XQP, you must separately install the performanceaO             update kit.  This kit is supported on OpenVMS V5.5-2 and V6.0 only. Q             OpenVMS V6.1 (and future versions) already includes the enhanced XQP.S  #         * Press RETURN to continue:E  B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.  W         %PWRKV50C-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 addedta         %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights databaseiT         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST.5         %UAF-I-ADDMSG, user record successfully addedq_         %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights databaseo>         %VMSINSTAL-I-RESTORE, Restoring product save set B ...N         %PWRKV50C-I-SKIPSET, Skipping product save set C (AXP Common only) ...>         %VMSINSTAL-I-RESTORE, Restoring product save set D ...S         %PWRKV50C-I-SKIPSET, Skipping product save set E (AXP LAN Manager only) ...rO         %PWRKV50C-I-SKIPSET, Skipping product save set F (VAX NetWare only) ... O         %PWRKV50C-I-SKIPSET, Skipping product save set G (AXP NetWare only) ... Q         %PWRKV50C-I-SKIPSET, Skipping product save set H (NetWare SYS Volume) ..._M         %PWRKV50C-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL >         %PWRKV50C-I-DCLCMDS, Installing PATHWORKS DCL commandsA         %PWRKV50C-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COMrQ         %PWRKV50C-I-SPECIFY, Specifying target directories for the provided filesn5         %PWRKV50C-I-OBSOLETE, Deleting obsolete files   4                                           Next Steps4                                           ----------  H   Sample LAN Manager Server Installation and Configuration Procedure A-3 S  E      5      Sample LAN Manager Server Installation Procedureo    O          To continue the installation procedure, enter the following command to =          execute the server configuration command procedures:n  "          $ @SYS$UPDATE:PWRK$CONFIG  S          For information about the configuration command procedures, see the Servera(          Installation and Upgrade Guide.  S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...v  2       Starting Installation Verification Procedure3       for PATHWORKS V5.0C for OpenVMS (LAN Manager)   /      %PWRK-I-NORMAL, IVP completed successfullyi  6       Installation of PWRKV50C V5.0 completed at 17:21  N      Enter the products to be processed from the next distribution volume set.      * Products:'       VMSINSTAL procedure done at 17:23                                                   K      A-4 Sample LAN Manager Server Installation and Configuration Procedure  C  k      H                        Sample LAN Manager Server Configuration Procedure  H         ________________________________________________________________  9         Sample LAN Manager Server Configuration Procedure_  G               The following example shows a sample configuration dialogO)               for the LAN Manager server.     !         $ @sys$update:pwrk$config:I         PATHWORKS V5.0C for OpenVMS (LAN Manager) Configuration Procedure   L             PATHWORKS stores and accesses the following types of data files:  +             o Configuration parameter files '             o License server data filese             o Log filesM!             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.  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.  H         Enter disk device name where PATHWORKS data files will be stored!         [SYS$SYSDEVICE:]: dkb300:Y7         Creating PATHWORKS directory tree on DKB300:...3  <             The LAN Manager ADMIN network account is used to=             administer the server.  The ADMIN network account ?             is mapped by default to the OpenVMS SYSTEM account.   E             If this server is to join a LAN Manager domain, the ADMIN G             network account password should be the same as the password ;             to the domain's existing ADMIN network account.   I             The network account password can be up to 14 characters long.             H   Sample LAN Manager Server Installation and Configuration Procedure A-5 M         6      Sample LAN Manager Server Configuration Procedure    *      Enter ADMIN network account password:!      Re-enter to verify password: +      Creating LAN Manager directory tree... :      Copying client files to LAN Manager directory tree...?      Copying remote boot files to LAN Manager directory tree... T      Creating PATHWORKS Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT ...R      Creating network accounts file PWRK$LMROOT:[LANMAN.DATAFILES]ACCOUNTS.LMX ...3      Changing password for ADMIN network account...o       Successfully modified ADMIN:      Creating sharefile PWRK$LMROOT:[LANMAN]SHAREFILE. ...$      New sharefile has been created.D      Creating FAT volume database PWRK$LMROOT:[LANMAN]FATVOL.DAT ...P      Creating MOP client database PWRK$RPLROOT:[000000]PWRK$MOP_DATABASE.DAT ...0      Reading current configuration parameters...  M        PATHWORKS V5.0C for OpenVMS is presently configured to run as follows:e  *         1.  Run the license server:     NO*         2.  PATHWORKS V4 compatibility: NO*         3.  Enable Remote Boot service: NO*         4.  Enable Timesource service:  NO+         5.  Enable Alerter service:     YES -         5a. Alert user names:           ADMINR.         6.  LAN Manager computer name:  SMITH10         7.  LAN Manager domain name:    LANGROUP&         8.  Other LAN Manager domains:,         9.  LAN Manager security mode:  USERQ         10. Server announce comment:    PATHWORKS V5.0C for OpenVMS (LAN Manager)_  =      Enter item number, or RETURN to use these values [done]:t"      Checking SYSGEN parameters...L      The current system configuration for SMITH1 will support 20 PC clients.+      PATHWORKS is configured to use DECnet.   K          Note: if you want this server to be the primary domain controller,cF          you should configure it to use all the transports used by any-          of the member servers in the domain.m  G          You can change the system configuration now or at a later time_.          by executing @SYS$UPDATE:PWRK$CONFIG.  =      Do you want to change the system configuration now [no]:p  K          You can upgrade PATHWORKS V4.x databases to V5 databases now or at M          a later time by executing @SYS$UPDATE:PWRK$UPGRADE.  Upgrading to V5R?          does not modify the original PATHWORKS V4.x databases.   K      A-6 Sample LAN Manager Server Installation and Configuration Proceduret e  e      H                        Sample LAN Manager Server Configuration Procedure    J         Do you want to upgrade PATHWORKS V4.x databases to V5 now [yes]: n  U             To automatically start PATHWORKS V5.0C for OpenVMS at system startup, you S             should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file Q             (SYS$MANAGER:SYSTARTUP_V5.COM for OpenVMS VAX systems prior to V6.0):a  $          $ @SYS$STARTUP:PWRK$STARTUP  Q             Note: Add this line below the lines that start all network transportse             (such as DECnet).K  N             You should also remove the line from SYS$MANAGER:SYSTARTUP_VMS.COM2             that starts the PATHWORKS V4.x server:  $          $ @SYS$STARTUP:PCFS_STARTUP  R         Do you want to start PATHWORKS V5.0C for OpenVMS on node SMITH1 now [yes]:.         PATHWORKS file server will use DECnet.4         PATHWORKS mail notification will use DECnet.<         Process NETBIOS created with identification 00000225C         Process PWRK$LICENSE_R created with identification 00000228 J         The PATHWORKS V5.0C server is configured to support 20 PC clients.@         Process PWRK$MASTER created with identification 000002B0H         The master process will now start all other PATHWORKS processes.  	         $U                                      H   Sample LAN Manager Server Installation and Configuration Procedure A-7 e  u                  H                                                                        BH         ________________________________________________________________  H           Sample NetWare Server Installation and Configuration Procedure      C               The following examples show a sample installation and =               configuration procedure for the NetWare server.n    H         ________________________________________________________________  4         Sample NetWare Server Installation Procedure  H         The following example shows a sample installation dialog for the         NetWare server.n             $ @sys$update:vmsinstala  A          OpenVMS VAX Software Product Installation Procedure V6.1s  #         It is 17-NOV-1994 at 17:00.   7         Enter a question mark (?) at any time for help.sF         * Are you satisfied with the backup of your system disk [YES]?A         * Where will the distribution volumes be mounted: dkb300:   R         Enter the products to be processed from the first distribution volume set.         * Products: pwrkv50c050S<         * Enter installation options you wish to use (none):1         The following products will be processed:            PWRKV50C V5.0   9          Beginning installation of PWRKV50C V5.0 at 17:00   >         %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 InstallationS  6             Please select which components to install:  H       Sample NetWare Server Installation and Configuration Procedure B-1 W         1      Sample NetWare Server Installation Procedure     /       PATHWORKS V5.0C for OpenVMS (LAN Manager) +       PATHWORKS V1.0C for OpenVMS (NetWare)o  <      * Do you want to install the LAN Manager server [NO]? n8      * Do you want to install the NetWare server [NO]? y  0      The following components will be installed:  +       PATHWORKS V1.0C for OpenVMS (NetWare)   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]?H      %PWRKV50C-I-VERSION, Checking for OpenVMS version 5.5-2 or later...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]?9      %PWRKV50C-I-FREEBLKS, Checking for 44000 free blocks   E                    User Accounts and User Identification Codes (UICs) E                    --------------------------------------------------   O          PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account,_O          PWRK$DEFAULT, and  a guest account, PWRK$GUEST.  The default UIC groupnE          number for both these new accounts depends on the following:l  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.p  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, incR            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 volumeK          containing client files used by the file server.  Please specify a E          disk that has a minimum of 32000 free disk blocks available.   G      B-2 Sample NetWare Server Installation and Configuration Procedure     P      H                             Sample NetWare Server Installation Procedure    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 andKI             FILER are placed in these subdirectories during installation.t  Q             Note: the server frequently accesses the data files stored on the SYShQ             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.  L         * NetWare SYS volume location [SYS$SYSDEVICE:[PWVN$SYSVOL]]: dkb300:  F                        Optional eXtended Qio Processor (XQP) AvailableF                        -----------------------------------------------  O             The PATHWORKS for OpenVMS distribution media includes a performancedT             update kit, VAXPWF11X01_060.  The performance update kit contains an XQPS             for the OpenVMS file system that will improve the server's performance.tQ             To use this enhanced XQP, you must separately install the performanceIO             update kit.  This kit is supported on OpenVMS V5.5-2 and V6.0 only. Q             OpenVMS V6.1 (and future versions) already includes the enhanced XQP.   #         * Press RETURN to continue:b  B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.                                      H       Sample NetWare Server Installation and Configuration Procedure B-3 ,  e      1      Sample NetWare Server Installation Procedurei    T      %PWRKV50C-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUESTS      %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$DEFAULT.g2      %UAF-I-ADDMSG, user record successfully added^      %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights databaseQ      %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST.l2      %UAF-I-ADDMSG, user record successfully added\      %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights databaseU      %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named NETBIOS$ACCESS.L\      %UAF-I-RDBADDMSG, identifier NETBIOS$ACCESS value: %X8001000F added to rights data base;      %VMSINSTAL-I-RESTORE, Restoring product save set B ...rK      %PWRKV50C-I-SKIPSET, Skipping product save set C (AXP Common only) ...aP      %PWRKV50C-I-SKIPSET, Skipping product save set D (VAX LAN Manager only) ...P      %PWRKV50C-I-SKIPSET, Skipping product save set E (AXP LAN Manager only) ...;      %VMSINSTAL-I-RESTORE, Restoring product save set F ...SL      %PWRKV50C-I-SKIPSET, Skipping product save set G (AXP NetWare only) ...O      %PWRKV50C-I-RESTORE, Restoring product save set H (NetWare SYS Volume) ... [      %PWRKV50C-I-PURGING, Purging PATHWORKS for OpenVMS (NetWare) files moved to SYS Volume W      %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PWVN].AJ      %PWRKV50C-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL>      %PWRKV50C-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COMN      %PWRKV50C-I-SPECIFY, Specifying target directories for the provided files2      %PWRKV50C-I-OBSOLETE, Deleting obsolete files  1                                        Next Steps 1                                        ----------   O          To continue the installation procedure, enter the following command tou=          execute the server configuration command procedures:   "          $ @SYS$UPDATE:PWVN$CONFIG  S          For information about the configuration command procedures, see the Server (          Installation and Upgrade Guide.  S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...t  2       Starting Installation Verification Procedure/       for PATHWORKS V1.0C for OpenVMS (NetWare)   /      %PWVN-I-NORMAL, IVP completed successfullye6       Installation of PWRKV50C V5.0 completed at 17:21  N      Enter the products to be processed from the next distribution volume set.      * Products:'       VMSINSTAL procedure done at 17:23F  G      B-4 Sample NetWare Server Installation and Configuration Procedured b  o      H                            Sample NetWare Server Configuration Procedure  H         ________________________________________________________________  5         Sample NetWare Server Configuration Procedure   G               The following example shows a sample configuration dialog %               for the NetWare server.p      !         $ @sys$update:pwvn$config   P                *****************************************************************P                * PATHWORKS V1.0C for OpenVMS (NetWare) Configuration Procedure *P                *****************************************************************P                *                                                               *P                *                  Copyright (C) 1992, 1994 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 PATHWORKSr/             for OpenVMS (NetWare) installation.,  M             If you need help with any question asked by this procedure, replyO5             to the question with a question mark (?).o  #         * Press RETURN to continue:   C             Defining PATHWORKS for OpenVMS (NetWare) logical names.g  L             PATHWORKS stores and accesses the following types of data files:  +             o Configuration parameter filesr'             o License server data filesx             o Log files.!             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.  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 degraderR             the performance of both the OpenVMS system and the server.  Therefore,R             Digital recommends that you specify a disk other than the system disk.  H       Sample NetWare Server Installation and Configuration Procedure B-5 d         2      Sample NetWare Server Configuration Procedure    G      * Enter disk device name where PATHWORKS data files will be stored       [SYS$SYSDEVICE:]: dkb300:4      Creating PATHWORKS directory tree on DKB300:...'      Creating NetWare directory tree...s  T          Scanning for supported Ethernet/TokenRing/FDDI controllers.  Please wait...  >       ESA is the only Network controller found on your system.D       It will be the device used by PATHWORKS for OpenVMS (NetWare).  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.S  -       Server name                : SMITH1_PNWd'       NVT Server name            : NONE >       System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]%       Run License Server         : NOr+       Internal Network Number    : 0000F5FAt%       Maximum SPX sockets        : 50          Network Type    :j       Connection      :        DLPI type       :e       Network Number  :o  &       Perform Bindup             : N/A&       Start Server when done     : YES  -         There are no networks configured yet.a         * Press RETURN to continue:  K          PATHWORKS for OpenVMS (NetWare) File Server name must be unique ono           all known IPX networks.  H      * Name of PATHWORKS for OpenVMS (NetWare) file server [SMITH1_PNW]:      G      B-6 Sample NetWare Server Installation and Configuration Proceduree i  t      H                            Sample NetWare Server Configuration Procedure    R             The PATHWORKS for OpenVMS (NetWare) product requires a system-specificN             directory  to  hold configuration information for the file server,O             and print server.  It needs to be on a disk with at least 3000 freeo             disk blocks.  C         * System-specific directory  [SYS$SPECIFIC:[PWVN$PRIVATE]]:L  Q             Novell Virtual Terminal (NVT) allows NetWare clients to log into this R             node using terminal emulation software that supports the NVT protocol.  ;         * Do you want to configure NVT on this system [NO]?c  N             PATHWORKS for OpenVMS (NetWare) client licenses are granted by theN             License Server.  In order to run a License Server, you must have a*             loaded PAK of client licenses.  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 NetWare @             File Server with this same internal network number).  O             If you are running DECnet, the default value is your DECnet addressr;             converted to hex and padded with leading zeros.r             e.g.:eK                 node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864"t  Q             If you are not running DECnet, the default value is "00000DEC" (which ;             just happens to be a valid hexadecimal number).:  ;         * Internal network number (hexadecimal) [0000F5FA]:   Q             Maximum SPX sockets is the maximum number of SPX sockets available tohQ             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 productsiN             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]:   H       Sample NetWare Server Installation and Configuration Procedure B-7 t         2      Sample NetWare Server Configuration Procedure           Network Type    :l       Connection      :G       DLPI type       :p       Network Number  :o  -         There are no networks configured yet.   E          At least one network must be configured in order to proceed.t  0      * Network Configuration Action (ADD) [ADD]:#          Configuring a new network.   @          There are two types of networks that can be configured.I          "LOCAL" networks are networks that have direct connections to anuQ          physical Network controller.  There can only be as many "LOCAL" networksOB          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 manyAT          "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. @       "NONE" returns you to Network Configuration Action prompt.  ,      * Network Type (LOCAL,TUNNEL,NONE) [L]:  1      Currently available Network controller list:              ESA(Ethernet), NONE L           "NONE" will return you to the Network Configuration Action prompt.  <      * Choose a Network controller from above listing [ESA]:  C            Input values for selecting a frame-type (DLPI-type) are:t  3                              DIX/SNAP    IEEE-802.2 2                   Media:                  (Sap E0)3                   -----      --------    ---------- 0              Token Ring:       (1)           (2)0                    FDDI:       (3)           (4)0                Ethernet:       (5)           (6)  9       Select a frame type for this >>>ETHERNET<<< device.f  E      *   Enter 5 for Ethernet_II (DIX), or 6 for 802.2 (Sap E0). [5]:t  G      B-8 Sample NetWare Server Installation and Configuration Procedure            H                            Sample NetWare Server Configuration Procedure    Q             Each configured network must have a unique Network Number.  This is asS             hexadecimal (0-9,A-F) number that can be up to 8 digits long.  For more S             information on choosing a Network Number, see the PATHWORKS for OpenVMSw0             (NetWare) Server Installation Guide.N             "NONE" will return you to the Network Configuration Action prompt.  &         * Network Number [0]: 21000001                                  #1!                               ---d"          Network Type    :   Local           Connection      :   ESA'          DLPI type       :   ETH_II_DIX %          Network Number  :   21000001   >             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]:D  W             This configuration procedure can start PATHWORKS for OpenVMS (NetWare) whenWV             it completes.  If you do not answer YES, then BINDUP will not be run, even(             if you have chosen to do so.  I         * Do you want to start PATHWORKS for OpenVMS (NetWare) now [YES]?t  =                         +-----------------------------------+R=                         | Current Configuration Information | =                         +-----------------------------------+r>                         Type Control-Y to abort configuration.  0          Server name                : SMITH1_PNW*          NVT Server name            : NONEA          System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]4(          Run License Server         : NO.          Internal Network Number    : 0000F5FA(          Maximum SPX sockets        : 50                                  #1!                               ---s"          Network Type    :   Local           Connection      :   ESA'          DLPI type       :   ETH_II_DIXl%          Network Number  :   21000001t  )          Perform Bindup             : N/A )          Start Server when done     : YESe  H       Sample NetWare Server Installation and Configuration Procedure B-9 b         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 fileuB      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.HELPmB      Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM fileE      Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM fileWH      Setting file ownership in DKB300:[PWVN$SYSVOL] to user PCFS$ACCOUNTF      Ignore any "SYSTEM-W-ACCONFLICT, file access conflict." warnings.E      Defining logical names for PATHWORKS V1.0C for OpenVMS (NetWare)m+      Begin verifying minimum resources...OK .      Complete verifying minimum resources...OK(      PATHWORKS file server will use IPX.1      PATHWORKS mail notification will use DECnet.n9      Process NETBIOS created with identification 000002A0t@      Process PWRK$LICENSE_R created with identification 000002E4$      Starting IPX Daemon (NPSD)...OK9      Starting PATHWORKS for OpenVMS (NetWare) Server...OKC      Purging old server logs...c       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:i  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.n  O          IMPORTANT:  Some sites use OpenVMS disk quotas.  If your site does so,rK          then  you may need to use the DISKQUOTA utility and enter a recordt?          for the PATHWORKS for OpenVMS (NetWare) Guest Account.           H      B-10 Sample NetWare Server Installation and Configuration Procedure i  i      H                            Sample NetWare Server Configuration Procedure    Q             IMPORTANT:  By default the PATHWORKS for OpenVMS (NetWare) SUPERVISORnM             account does not have a password.  It is suggested that after the P             file server is running that you change the SUPERVISOR password. NoteQ             that this must be done from a PC client logged in to this file server ,             using the client utility SYSCON.  M             The configuration of PATHWORKS for OpenVMS (NetWare) is complete.A  	         $G                                                                        H      Sample NetWare Server Installation and Configuration Procedure B-11 %  -                  H                                                                        CH         ________________________________________________________________  H          Sample Combined LAN Manager and NetWare Server Installation andH                                                  Configuration Procedure      C               The following examples show a sample installation andOG               configuration dialog for both the LAN Manager and NetWare1               servers.    H         ________________________________________________________________  C         Sample Combined LAN Manager and NetWare Server Installation          ProcedureS  F               The following example shows a sample installation dialog;               for both the LAN Manager and NetWare servers.)               $ @sys$update:vmsinstali  A          OpenVMS VAX Software Product Installation Procedure V6.1t  #         It is 17-NOV-1994 at 17:00.   7         Enter a question mark (?) at any time for help. F         * Are you satisfied with the backup of your system disk [YES]?A         * Where will the distribution volumes be mounted: dkb300:h  R         Enter the products to be processed from the first distribution volume set.         * Products: pwrkv50c050V<         * Enter installation options you wish to use (none):1         The following products will be processed:f           PWRKV50C V5.0o  9          Beginning installation of PWRKV50C V5.0 at 17:00o  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.l  H  Manager and NetWare Server Installation and Configuration Procedure C-1 o  g      J      Sample Combined LAN Manager and NetWare Server Installation Procedure    (       PATHWORKS for OpenVMS Installation  3          Please select which components to install:p  /       PATHWORKS V5.0C for OpenVMS (LAN Manager)w+       PATHWORKS V1.0C for OpenVMS (NetWare).  <      * Do you want to install the LAN Manager server [NO]? y8      * Do you want to install the NetWare server [NO]? y:      %PWRKV50C-I-OLDVERPCSA, PATHWORKS for VMS (PCSA V4.2)5      -PWRKV50C-I-OLDVERPCSA, was previously installedu  0      The following components will be installed:  /       PATHWORKS V5.0C for OpenVMS (LAN Manager) +       PATHWORKS V1.0C for OpenVMS (NetWare)v  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]?H      %PWRKV50C-I-VERSION, Checking for OpenVMS version 5.5-2 or later...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]?9      %PWRKV50C-I-FREEBLKS, Checking for 44000 free blocksP  E                    User Accounts and User Identification Codes (UICs) E                    --------------------------------------------------   O          PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account, O          PWRK$DEFAULT, and  a guest account, PWRK$GUEST.  The default UIC group E          number for both these new accounts depends on the following:s  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, inyR            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]:  `      C-2 Sample Combined LAN Manager and NetWare Server Installation and Configuration Procedure g  t      H    Sample Combined LAN Manager and NetWare Server Installation Procedure    O             The PATHWORKS for OpenVMS (NetWare) product comes with a SYS volumelN             containing client files used by the file server.  Please specify aH             disk that has a minimum of 32000 free disk blocks available.  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.m  Q             Note: the server frequently accesses the data files stored on the SYSdQ             volume.  If these files are stored on the system disk, it can degradesR             the performance of both the OpenVMS system and the server.  Therefore,R             Digital recommends that you specify a disk other than the system disk.  L         * NetWare SYS volume location [SYS$SYSDEVICE:[PWVN$SYSVOL]]: dkb300:  D                        Optional DECprint Supervisor (DCPS) AvailableD                        ---------------------------------------------  N             The PATHWORKS for OpenVMS distribution media includes two kits forR             the DECprint Supervisor (DCPS) for OpenVMS: DCPSVAX011 and DCPSAXP011.T             DCPS is a family of layered products that runs on OpenVMS VAX and AXP toU             provide access through the OpenVMS queueing system to selected PostScript R             printers.  To use DCPS on OpenVMS VAX, you must install the DCPSVAX011R             kit.  To use DCPS on OpenVMS AXP, you must install the DCPSAXP011 kit.T             You do not need a separate license to use DCPS with LAN Manager clients.  #         * Press RETURN to continue:   B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.                            H  Manager and NetWare Server Installation and Configuration Procedure C-3           J      Sample Combined LAN Manager and NetWare Server Installation Procedure    T      %PWRKV50C-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUESTS      %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$DEFAULT.T2      %UAF-I-ADDMSG, user record successfully added^      %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights databaseQ      %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST.r2      %UAF-I-ADDMSG, user record successfully added\      %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights database;      %VMSINSTAL-I-RESTORE, Restoring product save set B ... K      %PWRKV50C-I-SKIPSET, Skipping product save set C (AXP Common only) ...A;      %VMSINSTAL-I-RESTORE, Restoring product save set D ...tP      %PWRKV50C-I-SKIPSET, Skipping product save set E (AXP LAN Manager only) ...;      %VMSINSTAL-I-RESTORE, Restoring product save set F ...cL      %PWRKV50C-I-SKIPSET, Skipping product save set G (AXP NetWare only) ...O      %PWRKV50C-I-RESTORE, Restoring product save set H (NetWare SYS Volume) ...r[      %PWRKV50C-I-PURGING, Purging PATHWORKS for OpenVMS (NetWare) files moved to SYS Volume W      %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PWVN].nJ      %PWRKV50C-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL9      %PWRKV50C-I-DEFOBJ2, Defining DECnet object PCSA$RMI ;      %PWRKV50C-I-DCLCMDS, Installing PATHWORKS DCL commands.>      %PWRKV50C-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COMN      %PWRKV50C-I-SPECIFY, Specifying target directories for the provided files2      %PWRKV50C-I-OBSOLETE, Deleting obsolete files  1                                        Next Steps 1                                        ----------t  P          To continue the installation procedure, enter the following commands to=          execute the server configuration command procedures:F  "          $ @SYS$UPDATE:PWRK$CONFIG"          $ @SYS$UPDATE:PWVN$CONFIG  S          For information about the configuration command procedures, see the ServerK(          Installation and Upgrade Guide.  S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...e  2       Starting Installation Verification Procedure3       for PATHWORKS V5.0C for OpenVMS (LAN Manager)r  /      %PWRK-I-NORMAL, IVP completed successfully   2       Starting Installation Verification Procedure/       for PATHWORKS V1.0C for OpenVMS (NetWare)   /      %PWVN-I-NORMAL, IVP completed successfully06       Installation of PWRKV50C V5.0 completed at 17:21  `      C-4 Sample Combined LAN Manager and NetWare Server Installation and Configuration Procedure i         H    Sample Combined LAN Manager and NetWare Server Installation Procedure    Q         Enter the products to be processed from the next distribution volume set.          * Products:l*          VMSINSTAL procedure done at 17:23                                                                                    H  Manager and NetWare Server Installation and Configuration Procedure C-5           D      Sample Combined LAN Manager and NetWare Configuration Procedure  E      ________________________________________________________________.  D      Sample Combined LAN Manager and NetWare Configuration Procedure  C            The following example shows sample configuration dialogs"3            for the LAN Manager and NetWare servers.o        $ @sys$update:pwrk$configF      PATHWORKS V5.0C for OpenVMS (LAN Manager) Configuration Procedure  I          PATHWORKS stores and accesses the following types of data files:h  (          o Configuration parameter files$          o License server data files          o Log files          o Printer spool files'          o Virtual memory section filese  K          You can specify any existing OpenVMS disk device that has at leasttC          12000 free blocks of disk space to store these data files.p  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,bO          Digital recommends that you specify a disk other than the system disk.p  E      Enter disk device name where PATHWORKS data files will be stored       [SYS$SYSDEVICE:]: dkb300:4      Creating PATHWORKS directory tree on DKB300:...  9          The LAN Manager ADMIN network account is used to :          administer the server.  The ADMIN network account<          is mapped by default to the OpenVMS SYSTEM account.  B          If this server is to join a LAN Manager domain, the ADMIND          network account password should be the same as the password8          to the domain's existing ADMIN network account.  F          The network account password can be up to 14 characters long.              `      C-6 Sample Combined LAN Manager and NetWare Server Installation and Configuration Procedure a  0      H          Sample Combined LAN Manager and NetWare Configuration Procedure    -         Enter ADMIN network account password: $         Re-enter to verify password:.         Creating LAN Manager directory tree...=         Copying client files to LAN Manager directory tree... B         Copying remote boot files to LAN Manager directory tree...W         Creating PATHWORKS Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT ...eU         Creating network accounts file PWRK$LMROOT:[LANMAN.DATAFILES]ACCOUNTS.LMX ...:6         Changing password for ADMIN network account...#         Successfully modified ADMIN =         Creating sharefile PWRK$LMROOT:[LANMAN]SHAREFILE. ....'         New sharefile has been created.nG         Creating FAT volume database PWRK$LMROOT:[LANMAN]FATVOL.DAT ...eS         Creating MOP client database PWRK$RPLROOT:[000000]PWRK$MOP_DATABASE.DAT ...o3         Reading current configuration parameters...n  P           PATHWORKS V5.0C for OpenVMS is presently configured to run as follows:  -            1.  Run the license server:     NO -            2.  PATHWORKS V4 compatibility: NO--            3.  Enable Remote Boot service: NOr-            4.  Enable Timesource service:  NO-.            5.  Enable Alerter service:     YES0            5a. Alert user names:           ADMIN1            6.  LAN Manager computer name:  SMITH1P3            7.  LAN Manager domain name:    LANGROUP )            8.  Other LAN Manager domains:C/            9.  LAN Manager security mode:  USER T            10. Server announce comment:    PATHWORKS V5.0C for OpenVMS (LAN Manager)  @         Enter item number, or RETURN to use these values [done]:%         Checking SYSGEN parameters... O         The current system configuration for SMITH1 will support 20 PC clients.I.         PATHWORKS is configured to use DECnet.  N             Note: if you want this server to be the primary domain controller,I             you should configure it to use all the transports used by anyu0             of the member servers in the domain.  J             You can change the system configuration now or at a later time1             by executing @SYS$UPDATE:PWRK$CONFIG.   @         Do you want to change the system configuration now [no]:  N             You can upgrade PATHWORKS V4.x databases to V5 databases now or atP             a later time by executing @SYS$UPDATE:PWRK$UPGRADE.  Upgrading to V5B             does not modify the original PATHWORKS V4.x databases.  H  Manager and NetWare Server Installation and Configuration Procedure C-7 M  L      D      Sample Combined LAN Manager and NetWare Configuration Procedure    G      Do you want to upgrade PATHWORKS V4.x databases to V5 now [yes]: nS  R          To automatically start PATHWORKS V5.0C for OpenVMS at system startup, youP          should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM fileN          (SYS$MANAGER:SYSTARTUP_V5.COM for OpenVMS VAX systems prior to V6.0):  !       $ @SYS$STARTUP:PWRK$STARTUPP  N          Note: Add this line below the lines that start all network transports          (such as DECnet).  K          You should also remove the line from SYS$MANAGER:SYSTARTUP_VMS.COMa/          that starts the PATHWORKS V4.x server:O  !       $ @SYS$STARTUP:PCFS_STARTUPC  O      Do you want to start PATHWORKS V5.0C for OpenVMS on node SMITH1 now [yes]:e+      PATHWORKS file server will use DECnet. 1      PATHWORKS mail notification will use DECnet.E9      Process NETBIOS created with identification 000002F7 @      Process PWRK$LICENSE_R created with identification 000002FAG      The PATHWORKS V5.0C server is configured to support 20 PC clients.O=      Process PWRK$MASTER created with identification 0000018E E      The master process will now start all other PATHWORKS processes.d        $ @sys$update:pwvn$config  M             ***************************************************************** M             * PATHWORKS V1.0C for OpenVMS (NetWare) Configuration Procedure * M             *****************************************************************iM             *                                                               *QM             *                  Copyright (C) 1992, 1994 by                  *rM             *     Digital Equipment Corporation, Maynard, Massachusetts     *CM             *                           and                                 * M             *                   Novell, Incorporated                        *WM             *                   All rights reserved.                        *sM             *                                                               * M             *****************************************************************o  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.  `      C-8 Sample Combined LAN Manager and NetWare Server Installation and Configuration Procedure _  _      H          Sample Combined LAN Manager and NetWare Configuration Procedure    L             PATHWORKS stores and accesses the following types of data files:  +             o Configuration parameter files '             o License server data filesa             o Log files !             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.  M             Note: the server frequently accesses the data files stored on thelO             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.  C             The PATHWORKS directory tree already exists on DKB300:.eK             If you specify a different disk device, the PATHWORKS directoryu1             tree will be moved to the new device.c  J         * Enter disk device name where PATHWORKS data files will be stored         [DKB300:]:*         Creating NetWare directory tree...  W             Scanning for supported Ethernet/TokenRing/FDDI controllers.  Please wait...   A          ESA is the only Network controller found on your system. G          It will be the device used by PATHWORKS for OpenVMS (NetWare).T  U             PATHWORKS for OpenVMS (NetWare) has never been configured on this system.a  #         * Press RETURN to continue:n  =                         +-----------------------------------+d=                         | Current Configuration Information | =                         +-----------------------------------+ >                         Type Control-Y to abort configuration.  0          Server name                : SMITH1_PNW*          NVT Server name            : NONEA          System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]O(          Run License Server         : NO.          Internal Network Number    : 0000F5FA(          Maximum SPX sockets        : 50  H  Manager and NetWare Server Installation and Configuration Procedure C-9 L  M      D      Sample Combined LAN Manager and NetWare Configuration Procedure           Network Type    :i       Connection      :I       DLPI type       :r       Network Number  :   &       Perform Bindup             : N/A&       Start Server when done     : YES  -         There are no networks configured yet.I         * Press RETURN to continue:  K          PATHWORKS for OpenVMS (NetWare) File Server name must be unique oni           all known IPX networks.  H      * Name of PATHWORKS for OpenVMS (NetWare) file server [SMITH1_PNW]:  O          The PATHWORKS for OpenVMS (NetWare) product requires a system-specificeK          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.c  @      * 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 theeK          License Server.  In order to run a License Server, you must have a '          loaded PAK of client licenses.u  N          If you choose to run the license server, then the LAN Manager startupM          command procedure will also start the license server.  If you chooseOL          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          This is the internal network number used by the file server.  ItTP          should be unique on your network (i.e. there should be no other NetWare=          File Server with this same internal network number).l    a      C-10 Sample Combined LAN Manager and NetWare Server Installation and Configuration Proceduren    t      H          Sample Combined LAN Manager and NetWare Configuration Procedure    O             If you are running DECnet, the default value is your DECnet addressf;             converted to hex and padded with leading zeros.s             e.g.:aK                 node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864"   Q             If you are not running DECnet, the default value is "00000DEC" (whiche;             just happens to be a valid hexadecimal number).d  ;         * Internal network number (hexadecimal) [0000F5FA]:o  Q             Maximum SPX sockets is the maximum number of SPX sockets available touQ             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]:             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.  C             There are two types of networks that can be configured.lL             "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.bQ             "TUNNEL" networks connect to another node also running the IPX DECnetCV             Tunnel. The total number of "TUNNEL" networks is eight, minus however manyW             "LOCAL" networks are configured (i.e. if 2 "LOCAL" networks are configured,rQ             then there can be up to 6 "TUNNEL" networks").  There can only be one0>             "TUNNEL" network for each remote DECnet node name.C          "NONE" returns you to Network Configuration Action prompt.-  H  and        NetWare Server Installation and Configuration Procedure C-11 $  S      D      Sample Combined LAN Manager and NetWare Configuration Procedure    ,      * Network Type (LOCAL,TUNNEL,NONE) [L]:  1      Currently available Network controller list:n             ESA(Ethernet), NONERL           "NONE" will return you to the Network Configuration Action prompt.  <      * Choose a Network controller from above listing [ESA]:  C            Input values for selecting a frame-type (DLPI-type) are:i  3                              DIX/SNAP    IEEE-802.2K2                   Media:                  (Sap E0)3                   -----      --------    ---------- 0              Token Ring:       (1)           (2)0                    FDDI:       (3)           (4)0                Ethernet:       (5)           (6)  9       Select a frame type for this >>>ETHERNET<<< device.a  E      *   Enter 5 for Ethernet_II (DIX), or 6 for 802.2 (Sap E0). [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. K          "NONE" will return you to the Network Configuration Action prompt.   #      * Network Number [0]: 21000001r                              #1o                            ---       Network Type    :   Local        Connection      :   ESAO$       DLPI type       :   ETH_II_DIX"       Network Number  :   21000001  ;          A maximum of eight (8) networks can be configured.   I          If the above networks are configured correctly, then enter NONE.o  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, evenn%          if you have chosen to do so.o  F      * Do you want to start PATHWORKS for OpenVMS (NetWare) now [YES]?  a      C-12 Sample Combined LAN Manager and NetWare Server Installation and Configuration Proceduret e  r      H          Sample Combined LAN Manager and NetWare Configuration Procedure    =                         +-----------------------------------+n=                         | Current Configuration Information |u=                         +-----------------------------------+n>                         Type Control-Y to abort configuration.  0          Server name                : SMITH1_PNW*          NVT Server name            : NONEA          System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]e(          Run License Server         : NO.          Internal Network Number    : 0000F5FA(          Maximum SPX sockets        : 50                                  #1!                               ---p"          Network Type    :   Local           Connection      :   ESA'          DLPI type       :   ETH_II_DIXa%          Network Number  :   21000001r  )          Perform Bindup             : N/Ae)          Start Server when done     : YESt  3         * Is this configuration satisfactory [YES]?u4         Writing PWVN$CONF_DIR:PWVN$NWCONFIG.CFG file5         Writing PWVN$CONF_DIR:PWVN$NPSCONFIG.CFG filef8         Writing PWVN$CONF_DIR:PWVN$CONF_SYMBOLS.COM fileE         Writing Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$MSGS.DAT S         Writing Sconsole Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$SCONSOLE.HELPtL         Writing Config Help file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$CONFIG.HELPE         Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM fileeH         Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM fileK         Setting file ownership in DKB300:[PWVN$SYSVOL] to user PCFS$ACCOUNT I         Ignore any "SYSTEM-W-ACCONFLICT, file access conflict." warnings. H         Defining logical names for PATHWORKS V1.0C for OpenVMS (NetWare).         Begin verifying minimum resources...OK1         Complete verifying minimum resources...OKv+         PATHWORKS file server will use IPX.a4         PATHWORKS mail notification will use DECnet.'         Process NETBIOS already createdg.         Process PWRK$LICENSE_R already created'         Starting IPX Daemon (NPSD)...OKd<         Starting PATHWORKS for OpenVMS (NetWare) Server...OK"         Purging old server logs...#         Purging old config files...   H  and        NetWare Server Installation and Configuration Procedure C-13 n  d      D      Sample Combined LAN Manager and NetWare Configuration Procedure    8      IPX/DECnet Tunnel Daemon (STU)           : INACTIVE6      IPX Daemon (NPSD)                        : ACTIVE6      PATHWORKS for OpenVMS (NetWare) Server   : ACTIVE8      Print Services                           : INACTIVE8      NVT Daemon (NVT)                         : INACTIVE        $                                                                            a      C-14 Sample Combined LAN Manager and NetWare Server Installation and Configuration Procedure.    :                  H                                                                        DH         ________________________________________________________________  H          Sample Standalone License Server Installation and ConfigurationH                                                                Procedure      C               The following examples show a sample installation andgC               configuration dialog for a standalone license server.e    H         ________________________________________________________________  ?         Sample Standalone License Server Installation Procedure   F               The following exmaple shows a sample installation dialog0               for the standalone license server.               $ @sys$update:vmsinstale  A          OpenVMS VAX Software Product Installation Procedure V6.1P  #         It is 17-NOV-1994 at 14:46.e  7         Enter a question mark (?) at any time for help. F         * Are you satisfied with the backup of your system disk [YES]?A         * Where will the distribution volumes be mounted: dkb300:   R         Enter the products to be processed from the first distribution volume set.         * Products: pwrkv50c050r<         * Enter installation options you wish to use (none):1         The following products will be processed:            PWRKV50C V5.0u  9          Beginning installation of PWRKV50C V5.0 at 14:46   >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.e  +          PATHWORKS for OpenVMS Installation   H  Standalone  License Server Installation and Configuration Procedure D-1 g  h      <      Sample Standalone License Server Installation Procedure    3          Please select which components to install:   /       PATHWORKS V5.0C for OpenVMS (LAN Manager)E+       PATHWORKS V1.0C for OpenVMS (NetWare)f  :      * Do you want to install the LAN Manager server [NO]?6      * Do you want to install the NetWare server [NO]?A      * Do you want to install the PATHWORKS license server [YES]?a  0      The following components will be installed:  $       PATHWORKS V5.0C license server  A      If the selection is correct, the installation will continue.sD      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]?H      %PWRKV50C-I-VERSION, Checking for OpenVMS version 5.5-2 or later...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]?9      %PWRKV50C-I-FREEBLKS, Checking for 16000 free blocks   ?          All questions have been answered.  The installation ofA-          PATHWORKS for OpenVMS will continue.e  ;      %VMSINSTAL-I-RESTORE, Restoring product save set B ...RK      %PWRKV50C-I-SKIPSET, Skipping product save set C (AXP Common only) ...nP      %PWRKV50C-I-SKIPSET, Skipping product save set D (VAX LAN Manager only) ...P      %PWRKV50C-I-SKIPSET, Skipping product save set E (AXP LAN Manager only) ...L      %PWRKV50C-I-SKIPSET, Skipping product save set F (VAX NetWare only) ...L      %PWRKV50C-I-SKIPSET, Skipping product save set G (AXP NetWare only) ...N      %PWRKV50C-I-SKIPSET, Skipping product save set H (NetWare SYS Volume) ...J      %PWRKV50C-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL>      %PWRKV50C-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COMN      %PWRKV50C-I-SPECIFY, Specifying target directories for the provided files2      %PWRKV50C-I-OBSOLETE, Deleting obsolete files  1                                        Next Steps 1                                        ----------t  P          To continue the installation procedure, enter the following commands to=          execute the server configuration command procedures:   "          $ @SYS$UPDATE:PWRK$CONFIG"          $ @SYS$UPDATE:PWVN$CONFIG  S          For information about the configuration command procedures, see the Server (          Installation and Upgrade Guide.  R      D-2 Sample Standalone License Server Installation and Configuration Procedure           H                  Sample Standalone License Server Installation Procedure    V         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  5          Starting Installation Verification Procedures6          for PATHWORKS V5.0C for OpenVMS (LAN Manager)  2         %PWRK-I-NORMAL, IVP completed successfully  5          Starting Installation Verification Procedurea2          for PATHWORKS V1.0C for OpenVMS (NetWare)  2         %PWVN-I-NORMAL, IVP completed successfully9          Installation of PWRKV50C V5.0 completed at 14:55   Q         Enter the products to be processed from the next distribution volume set.          * Products: *          VMSINSTAL procedure done at 14:56                                                          H  Standalone  License Server Installation and Configuration Procedure D-3 x  i      Q      Sample LAN Manager Configuration Procedure for the Standalone License Servers  E      ________________________________________________________________s  B      Sample LAN Manager Configuration Procedure for the Standalone      License Serverd  >            The following is a sample LAN Manager configuration7            procedure for the standalone license server.a        $ @sys$update:pwrk$configF      PATHWORKS V5.0C for OpenVMS (LAN Manager) Configuration Procedure  I          PATHWORKS stores and accesses the following types of data files:e  (          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 leastoC          12000 free blocks of disk space to store these data files.   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,rO          Digital recommends that you specify a disk other than the system disk.-  E      Enter disk device name where PATHWORKS data files will be stored       [SYS$SYSDEVICE:]: dkb300:4      Creating PATHWORKS directory tree on DKB300:...  P        The PATHWORKS license server can serve PATHWORKS licenses for LAN ManagerN        clients over DECnet, NetBEUI, and TCP/IP, and NetWare clients over IPX.M        The LAN Manager and NetWare file servers do not need to be running for %        the license server to operate.   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]:eA      Do you want to serve PATHWORKS licenses over NetBEUI [no]: y >      Do you want to serve PATHWORKS licenses over TCP/IP [no]:  C      Do you want to start the PATHWORKS license server now [yes]: n         $  R      D-4 Sample Standalone License Server Installation and Configuration Procedure f  O      H  NetWare       Configuration Procedure for the Standalone License Server  H         ________________________________________________________________  A         Sample NetWare Configuration Procedure for the Standalonee         License Server      G               The following is a sample NetWare configuration procedure 0               for the standalone license server.  !         $ @sys$update:pwvn$config   P                *****************************************************************P                * PATHWORKS V1.0C for OpenVMS (NetWare) Configuration Procedure *P                *****************************************************************P                *                                                               *P                *                  Copyright (C) 1992, 1994 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 PATHWORKSr/             for OpenVMS (NetWare) installation.   M             If you need help with any question asked by this procedure, replyi5             to the question with a question mark (?).f  #         * Press RETURN to continue:   C             Defining PATHWORKS for OpenVMS (NetWare) logical names.   L             PATHWORKS stores and accesses the following types of data files:  +             o Configuration parameter filesh'             o License server data files              o Log filese!             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 D-5    S      M      Sample NetWare Configuration Procedure for the Standalone License Server     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,gO          Digital recommends that you specify a disk other than the system disk.d  @          The PATHWORKS directory tree already exists on DKB300:.H          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 storede      [DKB300:]:   T          Scanning for supported Ethernet/TokenRing/FDDI controllers.  Please wait...  >       ESA is the only Network controller found on your system.D       It will be the device used by PATHWORKS for OpenVMS (NetWare).  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.L  >       System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE]&       Serve licenses over IPX    : YES+       Internal Network Number    : 0000F5FAi%       Maximum SPX sockets        : 50          Network Type    :"       Connection      :        DLPI type       :        Network Number  :i  &       Start Server when done     : YES  -         There are no networks configured yet.T         * Press RETURN to continue:  O          The PATHWORKS for OpenVMS (NetWare) product requires a system-specificOK          directory  to  hold configuration information for the file server,rL          and print server.  It needs to be on a disk with at least 3000 free          disk blocks.r  R      D-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]]:o  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 aE*             loaded PAK of client licenses.  A         * Do you want to serve PATHWORKS licenses over IPX [YES]?   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 NetWare @             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.l             e.g.: K                 node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864"   Q             If you are not running DECnet, the default value is "00000DEC" (whiche;             just happens to be a valid hexadecimal number).e  ;         * Internal network number (hexadecimal) [0000F5FA]:   Q             Maximum SPX sockets is the maximum number of SPX sockets available to Q             processes using the IPX/SPX stack provided with PATHWORKS for OpenVMS P             (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 consulttQ             the documentation for those products when configuring this parameter.wC             Valid values for SPX sockets are 50, 200, 500 and 1000.e  P             If you change this parameter, you must reboot for it to take effect.  #         * Maximum SPX sockets [50]:a            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 D-7           M      Sample NetWare Configuration Procedure for the Standalone License ServerE    @          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.r@       "NONE" returns you to Network Configuration Action prompt.  ,      * Network Type (LOCAL,TUNNEL,NONE) [L]:  1      Currently available Network controller list:F             ESA(Ethernet), NONELL           "NONE" will return you to the Network Configuration Action prompt.  <      * Choose a Network controller from above listing [ESA]:  C            Input values for selecting a frame-type (DLPI-type) are:C  3                              DIX/SNAP    IEEE-802.2[2                   Media:                  (Sap E0)3                   -----      --------    ----------n0              Token Ring:       (1)           (2)0                    FDDI:       (3)           (4)0                Ethernet:       (5)           (6)  9       Select a frame type for this >>>ETHERNET<<< device.i  E      *   Enter 5 for Ethernet_II (DIX), or 6 for 802.2 (Sap E0). [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.d  #      * Network Number [0]: 21000001P                              #1n                            ---       Network Type    :   Local        Connection      :   ESA $       DLPI type       :   ETH_II_DIX"       Network Number  :   21000001  R      D-8 Sample Standalone License Server Installation and Configuration Procedure I         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]:_  T             This configuration procedure can start the PATHWORKS license server when             it completes.d  F         * Do you want to start the PATHWORKS license server now [YES]?  =                         +-----------------------------------+ =                         | Current Configuration Information |r=                         +-----------------------------------+_>                         Type Control-Y to abort configuration.  A          System-specific directory  : SYS$SPECIFIC:[PWVN$PRIVATE] )          Serve licenses over IPX    : YESo.          Internal Network Number    : 0000F5FA(          Maximum SPX sockets        : 50                                  #1!                               ---e"          Network Type    :   Local           Connection      :   ESA'          DLPI type       :   ETH_II_DIX %          Network Number  :   21000001   )          Start Server when done     : YESi                                H  Standalone  License Server Installation and Configuration Procedure D-9    t      M      Sample NetWare Configuration Procedure for the Standalone License Servero    0      * Is this configuration satisfactory [YES]?2      Writing PWVN$CONF_DIR:PWVN$NPSCONFIG.CFG file5      Writing PWVN$CONF_DIR:PWVN$CONF_SYMBOLS.COM fileaB      Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM fileE      Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM filenE      Defining logical names for PATHWORKS V1.0C for OpenVMS (NetWare) +      Begin verifying minimum resources...OKC.      Complete verifying minimum resources...OK<      PATHWORKS license server will use DECnet, NetBEUI, IPX.1      PATHWORKS mail notification will use DECnet. 9      Process NETBIOS created with identification 00000274A?      Process PWRK$NBDAEMON created with identification 00000278t$      Starting IPX Daemon (NPSD)...OK@      Process PWRK$LICENSE_S created with identification 00000284      Purging old server logs...e       Purging old config files...8      IPX/DECnet Tunnel Daemon (STU)           : INACTIVE6      IPX Daemon (NPSD)                        : ACTIVE8      PATHWORKS for OpenVMS (NetWare) Server   : INACTIVE8      Print Services                           : INACTIVE8      NVT Daemon (NVT)                         : INACTIVE  K          PATHWORKS for OpenVMS (NetWare) has been started with the command:S  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.   J          The configuration of PATHWORKS for OpenVMS (NetWare) is complete.        $                      S      D-10 Sample Standalone License Server Installation and Configuration ProcedureK C  S                  H                                                                        EH         ________________________________________________________________  H                                Sample LAN Manager Server Upgrade Reports    H         ________________________________________________________________           Sample Users Reporte  ?               The following is a sample PWRK$UPG$USERS.RPT fileCC               for a LAN Manager server that is not a primary domaine               controller.C  2         !+++++++++++ Users Report ++++++++++++++++  A         !This report lists the 4.x users that will be upgraded too&         !LAN Manager users by default.?         !Users upgraded must satisfy one of the three criteria:-?         !      1)  the user will have the PCFS$USER identifier.t<         !      2)  the user is a member of a 4.x PCSA group.E         !      3)  the user's default directory has one or more files 5         !          that have the Dos application ace.a  C         !For each user upgraded to a LAN Manager user, upgrade will D         !also create a share with the user name being the share name*         !as specified in the share report.  G         !This report can also be used as input into the actual upgrade.tL         !To use this file as a data file either specify the data file as is,O         !or put a comment character (!) in front of the user(s) that you do NOTr         !want upgraded.T  W         !To make the user name a different name than what is listed in the file, simplyyT         !add "= new_name" after the old name, where new_name is the name of the userD         !to be created. Names should be taken from the list of users4         !in the Primary Domain Controller List below  7         !OpenVMS users to be added as LAN Manager usersd      H                            Sample LAN Manager Server Upgrade Reports E-1 p  e            Sample Users Report          VERRILLI        !VERRILLI      JORDAN          !JORDAN"      HICKSCOURANT    !HICKSCOURANT      CARDINALE       !CARDINALE        BRODMERKLE      !BRODMERKLE      BRISTOW         !BRISTOWL      BJORK           !BJORK_      BERUBE          !BERUBE      BELLUSCI        !BELLUSCI      BELLIVEAU       !BELLIVEAUt  8      !OpenVMS users NOT to be added as LAN Manager users  (      !VPM$SERVER     !VPM$SERVER DEFAULT"      !SYSTEST_CLIG   !SYSTEST-UETP"      !SYSTEST        !SYSTEST-UETP$      !SYSTEM         !SYSTEM MANAGER      !PWRK$GUEST     !PATHWORKS(      !PWRK$DEFAULT   !PATHWORKSu*      !PHONE$SERVER   !PHONE$SERVER DEFAULT      !PCSA$RMI       !PCSA$RMI      !PCFS$ACCOUNT   !PCFS(      !NML$SERVER     !NML$SERVER DEFAULT*      !MIRRO$SERVER   !MIRRO$SERVER DEFAULT)      !MAIL$SERVER    !MAIL$SERVER DEFAULTu#      !FIELD          !FIELD SERVICEY      !DEFAULT        !  C      !LAN Manager Users found on Primary Domain Controller \\HYDRACo        !ADMIN                !      !BJORK                !      !CARDINALE            !      !CHENG                !      !DONMAC               !      !FLAHERTY             !      !GAUTREAU             !      !GLICKLER             !      !GUEST                !      !HYDRAC               !          2      E-2 Sample LAN Manager Server Upgrade Reports    t      H                                                     Sample Groups Report  H         ________________________________________________________________           Sample Groups Report  E               The following is a sample PWRK$UPG$GROUP.RPT file for a =               server that is not a primary domain controller.L  @         !++++++++++++++++++ Group Report +++++++++++++++++++++++  K         !This report lists the OpenVMS groups, OpenVMS resource identifiers T         !and PCSA 4.x groups that will be upgraded to LAN Manager groups by default.5         !Below each group is a list of their members.e+         !This report is informational only.   Q         !This report can also be used as input into the actual UAS merge upgrade.iL         !To use this file as a data file either specify the data file as is,P         !or put a comment character (!) in front of the group(s) that you do NOT         !want upgraded.o  S         !NOTE: If all the groups listed here are not upgraded, then the LAN Manager -         !security upgrade may not be complete_X         !To make the group name a different name than what is listed in the file, simplyU         !add "= new_name" after the old name, where new_name is the name of the groupe         !to be created.d  *         !There are 3 groups in this report  7         VMS360PCFS               !OpenVMS UIC Group 360          USERS=(*                BELLIVEAU                BELLUSCI*                BERUBEW                BJORK                BRISTOW                BRODMERKLE                 CARDINALE                HICKSCOURANT*                JORDAN                 VERRILLI 	         )   4         EDITING                  !PCFS Group EDITING         USERS=(h                BERUBE                 HICKSCOURANT                 VERRILLIC	         )   H                            Sample LAN Manager Server Upgrade Reports E-3                 Sample Groups Report     1      WRITERS                  !PCFS Group WRITERS       USERS=(             CARDINALE              BELLIVEAUg             BELLUSCI             BJORK              BRISTOW       )  D      !LAN Manager Groups found on Primary Domain Controller \\HYDRAC        !ADMINS
      !USERS=(*      !       ADMIN      !       GLICKLERh      !       HYDRACp      !)e
      !EDITINGu
      !USERS=(K      !       BRODMERKLEM      !       JORDANi      !      !GRAPHICS
      !USERS=(t      !       DEPATSY      !       HOGAN      !       PERKINS      !)o      !GUESTS
      !USERS=(       !       GUEST      !)o      !USERS 
      !USERS=(i      !       DONMACV      !       BURKE      !       CHENG      !       GAUTREAUd      !       FLAHERTY       !)d
      !SERVERS 
      !USERS=(f      !       HYDRACi      !)   2      E-4 Sample LAN Manager Server Upgrade Reports i  e      H                                                     Sample Groups Report  H         ________________________________________________________________  -         Sample File and Print Services Reportc  @               The following is a sample PWRK$UPG$SHARE.RPT file.      D         !+++++++++++ File and Print Services Report ++++++++++++++++  ?         !This report lists the 4.x file services, OpenVMS users B         !and OpenVMS print queues that are proposed to be upgraded*         !to LAN Manager shares by default.P         !During the actual upgrade to LAN Manager shares, the user will be askedB         !whether or not to upgrade OpenVMS users and print queues.  G         !This report can also be used as input into the actual upgrade.dO         !To use this file as input to the actual File and Print service upgradekP         !specify the data file as is, or put a comment character (!) in front of4         !the share(s) that you do NOT want upgraded.  S         !To make the share a different name than what is listed in the file, simplynU         !add "= new_name" after the old name, where new_name is the name of the shared         !to be created.t  Q         !NOTE:  If a 4.x file service has the same name as an OpenVMS print queuerK         !       or an OpenVMS user the 4.x file service will be upgraded toR8         !       and not the OpenVMS user or print queue.  :         !4.x File and Print Services to LAN Manager Shares  >         !Accessible from the basic and the enhanced redirector           WINWORD          PCCOMMON
         EXCELo
         ASCIIa  -         !Accessible from the basic redirectorS           WORD_PERFECT         PUBLIC_TEXTo         PUBLIC_DATA          POSTSCRIPT         LOTUS_123i  ,         !OpenVMS Users to LAN Manager Shares  6         !Accessible from basic and enhanced redirector  H                            Sample LAN Manager Server Upgrade Reports E-5 Y         *      Sample File and Print Services Report          SYSTEMT      NOPRIVu
      GAUTREAUT  0      !OpenVMS Print Queues to LAN Manager Shares  &      !Accessible from basic redirector        LPS20I4$PSn      LPS20I4$ANSIe      LPS20D4$PS       2LPS20D4$ANSI      LPS20APR$PS      LPS20APR$ANSI      LN03D4$PS      LN03D4$ANSI  I      ! Note: To use the Enhanced redirector with Basic redirector shares,a:      !        the share name must be changed to conform to$      !        8.3 Dos naming format.    E      ________________________________________________________________]        Sample UAS Merge Report  >            The following is a sample PWRK$UPG$UAS_SA.RPT file.    >      !+++++++++++ Standalone UAS Merge Report ++++++++++++++++  S      !This report lists the local UAS users and groups and the UAS users and groups 7      !listed on the Primary Domain Controller \\HYDRAC.u  Q      !The report also flags same name conflicts between the local and remote nodelF      !This report can be used as input into the Standalone UAS Merge .7      !Either use the report as is or to rename the user ,      !or group name, simply add "= new_name"4      !after the old name, where new_name is the nameJ      !the user or group will be renamed to. Names should be taken from theK      !list of users and groups in the Primary Domain Controller Lists belowe  +      !LAN Manager Users on the local system0    2      E-6 Sample LAN Manager Server Upgrade Reports d  u      H                                                  Sample UAS Merge Report    E         !ADMIN               !User ADMIN has a match at node \\HYDRAC I         !BELLIVEAU           !User BELLIVEAU has a match at node \\HYDRACaH         !BELLUSCI            !User BELLUSCI has a match at node \\HYDRACF         !BERUBE              !User BERUBE has a match at node \\HYDRACE         !BJORK               !User BJORK has a match at node \\HYDRACaG         !BRISTOW             !User BRISTOW has a match at node \\HYDRACuJ         !BRODMERKLE          !User BRODMERKLE has a match at node \\HYDRACE         !BURKE               !User BURKE has a match at node \\HYDRAC E         !GUEST               !User GUEST has a match at node \\HYDRAC L         !HICKSCOURANT        !User HICKSCOURANT has a match at node \\HYDRACF         !JORDAN              !User JORDAN has a match at node \\HYDRACI         !KCARDINALE          !User CARDINALE has a match at node \\HYDRAC Q         SVENSSON            !User SVENSSON DOES NOT have a match at node \\HYDRACoN         TRACY               !User TRACY DOES NOT have a match at node \\HYDRACH         !VERRILLI            !User VERRILLI has a match at node \\HYDRAC  F         !LAN Manager Users found on Primary Domain Controller \\HYDRAC           !ADMIN                !          !BELLIVEAU            !n         !BELLUSCI             !e         !BERUBE               !e         !BJORK                !t         !BRISTOW              !c         !BRODMERKLE           !y         !BURKE                !c         !CHENG                !k         !DONMAC               !l         !FLAHERTY             !e         !GAUTREAU             !n         !GLICKLER             !          !GUEST                !T         !HICKSCOURANT         !r         !HYDRAC               !          !JORDAN               !f         !KCARDINALE           !s         !VERRILLI             !h  /         !LAN Manager Groups on the local systemo            H                            Sample LAN Manager Server Upgrade Reports E-7 t  s            Sample UAS Merge Report    D      !ADMINS              !Group ADMINS has a match at node \\HYDRACD      !GUESTS              !Group GUESTS has a match at node \\HYDRACC      !USERS               !Group USERS has a match at node \\HYDRACnN      ARTISTS             !Group ARTISTS DOES NOT have a match at node \\HYDRACE      !EDITORS             !Group EDITORS has a match at node \\HYDRAC E      !WRITERS             !Group WRITERS has a match at node \\HYDRACi                                                                              2      E-8 Sample LAN Manager Server Upgrade Reports           H                                                  Sample UAS Merge Report    G         !LAN Manager Groups found on Primary Domain Controller \\HYDRAC            !ADMINSf         !USERS=(         !       ADMIN          !       GLICKLER         !       HYDRAC
         !)5         !EDITORS                  !PCFS Group EDITORS-         !USERS=(         !       BERUBE         !       HICKSCOURANT         !       VERRILLI         !       JORDAN         !       BRODMERKLE
         !)         !GRAPHICSi         !USERS=(         !       DEPATSYe         !       HOGANA         !       PERKINSN
         !)         !GUESTS          !USERS=(         !       GUEST 
         !)         !USERS         !USERS=(         !       BURKEc         !       DONMAC         !       CHENGT         !       GAUTREAU         !       FLAHERTY
         !)         !SERVERS         !USERS=(         !       HYDRAC
         !)5         !WRITERS                  !PCFS Group WRITERSe         !USERS=(         !       BELLIVEAU          !       BELLUSCI         !       BJORK     H                            Sample LAN Manager Server Upgrade Reports E-9                 Sample UAS Merge Report          !       BRISTOW      !       KCARDINALEs      !)a                                                                                    3      E-10 Sample LAN Manager Server Upgrade Reportsc e  r                  H                                                                        FH         ________________________________________________________________  H                                                          Files Installed      G               This appendix lists the files that are created during theC%               installation procedure.c    H         ________________________________________________________________  /         Files Common to LAN Manager and NetWare   G               Table F-1 describes the files created during installationTA               that are common to both the LAN Manager and NetWarey=               servers. The following information is included:   E               o  Table F-1 lists files common to both the LAN Manager %                  and NetWare servers.l  H               o  Table F-2 lists the files installed for the LAN Manager                  server only.t  D               o  Table F-3 lists the files installed for the NetWare                  server only.D  H         Table_F-1_Common_Files__________________________________________  H         File_________________________________Description________________  H         DCPS$EXAMPLES:PWRK$BORDER.LUP        DECprint Supervisor printer>                                              layup for borders  H         DCPS$EXAMPLES:PWRK$NOBORDER.LUP      DECprint Supervisor printerA                                              layup for no borders,  H                                                 (continued on next page)      H                                                      Files Installed F-1 t  w      ,      Files Common to LAN Manager and NetWare    E      Table_F-1_(Cont.)_Common_Files__________________________________0  E      File_________________________________Description________________   E      DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_    DECprint Supervisor printer @      BORDER.LUP                           layup for borders with1                                           Windows   E      DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_    DECprint Supervisor printer C      NOBORDER.LUP                         layup for no borders withb1                                           Windows   >      SYS$HELP:PCDISKHLP.HLB               DOS File Maintenance>                                           utility help library  D      SYS$HELP:PWRKV50C050.RELEASE_NOTES   PATHWORKS for OpenVMS (LAN@                                           Manager) Release Notes  ?      SYS$HELP:PWVNV10C010.RELEASE_NOTES   PATHWORKS for OpenVMS A                                           (NetWare) Release Notes   >      SYS$LIBRARY:PWRK$DEVCTL_DL1100.TLB   DEClaser 1100 device9                                           control library   >      SYS$LIBRARY:PWRK$DEVCTL_DL2100.TLB   DEClaser 2100 device9                                           control library_  ?      SYS$LIBRARY:PWRK$DEVCTL_DL2100P.TLB  DEClaser 2100P devicea9                                           control library_  >      SYS$LIBRARY:PWRK$DEVCTL_DL2200.TLB   DEClaser 2200 device9                                           control libraryl  ?      SYS$LIBRARY:PWRK$DEVCTL_DL2200P.TLB  DEClaser 2200P devicem9                                           control librarye  >      SYS$LIBRARY:PWRK$DEVCTL_DL3200.TLB   DEClaser 3200 device9                                           control libraryb  ?      SYS$LIBRARY:PWRK$DEVCTL_FX1050.TLB   FX1050 device controlr1                                           library   >      SYS$LIBRARY:PWRK$DEVCTL_FX850.TLB    FX850 device control1                                           librarye  D      SYS$LIBRARY:PWRK$DEVCTL_HP_          HP LaserJet device control1      LASERJET.TLB                         libraryg  E                                              (continued on next page)w        F-2 Files Installed r  a      H                                  Files Common to LAN Manager and NetWare    H         Table_F-1_(Cont.)_Common_Files__________________________________  H         File_________________________________Description________________  A         SYS$LIBRARY:PWRK$DEVCTL_LA210.TLB    LA210 device controld4                                              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 control 4                                              library  H         SYS$LIBRARY:PWRK$DEVCTL_LN03.TLB     LN03 device control library  E         SYS$LIBRARY:PWRK$DEVCTL_LN03P.TLB    LN03 PLUS device controlE4                                              library  F         SYS$LIBRARY:PWRK$DEVCTL_             Proprinter device control4         PROPRINTER.TLB                       library  H         SYS$LIBRARY:PWRK$DEVCTL_             Silentwriter device control4         SILENTWRITER.TLB                     library  E         SYS$LIBRARY:PWRK$PRINTER_            Printer information fileP         INFORMATION.DATY  E         SYS$LIBRARY:PWRK$VVTERMCAP.DAT       License manager terminalHA                                              capability data file   G         SYS$LIBRARY:XTI.H                    X/Open Transport InterfaceR8                                              header file  G         SYS$LOADABLE_                        Data structure definitionsY;         IMAGES:PCFSDRIVERDEF.STB             for PCFSDRIVERP  B         SYS$LOADABLE_IMAGES:PCFSDRIVER_      DECnet I/O and doubleG         V5.EXE                               mapping driver for OpenVMS 7                                              VAX V5.5-2Y  B         SYS$LOADABLE_IMAGES:PCFSDRIVER_      DECnet I/O and doubleG         V6.EXE                               mapping driver for OpenVMS >                                              VAX V6.0 and V6.1  H                                                 (continued on next page)  H                                                      Files Installed F-3           ,      Files Common to LAN Manager and NetWare    E      Table_F-1_(Cont.)_Common_Files__________________________________s  E      File_________________________________Description________________e  B      SYS$LOADABLE_IMAGES:PCIDRIVER_       Cluster Interconnect I/O@      V5.EXE                               driver for OpenVMS VAX0                                           V5.5-2  B      SYS$LOADABLE_IMAGES:PCIDRIVER_       Cluster Interconnect I/OE      V6.EXE                               driver for OpenVMS VAX V6.0s2                                           and V6.1  A      SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Streams system loadablefA      V1.EXE                               image for OpenVMS Alpha .                                           V1.5  :      SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Symbol table for?      V1.STB                               PWRK$STREAMSOS_V1.EXEe  A      SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Streams system loadablet?      V5.EXE                               image for OpenVMS VAXh0                                           V5.5-2  :      SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Symbol table for?      V5.STB                               PWRK$STREAMSOS_V5.EXEu  A      SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Streams system loadableLD      V6.EXE                               image for OpenVMS V6.0 and.                                           V6.1  :      SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Symbol table for?      V6.STB                               PWRK$STREAMSOS_V6.EXE   ?      SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  DECnet I/O and doubleBD      V1.EXE                               mapping driver for OpenVMS4                                           Alpha V1.5  :      SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  Symbol table for?      V1.STB                               SYS$PCFSDRIVER_V1.EXE   ?      SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  DECnet I/O and double D      V6.EXE                               mapping driver for OpenVMS4                                           Alpha V6.1  :      SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  Symbol table for?      V6.STB                               SYS$PCFSDRIVER_V6.EXED  E                                              (continued on next page)         F-4 Files Installed R  t      H                                  Files Common to LAN Manager and NetWare    H         Table_F-1_(Cont.)_Common_Files__________________________________  H         File_________________________________Description________________  E         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Cluster Interconnect I/O!E         V1.EXE                               driver for OpenVMS Alpha 1                                              V1.5   =         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Symbol table for A         V1.STB                               SYS$PCIDRIVER_V1.EXE_  E         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Cluster Interconnect I/OoE         V6.EXE                               driver for OpenVMS Alpha+1                                              V6.1   =         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Symbol table for A         V6.STB                               SYS$PCIDRIVER_V6.EXE   C         SYS$MANAGER:PWRK$DEFINE_             Command procedure thatuE         COMMANDS.COM[1]                      defines foreign commandsoD                                              for PATHWORKS utilities  C         SYS$MANAGER:PWRK$SHOWSYS.COM         Command procedure that F                                              shows status of PATHWORKS9                                              V5 processes(  C         SYS$MANAGER:PWVN$COMMANDS.COM        Command procedure that E                                              defines foreign commandsfB                                              for NetWare utilities  C         SYS$MANAGER:PWVN$COPY_CRASH.COM      Command procedure thatNG                                              copies a system crash dump   B         SYS$MESSAGE:PWRK$MSG.EXE             PATHWORKS for OpenVMS9                                              message fileu  ?         SYS$SHARE:NETBIOSSHR.EXE             NETBIOS for DECnet <                                              shareable image  A         SYS$SHARE:PCDISKSHR.EXE              DOS File MaintenanceID                                              utility shareable image  H         SYS$SHARE:PCSA_MAILSHR.EXE           Mail notification shareable2                                              image  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__           or command procedure.   H                                                 (continued on next page)  H                                                      Files Installed F-5 M  r      ,      Files Common to LAN Manager and NetWare    E      Table_F-1_(Cont.)_Common_Files__________________________________4  E      File_________________________________Description________________D  D      SYS$SHARE:PWRK$CMTLIBSHR.EXE         Configurator, Monitor, andA                                           Tuner shareable libraryc  D      SYS$SHARE:PWRK$CMTSHR.EXE            Configurator, Monitor, and?                                           Tuner shareable image   C      SYS$SHARE:PWRK$CSSHR_V1.EXE          Common services shareableRA                                           image for OpenVMS AlphaR.                                           V1.5  C      SYS$SHARE:PWRK$CSSHR_V5.EXE          Common services shareableiE                                           image for OpenVMS VAX V5.5-s+                                           2   C      SYS$SHARE:PWRK$CSSHR_V6.EXE          Common services shareableaD                                           image for OpenVMS V6.0 and.                                           V6.1  ;      SYS$SHARE:PWRK$FSLIB_FAT.EXE         FAT addon library!  <      SYS$SHARE:PWRK$FSLIB_ODS2.EXE        ODS2 addon library  C      SYS$SHARE:PWRK$LICENSE_LIBSHR.EXE    License shareable libraryi  E      SYS$SHARE:PWRK$PCMALTSHR.EXE         Alternative PATHWORKS cacheSA                                           manager shareable image   A      SYS$SHARE:PWRK$PCMSHR.EXE            PATHWORKS cache manager 9                                           shareable imageH  E      SYS$SHARE:PWRK$SDA.EXE               PATHWORKS extension for the\>                                           System Dump Analyzer  E      SYS$SHARE:PWRK$STREAMSSHR_V1.EXE     Streams shareable image for <                                           OpenVMS Alpha V1.5  E      SYS$SHARE:PWRK$STREAMSSHR_V5.EXE     Streams shareable image fors<                                           OpenVMS VAX V5.5-2  E      SYS$SHARE:PWRK$STREAMSSHR_V6.EXE     Streams shareable image fors?                                           OpenVMS V6.0 and V6.1   D      SYS$SHARE:PWRK$XTILIBSHR.EXE         X/Open Transport Interface;                                           shareable libraryJ  E                                              (continued on next page)A        F-6 Files Installed E  s      H                                  Files Common to LAN Manager and NetWare    H         Table_F-1_(Cont.)_Common_Files__________________________________  H         File_________________________________Description________________  G         SYS$SHARE:PWRK$XTINETBIOSSHR.EXE     X/Open Transport InterfacerH                                              shareable image for NETBIOS  G         SYS$SHARE:PWRK$XTINSPNBSHR.EXE       X/Open Transport Interface G                                              shareable image for DECnet   E         SYS$SHARE:SECURESHRP_V15_SSB.EXE     SECURESHRP.EXE image for ?                                              OpenVMS Alpha V1.5   C         SYS$STARTUP:PWRK$CHECK_PARAMS.COM    Command procedure that D                                              checks system resources  C         SYS$STARTUP:PWRK$COMMON_             Command procedure that D         LOGICALS.COM                         defines common logicals  D         SYS$STARTUP:PWRK$COMMON_             Common shutdown command6         SHUTDOWN.COM                         procedure  C         SYS$STARTUP:PWRK$COMMON_STARTUP.COM  Common startup commande6                                              procedure  D         SYS$STARTUP:PWRK$LICENSE_            License server shutdown>         SHUTDOWN.COM                         command procedure  C         SYS$STARTUP:PWRK$LICENSE_            License server startupT>         STARTUP.COM                          command procedure  C         SYS$STARTUP:PWRK$LOGICALS.COM        Command procedure that B                                              defines logical names  G         SYS$STARTUP:PWRK$SHUTDOWN.COM        Shutdown command procedure   F         SYS$STARTUP:PWRK$STARTUP.COM         Startup command procedure  C         SYS$STARTUP:PWVN$COMMON_             Command procedure thatgE         LOGICALS.COM                         defines NetWare cluster-NA                                              common logical namesL  C         SYS$STARTUP:PWVN$LOGICALS.COM        Command procedure that D                                              defines NetWare logical2                                              names  H                                                 (continued on next page)  H                                                      Files Installed F-7           ,      Files Common to LAN Manager and NetWare    E      Table_F-1_(Cont.)_Common_Files__________________________________U  E      File_________________________________Description________________H  E      SYS$STARTUP:PWVN$NPSD_START.COM      Command procedure that runs D                                           the NetWare Protocol Suite0                                           Daemon  B      SYS$STARTUP:PWVN$SHUTDOWN.COM        NetWare shutdown command3                                           procedure   A      SYS$STARTUP:PWVN$STARTUP.COM         NetWare startup command 3                                           procedure   E      SYS$STARTUP:PWVN$TUNNEL_START.COM    Command procedure that runs C                                           the NetWare DECnet tunneln  <      SYS$SYSTEM:NETBIOS.EXE               NETBIOS for DECnet  >      SYS$SYSTEM:PCDISK.EXE                DOS File Maintenance1                                           utility_  :      SYS$SYSTEM:PCFSDRIVER_V5.STB         Symbol table for;                                           PCFSDRIVER_V5.EXEa  :      SYS$SYSTEM:PCFSDRIVER_V6.STB         Symbol table for;                                           PCFSDRIVER_V6.EXE_  E      SYS$SYSTEM:PCIDRIVER_V5.STB          Symbol table for PCIDRIVER_ 0                                           V5.EXE  E      SYS$SYSTEM:PCIDRIVER_V6.STB          Symbol table for PCIDRIVER_e0                                           V6.EXE  ?      SYS$SYSTEM:PCSA$MAIL_SERVER.EXE      PATHWORKS mail server   A      SYS$SYSTEM:PCSA_CLAIM_NAME.EXE       PCSA claim name utility   @      SYS$SYSTEM:PCX$SERVER.COM            Command procedure thatD                                           starts the PC DECwindows X0                                           server  =      SYS$SYSTEM:PWRK$EVTREPORT.EXE        Event logger report 3                                           generator_  ?      SYS$SYSTEM:PWRK$KNBDAEMON.EXE        Kernel NETBIOS daemonr1                                           processK  E                                              (continued on next page)         F-8 Files Installed r  s      H                                  Files Common to LAN Manager and NetWare    H         Table_F-1_(Cont.)_Common_Files__________________________________  H         File_________________________________Description________________  H         SYS$SYSTEM:PWRK$LICENSE_             License count units utility         COUNTUNITS.EXE[1]L  A         SYS$SYSTEM:PWRK$LICENSE_MANAGER.EXE  License manager user_6                                              interface  >         SYS$SYSTEM:PWRK$LICENSE_             License registrar         REGISTRAR.EXE   ;         SYS$SYSTEM:PWRK$LICENSE_SERVER.EXE   License server   F         SYS$SYSTEM:PWRK$LOADSTREAMS_V1.EXE   Loader for streams systemG                                              loadable image for OpenVMSo7                                              Alpha V1.5u  F         SYS$SYSTEM:PWRK$LOADSTREAMS_V5.EXE   Loader for streams systemG                                              loadable image for OpenVMS 7                                              VAX V5.5-2   F         SYS$SYSTEM:PWRK$LOADSTREAMS_V6.EXE   Loader for streams systemG                                              loadable image for OpenVMSS:                                              V6.0 and V6.1  E         SYS$SYSTEM:PWRK$MASTER.EXE           Master process and eventS3                                              loggeri  >         SYS$SYSTEM:PWRK$MONITOR.EXE          PATHWORKS Monitor  C         SYS$SYSTEM:PWRK$NBDAEMON.EXE         NETBIOS daemon process   H         SYS$SYSTEM:PWRK$NBSHOW.EXE[1]        NetBEUI show status utility  A         SYS$SYSTEM:PWRK$PWMON.EXE[1]         PATHWORKS host-based <                                              monitor utility  ?         SYS$SYSTEM:PWRK$SETSHO.EXE           PATHWORKS Set/Show ?                                              Parameters utility0  D         SYS$SYSTEM:PWRK$SHOWQUOTA.EXE        Show Disk Quota utility  @         SYS$SYSTEM:PWRK$START.EXE            Utility that startsD                                              detached master process  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__           or command procedure.   H                                                 (continued on next page)  H                                                      Files Installed F-9 P  $      ,      Files Common to LAN Manager and NetWare    E      Table_F-1_(Cont.)_Common_Files__________________________________   E      File_________________________________Description________________   <      SYS$SYSTEM:PWRK$STOP.EXE             Utility that stops=                                           PATHWORKS processesl  ?      SYS$SYSTEM:PWRK$VERIFY.EXE           Utility that verifies_B                                           configuration parameters  D      SYS$SYSTEM:PWVN$DROUTER.EXE          NetWare utility that dumps;                                           the router tablesT  D      SYS$SYSTEM:PWVN$GETLAN.EXE           NetWare utility that shows=                                           this node's network   E      SYS$SYSTEM:PWVN$MERGE.EXE            NetWare utility that mergesB=                                           configuration filesV  @      SYS$SYSTEM:PWVN$NPSD.EXE             NetWare Protocol Suite7                                           Daemon (NPSD)T  A      SYS$SYSTEM:PWVN$NWCP.EXE             NetWare control programK  E      SYS$SYSTEM:PWVN$RROUTER.EXE          NetWare utility that resets ;                                           the router tables_  <      SYS$SYSTEM:PWVN$SAPD.EXE             Netware SAP Daemon  ?      SYS$SYSTEM:PWVN$STUACP.EXE           NetWare DECnet tunnel   B      SYS$TEST:PWRK$IVP.COM                LAN Manager Installation@                                           Verification Procedure/                                           (IVP).  B      SYS$TEST:PWRK$IVP.DAT                LAN Manager InstallationE                                           Verification Procedure dataf.                                           file  >      SYS$TEST:PWVN$IVP.COM                NetWare Installation@                                           Verification Procedure/                                           (IVP)S  >      SYS$TEST:PWVN$IVP.DAT                NetWare Installation@                                           Verification procedure3                                           data filen  E                                              (continued on next page)         F-10 Files InstalledR    D      H                                  Files Common to LAN Manager and NetWare    H         Table_F-1_(Cont.)_Common_Files__________________________________  H         File_________________________________Description________________  C         SYS$UPDATE:PWL$SERVER_STATE.DAT[2]   NetWare license serverd7                                              state fileN  C         SYS$UPDATE:PWRK$COMMANDS.CLD         PATHWORKS command line_8                                              definitions  C         SYS$UPDATE:PWRK$COMMON.SAV[3]        Backup saveset for the E                                              initial PATHWORKS commonv;                                              directory tree   A         SYS$UPDATE:PWRK$COMMON_CONFIG.COM    Common configuratione>                                              command procedure  B         SYS$UPDATE:PWRK$CONFIG.COM           Configuration command6                                              procedure  C         SYS$UPDATE:PWRK$DEFINE_FORMS.COM[3]  Command procedure that F                                              defines printer forms for6                                              PATHWORKS  H         SYS$UPDATE:PWRK$DEINSTAL.COM         PATHWORKS V5.0C for OpenVMSB                                              (LAN Manager) removal>                                              command procedure  H         SYS$UPDATE:PWRK$GETPARAM.COM         Command procedure that getsH                                              a parameter from LANMAN.INI  C         SYS$UPDATE:PWRK$INSTALL_             Command procedure thatlC         COMMANDS.COM                         installs PATHWORKS DCL 5                                              commands1  ;         SYS$UPDATE:PWRK$LICENSE_CONFIG.COM   License server B                                              configuration command6                                              procedure  H         [2]This_file_is_installed_only_if_PATHWORKS_V1.0C_for_OpenVMS___  ?         (NetWare) is being installed and you are upgrading fromS-         PATHWORKS V1.0 for OpenVMS (NetWare).f?         [3]This file is deleted after you configure the server.X  H                                                 (continued on next page)  H                                                     Files Installed F-11           ,      Files Common to LAN Manager and NetWare    E      Table_F-1_(Cont.)_Common_Files__________________________________   E      File_________________________________Description________________   @      SYS$UPDATE:PWRK$PURGE_               Command procedure thatB      WORKSTATIONS.COM[4]                  deletes MOP clients from6                                           NCL database  @      SYS$UPDATE:PWRK$SETINI.COM           Command procedure that<                                           updates LANMAN.INI4                                           parameters  E      SYS$UPDATE:PWRK$SETPARAM.COM         Command procedure that sets C                                           a parameter in LANMAN.INIO  @      SYS$UPDATE:PWRK$VERSIONS.COM         Command procedure that?                                           shows PATHWORKS imageO2                                           versions  ?      SYS$UPDATE:PWVN$CONFIG.COM           NetWare configurationM;                                           command procedure   A      SYS$UPDATE:PWVN$DEINSTAL.COM         NetWare product removal ;                                           command procedure   @      SYS$UPDATE:PWVN$RESIZE_STACK.COM     Command procedure that@                                           configures the NetWare4                                           transportsE      [4]This_file_is_deleted_after_you_install_DECnet_Phase_V_and____         start the server.E      ________________________________________________________________S  E      ________________________________________________________________Y  6      Files Created During the LAN Manager Installation  ?            Table F-2 describes the files created during the LANa             Manager installation.                  F-12 Files Installed            H                        Files Created During the LAN Manager Installation    H         Table_F-2_LAN_Manager_Files_____________________________________  H         File_________________________________Description________________  C         SYS$HELP:PWRK$ADMIN.HLB              Net Admin utility help 4                                              library  G         SYS$HELP:PWRK$MOP_MANAGER.HLB        MOP Remote Boot Management A                                              utility help library   F         SYS$HELP:PWRK$PCSA_MANAGER.HLB[1]    PCSA Manager help library  G         SYS$HELP:PWRK$SHOWINI.HLB[2]         Show LANMAN.INI Parameters A                                              utility help librarys  C         SYS$HELP:PWRK$UPGRADE.HLB            upgrade procedure help 4                                              library  C         SYS$MANAGER:PWRK$LMSHARE.COM         Command procedure thatl?                                              manipulates sharese  H         SYS$MANAGER:PWRK$LMSHARE_ADMIN.COM   Command procedure that setsH                                              the password for the ADMIN$2                                              share  E         SYS$SHARE:PWRK$CMT_LM.EXE            LAN Manager interface torG                                              the Configurator, Monitor, 6                                              and Tuner  G         SYS$SHARE:PWRK$LMAPISHR.EXE          LAN Manager APIs shareables2                                              image  @         SYS$SHARE:PWRK$NBLIB_DECNET.EXE      LAN Manager network@                                              interface to DECnet  @         SYS$SHARE:PWRK$NBLIB_NETBEUI.EXE     LAN Manager networkA                                              interface to NetBEUI   @         SYS$SHARE:PWRK$NBLIB_TCPIP.EXE       LAN Manager network@                                              interface to TCP/IP  H         SYS$STARTUP:PWRK$LMDMN_START.COM     Command procedure that runsC                                              the LAN Manager daemon$  H         [1]This_file_is_installed_only_if_you_have_PATHWORKS_V4.x_for___  )         OpenVMS installed on your system.SF         [2]This file is (or is associated with) an unsupported utility         or command procedure.   H                                                 (continued on next page)  H                                                     Files Installed F-13 g         6      Files Created During the LAN Manager Installation    E      Table_F-2_(Cont.)_LAN_Manager_Files_____________________________   E      File_________________________________Description________________   E      SYS$STARTUP:PWRK$LMMCP_START.COM     Command procedure that runsSD                                           the LAN Manager controller  E      SYS$STARTUP:PWRK$LMRIPL_START.COM    Command procedure that runsRD                                           the LAN Manager RPL Remote5                                           Boot server   E      SYS$STARTUP:PWRK$LMSRV_START.COM     Command procedure that runs @                                           the LAN Manager server  @      SYS$STARTUP:PWRK$PCSA_SHUTDOWN.COM   PATHWORKS for VMS V4.xD                                           shutdown command procedure  B      SYS$SYSTEM:PWRK$ADMIN.COM            Remote Net Admin command3                                           procedure   C      SYS$SYSTEM:PWRK$ADMIN.EXE            Character-oriented, menu- D                                           driven Net Admin interface  D      SYS$SYSTEM:PWRK$FATVOL.EXE           Initialization utility forA                                           the FAT volume databaser  <      SYS$SYSTEM:PWRK$LMDMN.EXE            LAN Manager daemon  @      SYS$SYSTEM:PWRK$LMMCP.EXE            LAN Manager controller  E      SYS$SYSTEM:PWRK$LMRIPL.EXE           LAN Manager RPL Remote Boot 0                                           server  <      SYS$SYSTEM:PWRK$LMSRV.EXE            LAN Manager server  A      SYS$SYSTEM:PWRK$LM_BUILDACC.EXE[2]   Standalone utility thatUE                                           initializes the LAN ManagerM@                                           user accounts database  A      SYS$SYSTEM:PWRK$LM_GROUP.EXE[2]      Standalone utility thatOA                                           manages the LAN ManagerK9                                           groups database   A      SYS$SYSTEM:PWRK$LM_MODAL.EXE[2]      Standalone utility thatLA                                           manages the LAN Manager 9                                           modals databaseU  E      [2]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.  E                                              (continued on next page)u        F-14 Files Installed            H                        Files Created During the LAN Manager Installation    H         Table_F-2_(Cont.)_LAN_Manager_Files_____________________________  H         File_________________________________Description________________  D         SYS$SYSTEM:PWRK$LM_SHARE.EXE[2]      Standalone utility thatD                                              manages the LAN Manager<                                              shares database  D         SYS$SYSTEM:PWRK$LM_USER.EXE[2]       Standalone utility thatD                                              manages the LAN ManagerC                                              user accounts databasen  G         SYS$SYSTEM:PWRK$MOP_MANAGER.EXE      MOP Remote Boot Management 4                                              utility  D         SYS$SYSTEM:PWRK$NET.EXE              LAN Manager NET utility  D         SYS$SYSTEM:PWRK$NET_DAEMON.EXE       LAN Manager NET utility;                                              helper programD  G         SYS$SYSTEM:PWRK$PCSA_MANAGER.EXE[1]  PCSA Manager clone for the G                                              Command Line Net interface   @         SYS$SYSTEM:PWRK$PCSA_RMI.COM[1]      Remote PCSA_MANAGER5                                              commands   G         SYS$SYSTEM:PWRK$SHOWINI.EXE[2]       Show LANMAN.INI Parameters 4                                              utility  @         SYS$SYSTEM:PWRK$START_PRINTERS.EXE   Utility that startsG                                              printer queues and printern9                                              destinationsB  C         SYS$UPDATE:PWRK$LANMAN.SAV[3]        Backup saveset for thei@                                              initial LAN Manager;                                              directory tree   H         SYS$UPDATE:PWRK$LMCONFIG.COM         Command procedure that setsG                                              up the initial LAN Manager ;                                              directory tree5  H         [1]This_file_is_installed_only_if_you_have_PATHWORKS_V4.x_for___  )         OpenVMS installed on your system._F         [2]This file is (or is associated with) an unsupported utility         or command procedure.S?         [3]This file is deleted after you configure the server.   H                                                 (continued on next page)  H                                                     Files Installed F-15           6      Files Created During the LAN Manager Installation    E      Table_F-2_(Cont.)_LAN_Manager_Files_____________________________v  E      File_________________________________Description________________   <      SYS$UPDATE:PWRK$PWUTIL.SAV[3]        Backup saveset for@                                           PATHWORKS client-based3                                           utilitiesx  @      SYS$UPDATE:PWRK$RPL.SAV[3]           Backup saveset for the?                                           initial RPL boot tree   E      SYS$UPDATE:PWRK$UPGRADE.COM          Command procedure that runs ?                                           the upgrade procedure_  9      SYS$UPDATE:PWRK$UPGRADE.EXE          Upgrade utilityc  D      SYS$UPDATE:PWRK$UPGRADE_LAD_TO_      Upgrade utility for Remote7      RPL.EXE[1]                           Boot database E      [1]This_file_is_installed_only_if_you_have_PATHWORKS_V4.x_for___I  &      OpenVMS installed on your system.<      [3]This file is deleted after you configure the server.E      ________________________________________________________________a  E      ________________________________________________________________a  2      Files Created During the NetWare Installation  C            Table F-3 describes the files created during the NetWareE            installation.  E      Table_F-3_NetWare_Files_________________________________________M  E      File_________________________________Description________________Y  E      PWVN$EXAMPLES:EXAMPLE.C              NetWare API program example .                                           in C  @      PWVN$EXAMPLES:EXAMPLE.COM            Command procedure thatD                                           builds the example program  E                                              (continued on next page)             F-16 Files Installed  P  W      H                            Files Created During the NetWare Installation    H         Table_F-3_(Cont.)_NetWare_Files_________________________________  H         File_________________________________Description________________  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 headeri1                                              file   G         SYS$LIBRARY:NWERRORS.H               NetWare errors header file   B         SYS$SHARE:PWVN$CACHE.EXE             NetWare cache manager<                                              shareable image  C         SYS$SHARE:PWVN$NWAPISHR.EXE          NetWare APIs shareable 2                                              image  H         SYS$STARTUP:PWVN$NVT_START.COM       Command procedure that runs;                                              the NVT daemonr  H         SYS$STARTUP:PWVN$NWCP_START.COM      Command procedure that runsH                                              the NetWare control program  H         SYS$STARTUP:PWVN$PSPAWNER_START.COM  Command procedure that runsE                                              the NetWare print server:4                                              spawner  H         SYS$STARTUP:PWVN$SERVER_START.COM    Command procedure that runs?                                              the NetWare server   A         SYS$SYSTEM:PWVN$BINDDOWN.EXE         NetWare utility thatSE                                              downloads or uploads the 4                                              bindery  H         SYS$SYSTEM:PWVN$DOSLOGIN.EXE         NetWare utility that does aE                                              login test from the host   @         SYS$SYSTEM:PWVN$NETWARE.EXE          NetWare file server  E         SYS$SYSTEM:PWVN$NVTD.EXE             NetWare Virtual Terminal.9                                              (NVT) daemonI  H                                                 (continued on next page)  H                                                     Files Installed F-17    P      2      Files Created During the NetWare Installation    E      Table_F-3_(Cont.)_NetWare_Files_________________________________e  E      File_________________________________Description________________S  >      SYS$SYSTEM:PWVN$PSERVER.EXE          NetWare print server  >      SYS$SYSTEM:PWVN$PSPAWNER.EXE         NetWare print server1                                           spawner:  @      SYS$SYSTEM:PWVN$SCONSOLE.EXE         NetWare system console  D      SYS$SYSTEM:PWVN$SLIST.EXE            NetWare utility that lists1                                           servers   D      SYS$SYSTEM:PWVN$TLIST.EXE            NetWare utility that lists8                                           trustee rights  D      SYS$SYSTEM:PWVN$ULIST.EXE            NetWare utility that lists/                                           users   @      SYS$UPDATE:PWRK$NETWARE.SAV[1]       Backup saveset for theC                                           initial NetWare directoryr.                                           tree  @      SYS$UPDATE:PWRK$NWCONFIG.COM         Command procedure thatE                                           sets up the initial NetWaret8                                           directory treeE      [1]This_file_is_deleted_after_you_configure_the_server._________l  E      ________________________________________________________________y  E      ________________________________________________________________o  +      LAN Manager and NetWare Disk Structure   ?            Figure F-1 shows the LAN Manager and NetWare on-diskC=            structure. Note that only part of the substructure >            is shown. For example, only part of the RPL on-disk<            substructure is shown; see the LAN Manager Remote?            Boot Guide for a complete diagram of the RPL on-disk             substructure.  E            The LANMAN subdirectory is only created if you install and B            configure LAN Manager. The NETWARE subdirectory is only8            created if you install and configure Netware.        F-18 Files Installed$ P  M      H                                   LAN Manager and NetWare Disk Structure                                                                                              H                                                     Files Installed F-19                       H                                                                        GH         ________________________________________________________________  H                    Logical Names for the LAN Manager and NetWare Servers      D               Table G-1 describes the logical names that are createdC               when you configure or start either the LAN Manager orS               NetWare servers.  C         Table G-1 PATHWORKS V5.0C for OpenVMS (LAN Manager) LogicalhH         __________Names_________________________________________________  H         Logical_name__________Description_______________________________  E         PWRK$ADDON_LIBRARY    Location of PATHWORKS file system addon '                               libraries_  E         PWRK$COMMON           Location of EVTLOG.DAT and PWMONUAF.DAT_#                               files   D         PWRK$COMMONROOT[1]    Root of the PATHWORKS common directory"                               tree  =         PWRK$LANMAN[3]        Location of the LANMAN.INI file   B         PWRK$LICENSE          PATHWORKS license database directory  G         PWRK$LMLOGS[3]        Log file area for LAN Manager controller, F                               daemon, file server, and RPL Remote Boot$                               server  9         PWRK$LMREPLEXPORT[2,3]Replicator export directorya  9         PWRK$LMREPLIMPORT[2,3]Replicator import directory   D         PWRK$LMROOT[1]        Root of the LAN Manager directory tree  ?         PWRK$LMUPGRADE[3]     Log file area for upgrade reportse  H         [1]This_logical_name_requires_that_you_specify_the_directory____           with it.:         [2]Supported as a location for logon scripts only.=         [3]This logical name is defined for LAN Manager only.   H                                                 (continued on next page)  H                Logical Names for the LAN Manager and NetWare Servers G-1           :      Logical Names for the LAN Manager and NetWare Servers    @      Table G-1 (Cont.) PATHWORKS V5.0C for OpenVMS (LAN Manager)E      __________________Logical_Names__________________________________  E      Logical_name__________Description________________________________  D      PWRK$LOGS             Log file area for master process, network?                            transports, license servers, and thel7                            server configuration utilityo  A      PWRK$NETWARE          Location of NetWare configuration file $                            templates  =      PWRK$NWROOT[1]        Root of the NetWare directory tree_  C      PWRK$PARAMS           Location of data files PWRK$CURRENT.DAT,_D                            PWRK$ACTIVE_nodename.DAT, PWRK$MODPARAMS_;                            nodename.DAT, and PWRK$AGEN_REQ_ '                            nodename.DAT   =      PWRK$PERFDATA         PATHWORKS monitor performance data $                            directory  ?      PWRK$PRINT            PATHWORKS printer database directoryR  E      PWRK$RPLROOT[1,3]     Root of the RPL Remote Boot directory tree[  ;      PWRK$ROOT[1]          Search list of PWRK$COMMONROOT:, 8                            PWRK$LMROOT: and PWRK$NWROOT:  A      PWRK$SECTION          Virtual memory section files directory   2      PWRK$SPOOL            Printer spool directory  E      PWRK$TEMP             Scratch disk area for temporary operations E      [1]This_logical_name_requires_that_you_specify_the_directory____E  
      with it.M:      [3]This logical name is defined for LAN Manager only.E      ________________________________________________________________             >      G-2 Logical Names for the LAN Manager and NetWare Servers L  M                  H                                                                        HH         ________________________________________________________________  H                                Logical Names for the NetWare Server Only      H               This appendix describes the logical names that are createdB               only for the PATHWORKS for OpenVMS (NetWare) server.    H         ________________________________________________________________  -         How NetWare Logical Names Are Created   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 otherlE               command procedures to generate logical names. Table H-1nG               lists these command procedures and describes the types of *               logical names they generate.                          H                            Logical Names for the NetWare Server Only H-1    F      #      Types of NetWare Logical Namesa    E      Table_H-1_Types_of_NetWare_Logical_Names_________________________  '                                 Type of_E      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 aSE      LOGICALS.COM_________________________particular_node.___________       E      ________________________________________________________________P  !      Common NetWare Logical Nameso  B            Table H-2 describes common logical names defined by the.            PWVN$COMMON_LOGICALS.COM procedure.  E      Table_H-2_Common_NetWare_Logical_Names__________________________   E      Logical_Name____________Description_____________________________t  D      PWVN$CONFIGURED_LIST    A list of the nodes that are configured+                              on the cluster   E      PWVN$EXAMPLES           The directory location for example files   A      PWVN$GUEST_ACCOUNT      The name of the GUEST account on the (                              file server  C      PWVN$GUEST_UIC          The User Identification Code (UIC) forKA                              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 Volume   %      PWVN$UPGRADE            Obsoletea  E                                              (continued on next page)u  2      H-2 Logical Names for the NetWare Server Only a  e      H                                             Common NetWare Logical Names    H         Table_H-2_(Cont.)_Common_NetWare_Logical_Names__________________  H         Logical_Name____________Description_____________________________  C         PWVN$IPX_SOCKETS[1]     The number of available IPX socketsi  C         PWVN$SPX_SOCKETS[1]     The number of available SPX socketsr  G         PWVN$NVT_USERS[1]       The maximum number of users who can loguH                                 in through Novell Virtual Terminal (NVT)H         [1]This_logical_name_is_added_by_the_configuration_procedure.___  H         ________________________________________________________________  H         ________________________________________________________________  %         Private NetWare Logical Namesh  F               Table H-3 describes private logical names defined by the2               PWVN$PRIVATE_LOGICALS.COM procedure.    H               Table_H-3_Private_NetWare_Logical_Names___________________  H               Logical_Name_______Definition_____________________________  F               PWVN$CONF_DIR      The directory location for the server4                                  configuration files  E               PWVN$ENET_DEVS     The names of the Ethernet controller ;                                  devices used by the serveri  ?               PWVN$LOGFILES      The directory location for theTD                                  PATHWORKS for OpenVMS (NetWare) log&                                  files  E               PWVN$NVT           A flag that indicates whether Novell H                                  Virtual Terminal (NVT) is configured on+                                  the server   <               PWVN$SERVER_NAME   The name of the file server  H                                                 (continued on next page)    H                            Logical Names for the NetWare Server Only H-3 i  y      "      Private NetWare Logical Names    E            Table_H-3_(Cont.)_Private_NetWare_Logical_Names___________   E            Logical_Name_______Definition_____________________________   E            PWVN$TUNNEL        A flag that indicates whether tunnelingiE            ___________________is_enabled_____________________________o                                                                              2      H-4 Logical Names for the NetWare Server Only                           H         ________________________________________________________________  H                                                                 Glossary                     back up (v.)  C               To copy the contents of an entire disk, directory, or                file.o                 backup (n.)e  E               A copy of the contents of an entire disk, directory, or                file.                  bindery (n.)  A               A database that contains information about existing5E               objects such as user, groups, workgroups, file servers,                 and print servers.                 client (n.)_  B               A personal computer or workstation, connected to theD               network with PATHWORKS for OpenVMS (NetWare), that canE               access resources on a server. A NetWare client can haves,               DOS software. See also server.                 configure (v.)  E               To select, install, and customize hardware and software (               for a computer or network.                 CPU (n.)  B               Central processing unit. The main unit of a computerC               that contains the circuits controlling interpretationAF               and execution of instructions. The CPU includes the main>               storage, arithmetic unit, and special registers.  H                                                               Glossary-1 H  K                        DECnet (n.)  C            Digital networking software that runs in both local areatB            and wide area networks. With DECnet, different types ofA            computers that have different operating systems can be_C            connected, and users can access information and servicesa             on a remote computer.  B            DECnet is a networking protocol and transport. See also            TCP/IP.              default (n.)_  D            The value assumed by a program if a value is not supplied            by the user.Y              directory (n.)E  C            A list of a set of files stored on a storage device such             as a file server.              Ethernet (n.)  C            A CSMA/CD system used for local communications networks. D            An Ethernet network uses coaxial cable developed by Xerox3            Corporation's Palo Alto Research Center.e               Ethernet address (n.)  <            An alphanumeric string, six bytes in length, thatE            identifies a node on the Ethernet. The string is six pairs_D            of hexadecimal digits, separated by hyphens (for example,            AA-00-04-00-91-27).              file server (n.)n  D            A network program that lets a client connect to available#            file and print services.E              group (n.)   >            In system administration, a collection of users whoA            have the same access to file services. Once users havel>            accounts, they can be assigned to a group. With oneB            command, the system administrator can assign and modify-            access for all users in the group.         Glossary-2l                                 hexadecimal (adj.)  F               Pertaining to a number system using base 16. HexadecimalG               notation includes the numbers 0 through 9 and the lettersbF               A through F. In base 10 (decimal notation), F equals 15.                 host system (n.)  E               A computer, such as a server, that provides services to                clients.  *               internal network number (n.)  F               In PATHWORKS for OpenVMS (NetWare), a unique hexadecimalH               number that is assigned to a file server. This number must               be:r  ?               -  Different from the the external network numbere  ,               -  Unique for each file server  &               See also network number.                 Internet (n.)   A               A group of networks that includes regional networksd?               and local networks at universities and commercial 7               institutions. See also DECnet and TCP/IP.E  #               Internet address (n.)   B               A 32-bit number identifying a host connection on theH               Internet. An Internet address consists of a network number               and host number.  )               Internet Protocol (IP) (n.)   G               A protocol that determines how data is sent from one hostWC               to another on the Internet. The IP also specifies theE%               format of IP datagrams..                 network (n.)  ?               A group of servers, clients, and devices that are F               connected to each other by communications lines to share(               information and resources.  H                                                               Glossary-3 b  F                        network number (n.)  C            In PATHWORKS for OpenVMS (NetWare), a hexadecimal number_A            that is assigned to the Ethernet segment that the filerC            server is connected to. Each client or server that is onrE            the same Ethernet segment shares the same external networkS4            number. See also internal network number.              node (n.)  C            An individual computer, such as a server or client, that =            can communicate with other computers in a network.E              password (n.)  E            A string of characters that uniquely confirms the identity 7            of a user to the system. See also user name.               segment (n.)   A            In an Ethernet network, a length of coaxial cable made1A            up of one or more cable sections connected with barrel &            connectors or T-connectors.              server (n.)  <            A computer on the network that controls access to@            resources such as files, printers, and communications4            devices. See also client and host system.              shutdown (n.)  @            The command used on an ULTRIX system to shut down the            network._  $            standalone license server  B            The term used to refer to the configuration of softwareE            that includes the license server without the file servers.              See also file server.              TCP/IP (n.)  A            Transmission Control Protocol/Internet Protocol. A set A            of protocols that governs the transport of information B            between computers and networks of dissimilar types. TheA            Internet is a group of networks that includes regionalsE            networks and local networks at universities and commercialo        Glossary-4     c            B               institutions. TCP/IP is an alternative to the DECnet1               network transport. See also DECnet.                  user name (n.)  B               The name a user types when logging in to the system.D               The combination of the user name and password uniquely?               identifies a user account to the system. See also                password.-                                                                        H                                                               Glossary-5 _  _                          E      ________________________________________________________________s  E                                                                 Indext    :      A                                    Complete upgrade;      ___________________________           See also Upgrade :      Additional Upgrade                    described,  7-57         Utilities menu, 7-35              Computer name_A      ADMIN account                         SCSNODE parameter and,_2        password on, 3-3                       1-14A      Alerter service                      Configuration procedure D        described, 3-6                      for LAN Manager, defined,1      alias,  3-8                              3-1 E      Alpha system                          for NetWare, defined,  4-1yA        operating system                    getting help for,  4-6 =          requirements,  1-7                interrupting,  4-6 D      Automatic shutdown                    preparing for the NetWare4        of file server, 8-9                    ,  4-5  >                                            prerequisites,  3-3=      B__________________________           questions in,  4-6R  A      BACKUP command,  1-10                 responding to prompts,e<      Backup domain controller                 3-11, 4-6, 5-48        described, 7-47                     running,  4-5B      Backward compatibility                sample script for,  D-1<        enabling, 3-4                       sample script forB                                               combined LAN Manager?      C__________________________              and NetWare,  C-6y@      Client licenses                       sample script for LAN;        described, 1-2                         Manager,  A-5gD      Client software                       sample script for NetWare4        LAN Manager, 1-8                       ,  B-5<        NetWare, 1-8                        sample script for@      Common logical names                     standalone license:        described, H-2                         server,  D-4:                                            starting,  3-11  E                                                               Index-1     l            :      Configuration procedure              Device name, 2-37         (cont'd)                          Disk services ;        starting server during,             upgrading,  7-48 4          3-9, 3-16, 4-12, 5-6,            Disk space=          5-12                              determining,  1-11 B        storage of old values in,          Disk space requirements,0          4-15                               1-119      Configuration utility, LAN            for XQP+,  9-3P6         Manager                           Domains, 3-68        described, 3-8                      defined,  7-2  +        running after                      ERE          configuration procedure          ___________________________eE          ,  3-8                           eXtended Qio Processor Plus   3      Container files,  7-48                See XQP+ B      Create Upgrade Reports               External network numbersB         menu, 6-12                         configuration and,  4-3        Custom upgradedE        See also Upgrade                   F__________________________t  A        described, 7-5                     File and Print Servicesg  2                                             reportC      D__________________________           See also Upgrade reports   E      Data loss                             as input to upgrade,  7-7,M2        preventing, 1-10                       7-10:      DECnet,  1-7                          described,  6-59      DECnet transport                      editing,  6-20 7        status of, 1-17                     sample,  E-5e/      DECprint Supervisor                  FileseC         software, 2-18                     created by installation,e1      Default answers                          F-1 5        for configuration                  File server_<          procedure,  4-6                   configuring,  4-1?        for installation                    reconfiguring,  4-14s9          procedure,  2-6                   starting,  8-4c9      Default settings                      stopping,  8-9w          changing, 3-16.E      Deinstallation procedure             G___________________________<        described, 10-2                    GBLPAGES parameterA        guidelines for, 10-1                checking and defining, 2        responding to prompts,                 1-12
          10-3n        starting, 10-2h        Index-2 r  a            B         Group Merge screen, 7-21,           Installation procedure7           7-28                                 (cont'd)s?         Groups report                         sample script forW  C          See also Upgrade reports                standalone license_<          as input to upgrade,  7-7,              server, D-1<             7-9                               starting,  2-4E          described,  6-4                    Installation Verificationl8          editing,  6-19                        Procedure5          sample,  E-3                         See IVP 6          Users report as input to,          InstallingB             6-12                              license server,  5-1  D         H                                   Internal network numbersE         ___________________________           configuration and,  4-3_>         Hardware requirements,              IPX DECnet tunnels;           1-6, 1-9                            defined,  4-4e/         Help                                IVPc;          for configuration                    running after_B             procedure,  4-6                      installation, 8-2D         Host-based security, 7-3              running automatically,5                                                  2-11 #         I__________________________SG         Installation                        K__________________________C  8          files created by,  F-1             Kit contents<          logical names created by,            checking,  1-9             G-1iG         Installation kit                    L__________________________ /          contents of,  2-2                  LANTE         Installation procedure                number of networks on ah<          described,  2-1                         server, 4-47          interrupting,  2-6                 LAN Manager(D          logical names and,  H-1              computer name defined,4          prerequisites,  2-3                     3-6G          questions in,  2-6                   domain name defined,  3-6eF          responding to prompts,               on-disk structure,  F-18D             2-6                               other domains defined,4          sample script for                       3-6B             combined LAN Manager              security modes,  3-6F             and NetWare,  C-1                 supported features,  7-2F          sample script for LAN              LAN Manager deinstallation8             Manager,  A-1                      procedure;          sample script for NetWare            sample,  10-5)             ,  B-1  H                                                                  Index-3 _  _            A      LAN Manager security,  7-3           NOS-based security, 7-3_        upgrading to, 7-34_E      License server                       O__________________________ ;        defined, 3-4                       OpenVMS files and 7        installation procedure,              directories A          5-1                               upgrading security on,_2      Licensing,  1-2                          7-34:      Local server                         Operating system>        Groups report and, 6-4               requirements,  1-7A        Users report and, 6-3              Optional software, 2-17e
      Log filet        for upgrade, 7-7, 7-10,E          7-15, 7-30                       P__________________________L  6      Logical names                        Part listing9        common, H-2                         checking,  1-9 D        created by installation,           PATHWORKS VMScluster alias8          G-1                               defined,  3-8A        creation of, H-1                   Postinstallation tasks, /        private, H-3                         8-1 >        redefined, 4-15                     configuration,  4-2@        startup procedure, 8-4             Preinstallation tasks,4        types of, H-1                        1-9, 2-3>      Logon validation                      checklist for,  1-8C        defined, 7-2                       Primary domain controller_  B                                            Groups report and,  6-4A      M__________________________           Users report and,  6-3e?      Member server                        Private logical names_:        described, 7-47                     described,  H-3?      Memory requirements,  1-8            PROCSECTCNT parametermA      Mixed architecture                    checking and defining, 2         VMSclusters, 1-18, 1-19,              1-13A         3-2                               Product identifier, 2-3   ?                                           PWRK$CONFIG procedure   <      N__________________________           See Configuration7      NetWare deinstallation                   procedure   A         procedure                         PWRK$DEINSTAL procedure   =        sample, 10-5                        See Deinstallation 7      Network numbers                          procedure D        configuration and, 4-3             PWRK$SHOSYS procedure, 6-6B      Network transport                    PWRK$SHUTDOWN procedure,/         requirements, 1-7                   6-7c        Index-4                 ?         PWVN$COMMON_LOGICALS.COM            Same-name conflictss7           procedure                            (cont'd) D          logical names created by,            with group names, in aG             H-2                                  custom upgrade without >         PWVN$CONFIG.COM procedure                reports, 7-26D          described,  4-2                      with group names, in a@          logical names and,  H-1                 UAS merge, 7-45A         PWVN$PRIVATE_LOGICALS.COM             with user names, inuC           procedure                              a complete upgradeiF          logical names created by,               without reports, 7-17C             H-3                               with user names, in aDG         PWVN$STARTUP.COM                         custom upgrade withoutw>          described,  8-4                         reports, 7-24G         PWVN$STARTUP.COM procedure            with user names, in a UASt<          logical names and,  H-1                 merge, 7-41  =         Q                                   SCSNODE parameterc=         ___________________________           defining,  1-14f:         Queue manager                       Security,  7-2?          starting,  1-16                      share-level,  3-6r  B                                               upgrading on OpenVMSG         R__________________________              files and directories,   5         Release notes, 2-3, 2-7                  7-34n>          printing,  1-5                       user-level,  3-62         Remote Boot service                 ServerB          described,  3-5                      displaying PATHWORKSB         Remote server management                 processes on, 6-6=          defined,  7-3                        starting during D         Required hardware, 1-6                   configuration, 3-9,F         Required software, 1-7                   3-16, 4-12, 5-6, 5-12<         Requirements                          stopping,  6-7B          disk space,  1-11                  Server Admin interface=             for XQP+,  9-3                    starting,  7-49 C          hardware,  1-6, 1-9                Server Admin Main menu, 3          memory,  1-8                          7-49eC          software,  1-7, 1-10               Server announce comment   ;                                               defined,  3-7-;         S__________________________         Server commands   @         Same-name conflicts                   defining at system=          with group names, in                    startup, 8-6h;             a complete upgrade              Server licensest=             without reports,  7-19            described,  1-2   H                                                                  Index-5    e            =      Server startup,  8-5                 System startup fileWD      Share-level security,  3-6            editing,  2-16, 5-14, 8-6        defined, 7-2aE      SHOW SYSTEM command,  1-16           T__________________________D;      Shutdown procedure                   Task summary, xvi 5        for file server, 8-9               TCP/IP, 1-7l<      Software requirements,               Timesource service:         1-7, 1-10                          described,  3-5@      Standalone license server,           Tunnel network numbersB         1-3, 5-1                           configuration and,  4-3      Standalone license serverE         configuration procedure           U__________________________ =        sample, D-1                        UAS merge procedureu;      Standalone license server             described,  7-35t<         startup, 5-13                      performing,  7-40:      Standalone server                    UAS Merge reportA        changing role of, 7-36,             as input to UAS merge,o2          7-47                                 7-41:      Standalone UAS Merge menu,            creating,  7-37;         7-37                               described,  7-36i@      Starting up the standalone            displaying in upgrade>         license server, 5-13                  procedure,  7-389      START/QUEUE/MANAGER command           editing,  7-38 C         , 1-16                             guidelines for creating, 2      Startup procedure                        7-367        for file server, 8-4                sample,  E-6t1      SYSTEM account                       Upgradet;        logging in to, 1-10                 See also upgrade.      System backup,  1-10n7      System disk                              procedurel5        input/output on, 3-3                performing E        space needed for                       without reports,  7-14,w5          installation,  1-11                     7-22uE      System parameters                        with reports,  7-6, 7-8o<        checking and defining,              reasons for,  7-29          1-12                              types of,  7-5 @      System shutdown                       viewing log file for,C        file server shutdown and,              7-7, 7-10, 7-15, 7-30 @          8-9                              upgrade procedure, 7-1?      System startup                        creating and editingvC        defining server commands               upgrade reports with, 1          at,  8-6                             6-1s:                                            described,  3-9          Index-6                 ?         upgrade procedure (cont'd)          VMScluster (cont'd)n  H          displaying reports in,               starting server in,  5-15,4             6-13, 7-38                           8-7C          getting help for,  6-11              XQP+ installation in,r5          Main menu,  6-10                        9-15 5          navigating,  6-11                  VMSINSTALe=          prerequisites,  6-6                  described,  2-1s@          starting,  6-7                       kit contents,  2-2?         Upgrade procedure                   VMSINSTAL procedure >          described,  7-3                      See Installation:         Upgrade reports                          procedure          creating,  6-1, 6-12 -          described,  6-2                    XeG          displaying in upgrade              ___________________________q7             procedure,  6-13                XQP+,  2-18eA          editing,  6-15                       deinstalling,  9-11 =          location of,  6-14                   described,  9-2 D          names of,  6-14                      disk space required to=          types of,  6-2                          install, 9-3_F         User accounts                         installation guidelines,4          duplicate,  6-3                         9-3>         User-level security, 3-6              installing,  9-3;          defined,  7-2                        responding to F         User Merge screen, 7-18,                 installation prompts,4           7-25                                   9-4A         Users report                          sample installation   F          See also Upgrade reports                procedure, 9-13, 9-15"          as input to Groups report             ,  6-12r#          as input to upgrade,  7-6,3             7-9           described,  6-3          editing,  6-15           sample,  E-1   #         V__________________________            VAX system          operating system              requirements,  1-7         VMScluster           installation in,  1-18,             3-10"          PATHWORKS alias for,  3-8  H                                                                  Index-7                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        