                                     7                      Compaq Advanced Server for OpenVMS @                      Server Installation and Configuration Guide  .                      Order Number: AA-RFM3B-TE                          March 2001   E                      This guide explains how to install and configure >                      the Advanced Server for OpenVMS software.          D                      Revision/Update Information: This manual super-B                                                   sedes the ServerB                                                   Installation andF                                                   Configuration Guide,=                                                   AA-RFM3A-TE   G                      Operating System:            OpenVMS Alpha Version 7                                                   7.2-1   F                      Software Version:            Advanced Server V7.3=                                                   for OpenVMS       0                      Compaq Computer Corporation#                      Houston, Texas                  E            __________________________________________________________   -             2001 Compaq Computer Corporation   C            Compaq, the Compaq logo, VAX, and VMS Registered in U.S. '            Patent and Trademark Office.   E            AlphaStation, DEC, DECnet, DECwindows, PATHWORKS, OpenVMS, >            and POLYCENTER are trademarks of Compaq InformationB            Technologies Group, L.P. in the United States and other            countries.   D            Microsoft, MS-DOS, Windows, and Windows NT are trademarksB            of Microsoft Corporation in the United States and other            countries. B            Intel is a trademark of Intel Corporation in the United&            States and other countries.E            UNIX is a trademark of The Open Group in the United States             and other countries.   E            All other product names mentioned herein may be trademarks )            of their respective companies.   D            Confidential computer software. Valid license from Compaq?            required for possession, use, or copying. Consistent D            with FAR 12.211 and 12.212, Commercial Computer Software,B            Computer Software Documentation, and Technical Data forE            Commercial Items are licensed to the U.S. Government under 0            vendor's standard commercial license.  @            Compaq shall not be liable for technical or editorial@            errors or omissions contained herein. The information@            in this document is provided "as is" without warranty?            of any kind and is subject to change without notice. >            The warranties for Compaq products are set forth in?            the express limited warranty statements accompanying ?            such products. Nothing herein should be construed as /            constituting an additional warranty.   E                                                                ZK6540   C            The Compaq Advanced Server for OpenVMS documentation set "            is available on CD-ROM.  A            This document was prepared using VAX DOCUMENT, Version             2.1.                                C    ________________________________________________________________   C                                                            Contents     C    Preface..................................................     xi     4    1  Before You Install Advanced Server for OpenVMS       Software  C       1.1  About the Advanced Server Software Kit..........     1-1 C       1.1.1   About VAX Systems ............................    1-2 C       1.1.2   Upgrading to Advanced Server for OpenVMS .....    1-2 8       1.1.2.1   LANMAN.INI Parameters Migrate to OpenVMSC                 Registry...................................     1-3 C       1.1.2.2   Upgrading OpenVMS Clusters.................     1-4 C       1.2  Installing DECprint Software....................     1-5 C       1.3  About Licensing.................................     1-5 C       1.3.1   License Requirements .........................    1-5 C       1.3.2   About the License Server .....................    1-6 C       1.4  About External Authentication...................     1-7 C       1.5  About the Release Notes.........................     1-8 4       1.5.1   How to Access the Release Notes BeforeC               Installation..................................    1-8 7       1.5.2   How to Access the Release Notes After the C               Installation..................................    1-8 C       1.6  Using the Installation Checklist................     1-8 :       1.7  Requirements for Installing Advanced Server forC            OpenVMS Software................................     1-9 C       1.7.1   Hardware Requirements ........................    1-9 C       1.7.2   Software Requirements ........................    1-9 C       1.7.3   Supported Client Software ....................   1-10 C       1.7.4   Memory Requirements ..........................   1-10 C       1.8  Preinstallation Tasks...........................    1-10 C       1.8.1   Step 1: Check the Part Listing ...............   1-12 C       1.8.2   Step 2: Check the Network Hardware ...........   1-12 C       1.8.3   Step 3: Log In to the SYSTEM Account .........   1-12   C                                                                 iii                  E          1.8.4  Step 4: Check the Required Software ..........   1-12 E          1.8.5  Step 5: Start the OpenVMS Registry Server ....   1-13 E          1.8.6  Step 6: Print and Read the Release Notes .....   1-14 E          1.8.7  Step 7: Check System Parameters ..............   1-14 E          1.8.7.1   GBLPAGES Parameter.........................   1-14 E          1.8.7.2   GBLSECTIONS Parameter......................   1-15 E          1.8.7.3   PROCSECTCNT Parameter......................   1-15 E          1.8.7.4   SCSNODE Parameter..........................   1-16 E          1.8.8  Step 8: Back Up the System ...................   1-17 E          1.8.9  Step 9: Check Disk Space Requirements ........   1-17 E          1.8.10 Step 10: Check the Queue Manager .............   1-18 E          1.8.11 Step 11: Check Time Zone and TDF .............   1-18 E          1.8.12 Step 12: Check DECnet Status .................   1-20 E          1.8.12.1  Checking DECnet (Phase IV) Status..........   1-20 E          1.8.12.2  Checking DECnet-Plus Status................   1-21 E          1.8.13 Step 13: Check TCP/IP Status .................   1-21 :          1.8.14 Step 14: Check for Existing OpenVMS ServerE                 Images and Files..............................   1-22 .          1.8.15 Step 15: Check OpenVMS ClusterE                 Configuration.................................   1-22 E          1.9  Next Step.......................................   1-24     7      2  Installing Advanced Server for OpenVMS Software   E          2.1  The Installation Procedure......................    2-1 E          2.1.1  Before You Start the Installation Procedure ..    2-2 E          2.1.2  Installing the Server ........................    2-4 E          2.1.3  What To Do After the Installation Completes ..   2-14 E          2.2  Troubleshooting Installation Problems...........   2-15 6          2.2.1  Installing Advanced Server for OpenVMSE                 Software on a VAX System......................   2-15 9          2.2.2  Installing Advanced Server for OpenVMS on 8                 a System Running Another Advanced ServerE                 Image.........................................   2-15 E          2.2.3  System Disk Restrictions .....................   2-16 ;          2.2.4  Installing Advanced Server for OpenVMS on a ;                 System with PATHWORKS for OpenVMS (Advanced E                 Server), Version 6.0A or Earlier..............   2-16 E          2.3  Next Steps......................................   2-17                 iv                  *         3  Configuring the Advanced Server  7            3.1  About the Advanced Server Configuration H                 Procedure.......................................     3-2H            3.1.1   What the Configuration Procedure Does ........    3-2>            3.2  Migrating LANMAN.INI Parameters to the OpenVMSH                 Registry........................................     3-44            3.3  Before You Start the Advanced ServerH                 Configuration Procedure.........................     3-5=            3.3.1   On What OpenVMS Disk Device Do You Want to H                    Store the Advanced Server Data Files?.........    3-5A            3.3.2   Do You Want to Change the System Configuration H                    Parameters Now?...............................    3-6?            3.3.2.1   Configuring Transports for a Backup Domain H                      Controller or Member Server................     3-7:            3.3.3   Do You Want to Change Any of the ServerH                    Configuration Settings?.......................   3-10=            3.3.4   What Do You Want the Administrator Account H                    Password to Be?...............................   3-14;            3.3.5   Are You Going to Supply Account/Password H                    Information?..................................   3-15H            3.3.6   What Is the Domain Administrator Password? ...   3-15;            3.3.7   Do You Want to Enter a New Administrator H                    Account Password?.............................   3-16H            3.3.8   Do You Want to Start the Server? .............   3-16>            3.4  How to Start the Advanced Server ConfigurationH                 Procedure.......................................    3-16?            3.5  How to Respond to Advanced Server Configuration H                 Prompts.........................................    3-16H            3.6  How to Change Server Configuration Settings.....    3-22H            3.7  Configuring the Advanced Server Domain Role.....    3-25>            3.7.1   Configuring the Advanced Server As a MemberH                    Server........................................   3-28:            3.7.1.1   Configuring a New Advanced Server forH                      OpenVMS to Be a Member Server..............    3-29@            3.7.1.2   Configuring an Existing Advanced Server forH                      OpenVMS BDC As a Member Server.............    3-32H            3.8  Configuring the Server Language.................    3-336            3.8.1   Considerations Regarding the ServerH                    Language......................................   3-33H            3.8.2   Example of Configuring the Server Language ...   3-34H            3.9  Configuring Windows NT Printer Management.......    3-36      H                                                                        v                 ;          3.9.1  Considerations Regarding Windows NT Printer E                 Management....................................   3-37 9          3.9.2  Example of Configuring Windows NT Printer E                 Management....................................   3-38 5          3.10 Troubleshooting Configuration Procedure E               Problems........................................   3-39 E          3.10.1 Registry Server Startup Problems .............   3-39 8          3.10.2 Ensuring Sufficient Resources to SupportE                 Clients.......................................   3-40 8          3.10.3 If Problems Occur When Reconfiguring theE                 Advanced Server...............................   3-41 E          3.11 The Advanced Server Network Adapter.............   3-41 E          3.11.1 Manually Defining the Network Adapter ........   3-42 8          3.11.2 What to Do If the Network Adapter Is NotE                 Found.........................................   3-43 E          3.12 Next Steps......................................   3-44     >      4  Configuring and Starting the Standalone License Server  E          4.1  About the License Server........................    4-1 :          4.2  Before You Begin to Configure the StandaloneE               License Server..................................    4-2 E          4.3  Configuring the Standalone License Server.......    4-3 E          4.4  Configuring the Transports......................    4-3 <          4.5  How to Respond to License Server ConfigurationE               Prompts.........................................    4-4 E          4.6  How to Start the Standalone License Server......    4-6 E          4.6.1  How to Start the License Server Manually .....    4-6 /          4.6.2  How to Start the License Server E                 Automatically.................................    4-7 =          4.6.3  How to Start the License Server in an OpenVMS E                 Cluster.......................................    4-7   -      5  After You Install the Advanced Server   E          5.1  Before You Begin Postinstallation Tasks.........    5-1 E          5.2  Verifying the Advanced Server Installation......    5-2 E          5.3  Starting the Advanced Server....................    5-2 E          5.3.1  When to Start the Advanced Server ............    5-2 E          5.3.2  What the Startup Procedure Does ..............    5-3 E          5.4  Ways to Start the Advanced Server...............    5-3 E          5.4.1  How to Start the Advanced Server Manually ....    5-4           vi                  3            5.4.2   How to Start the Advanced Server H                    Automatically.................................    5-4A            5.4.3   How to Start the Advanced Server in an OpenVMS H                    Cluster.......................................    5-4H            5.4.4   Troubleshooting the Startup ..................    5-5?            5.4.4.1   SYLOGIN.COM Contains Commands Not Suitable H                      for Detached Processes.....................     5-6H            5.4.4.2   OpenVMS Registry Services Not Available....     5-6@            5.4.5   Determining Initial Advanced Server ParameterH                    Values Stored in the OpenVMS Registry.........    5-7H            5.5  Stopping the Advanced Server....................     5-7H            5.6  Special Advanced Server Management Commands.....     5-8H            5.7  Setting Up External Authentication..............     5-8@            5.7.1   Setting Up External Authentication in OpenVMSH                    Clusters......................................   5-11?            5.7.2   Requirement for External Authentication Over H                    DECnet-Plus...................................   5-138            5.7.2.1   Configuring the Server Capacity forH                      External Authentication....................    5-13>            5.7.3   Configuring Externally Authenticated ClientH                    Connections...................................   5-13=            5.7.4   Bypassing External Authentication When the H                    Network Is Down...............................   5-14;            5.8  Converting Encoded File Names from ODS-2 to H                 ODS-5...........................................    5-14H            5.8.1   Using the File Name Conversion Utility .......   5-15H            5.8.2   Example of Converting an Encoded File Name ...   5-179            5.8.3   Example of Converting All Encoded File H                    Names.........................................   5-189            5.9  Installing Optional Server Administration H                 Tools...........................................    5-18    +         6  Implementing a Wide Area Network   H            6.1  Enabling Wide Area Network Support..............     6-1H            6.2  Using the LMHOSTS File in a Wide Area Network...     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-8H            6.3.1   Setting up WINS for OpenVMS Clusters .........    6-9  H                                                                      vii                 E          6.4  Using DNS in a Wide Area Network................    6-9r    5      7  Removing Advanced Server for OpenVMS Softwaref  E          7.1  Advanced Server Deinstallation..................    7-2m4          7.2  Removing Advanced Server ConfigurationE               Parameters......................................    7-3 E          7.3  Removing Advanced Server for OpenVMS Software...    7-3 >          7.3.1  Server Configuration Parameters in the OpenVMSE                 Registry......................................    7-6 E          7.4  Sample Advanced Server Removal Procedure........    7-6   *      A  Installation and Upgrade Checklist  =      B  Sample Advanced Server Installation and Configuration   E          B.1  Sample Advanced Server Installation Procedure...    B-1 E          B.2  Sample Advanced Server Configuration Procedure..    B-4   9      C  Sample Standalone License Server Installation and_         Configuration   ;          C.1  Sample Standalone License Server Installation,E               Procedure.......................................    C-1n8          C.2  Sample Configuration Dialog for StandaloneE               License Server..................................    C-3d  <      D  Sample External Authentication Software Installation    3      E  Advanced Server Files and On-Disk Structure   E          E.1  Advanced Server Files...........................    E-1 E          E.2  Advanced Server On-Disk Structure...............   E-19   %      F  Advanced Server Logical Namesr                	      viiin                 
         Indexn             Examples  H            2-1     Sample Installation Procedure-Part 1 .........    2-6  H            2-2     Sample Installation Procedure-Part 2 .........    2-8  H            2-3     Sample Installation Procedure-Part 3 .........    2-9  H            2-4     Sample Installation Procedure-Part 4 .........   2-11  H            2-5     Sample Installation Procedure-Part 5 .........   2-12  H            2-6     Sample Installation Procedure-Part 6 .........   2-13  H            2-7     Sample Installation Procedure-Part 7 .........   2-13           FiguresG  H            E-1     On-Disk Structure Diagram ....................   E-19           Tables  H            1-1     Preinstallation Checklist ....................   1-11  H            3-1     Advanced Server Configuration Prompts ........   3-17  H            3-2     Configuration Settings .......................   3-23  H            3-3     Server Roles in Each Type of Domain ..........   3-25  H            3-4     Methods for Changing Server Roles ............   3-27  H            3-5     OpenVMS Network Adapter Logicals .............   3-42  H            3-6     Undefined Adapter Messages ...................   3-44  H            4-1     License Server Configuration Prompts .........    4-4  H            5-1     PWCONVERT Qualifiers .........................   5-16  H            7-1     PRODUCT REMOVE Prompts .......................    7-5  H            A-1     Installation and Upgrade Checklist ...........    A-2  H            E-1     Files Installed for the Advanced Server ......    E-1  H            F-1     Advanced Server Logical Names ................    F-1  H                                                                       ix   o  a                      H         ________________________________________________________________  H                                                                  Preface      B               This guide explains how to install and configure theH               Compaq Advanced Server for OpenVMS software (also referredF               to as the "Advanced Server"). The installation procedure$               allows you to install:  -               o  The complete Advanced Server-  B               o  The standalone License Server, which may run on a:                  separate system in the local area network  G               o  The standalone external authentication software, which B                  may be used to provide external authentication onF                  OpenVMS Cluster member nodes that are not running the                   Advanced Server  @               o  Both the standalone License Server and external(                  authentication software           Intended Audienceo  C               This guide is written for OpenVMS system managers and.F               network administrators. It assumes that you are familiarH               with the following aspects of the Compaq OpenVMS operating               system:r  /               o  DIGITAL Command Language (DCL).  2               o  A text editor, such as EDT or EVE  9               o  POLYCENTER Software Installation utility.  F               This guide also assumes that you are familiar with basic'               Advanced Server concepts.e  H                                                                       xi .  .                  Document Structure   C            The following list can help you find information in this             guide:e  E            __________________________________________________________YE            Chapter_____Description___________________________________   C            Chapter 1   Describes prerequisites for the installationp!                        procedure..  <            Chapter 2   Describes the installation procedure.  D            Chapter 3   Describes the configuration procedure for the'                        Advanced Server.t  D            Chapter 4   Describes the configuration procedure for the1                        standalone License Server.   =            Chapter 5   Describes postinstallation tasks, such ?                        as running the Installation Verification.D                        Procedure and starting the server independent<                        of the installation and configuration"                        procedures.  B            Chapter 6   Describes how to set up Wide Area Networks.  B            Chapter 7   Describes how to remove Advanced Server for9                        OpenVMS software from your system.1  =            Appendix A  Provides a summary of installation and.=                        configuration tasks. You can photocopysB                        Appendix A and use it as a checklist as you'                        read this guide.t  D            Appendix B  Shows a sample installation and configuration9                        procedure for the Advanced Server.m  D            Appendix C  Shows a sample installation and configurationC                        procedure for the standalone License Server..  D            Appendix D  Shows a sample installation procedure for the=                        External Authentication software only.   B            Appendix E  Lists the files that are installed with the<                        Advanced Server for OpenVMS software.  >            Appendix F  Lists the logical names created for theE            ____________Advanced_Server.______________________________T        xii I  a                     Related Documents2  B               The following manuals provide more information about-               topics discussed in this guide:   H               __________________________________________________________H               Document______________Description_________________________  ?               Compaq Advanced       Provides an overview of and.G               Server for OpenVMS    introduction to the Advanced ServereF               Concepts and          software and associated networkingF               Planning Guide        concepts for system administrators1                                     and operatorsi  H               Compaq Advanced       Explains how to manage and customize@               Server for            the Advanced Server software               OpenVMS Server               Administrator's                Guide   H               Compaq Advanced       Provides command syntax descriptionsG               Server for OpenVMS    for all ADMINISTER commands and NETr7               Commands Reference    command equivalentsA               Manual  @               Compaq Advanced       Describes the License ServerG               Server for OpenVMS    software and how to manage Advanced 3               Guide to Managing     Server licenses.               Advanced Server3H               Licenses__________________________________________________  B               The following table lists related OpenVMS documents:                          H                                                                     xiii .  .          E            __________________________________________________________ E            OpenVMS_Document___________Description____________________7  E            OpenVMS Version 7.2        Describes the new features and  C            New Features Manual and    related release notes of the  D            Release Notes Manual.      OpenVMS Alpha system software.  B            OpenVMS Alpha Version 7.2  Describes how to install the=            Upgrade and Installation   OpenVMS system software             Manual.  C            OpenVMS System Manager's   A task-oriented guide (in twoeE            Manual                     volumes) to managing an OpenVMSaE                                       system; describes how to set up.B                                       the required system services  ?            OpenVMS System Management  A reference guide (in twoa?            Utilities Reference        volumes) to the utilities.@            Manual                     and tools used in managing7                                       an OpenVMS system   E            OpenVMS License            Explains how to load and manage3C            Management Utility Manual  license Product Authorization 1                                       Keys (PAKs).  =            OpenVMS Guide to Extended  Describes Extended FileA@            File Specifications        Specifications on OpenVMS,A                                       including how to set up and B                                       enable the ODS-5 file system  @            OpenVMS Guide to System    Describes OpenVMS securityD            Security                   features, including procedures;                                       for enabling externaln4                                       authentication  ?            OpenVMS Connectivity       Contains COM for OpenVMS,.C            Developer's Guide          OpenVMS Registry, and OpenVMS 8                                       Events information  >            Compaq C Run-Time Library  Describes utilities thatB            Utilities Reference        help you manage localization<            Manual                     and time zone data for<                                       international softwareE            ___________________________applications___________________i  @            For additional information about the OpenVMS productsD            and services, access the following OpenVMS World Wide Web            address:   )            http://www.openvms.compaq.com/.        xiv                          Reader's Commentsr  G               Compaq welcomes your comments on this manual. Please send <               comments to either of the following addresses:  /               Internet    openvmsdoc@compaq.comc  5               Mail        Compaq Computer Corporatione>                           OSSG Documentation Group, ZKO3-4/U08,                           110 Spit Brook Rd./                           Nashua, NH 03062-2698   -         How To Order Additional Documentation   ?               Use the following World Wide Web address 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.           Conventions.  G               The following conventions are used in the Advanced Servere                documentation set:  H               __________________________________________________________H               Convention____Meaning_____________________________________  B               Advanced      Advanced Server refers to the Advanced;               Server        Server for OpenVMS file server..  D               Italic        The use of italic text indicates a placeE                             holder for information or parameters thatcA                             you must provide. For example, if theeE                             procedure asks you to type file name, you.@                             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, and3/                             the system display..  C               Note          The use of Note provides information of./                             special importance.u  H                                                                       xv .  .          E            __________________________________________________________.E            Convention____Meaning_____________________________________t  C            Caution       The use of Caution provides information to.=                          avoid damaging software or hardware.   E            Warning       The use of Warning provides information that.9                          is essential to people's safety.h  D             . . .        A horizontal ellipsis following an entry inE                          a command line indicates that the entry or aeA                          similar entry can be repeated any numberV?                          of times. An ellipsis following a file C                          name indicates that additional parameters,l?                          values, or information can be entered.5  D                .         A vertical ellipsis in an example indicates8                .         that not all the data is shown.                .  @            Ctrl/x        While you hold down the Ctrl key, pressA                          another key or a pointing device button.   @            Return or     Return or Enter in text indicates where=            Enter         you should press the Return or Enter @                          key to execute a command or terminate a@                          sequence. This key is labeled Return or;                          Enter, depending on your keyboard..  >            <Tab>         In examples, a key name enclosed in a>                          box indicates that you press a key onB                          the keyboard. (In text, a key name is not,                          enclosed in a box.)  C                          In the HTML version of this document, thiscD                          convention appears as brackets, rather than                          a box.4  D            PF1 x         A sequence such as PF1 x indicates that youE                          must first press and release the key labeled C                          PF1 and then press and release another key E            ______________or_a_pointing_device_button.________________               xvi i  O                  H                                                                        1H         ________________________________________________________________  H                  Before You Install Advanced Server for OpenVMS Software      G               This chapter describes the hardware and software you must1H               have and the tasks you need to complete before you install7               the Advanced Server for OpenVMS software.   >               This chapter consists of the following sections:  D               o  Section 1.1, About the Advanced Server Software Kit  :               o  Section 1.2, Installing DECprint Software  -               o  Section 1.3, About Licensingi  ;               o  Section 1.4, About External Authentication   5               o  Section 1.5, About the Release Notes   >               o  Section 1.6, Using the Installation Checklist  B               o  Section 1.7, Requirements for Installing Advanced,                  Server for OpenVMS Software  3               o  Section 1.8, Preinstallation Tasks7  '               o  Section 1.9, Next Step.  2         1.1 About the Advanced Server Software Kit  G               The Advanced Server for OpenVMS kit contains the software.D               required to run the following server software options:  E               o  The complete Advanced Server software, including theeD                  License Server and external authentication software  >               o  The Advanced Server standalone License Server  @               o  The standalone external authentication software  F               o  Both the standalone License Server and the standalone1                  external authentication software   H              Before You Install Advanced Server for OpenVMS Software 1-1           <      Before You Install Advanced Server for OpenVMS Software/      1.1 About the Advanced Server Software Kite        1.1.1 About VAX Systems  ?            The Advanced Server for OpenVMS product is supported @            on OpenVMS Alpha systems only. You cannot install the>            Advanced Server for OpenVMS software on OpenVMS VAXB            systems. On VAX systems, you should continue to use theE            current PATHWORKS server software. If you have not alreadya>            done so, upgrade to PATHWORKS for OpenVMS (Advanced*            Server), Version 6.0C or later.  C            In mixed-architecture OpenVMS Clusters with the Advanced ;            Server for OpenVMS running on Alpha members, VAX B            members can still use external authentication. For more>            information, see Section 5.7.1, Setting Up External.            Authentication in OpenVMS Clusters.  C               ________________________Note ________________________   >               You cannot run multiple versions of the Advanced=               Server for OpenVMS or the PATHWORKS for OpenVMS.4               (Advanced Server) in the same cluster.  C               _____________________________________________________n  3      1.1.2 Upgrading to Advanced Server for OpenVMS   D            The Advanced Server for OpenVMS software may be installedA            and run only on OpenVMS Version 7.2-1 and higher AlphatA            systems. Therefore, it may be necessary to upgrade theC;            operating system as well as the server software.n  B            If the Advanced Server for OpenVMS Version 7.2 or laterD            is already installed, the installation and upgrade do not+            require an intermediate upgrade..  E            If PATHWORKS V6 for OpenVMS (Advanced Server) is currently.>            installed, ensure that it is Version 6.0C or later.A            Otherwise, upgrade to the current release of PATHWORKS B            V6 for OpenVMS (Advanced Server) before continuing. TheD            Advanced Server configuration procedure (PWRK$CONFIG.COM)E            automatically converts the PATHWORKS for OpenVMS (Advanced E            Server) data files to formats compatible with the AdvancedE9            Server for OpenVMS, as described in Chapter 3.1    @      1-2 Before You Install Advanced Server for OpenVMS Software F         H                  Before You Install Advanced Server for OpenVMS SoftwareH                               1.1 About the Advanced Server Software Kit  D               If PATHWORKS V5 for OpenVMS (LAN Manager) is currentlyC               installed, there is no direct upgrade to the AdvancedaD               Server for OpenVMS. If you want to retain the existingF               user, group, share, and security objects, you must firstA               upgrade to PATHWORKS for OpenVMS (Advanced Server),tC               Version 6.0C or later. For more information, refer to F               the Compaq PATHWORKS for OpenVMS Server Migration Guide.  C               For systems running the PATHWORKS V5 for OpenVMS (LANeH               Manager) file server on OpenVMS Alpha Version 6.2 systems,=               Compaq recommends the following migration path:   F               1. Upgrade the Version 5 file server to PATHWORKS V6 forB                  OpenVMS (Advanced Server), Version 6.0C or later.  F               2. Upgrade the operating system to OpenVMS Version 7.2-1                  or higher.   E               3. Upgrade the Version 6 file server to Advanced Serverw"                  V7.3 for OpenVMS.  C               Refer to the appropriate Software Product DescriptionqH               (SPD) for information about the OpenVMS versions supportedC               by each version of PATHWORKS for OpenVMS and Advancedr!               Server for OpenVMS.   A         1.1.2.1 LANMAN.INI Parameters Migrate to OpenVMS Registrye  D               Previous versions of the server software (for example,E               PATHWORKS for OpenVMS) use the LANMAN.INI file to store G               server parameters. The Advanced Server for OpenVMS storesfH               these parameters in the OpenVMS Registry, which is similar)               to the Windows NT Registry._  A               If you are upgrading a system from PATHWORKS V6 for_C               OpenVMS (Advanced Server) to Advanced Server V7.3 foreB               OpenVMS, the parameters and settings in the existingF               LANMAN.INI file are migrated to registry parameters whenE               you run the PWRK$CONFIG.COM configuration procedure for D               the first time. For more information, see Section 3.2,F               Migrating LANMAN.INI Parameters to the OpenVMS Registry.        H              Before You Install Advanced Server for OpenVMS Software 1-3           <      Before You Install Advanced Server for OpenVMS Software/      1.1 About the Advanced Server Software Kiti  '      1.1.2.2 Upgrading OpenVMS Clustersn  A            You can install the Advanced Server for OpenVMS on any E            OpenVMS Cluster member running OpenVMS Alpha Version 7.2-1 A            or higher. However, if PATHWORKS for OpenVMS (Advanced >            Server) or Advanced Server for OpenVMS is currentlyB            running on any cluster member, it must be stopped priorD            to installation. If the cluster members that will run theB            Advanced Server for OpenVMS share a common system disk,B            the installation can be performed on any cluster memberD            that shares the system disk. If cluster members that willB            run the Advanced Server for OpenVMS use separate systemA            disks, install the Advanced Server for OpenVMS on eacha            system.  B            If the OpenVMS Cluster contains other system disks (forD            example, to support VAX systems in the cluster or systemsB            running earlier versions of OpenVMS Alpha), these disksA            might have older versions of the PATHWORKS for OpenVMS A            (Advanced Server) installed on them. If so, remove the A            older versions to prevent accidental startup while the @            Advanced Server for OpenVMS is running on the OpenVMS>            Alpha Version 7.2-1 or later systems. To remove theC            PATHWORKS for OpenVMS (Advanced Server) product, execute_@            the command procedure SYS$UPDATE:PWRK$DEINSTAL from a>            cluster member that uses the system disk from which>            PATHWORKS is to be removed. For more information onA            using PWRK$DEINSTAL.COM, refer to the Compaq PATHWORKSS@            for OpenVMS (Advanced Server) Server Installation and            Configuration Guide.i  C            Note, however, if you are using external authentication, D            Compaq recommends that you set up external authentication>            software on all the nodes in the cluster. To set upC            external authentication support on nodes that do not run C            Compaq OpenVMS file servers, see Section 5.7, Setting Up #            External Authentication.d                @      1-4 Before You Install Advanced Server for OpenVMS Software           H                  Before You Install Advanced Server for OpenVMS SoftwareH                                         1.2 Installing DECprint Software  (         1.2 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 PostScripthH               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.  C               If you plan to use DECprint Supervisor for OpenVMS ontG               your system, Compaq recommends that you install it beforeeH               installing the Advanced Server. You must reboot the systemE               after installing the DECprint software. You can performhH               the reboot as part of the DECprint Supervisor installationE               procedure, or after you install the Advanced Server butf&               before you configure it.           1.3 About Licensinga  H               The following sections describe the licensing software and?               the license requirements for the Advanced Server.t  "         1.3.1 License Requirements  F               The Advanced Server requires that clients accessing fileF               and print services be appropriately licensed. To conformE               to this requirement, one of the following must be true:   F               o  The client must acquire a client-based license beforeE                  connecting to an Advanced Server for the first time.i  E               o  The Advanced Server must have a server-based license G                  available to assign to an unlicensed client attempting.8                  to use services of the Advanced Server.  D               In both cases, the license required to access AdvancedI               Server services is a Client Access license: PWLMXXXCA07.03.   @               If you are upgrading from PATHWORKS V6 for OpenVMSG               (Advanced Server) or Advanced Server for OpenVMS, Version H               7.2, refer to the Compaq Advanced Server for OpenVMS GuideH               to Managing Advanced Server Licenses for information about(               upgrading client licenses.    H              Before You Install Advanced Server for OpenVMS Software 1-5 e         <      Before You Install Advanced Server for OpenVMS Software      1.3 About Licensing  #      1.3.2 About the License Servery  E            The Advanced Server License Server is an optional softwareuC            program that you can run on your OpenVMS system to grantz            licenses to clients.   /            The License Server can be installed:   D            o  With the file server (automatically included with your'               file server installation)p  E            o  Separately from the file server (called the "standalonel               License Server")  B            In either case, you can configure the License Server to@            support clients using any of the following protocols:              o  DECnet  #            o  LAN Manager (NetBEUI)o              o  TCP/IP  C            Compaq recommends that you install the License Server oncC            a designated OpenVMS system without the Advanced Server. D            The Advanced Server for OpenVMS kit allows you to installA            the standalone License Server separately from the file0@            server. Alternatively, you can run the License Server@            on an OpenVMS Cluster with the Advanced Server, whereE            cluster failover provides increased availability. (Clusterv@            failover also provides increased availability for the(            Advanced Server file server.)  E            Each LAN needs only one active License Server. The licenseo>            product authorization keys (PAKs) must be loaded onA            the system that runs the License Server. In an OpenVMS_A            Cluster, the PAKs must be loaded into a shared license_            database.  E            __________________________________________________________h            For more information E            about_._._.___________Refer_to_._._.______________________h  C            Loading licenses      OpenVMS License Management Utilityd'                                  Manual   D            Configuring the       Chapter 4, Configuring and Starting>            License Server        the Standalone License Server  @      1-6 Before You Install Advanced Server for OpenVMS Software           H                  Before You Install Advanced Server for OpenVMS SoftwareH                                                      1.3 About Licensing  H               __________________________________________________________"               For more informationH               about_._._.___________Refer_to_._._.______________________  F               Managing licenses     Compaq Advanced Server for OpenVMSE                                     Guide to Managing Advanced Server H               ______________________Licenses____________________________  )         1.4 About External Authentication_  ?               External authentication is an optional feature of_C               OpenVMS systems that allows system managers to set up C               user accounts for which login authentication is basedtB               on a security mechanism other than OpenVMS security.A               The Advanced Server takes advantage of this featurepD               by providing the ability to use the Advanced Server orE               Windows NT-compatible user authentication mechanisms tohH               authenticate OpenVMS user logins. This allows users to logF               in at the OpenVMS login prompt using the Advanced ServerE               user name and password, and provides automatic passwordeH               synchronization for user accounts. External authenticationB               may be required if you are using the COM for OpenVMS               product.  @               When you install the complete Advanced Server, theC               files required to support external authentication are A               automatically included in the installation process.t  @               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 caneE               install the standalone external authentication softwareeB               on that disk (without installing the Advanced ServerH               software). On VAX member nodes, you must copy the externalD               authentication files from an Alpha system on which theD               Advanced Server is installed to the VAX node. For moreE               information about enabling external authentication, see >               Section 5.7, Setting Up External Authentication.            H              Before You Install Advanced Server for OpenVMS Software 1-7 e  a      <      Before You Install Advanced Server for OpenVMS Software       1.5 About the Release Notes         1.5 About the Release Notes  =            The Advanced Server V7.3 for OpenVMS Release Notes B            document contains important information you should knowE            before you install the product. Compaq recommends that you C            read the release notes before starting the installation.a  >      1.5.1 How to Access the Release Notes Before Installation  <            If you want to print the release notes before the@            installation, do the following to extract the release             notes to a text file:  3            o  Load the installation kit on a drive.   B            o  Enter the following POLYCENTER Software InstallationB               utility command, where file_name.txt is the name youE               specify for the text file, and directory-path specifies4C               the disk and directory name for the source drive thatuE               holds the Advanced Server for OpenVMS kit (for example,a+               /SOURCE=DAD$100:[ASOVMS073]):7  G      $ PRODUCT EXTRACT RELEASE_NOTES ADVANCEDSERVER/FILE=file_name.txt-       _$ /SOURCE=directory-path  B               If you do not specify a file name, the release notesE               are written to a file called DEFAULT.PCSI$RELEASE_NOTES A               in the current directory. If you do not specify the D               source qualifier, the POLYCENTER Software InstallationB               utility searches the location defined by the logicalD               name PCSI$SOURCE. If not defined, the utility searches,               the current default directory.  A      1.5.2 How to Access the Release Notes After the Installationt  A            If you want to see the release notes after the instal-SC            lation completes, you can read them on line or print thef6            file from SYS$HELP:ASOVMS073.RELEASE_NOTES.  )      1.6 Using the Installation Checklist   C            Appendix A, Installation and Upgrade Checklist, providest?            an installation and configuration checklist. You cansE            photocopy the checklist and use it to track the completion C            of the installation and configuration tasks described in             this guide.  @      1-8 Before You Install Advanced Server for OpenVMS Software o  h      H                  Before You Install Advanced Server for OpenVMS SoftwareH     1.7 Requirements for Installing Advanced Server for OpenVMS Software  C         1.7 Requirements for Installing Advanced Server for OpenVMSe             Software  G               The following sections describe the hardware and softwareaC               you need when you install Advanced Server for OpenVMSi               software.i  #         1.7.1 Hardware RequirementsU  E               All Alpha processors supported by the OpenVMS Operating E               System V7.2-1 are also supported by the Advanced Server E               for OpenVMS. For the latest information on the hardwarerE               that the server supports, refer to the Software Productv                Description (SPD).  #         1.7.2 Software Requirements_  B               To install Advanced Server for OpenVMS software suc-F               cessfully, you must have the following software properly6               installed and configured on your system:  7               o  OpenVMS Alpha Version 7.2-1 or higher.   H                  The Advanced Server runs on OpenVMS Alpha Version 7.2-1C                  (or higher) systems only, and requires the OpenVMSoB                  registry services. For more information about theH                  OpenVMS Registry, refer to the OpenVMS System Manager'sE                  Manual or the OpenVMS Connectivity Developer's Guide @                  (included on the OpenVMS Documentation CD-ROM).  B               o  The appropriate transport software to support theG                  network protocols used by other servers and by networkeA                  clients, including one or more of the following:m  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-cB                     party TCP/IP product can be used to provide IPE                     support. Refer to the Advanced Server for OpenVMSoD                     Software Product Description (SPD) for a list of.                     supported TCP/IP products.  H              Before You Install Advanced Server for OpenVMS Software 1-9    u      <      Before You Install Advanced Server for OpenVMS SoftwareI      1.7 Requirements for Installing Advanced Server for OpenVMS Softwareo  $      1.7.3 Supported Client Software  D            Advanced Server for OpenVMS supports connections from the&            following types of clients:              o  Windows NT V4.0               o  Windows 2000  '            o  Windows 2000 Professional               o  Windows 98              o  Windows 95  $            o  Windows for Workgroups              o  PATHWORKS 32        1.7.4 Memory Requirements  D            The minimum amount of physical memory required to run the=            Advanced Server on OpenVMS Alpha systems is 64 MB.         1.8 Preinstallation Tasks  D            Use the checklist in Table 1-1 to complete the preinstal-A            lation tasks that are described later in this section.                                   A      1-10 Before You Install Advanced Server for OpenVMS Software            H                  Before You Install Advanced Server for OpenVMS SoftwareH                                                1.8 Preinstallation Tasks  H               Table_1-1_Preinstallation_Checklist_______________________  /               <   >1.   Check the part listing.N  H               <   >2.   Make sure that the network hardware is installed&                         and connected.  H               <   >3.   Log in to the SYSTEM account (or another accountB                         that has all privileges enabled to run the0                         installation procedure).  ?               <   >4.   Make sure that the required software is,"                         installed.  :               <   >5.   Start the OpenVMS Registry Server.  /               <   >6.   Read the release notes.C  0               <   >7.   Check system parameters.  1               <   >8.   Back up the system disks..  G               <   >9.   Make sure that you have adequate disk space for %                         installation.   0               <   >10.  Check the queue manager.  :               <   >11.  Check the time zone configuration.  H               <   >12.  Make sure that DECnet or DECnet-Plus is running,H                         if you are planning to use the DECnet transport.  D               <   >13.  Make sure that TCP/IP is running, if you are=                         planning to use the TCP/IP transport.o  G               <   >14.  Check for existing Compaq OpenVMS server imagesc"                         and files.  G               <   >15.  Check the OpenVMS Cluster configuration, if youeH               __________are_installing_the_Advanced_Server_on_a_cluster.  E               Perform the following steps before you install Advancedd*               Server for OpenVMS software.  F                 ________________________Note  ________________________  ;                 All the steps except the last apply to bothnA                 standalone and cluster Advanced Servers. The last D                 step delineates what needs to be done for installing1                 the Advanced Server on a cluster.l  E                 _____________________________________________________t  H             Before You Install Advanced Server for OpenVMS Software 1-11           <      Before You Install Advanced Server for OpenVMS Software      1.8 Preinstallation Tasks  )      1.8.1 Step 1: Check the Part Listingv  B            The software part listing specifies the contents of theB            kit you receive. Check the contents of your kit against@            that information. If parts are missing or your kit is7            damaged, contact your Compaq representative.   -      1.8.2 Step 2: Check the Network Hardwarei  D            Advanced Server for OpenVMS runs on OpenVMS Alpha systemsA            that meet the software requirements. The PC local area "            network (LAN) requires:  D            o  A supported network controller board in the server and               in each client  A            o  The cables to connect each client and server to thee               networka  /      1.8.3 Step 3: Log In to the SYSTEM Accountl  C            Before you install Advanced Server for OpenVMS software,hD            log in to the SYSTEM account, or another account that hasD            all privileges enabled to run the installation procedure.  +            To log in to the SYSTEM account:   4            1. At the user name prompt, enter SYSTEM:                 Username: SYSTEM  ?            2. At the Password prompt, enter the password to thei;               SYSTEM account. The password you enter is nota               displayed.  .      1.8.4 Step 4: Check the Required Software  9            Advanced Server for OpenVMS software requires:g  B            o  The OpenVMS Alpha operating system, Version 7.2-1 or               higher.e  C            o  The DECnet network transport, if you are going to use C               the DECnet transport, the mail server, or the Licenseo!               Server over DECnet.D  E            o  The TCP/IP transport, if you are planning to use TCP/IPfD               for cluster or network communication. If you are goingB               to use the TCP/IP transport, you must have installed  A      1-12 Before You Install Advanced Server for OpenVMS Software  t  e      H                  Before You Install Advanced Server for OpenVMS SoftwareH                                                1.8 Preinstallation Tasks  H                  and configured a TCP/IP transport product, as describedG                  in the Advanced Server V7.3 for OpenVMS Release Notes.t  7         1.8.5 Step 5: Start the OpenVMS Registry Serverv  F               The OpenVMS Registry is installed as part of the OpenVMSB               installation. To provide registry services, you must+               complete the following steps:   E               1. Define the SYS$REGISTRY logical to point to the diskbA                  location where the Registry Server files will be                   stored.  C                  For example, to store the registry files on device ?                  DKA100: in directory [SYS$REGISTRY], enter the #                  following command:   C                  $ DEFINE/SYSTEM SYS$REGISTRY DKA100:[SYS$REGISTRY]h  E                  In an OpenVMS Cluster, be sure to specify a disk andoD                  directory that is available to all cluster members.  +               2. Start the Registry Server.a  D                  Compaq recommends that you have the Registry ServerH                  started automatically with system startup. This ensuresB                  proper operation of any Advanced Server utilitiesC                  that require the registry (such as PWRK$REGUTL andrA                  the Configuration Manager). To have the Registryd@                  Server started automatically at system startup,?                  run the OpenVMS Registry Configuration utilityiC                  (SYS$MANAGER:REG$CONFIG) and make sure the REG$TO_ H                  BE_STARTED logical is set to TRUE. For more informationE                  about starting the OpenVMS Registry Server, refer tonC                  the OpenVMS System Manager's Manual or the OpenVMS H                  Connectivity Developer's Guide (included in the OpenVMS'                  Documentation CD-ROM).o  C                  If you need to start the Registry Server manually, -                  enter the following command:,  /                  $ @SYS$STARTUP:REG$STARTUP.COM   A               For complete information about managing the OpenVMSoD               Registry, refer to the OpenVMS System Manager's ManualH               or the OpenVMS Connectivity Developer's Guide (included in0               the OpenVMS Documentation CD-ROM).  H             Before You Install Advanced Server for OpenVMS Software 1-13    i      <      Before You Install Advanced Server for OpenVMS Software      1.8 Preinstallation Tasks  3      1.8.6 Step 6: Print and Read the Release Notes   E            If you have not already read the release notes, you shouldiA            do so before installing the software. If you choose toeD            back up the system, as recommended in Section 1.8.8, Step@            8: Back Up the System, you can read the release notesD            during the backup. For more information, see Section 1.5,#            About the Release Notes.s  *      1.8.7 Step 7: Check System Parameters  >            Most systems have adequate system resources readily?            available to include the Advanced Server for OpenVMS_B            software. However, make sure that the following OpenVMSA            system parameters are set properly. Make any necessary_C            changes to the MODPARAMS.DAT file, then run AUTOGEN, and B            reboot your system. You can delay this reboot until theD            first reboot required for backing up your system disks (aB            backup is recommended in Section 1.8.8, Step 8: Back Up            the System).e  D            Make sure all other software that will be running on your?            system is indeed running. Note that if the PATHWORKS ?            for OpenVMS (Advanced Server) or Advanced Server for_D            OpenVMS is already running, your system is likely to haveA            sufficient resources to support the new version of theo'            Advanced Server for OpenVMS.   C               ________________________Note ________________________   ;               If these parameters are not set properly, you @               cannot configure the server after you complete the%               installation procedure.e  C               _____________________________________________________u        1.8.7.1 GBLPAGES Parameterm  E            The Advanced Server for OpenVMS requires that the value of 9            the GBLPAGES parameter be at least 7500 pages.c  C            To ensure that your system has enough free global pages,dE            do the following while the Advanced Server is not running:e  "            1. Enter the following:  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")  A      1-14 Before You Install Advanced Server for OpenVMS Softwarew s         H                  Before You Install Advanced Server for OpenVMS SoftwareH                                                1.8 Preinstallation Tasks  G                  The value of the FREE_GBLPAGES parameter is displayed.                   For example:u                    143576V  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  %         1.8.7.2 GBLSECTIONS ParameterA  H               The Advanced Server for OpenVMS requires that the value of7               the GBLSECTIONS parameter be at least 75.m  G               If you are installing the standalone License Server only,r,               the value must be at least 50.  ?               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:g                    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 = 75e  %         1.8.7.3 PROCSECTCNT Parameter   H               If you are going to install the Advanced Server, the valueA               of the PROCSECTCNT parameter should be at least 40.i  G               If you are installing the standalone License Server only,m,               the value must be at least 32.  >               To ensure that the value of the system parameter&               PROCSECTCNT is adequate:  %               1. Enter the following:e  ;                  $ WRITE SYS$OUTPUT F$GETSYI("PROCSECTCNT")   H             Before You Install Advanced Server for OpenVMS Software 1-15 t  i      <      Before You Install Advanced Server for OpenVMS Software      1.8 Preinstallation Tasks  B               The value of the PROCSECTCNT parameter is displayed.               For example:                 20  A            2. If the value is less than required, edit the systemhE               parameters file SYS$SYSTEM:MODPARAMS.DAT and add a lineM'               similar to the following:C  "               MIN_PROCSECTCNT = 40        1.8.7.4 SCSNODE Parameter  A            The SCSNODE parameter must be defined as your system's E            computer name. If you are running DECnet, the SCSNODE name 6            should be the same as the DECnet node name.  A            The SCSNODE parameter's preinstallation status affectsh6            what happens after you install, as follows:  E            __________________________________________________________t            If SCSNODE    AndE            is_._._.______you_._._._____Then_the_server_._._._________u  6            Not defined   Do not        Does not start."                          define it  .            Already       Do not        Starts."            defined       define it  E            Not defined   Define it     Starts, but the OpenVMS systemrE                                        renames print and batch queues B                                        to include the new computer@                                        name. Therefore, you mustA                                        requeue any existing printa?                                        or batch jobs to the newi@                                        queues. You may also haveE                                        to rebuild the queue database. ?                                        For information on these ?                                        system management tasks,oB                                        refer to the OpenVMS SystemE            ____________________________Manager's_Manual._____________s  C            To check whether the system parameter SCSNODE is definedn>            as your system's computer name, enter the following)            commands at the system prompt:   *            $ SCSNODE = F$GETSYI("SCSNODE")             $ SHOW SYMBOL SCSNODE  A      1-16 Before You Install Advanced Server for OpenVMS Software            H                  Before You Install Advanced Server for OpenVMS SoftwareH                                                1.8 Preinstallation Tasks  7               As a result, one of the following occurs:   G               o  If SCSNODE is defined, the computer name is displayed.uG                  For example, if your system's computer name is SPEEDY:e  &                  $ SHOW SYMBOL SCSNODE                     SPEEDY  D               o  If SCSNODE is not defined, the computer name is not                  displayed.   O               If SCSNODE is not defined, edit the file SYS$SYSTEM:MODPARAMS.DAT E               and define the parameter. For example, if your system'seH               computer name is SPEEDY, edit the file so that it contains!               the following line:e                  SCSNODE = "SPEEDY"  E               If you edit the file SYS$SYSTEM:MODPARAMS.DAT, you mustoF               run the OpenVMS command procedure AUTOGEN and reboot theF               system either now or at some time before configuring the"               server. For example:  =               $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK   C               For more information about using the AUTOGEN utility, H               refer to the OpenVMS System Management Utilities Reference               Manual.i  (         1.8.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.   3         1.8.9 Step 9: Check Disk Space Requirementse  A               To determine the number of disk blocks required forAF               your installation, refer to the Advanced Server V7.3 forG               OpenVMS Release Notes. To check the number of free blockso(               on the system disk, enter:  )               $ SHOW DEVICE SYS$SYSDEVICE   H             Before You Install Advanced Server for OpenVMS Software 1-17           <      Before You Install Advanced Server for OpenVMS Software      1.8 Preinstallation Tasks  C            The OpenVMS system displays information about the system B            disk, including the number of free blocks. For example:  C            Device     Device     Error    Volume    Free  Trans MntkC             Name      Status     Count     Label   Blocks Count Cnt C            DUA0:      Mounted        0    AXP072   724856   280   1f  ,      1.8.10 Step 10: Check the Queue Manager  @            It is not necessary to have the queue manager running?            during installation, but it must be running when you E            configure the server. You can enter the SHOW QUEUE/MANAGER A            command to check whether the queue manager is running:               $ SHOW QUEUE/MANAGERr  >            If the queue manager is running, the OpenVMS system7            displays a message similar to the following:a  @            Queue manager SYS$QUEUE_MANAGER, running, on SPEEDY::  ?            If the queue manager is not running, you can use the )            following command to start it:                $ START/QUEUE/MANAGER  E            For more information about the OpenVMS DCL commands, refer.)            to the OpenVMS DCL Dictionary.e  ,      1.8.11 Step 11: Check Time Zone and TDF  >            The Advanced Server's internal time management usesB            Greenwich Mean Time (GMT). To synchronize with a commonC            time format among computers in different time zones, the C            OpenVMS Coordinated Universal Time (UTC) system servicesiE            may be used. The Advanced Server system implements default C            date/time support using the UTC standard. UTC is similarnA            to GMT. Under the UTC time standard, zero hours occurs C            when the Greenwich Meridian is at midnight. Unlike localt?            time, which can go backward and forward depending on 7            daylight savings time, UTC always increases.   C            Local times can be up to 12 hours behind GMT or 13 hourso            ahead of it.   A      1-18 Before You Install Advanced Server for OpenVMS Software            H                  Before You Install Advanced Server for OpenVMS SoftwareH                                                1.8 Preinstallation Tasks  G               Because UTC is independent of time zones, you can use UTCsG               around the world; for example, it is 2:00 UTC at the same.G               moment in Paris as well as in Tokyo. You can examine datatE               that is time-stamped with UTC values in Paris and Tokyo E               without complicated conversions to deal with local time                zones.  A               To properly represent the time in your local server                environment:  F               1. Determine the time differential factor (TDF) for yourH                  system, which associates each local time zone with UTC.  D                  The TDF is the difference between your local systemC                  time and the Coordinated Universal Time (UTC). TherF                  difference is expressed in hours and minutes. The TDFE                  changes each time your local system time undergoes a F                  change, such as when it changes from daylight savingsH                  time to standard time; the UTC, on the other hand, does                  not change.  C                  The Americas have negative offsets from UTC, while B                  Europe, Africa, Asia, and Australia have positiveD                  offsets. For example, the TDF for New York, EasternG                  Standard Time, is -5:00. The TDF for eastern AustraliaMG                  is +10:00. The TDF for a region that observes daylight F                  savings is typically +1:00 from the standard time forE                  the region. For example, the TDF for New York during E                  daylight savings time is -4:00. To determine the TDFMB                  for your system, refer to the map included in the1                  OpenVMS System Manager's Manual.t  E               2. Set the time zone and time differential factor (TDF)iG                  settings on your system by running the OpenVMS commandgF                  procedure UTC$TIME_SETUP.COM. (This command procedure@                  defines the time-related logicals needed by theE                  Advanced Server.) From the SYSTEM account, enter thea:                  following command to begin the procedure:  2                  $ @SYS$MANAGER:UTC$TIME_SETUP.COM  F                  The procedure asks you which time parameters you wantE                  to configure. If your system resides in an area that D                  observes daylight savings time, the system time andA                  TDF must be modified appropriately when daylightdE                  savings starts and ends. To have these modifications   H             Before You Install Advanced Server for OpenVMS Software 1-19 P  a      <      Before You Install Advanced Server for OpenVMS Software      1.8 Preinstallation Tasks  >               done automatically twice a year, you can use theB               SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM command procedure.  D               When you elect to change the time zone or TDF setting,D               or both, the changes are also made clusterwide if your8               server participates in an OpenVMS Cluster.  ?               If you change any time zone information, you must <               restart the server for the time to be properly               represented.  @            For more information on running the command procedureD            and resetting the time zone and TDF, refer to the OpenVMS#            System Manager's Manual.   (      1.8.12 Step 12: Check DECnet Status  =            If you plan to use the DECnet transport, it is notaA            necessary to have DECnet or DECnet-Plus running duringsC            the installation; however, DECnet or DECnet-Plus must beRE            running on the system before you can configure the server.t  ?            To see whether DECnet is running on the system where A            you are planning to install the server software, entera@            the appropriate command depending on whether you haveD            installed DECnet (Phase IV), or DECnet-Plus, as described%            in the following sections.t  /      1.8.12.1 Checking DECnet (Phase IV) Status   ?            To check DECnet status, enter the following command:   "            $ MCR NCP SHOW EXECUTOR  =            o  If DECnet is running, the SHOW EXECUTOR display &               resembles the following:  >               Node Volatile Summary as of  1-SEP-2000 12:16:36  ,               Executor node = 9.000 (BRUTUS)  "               State           = on;               Identification  = DECnet for OpenVMS AXP V7.2t  C            o  If DECnet is not running, enter the following commando               to start it:  %               $ @SYS$MANAGER:STARTNET   A      1-20 Before You Install Advanced Server for OpenVMS Software            H                  Before You Install Advanced Server for OpenVMS SoftwareH                                                1.8 Preinstallation Tasks  ,         1.8.12.2 Checking DECnet-Plus Status  G               To check DECnet-Plus status, enter the following command:   /               $ SHOW LOGICAL NET$STARTUP_STATUSt  C               o  If DECnet-Plus is running, the system displays thea                  following:   H                  "NET$STARTUP_STATUS" = "RUNNING-ALL" (LNM$SYSTEM_TABLE)  C               o  If DECnet-Plus is not running, enter the followingc%                  command to start it:i  +                  $ @SYS$STARTUP:NET$STARTUPm  ?               For more information, refer to the DECnet product                documentation.  +         1.8.13 Step 13: Check TCP/IP Status   H               If you are planning to use the TCP/IP transport, make sureF               that TCP/IP is running and that the PWIP driver has beenG               loaded. The procedure depends on which TCP/IP product youeG               use. For specific information, refer to the documentationn/               for the TCP/IP product installed..  ?               For example, if TCP/IP Services for OpenVMS V5 isuB               installed, you can start the PWIP driver manually by-               entering the following command:b  3               $ @SYS$STARTUP:TCPIP$PWIP_STARTUP.COM   B               Alternatively, you can configure TCP/IP Services forA               OpenVMS to automatically start the PWIP driver whentB               TCP/IP is started, using the configuration procedure               TCPIP$CONFIG.COM.   A               After the installation is complete, you can use the D               Configuration Manager to configure the Advanced ServerC               for OpenVMS to use TCP/IP. You can do this during the_H               configuration procedure (PWRK$CONFIG) or after configuringC               the server. In the former case, PWRK$CONFIG gives you F               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.e  H             Before You Install Advanced Server for OpenVMS Software 1-21 c         <      Before You Install Advanced Server for OpenVMS Software      1.8 Preinstallation Tasks  A      1.8.14 Step 14: Check for Existing OpenVMS Server Images ando             Files               Make sure that:  ?            1. No Advanced Server (PATHWORKS Advanced Server andrB               Advanced Server for OpenVMS) images, or PATHWORKS V5B               for OpenVMS (LAN Manager) images, are running on theC               local system. No PATHWORKS OpenVMS servers or earlierTC               versions of the Advanced Server for OpenVMS should be .               running anywhere in the cluster.  A            2. No files from a PATHWORKS for OpenVMS (NetWare) kit @               are on the system disk. If such files are present,A               use SYS$UPDATE:PWVN$DEINSTAL.COM (included with the B               PATHWORKS for OpenVMS (NetWare) kit) to remove those               files.  <            3. No files from any PATHWORKS Advanced Server orE               Advanced Server for OpenVMS kit are in the SYS$SPECIFICe               directory tree.n  C            The POLYCENTER Software installation utility will detect >            if any of these conditions exist, and if the above-C            mentioned images or files are found, it will notify you.   8      1.8.15 Step 15: Check OpenVMS Cluster Configuration  D            You can run the Advanced Server on multiple OpenVMS Alpha9            Cluster members. To do so, follow these steps:   B            1. If you plan to use the TCP/IP transport, ensure thatC               all cluster members on which the Advanced Server willt0               run are in the same TCP/IP subnet.  B            2. If a PATHWORKS for OpenVMS, PATHWORKS V5 for OpenVMS?               (LAN Manager), or earlier version of the AdvancedCB               Server for OpenVMS is running on any cluster member,B               stop that server. For more information about earlier>               versions of the Advanced Server in clusters, see:               Section 1.1.2.2, Upgrading OpenVMS Clusters.  B               Note that to provide external authentication, Compaq@               recommends that you set up external authenticationA               software on all the nodes in the cluster. To set upSB               external authentication support on nodes that do not?               run Compaq OpenVMS file servers, see Section 5.7,r1               Setting Up External Authentication.   A      1-22 Before You Install Advanced Server for OpenVMS SoftwareS C  p      H                  Before You Install Advanced Server for OpenVMS SoftwareH                                                1.8 Preinstallation Tasks  @               3. On each system on which you want to install theF                  Advanced Server, complete the tasks described in this                  chapter.m  E                  In a cluster configuration that uses multiple system F                  disks, the OpenVMS Registry Server must be configuredF                  to use a common registry database. See Section 1.8.5,D                  Step 5: Start the OpenVMS Registry Server, for more                  information.   F                  On each cluster member that you want to use as a fileC                  and print server, you will run the Advanced Server.C                  configuration command procedure (PWRK$CONFIG.COM),DD                  as explained in Chapter 3, Configuring the AdvancedH                  Server. This ensures that each node has its appropriateG                  parameters set and enough resources to run the server.s  F               4. All cluster members that will run the Advanced Server%                  must share a common:   ?                  o  System user Authorization File (SYSUAF.DAT)   3                  o  Rightlist file (RIGHTSLIST.DAT)   E                  o  OpenVMS Registry datbase location (SYS$REGISTRY:)   N                  o  Advanced Server data directory location (PWRK$COMMONROOT:)  G               When installing the Advanced Server on an OpenVMS ClusteruD               member, if the following two conditions apply, you areE               forced to shut down the server and, possibly, to reboots-               the systems running the server:f  E               1. Advanced Servers are installed on two or more systems%                  disks in the cluster   A               2. The Advanced Server is already running on one or C                  more cluster members that are booted from a system E                  disk other than the one on which the installation is                   occuringO          H             Before You Install Advanced Server for OpenVMS Software 1-23           <      Before You Install Advanced Server for OpenVMS Software      1.9 Next Step        1.9 Next Step  @            To install the Advanced Server, proceed to Chapter 2,;            Installing Advanced Server for OpenVMS Software.f                                                                                  A      1-24 Before You Install Advanced Server for OpenVMS SoftwareS E                     H                                                                        2H         ________________________________________________________________  H                          Installing Advanced Server for OpenVMS Software      @               This chapter describes how to install the AdvancedG               Server for OpenVMS software using the POLYCENTER SoftwareiH               Installation (PCSI) utility. You must follow the procedureH               outlined here regardless of whether you are upgrading fromG               a previous version of the server or installing the serverr!               for the first time.e  G               For information about how to install the product directly F               from the OpenVMS Alpha CD-ROM menu, refer to the OpenVMS@               Alpha Version 7.2 Upgrade and Installation Manual.  H               For information about the POLYCENTER Software InstallationD               utility, refer to the OpenVMS System Manager's Manual.  D               Before you begin the installation procedure, make sureF               that you have completed the preinstallation tasks listedB               in Chapter 1, Before You Install Advanced Server for               OpenVMS Software.O  >               This chapter consists of the following sections:  8               o  Section 2.1, The Installation Procedure  C               o  Section 2.2, Troubleshooting Installation Problemsk  (               o  Section 2.3, Next Steps  &         2.1 The Installation Procedure  G               The POLYCENTER Software Installation utility performs ther               following:  G               o  Determines whether the installation is being done on aeF                  VAX system or an Alpha system. If it is a VAX system,F                  the installation terminates. The Advanced Server runs'                  on Alpha systems only.S  H                      Installing Advanced Server for OpenVMS Software 2-1 e  S      4      Installing Advanced Server for OpenVMS Software#      2.1 The Installation Procedurec  @            o  Creates Advanced Server accounts on the system, if               necessary.  B            o  Copies the Advanced Server files in the installation%               kit to the target disk.X  B            o  Creates DECnet objects, if you are running DECnet or               DECnet-Plus.  E            o  Installs the OpenVMS DCL command definition file, whichnE               includes ADMINISTER commands and facilitates managementu%               of the Advanced Server.   B            o  Installs the Advanced Server logical name definition               file.A  %            o  Deletes obsolete files.   ;            o  Verifies that the software has been installediC               successfully. See Section 5.2, Verifying the AdvancedR@               Server Installation, for information on how to runB               the POLYCENTER Software Installation utility so that?               the procedure automatically runs the InstallationmC               Verification Procedure after installing the software.M  E            o  Detects whether a reboot is necessary, and requests one E               only if and when necessary. You are given the option ofGE               delaying a required reboot; for example, if you want to A               configure or change more settings before rebooting.e  6      2.1.1 Before You Start the Installation Procedure  B            Before you start the installation procedure, answer the            following questions:g  -            1. What is the product identifier?   B               The product identifier tells the POLYCENTER Software@               Installation utility which product to install. TheD               product identifier for the Advanced Server for OpenVMS-               software kit is ADVANCEDSERVER.   A            2. What is the name of the device on which you want to                mount the media?  >               The device name depends on the type of media andD               computer you have. For example, if you want to mount aB               CD-ROM on the CD-ROM drive of your AlphaStation 400,.               the device name might be DKA400.  8      2-2 Installing Advanced Server for OpenVMS Software u  t      H                          Installing Advanced Server for OpenVMS SoftwareH                                           2.1 The Installation Procedure  ,               3. Do you want to install the:  6                  o  Complete Advanced Server software?  ,                  o  The License Server only?  <                  o  The external authentication images only?  H                  o  Both the License Server and the external authentica-%                     tion images only?,  E                  You can install these components on any Alpha systemTH                  running OpenVMS Version 7.2-1 or higher. If you installE                  the complete Advanced Server software or the License E                  Server software, and PATHWORKS for OpenVMS (AdvancedcH                  Server) was previously installed, the server data filesH                  are automatically upgraded during server configuration,D                  as described in Chapter 3, Configuring the Advanced                  Server.  C                  If you choose not to install the complete Advanced,A                  Server software, you can choose one of the othersH                  options. If you choose to install the complete AdvancedA                  Server, you will not be given the other options.1  B                  If the system is designated to run the standaloneC                  License Server, you can install the License Server A                  software instead of the complete Advanced Server H                  software. Compaq recommends that you run the standaloneF                  License Server on a designated License Server system.D                  You can decide later (during configuration) whetherF                  to run the License Server. The License Server and theF                  external authentication images are installed with the7                  complete Advanced Server installation.d  F                  If you have installed the Advanced Server and enabledC                  external authentication in an OpenVMS Cluster thatiG                  includes Alpha systems running OpenVMS 7.2-1 or later,$G                  and if these systems boot from a system disk that willmH                  not have the Advanced Server installed, you can installC                  the standalone external authentication software onsE                  that system disk. For more information on setting updE                  external authentication, see Section 5.7, Setting Upi)                  External Authentication.A  A               4. What is the User Identification Code (UIC) groupo                  number?  H                      Installing Advanced Server for OpenVMS Software 2-3 m  c      4      Installing Advanced Server for OpenVMS Software#      2.1 The Installation Procedured  @               The Advanced Server installation procedure createsD               the OpenVMS user accounts PWRK$DEFAULT and PWRK$GUEST,A               if they do not already exist. The default selection C               displayed in the installation dialog is determined as                follows:  E               _______________________________________________________ E               If_._._._________________The_default_is_._._.__________d  E               You are installing the   The first available unused UIC B               file server for the      group number, starting with+               first time               360.o  D               An account named         The same group number as thatC               PCFS$ACCOUNT already     associated with the existingu<               exists                   account PCFS$ACCOUNT.  C               The file server          The same group number as thetE               accounts_already_exist___existing_accounts.____________t         2.1.2 Installing the Server  B            When you have completed the recommended preinstallationC            tasks outlined in Chapter 1, Before You Install AdvancednA            Server for OpenVMS Software, and have read the release >            notes, you are ready to use the POLYCENTER SoftwareB            Installation utility to install the Advanced Server forA            OpenVMS. (For additional details for using the utilityoC            to install, manage, and remove software products on your1A            system, refer to the OpenVMS System Manager's Manual.)   E            During a product upgrade, existing configuration files areSD            preserved in case you want to use them when you configure(            this version of the software.  ?            To install the Advanced Server for OpenVMS software,s            proceed as follows:  ?            1. Load the installation kit media onto an availablec               drive.  >            2. Log in to the SYSTEM account, or an account with$               equivalent privileges.  C            3. Check to make sure that other users are not logged in,               to the system.  8      2-4 Installing Advanced Server for OpenVMS Software           H                          Installing Advanced Server for OpenVMS SoftwareH                                           2.1 The Installation Procedure  C               4. If a previous version of the software is installedoE                  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$SHUTDOWN   -                  For a cluster server, enter:n  5                  $ @SYS$STARTUP:PWRK$SHUTDOWN CLUSTERh  E               5. If you have DECnet configured on your system and youdD                  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-name   E                  where file-name is the name of the file to which your&                  want the log written.  C               6. Start the POLYCENTER Software Installation utility.A                  by entering the PRODUCT INSTALL command with thecC                  source directory path appropriate for your system.w                  For example:t  H                  $ PRODUCT INSTALL ADVANCEDSERVER /SOURCE=directory-path  @                  where directory-path specifies the disk and di-A                  rectory name for the source drive that holds thev>                  Advanced Server for OpenVMS kit. For example,-                  /SOURCE=DAD$100:[ASOVMS073].   @                  If you do not specify the source qualifier, theF                  POLYCENTER Software Installation utility searches theE                  location defined by the logical name PCSI$SOURCE. IfnF                  not defined, the utility searches the current default                  directory.c  C                  The utility installs your software at the locationSA                  defined by the PCSI$DESTINATION logical. If that F                  logical is not defined, then it installs the softwareE                  in SYS$COMMON:[VMS$COMMON] and directories under it.   E                 ______________________ Caution ______________________K  >                 Compaq recommends that you do not redefine the;                 PCSI$DESTINATION logical and do not use thegC                 /DESTINATION qualifier when installing the AdvancedRC                 Server for OpenVMS with PCSI. If the destination isd  H                      Installing Advanced Server for OpenVMS Software 2-5           4      Installing Advanced Server for OpenVMS Software#      2.1 The Installation Procedure   ?               anything other than the default, the installation$?               will probably fail and the installed kit will notn               work correctly.o  C               _____________________________________________________d  >               Note that by default, the installation procedure>               displays a minimum of text. To get supplementaryD               information for each of the prompts, specify the /HELPD               qualifier with the PRODUCT INSTALL command, such as in$               the following example:  F               $ PRODUCT INSTALL ADVANCEDSERVER /SOURCE=directory-path-               _$ /HELP  D            7. The interactive installation procedure begins, and you+               are prompted for information.   >               A sample installation script is included section<               by section, beginning with Example 2-1, Sample>               Installation Procedure-Part 1, with each section@               accompanied by additional explanatory information.  A               The actual installation script that is displayed on @               your system might include additional questions andC               information, depending on your current configuration.   C               ________________________Note ________________________   A               To stop the installation at any time, press Ctrl/Y.a?               The installation procedure deletes any files thatm'               were created, then exits.i  C               _____________________________________________________   5      Example 2-1 Sample Installation Procedure-Part 1a  <      $ PRODUCT INSTALL ADVANCEDSERVER/SOURCE=DKA100:[000000]  -      The following product has been selected:h?          CPQ AXPVMS ADVANCEDSERVER V7.3         Layered ProductO  .      Do you want to continue? [YES] Y <Return>  %      Configuration phase starting ...n  E                                              (continued on next page)l  8      2-6 Installing Advanced Server for OpenVMS Software n  o      H                          Installing Advanced Server for OpenVMS SoftwareH                                           2.1 The Installation Procedure  @         Example 2-1 (Cont.) Sample Installation Procedure-Part 1  N         You will be asked to choose options, if any, for each selected product         and foroI         any products that may be installed to satisfy software dependencyo         requirements.f  C         CPQ AXPVMS ADVANCEDSERVER V7.3: Advanced Server for OpenVMSu  6             Copyright 2000 Compaq Computer Corporation  B             Advanced Server is sold by Compaq Computer Corporation  H             Advanced Server requires PAK PWLMXXXCA07.03 for each client.K                 This installation procedure requires that all the followingi)                 conditions are satisfied: D                 1.  This procedure is running on an Alpha processor.?                 2.  The system is running OpenVMS 7.2 or later. B                 3.  All required privileges are currently enabled.F                 4.  No PATHWORKS or Advanced Server images are running<                     on this node or anywhere in the cluster.G                 5.  No files from a PATHWORKS (NetWare) kit are presentl(                     on this system disk.F                 6.  No files from any Pathworks or Advanced Server kit<                     are in SYS$SPECIFIC on this system disk.  F                 This procedure checks if the conditions are satisfied.?                 If they are satisfied, the procedure continues.v,                 If not, the procedure stops.  /         Do you want to continue? [YES] <Return>   F                 __________Explanatory  Text for Example 2-1 __________  ;                 In this installation example, the installer >                 specifies the source for the installation. TheA                 "Configuration phase starting ..." message referss?                 to the configuration of the POLYCENTER Software D                 Installation utility database, not to the configura-?                 tion of the Advanced Server for OpenVMS itself.d  D                 The first part of the installation script identifiesD                 the product being installed and lists the conditions?                 that the procedure checks before continuing thev  H                      Installing Advanced Server for OpenVMS Software 2-7           4      Installing Advanced Server for OpenVMS Software#      2.1 The Installation Procedure_  A               installation. If you know that one or more of thesea@               conditions have not been met, enter NO to stop the@               procedure, and then do what is required to satisfy               the conditions.E  ?               If you know these conditions have been met, press A               Return to continue with the installation procedure.t?               If you continue, and the procedure finds that anyh;               one of these conditions was not met, then yous;               will see a message such as the one documentedl>               in Section 2.2.1, Installing Advanced Server forA               OpenVMS Software on a VAX System, or Section 2.2.2,r@               Installing Advanced Server for OpenVMS on a System@               Running Another Advanced Server Image. Satisfy the=               required conditions that were not met, and theno$               restart the procedure.  ?               When you continue the procedure (answering YES tot=               the "Do you want to continue?" prompt), you arelA               prompted to select one of the following choices for                the installation.f  C               _____________________________________________________o  5      Example 2-2 Sample Installation Procedure-Part 2n  0              Select one of the numbered options:F              1  Install the complete Advanced Server         [default]/              2  Install only the License Servero?              3  Install only the external authentication images 7              4  Install both the License Server and the 3                      external authentication imagess      Option: [1] <Return>i  C               __________Explanatory Text for Example 2-2 __________l  =               This part of the script gives you the option ofrA               installing the complete Advanced Server for OpenVMSd@               product, or installing only the standalone LicenseA               Server, only the standalone external authenticationf?               images, or installing both the standalone Licensee?               Server and the standalone external authenticationi               images.r    8      2-8 Installing Advanced Server for OpenVMS Software    n      H                          Installing Advanced Server for OpenVMS SoftwareH                                           2.1 The Installation Procedure  >                 In this example, the complete installation was6                 selected, and the procedure continues.  E                 _____________________________________________________i  8         Example 2-3 Sample Installation Procedure-Part 3  H         A PWRK$STREAMSOS_V*.EXE execlet from a previous kit is currently(         loaded into memory on this node.K         You must reboot this node before starting the product on this node.   D         For complete information about the reasons a reboot might beL         necessary and how to avoid unnecessary reboots, see the Installation          and Configuration Guide.           Select an option: C         1. Delay reboot as long as possible on all nodes. [default] J         2. Prevent PWRK$CONFIG configuration on any node using this system#            disk until after reboot.oM         3. Prevent PWRK$CONFIG configuration on all nodes until after reboot. I         4. Prevent startup on any node using this system disk until afterf            after reboot.;         5. Prevent startup on all nodes until after reboot.            Option: [1] <Return>  F                 __________Explanatory  Text for Example 2-3 __________  A                 The installation procedure will check for circum-rD                 stances requiring a system reboot. A reboot might be                 needed if:  @                 o  A previous version of a server driver (PCF or@                    PCI) or of an execlet (PWRK$STREAMSOS_V*.EXE)@                    execlet, was detected in memory. The previousB                    version could be from either an Advanced Server@                    for OpenVMS or PATHWORKS for OpenVMS product.C                    (Reboot is required before starting the Advanced                     Server.)c  E                 o  System parameters were changed (in MODPARAMS.DAT), B                    or server parameters were changed in a way thatB                    affected system parameters. (Reboot is requiredC                    before configuring the Advanced Server, as notedo  H                      Installing Advanced Server for OpenVMS Software 2-9 n  S      4      Installing Advanced Server for OpenVMS Software#      2.1 The Installation Procedureu  A                  in Chapter 1, Before You Install Advanced Serverr'                  for OpenVMS Software.)f  ?               If a PATHWORKS for OpenVMS or Advanced Server fore<               OpenVMS product has been installed and startedB               previously, certain images remain on the system evenA               after the product has been stopped or removed. As ay@               result, before the Advanced Server for OpenVMS canA               be started, you need to reboot the system to remove.               the old image.  9               To help minimize downtime, the installationS:               procedure requests a reboot only if and when;               necessary. You are not forced to reboot afterd               installation.u  @               In Example 2-3, Sample Installation Procedure-Part>               3, software from a previous product installationA               was detected (in this case, a PWRK$STREAMSOS_V*.EXEf'               file; for example, eitherr?               PWRK$STREAMSOS_V6.EXE from PATHWORKS for OpenVMS,h?               or PWRK$STREAMSOS_V7.EXE from Advanced Server fore?               OpenVMS). A reboot is necessary unless you do not A               plan to run the Advanced Server for OpenVMS on this                system.t  B               You have the option of delaying a required reboot soA               that you can complete installation or configuration @               processes that would be expedient to finish before@               rebooting. For example, when installing the server>               on an OpenVMS Cluster, you might want to delay aB               reboot until you complete the server installation on@               all nodes of the cluster. Note that it is possible>               to avoid the reboot by delaying it indefinitely.  B               You also have the option of preventing the installed                server from being:  >               o  Configured on any node using this system diskB                  (the disk on which you are installing the server)#                  until after rebootn  <               o  Configured on all cluster nodes until after                  rebootS  A               o  Started on any node using this system disk untild                  after reboot   9      2-10 Installing Advanced Server for OpenVMS Softwarec S  e      H                          Installing Advanced Server for OpenVMS SoftwareH                                           2.1 The Installation Procedure  ?                 o  Started on all cluster nodes until after theg                    reboot   ?                 These options enable you to prevent unnecessary_A                 reboots such as on a cluster, when installing thefD                 server on a common disk. When you install the serverB                 on one node, you can use these options so that youB                 can complete the installation and configuration onC                 the other cluster nodes before starting the server.r=                 You will only have to reboot the system once.h  E                 _____________________________________________________N    8         Example 2-4 Sample Installation Procedure-Part 4  H                       User Accounts and User Identification Codes (UICs)H                       --------------------------------------------------  I             The Advanced Server V7.3 for OpenVMS installation creates tworK             OpenVMS accounts:  a default account, PWRK$DEFAULT, and a guest G             account, PWRK$GUEST.  The default UIC group number for bothN8             these new accounts depends on the following:  F             o If you are installing the server for the first time, theD               default is the first unused UIC group number, starting               with 360.   >             o If a PCFS$ACCOUNT already exists, the default is@               the UIC group number associated with PCFS$ACCOUNT.  E             o If a PWRK$DEFAULT or PWRK$GUEST account already exists, A               the default is the UIC group number associated with H               PWRK$DEFAULT or PWRK$GUEST, in preference to PCFS$ACCOUNT.G               However, the default UIC group number will not be used to 6               change the UIC of any existing accounts.  A             For more information about UIC group numbers, see the ,             OpenVMS System Manager's Manual.  H                                                 (continued on next page)        H                     Installing Advanced Server for OpenVMS Software 2-11 a  d      4      Installing Advanced Server for OpenVMS Software#      2.1 The Installation Proceduree  =      Example 2-4 (Cont.) Sample Installation Procedure-Part 4   '      Enter default UIC group number for        PWRK$DEFAULT and PWRK$GUEST      Group: [360] <Return>>      Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST(      PWRK$DEFAULT account already exists&      PWRK$GUEST account already exists      C               __________Explanatory Text for Example 2-4 __________K  B               You are prompted for a default UIC group number only@               if you are installing the complete Advanced ServerB               for OpenVMS product. If you do not want to associateA               the newly created OpenVMS accounts PWRK$DEFAULT and:B               PWRK$GUEST with the default user identification codeA               (UIC) group number, specify another three-digit UIC                group number.   C               _____________________________________________________   5      Example 2-5 Sample Installation Procedure-Part 5t  <      * This product does not have any configuration options.    C               __________Explanatory Text for Example 2-5 __________T  @               Configuration choices were already made during the               procedure.  1               The procedure continues as follows.o  C               _____________________________________________________r                  9      2-12 Installing Advanced Server for OpenVMS Software            H                          Installing Advanced Server for OpenVMS SoftwareH                                           2.1 The Installation Procedure  8         Example 2-6 Sample Installation Procedure-Part 6  $         Execution phase starting ...  ?         The following product will be installed to destination: M             CPQ AXPVMS ADVANCEDSERVER V7.3         DISK$AXP0721:[VMS$COMMON.]b  <         Portion done: 0%...10%...20%...30%...40%...70%...90%F             To automatically start Advanced Server V7.3 for OpenVMS atD             system startup, you should add the following line to the/             SYS$MANAGER:SYSTARTUP_VMS.COM file._  +                 $ @SYS$STARTUP:PWRK$STARTUPu  J             Note: Add this line after the lines that start all the network'             transports, such as DECnet.i  J             Before starting Advanced Server V7.3 for OpenVMS on this node,I             be sure to configure the product (@SYS$UPDATE:PWRK$CONFIG) on @             each node in the cluster where the product will run.           ...100%o  1         The following product has been installed: B             CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Product  F                 __________Explanatory  Text for Example 2-6 __________  =                 While the executive phase of the installation_=                 is in process, the script informs you as each >                 portion completes (a percentage indicating howA                 much has completed). It then explains how to haver@                 the server start automatically at system startupB                 and reminds you to run the configuration procedure?                 before starting the server. (Note that with theyB                 installation of the external authentication imagesB                 only, start up and configuration are not options.)  E                 _____________________________________________________c  8         Example 2-7 Sample Installation Procedure-Part 7  H                                                 (continued on next page)    H                     Installing Advanced Server for OpenVMS Software 2-13    u      4      Installing Advanced Server for OpenVMS Software#      2.1 The Installation Procedureq  =      Example 2-7 (Cont.) Sample Installation Procedure-Part 7t  @      %PCSI-I-IVPEXECUTE, executing test procedure for CPQ AXPVMS      ADVANCEDSERVER V7.3 ...  6      Copyright Compaq Computer Corporation 1998, 2000.  9              Starting Installation Verification Procedures1              for Advanced Server V7.3 for OpenVMS   /      %PWRK-I-NORMAL, IVP completed successfully_>      %PCSI-I-IVPSUCCESS, test procedure completed successfully      $  C               __________Explanatory Text for Example 2-7 __________   ?               The procedure verifies the installation, and thenD               finishes.   C               _____________________________________________________   6      2.1.3 What To Do After the Installation Completes  C            If you have installed the external authentication imageslC            only, you can proceed to enable external authentication, ;            as explained in Section 5.7, Setting Up External D            Authentication. For other installations, do the following,            after the installation completes:  B            1. If you had a previous version of Advanced Server for@               OpenVMS running on your system, reboot your system@               before starting the Advanced Server, if necessary.>               See the discussion of circumstances when reboots>               are necessary, in the explanatory text following@               Example 2-3, Sample Installation Procedure-Part 3.  C            2. Proceed to Chapter 3 to configure the Advanced ServerP               for OpenVMS.  >            After the installation completes, you can display aB            list of the Advanced Server for OpenVMS files that were7            installed by entering the following command:o  ?            $ PRODUCT LIST ADVANCEDSERVER /SOURCE=directory-path   9      2-14 Installing Advanced Server for OpenVMS Softwaren e         H                          Installing Advanced Server for OpenVMS SoftwareH                                           2.1 The Installation Procedure  H               where directory-path specifies the disk and directory nameE               for the source drive that holds the Advanced Server forAG               OpenVMS kit. For example, /SOURCE=DAD$100:[ASOVMS073]. IfmE               you do not specify the source qualifier, the POLYCENTERaA               Software Installation utility searches the locationiF               defined by the logical name PCSI$SOURCE. If not defined,A               the utility searches the current default directory.n    1         2.2 Troubleshooting Installation Problems   C               The following sections describe some problems you caneB               encounter if you install Advanced Server for OpenVMSA               software in an environment that is not appropriate.i  F         2.2.1 Installing Advanced Server for OpenVMS Software on a VAX               System  F               The Advanced Server does not run on OpenVMS VAX systems.D               If you attempt to install the Advanced Server on a VAXB               system, the POLYCENTER Software Installation utility@               procedure displays the following error message and*               terminates the installation:  J               Advanced Server V7.3 for OpenVMS does not run on OpenVMS VAX               systems.I               You can install this product on OpenVMS Alpha systems only.f  @         2.2.2 Installing Advanced Server for OpenVMS on a System3               Running Another Advanced Server Imagec  ?               If you attempt to install the Advanced Server foroG               OpenVMS on a system (or anywhere in a cluster) on which arH               PATHWORKS for OpenVMS or Advanced Server for OpenVMS imageG               is running, the installation procedure displays a message $               such as the following:  H               Advanced Server V7.3 for OpenVMS cannot be installed whileE               any PATHWORKS or Advanced Server processes are running. G               If this node is part of a cluster, no node of the cluster 1               can be running any of those images.m  M         At least one of the preconditions for installation have not been met.     H                     Installing Advanced Server for OpenVMS Software 2-15 d  .      4      Installing Advanced Server for OpenVMS Software.      2.2 Troubleshooting Installation Problems  4      See the Installation Guide for more information'      %PCSI-E-S_OPFAIL, operation failed H      %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error      condition      C               _________What To Do If You See This Message _________   =               Stop these server images from running, and thent1               restart the installation procedure.   C               _____________________________________________________l  #      2.2.3 System Disk Restrictionse  D            If the installation procedure detects PATHWORKS (NetWare)@            files, the procedure will notify you and request that>            you remove those files and restart the installationD            procedure. The same is true if the installation procedure>            detects PATHWORKS for OpenVMS files or any Advanced@            Server files in a SYS$SPECIFIC: directory. If certain<            images are detected in system memory (such as the@            PWRK$STREAMSOS_V*.EXE file, as in Example 2-3, Sample=            Installation Procedure-Part 3), the procedure willeD            continue, notifying you that a reboot is necessary before4            starting the Advanced Server for OpenVMS.  B      2.2.4 Installing Advanced Server for OpenVMS on a System withC            PATHWORKS for OpenVMS (Advanced Server), Version 6.0A ore            Earlier  A            If the system has Version 6.0A or earlier of PATHWORKSeD            for OpenVMS (Advanced Server) installed, the installation4            procedure displays the following message:  A            The migration path from PATHWORKS V6.0 to the AdvancedA?            Server is valid, but not recommended. Do you want tod1            continue with the installation? [YES]:o  E            Compaq recommends that you upgrade to Advanced Server V7.3pD            for OpenVMS from PATHWORKS for OpenVMS (Advanced Server),C            Version 6.0C or later. To upgrade from previous versions @            of the server, follow the migration path described inC            Section 1.1.2, Upgrading to Advanced Server for OpenVMS,.?            before you install Advanced Server V7.3 for OpenVMS.   9      2-16 Installing Advanced Server for OpenVMS Software$ F  c      H                          Installing Advanced Server for OpenVMS SoftwareH                                                           2.3 Next Steps           2.3 Next Steps  H               To continue, depending on which server you are installing,&               do one of the following:  H         ________________________________________________________________H         If_you_are_._._.________Proceed_to_._._.________________________  C         Installing the          Chapter 3, Configuring the Advanced &         complete Advanced       Server         Server  G         Installing the          Chapter 4, Configuring and Starting thea9         standalone License      Standalone License Serveri         Server  @         Installing the          Section 5.7, Setting Up ExternalH         standalone external     Authentication, and refer to the OpenVMS9         authentication          Guide to System Security. H         software________________________________________________________                                                  H                     Installing Advanced Server for OpenVMS Software 2-17                         H                                                                        3H         ________________________________________________________________  H                                          Configuring the Advanced Server      B               This chapter describes how to configure the Advanced=               Server, and consists of the following sections:T  E               o  Section 3.1, About the Advanced Server Configuration                   Procedure  D               o  Section 3.2, Migrating LANMAN.INI Parameters to the!                  OpenVMS Registry   B               o  Section 3.3, Before You Start the Advanced Server(                  Configuration Procedure  >               o  Section 3.4, How to Start the Advanced Server(                  Configuration Procedure  ?               o  Section 3.5, How to Respond to Advanced Servers&                  Configuration Prompts  @               o  Section 3.6, How to Change Server Configuration                  Settings   D               o  Section 3.7, Configuring the Advanced Server Domain                  Role   =               o  Section 3.8, Configuring the Server Language   G               o  Section 3.9, Configuring Windows NT Printer Management   F               o  Section 3.10, Troubleshooting Configuration Procedure                  Problemsd  B               o  Section 3.11, The Advanced Server Network Adapter  )               o  Section 3.12, Next Steps   H                                      Configuring the Advanced Server 3-1 o  a      $      Configuring the Advanced Server:      3.1 About the Advanced Server Configuration Procedure  :      3.1 About the Advanced Server Configuration Procedure  ?            The Advanced Server initial configuration procedure,nC            PWRK$CONFIG.COM, is installed by the Advanced Server ford*            OpenVMS installation procedure.  =            Like the installation procedure, the configurationuB            procedure asks you a series of questions (by displayingE            prompts). The procedure uses your answers to configure the             Advanced Server.   C            You can use the PWRK$CONFIG procedure to reconfigure the B            server at any time later. Note that the script contents0            change after the first configuration.  0      3.1.1 What the Configuration Procedure Does  3            PWRK$CONFIG is a command procedure that:   E            o  Creates the Advanced Server on-disk structure (shown in >               Section E.2, Advanced Server On-Disk Structure).  @            o  Upgrades any existing file server user account andE               share databases, such as when upgrading the server from B               a previous version, or when the currently configuredB               language is not compatible with the language used by'               the existing file server.y  C            o  If configuring a previously configured server, storesrA               the original accounts database in specially-createdeE               directories. (For more information, see Section 3.10.3,e?               If Problems Occur When Reconfiguring the Advancedo               Server.)  =            o  Starts the Registry server if it is not alreadyr               running.  ?            o  If you are upgrading from a PATHWORKS for OpenVMS_D               server to Advanced Server for OpenVMS, migrates serverE               configuration parameters from the PATHWORKS for OpenVMSA@               LANMAN.INI file to the OpenVMS Registry. (For more@               information, see Section 3.2, Migrating LANMAN.INI2               Parameters to the OpenVMS Registry.)    (      3-2 Configuring the Advanced Server f  t      H                                          Configuring the Advanced ServerH                    3.1 About the Advanced Server Configuration Procedure  A               o  Allows you to enter the Configuration Manager totG                  modify configuration parameters that affect the systemuD                  environment and to verify the configuration settingE                  against the available system resources. For example,rG                  you can specify the transports the server will run and$F                  the maximum number of clients that can connect to the'                  server simultaneously.   F                  For more information about the Configuration Manager,G                  refer to the Compaq Advanced Server for OpenVMS Server '                  Administrator's Guide.   B               o  Allows you to modify server configuration defaultC                  settings such as server role, domain name, and the +                  services that are enabled.p  >               o  On a server that will run as a primary domainC                  controller or member server, allows you to specifyo4                  the Administrator account password.  =               o  Gives you the option of starting the server.   H               After you install the server, you must run the PWRK$CONFIGF               configuration procedure before you can start the server.E               In an OpenVMS Cluster, before you start the server, you E               must run PWRK$CONFIG on each node where you plan to runnB               the server. Although the nodes in an OpenVMS ClusterB               function as a single unit in a domain, treat them as=               individual units for purposes of configuration.M                                H                                      Configuring the Advanced Server 3-3 :         $      Configuring the Advanced Server@      3.2 Migrating LANMAN.INI Parameters to the OpenVMS Registry  @      3.2 Migrating LANMAN.INI Parameters to the OpenVMS Registry  D            The PATHWORKS for OpenVMS and Advanced Server for OpenVMSB            servers store server parameters in different locations.@            PATHWORKS for OpenVMS servers use the LANMAN.INI fileA            to store server configuration parameters. The Advancedf>            Server for OpenVMS uses the OpenVMS Registry, whichA            is similar to the Windows NT registry. For information D            about managing the server configuration parameters in theD            OpenVMS Registry, refer to the Compaq Advanced Server for0            OpenVMS Server Administrator's Guide.  C            If you are upgrading a system from PATHWORKS for OpenVMS =            to Advanced Server for OpenVMS, the parameters and @            settings in the existing LANMAN.INI file are migratedC            to the OpenVMS Registry when you run the PWRK$CONFIG.COMd;            configuration procedure for the first time after >            installation. (The Advanced Server for OpenVMS doesA            not read parameter settings from the LANMAN.INI file.)AA            After they have been migrated to the OpenVMS Registry, D            you manage the parameters in the registry. The LANMAN.INIE            file is retained in case the system will run PATHWORKS for             OpenVMS again later.   ?            The PWRK$CONFIG.COM configuration procedure performsa>            a one-time migration of the parameters. At the time=            the parameters are migrated into the registry, thep>            PWRK$CONFIG procedure sets the data associated withB            the LanmanIniMigrated value in the OpenVMS Registry. IfA            this value exists and has data associated with it, theSB            PWRK$CONFIG procedure will omit the parameter migration            process.x  C            You can display the value and its associated data in thes9            OpenVMS Registry using the following commands:s  3            $ REGUTL :== $SYS$SYSTEM:PWRK$REGUTL.EXEp  2            $ REGUTL SHOW VALUE * LANMANINIMIGRATED  ?            In the following example, the data displayed for theh@            LanmanIniMigrated value indicates that the parameters-            were migrated on October 29, 2000:e    (      3-4 Configuring the Advanced Server t  h      H                                          Configuring the Advanced ServerH              3.2 Migrating LANMAN.INI Parameters to the OpenVMS Registry  N               Key: SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters&               Value: LanmanIniMigrated               Type: StringJ               Current Data: LANMAN.INI migrated on 29-OCT-2000 15:31:48.90  F               The following example shows what data might be displayedD               for the LanmanIniMigrated value if you are configuringG               your Advanced Server for OpenVMS on a system that has notuF               had PATHWORKS for OpenVMS configured on it (that is, you<               are not upgrading from PATHWORKS for OpenVMS):  4               REGUTL> SHOW VALUE * LANMANINIMIGRATED  N               Key: SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters&               Value: LanmanIniMigrated               Type: StringP               Current Data: No LANMAN.INI to migrate on  29-OCT-2000 15:31:48.90  D               Refer to the Compaq Advanced Server for OpenVMS ServerD               Administrator's Guide for more information about usingD               the PWRK$REGUTL utility to manage server configuration1               parameters in the OpenVMS Registry.a  >         3.3 Before You Start the Advanced Server Configuration             Procedure   H               Before you start the PWRK$CONFIG command procedure, answer@               the questions discussed in the following sections.  B         3.3.1 On What OpenVMS Disk Device Do You Want to Store the)               Advanced Server Data Files?   %               The data files include:v  .               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 Advanced Server 3-5 n  s      $      Configuring the Advanced ServerE      3.3 Before You Start the Advanced Server Configuration Procedurel  B            By default, the configuration procedure copies the dataC            files to the system device (SYS$SYSDEVICE). However, youfC            can specify any existing OpenVMS disk device that has atrD            least 85,000 free blocks of disk space. The amount needed/            depends on the components installed.r  E            When you select a disk for the Advanced Server data files, &            keep the following in mind:  >            o  The Advanced Server frequently accesses the data>               files copied to the specified disk device, whichA               generates input to and output from the disk. HavingtC               these operations occur on the system disk can degradem@               the performance of both the OpenVMS system and theD               Advanced Server. Therefore, Compaq recommends that you?               specify a disk device other than the system disk.b  C            o  On an OpenVMS Cluster with multiple system disks, alleE               nodes on which you plan to run the Advanced Server mustnC               use the same disk device to store and access AdvancedVA               Server data files. Using separate disks on separatea5               cluster members is strictly prohibited.   B            o  You can run the PWRK$CONFIG command procedure at anyC               time, to change the disk device where Advanced Server E               data files are stored. PWRK$CONFIG automatically copies E               the data files to the new location and deletes the dataO.               files from the current location.  D      3.3.2 Do You Want to Change the System Configuration Parameters            Now?   B            If you respond "YES" to the prompt to change the system@            configuration parameters, you start the Configuration?            Manager. The Configuration Manager is a utility that A            allows you to modify and verify the system environment @            configuration parameter settings, such as the maximum@            number of clients that can connect to the server, the@            percentage of physical memory the server can use, and4            which network transports the server uses.  <            You can change the system configuration parameterC            settings after starting the Advanced Server by using the D            Configuration Manager. For more information, refer to theD            Compaq Advanced Server for OpenVMS Server Administrator'sC            Guide. Section B.2, Sample Advanced Server ConfigurationS  (      3-6 Configuring the Advanced Server d  c      H                                          Configuring the Advanced ServerH         3.3 Before You Start the Advanced Server Configuration Procedure  E               Procedure, shows the basic Configuration Manager screen G               displayed when you opt to change the system configuration 4               parameter settings during PWRK$CONFIG.  E         3.3.2.1 Configuring Transports for a Backup Domain Controllerr                  or Member Server  @               If you are configuring a server as a backup domainE               controller (BDC) or a member server, you must select atiF               least one transport that will also be run by the primaryH               domain controller (PDC). Otherwise, the configuration will               fail.i  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 networksnF                  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 different C                  TCP/IP subnet, both the server you are configuringiA                  and the PDC must be configured to use the TCP/IPdD                  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 andG                  LMHOSTS file for NetBIOS name resolution, as described E                  in Chapter 6, Implementing a Wide Area Network. (YoueG                  can select one, two, or all three of these methods for0"                  name resolution.)  H               o  If you are using WINS for network name resolution, bothE                  the 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,eH                  clients should connect to the Advanced Server using theE                  Advanced Server cluster alias. However, the AdvancedhB                  Server does not dynamically register the AdvancedF                  Server cluster alias with the WINS server. Therefore,D                  you should define a static multihomed entry for the  H                                      Configuring the Advanced Server 3-7 e         $      Configuring the Advanced ServerE      3.3 Before You Start the Advanced Server Configuration Procedured  B               Advanced Server alias in the WINS database. For moreA               information, see Section 6.3.1, Setting up WINS for,B               OpenVMS Clusters. If you plan to use DNS for NetBIOSC               name resolution, you might need to remove this staticSE               multihomed entry from the WINS database (if clients are_B               configured to use both WINS and DNS for NetBIOS nameE               resolution, they first query the WINS server to resolve-               the name).  E            o  If you are using the LMHOSTS file, it must be set up on D               the PDC as well as the BDCs and member servers. BeforeC               you configure any BDC or member server that is not oneB               the same subnet as the PDC, make sure that a specialC               NetBIOS name entry for the PDC is in the LMHOSTS filelA               on that BDC or member server; otherwise, the BDC ord?               member server will not find the PDC and will fail B               to join the existing domain. This NetBIOS name entryD               should be the same as the domain name, space padded toC               15 characters, with the hexadecimal control character B               1B appended to it. You map the IP address of the PDCC               to this special name. For example, if the domain name C               is LANGROUP and the PDC of LANGROUP is DOMPDC with anoD               IP address of 10.20.30.40, the BDCs and member serversD               would need to add the following lines to their LMHOSTS               file:r  6               10.20.30.40  DOMPDC  #PRE  #DOM:LANGROUP6               10.20.30.40 "LANGROUP       \0x1B"  #PRE  A               Note that the total number of characters within the D               quotes should always be 20 characters (the domain name?               padded to 15 characters, plus the five charactersv<               required for the hexadecimal control character               (\0x1B)).   A               For more information, see Chapter 6, Implementing aa                Wide Area Network.  E               If your Advanced Server will run in an OpenVMS Cluster, C               other domain controllers (including the PDC) that are C               not in the same subnet as the Advanced Server clusterP?               must add an entry for the Advanced Server cluster @               alias to their LMHOSTS file. This assumes they areA               not using other methods (WINS or DNS) for resolving B               NetBIOS names. For domain operations, all the domainC               controllers in the cluster operate as a single domain   (      3-8 Configuring the Advanced Server u  t      H                                          Configuring the Advanced ServerH         3.3 Before You Start the Advanced Server Configuration Procedure  E                  controller identified by the Advanced Server cluster G                  alias name, rather than by the specific computer namesuD                  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, theA                  entry for the Advanced Server cluster alias mustoC                  be mapped to the IP address of one specific serveruB                  cluster member. If the Advanced Server is stoppedD                  on that cluster member, you must modify the LMHOSTSE                  file to map the cluster alias name to the IP addresstD                  of a cluster member on which the Advanced Server isF                  still running. On systems running a Microsoft WindowsC                  operating system, the NetBIOS name cache must also D                  be reloaded using the command NBTSTAT -R (capital R                  required).   B                  Due to the LMHOSTS limitations noted above, it isA                  difficult (and perhaps unmanageable) to gain the A                  benefits of load balancing and failover using an                   LMHOSTS file.  C               o  If your Advanced Server runs in an OpenVMS ClusteryB                  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. RemoveeG                  any entries for the Advanced Server cluster alias fromtD                  the LMHOSTS file and WINS database. Compaq stronglyF                  recommends that the Advanced Server cluster alias notH                  be the same as the TCP/IP cluster alias (referred to asG                  the TCP/IP cluster impersonator name). For information$B                  on setting up load balancing, refer to the CompaqC                  Advanced Server for OpenVMS Server Administrator'sr                  Guide.h  H               To enable any of the wide area networking implementations,G               select them using the Configuration Manager, as described >               in the Compaq Advanced Server for OpenVMS Server$               Administrator's Guide.              H                                      Configuring the Advanced Server 3-9    O      $      Configuring the Advanced ServerE      3.3 Before You Start the Advanced Server Configuration Procedure   @      3.3.3 Do You Want to Change Any of the Server Configuration            Settings?  7            The server configuration settings determine:t  -            o  Whether the License Server runs   ?               The License Server is a software program that you B               can run on your OpenVMS system to grant client-basedE               licenses. Any client that wants to use server resourcesu@               must have a valid license. Each local area networkE               (LAN) needs only one License Server. The client licensesE               product authorization keys (PAKs) must be loaded on the 2               system that runs the License Server.  ?               In an OpenVMS Cluster, the PAKs must be loaded inC@               a shared license database available to all cluster               members.  D               The License Server runs only if you enable it with the&               configuration procedure.  B               -  If you are using client-based licensing, you must?                  run the License Server. Compaq recommends thatSA                  you run the License Server on a different systemuA                  than the Advanced Server. See Section 1.3, Abouts1                  Licensing, for more information.   C               -  If you are using server-based licenses, you do not 0                  need to run the License Server.  :               By default, the License Server does not run.  1            o  Whether the Timesource service runs   >               The Timesource service allows your server to act@               as a time server. Other servers on the network canD               synchronize with the time server to coordinate network@               events (for example, running batch programs on allD               computers the same time each day). Each LAN needs only               one time server.  >               By default, the Timesource service does not run.  .            o  Whether the Alerter service runs  A               The Alerter service sends messages called alerts tohA               servers and clients that run the Messenger service.t  3               By default, the Alerter service runs.   ;            o  Names of the users who receive alert messagesn  )      3-10 Configuring the Advanced Servero t         H                                          Configuring the Advanced ServerH         3.3 Before You Start the Advanced Server Configuration Procedure  I                  By default, alert messages are sent to the Administratory                  account.   9               o  Whether the Netlogon service is enabled.$  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 onEB                  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.h  7                  By default, the Netlogon service runs.g                 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, referC                  to the Compaq Advanced Server for OpenVMS Concepts1F                  and Planning Guide and the Compaq Advanced Server for6                  OpenVMS 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 primaryrB                  domain controller (PDC), 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.t  H                  For more details on configuring the server domain role,H                  see Section 3.7, Configuring the Advanced Server Domain                  Role.                 o  Computer name  G                  This unique name identifies your server in the domain.oF                  You define this name or accept the default value when5                  you run the configuration procedure.   H                                     Configuring the Advanced Server 3-11           $      Configuring the Advanced ServerE      3.3 Before You Start the Advanced Server Configuration Procedure   A               The PWRK$CONFIG procedure will not prevent you from >               specifying the same named PDC if another node or@               cluster has previously been defined and is runningD               in that role. However, on the new (duplicate) PDC, theC               Netlogon service will not be started. The PDC must bef#               unique in the domain.f  C               The default computer name is the same as the server'su               SCSNODE name.   +            o  Advanced Server cluster aliasw  D               If your server is a member of an OpenVMS Cluster, thisD               is the name that all servers in the cluster share. TheC               alias lets remote nodes (including clients) treat all C               server members in the cluster as a single server. For D               example, a client user can specify the Advanced ServerD               cluster alias to connect to any server in the cluster;E               the user need not know the specific node in the clusterm'               to which it is connected.p  B               If DECnet has been configured to run in the cluster,C               the default Advanced Server cluster alias is the samerC               as the DECnet cluster alias. If a DECnet alias is noti@               defined, the default Advanced Server cluster aliasC               is nodename_ALIAS, where nodename is the SCSNODE namew@               of the cluster member from which you initially run               PWRK$CONFIG.  C               ________________________Note ________________________   A               Compaq strongly recommends that the Advanced ServertB               cluster alias and the TCP/IP cluster alias (referred<               to as the TCP/IP impersonator cluster name) be               different.  ?               Do not use the name of the domain as the Advanced =               Server cluster alias; if they are the same, theO2               NetLogon service will fail to start.  C               _____________________________________________________   %            o  Server announce commentn  E               This is the text that the Advanced Server displays whenmC               it announces its presence on the network and when yout2               display a list of available servers.  )      3-12 Configuring the Advanced Server            H                                          Configuring the Advanced ServerH         3.3 Before You Start the Advanced Server Configuration Procedure  H                  The default server announce comment is "Advanced Server#                  V7.3 for OpenVMS."c  )               o  Advanced Server language   F                  This determines the language and associated characterF                  set (one of several ISO-8859 character sets) that theE                  Advanced Server uses for encoding text, such as fileGF                  and share names, user names, description strings, and<                  any content of ADMINISTER command displays.  D                  The default is English (USA). You can configure anyH                  one of over 40 languages, many which include support ofE                  extended character set characters. For an up-to-date G                  list of languages that are officially supported, refer ;                  to the Software Product Description (SPD).f  F                 ________________________Note  ________________________  D                 The same language must be used by all servers in theD                 domain. Compaq recommends that all clients that willD                 access the server also be configured to use the same@                 language; otherwise, names containing charactersC                 that are not supported by the server language mightl2                 not appear to clients as expected.  E                 _____________________________________________________o  B                  If your disk device includes ODS-2 file names (inA                  specific, file names that include escape-encodeddG                  characters in the format __XX), you must first convertoD                  the file names to ODS-5 file names, as explained inF                  Section 5.8, Converting Encoded File Names from ODS-2G                  to ODS-5. Section 3.8, Configuring the Server LanguagerH                  explains how to configure the Advanced Server language.C                  For more information on languages, character sets,rE                  and Unicode, refer to the Compaq Advanced Server ford6                  OpenVMS Server Administrator's Guide.  )               o  Enable NT style printing   D                  This gives you a choice of managing shared printersD                  either from a remote Windows NT computer or locallyF                  using the ADMINISTER command interface at the server.B                  When enabled, administrators can store the latestA                  drivers for the printers on the Advanced Server. F                  When new drivers are distributed, administrators have  H                                     Configuring the Advanced Server 3-13 l  s      $      Configuring the Advanced ServerE      3.3 Before You Start the Advanced Server Configuration Procedurew  A               to update a single location only. When client users B               set up printers to use from their workstations, theyA               are able to download the appropriate printer drivere               automatically.  A               The default is local management of shared printers,h@               using ADMINISTER commands. When you enable WindowsB               NT printer management, only limited functionality isA               available for managing printers with the ADMINISTERiD               interface. Before configuring Windows NT style printerA               management, see the considerations and restrictionso@               in Section 3.9.1, Considerations Regarding Windows>               NT Printer Management. Section 3.9.2, Example ofA               Configuring Windows NT Printer Management, includesoD               a sample configuration script showing how to configure2               Windows NT style printer management.  ?               For more information about management of Advancedt?               Server print shares, refer to the Compaq Advancedn>               Server for OpenVMS Server Administrator's Guide.  A            For more information about changing configuration set-bE            tings, see Section 3.6, How to Change Server Configuratione            Settings.  ?            For more information about each server configuration C            setting, refer to the Compaq Advanced Server for OpenVMS (            Server Administrator's Guide.  A      3.3.4 What Do You Want the Administrator Account Password tos            Be?  D            If you are configuring a PDC, the configuration procedure@            prompts you to specify the password to be set for theA            domain Administrator account. If you are configuring a E            member server, the configuration procedure prompts you for C            the member server's local Administrator account password =            to be set. The member server's local Administrator ?            account password gives access to the member server'saE            local security account database. As with Windows NT, theresC            may be situtations where you would like to allow certainSD            people to manage a member server's local database without?            giving them the ability to manage the entire domain.E    )      3-14 Configuring the Advanced Server  r  e      H                                          Configuring the Advanced ServerH         3.3 Before You Start the Advanced Server Configuration Procedure  C               Passwords are case sensitive and can contain up to 14 F               characters. Valid characters are alphanumeric characters:               and any of the following special characters:  *               ! # $ % & () - . ^ _ ` { } ~  C         3.3.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:l  F               o  Have the computer added to the domain manually by the%                  domain administratorW  F               o  Have the computer added by supplying an administratorG                  account user name and password during execution of the (                  configuration procedure  E               The former option is useful if the domain administrator E               does not wish to give out the user name and password ofnC               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 commandiB               or the Windows NT Server Manager to add the computerC               to the domain. If this is the case, answer NO to this G               prompt, and you will not be prompted for account/passworde               information.  E               With the latter option, the configuration procedure re-rH               quests the domain's PDC to add the computer to the domain.E               You will be prompted for a domain administrator account D               user name and password, as explained in Section 3.3.6,9               What Is the Domain Administrator Password?.S  8         3.3.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.3.5, Are You Going to SupplyA               Account/Password Information?, the PDC is requested B               to add the computer to the domain. The PDC validatesA               the account user name and password on behalf of theaD               configuration procedure. Enter the password, observingH               the rules specified in Section 3.3.4, What Do You Want the4               Administrator Account Password to Be?.  H                                     Configuring the Advanced Server 3-15 r  u      $      Configuring the Advanced ServerE      3.3 Before You Start the Advanced Server Configuration Procedure   ;      3.3.7 Do You Want to Enter a New Administrator Account             Password?  A            In certain cases, you are prompted whether you want tomA            enter a new Administrator password. This gives you thel.            opportunity to change the password.  +      3.3.8 Do You Want to Start the Server?t  D            The configuration procedure asks you if you want to start?            the Advanced Server. If you do not want to start the E            Advanced Server at this time, you can do so later from themD            command line after the configuration procedure completes.  E            Before you start the server on any OpenVMS Cluster member,eC            Compaq recommends that you configure the Advanced ServervC            on each cluster member that you want to use as a server.dB            You can then use the SYSMAN utility to start the serverD            on all cluster members. If you choose to start the serverE            individually on each cluster member, make sure that you do D            so from the SYSTEM account (or a similar account) on eachD            server node. For more information, see Section 5.4.3, How>            to Start the Advanced Server in an OpenVMS Cluster.  A      3.4 How to Start the Advanced Server Configuration Procedure   B            After the installation procedure completes, the OpenVMS+            system prompt ($)  is displayed.   B            1. Ensure that you are logged in to the SYSTEM account.  <            2. Start the configuration procedure by entering:  '               $ @SYS$UPDATE:PWRK$CONFIGt  @      3.5 How to Respond to Advanced Server Configuration Prompts  B            Table 3-1, Advanced Server Configuration Prompts, tells=            you how to respond to the prompts that PWRK$CONFIGn            displays.  C               ________________________Note ________________________s  :               Table 3-1 shows only the prompts PWRK$CONFIG:               displays; it does not show any informational;               messages. For a complete sample configurationf  )      3-16 Configuring the Advanced Servern e  r      H                                          Configuring the Advanced ServerH              3.5 How to Respond to Advanced Server Configuration Prompts  >                 script, see Appendix B, Sample Advanced Server/                 Installation and Configuration.   E                 _____________________________________________________y  H         Table_3-1_Advanced_Server_Configuration_Prompts_________________  7         At this prompt . . . If you want the configura-oH         _____________________tion_procedure_to_._._.______Enter_._._.___  C         Do you want to       Shut down the server or,     Press the D         continue with        if your server is part of    Return key4         configuration        an OpenVMS Cluster, all3         [YES]:[1]            servers in the clustere  <                              Abort the configuration      NO&                              procedure  C         Enter disk device    Copy the Advanced Server     Press therD         name where Advanced  on-disk structure to the     Return key8         Server data files    default OpenVMS disk device&         will be stored       displayed3         [default_device]:    If you ran PWRK$CONFIGt  4                              previously, the default7                              disk device is the one you 4                              specified the last time7                              you configured the server; 3                              otherwise, the defaultr5                              device is SYS$SYSDEVICE.   E                              Copy the Advanced Server     device_name 1                              on-disk structure too3                              an OpenVMS disk devicee7                              different from the default &                              displayed  B         [1]This prompt is displayed only if the server is running.  H                                                 (continued on next page)          H                                     Configuring the Advanced Server 3-17 d  i      $      Configuring the Advanced Server@      3.5 How to Respond to Advanced Server Configuration Prompts  E      Table_3-1_(Cont.)_Advanced_Server_Configuration_Prompts_________1  4      At this prompt . . . If you want the configura-E      _____________________tion_procedure_to_._._.______Enter_._._.___.  @      Do you want to       Access the Configuration     Press theA      change the server    Manager tool to change       Return key.C      configuration        parameters affecting the     For detailedtB      parameters now?      system environment for the   information<      [YES]:               server                       about  @                                                        using theD                                                        ConfigurationE                                                        Manager, refer D                                                        to the Compaq?                                                        Advanced A                                                        Server for E                                                        OpenVMS ServernF                                                        Administrator's=                                                        Guide.   9                           Complete the configuration   NOn.                           without entering the/                           Configuration Managere  @      Enter item number,   Accept the server            Press theA      or RETURN to         configuration parameters     Return keyd2      use these values     displayed (these are the.      [DONE]:              ten or so parameters1                           that directly affect or 4                           define the server software(                           configuration)  E                                              (continued on next page)                       )      3-18 Configuring the Advanced Serverd i  e      H                                          Configuring the Advanced ServerH              3.5 How to Respond to Advanced Server Configuration Prompts  H         Table_3-1_(Cont.)_Advanced_Server_Configuration_Prompts_________  7         At this prompt . . . If you want the configura-yH         _____________________tion_procedure_to_._._.______Enter_._._.___  D                              Change the configuration     The numberD                              settings displayed           associatedH                                                           with a settingE                                                           you want tooA                                                           change.   F                                                           For detailedE                                                           information E                                                           on changingeG                                                           these defaultoG                                                           configuration G                                                           settings, see F                                                           Section 3.6,@                                                           How toG                                                           Change ServerdG                                                           Configuration(C                                                           Settings.e  C         Are you going to     Have the computer            Press thedD         supply account       added automatically by       Return key7         /password            PWRK$CONFIG, prompting youl7         information?         for a domain administrator_2         [YES]:[4]            account user name and%                              password   <                              Have the computer added      NO6                              manually (for example, by6                              the domain administrator)/                              so that the domain 5                              administrator's passwordi1                              need not be divulgedt  H         [4]This prompt is displayed only if you are configuring a BDC or3         member server (joining an existing domain).   H                                                 (continued on next page)      H                                     Configuring the Advanced Server 3-19           $      Configuring the Advanced Server@      3.5 How to Respond to Advanced Server Configuration Prompts  E      Table_3-1_(Cont.)_Advanced_Server_Configuration_Prompts_________t  4      At this prompt . . . If you want the configura-E      _____________________tion_procedure_to_._._.______Enter_._._.___.  ?      Enter the name       Enter the name of the        PDC-namem3      of the primary       primary domain controllere3      domain controller    (PDC) for the domain your ,      for domain domain-   server is joining.      name[4]  ?      Enter Administrator  Associate a password with    passwordf@      account pass-        the Administrator account    Enter theB      word:[3]                                          password to  A                                                        be set fornC                                                        the domain's ?                                                        existingnD                                                        Administrator?                                                        account.   @      Do you want to       Keep the existing            Press theA      enter a new          Administrator account        Return keym"      Administrator        password      account passworde      [NO]:[2,3]   :                           Prompt you to enter a        YES3                           new Administrator accountl"                           password  ?      Re-enter to verify                                password       password [3,4,5]:  C      [2]This prompt is displayed if you ran PWRK$CONFIG previously.oC      [3]This prompt is displayed only if you are configuring a PDC.rE      [4]This prompt is displayed only if you are configuring a BDC oro0      member server (joining an existing domain).E      [5]This prompt is displayed only if you are configuring a memberE      server.  E                                              (continued on next page)     )      3-20 Configuring the Advanced Server  d         H                                          Configuring the Advanced ServerH              3.5 How to Respond to Advanced Server Configuration Prompts  H         Table_3-1_(Cont.)_Advanced_Server_Configuration_Prompts_________  7         At this prompt . . . If you want the configura-sH         _____________________tion_procedure_to_._._.______Enter_._._.___  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 to D         Administrator                                     be set forD         account:[5]                                       the member  H                                                           server's localG                                                           AdministratoreB                                                           account.  B         Enter the account                                 passwordC         password in the                                   Enter thepE         required case[4]                                  password inn  D                                                           the properH                                                           case, matchingE                                                           the current H                                                           domain accountC                                                           password.a  C         Do you want to       Start the server au-         Press thetD         start the Advanced   tomatically after the        Return key4         Server V7.3 for      configuration procedure&         OpenVMS on node      completes         node_name now          [YES]:[6]S  <                              Not start the server         NOH         [4]This prompt is displayed only if you are configuring a BDC or3         member server (joining an existing domain). H         [5]This prompt is displayed only if you are configuring a member         server.sF         [6]This prompt is displayed only if the Advanced Server can beH         started without first executing AUTOGEN or rebooting the system.H         ________________________________________________________________        H                                     Configuring the Advanced Server 3-21           $      Configuring the Advanced Server4      3.6 How to Change Server Configuration Settings  4      3.6 How to Change Server Configuration Settings  C            After you exit the Configuration Manager, the configura-nA            tion procedure displays a list of server configurationn?            settings and a prompt that lets you change them; forn            example:   =        Advanced Server for OpenVMS is presently configured toa        run as follows:  7         1.  Run the License Server:                  NO 7         2.  Enable Timesource service:               NOe8         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:           COBRAZ A         7a. Advanced Server OpenVMS Cluster alias:   COBRAZ_ALIASeI         8.  Server announce comment:     Advanced Server V7.3 for OpenVMSCB         9.  Advanced Server language:                English (USA)7         10. Enable NT style printing:                NO =      Enter item number, or RETURN to use these values [DONE]:a  A            o  To change a server configuration setting, enter thee@               number of the setting you want to change. A promptB               is then displayed that lets you change that setting.C               Table 3-2, Configuration Settings, describes possibler&               values for each setting.  E            o  To save the settings after you complete your changes orgD               to accept the settings displayed, press the Return keyB               to use the default answer DONE. For more information=               about server configuration, refer to the Compaq @               Advanced Server for OpenVMS Server Administrator's               Guide.                  )      3-22 Configuring the Advanced Servern m  o      H                                          Configuring the Advanced ServerH                          3.6 How to Change Server Configuration Settings  H         Table_3-2_Configuration_Settings________________________________  H         Setting_________________Possible_Values_________________________  ?         1. Run the License      YES, to run the License Server.tF         Server:                 NO, to use the default and not run the/                                 License Server.   F         2. Enable Timesource    YES, to enable the Timesource service.E         service:                NO, to use the default and not enables7                                 the Timesource service.   E         3. Enable Alerter       YES, to accept the default and enable 4         service:                the Alerter service.C                                 NO, to disable the Alerter service.   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 enable 5         service:[2]             the Netlogon service. D                                 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 yourh1                                 company or group.e  G         6. Advanced Server      PRIMARY, to designate the server as theo#         role:                   PDCnH                                 BACKUP, to designate the server as a BDCD                                 MEMBER, to designate the server as a.                                 member server.C                                 For more information on configuringSA                                 the domain role, see Section 3.7, F                                 Configuring the Advanced Server Domain%                                 Role..  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)  H                                     Configuring the Advanced Server 3-23 a  d      $      Configuring the Advanced Server4      3.6 How to Change Server Configuration Settings  E      Table_3-2_(Cont.)_Configuration_Settings________________________e  E      Setting_________________Possible_Values_________________________   D      7. Advanced Server      A computer name of up to 15 characters.E      computer name:          Press the Return key to use the default.oB                              If this is the first time running theD                              configuration procedure, the default is8                              your system's SCSNODE name.  B      7a. Advanced Server     The Advanced Server cluster alias forE      OpenVMS Cluster         the OpenVMS Cluster to which your servera%      alias:[3]               belongs.sE                              Press the Return key to use the default.a@                              If DECnet is configured to run, theA                              default is the DECnet cluster alias. D                              If DECnet is not configured to run, the7                              default is nodename_ALIAS.t  A      8. Server announce      A text string of up to 48 characters_A      comment:                that the server uses to announce itse5                              presence on the network.tE                              Press the Return key to use the default._  D      9. Advanced Server      The option number of the language to beE      language:               used by the Advanced Server. The default .                              is English (USA).E                              Press the Return key to use the default. @                              For more information on configuringB                              the server language, see Section 3.8,=                              Configuring the Server Language.   @      10. Enable NT style     YES, to enable remote management of=      printing:               server printers from Windows NT. D                              NO, to use the default, managing serverC                              printers locally, using the ADMINISTERu/                              command interface.s@                              For more information on configuring?                              Windows NT printer management, seev@                              Section 3.9, Configuring Windows NT0                              Printer Management.-      [3]Displayed only in an OpenVMS Cluster.d  E      ________________________________________________________________t  )      3-24 Configuring the Advanced Serveri d  c      H                                          Configuring the Advanced ServerH                          3.7 Configuring the Advanced Server Domain Role  7         3.7 Configuring the Advanced Server Domain Role   C               Depending on the domain type, the Advanced Server can D               participate in a domain as either the PDC, a BDC, or a               member server.  G               There are three kinds of domains that the Advanced Servere!               may participate in:u  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  C               o  Windows 2000 native-mode domains (also referred to F                  as a pure Windows 2000 domains), which are domains inG                  which all domain controllers are Windows 2000 systems; H                  Advanced Servers can participate as member servers only  G               Table 3-3, Server Roles in Each Type of Domain, lists for @               each type of domain the roles the server can take:  H               Table_3-3_Server_Roles_in_Each_Type_of_Domain_____________                 For DomainE               Type:         The Advanced Server Can Take These Roles: H               ______________PDC__BDC__Member_Server_____________________  '               Windows NT    X    X    X   '               Windows 2000       X    X                Mixed-Mode  '               Windows 2000            XrH               Native-Mode_______________________________________________  ?               Each Windows NT domain must have one PDC. The PDCpF               stores the domain's master copy of the security accounts               database.h    H                                     Configuring the Advanced Server 3-25           $      Configuring the Advanced Server4      3.7 Configuring the Advanced Server Domain Role  ?            When you install the Advanced Server to create a newS?            Windows NT domain, the new server becomes the PDC byn@            default. When you install server software and specifyD            an existing domain name, the server can join the existing1            domain only as a BDC or member server.   C            A domain does not have to have BDCs, but one or more are_A            recommended. A BDC keeps a copy of the domain's master ?            security accounts database. The copy of the security @            accounts database stored on BDCs is synchronized with@            the PDC's master database. PDCs and BDCs can validate(            logon requests in the domain.  @            A member server does not store a copy of the domain'sA            security accounts database and does not validate logon A            requests. Member servers rely on domain controllers to D            validate credentials of users requesting access to memberD            server shares. The advantages of configuring the AdvancedA            Server as a member server are listed in Section 3.7.1, >            Configuring the Advanced Server As a Member Server.  D            In an OpenVMS Cluster, all nodes on the cluster must haveA            the same role. If you change the role of one node, the B            other nodes are automatically changed to the same role.  ?            When you configure the Advanced Server for the firstd@            time, you select the role your server will perform inA            the domain. There may be times when you need to change @            the role of your server. The method you use to changeC            the server depends on the current role of the server and @            the role you want to change it to. To change the role@            of the server from a BDC to a PDC, or vice versa, use@            the ADMINISTER SET COMPUTER/ROLE command. To change aC            server BDC to a member server, you must use PWRK$CONFIG,oB            as explained in Section 3.7.1, Configuring the AdvancedA            Server As a Member Server. To change a PDC to a member D            server, you must first promote another BDC to a PDC; thenD            the original PDC is demoted automatically to a BDC, afterA            which you can use PWRK$CONFIG to change it to a memberrD            server. Use PWRK$CONFIG also to change a member server toE            a BDC. (This restriction is similar (but less restrictive) E            to that of Windows NT, which requires the operating systemd?            to be reinstalled to change a domain controller to aeA            member server, or vice versa.) For more information onp?            changing the role of the server from a BDC to a PDC,s  )      3-26 Configuring the Advanced Serveru n  h      H                                          Configuring the Advanced ServerH                          3.7 Configuring the Advanced Server Domain Role  D               or vice versa, refer to the Compaq Advanced Server forF               OpenVMS Server Administrator's Guide. Table 3-4, MethodsF               for Changing Server Roles, summarizes which role changes8               are allowed and disallowed by PWRK$CONFIG.    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 PDCe  /               BDC      Member   Use PWRK$CONFIG   H               Member   PDC      Use PWRK$CONFIG to change this server toF                                 a BDC, and then use the ADMINISTER SETH                                 COMPUTER/ROLE command to promote the BDC(                                 to a PDC  /               Member   BDC      Use PWRK$CONFIG   C               PDC      BDC      Use ADMINISTER SET COMPUTER/ROLE to H                                 promote a BDC in the domain to PDC; thisG                                 promotion demotes the original PDC to as#                                 BDC   C               PDC      Member   Use ADMINISTER SET COMPUTER/ROLE tosF                                 promote an existing BDC to a PDC; thisB                                 promotion demotes the PDC to a BDCE                                 so that you can change it to a memberyH               __________________server,_using_PWRK$CONFIG_______________  E                 ______________________ Caution ______________________   <                 If you reconfigure a BDC as a member server,<                 PWRK$CONFIG automatically removes the domain:                 controller's domain user account database.  <                 If you reconfigure a member server to a BDC,<                 PWRK$CONFIG automatically removes the member5                 server's local user account database..  >                 In either case, because of loss of local group>                 information, access to some resources might be?                 affected. If resource permissions have been setn?                 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  H                                     Configuring the Advanced Server 3-27           $      Configuring the Advanced Server4      3.7 Configuring the Advanced Server Domain Role  >               permissions will remain in effect after the role               change.   C               _____________________________________________________e  =      3.7.1 Configuring the Advanced Server As a Member Server   =            Use the PWRK$CONFIG.COM configuration procedure torC            configure the Advanced Server to participate in a domainc@            as a member server. You cannot use the ADMINISTER SETA            COMPUTER/ROLE command to change an Advanced Server for B            OpenVMS domain controller to a member server role or to>            change a member server to a domain controller role.  C            You can configure the Advanced Server as a member servert@            if it is joining an existing domain that has a PDC inE            operation. If the domain consists of a native-mode Windows D            2000 environment (also referred to as a pure Windows 2000C            domain, this is a domain in which all domain controllersrC            are Windows 2000 systems), the domain must first includemE            at least one domain controller before you can configure an .            Advanced Server as a member server.  E            You may want to configure your Advanced Server for OpenVMSuB            as a member server instead of a BDC (or PDC) for any of!            the following reasons:_  ?            o  Member servers do not spend time validating logono@               requests. Thus, this role can be a good choice for?               servers that have heavy workloads or that perform ,               extremely time-critical tasks.  @            o  More important, configuring one or more servers as?               member servers rather than domain controllers can A               help decrease the network load, eliminating networksB               traffic normally generated by domain controllers forA               replicating user databases and authenticating logon E               requests. When a client attempts to find a logon server ?               to authenticate a request, all domain controllersA@               respond to the request. In some environments, this=               can generate a significant load on the network.o  >            o  Configuring the Advanced Server for OpenVMS as aE               member server allows the Advanced Server for OpenVMS to C               participate in a native-mode Windows 2000 environment 7               without interruption to that environment.   )      3-28 Configuring the Advanced Servern c  o      H                                          Configuring the Advanced ServerH                          3.7 Configuring the Advanced Server Domain Role  B               o  If in the future your Advanced Server for OpenVMSH                  server is moved to a different domain, it is simpler toG                  move it as a member server from one domain to another.   @               The next two sections explain how to configure theB               Advanced Server as a member server: Section 3.7.1.1,A               Configuring a New Advanced Server for OpenVMS to BehB               a Member Server, and Section 3.7.1.2, Configuring anB               Existing Advanced Server for OpenVMS BDC As a Member               Server.O  E         3.7.1.1 Configuring a New Advanced Server for OpenVMS to Be a                  Member Serverd  F               While installing a new Advanced Server for OpenVMS in anF               existing domain, you can configure it as a member serverE               during the PWRK$CONFIG.COM configuration procedure. ThevG               domain must include one active PDC; a native-mode WindowsnF               2000 domain must include at least one domain controller.  H               The following PWRK$CONFIG.COM output shows how an AdvancedG               Server for OpenVMS server might be configured as a membertF               server. Preceding this part of the procedure, item 5 wasD               selected to specify UPTIME as the domain. This exampleE               assumes the UPTIME domain is a native-mode Windows 2000:E               domain that already has one or more domain controllers.   4         Reading current configuration parameters ...  E           Your Advanced Server for OpenVMS is presently configured toc           run as follows:e  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:         YESr6            5.  Advanced Server domain:          UPTIME7            6.  Advanced Server role:            PRIMARY 6            7.  Advanced Server computer name:   GRATDAD            7a. Advanced Server OpenVMS Cluster alias:   GRATDA_ALIASK            8.  Server announce comment:    Advanced Server V7.3 for OpenVMS =            9.  Advanced Server language:        English (USA) 2            10. Enable NT style printing:        NOK         Enter item number, or RETURN to use these values [DONE]: 6 <Return>   H                                     Configuring the Advanced Server 3-29    R      $      Configuring the Advanced Server4      3.7 Configuring the Advanced Server Domain Role  G        The Advanced Server role is the part the server will play in its         domain.  E        A primary domain controller maintains the domain's master userr.        accounts database and validates logins.  I        A backup domain controller receives copies of the master database,s8        validates logins, and can be promoted to primary.  E        A member server does not receive copies of the master database G        or validate logins.  It relies on domain controllers to validate         user credentials.  C      Enter the role of this server (P)rimary/(B)ackup/(M)ember [P]:m      M <Return>   A        Before joining a domain, the computer must be added to the)3        domain. This can be done in one of two ways:h  D            - the administrator of the domain uses the administrative9              tools to add this computer to the domain, or   C            - the computer is added automatically by this procedure; B              you must supply an administrator account and passwordL      Are you going to supply account/password information [Y]/N YES <Return>  G      Enter the name of the primary domain controller for domain UPTIME:       SUNDA <Return> J      Enter the name of the administrator account: [Administrator] <Return>G      Enter the account password in the required case:          <Return>t3      Re-enter to verify password:          <Return>e  9      Process NETBIOS created with identification 206010B5 ?      Process PWRK$NBDAEMON created with identification 206010B7 @      Process PWRK$KNBDAEMON created with identification 206010B9&      Confirming domain name with SUNDA6      Successfully retrieved domain name from SUNDA ...  B        Your Advanced Server for OpenVMS is presently configured to        run as follows:          )      3-30 Configuring the Advanced Server            H                                          Configuring the Advanced ServerH                          3.7 Configuring the Advanced Server Domain Role  2            1.  Run the License Server:          NO2            2.  Enable Timesource service:       NO3            3.  Enable Alerter service:          YESd=            3a. Alert user names:                Administrator 3            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_ALIASK            8.  Server announce comment:    Advanced Server V7.3 for OpenVMSr=            9.  Advanced Server language:        English (USA)e2            10. Enable NT style printing:        NOI         Enter item number, or RETURN to use these values [DONE]: <Return>   4         Saving parameters to the OpenVMS Registry...!         Creating SAM datafiles...E            .            .            .?            The Advanced Server Administrator account is used toc<            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 longaA            and the case of the characters used will be preserved._  N         Enter a password for this Member Server's local Administrator account:         <Return>  -         Re-enter to verify password: <Return>i  6         Changing password for Administrator account...  D         Setting character set information in databases as needed ...  @            ... Setting share database character set information.>            ... Setting ACL database character set information.$         Checking system resources...              H                                     Configuring the Advanced Server 3-31 a  d      $      Configuring the Advanced Server4      3.7 Configuring the Advanced Server Domain Role  D      3.7.1.2 Configuring an Existing Advanced Server for OpenVMS BDC              As a Member Servern  B            When you configure a BDC to become a member server, theD            script is similar to the one for configuring a new serverD            as a member server. One exception is that the script will'            display the following lines:D  =       Changing from backup domain controller to member servernF       results in the re-creation of the Advanced Server SAM databases.G       If there is any problem with the configuration, your existing SAMa!       databases will be restored.0  A            The BDC's domain-wide account database is removed, andmA            the member server's local database is created. Server-yA            specific data is retained from the BDC's database. Thee@            configuration procedure saves the domain-wide accountB            database in case you need to restore it later (for moreB            information, see Section 3.10.3, If Problems Occur When.            Reconfiguring the Advanced Server).  =            The following two displays show the role of server C            LIONHEART before and after reconfiguration to the membereA            server role. The display symbol for a member server isM            [SV].  %      LANDOFOZ\\TINMAN> SHOW COMPUTERS   $      Computers in domain "LANDOFOZ":9      Computer       Type                      DescriptionrK      -------        ------------------------  ----------------------------- N      [PD] TINMAN    OpenVMS (NT 4.0) Primary  Advanced Server V7.3 for OpenVMS  N      [BD] LIONHEART OpenVMS (NT 4.0) Backup   Advanced Server V7.3 for OpenVMS  O      [BD] DOROTHY   OpenVMS (NT 3.51) Backup  Advanced Server V7.2A for OpenVMSn          Total of 3 computersb        [reconfigure server role]      .      .      .%      LANDOFOZ\\TINMAN> SHOW COMPUTERSa  $      Computers in domain "LANDOFOZ":9      Computer       Type                      Description K      -------        ------------------------  -----------------------------rN      [PD] TINMAN    OpenVMS (NT 4.0) Primary  Advanced Server V7.3 for OpenVMS  )      3-32 Configuring the Advanced Servere c  t      H                                          Configuring the Advanced ServerH                          3.7 Configuring the Advanced Server Domain Role  O       [SV] LIONHEART OpenVMS (NT 4.0) Server   Advanced Server V7.3 for OpenVMSo  P       [BD] DOROTHY   OpenVMS (NT 3.51) Backup  Advanced Server V7.2A for OpenVMS             Total of 3 computers  +         3.8 Configuring the Server Languager  @               By default, the language of the Advanced Server isC               "English (USA)". You can configure any one of over 40sG               languages for the Advanced Server. For an up-to-date listeC               of the languages officially supported by the AdvancedtF               Server, refer to the Software Product Description (SPD).  :         3.8.1 Considerations Regarding the Server Language  @               Consider the following when configuring the server               language:   C               o  The same language should be used by all servers ineC                  a domain. All Advanced Servers in the same clustercF                  automatically share the same language (they share theF                  same registry database where the language is stored).  E               o  Although you can change the server's language at any B                  time (after stopping the Advanced Server), CompaqH                  recommends that once a choice is made, you do not alter                  that choice.t  @                  Certain objects might exist whose names includeE                  characters that are not included in the new languageDE                  that you select. For example, after you select a newoF                  language, PWRK$CONFIG might convert (depending on theC                  language) all text strings in the Security AccountaD                  Manager (SAM), access control list (ACL), and shareG                  databases from the old character set (for the previouscA                  language) to the new set (for the new language).i  A                  If one or more of these databases are converted,r<                  PWRK$CONFIG displays the following message:  L                  Setting character set information in databases as needed...  B                  In addition, a message will be displayed for each,                  database affected, such as:  F                  ... Setting share database character set information.  H                                     Configuring the Advanced Server 3-33 e  r      $      Configuring the Advanced Server(      3.8 Configuring the Server Language  <               If any of these databases contain text strings=               that cannot be converted (that is, object names ?               that contain characters not included in the newly_A               configured Advanced Server language character set),_=               the PWRK$CONFIG procedure reverts to the set ofSA               databases that existed prior to conversion attempt.eC               Error messages will indicate the names that could not E               be converted, and the language is reset to the originaleD               language. You must rename (or remove) the objects thatB               cannot be converted, and rerun PWRK$CONFIG to change               the language.   E               Note that for some languages, PWRK$CONFIG does not needID               to convert the text strings in the databases mentionedD               above - it changes the client code page value only. (AB               client code page is an ordered set of 256 charactersA               that extends the limits of ASCII (American Standard A               Code for Information Interchange) character sets to A               support the variety of characters used in languages ?               internationally. Each language-specific code page A               overlays the same set of 8-bit values. For example, @               a specific 8-bit value in a code page used for theE               English language can be used for another character used_)               for the Cyrillic language.)u  5      3.8.2 Example of Configuring the Server Language   B            During the PWRK$CONFIG.COM configuration procedure, youC            can configure an Advanced Server language other than the A            default by selecting option 9. The procedure lists the E            configurable languages. At the prompt, enter the number of (            the language you want to use.  ;            In the following example, the Hebrew language is 0            configured (character set ISO8859-8).  B        Your Advanced Server for OpenVMS is presently configured to        run as follows:              )      3-34 Configuring the Advanced Servero h         H                                          Configuring the Advanced ServerH                                      3.8 Configuring the Server Language  2            1.  Run the License Server:          NO2            2.  Enable Timesource service:       NO3            3.  Enable Alerter service:          YESe=            3a. Alert user names:                Administrator_3            4.  Enable Netlogon service:         YES78            5.  Advanced Server domain:          LANDOFOZ6            6.  Advanced Server role:            MEMBER9            7.  Advanced Server computer name:   LIONHEARTpG            7a. Advanced Server OpenVMS Cluster alias:   LIONHEART_ALIASIK            8.  Server announce comment:    Advanced Server V7.3 for OpenVMS =            9.  Advanced Server language:        English (USA) 2            10. Enable NT style printing:        NOK         Enter item number, or RETURN to use these values [DONE]: 9 <Return>r  C         ******************** W A R N I N G ************************ A         Although you can change the server's language at any timei?         (after stopping the Advanced Server), Compaq recommendsiA         that once a choice is made, you do not alter that choice. B         Certain objects might exist whose names include charactersB         that are not included in the new language that you select.@         Error messages will indicate the names that could not beA         converted, and the language will be reset to the originalp>         language. If you want to change the language, you must;         first rename (or remove) the objects that cannot beo@         converted, and rerun PWRK$CONFIG to change the language.D         ***********************************************************"E         Do you want to continue with item number 9 (Y/[N]) Y <Return>lG          1) Afrikaans           16) French               31) PortugueserP          2) Albanian            17) French (Ca. MS-DOS)  32) Portuguese (MS-DOS)E          3) Basque              18) German               33) Romanian D          4) Belarussian         19) Greek                34) RussianO          5) Bulgarian           20) Greek (IBM)          35) Serbian (Cyrillic)uL          6) Catalan             21) Hebrew               36) Serbian (Latin)C          7) Croatian            22) Hungarian            37) SlovakeF          8) Czech               23) IBM Cyrillic         38) SlovenianD          9) Danish              24) Icelandic            39) SpanishD         10) Dutch               25) Icelandic (MS-DOS)   40) SwedishD         11) English (USA)       26) Indonesian           41) TurkishF         12) English (USA)+Euro  27) Italian              42) UkrainianL         13) English (Other)     28) Nordic L. (MS-DOS)   43) Western Europe+A         14) Faeroese            29) Norwegian                Euror*         15) Finnish             30) Polish      H                                     Configuring the Advanced Server 3-35 e  r      $      Configuring the Advanced Server(      3.8 Configuring the Server Language  H        The Advanced Server language specifies the internal character setC        encoding for strings, character casing rules, and the client         code page.d  N      Enter Advanced Server language by number for this cluster [English(USA)]:      21 <Return>  B        Your Advanced Server for OpenVMS is presently configured to        run as follows:  /         1.  Run the License Server:          NOb/         2.  Enable Timesource service:       NOf0         3.  Enable Alerter service:          YES:         3a. Alert user names:                Administrator0         4.  Enable Netlogon service:         YES5         5.  Advanced Server domain:          LANDOFOZm3         6.  Advanced Server role:            MEMBERM6         7.  Advanced Server computer name:   LIONHEARTD         7a. Advanced Server OpenVMS Cluster alias:   LIONHEART_ALIASH         8.  Server announce comment:    Advanced Server V7.3 for OpenVMS3         9.  Advanced Server language:        Hebrew /         10. Enable NT style printing:        NOcF      Enter item number, or RETURN to use these values [DONE]: <Return>  2      3.9 Configuring Windows NT Printer Management  @            By default, printers shared by the server are managed?            locally using the ADMINISTER user interface. You cantE            configure the server to support management of the printersrD            from Windows NT. This allows you to take advantage of theD            Windows NT style of printer management, using the WindowsB            NT print services dialog boxes, such as the Add Printer&            wizard for adding printers.  ?            Administrators can then store the latest drivers fort@            the printers on the Advanced Server. When new driversB            are distributed, administrators have to update a singleB            location only. When client users set up printers to useA            from their workstations, they are able to download the 4            appropriate printer driver automatically.  >            Before configuring your sever to support Windows NTC            printer management, be sure to familiarize yourself with D            the considerations noted in Section 3.9.1, Considerations3            Regarding Windows NT Printer Management.a  )      3-36 Configuring the Advanced Server            H                                          Configuring the Advanced ServerH                            3.9 Configuring Windows NT Printer Management  D         3.9.1 Considerations Regarding Windows NT Printer Management  E               Consider the following before choosing to configure themE               Windows NT style of printer management. When you enable ,               Windows NT printer management:  E               o  Only limited functionality is available for managingtD                  printers with the ADMINISTER interface. (Similarly,E                  when the default printer management style is enabledlH                  (using the ADMINISTER interface), limited functionalityD                  is available for managing the printers from Windows                  NT.)   C               o  Printers or print queues that were already definedoA                  on the server are upgraded automatically so thateG                  clients can continue to share these printers and theiriG                  queues. However, management of these upgraded printersuA                  from Windows NT is limited. To gain full WindowssD                  NT management functionality for these printers, useE                  Windows NT print services to delete the printers andrH                  then to add the printers back onto the Advanced Server.  F                 ________________________Note  ________________________  D                 When running PWRK$CONFIG to reconfigure the AdvancedC                 Server, printers that have been upgraded previouslya'                 are not upgraded again.N  E                 _____________________________________________________e  E               o  Once you configure the Windows NT printer management G                  style, if you decide to reconfigure your server to thecE                  default local printer management style, all printers:D                  will be unusable. You will have to perform several,H                  time-consuming tasks to make printers functional again.  A               o  Be sure to refer to the Advanced Server V7.3 foro>                  OpenVMS Release Notes for more information onF                  restrictions regarding Windows NT printer management.            H                                     Configuring the Advanced Server 3-37           $      Configuring the Advanced Server2      3.9 Configuring Windows NT Printer Management  ?      3.9.2 Example of Configuring Windows NT Printer Management   B            During the PWRK$CONFIG.COM configuration procedure, you?            can configure Windows NT style printer management by @            selecting option 10. The procedure displays a warningD            and asks you if you are sure you want to make the change,-            as shown in the following example:   B        Your Advanced Server for OpenVMS is presently configured to        run as follows:  /         1.  Run the License Server:          NOi/         2.  Enable Timesource service:       NO 0         3.  Enable Alerter service:          YES:         3a. Alert user names:                Administrator0         4.  Enable Netlogon service:         YES5         5.  Advanced Server domain:          LANDOFOZ 3         6.  Advanced Server role:            MEMBER 6         7.  Advanced Server computer name:   LIONHEARTD         7a. Advanced Server OpenVMS Cluster alias:   LIONHEART_ALIASH         8.  Server announce comment:    Advanced Server V7.3 for OpenVMS:         9.  Advanced Server language:        English (USA)/         10. Enable NT style printing:        NOnI      Enter item number, or RETURN to use these values [DONE]: 10 <Return>t  @      ******************** W A R N I N G ************************B      Before enabling this feature, make sure you are familiar withE      the Windows NT printer management restrictions documented in therG      Release Notes. Note that once you configure the Windows NT printer D      management style, if you reconfigure your server to the defaultG      local printer management style, all printers will be unusable. You G      will have to perform several time-consuming tasks to make printers       functional again.A      ***********************************************************" $      Are you sure you want to enable6      Windows NT printer management? [Y/[N]] Y <Return>  -      10. Enable NT style printing: Y <Return>i              )      3-38 Configuring the Advanced Serverr i  o      H                                          Configuring the Advanced ServerH                    3.10 Troubleshooting Configuration Procedure Problems  =         3.10 Troubleshooting Configuration Procedure Problems   ,               This section describes how to:  >               o  Troubleshoot Registry Server startup problems  A               o  Ensure sufficient resources will be available toi                   support clients  /         3.10.1 Registry Server Startup Problems   G               For proper operation of the PWRK$CONFIG.COM configuration F               procedure and the file server, registry services must beB               available on the system running the Advanced Server.  E               In an OpenVMS Cluster environment, the OpenVMS RegistrybD               can be configured so that the Registry Server does notB               run on the server node but rather on another node inF               the cluster. However, Compaq recommends that the OpenVMSH               Registry be configured to run the Registry Server on everyG               Advanced Server node. This ensures that registry services C               are available to the file server. For instructions on @               starting the Registry Server and enabling registryD               services, see Section 1.8.5, Step 5: Start the OpenVMS               Registry Server.  L               o  If registry services are not available, the PWRK$CONFIG.COMA                  procedure attempts to start the OpenVMS Registry D                  Server. If the attempt is successful, the procedure0                  displays the following message:  O                  Checking to see if the OpenVMS Registry Services are availablec                  ...N                  %RUN-S-PROC_ID, identification of created process is 0000023B  @               o  If the SYS$REGISTRY logical is not defined, theC                  OpenVMS Registry will not start. In this case, theMD                  PWRK$CONFIG.COM displays the following messages and                  terminates:  E         Checking to see if OpenVMS Registry Services are available...   B             SYS$REGISTRY must be defined to start the VMS Registry  M         %PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for thisg          systemaH         %PWRK-F-CONFIGERR, severe error encountered during configuration  G             OpenVMS Registry Services are not available on this system.r  H                                     Configuring the Advanced Server 3-39 e  a      $      Configuring the Advanced Server:      3.10 Troubleshooting Configuration Procedure Problems  H          Some file server parameters are stored in the OpenVMS Registry.J          For the file server or file server utilities to be able to accessF          these parameters, OpenVMS Registry Services must be available          on this system.  G          Since the file server requires access to the OpenVMS Registry,eD          it is recommended that OpenVMS Registry Services be startedG          as part of system start-up, before the file server is started.iC          For instructions on how to start OpenVMS Registry Services 7          please refer to the file server release notes.e  >          This configuration is incomplete and cannot continue.8          You must execute @SYS$UPDATE:PWRK$CONFIG again.H          Please configure and start the OpenVMS Registry Services before          doing so.  =               You must enable registry services and start then;               Registry Server, then run the PWRK$CONFIG.COM,B               procedure again. For more information about enabling<               and starting the Registry Server, refer to the<               OpenVMS System Manager's Manual or the OpenVMSE               Connectivity Developer's Guide (included in the OpenVMSh$               Documentation CD-ROM).  <      3.10.2 Ensuring Sufficient Resources to Support Clients  =            The Advanced Server requests the resources that ita>            needs using the OpenVMS AUTOGEN utility. If AUTOGENE            underestimates the resources required for use by processes C            other than the Advanced Server, and these resources haverE            already been consumed when the Advanced Server is started,SD            there may be insufficient resources left for the Advanced;            Server to support the desired number of clients.j  >            To ensure sufficient resource allocation to support=            clients, make sure that all software that will runh=            concurrently with the Advanced Server is installed =            and started before you run the the Advanced ServeroB            configuration procedure (PWRK$CONFIG.COM). If TCP/IP isE            selected as a transport, make sure that the TCP/IP producte>            is loaded before you run the PWRK$CONFIG procedure.        )      3-40 Configuring the Advanced Server  v  e      H                                          Configuring the Advanced ServerH                    3.10 Troubleshooting Configuration Procedure Problems  C               After you successfully configure the Advanced Server,bE               it may not start, reporting that there are insufficienteE               resources to support any clients. In this case, examinetF               the following file to determine the system resource thatG               needs to be increased (nodename is the name of the servert               node):  6               PWRK$LOGS:PWRK$CONFIG_ERROR_nodename.LOG  F               To increase the resource, make the appropriate modifica-C               tions to the MODPARAMS.DAT file and then run AUTOGEN.s  G         3.10.3 If Problems Occur When Reconfiguring the Advanced Serverr  D               If you reconfigure a previously configured server, theE               PWRK$CONFIG command procedure creates subdirectories inIH               the PWRK$LMDOMAINS: and PWRK$LMDATAFILES: directories, and@               stores the original accounts database files there.  G               The names of the subdirectories are based on the date and F               time, such as 16JUN200014314818.DIR, indicating that theH               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.t  0         3.11 The Advanced Server Network Adapter  A               The PWRK$CONFIG configuration might need to use the D               network to communicate with the PDC. If the system hasB               more than one network adapter (also referred to as aA               network interface card), the default adapter chosenrD               by PWRK$CONFIG might not be the correct interface. Or,B               on some newer systems, the Advanced Server might notG               recognize the only network adapter present. In cases suchLE               as these, you can define system logical names to directoD               the Advanced Server to use a specific interface. If noD               such logical is defined, PWRK$CONFIG selects the firstD               adapter (alphabetically) defined on your system from a%               list of known adapters.G  H                                     Configuring the Advanced Server 3-41 g  t      $      Configuring the Advanced Server-      3.11 The Advanced Server Network Adaptero  E            If the server has access to more than one network adapter,eA            and you do not want to use the adapter selected, or ift@            the system has a network adapter that is not found or>            recognized by the Advanced Server, you can manually@            specify the network adapter to use with the transport            you specified.h  1      3.11.1 Manually Defining the Network Adapter)  B            To manually define the network adapter to be used for a1            specific protocol, follow these steps:*  B            1. Use the DCL DEFINE/SYSTEM command to define a systemA               logical name that specifies the network adapter, as A               shown in the following examples. Table 3-5, OpenVMSaA               Network Adapter Logicals, lists the OpenVMS logical D               name that you can use for each transport. You must addD               the appropriate logicals to SYS$MANAGER:SYLOGICALS.COM5               to have them available after rebooting.   !            2. Restart the server:   )               $ @SYS$STARTUP:PWRK$STARTUP3  E            Table_3-5_OpenVMS_Network_Adapter_Logicals________________   E            Logical_Name____________________Transport_________________3  1            NETBIOS$DEVICE                  DECnetl  1            PWRK$KNBDAEMON_DEVICE           TCP/IP   E            PWRK$NETBEUI_DEVICE_____________NetBEUI___________________   D            The following examples show how to define the appropriate>            network adapter for the DECnet, TCP/IP, and NetBEUI$            transports, respectively:  @            o  To specify adapter EWA0: for the DECnet transport,*               enter the following command:  2               $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:  @            o  To specify adapter ESA0: for the TCP/IP transport,*               enter the following command:  )      3-42 Configuring the Advanced Servere e  r      H                                          Configuring the Advanced ServerH                                 3.11 The Advanced Server Network Adapter  <                  $ 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 thefA                 Advanced Server, make sure the adapter you selectrB                 corresponds to the first adapter listed in the TCP)                 /IP local hosts database.c  E                 _____________________________________________________   D               o  To specify adapter ESA1: for the NetBEUI transport,-                  enter the following command:l  :                  $ 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:n7               $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0:t  F                 ________________________Note  ________________________  C                 The names of adapters defined by use of the logicaltA                 names PWRK$NETBEUI_DEVICE, PWRK$KNBDAEMON_DEVICE,wD                 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 notr!                 operate properly.   E                 _____________________________________________________e  =         3.11.2 What to Do If the Network Adapter Is Not Founda  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 ofhF               the failing processes (NETBIOS, which is always present,F               and PWRK$KNBDAEMON and PWRK$NBDAEMON, if present) writesD               an error message to its log file. Table 3-6, Undefined  H                                     Configuring the Advanced Server 3-43 b  r      $      Configuring the Advanced Server-      3.11 The Advanced Server Network Adapteru  B            Adapter Messages, shows each process, the log file thatC            records the error message from the process, and examples ?            of the text of the error message. In the examples in E            Table 3-6, the server node name is MYNODE. All three error B            messages have the same meaning: that no such device was            found by the server.     E      Table_3-6_Undefined_Adapter_Messages____________________________   E      Process__________Log_File_Name__________________________________o  9      PWRK$KNBDAEMON   PWRK$LOGS:PWRK$KNBDAEMON_MYNODE.LOG   
      Message:c  C      Tue Mar 24 13:13:50 2000 get_phys_addr: Failed to get EthernetwE      device_characteristics__________________________________________d  8      PWRK$NBDAEMON    PWRK$LOGS:PWRK$NBDAEMON_MYNODE.LOG  
      Message:t  E      Tue_Mar_24_13:13:50_2000_Failed_to_open_datalink________________c  2      NETBIOS          PWRK$LOGS:NETBIOS_MYNODE.LOG  
      Message:r  A      %NB-W-ERRSIGNAL, exceptional conditional detected at 24-Mar-_      2000 13:13:50.00_E      -SYSTEM-W-NOSUCHDEV,_no_such_device_available___________________   ?            If you find any of the messages listed in Table 3-6,dD            define the network adapter for the appropriate processes,C            using the procedure outlined in Section 3.11.1, Manually C            Defining the Network Adapter. For example, if the server >            reported an unknown device, enter the DEFINE/SYSTEM>            commands to define the appropriate adapter for each"            protocol on the server.        3.12 Next Steps  E            You can start the Advanced Server automatically as part ofn'            the configuration procedure.   E            If you are ready to start the server, see Chapter 5, AfterV=            You Install the Advanced Server, for instructions.r  )      3-44 Configuring the Advanced Servern                       H                                                                        4H         ________________________________________________________________  H                   Configuring and Starting the Standalone License Server      G               The License Server is a software program that you can runu@               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:o  6               o  Section 4.1, About the License Server  ?               o  Section 4.2, Before You Begin to Configure theu*                  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  H               The Advanced Server for OpenVMS 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- @               based licenses. The same License Server can manageF               licenses for client access to any of the following types               of file servers:  H               Configuring and Starting the Standalone License Server 4-1 e  i      ;      Configuring and Starting the Standalone License Server*!      4.1 About the License Server   4            o  PATHWORKS V5 for OpenVMS (LAN Manager)  8            o  PATHWORKS V6 for OpenVMS (Advanced Server)  )            o  Advanced Server for OpenVMS3  ?            The License Server included with Advanced Server for A            OpenVMS will not issue or manage PATHWORKS for OpenVMS @            (NetWare) licenses. If you have clients using NetWareD            networking software, maintain the existing version of theD            License Server on a different system from the one that is'            running the Advanced Server.   .            You can install the License Server:  1            o  Separately from the Advanced Server   5            o  In conjunction with the Advanced Server   C            Compaq recommends that you install the License Server on C            a designated OpenVMS system without the Advanced Server. D            Therefore, the Advanced Server for OpenVMS kit allows youC            to install the standalone License Server separately from B            the file server. Alternatively, you can run the LicenseA            Server on an OpenVMS Cluster with the Advanced Server, E            where cluster failover provides reliability. (You can also C            run the License Server on an OpenVMS Cluster without they            Advanced Server.)  @            In an OpenVMS Cluster, the PAKs must be loaded into a?            shared license database. For detailed information onrA            managing licenses, refer to the Compaq Advanced ServercB            for OpenVMS Guide to Managing Advanced Server Licenses.  D      4.2 Before You Begin to Configure the Standalone License Server  B            You install the standalone License Server from the sameD            software kit that you use to install the Advanced Server.@            The procedures are described in Chapter 2, Installing0            Advanced Server for OpenVMS Software.          ?      4-2 Configuring and Starting the Standalone License Server  U  -      H                   Configuring and Starting the Standalone License ServerH                            4.3 Configuring the Standalone License Server  5         4.3 Configuring the Standalone License ServerP  A               You must configure the standalone License Server totD               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 followingo               transports:                  o  DECnet-                 o  NetBEUI                 o  TCP/IPi  D               Because the License Server supports all these types ofG               transports, the startup and shutdown procedures have beenrG               carefully designed to prevent unexpected interruptions inrE               service. You can start and shut down the License ServerrG               using the file server command procedures PWRK$STARTUP.COM G               and PWRK$SHUTDOWN.COM. For more information on starting amF               standalone License Server, see Section 4.6, How to Start,               the Standalone License Server.  J               The following table shows details about the PWRK$STARTUP.COM               procedure:  H               __________________________________________________________               If the               following isH               configured_______Then_the_following_is_started____________  /               DECnet           DECnet transport   0               NetBEUI          NetBEUI transport  /               TCP/IP           TCP/IP transportn  H               DECnet           DECnet transport for Advanced Server mail+                                notificationt  H               License_Server___License_Server_component_________________  &         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.  H               Configuring and Starting the Standalone License Server 4-3 n  i      ;      Configuring and Starting the Standalone License Servere#      4.4 Configuring the Transportsi  B            After the installation procedure completes, the OpenVMS=            system prompt ($)  is displayed. If the system wass+            rebooted following installation:e  B            1. Ensure that you are logged in to the SYSTEM account.  <            2. Start the configuration procedure by entering:  '               $ @SYS$UPDATE:PWRK$CONFIG   3            3. Respond to the configuration prompts.   ?      4.5 How to Respond to License Server Configuration Prompts   A            Table 4-1, License Server Configuration Prompts, tells E            you how to respond to the prompts displayed by PWRK$CONFIGs<            when you configure the standalone License Server.  C               ________________________Note ________________________e  ?               Table 4-1 shows only the prompts that PWRK$CONFIG :               displays; it does not show any informational;               messages. For a complete sample configuration ?               script, see Appendix C, Sample Standalone Licenser4               Server Installation and Configuration.  C               _____________________________________________________t  E      Table_4-1_License_Server_Configuration_Prompts__________________e  2      At this            If you want the configura-E      prompt_._._._______tion_procedure_to_._._.______Enter_._._._____t  =      Enter disk device  Copy the server on-disk      <Return>n0      name where         structure to the default+      the Advanced       OpenVMS disk deviceW!      Server data files  displayed /      will be stored     (If you ran PWRK$CONFIGo/      [default_device]:  previously, the defaultA  2                         disk device is the one you3                         specified the last time your/                         configured the server.)u  E                                              (continued on next page)r  ?      4-4 Configuring and Starting the Standalone License ServerK D  F      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__________  5         At this            If you want the configura-0H         prompt_._._._______tion_procedure_to_._._.______Enter_._._._____  C                            Copy the Advanced Server     device_namel/                            on-disk structure to 1                            an OpenVMS disk deviceo5                            different from the defaults$                            displayed  @         Do you want to     Allow licenses to be served  <Return>&         serve client-      over DECnet         based licenses         over DECnete         [YES]:[1]e  :                            Not allow licenses to be     NO-                            served over DECnet   ;         Do you want to     Allow licenses to be served  YES '         serve client-      over NetBEUI          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/IPg         [NO]:[1]  @                            Not allow licenses to be     <Return>-                            served over TCP/IPi  C         [1]Default answers may differ if you ran the License Servern+         configuration procedure previously.   H                                                 (continued on next page)    H               Configuring and Starting the Standalone License Server 4-5           ;      Configuring and Starting the Standalone License Server ?      4.5 How to Respond to License Server Configuration Prompts   E      Table_4-1_(Cont.)_License_Server_Configuration_Prompts__________i  2      At this            If you want the configura-E      prompt_._._._______tion_procedure_to_._._.______Enter_._._._____p  =      Do you want        Start the server au-         <Return>s-      to start the       tomatically after thet/      Advanced Server    configuration procedureS!      License Server     completes       now [YES]:a  7                         Complete the configuration   NO 2                         procedure without startingE      ___________________the_server___________________________________   3      4.6 How to Start the Standalone License Server   C            You can start the License Server in any of the followingO            ways:  A            o  During the configuration procedure, as described intE               Section 4.3, Configuring the Standalone License Server.   -            o  Manually from the command line._  1            o  Automatically each time you reboot._  3      4.6.1 How to Start the License Server ManuallyS  =            If you did not start the License Server during theIC            configuration procedure, you can start it manually usingt!            the following command:   &            $ @SYS$STARTUP:PWRK$STARTUP  ?            The License Server will use DECnet, NetBEUI, TCP/IP.I?            Process NETBIOS created with identification 0000011E E            Process PWRK$NBDAEMON created with identification 00000120nF            Process PWRK$KNBDAEMON created with identification 00000122F            Process PWRK$LICENSE_S created with identification 00000124            $        ?      4-6 Configuring and Starting the Standalone License ServerS e         H                   Configuring and Starting the Standalone License ServerH                           4.6 How to Start the Standalone License Server  ;         4.6.2 How to Start the License Server AutomaticallyE  G               To make sure that the License Server starts automatically_5               each time you boot your OpenVMS system:e  M               1. Edit the system startup file, SYS$STARTUP:SYSTARTUP_VMS.COM.b  C               2. Add the startup command, as shown in the followingcE                  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:STARTNETd                  $ ENDIF                  .                  .                  .  ,                  $ @SYS$STARTUP:PWRK$STARTUP  C         4.6.3 How to Start the License Server in an OpenVMS Cluster   C               If you installed and configured the License Server onKB               multiple members of the same OpenVMS Cluster, CompaqC               suggests that you use the SYSMAN utility to start the_H               server manually and simultaneously on all cluster members.               To do so:   G               1. Make sure that you are logged in to the SYSTEM account <                  on one of the nodes in the OpenVMS Cluster.  6               2. Start the SYSMAN utility by entering:  (                  $ RUN SYS$SYSTEM:SYSMAN  D               3. Define all the cluster members on which you want toE                  start the standalone License Server. For example, if F                  you want to start the License Server on nodes SPEEDY,C                  SPIN, and SPAN, enter the following at the SYSMAN>                   prompt:  @                  SYSMAN> SET ENVIRONMENT/NODE=(SPEEDY,SPIN,SPAN)  F               4. Start the License Server on the nodes you defined. AtA                  the SYSMAN> prompt, enter the following command:o  5                  SYSMAN> DO @SYS$STARTUP:PWRK$STARTUPa  H               Configuring and Starting the Standalone License Server 4-7 e n                     H                                                                        5H         ________________________________________________________________  H                                    After You Install the Advanced Server      D               This chapter describes tasks you can perform after youG               install the Advanced Server and consists of the following                sections:r  E               o  Section 5.1, Before You Begin Postinstallation Tasksl  H               o  Section 5.2, Verifying the Advanced Server Installation  :               o  Section 5.3, Starting the Advanced Server  ?               o  Section 5.4, Ways to Start the Advanced Servere  :               o  Section 5.5, Stopping the Advanced Server  @               o  Section 5.6, Special Advanced Server Management                  Commands_  @               o  Section 5.7, Setting Up External Authentication  F               o  Section 5.8, Converting Encoded File Names from ODS-2                  to ODS-5   G               o  Section 5.9, Installing Optional Server AdministrationE                  Tools  3         5.1 Before You Begin Postinstallation Tasksd  G               Before you start the Advanced Server, make sure you have:e  ?               o  Installed the Advanced Server, as described in_B                  Chapter 2, Installing Advanced Server for OpenVMS                  Software.  G               o  Completed the configuration procedure, as described in0<                  Chapter 3, Configuring the Advanced Server.  H                                After You Install the Advanced Server 5-1 d         *      After You Install the Advanced Server3      5.2 Verifying the Advanced Server Installationi  3      5.2 Verifying the Advanced Server Installationh  C            If the installation verification procedure (IVP) did notuB            run when you installed the Advanced Server, you can runA            it now (or anytime later) to make sure that the servere@            installed successfully. (When you specify the /NOTEST>            qualifier with the PRODUCT INSTALL command, the IVP#            procedure does not run.)   7            To run the IVP, enter the following command:   $            $ @SYS$TEST:PWRK$PCSI_IVP  E      ________________________________________________________________       If the       installa-   Then the IVP E      tion_._._.__displays_._._.________And_you_should_._._.___________  ;      Succeeded   The message: %PWRK-I-NORMAL, IVP completedo                  successfullyd  E                                        Start the server, as describedeC                                        in Section 5.3, Starting then7                                        Advanced Server.r  /      Failed      An error message, followed by: 0                  -PWRK-E-IVPFAIL, IVP has failed  A                                        Reinstall the software, asu>                                        described in Chapter 2,A                                        Installing Advanced ServerrE      __________________________________for_OpenVMS_Software._________r  %      5.3 Starting the Advanced Serverf  D            The following sections describe how to start the Advanced5            Server and how to automate server startup.s  ,      5.3.1 When to Start the Advanced Server  <            You must configure the Advanced Server before you=            can start it for the first time. After running thee>            configuration procedure, you can start and stop the'            Advanced Server at any time.O  .      5-2 After You Install the Advanced Server           H                                    After You Install the Advanced ServerH                                         5.3 Starting the Advanced Server  -         5.3.2 What the Startup Procedure Does-  $               The startup procedure:  3               1. Checks for the required privilegesh  ?               2. Verifies that required configuration files are                   available  H               3. Verifies that the server has been configured, and exits                  if it has not  >               4. If a reboot is required, verifies that it was3                  performed, and exits if it was notn  (               5. Loads transport drivers                  6. Installs images  3               7. Starts transport support processes   A               8. Starts the OpenVMS Registry Server, if necessary   /               9. Starts each of the components:   %                  o  License Registrard  2                  o  License Server (if configured)                    o  File server   F               10.Records a list of all Advanced Server parameters thatD                  are set in the OpenVMS Registry (see Section 5.4.5,E                  Determining Initial Advanced Server Parameter Valuesr0                  Stored in the OpenVMS Registry)  -         5.4 Ways to Start the Advanced Servera  0               You can start the Advanced Server:  D               o  During the configuration procedure, as described in;                  Chapter 3, Configuring the Advanced Servere  /               o  Manually from the command line   3               o  Automatically each time you rebootl  H                                After You Install the Advanced Server 5-3           *      After You Install the Advanced Server*      5.4 Ways to Start the Advanced Server  4      5.4.1 How to Start the Advanced Server Manually  >            If you did not start the Advanced Server during theE            configuration procedure, you can start it now by entering:v  &            $ @SYS$STARTUP:PWRK$STARTUP  B            The Advanced Server starts, and messages similar to the#            following are displayed:   <            The file server will use DECnet, NetBEUI, TCP/IP.=            Advanced Server mail notification will use DECnet.c?            Process NETBIOS created with identification 00000248iE            Process PWRK$NBDAEMON created with identification 0000024AoF            Process PWRK$KNBDAEMON created with identification 0000024CF            Process PWRK$LICENSE_R created with identification 0000024EL            Checking to see if the OpenVMS Registry Services are available...F            The Advanced Server is configured to support 20 PC clients.C            Process PWRK$MASTER created with identification 00000251 F            The master process will now start all other Advanced Server            processes.n  9      5.4.2 How to Start the Advanced Server Automaticallyn  E            To make sure that the Advanced Server starts automaticallytA            each time you boot your OpenVMS system, edit the site-oD            specific startup file, SYS$STARTUP:SYSTARTUP_VMS.COM. AddD            the Advanced Server startup command to the file below all<            lines that start network transports. For example:  !            $ START/NETWORK DECNET             .            .            .  &            $ @SYS$STARTUP:PWRK$STARTUP  A      5.4.3 How to Start the Advanced Server in an OpenVMS Clusterl  A            If you installed and configured the Advanced Server onv?            multiple members of the same OpenVMS Cluster, Compaq B            recommends that you use the SYSMAN utility to start theE            Advanced Server manually and simultaneously on all cluster             members.L  .      5-4 After You Install the Advanced Server           H                                    After You Install the Advanced ServerH                                    5.4 Ways to Start the Advanced Server  D               To start the Advanced Server on all cluster members atF               the same time, make sure you are logged in to the SYSTEMD               account on one of the member nodes, then run SYSMAN as               follows:  H         ________________________________________________________________H         Enter_this_command..._______To..._______________________________  =         $ RUN SYS$SYSTEM:SYSMAN     Start the SYSMAN utility.c  7         SYSMAN> SET ENVIRONMENT/NODE=(SPEEDY,SPIN,SPAN)p  F                                     Define the OpenVMS Cluster membersE                                     on which to start the server. For D                                     example, SPEEDY, SPIN, and SPAN.  ,         SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP  H                                     Start the Advanced Server on all theE                                     nodes you defined in the previous ,                                     command.  H         SYSMAN>_EXIT________________Exit_the_SYSMAN_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                 ______________________________________________________  )         5.4.4 Troubleshooting the Startup_  H               Some of the problems that prevent the Advanced Server from?               starting are discussed in the following sections:   C               o  Section 5.4.4.1, SYLOGIN.COM Contains Commands Notc0                  Suitable for Detached Processes  ?               o  Section 5.4.4.2, OpenVMS Registry Services Not                   Available)_  H                                After You Install the Advanced Server 5-5 t  _      *      After You Install the Advanced Server*      5.4 Ways to Start the Advanced Server  D      5.4.4.1 SYLOGIN.COM Contains Commands Not Suitable for Detached              Processes  <            Advanced Server processes are detached processes.>            During startup, all detached processes must execute@            the site-specific system login procedure (by default,$            SYS$MANAGER:SYLOGIN.COM).  E            If Advanced Server startup does not complete successfully, ?            check the SYLOGIN.COM procedure. Make sure that only A            commands that should be executed by detached processes 7            are executed during Advanced Server startup.n  ?            In SYLOGIN.COM, you can use the DCL lexical function B            F$MODE or F$GETJPI to conditionalize DCL commands, such@            as $SET TERM/INQUIRE, that should be executed only by?            nondetached processes, so that they are not executedaC            during Advanced Server startup. Refer to the OpenVMS DCLc+            Dictionary for more information.r  4      5.4.4.2 OpenVMS Registry Services Not Available  =            The Advanced Server will start only if the OpenVMS A            registry services are available. For information aboutaD            starting the Registry Server, refer to the OpenVMS SystemC            Manager's Manual or the OpenVMS Connectivity Developer's @            Guide (included in the OpenVMS Documentation CD-ROM).  @            If the Registry Server is started as part of Advanced@            Server startup, a message similar to the following is.            displayed by the startup procedure:  F      Checking to see if the OpenVMS Registry Services are available...B      %RUN-S-PROC-ID, identification of created process is 0000023B  B            If the Registry Server cannot be started, the following<            message is displayed and the startup procedure is            terminated:              .      5-6 After You Install the Advanced Server           H                                    After You Install the Advanced ServerH                                    5.4 Ways to Start the Advanced Server  C             SYS$REGISTRY must be defined to start the VMS Registry.   H         %PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for         this systemvB         %PWRK-F-STARTERR, severe error encountered during start-up  G             OpenVMS Registry Services are not available on this system.   K             Some file server parameters are stored in the OpenVMS Registry.LM             For the file server or file server utilities to be able to access I             these parameters, OpenVMS Registry Services must be available G             on this system.  Without them the file server cannot start._  	         $e  B         5.4.5 Determining Initial Advanced Server Parameter Values,               Stored in the OpenVMS Registry  E               The Advanced Server startup procedure records a list of H               all Advanced Server parameters that are set in the OpenVMSC               Registry. You can use this list as a reference if you G               should ever need the latest parameter values. The list is_E               stored in the following location, where nodename is theL'               name of your server node:t  ;               PWRK$PARAMS:PWRK$REGISTRY_PARAMS_nodename.LIS   (         5.5 Stopping the Advanced Server  B               You can stop the Advanced Server at any time for any6               reason, which can include the following:  H               o  When you want to change server configuration parameters  6               o  As part of an orderly system shutdown  G               To stop the Advanced Server, enter the following command:c  *               $ @SYS$STARTUP:PWRK$SHUTDOWN>               Shutting down the currently running server(s)...  *               For a cluster server, enter:  2               $ @SYS$STARTUP:PWRK$SHUTDOWN CLUSTER  ?               To stop the Advanced Server as part of an orderly D               system shutdown, add the shutdown command to the site-G               specific system shutdown procedure. In addition, prior to E               shutting down the server, announce the planned shutdown C               to connected users by using the ADMINISTER SEND/USERSe  H                                After You Install the Advanced Server 5-7 n  i      *      After You Install the Advanced Server%      5.5 Stopping the Advanced Server   A            command, as in the following example, which alerts all -            users connected to server WOODMAN:a  P            LANDOFOZ\\TINMAN> SEND/USERS/SERVER=WOODMAN "Shutdown @ 1pm today!!!"  4      5.6 Special Advanced Server Management Commands  @            Compaq provides numerous command procedures that, forA            example, provide shortcuts for invoking certain servertA            management commands and procedures. You can see a listpB            of these commands by examining the contents of the file0            SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM.  C            You can define these Advanced Server management commandsd@            automatically when you log in to the account that you@            use to manage the Advanced Server. To define AdvancedC            Server commands at login, edit the LOGIN.COM file of thes8            privileged account to add the following line:  .            $ @SYS$STARTUP:PWRK$DEFINE_COMMANDS  +      5.7 Setting Up External Authentication   ?            The OpenVMS operating system Versions 7.1 and higher @            provide support for external authentication. AdvancedA            Server participates with the operating system to allow @            Advanced Server domain users to log in to the OpenVMSA            operating system using the Advanced Server domain usert            name and password.   A            External authentication can provide automatic passwords;            synchronization between an OpenVMS account and as<            corresponding Advanced Server domain account. The@            passwords are synchronized whenever a user logs in to@            the OpenVMS account, provided that an Advanced ServerA            domain controller is available to service the request.SD            With external authentication enabled, users who have both@            OpenVMS and Advanced Server domain accounts can avoid/            maintaining two different passwords.>  D            By default, external authentication is disabled. However,>            when you start the Advanced Server, server externalB            authentication is automatically enabled, if the OpenVMS<            system administrator has defined logical names in  .      5-8 After You Install the Advanced Server    A      H                                    After You Install the Advanced ServerH                                   5.7 Setting Up External Authentication  G               SYSTARTUP_VMS.COM and marked user accounts in the SYSUAF, C               as described in the OpenVMS Guide to System Security.   A               No additional configuration is necessary on cluster H               members running the Advanced Server to enable the AdvancedB               Server to participate in the external authenticationD               process. However, to use external authentication in anD               Advanced Server cluster, all cluster members should beE               configured to be able to process OpenVMS logon requests A               for network users, so that externally authenticated2A               users can log on to the cluster through any node inlC               the cluster. A cluster member that is not running the H               complete Advanced Server can be configured to authenticateC               logon requests from network users if it has access toIH               external authentication software on a shared cluster disk.C               If it does not have access to external authentication H               software on a shared cluster disk, you can enable externalH               authentication on that system by copying only the externalA               authentication images to the system disk, followingdC               the steps given in Section 5.7.1, Setting Up Externalf1               Authentication in OpenVMS Clusters.V  G               To provide external authentication on the Advanced Servern7               system, perform the following procedures:e  H               __________________________________________________________H               Step___Procedure_______________________Refer_to_._._._____  ?               1.     Install one of the following:   Chapter 2,DH                      o  The Advanced Server          Installing AdvancedG                                                      Server for OpenVMS$>                      o  The standalone external      Software./                         authentication softwarei  1                              _______Note  ________  .                              At least one node+                              in the cluster )                              must run the .                              complete Advanced-                              Server software.   0                              ___________________    H                                After You Install the Advanced Server 5-9    s      *      After You Install the Advanced Server+      5.7 Setting Up External Authentication   E            __________________________________________________________ E            Step___Procedure_______________________Refer_to_._._._____   B            2.     Enable external authentication  OpenVMS Guide toA                   for the OpenVMS system.         System Securityr  B            3.     Set the OpenVMS user            OpenVMS Guide toA                   account to invoke external      System Security !                   authentication.   A            4.     Establish host mapping between  Compaq Advancedu<                   the Advanced Server domain      Server for@                   user account and the OpenVMS    OpenVMS ServerA                   user account, if necessary.     Administrator'ss7                                                   Guide   @            5.     If your Advanced Server is      Section 5.7.1,E                   participating in an OpenVMS     Setting Up External C                   Cluster, set up external        Authentication inrB                   authentication on all cluster   OpenVMS Clusters                   members.  A            6.     If you want to change the       Compaq Advanced <                   default domain used for         Server for@                   external authentication         OpenVMS ServerA                   (the local server's domain      Administrator'sd7                   is the default domain           Guides)                   for users when externalm0                   authentication is established:,                   if a user does not specify)                   a domain name at login, -                   the system uses the default -                   domain for authentication), (                   set the system logical*                   PWRK$ACME_DEFAULT_DOMAIN                   accordingly.  A            7.     If establishing external        Compaq Advancedp<                   authentication for users in     Server for@                   trusted domains, add the name   OpenVMS ServerA                   of the trusted domain(s) to     Administrator'sc7                   the OpenVMS Registry value      GuiderE            _______HOSTMAPDOMAINS.____________________________________e    /      5-10 After You Install the Advanced Servera d  r      H                                    After You Install the Advanced ServerH                                   5.7 Setting Up External Authentication  D         5.7.1 Setting Up External Authentication in OpenVMS Clusters  D               If external authentication is being used in an OpenVMSD               Cluster, Compaq recommends that all cluster members beE               configured to be able to process OpenVMS logon requestspF               for network users. If one or more members do not support?               external authentication, users that have externalaE               authentication set in their account records will not beTG               able to log on to those hosts not configured for externalv               authentication.E  F               Once external authentication is enabled properly on eachH               OpenVMS system in the cluster, as described in the OpenVMSF               Guide to System Security, no additional configuration isD               necessary on Advanced Server cluster members to enable@               them to participate in the external authenticationG               process. External authentication is enabled automatically 2               when the Advanced Server is started.  H               A cluster member that is not running the complete AdvancedG               Server can authenticate logon requests from network users G               if it has access to external authentication software on avG               shared cluster disk. Note that external authentication iseH               not supported on OpenVMS systems prior to V7.1. Therefore,C               to ensure that external authentication works properlyaF               on the cluster, Compaq recommends that you make sure allF               systems in the cluster that are not running the Advanced7               Server are running OpenVMS V7.1 or later.S  D               If the cluster member does not have access to externalC               authentication software on a shared cluster disk, yourB               can enable external authentication on that system byG               performing the following steps; for a cluster member that G               does have access to external authentication software on a G               shared cluster disk, you need only perform steps 2 and 3:   H               1. If the cluster member is a VAX node, copy the followingC                  external authentication files from any system diskeB                  where the complete Advanced Server for OpenVMS isE                  installed to the location indicated on the VAX node:t  C         SYS$LIBRARY:PWRK$ACME_MODULE_VAX.EXE to SYS$COMMON:[SYSLIB]n  E         SYS$STARTUP:PWRK$ACME_STARTUP.COM to SYS$COMMON:[SYS$STARTUP]_  H                               After You Install the Advanced Server 5-11 _  _      *      After You Install the Advanced Server+      5.7 Setting Up External Authentication   =               If the cluster member is an OpenVMS Alpha node, A               Version 7.2-1 or later, run the POLYCENTER Software C               Installation utility on the system, using the PRODUCT =               INSTALL ADVANCEDSERVER command, as explained inS>               Section 2.1.2, Installing the Server. Select theC               External Authentication Images only option to install E               the External Authentication images without the Advanced                Server.   ?               If the Alpha system is Version 7.1, then copy theSE               following external authentication files from any systemeD               disk where the complete Advanced Server for OpenVMS isD               installed to the location indicated on the Alpha node:  B      SYS$LIBRARY:PWRK$ACME_MODULE_ALPHA.EXE to SYS$COMMON:[SYSLIB]  B      SYS$STARTUP:PWRK$ACME_STARTUP.COM to SYS$COMMON:[SYS$STARTUP]  B            2. Define the following logical name in a node-specificB               system startup file (not clusterwide), or if using a1               shared system startup file such as U0               SYS$COMMON:[SYSMGR]SYLOGICALS.COM,E               ensure that you conditionalize the DEFINE command baseduC               on the node name (that is, using the lexical functionr               F$GETSYI).  K      $ DEFINE/SYSTEM/EXE PWRK$ACME_SERVER scsnode1_name[,scsnode2_name,...]   >               Each scsnodex_name is an equivalence name, which@               is the SCSNODE name of a cluster member running anB               Advanced Server that can be used to process external@               authentication requests. You can include all, or a@               subset of, the names of the Advanced Server memberB               nodes. This allows you to specify the order in which@               the requesting host contacts the hosts running theE               complete Advanced Server software for an authentication =               request. If the first node in the list does notuE               respond, the requesting host asks the next host, and soa               forth.  C               ________________________Note ________________________c  <               If you specify a subset of the Advanced Server@               member nodes, in order for external authentication=               requests to be processed properly, the AdvancednB               Server should be running (available) on at least one  /      5-12 After You Install the Advanced Server  c  i      H                                    After You Install the Advanced ServerH                                   5.7 Setting Up External Authentication  C                 of those specified cluster members. Otherwise, even D                 if another Advanced Server member node not specifiedC                 in the list is currently running, the requests willr!                 not be processed.   E                 _____________________________________________________   A               3. Invoke the SYS$STARTUP:PWRK$ACME_STARTUP command 1                  procedure during system startup.e  G               4. Set the OpenVMS user account on all cluster members to H                  allow external authentication, and if necessary, set upG                  host mapping between the OpenVMS user accounts and thesD                  Advanced Server user accounts. For more informationB                  about enabling OpenVMS user accounts for externalE                  authentication, refer to the OpenVMS Guide to SystemeE                  Security. For more information about setting up host A                  mapping, refer to the Compaq Advanced Server for 6                  OpenVMS Server Administrator's Guide.  F         5.7.2 Requirement for External Authentication Over DECnet-Plus  @               To allow users to be externally authenticated overG               DECnet-Plus for OpenVMS, set the OpenVMS system parametertG               NET_CALLOUTS to 255. This enables Advanced Server user IDr<               mapping and authentication for network logins.  <         5.7.2.1 Configuring the Server Capacity for External                 Authentication  B               By default, the Advanced Server can support up to 10A               simultaneous external authentication logon requestseG               (signons). You can modify this maximum to suit the serverME               requirements, using the Configuration Manager. For moretF               details, refer to the Compaq Advanced Server for OpenVMS+               Server Administrator's Guide.   E         5.7.3 Configuring Externally Authenticated Client Connections   H               By default, the Advanced Server supports the processing ofE               up to 10 simultaneous external authentication requests.tE               You can modify this maximum to suit the Advanced ServereE               requirements, using the Configuration Manager. To startdE               the Configuration Manager, enter the following command:o  (               $ ADMINISTER/CONFIGURATION  H                               After You Install the Advanced Server 5-13 e  r      *      After You Install the Advanced Server+      5.7 Setting Up External Authenticationh  <            The basic server parameters include the number of;            simultaneous activations for users with external             authentication.  =            For more information about using the ConfigurationeC            Manager, refer to the Compaq Advanced Server for OpenVMS (            Server Administrator's Guide.  @      5.7.4 Bypassing External Authentication When the Network Is            DownS  <            External authentication cannot occur if a networkC            connection is required and the network is down. However,aB            as a temporary solution, privileged users can enter theC            /LOCAL_PASSWORD qualifier after the OpenVMS user name atwE            the login prompt, to specify local authentication. Be suredC            to specify the OpenVMS user name and password when using )            the /LOCAL_PASSWORD qualifier.r  B            Because using the /LOCAL_PASSWORD qualifier effectivelyB            overrides the security policy established by the systemB            manager, it is allowed only when the user's account hasD            SYSPRV as an authorized privilege. This allows the systemC            manager to gain access to the system when the network isgC            down. When Bit 1 of the equivalence string is set in therB            SYS$SINGLE_SIGNON logical name, nonprivileged users whoC            are normally externally authenticated can log in locallysA            (the /LOCAL_PASSWORD qualifier need not be specified).o  C            For more information about the /LOCAL_PASSWORD qualifier D            for the login command line, refer to the OpenVMS Guide to            System Security.   :      5.8 Converting Encoded File Names from ODS-2 to ODS-5  @            Existing Advanced Server shares may be converted fromB            ODS-2 to ODS-5 to take advantage of the OpenVMS support?            of extended file specifications. The Advanced ServerOA            for OpenVMS software provides a conversion utility for D            converting ODS-2 encoded file names on ODS-5 devices thatA            have been converted from ODS-2. The conversion utilityeD            removes escape-encoded characters in file names, changingA            the file names to ISO Latin-1 characters. For example,g@            if a file name is created on an ODS-2 disk containingA            the character-encoding sequence __E4, to represent them  /      5-14 After You Install the Advanced Servera p  M      H                                    After You Install the Advanced ServerH                    5.8 Converting Encoded File Names from ODS-2 to ODS-5  H               lowercase a-umlaut (), the conversion utility removes the<               encoding and replaces it with the  character.  B               You can convert ODS-2 file names to ODS-5 file names               after:  G               o  The Advanced Server for OpenVMS has been installed andr                  configured.  E               o  The disk device containing escape-encoded file names E                  has been converted from ODS-2 to ODS-5. Refer to themB                  OpenVMS Guide to Extended File Specifications forD                  information about converting disk devices to ODS-5.  F                 ________________________Note  ________________________  >                 If you plan to configure a language other thanA                 the default (English (USA)), and your disk device B                 includes ODS-2 file names (names including escape-A                 encoded characters in the format __XX),  you mustaA                 convert all the file names before configuring then                 new language.l  E                 _____________________________________________________n  4         5.8.1 Using the File Name Conversion Utility  G               The file name conversion utility that converts file namesmH               from the encoding used on ODS-2 file systems to ISO Latin-               1 file names is:  *               SYS$SYSTEM:PWRK$CNVTOHFS.EXE  F               When the Advanced Server commands have been defined, youG               can use the PWCONVERT system management command to invoke E               the file name conversion utility. For information about F               defining Advanced Server system management commands, seeG               Section 5.6, Special Advanced Server Management Commands. E               For example, to define the PWCONVERT command, enter the $               following DCL command:  ;               $ PWCONVERT :== $SYS$SYSTEM:PWRK$CNVTOHFS.EXEh  5               The format of the PWCONVERT command is:h  /               $ PWCONVERT /qualifiers file-spec   H                               After You Install the Advanced Server 5-15    u      *      After You Install the Advanced Server:      5.8 Converting Encoded File Names from ODS-2 to ODS-5              Where:m  <            o  Qualifiers are optional. They are described inE               Table 5-1, PWCONVERT Qualifiers. The default setting isP-               used if you omit the qualifier._  E            o  The file-spec argument is required, and may include the 9               device name, directory name, and file name.n  B               -  If you specify only a disk device, the conversionD                  utility scans the entire device for file names that=                  are encoded, and converts them if necessary.   B               -  If you specify a disk device and a directory, allA                  the files in the specified directory are scannedlE                  and converted if necessary. You may include wildcard >                  characters in directory names and file names.  ?               -  If you specify a disk device, directory, and a ?                  single file name, only that file is converted.v  ;               -  If you enter the PWCONVERT command with nor>                  file specification, it prompts you for a file,                  specification. For example:                    $ PWCONVERT                  FILENAME:  E                  In response to this prompt, you must supply a devicenB                  name, and optionally a directory and file name to5                  convert. You may include qualifiers.   E      Table_5-1_PWCONVERT_Qualifiers__________________________________e  E      Qualifier________Description_____________________Default________   :      /CODE_PAGE=n     The code page used to           None3                       translate encoded characters,r3                       where n is the code page. For 1                       more information about codef1                       pages, refer to the OpenVMS $                       User's Manual.  E                                              (continued on next page)   /      5-16 After You Install the Advanced Servern p  t      H                                    After You Install the Advanced ServerH                    5.8 Converting Encoded File Names from ODS-2 to ODS-5  H         Table_5-1_(Cont.)_PWCONVERT_Qualifiers__________________________  H         Qualifier________Description_____________________Default________  C         /DISABLE=keyword Disables the function of the    /NODISABLE 5                          conversion utility specifiedo5                          by the keyword. The keywords                           are:s  5                          o  ACE, which specifies thats7                             the conversion utility will 5                             not check for "PATHWORKS" .                             ACEs on the files.  2                          o  STRUCTURE_LEVEL, which.                             specifies that the3                             conversion utility will 5                             not check the file systemq2                             type (ODS-2 or ODS-5).  @         /LOG=log-file-   Creates a log file containing   /NOLOG.D         specification    the file names converted. You   InformationE                          can specify the location and    is displayeddH                          name of the log file using      and no log fileD                          this qualifier.                 is created.  C         /VERBOSE         Displays all the file names     /NOVERBOSEr6                          scanned during the conversion#                          operation.e  >         /NOLIST          Suppresses the display of       /LIST4                          all the file names that are7                          converted. Only error messageslH         _________________are_displayed._________________________________  8         5.8.2 Example of Converting an Encoded File Name  A               In this example, the file named A FILE.TXT has beeneC               created by a Windows 95 client on DISKA, and has beenoA               encoded as A__20FILE.TXT. The device DISKA has beentD               converted from ODS-2 to ODS-5. As viewed from OpenVMS,*               the file appears as follows:      H                               After You Install the Advanced Server 5-17 n  e      *      After You Install the Advanced Server:      5.8 Converting Encoded File Names from ODS-2 to ODS-5  $            $ DIRECTORY DISKA:[FILES]"            Directory DISKA:[FILES]               .u               .                ..            A__20FILE.TXT            $  B            Use the PWCONVERT command to convert this file name, as            follows:e  9            $ PWCONVERT/VERBOSE DISKA:[FILES]A__20FILE.TXT   7            Scanning file - DISKA:[FILES]A__20FILE.TXT;1 .            Renamed A__20FILE.TXT to A FILE.TXT  #            Convert Utility Complete               $  7      5.8.3 Example of Converting All Encoded File Nameso  A            To convert all the encoded file names on a disk device A            and directory, enter the PWCONVERT command, specifying A            the disk device and directory without a file name. For C            example, to convert all the encoded file names stored on 2            device DISK$USER1, enter the following:              $ PWCONVERT             FILENAME: DISK$USER1:  .            Renamed A__20FILE.TXT to A FILE.TXT               .s               .                .n#            Convert Utility Completes  8      5.9 Installing Optional Server Administration Tools  =            The Advanced Server provides optional client-basedl?            server administration tools that allow you to manage,@            the server from Windows 2000, Windows 98, Windows 95,?            Windows for Workgroups, or Windows NT clients. These D            tools are available in the PWUTIL share after installing,/            configuring and starting the server.s  /      5-18 After You Install the Advanced Servert o  h      H                                    After You Install the Advanced ServerH                      5.9 Installing Optional Server Administration Tools  C               The SRVTOOLS directory in the PWUTIL share contains arE               subdirectory for each type of client computer. Refer to E               the README.TXT file in the appropriate subdirectory forrC               instructions on installing the software on the clientt               computer.f  H               Refer to the Windows NT Server documentation or use onlineC               Help for more information about how to use Windows NT *               server administration tools.                                                                        H                               After You Install the Advanced Server 5-19 v e                     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 productsPD               supported by the Advanced Server for OpenVMS software.  >               This chapter consists of the following sections:  @               o  Section 6.1, Enabling Wide Area Network Support  C               o  Section 6.2, Using the LMHOSTS File in a Wide AreaL                  Network  ?               o  Section 6.3, Using WINS in a Wide Area Network   >               o  Section 6.4, Using DNS in a Wide Area Network  .         6.1 Enabling Wide Area Network Support  H               The Advanced Server for OpenVMS software allows you to useH               one or more of the following methods for wide area network               name resolution:                 o  LMHOSTS fileh  5               o  Windows Internet Name Service (WINS)i  )               o  Domain Name System (DNS)   G               To use them, they must be enabled using the Configuration F               Manager. You can enable them through the PWRK$CONFIG.COMK               command procedure, which provides access to the ConfigurationnF               Manager when you answer YES to the question "Do you wantG               to change server configuration parameters." To enable one F               or more of the wide area network support methods, selectH               the Transports screen and select the appropriate checkbox.H               Alternatively, you can run the Configuration Manager afterG               the server is configured and started, as described in thesG               Compaq Advanced Server for OpenVMS Server Administrator'sa               Guide.  H                                     Implementing a Wide Area Network 6-1           %      Implementing a Wide Area Networke6      6.2 Using the LMHOSTS File in a Wide Area Network  6      6.2 Using the LMHOSTS File in a Wide Area Network  @            The Advanced Server for OpenVMS software provides the@            ability to set up a wide area network with the TCP/IP>            transport through the use of the LMHOSTS file. This@            file contains a list of domain controllers and memberD            servers in the same domain and also domain controllers inE            domains that have trusts established with that domain. TheaD            LMHOSTS file allows the Advanced Server to participate in2            a Windows NT wide area network as well.  C            Unlike a Windows NT Server, the Advanced Server does noteC            support remote LMHOSTS files (called into the Windows NTrA            LMHOSTS file using #INCLUDE). To include the same hostnD            names as an existing LMHOSTS file on a Windows NT Server,E            copy the LMHOSTS file to the Advanced Server then manuallymD            insert the entries into the Advanced Server LMHOSTS file.  C               ______________________ Caution ______________________d  ?               If you plan to use cluster load balancing in WANse?               (using DNS for NetBIOS resolution of the Advancede=               Server cluster alias name), you must remove alln<               entries for the cluster alias from the LMHOSTS?               file on all systems that will access the Advanced ?               Server cluster and that have enabled DNS for name >               resolution. For more information on cluster load@               balancing, refer to the Compaq Advanced Server for3               OpenVMS Server Administrator's Guide.   C               _____________________________________________________   0      6.2.1 Setting Up a TCP/IP Wide Area Network  C            To set up a TCP/IP wide area network, modify the LMHOSTSaB            file, adding the host names and TCP/IP addresses of theA            domain controllers and member servers in the wide arealA            network that are in the same domain or in domains thath5            have trust relationships with that domain.   D            The LMHOSTS file must be set up on all domain controllersE            and member servers in the domain, unless other methods are A            used to resolve NetBIOS names. Make sure your Advanced >            Server LMHOSTS file includes entries for all domainB            controllers and member servers of the domain and domain  )      6-2 Implementing a Wide Area Networke -         H                                         Implementing a Wide Area NetworkH                        6.2 Using the LMHOSTS File in a Wide Area Network  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 in F               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 PDC H               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-wideeD               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,eF               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.e  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.d  #         6.2.2 The LMHOSTS Directoryr  G               You set up a wide area network by supplying the following D               file on all OpenVMS file servers that are in different               subnets:  *               PWRK$LMROOT:[LANMAN]LMHOSTS.  H               (The LMHOSTS file has no file extension; include the final               dot, as shown.)c    H                                     Implementing a Wide Area Network 6-3 o  i      %      Implementing a Wide Area Networkn6      6.2 Using the LMHOSTS File in a Wide Area Network        6.2.3 LMHOSTS File Syntax  D            In the LMHOSTS file, create a list of nodes by specifying,            the following line for each node:  4            address NetBIOSname #PRE #DOM:domain_name              Where:   E            o  address is an Internet address of form x.x.x.x, where xt0               is a decimal number from 0 to 255.  A            o  NetBIOSname is a name from 1 to 16 characters long, A               and may include a control character. (The format of ?               a control character is \0Xnn or \nn, where n is ac!               hexadecimal digit.)   D               To include a nonprinting or control character, enclose@               the name in double quotation marks. All alphabeticC               characters are set to uppercase characters before the-@               name is loaded into cache (see the #PRE directive,*               below) or used for matching.  D               If you wish to include the 16th-byte control character.               in the name explicitly, you must  E               o  Pad the name with spaces to control the placement of '                  the control character.a  E               o  Enclose the name and control character within double                   quotes.  9               The following are some valid NetBIOS names:_                 speedy$               "LANDOFOZ       \0x1B"  C            o  #PRE is an optional directive that indicates that thefD               entry should be preloaded into the cache. Entries thatA               have the #PRE tag are preloaded into the cache when$E               the Advanced Server first starts up. If you add a #PRE-aA               tagged entry to the LMHOSTS file after the AdvancedtC               Server starts up, the name will not be preloaded intoi?               the cache until the Advanced Server is restarted.eD               However, the name will be available at the next lookup"               of the LMHOSTS file.  )      6-4 Implementing a Wide Area Networke e  C      H                                         Implementing a Wide Area NetworkH                        6.2 Using the LMHOSTS File in a Wide Area Network  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 logoneG                  and browser services behave in routed environments. ItiE                  is also used in user account management and in trust                   relationships.n  C               For example, the following entries should be included E               in the LMHOSTS file on a BDC that is not in the same IPrF               subnet as the PDC (if the two systems are in the same IPG               subnet, they can resolve names using broadcasts). In this G               example, the PDC name is DOMPDC at IP address 10.20.30.40 %               in the domain LANGROUP:t  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 the H               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 IP %               address of the new PDC.M  E               If the domain PDC is a PATHWORKS or Advanced Server forcF               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 \0x1BOC               name will be released by that cluster member and will F               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 determine H               the cluster member that has registered and currently holdsC               the \0x1B name, execute the NBSHOW KNB command at theDE               OpenVMS DCL prompt on each node of the cluster and look_E               for the \0x1B name in the name table that is displayed._G               The \0x1B name will show up in the name table of only one E               of the cluster members. The command NBSHOW is a speciale  H                                     Implementing a Wide Area Network 6-5           %      Implementing a Wide Area Networki6      6.2 Using the LMHOSTS File in a Wide Area Network  D            Advanced Server management command that is defined in theA            command file SYS$MANAGER:PWRK$DEFINE_COMMANDS.COM; for E            more information, see Section 5.6, Special Advanced Serverc            Management Commands.   C               ______________________ Caution ______________________c  =               If LMHOSTS files are not updated on all systemsS>               to reflect a PDC change, these systems might not@               be able to find the PDC for the domain. This would1               affect domain operations adversely.t  C               _____________________________________________________l  @            In environments using trust relationships, the domainB            controllers in trusting domains must establish a secureA            communications channel with a domain controller in thes>            trusting domain. This allows a user with an accountA            in one domain to access resources provided by a domainT=            that trusts the user's domain (called pass-through @            authentication). Therefore, domain controllers in theC            trusting domain, as well as those in the trusted domain,.C            should list all domain controllers from the other domaini@            in their respective LMHOSTS file. (This assumes otherA            NetBIOS name resolution methods, such as WINS, are notnB            being used.) Each domain controller should also include@            a \0x1B entry for the PDC of the other domain. In theC            following example, the domain LANGROUP trusts the domainfA            CORPDOM. The LANGROUP domain consists of the followingY            domain controllers:  E            __________________________________________________________$E            Name____IP_Address____Role________________________________   $            LGPPDC  192.20.30.40  PDC  E            LGPBDC__192.20.30.41__BDC_________________________________T  >            The CORPDOM domain consists of the following domain            controllers:O  E            __________________________________________________________]E            Name________IP_Address____Role____________________________   (            CORPPDC     110.5.5.5     PDC  )      6-6 Implementing a Wide Area NetworkE d  F      H                                         Implementing a Wide Area NetworkH                        6.2 Using the LMHOSTS File in a Wide Area Network  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 theSE               following entries in the LMHOSTS file located on domainp-               controllers in domain LANGROUP:t  6               110.5.5.5   CORPPDC #PRE    #DOM:CORPDOM5               110.5.5.5  "CORPDOM        \0x1B"  #PRE 7               110.5.5.20  CORPBDC1 #PRE    #DOM:CORPDOM 9               110.10.1.1  CORPBDC2   #PRE    #DOM:CORPDOMs  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:   6               192.20.30.40 LGPPDC  #PRE  #DOM:LANGROUP7               192.20.30.40 "LANGROUP       \0x1B"  #PREc6               192.20.30.41 LGPBDC  #PRE  #DOM:LANGROUP  ?               The #DOM directive is required in these cases. ItnE               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.   '         6.2.4 Managing the LMHOSTS Filee  E               To change the list of available nodes, you can edit the G               file at any time. Domain controller entries (specified by_G               the #DOM directive) and computer name entries without thenF               #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 versionsnE               of the LMHOSTS file to any name other than LMHOSTS. Or,iF               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  o      %      Implementing a Wide Area Networkr6      6.2 Using the LMHOSTS File in a Wide Area Network  C            option. When you use the Configuration Manager to enable @            or disable LMHOSTS name resolution, the change is notE            dynamic; that is, the change will not go into effect until 8            the next time the Advanced Server is started.  >            When you add an entry to the LMHOSTS file while the@            Advanced Server is running, if the entry includes theC            #PRE directive, the entry will not be cached permanently E            (as directed by the #PRE part of the entry) until the next B            restart of the server; however, the change is effectiveC            immedately, as it will be read dynamically when the namek%            next needs to be resolved.c  %      6.2.5 Using the LMHOSTS Log File   A            If errors occur when the LMHOSTS file is accessed, thes5            errors are recorded in the following file:e  8            PWRK$LMROOT:[LOGS]PWRK$KNBDAEMON_nodename.LOG  D            This file is open and being written to while the AdvancedB            Server is running. To close the log file, you must stop            the Advanced Server.   @            To prevent the log file from becoming too large, eachC            error is logged only once - the first time it occurs. IfyE            an error is found in the log file, it is not logged again.r  *      6.3 Using WINS in a Wide Area Network  B            You can configure the Advanced Server as a WINS client.?            This allows the Advanced Server to use a WINS Server B            for NetBIOS name registration, resolution, renewal, and8            release in a wide area network configuration.  ?            For more information on how to use the Configuration @            Manager to configure the Advanced Server to use WINS,A            refer to the Compaq Advanced Server for OpenVMS Serverr!            Administrator's Guide.C            )      6-8 Implementing a Wide Area Networkn i  n      H                                         Implementing a Wide Area NetworkH                                    6.3 Using WINS in a Wide Area Network  2         6.3.1 Setting up WINS for OpenVMS Clusters  C               To allow clients that are configured for WINS supportaB               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.i  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 theh               Advanced Server.  E               For more information about adding static entries to the_F               WINS database, refer to your WINS product documentation.  E                 ______________________ Caution ______________________e  A                 If you plan to use DNS name resolution to providedC                 cluster load balancing in WANs, you must remove allrB                 static entries for the cluster alias from the WINSB                 database. For more information on enabling clusterD                 load balancing in WANs, refer to the Compaq Advanced@                 Server for OpenVMS Server Administrator's Guide.  E                 _____________________________________________________o  ,         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 for G               NetBIOS name resolution. The Advanced Server uses DNS for H               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 usesiA                 WINS, LMHOSTS, or broadcast methods for resolving                  names.  E                 _____________________________________________________   H                                     Implementing a Wide Area Network 6-9 t  L      %      Implementing a Wide Area Networkn)      6.4 Using DNS in a Wide Area Networkt  ?            For more information on how to use the Configuration ?            Manager to configure the Advanced Server to use DNS,aA            refer to the Compaq Advanced Server for OpenVMS Serverh!            Administrator's Guide.o                                                                                  *      6-10 Implementing a Wide Area Network h  x                  H                                                                        7H         ________________________________________________________________  H                            Removing Advanced Server for OpenVMS Software      F               This chapter describes how to remove Advanced Server for0               OpenVMS software from your system.  F               If you have to reinstall the Advanced Server for OpenVMSC               software, you might first need to remove the Advancedi*               Server for OpenVMS software.  E               For example, if the Installation Verification ProcedureoH               indicated that the software installation procedure failed,G               you must reinstall the software. But first you might need 5               to remove the Advanced Server software.   B               o  If the system has enough free disk space, you canG                  install the server again without removing the Advancedt                  Server.  H               o  If the system does not have enough disk space, you mustC                  remove the Advanced Server before reinstalling it.   E               For more information about disk space requirements, seemC               Section 1.8.9, Step 9: Check Disk Space Requirements.e  >               This chapter consists of the following sections:  <               o  Section 7.1, Advanced Server Deinstallation  D               o  Section 7.2, Removing Advanced Server Configuration                  Parameters   B               o  Section 7.3, Removing Advanced Server for OpenVMS                  Softwarea  F               o  Section 7.4, Sample Advanced Server Removal Procedure    H                        Removing Advanced Server for OpenVMS Software 7-1 r  o      2      Removing Advanced Server for OpenVMS Software'      7.1 Advanced Server Deinstallationh  '      7.1 Advanced Server Deinstallation   B            You remove the Advanced Server using the PRODUCT REMOVE@            command. The removal procedure performs the following            operations:  2            o  Shuts down the server automatically.  D            o  Prompts you to enter information necessary to complete$               the removal procedure.  >            o  Attempts to start the OpenVMS Registry Server if2               registry services are not available.  E            o  Removes all Advanced Server for OpenVMS images, supportoB               files, and logical names that are created during the%               installation procedure.n  D            o  Prompts you whether to remove all Advanced Server dataC               files from the system. If you respond YES, it deletespA               the data files as well as all known Advanced Server E               keys and values in the OpenVMS Registry. If you respondu?               NO, it creates a file that contains a list of alltA               Advanced Server parameters that were in the OpenVMSd;               Registry before removing the server software.   E            o  Removes the Advanced Server user accounts if you deletee               the data files.o  C            o  Prompts you whether you want to remove clean up tools ?               that are provided with the Advanced Server. These D               tools include PWRK$FIXACE and PWRK$DELETEACE. For more@               information about these tools, refer to the Compaq@               Advanced Server for OpenVMS Server Administrator's               Guide.  >            o  Prompts you whether you want to save the NETBIOS=               image SYS$COMMON:[SYSEXE]NETBIOS.EXE (if it wasnA               installed) so that you can restore it if necessary. E               For example, you might discover later that it is needed A               by another product. (Older versions of the Advanced B               Server for OpenVMS and PATHWORKS for OpenVMS require?               the NETBIOS image.) Depending on your response toiA               this prompt, the procedure saves or deletes severalr@               other related files. The saved files are stored in.               SYS$COMMON:[SYSUPD.PWRK$SAFETY].  6      7-2 Removing Advanced Server for OpenVMS Software a  I      H                            Removing Advanced Server for OpenVMS SoftwareH                                       7.1 Advanced Server Deinstallation  F               o  Removes the NETBIOS$ACCESS OpenVMS identifier, unless6                  you choose to save the NETBIOS image.  C               o  Removes Advanced Server DECnet objects, unless youU2                  choose to save the NETBIOS image.  =               o  Deassigns all Advanced Server logical names.n  I               o  Removes any old Advanced Server files from SYS$SPECIFIC,hD                  such as patches, that might have been copied there.  =         7.2 Removing Advanced Server Configuration Parameterso  A               When you remove the Advanced Server data files, thedD               removal procedure will remove the server configurationH               parameters that are stored as values, and their keys, from#               the OpenVMS Registry.   @               To complete this operation, the removal procedure:  D               o  Requires that registry services be available on theC                  system. The Registry Server must be running on the D                  system or in the cluster, and the registry databaseF                  must be available on the system. If registry servicesF                  are not available, the removal procedure will attemptH                  to start the Registry Server. Registry services must beF                  enabled on the system to run the Registry Server. ForG                  more information about ensuring that registry services E                  are available, refer to the OpenVMS System Manager's E                  Manual or the OpenVMS Connectivity Developer's Guide @                  (included in the OpenVMS Documentation CD-ROM).  E               o  Invokes the PWRK$REGUTL parameter management utility E                  (described in the Compaq Advanced Server for OpenVMS /                  Server Administrator's Guide).H  9         7.3 Removing Advanced Server for OpenVMS Softwarem  G               To start the removal procedure and remove Advanced Server #               for OpenVMS software:F  E               1. Ensure that you are logged in to the SYSTEM account.n  B               2. Ensure that no processes are running the Advanced:                  Server ADMINISTER command-line interface.  H                        Removing Advanced Server for OpenVMS Software 7-3           2      Removing Advanced Server for OpenVMS Software6      7.3 Removing Advanced Server for OpenVMS Software  >            3. Start the removal command procedure, as follows:  -               $ PRODUCT REMOVE ADVANCEDSERVER   >            Table 7-1, PRODUCT REMOVE Prompts, tells you how to<            respond to the prompts that the removal procedure            displays.                                                                            6      7-4 Removing Advanced Server for OpenVMS Software           H                            Removing Advanced Server for OpenVMS SoftwareH                        7.3 Removing Advanced Server for OpenVMS Software  H         Table_7-1_PRODUCT_REMOVE_Prompts________________________________  M                                 If you want the removal           Enter . . .lH         At_this_prompt_._._.____procedure_to_._._.______________________  J         Do you want to          Continue                          <Return>         continue? [YES]c  D                                 Exit                              NO  J         Information about the   Save the Advanced Server on-      <Return>=         use of the Advanced     disk structure, including theo:         Server may have         security accounts database:         accumulated in data     (SAM), the share database,<         files. Delete those     and the server configuration9         files? [NO]:            parameters in the OpenVMS_<                                 Registry (see Section 7.3.1,?                                 Server Configuration Parameters28                                 in the OpenVMS Registry)  E                                 Remove the Advanced Server        YES <                                 on-disk structure, including>                                 the security accounts database:                                 (SAM), the share database,<                                 and the server configuration*                                 parameters  J         Save clean up tools?    Save the PWRK$FIXACE and          <Return>4         [YES]                   PWRK$DELETEACE tools  D                                 Delete these tools                NO  J         Save a copy of          Save the NETBIOS image and        <Return>8         NETBIOS.EXE? [YES]      related files so you can?                                 restore it later, if necessary._  D                                 Delete the NETBIOS image and      NOH         ________________________related_files___________________________              H                        Removing Advanced Server for OpenVMS Software 7-5 p         2      Removing Advanced Server for OpenVMS Software6      7.3 Removing Advanced Server for OpenVMS Software  B      7.3.1 Server Configuration Parameters in the OpenVMS Registry  ?            When you are prompted whether to delete the Advanced2            Server data files:   B            o  If you respond YES, in addition to deleting the data@               files (the Advanced Server directory structure and@               associated files created during installation), theB               procedure deletes all known Advanced Server keys and/               values from the OpenVMS Registry.#  D            o  If you respond NO, the procedure creates the following               file:3*               PWRK$LANMAN:SYS$REGISTRY.LIS>               This file contains a list of all Advanced ServerA               parameters that were in the OpenVMS Registry before =               removing the Advanced Server. Once the AdvancedeA               Server product is removed, PWRK$REGUTL is no longernC               available for managing Registry parameters. To remove @               the Advanced Server parameters left in the OpenVMS@               Registry, use the OpenVMS Registry Control ProgramE               (REG$CP.EXE). See the PWRK$LANMAN:SYS$REGISTRY.LIS file C               to determine which keys and values are to be removed.b  1      7.4 Sample Advanced Server Removal Procedurem  A            This is a sample of the removal procedure for Advancedc            Server software.   -      The following product has been selected: ?          CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Producte  0      Do you want to continue? [YES] YES <Return>  <      The following product will be removed from destination:J          CPQ AXPVMS ADVANCEDSERVER V7.3         DISK$AXP0721:[VMS$COMMON.]  !      Portion done: 0%...10%...20%S  >      Information about the use of the Advanced Server may have      accumulated in data files.s*      Delete those files? [NO] YES <Return>  >      Some portions of Advanced Server may be useful even after       Advanced Server is removed.+      Save clean up tools? [YES] NO <Return>o  6      7-6 Removing Advanced Server for OpenVMS Software g  e      H                            Removing Advanced Server for OpenVMS SoftwareH                             7.4 Sample Advanced Server Removal Procedure  A         If PCSI provided the image SYS$COMMON:[SYSEXE]NETBIOS.EXEtC         and does not know of another product also using that image,iA         then PCSI will remove that image.  It is possible anotherw@         program uses that image but PCSI does not know about it.?         This procedure can save the image so you can restore it C         in case it is needed. Several related files are also saved.u2         Save a copy of NETBIOS.EXE? [YES] <Return>  D         The OpenVMS Registry server is already started on this node.  <         Removing Advanced Server registry parameter and keys@         Removing PWRK$DEFAULT and PWRK$GUEST OpenVMS accounts...  ?         Saving Advanced Server for OpenVMS NETBIOS component...r.         Deleting Advanced Server data files...@         Deassigning Advanced Server for OpenVMS logical names...  9         ...30%...40%...50%...60%...70%...80%...90%...100%   /         The following product has been removed:uB             CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Product                                                H                        Removing Advanced Server for OpenVMS Software 7-7      o                  H                                                                        AH         ________________________________________________________________  H                                       Installation and Upgrade Checklist      E               Table A-1 summarizes the tasks that you need to performaC               to install and configure the Advanced Server. You canmH               photocopy this table and use it as a checklist as you read8               about and complete the tasks in this book.                                                              H                                   Installation and Upgrade Checklist A-1 n         '      Installation and Upgrade Checklistl    E      Table_A-1_Installation_and_Upgrade_Checklist____________________W  =      <   >1.   Prepare for the installation by completing allpE                preinstallation tasks on the checklist in Section 1.8,r>                Preinstallation Tasks, including the following:  )                a. Check the part listing.d  @                b. Make sure that you have the required hardware.  @                c. Log in to the SYSTEM account (or an equivalent                   account).   B                d. Make sure your system has the required software.  D                e. Check that OpenVMS registry services are available0                   on the Advanced Server system.  )                f. Read the release notes.   @                g. Make sure that the system parameters GBLPAGES,?                   GBLSECTIONS, PROCSECTCNT, and SCSNODE are setu                   properly.   +                h. Back up the system disks._  >                i. Make sure that you have enough disk space to'                   install the software.b  >                j. Make sure that the queue manager is running.  4                k. Check the time zone configuration.  D                l. Verify that DECnet (or DECnet-Plus) and TCP/IP, if&                   needed, are running.  E                m. Check for existing Compaq OpenVMS server images andd&                   files on the system.  D                n. Check OpenVMS Cluster configuration, if installing                   on a Cluster.   E                                              (continued on next page)l    +      A-2 Installation and Upgrade Checklist            H                                       Installation and Upgrade Checklist    H         Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________  A         <   >2.   Start the installation procedure and respond toeE                   installation prompts. You may choose to install thet                   following:  1                   o  The complete Advanced Server   G                   o  The standalone License Server (if you chose not toe1                      install the Advanced Server)h  H                   o  The standalone external authentication software (ifB                      you chose not to install the Advanced Server)  D                   o  Both the standalone License Server and externalA                      authentication software (if you chose not toe1                      install the Advanced Server)   B         <   >3.   Start the configuration procedure and respond to(                   configuration prompts.  E         <   >4.   Run the Installation Verification Procedure (if youGH                   did not do so when you installed the Advanced Server).  A         <   >5.   Start the server (if you did not do so when you 2                   configured the Advanced Server).  @         <   >6.   Install Windows NT server administration toolsH         __________(optional).___________________________________________                                H                                   Installation and Upgrade Checklist A-3 e e  r                  H                                                                        BH         ________________________________________________________________  H                    Sample Advanced Server Installation and Configuration      G               This appendix shows sample installation and configuration A               procedures for the Advanced Server when it is being,9               installed for the first time on the system.y  9         B.1 Sample Advanced Server Installation Procedureo  F               The following example shows a sample installation dialogF               for the Advanced Server. The installation dialog differs2               slightly according to circumstances.  ?         $ PRODUCT INSTALL ADVANCEDSERVER/SOURCE=DKA100:[000000]   0         The following product has been selected:B             CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Product  (         Configuration phase starting ...  N         You will be asked to choose options, if any, for each selected product         and foriI         any products that may be installed to satisfy software dependency          requirements.2  C         CPQ AXPVMS ADVANCEDSERVER V7.3: Advanced Server for OpenVMS   6             Copyright 2000 Compaq Computer Corporation  B             Advanced Server is sold by Compaq Computer Corporation  H             Advanced Server requires PAK PWLMXXXCA07.03 for each client.            H                Sample Advanced Server Installation and Configuration B-1           :      Sample Advanced Server Installation and Configuration6      B.1 Sample Advanced Server Installation Procedure  H              This installation procedure requires that all the following&              conditions are satisfied:A              1.  This procedure is running on an Alpha processor.o<              2.  The system is running OpenVMS 7.2 or later.?              3.  All required privileges are currently enabled. C              4.  No PATHWORKS or Advanced Server images are running 9                  on this node or anywhere in the cluster.eD              5.  No files from a PATHWORKS (NetWare) kit are present%                  on this system disk.eC              6.  No files from any Pathworks or Advanced Server kit 9                  are in SYS$SPECIFIC on this system disk.   C              This procedure checks if the conditions are satisfied. D              If they are satisfied, the procedure continues. If not,!              the procedure stops.S  ,      Do you want to continue? [YES] <Return>  0              Select one of the numbered options:F              1  Install the complete Advanced Server         [default]/              2  Install only the License Server ?              3  Install only the external authentication imagesu7              4  Install both the License Server and the 3                      external authentication images       Option: [1] <Return>o  K      This node contains a PWRK$STREAMSOS_V*.EXE execlet from a previous kit       loaded into memory.H      A node that will not run this product does not have to be rebooted.H      A node that did not run a previous version of this product does notE      have to be rebooted.  Only nodes that ran a previous version andI/      will run the new version must be rebooted.S  J      Depending on the existing configuration and the desired configurationF      of a node it might be necessary to reboot a node before it can beE      configured, after it has been configured, or both. Both is rare.e  A      For complete information about the reasons a reboot might beeI      necessary and how to avoid unnecessary reboots, see the Installation       and Configuration Guide.e          >      B-2 Sample Advanced Server Installation and Configuration s  e      H                    Sample Advanced Server Installation and ConfigurationH                        B.1 Sample Advanced Server Installation Procedure           Select an option: C         1. Delay reboot as long as possible on all nodes. [default]cJ         2. Prevent PWRK$CONFIG configuration on any node using this system#            disk until after reboot. M         3. Prevent PWRK$CONFIG configuration on all nodes until after reboot.eI         4. Prevent startup on any node using this system disk until afterO            reboot.;         5. Prevent startup on all nodes until after reboot.            Option: [1] <Return>  H                       User Accounts and User Identification Codes (UICs)H                       --------------------------------------------------  I             The Advanced Server V7.3 for OpenVMS installation creates two K             OpenVMS accounts:  a default account, PWRK$DEFAULT, and a guestiG             account, PWRK$GUEST.  The default UIC group number for bothe8             these new accounts depends on the following:  G              o If you are installing the server for the first time, the E                default is the first unused UIC group number, startings                with 360.  ?              o If a PCFS$ACCOUNT already exists, the default is,A                the UIC group number associated with PCFS$ACCOUNT.h  F              o If a PWRK$DEFAULT or PWRK$GUEST account already exists,B                the default is the UIC group number associated withI                PWRK$DEFAULT or PWRK$GUEST, in preference to PCFS$ACCOUNT.tH                However, the default UIC group number will not be used to7                change the UIC of any existing accounts.l  B              For more information about UIC group numbers, see the-              OpenVMS System Manager's Manual.   *         Enter default UIC group number for#         PWRK$DEFAULT and PWRK$GUEST          Group: [360] <Return>tA         Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUESTd+         PWRK$DEFAULT account already existsS)         PWRK$GUEST account already exists.  ?         * This product does not have any configuration options.o  $         Execution phase starting ...  ?         The following product will be installed to destination: M             CPQ AXPVMS ADVANCEDSERVER V7.3         DISK$AXP0721:[VMS$COMMON.].  H                Sample Advanced Server Installation and Configuration B-3 I  T      :      Sample Advanced Server Installation and Configuration6      B.1 Sample Advanced Server Installation Procedure  9      Portion done: 0%...10%...20%...30%...40%...60%...90%vC          To automatically start Advanced Server V7.3 for OpenVMS ateA          system startup, you should add the following line to theO,          SYS$MANAGER:SYSTARTUP_VMS.COM file.  (              $ @SYS$STARTUP:PWRK$STARTUP  G          Note: Add this line after the lines that start all the networky$          transports, such as DECnet.  G          Before starting Advanced Server V7.3 for OpenVMS on this node, F          be sure to configure the product (@SYS$UPDATE:PWRK$CONFIG) on=          each node in the cluster where the product will run.3      ...100%  .      The following product has been installed:?          CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Product   @      %PCSI-I-IVPEXECUTE, executing test procedure for CPQ AXPVMS       ADVANCEDSERVER V7.3 ....  6      Copyright Compaq Computer Corporation 1998, 2000.  9              Starting Installation Verification ProcedureR1              for Advanced Server V7.3 for OpenVMS   /      %PWRK-I-NORMAL, IVP completed successfullyO>      %PCSI-I-IVPSUCCESS, test procedure completed successfully      $  7      B.2 Sample Advanced Server Configuration Procedurel  D            The following example shows a sample configuration dialog#            for the Advanced Server.,        $ @SYS$UPDATE:PWRK$CONFIG=      Advanced Server V7.3 for OpenVMS Configuration Procedure?  <        The Advanced Server stores and accesses the following        types of data files:e  &        o Configuration parameter files"        o License Server data files        o Log files        o Printer spool files%        o Virtual memory section files   I        You can specify any existing OpenVMS disk device that has at leastnB        85,000 free blocks of disk space to store these data files.  >      B-4 Sample Advanced Server Installation and Configuration a  d      H                    Sample Advanced Server Installation and ConfigurationH                       B.2 Sample Advanced Server Configuration Procedure  K           Note: The server frequently accesses the data files stored on theLM           disk.  If these files are stored on the system disk, it can degrade P           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:a  O           If this OpenVMS cluster has multiple system disks, make sure that all =           nodes on which you plan to run the Advanced Server:_  H           o Use the same disk device to store and access Advanced Server             data files.   O           o Share the same SYSUAF.DAT file. In each system disk's startup file,SL             define a system logical name that points all nodes to the shared)             SYSUAF.DAT file. For example:r  M             $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat   D             The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM  K         Enter disk device name where the Advanced Server data files will bet)         stored [SYS$SYSDEVICE:]: <Return> =         Creating Advanced Server directory tree on PWROOT:...aE         PWRK$LICENSE_SERVER_STATE.DAT already exists, not superseded.fA         %CREATE-I-EXISTS, PWRK$COMMONROOT:[000000] already exists I         Checking to see if the OpenVMS Registry Services are available... E         %RUN-S-PROC_ID, identification of created process is 0000023BeF         Populating OpenVMS Registry with required Advanced Server & NT         parameters...eE         Please wait, this may take one to two minutes to complete ... P         Required OpenVMS Registry file server keys and values have been created.B         Migrating LANMAN.INI parameters to the OpenVMS Registry...'         Verifying SAM database files...l2         Creating Advanced Server directory tree...A         Copying client files to Advanced Server directory tree... P         Creating the Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT...  O           Changing the server configuration parameters will allow you to modify M           this server's client capacity and select the transports to be used.C  +           SPEEDY is currently configured tor%               + support 20 PC clients 6               + use the following transport(s): DECnet  J           If you want this server to be the primary domain controller, youJ           should configure it to use all the transports used by the backup>           domain controllers and member servers in the domain.  H                Sample Advanced Server Installation and Configuration B-5    t      :      Sample Advanced Server Installation and Configuration7      B.2 Sample Advanced Server Configuration Procedureu  B        If you want this server to be a backup domain controller orB        member server, you should configure it to have at least oneG        transport in common with the domain's primary domain controller,v.        otherwise this configuration will fail.  H        If you do not change the configuration parameters now, you may do'        so later by typing ADMIN/CONFIG.n  C      Do you want to change the server configuration parameters now?       [YES]:Y <Return>I  D      ******* Advanced Server Configuration for node SPEEDY *********D      * Options Help                                                *D      *                                                             *D      *                                                             *D      * *Server's Client Capacity********************************** *D      * *                                                         * *D      * *                                                         * *D      * * (  ) Maximize Client Capacity Using AUTOGEN/Reboot      * *D      * * (* ) Maximize Client Capacity Without AUTOGEN or Reboot * *D      * * (  ) User Supplied Client Capacity                      * *D      * *                                                         * *D      * *  Client Capacity: 20                                    * *D      * *                                                         * *D      * *********************************************************** *D      *                                                             *D      * Percent of Physical Memory Used: 80                         *D      *                                                             *D      * Data Cache Size (Kbytes): 12888                             *D      *                                                             *D      * Maximum Concurrent Signons: 10                              *D      * OpenVMS Process Priority: 9                                 *D      *                                                             *D      * **********  ********  ***************  *****************    *D      * * Verify *  * Quit *  * Advanced... *  * Transports... *    *D      * **********  ********  ***************  *****************    *D      *                                                             *D      * Enter data cache size in Kbytes *****************************	         .:	         . 	         .h1      Reading current configuration parameters ...r  B        Your Advanced Server for OpenVMS is presently configured to        run as follows:  >      B-6 Sample Advanced Server Installation and Configuration s         H                    Sample Advanced Server Installation and ConfigurationH                       B.2 Sample Advanced Server Configuration Procedure  2            1.  Run the License Server:          NO2            2.  Enable Timesource service:       NO3            3.  Enable Alerter service:          YESC=            3a. Alert user names:                Administrator 3            4.  Enable Netlogon service:         YES 8            5.  Advanced Server domain:          LANGROUP7            6.  Advanced Server role:            PRIMARY 6            7.  Advanced Server computer name:   SPEEDYD            7a. Advanced Server OpenVMS Cluster alias:   SPEEDY_ALIASK            8.  Server announce comment:    Advanced Server V7.3 for OpenVMS =            9.  Advanced Server language:        English (USA) 2           10.  Enable NT style printing:        NOK         Enter item number, or RETURN to use these values [DONE]: 5 <Return>g  K           An Advanced Server domain is a collection of computers that share J           a common security database and policy.  Each domain has a unique1           name.  A network can have many domains.   J           The Advanced Server domain name can be up to 15 characters long.C           The domain name must be different than the computer name.   I         Enter Advanced Server domain name for this system [5]: SPUNKY.DOMs         <Return>  E           Your Advanced Server for OpenVMS is presently configured toc           run as follows:   2            1.  Run the License Server:          NO2            2.  Enable Timesource service:       NO3            3.  Enable Alerter service:          YESl=            3a. Alert user names:                Administratory3            4.  Enable Netlogon service:         YES :            5.  Advanced Server domain:          SPUNKY.DOM7            6.  Advanced Server role:            PRIMARYc6            7.  Advanced Server computer name:   SPEEDYD            7a. Advanced Server OpenVMS Cluster alias:   SPEEDY_ALIASK            8.  Server announce comment:    Advanced Server V7.3 for OpenVMSh=            9.  Advanced Server language:        English (USA) 2           10.  Enable NT style printing:        NOI         Enter item number, or RETURN to use these values [DONE]: <Return>           H                Sample Advanced Server Installation and Configuration B-7    s      :      Sample Advanced Server Installation and Configuration7      B.2 Sample Advanced Server Configuration Procedure   1      Saving parameters to the OpenVMS Registry...i      Creating SAM datafiles...A      Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB ... $      New sharefile has been created.      ADMIN$ added_      IPC$ added_      PWUTIL added_      PWLICENSE added      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.  =          The account password can be up to 14 characters longy?          and the case of the characters used will be preserved.   *      Enter Administrator account password:!      Re-enter to verify password:   3      Changing password for Administrator account...f!      Checking system resources...i  C      The current system configuration for SPEEDY will support 20 PC=
      clients. F      The Advanced Server is configured to use DECnet, NetBEUI, TCP/IP.  D          To automatically start the Advanced Server V7.3 for OpenVMSD          at system startup, you should add the following line to the,          SYS$MANAGER:SYSTARTUP_VMS.COM file.  &            $ @SYS$STARTUP:PWRK$STARTUP  C          Note: Add this line below the lines that start all network %          transports (such as DECnet).c                    >      B-8 Sample Advanced Server Installation and Configuration           H                    Sample Advanced Server Installation and ConfigurationH                       B.2 Sample Advanced Server Configuration Procedure  H         Do you want to start the Advanced Server V7.3 on node SPEEDY now         [YES]: <Return>d9         The file server will use DECnet, NetBEUI, TCP/IP.a:         Advanced Server mail notification will use DECnet.<         Process NETBIOS created with identification 00000248B         Process PWRK$NBDAEMON created with identification 0000024AC         Process PWRK$KNBDAEMON created with identification 0000024COC         Process PWRK$LICENSE_R created with identification 0000024ErI         Checking to see if the OpenVMS Registry Services are available...rC         The Advanced Server is configured to support 20 PC clients.e@         Process PWRK$MASTER created with identification 00000251<         The master process will now start all other Advanced         Server processes.s  	         $S                                                            H                Sample Advanced Server Installation and Configuration B-9 i                       H                                                                        CH         ________________________________________________________________  H          Sample Standalone License Server Installation and Configuration      G               This appendix shows sample installation and configurationeF               procedures for a standalone License Server on an OpenVMS               Cluster.  C         C.1 Sample Standalone License Server Installation Procedurea  F               The following example shows a sample installation dialog0               for the standalone License Server.  1         $ PRODUCT INSTALL ADVANCEDSERVER <RETURN>   0         The following product has been selected:B             CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Product  /         Do you want to continue? [YES] <RETURN>i  (         Configuration phase starting ...  N         You will be asked to choose options, if any, for each selected product         and fornI         any products that may be installed to satisfy software dependency          requirements.   C         CPQ AXPVMS ADVANCEDSERVER V7.3: Advanced Server for OpenVMSm  6             Copyright 2000 Compaq Computer Corporation  B             Advanced Server is sold by Compaq Computer Corporation              H      Sample Standalone License Server Installation and Configuration C-1 a  n      D      Sample Standalone License Server Installation and Configuration@      C.1 Sample Standalone License Server Installation Procedure  E          Advanced Server requires PAK PWLMXXXCA07.03 for each client.oA       This installation procedure requires that all the followingP       conditions are satisfied:o:       1.  This procedure is running on an Alpha processor.5       2.  The system is running OpenVMS 7.2 or later.e8       3.  All required privileges are currently enabled.<       4.  No PATHWORKS or Advanced Server images are running2           on this node or anywhere in the cluster.=       5.  No files from a PATHWORKS (NetWare) kit are present            on this system disk.<       6.  No files from any PATHWORKS or Advanced Server kit2           are in SYS$SPECIFIC on this system disk.  <       This procedure checks if the conditions are satisfied.5       If they are satisfied, the procedure continues.U"       If not, the procedure stops.  ,      Do you want to continue? [YES] <RETURN>)       Select one of the numbered options:n@       1.  Install the complete Advanced Server         [default])       2.  Install only the License Server 9       3.  Install only the external authentication images 1       4.  Install both the License Server and theS%        external authentication images,      Option: [1] 2 <RETURN>pI      This node does not have to be rebooted before starting this product.o  A      For complete information about the reasons a reboot might behI      necessary and how to avoid unnecessary reboots, see the InstallationS      and Configuration Guide.T        Select an option:@      1. Delay reboot as long as possible on all nodes. [default]G      2. Prevent PWRK$CONFIG configuration on any node using this systemm          disk until after reboot.J      3. Prevent PWRK$CONFIG configuration on all nodes until after reboot.@      4. Prevent startup on any node using this system disk until         after reboot.n8      5. Prevent startup on all nodes until after reboot.        Option: [1] 1 <RETURN>U  <      * This product does not have any configuration options.  !      Execution phase starting ...   H      C-2 Sample Standalone License Server Installation and Configuration           H          Sample Standalone License Server Installation and ConfigurationH              C.1 Sample Standalone License Server Installation Procedure  ?         The following product will be installed to destination: M             CPQ AXPVMS ADVANCEDSERVER V7.3         DISK$AXP0721:[VMS$COMMON.]S  N         Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%         ...100%.  1         The following product has been installed:eB             CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Product  C         %PCSI-I-IVPEXECUTE, executing test procedure for CPQ AXPVMS            ADVANCEDSERVER V7.3 ...  9         Copyright Compaq Computer Corporation 1998, 2000.t  5          Starting Installation Verification Procedure.-          for Advanced Server V7.3 for OpenVMS.  2         %PWRK-I-NORMAL, IVP completed successfullyA         %PCSI-I-IVPSUCCESS, test procedure completed successfullyi  E         C.2 Sample Configuration Dialog for Standalone License Servero  G               The following example shows a sample configuration dialog 0               for the standalone License Server.  !         $ @SYS$UPDATE:PWRK$CONFIGV@         Advanced Server V7.3 for OpenVMS Configuration Procedure  ?           The Advanced Server stores and accesses the followingr           types of data files:  )           o Configuration parameter files %           o License Server data filess           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.   K           Note: The server frequently accesses the data files stored on therM           disk.  If these files are stored on the system disk, it can degradegP           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>  O           If this OpenVMS Cluster has multiple system disks, make sure that allr=           nodes on which you plan to run the Advanced Server:S  H      Sample Standalone License Server Installation and Configuration C-3           D      Sample Standalone License Server Installation and ConfigurationB      C.2 Sample Configuration Dialog for Standalone License Server  E        o Use the same disk device to store and access Advanced Server           data files.  L        o Share the same SYSUAF.DAT file. In each system disk's startup file,I          define a system logical name that points all nodes to the sharedm&          SYSUAF.DAT file. For example:  J          $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat  A          The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM   H      Enter disk device name where the Advanced Server data files will be&      stored [SYS$SYSDEVICE:]: <RETURN>A      Creating Advanced Server directory tree on SYS$SYSDEVICE:... >      %CREATE-I-EXISTS, PWRK$COMMONROOT:[000000] already exists  =        The License Server can serve client-based licenses for @        Advanced Server clients over DECnet, NetBEUI, and TCP/IP.>        The Advanced Server need not be running for the License        Server to operate.u  K      Do you want to serve client-based licenses over DECnet [YES]: <Return>eM      Do you want to serve client-based licenses over NetBEUI [NO]: Y <Return>:L      Do you want to serve client-based licenses over TCP/IP [NO]: Y <Return>  P      Do you want to start the Advanced Server License Server now [YES]: <Return>  9      The License Server will use DECnet, NetBEUI, TCP/IP.   9      Process NETBIOS created with identification 2960012Be  ?      Process PWRK$NBDAEMON created with identification 2960012D0  @      Process PWRK$KNBDAEMON created with identification 2960012F  @      Process PWRK$LICENSE_S created with identification 29600131  F       To automatically start the License Server at system startup, you*       should add the following line to the)       SYS$MANAGER:SYSTARTUP_VMS.COM file:r  .            $ @SYS$STARTUP:PWRK$LICENSE_STARTUP  A        Note: Add this line below the lines that start all network.#        transports (such as DECnet).d        $  H      C-4 Sample Standalone License Server Installation and Configuration R  O                  H                                                                        DH         ________________________________________________________________  H                     Sample External Authentication Software Installation      F               The following example shows a sample installation dialogD               when you select to install the External AuthenticationG               software only. Note that you cannot use the configuration H               procedure PWRK$CONFIG after this installation. Attempts to0               do so result in the message shown.  1         $ PRODUCT INSTALL ADVANCED SERVER<Return>   0         The following product has been selected:N             CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Product [Installed]  /         Do you want to continue? [YES] <Return>   (         Configuration phase starting ...  N         You will be asked to choose options, if any, for each selected product         and for I         any products that may be installed to satisfy software dependency          requirements.e  C         CPQ AXPVMS ADVANCEDSERVER V7.3: Advanced Server for OpenVMSD  6             Copyright 2000 Compaq Computer Corporation  B             Advanced Server is sold by Compaq Computer Corporation  H             Advanced Server requires PAK PWLMXXXCA07.03 for each client.D          This installation procedure requires that all the following"          conditions are satisfied:=          1.  This procedure is running on an Alpha processor. 8          2.  The system is running OpenVMS 7.2 or later.;          3.  All required privileges are currently enabled. ?          4.  No PATHWORKS or Advanced Server images are running 5              on this node or anywhere in the cluster.i@          5.  No files from a PATHWORKS (NetWare) kit are present!              on this system disk.*?          6.  No files from any PATHWORKS or Advanced Server kit 5              are in SYS$SPECIFIC on this system disk.   H                 Sample External Authentication Software Installation D-1           9      Sample External Authentication Software Installation     <       This procedure checks if the conditions are satisfied.5       If they are satisfied, the procedure continues. "       If not, the procedure stops.  -      Do you want to continue? [YES]  <Return> )       Select one of the numbered options: @       1.  Install the complete Advanced Server         [default])       2.  Install only the License Server 9       3.  Install only the external authentication images 1       4.  Install both the License Server and the %        external authentication imagesS      Option: [1] 3  <Return>E      A PWRK$STREAMSOS_V*.EXE execlet from a previous kit is currently #      loaded in memory on this node.*H      You must reboot this node before starting the product on this node.  A      For complete information about the reasons a reboot might be I      necessary and how to avoid unnecessary reboots, see the Installation       and Configuration Guide.         Select an option:@      1. Delay reboot as long as possible on all nodes. [default]G      2. Prevent PWRK$CONFIG configuration on any node using this system           disk until after reboot.J      3. Prevent PWRK$CONFIG configuration on all nodes until after reboot.@      4. Prevent startup on any node using this system disk until         after reboot.S8      5. Prevent startup on all nodes until after reboot.        Option: [1] 1  <Return>  <      * This product does not have any configuration options.  !      Execution phase starting ...   <      The following product will be installed to destination:J          CPQ AXPVMS ADVANCEDSERVER V7.3         DISK$AXP0721:[VMS$COMMON.]  K      Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%       ...100%  .      The following product has been installed:?          CPQ AXPVMS ADVANCEDSERVER V7.3         Layered Productn  @      %PCSI-I-IVPEXECUTE, executing test procedure for CPQ AXPVMS       ADVANCEDSERVER V7.3 ...A  6      Copyright Compaq Computer Corporation 1998, 2000.  =      D-2 Sample External Authentication Software Installation:           H                     Sample External Authentication Software Installation    5          Starting Installation Verification Procedureu-          for Advanced Server V7.3 for OpenVMSa  2         %PWRK-I-NORMAL, IVP completed successfullyA         %PCSI-I-IVPSUCCESS, test procedure completed successfully   	         $t+         $ @SYS$UPDATE:PWRK$CONFIG  <Return> L         %DCL-E-OPENIN, error opening SYS$SYSROOT:[SYSUPD]PWRK$CONFIG.COM; as           input $           -RMS-E-FNF, file not found                                                                    H                 Sample External Authentication Software Installation D-3 s l  o                  H                                                                        EH         ________________________________________________________________  H                              Advanced Server Files and On-Disk Structure      <               This appendix includes the following sections:  3               o  Section E.1, Advanced Server Files   ?               o  Section E.2, Advanced Server On-Disk StructureR  !         E.1 Advanced Server Filesm  >               Table E-1 describes the files created during the2               installation of the Advanced Server.  H         Table_E-1_Files_Installed_for_the_Advanced_Server_______________  H         File_________________________________Description________________  H         DCPS$EXAMPLES:__________________________________________________  H         PWRK$BORDER.LUP[5]                   DECprint Supervisor printer>                                              layup for borders  H         PWRK$NOBORDER.LUP[5]                 DECprint Supervisor printerA                                              layup for no bordersi  H         PWRK$REV_LANDSCAPE_BORDER.LUP[5]     DECprint Supervisor printerC                                              layup for borders withA4                                              Windows  H         PWRK$REV_LANDSCAPE_NOBORDER.LUP[5]   DECprint Supervisor printerF                                              layup for no borders with4                                              Windows=         [5]This file is installed with the standalone LicenseuA         Server software installations as well as with full servers         installations.  H                                                 (continued on next page)  H                          Advanced Server Files and On-Disk Structure E-1 t  r      0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______U  E      File_________________________________Description________________r  E      SYS$HELP:_______________________________________________________o  D      ASOVMS073.RELEASE_NOTES              Release notes for AdvancedA                                           Server V7.3 for OpenVMSs  @      AS$HLP.HLB[1],[5]                    Help file for AdvancedE                                           Server System Dump Analyzeri@                                           (SDA) (associated with@                                           AS$SDA.EXE and invokedE                                           within SDA with the AS HELPt2                                           command)  >      CS$HLP.HLB[1],[5]                    Help file for common>                                           services System DumpD                                           Analyzer (SDA) (associatedE                                           with CS$SDA.EXE and invoked E                                           within SDA with the CS HELP 2                                           command)  >      PCDISKHLP.HLB[5]                     DOS File Maintenance>                                           utility help library  D      PWRK$ADMIN_CFG.HLB                   Configuration Manager help1                                           libraryl  >      PWRK$ADMIN_LIC.HLB[5]                License Manager help1                                           library   B      PWRK$MANAGER.HLB                     ADMINISTER commands help1                                           library   C      PWRK$PWMONITOR.HLB[1], [5]           Help file for PWRK$PWMON, @                                           the host-based monitorA                                           utility (invoked withindC                                           PWRK$PWMON with the PWMONl7                                           HELP command)s  H      PWRK$SHOWINI.HLB[1]                  Help file for PWRK$SHOWINI.EXE  C      [1]This file is (or is associated with) an unsupported utility       or command procedure.:      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations.   E                                              (continued on next page)E  4      E-2 Advanced Server Files and On-Disk Structure    c      H                              Advanced Server Files and On-Disk StructureH                                                E.1 Advanced Server Files  H         Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______  H         File_________________________________Description________________  H         SYS$HELP:_______________________________________________________  A         STREAMS$HLP.HLB[1],[5]               Help file for SystempD                                              Dump Analyzer (SDA) forE                                              streams (protocol layer)eF                                              analysis (associated withH                                              STREAMS$SDA.EXE and invokedH                                              within SDA with the STREAMS:                                              HELP command)  H         ________________________________________________________________H         SYS$LIBRARY:____________________________________________________  G         AS$SDA.EXE[1],[5]                    System Dump Analyzer (SDA) D                                              extension for analyzingG                                              Advanced Server system and 2                                              dumps  G         CS$SDA.EXE[1],[5]                    System Dump Analyzer (SDA)tD                                              extension for analyzingB                                              common services dumps  ?         NETBIOSSHR.EXE[5]                    NetBIOS for DECnetR<                                              shareable image  A         PCDISKSHR.EXE[5]                     DOS File MaintenancetD                                              utility shareable image  H         PCSA_MAILSHR.EXE[5]                  Mail notification shareable2                                              image  D         PWRK$ACME_MODULE_ALPHA.EXE[4]        External authentication8                                              Alpha image  F         [1]This file is (or is associated with) an unsupported utility         or command procedure. :         [4]This file is installed with standalone externalB         authentication software installations as well as with full         server installations.r=         [5]This file is installed with the standalone LicenserA         Server software installations as well as with full serverl         installations.  H                                                 (continued on next page)  H                          Advanced Server Files and On-Disk Structure E-3 [  1      0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______t  E      File_________________________________Description________________n  E      SYS$LIBRARY:____________________________________________________o  E      PWRK$ACME_MODULE_VAX.EXE[4]          External authentication VAX /                                           imageP  D      PWRK$CMTLIBSHR.EXE[1],[3],[5]        Configurator, Monitor, andA                                           Tuner shareable library%E                                           (not usable with the latestaA                                           version of the AdvancedP=                                           Server for OpenVMS;fE                                           logging is now performed byo5                                           PWRK$PWMON)t  C      PWRK$CMT_LM.EXE[1],[3]               Advanced Server interfaceV>                                           to the Configurator,A                                           Monitor, and Tuner (nots@                                           usable with the latestA                                           version of the Advancede=                                           Server for OpenVMS;eE                                           logging is now performed by 5                                           PWRK$PWMON)h  D      PWRK$CMTSHR.EXE[1],[3],[5]           Configurator, Monitor, andD                                           Tuner shareable image (not@                                           usable with the latestA                                           version of the Advanced =                                           Server for OpenVMS;aE                                           logging is now performed bya5                                           PWRK$PWMON)s  C      [1]This file is (or is associated with) an unsupported utilityt      or command procedure.<      [3]This file is an unsupported utility and is no longer5      compatible with the Advanced Server for OpenVMS.m7      [4]This file is installed with standalone external ?      authentication software installations as well as with fulli      server installations.:      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations.t  E                                              (continued on next page)n  4      E-4 Advanced Server Files and On-Disk Structure o  g      H                              Advanced Server Files and On-Disk StructureH                                                E.1 Advanced Server Files  H         Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______  H         File_________________________________Description________________  H         SYS$LIBRARY:____________________________________________________  F         PWRK$CSSHR_V7.EXE                    Common services shareable2                                              image  A         PWRK$DEVCTL_DL1100.TLB[5]            DEClaser 1100 deviceS<                                              control library  A         PWRK$DEVCTL_DL2100.TLB[5]            DEClaser 2100 device[<                                              control library  B         PWRK$DEVCTL_DL2100P.TLB[5]           DEClaser 2100P device<                                              control library  A         PWRK$DEVCTL_DL2200.TLB[5]            DEClaser 2200 devicea<                                              control library  B         PWRK$DEVCTL_DL2200P.TLB[5]           DEClaser 2200P device<                                              control library  A         PWRK$DEVCTL_DL3200.TLB[5]            DEClaser 3200 deviceS<                                              control library  B         PWRK$DEVCTL_FX1050.TLB[5]            FX1050 device control4                                              library  A         PWRK$DEVCTL_FX850.TLB[5]             FX850 device controlN4                                              library  C         PWRK$DEVCTL_GENERIC.TLB[5]           Generic device controla4                                              library  G         PWRK$DEVCTL_HP_LASERJET.TLB[5]       HP LaserJet device controlR4                                              library  H         PWRK$DEVCTL_LA50.TLB[5]              LA50 device control library  H         PWRK$DEVCTL_LA51.TLB[5]              LA51 device control library  H         PWRK$DEVCTL_LA70.TLB[5]              LA70 device control library  H         PWRK$DEVCTL_LA75.TLB[5]              LA75 device control library  A         PWRK$DEVCTL_LA75P.TLB[5]             LA75P device control_4                                              library  =         [5]This file is installed with the standalone License A         Server software installations as well as with full servers         installations.  H                                                 (continued on next page)  H                          Advanced Server Files and On-Disk Structure E-5 .  t      0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______e  E      File_________________________________Description________________n  E      SYS$LIBRARY:____________________________________________________o  >      PWRK$DEVCTL_LA210.TLB[5]             LA210 device control1                                           library   >      PWRK$DEVCTL_LA324.TLB[5]             LA324 device control1                                           library   E      PWRK$DEVCTL_LG01.TLB[5]              LG01 device control library   E      PWRK$DEVCTL_LG02.TLB[5]              LG02 device control libraryd  E      PWRK$DEVCTL_LG06.TLB[5]              LG06 device control libraryr  E      PWRK$DEVCTL_LG31.TLB[5]              LG31 device control libraryi  >      PWRK$DEVCTL_LJ250.TLB[5]             LJ250 device control1                                           libraryi  E      PWRK$DEVCTL_LN03.TLB[5]              LN03 device control library2  B      PWRK$DEVCTL_LN03P.TLB[5]             LN03 PLUS device control1                                           librarya  >      PWRK$DEVCTL_LN03R.TLB[5]             LN03R device control1                                           libraryW  C      PWRK$DEVCTL_PROPRINTER.TLB[5]        Proprinter device controlN1                                           library   E      PWRK$DEVCTL_SILENTWRITER.TLB[5]      SilentWriter device control 1                                           libraryn  A      PWRK$FSLIB_ODS2.EXE[5]               ODS2/ODS5 addon librarya  C      PWRK$LICENSE_LIBSHR.EXE[5]           License shareable librarye  <      PWRK$LICENSE_MGMTSHR.EXE[5]          License management9                                           shareable imagen  C      PWRK$LMAPISHR.EXE[5]                 Advanced Server shareable /                                           image[  C      PWRK$LMRPCAPISHR.EXE[5]              Advanced Server shareable /                                           image.  :      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations.l  E                                              (continued on next page)*  4      E-6 Advanced Server Files and On-Disk Structure t         H                              Advanced Server Files and On-Disk StructureH                                                E.1 Advanced Server Files  H         Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______  H         File_________________________________Description________________  H         SYS$LIBRARY:____________________________________________________  F         PWRK$LMRPCSHR.EXE[5]                 Advanced Server shareable2                                              image  F         PWRK$LMRPCXNPSHR.EXE                 Advanced Server shareable2                                              image  F         PWRK$LMTASKSHR.EXE[5]                Advanced Server shareable2                                              image  F         PWRK$MGTLIBSHR.EXE[5]                Advanced Server shareable2                                              image  D         PWRK$MSV1_0_ACMESHR.EXE[4]           External authentication<                                              support library  D         PWRK$NBLIB_DECNET.EXE                Advanced Server network@                                              interface to DECnet  D         PWRK$NBLIB_NETBEUI.EXE               Advanced Server networkA                                              interface to NetBEUI   D         PWRK$NBLIB_TCPIP.EXE                 Advanced Server network@                                              interface to TCP/IP  D         PWRK$PCMSHR.EXE[5]                   Cache manager shareable2                                              image  E         PWRK$PRINTER_INFORMATION.DAT[5]      Printer information fileu  :         [4]This file is installed with standalone externalB         authentication software installations as well as with full         server installations. =         [5]This file is installed with the standalone License A         Server software installations as well as with full servert         installations.  H                                                 (continued on next page)  H                          Advanced Server Files and On-Disk Structure E-7 _  _      0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______t  E      File_________________________________Description________________i  E      SYS$LIBRARY:____________________________________________________   B      PWRK$SDA.EXE[1],[5]                  Extension for the SystemA                                           Dump Analyzer (SDA) for ?                                           analyzing systems anda=                                           dumps, for backward_A                                           compatibility (replaced_D                                           by AS$SDA.EXE, CS$SDA.EXE,>                                           and STREAMS$SDA.EXE)  D      PWRK$SDA_V1.EXE[1],[5]               Original extension for the>                                           System Dump Analyzer  B      PWRK$STREAMSSHR_V7.EXE[5]            Streams (protocol layer)9                                           shareable imagep  ?      PWRK$WHAT_TO_INSTALL.TXT             Text file used by thee@                                           installation procedure<                                           to display menu of>                                           installation options  D      PWRK$WINLIBSHR.EXE[5]                Advanced Server character-=                                           cell user interfaceu9                                           shareable imagel  D      PWRK$XTILIBSHR.EXE[5]                X/Open Transport Interface;                                           shareable library   D      PWRK$XTINETBIOSSHR.EXE[5]            X/Open Transport InterfaceE                                           shareable image for NetBIOSl  D      PWRK$XTINSPNBSHR.EXE[5]              X/Open Transport InterfaceD                                           shareable image for DECnet  B      STREAMS$SDA.EXE[1],[5]               System Dump Analyzer forE                                           analyzing streams (protocol @                                           layer) loadable imagesC      [1]This file is (or is associated with) an unsupported utility       or command procedure.:      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations.   E                                              (continued on next page)   4      E-8 Advanced Server Files and On-Disk Structure           H                              Advanced Server Files and On-Disk StructureH                                                E.1 Advanced Server Files  H         Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______  H         File_________________________________Description________________  H         SYS$LOADABLE_IMAGES:____________________________________________  G         PCFSDRIVERDEF.STB[5]                 Data structure definitions ;                                              for PCFSDRIVER   E         PWRK$STREAMSOS_V7.EXE[5]             Streams (protocol layer) B                                              system loadable image  =         PWRK$STREAMSOS_V7.STB[5]             Symbol table foreB                                              PWRK$STREAMSOS_V7.EXE=                                              (protocol layer)d  B         SYS$PCFSDRIVER_V7.EXE[5]             DECnet I/O and double;                                              mapping driver   =         SYS$PCFSDRIVER_V7.STB[5]             Symbol table for B                                              SYS$PCFSDRIVER_V7.EXE  E         SYS$PCIDRIVER_V7.EXE[5]              Cluster Interconnect I/O 3                                              driver   =         SYS$PCIDRIVER_V7.STB[5]              Symbol table forOA                                              SYS$PCIDRIVER_V7.EXEr  H         ________________________________________________________________H         SYS$MANAGER:____________________________________________________  C         PWRK$DEFINE_COMMANDS.COM[1],[5]      Command procedure that @                                              defines symbols forG                                              commands that run AdvancedA=                                              Server utilities   C         PWRK$SHOWSYS.COM[5]                  Command procedure that-H                                              shows status of file server6                                              processes  H         ________________________________________________________________H         SYS$MESSAGE:____________________________________________________  F         [1]This file is (or is associated with) an unsupported utility         or command procedure. =         [5]This file is installed with the standalone License A         Server software installations as well as with full server          installations.  H                                                 (continued on next page)  H                          Advanced Server Files and On-Disk Structure E-9 n         0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______S  E      File_________________________________Description________________   E      SYS$MESSAGE:____________________________________________________   E      PWRK$MSG.EXE[5]                      Advanced Server for OpenVMS 6                                           message file  E      ________________________________________________________________ E      SYS$STARTUP:____________________________________________________   B      PCSA$MAIL_STARTUP.COM[5]             PCSAMAIL command for TCPB                                           /IP clients invoking the?                                           PATHWORKS mail server[  A      PWRK$ACME_STARTUP.COM[4]             External authentication 6                                           startup file  @      PWRK$CHECK_PARAMS.COM[5]             Command procedure thatA                                           checks system resourcesM  @      PWRK$COMMON_LOGICALS.COM[5]          Command procedure thatA                                           defines common logicalsi  A      PWRK$COMMON_SHUTDOWN.COM[5]          Common shutdown commandp3                                           procedurea  @      PWRK$COMMON_STARTUP.COM[5]           Common startup command3                                           procedure   @      PWRK$GATHER_INFO.COM                 Command procedure thatB                                           gathers information intoB                                           a save set for reporting2                                           problems  B      PWRK$IS_REBOOT_NEEDED.COM            Command procedure calledB                                           during installation thatE                                           determines whether a reboot_3                                           is needede  7      [4]This file is installed with standalone external_?      authentication software installations as well as with full_      server installations.:      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations.   E                                              (continued on next page)   5      E-10 Advanced Server Files and On-Disk Structuret a         H                              Advanced Server Files and On-Disk StructureH                                                E.1 Advanced Server Files  H         Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______  H         File_________________________________Description________________  H         SYS$STARTUP:____________________________________________________  D         PWRK$LICENSE_R_START.COM[5]          Startup for the License6                                              Registrar  D         PWRK$LICENSE_S_START.COM[5]          Startup for the License3                                              Server   D         PWRK$LICENSE_SHUTDOWN.COM[5]         License Server shutdown>                                              command procedure  C         PWRK$LICENSE_STARTUP.COM[5]          License Server startupr>                                              command procedure  A         PWRK$LMBROWSER_START.COM             Browser startup filee  C         PWRK$LMMCP_START.COM                 Command procedure thattE                                              runs the Advanced ServerV7                                              controllers  H         PWRK$LMSRV_START.COM                 Command procedure that runs@                                              the Advanced Server  C         PWRK$LOGICALS.COM[5]                 Command procedure thattB                                              defines logical names  C         PWRK$PCSA_SHUTDOWN.COM               PATHWORKS for VMS V4.x G                                              shutdown command proceduree  G         PWRK$SHUTDOWN.COM[5]                 Shutdown command proceduree  F         PWRK$STARTUP.COM[5]                  Startup command procedure  H         ________________________________________________________________H         SYS$I18n.LOCALES.SYSTEM_________________________________________  @         PWRK$ISO8859-1-EURO.LOCALE           Locale file for theE                                              ISO8859-1-EURO charactere0                                              set  @         PWRK$ISO8859-1.LOCALE                Locale file for theD                                              ISO8859-1 character set:                                              (the default)  =         [5]This file is installed with the standalone LicensebA         Server software installations as well as with full serverW         installations.  H                                                 (continued on next page)  H                         Advanced Server Files and On-Disk Structure E-11 0  v      0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______   E      File_________________________________Description________________   E      SYS$I18n.LOCALES.SYSTEM_________________________________________   =      PWRK$ISO8859-2.LOCALE                Locale file for the A                                           ISO8859-2 character set   =      PWRK$ISO8859-5.LOCALE                Locale file for the A                                           ISO8859-5 character set   =      PWRK$ISO8859-7.LOCALE                Locale file for theFA                                           ISO8859-7 character setl  =      PWRK$ISO8859-8.LOCALE                Locale file for thecA                                           ISO8859-8 character set   =      PWRK$ISO8859-9.LOCALE                Locale file for theoA                                           ISO8859-9 character set   E      ________________________________________________________________ E      SYS$SYSTEM:_____________________________________________________0  B      PWRK$FIXMEMSRV.EXE                   Support image for member5                                           server role   <      NETBIOS.EXE[5]                       NetBIOS for DECnet  >      PCDISK.EXE[5]                        DOS File Maintenance1                                           utilityL  ?      PCSA$MAIL_SERVER.EXE[5]              PATHWORKS client mail 0                                           server  A      PCSA_CLAIM_NAME.EXE[5]               PCSA claim name utilityt  @      PCX$SERVER.COM                       Command procedure thatD                                           starts the PC DECwindows X0                                           server  C      PWRK$ACLADM.EXE                      Server configuration toold  B      PWRK$ADMIN.COM                       Remote Net Admin command3                                           proceduree  ?      PWRK$ADMIN_CFG.EXE                   Configuration Manager_1                                           utility_  :      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations.   E                                              (continued on next page)   5      E-12 Advanced Server Files and On-Disk StructureE L  0      H                              Advanced Server Files and On-Disk StructureH                                                E.1 Advanced Server Files  H         Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______  H         File_________________________________Description________________  H         SYS$SYSTEM:_____________________________________________________  D         PWRK$ADMIN_LIC.EXE[5]                License Manager utility  B         PWRK$BANNER.EXE                      Utility that collectsC                                              system information and E                                              inserts it at top of log 2                                              files  F         PWRK$BLOBADM.EXE                     Server configuration tool  F         PWRK$CHACL.EXE                       Server configuration tool  F         PWRK$CHDOMAIN.EXE                    Server configuration tool  D         PWRK$CHGROUP.EXE[1]                  Standalone utility thatH                                              manages the Advanced Server<                                              groups database  D         PWRK$CHUSER.EXE[1]                   Standalone utility thatH                                              manages the Advanced ServerC                                              user accounts databaseI  F         PWRK$CNVTOHFS.EXE[5]                 ODS-5 filename conversion4                                              utility  E         PWRK$DELETEACE.EXE[5]                File ACE removal utility   D         PWRK$FIXACE.EXE[5]                   File ACE repair utility  B         PWRK$ELFREAD.EXE                     Event log file reader4                                              utility  @         PWRK$EVTREPORT.EXE[5]                Event logger report6                                              generator  F         PWRK$GETROLE.EXE                     Server configuration tool  B         PWRK$KNBDAEMON.EXE[5]                Kernel NETBIOS daemon?                                              process for TCP/IP_  >         PWRK$LICENSE_REGISTRAR.EXE[5]        License Registrar  F         [1]This file is (or is associated with) an unsupported utility         or command procedure. =         [5]This file is installed with the standalone LicenseeA         Server software installations as well as with full serverK         installations.  H                                                 (continued on next page)  H                         Advanced Server Files and On-Disk Structure E-13 e  e      0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______   E      File_________________________________Description________________A  E      SYS$SYSTEM:_____________________________________________________r  8      PWRK$LICENSE_SERVER.EXE[5]           License Server  A      PWRK$LMBROWSER.EXE                   Advanced Server browser /                                           imageP  ;      PWRK$LMECHO.EXE[1]                   Debugging utility   D      PWRK$LMMCP.EXE                       Advanced Server controller  A      PWRK$LMSHARE.EXE[1]                  Standalone utility that E                                           manages the Advanced Server59                                           shares database   D      PWRK$LMSRV.EXE                       Advanced Server executable  ;      PWRK$LMSTAT.EXE[1]                   Debugging utility   <      PWRK$LOADSTREAMS_V7.EXE[5]           Loader for streamsA                                           (protocol layer) system 8                                           loadable image  E      PWRK$LR_SHOW_USAGE.EXE[1],[5]        License count units utilityn  ;      PWRK$LSACL.EXE[1]                    Debugging utilityA  C      PWRK$MAKEMACH.EXE                    Server configuration tooll  7      PWRK$MANAGER.EXE[5]                  ADMIN utilitye  ;      PWRK$MAPUNAME.EXE[1]                 Debugging utilitye  B      PWRK$MASTER.EXE[1]                   Master process and event0                                           logger  A      PWRK$MODAL.EXE[1]                    Standalone utility that E                                           manages the Advanced Server 9                                           modals database   C      [1]This file is (or is associated with) an unsupported utility       or command procedure.:      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations.X  E                                              (continued on next page)e  5      E-14 Advanced Server Files and On-Disk Structuren z         H                              Advanced Server Files and On-Disk StructureH                                                E.1 Advanced Server Files  H         Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______  H         File_________________________________Description________________  H         SYS$SYSTEM:_____________________________________________________  F         PWRK$MONITOR.EXE[1],[3],[5]          PATHWORKS Monitor utilityH                                              (not usable with the latestD                                              version of the Advanced@                                              Server for OpenVMS;D                                              replaced by PWRK$PWMON)  G         PWRK$NBDAEMON.EXE[5]                 NetBIOS daemon process for 4                                              NetBEUI  H         PWRK$NBSHOW.EXE[1],[5]               NetBEUI show status utility  >         PWRK$NETEVENT.EXE[1]                 Debugging utility  G         PWRK$PWMON.EXE[1],[5]                Host-based monitor utility   ?         PWRK$REGUTL.EXE[5]                   Registry parameter ?                                              management utility   F         PWRK$RMACL.EXE                       Server configuration tool  F         PWRK$SAMCHECK.EXE                    Server configuration tool  H         PWRK$SETSHO.EXE[5]                   Set/Show Parameters utility  B         PWRK$SHOWINI.EXE[1]                  Utility that displaysA                                              server configurationr7                                              parameterse  D         PWRK$SHOWQUOTA.EXE[5]                Show Disk Quota utility  >         PWRK$SRVCONFIG.EXE[1]                Debugging utility  @         PWRK$START.EXE[5]                    Utility that startsD                                              detached master process  @         PWRK$START_PRINTERS.EXE              Utility that startsG                                              printer queues and printer 9                                              destinations   F         [1]This file is (or is associated with) an unsupported utility         or command procedure. ?         [3]This file is an unsupported utility and is no longerT8         compatible with the Advanced Server for OpenVMS.=         [5]This file is installed with the standalone License A         Server software installations as well as with full serverV         installations.  H                                                 (continued on next page)  H                         Advanced Server Files and On-Disk Structure E-15           0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______   E      File_________________________________Description________________S  E      SYS$SYSTEM:_____________________________________________________V  ;      PWRK$STARTSVC.EXE[1]                 Debugging utility_  C      PWRK$STOP.EXE[5]                     Utility that stops server_3                                           processesN  C      PWRK$VAPFADM.EXE                     Server configuration tool   ?      PWRK$VERIFY.EXE[5]                   Utility that verifies B                                           configuration parameters  E      ________________________________________________________________ E      SYS$TEST:_______________________________________________________   C      PWRK$PCSI_IVP.COM                    Installation Verification 9                                           Procedure (IVP)_  C      PWRK$PCSI_IVP.DAT                    Installation Verification_=                                           Procedure data filee  E      ________________________________________________________________oE      SYS$UPDATE:_____________________________________________________   =      PWRK$COMMANDS.CLD[5]                 Server command linee5                                           definitions   @      PWRK$COMMON.SAV[2],[5]               Backup saveset for theB                                           initial server directory.                                           tree  >      PWRK$COMMON_CONFIG.COM[5]            Common configuration;                                           command procedure_  @      PWRK$CONFIG.COM[5]                   One-time configuration;                                           command procedure   @      PWRK$DEFINE_FORMS.COM[2],[5]         Command procedure that?                                           defines printer forms   C      [1]This file is (or is associated with) an unsupported utility       or command procedure.<      [2]This file is deleted after you configure the server.:      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations.   E                                              (continued on next page)   5      E-16 Advanced Server Files and On-Disk Structure            H                              Advanced Server Files and On-Disk StructureH                                                E.1 Advanced Server Files  H         Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______  H         File_________________________________Description________________  H         SYS$UPDATE:_____________________________________________________  D         PWRK$DEINSTAL.COM                    Advanced Server removalB                                              command procedure (ifC                                              server is installed bynB                                              PCSI, use the PRODUCTH                                              REMOVE command to deinstall4                                              server)  H         PWRK$GETPARAM.COM[5]                 Command procedure that getsF                                              a parameter from PWRK.INI  C         PWRK$INSTALL_COMMANDS.COM[5]         Command procedure that E                                              installs Advanced Serverl9                                              DCL commandso  C         PWRK$LANMAN.SAV[2],[5]               BACKUP saveset for thenD                                              initial Advanced Server;                                              directory tree   F         PWRK$LICENSE_CONFIG.COM[5]           License Server configura-C                                              tion command proceduret  G         PWRK$LICENSE.SAV                     PATHWORKS client licensingOD                                              software BACKUP saveset  H         PWRK$LMCONFIG.COM                    Command procedure that setsD                                              up the initial AdvancedB                                              Server directory tree  C         PWRK$MIGRATE_INI.COM[5]              Command procedure that5@                                              migrates LANMAN.INIF                                              parameters to the OpenVMS5                                              Registry   ?         [2]This file is deleted after you configure the server.   =         [5]This file is installed with the standalone License A         Server software installations as well as with full server          installations.  H                                                 (continued on next page)  H                         Advanced Server Files and On-Disk Structure E-17 L  P      0      Advanced Server Files and On-Disk Structure      E.1 Advanced Server Files  E      Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______   E      File_________________________________Description________________d  E      SYS$UPDATE:_____________________________________________________v  ;      PWRK$PCSI_CHECK_SYS$SPECIFIC.COM     Command procedurem>                                           that detects whetherD                                           SYS$SPECIFIC has any files@                                           or images that must beE                                           removed before installation   B      PWRK$PCSI_CLEANUP_SYS$SPECIFIC.COM   Command procedure calledA                                           by the installation and_C                                           deinstallation proceduresLE                                           to remove old server imagesI9                                           in SYS$SPECIFIC   @      PWRK$PCSI_REMOVE_MASTER.COM          Deinstallation command@                                           procedure for removingC                                           Advanced Server files and 0                                           images  <      PWRK$PWUTIL.SAV[2]                   BACKUP saveset for@                                           PATHWORKS client-based3                                           utilitiess  @      PWRK$RESTORE_NETBIOS.COM             Command procedure thatB                                           stores the NETBIOS image=                                           after the server is 5                                           deinstalled1  ;      PWRK$SETINI.COM[5]                   Command procedured=                                           that updates server_B                                           configuration parameters  E      PWRK$SETPARAM.COM[5]                 Command procedure that setsOA                                           a parameter in PWRK.INI   @      PWRK$VERSIONS.COM[5]                 Command procedure thatE                                           shows server image versions <      [2]This file is deleted after you configure the server.  :      [5]This file is installed with the standalone License>      Server software installations as well as with full server      installations. E      ________________________________________________________________8  5      E-18 Advanced Server Files and On-Disk Structure            H                              Advanced Server Files and On-Disk StructureH                                    E.2 Advanced Server On-Disk Structure  -         E.2 Advanced Server On-Disk Structure_  E               Figure E-1 shows the Advanced Server on-disk structure. ?               Note that only part of the substructure is shown.   2               Figure E-1 On-Disk Structure Diagram  *               pwrk$commonroot, pwrk$lmroot                 |                  |___datafiles                  |                  |___lanman                 |R"                 |     ---.accounts#                 |     ---.datafiles                  |     ---.debugS!                 |     ---.domainsC                 |     ---.logs                 |     ---.repl!                 |     ---.samsave                   |     ---.shares!                 |     ---.upgrade                  |                  |___licenseP                 |                  |___logs                 |                  |___params                 |e                 |___perfdata                 |                  |___print                  |X                 |___sectiont                 |                  |___spool                  |                  |___temp              H                         Advanced Server Files and On-Disk Structure E-19 e r                     H                                                                        FH         ________________________________________________________________  H                                            Advanced Server Logical Names      D               Table F-1 describes the logical names that are created?               when you configure and start the Advanced Server._  H         Table_F-1_Advanced_Server_Logical_Names_________________________  H         Logical_Name_______________Description__________________________  D         NETBIOS$DEVICE             Used for the DECnet device - thisE                                    logical name is not defined duringcE                                    installation; it is used to define A                                    network adapters under certain G                                    circumstances (for more information,BH                                    see Section 3.11, The Advanced Server3                                    Network Adapter)o  D         PWRK$ACME_SERVER           On an OpenVMS Cluster member thatE                                    is not running the Advanced Server D                                    software and does not have accessF                                    to external authentication softwareE                                    by means of a shared cluster disk, B                                    defines OpenVMS Advanced ServerH                                    cluster members designated to processG                                    external authentication requests fornD                                    that member; this logical name isG                                    not defined during installation (forKG                                    more information, see Section 5.7.1,EH                                    Setting Up External Authentication in4                                    OpenVMS Clusters)  H                                                 (continued on next page)          H                                        Advanced Server Logical Names F-1 g  t      "      Advanced Server Logical Names    E      Table_F-1_(Cont.)_Advanced_Server_Logical_Names_________________   E      Logical_Name_______________Description__________________________   D      PWRK$ACME_DEFAULT_DOMAIN   Defines the default domain for usersC                                 using external authentication; this B                                 logical name is not defined duringC                                 installation (for more information,.C                                 refer to the Compaq Advanced ServertB                                 for OpenVMS Server Administrator's&                                 Guide)  A      PWRK$ADDON_LIBRARY         Location of file system shareables&                                 images  @      PWRK$COMMON                Top-level directory for Advanced&                                 Server  B      PWRK$COMMONROOT[1]         Root of the Advanced Server common.                                 directory tree  ?      PWRK$DATAFILES             Character code page translationc,                                 mapping data  @      PWRK$KNBDAEMON_DEVICE      Used for the TCP/IP device, thisB                                 logical name is not defined duringB                                 installation; it is used to define>                                 network adapters under certainD                                 circumstances (for more information,E                                 see Section 3.11, The Advanced Servera0                                 Network Adapter)  4      PWRK$LANMAN                Advanced Server area  ,      PWRK$LICENSE               License area  ?      PWRK$LMDATAFILES           Advanced Server data files area   B      PWRK$LMDEBUG               Area where trace files are written  D      PWRK$LMDOMAINS             Advanced Server domain database area  =      PWRK$LMLOGS                Advanced Server log file areaA  E      PWRK$LMROOT[1]             Root of the Advanced Server directoryA$                                 tree  =      PWRK$LMMSGFILES            Advanced Server message filest  A      [1]This logical name requires that you specify the directorye
      with it.   E                                              (continued on next page)   &      F-2 Advanced Server Logical Names           H                                            Advanced Server Logical Names    H         Table_F-1_(Cont.)_Advanced_Server_Logical_Names_________________  H         Logical_Name_______________Description__________________________  ?         PWRK$LMUPGRADE             Advanced Server upgrade areaa  @         PWRK$LOADSTREAMS           Logical for LoadStreams image  7         PWRK$LOGS                  Common log file areaa  H         PWRK$LR_DISABLE_CLIENT_    Defines whether the License RegistrarD         PING                       checks for a client-based licenseG                                    or, instead, attempts immediately toFE                                    assign a server-based license. ForeH                                    more information, refer to the CompaqG                                    Advanced Server for OpenVMS Guide to_E                                    Managing Advanced Server Licenses.M  C         PWRK$LR_LICENSE_REPORT_    Determines the interval at whicheF         INTERVAL                   reports about server-based licenses?                                    are generated in the LicenseeH                                    Registrar log file; by default, these<                                    reports are not generated  G         PWRK$LR_LOG_SERVERBASED_   Determines whether events related toED         ACTIVITY                   server-based licensing are logged  A         PWRK$LS_V7_ACCESS_UPGRADE  Included in the License ServeriA                                    startup file to allow upgradesiC                                    of PATHWORKS V5 for OpenVMS (LAN C                                    Manager) client license requestst  D         PWRK$NETBEUI_DEVICE        Used for the NetBEUI device, thisE                                    logical name is not defined duringrE                                    installation; it is used to defineaA                                    network adapters under certainiG                                    circumstances (for more information,fH                                    see Section 3.11, The Advanced Server3                                    Network Adapter)Q  1         PWRK$PARAMS                Parameter area   F         PWRK$PERFDATA              Advanced Server monitor performance1                                    data directory   C         PWRK$PRINT                 Advanced Server printer database ,                                    directory  H                                                 (continued on next page)  H                                        Advanced Server Logical Names F-3 a  c      "      Advanced Server Logical Names    E      Table_F-1_(Cont.)_Advanced_Server_Logical_Names_________________d  E      Logical_Name_______________Description__________________________   2      PWRK$SAMSAVE               SAMCHECK data area  2      PWRK$SAMSAVEX              SAMCHECK data area  1      PWRK$SECTION               Section file area   *      PWRK$SPOOL                 Spool area  >      PWRK$TEMP                  Advanced Server temporary area  E      PWRK$VERSION_______________Advanced_Server_version______________s                                                            &      F-4 Advanced Server Logical Names e  v                          E      ________________________________________________________________   E                                                                 Index     B      A                                    Advanced Server (cont'd)D      ___________________________           sample removal procedure,1      ADMIN/CONFIG                             7-6   9        See Configuration Manager           starting,  5-2o:      Administrator account                 starting duringB        local to member server,                configuration,  3-168          3-14                              startup,  5-39      Administrator account                 stopping,  5-7_C         password                           user accounts, removing, 1        changing, 3-16                         7-2 >        for member server, 3-14            Advanced Server disk=        joining a domain, 3-15              changing the,  3-6 @        setting, 3-14                      Advanced Server imagesD        verifying, 3-15                     checking status of,  1-229        whether to provide during          Alerter service_@          configuration,  3-15              description of,  3-10      Advanced ServerE        cluster alias, 3-12                B__________________________ >        data files, removing, 7-2          BACKUP command, 1-17B        files, E-1                         Backup domain controllerD        files detected in                   designating,  3-11, 3-23,2          SYS$SPECIFIC:,  2-16                 3-25C        logical names, F-1                 Backup domain controllers B        logical names,                      configuring transports,1          deassigning,  7-3                    3-7,.        NETBIOS image, removing,           Boot          7-25        on-disk structure, E-19             See Rebootf          role, 3-11, 3-23t           changing, 3-27           configuring, 3-25         sample installation and          configuration,  B-1  E                                                               Index-1o a  i            >                                           Configuring (cont'd)?      C__________________________           member server,  3-28   D      Character set,  3-13, 3-24            member server transports,1        configuring, 3-33                      3-7OC           considerations, 3-33             wide area networks,  3-7AB           example, 3-34                   Converting file names to8      Checklist for installation,            ODS-5,  5-149         A-1                               Convert utilityYC      Client-based server                   See File name conversion 5         administration tools,                 utilityr         5-19E      Client software,  1-10               D__________________________   4      Clusters                             Data files  9        See OpenVMS Clusters                removing,  7-2t3      Code page,  3-34                     Data loss <      Computer name,  3-11                  preventing,  1-17;        SCSNODE parameter and,              restoring during D          1-16                                 reconfiguration,  3-41?      Configuration Manager,               Daylight savings timeM9         1-13, 3-3                          setting,  1-19 .      Configuration procedure              DCPSB        Advanced Server, 3-2                See DECprint Supervisor=        disk space required, 3-6               (DCPS) software 0        for previously configured          DECnet:          server,  3-41                     checking,  1-20:        logical names created,              starting,  1-208          F-1                              DECnet objects9        preparing for the                   removing,  7-3 5          Advanced Server,  3-5            DECnet-Plusc:        prerequisites, 3-5                  checking,  1-21:        responding to prompts,              starting,  1-21?          3-16, 4-4                        DECnet transport, 1-9 A        sample script for                   checking status,  1-20 9          standalone License                running duringWB          Server,  C-1, C-3                    configuration,  1-20D        starting, 3-16                     DECprint Supervisor (DCPS):        starting server during,              software,  1-5B          3-16, 3-21, 4-6                  Deinstallation procedure7      Configuration settings                See Removing 6        modifying, 3-22                    Deinstalling>      Configuring                           Advanced Server for5        backup domain controller               OpenVMS B          transports,  3-7                     guidelines for,  7-1        Index-2 c  S            C         Device name, 2-2                    External authenticationaC         Disk, system                          See also Pass-through1?          restrictions during                     authenticationF>             installation,  2-16               bypassing,  5-14@         Disk space                            configuring clientF          determining,  1-17                      connections for, 5-13@          requirement for                      in clusters,  1-22E             configuration,  3-6               on a system not running E         Disk space requirements,                 the Advanced Server, 5           1-17                                   5-11lF         DNS                                   requirement over DECnet-;          configuring to use,  6-10               Plus, 5-13lD          setup,  6-9                          server capacity,  5-13>         Domain                                setting up,  5-8C          joining automatically, by            setting up in OpenVMSS?             PWRK$CONFIG,  3-15                   Clusters, 5-11iC          joining manually, by               External authenticatione7             ADMINISTER ADD COMPUTER            softwaredG             command,  3-15                    sample installation,  D-1 F         Domain administrator                  standalone installation,4           account                                2-3           local to member server,G             3-14                            F__________________________r@         Domain administrator                File name conversion<           account password                     utility, 5-15          changing,  3-16!          for member server,  3-14eG          joining a domain,  3-15            G__________________________d  >          verifying,  3-15                   GBLPAGES parameterD          whether to provide during            checking and defining,5             configuration,  3-15                 1-14dA         Domain name                         GBLSECTIONS parametereD          term defined,  3-11                  checking and defining,5         Domain role                              1-15           changing,  3-27-          configuring,  3-25                 HiG                                             ___________________________cB         E__________________________         Hardware requirements,8         Extended character sets,               1-9, 1-12             3-13, 3-24, 3-33          configuring             example,  3-34  H                                                                  Index-3 s  d            6                                           IVP (cont'd)8      I__________________________           running after  @      Installation                             installation,  5-2        checklist, A-1 E      Installation procedure               K__________________________ 6        external authentication,           Kit contents:          D-1                               checking,  1-11        failure, another server+          running,  2-15                   L E        failure, installing on             ___________________________ >          OpenVMS VAX,  2-15               Language, 3-13, 3-24;        failure, system disk has            code page,  3-34 =          other server files,               configuring,  3-33 C          2-16                                 considerations,  3-33 <        files installed, 2-15,                 example,  3-34?          E-1                              LANMAN.INI parameters ?        interrupting, 2-6                   migrating to OpenVMSa<        prerequisites, 2-2                     Registry,  3-4E        PWRK$STREAMSOS_V*.EXE              LanmanIniMigrated parameter 2          detected,  2-9                     ,  3-4C        sample script for                  License Server, 1-6, 3-10nC          Advanced Server,  B-1             configuration procedure, 1        sample script for                      4-1 B          standalone License                installation procedure,1          Server,  C-1                         4-1 C        standalone License Server           standalone installation,e1          ,  4-1                               2-3 E        starting, 2-4                       startup and shutdown,  4-3lA        what it does, 2-1                  Licensing requirements, /      Installation requirements              1-5_1        disk space, 1-17                   LMHOSTS C        hardware, 1-9, 1-12                 configuring to use,  6-2 C        licensing, 1-5                      transport configuration, 1        memory, 1-10                           3-8 B        software, 1-9, 1-12                LMHOSTS name resolution,/      Installation Verification              3-8eC         Procedure                         Load balancing, 3-7, 3-9,T4        See IVP                              6-2, 6-97      Installed files                      Logical namesO@        displaying, 2-15                    Advanced Server,  F-1<      IVP                                   deassigning,  7-3B        during installation, 2-13           startup procedure,  5-3          Index-4 e  l            B                                             Network interface cardA         M__________________________           See Network adapterS  =         Management commands                 Network transporte@          shortcuts for,  5-8                   requirements, 1-9/         Member server                       NIC A          advantage of,  3-28                  See Network adapter           configuring,  3-28n-          designating,  3-11, 3-23,          O G             3-25                            ___________________________ D          in OpenVMS cluster,  3-7           On-disk structure,  E-19<          local Administrator                OpenVMS ClustersE             account password,  3-14           checking configuration, 5         Member servers                           1-11NH          configuring transports,              cluster alias,  3-12, 3-24C             3-7                               configuring nodes in,L:         Memory requirements, 1-10                3-3, 3-39F         Migrating                             disk device for AdvancedB          LANMAN.INI parameters,                  Server files, 3-6?             1-3                               enabling externaleC          to Advanced Server,  1-3                authentication in,r4                                                  5-9E         N__________________________           external authenticatione9         NETBIOS$ACCESS OpenVMS                   in, 5-11)E           identifier                          installation in,  1-22, 5          removing,  7-2                          3-16ME         NETBIOS$DEVICE, 3-42                  LMHOSTS file,  3-8, 6-6 H         NETBIOS image                         load balancing,  3-7, 3-8,9          removing,  7-2                          3-9, 6-2rG         NetBIOS name resolution               load balancing using DNS, 4          using DNS,  6-9                         6-9H          using LMHOSTS,  6-2                  loading PAKs on,  1-6, 4-2B          using WINS,  6-8                     member servers,  3-7D         NETBIOS process, 3-43                 running License Server=         Netlogon service, 3-11                   on, 1-6, 4-2 G         NetLogon service                      sample standalone License H          fails to start,  3-12                   Server installation andC         Network adapter, 3-41                    configuration, C-1SC          defining,  3-42                      server role in,  3-11RG          NETBIOS$DEVICE,  3-42                starting server in,  4-7,E4          not found,  3-43                        5-4C          OpenVMS logicals,  3-42              upgrading to AdvancedaD          PWRK$KNBDAEMON_DEVICE,                  Server for OpenVMS,4             3-42                                 1-4#          PWRK$NETBEUI_DEVICE,  3-42   H                                                                  Index-5 e               2      OpenVMS Clusters (cont'd)            PasswordA        WINS Server setup for,              administrator account, 2          6-9                                  3-15C      OpenVMS reboot                       PATHWORKS (NetWare) files D        delaying, 2-10                      detected on installation,2        preventing if unnecessary              2-16D          ,  2-10                          PATHWORKS Advanced Servers?        when needed, 2-9, 2-10              installing on,  2-16 :      OpenVMS Registry,  3-4                upgrading,  1-2?        removing server                    PATHWORKS for OpenVMSa<          parameters,  7-3                  files detected inB        server parameter values                SYS$SPECIFIC:,  2-16B          at startup,  5-7                 PATHWORKS V5 for OpenVMS9        starting, 1-13                       (LAN Manager)a:      OpenVMS Registry Server,              upgrading,  1-3  C         1-3                               PCSI (POLYCENTER Software A        starting, 1-13                       Installation utility) ;      OpenVMS VAX systems,  2-15            See Installation 7      Operating system                         procedure =         requirements, 1-9                 POLYCENTER Software-@      Optional software,  5-18               Installation utility  ;      P                                     See Installationg7      ___________________________              procedure A      Parameters                           Postinstallation tasks,D/        affecting system, 3-3,               5-1I@          3-6                              Preinstallation tasks,5        LanmanIniMigrated, 3-4               1-11, 2-2r?        migrating, 3-4                      checklist for,  1-10gC        removing, 7-3                      Primary domain controllerSD        server configuration,               designating,  3-11, 3-23,2          3-18                                 3-25B           configuring, 3-22               Printer management style=      Parameter settings                    configuring,  3-36 <        affecting system, 3-3,                 example,  3-38@          3-6                               considerations,  3-372        server, 3-18                       PrintersE           configuring, 3-22                management of,  3-13, 3-24v@      Part listing                             configuring style,5        checking, 1-11                            3-36 C      Pass-through authentication              considerations,  3-37 ?         , 6-6                             PROCSECTCNT parameterT  A        See also External                   checking and defining, 2          authentication                       1-15        Index-6                 ;         Product identifier, 2-2             Reboot (cont'd)n  H         Protocols                             and system changes,  1-14,5          See Transports                          1-17NH         PWCONVERT command, 5-15               avoiding on cluster,  1-23=         PWRK$ACME_SERVER logical,             delaying,  2-10EG           5-12                                preventing if unnecessary 7         PWRK$CONFIG procedure                    , 2-10RG          See Configuration                    requirements after,  3-16a=             procedure                         starting serverdF         PWRK$DEFINE_COMMANDS.COM,                automatically during,4           5-8                                    5-4E         PWRK$DELETEACE                        when needed,  2-9, 2-10_B          removing,  7-2                     Reconfiguration,  3-41  4         PWRK$FIXACE                         Registry  B          removing,  7-2                       See OpenVMS Registry;         PWRK$KNBDAEMON process,             Registry Serverd=           3-43                                starting,  1-13 ?         PWRK$KNBDAEMON_DEVICE,              Release notes,  1-8n<           3-42                                location afterC         PWRK$NBDAEMON process,                   installation, 2-15 <           3-43                                printing,  1-84         PWRK$NETBEUI_DEVICE, 3-42           RemovingD         PWRK$REGUTL utility, 1-13,            Advanced Server,  7-1,9           3-5                                    7-2, 7-3eB         PWRK$STARTUP.COM                      server configuration@          See Startup procedure                   parameters, 7-3  -         PWRK$STREAMSOS_V*.EXE               SrG          detected during                    ___________________________r=             installation,  2-9              SCSNODE parametera=                                               defining,  1-16eD         Q__________________________         Security Account ManagerC         Queue manager                          (SAM) database, 3-3379          running during                       files,  3-5oF             configuration,  1-18            Security accounts database?          starting,  1-18                      on primary domain B                                                  controllers, 3-25G         R                                   Server administration toolsd?         ___________________________           installing,  5-18eD         Reboot                              Server announce comment,3          and DECprint Supervisor               3-12              for OpenVMS              installation,  1-5  H                                                                  Index-7                 :      Server configuration                 Startup (cont'd):         parameters, 3-18                   procedure,  5-3C        configuring, 3-22                   storing OpenVMS Registry E        migrating from LANMAN.INI              server parameter values 4          ,  3-4                               ,  5-7E      Servers                               troubleshooting,  5-5, 5-6 D        capacity for external               using the SYSMAN utility,1          authentication,  5-13                5-5 8        starting during                    SYSTEM account?          configuration,  3-21,             logging in to,  1-12 =          4-6                              System backup, 1-17 5      Server system configuration          System disk_>         parameters, 3-3, 3-6               restrictions duringA      SHOW QUEUE/MANAGER command,              installation,  2-16n;         1-18                               space needed for A      Shutdown procedure,  5-7                 installation,  1-17 ;      Software requirements,               System parameters A         1-9, 1-12                          checking and defining, 2      Standalone License Server,               1-147         1-6, 4-2                          System reboott:        sample installation and             delaying,  2-10D          configuration procedure           preventing if unnecessary5          ,  C-1                               ,  2-10fB        startup, 4-6                        when needed,  2-9, 2-10  
      Starting E        Advanced Server, 5-2               T__________________________ 5        Advanced Server during             TCP/IP, 1-9 A          configuration,  3-16              checking status,  1-21mC        DECnet, 1-20, 1-21                  configuring the Advanced @        License Server                         Server to support,2          automatically,  4-7                  1-21=        License Server manually,            in clusters,  1-22-:          4-6                               starting,  1-21D        OpenVMS Registry, 1-13             TCP/IP cluster alias, 3-9,0        standalone License Server            3-12E          ,  4-6                           TCP/IP cluster impersonatorS<        TCP/IP, 1-21                         name,  3-9, 3-12-      START/QUEUE/MANAGER command          TDF @         , 1-18                             See Time differential      Startup4        Advanced Server, 5-3                   factorB        automatic, 5-4                     Time differential factor9        in OpenVMS Clusters, 5-4            setting,  1-19p          manual, 5-4        Index-8                 0         Timesource service                  WINSF          description of,  3-10                configuring to use,  6-89         Time zone setting, 1-19               setup,  6-8s?          checking,  1-18                      setup for OpenVMSe>         Transports                               Clusters, 6-9F          for LMHOSTS,  3-8                    transport configuration,4          for WINS,  3-7                          3-7          selecting,  3-7  #         U__________________________            Unicode (UCS-2)             See Extended character              sets         Upgrading           file servers,  1-2           OpenVMS Clusters,  1-4           PATHWORKS Advanced              Servers,  1-3          User accounts           removing,  7-2u  #         W__________________________i           Wide area domain, 6-1u         Wide area networking          providing,  3-7         Windows 2000#          domain environment,  3-25,              3-28         Windows 2000 mixed-modet           domain,  3-25t          Windows 2000 native-mode           domain,  3-25          Windows NT printer!           management,  3-13, 3-24           configuring,  3-36e             example,  3-38          considerations,  3-37         Windows NT server            administration tools,t           5-19          installing,  5-18  H                                                                  Index-9