                 1                      Compaq PATHWORKS for OpenVMS @                      Server Installation and Configuration Guide  .                      Order Number: AA-R6G1C-TE    !                      October 2001   E                      This guide explains how to install and configure @                      the PATHWORKS for OpenVMS (Advanced Server)F                      software, including the standalone License ServerB                      and external authentication software, and the%                      Upgrade utility.           G                      Revision/Update Information: This guide supersedes F                                                   the Compaq PATHWORKSG                                                   for OpenVMS (Advanced @                                                   Server) ServerB                                                   Installation andF                                                   Configuration Guide,?                                                   Version 6.0B.   G                      Operating System:            OpenVMS Alpha Version D                                                   6.2, 7.2-1, 7.2-2,5                                                   7.3 E                                                   OpenVMS VAX Version ?                                                   6.2, 7.2, 7.3   D                      Software Version:            PATHWORKS V6.1 forC                                                   OpenVMS (Advanced 9                                                   Server)         0                      Compaq Computer Corporation#                      Houston, Texas                  H               __________________________________________________________  0                2001 Compaq Computer Corporation  H               COMPAQ, the Compaq logo, OpenVMS, Tru64, DECnet, VAX, VMS,G               and the DIGITAL logo are trademarks of Compaq Information &               Technologies Group, L.P.  G               Microsoft, MS-DOS, Windows, and Windows NT are trademarks '               of Microsoft Corporation. 8               Intel is a trademark of Intel Corporation.4               UNIX is a trademark of The Open Group.    H               All other product names mentioned herein may be trademarks,               of their respective companies.  G               Confidential computer software. Valid license from Compaq B               required for possession, use, or copying. ConsistentG               with FAR 12.211 and 12.212, Commercial Computer Software, E               Computer Software Documentation, and Technical Data for H               Commercial Items are licensed to the U.S. Government under3               vendor's standard commercial license.   C               Compaq shall not be liable for technical or editorial C               errors or omissions contained herein. The information C               in this document is provided "as is" without warranty B               of any kind and is subject to change without notice.A               The warranties for Compaq products are set forth in B               the express limited warranty statements accompanyingB               such products. Nothing herein should be construed as2               constituting an additional warranty.  H                                                                   ZK6555  G               The PATHWORKS for OpenVMS (Advanced Server) documentation )               set is available on CD-ROM.   C               This document was prepared using DECdocument, Version                3.3-1b.                                E      ________________________________________________________________   E                                                              Contents     E      Preface..................................................     xi     4      1  Before You Install PATHWORKS Advanced Server  9            1.1   About the PATHWORKS for OpenVMS Software E                  Kit..........................................    1-1 >            1.1.1     About the PATHWORKS for OpenVMS (NetWare)E                      Server...................................    1-2 9            1.2   If You Are Upgrading from PATHWORKS (LAN E                  Manager).....................................    1-2 E            1.3   Installing DECprint Software.................    1-2 E            1.4   About Licensing..............................    1-3 E            1.4.1     License Requirements.....................    1-3 E            1.4.2     About the License Server.................    1-4 E            1.5   About External Authentication................    1-5 E            1.6   Reading the Release Notes....................    1-6 E            1.6.1     How to Access the Release Notes..........    1-6 E            1.7   Using the Installation Checklist.............    1-7 6            1.8   Requirements for Installing PATHWORKSE                  Advanced Server Software.....................    1-7 E            1.8.1     Hardware Requirements....................    1-7 E            1.8.2     Software Requirements....................    1-8 E            1.8.3     Supported Client Software................    1-8 E            1.8.4     Memory Requirements......................    1-8 E            1.9   Preinstallation Tasks........................    1-9 E            1.9.1     Step 1: Check the Part Listing...........   1-10 E            1.9.2     Step 2: Check the Network Hardware.......   1-10 E            1.9.3     Step 3: Log In to the SYSTEM Account.....   1-10 E            1.9.4     Step 4: Check the Required Software......   1-11 7            1.9.5     Step 5: Print and Read the Release E                      Notes....................................   1-11 E            1.9.6     Step 6: Check System Parameters..........   1-11   E                                                                   iii                  H               1.9.7     Step 7: Check ENQLM Process Quota........   1-16H               1.9.8     Step 8: Back Up the System...............   1-17H               1.9.9     Step 9: Check Disk Space Requirements....   1-17H               1.9.10    Step 10: Check the Queue Manager.........   1-17H               1.9.11    Step 11: Check Time Zone and TDF.........   1-18H               1.9.12    Step 12: Check DECnet Status.............   1-19H               1.9.12.1    Checking DECnet (Phase IV) Status......   1-19H               1.9.12.2    Checking DECnet-Plus Status............   1-19H               1.9.13    Step 13: Check TCP/IP Status.............   1-20;               1.9.14    Step 14: Check for Existing OpenVMS H                         Server Images and Files..................   1-216               1.9.15    Step 15: Check OpenVMS ClusterH                         Configuration............................   1-21H               1.10  Next Step....................................   1-23    3         2  Installing the PATHWORKS Advanced Server   H               2.1   About the Installation Procedure.............    2-1H               2.1.1     What is VMSINSTAL?.......................    2-1>               2.1.2     PATHWORKS Advanced Server InstallationH                         Kit......................................    2-2H               2.1.3     What VMSINSTAL Does......................    2-2H               2.2   Installing the Server........................    2-2H               2.2.1     Before You Start VMSINSTAL...............    2-3H               2.2.2     How to Respond to Prompts................    2-6H               2.2.3     How to Start VMSINSTAL...................    2-69               2.2.4     What To Do After the Installation H                         Completes................................   2-25H               2.3   Troubleshooting Installation Problems........   2-26?               2.3.1     Installing PATHWORKS Advanced Server on @                         a System Running Another Advanced ServerH                         Image....................................   2-26@               2.3.2     Installing the PATHWORKS Advanced ServerH                         on a System with the NetWare Server......   2-26A               2.3.3     Installing PATHWORKS Advanced Server on a H                         System with PATHWORKS (LAN Manager)......   2-27@               2.3.4     Installing the Standalone License Server@                         on a System Where the PATHWORKS AdvancedH                         Server Has Been Installed................   2-27>               2.3.5     Installing the External AuthenticationH                         Software.................................   2-28H               2.4   Next Steps...................................   2-28    
         iv                 4         3  Configuring the PATHWORKS Advanced Server  ;               3.1   About the Advanced Server Configuration H                     Procedure....................................    3-1H               3.1.1     What the Configuration Procedure Does....    3-28               3.2   Before You Start the Advanced ServerH                     Configuration Procedure......................    3-3:               3.2.1     On What OpenVMS Disk Device Do You>                         Want to Store the Advanced Server DataH                         Files?...................................    3-38               3.2.2     Do You Want to Change the SystemH                         Configuration Parameters Now?............    3-4=               3.2.2.1     Configuring Transports for a Backup H                           Domain Controller or Member Server.....    3-5?               3.2.3     Do You Want to Change Any of the Server H                         Configuration Settings?..................    3-8:               3.2.4     What Do You Want the AdministratorH                         Account Password to Be?..................   3-11@               3.2.5     Are You Going to Supply Account/PasswordH                         Information?.............................   3-118               3.2.6     What Is the Domain AdministratorH                         Password?................................   3-12@               3.2.7     Do You Want to Enter a New AdministratorH                         Account Password?........................   3-12H               3.2.8     Do You Want to Start the Server?.........   3-124               3.3   How to Start the Advanced ServerH                     Configuration Procedure......................   3-135               3.4   How to Respond to Advanced Server H                     Configuration Prompts........................   3-137               3.5   How to Change Default Configuration H                     Settings.....................................   3-19:               3.6   Configuring the Advanced Server DomainH                     Role.........................................   3-21<               3.6.1     Configuring the Advanced Server as aH                         Member Server............................   3-25>               3.6.1.1     Configuring a New PATHWORKS AdvancedH                           Server as a Member Server..............   3-26;               3.6.1.2     Configuring an Existing PATHWORKS 9                           Advanced Server BDC As a Member H                           Server.................................   3-29;               3.7   Troubleshooting Configuration Procedure H                     Problems.....................................   3-30      H                                                                        v                 @               3.7.1     Ensuring Sufficient Resources to SupportH                         Clients..................................   3-30@               3.7.2     If Problems Occur When Reconfiguring theH                         Advanced Server..........................   3-31H               3.8   The Advanced Server Network Adapter..........   3-31H               3.8.1     Manually Defining the Network Adapter....   3-32@               3.8.2     What to Do If the Network Adapter Is NotH                         Found....................................   3-33H               3.9   Next Steps...................................   3-35    A         4  Configuring and Starting the Standalone License Server   H               4.1   About the License Server.....................    4-1@               4.2   Before You Begin to Configure the StandaloneH                     License Server...............................    4-2H               4.3   Configuring the Standalone License Server....    4-3H               4.4   Configuring the Transports...................    4-34               4.5   How to Respond to License ServerH                     Configuration Prompts........................    4-4H               4.6   How to Start the Standalone License Server...    4-67               4.6.1     How to Start the License Server H                         Manually.................................    4-67               4.6.2     How to Start the License Server H                         Automatically............................    4-6=               4.6.3     How to Start the License Server in an H                         OpenVMS Cluster..........................    4-7  :         5  After You Install the PATHWORKS Advanced Server  H               5.1   Before You Begin Postinstallation Tasks......    5-1A               5.2   Verifying the PATHWORKS for OpenVMS (Advanced H                     Server) Installation.........................    5-3H               5.3   Starting the PATHWORKS Advanced Server.......    5-4<               5.3.1     When to Start the PATHWORKS AdvancedH                         Server...................................    5-4H               5.3.2     What the Startup Procedure Does..........    5-4;               5.3.3     How to Start the PATHWORKS Advanced H                         Server Manually..........................    5-5;               5.3.4     How to Start the PATHWORKS Advanced H                         Server Automatically.....................    5-5;               5.3.5     How to Start the PATHWORKS Advanced H                         Server in an OpenVMS Cluster.............    5-5H               5.3.6     Troubleshooting the Startup..............    5-7  
         vi                 H               5.4   Stopping the PATHWORKS Advanced Server.......    5-7;               5.4.1     When to Stop the PATHWORKS Advanced H                         Server...................................    5-7:               5.4.2     How to Stop the PATHWORKS AdvancedH                         Server...................................    5-7A               5.4.3     How to Stop the PATHWORKS Advanced Server H                         on System Shutdown.......................    5-8;               5.5   How to Define PATHWORKS Advanced Server H                     Commands When You Log In.....................    5-8H               5.6   Setting Up External Authentication...........    5-8=               5.6.1     Setting Up External Authentication in H                         OpenVMS Clusters.........................   5-12?               5.6.2     Requirement for External Authentication H                         Over DECnet-Plus.........................   5-14;               5.6.3     Configuring the Server Capacity for H                         External Authentication..................   5-14>               5.6.4     Bypassing External Authentication WhenH                         the Network Is Down......................   5-15H               5.6.5     Disabling External Authentication........   5-15=               5.7   Installing Optional Server Administration H                     Tools........................................   5-16    +         6  Implementing a Wide Area Network   H               6.1   Enabling Wide Area Networking................    6-18               6.2   Using the LMHOSTS File for Wide AreaH                     Networking...................................    6-2H               6.2.1     Setting up a TCP/IP Wide Area Network....    6-2H               6.2.2     The LMHOSTS Directory....................    6-3H               6.2.3     LMHOSTS File Syntax......................    6-4H               6.2.4     Managing the LMHOSTS File................    6-7H               6.2.5     Using the LMHOSTS Log File...............    6-8H               6.3   Using WINS in a Wide Area Network............    6-8;               6.3.1     Setting up WINS Support for OpenVMS H                         Clusters.................................    6-9H               6.4   Using DNS in a Wide Area Network.............    6-9                H                                                                      vii                 6         7  Removing PATHWORKS Advanced Server Software  <               7.1   PATHWORKS Advanced Server DeinstallationH                     Command Procedure............................    7-2;               7.1.1     Using the PATHWORKS Advanced ServereH                         Deinstallation Procedure.................    7-38               7.1.2     Sample PATHWORKS Advanced ServerH                         Deinstallation Procedure.................    7-4H               7.2   Removing the PATHWORKS NetWare Server........    7-5<               7.2.1     Sample NetWare Server DeinstallationH                         Procedure................................    7-6  -         A  Installation and Upgrade Checklist     @         B  Sample Complete Server Installation and Configuration  H               B.1   Sample Server Installation...................    B-1H               B.2   Sample Server Configuration..................    B-4  <         C  Sample Standalone License Server Installation and            Configuration  4               C.1   Sample Standalone License ServerH                     Installation.................................    C-14               C.2   Sample Standalone License ServerH                     Configuration................................    C-3  '         D  Upgrade Utility Installation,  H               D.1   Installing the Upgrade Utility...............    D-1H               D.2   Sample Upgrade Utility Installation..........    D-2  6         E  Sample External Authentication Installation  ;               E.1   Sample External Authentication Software H                     Installation.................................    E-1                         viii c  a            @         F  PATHWORKS Advanced Server Files and On-Disk Structure  H               F.1   PATHWORKS Advanced Server Files..............    F-15               F.2   PATHWORKS Advanced Server On-DiskcH                     Structure....................................   F-15  2         G  PATHWORKS Advanced Server Logical Names    
         Indexc             Examples  H               2-1       Sample Installation Procedure-Part 1.....    2-8  H               2-2       Sample Installation Procedure-Part 2.....   2-10  H               2-3       Sample Installation Procedure-Part 3.....   2-11  H               2-4       Sample Installation Procedure-Part 4.....   2-13  H               2-5       Sample Installation Procedure-Part 5.....   2-15           Figuresc  9               F-1       PATHWORKS Advanced Server On-DiskfH                         Structure Diagram........................   F-16           Tables  H               1-1       Preinstallation Checklist................    1-9  H               1-2       GBLPAGES Parameter Minimum Value.........   1-12  H               1-3       GBLSECTIONS Parameter Minimum Value......   1-13  H               1-4       PROCSECTCNT Parameter Minimum Value......   1-14  H               2-1       Installation Questions...................   2-16  ?               3-1       PATHWORKS Advanced Server Configuration_H                         Prompts..................................   3-14  H               3-2       Configuration Settings...................   3-19  A               3-3       Advanced Server Roles in Different DomaineH                         Types....................................   3-22  H               3-4       Methods for Changing Server Roles........   3-24  H               3-5       OpenVMS Network Adapter Logicals.........   3-32  H               3-6       Undefined Adapter Messages...............   3-34  H               4-1       License Server Configuration Prompts.....    4-4  H                                                                       ix 1               ;               5-1       Steps That Must Be Completed BeforeAH                         Postinstallation.........................    5-2  <               5-2       IVP Indications and Steps You ShouldH                         Take.....................................    5-3  9               5-3       Starting the Server in an OpenVMS H                         Cluster..................................    5-6  H               7-1       PWRK$DEINSTAL Prompts....................    7-4  H               7-2       PWVN$DEINSTAL Prompts....................    7-5  H               A-1       Installation and Upgrade Checklist.......    A-2  9               F-1       Files Installed for the PATHWORKSrH                         Advanced Server..........................    F-1  9               G-1       PATHWORKS Advanced Server Logical3H                         Names....................................    G-1                                                  	         x  1                         H         ________________________________________________________________  H                                                                  Preface      B               This guide explains how to install and configure the*               following PATHWORKS servers:  G               o  PATHWORKS for OpenVMS (Advanced Server) file and printS                  server   4               o  PATHWORKS standalone License Server  %               o  Upgrade utility only6  6               o  External authentication software only           Intended Audience   C               This guide is written for OpenVMS system managers and H               network server administrators. It assumes you are familiarH               with the following aspects of the Compaq OpenVMS operating               system:h  /               o  Digital Command Language (DCL)   2               o  A text editor, such as EDT or EVE  ,               o  VMSINSTAL command procedure  F               This guide also assumes that you are familiar with basic6               Advanced Server and networking concepts.           Document Structure  F               The following list can help you find information in this               guide:    H                                                                       xi               H               __________________________________________________________H               Chapter_____Description___________________________________  F               Chapter 1   Describes prerequisites for the installation#                           procedure.  >               Chapter 2   Describes the installation procedure  G               Chapter 3   Describes the configuration procedure for theu3                           PATHWORKS Advanced Server   G               Chapter 4   Describes the configuration procedure for the 3                           standalone License Serveri  @               Chapter 5   Describes postinstallation tasks, suchB                           as running the Installation VerificationG                           Procedure and starting the server independent.?                           of the installation and configurationL$                           procedures  D               Chapter 6   Describes how to set up Wide Area Networks  H               Chapter 7   Describes how to remove the PATHWORKS Advanced1                           Server from your system   B               Appendix A  Provides a checklist of installation and@                           configuration tasks; you can photocopy>                           Appendix A, Installation and UpgradeE                           Checklist, and use it as a checklist as your)                           read this guide.  G               Appendix B  Shows a sample installation and configurationWE                           procedure for the PATHWORKS Advanced Servera  G               Appendix C  Shows a sample installation and configurationeE                           procedure for the standalone License Serverg  G               Appendix D  Shows a sample installation procedure for the )                           Upgrade utility   C               Appendix E  Shows a sample installation procedure forn?                           external authentication software onlyg  A               Appendix F  Lists the files that are installed with.E                           PATHWORKS Advanced Server and shows the on-.(                           disk structure  A               Appendix G  Lists the logical names created for thevH               ____________PATHWORKS_Advanced_Server_____________________           xii                           Related Documents.  B               The following manuals provide more information about-               topics discussed in this guide:u  H               __________________________________________________________H               Document______________Description_________________________  G               Compaq PATHWORKS for  Explains how to upgrade a PATHWORKS H               OpenVMS (Advanced     (LAN Manager) server to PATHWORKS V6A               Server) Server        for OpenVMS (Advanced Server)                Migration Guidea  ?               Compaq Advanced       Provides an overview of andnA               Server for OpenVMS    introduction to the PATHWORKSl@               Concepts and          Advanced Server software andF               Planning Guide        associated networking concepts forG                                     system administrators and operatorsa  H               Compaq PATHWORKS for  Explains how to manage and customizeA               OpenVMS (Advanced     the PATHWORKS Advanced Server ,               Server) Server        software               Administrator's.               Guide   H               Compaq Advanced       Provides command syntax descriptionsG               Server for OpenVMS    for all ADMINISTER commands and NETo7               Commands Reference    command equivalents                Manual  @               Compaq Advanced       Describes the License ServerH               Server for OpenVMS    software and how to manage PATHWORKSA               Guide to Managing     for OpenVMS (Advanced Server).,               Advanced Server       licensesH               Licenses__________________________________________________  B               The following table lists related OpenVMS documents.                H                                                                     xiii -             H               __________________________________________________________H               OpenVMS_Document___________Description____________________  C               OpenVMS Version 7.x        Describes the new featuresrD               New Features and           of the OpenVMS software andD               Documentation Overview     provides an overview of theG               Manual                     documentation that supports itn  E               OpenVMS Alpha Version 7.x  Describes how to install thesF               Upgrade and Installation   OpenVMS Alpha system software               Manual  E               OpenVMS VAX Version 7.x    Describes how to install the D               Upgrade and Installation   OpenVMS VAX system software               Manual  F               OpenVMS System Manager's   A task-oriented guide (in twoH               Manual                     volumes) to managing an OpenVMSH                                          system; describes how to set upE                                          the required system servicesd  B               OpenVMS System Management  A reference guide (in twoB               Utilities Reference        volumes) to the utilitiesC               Manual                     and tools used in managing :                                          an OpenVMS system  H               OpenVMS License            Explains how to load and manageF               Management Utility Manual  license Product Authorization4                                          Keys (PAKs)  F               OpenVMS Guide to System    Describes the system securityG               Security                   features of OpenVMS, includinga@                                          procedures for enablingH               ___________________________external_authentication________  C               For additional information about the OpenVMS products.G               and services, access the following OpenVMS World Wide Web                address:  ,               http://www.openvms.compaq.com/                     xivS t  e                     Reader's Comments     G               Compaq welcomes your comments on this manual. Please send <               comments to either of the following addresses:  /               Internet    openvmsdoc@compaq.com   5               Mail        Compaq Computer Corporation.>                           OSSG Documentation Group, ZKO3-4/U08,                           110 Spit Brook Rd./                           Nashua, NH 03062-2698   -         How To Order Additional Documentationr  H               Visit the following World Wide Web address for information:               about how to order additional documentation:  ,               http://www.openvms.compaq.com/  F               If you need help deciding which documentation best meets,               your needs, call 800-282-6672.           Conventionst  F               The term PATHWORKS Advanced Server is used in this guideE               to refer to the PATHWORKS for OpenVMS (Advanced Server)oD               file and print server. Mentions of Compaq OpenVMS fileF               and print servers refers to the PATHWORKS family of fileC               and print servers, including PATHWORKS (LAN Manager),WD               PATHWORKS for OpenVMS (NetWare), PATHWORKS for OpenVMSE               (Advanced Server), and the Advanced Server for OpenVMS.A  A               The following conventions are used in the PATHWORKS.,               Advanced Server documentation:  H               __________________________________________________________H               Convention____Meaning_____________________________________  G               DECnet        Applies to both DECnet Phase IV and DECnet- =                             Plus, unless otherwise specified.         H                                                                       xv r  .          H               __________________________________________________________H               Convention____Meaning_____________________________________  >               Italic        The use of italic text indicates aE                             placeholder for information or parameters.F                             that you must provide. For example, if theE                             procedure asks you to type file name, youh@                             must type the actual name of a file.  H                             Italic text also indicates new terms and theE                             titles of other documentation referenced..  F               monospace     The use of monospace text indicates actualG                             commands and characters that you enter, and-/                             the system display.t  C               Note          The use of Note provides information of./                             special importance.l  F               Caution       The use of Caution provides information to@                             avoid damaging software or hardware.  H               Warning       The use of Warning provides information that<                             is essential to people's safety.  G                . . .        A horizontal ellipsis following an entry inrH                             a command line indicates that the entry or aD                             similar entry can be repeated any numberB                             of times. An ellipsis following a fileF                             name indicates that additional parameters,B                             values, or information can be entered.  G                   .         A vertical ellipsis in an example indicates ;                   .         that not all the data is shown.                    ..  C               Ctrl/x        While you hold down the Ctrl key, presspD                             another key or a pointing device button.  C               Return or     Return or Enter in text indicates where.@               Enter         you should press the Return or EnterC                             key to execute a command or terminate aRC                             sequence. This key is labeled Return orH>                             Enter, depending on your keyboard.             xvi. .  .          H               __________________________________________________________H               Convention____Meaning_____________________________________  A               <Tab>         In examples, a key name enclosed in a A                             box indicates that you press a key on E                             the keyboard. (In text, a key name is not /                             enclosed in a box.)l  F                             In the HTML version of this document, thisG                             convention appears as brackets, rather thanS"                             a box.  G               PF1 x         A sequence such as PF1 x indicates that you.H                             must first press and release the key labeledF                             PF1 and then press and release another keyH               ______________or_a_pointing_device_button.________________                                                            H                                                                     xvii    v                  H                                                                        1H         ________________________________________________________________  H                             Before You Install PATHWORKS Advanced Server      G               This chapter describes the hardware and software you mustlH               have and the tasks you need to complete before you install1               PATHWORKS Advanced Server software..  >               This chapter consists of the following sections:  F               o  Section 1.1, About the PATHWORKS for OpenVMS Software                  Kit  F               o  Section 1.2, If You Are Upgrading from PATHWORKS (LAN                  Manager)s  :               o  Section 1.3, Installing DECprint Software  -               o  Section 1.4, About Licensinge  ;               o  Section 1.5, About External Authentication   7               o  Section 1.6, Reading the Release Notes1  >               o  Section 1.7, Using the Installation Checklist  C               o  Section 1.8, Requirements for Installing PATHWORKSr)                  Advanced Server Software   3               o  Section 1.9, Preinstallation Tasks-  (               o  Section 1.10, Next Step  8         1.1 About the PATHWORKS for OpenVMS Software Kit  F               The PATHWORKS for OpenVMS (Advanced Server) kit containsA               the software required to run the following software #               installation options:i  F               o  The complete PATHWORKS Advanced Server file and printH                  server software, including the License Server, external>                  authentication software, and Upgrade utility.  .               o  The standalone License Server  H                         Before You Install PATHWORKS Advanced Server 1-1    -      4         Before You Install PATHWORKS Advanced Server8         1.1 About the PATHWORKS for OpenVMS Software Kit  @               o  The standalone external authentication software  $               o  The Upgrade utility  G               The Upgrade utility helps you migrate from PATHWORKS (LAN E               Manager) to PATHWORKS V6 for OpenVMS (Advanced Server).   >         1.1.1 About the PATHWORKS for OpenVMS (NetWare) Server  E               The PATHWORKS for OpenVMS (NetWare) server is no longer-G               supported. PATHWORKS for OpenVMS (Advanced Server) cannot F               be installed on a system where the PATHWORKS for OpenVMS@               (NetWare) server is installed. If the installationA               procedure finds the PATHWORKS for OpenVMS (NetWare)pE               server, it optionally invokes the PATHWORKS for OpenVMSiH               (NetWare) removal procedure (PWVN$DEINSTAL), to remove theE               NetWare server software before installing the PATHWORKS.F               Advanced Server software. For more information about theE               NetWare server removal procedure, refer to Section 7.2,.4               Removing the PATHWORKS NetWare Server.  D               If your clients continue to depend on NetWare softwareB               to connect to the system, or if you need the IPX/SPXH               transport for any reason, you should designate a system to=               run the PATHWORKS for OpenVMS (NetWare) server.   =         1.2 If You Are Upgrading from PATHWORKS (LAN Manager)   E               If you have PATHWORKS (LAN Manager) installed, you mustaG               install the new PATHWORKS Advanced Server. You can choose H               to install just the Upgrade utility initially, and installF               the PATHWORKS Advanced Server later. Refer to the CompaqF               PATHWORKS for OpenVMS (Advanced Server) Server Migration)               Guide for more information.o  (         1.3 Installing DECprint Software  B               DECprint Supervisor for OpenVMS (DCPS) is a printing@               system that provides queue management and printingE               features for PostScript printers. To share a PostScriptgH               printer, selected PostScript printers might require use ofE               the DECprint Supervisor for OpenVMS (DCPS) software for D               communication with the printers over DECnet or TCP/IP.    8         1-2 Before You Install PATHWORKS Advanced Server o  g      H                             Before You Install PATHWORKS Advanced ServerH                                         1.3 Installing DECprint Software  C               If you plan to use DECprint Supervisor for OpenVMS on G               your system, Compaq recommends that you install it before H               installing the Advanced Server. You must reboot the systemE               after installing the DECprint software. You can performiH               the reboot as part of the DECprint Supervisor installationE               procedure, or after you install the Advanced Server but_&               before you configure it.           1.4 About Licensingp  C               The following sections describe the way the PATHWORKS E               Advanced Server software is licensed, and how to ensure A               clients accessing the server are properly licensed.n  "         1.4.1 License Requirements  A               The PATHWORKS Advanced Server requires that clients @               accessing file and print services be appropriatelyB               licensed. To conform to this requirement, one of the%               following must be true:   F               o  The client must present a client-based license beforeH                  each attempt to connect to a PATHWORKS Advanced Server.  G               o  The PATHWORKS Advanced Server must have a server-based D                  license available to assign to an unlicensed clientE                  attempting to use services of the PATHWORKS Advanced                   Server.  F               In either case, the license required to access PATHWORKS@               V6.1 for OpenVMS (Advanced Server) services is theH               PATHWORKS Client Access license: PWLMXXXCA07.03 or higher,6               or an equivalent client virtual license.  G               If you are upgrading from PATHWORKS LAN Manager, refer to G               the Compaq PATHWORKS for OpenVMS (Advanced Server) Server D               Migration Guide for information about upgrading client               license requests.               H                         Before You Install PATHWORKS Advanced Server 1-3 h         4         Before You Install PATHWORKS Advanced Server         1.4 About Licensingn  &         1.4.2 About the License Server  B               The PATHWORKS License Server is an optional softwareF               program that you can run on your OpenVMS system to grant"               licenses to clients.  2               The License Server can be installed:  G               o  With the file and print server (automatically included.>                  with your file and print server installation)  F               o  Separately from the file and print server (called the-                  "standalone License Server")   B               In either case, you can configure the License ServerC               to support clients using any of the following network                protocols:                 o  DECnetr  &               o  LAN Manager (NetBEUI)                 o  TCP/IP   F               Compaq recommends that you install the License Server onD               a designated OpenVMS system without the PATHWORKS fileA               server. (The PATHWORKS Advanced Server installationO@               procedure allows you to install the License ServerB               separately from the file server.) Alternatively, youC               can run the License Server on an OpenVMS Cluster withAF               PATHWORKS file and print servers, where cluster failover#               provides reliability.l  F               Each LAN needs only one active PATHWORKS License Server.A               (The same License Server can support both PATHWORKS E               LAN Manager and PATHWORKS Advanced Server clients.) The F               license product authorization keys (PAKs) must be loadedF               on the system that runs the PATHWORKS License Server. InG               an OpenVMS Cluster, the PAKs must be loaded into a shared'               license database.   H               __________________________________________________________H               Information_Required__Source______________________________  F               Loading licenses      OpenVMS License Management Utility*                                     Manual  8         1-4 Before You Install PATHWORKS Advanced Server a  a      H                             Before You Install PATHWORKS Advanced ServerH                                                      1.4 About Licensing  H               __________________________________________________________H               Information_Required__Source______________________________  G               Configuring the       Chapter 4, Configuring and Starting A               License Server        the Standalone License Server_  F               Managing PATHWORKS    Compaq Advanced Server for OpenVMSE               Advanced Server       Guide to Managing Advanced ServersH               licenses______________Licenses____________________________  )         1.5 About External Authenticationv  G               External authentication is an optional feature of OpenVMS @               systems that allows system managers to set up userC               accounts for which login authentication is based on an=               security mechanism other than OpenVMS security.a  >               The PATHWORKS Advanced Server takes advantage of>               this feature by providing the ability to use theE               PATHWORKS Advanced Server or Windows NT-compatible usermD               authentication mechanisms to authenticate OpenVMS userF               logins. This allows users to log in at the OpenVMS loginF               prompt using the PATHWORKS Advanced Server user name andC               password. In addition, it provides automatic passwordn0               synchronization for user accounts.  F               When you install the complete PATHWORKS Advanced Server,G               the files required to support external authentication are A               automatically included in the installation process.p  @               When you install the Advanced Server in an OpenVMSD               Cluster, if you want to enable external authenticationD               on OpenVMS Cluster member nodes on which the server isG               not running and which share the same system disk, you can E               install the standalone external authentication software B               on that disk (without installing the Advanced ServerE               software). On OpenVMS Version 7.1 Alpha and VAX clusterdF               members, you must copy the external authentication filesH               from a system on which the Advanced Server is installed to.               the OpenVMS Version 7.1 systems.  B               For more information about enabling external authen-A               tication, refer to Section 5.6, Setting Up Externall               Authentication.o  H                         Before You Install PATHWORKS Advanced Server 1-5 m  c      4         Before You Install PATHWORKS Advanced Server%         1.6 Reading the Release NotesS  %         1.6 Reading the Release Notes   E               The PATHWORKS Advanced Server installation kit includes H               the Compaq PATHWORKS for OpenVMS (Advanced Server) ReleaseF               Notes. Compaq recommends that you read the release notes/               before starting the installation.t  F                 ________________________Note  ________________________  C                 The installation procedure copies the release notesrA                 into the SYS$HELP: area, where they are available *                 after server installation.  E                 _____________________________________________________e  -         1.6.1 How to Access the Release NotesM  H               Use the following table to decide how to print the release               notes:  H         ________________________________________________________________         DesiredHH         Result________Required_Steps____________________________________  '         Print the     Do the following:V>         release       1. Load the installation kit on a drive.
         notes G         before the    2. Enter the following commands, replacing device_G         installation     with the name of the device (and if the deviceeG                          is a disk, also designate the directory) where 9                          you loaded the installation kit:            $ MOUNT device: PWRKI         $ BACKUP/SELECT=PWRK061.RELEASE_NOTES device:PWRK061.A/SAVE_SET *   %         $ PRINT PWRK061.RELEASE_NOTES                   8         1-6 Before You Install PATHWORKS Advanced Server           H                             Before You Install PATHWORKS Advanced ServerH                                            1.6 Reading the Release Notes  H         ________________________________________________________________         DesiredvH         Result________Required_Steps____________________________________  '         Print the     Do the following: >         release       1. Load the installation kit on a drive.
         noteslA         during the    2. Enter the following command to start the 0         installation     installation procedure:  A                       $ @VMSINSTAL PWRK061 device_name: OPTIONS N   F                       The installation procedure prompts you to either@                       print or display the release notes. In anyF                       case, the release notes are always copied to theH         ______________SYS$HELP:_area.___________________________________  ,         1.7 Using the Installation Checklist  F               Appendix A, Installation and Upgrade Checklist, providesF               an installation and configuration summary checklist. YouE               can photocopy the summary checklist and use it to track H               the completion of the installation and configuration tasks&               described in this guide.  A         1.8 Requirements for Installing PATHWORKS Advanced Server              Software  G               The following sections describe the hardware and software G               that may be required to install PATHWORKS Advanced Server                on the system.  #         1.8.1 Hardware Requirements   C               All Alpha and VAX processors supported by the OpenVMS B               operating system are also supported by the PATHWORKS@               Advanced Server. For the latest information on theF               hardware that the server supports, refer to the Software(               Product Description (SPD).  @               Make sure that the network (including cables, PCs,C               servers, and other hardware) is connected. For a listaD               of the hardware that the server supports, refer to the1               Software Product Description (SPD).   H                         Before You Install PATHWORKS Advanced Server 1-7           4         Before You Install PATHWORKS Advanced ServerJ         1.8 Requirements for Installing PATHWORKS Advanced Server Software  #         1.8.2 Software Requirementsp  D               To install PATHWORKS Advanced Server successfully, youE               must have the following software properly installed andI(               configured on your system:  D               o  OpenVMS Alpha Version 7.3, 7.2-2, 7.2-1, or 6.2, or5                  OpenVMS VAX Version 7.3, 7.2, or 6.2   B               o  The appropriate transport software to support theG                  network protocols used by other servers and by network1A                  clients, including one or more of the following:s  4                  -  DECnet or DECnet-Plus (optional)  E                     DECnet or DECnet-Plus may optionally be installed_B                     when you install the OpenVMS operating system.  %                  -  TCP/IP (optional)   E                     TCP/IP Services for OpenVMS or a supported third- B                     party TCP/IP product can be used to provide IPC                     support. Refer to the PATHWORKS Advanced Server_D                     Software Product Description (SPD) for a list of.                     supported TCP/IP products.  '         1.8.3 Supported Client Softwarer  E               PATHWORKS Advanced Server supports connections from them)               following types of clients:H                 o  Windows 2000                  o  Windows NT 4.0t                 o  Windows 98                  o  Windows 95b  '               o  Windows for Workgroups                  o  PATHWORKS 32   !         1.8.4 Memory Requirementsf  G               The system must have at least 64 MB of physical memory to10               run the PATHWORKS Advanced Server.  8         1-8 Before You Install PATHWORKS Advanced Server 5  b      H                             Before You Install PATHWORKS Advanced ServerH                                                1.9 Preinstallation Tasks  !         1.9 Preinstallation Tasksu  ?               Use the following checklist to make sure you haverC               completed all the tasks you should perform before you H               install the software. Each task is described later in this               section.  H               Table_1-1_Preinstallation_Checklist_______________________  /               <   >1.   Check the part listing.l  H               <   >2.   Make sure that the network hardware is installed&                         and connected.  5               <   >3.   Log in to the SYSTEM account.   ?               <   >4.   Make sure that the required software isa"                         installed.  /               <   >5.   Read the release notes.   0               <   >6.   Check system parameters.  1               <   >7.   Back up the system disks.P  G               <   >8.   Make sure that you have adequate disk space fora%                         installation.n  0               <   >9.   Check the queue manager.  :               <   >10.  Check the time zone configuration.  D               <   >11.  Make sure that DECnet is running, if you are=                         planning to use the DECnet transport.   D               <   >12.  Make sure that TCP/IP is running, if you are=                         planning to use the TCP/IP transport.e  G               <   >13.  Check for existing Compaq OpenVMS server imagesl"                         and files.  G               <   >14.  Check the OpenVMS Cluster configuration, if younE                         are installing PATHWORKS Advanced Server on a H               __________cluster.________________________________________  H                         Before You Install PATHWORKS Advanced Server 1-9           4         Before You Install PATHWORKS Advanced Server!         1.9 Preinstallation Taskse  G               Before you install PATHWORKS Advanced Server, perform thee               following steps.  F                 ________________________Note  ________________________  ;                 All the steps except the last apply to both A                 standalone and cluster Advanced Servers. The last D                 step delineates what needs to be done for installing1                 the Advanced Server on a cluster.   E                 _____________________________________________________   ,         1.9.1 Step 1: Check the Part Listing  A               The software part listing specifies the contents ofSA               the kit you receive. Check the contents of your kittD               against that information. If parts are missing or yourF               kit is damaged, contact your Compaq Computer Corporation               representative.   0         1.9.2 Step 2: Check the Network Hardware  D               PATHWORKS Advanced Server runs on OpenVMS systems thatG               meet the software requirements. The PC local area networke               (LAN) requires:   G               o  A supported network controller board in the server and                   in each clientp  D               o  The cables to connect each client and server to the                  network  2         1.9.3 Step 3: Log In to the SYSTEM Account  B               Before you install PATHWORKS Advanced Server, log inD               to the SYSTEM account, or another account that has allC               privileges enabled to run the installation procedure.   .               To log in to the SYSTEM account:  7               1. At the user name prompt, enter SYSTEM:   !                  Username: SYSTEMn  B               2. At the Password prompt, enter the password to the>                  SYSTEM account. The password you enter is not                  displayed.   9         1-10 Before You Install PATHWORKS Advanced Servert p  i      H                             Before You Install PATHWORKS Advanced ServerH                                                1.9 Preinstallation Tasks  1         1.9.4 Step 4: Check the Required Softwareb  ?               PATHWORKS Advanced Server requires the following:   D               o  OpenVMS operating system, Alpha Version 7.3, 7.2-2,?                  7.2-1, or 6.2, or VAX Version 7.3, 7.2, or 6.2   C               o  DECnet or DECnet-Plus, if you are going to use the B                  DECnet transport, the mail server, or the License$                  Server over DECnet.  E               o  A TCP/IP product, if you are going to use the TCP/IP G                  for cluster or network communication. Supported TCP/IP C                  products are described in the Compaq PATHWORKS for 9                  OpenVMS (Advanced Server) Release Notes.e  6         1.9.5 Step 5: Print and Read the Release Notes  H               If you have not already read the release notes, you shouldD               do so before installing the software. If you choose toG               back up the system, as recommended in Section 1.9.8, StepeC               8: Back Up the System, you can read the release notestE               during the backup. See Section 1.6, Reading the Releasee*               Notes, for more information.  -         1.9.6 Step 6: Check System Parametersr  A               Most systems have adequate system resources readilyr@               available to include the PATHWORKS Advanced ServerE               software. However, make sure that the following OpenVMS D               system parameters are set properly. Make any necessaryF               changes to the MODPARAMS.DAT file, then run AUTOGEN, andE               reboot your system. You can delay this reboot until the G               first reboot required for backing up your system disks (a E               backup is recommended in Section 1.9.8, Step 8: Back Up                the System).  G               Make sure all other software that will be running on your H               system is indeed running before and while you run AUTOGEN.  F                 ________________________Note  ________________________  =                 If these parameters are not set properly, youaB                 cannot configure the server after you complete the'                 installation procedure.o  E                 _____________________________________________________c  H                        Before You Install PATHWORKS Advanced Server 1-11           4         Before You Install PATHWORKS Advanced Server!         1.9 Preinstallation Tasks                   GBLPAGES parameter  >               The minimum value of this parameter is listed in:               Table 1-2, GBLPAGES Parameter Minimum Value.  H               Table_1-2_GBLPAGES_Parameter_Minimum_Value________________  C               Minimum Value for a VAX    Minimum Value for an AlpharH               system_____________________system_________________________  H               3500_pages_________________7500_pages_____________________  F               To ensure that your system has enough free global pages,H               do the following while the Advanced Server is not running:                                                              9         1-12 Before You Install PATHWORKS Advanced Servero d         H                             Before You Install PATHWORKS Advanced ServerH                                                1.9 Preinstallation Tasks  %               1. Enter the following:_  =                  $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")   F                  The value of the GBLPAGES parameter is displayed. For                  example:                     143576t  D               2. If the value is less than required, edit the systemH                  parameters file SYS$SYSTEM:MODPARAMS.DAT and add a line*                  similar to the following:  $                  MIN_GBLPAGES = 7500  #               GBLSECTIONS parametern  C               The minimum value of this parameter differs depending_A               on which server is to be installed, as described in_=               Table 1-3, GBLSECTIONS Parameter Minimum Value.,  H               Table_1-3_GBLSECTIONS_Parameter_Minimum_Value_____________  H               Minimum Value for the      Minimum Value for the PATHWORKSH               standalone_License_Server__Advanced_Server_Installation___  H               50_________________________75_____________________________  ?               To ensure that your system has enough free global E               sections, do the following while the Advanced Server is                not running:  %               1. Enter the following:   =                  $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")   E                  The value of the GBLSECTIONS parameter is displayed.                   For example:                     249  D               2. If the value is less than required, edit the systemH                  parameters file SYS$SYSTEM:MODPARAMS.DAT and add a line*                  similar to the following:  %                  MIN_GBLSECTIONS = 75l  H                        Before You Install PATHWORKS Advanced Server 1-13 R  A      4         Before You Install PATHWORKS Advanced Server!         1.9 Preinstallation Tasksr  #               PROCSECTCNT parameters  C               The minimum value of this parameter differs dependingdA               on which server is to be installed, as described inl=               Table 1-4, PROCSECTCNT Parameter Minimum Value.h  H               Table_1-4_PROCSECTCNT_Parameter_Minimum_Value_____________  H               Minimum Value for the      Minimum Value for the PATHWORKSH               Standalone_License_Server__Advanced_Server_Installation___  H               32_________________________40_____________________________  >               To ensure that the value of the system parameter&               PROCSECTCNT is adequate:  %               1. Enter the following:   ;                  $ WRITE SYS$OUTPUT F$GETSYI("PROCSECTCNT")s  E                  The value of the PROCSECTCNT parameter is displayed.l                  For example:                     20e  D               2. If the value is less than required, edit the systemH                  parameters file SYS$SYSTEM:MODPARAMS.DAT and add a line*                  similar to the following:  %                  MIN_PROCSECTCNT = 40a                 SCSNODE parametere  F               This parameter must be defined as your system's computerF               name. If you are running DECnet, the SCSNODE name should2               be the same as the DECnet node name.  D               The SCSNODE parameter's preinstallation status affects9               what happens after you install, as follows:S            9         1-14 Before You Install PATHWORKS Advanced Servere l  e      H                             Before You Install PATHWORKS Advanced ServerH                                                1.9 Preinstallation Tasks  H               __________________________________________________________?               SCSNODE                     Server Response AftereH               Status________Your_Action___Installation__________________  9               Not defined   Do not        Does not start. %                             define itn  1               Already       Do not        Starts. %               defined       define it_  H               Not defined   Define it     Starts, but the OpenVMS systemH                                           renames print and batch queuesE                                           to include the new computertC                                           name. Therefore, you musttD                                           requeue any existing printB                                           or batch jobs to the newC                                           queues. You may also have H                                           to rebuild the queue database.B                                           For information on theseB                                           system management tasks,E                                           refer to the OpenVMS System H               ____________________________Manager's_Manual._____________  F               To check whether the system parameter SCSNODE is definedA               as your system's computer name, enter the following_,               commands at the system prompt:  -               $ SCSNODE = F$GETSYI("SCSNODE")_#               $ SHOW SYMBOL SCSNODEe  7               As a result, one of the following occurs:n  G               o  If SCSNODE is defined, the computer name is displayed.iG                  For example, if your system's computer name is SPEEDY::  &                  $ SHOW SYMBOL SCSNODE                     SPEEDY  D               o  If SCSNODE is not defined, the computer name is not                  displayed.n  F                  If SCSNODE is not defined, edit the system parametersH                  file SYS$SYSTEM:MODPARAMS.DAT and define the parameter.G                  For example, if your system's computer name is SPEEDY,nF                  edit the file so that it contains the following line:  #                  SCSNODE = "SPEEDY"t  H                        Before You Install PATHWORKS Advanced Server 1-15 u  r      4         Before You Install PATHWORKS Advanced Server!         1.9 Preinstallation Tasksa  C                  If you edit the file SYS$SYSTEM:MODPARAMS.DAT, yourC                  must run the OpenVMS command procedure AUTOGEN andeD                  reboot the system either now or at some time before5                  configuring the server. For example:A  @                  $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK  A               For information about running AUTOGEN, refer to theoC               OpenVMS System Management Utilities Reference Manual.   /         1.9.7 Step 7: Check ENQLM Process QuotaS  E               Make sure that the ENQLM quota for the user account you G               use for configuring the Advanced Server is set to a value D               of 500 or greater. If it is not set appropriately, youE               will not be able to configure the Advanced Server afters)               the installation procedure.s  D               To determine the current setting for this quota, enterG               the following command while logged in to the user account G               from which you will run the PWRK$CONFIG.COM configuratione               procedure:  6               $ WRITE SYS$OUTPUT F$GETJPI("", "ENQLM")  @               The value of the ENQLM parameter is displayed. For               example:                 2000  E               If the value is less than required, follow these steps:   @               1. Set the process default device and directory to                  SYS$SYSTEM.  G               2. At the system prompt, enter the MCR AUTHORIZE command.   C               3. At the UAF prompt, enter the MODIFY command, as in F                  the following example, where user-account is the nameF                  of the user account from which you will configure the@                  server, and value is a value of 500 or greater:  5                  UAF> MODIFY user-account/ENQLM=value     9         1-16 Before You Install PATHWORKS Advanced Server            H                             Before You Install PATHWORKS Advanced ServerH                                                1.9 Preinstallation Tasks  (         1.9.8 Step 8: Back Up the System  D               To safeguard against the loss of valuable data, CompaqF               recommends that you back up all disks on your system (orF               at least the system disk) before you install any layered               product.  H               To do a system backup, use the OpenVMS BACKUP command. ForH               information about the BACKUP command, refer to the OpenVMS;               System Management Utilities Reference Manual.s  3         1.9.9 Step 9: Check Disk Space Requirements   F               To determine the number of disk blocks required for yourB               installation, refer to the PATHWORKS Advanced Server               release notes.  D               To check the number of free blocks on the system disk,               enter:  )               $ SHOW DEVICE SYS$SYSDEVICEl  F               The OpenVMS system displays information about the systemE               disk, including the number of free blocks. For example:   F               Device     Device     Error    Volume    Free  Trans MntF                Name      Status     Count     Label   Blocks Count CntF               DUA0:      Mounted        0    AXP072   724856   280   1  /         1.9.10 Step 10: Check the Queue Managero  C               It is not necessary to have the queue manager running ?               during installation and configuration, but CompaqoB               recommends that it be running when you configure theE               server. You can enter the SHOW QUEUE/MANAGER command to 9               check whether the queue manager is running:   "               $ SHOW QUEUE/MANAGER  B               If the queue manager is running, your OpenVMS system:               displays a message similar to the following:  C               Queue manager SYS$QUEUE_MANAGER, running, on CPEEDY::q  B               If the queue manager is not running, you can use the,               following command to start it:  #               $ START/QUEUE/MANAGERz  H                        Before You Install PATHWORKS Advanced Server 1-17    y      4         Before You Install PATHWORKS Advanced Server!         1.9 Preinstallation Tasks.  H               For more information about the OpenVMS DCL commands, refer,               to the OpenVMS DCL Dictionary.  /         1.9.11 Step 11: Check Time Zone and TDFe  G               To check the time zone and time differential factor (TDF) G               settings on the system, run the OpenVMS command procedure F               SYS$MANAGER:UTC$TIME_SETUP.COM. From the SYSTEM account,A               enter the following command to begin the procedure:   /               $ @SYS$MANAGER:UTC$TIME_SETUP.COMr  G               PATHWORKS Advanced Server's internal time management uses G               Greenwich Mean Time (GMT). To properly represent the timeWF               in the local environment, the time zone information must5               be set up before the server is started._  F               To set the time zone on your OpenVMS system, execute the*               following command procedure:  2               @ SYS$MANAGER:UTC$TIMEZONE_SETUP.COM  F               To set the time zone differential factor for the OpenVMS>               system, execute the following command procedure:  1               @ SYS$MANAGER:UTC$CONFIGURE_TDF.COM1  B               If you change any time zone information, such as theH               daylight savings time setting, you must restart the server6               for the time to be properly represented.  F                 ________________________Note  ________________________  A                 For diagnostic purposes, you can check the server C                 log file for the values of the TDF (in seconds) andK.                 the daylight saving time flag.  E                 _____________________________________________________   G               For more information on running the command procedure andrE               resetting time zone and TDF, see the section on setting C               time zone information in the OpenVMS System Manager's                Manual.     9         1-18 Before You Install PATHWORKS Advanced Server     o      H                             Before You Install PATHWORKS Advanced ServerH                                                1.9 Preinstallation Tasks  +         1.9.12 Step 12: Check DECnet Status   @               If you plan to use the DECnet transport, it is notD               necessary to have DECnet or DECnet-Plus running duringF               the installation; however, DECnet or DECnet-Plus must beH               running on the system before you can configure the server.  B               To see whether DECnet is running on the system whereD               you are planning to install the server software, enterC               the appropriate command depending on whether you have G               installed DECnet (Phase IV), or DECnet-Plus, as describedS(               in the following sections.  2         1.9.12.1 Checking DECnet (Phase IV) Status  B               To check DECnet status, enter the following command:  %               $ MCR NCP SHOW EXECUTORo  @               o  If DECnet is running, the SHOW EXECUTOR display)                  resembles the following:r  A                  Node Volatile Summary as of  1-JUL-2001 12:16:36e  /                  Executor node = 9.000 (BRUTUS)   %                  State           = on >                  Identification  = DECnet for OpenVMS AXP V7.2  F               o  If DECnet is not running, enter the following command                  to start it:)  (                  $ @SYS$MANAGER:STARTNET  ,         1.9.12.2 Checking DECnet-Plus Status  G               If you use DECnet-Plus (formerly DECnet/OSI for OpenVMS),oF               enter the following command to see whether it is runningH               on the system where you are planning to install the server               software:n  /               $ SHOW LOGICAL NET$STARTUP_STATUSb  C               o  If DECnet-Plus is running, the system displays them                  following:.  H                  "NET$STARTUP_STATUS" = "RUNNING-ALL" (LNM$SYSTEM_TABLE)  C               o  If DECnet-Plus is not running, enter the followingP%                  command to start it:   +                  $ @SYS$STARTUP:NET$STARTUP   H                        Before You Install PATHWORKS Advanced Server 1-19           4         Before You Install PATHWORKS Advanced Server!         1.9 Preinstallation Tasksy  ?               For more information, refer to the DECnet producto               documentation.  +         1.9.13 Step 13: Check TCP/IP Statuso  H               If you are planning to use the TCP/IP transport, make sureE               that TCP/IP is running and that the PATHWORKS IP (PWIP) D               driver has been loaded. The procedure for starting theE               TCP/IP product and the PWIP driver differs depending on_D               the TCP/IP product running on the system. Refer to theF               documentation for your TCP/IP product for information on6               how to start TCP/IP and the PWIP driver.  C               For example, if TCP/IP Services for OpenVMS Version 5 E               is installed, you can start the PWIP driver manually by -               entering the following command:e  3               $ @SYS$STARTUP:TCPIP$PWIP_STARTUP.COM   B               Alternatively, you can configure TCP/IP Services forA               OpenVMS to automatically start the PWIP driver wheniB               TCP/IP is started, using the configuration procedure               TCPIP$CONFIG.COM.   B               For TCP/IP Services for OpenVMS Version 4.x, use theG               configuration procedure UCX$CONFIG.COM to enable the PWIP F               driver on TCP/IP startup, or enter the following OpenVMS               commands:y  (               $ @SYS$STARTUP:UCX$STARTUP-               $ @SYS$STARTUP:UCX$PWIP_STARTUP   >               You can add these commands to the system startup               procedure.  A               After the installation is complete, you can use the >               Configuration Manager to configure the PATHWORKSG               Advanced Server to use TCP/IP. You can do this during thenH               configuration procedure (PWRK$CONFIG) or after configuringC               the server. In the former case, PWRK$CONFIG gives youeF               the option of invoking the Configuration Manager. In theF               latter case, you can invoke the Configuration Manager atG               the DCL prompt by entering the ADMINISTER/CONFIG command.:    9         1-20 Before You Install PATHWORKS Advanced Servero w  :      H                             Before You Install PATHWORKS Advanced ServerH                                                1.9 Preinstallation Tasks  D         1.9.14 Step 14: Check for Existing OpenVMS Server Images and                Files                 Make sure that:e  H               1. No Compaq OpenVMS file and print server images (currentH                  or earlier versions) are running on the local system orF                  on any member of the OpenVMS Cluster (when installing                  on a cluster)._  D               2. No files from a PATHWORKS for OpenVMS (NetWare) kitC                  are on the system disk. If such files are present, D                  use SYS$UPDATE:PWVN$DEINSTAL.COM (included with theE                  PATHWORKS for OpenVMS (NetWare) kit) to remove thoseI                  files.R  C               3. No PATHWORKS or Advanced Server for OpenVMS imageseB                  reside in the SYS$SPECIFIC: directory area of theB                  system disk on which PATHWORKS will be installed.C                  (When PATHWORKS V6.1 for OpenVMS (Advanced Server)nD                  is installed, images in the SYS$SPECIFIC: directoryE                  area will be used before the corresponding images inlD                  the SYS$COMMON: directory area are used.) To removeE                  the PATHWORKS or Advanced Server (V7.2 or V7.2A) for H                  OpenVMS files, use the PWRK$DEINSTAL utility. To removeD                  the Advanced Server V7.3 for OpenVMS files, use theD                  PRODUCT REMOVE command, as documented in the CompaqD                  Advanced Server for OpenVMS Server Installation and%                  Configuration Guide.   F               The server VMSINSTAL installation utility will detect ifG               any of these conditions exist, and if the images or files G               are found, it will notify you. The VMSINSTAL installation F               utility automatically deletes, without notification, anyG               files from a PATHWORKS Advanced Server or Advanced Server G               for OpenVMS kit found in the SYS$SPECIFIC directory tree.   ;         1.9.15 Step 15: Check OpenVMS Cluster Configuration   A               You can run the Advanced Server on multiple OpenVMS <               Cluster members. To do so, follow these steps:  B               1. An OpenVMS Cluster can include both VAX and AlphaD                  member nodes. The PATHWORKS Advanced Server can runC                  on any VAX or Alpha cluster member that is runningsD                  a supported version of OpenVMS. However, an OpenVMSE                  Cluster cannot support two different versions of thee  H                        Before You Install PATHWORKS Advanced Server 1-21 i  a      4         Before You Install PATHWORKS Advanced Server!         1.9 Preinstallation Tasks   E                  file and print server (for example, PATHWORKS V6 for G                  OpenVMS (Advanced Server) and Advanced Server V7.3 for                   OpenVMS).  F               2. Decide which member nodes in the OpenVMS Cluster willF                  run the Advanced Server, then identify all the systemG                  disks that will be used by those member nodes. InstallrC                  the Advanced Server on each of those system disks.   H                  If the OpenVMS Cluster contains other system disks (forE                  example, to support systems running earlier versionseC                  of OpenVMS), these disks might have older versionssF                  of Compaq OpenVMS file and print servers installed onG                  them. If so, remove the older versions to prevent themiH                  from accidentally starting up while the Advanced ServerE                  is running on the current OpenVMS systems. To remove E                  the PATHWORKS for OpenVMS (Advanced Server) product,jG                  execute the command procedure SYS$UPDATE:PWRK$DEINSTAL E                  from a cluster member that uses the system disk fromeG                  which PATHWORKS is to be removed. For more informationnD                  on using PWRK$DEINSTAL.COM, see Chapter 7, RemovingB                  PATHWORKS Advanced Server Software. To remove theB                  Advanced Server V7.3 for OpenVMS product, use theD                  PRODUCT REMOVE command, as documented in the CompaqD                  Advanced Server for OpenVMS Server Installation andG                  Configuration Guide. To remove earlier versions of the D                  Advanced Server for OpenVMS, use PWRK$DEINSTAL.COM.E                  To remove a PATHWORKS (LAN Manager) product, use the B                  PWRK$DEINSTAL utility that was installed with theD                  product. The PATHWORKS (LAN Manager) server must be2                  stopped before you can remove it.  E               3. If you plan to use the TCP/IP transport, ensure thathF                  all cluster members on which the Advanced Server will3                  run are in the same TCP/IP subnet.s  C               4. If an earlier version of the PATHWORKS for OpenVMSeG                  (Advanced Server) or any other Compaq OpenVMS file andYH                  print server is running on any cluster member, stop the5                  server on the cluster member system.   @               5. On each system on which you want to install theF                  Advanced Server, complete the tasks described in this                  chapter.   9         1-22 Before You Install PATHWORKS Advanced ServerT o         H                             Before You Install PATHWORKS Advanced ServerH                                                1.9 Preinstallation Tasks  F                  On each cluster member that you want to use as a fileC                  and print server, you will run the Advanced ServerbC                  configuration command procedure (PWRK$CONFIG.COM),gE                  as explained in Chapter 3, Configuring the PATHWORKS E                  Advanced Server. This ensures that each node has itsuG                  appropriate parameters set and enough resources to runs                  the server.  F               6. All cluster members that will run the Advanced Server%                  must share a common:d  ?                  o  System user authorization file (SYSUAF.DAT)   3                  o  Rightlist file (RIGHTSLIST.DAT),  N                  o  Advanced Server data directory location (PWRK$COMMONROOT:)  B               7. When installing the Advanced Server on an OpenVMSG                  Cluster member, if the following two conditions apply,(A                  you are must shut down the server and reboot theiG                  systems running the server. (You can avoid the reboot, !                  as noted below.)d  H                  1. Advanced Servers are installed on two or more system(                     disks in the cluster  D                  2. The Advanced Server is already running on one orF                     more cluster members that are booted from a systemH                     disk other than the one on which the installation is                     occuring  G                  To avoid having to reboot the systems that are alreadydF                  running the Advanced Server, the system administratorE                  can deassign the logical name (PWRK$REBOOT_REQUIRED)dG                  that forces the reboot to occur on each affected node,a                  as follows:  8                   $ DEASSIGN/SYSTEM PWRK$REBOOT_REQUIRED           1.10 Next Step  >               To install PATHWORKS Advanced Server, proceed toB               Chapter 2, Installing the PATHWORKS Advanced Server.    H                        Before You Install PATHWORKS Advanced Server 1-23    o                  H                                                                        2H         ________________________________________________________________  H                                 Installing the PATHWORKS Advanced Server      E               This chapter describes how to install the PATHWORKS for G               OpenVMS (Advanced Server) software. You must follow these G               procedures regardless of whether you are upgrading from a E               previous version of the server or installing the serverc!               for the first time.   D               Before you begin the installation procedure, make sureF               that you have completed the preinstallation tasks listedA               in Chapter 1, Before You Install PATHWORKS Advanced                Server.   >               This chapter consists of the following sections:  >               o  Section 2.1, About the Installation Procedure  3               o  Section 2.2, Installing the Server   C               o  Section 2.3, Troubleshooting Installation Problemso  (               o  Section 2.4, Next Steps  ,         2.1 About the Installation Procedure  H               The following sections describe the installation procedure               and what it does.r            2.1.1 What is VMSINSTAL?  H               VMSINSTAL is the standard command procedure for installingA               software on the OpenVMS operating system. VMSINSTALmG               consists of a series of questions (prompts). Your answerssG               to these questions provide VMSINSTAL with the information,>               needed for installing PATHWORKS Advanced Server.    H                             Installing the PATHWORKS Advanced Server 2-1           0         Installing the PATHWORKS Advanced Server,         2.1 About the Installation Procedure  8         2.1.2 PATHWORKS Advanced Server Installation Kit  E               The VMSINSTAL installation kit includes several OpenVMSiF               BACKUP save sets. The save set PWRK061.A always containsH               the file KITINSTAL.COM and the release notes. The savesetsD               included in the software kit are listed in the product               release notes.  !         2.1.3 What VMSINSTAL Doesn  )               When you use VMSINSTAL, it:I  G               1. Determines whether the PATHWORKS for OpenVMS (NetWare)oA                  server is installed on the system, and if it is,T@                  optionally removes the NetWare server software.  G               2. Creates PATHWORKS Advanced Server accounts on the filer0                  and print server, if necessary.  G               3. Restores the files from the save sets in the installa-e                  tion kit.  E               4. Creates DECnet objects, if you are running DECnet or                   DECnet-Plus.r  C               5. Installs the PATHWORKS Advanced Server DCL command !                  definition file.e  E               6. Installs the PATHWORKS Advanced Server logical names "                  definition files.  (               7. Deletes obsolete files.  >               8. Installs the PATHWORKS Advanced Server files.  >               9. Verifies that the software has been installedH                  successfully. (See Section 5.2, Verifying the PATHWORKS@                  for OpenVMS (Advanced Server) Installation, forH                  information on how to run the Installation Verification:                  Procedure after installing the software.)  !         2.2 Installing the Server   H               The following sections describe how to prepare informationD               required during the installation procedure, and how toD               specify the required information during the procedure.  4         2-2 Installing the PATHWORKS Advanced Server e  e      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  (         2.2.1 Before You Start VMSINSTAL  B               Before you start the VMSINSTAL command procedure, beG               prepared to answer the following questions. The questionsyH               that VMSINSTAL asks depend on the software environment and!               options you select.   0               1. What is the product identifier?  G                  The product identifier tells VMSINSTAL which save setscD                  to copy from the media to a disk on the system. TheE                  product identifier for PATHWORKS Advanced Server is:                     PWRK061  D               2. What is the name of the device on which you want to!                  mount the media?,  A                  The device name depends on the type of media andnG                  computer you have. For example, if you want to mount a E                  CD-ROM on the CD-ROM drive of your Alphastation 400, 1                  the device name might be DKA400.t  F               3. Do you want to access the online release notes during,                  the installation procedure?  C                  You can tell VMSINSTAL to ask you whether you want0D                  to display or print the online release notes duringE                  installation. Because the release notes may describe H                  important changes to the installation procedure, CompaqH                  recommends that you read them. Procedures for obtainingH                  the release notes are described in Section 1.6, Reading#                  the Release Notes.   A               4. Do you want to install just the Upgrade utility?   F                  If the PATHWORKS (LAN Manager) server is installed onD                  the system, you are prompted to install the UpgradeG                  utility separately, which allows you to upgrade server D                  database files before you install the PATHWORKS forG                  OpenVMS (Advanced Server). Appendix D, Upgrade UtilitynA                  Installation, shows a sample installation of the !                  Upgrade utility.R  C                  To install the PATHWORKS Advanced Server, you must ?                  upgrade the server databases. If you choose toTF                  install just the Upgrade utility, you can install theH                  PATHWORKS Advanced Server later, after you upgrade your  H                             Installing the PATHWORKS Advanced Server 2-3 y  a      0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Serverd  H                  databases. If you install the PATHWORKS Advanced ServerA                  software, the Upgrade utility is also installed.   D               5. Do you want to preserve the PATHWORKS (LAN Manager)/                  environment, and if so, where?t  C                  If you are upgrading from PATHWORKS (LAN Manager),sC                  you can choose to have the PATHWORKS (LAN Manager)/E                  data files copied to the location you specify in the E                  installation procedure. This allows you to roll backgD                  to PATHWORKS (LAN Manager) later, after configuringE                  and starting the PATHWORKS Advanced Server. Refer to C                  the Compaq PATHWORKS for OpenVMS (Advanced Server) F                  Server Migration Guide for more information about the.                  PATHWORKS Rollback procedure.  D                  If you have V4.x of PATHWORKS for OpenVMS, you mustE                  upgrade to PATHWORKS (LAN Manager) before installing @                  PATHWORKS V6 for OpenVMS (Advanced Server). ForD                  instructions on upgrading from V4.x to V5, refer toC                  the Compaq PATHWORKS for OpenVMS (Advanced Server)n(                  Server Migration Guide.  A               6. Do you want to install PATHWORKS Advanced Server                   software?  ?                  This option allows you to install the completed@                  PATHWORKS for OpenVMS (Advanced Server) server,F                  including the Upgrade utility, the integrated LicenseB                  Server, and the external authentication software.  @                  Appendix B, Sample Complete Server InstallationC                  and Configuration, shows a sample installation and D                  configuration of the complete PATHWORKS for OpenVMS*                  (Advanced Server) server.  F               7. 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 Server B                  software only. Compaq recommends that you run theB                  standalone License Server on a designated License                  Server system.t    4         2-4 Installing the PATHWORKS Advanced Server c  s      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  C                  The installation procedure gives you the option tosD                  install the standalone License Server software fromE                  the PATHWORKS for OpenVMS (Advanced Server) software(C                  kit. In this case, the complete PATHWORKS Advanced D                  Server (including the file and print server) is notE                  installed. If the complete PATHWORKS Advanced Server G                  is installed, you cannot choose the standalone Licenseh,                  Server installation option.  J                  Appendix C, Sample Standalone License Server InstallationC                  and Configuration, shows a sample installation and @                  configuration of the standalone License Server.  F               8. Do you want to install PATHWORKS external authentica-$                  tion software only?  F                  If you have installed the Advanced Server and enabledC                  external authentication in an OpenVMS Cluster thatnF                  includes Alpha systems running OpenVMS 7.2-1 or laterE                  and VAX systems running OpenVMS 7.2 or later, and if D                  these systems boot from a system disk that will notD                  have the Advanced Server installed, you can installH                  the standalone external authentication software on thatD                  system disk. For more information, see Section 1.5,B                  About External Authentication. Appendix E, SampleE                  External Authentication Installation, shows a sampleiG                  installation of the standalone external authenticationt                  software.  A               9. What is the user identification code (UIC) group                   number?  E                  The PATHWORKS Advanced Server installation procedureaC                  creates the OpenVMS user accounts PWRK$DEFAULT andrB                  PWRK$GUEST, if they do not already exist. When anF                  OpenVMS user account is created, it is assigned a UICE                  group number. The default selection displayed by thesA                  installation procedure is determined as follows:a  H                  _______________________________________________________H                  Condition__________________Default_Displayed___________  F                  You are installing         The first available unusedF                  PATHWORKS Advanced Server  UIC group number, starting4                  for the first time         with 360  H                             Installing the PATHWORKS Advanced Server 2-5 l  h      0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Server   H                  _______________________________________________________H                  Condition__________________Default_Displayed___________  A                  PATHWORKS (LAN Manager)    The same group number C                  is currently installed,    as that associated with @                  an account named           the existing account8                  PCFS$ACCOUNT already       PCFS$ACCOUNT                  exists   H                  The file and print server  The same group number as theH                  accounts_already_exist_____existing_accounts___________  '         2.2.2 How to Respond to Promptsp  ?               An asterisk (*) at the beginning of a line in the:E               installation procedure identifies a prompt to which yous               must respond.   @               Usually the prompt has a default answer, which theC               procedure displays in square brackets ([]) at the end                of the question.  =               To accept a default, press Return. For example:   8               * Is the selection correct [YES]? <Return>  $         2.2.3 How to Start VMSINSTAL  E               When you have completed the recommended preinstallation G               tasks outlined in Chapter 1, Before You Install PATHWORKS C               Advanced Server, and have read the release notes, you F               are ready to use the VMSINSTAL installation procedure toH               install the PATHWORKS Advanced Server. To start VMSINSTAL:  E               1. Ensure that you are logged in to the SYSTEM account.   E               2. Load the installation kit media onto a drive. (It issD                  not necessary to mount the drive, but it must be onG                  line so that the installation procedure can mount it.)a  G               3. Enter the following command to check the status of theKF                  device on which you have loaded the installation kit,F                  replacing device_name with the name of the applicable                  device:  *                  $ SHOW DEVICE device_name  4         2-6 Installing the PATHWORKS Advanced Server i  a      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server                    For example:   '                  $ SHOW DEVICE $1$DUS0:P  M                  Device             Device  Error  Volume  Free    Trans  MntnM                   Name              Status  Count  Label   Blocks  Count  CnteM                  $1$DUS0: (HSC001)  Mounted     0  HUBSYS  347718    628    4b  E                  If the device status is Offline, enter the following F                  command to place the device online, replacing device_3                  name with the name of your device:h  3                  $ SET DEVICE/AVAILABLE device_name   =               4. Change your default directory to SYS$UPDATE:   )                  $ SET DEFAULT SYS$UPDATEl  F               5. Check to make sure that other users are not logged in                  to the system.z  C               6. If a previous version of the software is installedIE                  on the system, shut it down. In a cluster, shut down F                  the software on all cluster members. For a noncluster                  server, enter:   -                  $ @SYS$STARTUP:PWRK$SHUTDOWNa  -                  For a cluster server, enter:h  5                  $ @SYS$STARTUP:PWRK$SHUTDOWN CLUSTERg  E               7. If you have DECnet configured on your system and you.D                  want to create a log of the installation procedure,C                  enter the following command and then log in to the &                  system account again:  +                  $ SET HOST 0/LOG=file-namem  E                  where file-name is the name of the file to which you &                  want the log written.  @               8. Start VMSINSTAL and specify the PWRK061 product>                  identifier, the media device, and whether youC                  want access to the online release notes during thes(                  installation procedure:  H                             Installing the PATHWORKS Advanced Server 2-7           0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Server   H         ________________________________________________________________          Access the Release NotesH         During_Installation?______Command_Line__________________________  H         Yes                       @VMSINSTAL PWRK061 device_name OPTIONS#                                   N   H         No________________________@VMSINSTAL_PWRK061_device_name________  G               9. The interactive installation procedure begins, and yout.                  are prompted for information.  A                  A sample installation script is included section ?                  by section, beginning with Example 2-1, Sample A                  Installation Procedure-Part 1, with each section C                  accompanied by additional explanatory information.r  D                  The actual installation script that is displayed onC                  your system might include additional questions and F                  information, depending on your current configuration.  F                 ________________________Note  ________________________  >                 To interrupt the installation procedure, press@                 <Ctrl/Y> at any time. The installation procedure@                 deletes any files that were created, then exits.>                 Then you can restart the installation from the                 beginning.  E                 _____________________________________________________o  8         Example 2-1 Sample Installation Procedure-Part 1  F         $@SYS$UPDATE:VMSINSTAL PWRK061 SYS$DEVICE:[KITS.PWRK] <Return>  L                 OpenVMS AXP Software Product Installation Procedure V7.2-1H1  #         It is 13-JUL-2001 at 16:59.m  7         Enter a question mark (?) at any time for help.n  H                                                 (continued on next page)      4         2-8 Installing the PATHWORKS Advanced Server A  O      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  @         Example 2-1 (Cont.) Sample Installation Procedure-Part 1  F         %VMSINSTAL-W-ACTIVE, The following processes are still active:                TCPIP$ESNMP                TCPIP$OS_MIBS                TCPIP$HR_MIBe9         * Do you want to continue anyway [NO]? Y <Return>N  O         * Are you satisfied with the backup of your system disk [YES]? <Return>e  1         The following products will be processed:              PWRK V6.1   <                 Beginning installation of PWRK V6.1 at 16:59  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...I         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to          SYS$HELP.   2                 PATHWORKS for OpenVMS Installation  C             Compaq Computer Corporation 2000. All rights reserved.r  I            Restricted Rights: Use, duplication, or disclosure by the U.S.eM            Government is subject to restrictions as set forth in subparagraph M            (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR -            52.227-14 Alt. III, as applicable.a  H            This software is proprietary to and embodies the confidentialI            technology of Compaq Computer Corporation. Possession, use, oraN            copying of this software and media is authorized only pursuant to aJ            valid written license from Compaq or an authorized sublicensor.  F                 __________Explanatory  Text for Example 2-1 __________  >                 In Example 2-1, Sample Installation Procedure-A                 Part 1, the installer specifies the source device @                 SYS$DEVICE:[KITS.PWRK] for the installation kit.  C                 The first part of the installation script indicates >                 that certain processes are already running andB                 gives you the option of continuing or stopping the@                 procedure. In this example, the processes listedB                 are part of the Compaq TCP/IP Services for OpenVMS/                 software running on the system.   H                             Installing the PATHWORKS Advanced Server 2-9           0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Servera  @                 If you continue (respond YES to the prompt), theC                 procedure asks if you are satisfied with the backupo=                 (backup of the system is recommended prior to ?                 installing the server), and then identifies the (                 product being installed.  E                 _____________________________________________________   8         Example 2-2 Sample Installation Procedure-Part 2  =             Please select from the following install options:H  8             PATHWORKS V6.1 for OpenVMS (Advanced Server)N             PATHWORKS V6.1 for OpenVMS (Advanced Server) License Server (only)1             External Authentication images (only)c  N         * Do you want to install the complete PATHWORKS V6.1 for OpenVMS [NO]?         Y <Return>M         %PWRK-I-OLDVERPWRK, PATHWORKS V6.0-400D for OpenVMS (Advanced Server)44         -PWRK-I-OLDVERPWRK, was previously installed  3         The following components will be installed:   <                 PATHWORKS V6.1 for OpenVMS (Advanced Server)  D         If the selection is correct, the installation will continue.G         If the selection is not correct, you can change your selection. ?         Press CTRL/Y if you want to terminate the installation.r  2         * Is the selection correct [YES]? <Return>  F                 __________Explanatory  Text for Example 2-2 __________  ?                 This part of the script gives you the option ofsA                 installing the complete PATHWORKS Advanced Server ?                 product, installing only the standalone Licensei?                 Server, installing only the standalone external =                 authentication images, or installing only thei                  Upgrade utility.  B                 In Example 2-2, Sample Installation Procedure-PartB                 2, the complete installation was selected, and theC                 procedure continues. A message indicates a previous     5         2-10 Installing the PATHWORKS Advanced Serverh           H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  D                 version of the Advanced Server has been installed on                 this system.  E                 _____________________________________________________       8         Example 2-3 Sample Installation Procedure-Part 3  F         %PWRK-I-VERSION, Checking for OpenVMS version 6.2, or later...               NOTE             ----K             Because this kit provides a new streams execlet for NetBEUI and J             TCP/IP, you MUST reboot the system to complete installation ofN             PATHWORKS.  If you do not reboot the system at this time, you must?             remember to reboot later before starting PATHWORKS.T  K             To complete the installation of this product, you should rebootLM             the system.  If it is not convenient to reboot at this time, then /             enter NO to the following question.i  F             If you enter NO, the installation procedure will continue.  J         * Will you allow a system shutdown after this product is installed         [YES]? <Return> <         * How many minutes for system shutdown [0]: <Return>F         * Do you want to do an automatic system reboot [YES]? <Return>N         * Do you want to run the IVP after the installation is finished [YES]?         <Return>  B         * Do you want to purge files replaced by this installation         [YES]? <Return> 9         %PWRK-I-FREEBLKS, Checking for 160000 free blocksF  J           ****************************************************************I           * You must shut down the Advanced Server before you continue  * 5           * installing PATHWORKS V6 for OpenVMS.    *oJ           ****************************************************************  P             If you do not shut down the server, the installation will terminate.  F         * Do you want to shut down the Advanced Server [YES]? <Return>8         Shutting down the currently running server(s)...  H                            Installing the PATHWORKS Advanced Server 2-11 n         0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Serveri      F                 __________Explanatory  Text for Example 2-3 __________  >                 In Example 2-3, Sample Installation Procedure-B                 Part 3, the installation procedure checks that the@                 OpenVMS system for installation of the server isA                 OpenVMS Version 6.2 or later. If it is an earlier 6                 version, the installation would abort.  B                 The installation procedure then checks for circum-D                 stances requiring a system reboot. A reboot might be                 needed if:  @                 o  A previous version of a server driver (PCF orA                    PCI) or of an execlet (PWRK$STREAMSOS_Vn.EXE), ?                    was detected in memory. The previous version >                    could be from either an Advanced Server forC                    OpenVMS or PATHWORKS for OpenVMS product. RebootRC                    is required before starting the Advanced Server.t  E                 o  System parameters were changed (in MODPARAMS.DAT),uB                    or server parameters were changed in a way thatA                    affected system parameters. Reboot is requiredt=                    before configuring the Advanced Server, as C                    noted in Chapter 1, Before You Install PATHWORKS #                    Advanced Server.n  B                 If a Compaq OpenVMS file and print server has been@                 installed and started previously, certain imagesB                 remain in system memory even after the product has@                 been stopped or removed. As a result, before theB                 Advanced Server can be started, you need to reboot?                 the system to remove the old image from memory.   ;                 To help minimize downtime, the installation <                 procedure requests a reboot only if and when=                 necessary. You are not forced to reboot aftert                 installation.h  B                 In Example 2-3, Sample Installation Procedure-Part@                 3, software from an earlier version of PATHWORKSD                 for OpenVMS was detected (such as an earlier versionC                 of the PWRK$STREAMSOS_Vn.EXE execlet; note that the B                 version, n, corresponds to the version of OpenVMS,?                 not of PATHWORKS). A reboot is necessary unless   5         2-12 Installing the PATHWORKS Advanced Servere e  d      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  B                 you do not plan to run the Advanced Server on this                 system.e  B                 The installation procedure gives you the option of@                 delaying the reboot by continuing the procedure.B                 You might want to delay the reboot so that you can@                 complete installation or configuration processesC                 that would be expedient to finish before rebooting._=                 For example, when installing the server on anuA                 OpenVMS Cluster, you might want to delay a reboot >                 until you complete the server installation and:                 configuration on all nodes of the cluster.  A                 To delay the reboot, continuing the installation, A                 enter NO at the prompt asking if you will allow a B                 system shutdown after the product is installed. InC                 this example, the reboot is opted for, and then the_A                 procedure prompts the installer for the number ofA=                 minutes to elapse before the shutdown occurs.n  C                 The installer is also prompted whether an automatic D                 system reboot is requested, whether the installation>                 verification procedure should be run after theD                 installation, and whether to purge files replaced byC                 this installation or keep previous versions intact. D                 The installation verification procedure (IVP) can beB                 run automatically, as shown in Example 2-5, Sample?                 Installation Procedure-Part 5, or independentlys>                 of the installation procedure, as described in@                 Section 5.2, Verifying the PATHWORKS for OpenVMS/                 (Advanced Server) Installation.   E                 _____________________________________________________   8         Example 2-4 Sample Installation Procedure-Part 4    H                                                 (continued on next page)              H                            Installing the PATHWORKS Advanced Server 2-13 H  K      0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Server   @         Example 2-4 (Cont.) Sample Installation Procedure-Part 4  H                       User Accounts and User Identification Codes (UICs)H                       --------------------------------------------------  P           PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account,P           PWRK$DEFAULT, and  a guest account, PWRK$GUEST.  The default UIC groupF           number for both these new accounts depends on the following:  O           o If you are installing the server for the first time, the default isoA             the first unused UIC group number, starting with 360.w  P           o If there is an existing account PCFS$ACCOUNT, the default is the UIC6             group number associated with PCFS$ACCOUNT.  K           o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, theeK             default is the UIC group number associated with PWRK$DEFAULT or2L             PWRK$GUEST, in preference to PCFS$ACCOUNT.  However, the default!             UIC group number will C             not be used to change the UIC of any existing accounts.   P             For more information about UIC group numbers, see the OpenVMS System             Manager's Manual.   O         * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]:          <Return>  B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.  H         %PWRK-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and         PWRK$GUESTB         %PWRK-I-DEFAULTEXISTS, PWRK$DEFAULT account already exists>         %VMSINSTAL-I-RESTORE, Restoring product save set C ...>         %VMSINSTAL-I-RESTORE, Restoring product save set E ...I         %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAILI:         %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commandsM         %PWRK-I-SPECIFY, Specifying target directories for the provided filesu1         %PWRK-I-OBSOLETE, Deleting obsolete files   1                                        Next Steps 1                                        ----------   M           To continue the installation procedure, enter the following commandf@           to execute the server configuration command procedure:  H                                                 (continued on next page)  5         2-14 Installing the PATHWORKS Advanced Servero    i      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  @         Example 2-4 (Cont.) Sample Installation Procedure-Part 4  #           $ @SYS$UPDATE:PWRK$CONFIG,  L           For information about the configuration command procedure, see theK           PATHWORKS (Advanced Server) Installation and Configuration Guide.   	         $ G         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target          directories...    F                 __________Explanatory  Text for Example 2-4 __________  >                 In Example 2-4, Sample Installation Procedure-B                 Part 4, the script prompts for a default UIC groupA                 number. It does so only if you are installing theSB                 complete PATHWORKS Advanced Server product. If youB                 do not want to associate the newly created OpenVMS=                 accounts PWRK$DEFAULT and PWRK$GUEST with therD                 default user identification code (UIC) group number,=                 specify another three-digit UIC group number.   C                 At this point, all questions have been answered andlD                 the installation process continues. The installation@                 procedure then reminds the installer to continue>                 with the configuration process by invoking the8                 PWRK$CONFIG.COM configuration procedure.  E                 _____________________________________________________   8         Example 2-5 Sample Installation Procedure-Part 5  :          Copyright Compaq Computer Corporation 1993, 2001.  5          Starting Installation Verification Procedure 9          for PATHWORKS V6.1 for OpenVMS (Advanced Server)   2         %PWRK-I-NORMAL, IVP completed successfully5          Installation of PWRK V6.1 completed at 17:05   F             Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  H                                                 (continued on next page)  H                            Installing the PATHWORKS Advanced Server 2-15 .  K      0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Server   @         Example 2-5 (Cont.) Sample Installation Procedure-Part 5  N             Creating installation data file: VMI$ROOT:[SYSUPD]PWRK061.VMI_DATA  G         %VMSINSTAL-I-SHUTDOWN, This product requires that the system bee         rebooted.   7          SHUTDOWN -- Perform an Orderly System ShutdownS#                      on node TINMAN   C         Do you really want to shutdown node TINMAN [NO]? Y <return> *          VMSINSTAL procedure done at 17:09  F                 __________Explanatory  Text for Example 2-5 __________  B                 In Example 2-5, Sample Installation Procedure-PartD                 5, the procedure verifies the installation, and then                 finishes.r  E                 _____________________________________________________   F               Table 2-1, Installation Questions includes details aboutG               most of the prompts that VMSINSTAL might display, depend- G               ing on the environment and options you select. Table 2-1,LD               Installation Questions does not show any informationalB               messages. For a complete sample installation script,E               see Appendix B, Sample Complete Server Installation and                Configuration.  H         Table_2-1_Installation_Questions________________________________  A                                                         Action or @                                                         ResponseH         Question___________Your_Desired_Result__________Required________  @         Are you            Continue                     <Return>         satisfied with         the backup of          your system disk         [YES]?  H                                                 (continued on next page)      5         2-16 Installing the PATHWORKS Advanced Server_ _  l      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action orp@                                                         ResponseH         Question___________Your_Desired_Result__________Required________  :                            Exit                         NO  9         Select option      Display the release notes    1cC         [2]:[1]            on the screen                To stop the   F                                                         display at anyC                                                         time, press A                                                         <Ctrl/C>.o  E                            Print the release notes      2 or <Return>i  H                                                         You are promptedC                                                         for a printeC                                                         queue name,_G                                                         and the release-E                                                         notes file ismC                                                         sent to theeG                                                         specified queueSD                                                         (the defaultF                                                         print queue isC                                                         SYS$PRINT).   H         [1]This_question_is_displayed_only_if_you_specify_OPTIONS_N_whenH         you start the VMSINSTAL command procedure or if there are active          processes on the system.  H                                                 (continued on next page)                      H                            Installing the PATHWORKS Advanced Server 2-17 s  c      0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Servere  H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action ors@                                                         ResponseH         Question___________Your_Desired_Result__________Required________  9                            Print the release notes      3oH                            and display them on the      You are promptedC                            screen                       for a print   C                                                         queue name,,G                                                         and the releaserE                                                         notes file isnC                                                         sent to the G                                                         specified queue D                                                         (the defaultF                                                         print queue isC                                                         SYS$PRINT)._  C                                                         To stop the-F                                                         screen displayD                                                         at any time,G                                                         press <Ctrl/C>.P  9                            Continue without dis-        4 2                            playing or printing the(                            release notes  @         Do you want        Install one or more          <Return>"         to install the     servers         upgrade utility          only [NO]?[2]I  ;                            Install only the Upgrade     YES "                            utility  H         [2]The_release_notes_are_automatically_copied_to_SYS$HELP.______  H                                                 (continued on next page)            5         2-18 Installing the PATHWORKS Advanced Server  t  n      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action orR@                                                         ResponseH         Question___________Your_Desired_Result__________Required________  ;         Do you want to     Continue                     YES          continue the         installation         [NO]?[1]  @                            Exit                         <Return>  ;         Do you want        Install the PATHWORKS        YESl*         to install         Advanced Server         the complete         PATHWORKS V6.1         for OpenVMSh
         [NO]?n  @                            Omit the PATHWORKS           <Return>*                            Advanced Server  @         Do you want to     Retain the PATHWORKS V5      <Return>4         preserve the V5    for OpenVMS (LAN Manager)2         (LAN Manager)      environment so that you/         environment        can use the rollback-1         [YES]?[2]          procedure described ine3                            the Compaq PATHWORKS fori4                            OpenVMS (Advanced Server)1                            Server Migration Guide   :                            Not retain the V5            NO&                            environment  H         [1]This_question_is_displayed_only_if_you_specify_OPTIONS_N_whenH         you start the VMSINSTAL command procedure or if there are active          processes on the system.B         [2]The release notes are automatically copied to SYS$HELP.  H                                                 (continued on next page)      H                            Installing the PATHWORKS Advanced Server 2-19 A  O      0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Servere  H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action ora@                                                         ResponseH         Question___________Your_Desired_Result__________Required________  @         Enter the          Preserve the V5 envi-        <Return>1         directory to       ronment in the default *         preserve the       directory shown         V5 environment$         [SYS$SYSDEVICE:[000000]]:[3]  C                            Preserve the V5 environ-     A differenteA                            ment on another device or    device or B                            in another directory         directory.  ;         Do you want        Install the standalone       YESfC         to install         License Server               This optionlD         the PATHWORKS                                   installs theF         License Server                                  License ServerE         only [NO]?[4]                                   and transportl  H                                                         software withoutE                                                         the PATHWORKSr@                                                         AdvancedE                                                         Server. Refer E                                                         to Chapter 4,sC                                                         Configuring D                                                         and StartingF                                                         the StandaloneF                                                         License Server@                                                         for moreD                                                         information.  H         [3]This_question_is_displayed_only_if_your_system_is_currently__,         running the PATHWORKS (LAN Manager).G         [4]This question is displayed only if you chose to preserve thed;         PATHWORKS V5 for OpenVMS (LAN Manager) environment.o  H                                                 (continued on next page)        5         2-20 Installing the PATHWORKS Advanced Server  p  e      H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action or @                                                         ResponseH         Question___________Your_Desired_Result__________Required________  @                            Install the PATHWORKS        <Return>C                            Advanced Server with the     This option B                            License Server               causes the  D                                                         installationD                                                         procedure toF                                                         proceed to theF                                                         next question.  ;         Do you want to     Install only the external    YES C         install only       authentication software      This optionf@         the external                                    installsD         authentication                                  the externalF         images [NO]?[4]                                 authentication  H                                                         software withoutE                                                         the PATHWORKSuH                                                         Advanced Server.  @                            Install the complete         <Return>C                            PATHWORKS Advanced Server    This option B                            or install the standalone    causes theD                            License Server               installation  D                                                         procedure toG                                                         repeat previouslA                                                         questionsTC                                                         so that yousB                                                         can selectD                                                         the completeA                                                         PATHWORKS G                                                         Advanced ServeruC                                                         or only theeG                                                         License Server.t  H         [4]This_question_is_displayed_only_if_you_chose_to_preserve_the_;         PATHWORKS V5 for OpenVMS (LAN Manager) environment.   H                                                 (continued on next page)  H                            Installing the PATHWORKS Advanced Server 2-21 e         0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Server   H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action or @                                                         ResponseH         Question___________Your_Desired_Result__________Required________  @         Is the selection   Use the selection            <Return>         correct [YES]?  :                            Change the selection         NO  @                            Terminate the installation   <Ctrl/Y>  @         Will you allow a   Shut down the system         <Return>1         system shutdown    as part of the product-1         after this         installation procedureo         product is         installed [YES]?  :                            Complete the installation    NOG                            procedure without shutting   System shutdown D                            down the system              is required,  C                                                         to complete C                                                         the product)H                                                         installation. IfF                                                         you answer NO,E                                                         you must shutvG                                                         down the system F                                                         manually afterH                                                         the installationD                                                         procedure isA                                                         finished.   @         Do you want to     Reboot the system            <Return>5         do an automatic    automatically after systema#         system reboot      shutdownr         [YES]?  :                            Reboot the system manually   NO  H                                                 (continued on next page)      5         2-22 Installing the PATHWORKS Advanced Server            H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action orv@                                                         ResponseH         Question___________Your_Desired_Result__________Required________  @         Do you want        Run the Installation         <Return>1         to run the         Verification Procedureg4         IVP after the      (IVP) automatically after5         installation is    the installation procedurel$         finished [YES]?    completes  :                            Not run the IVP              NO  ?                                                         You can C                                                         run the IVPRF                                                         independent ofH                                                         the installationB                                                         procedure.D                                                         For detailedF                                                         information onG                                                         running the IVP F                                                         independently,H                                                         see Section 5.2,E                                                         Verifying the A                                                         PATHWORKSmC                                                         for OpenVMSaA                                                         (AdvancedT?                                                         Server)rE                                                         Installation.a  @         Do you want        Purge all files it           <Return>#         to purge files     replaces          replaced by this         installation         [YES]?  :                            Not purge any files it       NO#                            replacesi  H                                                 (continued on next page)        H                            Installing the PATHWORKS Advanced Server 2-23           0         Installing the PATHWORKS Advanced Server!         2.2 Installing the Server   H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action or @                                                         ResponseH         Question___________Your_Desired_Result__________Required________  @         Do you want to     Delete the files and         <Return>4         continue with      continue the installation         the installation         [YES]?[5]   :                            Leave the files intact and   NO5                            terminate the installation   @         Do you want        Shut down the License        <Return>2         to shut down       Server and continue the'         the PATHWORKS      installation          License Server         [YES]?[6]g  :                            Keep the server running      NO,                            and terminate the'                            installatione  @         Do you want        Shut down the server and     <Return>4         to shut down       continue the installation         the PATHWORKS          Advanced Server          [YES]?[6]_  :                            Keep the server running      NO,                            and terminate the'                            installationt  H         [5]This_question_is_displayed_only_if_you_chose_not_to_install__&         the PATHWORKS Advanced Server.G         [6]This question is displayed only if there are PATHWORKS files '         in system-specific directories.r  H                                                 (continued on next page)        5         2-24 Installing the PATHWORKS Advanced Servere n         H                                 Installing the PATHWORKS Advanced ServerH                                                2.2 Installing the Server  H         Table_2-1_(Cont.)_Installation_Questions________________________  A                                                         Action or @                                                         ResponseH         Question___________Your_Desired_Result__________Required________  @         Enter default      Associate the newly          <Return>.         UIC group          created OpenVMS ac-2         number for         counts PWRK$DEFAULT and2         PWRK$DEFAULT and   PWRK$GUEST with the de-4         PWRK$GUEST[nnn]:   fault user identification2                            code (UIC) group number                             (nnn)  E                            Associate the newly          A three-digit C                            created accounts with        UIC number. D                            the UIC group number you     For detailedC                            specify                      information   G                                                         about UIC groupgD                                                         numbers, seeC                                                         the OpenVMS H                                                         System Manager'sH         ________________________________________________Manual._________  9         2.2.4 What To Do After the Installation Completest  F               If you have installed the external authentication imagesF               only, you can proceed to enable external authentication,>               as explained in Section 5.6, Setting Up ExternalG               Authentication. For other installations, do the following /               after the installation completes:   E               1. If you had a previous version of the Advanced Server B                  running on your system, reboot your system beforeA                  configuring the newly installed Advanced Server. E                  See the discussion in the explanatory text following C                  Example 2-3, Sample Installation Procedure-Part 3.   @               2. Proceed to Chapter 3 to configure the PATHWORKS!                  Advanced Server.o  E               Appendix F, PATHWORKS Advanced Server Files and On-DisknA               Structure, lists and describes files created by thet%               installation procedure.   H                            Installing the PATHWORKS Advanced Server 2-25 i         0         Installing the PATHWORKS Advanced Server1         2.3 Troubleshooting Installation Problemsa  1         2.3 Troubleshooting Installation Problems   C               The following sections describe some problems you canrG               encounter if you install the PATHWORKS Advanced Server inl5               an environment that is not appropriate.u  F         2.3.1 Installing PATHWORKS Advanced Server on a System Running+               Another Advanced Server Image   H               If you attempt to install the PATHWORKS Advanced Server onF               a system, or anywhere in a cluster, on which a PATHWORKSA               for OpenVMS or Advanced Server for OpenVMS image is D               running, the installation procedure displays a message$               such as the following:  J         ******************************************************************E         * You must shut down the Advanced Servers on all nodes in theeJ         * cluster before you continue installing PATHWORKS V6 for OpenVMS.J         ******************************************************************  B         If you do not shut down the servers, the installation will         terminate.  F               Shut down the servers on all nodes in the cluster before+               continuing your installation.   G         2.3.2 Installing the PATHWORKS Advanced Server on a System with                 the NetWare Server  D               The PATHWORKS Advanced Server cannot be installed on aF               system where the NetWare server is installed. If you at-H               tempt to install the PATHWORKS Advanced Server on a systemE               where the NetWare server is installed, the installation F               procedure optionally invokes the NetWare server software@               removal procedure (SYS$STARTUP:PWVN$DEINSTAL.COM).  E               When the installation procedure detects the presence of G               the NetWare server, it displays the following message andt               question:   N               %PWRKV60-E-OLDVERPWNV, PATHWORKS V6.0-nnnx for OpenVMS (NetWare)M               was previously installed.  This product is no longer supported.rL               To install the PATHWORKS V6.1 for OpenVMS product, the NetWare*               product must be deinstalled.  G               * Will you allow this installation procedure to deinstall )               * the NetWare product [NO]?   5         2-26 Installing the PATHWORKS Advanced Server            H                                 Installing the PATHWORKS Advanced ServerH                                2.3 Troubleshooting Installation Problems  ?               To remove the NetWare server software, enter YES.n  F               To terminate the installation procedure without removingG               the NetWare server software, enter NO, or press <Return>.   B               You can remove the NetWare server manually using theF               procedure in Section 7.2, Removing the PATHWORKS NetWareH               Server. Then start the VMSINSTAL procedure again after the.               NetWare server has been removed.  C         2.3.3 Installing PATHWORKS Advanced Server on a System withh%               PATHWORKS (LAN Manager)   H               You can upgrade PATHWORKS V5 for OpenVMS (Advanced Server)C               to PATHWORKS V6 for OpenVMS (Advanced Server). If the G               system has PATHWORKS (LAN Manager) installed, you can use G               the Upgrade utility, as described in the Compaq PATHWORKS F               for OpenVMS (Advanced Server) Server Migration Guide, toG               upgrade server information before you configure and start ,               the PATHWORKS Advanced Server.  B         2.3.4 Installing the Standalone License Server on a SystemD               Where the PATHWORKS Advanced Server Has Been Installed  F               If you install the standalone License Server on a systemE               where the PATHWORKS Advanced Server has been installed, H               the installation procedure displays the following message:  L               The PATHWORKS Advanced Server was previously installed and youL               have selected to install the License Server only.  Because theH               PATHWORKS Advanced Server includes the License Server, theC               complete PATHWORKS Advanced Server must be installed.   ?               The installation procedure will choose to installpC               the PATHWORKS Advanced Server. You have the option ofKE               continuing with this installation, or you can terminatesA               the installation procedure by pressing <Ctrl/Y>. ToeC               install the standalone License Server on this system,iA               you must first remove the PATHWORKS Advanced ServerdH               software using the PWRK$DEINSTAL.COM command procedure, asH               described in Chapter 7, Removing PATHWORKS Advanced ServerA               Software. Then start the VMSINSTAL procedure again.i  D               For a sample installation and configuration script forC               the standalone license server, see Appendix C, Sample G               Standalone License Server Installation and Configuration.e  H                            Installing the PATHWORKS Advanced Server 2-27 R         0         Installing the PATHWORKS Advanced Server1         2.3 Troubleshooting Installation Problems   =         2.3.5 Installing the External Authentication Software   E               You cannot install the external authentication software B               only, if you have previously installed the PATHWORKSB               Advanced Server. The installation procedure displaysF               the following message if you try to install the external>               authentication images under these circumstances:  G         The PATHWORKS Advanced Server was previously installed, and you          have selected G         to install the external authentication images only. Because the N         PATHWORKS Advanced Server includes the external authentication images,         the B         complete PATHWORKS Advanced Server must also be installed.  D               You must remove the PATHWORKS Advanced Server softwareC               to be able to select this option. To remove PATHWORKSrH               Advanced Server software, run the PWRK$DEINSTAL procedure,D               as described in Chapter 7, Removing PATHWORKS Advanced               Server Software.  ?               For a sample installation script for the externalnD               authentication images, see Appendix E, Sample External*               Authentication Installation.           2.4 Next Steps  H               To continue, depending on the software you are installing,:               proceed as indicated in the following table:  H         ________________________________________________________________E                               Where to Go Next in   What Is Described H         Software_Installed____the_Documentation_____There_______________  A         PATHWORKS Advanced    Chapter 3,            Configure the F         Server (file and      Configuring the       PATHWORKS Advanced;         print server)         PATHWORKS Advanced    Server. $                               Server  A         Standalone license    Chapter 4,            Configure theeF         server                Configuring and       standalone license;                               Starting the          server.d0                               Standalone License$                               Server  5         2-28 Installing the PATHWORKS Advanced Servere e  r      H                                 Installing the PATHWORKS Advanced ServerH                                                           2.4 Next Steps  H         ________________________________________________________________E                               Where to Go Next in   What Is Described_H         Software_Installed____the_Documentation_____There_______________  C         Upgrade utility only  Compaq PATHWORKS for  Use the UpgradeaE                               OpenVMS (Advanced     utility to createeD                               Server) Server        and edit upgrade<                               Migration Guide       reports.  D         Standalone external   Section 5.6,          Set up PATHWORKSD         authentication        Setting Up External   external authen-C         software              Authentication        tication on thewH         ____________________________________________system._____________                                                                H                            Installing the PATHWORKS Advanced Server 2-29                       H                                                                        3H         ________________________________________________________________  H                                Configuring the PATHWORKS Advanced Server      C               This chapter describes how to configure the PATHWORKS E               Advanced Server and consists of the following sections:r  E               o  Section 3.1, About the Advanced Server Configurationn                  Procedure  B               o  Section 3.2, Before You Start the Advanced Server(                  Configuration Procedure  >               o  Section 3.3, How to Start the Advanced Server(                  Configuration Procedure  ?               o  Section 3.4, How to Respond to Advanced Server?&                  Configuration Prompts  A               o  Section 3.5, How to Change Default Configuration                   Settings)  D               o  Section 3.6, Configuring the Advanced Server Domain                  Role   E               o  Section 3.7, Troubleshooting Configuration Procedure                   Problems   A               o  Section 3.8, The Advanced Server Network AdapterQ  (               o  Section 3.9, Next Steps  =         3.1 About the Advanced Server Configuration Procedure   B               The Advanced Server initial configuration procedure,E               PWRK$CONFIG.COM, is installed by the PATHWORKS Advanced B               Server installation procedure. Like the installationF               procedure, the configuration procedure asks you a seriesF               of questions (by displaying prompts). The procedure usesF               your answers to configure the PATHWORKS Advanced Server.  H                            Configuring the PATHWORKS Advanced Server 3-1           1         Configuring the PATHWORKS Advanced Server =         3.1 About the Advanced Server Configuration Procedure   H               You can use the PWRK$CONFIG.COM configuration procedure toE               reconfigure the server at any time later. Note that the C               script contents change after the first configuration.   3         3.1.1 What the Configuration Procedure Does   :               PWRK$CONFIG.COM is a command procedure that:  >               o  Creates the PATHWORKS Advanced Server on-diskH                  structure. (Appendix F, PATHWORKS Advanced Server FilesE                  and On-Disk Structure, shows the on-disk structure).   A               o  Upgrades any existing file and print server user D                  account and share databases, such as when upgrading4                  the server from a previous version.  F               o  If configuring a previously configured server, storesD                  the original accounts database in specially-createdG                  directories. (For more information, see Section 3.7.2,aB                  If Problems Occur When Reconfiguring the Advanced                  Server.)   H               o  Allows you to enter the Configuration Manager to modifyB                  system configuration parameters and to verify theC                  configuration setting against the available system G                  resources. For example, you can specify the transportsIF                  the server will run and the maximum number of clients?                  that can connect to the server simultaneously.S  F                  For more information about the Configuration Manager,D                  refer to the Compaq PATHWORKS for OpenVMS (Advanced6                  Server) Server Administrator's Guide.  G               o  Creates the PATHWORKS Advanced Server user account and_!                  share databases.w  B               o  Allows you to modify server configuration defaultC                  settings such as server role, domain name, and theY+                  services that are enabled.t  >               o  On a server that will run as a primary domainC                  controller or member server, allows you to specify 4                  the Administrator account password.  =               o  Gives you the option of starting the server.e  5         3-2 Configuring the PATHWORKS Advanced Server  K         H                                Configuring the PATHWORKS Advanced ServerH                    3.1 About the Advanced Server Configuration Procedure  H               After you install the server, you must run PWRK$CONFIG.COME               before you can start the server. In an OpenVMS Cluster,?C               before you start the server on any node, you must run D               PWRK$CONFIG.COM on each node where you plan to run theG               server. Although the nodes in an OpenVMS Cluster function_D               as a single unit in a domain, treat them as individual2               units for purposes of configuration.  >         3.2 Before You Start the Advanced Server Configuration             Procedure   E               Before you start the PWRK$CONFIG.COM command procedure, A               check that the ENQLM quota system process parameter >               for the user account from which you will run theC               PWRK$CONFIG.COM procedure is set to a value of 500 oraF               greater. For information on how to determine the currentG               setting and how to increase the value, see Section 1.9.7, C               Step 7: Check ENQLM Process Quota. In addition, checknG               the system parameters discussed in Section 1.9.6, Step 6: &               Check System Parameters.  B               Be prepared to answer the questions discussed in theH               following sections. The questions asked by PWRK$CONFIG.COME               depend on the options you select and on such factors asnG               server role and whether you are configuring the server to ,               join a new or existing domain.  B         3.2.1 On What OpenVMS Disk Device Do You Want to Store the)               Advanced Server Data Files?   %               The data files include:m  .               o  Configuration parameter files  *               o  License Server data files                 o  Log files  $               o  Printer spool files  "               o  Server data files  >               o  Security Account Manager (SAM) database files  E               o  Client-based server administration tools and license                   kits   -               o  Virtual memory section files_  H                            Configuring the PATHWORKS Advanced Server 3-3 I  a      1         Configuring the PATHWORKS Advanced Server H         3.2 Before You Start the Advanced Server Configuration Procedure  E               By default, the configuration procedure copies the data.F               files to the system device (SYS$SYSDEVICE). However, youF               can specify any existing OpenVMS disk device that has atG               least 85,000 free blocks of disk space. The amount needede2               depends on the components installed.  H               When you select a disk for the Advanced Server data files,)               keep the following in mind:s  A               o  The Advanced Server frequently accesses the data A                  files copied to the specified disk device, whichtD                  generates input to and output from the disk. HavingF                  these operations occur on the system disk can degradeC                  the performance of both the OpenVMS system and the G                  Advanced Server. Therefore, Compaq recommends that you B                  specify a disk device other than the system disk.  F               o  On an OpenVMS Cluster with multiple system disks, allH                  nodes on which you plan to run the Advanced Server mustF                  use the same disk device to store and access AdvancedD                  Server data files. Using separate disks on separate8                  cluster members is strictly prohibited.  E               o  You can run the PWRK$CONFIG.COM command procedure atiC                  any time, to change the disk device where Advancedy>                  Server data files are stored. PWRK$CONFIG.COMH                  automatically copies the data files to the new locationF                  and deletes the data files from the current location.  G         3.2.2 Do You Want to Change the System Configuration Parametersa               Now?  E               If you respond "YES" to the prompt to change the system*A               configuration parameters, the Configuration Manager A               starts. The Configuration Manager is a utility that D               allows you to modify and verify the system environmentC               configuration parameter settings, such as the maximumeC               number of clients that can connect to the server, the C               percentage of physical memory the server can use, andy7               which network transports the server uses.R  ?               You can change the system configuration parametervB               settings after starting the Advanced Server by usingC               the Configuration Manager (invoking the Configurationf?               Manager with the ADMINISTER/CONFIGURATION commande@               at the DCL prompt). For more information, refer to  5         3-4 Configuring the PATHWORKS Advanced Servery v  s      H                                Configuring the PATHWORKS Advanced ServerH         3.2 Before You Start the Advanced Server Configuration Procedure  @               the Compaq PATHWORKS for OpenVMS (Advanced Server)?               Server Administrator's Guide. Section B.2, SamplePA               Server Configuration, shows the basic Configuration A               Manager screen displayed when you opt to change theoC               system configuration parameter settings during use ofc               PWRK$CONFIG.COM.  E         3.2.2.1 Configuring Transports for a Backup Domain Controllera                  or Member Server  @               If you are configuring a server as a backup domainB               controller (BDC) or a member server, you must selectE               at least one transport that is also used by the primary H               domain controller (PDC). Otherwise, the configuration will               fail.r  D               When you select the transports to run on a server that@               will participate in wide area networking, keep the                following in mind:  @               o  In a wide area network, the TCP/IP transport isC                  required. (DECnet also supports wide area networksaF                  but the functionality it provides is not as extensiveH                  as that provided by TCP/IP.) In a cluster, all Advanced;                  Server members must be in the same subnet.   F               o  If you are configuring a BDC or member server to joinC                  an existing domain where the PDC is on a differentnC                  TCP/IP subnet, both the server you are configuringAA                  and the PDC must be configured to use the TCP/IPtD                  transport, and you must set up wide area networkingD                  using either a WINS (Windows Internet Name Service)A                  Server, a Domain Name System (DNS) server, or anAG                  LMHOSTS file for NetBIOS name resolution, as describedsE                  in Chapter 6, Implementing a Wide Area Network. (You G                  can select one, two, or all three of these methods for "                  name resolution.)  G               o  If you are using WINS for network name resolution, thenF                  PDC and any BDCs and member servers should use a WINS;                  Server to provide NetBIOS name resolution.   H                  If your Advanced Server will run in an OpenVMS Cluster,E                  to gain the benefits of load balancing and failover,tH                  clients should connect to the Advanced Server using theE                  Advanced Server cluster alias. However, the Advanced   H                            Configuring the PATHWORKS Advanced Server 3-5    t      1         Configuring the PATHWORKS Advanced Server H         3.2 Before You Start the Advanced Server Configuration Procedure  B                  Server does not dynamically register the AdvancedF                  Server cluster alias with the WINS server. Therefore,D                  you should define a static multihomed entry for theE                  Advanced Server alias in the WINS database. For more H                  information, see Section 6.3.1, Setting up WINS SupportA                  for OpenVMS Clusters. If you plan to use DNS for G                  NetBIOS name resolution, you do not define this static G                  multihomed entry in the WINS database. (If Windows 95, D                  Windows 98, or Windows NT clients are configured toH                  use both WINS and DNS for NetBIOS name resolution, theyB                  first query the WINS server to resolve the name.)  H               o  If you are using the LMHOSTS file, it must be set up onG                  the PDC as well as the BDCs and member servers. BeforeiF                  you configure any BDC or member server that is not onE                  the same subnet as the PDC, make sure that a specialnF                  NetBIOS name entry for the PDC is in the LMHOSTS fileD                  on that BDC or member server; otherwise, the BDC orB                  member server will not find the PDC and will failE                  to join the existing domain. This NetBIOS name entrycG                  should be the same as the domain name, space padded to F                  15 characters, with the hexadecimal control characterE                  1B appended to it. You map the IP address of the PDC F                  to this special name. For example, if the domain nameF                  is LANGROUP and the PDC of LANGROUP is DOMPDC with anG                  IP address of 10.20.30.40, the BDCs and member servers G                  would need to add the following lines to their LMHOSTSt                  file:  9                  10.20.30.40  DOMPDC  #PRE  #DOM:LANGROUP 9                  10.20.30.40 "LANGROUP       \0x1B"  #PREt  D                  Note that the total number of characters within theG                  quotes should always be 20 characters (the domain name B                  padded to 15 characters, plus the five characters?                  required for the hexadecimal control character                   (\0x1B)).  D                  For more information, see Chapter 6, Implementing a#                  Wide Area Network.   H                  If your Advanced Server will run in an OpenVMS Cluster,F                  other domain controllers (including the PDC) that areF                  not in the same subnet as the Advanced Server clusterB                  must add an entry for the Advanced Server cluster  5         3-6 Configuring the PATHWORKS Advanced Server            H                                Configuring the PATHWORKS Advanced ServerH         3.2 Before You Start the Advanced Server Configuration Procedure  C                  alias to their LMHOSTS file. This assumes they are D                  not using other methods (WINS or DNS) for resolvingE                  NetBIOS names. For domain operations, all the domain_F                  controllers in the cluster operate as a single domainE                  controller identified by the Advanced Server clustereG                  alias name, rather than by the specific computer namesdD                  of the individual cluster members. However, becauseF                  the LMHOSTS file does not offer any means for mappingD                  multiple IP addresses to a single NetBIOS name, theD                  entry for the Advanced Server cluster alias must beH                  mapped to the IP address of one specific server clusterB                  member. If the Advanced Server is stopped on thatD                  cluster member, you must modify the LMHOSTS file onF                  all clients and servers to map the cluster alias nameC                  to the IP address of a cluster member on which the G                  Advanced Server is still running. On systems running a E                  Microsoft Windows operating system, the NetBIOS name3F                  cache must also be reloaded using the command NBTSTAT)                  -R (capital R required).u  B                  Due to the LMHOSTS limitations noted above, it isA                  difficult (and perhaps unmanageable) to gain therA                  benefits of load balancing and failover using anc                  LMHOSTS file.  C               o  If your Advanced Server runs in an OpenVMS ClusteriB                  and you have it set up for cluster load balancingB                  using DNS, then enable the use of DNS for NetBIOSC                  name resolution on all servers and clients. Remove G                  any entries for the Advanced Server cluster alias from D                  the LMHOSTS file and WINS database. Compaq stronglyF                  recommends that the Advanced Server cluster alias notB                  be the same as the TCP/IP cluster alias (referredA                  to as the TCP/IP cluster impersonator name). ForoC                  information on setting up load balancing, refer to3C                  the Compaq PATHWORKS for OpenVMS (Advanced Server)3.                  Server Administrator's Guide.  H               To enable any of the wide area networking implementations,G               select them using the Configuration Manager, as describedyC               in the Compaq PATHWORKS for OpenVMS (Advanced Server).+               Server Administrator's Guide.r      H                            Configuring the PATHWORKS Advanced Server 3-7 s  y      1         Configuring the PATHWORKS Advanced ServereH         3.2 Before You Start the Advanced Server Configuration Procedure  C         3.2.3 Do You Want to Change Any of the Server Configuration                Settings?   :               The server configuration settings determine:  0               o  Whether the License Server runs  B                  The License Server is a software program that youE                  can run on your OpenVMS system to grant client-basedeH                  licenses. Any client that wants to use server resourcesC                  must have a valid license. Each local area networkdH                  (LAN) needs only one License Server. The client licenseH                  product authorization keys (PAKs) must be loaded on the5                  system that runs the License Server.   B                  In an OpenVMS Cluster, the PAKs must be loaded inC                  a shared license database available to all clusters                  members.   G                  The License Server runs only if you enable it with theo)                  configuration procedure.t  E                  -  If you are using client-based licensing, you mustdB                     run the License Server. Compaq recommends thatD                     you run the License Server on a different systemD                     than the Advanced Server. See Section 1.4, About4                     Licensing, for more information.  F                  -  If you are using server-based licenses, you do not3                     need to run the License Server.   =                  By default, the License Server does not run.t  4               o  Whether the Timesource service runs  A                  The Timesource service allows your server to actiC                  as a time server. Other servers on the network canfG                  synchronize with the time server to coordinate networkeC                  events (for example, running batch programs on all.G                  computers the same time each day). Each LAN needs onlyn!                  one time server.s  A                  By default, the Timesource service does not run.u  1               o  Whether the Alerter service runsm  D                  The Alerter service sends messages called alerts toD                  servers and clients that run the Messenger service.  6                  By default, the Alerter service runs.  >               o  Names of the users who receive alert messages  5         3-8 Configuring the PATHWORKS Advanced Server            H                                Configuring the PATHWORKS Advanced ServerH         3.2 Before You Start the Advanced Server Configuration Procedure  I                  By default, alert messages are sent to the Administrator                   account.   9               o  Whether the NetLogon service is enabled.t  H                  In a domain, the NetLogon service distributes a domain-F                  wide user accounts database to all domain controllersH                  running NetLogon. The service allows for single domain-E                  wide logon that enables users to access resources on B                  any server in the domain. The NetLogon service isD                  required for smooth operation of the domain; CompaqH                  recommends that the NetLogon service always be enabled,)                  even on a member server.   7                  By default, the NetLogon service runs.                  o  Domain name  D                  This is the domain in which your server is located.D                  A domain is a subdivision of clients and servers onD                  the network. For more information on domains, referG                  to the Compaq Advanced Server for OpenVMS Concepts anduD                  Planning Guide and the Compaq PATHWORKS for OpenVMS@                  (Advanced Server) Server Administrator's Guide.  G                  The default domain name is LANGROUP. You can specify a :                  name that reflects your company or group.  #               o  Role of the server   F                  This is the role of the server in the domain. You canC                  designate an Advanced Server as either the primaryoD                  domain controller (PDC), a backup domain controller@                  (BDC), or a member server. When you install theH                  Advanced Server in a new domain, the new server becomesE                  the PDC by default. In an OpenVMS Cluster, all nodes G                  on the cluster have the same role: when you change the F                  role of one, the change applies to all the servers on                  the cluster.   H                  For more details on configuring the server domain role,H                  see Section 3.6, Configuring the Advanced Server Domain                  Role.                 o  Computer name  G                  This unique name identifies your server in the domain. F                  You define this name or accept the default value when5                  you run the configuration procedure.s  H                            Configuring the PATHWORKS Advanced Server 3-9 y         1         Configuring the PATHWORKS Advanced ServereH         3.2 Before You Start the Advanced Server Configuration Procedure  C                  The PWRK$CONFIG.COM procedure will not prevent you F                  from specifying the same named PDC if another node orF                  cluster has previously been defined and is running inD                  that role. However, on the new (duplicate) PDC, theF                  NetLogon service will not be started. The PDC must be&                  unique in the domain.  F                  The default computer name is the same as the server's                  SCSNODE name.  .               o  Advanced Server cluster alias  G                  If your server is a member of an OpenVMS Cluster, thiseG                  is the name that all servers in the cluster share. TheOF                  alias lets remote nodes (including clients) treat allF                  server members in the cluster as a single server. ForG                  example, a client user can specify the Advanced Server G                  cluster alias to connect to any server in the cluster;mH                  the user need not know the specific node in the cluster*                  to which it is connected.  E                  If DECnet has been configured to run in the cluster,SF                  the default Advanced Server cluster alias is the sameF                  as the DECnet cluster alias. If a DECnet alias is notC                  defined, the default Advanced Server cluster aliasuF                  is nodename_ALIAS, where nodename is the SCSNODE nameC                  of the cluster member from which you initially runs!                  PWRK$CONFIG.COM.a  F                 ________________________Note  ________________________  C                 Compaq strongly recommends that the Advanced ServervD                 cluster alias and the TCP/IP cluster alias (referred>                 to as the TCP/IP impersonator cluster name) be                 different.  A                 Do not use the name of the domain as the Advancede?                 Server cluster alias; if they are the same, the 4                 NetLogon service will fail to start.  E                 _____________________________________________________y  (               o  Server announce comment  H                  This is the text that the Advanced Server displays whenF                  it announces its presence on the network and when you5                  display a list of available servers.K  6         3-10 Configuring the PATHWORKS Advanced Server    C      H                                Configuring the PATHWORKS Advanced ServerH         3.2 Before You Start the Advanced Server Configuration Procedure  G                  The default server announce comment is "PATHWORKS V6.1e0                  for OpenVMS (Advanced Server)."  ?               For more information about changing configurationd>               settings, see Section 3.5, How to Change Default%               Configuration Settings.o  B               For more information about each server configuration@               setting, refer to the Compaq PATHWORKS for OpenVMS=               (Advanced Server) Server Administrator's Guide.c  D         3.2.4 What Do You Want the Administrator Account Password to               Be?   G               If you are configuring a PDC, the configuration procedureoC               prompts you to specify the password to be set for the D               domain Administrator account. If you are configuring aH               member server, the configuration procedure prompts you forF               the member server's local Administrator account password@               to be set. The member server's local AdministratorB               account password gives access to the member server'sH               local security account database. As with Windows NT, thereF               may be situtations where you would like to allow certainG               people to manage a member server's local database without B               giving them the ability to manage the entire domain.  C               Passwords are case sensitive and can contain up to 14tF               characters. Valid characters are alphanumeric characters:               and any of the following special characters:  *               ! # $ % & () - . ^ _ ` { } ~  C         3.2.5 Are You Going to Supply Account/Password Information?   D               If you are configuring your server to join an existingA               domain (as a BDC or member server), you can either:   F               o  Have the computer added to the domain manually by the%                  domain administratore  F               o  Have the computer added by supplying an administratorG                  account user name and password during execution of the (                  configuration procedure    H                           Configuring the PATHWORKS Advanced Server 3-11           1         Configuring the PATHWORKS Advanced ServerMH         3.2 Before You Start the Advanced Server Configuration Procedure  E               The former option is useful if the domain administratoruE               does not wish to give out the user name and password ofAC               the Administrator account in the domain to the personnD               configuring this server to join the domain. The domainG               administrator can use the ADMINISTER ADD COMPUTER commandnB               or the Windows NT Server Manager to add the computerC               to the domain. If this is the case, answer NO to thisvG               prompt, and you will not be prompted for account/passwordt               information.  E               With the latter option, the configuration procedure re-iH               quests the domain's PDC to add the computer to the domain.E               You will be prompted for a domain administrator accountID               user name and password, as explained in Section 3.2.6,9               What Is the Domain Administrator Password?.   8         3.2.6 What Is the Domain Administrator Password?  F               When you choose to have the computer added automaticallyD               by the configuration procedure, you are prompted for aB               domain administrator account user name and password.@               As noted in Section 3.2.5, Are You Going to SupplyA               Account/Password Information?, the PDC is requestedrB               to add the computer to the domain. The PDC validatesA               the account user name and password on behalf of the D               configuration procedure. Enter the password, observingH               the rules specified in Section 3.2.4, What Do You Want the4               Administrator Account Password to Be?.  >         3.2.7 Do You Want to Enter a New Administrator Account               Password?i  D               In certain cases, you are prompted whether you want toD               enter a new Administrator password. This gives you the1               opportunity to change the password.s  .         3.2.8 Do You Want to Start the Server?  G               The configuration procedure asks you if you want to start B               the Advanced Server. If you do not want to start theH               Advanced Server at this time, you can do so later from theG               command line after the configuration procedure completes.M      6         3-12 Configuring the PATHWORKS Advanced Server #  t      H                                Configuring the PATHWORKS Advanced ServerH         3.2 Before You Start the Advanced Server Configuration Procedure  H               Before you start the server on any OpenVMS Cluster member,F               Compaq recommends that you configure the Advanced ServerF               on each cluster member that you want to use as a server.E               You can then use the SYSMAN utility to start the serverrG               on all cluster members. If you choose to start the serverdE               individually on each cluster member, make sure that you E               do so from the SYSTEM account (or a similar account) ondH               each server node. For more information, see Section 5.3.5,F               How to Start the PATHWORKS Advanced Server in an OpenVMS               Cluster.  E               For detailed information on alternate ways to start theiF               server, see Section 5.3, Starting the PATHWORKS Advanced               Server.   D         3.3 How to Start the Advanced Server Configuration Procedure  E               After the installation procedure completes, the OpenVMS ?               system prompt ($) is displayed. If the system was C               rebooted following installation, log in to the SYSTEM A               account or an equivalent account. If the system wasaA               not rebooted, ensure that you are logged in to suchbD               an account. Then, start the configuration procedure by               entering:   '               $ @SYS$UPDATE:PWRK$CONFIGn  H               In an OpenVMS Cluster, PWRK$CONFIG.COM must be run on eachE               member node on which the server is to run. If you firstuG               start the server at any node, and then attempt to run the D               PWRK$CONFIG.COM configuration procedure, the procedure(               will shut down the server.  C         3.4 How to Respond to Advanced Server Configuration Promptsl  @               Table 3-1, PATHWORKS Advanced Server ConfigurationC               Prompts, tells you how to respond to the prompts thato'               PWRK$CONFIG.COM displays.   F                 ________________________Note  ________________________  @                 Table 3-1 shows only the prompts PWRK$CONFIG.COM<                 displays; it does not show any informational=                 messages. For a complete sample configurationn  H                           Configuring the PATHWORKS Advanced Server 3-13           1         Configuring the PATHWORKS Advanced Server C         3.4 How to Respond to Advanced Server Configuration Promptsl  >                 script, see Appendix B, Sample Complete Server/                 Installation and Configuration.   E                 _____________________________________________________e  H         Table_3-1_PATHWORKS_Advanced_Server_Configuration_Prompts_______  H         Prompt_______________Desired_Result_______________Your_Response_  C         Do you want to       Shut down the server or,     Press theaD         continue with        if your server is part of    Return key4         configuration        an OpenVMS Cluster, all3         [YES]:[1]            servers in the clusterm  <                              Abort the configuration      NO&                              procedure  C         Enter disk           Copy the PATHWORKS on-       Press the D         device name          disk structure to the        Return key8         where PATHWORKS      default OpenVMS disk device'         data files           displayed.t7         will be stored       If you ran PWRK$CONFIG.COMg4         [default_device]:    previously, the default  7                              disk device is the one you 8                              specified the last time you3                              configured the server.S  E                              Copy the PATHWORKS on-disk   device_namer4                              structure to an OpenVMS7                              disk device different fromL2                              the default displayed  H         [1]This_prompt_is_displayed_only_if_the_server_is_running.______  H                                                 (continued on next page)                  6         3-14 Configuring the PATHWORKS Advanced Server A  n      H                                Configuring the PATHWORKS Advanced ServerH              3.4 How to Respond to Advanced Server Configuration Prompts  A         Table 3-1 (Cont.) PATHWORKS Advanced Server ConfigurationhH         __________________Prompts_______________________________________  H         Prompt_______________Desired_Result_______________Your_Response_  C         Do you want to       Access the Configuration     Press theiD         change the server    Manager tool to change       Return keyF         configuration        parameters affecting the     For detailedE         parameters now?      system environment for the   information ?         [YES]:               server                       about   C                                                           using thetG                                                           ConfigurationoH                                                           Manager, referG                                                           to the CompaqeC                                                           PATHWORKSeE                                                           for OpenVMShC                                                           (Advanced H                                                           Server) ServerI                                                           Administrator'sc@                                                           Guide.  <                              Complete the configuration   NO1                              without entering thee2                              Configuration Manager  C         Enter item number,   Accept the server            Press theuD         or RETURN to         configuration parameters     Return key5         use these values     displayed (these are the 1         [DONE]:              ten or so parametersh4                              that directly affect or7                              define the server softwaree+                              configuration)e  H                                                 (continued on next page)                    H                           Configuring the PATHWORKS Advanced Server 3-15 t  o      1         Configuring the PATHWORKS Advanced ServerhC         3.4 How to Respond to Advanced Server Configuration Promptsa  A         Table 3-1 (Cont.) PATHWORKS Advanced Server ConfigurationNH         __________________Prompts_______________________________________  H         Prompt_______________Desired_Result_______________Your_Response_  D                              Change the configuration     The numberD                              settings displayed           associatedH                                                           with a settingE                                                           you want to A                                                           change.   F                                                           For detailedE                                                           informationfE                                                           on changingvG                                                           these defaultpG                                                           configurationiG                                                           settings, see F                                                           Section 3.5,G                                                           How to ChangesA                                                           DefaultsG                                                           Configuration C                                                           Settings.   C         Are you going        Have the computer            Press thevD         to supply            added automatically          Return key0         account/password     by PWRK$CONFIG.COM,7         information?         prompting you for a domainc7         [YES]:[4]            administrator account useri.                              name and password  <                              Have the computer added      NO6                              manually (for example, by6                              the domain administrator)/                              so that the domain 5                              administrator's passwordh1                              need not be divulgedr  H         [4]This_prompt_is_displayed_if_you_are_configuring_a_BDC_or_____3         member server (joining an existing domain).t  H                                                 (continued on next page)      6         3-16 Configuring the PATHWORKS Advanced Server    v      H                                Configuring the PATHWORKS Advanced ServerH              3.4 How to Respond to Advanced Server Configuration Prompts  A         Table 3-1 (Cont.) PATHWORKS Advanced Server ConfigurationdH         __________________Prompts_______________________________________  H         Prompt_______________Desired_Result_______________Your_Response_  B         Enter the name       Enter the name of the        PDC-name6         of the primary       primary domain controller6         domain controller    (PDC) for the domain your/         for domain domain-   server is joining.o         name[4]m  B         Enter Administrator  Associate a password with    passwordC         account pass-        the Administrator account    Enter theoE         word:[3]                                          password to   D                                                           be set forF                                                           the domain'sB                                                           existingG                                                           AdministratorcB                                                           account.  C         Do you want to       Keep the existing            Press thecD         enter a new          Administrator account        Return key%         Administrator        password          account password         [NO]:[2,3]  =                              Prompt you to enter a        YES 6                              new Administrator account%                              password   B         Re-enter to verify                                password         password [3,4,5]:_  H         [2]This_prompt_is_displayed_if_you_ran_PWRK$CONFIG.COM__________         previously.eD         [3]This prompt is displayed if you are configuring a primary         domain controller.C         [4]This prompt is displayed if you are configuring a BDC ore3         member server (joining an existing domain). C         [5]This prompt is displayed if you are configuring a member          server.w  H                                                 (continued on next page)  H                           Configuring the PATHWORKS Advanced Server 3-17    i      1         Configuring the PATHWORKS Advanced Server C         3.4 How to Respond to Advanced Server Configuration Prompts   A         Table 3-1 (Cont.) PATHWORKS Advanced Server ConfigurationCH         __________________Prompts_______________________________________  H         Prompt_______________Desired_Result_______________Your_Response_    B         Enter a password     Associate a password with    passwordC         for this member      the member server's local    Enter the E         server's local       Administrator account        password toiD         Administrator                                     be set forD         account:[5]                                       the member  H                                                           server's localG                                                           AdministratorAB                                                           account.  B         Enter the account                                 passwordC         password in the                                   Enter thecE         required case[4]                                  password in   D                                                           the properH                                                           case, matchingE                                                           the currentoH                                                           domain accountC                                                           password.   C         Do you want to       Start the server au-         Press the D         start PATHWORKS      tomatically after the        Return key3         V6.1 for OpenVMS on  installation procedured&         node node_name now   completes         [YES]:[6]m  <                              Not start the server         NOH         [4]This_prompt_is_displayed_if_you_are_configuring_a_BDC_or_____3         member server (joining an existing domain). C         [5]This prompt is displayed if you are configuring a member.         server. F         [6]This prompt is displayed only if the Advanced Server can beH         started without first executing AUTOGEN or rebooting the system.H         ________________________________________________________________        6         3-18 Configuring the PATHWORKS Advanced Server           H                                Configuring the PATHWORKS Advanced ServerH                         3.5 How to Change Default Configuration Settings  8         3.5 How to Change Default Configuration Settings  F               After you exit the Configuration Manager, the configura-D               tion procedure displays a list of server configurationB               settings and a prompt that lets you change them; for               example:  @           Advanced Server for OpenVMS is presently configured to           run as follows:v  :            1.  Run the License Server:                  NO:            2.  Enable Timesource service:               NO;            3.  Enable Alerter service:                  YES E            3a. Alert user names:                        Administrator ;            4.  Enable Netlogon service:                 YESr@            5.  Advanced Server domain:                  LANGROUP?            6.  Advanced Server role:                    PRIMARYu>            7.  Advanced Server computer name:           COBRAZD            7a. Advanced Server OpenVMS Cluster alias:   COBRAZ_ALIASF            8.  Server announce comment:     PATHWORKS V6.1 for OpenVMS@         Enter item number, or RETURN to use these values [DONE]:  D               o  To change a server configuration setting, enter theC                  number of the setting you want to change. A promptIE                  is then displayed that lets you change that setting.oF                  Table 3-2, Configuration Settings, describes possible)                  values for each setting.   E               o  To save the settings after you complete your changes ?                  or to accept the settings displayed, press the D                  Return key to use the default answer DONE. For moreE                  information about server configuration, refer to the F                  Compaq PATHWORKS for OpenVMS (Advanced Server) Server'                  Administrator's Guide.r  H         Table_3-2_Configuration_Settings________________________________  H         Setting_________________Possible_Values_________________________  ?         1. Run the License      YES, to run the License Server.oF         Server:                 NO, to use the default and not run the/                                 License Server.s  H                                                 (continued on next page)  H                           Configuring the PATHWORKS Advanced Server 3-19 r  o      1         Configuring the PATHWORKS Advanced Server 8         3.5 How to Change Default Configuration Settings  H         Table_3-2_(Cont.)_Configuration_Settings________________________  H         Setting_________________Possible_Values_________________________  F         2. Enable Timesource    YES, to enable the Timesource service.E         service:                NO, to use the default and not enable 7                                 the Timesource service.n  E         3. Enable Alerter       YES, to accept the default and enableu4         service:                the Alerter service.C                                 NO, to disable the Alerter service.t  D         3a. Alert user          A comma-delimited list of user namesF         names:[1]               (each containing up to 20 characters),?                                 who can receive alert messages.   E         4. Enable Netlogon      YES, to accept the default and enableS5         service:[2]             the NetLogon service.aD                                 NO, to disable the NetLogon service.  E         5. Advanced Server      A domain name of up to 15 characters. H         domain:                 Press the Return key to use the default.H                                 The default domain name is LANGROUP. YouE                                 can specify a name that reflects your 1                                 company or group.e  G         6. Advanced Server      PRIMARY, to designate the server as thep#         role:                   PDC H                                 BACKUP, to designate the server as a BDCD                                 MEMBER, to designate the server as a.                                 member server.C                                 For more information on configuringrA                                 the domain role, see Section 3.6,SF                                 Configuring the Advanced Server Domain%                                 Role.   G         7. Advanced Server      A computer name of up to 15 characters.rH         computer name:          Press the Return key to use the default.E                                 If this is the first time running thesG                                 configuration procedure, the default isf;                                 your system's SCSNODE name.n  H         [1]Displayed_only_if_Alerter_service_is_enabled.________________  @         [2]Compaq recommends that the NetLogon service always be)         enabled, even on a member server._  H                                                 (continued on next page)  6         3-20 Configuring the PATHWORKS Advanced Server y  f      H                                Configuring the PATHWORKS Advanced ServerH                         3.5 How to Change Default Configuration Settings  H         Table_3-2_(Cont.)_Configuration_Settings________________________  H         Setting_________________Possible_Values_________________________  E         7a. Advanced Server     The Advanced Server cluster alias foriH         OpenVMS Cluster         the OpenVMS Cluster to which your server(         alias:[3]               belongs.H                                 Press the Return key to use the default.C                                 If DECnet is configured to run, the D                                 default is the DECnet cluster alias.G                                 If DECnet is not configured to run, thef:                                 default is nodename_ALIAS.  D         8. Server announce      A text string of up to 48 charactersD         comment:                that the server uses to announce itsG                                 presence on the network. Do not use the 5                                 following characters:e  =                                 " / \ [ ] : ; | = , + * ? < >e  A                                 Enclose any other nonalphanumeric >                                 characters in quotation marks.H                                 Press the Return key to use the default.H         [3]Displayed_only_in_an_OpenVMS_Cluster.________________________  H         ________________________________________________________________  7         3.6 Configuring the Advanced Server Domain Role   C               Depending on the domain type, the Advanced Server can D               participate in a domain as the PDC, a BDC, or a member               server._  C               The Advanced Server may participate in three kinds of                domains:  B               o  Windows NT domains, in which Advanced Servers can@                  participate as a PDC, BDCs, and member servers.  C               o  Windows 2000 mixed-mode domains, which are domains B                  that include both Windows 2000 domain controllers@                  and Windows NT or Compaq Advanced Server domainF                  controllers; Advanced Servers can participate as BDCs'                  and as member servers.d  H                           Configuring the PATHWORKS Advanced Server 3-21    f      1         Configuring the PATHWORKS Advanced Servern7         3.6 Configuring the Advanced Server Domain Roleo  C               o  Windows 2000 native-mode domains (also referred tonD                  as pure Windows 2000 domains), which are domains inG                  which all domain controllers are Windows 2000 systems; C                  Advanced Servers can participate as member servers                   only.  B               Table 3-3, Advanced Server Roles in Different DomainG               Types, lists for each type of domain the roles the server                can take.a  H               Table_3-3_Advanced_Server_Roles_in_Different_Domain_Types_  H               Domain_Type___PDC__BDC__Member_Server_____________________  '               Windows NT    X    X    X   '               Windows 2000       X    X                mixed mode  '               Windows 2000            X H               native_mode_______________________________________________  ?               Each Windows NT domain must have one PDC. The PDC F               stores the domain's master copy of the security accounts               database.   B               When you install the Advanced Server to create a newB               Windows NT domain, the new server becomes the PDC byC               default. When you install server software and specifysG               an existing domain name, the server can join the existingo4               domain only as a BDC or member server.  A               A domain does not require BDCs, but one or more arewD               recommended. A BDC keeps a copy of the domain's masterB               security accounts database. The copy of the securityC               accounts database stored on BDCs is synchronized withdG               the PDC's master database. In this way, PDCs and BDCs canr4               validate logon requests in the domain.  C               A member server does not store a copy of the domain'srD               security accounts database and does not validate logonD               requests. Member servers rely on domain controllers toG               validate credentials of users requesting access to memberoG               server shares. The advantages of configuring the AdvancedeD               Server as a member server are listed in Section 3.6.1,A               Configuring the Advanced Server as a Member Server.   6         3-22 Configuring the PATHWORKS Advanced Server           H                                Configuring the PATHWORKS Advanced ServerH                          3.6 Configuring the Advanced Server Domain Role  G               In an OpenVMS Cluster, all nodes on the cluster must have D               the same role. If you change the role of one node, theA               other nodes are automatically changed to that role.   B               When you configure the Advanced Server for the firstG               time, you select the role your server will perform in the F               domain. At times you may need to change the role of yourH               server. The method you use to change the server depends onF               the current role of the server and the role to which youH               want to change it. To change the role of the server from aF               BDC to a PDC, or from a PDC to a BDC, use the ADMINISTERD               SET COMPUTER/ROLE command. To change a server BDC to aG               member server, you must use PWRK$CONFIG.COM, as explainedOD               in Section 3.6.1, Configuring the Advanced Server as aD               Member Server. To change a PDC to a member server, youH               must first promote another BDC to a PDC; then the originalD               PDC is demoted automatically to a BDC, after which youF               can use PWRK$CONFIG.COM to change it to a member server.E               Use PWRK$CONFIG.COM also to change a member server to anG               BDC. (This restriction is similar to but less restrictive C               than that of Windows NT, which requires the operating_D               system to be reinstalled to change a domain controllerF               to a member server, or vice versa.) For more informationE               on changing the role of the server from a BDC to a PDC, F               or vice versa, refer to the Compaq PATHWORKS for OpenVMSH               (Advanced Server) Server Administrator's Guide. Table 3-4,F               Methods for Changing Server Roles, summarizes which roleD               changes are allowed and disallowed by PWRK$CONFIG.COM.                                  H                           Configuring the PATHWORKS Advanced Server 3-23 t  t      1         Configuring the PATHWORKS Advanced Server 7         3.6 Configuring the Advanced Server Domain Role   H               Table_3-4_Methods_for_Changing_Server_Roles_______________  H               From:____To:______Method__________________________________  H               BDC      PDC      Use ADMINISTER SET COMPUTER/ROLE command<                                 to promote the BDC to a PDC.  4               BDC      Member   Use PWRK$CONFIG.COM.  B               Member   PDC      Use PWRK$CONFIG.COM to change thisA                                 server to a BDC, and then use the D                                 ADMINISTER SET COMPUTER/ROLE command<                                 to promote the BDC to a PDC.  4               Member   BDC      Use PWRK$CONFIG.COM.  C               PDC      BDC      Use ADMINISTER SET COMPUTER/ROLE tonH                                 promote a BDC in the domain to PDC; thisG                                 promotion demotes the original PDC to a $                                 BDC.  C               PDC      Member   Use ADMINISTER SET COMPUTER/ROLE torF                                 promote an existing BDC to a PDC; thisB                                 promotion demotes the PDC to a BDCE                                 so that you can change it to a memberMH               __________________server,_using_PWRK$CONFIG.COM.__________  E                 ______________________ Caution ______________________   <                 If you reconfigure a BDC as a member server,@                 PWRK$CONFIG.COM automatically removes the domain:                 controller's domain user account database.  <                 If you reconfigure a member server to a BDC,@                 PWRK$CONFIG.COM automatically removes the member5                 server's local user account database.g  >                 In either case, because of loss of local group>                 information, access to some resources might be?                 affected. If resource permissions have been set_?                 using local groups, those permissions will have B                 to be reset. If resource permissions have been setB                 using global groups or global user accounts, those@                 permissions will remain in effect after the role                 change.c  E                 _____________________________________________________   6         3-24 Configuring the PATHWORKS Advanced Server n  5      H                                Configuring the PATHWORKS Advanced ServerH                          3.6 Configuring the Advanced Server Domain Role  @         3.6.1 Configuring the Advanced Server as a Member Server  @               Use the PWRK$CONFIG.COM configuration procedure toF               configure the Advanced Server to participate in a domainC               as a member server. You cannot use the ADMINISTER SET[G               COMPUTER/ROLE command to change an Advanced Server domain F               controller to a member server role or to change a member1               server to a domain controller role.   F               You can configure the Advanced Server as a member serverC               if it is joining an existing domain that has a PDC in                operation.  H               You may want to configure your Advanced Server as a memberG               server instead of a BDC (or PDC) for any of the followingt               reasons:  B               o  Member servers do not spend time validating logonC                  requests. Thus, this role can be a good choice for B                  servers that have heavy workloads or that perform/                  extremely time-critical tasks._  H               o  More important, configuring one or more servers as mem-G                  ber servers rather than as domain controllers can help G                  decrease the network load, thereby eliminating network E                  traffic normally generated by domain controllers for H                  replicating user databases and for authenticating logonH                  requests. When a client attempts to find a logon serverB                  to authenticate a request, all domain controllersC                  respond to the request. In some environments, thiso@                  can generate a significant load on the network.  C               o  Configuring the Advanced Server as a member serverfG                  allows the Advanced Server to participate in a WindowsiE                  2000 native-mode environment without interruption to "                  that environment.  G               o  If in the future your PATHWORKS Advanced Server serverlF                  is moved to a different domain, it is simpler to moveF                  it as a member server from one domain to another than%                  to move it as a BDC.   @               The next two sections explain how to configure theB               Advanced Server as a member server: Section 3.6.1.1,E               Configuring a New PATHWORKS Advanced Server as a Member B               Server, and Section 3.6.1.2, Configuring an Existing?               PATHWORKS Advanced Server BDC As a Member Server.   H                           Configuring the PATHWORKS Advanced Server 3-25    r      1         Configuring the PATHWORKS Advanced Server 7         3.6 Configuring the Advanced Server Domain RoleE  G         3.6.1.1 Configuring a New PATHWORKS Advanced Server as a Member                  Server  D               While installing a new PATHWORKS Advanced Server in anF               existing domain, you can configure it as a member serverE               during the PWRK$CONFIG.COM configuration procedure. Theo1               domain must include one active PDC.t  B               The following PWRK$CONFIG.COM output shows how a newB               PATHWORKS Advanced Server server might be configuredB               as a member server. As shown, you must first specifyE               an existing domain (in this case, UPTIME). This exampleOE               assumes the UPTIME domain is a Windows 2000 native-moderE               domain that already has one or more domain controllers._  4         Reading current configuration parameters ...  E           Your Advanced Server for OpenVMS is presently configured to,           run as follows:o  2            1.  Run the License Server:          NO2            2.  Enable Timesource service:       NO3            3.  Enable Alerter service:          YES =            3a. Alert user names:                Administrator 3            4.  Enable Netlogon service:         YESr8            5.  Advanced Server domain:          LANGROUP7            6.  Advanced Server role:            PRIMARYt6            7.  Advanced Server computer name:   GRATDAD            7a. Advanced Server OpenVMS Cluster alias:   GRATDA_ALIASE            8.  Server announce comment:    PATHWORKS V6.1 for OpenVMStK         Enter item number, or RETURN to use these values [DONE]: 5 <Return>t  L         ************************* W A R N I N G ****************************C         You chose item number 5 from the menu.  Changing the domaindG         name will cause the existing SAM databases to be RE-INITIALIZED K         resulting in the loss of any data currently in these databases (forr2         example, user accounts, group names, etc).L         ********************************************************************  E         Do you want to continue with item number 5 (Y/[N]) Y <Return>.  K           An Advanced Server domain is a collection of computers that share2J           a common security database and policy.  Each domain has a unique1           name.  A network can have many domains.e  6         3-26 Configuring the PATHWORKS Advanced Server    a      H                                Configuring the PATHWORKS Advanced ServerH                          3.6 Configuring the Advanced Server Domain Role  D           The Advanced Server domain name can be up to 15 charactersJ           long.  The domain name must be different than the computer name.  E         Enter Advanced Server domain name for this system [LANGROUP]:          UPTIME <Return>               .            .            .  K         Enter item number, or RETURN to use these values [DONE]: 6 <Return>   J           The Advanced Server role is the part the server will play in its           domain.o  H           A primary domain controller maintains the domain's master user1           accounts database and validates logins.   L           A backup domain controller receives copies of the master database,;           validates logins, and can be promoted to primary.   H           A member server does not receive copies of the master databaseJ           or validate logins.  It relies on domain controllers to validate           user credentials.g  F         Enter the role of this server (P)rimary/(B)ackup/(M)ember [P]:         M <Return>  D           Before joining a domain, the computer must be added to the7           domain.  This can be done in one of two ways:s  G               - the administrator of the domain uses the administrative <                 tools to add this computer to the domain, or  F               - the computer is added automatically by this procedure;E                 you must supply an administrator account and password   O         Are you going to supply account/password information [Y]/N YES <Return>   J         Enter the name of the primary domain controller for domain UPTIME:         SUNDA <Return>M         Enter the name of the administrator account: [Administrator] <Return>d  J         Enter the account password in the required case:          <Return>  6         Re-enter to verify password:          <Return>  H                           Configuring the PATHWORKS Advanced Server 3-27 e  l      1         Configuring the PATHWORKS Advanced Servere7         3.6 Configuring the Advanced Server Domain Roles  <         Process NETBIOS created with identification 206010B5B         Process PWRK$NBDAEMON created with identification 206010B7C         Process PWRK$KNBDAEMON created with identification 206010B9t-         Confirming domain name with SUNDA ...:6         Successfully retrieved domain name from SUNDA.,         Validating user name and password...6         Successfully validated user name and password.  >           PATHWORKS V6.1 for OpenVM is presently configured to           run as follows:   2            1.  Run the License Server:          NO2            2.  Enable Timesource service:       NO3            3.  Enable Alerter service:          YES =            3a. Alert user names:                Administratory3            4.  Enable Netlogon service:         YES_6            5.  Advanced Server domain:          UPTIME6            6.  Advanced Server role:            MEMBER6            7.  Advanced Server computer name:   GRATDAD            7a. Advanced Server OpenVMS Cluster alias:   GRATDA_ALIASE            8.  Server announce comment:    PATHWORKS V6.1 for OpenVMS   I         Enter item number, or RETURN to use these values [DONE]: <Return>            Saving parameters ...n!         Creating SAM datafiles...SD         Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB ...  '         New sharefile has been created.e           ADMIN$ added         IPC$ added         PWUTIL added         PWLICENSE addedc         PWLIC added   ?            The Advanced Server Administrator account is used to <            administer the server.  The Administrator account>            is mapped by default to the OpenVMS SYSTEM account.  M            The Administrator account password can be up to 14 characters longrA            and the case of the characters used will be preserved.a  N         Enter a password for this Member Server's local Administrator account:                <Return>   4         Re-enter to verify password:        <Return>  6         3-28 Configuring the PATHWORKS Advanced Server    0      H                                Configuring the PATHWORKS Advanced ServerH                          3.6 Configuring the Advanced Server Domain Role  6         Changing password for Administrator account...$         Checking system resources...            .            .            .  E         3.6.1.2 Configuring an Existing PATHWORKS Advanced Server BDC "                 As a Member Server  E               When you configure a BDC to become a member server, the G               script is similar to the one for configuring a new server G               as a member server. One exception is that the script will_*               display the following lines:  @          Changing from backup domain controller to member serverI          results in the re-creation of the Advanced Server SAM databases. J          If there is any problem with the configuration, your existing SAM$          databases will be restored.  D               The BDC's domain-wide account database is removed, andD               the member server's local database is created. Server-D               specific data is retained from the BDC's database. TheC               configuration procedure saves the domain-wide accountsE               database in case you need to restore it later (for morefD               information, see Section 3.7.2, If Problems Occur When1               Reconfiguring the Advanced Server).   @               The following two displays show the role of serverF               LIONHEART before and after reconfiguration to the memberD               server role. The display symbol for a member server is               [SV].i  (         LANDOFOZ\\TINMAN> SHOW COMPUTERS  '         Computers in domain "LANDOFOZ": <         Computer       Type                      DescriptionN         -------        ------------------------  -----------------------------K         [PD] TINMAN    OpenVMS (NT 3.51) Primary PATHWORKS V6.1 for OpenVMS          (Advanced Server)r  K         [BD] LIONHEART OpenVMS (NT 3.51) Backup  PATHWORKS V6.1 for OpenVMSM         (Advanced Server)-  I         [BD] DOROTHY   OpenVMS (NT 4.0) Backup   Advanced Server V7.3 for 8                                                  OpenVMS             Total of 3 computers  H                           Configuring the PATHWORKS Advanced Server 3-29 l  d      1         Configuring the PATHWORKS Advanced Server.7         3.6 Configuring the Advanced Server Domain Rolet  !         [reconfigure server role]o	         . 	         . 	         .y(         LANDOFOZ\\TINMAN> SHOW COMPUTERS  '         Computers in domain "LANDOFOZ":l<         Computer       Type                      DescriptionN         -------        ------------------------  -----------------------------K         [PD] TINMAN    OpenVMS (NT 3.51) Primary PATHWORKS V6.1 for OpenVMS          (Advanced Server)h  K         [SV] LIONHEART OpenVMS (NT 3.51) Server  PATHWORKS V6.1 for OpenVMS          (Advanced Server)   I         [BD] DOROTHY   OpenVMS (NT 4.0) Backup   Advanced Server V7.3 foro8                                                  OpenVMS             Total of 3 computers  <         3.7 Troubleshooting Configuration Procedure Problems  .               The following sections describe:  H               o  How to ensure sufficient resources will be available to                   support clients  H               o  How to recover if problems occur when reconfiguring the                   Advanced Server  >         3.7.1 Ensuring Sufficient Resources to Support Clients  C               PATHWORKS Advanced Server requests the resources thatrD               it needs using the OpenVMS AUTOGEN utility. If AUTOGENH               underestimates the resources required for use by processesG               other than PATHWORKS Advanced Server, and these resourcesvG               have already been consumed when PATHWORKS Advanced ServeroF               is started, there may be insufficient resources left forH               PATHWORKS Advanced Server to support the desired number of               clients.  A               To ensure sufficient resource allocation to supporta@               clients, make sure that all software that will runF               concurrently with PATHWORKS Advanced Server is installedF               and started before you run the PATHWORKS Advanced ServerA               configuration procedure. If TCP/IP is selected as af  6         3-30 Configuring the PATHWORKS Advanced Server l  -      H                                Configuring the PATHWORKS Advanced ServerH                     3.7 Troubleshooting Configuration Procedure Problems  D               transport, make sure that the TCP/IP product is loaded;               before you run the PWRK$CONFIG.COM procedure.   E               After you successfully configure the PATHWORKS AdvancedW@               Server, it may not start, reporting that there areD               insufficient resources to support any clients. In thisF               case, examine the following file to determine the systemG               resource that needs to be increased (nodename is the nameO"               of the server node):  2               PWRK$LOGS:PWRK$CONFIG_ERROR_node.LOG  G               To increase the resource allocation, make the appropriate >               modifications to the MODPARAMS.DAT file and thenA               run AUTOGEN. Refer to Chapter 1, Before You InstallsC               PATHWORKS Advanced Server, for more information aboutr=               the requirements for system parameter settings.   F         3.7.2 If Problems Occur When Reconfiguring the Advanced Server  D               If you reconfigure a previously configured server, theF               PWRK$CONFIG.COM command procedure creates subdirectoriesG               in the PWRK$LMDOMAINS: and PWRK$LMDATAFILES: directories,nD               and stores the original accounts database files there.  G               The names of the subdirectories are based on the date anduE               time, such as 16JUN20014314818.DIR, indicating that the H               directory was created on 16-JUN-2000 at approximately 2:32               p.m.  F               If an error occurs during configuration, the server con-F               figuration will be returned to its original state. AfterF               you are confident you have a successful reconfiguration,D               you can manually delete these subdirectories and their               contents.o  /         3.8 The Advanced Server Network Adapter   D               PATHWORKS might need to use the network to communicateC               with the PDC. If the system has more than one network E               adapter (also referred to as a network interface card),_F               the default adapter chosen by PATHWORKS might not be theH               correct interface. Or, on some newer systems, the AdvancedA               Server might not recognize the only network adapternC               present. In such cases, you can define system logicaleC               names to direct the Advanced Server to use a specificr  H                           Configuring the PATHWORKS Advanced Server 3-31 i         1         Configuring the PATHWORKS Advanced Servert/         3.8 The Advanced Server Network Adaptero  A               interface. If no such logical is defined, PATHWORKStC               selects the first adapter (alphabetically) defined on 8               your system from a list of known adapters.  G               If the server has access to more than one network adapteraD               and you do not want to use the adapter selected, or ifC               the system has a network adapter that is not found or A               recognized by the Advanced Server, you can manuallywC               specify the network adapter to use with the transportt               you specified.  3         3.8.1 Manually Defining the Network Adapterd  E               To manually define the network adapter to be used for apE               specific protocol (after restarting the server), follow                these steps:  E               1. Use the DCL command DEFINE/SYSTEM to define a systemnD                  logical name that specifies the network adapter, asD                  shown in the following examples. Table 3-5, OpenVMSD                  Network Adapter Logicals, lists the OpenVMS logicalG                  name that you can use for each transport. You must addeG                  the appropriate logicals to SYS$MANAGER:SYLOGICALS.COMa8                  to have them available after rebooting.  $               2. Restart the server:  ,                  $ @SYS$STARTUP:PWRK$STARTUP  H               Table_3-5_OpenVMS_Network_Adapter_Logicals________________  H               Logical_Name____________________Transport_________________  4               NETBIOS$DEVICE                  DECnet  4               PWRK$KNBDAEMON_DEVICE           TCP/IP  H               PWRK$NETBEUI_DEVICE_____________NetBEUI___________________  G               The following examples show how to define the appropriatemA               network adapter for the DECnet, TCP/IP, and NetBEUIn'               transports, respectively:e  C               o  To specify adapter EWA0: for the DECnet transport,n-                  enter the following command:m  5                  $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:   6         3-32 Configuring the PATHWORKS Advanced Server e  r      H                                Configuring the PATHWORKS Advanced ServerH                                  3.8 The Advanced Server Network Adapter  C               o  To specify adapter ESA0: for the TCP/IP transport,h-                  enter the following command:g  <                  $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE ESA0:  F                 ________________________Note  ________________________  B                 If TCP/IP is running on multiple network adapters,C                 and you select one of those adapters for use by theeA                 Advanced Server, make sure the adapter you selectu>                 corresponds to the first adapter listed in the,                 TCP/IP local hosts database.  E                 _____________________________________________________t  D               o  To specify adapter ESA1: for the NetBEUI transport,-                  enter the following command:n  :                  $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE ESA1:  A               Note that you can specify the same adapter for eacha4               protocol, as in the following example:  2               $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:9               $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0:g7               $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0:n  F                 ________________________Note  ________________________  C                 The names of adapters defined by use of the logical A                 names PWRK$NETBEUI_DEVICE, PWRK$KNBDAEMON_DEVICE, D                 and NETBIOS$DEVICE must not start with an underscoreB                 (_); otherwise, the PWRK$KNBDAEMON will not start,A                 and other processes will start, but they will not !                 operate properly.e  E                 _____________________________________________________e  <         3.8.2 What to Do If the Network Adapter Is Not Found  I               The NETBIOS, PWRK$KNBDAEMON (for TCP/IP), and PWRK$NBDAEMON*C               (for NetBEUI) processes require that their associated B               network adapter is known and available to the serverD               software. It is possible that new network adapters areG               released that are not known to the current version of the G               Advanced Server software. If the Advanced Server does not*E               find or recognize the selected network adapter, each ofwF               the failing processes (NETBIOS, which is always present,  H                           Configuring the PATHWORKS Advanced Server 3-33 m  s      1         Configuring the PATHWORKS Advanced Server /         3.8 The Advanced Server Network Adapter   F               and PWRK$KNBDAEMON and PWRK$NBDAEMON, if present) writesD               an error message to its log file. Table 3-6, UndefinedE               Adapter Messages, shows each process, the log file thatoF               records the error message from the process, and examplesB               of the text of the error message. In the examples inH               Table 3-6, the server node name is MYNODE. All three errorE               messages have the same meaning: that no such device was "               found by the server.    H         Table_3-6_Undefined_Adapter_Messages____________________________  H         Process__________Log_File_Name__________________________________  <         PWRK$KNBDAEMON   PWRK$LOGS:PWRK$KNBDAEMON_MYNODE.LOG           Message:  F         Tue Mar 24 13:13:50 2000 get_phys_addr: Failed to get EthernetH         device_characteristics__________________________________________  ;         PWRK$NBDAEMON    PWRK$LOGS:PWRK$NBDAEMON_MYNODE.LOG            Message:  H         Tue_Mar_24_13:13:50_2000_Failed_to_open_datalink________________  5         NETBIOS          PWRK$LOGS:NETBIOS_MYNODE.LOG            Message:  <         %NB-W-ERRSIGNAL, exceptional conditional detected at         24-Mar-2000 13:13:50.00iH         -SYSTEM-W-NOSUCHDEV,_no_such_device_available___________________  B               If you find any of the messages listed in Table 3-6,G               define the network adapter for the appropriate processes,oE               using the procedure outlined in Section 3.8.1, ManuallyaF               Defining the Network Adapter. For example, if the serverA               reported an unknown device, enter the DEFINE/SYSTEMnA               commands to define the appropriate adapter for eache%               protocol on the server.o      6         3-34 Configuring the PATHWORKS Advanced Server h  d      H                                Configuring the PATHWORKS Advanced ServerH                                                           3.9 Next Steps           3.9 Next Steps  G               You can start the PATHWORKS Advanced Server automatically-5               as part of the configuration procedure.a  B               o  If you are upgrading from PATHWORKS (LAN Manager)@                  perform the upgrade procedures described in theF                  Compaq PATHWORKS for OpenVMS (Advanced Server) Server!                  Migration Guide.w  E               o  If you are ready to start the server, see Chapter 5,.E                  After You Install the PATHWORKS Advanced Server, fori                  instructions.                                                                H                           Configuring the PATHWORKS Advanced Server 3-35 f  o                  H                                                                        4H         ________________________________________________________________  H                   Configuring and Starting the Standalone License Server      G               The License Server is a software program that you can run:@               on an OpenVMS system to grant licenses to clients.  C               This chapter describes how to configure and start the F               standalone License Server, and consists of the following               sections:e  6               o  Section 4.1, About the License Server  ?               o  Section 4.2, Before You Begin to Configure thea*                  Standalone License Server  G               o  Section 4.3, Configuring the Standalone License ServerE  8               o  Section 4.4, Configuring the Transports  >               o  Section 4.5, How to Respond to License Server&                  Configuration Prompts  H               o  Section 4.6, How to Start the Standalone License Server  $         4.1 About the License Server  F               The PATHWORKS Advanced Server License Server can provideB               license verification for clients requiring access toD               PATHWORKS (LAN Manager) servers, PATHWORKS for OpenVMSH               (Advanced Server) servers, and Advanced Server for OpenVMS               servers.  H               The License Server is required for client-based licensing.F               If you are using server-based licensing, you do not have(               to run the License Server.  G               Each LAN needs only one License Server to support client-i@               based licenses. The same License Server can manageF               licenses for client access to any of the following types(               of file and print servers:  H               Configuring and Starting the Standalone License Server 4-1           >         Configuring and Starting the Standalone License Server$         4.1 About the License Server  7               o  PATHWORKS V5 for OpenVMS (LAN Manager)   ;               o  PATHWORKS V6 for OpenVMS (Advanced Server)i  ,               o  Advanced Server for OpenVMS  1               You can install the License Server:e  4               o  Separately from the Advanced Server  8               o  In conjunction with the Advanced Server  F               Compaq recommends that you install the License Server onF               a designated OpenVMS system without the Advanced Server.E               The PATHWORKS Advanced Server kit allows you to install H               the standalone License Server separately from the file andE               print server. You can run the standalone License ServerdD               on an OpenVMS Cluster, where cluster failover provides               reliability.  C               In an OpenVMS Cluster, the PAKs must be loaded into aeB               shared license database. For detailed information onD               managing licenses, refer to the Compaq Advanced ServerE               for OpenVMS Guide to Managing Advanced Server Licenses.s  F                 ________________________Note  ________________________  C                 The License Server included with PATHWORKS Advanced =                 Server will not issue or manage PATHWORKS for ?                 OpenVMS (NetWare) licenses. If you have clients-;                 using NetWare networking software, maintainP=                 the existing version of the License Server on ?                 a different system from the one that is runningn*                 PATHWORKS Advanced Server.  E                 _____________________________________________________   G         4.2 Before You Begin to Configure the Standalone License Serverc  E               You install the standalone License Server from the sameS@               software kit that you use to install the PATHWORKS>               Advanced Server. The procedures are described inB               Chapter 2, Installing the PATHWORKS Advanced Server.    B         4-2 Configuring and Starting the Standalone License Server n  m      H                   Configuring and Starting the Standalone License ServerH                            4.3 Configuring the Standalone License Server  5         4.3 Configuring the Standalone License ServerT  A               You must configure the standalone License Server toLD               provide licenses to clients in the LAN. Therefore, youD               select the appropriate transports used by the clients.G               You can configure the License Server to use the following                transports:o                 o  DECnet                  o  NetBEUI                 o  TCP/IP   A               Because the License Server supports all these typesH@               of transports, the startup and shutdown procedures@               have been carefully designed to prevent unexpectedC               interruptions in service. You can start and shut down H               the License Server using the file and print server commandD               procedures PWRK$STARTUP.COM and PWRK$SHUTDOWN.COM. ForG               more information on starting a standalone License Server, B               see Section 4.6, How to Start the Standalone License               Server.W  &         4.4 Configuring the Transports  G               The following section describes how to use the configura- H               tion command procedure to configure the transports for the(               standalone License Server.  E               After the installation procedure completes, the OpenVMSe?               system prompt ($) is displayed. If the system waslB               rebooted following installation, ensure that you areD               logged in to the SYSTEM account, and do the following:  ?               1. Start the configuration procedure by entering:   *                  $ @SYS$UPDATE:PWRK$CONFIG  6               2. Respond to the configuration prompts.          H               Configuring and Starting the Standalone License Server 4-3 e  e      >         Configuring and Starting the Standalone License ServerB         4.5 How to Respond to License Server Configuration Prompts  B         4.5 How to Respond to License Server Configuration Prompts  D               Table 4-1, License Server Configuration Prompts, tellsH               you how to respond to the prompts displayed by PWRK$CONFIG?               when you configure the standalone License Server.h  F                 ________________________Note  ________________________  A                 Table 4-1 shows only the prompts that PWRK$CONFIGn<                 displays; it does not show any informational=                 messages. For a complete sample configurationhA                 script, see Appendix C, Sample Standalone Licensea6                 Server Installation and Configuration.  E                 _____________________________________________________O  H         Table_4-1_License_Server_Configuration_Prompts__________________  H         Prompt_____________Desired_Outcome______________How_to_Respond__  @         Enter disk device  Copy the server on-disk      <Return>3         name where         structure to the default .         the Advanced       OpenVMS disk device4         Server data files  displayed; you need 5,0004         will be stored     free blocks of disk space5         [default_device]:  to store these data files.   2                            (If you ran PWRK$CONFIG2                            previously, the default5                            disk device is the one you 6                            specified the last time you2                            configured the server.)  C                            Copy the PATHWORKS Advanced  device_namet3                            Server on-disk structure 4                            to an OpenVMS disk device5                            different from the defaulti$                            displayed  H                                                 (continued on next page)          B         4-4 Configuring and Starting the Standalone License Server t  s      H                   Configuring and Starting the Standalone License ServerH               4.5 How to Respond to License Server Configuration Prompts  H         Table_4-1_(Cont.)_License_Server_Configuration_Prompts__________  H         Prompt_____________Desired_Outcome______________How_to_Respond__  @         Do you want to     Allow licenses to be served  <Return>&         serve client-      over DECnet         based licenses         over DECnet          [YES]:[1]   :                            Not allow licenses to be     NO-                            served over DECnetc  ;         Do you want to     Allow licenses to be served  YES '         serve client-      over NetBEUIa         based licenses         over NetBEUI         [NO]:[1]  @                            Not allow licenses to be     <Return>.                            served over NetBEUI  ;         Do you want to     Allow licenses to be served  YES &         serve client-      over TCP/IP         based licenses         over TCP/IPa         [NO]:[1]  @                            Not allow licenses to be     <Return>-                            served over TCP/IP   @         Do you want        Start the server au-         <Return>0         to start the       tomatically after the2         PATHWORKS License  configuration procedure$         Server now [YES]:  completes  :                            Complete the configuration   NO5                            procedure without startinge%                            the servereH         [1]Default_answers_may_differ_if_you_ran_the_PWRK$CONFIG________         procedure previously.iH         ________________________________________________________________    H               Configuring and Starting the Standalone License Server 4-5 f  e      >         Configuring and Starting the Standalone License Server6         4.6 How to Start the Standalone License Server  6         4.6 How to Start the Standalone License Server  F               You can start the License Server in any of the following               ways:n  D               o  During the configuration procedure, as described inH                  Section 4.3, Configuring the Standalone License Server.  0               o  Manually from the command line.  4               o  Automatically each time you reboot.  6         4.6.1 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 command:  2               $ @SYS$STARTUP:PWRK$STARTUP <Return>  B               The License Server will use DECnet, NetBEUI, TCP/IP.B               Process NETBIOS created with identification 0000011EH               Process PWRK$NBDAEMON created with identification 00000120I               Process PWRK$KNBDAEMON created with identification 00000122 I               Process PWRK$LICENSE_S created with identification 00000124                $d  ;         4.6.2 How to Start the License Server Automaticallyt  G               To make sure that the License Server starts automaticallyE5               each time you boot your OpenVMS system:o  E               1. Edit the system startup file (SYS$STARTUP:SYSTARTUP_u                  VMS.COM).  C               2. Add the startup command, as shown in the following E                  example. Add the command to the file below all lines E                  that start network transports. The following example ,                  shows how to edit the file.  @                  $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. ""-                  $ THEN @SYS$MANAGER:STARTNETU                  $ ENDIF                  .                  .                  .  ,                  $ @SYS$STARTUP:PWRK$STARTUP  B         4-6 Configuring and Starting the Standalone License Server    t      H                   Configuring and Starting the Standalone License ServerH                           4.6 How to Start the Standalone License Server  C         4.6.3 How to Start the License Server in an OpenVMS Cluster   C               If you installed and configured the License Server on B               multiple members of the same OpenVMS Cluster, CompaqC               suggests that you use the SYSMAN utility to start the G               License Server manually and simultaneously on all cluster_                members. To do so:  G               1. Make sure that you are logged in to the SYSTEM accountlC                  on one of the server nodes in the OpenVMS Cluster._  6               2. Start the SYSMAN utility by entering:  (                  $ RUN SYS$SYSTEM:SYSMAN  D               3. Define all the cluster members on which you want toE                  start the standalone License Server. For example, ifrF                  you want to start the License Server on nodes HYDRAA,$                  HYDRAB, and HYDRAC:  D                  SYSMAN> SET ENVIRONMENT/NODE=(HYDRAA,HYDRAB,HYDRAC)  F               4. Start the License Server on the nodes you defined. AtA                  the SYSMAN> prompt, enter the following command:e  5                  SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP   H               Only one License Server in the cluster will be active at aG               time. If that License Server becomes unavailable, cluster D               failover activates one of the other License Servers to               take over.                            H               Configuring and Starting the Standalone License Server 4-7 m  a                  H                                                                        5H         ________________________________________________________________  H                          After You Install the PATHWORKS Advanced Server      @               This chapter describes tasks you can perform afterD               you install the PATHWORKS Advanced Server software and1               consists of the following sections:   E               o  Section 5.1, Before You Begin Postinstallation Tasks_  A               o  Section 5.2, Verifying the PATHWORKS for OpenVMS_/                  (Advanced Server) InstallationR  D               o  Section 5.3, Starting the PATHWORKS Advanced Server  D               o  Section 5.4, Stopping the PATHWORKS Advanced Server  E               o  Section 5.5, How to Define PATHWORKS Advanced Server )                  Commands When You Log In   @               o  Section 5.6, Setting Up External Authentication  G               o  Section 5.7, Installing Optional Server AdministrationO                  Tools  3         5.1 Before You Begin Postinstallation Tasksc  G               Before proceeding, make sure you have completed the stepsuH               listed in the second column of Table 5-1, depending on theB               task you are performing, listed in the first column.                  H                      After You Install the PATHWORKS Advanced Server 5-1    .      7         After You Install the PATHWORKS Advanced Serverx3         5.1 Before You Begin Postinstallation Tasksw  L               Table_5-1_Steps_That_Must_Be_Completed_Before_Postinstallation                 Task You AreH               Performing____________Steps_Required______________________                 Installing theA               PATHWORKS Advanced    1. Completed the installationeH               Server                   procedure described in Chapter 2,  H                                        Installing the PATHWORKS Advanced.                                        Server.  B                                     2. Completed the configurationH                                        procedure described in Chapter 3,@                                        Configuring the PATHWORKS7                                        Advanced Server.                  Upgrading a A               PATHWORKS (LAN        1. Completed the installation >               Manager) server          procedures described in@               to PATHWORKS V6 for      Chapter 2, Installing theA               OpenVMS (Advanced        PATHWORKS Advanced Server.r               Server) serverF                                     2. Completed the upgrade procedureH                                        described in the Compaq PATHWORKSD                                        for OpenVMS (Advanced Server)>                                        Server Migration Guide.  B                                     3. Completed the configurationH                                        procedure described in Chapter 3,@                                        Configuring the PATHWORKS7                                        Advanced Server.g                 Installing theA               Standalone License    1. Completed the installation >               Server                   procedures described in  @                                        Chapter 2, Installing theA                                        PATHWORKS Advanced Server.n  B                                     2. Completed the configurationH                                        procedure described in Chapter 4,C                                        Configuring and Starting therA                                        Standalone License Server.O  !               Installing externalnH               authentication        Completed the installation procedureF               software only         described in Chapter 2, Installing  H               ______________________the_PATHWORKS_Advanced_Server.______;         5-2 After You Install the PATHWORKS Advanced Server  u  d      H                          After You Install the PATHWORKS Advanced ServerH   5.2 Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation  A         5.2 Verifying the PATHWORKS for OpenVMS (Advanced Server)              Installation  D               If you did not run the IVP as part of the installationB               procedure, as described in Chapter 2, Installing the?               PATHWORKS Advanced Server, you can run it now (or C               anytime later) to make sure that the server installede               successfully.   E               To run the IVP for PATHWORKS Advanced Server, enter thep                following command:  "               $ @SYS$TEST:PWRK$IVP  C               Table 5-2, IVP Indications and Steps You Should Take, H               indicates the steps to take according to the status of the,               installation indicated by IVP.  H         Table_5-2_IVP_Indications_and_Steps_You_Should_Take_____________           InstallationH         Status________IVP_Indication__________________Steps_to_Take_____  ?         Succeeded     The message %PWRK-I-NORMAL, IVP completedy"                       successfully  B                                                       If it is notF                                                       already running,G                                                       start the server,bE                                                       as described iniB                                                       Section 5.3,B                                                       Starting theH                                                       PATHWORKS Advanced=                                                       Server._  H         Failed        An error message, followed by -PWRK-E-IVPFAIL, IVP                        has failed  C                                                       Reinstall thetB                                                       software, asB                                                       described in@                                                       Chapter 2,D                                                       Installing theH                                                       PATHWORKS AdvancedH         ______________________________________________Server.___________  H                      After You Install the PATHWORKS Advanced Server 5-3           7         After You Install the PATHWORKS Advanced Server 2         5.3 Starting the PATHWORKS Advanced Server  2         5.3 Starting the PATHWORKS Advanced Server  H               The following sections describe what the startup procedureG               does, when and how to start the PATHWORKS Advanced ServergF               (manually or automatically), and and how to troubleshoot$               problems with startup.  0               You can start the Advanced Server:  D               o  During the configuration procedure, as described inE                  Chapter 3, Configuring the PATHWORKS Advanced Server   /               o  Manually from the command lineb  3               o  Automatically each time you reboote  9         5.3.1 When to Start the PATHWORKS Advanced Server   G               You must configure the server before you can start it forTH               the first time. After running the configuration procedure,<               you can start and stop the server at any time.  -         5.3.2 What the Startup Procedure Doesd  $               The startup procedure:  4               1. Checks for the required privileges.  ?               2. Verifies that required configuration files area                  available.P  H               3. Verifies that the server has been configured, and exits                  if it was not.e  >               4. If a reboot is required, verifies that it was4                  performed, and exits if it was not.  )               5. Loads transport drivers.l  !               6. Installs images.e  4               7. Starts transport support processes.  /               8. Starts each of the components:a  %                  o  License Registrare  2                  o  License Server (if configured)  )                  o  File and print server   ;         5-4 After You Install the PATHWORKS Advanced Servero e  r      H                          After You Install the PATHWORKS Advanced ServerH                               5.3 Starting the PATHWORKS Advanced Server  A         5.3.3 How to Start the PATHWORKS Advanced Server Manuallyo  G               If you did not start the PATHWORKS Advanced Server duringtB               the configuration procedure, you can start it now by               entering:S  )               $ @SYS$STARTUP:PWRK$STARTUPR  H               The PATHWORKS Advanced Server starts, and messages similar-               to the following are displayed:   <               PATHWORKS file server will use DECnet, TCP/IP.:               PATHWORKS mail notification will use DECnet.B               Process NETBIOS created with identification 0000009AI               Process PWRK$LICENSE_R created with identification 0000009D_O               The PATHWORKS V6.1 server is configured to support 20 PC clients. F               Process PWRK$MASTER created with identification 000000A2N               The master process will now start all other PATHWORKS processes.  F         5.3.4 How to Start the PATHWORKS Advanced Server Automatically  D               To make sure that the server starts automatically each0               time you boot your OpenVMS system:  M               1. Edit the system startup file, SYS$STARTUP:SYSTARTUP_VMS.COM.D  F               2. Add the @SYS$STARTUP:PWRK$STARTUP command to the fileC                  below all lines that start network transports. Forr                  example:   '                  $ START/NETWORK DECNET                   .                  .                  .  ,                  $ @SYS$STARTUP:PWRK$STARTUP  F         5.3.5 How to Start the PATHWORKS Advanced Server in an OpenVMS               ClusterP  C               Before starting the server in an OpenVMS Cluster, the F               server software must be installed and configured on eachB               cluster member on which the server is to run. If youD               installed and configured the PATHWORKS Advanced ServerE               on multiple members of the same OpenVMS Cluster, Compaq E               recommends that you use the SYSMAN utility to start the H               server manually and simultaneously on all cluster members.  H                      After You Install the PATHWORKS Advanced Server 5-5           7         After You Install the PATHWORKS Advanced Server 2         5.3 Starting the PATHWORKS Advanced Server  D               To start the server on all cluster members at the sameE               time, make sure you are logged in to the SYSTEM account.F               on one of the server nodes, then run SYSMAN as indicatedG               in the second column of Table 5-3, Starting the Server innE               an OpenVMS Cluster, according to the result you want to 5               achieve, as listed in the first column.C    H         Table_5-3_Starting_the_Server_in_an_OpenVMS_Cluster_____________  H         Desired_Result________Command_to_Enter__________________________  5         Start the SYSMAN      $ RUN SYS$SYSTEM:SYSMANv         utilitye           Define the OpenVMS7         Cluster members on    SYSMAN> SET ENVIRONMENT - >         which to start the    _SYSMAN> NODE=(SPEEDY,SPIN,SPAN)         server (in this          example, SPEEDY,         SPIN, and SPAN)c  B         Start the PATHWORKS   SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP         Advanced Server          on all the nodes         you defined in the         previous command  *         Exit the SYSMAN       SYSMAN> EXITH         utility_________________________________________________________  F                 ________________________Note  ________________________  B                 If you are using the STARTUP feature of the SYSMAND                 utility to start Advanced Server, you must pass a P1>                 parameter of " " (null or space). For example:  J                 SYSMAN> STARTUP ADD FILE PWRK$STARTUP.COM/PARAMETER=P1:" "  B                 For more information on using the SYSMAN utility's<                 STARTUP feature, refer to the OpenVMS System6                 Management Utilities Reference Manual.  E                 _____________________________________________________i  ;         5-6 After You Install the PATHWORKS Advanced ServerS d  n      H                          After You Install the PATHWORKS Advanced ServerH                               5.3 Starting the PATHWORKS Advanced Server  )         5.3.6 Troubleshooting the Startuph  >               PATHWORKS Advanced Server processes are detachedD               processes. During startup, all detached processes mustB               execute the site-specific system login procedure (by0               default, SYS$MANAGER:SYLOGIN.COM).  H               If the PATHWORKS Advanced Server startup does not completeF               successfully, check the SYLOGIN.COM procedure. Make sureD               that only commands that should be executed by detachedB               processes are executed during the PATHWORKS Advanced               Server startup.B  B               In SYLOGIN.COM, you can use the DCL lexical functionE               F$MODE or F$GETJPI to conditionalize DCL commands, suchtC               as $SET TERM/INQUIRE, that should be executed only byiB               nondetached processes, so that they are not executedD               during the PATHWORKS Advanced Server startup. Refer to>               the OpenVMS DCL Dictionary for more information.  2         5.4 Stopping the PATHWORKS Advanced Server  F               The following sections describe when and how to stop the(               PATHWORKS Advanced Server.  8         5.4.1 When to Stop the PATHWORKS Advanced Server  G               You can stop the server at any time for any reason, whiche(               can include the following:  :               o  When you want to change server parameters  6               o  As part of an orderly system shutdown  :               o  As needed to troubleshoot server problems  7         5.4.2 How to Stop the PATHWORKS Advanced Server   >               To stop the server, enter the following command:  *               $ @SYS$STARTUP:PWRK$SHUTDOWN  *               For a cluster server, enter:  2               $ @SYS$STARTUP:PWRK$SHUTDOWN CLUSTER  G               Before shutting down the OpenVMS operating system, Compaqr-               recommends stopping the server.e  H                      After You Install the PATHWORKS Advanced Server 5-7 a  p      7         After You Install the PATHWORKS Advanced Server 2         5.4 Stopping the PATHWORKS Advanced Server  A         5.4.3 How to Stop the PATHWORKS Advanced Server on Systemo               Shutdown  G               To stop the server as part of an orderly system shutdown, B               add the shutdown command to the site-specific systemE               shutdown procedure. In addition, prior to shutting down D               the server, announce the planned shutdown to connectedE               users by using the ADMINISTER SEND/USERS command, as inSH               the following example, which alerts all users connected to               server WOODMAN:a  :               LANDOFOZ\\TINMAN> SEND/USERS/SERVER=WOODMAN-;               _LANDOFOZ\\TINAMAN> "Shutdown @ 1pm today!!!"   E         5.5 How to Define PATHWORKS Advanced Server Commands When YouR             Log In  C               Compaq provides numerous command procedures that, forsD               example, provide shortcuts for invoking certain serverD               management commands and procedures. You can see a listE               of these commands by examining the contents of the filev3               SYS$MANAGER:PWRK$DEFINE_COMMANDS.COM.c  F               You can define these Advanced Server management commandsC               automatically when you log in to the account that you C               use to manage the Advanced Server. To define Advanced F               Server commands at login, edit the LOGIN.COM file of the;               privileged account to add the following line:_  1               $ @SYS$MANAGER:PWRK$DEFINE_COMMANDS   .         5.6 Setting Up External Authentication  B               The OpenVMS operating system Versions 7.1 and higherD               provide support for external authentication. PATHWORKSE               Advanced Server participates with the OpenVMS operatingoD               system to allow PATHWORKS Advanced Server domain usersC               to log in to the OpenVMS operating system using their H               PATHWORKS Advanced Server domain user names and passwords.H               The PATHWORKS Advanced Server externally authenticates the               login request.        ;         5-8 After You Install the PATHWORKS Advanced Servern A  O      H                          After You Install the PATHWORKS Advanced ServerH                                   5.6 Setting Up External Authentication  D               External authentication can provide automatic password>               synchronization between an OpenVMS account and aA               corresponding Advanced Server domain account. Users A               who have both OpenVMS and PATHWORKS Advanced ServereF               domain user accounts can avoid maintaining two differentG               passwords. If the domain account password is changed, theTH               OpenVMS LOGINOUT program sets the OpenVMS account passwordH               to the domain account password the next time the user logsH               in to the OpenVMS account. If the user changes the OpenVMSE               password with the DCL SET PASSWORD command, the the SET_H               PASSWORD command sends the password change to the AdvancedC               Server external authenticator. For synchronization to C               succeed, an Advanced Server domain controller must be A               available and the domain account password must meetK*               OpenVMS syntax requirements.  D               When you start the Advanced Server, external authenti-D               cation is automatically enabled for user accounts thatD               are flagged for external authentication in the SYSUAF.G               (To enable external authentication, PWRK$ACME_STARTUP.COM C               defines bit 0 of the SYS$SINGLE_SIGNON logical to themA               value 1. You can disable external authentication byoE               changing the default value of this bit. For information E               on disabling external authentication and about definingeB               the other bits in the SYS$SINGLE_SIGNON logical, see@               Section 5.6.5, Disabling External Authentication.)  D               For more information about enabling external authenti-E               cation on OpenVMS, refer to the OpenVMS Guide to System                Security.   A               No additional configuration is necessary on clustertH               members running the Advanced Server to enable the AdvancedB               Server to participate in the external authenticationA               process. However, to use external authentication invD               an Advanced Server cluster, all cluster members shouldC               be configured to use external authentication, so that F               externally authenticated users can log on to the clusterG               through any node in the cluster. A cluster member that isSH               not running the complete Advanced Server can be configuredB               to authenticate logon requests from network users ifD               it has access to external authentication software on aD               shared cluster system disk. If it does not have accessE               to external authentication software on a shared cluster   H                      After You Install the PATHWORKS Advanced Server 5-9 a  o      7         After You Install the PATHWORKS Advanced Server .         5.6 Setting Up External Authentication  D               system disk, you can enable external authentication onE               that system by copying only the external authenticationSB               images to the system disk, following the steps givenE               in Section 5.6.1, Setting Up External Authentication inM               OpenVMS Clusters.   G               To provide external authentication on the system, performt"               the following steps:  .               1. Install one of the following:  1                  o  The PATHWORKS Advanced Servero  D                  o  The standalone PATHWORKS external authentication                     software  F                 ________________________Note  ________________________  =                 At least one node in the cluster must run theW2                 complete Advanced Server software.  E                 _____________________________________________________o  D                  For more information, see Chapter 2, Installing the+                  PATHWORKS Advanced Server.p  C               2. Set the appropriate OpenVMS user accounts to allow_>                  external authentication (in SYSUAF). For moreB                  information, refer to the OpenVMS Guide to System                  Security.  E               3. If the PATHWORKS Advanced Server is installed, start G                  the server and external authentication will be enabled H                  for all user accounts allowing external authentication.  D                  If the standalone PATHWORKS external authentication>                  software is installed, perform the following:  E                  a. Add the following lines to your SYSTARTUP_VMS.COM                      file:   ;                     $ DEFINE/SYSTEM/EXE SYS$SINGLE_SIGNON 1 8                     $ @SYS$STARTUP:PWRK$ACME_STARTUP.COM  D                     In a cluster, add these preceding two lines plusC                     the following in a node-specific system startup G                     file (not clusterwide), or if using a shared system K                     startup file such as SYS$COMMON:[SYSMGR]SYLOGICALS.COM,eE                     ensure that you conditionalize the DEFINE command   <         5-10 After You Install the PATHWORKS Advanced Server e         H                          After You Install the PATHWORKS Advanced ServerH                                   5.6 Setting Up External Authentication  F                     based on the node name (that is, using the lexical'                     function F$GETSYI).H  N         $ DEFINE/SYSTEM/EXE PWRK$ACME_SERVER scsnode1_name[,scsnode2_name,...]  D                     Each scsnodex_name is an equivalence name, whichC                     is the SCSNODE name of a cluster member runningsB                     an Advanced Server that can be used to processE                     external authentication requests. You can include B                     all, or a subset of, the names of the AdvancedC                     Server member nodes. This allows you to specifyeG                     the order in which the requesting host contacts thedG                     hosts running the complete Advanced Server software G                     for an authentication request. If the first node in G                     the list does not respond, the requesting host asksr0                     the next host, and so forth.  D                  For more information, refer to the OpenVMS Guide to3                  System Security and Section 5.6.1.   B               4. Establish host mapping between PATHWORKS AdvancedB                  Server domain user accounts and the corresponding>                  OpenVMS user accounts, if necessary. For moreG                  information, refer to the Compaq PATHWORKS for OpenVMSs@                  (Advanced Server) Server Administrator's Guide.  G               5. If your Advanced Server is participating in an OpenVMS G                  Cluster, set up external authentication on all clustersB                  members. For more information, see Section 5.6.1,H                  Setting Up External Authentication in OpenVMS Clusters.  B               6. If you want to change the default domain used for@                  external authentication, set the system logicalA                  PWRK$ACME_DEFAULT_DOMAIN accordingly. (The local E                  server's domain is the default domain for users whenrB                  external authentication is established: if a userD                  does not specify a domain name at login, the systemF                  uses the default domain for authentication.) For moreG                  information, refer to the Compaq PATHWORKS for OpenVMSo@                  (Advanced Server) Server Administrator's Guide.  E               7. If establishing external authentication for users in G                  trusted domains, add the name of the trusted domain(s)tE                  to the LANMAN.INI parameter HostMapDomains. For morelG                  information, refer to the Compaq PATHWORKS for OpenVMSD@                  (Advanced Server) Server Administrator's Guide.  H                     After You Install the PATHWORKS Advanced Server 5-11 0  _      7         After You Install the PATHWORKS Advanced Servero.         5.6 Setting Up External Authentication  ?               For information about enabling Authentication andrF               Credential Management (SYS$ACM) for authenticating usersG               and determining the user security profile for OpenVMS and G               Windows NT, refer to the OpenVMS Connectivity Developer'seC               Guide (included in the OpenVMS Documentation CD-ROM).a  D         5.6.1 Setting Up External Authentication in OpenVMS Clusters  H               If you are running PATHWORKS Advanced Server in an OpenVMSD               Cluster, Compaq recommends that all cluster members beE               configured to be able to process OpenVMS logon requests                 for network users.  B               As noted in the preceding section, when the AdvancedD               Server is started on a system, external authenticationD               is enabled automatically for user accounts flagged forE               external authentication in the SYSUAF. A cluster memberaB               that is not running the complete Advanced Server canF               authenticate logon requests from network users if it hasD               access to external authentication software on a sharedD               cluster disk. Note that external authentication is notG               supported on OpenVMS systems prior to V7.1. Therefore, tobG               ensure that external authentication works properly on thevG               cluster, Compaq recommends that you make sure all systemsr?               in the cluster are running OpenVMS V7.1 or later.   D               If the cluster member does not have access to externalG               authentication software on a shared cluster disk, you can F               enable external authentication on that system by copyingG               just the external authentication images onto that system.   G               If the cluster member has a shared system disk, skip step E               1 below and perform the remaining steps. If the clustergD               member does not have a shared system disk, perform all               steps.  E               1. If the member node that is not running the PATHWORKS$F                  Advanced Server is running OpenVMS Alpha Version 7.2-A                  1 or later or OpenVMS VAX V7.2 or later, installsA                  the standalone PATHWORKS external authenticationiD                  software on that member node from the PATHWORKS forH                  OpenVMS (Advanced Server) software kit, as described inE                  Chapter 2, Installing the PATHWORKS Advanced Server.r    <         5-12 After You Install the PATHWORKS Advanced Server    l      H                          After You Install the PATHWORKS Advanced ServerH                                   5.6 Setting Up External Authentication  E                  If the member node that is not running the PATHWORKStD                  Advanced Server is running OpenVMS VAX Version 7.1,F                  copy the following external authentication files fromF                  any system disk where the complete PATHWORKS AdvancedE                  Server is installed to the location indicated on thee                  VAX node:  C         SYS$LIBRARY:PWRK$ACME_MODULE_VAX.EXE to SYS$COMMON:[SYSLIB]   E         SYS$STARTUP:PWRK$ACME_STARTUP.COM to SYS$COMMON:[SYS$STARTUP]   E                  If the member node that is not running the PATHWORKS F                  Advanced Server is running OpenVMS Alpha Version 7.1,F                  then copy the following external authentication filesB                  from any system disk where the complete PATHWORKSG                  Advanced Server is installed to the location indicatedn#                  on the Alpha node:t  E         SYS$LIBRARY:PWRK$ACME_MODULE_ALPHA.EXE to SYS$COMMON:[SYSLIB]   E         SYS$STARTUP:PWRK$ACME_STARTUP.COM to SYS$COMMON:[SYS$STARTUP]W  B               2. Add the following lines in a node-specific systemE                  startup file (not clusterwide), or if using a sharedl,                  system startup file such asC                  SYS$COMMON:[SYSMGR]SYLOGICALS.COM, ensure that you D                  conditionalize the DEFINE command based on the nodeE                  name (that is, using the lexical function F$GETSYI).d  /         $ DEFINE/SYSTEM/EXE SYS$SINGLE_SIGNON 1EN         $ DEFINE/SYSTEM/EXE PWRK$ACME_SERVER scsnode1_name[,scsnode2_name,...]'         $ @SYS$STARTUP:ACME_STARTUP.COM   D                  In the second line, each scsnodex_name is an equiv-D                  alence name, which is the SCSNODE name of a clusterC                  member running an Advanced Server that can be usednE                  to process external authentication requests. You candG                  include all, or a subset of, the names of the AdvancedrD                  Server member nodes. This allows you to specify theF                  order in which the requesting host contacts the hostsE                  running the complete Advanced Server software for annF                  authentication request. If the first node in the listD                  does not respond, the requesting host asks the next$                  host, and so forth.  H                     After You Install the PATHWORKS Advanced Server 5-13           7         After You Install the PATHWORKS Advanced ServerS.         5.6 Setting Up External Authentication  F                 ________________________Note  ________________________  >                 If you specify a subset of the Advanced ServerB                 member nodes, in order for external authentication?                 requests to be processed properly, the AdvancediD                 Server should be running (available) on at least oneC                 of those specified cluster members. Otherwise, even D                 if another Advanced Server member node not specifiedC                 in the list is currently running, the requests will !                 not be processed.o  E                 _____________________________________________________d  A               3. Invoke the SYS$STARTUP:PWRK$ACME_STARTUP commandE1                  procedure during system startup.n  E               4. Set appropriate OpenVMS user accounts on all clusterMA                  members to allow external authentication, and if H                  necessary, set up host mapping between the OpenVMS userD                  accounts and the Advanced Server user accounts. ForF                  more information about enabling OpenVMS user accountsH                  for external authentication, refer to the OpenVMS GuideG                  to System Security. For more information about settingiC                  up host mapping, refer to the Compaq PATHWORKS forfH                  OpenVMS (Advanced Server) Server Administrator's Guide.E                  (For OpenVMS V7.1 systems, refer to the OpenVMS V7.1 &                  New Featuers Manual.)  F         5.6.2 Requirement for External Authentication Over DECnet-Plus  @               To allow users to be externally authenticated overG               DECnet-Plus for OpenVMS, set the OpenVMS system parameteriG               NET_CALLOUTS to 255. This enables Advanced Server user ID <               mapping and authentication for network logins.  :         5.6.3 Configuring the Server Capacity for External               Authentication  B               By default, the Advanced Server can support up to 10A               simultaneous external authentication logon requestsa@               (signons). You can modify this maximum to suit theC               Advanced Server requirements, using the Configuration D               Manager. To start the Configuration Manager, enter the                following command:  (               $ ADMINISTER/CONFIGURATION  <         5-14 After You Install the PATHWORKS Advanced Server           H                          After You Install the PATHWORKS Advanced ServerH                                   5.6 Setting Up External Authentication  ?               The basic server parameters include the number of >               simultaneous activations for users with external               authentication.a  @               For more information about using the Configuration@               Manager, refer to the Compaq PATHWORKS for OpenVMS=               (Advanced Server) Server Administrator's Guide.d  C         5.6.4 Bypassing External Authentication When the Network IsM               Down  ?               External authentication cannot occur if a networknF               connection is required and the network is down. However,E               as a temporary solution, privileged users can enter thehF               /LOCAL_PASSWORD qualifier after the OpenVMS user name atH               the login prompt, to specify local authentication. Be sureF               to specify the OpenVMS user name and password when using,               the /LOCAL_PASSWORD qualifier.  E               Because using the /LOCAL_PASSWORD qualifier effectively E               overrides the security policy established by the systemeE               manager, it is allowed only when the user's account hasbG               SYSPRV as an authorized privilege. This allows the systemtF               manager to gain access to the system when the network isF               down. When Bit 1 of the equivalence string is set in theE               SYS$SINGLE_SIGNON logical name, nonprivileged users who F               are normally externally authenticated can log in locallyD               (the /LOCAL_PASSWORD qualifier need not be specified).  F               For more information about the /LOCAL_PASSWORD qualifierD               for the login command line, refer to the OpenVMS GuideC               to System Security. (For OpenVMS Version 7.1 systems,nH               refer to the OpenVMS System Management Utilities Reference>               Manual in the OpenVMS Version 7.1 documentation.  /         5.6.5 Disabling External Authentication   F               If you want to disable external authentication, then be-G               fore starting the Advanced Server, define the SYS$SINGLE_ A               SIGNON logical to a value of 0, as in the following                example:  ;               $ DEFINE/SYSTEM/EXECUTIVE SYS$SINGLE_SIGNON 0u  H               For more information about SYS$SINGLE_SIGNON and disablingF               external authentication on OpenVMS, refer to the OpenVMS'               Guide to System Security.   H                     After You Install the PATHWORKS Advanced Server 5-15    o      7         After You Install the PATHWORKS Advanced Server ;         5.7 Installing Optional Server Administration Tools   ;         5.7 Installing Optional Server Administration Toolss  E               The PATHWORKS Advanced Server provides optional client- A               based server administration tools that allow you tovD               manage the server from Windows 95, Windows 98, Windows@               for Workgroups, or Windows NT clients. These toolsA               are available in the PWUTIL share after installing, 2               configuring and starting the server.  C               The SRVTOOLS directory in the PWUTIL share contains asE               subdirectory for each type of client computer. Refer toiE               the README.TXT file in the appropriate subdirectory foreC               instructions on installing the software on the cliento               computer.   H               Refer to the Windows NT Server documentation or use onlineC               Help for more information about how to use Windows NTr*               Server administration tools.                                                      <         5-16 After You Install the PATHWORKS Advanced Server t  c                  H                                                                        6H         ________________________________________________________________  H                                         Implementing a Wide Area Network      F               This chapter describes how to set up a wide area networkG               (WAN) using one of the TCP/IP transport software productso5               supported by PATHWORKS Advanced Server.V  >               This chapter consists of the following sections:  ;               o  Section 6.1, Enabling Wide Area Networking   B               o  Section 6.2, Using the LMHOSTS File for Wide Area                  Networkingo  ?               o  Section 6.3, Using WINS in a Wide Area Networkt  >               o  Section 6.4, Using DNS in a Wide Area Network  )         6.1 Enabling Wide Area Networking   D               The PATHWORKS Advanced Server allows you to use one orF               more of the following methods for wide area network name               resolution:   (               o  LMHOSTS file for TCP/IP  5               o  Windows Internet Name Servers (WINS)n  )               o  Domain Name System (DNS)l  G               To use them, they must be enabled using the ConfigurationsF               Manager. You can enable them through the PWRK$CONFIG.COMK               command procedure, which provides access to the Configuration F               Manager when you answer YES to the question "Do you wantG               to change server configuration parameters." To enable onetE               or more of the wide area networking methods, select the D               Transports screen and select the appropriate checkbox.H               Alternatively, you can run the Configuration Manager afterC               the server is configured and started, as described insG               the Compaq PATHWORKS for OpenVMS (Advanced Server) Serveri$               Administrator's Guide.  H                                     Implementing a Wide Area Network 6-1    n      (         Implementing a Wide Area Network;         6.2 Using the LMHOSTS File for Wide Area Networkingn  ;         6.2 Using the LMHOSTS File for Wide Area Networkingh  A               The PATHWORKS Advanced Server software provides thetC               ability to set up a wide area network with the TCP/IPtA               transport through the use of the LMHOSTS file. ThisnC               file contains a list of domain controllers and membersG               servers in the same domain and also domain controllers intH               domains that have trusts established with that domain. TheG               LMHOSTS file allows the Advanced Server to participate in 5               a Windows NT wide area network as well.   F               Unlike a Windows NT Server, the Advanced Server does notF               support remote LMHOSTS files (called into the Windows NTD               LMHOSTS file using #INCLUDE). To include the same hostG               names as an existing LMHOSTS file on a Windows NT Server, H               copy the LMHOSTS file to the Advanced Server then manuallyG               insert the entries into the Advanced Server LMHOSTS file.t  E                 ______________________ Caution ______________________e  A                 If you plan to use cluster load balancing in WANsgA                 (using DNS for NetBIOS resolution of the Advanced.?                 Server cluster alias name), you must remove all >                 entries for the cluster alias from the LMHOSTSA                 file on all systems that will access the Advanced A                 Server cluster and that have enabled DNS for name @                 resolution. For more information on cluster loadD                 balancing, refer to the Compaq PATHWORKS for OpenVMS?                 (Advanced Server) Server Administrator's Guide.   E                 _____________________________________________________   3         6.2.1 Setting up a TCP/IP Wide Area Network'  F               To set up a TCP/IP wide area network, modify the LMHOSTSE               file, adding the host names and TCP/IP addresses of the D               domain controllers and member servers in the wide areaD               network that are in the same domain or in domains that8               have trust relationships with that domain.  G               The LMHOSTS file must be set up on all domain controllersOH               and member servers in the domain, unless other methods areD               used to resolve NetBIOS names. Make sure your AdvancedA               Server LMHOSTS file includes entries for all domainrE               controllers and member servers of the domain and domains  ,         6-2 Implementing a Wide Area Network r  l      H                                         Implementing a Wide Area NetworkH                      6.2 Using the LMHOSTS File for Wide Area Networking  F               controllers in domains that have trusts established with               that domain.  D               Note the following when configuring a server that willE               be a backup domain controller (BDC) or member server infF               an existing domain: if the LMHOSTS file does not includeH               entries for a primary domain controller (PDC) that is in aF               different TCP/IP subnet, your server will not be able toG               find that PDC. Make sure you include entries for that PDCdH               in the LMHOSTS file before running PWRK$CONFIG to join theB               existing domain. Two entries are required for a PDC:  D               o  One standard entry for the computer name of the PDC  E               o  One entry that uniquely identifies the system as the B                  PDC of the domain. This entry contains the domainB                  name (space padded to 15 characters) with a 16th-D                  byte control character of \0x1B. See the example in4                  Section 6.2.3, LMHOSTS File Syntax.  C               BDCs periodically retrieve changes to the domain-widegD               security accounts database from the PDC. If you omit aD               BDC from the LMHOSTS file on the PDC, the PDC will notH               notify the BDC that database changes need to be retrieved.C               Or, if a BDC omits the necessary entries for the PDC,iF               the BDC will be unable to locate the PDC when attemptingE               to retrieve database changes. In either case, the BDC's /               database will become out of date.   B               You can modify the LMHOSTS file at any time. As longD               as the LMHOSTS file exists, users can establish TCP/IP;               connections to any server listed in the file.n  #         6.2.2 The LMHOSTS Directory   G               You set up a wide area network by supplying the followingaD               file on all OpenVMS file and print servers that are in                different subnets:  *               PWRK$LMROOT:[LANMAN]LMHOSTS.  G               The LMHOSTS file has no file extension; include the finalg               dot, as shown.    H                                     Implementing a Wide Area Network 6-3           (         Implementing a Wide Area Network;         6.2 Using the LMHOSTS File for Wide Area Networking   !         6.2.3 LMHOSTS File Syntax   G               In the LMHOSTS file, create a list of nodes by specifying /               the following line for each node:A  7               address NetBIOSname #PRE #DOM:domain_namel                 Where:  H               o  address is an Internet address of form x.x.x.x, where x3                  is a decimal number from 0 to 255.i  D               o  NetBIOSname is a name from 1 to 16 characters long,D                  and may include a control character. (The format ofB                  a control character is \0Xnn or \nn, where n is a$                  hexadecimal digit.)  G                  To include a nonprinting or control character, enclose C                  the name in double quotation marks. All alphabeticnF                  characters are set to uppercase characters before theC                  name is loaded into cache (see the #PRE directive,t-                  below) or used for matching.o  G                  If you wish to include the 16th-byte control characterB1                  in the name explicitly, you mustS  H                  o  Pad the name with spaces to control the placement of*                     the control character.  H                  o  Enclose the name and control character within double                     quotes.   <                  The following are some valid NetBIOS names:                    speedyh'                  "LANDOFOZ       \0x1B"   F               o  #PRE is an optional directive that indicates that theG                  entry should be preloaded into the cache. Entries thatWD                  have the #PRE tag are preloaded into the cache whenH                  the Advanced Server first starts up. If you add a #PRE-D                  tagged entry to the LMHOSTS file after the AdvancedF                  Server starts up, the name will not be preloaded intoB                  the cache until the Advanced Server is restarted.G                  However, the name will be available at the next lookupa%                  of the LMHOSTS file.S  ,         6-4 Implementing a Wide Area Network           H                                         Implementing a Wide Area NetworkH                      6.2 Using the LMHOSTS File for Wide Area Networking  B               o  #DOM:domain-name designates the entry as a domainF                  controller in the domain specified by domain-name. ItF                  is required when the entry is a domain controller. ItF                  should not be included on entries for member servers.  E                  The #DOM:domain-name directive affects how the logonnG                  and browser services behave in routed environments. It_E                  is also used in user account management and in trust                   relationships.r  C               For example, the following entries should be includedpE               in the LMHOSTS file on a BDC that is not in the same IPaF               subnet as the PDC (if the two systems are in the same IPG               subnet, they can resolve names using broadcasts). In thiseG               example, the PDC name is DOMPDC at IP address 10.20.30.40u%               in the domain LANGROUP:e  6               10.20.30.40  DOMPDC  #PRE  #DOM:LANGROUP6               10.20.30.40 "LANGROUP       \0x1B"  #PRE  G               The \0x1B name will be registered only by the PDC for thetH               domain. If a BDC is promoted to PDC, the original PDC willF               release the \0x1B name, allowing the new PDC to registerF               it; LMHOSTS files on other systems that contain an entryC               for this \0x1B name must be updated to reflect the IPc%               address of the new PDC.m  E               If the domain PDC is a PATHWORKS or Advanced Server for F               OpenVMS server running on multiple members of an OpenVMSF               Cluster, only one cluster member will register the \0x1BF               name (the first to start the NetLogon service). However,C               if the server stops on that cluster member, the \0x1BpC               name will be released by that cluster member and willFF               then be registered by another cluster member running theF               server. In this scenario, LMHOSTS files on other systemsG               that contain an entry for this \0x1B name must be updatedsF               to reflect the IP address of the cluster member that hasE               registered, and now holds, the \0x1B name. To determinelH               the cluster member that has registered and currently holdsC               the \0x1B name, execute the NBSHOW KNB command at therE               OpenVMS DCL prompt on each node of the cluster and lookaE               for the \0x1B name in the name table that is displayed.mG               The \0x1B name will show up in the name table of only onefE               of the cluster members. The command NBSHOW is a speciale  H                                     Implementing a Wide Area Network 6-5 U  I      (         Implementing a Wide Area Network;         6.2 Using the LMHOSTS File for Wide Area Networkingt  G               Advanced Server management command that is defined in the D               command file SYS$MANAGER:PWRK$DEFINE_COMMANDS.COM; forH               more information, see Section 5.5, How to Define PATHWORKS7               Advanced Server Commands When You Log In.i  E                 ______________________ Caution ______________________   ?                 If LMHOSTS files are not updated on all systems @                 to reflect a PDC change, these systems might notB                 be able to find the PDC for the domain. This would3                 affect domain operations adversely.c  E                 _____________________________________________________d  C               In environments using trust relationships, the domainpE               controllers in trusting domains must establish a secure D               communications channel with a domain controller in theC               trusted domain. This allows a user with an account inVB               the trusted domain to access resources provided by aG               domain that trusts the user's domain (called pass-througheC               authentication). Therefore, domain controllers in theeF               trusting domain, as well as those in the trusted domain,F               should list all domain controllers from the other domainC               in their respective LMHOSTS file. (This assumes othermD               NetBIOS name resolution methods, such as WINS, are notE               being used.) Each domain controller should also includeoC               a \0x1B entry for the PDC of the other domain. In theiF               following example, the domain LANGROUP trusts the domainD               CORPDOM. The LANGROUP domain consists of the following!               domain controllers:   H               __________________________________________________________H               Name____IP_Address____Role________________________________  '               LGPPDC  192.20.30.40  PDCs  H               LGPBDC__192.20.30.41__BDC_________________________________  A               The CORPDOM domain consists of the following domainf               controllers:  H               __________________________________________________________H               Name________IP_Address____Role____________________________  +               CORPPDC     110.5.5.5     PDC   ,         6-6 Implementing a Wide Area Network G         H                                         Implementing a Wide Area NetworkH                      6.2 Using the LMHOSTS File for Wide Area Networking  H               __________________________________________________________H               Name________IP_Address____Role____________________________  +               CORPBDC1    110.5.5.20    BDC.  H               CORPBDC2____110.10.1.1____BDC_____________________________  D               To enable the domain controllers in domain LANGROUP toG               locate a domain controller in domain CORPDOM, include thenE               following entries in the LMHOSTS file located on domainm-               controllers in domain LANGROUP:   6               110.5.5.5   CORPPDC #PRE    #DOM:CORPDOM5               110.5.5.5  "CORPDOM        \0x1B"  #PREi7               110.5.5.20  CORPBDC1 #PRE    #DOM:CORPDOM 9               110.10.1.1  CORPBDC2   #PRE    #DOM:CORPDOMc  C               Similarly, to enable the domain controllers in domain.@               CORPDOM to locate the domain controllers in domainD               LANGROUP, include the following entries in the LMHOSTSG               file located on the domain controllers in domain CORPDOM:W  6               192.20.30.40 LGPPDC  #PRE  #DOM:LANGROUP7               192.20.30.40 "LANGROUP       \0x1B"  #PRE 6               192.20.30.41 LGPBDC  #PRE  #DOM:LANGROUP  ?               The #DOM directive is required in these cases. ItsE               explicitly designates the system as a domain controller F               in the specified domain. Note that if you include memberH               servers in the LMHOSTS file (whether they be Windows NT orG               Advanced Server member servers), you should omit the #DOM C               directive. Member servers are not domain controllers.k  '         6.2.4 Managing the LMHOSTS FileI  E               To change the list of available nodes, you can edit thenG               file at any time. Domain controller entries (specified byiG               the #DOM directive) and computer name entries without the F               #PRE directive are resolved by checking the LMHOSTS fileH               dynamically. This check occurs whenever a name needs to be:               resolved and is not found in the name cache.  E               To disable LMHOSTS name resolution, rename all versions E               of the LMHOSTS file to any name other than LMHOSTS. Or, F               you can use the Configuration Manager to disable LMHOSTSA               name resolution. Start the Configuration Manager ($ D               ADMIN/CONFIG), select the Transports option, and clearB               the check mark next to the Enable LMHOSTS Resolution  H                                     Implementing a Wide Area Network 6-7    m      (         Implementing a Wide Area Network;         6.2 Using the LMHOSTS File for Wide Area Networking   F               option. When you use the Configuration Manager to enableC               or disable LMHOSTS name resolution, the change is not H               dynamic; that is, the change will not go into effect until;               the next time the Advanced Server is started.k  A               When you add an entry to the LMHOSTS file while thegC               Advanced Server is running, if the entry includes therF               #PRE directive, the entry will not be cached permanentlyH               (as directed by the #PRE part of the entry) until the nextE               restart of the server; however, the change is effective F               immedately, as it will be read dynamically when the name(               next needs to be resolved.  (         6.2.5 Using the LMHOSTS Log File  D               If errors occur when the LMHOSTS file is accessed, the8               errors are recorded in the following file:  ;               PWRK$LMROOT:[LOGS]PWRK$KNBDAEMON_nodename.LOGH  H               This file is open and being written to while the PATHWORKSD               Advanced Server is running. To close the log file, you6               must stop the PATHWORKS Advanced Server.  C               To prevent the log file from becoming too large, each C               error is logged only once - the first time it occurs.rD               If an error is found in the log file, it is not logged               again.  -         6.3 Using WINS in a Wide Area Networka  G               You can configure the PATHWORKS Advanced Server as a WINScC               client. This allows the Advanced Server to use a WINSnH               Server for NetBIOS name registration, resolution, renewal,?               and release in a wide area network configuration.   B               For more information on how to use the ConfigurationC               Manager to configure the Advanced Server to use WINS,uA               refer to the Compaq PATHWORKS for OpenVMS (AdvancedN3               Server) Server Administrator's Guide.e          ,         6-8 Implementing a Wide Area Network           H                                         Implementing a Wide Area NetworkH                                    6.3 Using WINS in a Wide Area Network  :         6.3.1 Setting up WINS Support for OpenVMS Clusters  C               To allow clients that are configured for WINS supporthB               to use an Advanced Server alias name to connect to aB               clustered Advanced Server across a WAN, you must addD               to the WINS database a static multihomed entry for the)               Advanced Server alias name.t  F               When adding the static multihomed entry for the AdvancedD               Server alias name, you should enter the TCP/IP addressE               of each node in the OpenVMS Cluster that is running the                Advanced Server.  E               For more information about adding static entries to the F               WINS database, refer to your WINS product documentation.  E                 ______________________ Caution ______________________a  A                 If you plan to use DNS name resolution to providecA                 cluster load balancing in WANs, you might need toiD                 remove all static entries for the cluster alias fromA                 the WINS database. (If Windows 95, Windows 98, or B                 Windows NT clients are configured to use both WINS?                 and DNS for NetBIOS name resolution, they firsteD                 query the WINS server to resolve the name.) For moreA                 information about enabling cluster load balancingtB                 in WANs, refer to the Compaq PATHWORKS for OpenVMS?                 (Advanced Server) Server Administrator's Guide.   E                 _____________________________________________________   ,         6.4 Using DNS in a Wide Area Network  D               You can configure the Advanced Server as a DNS client.E               This allows the Advanced Server to use a DNS server forfG               NetBIOS name resolution. The Advanced Server uses DNS forGH               name resolution as a last resort if all other methods fail(               to resolve a NetBIOS name.  F                 ________________________Note  ________________________  D                 DNS name resolution is not provided as a replacementB                 for WINS and/or LMHOSTS but rather as a supplementA                 to them. With DNS, the Advanced Server still usesr  H                                     Implementing a Wide Area Network 6-9 e  n      (         Implementing a Wide Area Network,         6.4 Using DNS in a Wide Area Network  A                 WINS, LMHOSTS, or broadcast methods for resolvingD                 names.  E                 _____________________________________________________c  B               For more information on how to use the ConfigurationH               Manager to configure the Advanced Server to use DNS, referC               to the Compaq PATHWORKS for OpenVMS (Advanced Server)s+               Server Administrator's Guide.a                                                                        -         6-10 Implementing a Wide Area Networks e  H                  H                                                                        7H         ________________________________________________________________  H                              Removing PATHWORKS Advanced Server Software      @               This chapter describes how to remove the PATHWORKS8               Advanced Server software from your system.  >               This chapter consists of the following sections:  F               o  Section 7.1, PATHWORKS Advanced Server Deinstallation"                  Command Procedure  C               o  Section 7.2, Removing the PATHWORKS NetWare Server   C               You may need to remove server software for one of the                 following reasons:  +               o  If the installation failed   D                  If the IVP indicates that the software installationC                  procedure failed, you must reinstall the PATHWORKS *                  Advanced Server software.  C                  If your system has enough free disk space, you canuB                  install the server again without deinstalling theG                  PATHWORKS Advanced Server. However, if you do not haveaF                  enough disk space, you must remove PATHWORKS Advanced/                  Server before reinstalling it.g  H                  For more information about disk space requirements, seeF                  Section 1.9.9, Step 9: Check Disk Space Requirements.  %               o  If you are upgradingo  C                  If the system is running the PATHWORKS for OpenVMScC                  (NetWare) server, the NetWare server software mustaE                  be removed before you can install PATHWORKS AdvancedoH                  Server. If the NetWare server is installed when you runF                  the PATHWORKS Advanced Server installation procedure,G                  it gives you the option of removing the NetWare server B                  software (Section 2.3.2, Installing the PATHWORKSF                  Advanced Server on a System with the NetWare Server).C                  Alternatively, you can manually remove the NetWare   H                          Removing PATHWORKS Advanced Server Software 7-1           3         Removing PATHWORKS Advanced Server Software     E                  server using the procedure described in Section 7.2, 7                  Removing the PATHWORKS NetWare Server.d    F         7.1 PATHWORKS Advanced Server Deinstallation Command Procedure  F               You remove the PATHWORKS Advanced Server using a commandC               procedure that is included when you install PATHWORKS C               Advanced Server. The deinstallation command procedureu0               performs the following operations:  5               o  Shuts down the server automatically.   G               o  Prompts you to enter information necessary to complete .                  the deinstallation procedure.  F               o  Removes all PATHWORKS Advanced Server images, supportE                  files, and logical names that are created during they(                  installation procedure.  G               o  Prompts you whether to remove all Advanced Server data '                  files from the system..  F               o  Removes the PATHWORKS Advanced Server accounts if you'                  delete the data files.e  C               o  If an an older PATHWORKS server (such as PATHWORKS F                  for OpenVMS (Macintosh) or PATHWORKS V4) is detected,C                  prompts you whether you want to delete the NETBIOS D                  image SYS$COMMON:[SYSEXE]NETBIOS.EXE. Normally, youD                  should not delete the NETBIOS image. You might wantE                  to delete it if you are installing an older kit, foriD                  example. Depending on your response to this prompt,E                  the procedure saves or deletes several other related0F                  files. If you delete the NETBIOS image, the PATHWORKSF                  mail server and DOS File Maintenance utility will not                  operate.   F                  Saved files include files that might be needed later,                  such as:a  C                  -  PWRK$DELETEACE.EXE and PWRK$FIXACE.EXE, both ofnD                     which can be used to optimize disk storage - theC                     former by removing unwanted ACEs, the latter bywD                     compressing ACEs, removing unnecessary ACEs, andB                     preventing ACEs from being propagated to filesE                     created in shares. For more information, refer toi  7         7-2 Removing PATHWORKS Advanced Server SoftwareN o         H                              Removing PATHWORKS Advanced Server SoftwareH           7.1 PATHWORKS Advanced Server Deinstallation Command Procedure  F                     the Compaq PATHWORKS for OpenVMS (Advanced Server)1                     Server Administrator's Guide.   H                  -  PWRK$DEINSTAL.COM, which you might need for removingH                     data files at a later time, if you opted to save theB                     data files while removing the server software.  F               o  Removes the NETBIOS$ACCESS OpenVMS identifier, unless6                  you choose to save the NETBIOS image.  B               o  Removes PATHWORKS Advanced Server DECnet objects.  =               o  Deassigns all Advanced Server logical names.1  @         7.1.1 Using the PATHWORKS Advanced Server Deinstallation               Proceduree  H               To start the deinstallation procedure and remove PATHWORKS'               Advanced Server software:   E               1. Ensure that you are logged in to the SYSTEM account.   B               2. Ensure that no processes are running the Advanced:                  Server ADMINISTER command-line interface.  H               3. Start the deinstallation command procedure, as follows:  ,                  $ @SYS$UPDATE:PWRK$DEINSTAL  H               Table 7-1, PWRK$DEINSTAL Prompts, tells you how to respondC               to the prompts the deinstallation procedure displays._                            H                          Removing PATHWORKS Advanced Server Software 7-3           3         Removing PATHWORKS Advanced Server SoftwaresF         7.1 PATHWORKS Advanced Server Deinstallation Command Procedure  H         Table_7-1_PWRK$DEINSTAL_Prompts_________________________________  J         Prompt__________________Desired_Outcome___________________Response  E         Are you sure you        Continue                          YESo         want to deinstalln         PATHWORKS Advanced         Server[no]:c  J                                 Exit                              <Return>  J         Do you want to          Save the PATHWORKS Advanced       <Return>9         delete the PATHWORKS    Server on-disk structure,s;         Advanced Server data    including the user accountsh3         files [no]:             and share databases   E                                 Remove the PATHWORKS Advanced     YES 9                                 Server on-disk structure, ;                                 including the user accounts H         ________________________and_share_databases_____________________  G         7.1.2 Sample PATHWORKS Advanced Server Deinstallation Proceduren  B               This is a sample of the deinstallation procedure forB               PATHWORKS Advanced Server software. In this example,H               PATHWORKS is not currently running. If PATHWORKS PATHWORKSA               is running, the deinstallation procedure shuts down_5               PATHWORKS and indicates it is doing so.   O         This procedure deletes all PATHWORKS V6.1 for OpenVMS (Advanced Server)          images.3  E         Are you sure you want to deinstall PATHWORKS V6.1 for OpenVMS_-         (Advanced Server)? [no]: YES <Return>nO         Do you want to delete the Advanced Server data files [no]: YES <Return>_  7         Deleting PATHWORKS for OpenVMS common images... ;         Deleting PATHWORKS for OpenVMS NETBIOS component..._G         Deleting PATHWORKS V6.1 for OpenVMS (Advanced Server) images...m.         Deleting Advanced Server data files...<         Removing PWRK$DEFAULT and PWRK$GUEST VMS accounts...:         Removing PATHWORKS V6.1 for OpenVMS identifiers...=         Removing PATHWORKS V6.1 for OpenVMS DECnet objects..._?         Deassigning PATHWORKS V6.1 for OpenVMS logical names...AH         PATHWORKS V6.1 for OpenVMS (Advanced Server) is now deinstalled.  7         7-4 Removing PATHWORKS Advanced Server Software_ _  _      H                              Removing PATHWORKS Advanced Server SoftwareH                                7.2 Removing the PATHWORKS NetWare Server  1         7.2 Removing the PATHWORKS NetWare Servert  @               The PATHWORKS for OpenVMS (NetWare) software is noE               longer included with the PATHWORKS for OpenVMS softwareMC               kit. You must run the PATHWORKS for OpenVMS (NetWare) G               deinstallation procedure before you install PATHWORKS forO(               OpenVMS (Advanced Server).  B               To start the deinstallation procedure and remove the'               PATHWORKS NetWare server:l  A               1. Be sure you are logged in to the SYSTEM account.   H               2. Start the NetWare deinstallation procedure, as follows:  ,                  $ @SYS$UPDATE:PWVN$DEINSTAL  H               Table 7-2, PWVN$DEINSTAL Prompts, tells you how to respondH               to the prompts the NetWare server deinstallation procedure               displays.   H         Table_7-2_PWVN$DEINSTAL_Prompts_________________________________  J         Prompt__________________Desired_Outcome___________________Response  E         Are you sure you want   Continue                          YESe         to deinstall Compaq          PATHWORKS V1.0H forr         OpenVMS (NetWare)#         [no][1]:  J                                 Exit                              <Return>  J         Do you want to delete   Save the NetWare on-disk          <Return>8         the NetWare data files  structure, including the3         [no]:                   configuration Files   E                                 Remove the NetWare on-disk        YESE8                                 structure, including the3                                 configuration filesa  J         Do you want to delete   Save the NetWare SYS volume       <Return>         the NetWare SYS Volume
         [no]:n  E                                 Remove the NetWare SYS volume     YESeH         [1]To_install_PATHWORKS_Advanced_Server,_you_must_respond_to____         this question with YES.   H                          Removing PATHWORKS Advanced Server Software 7-5 G  s      3         Removing PATHWORKS Advanced Server Softwareh1         7.2 Removing the PATHWORKS NetWare Server   H         ________________________________________________________________  <         7.2.1 Sample NetWare Server Deinstallation Procedure  B               This is a sample of the deinstallation procedure for.               PATHWORKS for OpenVMS (NetWare).  ,         $ @SYS$UPDATE:PWVN$DEINSTAL <Return>J         This procedure shuts down all PATHWORKS V1.0H for OpenVMS servers,E         and deletes all PATHWORKS V1.0H for OpenVMS (NetWare) images.e  P         Are you sure you want to deinstall PATHWORKS V1.0H for OpenVMS (NetWare)         [no]: YES <Return>G         Do you want to delete the NetWare SYS Volume [no]: YES <Return>   :         Stopping PATHWORKS for OpenVMS (NetWare) Server...           Process NETBIOS stoppedy&         Process PWRK$LICENSE_R stopped%         Stopping IPX Daemon (NPSD)...f  7         Deleting PATHWORKS for OpenVMS common images...m;         Deleting PATHWORKS for OpenVMS NETBIOS component....@         Deleting PATHWORKS V1.0H for OpenVMS (NetWare) images...&         Deleting NetWare data files...&         Deleting NetWare SYS Volume...<         Removing PWRK$DEFAULT and PWRK$GUEST VMS accounts...;         Removing PATHWORKS V1.0H for OpenVMS identifiers...o>         Removing PATHWORKS V1.0H for OpenVMS DECnet objects...@         Deassigning PATHWORKS V1.0H for OpenVMS logical names...A         PATHWORKS V1.0H for OpenVMS (NetWare) is now deinstalled.t                            7         7-6 Removing PATHWORKS Advanced Server Software  h  i                  H                                                                        AH         ________________________________________________________________  H                                       Installation and Upgrade Checklist      H               Table A-1 summarizes the tasks that you need to perform toF               install and configure the PATHWORKS Advanced Server. YouG               can photocopy this table and use it as a checklist as youo=               read about and complete the tasks in this book.                                                               H                                   Installation and Upgrade Checklist A-1    v      *         Installation and Upgrade Checklist    H         Table_A-1_Installation_and_Upgrade_Checklist____________________  @         <   >1.   Prepare for the installation by completing allH                   preinstallation tasks on the checklist in Section 1.9,A                   Preinstallation Tasks, including the following:l  ,                   a. Check the part listing.  C                   b. Make sure that you have the required hardware.   C                   c. Log in to the SYSTEM account (or an equivalent                       account).  E                   d. Make sure your system has the required software.t  ,                   e. Read the release notes.  C                   f. Make sure that the system parameters GBLPAGES, B                      GBLSECTIONS, PROCSECTCNT, and SCSNODE are set                      properly.  G                   g. Make sure the ENQLM quota system process parameterd%                      is set properly.   .                   h. Back up the system disks.  A                   i. Make sure that you have enough disk space to_*                      install the software.  A                   j. Make sure that the queue manager is running.b  7                   k. Check the time zone configuration.e  G                   l. Verify that DECnet (or DECnet-Plus) and TCP/IP, ift)                      needed, are running.   D                   m. Check for existing Compaq OpenVMS server imagesG                      and files on the system. The system should be free E                      of PATHWORKS for OpenVMS (NetWare) and PATHWORKSnH                      (LAN Manager) files, and no Compaq OpenVMS file and=                      printer server images should be running.v  G                   n. Check OpenVMS Cluster configuration, if installing_+                      on an OpenVMS Cluster.   H                                                 (continued on next page)  .         A-2 Installation and Upgrade Checklist    h      H                                       Installation and Upgrade Checklist    H         Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________  A         <   >2.   Start the installation procedure and respond toeB                   installation prompts. You may choose to install:  ;                   o  The complete PATHWORKS Advanced Servers  -                   o  The Upgrade utility onlyo  ,                   o  The License Server only  H                   o  The PATHWORKS external authentication software only  E                   When installing the PATHWORKS Advanced Server in an G                   OpenVMS Cluster, perform these functions in the order                    indicated:  E                   1. Install the server everywhere appropriate in the $                      OpenVMS Cluster  C                   2. Configure the server everywhere in the clustero  E                   3. Then, start the server everywhere in the clusterc  B         <   >3.   Start the configuration procedure and respond to(                   configuration prompts.  D         <   >4.   If you are upgrading from PATHWORKS V5 for OpenVMSF                   (LAN Manager), complete the upgrade procedure. ReferG                   to the Compaq PATHWORKS for OpenVMS (Advanced Server) F                   Server Migration Guide for information about how to:  5                   a. Determine the role of the server   '                   b. Upgrade the serverO  -                   c. Upgrade OpenVMS Clusters   +                   d. Create upgrade reportsR  -                   e. Upgrade users and groupso  #                   f. Upgrade sharesr  %                   g. Upgrade security   <                   h. Upgrade server configuration parameters  H                                                 (continued on next page)  H                                   Installation and Upgrade Checklist A-3 r         *         Installation and Upgrade Checklist    H         Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________  E         <   >5.   Run the Installation Verification Procedure (if youe?                   did not do so when you installed the server).A  A         <   >6.   Start the server (if you did not do so when youhH         __________configured_the_server)._______________________________                                                                            .         A-4 Installation and Upgrade Checklist a                     H                                                                        BH         ________________________________________________________________  H                    Sample Complete Server Installation and Configuration      G               This appendix shows sample installation and configurationhH               procedures for the PATHWORKS Advanced Server on an OpenVMS               Cluster.  &         B.1 Sample Server Installation  F               The following example shows a sample installation dialog0               for the PATHWORKS Advanced Server.  G         $ @SYS$UPDATE:VMSINSTAL PWRK061 SYS$DEVICE:[KITS.PWRK] <Return> F           OpenVMS AXP Software Product Installation Procedure V7.2-1H1  #         It is 16-SEP-2001 at 15:29.R7         Enter a question mark (?) at any time for help. O         * Are you satisfied with the backup of your system disk [YES]? <Return>W  1         The following products will be processed:d           PWRK V6.1e5          Beginning installation of PWRK V6.1 at 15:29   >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...I         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to          SYS$HELP.   +          PATHWORKS for OpenVMS InstallationC  C             Compaq Computer Corporation 2000. All rights reserved.v  I            Restricted Rights: Use, duplication, or disclosure by the U.S. M            Government is subject to restrictions as set forth in subparagraphuM            (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FARw-            52.227-14 Alt. III, as applicable.   H            This software is proprietary to and embodies the confidentialI            technology of Compaq Computer Corporation. Possession, use, ornN            copying of this software and media is authorized only pursuant to aJ            valid written license from Compaq or an authorized sublicensor.  H                Sample Complete Server Installation and Configuration B-1 f  s      =         Sample Complete Server Installation and Configuration &         B.1 Sample Server Installation  =             Please select from the following install options:O  8             PATHWORKS V6.1 for OpenVMS (Advanced Server)N             PATHWORKS V6.1 for OpenVMS (Advanced Server) License Server (only)1             External Authentication images (only)i  N         * Do you want to install the complete PATHWORKS V6.1 for OpenVMS [NO]?         YES <return>  3         The following components will be installed:a  5          PATHWORKS V6.1 for OpenVMS (Advanced Server)e  D         If the selection is correct, the installation will continue.G         If the selection is not correct, you can change your selection.y?         Press CTRL/Y if you want to terminate the installation.   2         * Is the selection correct [YES]? <Return>  )                                      NOTEv)                                      ---- P          Because this kit provides a new streams execlet for NetBEUI and TCP/IP,>          you MUST reboot all nodes in the cluster that are nowM          running or have run PATHWORKS to complete installation of PATHWORKS. J          If you do not reboot the nodes at this time, you must remember to5          reboot them later before starting PATHWORKS.m  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.K  J         * Will you allow a system shutdown after this product is installed         [YES]? NO <Return>F         %PWRK-I-VERSION, Checking for OpenVMS version 6.2, or later...G         * Do you want to run the IVP after the installation is finishedg         [YES]? <Return>aB         * Do you want to purge files replaced by this installation         [YES]? <Return>n9         %PWRK-I-FREEBLKS, Checking for 160000 free blocksI  E                    User Accounts and User Identification Codes (UICs) E                    --------------------------------------------------r  N         PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account,N         PWRK$DEFAULT, and  a guest account, PWRK$GUEST.  The default UIC groupD         number for both these new accounts depends on the following:  A         B-2 Sample Complete Server Installation and Configuration            H                    Sample Complete Server Installation and ConfigurationH                                           B.1 Sample Server Installation  M         o If you are installing the server for the first time, the default iso?           the first unused UIC group number, starting with 360.R  N         o If there is an existing account PCFS$ACCOUNT, the default is the UIC4           group number associated with PCFS$ACCOUNT.  I         o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, themI           default is the UIC group number associated with PWRK$DEFAULT orgJ           PWRK$GUEST, in preference to PCFS$ACCOUNT.  However, the default           UIC group number will A           not be used to change the UIC of any existing accounts._  P             For more information about UIC group numbers, see the OpenVMS System             Manager's Manual.   H         * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST         [360]: <Return>   B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.  H         %PWRK-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and         PWRK$GUESTH         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named         PWRK$DEFAULT.n5         %UAF-I-ADDMSG, user record successfully added H         %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001]          added to rights databaseH         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named         PWRK$GUEST._5         %UAF-I-ADDMSG, user record successfully added F         %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002]          added to rights database>         %VMSINSTAL-I-RESTORE, Restoring product save set C ...>         %VMSINSTAL-I-RESTORE, Restoring product save set E ...I         %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL :         %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commandsM         %PWRK-I-SPECIFY, Specifying target directories for the provided filesS1         %PWRK-I-OBSOLETE, Deleting obsolete filess  1                                        Next StepsW1                                        ----------[  O          To continue the installation procedure, enter the following command too<          execute the server configuration command procedure:  "          $ @SYS$UPDATE:PWRK$CONFIG  H                Sample Complete Server Installation and Configuration B-3 n         =         Sample Complete Server Installation and Configurationi&         B.1 Sample Server Installation  K          For information about the configuration command procedure, see theiJ          PATHWORKS (Advanced Server) Installation and Configuration Guide.  G         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their targetH         directories...  I          Copyright Compaq Computer Corporation 2001. All rights reserved.e  5          Starting Installation Verification Procedure 9          for PATHWORKS V6.1 for OpenVMS (Advanced Server)   2         %PWRK-I-NORMAL, IVP completed successfully5          Installation of PWRK V6.1 completed at 15:36S  F             Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORYN             Creating installation data file: VMI$ROOT:[SYSUPD]PWRK061.VMI_DATA  *          VMSINSTAL procedure done at 15:36  '         B.2 Sample Server Configurationi  G               The following example shows a sample configuration dialogn0               for the PATHWORKS Advanced Server.  *         $ @SYS$UPDATE:PWRK$CONFIG <Return>L         PATHWORKS V6.1 for OpenVMS (Advanced Server) Configuration Procedure  J           PATHWORKS stores and accesses the following types of data files:  )           o Configuration parameter files$%           o License Server data filesa           o Log filesP           o Printer spool files (           o Virtual memory section files  L           You can specify any existing OpenVMS disk device that has at leastC           5000 free blocks of disk space to store these data files.t  K           Note: the server frequently accesses the data files stored on the M           disk.  If these files are stored on the system disk, it can degrademO           the performance of both the OpenVMS system and the server. Therefore, O           Compaq recommends that you specify a disk other than the system disk.   *         Press RETURN to continue: <Return>  N          If this OpenVMS Cluster has multiple system disks, make sure that all2          nodes on which you plan to run PATHWORKS:  M          o Use the same disk device to store and access PATHWORKS data files.   A         B-4 Sample Complete Server Installation and Configuration            H                    Sample Complete Server Installation and ConfigurationH                                          B.2 Sample Server Configuration  N          o Share the same SYSUAF.DAT file. In each system disk's startup file,K            define a system logical name that points all nodes to the shared (            SYSUAF.DAT file. For example:  L            $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat  C            The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COMe  H         Enter disk device name where PATHWORKS data files will be stored-         [SYS$SYSDEVICE:]: DISK$PWRK: <Return>p:         Creating PATHWORKS directory tree on DISK$PWRK:...2         Creating Advanced Server directory tree...A         Copying client files to Advanced Server directory tree...U:         Creating PATHWORKS Monitor user authorization file$         PWRK$COMMON:PWMONUAF.DAT ...                                                            H                Sample Complete Server Installation and Configuration B-5 .  f      =         Sample Complete Server Installation and Configuration '         B.2 Sample Server ConfigurationS  M         Changing the server configuration parameters will allow you to modify K         this server's client capacity and select the transports to be used.t  )         COBRAZ is currently configured toi#             + support 20 PC clientss4             + use the following transport(s): DECnet  O         If you want this server to be the primary domain controller, you should P         configure it to use all the transports used by any of the backup servers         in the domain.  L         If you want this server to be a backup domain controller, you shouldO         configure it to have at least one transport in common with the domain's J         primary domain controller, otherwise this configuration will fail.  L         If you do not change the configuration parameters now, you may do so%         later by typing ADMIN/CONFIG.e  M         Do you want to change the server configuration parameters now? [YES]:          NO <Return>   4         Reading current configuration parameters ...  O           PATHWORKS V6.0 for OpenVMS is presently configured to run as follows:i  7            1.  Run the License Server:               NOm7            2.  Enable Timesource service:            NO 8            3.  Enable Alerter service:               YESB            3a. Alert user names:                     Administrator8            4.  Enable Netlogon service:              YES=            5.  Advanced Server domain:               LANGROUP <            6.  Advanced Server role:                 PRIMARY;            7.  Advanced Server computer name:        COBRAZdA            7a. PATHWORKS OpenVMS Cluster alias:      COBRAZ_ALIASCE            8.  Server announce comment:    PATHWORKS V6.1 for OpenVMSl<                                            (Advanced Server)I         Enter item number, or RETURN to use these values [DONE]: <Return>k           Saving parameters ... 1         Checking the access control list file ... *         Successfully created new ACL storeE         Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB. ... '         New sharefile has been created.a         ADMIN$ added         IPC$ added         PWUTIL added  A         B-6 Sample Complete Server Installation and Configuration            H                    Sample Complete Server Installation and ConfigurationH                                          B.2 Sample Server Configuration  @             The Advanced Server Administrator account is used to=             administer the server.  The Administrator account ?             is mapped by default to the OpenVMS SYSTEM account.M  N             The Administrator account password can be up to 14 characters longB             and the case of the characters used will be preserved.  <         Enter Administrator account password:       <Return>  3         Re-enter to verify password:       <Return>n  6         Changing password for Administrator account...$         Checking system resources...  O         The current system configuration for COBRAZ will support 20 PC clients. .         PATHWORKS is configured to use DECnet.  M          To automatically start PATHWORKS V6.1 for OpenVMS at system startup,(O          you should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COMs          file.  $            @SYS$STARTUP:PWRK$STARTUP  N          Note: Add this line below the lines that start all network transports          (such as DECnet).  N          Before starting PATHWORKS V6.1 for OpenVMS on this system, be sure toN          execute @SYS$UPDATE:PWRK$CONFIG on each node that will run PATHWORKS.  F         Do you want to start PATHWORKS V6.1 for OpenVMS on node COBRAZ         now [yes]: NO <Return>  	         $                         H                Sample Complete Server Installation and Configuration B-7 p  p                  H                                                                        CH         ________________________________________________________________  H          Sample Standalone License Server Installation and Configuration      G               This appendix shows sample installation and configurationdF               procedures for a standalone License Server on an OpenVMS               Cluster.  9         C.1 Sample Standalone License Server Installationt  F               The following example shows a sample installation dialog0               for the standalone License Server.  G         $ @SYS$UPDATE:VMSINSTAL PWRK061 SYS$DEVICE:[KITS.PWRK] <Return>vF           OpenVMS AXP Software Product Installation Procedure V7.2-1H1#         It is 16-SEP-2001 at 16:08. 7         Enter a question mark (?) at any time for help.eO         * Are you satisfied with the backup of your system disk [YES]? <Return>t  1         The following products will be processed:t           PWRK V6.1o5          Beginning installation of PWRK V6.1 at 16:08M  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...I         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved tor         SYS$HELP.   +          PATHWORKS for OpenVMS Installation   C             Compaq Computer Corporation 2000. All rights reserved.s  I            Restricted Rights: Use, duplication, or disclosure by the U.S.UM            Government is subject to restrictions as set forth in subparagraphsM            (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR -            52.227-14 Alt. III, as applicable.a  H            This software is proprietary to and embodies the confidentialI            technology of Compaq Computer Corporation. Possession, use, or_N            copying of this software and media is authorized only pursuant to aJ            valid written license from Compaq or an authorized sublicensor.  H      Sample Standalone License Server Installation and Configuration C-1 _  o      G         Sample Standalone License Server Installation and Configuration 9         C.1 Sample Standalone License Server Installation-  <            Please select from the following install options:  7            PATHWORKS V6.1 for OpenVMS (Advanced Server) M            PATHWORKS V6.1 for OpenVMS (Advanced Server) License Server (only)_0            External Authentication images (only)  N         * Do you want to install the complete PATHWORKS V6.1 for OpenVMS [NO]?         NO <Return>gH         * Do you want to install only the PATHWORKS License Server [NO]?         YES <Return>N         * Do you want to install only the External Authentication images [NO]?         NO <Return>a  3         The following components will be installed:K  &          PATHWORKS V6.1 License Server  D         If the selection is correct, the installation will continue.G         If the selection is not correct, you can change your selection.S?         Press CTRL/Y if you want to terminate the installation.   2         * Is the selection correct [YES]? <Return>F         %PWRK-I-VERSION, Checking for OpenVMS version 6.2, or later...  $                                 NOTE$                                 ----I           Because this kit provides a new streams execlet for NetBEUI andeH           TCP/IP, you MUST reboot the system to complete installation ofL           PATHWORKS.  If you do not reboot the system at this time, you must=           remember to reboot later before starting PATHWORKS.   I           To complete the installation of this product, you should rebootyK           the system.  If it is not convenient to reboot at this time, thens-           enter NO to the following question.2  D           If you enter NO, the installation procedure will continue.J         * Will you allow a system shutdown after this product is installed         [YES]? <Return> <         * How many minutes for system shutdown [0]: <Return>F         * Do you want to do an automatic system reboot [YES]? <Return>G         * Do you want to run the IVP after the installation is finishedo         [YES]? <Return> B         * Do you want to purge files replaced by this installation         [YES]? <Return>a9         %PWRK-I-FREEBLKS, Checking for 160000 free blocks   B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.  K         C-2 Sample Standalone License Server Installation and Configuration( a  d      H          Sample Standalone License Server Installation and ConfigurationH                        C.1 Sample Standalone License Server Installation  >         %VMSINSTAL-I-RESTORE, Restoring product save set C ...>         %VMSINSTAL-I-RESTORE, Restoring product save set E ...I         %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAILi:         %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commandsM         %PWRK-I-SPECIFY, Specifying target directories for the provided filesn1         %PWRK-I-OBSOLETE, Deleting obsolete files[  G         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target          directories...  :          Copyright Compaq Computer Corporation 1993, 2001.  7            Starting Installation Verification Procedures;            for PATHWORKS V6.1 for OpenVMS (Advanced Server)T  2         %PWRK-I-NORMAL, IVP completed successfully7            Installation of PWRK V6.1 completed at 19:33r  E            Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY   M            Creating installation data file: VMI$ROOT:[SYSUPD]PWRK061.VMI_DATAe  -             VMSINSTAL procedure done at 19:34i  :         C.2 Sample Standalone License Server Configuration  E               The following example shows a sample PATHWORKS Advanced G               Server configuration procedure for the standalone License                Server.r  *         $ @SYS$UPDATE:PWRK$CONFIG <Return>L         PATHWORKS V6.1 for OpenVMS (Advanced Server) Configuration Procedure  I          PATHWORKS stores and accesses the following types of data files:p  (          o Configuration parameter files$          o License Server data files          o Log files          o Printer spool files'          o Virtual memory section filesi  K          You can specify any existing OpenVMS disk device that has at least-B          5000 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,fN          Compaq recommends that you specify a disk other than the system disk.  H      Sample Standalone License Server Installation and Configuration C-3    t      G         Sample Standalone License Server Installation and Configurationd:         C.2 Sample Standalone License Server Configuration  N          If this OpenVMS Cluster has multiple system disks, make sure that all2          nodes on which you plan to run PATHWORKS:  M          o Use the same disk device to store and access PATHWORKS data files.W  N          o Share the same SYSUAF.DAT file. In each system disk's startup file,K            define a system logical name that points all nodes to the sharedd(            SYSUAF.DAT file. For example:  L            $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat  C            The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM   H         Enter disk device name where PATHWORKS data files will be stored-         [SYS$SYSDEVICE:]: DISK$PWRK: <Return><  :         Creating PATHWORKS directory tree on DISK$PWRK:...  F          The PATHWORKS License Server can serve PATHWORKS licenses forB          Advanced Server clients over DECnet, NetBEUI, and TCP/IP.(          The Advanced Server file serverG          does not need to be running for the License Server to operate.T  K         Do you want to serve PATHWORKS licenses over DECnet [yes]: <Return>DO         Do you want to serve PATHWORKS licenses over NetBEUI [no]: YES <Return>aN         Do you want to serve PATHWORKS licenses over TCP/IP [no]: YES <Return>  P         Do you want to start the PATHWORKS License Server now [yes]: NO <Return>  	         $D                              K         C-4 Sample Standalone License Server Installation and ConfigurationR O                     H                                                                        DH         ________________________________________________________________  H                                             Upgrade Utility Installation      F               This appendix shows a sample installation of the Upgrade               utility.  *         D.1 Installing the Upgrade Utility  E               As a first step in upgrading a system that is running a-G               previously released version of PATHWORKS Advanced Server,oH               you can install the Upgrade utility without installing theE               server. Doing this allows you to run the PATHWORKS (LANpE               Manager) server while performing the upgrade procedure,aB               avoiding any interruption of services to your users.  B               If you install the Upgrade utility only, the on-diskD               structure and datafile format are not changed, and theC               PATHWORKS (LAN Manager) executables are not replaced.F  E               When you execute the installation procedure on a system D               that is running PATHWORKS (LAN Manager), the procedureE               offers you the option of installing the Upgrade utility D               only. To install the Upgrade utility only, select this               option.u  F                 ________________________Note  ________________________  >                 When you install the Upgrade utility only, youB                 cannot run the Installation Verification Procedure?                 (IVP); therefore, the prompt asking whether you ?                 want to run the IVP is not displayed during then                 installation.u  E                 _____________________________________________________         H                                         Upgrade Utility Installation D-1 r  )      $         Upgrade Utility Installation/         D.2 Sample Upgrade Utility Installationt  /         D.2 Sample Upgrade Utility Installatione  @               The following example shows a sample procedure for7               installation of the Upgrade utility only.o  G         $ @SYS$UPDATE:VMSINSTAL PWRK061 SYS$DEVICE:[KITS.PWRK] <Return>iB           OpenVMS VAX Software Product Installation Procedure V6.2#         It is 22-AUG-2001 at 15:14.o7         Enter a question mark (?) at any time for help.o?         * Are you satisfied with the backup of your system diskd         [YES]? Y <Return>   1         The following products will be processed:e           PWRK V6.1 5          Beginning installation of PWRK V6.1 at 15:14e  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...I         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved tor         SYS$HELP.   +          PATHWORKS for OpenVMS Installation   C             Compaq Computer Corporation 2000. All rights reserved.l  I            Restricted Rights: Use, duplication, or disclosure by the U.S. M            Government is subject to restrictions as set forth in subparagraphaM            (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR -            52.227-14 Alt. III, as applicable.   H            This software is proprietary to and embodies the confidentialI            technology of Compaq Computer Corporation. Possession, use, or:N            copying of this software and media is authorized only pursuant to aJ            valid written license from Compaq or an authorized sublicensor.  I             You have the option to install only the PATHWORKS for OpenVMS G             Advanced Server upgrade utility, which upgrades your serverrI             environment from V5 to V6.  If you choose to install only theeI             upgrade utility, no file server components will be installed.   M             The upgrade utility allows you to continue to run your V5 serversOO             while you perform the upgrade.  You may install the Advanced Server <             after your server environment has been upgraded.  K             However, if you choose not to install the upgrade utility only, L             the installation will proceed with the regular kit installation.O             You may invoke the upgrade utility after the installation by typingc'             @SYS$UPDATE:PWRK$V6UPGRADE.t  P           The following question allows you to install only the upgrade utility:  (         D-2 Upgrade Utility Installation    n      H                                             Upgrade Utility InstallationH                                  D.2 Sample Upgrade Utility Installation  L         * Do you want to install the upgrade utility only [NO]? YES <Return>F         %PWRK-I-VERSION, Checking for OpenVMS version 6.1, or later...B         * Do you want to purge files replaced by this installation         [YES]? <Return>e8         %PWRK-I-FREEBLKS, Checking for 30500 free blocks>         %VMSINSTAL-I-RESTORE, Restoring product save set B ...  L         %PWRK-I-SKIPSET, Skipping product save set C (Alpha Common only) ...                                                                          H                                         Upgrade Utility Installation D-3    s      $         Upgrade Utility Installation/         D.2 Sample Upgrade Utility InstallationN  1                                         Next Step 1                                         ---------   H             To upgrade the server, enter the following command to invoke'             the server upgrade utility:i  (             $ @SYS$UPDATE:PWRK$V6UPGRADE  H             For information about the upgrade utility, see the PATHWORKS5             (Advanced Server) Server Migration Guide.v  ,         $ @SYS$UPDATE:PWRK$V6UPGRAD <Return>  G         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target          directories...  5          Installation of PWRK V6.1 completed at 15:15 *          VMSINSTAL procedure done at 15:15  9             PATHWORKS Advanced Server V60 Upgrade Utility 9             ---------------------------------------------s>          This procedure is used to invoke the Upgrade utility.<          This command procedure will ask you a few questions-          before starting the Upgrade utility.c  I          If you're upgrading this server as a backup domain controller it G          needs to communicate with the primary domain controller (PDC). E          In order to communicate with the PDC a transport needs to beu          started.   @          Will this server be upgraded as a BDC or Member server?         [NO]: Y <Return>  L          The upgrade procedure uses only one of the transports configured onJ          the server. Choose a transport, and make sure that the designated=          primary domain controller is running that transport.b  L          This PATHWORKS server is configured to use DECnet, NetBEUI, TCP/IP.  K          Which transport do you want to use for upgrade? [DECnet]: <Return>   .         Process PWRK$KNBDAEMON already created      (         D-4 Upgrade Utility Installation    o                  H                                                                        EH         ________________________________________________________________  H                              Sample External Authentication Installation      G               This appendix shows a sample procedure for installing the:4               external authentication software only.  @         E.1 Sample External Authentication Software Installation  F               The following example shows a sample installation dialog<               for the external authentication software only.  G            OpenVMS AXP Software Product Installation Procedure V7.2-1H1u  "         It is 8-SEP-2001 at 19:48.  7         Enter a question mark (?) at any time for help.oO         * Are you satisfied with the backup of your system disk [YES]? <Return>   1         The following products will be processed:p           PWRK V6.1   5          Beginning installation of PWRK V6.1 at 19:48   >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...F         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved         to SYS$HELP.  /              PATHWORKS for OpenVMS Installationp  C             Compaq Computer Corporation 2000. All rights reserved.d  I            Restricted Rights: Use, duplication, or disclosure by the U.S.pM            Government is subject to restrictions as set forth in subparagraphlM            (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FARS-            52.227-14 Alt. III, as applicable.6  H            This software is proprietary to and embodies the confidentialI            technology of Compaq Computer Corporation. Possession, use, or N            copying of this software and media is authorized only pursuant to aJ            valid written license from Compaq or an authorized sublicensor.  H                          Sample External Authentication Installation E-1 l  o      3         Sample External Authentication Installatione@         E.1 Sample External Authentication Software Installation  =             Please select from the following install options:   8             PATHWORKS V6.1 for OpenVMS (Advanced Server)N             PATHWORKS V6.1 for OpenVMS (Advanced Server) License Server (only)1             External Authentication images (only)U  H         * Do you want to install the complete PATHWORKS V6.1 for OpenVMS         [NO]? <Return>B         * Do you want to install only the PATHWORKS License Server         [NO]? <Return>H         * Do you want to install only the External Authentication images         [NO]? YES   3         The following components will be installed:o  0            External Authentication images (only)  D         If the selection is correct, the installation will continue.G         If the selection is not correct, you can change your selection.o?         Press CTRL/Y if you want to terminate the installation.   2         * Is the selection correct [YES]? <Return>F         %PWRK-I-VERSION, Checking for OpenVMS version 6.2, or later...G         * Do you want to run the IVP after the installation is finished          [YES]? <Return>.B         * Do you want to purge files replaced by this installation         [YES]? <Return>e9         %PWRK-I-FREEBLKS, Checking for 160000 free blockse  B             All questions have been answered.  The installation of0             PATHWORKS for OpenVMS will continue.  >         %VMSINSTAL-I-RESTORE, Restoring product save set C ...>         %VMSINSTAL-I-RESTORE, Restoring product save set E ...I         %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL M         %PWRK-I-SPECIFY, Specifying target directories for the provided filesv1         %PWRK-I-OBSOLETE, Deleting obsolete filesa  G         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their targeta         directories...  :          Copyright Compaq Computer Corporation 1993, 2001.  8             Starting Installation Verification Procedure<             for PATHWORKS V6.1 for OpenVMS (Advanced Server)  2         %PWRK-I-NORMAL, IVP completed successfully5          Installation of PWRK V6.0 completed at 19:52t  7         E-2 Sample External Authentication Installation  /         H                              Sample External Authentication InstallationH                 E.1 Sample External Authentication Software Installation  F             Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  N             Creating installation data file: VMI$ROOT:[SYSUPD]PWRK061.VMI_DATA  *          VMSINSTAL procedure done at 19:54                                                                                H                          Sample External Authentication Installation E-3 o  a                  H                                                                        FH         ________________________________________________________________  H                    PATHWORKS Advanced Server Files and On-Disk Structure      <               This appendix includes the following sections:  H               o  Section F.1, PATHWORKS Advanced Server Files, describesC                  the files that are created during the installation                   procedure.n  ?               o  Section F.2, PATHWORKS Advanced Server On-DisklH                  Structure, shows the on-disk structure of the PATHWORKS!                  Advanced Server.   +         F.1 PATHWORKS Advanced Server Filesi  C               Table F-1, Files Installed for the PATHWORKS AdvancednF               Server, describes the files created during the installa-4               tion of the PATHWORKS Advanced Server.  H         Table_F-1_Files_Installed_for_the_PATHWORKS_Advanced_Server_____  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 bordersr  H         DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_    DECprint Supervisor printerC         BORDER.LUP                           layup for borders with 4                                              Windows  H         DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_    DECprint Supervisor printerF         NOBORDER.LUP                         layup for no borders with4                                              Windows  H                                                 (continued on next page)  H                PATHWORKS Advanced Server Files and On-Disk Structure F-1 m         =         PATHWORKS Advanced Server Files and On-Disk Structuren+         F.1 PATHWORKS Advanced Server Files   D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  G         SYS$HELP:AS$HLP.HLB[1]               System Dump Analyzer (SDA)lE                                              help library (associatedrH                                              with AS$SDA.EXE and invokedH                                              within SDA with the AS HELP5                                              command)   A         SYS$HELP:CS$HLP.HLB[1]               Help file for commontA                                              services System DumptG                                              Analyzer (SDA) (associated H                                              with CS$SDA.EXE and invokedH                                              within SDA with the CS HELP5                                              command)e  A         SYS$HELP:PCDISKHLP.HLB               DOS File MaintenanceiA                                              utility help librarym  A         SYS$HELP:PWRK$ADMIN_LIC.HLB          License Manager help 4                                              library  G         SYS$HELP:PWRK$ADMIN_CFG.HLB          Configuration Manager helps1                                              filef  E         SYS$HELP:PWRK$MANAGER.HLB            ADMINISTER commands helpe4                                              library  K         SYS$HELP:PWRK$SHOWINI.HLB[1]         Help file for PWRK$SHOWINI.EXE   F         SYS$HELP:PWRK$V6UPGRADE.HLB          Upgrade utility help file  F         SYS$HELP:PWRK061.RELEASE_NOTES       PATHWORKS Advanced Server:                                              release notes  F         SYS$HELP:SDA.HLP                     System Dump Analyzer help4                                              library  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.   H                                                 (continued on next page)  A         F-2 PATHWORKS Advanced Server Files and On-Disk Structuren           H                    PATHWORKS Advanced Server Files and On-Disk StructureH                                      F.1 PATHWORKS Advanced Server Files  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  A         SYS$HELP:STREAMS$HLP.HLB[1]          Help file for System D                                              Dump Analyzer (SDA) forE                                              streams (protocol layer)rF                                              analysis (associated withH                                              STREAMS$SDA.EXE and invokedH                                              within SDA with the STREAMS:                                              HELP command)  G         SYS$LIBRARY:AS$SDA.EXE[1]            System Dump Analyzer (SDA) D                                              extension for analyzingG                                              Advanced Server system andh2                                              dumps  G         SYS$LIBRARY:CS$SDA.EXE[1]            System Dump Analyzer (SDA)yD                                              extension for analyzingB                                              common services dumps  ?         SYS$LIBRARY:NETBIOSSHR.EXE           NetBIOS for DECnet <                                              shareable image  A         SYS$LIBRARY:PCDISKSHR.EXE            DOS File Maintenance D                                              utility shareable image  H         SYS$LIBRARY:PCSA_MAILSHR.EXE         Mail notification shareable2                                              image  A         SYS$STARTUP:PCSA$MAIL_STARTUP.COM    PCSAMAIL command foraD                                              TCP/IP clients invokingF                                              the PATHWORKS mail server  D         SYS$LIBRARY:PWRK$ACME_MODULE_        External authentication8         ALPHA.EXE                            Alpha image  H         SYS$LIBRARY:PWRK$ACME_MODULE_        External authentication VAX2         VAX.EXE                              image  B         SYS$LIBRARY:PWRK$CMT_LM.EXE          User interface to theC                                              Configurator, Monitor,a>                                              and Tuner utility  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.   H                                                 (continued on next page)  H                PATHWORKS Advanced Server Files and On-Disk Structure F-3 2         =         PATHWORKS Advanced Server Files and On-Disk Structure +         F.1 PATHWORKS Advanced Server Filesf  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  C         SYS$LIBRARY:PWRK$CMTLIBSHR.EXE       Configurator, Monitor,eF                                              and Tuner (CMT) shareable4                                              library  G         SYS$LIBRARY:PWRK$CMTSHR.EXE          Configurator, Monitor, andsH                                              Tuner (CMT) shareable image  F         SYS$LIBRARY:PWRK$CSSHR_V7.EXE        Common services shareable2                                              image  F         SYS$LIBRARY:PWRK$CSSHR_V6.EXE        Common services shareable2                                              image  C         SYS$LIBRARY:PWRK$DEVCTL_GENERIC.TLB  Generic device control,4                                              library  H         SYS$LIBRARY:PWRK$DEVCTL_LA51.TLB     LA51 device control library  H         SYS$LIBRARY:PWRK$DEVCTL_LA70.TLB     LA70 device control library  A         SYS$LIBRARY:PWRK$DEVCTL_LA75P.TLB    LA75P device control 4                                              library  H         SYS$LIBRARY:PWRK$DEVCTL_LG01.TLB     LG01 device control library  H         SYS$LIBRARY:PWRK$DEVCTL_LG02.TLB     LG02 device control library  H         SYS$LIBRARY:PWRK$DEVCTL_LG06.TLB     LG06 device control library  H         SYS$LIBRARY:PWRK$DEVCTL_LG31.TLB     LG31 device control library  A         SYS$LIBRARY:PWRK$DEVCTL_LN03R.TLB    LN03R device control 4                                              library  A         SYS$LIBRARY:PWRK$DEVCTL_DL1100.TLB   DEClaser 1100 devicel<                                              control library  A         SYS$LIBRARY:PWRK$DEVCTL_DL2100.TLB   DEClaser 2100 deviceK<                                              control library  B         SYS$LIBRARY:PWRK$DEVCTL_DL2100P.TLB  DEClaser 2100P device<                                              control library  A         SYS$LIBRARY:PWRK$DEVCTL_DL2200.TLB   DEClaser 2200 deviceD<                                              control library  B         SYS$LIBRARY:PWRK$DEVCTL_DL2200P.TLB  DEClaser 2200P device<                                              control library  H                                                 (continued on next page)  A         F-4 PATHWORKS Advanced Server Files and On-Disk Structurec           H                    PATHWORKS Advanced Server Files and On-Disk StructureH                                      F.1 PATHWORKS Advanced Server Files  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  A         SYS$LIBRARY:PWRK$DEVCTL_DL3200.TLB   DEClaser 3200 device <                                              control library  B         SYS$LIBRARY:PWRK$DEVCTL_FX1050.TLB   FX1050 device control4                                              library  A         SYS$LIBRARY:PWRK$DEVCTL_FX850.TLB    FX850 device controlr4                                              library  G         SYS$LIBRARY:PWRK$DEVCTL_HP_          HP LaserJet device controlt4         LASERJET.TLB                         library  A         SYS$LIBRARY:PWRK$DEVCTL_LA210.TLB    LA210 device controll4                                              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 controle4                                              library  H         SYS$LIBRARY:PWRK$DEVCTL_LN03.TLB     LN03 device control library  E         SYS$LIBRARY:PWRK$DEVCTL_LN03P.TLB    LN03 PLUS device control 4                                              library  F         SYS$LIBRARY:PWRK$DEVCTL_PROPRINTER.TLProprinter device control4                                              library  H         SYS$LIBRARY:PWRK$DEVCTL_SILENTWRITER.SilentWriter device control4                                              library  D         SYS$LIBRARY:PWRK$FSLIB_ODS2.EXE      ODS2/ODS5 addon library  F         SYS$LIBRARY:PWRK$LICENSE_LIBSHR.EXE  License shareable library  ?         SYS$LIBRARY:PWRK$LICENSE_            License managementN<         MGMTSHR.EXE                          shareable image  F         SYS$LIBRARY:PWRK$LMAPISHR.EXE        PATHWORKS Advanced Server<                                              shareable image  F         SYS$LIBRARY:PWRK$LMRPCAPISHR.EXE     PATHWORKS Advanced Server<                                              shareable image  H                                                 (continued on next page)  H                PATHWORKS Advanced Server Files and On-Disk Structure F-5 a  n      =         PATHWORKS Advanced Server Files and On-Disk Structure +         F.1 PATHWORKS Advanced Server Files   D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  F         SYS$LIBRARY:PWRK$LMRPCSHR.EXE        PATHWORKS Advanced Server<                                              shareable image  F         SYS$LIBRARY:PWRK$LMRPCXNPSHR.EXE     PATHWORKS Advanced Server<                                              shareable image  F         SYS$LIBRARY:PWRK$LMTASKSHR.EXE       PATHWORKS Advanced Server<                                              shareable image  F         SYS$LIBRARY:PWRK$MGTLIBSHR.EXE       PATHWORKS Advanced Server<                                              shareable image  F         SYS$LIBRARY:PWRK$NBLIB_DECNET.EXE    PATHWORKS Advanced ServerH                                              network interface to DECnet  F         SYS$LIBRARY:PWRK$NBLIB_NETBEUI.EXE   PATHWORKS Advanced ServerA                                              network interface tob4                                              NetBEUI  F         SYS$LIBRARY:PWRK$NBLIB_TCPIP.EXE     PATHWORKS Advanced ServerH                                              network interface to TCP/IP  D         SYS$LIBRARY:PWRK$PCMSHR.EXE          Cache manager shareable2                                              image  E         SYS$LIBRARY:PWRK$PRINTER_            Printer information file          INFORMATION.DATa  E         SYS$LIBRARY:PWRK$SDA.EXE[1]          Extension for the SystemtD                                              Dump Analyzer (SDA) forB                                              analyzing systems and@                                              dumps, for backwardD                                              compatibility (replacedG                                              by AS$SDA.EXE, CS$SDA.EXE,oA                                              and STREAMS$SDA.EXE)   C         SYS$LIBRARY:PWRK$SDA_V1.EXE[1]       Original extension forsA                                              System Dump Analyzers  D         SYS$LIBRARY:PWRK$STREAMSSHR_V7.EXE   Streams shareable image  D         SYS$LIBRARY:PWRK$STREAMSSHR_V6.EXE   Streams shareable image  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.t  H                                                 (continued on next page)  A         F-6 PATHWORKS Advanced Server Files and On-Disk Structure.           H                    PATHWORKS Advanced Server Files and On-Disk StructureH                                      F.1 PATHWORKS Advanced Server Files  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  F         SYS$LIBRARY:PWRK$WINLIBSHR.EXE       PATHWORKS Advanced Server@                                              character-cell userF                                              interface shareable image  G         SYS$LIBRARY:PWRK$XTILIBSHR.EXE       X/Open Transport InterfaceP>                                              shareable library  G         SYS$LIBRARY:PWRK$XTINETBIOSSHR.EXE   X/Open Transport Interface.H                                              shareable image for NetBIOS  G         SYS$LIBRARY:PWRK$XTINSPNBSHR.EXE     X/Open Transport Interface G                                              shareable image for DECnete  A         SYS$LIBRARY:SDA.EXE                  System Dump Analyzert  @         SYS$LIBRARY:STREAMS$SDA.EXE[1]       Streams System Dump?                                              Analyzer image foroH                                              analyzing streams (protocolC                                              layer) loadable imagesD  G         SYS$LOADABLE_IMAGES:PCFSDRIVERDEF.STBData structure definitions:;                                              for PCFSDRIVER   D         SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Streams system-loadable2         V6.EXE                               image  D         SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Streams system-loadable2         V7.EXE                               image  =         SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Symbol table for_B         V6.STB                               PWRK$STREAMSOS_V6.EXE  =         SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_  Symbol table for B         V7.STB                               PWRK$STREAMSOS_V7.EXE  B         SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  DECnet I/O and double;         V7.EXE                               mapping drivero  =         SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  Symbol table foreB         V6.STB                               SYS$PCFSDRIVER_V6.EXE  =         SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_  Symbol table for.B         V7.STB                               SYS$PCFSDRIVER_V7.EXE  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.l  H                                                 (continued on next page)  H                PATHWORKS Advanced Server Files and On-Disk Structure F-7 _  _      =         PATHWORKS Advanced Server Files and On-Disk StructureP+         F.1 PATHWORKS Advanced Server Filesr  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  E         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Cluster Interconnect I/O 3         V6.EXE                               driverb  E         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Cluster Interconnect I/O 3         V7.EXE                               drivere  =         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Symbol table forpA         V6.STB                               SYS$PCIDRIVER_V6.EXEW  =         SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_   Symbol table foruA         V7.STB                               SYS$PCIDRIVER_V7.EXEa  C         SYS$MANAGER:PWRK$DEFINE_COMMANDS.COM[Command procedure thate@                                              defines symbols forH                                              commands that run PATHWORKSF                                              Advanced Server utilities  C         SYS$MANAGER:PWRK$DEFINE_ROOT.COM     Directory tree logical_H                                              command file created during9                                              PWRK$CONFIG.   C         SYS$MANAGER:PWRK$SHOWSYS.COM         Command procedure that E                                              shows status of file and C                                              print server processes   D         SYS$MESSAGE:PWRK$MSG.EXE             Advanced Server message1                                              file   A         SYS$STARTUP:PCSA$MAIL_STARTUP.COM    PCSAMAIL command for D                                              TCP/IP clients invokingF                                              the PATHWORKS mail server  D         SYS$STARTUP:PWRK$ACME_STARTUP.COM    External authentication9                                              startup fileB  C         SYS$STARTUP:PWRK$CHECK_PARAMS.COM    Command procedure that D                                              checks system resources  C         SYS$STARTUP:PWRK$COMMON_LOGICALS.COM Command procedure that D                                              defines common logicals  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.L  H                                                 (continued on next page)  A         F-8 PATHWORKS Advanced Server Files and On-Disk Structure  e  r      H                    PATHWORKS Advanced Server Files and On-Disk StructureH                                      F.1 PATHWORKS Advanced Server Files  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  D         SYS$STARTUP:PWRK$COMMON_SHUTDOWN.COM Common shutdown command6                                              procedure  C         SYS$STARTUP:PWRK$COMMON_STARTUP.COM  Common startup commandr6                                              procedure  C         SYS$STARTUP:PWRK$GATHER_INFO.COM     Command procedure that E                                              gathers information into E                                              a save set for reporting 5                                              problems_  D         SYS$STARTUP:PWRK$LICENSE_R_          Startup for the License6         START.COM                            Registrar  D         SYS$STARTUP:PWRK$LICENSE_S_          Startup for the License3         START.COM                            Server   D         SYS$STARTUP:PWRK$LICENSE_            License Server shutdown>         SHUTDOWN.COM                         command procedure  C         SYS$STARTUP:PWRK$LICENSE_            License Server startup >         STARTUP.COM                          command procedure  A         SYS$STARTUP:PWRK$LMBROWSER_          Browser startup file$         START.COM1  C         SYS$STARTUP:PWRK$LMMCP_START.COM     Command procedure that H                                              runs the PATHWORKS Advanced>                                              Server controller  C         SYS$STARTUP:PWRK$LMSRV_START.COM     Command procedure that H                                              runs the PATHWORKS Advanced3                                              Server   C         SYS$STARTUP:PWRK$LOGICALS.COM        Command procedure thatSB                                              defines logical names  C         SYS$STARTUP:PWRK$PCSA_SHUTDOWN.COM   PATHWORKS for VMS V4.x G                                              shutdown command procedure   G         SYS$STARTUP:PWRK$SHUTDOWN.COM        Shutdown command procedurei  F         SYS$STARTUP:PWRK$STARTUP.COM         Startup command procedure  ?         SYS$SYSTEM:NetBIOS.EXE               NetBIOS for DECnet   H                                                 (continued on next page)  H                PATHWORKS Advanced Server Files and On-Disk Structure F-9    Y      =         PATHWORKS Advanced Server Files and On-Disk StructureL+         F.1 PATHWORKS Advanced Server Filese  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  A         SYS$SYSTEM:PCDISK.EXE                DOS File Maintenance 4                                              utility  B         SYS$SYSTEM:PCSA$MAIL_SERVER.EXE      PATHWORKS client mail3                                              server   D         SYS$SYSTEM:PCSA_CLAIM_NAME.EXE       PCSA claim name utility  C         SYS$SYSTEM:PCX$SERVER.COM            Command procedure that G                                              starts the PC DECwindows XH?                                              server (eXcursion)n  F         SYS$SYSTEM:PWRK$ACLADM.EXE           Server configuration tool  E         SYS$SYSTEM:PWRK$ADMIN.COM            Remote Net Admin command_6                                              procedure  B         SYS$SYSTEM:PWRK$ADMIN_CFG.EXE        Configuration Manager4                                              utility  D         SYS$SYSTEM:PWRK$ADMIN_LIC.EXE        License Manager utility  B         SYS$SYSTEM:PWRK$BANNER.EXE           Utility that collectsC                                              system information and E                                              inserts it at top of log 2                                              files  F         SYS$SYSTEM:PWRK$BLOBADM.EXE          Server configuration tool  F         SYS$SYSTEM:PWRK$CHACL.EXE            Server configuration tool  F         SYS$SYSTEM:PWRK$CHDOMAIN.EXE         Server configuration tool  D         SYS$SYSTEM:PWRK$CHGROUP.EXE[1]       Standalone utility thatB                                              manages the PATHWORKSC                                              Advanced Server groupsT5                                              database   D         SYS$SYSTEM:PWRK$CHUSER.EXE[1]        Standalone utility thatB                                              manages the PATHWORKSA                                              Advanced Server userR>                                              accounts database  E         SYS$SYSTEM:PWRK$CHANGEV5ROLE.EXE     V5 to V6 Upgrade utility   H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.   H                                                 (continued on next page)  B         F-10 PATHWORKS Advanced Server Files and On-Disk Structure    Y      H                    PATHWORKS Advanced Server Files and On-Disk StructureH                                      F.1 PATHWORKS Advanced Server Files  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  B         SYS$SYSTEM:PWRK$DELETEACE.EXE        File ACE utility thatB                                              removes unwanted ACEs  B         SYS$SYSTEM:PWRK$ELFREAD.EXE          Event log file reader4                                              utility  @         SYS$SYSTEM:PWRK$EVTREPORT.EXE        Event logger report6                                              generator  B         SYS$SYSTEM:PWRK$FIXACE.EXE           File ACE utility thatE                                              compresses ACEs, removes E                                              unnecessary ACEs, and so 2                                              forth  F         SYS$SYSTEM:PWRK$GETROLE.EXE          Server configuration tool  B         SYS$SYSTEM:PWRK$KNBDAEMON.EXE        Kernel NetBIOS daemon4                                              process  >         SYS$SYSTEM:PWRK$LICENSE_REGISTRAR.EXELicense Registrar  ;         SYS$SYSTEM:PWRK$LICENSE_SERVER.EXE   License Serverd  A         SYS$SYSTEM:PWRK$LMECHO.EXE           Debugging utility[1]   F         SYS$SYSTEM:PWRK$LMBROWSER.EXE        PATHWORKS Advanced Server:                                              browser image  F         SYS$SYSTEM:PWRK$LMMCP.EXE            PATHWORKS Advanced Server7                                              controllerY  D         SYS$SYSTEM:PWRK$LMSHARE.EXE[1]       Standalone utility thatB                                              manages the PATHWORKSC                                              Advanced Server shares:5                                              database   F         SYS$SYSTEM:PWRK$LMSRV.EXE            PATHWORKS Advanced Server  A         SYS$SYSTEM:PWRK$LMSTAT.EXE           Debugging utility[1]:  G         SYS$SYSTEM:PWRK$LOADSTREAMS_V6.EXE   Loader for streams system-:;                                              loadable image   G         SYS$SYSTEM:PWRK$LOADSTREAMS_V7.EXE   Loader for streams system-T;                                              loadable image   H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.l  H                                                 (continued on next page)  H               PATHWORKS Advanced Server Files and On-Disk Structure F-11 L  N      =         PATHWORKS Advanced Server Files and On-Disk StructureL+         F.1 PATHWORKS Advanced Server Files   D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  H         SYS$SYSTEM:PWRK$LR_SHOW_USAGE.EXE[1] License count units utility  A         SYS$SYSTEM:PWRK$LSACL.EXE            Debugging utility[1]   F         SYS$SYSTEM:PWRK$MAKEMACH.EXE         Server configuration tool  D         SYS$SYSTEM:PWRK$MANAGER.EXE          ADMINISTER command lineC                                              user interface utilitya  A         SYS$SYSTEM:PWRK$MAPUNAME.EXE         Debugging utility[1]h  E         SYS$SYSTEM:PWRK$MASTER.EXE           Master process and event_3                                              logger_  D         SYS$SYSTEM:PWRK$MODAL.EXE[1]         Standalone utility thatB                                              manages the PATHWORKSC                                              Advanced Server modalsR5                                              database   F         SYS$SYSTEM:PWRK$MONITOR.EXE          PATHWORKS Monitor utility  C         SYS$SYSTEM:PWRK$NBDAEMON.EXE         NetBIOS daemon process   H         SYS$SYSTEM:PWRK$NBSHOW.EXE[1]        NetBEUI show status utility  A         SYS$SYSTEM:PWRK$NETEVENT.EXE         Debugging utility[1]   G         SYS$SYSTEM:PWRK$PWMON.EXE[1]         Host-based monitor utility   F         SYS$SYSTEM:PWRK$RMACL.EXE            Server configuration tool  F         SYS$SYSTEM:PWRK$SAMCHECK.EXE[1]      Server configuration tool  H         SYS$SYSTEM:PWRK$SETSHO.EXE           Set/Show Parameters utility  G         SYS$SYSTEM:PWRK$SHOWINI.EXE[1]       Utility that displays file H                                              and print server parameters  D         SYS$SYSTEM:PWRK$SHOWQUOTA.EXE        Show Disk Quota utility  A         SYS$SYSTEM:PWRK$SRVCONFIG.EXE        Debugging utility[1]e  @         SYS$SYSTEM:PWRK$START.EXE            Utility that startsD                                              detached master process@                                              and other processes  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.   H                                                 (continued on next page)  B         F-12 PATHWORKS Advanced Server Files and On-Disk Structure           H                    PATHWORKS Advanced Server Files and On-Disk StructureH                                      F.1 PATHWORKS Advanced Server Files  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  @         SYS$SYSTEM:PWRK$START_PRINTERS.EXE   Utility that startsG                                              printer queues and printers9                                              destinations   A         SYS$SYSTEM:PWRK$STARTSVC.EXE         Debugging utility[1]   F         SYS$SYSTEM:PWRK$STOP.EXE             Utility that stops server6                                              processes  F         SYS$SYSTEM:PWRK$VAPFADM.EXE          Server configuration tool  B         SYS$SYSTEM:PWRK$VERIFY.EXE           Utility that verifiesE                                              configuration parameters_  F         SYS$TEST:PWRK$IVP.COM                Installation Verification<                                              Procedure (IVP)  F         SYS$TEST:PWRK$IVP.DAT                Installation Verification@                                              Procedure data file  @         SYS$UPDATE:PWRK$COMMANDS.CLD         Server command line8                                              definitions  C         SYS$UPDATE:PWRK$COMMON.SAV[2]        Backup saveset for theIE                                              initial server directory 1                                              treer  A         SYS$UPDATE:PWRK$COMMON_CONFIG.COM    Common configurationp>                                              command procedure  G         SYS$UPDATE:PWRK$CONFIG.COM           Main configuration commands6                                              procedure  C         SYS$UPDATE:PWRK$DEFINE_FORMS.COM[2]  Command procedure that B                                              defines printer forms  F         SYS$UPDATE:PWRK$DEINSTAL.COM         PATHWORKS Advanced ServerF                                              removal command procedure  H         SYS$UPDATE:PWRK$GETPARAM.COM         Command procedure that getsF                                              a parameter from PWRK.INI  H         [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__         or command procedure.R?         [2]This file is deleted while you configure the server.   H                                                 (continued on next page)  H               PATHWORKS Advanced Server Files and On-Disk Structure F-13           =         PATHWORKS Advanced Server Files and On-Disk Structure7+         F.1 PATHWORKS Advanced Server FilesM  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  C         SYS$UPDATE:PWRK$INSTALL_COMMANDS.COM Command procedure thatO@                                              installs server DCL5                                              commands   C         SYS$UPDATE:PWRK$LANMAN.SAV[2]        BACKUP saveset for the G                                              initial PATHWORKS Advanced B                                              Server directory tree  F         SYS$UPDATE:PWRK$LICENSE_CONFIG.COM   License Server configura-C                                              tion command procedured  E         SYS$UPDATE:PWRK$LICENSE.SAV          PATHWORKS client license 4                                              saveset  H         SYS$UPDATE:PWRK$LMCONFIG.COM         Command procedure that setsE                                              up the initial PATHWORKSYF                                              Advanced Server directory1                                              treeE  C         SYS$UPDATE:PWRK$SETINI.COM           Command procedure that C                                              updates file and printE>                                              server parameters  H         SYS$UPDATE:PWRK$SETPARAM.COM         Command procedure that setsD                                              a parameter in PWRK.INI  C         SYS$UPDATE:PWRK$VERSIONS.COM         Command procedure thatpH                                              shows server image versions  >         SYS$UPDATE:PWRK$ROLLBACK.COM         Command procedureA                                              for restoring the V5e8                                              environment  E         SYS$UPDATE:PWRK$V6UPGRADE.EXE        V5 to V6 Upgrade utility   E         SYS$UPDATE:PWRK$V6UPGRADE.COM        V5 to V6 upgrade command 6                                              procedure  (         SYS$UPDATE:PWRK$V6UPGRADE_V6.EXE  (         SYS$UPDATE:PWRK$V6UPGRADE_V7.EXE  H         [2]This_file_is_deleted_while_you_configure_the_server._________  H                                                 (continued on next page)  B         F-14 PATHWORKS Advanced Server Files and On-Disk Structure Y  T      H                    PATHWORKS Advanced Server Files and On-Disk StructureH                                      F.1 PATHWORKS Advanced Server Files  D         Table F-1 (Cont.) Files Installed for the PATHWORKS AdvancedH         __________________Server________________________________________  H         File_________________________________Description________________  ?         SYS$UPDATE:PWRK$PWUTIL.SAV[2]        BACKUP saveset for C                                              PATHWORKS client-basedC6                                              utilitiesH         [2]This_file_is_deleted_while_you_configure_the_server._________  H         ________________________________________________________________  7         F.2 PATHWORKS Advanced Server On-Disk Structured  E               Figure F-1, PATHWORKS Advanced Server On-Disk Structure B               Diagram, shows the PATHWORKS Advanced Server on-diskH               structure. Note that only a portion of the substructure is               shown.                                                      H               PATHWORKS Advanced Server Files and On-Disk Structure F-15 _  _      =         PATHWORKS Advanced Server Files and On-Disk Structures7         F.2 PATHWORKS Advanced Server On-Disk StructureO  D               Figure F-1 PATHWORKS Advanced Server On-Disk Structure                           Diagram  *               pwrk$commonroot, pwrk$lmroot                 |                  |___lanman                 |u"                 |     ---.accounts#                 |     ---.datafiles                  |     ---.debug !                 |     ---.domainst                 |     ---.logs                 |     ---.repl!                 |     ---.samsave                   |     ---.shares!                 |     ---.upgrade                  |r                 |___licenseO                 |                  |___logs                 |K                 |___params                 |                  |___perfdata                 |                  |___printK                 |                  |___section                  |                  |___spoold                 |                  |___temp                          B         F-16 PATHWORKS Advanced Server Files and On-Disk Structure u                     H                                                                        GH         ________________________________________________________________  H                                  PATHWORKS Advanced Server Logical Names      A               Table G-1, PATHWORKS Advanced Server Logical Names,TC               describes the logical names that are created when you ?               configure or start the PATHWORKS Advanced Server.   H               Table_G-1_PATHWORKS_Advanced_Server_Logical_Names_________  H               Logical_Name_______________Description____________________  D               NETBIOS$DEVICE             Used for the DECnet device.A                                          This logical name is not E                                          defined during installation;UE                                          it is used to define networkK?                                          adapters under certainTA                                          circumstances. (For more F                                          information, see Section 3.8,D                                          The Advanced Server Network2                                          Adapter.)  A               PWRK$ACME_MODULE           System-specific external H                                          authentication software (either7                                          VAX or Alpha)._  H                                                 (continued on next page)                        H                              PATHWORKS Advanced Server Logical Names G-1           /         PATHWORKS Advanced Server Logical NamesL    H               Table_G-1_(Cont.)_PATHWORKS_Advanced_Server_Logical_Names_  H               Logical_Name_______________Description____________________  E               PWRK$ACME_SERVER           On an OpenVMS Cluster memberu@                                          that is not running theA                                          Advanced Server softwareeA                                          and does not have accesseC                                          to external authenticationRF                                          software by means of a sharedF                                          cluster disk, defines OpenVMS@                                          Advanced Server clusterF                                          members designated to process@                                          external authenticationB                                          requests for that member.A                                          This logical name is not E                                          defined during installation.$C                                          (For more information, see B                                          Section 5.6.1, Setting UpC                                          External Authentication in ;                                          OpenVMS Clusters.)l  C               PWRK$ACME_DEFAULT_DOMAIN   Defines the default domainWA                                          for users using externalgE                                          authentication. This logical C                                          name is not defined during @                                          installation. (For moreB                                          information, refer to theE                                          Compaq PATHWORKS for OpenVMSYA                                          (Advanced Server) Server @                                          Administrator's Guide.)  @               PWRK$ADDON_LIBRARY         Location of file system9                                          shareable imagesP  @               PWRK$COMMON                Top-level directory forB                                          PATHWORKS Advanced Server  G               PWRK$COMMONROOT[1]         Root of the PATHWORKS AdvancedlE                                          Server common directory treec  ?               PWRK$CSSHR                 Common services module_  H               [1]This_logical_name_requires_that_you_specify_the________                directory with it.  H                                                 (continued on next page)  3         G-2 PATHWORKS Advanced Server Logical NamesT P  $      H                                  PATHWORKS Advanced Server Logical Names    H               Table_G-1_(Cont.)_PATHWORKS_Advanced_Server_Logical_Names_  H               Logical_Name_______________Description____________________  D               PWRK$KNBDAEMON_DEVICE      Used for the TCP/IP device,A                                          this logical name is not E                                          defined during installation; E                                          it is used to define networkR?                                          adapters under certainPA                                          circumstances. (For more F                                          information, see Section 3.8,D                                          The Advanced Server Network2                                          Adapter.)  G               PWRK$LANMAN                PATHWORKS Advanced Server area.  H               PWRK$LANMAN_STARTED        Indicates whether the PATHWORKSA                                          Advanced Server has been 1                                          started.   B               PWRK$LICENSE               PATHWORKS Advanced Server5                                          license area   G               PWRK$LMDATAFILES           PATHWORKS Advanced Server data 3                                          files area   C               PWRK$LMDEBUG               Area where trace files areM0                                          written  B               PWRK$LMDOMAINS             PATHWORKS Advanced Server4                                          domain area  F               PWRK$LMLOGS                PATHWORKS Advanced Server log2                                          file area  F               PWRK$LMMSGFILES            Advanced Server message files  G               PWRK$LMROOT[1]             Root of the PATHWORKS Advancedp>                                          Server directory tree  F               PWRK$LMMSGFILES            Advanced Server message files  B               PWRK$LMUPGRADE             PATHWORKS Advanced Server5                                          upgrade areaD  F               PWRK$LMREPLEXPORT          Export replication files area  F               PWRK$LMREPLIMPORT          Import replication files area  H               [1]This_logical_name_requires_that_you_specify_the________                directory with it.  H                                                 (continued on next page)  H                              PATHWORKS Advanced Server Logical Names G-3 i  u      /         PATHWORKS Advanced Server Logical Names     H               Table_G-1_(Cont.)_PATHWORKS_Advanced_Server_Logical_Names_  H               Logical_Name_______________Description____________________  A               PWRK$LMSAMSAVE             SAM database backup areag  A               PWRK$LMSAMSAVEX            SAM database backup areae  F               PWRK$LOADSTREAMS           Logical for LoadStreams image  =               PWRK$LOGS                  Common log file areat  D               PWRK$LR_DISABLE_CLIENT_    Defines whether the LicenseG               PING                       Registrar checks for a client- C                                          based license or, instead,$G                                          attempts immediately to assign$E                                          a server-based license. (For$C                                          more information, refer to C                                          the Compaq Advanced Server F                                          for OpenVMS Guide to ManagingC                                          Advanced Server Licenses.)   C               PWRK$LR_LICENSE_REPORT_    Determines the interval atlD               INTERVAL                   which reports about server-H                                          based licenses are generated inH                                          the License Registrar log file;F                                          by default, these reports are7                                          not generated.D  B               PWRK$LR_LOG_SERVERBASED_   Determines whether events@               ACTIVITY                   related to server-based>                                          licensing are logged.  G               PWRK$LS_V6_ACCESS_UPGRADE  Included in the License Server_G                                          startup file to allow upgrades D                                          of PATHWORKS V5 for OpenVMSE                                          (LAN Manager) client license 2                                          requests.  G               PWRK$LS_V7_ACCESS_UPGRADE  Included in the License ServerAG                                          startup file to allow upgrades D                                          of PATHWORKS V5 for OpenVMSE                                          (LAN Manager) client licenseD2                                          requests.  H                                                 (continued on next page)  3         G-4 PATHWORKS Advanced Server Logical Names            H                                  PATHWORKS Advanced Server Logical Names    H               Table_G-1_(Cont.)_PATHWORKS_Advanced_Server_Logical_Names_  H               Logical_Name_______________Description____________________  E               PWRK$NETBEUI_DEVICE        Used for the NetBEUI device,oA                                          this logical name is notiE                                          defined during installation;tE                                          it is used to define networki?                                          adapters under certainVA                                          circumstances. (For moreiF                                          information, see Section 3.8,D                                          The Advanced Server Network2                                          Adapter.)  7               PWRK$PARAMS                Parameter areau  4               PWRK$PCFSDRIVER            PCFS driver  3               PWRK$PCIDRIVER             PCI driver   F               PWRK$PERFDATA              PATHWORKS monitor performance7                                          data directory   B               PWRK$PRINT                 PATHWORKS Advanced ServerC                                          printer database directory   @               PWRK$ROOT                  Top-level directory forB                                          PATHWORKS Advanced Server  ;               PWRK$SAMSAVE               SAMCHECK data areaL  ;               PWRK$SAMSAVEX              SAMCHECK data area   :               PWRK$SECTION               Section file area  H               PWRK$SHARED_IMAGES         Indicates whether shared images:                                          have been loaded.  3               PWRK$SPOOL                 Spool areap  E               PWRK$TEMP                  Temporary PATHWORKS Advanced 5                                          Server files   F               PWRK$VERSION               File and print server versionH               ___________________________number_________________________  H                              PATHWORKS Advanced Server Logical Names G-5    H                          E      ________________________________________________________________c  E                                                                 Index_    B      A                                    Advanced Server (cont'd)@      ___________________________           sample deinstallation=      ADMINISTER/CONFIGURATION                 procedure,  7-4a  B        See Configuration Manager           sample installation andA      Administrator account                    configuration,  B-4 9        local to member server,             starting,  5-4P:          3-11                              starting duringC        password                               configuration,  3-12,C2           changing, 3-12                      3-188           for member server,               startup,  5-49             3-11                           stopping,  5-7eC           joining a domain,                user accounts, removing, 1             3-11, 3-12                        7-2u>           setting, 3-11                   Advanced Server disk=           verifying, 3-11, 3-12            changing the,  3-4 @           whether to provide              Advanced Server imagesD             during configuration           checking status of,  1-219             ,  3-11                       Alerter service ?      Advanced Server                       description of,  3-8 <        cluster alias, 3-10                Automatic shutdownD        configuring, 3-1                    of file and print server,1        data files, removing, 7-2              5-8Y        files installed for, F-1 E        installing, 2-2                    B__________________________s>        kit contents, 2-2                  BACKUP command, 1-17B        logical names, G-1                 Backup domain controllerB        logical names,                      configuring transports,1          deassigning,  7-3                    3-5RC        NETBIOS image, removing,            designating,  3-9, 3-20,62          7-2                                  3-21        role, 3-9, 3-20           changing, 3-23           configuring, 3-21P  E                                                               Index-1i i  i            C         BDC                                 Configuration procedure 7          See Backup domain                     (cont'd)-  ?             controller                        sample script for C         Boot                                     standalone Licenser<          See Reboot                              Server, C-3=                                               starting,  3-13 E         C__________________________           starting server during,_;         Checklist for installation               3-12, 3-18_A           and configuration,  A-1             starting standaloneRG         Client-based server                      License Server during, 4           administration tools,                  4-57           5-16                              Configuring_F         Client software                       backup domain controller@          LAN Manager,  1-8                       transports, 3-5B          supported,  1-8                      member server,  3-25G                                               member server transports, 4         Clusters                                 3-5  G          See OpenVMS Clusters                 standalone License Server ;         Computer name, 3-9                       , 4-2, 4-3 F          SCSNODE parameter and,               wide area networks,  3-5             1-15G         Configuration Manager,              D__________________________s6           3-2, 3-4                          Data files<         Configuration procedure               removing,  7-25          changing default settings          Data loss ?             ,  3-19                           preventing,  1-17 >          disk space required for              restoring duringF             complete server data                 reconfiguration, 3-310             files,  3-4                     DCPSE          disk space required for              See DECprint Supervisor @             standalone License                   (DCPS) software2             Server data files,  4-4         DECnet=          for Advanced Server,  3-1            starting,  1-19 =          for previously configured          DECnet (Phase IV) D             server,  3-31                     checking status,  1-19:          preparing for the                  DECnet objects<             Advanced Server,  3-3             removing,  7-37          prerequisites,  3-3                DECnet-Plus D          responding to prompts,               checking status,  1-19=             3-13, 4-4                         starting,  1-19 B          sample script for                  DECnet transport,  1-8<             PATHWORKS Advanced                running duringD             Server,  B-4                         configuration, 1-19           Index-2l -  P            7         DECnet transport (cont'd)           Domain name @          status of,  1-19                     term defined,  3-97         DECprint Supervisor for             Domain role =           OpenVMS (DCPS) software,            changing,  3-23 @           1-2                                 configuring,  3-21            Deinstallation procedureG          description of,  7-2               E__________________________   7          guidelines for,  7-1               ENQLM quota E          PATHWORKS Advanced Server            minimum required,  1-16 C             ,  7-3                          External authentication C          PATHWORKS for OpenVMS                See also Pass-through ?             (NetWare),  7-5                      authentication >         Device name, 2-3                      bypassing,  5-15@         Disk space requirements,              configuring clientF           1-17                                   connections for, 5-14E          configuring complete                 on a system not running E             server data files,  3-4              the Advanced Server, 5          configuring License                     5-12 F             Server,  4-4                      requirement over DECnet-;          determining,  1-17                      Plus, 5-14ND         DNS                                   server capacity,  5-14>          configuring to use,  6-10            setting up,  5-8@          setup,  6-9                          setting up OpenVMS?         Domain                                   Clusters, 5-12 C          joining automatically, by          External authentication 7             PWRK$CONFIG,  3-11                 software ?          joining manually, by                 installing,  2-28 A             ADMINISTER ADD COMPUTER           sample installation <             command,  3-11                       script, E-1D         Domain administrator                  separate installation,4           account                                2-5           local to member server,G             3-11                            F__________________________ B          password                           File and print servers;             changing,  3-12                   NetWare,  1-2 <             for member server,                starting,  5-4<                3-11                           stopping,  5-71             joining a domain,               Files$C                3-11, 3-12                     created by installing C             verifying,  3-11, 3-12               PATHWORKS Advanced <             whether to provide                   Server, F-1#                during configuration                 ,  3-11  H                                                                  Index-3                 B                                             Installation procedure7         G__________________________            (cont'd)   ?         GBLPAGES parameter                    sample script for C          checking and defining,                  standalone License <             1-12                                 Server, C-1G         GBLSECTIONS parameter                 sample script for Upgrade =          checking and defining,                  utility, D-2eG             1-13                              standalone License Server   6                                                  , 4-1<         H__________________________           starting,  2-6E         Hardware requirements,              Installation requirements ?           1-7, 1-10                           disk space,  1-17r<                                               hardware,  1-7H         I                                     in OpenVMS Clusters,  1-21=         ___________________________           licensing,  1-3 :         Installation kit                      memory,  1-8B          contents of,  2-2                    software,  1-8, 1-11E         Installation procedure              Installation Verificationg8          checklist,  A-1                       Procedure5          description,  2-1                    See IVPR;          failure, another server            Installed files_?             running,  2-26                    displaying,  2-25 /          files created by,  F-1             IVP_H          files installed,  2-25               during installation,  2-15>          information required for,            restriction whenC             2-2                                  installing UpgradenB          interrupting,  2-8                      utility only, D-1;          logical names created by,            running afteraB             G-1                                  installation, 5-3D          options,  2-3                        running automatically,5          prerequisites,  2-3                     2-23           PWRK$STREAMSOS_Vn.EXE-             detected,  2-11                 KAG          questions in,  2-8                 ___________________________e8          responding to prompts,             Kit contents=             2-6                               checking,  1-10             sample script forG             external authentication         L__________________________W  E             software,  E-1                  License Server,  1-4, 3-8 F          sample script for                    configuration procedure,4             PATHWORKS Advanced                   4-1E             Server,  B-1                      installation procedure,   4                                                  4-1           Index-4  w  t            9         License Server (cont'd)             NETBIOS imager<          standalone installation,             removing,  7-2C             2-4, 2-27                       NetBIOS name resolution =          startup and shutdown,  4-3           using DNS,  6-9 A         Licensing                             using LMHOSTS,  6-2 >          requirements,  1-3                   using WINS,  6-8B         LMHOSTS                             NETBIOS process,  3-33<          configuring to use,  6-2           NetLogon serviceC          transport configuration,             fails to start,  3-10n?             3-6                               function of,  3-9D  :         LMHOSTS name resolution,            NetWare server  G           3-6                                 See PATHWORKS for OpenVMS :         Load balancing, 3-5, 3-7,                (NetWare)B           6-2, 6-9                          Network adapter,  3-31=         Logical names                         defining,  3-32pC          created by PATHWORKS                 NETBIOS$DEVICE,  3-32l>             Advanced Server                   not found,  3-33E             installation,  G-1                OpenVMS logicals,  3-32eD          deassigning,  7-3                    PWRK$KNBDAEMON_DEVICE,5          startup procedure,  5-4                 3-32 H                                               PWRK$NETBEUI_DEVICE,  3-32  B         M__________________________         Network interface card  A         Management commands                   See Network adapter =          shortcuts for,  5-8                Network transportL@         Member server                          requirements, 1-8  /          advantage of,  3-25                NIC A          configuring,  3-25                   See Network adapter            configuring transports,G             3-5                             O__________________________ <          designating,  3-9, 3-20,           OpenVMS ClustersE             3-21                              checking configuration, 4          in OpenVMS Cluster,  3-5                1-9H          local Administrator                  cluster alias,  3-10, 3-21C             account password,  3-11           configuring nodes in, :         Memory requirements, 1-8                 3-3, 3-13  F         N                                     disk device for AdvancedB         ___________________________              Server files, 3-4?         NETBIOS$ACCESS OpenVMS                enabling externallC           identifier                             authentication in,r4          removing,  7-2                          5-9C         NETBIOS$DEVICE, 3-32                  installing server in,   A                                                  1-21, 2-13, 3-13eE                                               LMHOSTS file,  3-6, 6-6e  H                                                                  Index-5                 8         OpenVMS Clusters (cont'd)           Part listing=          load balancing,  3-5, 3-6,           checking,  1-10eG             3-7, 6-2                        Pass-through authentications4          load balancing using DNS,             , 6-6  ?             6-9                               See also Externale?          loading client license                  authenticationo4             PAKs on,  4-2                   PasswordD          loading PAKs on,  1-4, 4-2           administrator account,5          member servers,  3-5                    3-11 D          running License Server             PATHWORKS cluster alias,3             on,  1-4, 4-2                      3-10AA          sample installation on,            PATHWORKS for OpenVMS C             C-1                                (NetWare), 1-2, 2-26 G          sample standalone                    deinstallation procedure, 4             configuration procedure              7-5<             ,  C-3                            licenses,  4-2C          server role in,  3-9                 sample deinstallationt?          setting up external                     procedure, 7-6 /             authentication,  5-12           PDC @          starting server in,  3-13,           See Primary domain;             5-5                                  controller C          starting standalone                Postinstallation tasks, 2             License Server in,                 5-1B             4-7                             Preinstallation tasks,8          WINS setup for,  6-9                  1-10, 2-3=         OpenVMS reboot                        checklist,  1-9uE          delaying,  2-13                    Primary domain controller F          preventing if unnecessary            designating,  3-9, 3-20,5             ,  2-12                              3-21 A          when needed,  2-12                 PROCSECTCNT parameterPD         Operating system                      checking and defining,5           requirements,  1-8                     1-14 D         Optional software, 5-16             Product identifier,  2-3  5         P                                   Protocols <         ___________________________           See TransportsE         Parameters                          PWRK$ACME_SERVER logical, 3          affecting system,  3-2,               5-13a;             3-4                             PWRK$CONFIG.COMrF          server configuration,                 configuration procedureD             3-15                              See also Configuration:             configuring,  3-19                   procedure  D                                               description and usage,4                                                  3-1           Index-6  _  _            F         PWRK$DEFINE_COMMANDS.COM,           Release notes,  1-11, 2-3,3           5-8                                  2-17 E         PWRK$DEINSTAL procedure               in SYS$HELP: area,  1-6_<          See Deinstallation                   location afterC             procedure                            installation, 2-25 <         PWRK$DELETEACE.EXE, 7-2               printing,  1-68         PWRK$FIXACE.EXE, 7-2                Requirements=         PWRK$KNBDAEMON process,               hardware,  1-10C  -           3-33                              SnG         PWRK$KNBDAEMON_DEVICE,              ___________________________ =           3-32                              SCSNODE parameter =         PWRK$NBDAEMON process,                defining,  1-15pD           3-33                              Security Account Manager=         PWRK$NETBEUI_DEVICE, 3-32              (SAM) databaser9         PWRK$STARTUP.COM                      files,  3-3 F          See Startup procedure              Security accounts database?         PWRK$STREAMSOS_Vn.EXE                 on primary domain B          detected during                         controllers, 3-222             installation,  2-11             ServerC         PWVN$STARTUP.COM                      capacity for external E          description of,  5-4                    authentication, 5-14eF                                               on-disk structure,  F-15=         Q                                     starting duringiD         ___________________________              configuration, 3-18G         Queue manager                       Server administration tools,?          checking,  1-17                      installing,  5-16sD          running during                     Server announce comment,3             configuration,  1-17               3-10 F          starting,  1-17                    Server configuration,  3-8  @                                             Server configuration?         R__________________________            parameters, 3-15   >         Reboot                                affecting serverC          and DECprint Supervisor                 configuration, 3-81>             for OpenVMS                       affecting systemB             installation,  1-3                   environment, 3-2,4          and system changes,  1-11               3-4@          delaying,  2-13                      configuring,  3-19G          preventing if unnecessary          SHOW QUEUE/MANAGER command,l3             ,  2-12                            1-17 >          when needed,  2-12                 Shutdown procedureG         Reconfiguration, 3-31                 for file and print server 6                                                  , 5-7  H                                                                  Index-7 l               <         Software requirements,              Startup (cont'd)G           1-8, 1-11                           using the SYSMAN utility, 4         Standalone License Server,               5-6E           1-4, 4-2                          Stopping the server,  5-7 7          sample installation and            SYLOGIN.COM D             configuration procedure           conditionalizing,  5-7D             ,  C-1                          SYS$SINGLE_SIGNON,  5-9,9          starting during                       5-13, 5-15 :             configuration,  4-5             SYSMAN utilityA          startup,  4-6                        using STARTUP,  5-6t:         START/QUEUE/MANAGER command         SYSTEM accountB           ,  1-17                             logging in to,  1-10@         Starting                            System backup,  1-177          Advanced Server,  5-4              System disk_>          Advanced Server during               space needed forC             configuration,  3-12                 installation, 1-17 =          DECnet,  1-19                      System parameters D          PATHWORKS Advanced Server            checking and defining,5             automatically,  5-5                  1-11g9          PATHWORKS Advanced Server          System rebootu=             in OpenVMS Clusters,              delaying,  2-13 G             5-5                               preventing if unnecessary 7          PATHWORKS Advanced Server               , 2-12t@             manually,  5-5                    when needed,  2-12;          standalone License Server          System shutdown C             ,  4-6                            file and print server B          standalone License Server               shutdown and, 5-8:             automatically,  4-6             System startupC          standalone License Server            troubleshooting,  5-7s?             during configuration,           System startup fileo;             4-5                               editing,  5-5   -          standalone License Server          T G             in a cluster,  4-7              ___________________________ >          standalone License Server          Task summary,  A-18             manually,  4-6                  TCP/IP,  1-8F          TCP/IP,  1-20                        configuring the AdvancedC         Startup                                  Server to support, 5          Advanced Server,  5-4                   1-20 @          automatic,  5-5                      in clusters,  1-21=          manual,  5-5                         starting,  1-20 >          procedure for file and               status of,  1-20               print server,  5-4          troubleshooting,  5-7           Index-8e e  o            9         TCP/IP cluster alias, 3-7,          WINS (cont'd) ?           3-10                                setup for OpenVMS >         TCP/IP cluster impersonator              Clusters, 6-9F           name,  3-7, 3-10                    transport configuration,4         Timesource service                       3-5          description of,  3-8          Time zone            checking setting,  1-18         Transports          for LMHOSTS,  3-6          for WINS,  3-5           selecting,  3-5  #         U__________________________   !         Upgrade utility, 1-2, D-1           Upgrading PATHWORKS (LAN           Manager),  2-27v         User accountsi          removing,  7-2   #         V__________________________            VMSINSTALu            See also Installation             procedure           description,  2-1          starting,  2-6   #         W__________________________4           Wide area domain, 6-1-         Wide area networking          providing,  3-5         Windows 2000#          domain environment,  3-22,              3-25!          mixed-mode domain,  3-21 "          native-mode domain,  3-21         Windows NT server            administration tools,            5-16          installing,  5-16         WINS!          configuring to use,  6-8   H                                                                  Index-9