Compaq Advanced Server for OpenVMS Server Installation and Configuration Guide Order Number: AA-RFM3B-TE March 2001 This guide explains how to install and configure the Advanced Server for OpenVMS software. Revision/Update Information: This manual super- sedes the Server Installation and Configuration Guide, AA-RFM3A-TE Operating System: OpenVMS Alpha Version 7.2-1 Software Version: Advanced Server V7.3 for OpenVMS Compaq Computer Corporation Houston, Texas __________________________________________________________ © 2001 Compaq Computer Corporation Compaq, the Compaq logo, VAX, and VMS Registered in U.S. Patent and Trademark Office. AlphaStation, DEC, DECnet, DECwindows, PATHWORKS, OpenVMS, and POLYCENTER are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Intel is a trademark of Intel Corporation in the United States and other countries. UNIX is a trademark of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under 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. ZK6540 The Compaq Advanced Server for OpenVMS documentation set is available on CD-ROM. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. xi 1 Before You Install Advanced Server for OpenVMS Software 1.1 About the Advanced Server Software Kit.......... 1-1 1.1.1 About VAX Systems ............................ 1-2 1.1.2 Upgrading to Advanced Server for OpenVMS ..... 1-2 1.1.2.1 LANMAN.INI Parameters Migrate to OpenVMS Registry................................... 1-3 1.1.2.2 Upgrading OpenVMS Clusters................. 1-4 1.2 Installing DECprint Software.................... 1-5 1.3 About Licensing................................. 1-5 1.3.1 License Requirements ......................... 1-5 1.3.2 About the License Server ..................... 1-6 1.4 About External Authentication................... 1-7 1.5 About the Release Notes......................... 1-8 1.5.1 How to Access the Release Notes Before Installation.................................. 1-8 1.5.2 How to Access the Release Notes After the Installation.................................. 1-8 1.6 Using the Installation Checklist................ 1-8 1.7 Requirements for Installing Advanced Server for OpenVMS Software................................ 1-9 1.7.1 Hardware Requirements ........................ 1-9 1.7.2 Software Requirements ........................ 1-9 1.7.3 Supported Client Software .................... 1-10 1.7.4 Memory Requirements .......................... 1-10 1.8 Preinstallation Tasks........................... 1-10 1.8.1 Step 1: Check the Part Listing ............... 1-12 1.8.2 Step 2: Check the Network Hardware ........... 1-12 1.8.3 Step 3: Log In to the SYSTEM Account ......... 1-12 iii 1.8.4 Step 4: Check the Required Software .......... 1-12 1.8.5 Step 5: Start the OpenVMS Registry Server .... 1-13 1.8.6 Step 6: Print and Read the Release Notes ..... 1-14 1.8.7 Step 7: Check System Parameters .............. 1-14 1.8.7.1 GBLPAGES Parameter......................... 1-14 1.8.7.2 GBLSECTIONS Parameter...................... 1-15 1.8.7.3 PROCSECTCNT Parameter...................... 1-15 1.8.7.4 SCSNODE Parameter.......................... 1-16 1.8.8 Step 8: Back Up the System ................... 1-17 1.8.9 Step 9: Check Disk Space Requirements ........ 1-17 1.8.10 Step 10: Check the Queue Manager ............. 1-18 1.8.11 Step 11: Check Time Zone and TDF ............. 1-18 1.8.12 Step 12: Check DECnet Status ................. 1-20 1.8.12.1 Checking DECnet (Phase IV) Status.......... 1-20 1.8.12.2 Checking DECnet-Plus Status................ 1-21 1.8.13 Step 13: Check TCP/IP Status ................. 1-21 1.8.14 Step 14: Check for Existing OpenVMS Server Images and Files.............................. 1-22 1.8.15 Step 15: Check OpenVMS Cluster Configuration................................. 1-22 1.9 Next Step....................................... 1-24 2 Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure...................... 2-1 2.1.1 Before You Start the Installation Procedure .. 2-2 2.1.2 Installing the Server ........................ 2-4 2.1.3 What To Do After the Installation Completes .. 2-14 2.2 Troubleshooting Installation Problems........... 2-15 2.2.1 Installing Advanced Server for OpenVMS Software on a VAX System...................... 2-15 2.2.2 Installing Advanced Server for OpenVMS on a System Running Another Advanced Server Image......................................... 2-15 2.2.3 System Disk Restrictions ..................... 2-16 2.2.4 Installing Advanced Server for OpenVMS on a System with PATHWORKS for OpenVMS (Advanced Server), Version 6.0A or Earlier.............. 2-16 2.3 Next Steps...................................... 2-17 iv 3 Configuring the Advanced Server 3.1 About the Advanced Server Configuration Procedure....................................... 3-2 3.1.1 What the Configuration Procedure Does ........ 3-2 3.2 Migrating LANMAN.INI Parameters to the OpenVMS Registry........................................ 3-4 3.3 Before You Start the Advanced Server Configuration Procedure......................... 3-5 3.3.1 On What OpenVMS Disk Device Do You Want to Store the Advanced Server Data Files?......... 3-5 3.3.2 Do You Want to Change the System Configuration Parameters Now?............................... 3-6 3.3.2.1 Configuring Transports for a Backup Domain Controller or Member Server................ 3-7 3.3.3 Do You Want to Change Any of the Server Configuration Settings?....................... 3-10 3.3.4 What Do You Want the Administrator Account Password to Be?............................... 3-14 3.3.5 Are You Going to Supply Account/Password Information?.................................. 3-15 3.3.6 What Is the Domain Administrator Password? ... 3-15 3.3.7 Do You Want to Enter a New Administrator Account Password?............................. 3-16 3.3.8 Do You Want to Start the Server? ............. 3-16 3.4 How to Start the Advanced Server Configuration Procedure....................................... 3-16 3.5 How to Respond to Advanced Server Configuration Prompts......................................... 3-16 3.6 How to Change Server Configuration Settings..... 3-22 3.7 Configuring the Advanced Server Domain Role..... 3-25 3.7.1 Configuring the Advanced Server As a Member Server........................................ 3-28 3.7.1.1 Configuring a New Advanced Server for OpenVMS to Be a Member Server.............. 3-29 3.7.1.2 Configuring an Existing Advanced Server for OpenVMS BDC As a Member Server............. 3-32 3.8 Configuring the Server Language................. 3-33 3.8.1 Considerations Regarding the Server Language...................................... 3-33 3.8.2 Example of Configuring the Server Language ... 3-34 3.9 Configuring Windows NT Printer Management....... 3-36 v 3.9.1 Considerations Regarding Windows NT Printer Management.................................... 3-37 3.9.2 Example of Configuring Windows NT Printer Management.................................... 3-38 3.10 Troubleshooting Configuration Procedure Problems........................................ 3-39 3.10.1 Registry Server Startup Problems ............. 3-39 3.10.2 Ensuring Sufficient Resources to Support Clients....................................... 3-40 3.10.3 If Problems Occur When Reconfiguring the Advanced Server............................... 3-41 3.11 The Advanced Server Network Adapter............. 3-41 3.11.1 Manually Defining the Network Adapter ........ 3-42 3.11.2 What to Do If the Network Adapter Is Not Found......................................... 3-43 3.12 Next Steps...................................... 3-44 4 Configuring and Starting the Standalone License Server 4.1 About the License Server........................ 4-1 4.2 Before You Begin to Configure the Standalone License Server.................................. 4-2 4.3 Configuring the Standalone License Server....... 4-3 4.4 Configuring the Transports...................... 4-3 4.5 How to Respond to License Server Configuration Prompts......................................... 4-4 4.6 How to Start the Standalone License Server...... 4-6 4.6.1 How to Start the License Server Manually ..... 4-6 4.6.2 How to Start the License Server Automatically................................. 4-7 4.6.3 How to Start the License Server in an OpenVMS Cluster....................................... 4-7 5 After You Install the Advanced Server 5.1 Before You Begin Postinstallation Tasks......... 5-1 5.2 Verifying the Advanced Server Installation...... 5-2 5.3 Starting the Advanced Server.................... 5-2 5.3.1 When to Start the Advanced Server ............ 5-2 5.3.2 What the Startup Procedure Does .............. 5-3 5.4 Ways to Start the Advanced Server............... 5-3 5.4.1 How to Start the Advanced Server Manually .... 5-4 vi 5.4.2 How to Start the Advanced Server Automatically................................. 5-4 5.4.3 How to Start the Advanced Server in an OpenVMS Cluster....................................... 5-4 5.4.4 Troubleshooting the Startup .................. 5-5 5.4.4.1 SYLOGIN.COM Contains Commands Not Suitable for Detached Processes..................... 5-6 5.4.4.2 OpenVMS Registry Services Not Available.... 5-6 5.4.5 Determining Initial Advanced Server Parameter Values Stored in the OpenVMS Registry......... 5-7 5.5 Stopping the Advanced Server.................... 5-7 5.6 Special Advanced Server Management Commands..... 5-8 5.7 Setting Up External Authentication.............. 5-8 5.7.1 Setting Up External Authentication in OpenVMS Clusters...................................... 5-11 5.7.2 Requirement for External Authentication Over DECnet-Plus................................... 5-13 5.7.2.1 Configuring the Server Capacity for External Authentication.................... 5-13 5.7.3 Configuring Externally Authenticated Client Connections................................... 5-13 5.7.4 Bypassing External Authentication When the Network Is Down............................... 5-14 5.8 Converting Encoded File Names from ODS-2 to ODS-5........................................... 5-14 5.8.1 Using the File Name Conversion Utility ....... 5-15 5.8.2 Example of Converting an Encoded File Name ... 5-17 5.8.3 Example of Converting All Encoded File Names......................................... 5-18 5.9 Installing Optional Server Administration Tools........................................... 5-18 6 Implementing a Wide Area Network 6.1 Enabling Wide Area Network Support.............. 6-1 6.2 Using the LMHOSTS File in a Wide Area Network... 6-2 6.2.1 Setting Up a TCP/IP Wide Area Network ........ 6-2 6.2.2 The LMHOSTS Directory ........................ 6-3 6.2.3 LMHOSTS File Syntax .......................... 6-4 6.2.4 Managing the LMHOSTS File .................... 6-7 6.2.5 Using the LMHOSTS Log File ................... 6-8 6.3 Using WINS in a Wide Area Network............... 6-8 6.3.1 Setting up WINS for OpenVMS Clusters ......... 6-9 vii 6.4 Using DNS in a Wide Area Network................ 6-9 7 Removing Advanced Server for OpenVMS Software 7.1 Advanced Server Deinstallation.................. 7-2 7.2 Removing Advanced Server Configuration Parameters...................................... 7-3 7.3 Removing Advanced Server for OpenVMS Software... 7-3 7.3.1 Server Configuration Parameters in the OpenVMS Registry...................................... 7-6 7.4 Sample Advanced Server Removal Procedure........ 7-6 A Installation and Upgrade Checklist B Sample Advanced Server Installation and Configuration B.1 Sample Advanced Server Installation Procedure... B-1 B.2 Sample Advanced Server Configuration Procedure.. B-4 C Sample Standalone License Server Installation and Configuration C.1 Sample Standalone License Server Installation Procedure....................................... C-1 C.2 Sample Configuration Dialog for Standalone License Server.................................. C-3 D Sample External Authentication Software Installation E Advanced Server Files and On-Disk Structure E.1 Advanced Server Files........................... E-1 E.2 Advanced Server On-Disk Structure............... E-19 F Advanced Server Logical Names viii Index Examples 2-1 Sample Installation Procedure-Part 1 ......... 2-6 2-2 Sample Installation Procedure-Part 2 ......... 2-8 2-3 Sample Installation Procedure-Part 3 ......... 2-9 2-4 Sample Installation Procedure-Part 4 ......... 2-11 2-5 Sample Installation Procedure-Part 5 ......... 2-12 2-6 Sample Installation Procedure-Part 6 ......... 2-13 2-7 Sample Installation Procedure-Part 7 ......... 2-13 Figures E-1 On-Disk Structure Diagram .................... E-19 Tables 1-1 Preinstallation Checklist .................... 1-11 3-1 Advanced Server Configuration Prompts ........ 3-17 3-2 Configuration Settings ....................... 3-23 3-3 Server Roles in Each Type of Domain .......... 3-25 3-4 Methods for Changing Server Roles ............ 3-27 3-5 OpenVMS Network Adapter Logicals ............. 3-42 3-6 Undefined Adapter Messages ................... 3-44 4-1 License Server Configuration Prompts ......... 4-4 5-1 PWCONVERT Qualifiers ......................... 5-16 7-1 PRODUCT REMOVE Prompts ....................... 7-5 A-1 Installation and Upgrade Checklist ........... A-2 E-1 Files Installed for the Advanced Server ...... E-1 F-1 Advanced Server Logical Names ................ F-1 ix ________________________________________________________________ Preface This guide explains how to install and configure the Compaq Advanced Server for OpenVMS software (also referred to as the "Advanced Server"). The installation procedure allows you to install: o The complete Advanced Server o The standalone License Server, which may run on a separate system in the local area network o The standalone external authentication software, which may be used to provide external authentication on OpenVMS Cluster member nodes that are not running the Advanced Server o Both the standalone License Server and external authentication software Intended Audience This guide is written for OpenVMS system managers and network administrators. It assumes that you are familiar with the following aspects of the Compaq OpenVMS operating system: o DIGITAL Command Language (DCL) o A text editor, such as EDT or EVE o POLYCENTER Software Installation utility This guide also assumes that you are familiar with basic Advanced Server concepts. xi Document Structure The following list can help you find information in this guide: __________________________________________________________ Chapter_____Description___________________________________ Chapter 1 Describes prerequisites for the installation procedure. Chapter 2 Describes the installation procedure. Chapter 3 Describes the configuration procedure for the Advanced Server. Chapter 4 Describes the configuration procedure for the standalone License Server. Chapter 5 Describes postinstallation tasks, such as running the Installation Verification Procedure and starting the server independent of the installation and configuration procedures. Chapter 6 Describes how to set up Wide Area Networks. Chapter 7 Describes how to remove Advanced Server for OpenVMS software from your system. Appendix A Provides a summary of installation and configuration tasks. You can photocopy Appendix A and use it as a checklist as you read this guide. Appendix B Shows a sample installation and configuration procedure for the Advanced Server. Appendix C Shows a sample installation and configuration procedure for the standalone License Server. Appendix D Shows a sample installation procedure for the External Authentication software only. Appendix E Lists the files that are installed with the Advanced Server for OpenVMS software. Appendix F Lists the logical names created for the ____________Advanced_Server.______________________________ xii Related Documents The following manuals provide more information about topics discussed in this guide: __________________________________________________________ Document______________Description_________________________ Compaq Advanced Provides an overview of and Server for OpenVMS introduction to the Advanced Server Concepts and software and associated networking Planning Guide concepts for system administrators and operators Compaq Advanced Explains how to manage and customize Server for the Advanced Server software OpenVMS Server Administrator's Guide Compaq Advanced Provides command syntax descriptions Server for OpenVMS for all ADMINISTER commands and NET Commands Reference command equivalents Manual Compaq Advanced Describes the License Server Server for OpenVMS software and how to manage Advanced Guide to Managing Server licenses Advanced Server Licenses__________________________________________________ The following table lists related OpenVMS documents: xiii __________________________________________________________ OpenVMS_Document___________Description____________________ OpenVMS Version 7.2 Describes the new features and New Features Manual and related release notes of the Release Notes Manual. OpenVMS Alpha system software. OpenVMS Alpha Version 7.2 Describes how to install the Upgrade and Installation OpenVMS system software Manual OpenVMS System Manager's A task-oriented guide (in two Manual volumes) to managing an OpenVMS system; describes how to set up the required system services OpenVMS System Management A reference guide (in two Utilities Reference volumes) to the utilities Manual and tools used in managing an OpenVMS system OpenVMS License Explains how to load and manage Management Utility Manual license Product Authorization Keys (PAKs) OpenVMS Guide to Extended Describes Extended File File Specifications Specifications on OpenVMS, including how to set up and enable the ODS-5 file system OpenVMS Guide to System Describes OpenVMS security Security features, including procedures for enabling external authentication OpenVMS Connectivity Contains COM for OpenVMS, Developer's Guide OpenVMS Registry, and OpenVMS Events information Compaq C Run-Time Library Describes utilities that Utilities Reference help you manage localization Manual and time zone data for international software ___________________________applications___________________ For additional information about the OpenVMS products and services, access the following OpenVMS World Wide Web address: http://www.openvms.compaq.com/ xiv Reader's Comments Compaq welcomes your comments on this manual. Please send comments to either of the following addresses: Internet openvmsdoc@compaq.com Mail Compaq Computer Corporation 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/ If you need help deciding which documentation best meets your needs, call 800-282-6672. Conventions The following conventions are used in the Advanced Server documentation set: __________________________________________________________ Convention____Meaning_____________________________________ Advanced Advanced Server refers to the Advanced Server Server for OpenVMS file server. Italic The use of italic text indicates a place holder for information or parameters that you must provide. For example, if the procedure asks you to type file name, you must type the actual name of a file. Italic text also indicates new terms and the titles of other documentation referenced. monospace The use of monospace text indicates actual commands and characters that you enter, and the system display. Note The use of Note provides information of special importance. xv __________________________________________________________ Convention____Meaning_____________________________________ Caution The use of Caution provides information to avoid damaging software or hardware. Warning The use of Warning provides information that is essential to people's safety. . . . A horizontal ellipsis following an entry in a command line indicates that the entry or a similar entry can be repeated any number of times. An ellipsis following a file name indicates that additional parameters, values, or information can be entered. . A vertical ellipsis in an example indicates . that not all the data is shown. . Ctrl/x While you hold down the Ctrl key, press 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. In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box. PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key ______________or_a_pointing_device_button.________________ xvi 1 ________________________________________________________________ Before You Install Advanced Server for OpenVMS Software This chapter describes the hardware and software you must have and the tasks you need to complete before you install the Advanced Server for OpenVMS software. This chapter consists of the following sections: o Section 1.1, About the Advanced Server Software Kit o Section 1.2, Installing DECprint Software o Section 1.3, About Licensing o Section 1.4, About External Authentication o Section 1.5, About the Release Notes o Section 1.6, Using the Installation Checklist o Section 1.7, Requirements for Installing Advanced Server for OpenVMS Software o Section 1.8, Preinstallation Tasks o Section 1.9, Next Step 1.1 About the Advanced Server Software Kit The Advanced Server for OpenVMS kit contains the software required to run the following server software options: o The complete Advanced Server software, including the License Server and external authentication software o The Advanced Server standalone License Server o The standalone external authentication software o Both the standalone License Server and the standalone external authentication software 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 Kit 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 VAX systems. On VAX systems, you should continue to use the current PATHWORKS server software. If you have not already done so, upgrade to PATHWORKS for OpenVMS (Advanced Server), Version 6.0C or later. In mixed-architecture OpenVMS Clusters with the Advanced Server for OpenVMS running on Alpha members, VAX members can still use external authentication. For more information, see Section 5.7.1, Setting Up External Authentication in OpenVMS Clusters. ________________________Note ________________________ You cannot run multiple versions of the Advanced Server for OpenVMS or the PATHWORKS for OpenVMS (Advanced Server) in the same cluster. _____________________________________________________ 1.1.2 Upgrading to Advanced Server for OpenVMS The Advanced Server for OpenVMS software may be installed and run only on OpenVMS Version 7.2-1 and higher Alpha systems. Therefore, it may be necessary to upgrade the operating system as well as the server software. If the Advanced Server for OpenVMS Version 7.2 or later is already installed, the installation and upgrade do not require an intermediate upgrade. If PATHWORKS V6 for OpenVMS (Advanced Server) is currently installed, ensure that it is Version 6.0C or later. Otherwise, upgrade to the current release of PATHWORKS V6 for OpenVMS (Advanced Server) before continuing. The Advanced Server configuration procedure (PWRK$CONFIG.COM) automatically converts the PATHWORKS for OpenVMS (Advanced Server) data files to formats compatible with the Advanced Server for OpenVMS, as described in Chapter 3. 1-2 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.1 About the Advanced Server Software Kit If PATHWORKS V5 for OpenVMS (LAN Manager) is currently installed, there is no direct upgrade to the Advanced Server for OpenVMS. If you want to retain the existing user, group, share, and security objects, you must first upgrade to PATHWORKS for OpenVMS (Advanced Server), Version 6.0C or later. For more information, refer to the Compaq PATHWORKS for OpenVMS Server Migration Guide. For systems running the PATHWORKS V5 for OpenVMS (LAN Manager) file server on OpenVMS Alpha Version 6.2 systems, Compaq recommends the following migration path: 1. Upgrade the Version 5 file server to PATHWORKS V6 for OpenVMS (Advanced Server), Version 6.0C or later. 2. Upgrade the operating system to OpenVMS Version 7.2-1 or higher. 3. Upgrade the Version 6 file server to Advanced Server V7.3 for OpenVMS. Refer to the appropriate Software Product Description (SPD) for information about the OpenVMS versions supported by each version of PATHWORKS for OpenVMS and Advanced Server for OpenVMS. 1.1.2.1 LANMAN.INI Parameters Migrate to OpenVMS Registry Previous versions of the server software (for example, PATHWORKS for OpenVMS) use the LANMAN.INI file to store server parameters. The Advanced Server for OpenVMS stores these parameters in the OpenVMS Registry, which is similar to the Windows NT Registry. If you are upgrading a system from PATHWORKS V6 for OpenVMS (Advanced Server) to Advanced Server V7.3 for OpenVMS, the parameters and settings in the existing LANMAN.INI file are migrated to registry parameters when you run the PWRK$CONFIG.COM configuration procedure for the first time. For more information, see Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry. 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 Kit 1.1.2.2 Upgrading OpenVMS Clusters You can install the Advanced Server for OpenVMS on any OpenVMS Cluster member running OpenVMS Alpha Version 7.2-1 or higher. However, if PATHWORKS for OpenVMS (Advanced Server) or Advanced Server for OpenVMS is currently running on any cluster member, it must be stopped prior to installation. If the cluster members that will run the Advanced Server for OpenVMS share a common system disk, the installation can be performed on any cluster member that shares the system disk. If cluster members that will run the Advanced Server for OpenVMS use separate system disks, install the Advanced Server for OpenVMS on each system. If the OpenVMS Cluster contains other system disks (for example, to support VAX systems in the cluster or systems running earlier versions of OpenVMS Alpha), these disks might have older versions of the PATHWORKS for OpenVMS (Advanced Server) installed on them. If so, remove the 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 the 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 on using PWRK$DEINSTAL.COM, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide. Note, however, if you are using external authentication, Compaq recommends that you set up external authentication software on all the nodes in the cluster. To set up external authentication support on nodes that do not run Compaq OpenVMS file servers, see Section 5.7, Setting Up External Authentication. 1-4 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.2 Installing DECprint Software 1.2 Installing DECprint Software DECprint Supervisor for OpenVMS (DCPS) is a printing system that provides queue management and printing features for PostScript printers. To share a PostScript printer, selected PostScript printers might require use of the DECprint Supervisor for OpenVMS (DCPS) software for communication with the printers over DECnet or TCP/IP. If you plan to use DECprint Supervisor for OpenVMS on your system, Compaq recommends that you install it before installing the Advanced Server. You must reboot the system after installing the DECprint software. You can perform the reboot as part of the DECprint Supervisor installation procedure, or after you install the Advanced Server but before you configure it. 1.3 About Licensing The following sections describe the licensing software and the license requirements for the Advanced Server. 1.3.1 License Requirements The Advanced Server requires that clients accessing file and print services be appropriately licensed. To conform to this requirement, one of the following must be true: o The client must acquire a client-based license before connecting to an Advanced Server for the first time. o The Advanced Server must have a server-based license available to assign to an unlicensed client attempting to use services of the Advanced Server. In both cases, the license required to access Advanced Server services is a Client Access license: PWLMXXXCA07.03. If you are upgrading from PATHWORKS V6 for OpenVMS (Advanced Server) or Advanced Server for OpenVMS, Version 7.2, refer to the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses for information about upgrading client licenses. Before You Install Advanced Server for OpenVMS Software 1-5 Before You Install Advanced Server for OpenVMS Software 1.3 About Licensing 1.3.2 About the License Server The Advanced Server License Server is an optional software program that you can run on your OpenVMS system to grant licenses to clients. The License Server can be installed: o With the file server (automatically included with your file server installation) o Separately from the file server (called the "standalone License Server") 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 TCP/IP Compaq recommends that you install the License Server on a designated OpenVMS system without the Advanced Server. The Advanced Server for OpenVMS kit allows you to install the standalone License Server separately from the file server. Alternatively, you can run the License Server on an OpenVMS Cluster with the Advanced Server, where cluster failover provides increased availability. (Cluster failover also provides increased availability for the Advanced Server file server.) Each LAN needs only one active License Server. The license product authorization keys (PAKs) must be loaded on the system that runs the License Server. In an OpenVMS Cluster, the PAKs must be loaded into a shared license database. __________________________________________________________ For more information about_._._.___________Refer_to_._._.______________________ Loading licenses OpenVMS License Management Utility Manual Configuring the Chapter 4, Configuring and Starting License Server the Standalone License Server 1-6 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.3 About Licensing __________________________________________________________ For more information about_._._.___________Refer_to_._._.______________________ Managing licenses Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server ______________________Licenses____________________________ 1.4 About External Authentication External authentication is an optional feature of OpenVMS systems that allows system managers to set up user accounts for which login authentication is based on a security mechanism other than OpenVMS security. The Advanced Server takes advantage of this feature by providing the ability to use the Advanced Server or Windows NT-compatible user authentication mechanisms to authenticate OpenVMS user logins. This allows users to log in at the OpenVMS login prompt using the Advanced Server user name and password, and provides automatic password synchronization for user accounts. External authentication may be required if you are using the COM for OpenVMS product. When you install the complete Advanced Server, the files required to support external authentication are automatically included in the installation process. When you install the Advanced Server in an OpenVMS Cluster, if you want to enable external authentication on OpenVMS Cluster member nodes on which the server is not running and which share the same system disk, you can install the standalone external authentication software on that disk (without installing the Advanced Server software). On VAX member nodes, you must copy the external authentication files from an Alpha system on which the Advanced Server is installed to the VAX node. For more information about enabling external authentication, see Section 5.7, Setting Up External Authentication. Before You Install Advanced Server for OpenVMS Software 1-7 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 document contains important information you should know before you install the product. Compaq recommends that you read the release notes before starting the installation. 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: o Load the installation kit on a drive. o Enter the following POLYCENTER Software Installation utility command, where file_name.txt is the name you specify for the text file, and directory-path specifies the disk and directory name for the source drive that holds the Advanced Server for OpenVMS kit (for example, /SOURCE=DAD$100:[ASOVMS073]): $ PRODUCT EXTRACT RELEASE_NOTES ADVANCEDSERVER/FILE=file_name.txt- _$ /SOURCE=directory-path If you do not specify a file name, the release notes are written to a file called DEFAULT.PCSI$RELEASE_NOTES in the current directory. If you do not specify the source qualifier, the POLYCENTER Software Installation utility searches the location defined by the logical name PCSI$SOURCE. If not defined, the utility searches the current default directory. 1.5.2 How to Access the Release Notes After the Installation If you want to see the release notes after the instal- lation completes, you can read them on line or print the file from SYS$HELP:ASOVMS073.RELEASE_NOTES. 1.6 Using the Installation Checklist Appendix A, Installation and Upgrade Checklist, provides an installation and configuration checklist. You can photocopy the checklist and use it to track the completion of the installation and configuration tasks described in this guide. 1-8 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.7 Requirements for Installing Advanced Server for OpenVMS Software 1.7 Requirements for Installing Advanced Server for OpenVMS Software The following sections describe the hardware and software you need when you install Advanced Server for OpenVMS software. 1.7.1 Hardware Requirements All Alpha processors supported by the OpenVMS Operating System V7.2-1 are also supported by the Advanced Server for OpenVMS. For the latest information on the hardware that the server supports, refer to the Software Product Description (SPD). 1.7.2 Software Requirements To install Advanced Server for OpenVMS software suc- cessfully, you must have the following software properly installed and configured on your system: o OpenVMS Alpha Version 7.2-1 or higher. The Advanced Server runs on OpenVMS Alpha Version 7.2-1 (or higher) systems only, and requires the OpenVMS registry services. For more information about the OpenVMS Registry, refer to the OpenVMS System Manager's Manual or the OpenVMS Connectivity Developer's Guide (included on the OpenVMS Documentation CD-ROM). o The appropriate transport software to support the network protocols used by other servers and by network clients, including one or more of the following: - DECnet or DECnet-Plus (optional) DECnet or DECnet-Plus may optionally be installed when you install the OpenVMS operating system. - TCP/IP (optional) TCP/IP Services for OpenVMS or a supported third- party TCP/IP product can be used to provide IP support. Refer to the Advanced Server for OpenVMS Software Product Description (SPD) for a list of supported TCP/IP products. Before You Install Advanced Server for OpenVMS Software 1-9 Before You Install Advanced Server for OpenVMS Software 1.7 Requirements for Installing Advanced Server for OpenVMS Software 1.7.3 Supported Client Software 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 The minimum amount of physical memory required to run the Advanced Server on OpenVMS Alpha systems is 64 MB. 1.8 Preinstallation Tasks Use the checklist in Table 1-1 to complete the preinstal- lation tasks that are described later in this section. 1-10 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks Table_1-1_Preinstallation_Checklist_______________________ < >1. Check the part listing. < >2. Make sure that the network hardware is installed and connected. < >3. Log in to the SYSTEM account (or another account that has all privileges enabled to run the installation procedure). < >4. Make sure that the required software is installed. < >5. Start the OpenVMS Registry Server. < >6. Read the release notes. < >7. Check system parameters. < >8. Back up the system disks. < >9. Make sure that you have adequate disk space for installation. < >10. Check the queue manager. < >11. Check the time zone configuration. < >12. Make sure that DECnet or DECnet-Plus is running, if you are planning to use the DECnet transport. < >13. Make sure that TCP/IP is running, if you are planning to use the TCP/IP transport. < >14. Check for existing Compaq OpenVMS server images and files. < >15. Check the OpenVMS Cluster configuration, if you __________are_installing_the_Advanced_Server_on_a_cluster. Perform the following steps before you install Advanced Server for OpenVMS software. ________________________Note ________________________ All the steps except the last apply to both standalone and cluster Advanced Servers. The last step delineates what needs to be done for installing the Advanced Server on a cluster. _____________________________________________________ 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 Listing The software part listing specifies the contents of the kit you receive. Check the contents of your kit against that information. If parts are missing or your kit is damaged, contact your Compaq representative. 1.8.2 Step 2: Check the Network Hardware Advanced Server for OpenVMS runs on OpenVMS Alpha systems that meet the software requirements. The PC local area network (LAN) requires: o A supported network controller board in the server and in each client o The cables to connect each client and server to the network 1.8.3 Step 3: Log In to the SYSTEM Account Before you install Advanced Server for OpenVMS software, log in to the SYSTEM account, or another account that has all privileges enabled to run the installation procedure. To log in to the SYSTEM account: 1. At the user name prompt, enter SYSTEM: Username: SYSTEM 2. At the Password prompt, enter the password to the SYSTEM account. The password you enter is not displayed. 1.8.4 Step 4: Check the Required Software Advanced Server for OpenVMS software requires: o The OpenVMS Alpha operating system, Version 7.2-1 or higher. o The DECnet network transport, if you are going to use the DECnet transport, the mail server, or the License Server over DECnet. o The TCP/IP transport, if you are planning to use TCP/IP for cluster or network communication. If you are going to use the TCP/IP transport, you must have installed 1-12 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks and configured a TCP/IP transport product, as described in the Advanced Server V7.3 for OpenVMS Release Notes. 1.8.5 Step 5: Start the OpenVMS Registry Server The OpenVMS Registry is installed as part of the OpenVMS installation. To provide registry services, you must complete the following steps: 1. Define the SYS$REGISTRY logical to point to the disk location where the Registry Server files will be stored. For example, to store the registry files on device DKA100: in directory [SYS$REGISTRY], enter the following command: $ DEFINE/SYSTEM SYS$REGISTRY DKA100:[SYS$REGISTRY] In an OpenVMS Cluster, be sure to specify a disk and directory that is available to all cluster members. 2. Start the Registry Server. Compaq recommends that you have the Registry Server started automatically with system startup. This ensures proper operation of any Advanced Server utilities that require the registry (such as PWRK$REGUTL and the Configuration Manager). To have the Registry Server started automatically at system startup, run the OpenVMS Registry Configuration utility (SYS$MANAGER:REG$CONFIG) and make sure the REG$TO_ BE_STARTED logical is set to TRUE. For more information about starting the OpenVMS Registry Server, refer to the OpenVMS System Manager's Manual or the OpenVMS Connectivity Developer's Guide (included in the OpenVMS Documentation CD-ROM). If you need to start the Registry Server manually, enter the following command: $ @SYS$STARTUP:REG$STARTUP.COM For complete information about managing the OpenVMS Registry, refer to the OpenVMS System Manager's Manual or the OpenVMS Connectivity Developer's Guide (included in the OpenVMS Documentation CD-ROM). Before You Install Advanced Server for OpenVMS Software 1-13 Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks 1.8.6 Step 6: Print and Read the Release Notes If you have not already read the release notes, you should do so before installing the software. If you choose to back up the system, as recommended in Section 1.8.8, Step 8: Back Up the System, you can read the release notes during the backup. For more information, see Section 1.5, About the Release Notes. 1.8.7 Step 7: Check System Parameters Most systems have adequate system resources readily available to include the Advanced Server for OpenVMS software. However, make sure that the following OpenVMS system parameters are set properly. Make any necessary changes to the MODPARAMS.DAT file, then run AUTOGEN, and reboot your system. You can delay this reboot until the first reboot required for backing up your system disks (a backup is recommended in Section 1.8.8, Step 8: Back Up the System). 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 OpenVMS is already running, your system is likely to have sufficient resources to support the new version of the Advanced Server for OpenVMS. ________________________Note ________________________ If these parameters are not set properly, you cannot configure the server after you complete the installation procedure. _____________________________________________________ 1.8.7.1 GBLPAGES Parameter The Advanced Server for OpenVMS requires that the value of the GBLPAGES parameter be at least 7500 pages. To ensure that your system has enough free global pages, do the following while the Advanced Server is not running: 1. Enter the following: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 1-14 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks The value of the FREE_GBLPAGES parameter is displayed. For example: 143576 2. If the value is less than required, edit the system parameters file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following: MIN_GBLPAGES = 7500 1.8.7.2 GBLSECTIONS Parameter The Advanced Server for OpenVMS requires that the value of the GBLSECTIONS parameter be at least 75. If you are installing the standalone License Server only, the value must be at least 50. To ensure that your system has enough free global sections, do the following while the Advanced Server is not running: 1. Enter the following: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") The value of the GBLSECTIONS parameter is displayed. For example: 249 2. If the value is less than required, edit the system parameters file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following: MIN_GBLSECTIONS = 75 1.8.7.3 PROCSECTCNT Parameter If you are going to install the Advanced Server, the value of the PROCSECTCNT parameter should be at least 40. If you are installing the standalone License Server only, the value must be at least 32. To ensure that the value of the system parameter PROCSECTCNT is adequate: 1. Enter the following: $ WRITE SYS$OUTPUT F$GETSYI("PROCSECTCNT") Before You Install Advanced Server for OpenVMS Software 1-15 Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks The value of the PROCSECTCNT parameter is displayed. For example: 20 2. If the value is less than required, edit the system parameters file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following: MIN_PROCSECTCNT = 40 1.8.7.4 SCSNODE Parameter The SCSNODE parameter must be defined as your system's computer name. If you are running DECnet, the SCSNODE name should be the same as the DECnet node name. The SCSNODE parameter's preinstallation status affects what happens after you install, as follows: __________________________________________________________ If SCSNODE And is_._._.______you_._._._____Then_the_server_._._._________ Not defined Do not Does not start. define it Already Do not Starts. defined define it Not defined Define it Starts, but the OpenVMS system renames print and batch queues to include the new computer name. Therefore, you must requeue any existing print or batch jobs to the new queues. You may also have to rebuild the queue database. For information on these system management tasks, refer to the OpenVMS System ____________________________Manager's_Manual._____________ To check whether the system parameter SCSNODE is defined as your system's computer name, enter the following commands at the system prompt: $ SCSNODE = F$GETSYI("SCSNODE") $ SHOW SYMBOL SCSNODE 1-16 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks As a result, one of the following occurs: o If SCSNODE is defined, the computer name is displayed. For example, if your system's computer name is SPEEDY: $ SHOW SYMBOL SCSNODE SPEEDY o If SCSNODE is not defined, the computer name is not displayed. If SCSNODE is not defined, edit the file SYS$SYSTEM:MODPARAMS.DAT and define the parameter. For example, if your system's computer name is SPEEDY, edit the file so that it contains the following line: SCSNODE = "SPEEDY" If you edit the file SYS$SYSTEM:MODPARAMS.DAT, you must run the OpenVMS command procedure AUTOGEN and reboot the system either now or at some time before configuring the server. For example: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK For more information about using the AUTOGEN utility, refer to the OpenVMS System Management Utilities Reference Manual. 1.8.8 Step 8: Back Up the System To safeguard against the loss of valuable data, Compaq recommends that you back up all disks on your system (or at least the system disk) before you install any layered product. To do a system backup, use the OpenVMS BACKUP command. For information about the BACKUP command, refer to the OpenVMS System Management Utilities Reference Manual. 1.8.9 Step 9: Check Disk Space Requirements To determine the number of disk blocks required for your installation, refer to the Advanced Server V7.3 for OpenVMS Release Notes. To check the number of free blocks on the system disk, enter: $ SHOW DEVICE SYS$SYSDEVICE Before You Install Advanced Server for OpenVMS Software 1-17 Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks The OpenVMS system displays information about the system disk, including the number of free blocks. For example: Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DUA0: Mounted 0 AXP072 724856 280 1 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 configure the server. You can enter the SHOW QUEUE/MANAGER command to check whether the queue manager is running: $ SHOW QUEUE/MANAGER If the queue manager is running, the OpenVMS system displays a message similar to the following: 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 For more information about the OpenVMS DCL commands, refer to the OpenVMS DCL Dictionary. 1.8.11 Step 11: Check Time Zone and TDF The Advanced Server's internal time management uses Greenwich Mean Time (GMT). To synchronize with a common time format among computers in different time zones, the OpenVMS Coordinated Universal Time (UTC) system services may be used. The Advanced Server system implements default date/time support using the UTC standard. UTC is similar to GMT. Under the UTC time standard, zero hours occurs when the Greenwich Meridian is at midnight. Unlike local time, which can go backward and forward depending on daylight savings time, UTC always increases. Local times can be up to 12 hours behind GMT or 13 hours ahead of it. 1-18 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks Because UTC is independent of time zones, you can use UTC around the world; for example, it is 2:00 UTC at the same moment in Paris as well as in Tokyo. You can examine data that is time-stamped with UTC values in Paris and Tokyo without complicated conversions to deal with local time zones. To properly represent the time in your local server environment: 1. Determine the time differential factor (TDF) for your system, which associates each local time zone with UTC. The TDF is the difference between your local system time and the Coordinated Universal Time (UTC). The difference is expressed in hours and minutes. The TDF changes each time your local system time undergoes a change, such as when it changes from daylight savings time to standard time; the UTC, on the other hand, does not change. The Americas have negative offsets from UTC, while Europe, Africa, Asia, and Australia have positive offsets. For example, the TDF for New York, Eastern Standard Time, is -5:00. The TDF for eastern Australia is +10:00. The TDF for a region that observes daylight savings is typically +1:00 from the standard time for the region. For example, the TDF for New York during daylight savings time is -4:00. To determine the TDF for your system, refer to the map included in the OpenVMS System Manager's Manual. 2. Set the time zone and time differential factor (TDF) settings on your system by running the OpenVMS command procedure UTC$TIME_SETUP.COM. (This command procedure defines the time-related logicals needed by the Advanced Server.) From the SYSTEM account, enter the following command to begin the procedure: $ @SYS$MANAGER:UTC$TIME_SETUP.COM The procedure asks you which time parameters you want to configure. If your system resides in an area that observes daylight savings time, the system time and TDF must be modified appropriately when daylight savings starts and ends. To have these modifications Before You Install Advanced Server for OpenVMS Software 1-19 Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks done automatically twice a year, you can use the SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM command procedure. When you elect to change the time zone or TDF setting, or both, the changes are also made clusterwide if your 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 procedure 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 not necessary to have DECnet or DECnet-Plus running during the installation; however, DECnet or DECnet-Plus must be running on the system before you can configure the server. To see whether DECnet is running on the system where you are planning to install the server software, enter the appropriate command depending on whether you have installed DECnet (Phase IV), or DECnet-Plus, as described in the following sections. 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.2 o If DECnet is not running, enter the following command to start it: $ @SYS$MANAGER:STARTNET 1-20 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks 1.8.12.2 Checking DECnet-Plus Status To check DECnet-Plus status, enter the following command: $ SHOW LOGICAL NET$STARTUP_STATUS o If DECnet-Plus is running, the system displays the following: "NET$STARTUP_STATUS" = "RUNNING-ALL" (LNM$SYSTEM_TABLE) o If DECnet-Plus is not running, enter the following command to start it: $ @SYS$STARTUP:NET$STARTUP For more information, refer to the DECnet product documentation. 1.8.13 Step 13: Check TCP/IP Status If you are planning to use the TCP/IP transport, make sure that TCP/IP is running and that the PWIP driver has been loaded. The procedure depends on which TCP/IP product you use. For specific information, refer to the documentation for the TCP/IP product installed. For example, if TCP/IP Services for OpenVMS V5 is installed, you can start the PWIP driver manually by entering the following command: $ @SYS$STARTUP:TCPIP$PWIP_STARTUP.COM Alternatively, you can configure TCP/IP Services for OpenVMS to automatically start the PWIP driver when TCP/IP is started, using the configuration procedure TCPIP$CONFIG.COM. After the installation is complete, you can use the Configuration Manager to configure the Advanced Server for OpenVMS to use TCP/IP. You can do this during the configuration procedure (PWRK$CONFIG) or after configuring the server. In the former case, PWRK$CONFIG gives you the option of invoking the Configuration Manager. In the latter case, you can invoke the Configuration Manager at the DCL prompt by entering the ADMINISTER/CONFIG command. Before You Install Advanced Server for OpenVMS Software 1-21 Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks 1.8.14 Step 14: Check for Existing OpenVMS Server Images and Files Make sure that: 1. No Advanced Server (PATHWORKS Advanced Server and Advanced Server for OpenVMS) images, or PATHWORKS V5 for OpenVMS (LAN Manager) images, are running on the local system. No PATHWORKS OpenVMS servers or earlier versions of the Advanced Server for OpenVMS should be running anywhere in the cluster. 2. No files from a PATHWORKS for OpenVMS (NetWare) kit are on the system disk. If such files are present, use SYS$UPDATE:PWVN$DEINSTAL.COM (included with the PATHWORKS for OpenVMS (NetWare) kit) to remove those files. 3. No files from any PATHWORKS Advanced Server or Advanced Server for OpenVMS kit are in the SYS$SPECIFIC directory tree. The POLYCENTER Software installation utility will detect if any of these conditions exist, and if the above- mentioned images or files are found, it will notify you. 1.8.15 Step 15: Check OpenVMS Cluster Configuration You can run the Advanced Server on multiple OpenVMS Alpha Cluster members. To do so, follow these steps: 1. If you plan to use the TCP/IP transport, ensure that all cluster members on which the Advanced Server will run are in the same TCP/IP subnet. 2. If a PATHWORKS for OpenVMS, PATHWORKS V5 for OpenVMS (LAN Manager), or earlier version of the Advanced Server for OpenVMS is running on any cluster member, stop that server. For more information about earlier versions of the Advanced Server in clusters, see Section 1.1.2.2, Upgrading OpenVMS Clusters. Note that to provide external authentication, Compaq recommends that you set up external authentication software on all the nodes in the cluster. To set up external authentication support on nodes that do not run Compaq OpenVMS file servers, see Section 5.7, Setting Up External Authentication. 1-22 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Preinstallation Tasks 3. On each system on which you want to install the Advanced Server, complete the tasks described in this chapter. In a cluster configuration that uses multiple system disks, the OpenVMS Registry Server must be configured to use a common registry database. See Section 1.8.5, Step 5: Start the OpenVMS Registry Server, for more information. On each cluster member that you want to use as a file and print server, you will run the Advanced Server configuration command procedure (PWRK$CONFIG.COM), as explained in Chapter 3, Configuring the Advanced Server. This ensures that each node has its appropriate parameters set and enough resources to run the server. 4. All cluster members that will run the Advanced Server must share a common: o System user Authorization File (SYSUAF.DAT) o Rightlist file (RIGHTSLIST.DAT) o OpenVMS Registry datbase location (SYS$REGISTRY:) o Advanced Server data directory location (PWRK$COMMONROOT:) When installing the Advanced Server on an OpenVMS Cluster member, if the following two conditions apply, you are forced to shut down the server and, possibly, to reboot the systems running the server: 1. Advanced Servers are installed on two or more system disks in the cluster 2. The Advanced Server is already running on one or more cluster members that are booted from a system disk other than the one on which the installation is occuring 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. 1-24 Before You Install Advanced Server for OpenVMS Software 2 ________________________________________________________________ Installing Advanced Server for OpenVMS Software This chapter describes how to install the Advanced Server for OpenVMS software using the POLYCENTER Software Installation (PCSI) utility. You must follow the procedure outlined here regardless of whether you are upgrading from a previous version of the server or installing the server for the first time. For information about how to install the product directly from the OpenVMS Alpha CD-ROM menu, refer to the OpenVMS Alpha Version 7.2 Upgrade and Installation Manual. For information about the POLYCENTER Software Installation utility, refer to the OpenVMS System Manager's Manual. Before you begin the installation procedure, make sure that you have completed the preinstallation tasks listed in Chapter 1, Before You Install Advanced Server for OpenVMS Software. This chapter consists of the following sections: o Section 2.1, The Installation Procedure o Section 2.2, Troubleshooting Installation Problems o Section 2.3, Next Steps 2.1 The Installation Procedure The POLYCENTER Software Installation utility performs the following: o Determines whether the installation is being done on a VAX system or an Alpha system. If it is a VAX system, the installation terminates. The Advanced Server runs on Alpha systems only. Installing Advanced Server for OpenVMS Software 2-1 Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure o Creates Advanced Server accounts on the system, if necessary. o Copies the Advanced Server files in the installation kit to the target disk. o Creates DECnet objects, if you are running DECnet or DECnet-Plus. o Installs the OpenVMS DCL command definition file, which includes ADMINISTER commands and facilitates management of the Advanced Server. o Installs the Advanced Server logical name definition file. o Deletes obsolete files. o Verifies that the software has been installed successfully. See Section 5.2, Verifying the Advanced Server Installation, for information on how to run the POLYCENTER Software Installation utility so that the procedure automatically runs the Installation Verification Procedure after installing the software. o Detects whether a reboot is necessary, and requests one only if and when necessary. You are given the option of delaying a required reboot; for example, if you want to configure or change more settings before rebooting. 2.1.1 Before You Start the Installation Procedure Before you start the installation procedure, answer the following questions: 1. What is the product identifier? The product identifier tells the POLYCENTER Software Installation utility which product to install. The product identifier for the Advanced Server for OpenVMS software kit is ADVANCEDSERVER. 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 and computer you have. For example, if you want to mount a CD-ROM on the CD-ROM drive of your AlphaStation 400, the device name might be DKA400. 2-2 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure 3. Do you want to install the: o Complete Advanced Server software? o The License Server only? o The external authentication images only? o Both the License Server and the external authentica- tion images only? You can install these components on any Alpha system running OpenVMS Version 7.2-1 or higher. If you install the complete Advanced Server software or the License Server software, and PATHWORKS for OpenVMS (Advanced Server) was previously installed, the server data files are automatically upgraded during server configuration, as described in Chapter 3, Configuring the Advanced Server. If you choose not to install the complete Advanced Server software, you can choose one of the other options. If you choose to install the complete Advanced Server, you will not be given the other options. If the system is designated to run the standalone License Server, you can install the License Server software instead of the complete Advanced Server software. Compaq recommends that you run the standalone License Server on a designated License Server system. You can decide later (during configuration) whether to run the License Server. The License Server and the external authentication images are installed with the complete Advanced Server installation. If you have installed the Advanced Server and enabled external authentication in an OpenVMS Cluster that includes Alpha systems running OpenVMS 7.2-1 or later, and if these systems boot from a system disk that will not have the Advanced Server installed, you can install the standalone external authentication software on that system disk. For more information on setting up external authentication, see Section 5.7, Setting Up External Authentication. 4. What is the User Identification Code (UIC) group number? Installing Advanced Server for OpenVMS Software 2-3 Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure The Advanced Server installation procedure creates the OpenVMS user accounts PWRK$DEFAULT and PWRK$GUEST, if they do not already exist. The default selection displayed in the installation dialog is determined as follows: _______________________________________________________ If_._._._________________The_default_is_._._.__________ You are installing the The first available unused UIC file server for the group number, starting with first time 360. An account named The same group number as that PCFS$ACCOUNT already associated with the existing exists account PCFS$ACCOUNT. The file server The same group number as the accounts_already_exist___existing_accounts.____________ 2.1.2 Installing the Server When you have completed the recommended preinstallation tasks outlined in Chapter 1, Before You Install Advanced Server for OpenVMS Software, and have read the release notes, you are ready to use the POLYCENTER Software Installation utility to install the Advanced Server for OpenVMS. (For additional details for using the utility to install, manage, and remove software products on your system, refer to the OpenVMS System Manager's Manual.) During a product upgrade, existing configuration files are preserved in case you want to use them when you configure this version of the software. To install the Advanced Server for OpenVMS software, proceed as follows: 1. Load the installation kit media onto an available drive. 2. Log in to the SYSTEM account, or an account with equivalent privileges. 3. Check to make sure that other users are not logged in to the system. 2-4 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure 4. If a previous version of the software is installed on the system, shut it down. In a cluster, shut down the software on all cluster members. For a noncluster server, enter: $ @SYS$STARTUP:PWRK$SHUTDOWN For a cluster server, enter: $ @SYS$STARTUP:PWRK$SHUTDOWN CLUSTER 5. If you have DECnet configured on your system and you want to create a log of the installation procedure, enter the following command and then log in to the system account again: $ SET HOST 0/LOG=file-name where file-name is the name of the file to which you want the log written. 6. Start the POLYCENTER Software Installation utility by entering the PRODUCT INSTALL command with the source directory path appropriate for your system. For example: $ PRODUCT INSTALL ADVANCEDSERVER /SOURCE=directory-path where directory-path specifies the disk and di- rectory name for the source drive that holds the Advanced Server for OpenVMS kit. For example, /SOURCE=DAD$100:[ASOVMS073]. If you do not specify the source qualifier, the POLYCENTER Software Installation utility searches the location defined by the logical name PCSI$SOURCE. If not defined, the utility searches the current default directory. The utility installs your software at the location defined by the PCSI$DESTINATION logical. If that logical is not defined, then it installs the software in SYS$COMMON:[VMS$COMMON] and directories under it. ______________________ Caution ______________________ Compaq recommends that you do not redefine the PCSI$DESTINATION logical and do not use the /DESTINATION qualifier when installing the Advanced Server for OpenVMS with PCSI. If the destination is Installing Advanced Server for OpenVMS Software 2-5 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 not work correctly. _____________________________________________________ Note that by default, the installation procedure displays a minimum of text. To get supplementary information for each of the prompts, specify the /HELP qualifier with the PRODUCT INSTALL command, such as in the following example: $ PRODUCT INSTALL ADVANCEDSERVER /SOURCE=directory-path- _$ /HELP 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. The actual installation script that is displayed on your system might include additional questions and information, depending on your current configuration. ________________________Note ________________________ To stop the installation at any time, press Ctrl/Y. The installation procedure deletes any files that were created, then exits. _____________________________________________________ Example 2-1 Sample Installation Procedure-Part 1 $ PRODUCT INSTALL ADVANCEDSERVER/SOURCE=DKA100:[000000] The following product has been selected: CPQ AXPVMS ADVANCEDSERVER V7.3 Layered Product Do you want to continue? [YES] Y Configuration phase starting ... (continued on next page) 2-6 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure Example 2-1 (Cont.) Sample Installation Procedure-Part 1 You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. CPQ AXPVMS ADVANCEDSERVER V7.3: Advanced Server for OpenVMS Copyright 2000 Compaq Computer Corporation Advanced Server is sold by Compaq Computer Corporation Advanced Server requires PAK PWLMXXXCA07.03 for each client. This installation procedure requires that all the following conditions are satisfied: 1. This procedure is running on an Alpha processor. 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 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 kit are in SYS$SPECIFIC on this system disk. This procedure checks if the conditions are satisfied. If they are satisfied, the procedure continues. If not, the procedure stops. Do you want to continue? [YES] __________Explanatory Text for Example 2-1 __________ In this installation example, the installer specifies the source for the installation. The "Configuration phase starting ..." message refers to the configuration of the POLYCENTER Software Installation utility database, not to the configura- tion of the Advanced Server for OpenVMS itself. The first part of the installation script identifies the product being installed and lists the conditions that the procedure checks before continuing the Installing Advanced Server for OpenVMS Software 2-7 Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure installation. If you know that one or more of these conditions have not been met, enter NO to stop the procedure, and then do what is required to satisfy the conditions. If you know these conditions have been met, press Return to continue with the installation procedure. If you continue, and the procedure finds that any one of these conditions was not met, then you will see a message such as the one documented in Section 2.2.1, Installing Advanced Server for OpenVMS Software on a VAX System, or Section 2.2.2, Installing Advanced Server for OpenVMS on a System Running Another Advanced Server Image. Satisfy the required conditions that were not met, and then restart the procedure. When you continue the procedure (answering YES to the "Do you want to continue?" prompt), you are prompted to select one of the following choices for the installation. _____________________________________________________ Example 2-2 Sample Installation Procedure-Part 2 Select one of the numbered options: 1 Install the complete Advanced Server [default] 2 Install only the License Server 3 Install only the external authentication images 4 Install both the License Server and the external authentication images Option: [1] __________Explanatory Text for Example 2-2 __________ This part of the script gives you the option of installing the complete Advanced Server for OpenVMS product, or installing only the standalone License Server, only the standalone external authentication images, or installing both the standalone License Server and the standalone external authentication images. 2-8 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure In this example, the complete installation was selected, and the procedure continues. _____________________________________________________ Example 2-3 Sample Installation Procedure-Part 3 A PWRK$STREAMSOS_V*.EXE execlet from a previous kit is currently loaded into memory on this node. You must reboot this node before starting the product on this node. For complete information about the reasons a reboot might be 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] 2. Prevent PWRK$CONFIG configuration on any node using this system disk until after reboot. 3. Prevent PWRK$CONFIG configuration on all nodes until after reboot. 4. Prevent startup on any node using this system disk until after after reboot. 5. Prevent startup on all nodes until after reboot. Option: [1] __________Explanatory Text for Example 2-3 __________ The installation procedure will check for circum- 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 previous version could be from either an Advanced Server for OpenVMS or PATHWORKS for OpenVMS product. (Reboot is required before starting the Advanced Server.) o System parameters were changed (in MODPARAMS.DAT), or server parameters were changed in a way that affected system parameters. (Reboot is required before configuring the Advanced Server, as noted Installing Advanced Server for OpenVMS Software 2-9 Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure in Chapter 1, Before You Install Advanced Server for OpenVMS Software.) If a PATHWORKS for OpenVMS or Advanced Server for OpenVMS product has been installed and started previously, certain images remain on the system even after the product has been stopped or removed. As a result, before the Advanced Server for OpenVMS can be started, you need to reboot the system to remove the old image. To help minimize downtime, the installation procedure requests a reboot only if and when necessary. You are not forced to reboot after installation. In Example 2-3, Sample Installation Procedure-Part 3, software from a previous product installation was detected (in this case, a PWRK$STREAMSOS_V*.EXE file; for example, either PWRK$STREAMSOS_V6.EXE from PATHWORKS for OpenVMS, or PWRK$STREAMSOS_V7.EXE from Advanced Server for OpenVMS). A reboot is necessary unless you do not plan to run the Advanced Server for OpenVMS on this system. You have the option of delaying a required reboot so 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 a 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. You also have the option of preventing the installed server from being: o Configured on any node using this system disk (the disk on which you are installing the server) until after reboot o Configured on all cluster nodes until after reboot o Started on any node using this system disk until after reboot 2-10 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure o Started on all cluster nodes until after the reboot These options enable you to prevent unnecessary reboots such as on a cluster, when installing the server on a common disk. When you install the server on one node, you can use these options so that you can complete the installation and configuration on the other cluster nodes before starting the server. You will only have to reboot the system once. _____________________________________________________ Example 2-4 Sample Installation Procedure-Part 4 User Accounts and User Identification Codes (UICs) -------------------------------------------------- The Advanced Server V7.3 for OpenVMS installation creates two OpenVMS accounts: a default account, PWRK$DEFAULT, and a guest account, PWRK$GUEST. The default UIC group number for both these new accounts depends on the following: o If you are installing the server for the first time, the 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. o If a PWRK$DEFAULT or PWRK$GUEST account already exists, the default is the UIC group number associated with PWRK$DEFAULT or PWRK$GUEST, in preference to PCFS$ACCOUNT. However, the default UIC group number will not be used to change the UIC of any existing accounts. For more information about UIC group numbers, see the OpenVMS System Manager's Manual. (continued on next page) Installing Advanced Server for OpenVMS Software 2-11 Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure Example 2-4 (Cont.) Sample Installation Procedure-Part 4 Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST Group: [360] Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST PWRK$DEFAULT account already exists PWRK$GUEST account already exists __________Explanatory Text for Example 2-4 __________ You are prompted for a default UIC group number only if you are installing the complete Advanced Server for OpenVMS product. If you do not want to associate the newly created OpenVMS accounts PWRK$DEFAULT and PWRK$GUEST with the default user identification code (UIC) group number, specify another three-digit UIC group number. _____________________________________________________ Example 2-5 Sample Installation Procedure-Part 5 * This product does not have any configuration options. __________Explanatory Text for Example 2-5 __________ Configuration choices were already made during the procedure. The procedure continues as follows. _____________________________________________________ 2-12 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure Example 2-6 Sample Installation Procedure-Part 6 Execution phase starting ... The following product will be installed to destination: CPQ AXPVMS ADVANCEDSERVER V7.3 DISK$AXP0721:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...70%...90% To automatically start Advanced Server V7.3 for OpenVMS at system startup, you should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file. $ @SYS$STARTUP:PWRK$STARTUP Note: Add this line after the lines that start all the network transports, such as DECnet. Before starting Advanced Server V7.3 for OpenVMS on this node, be sure to configure the product (@SYS$UPDATE:PWRK$CONFIG) on each node in the cluster where the product will run. ...100% The following product has been installed: CPQ AXPVMS ADVANCEDSERVER V7.3 Layered Product __________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 how much has completed). It then explains how to have the server start automatically at system startup and reminds you to run the configuration procedure before starting the server. (Note that with the installation of the external authentication images only, start up and configuration are not options.) _____________________________________________________ Example 2-7 Sample Installation Procedure-Part 7 (continued on next page) Installing Advanced Server for OpenVMS Software 2-13 Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure Example 2-7 (Cont.) Sample Installation Procedure-Part 7 %PCSI-I-IVPEXECUTE, executing test procedure for CPQ AXPVMS ADVANCEDSERVER V7.3 ... Copyright Compaq Computer Corporation 1998, 2000. Starting Installation Verification Procedure for Advanced Server V7.3 for OpenVMS %PWRK-I-NORMAL, IVP completed successfully %PCSI-I-IVPSUCCESS, test procedure completed successfully $ __________Explanatory Text for Example 2-7 __________ The procedure verifies the installation, and then finishes. _____________________________________________________ 2.1.3 What To Do After the Installation Completes If you have installed the external authentication images only, you can proceed to enable external authentication, as explained in Section 5.7, Setting Up External Authentication. For other installations, do the following after the installation completes: 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. 2. Proceed to Chapter 3 to configure the Advanced Server for OpenVMS. After the installation completes, you can display a list of the Advanced Server for OpenVMS files that were installed by entering the following command: $ PRODUCT LIST ADVANCEDSERVER /SOURCE=directory-path 2-14 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.1 The Installation Procedure where directory-path specifies the disk and directory name for the source drive that holds the Advanced Server for OpenVMS kit. For example, /SOURCE=DAD$100:[ASOVMS073]. If you do not specify the source qualifier, the POLYCENTER Software Installation utility searches the location defined by the logical name PCSI$SOURCE. If not defined, the utility searches the current default directory. 2.2 Troubleshooting Installation Problems The following sections describe some problems you can encounter if you install Advanced Server for OpenVMS software in an environment that is not appropriate. 2.2.1 Installing Advanced Server for OpenVMS Software on a VAX System The Advanced Server does not run on OpenVMS VAX systems. If you attempt to install the Advanced Server on a VAX system, the POLYCENTER Software Installation utility procedure displays the following error message and terminates the installation: Advanced Server V7.3 for OpenVMS does not run on OpenVMS VAX systems. You can install this product on OpenVMS Alpha systems only. 2.2.2 Installing Advanced Server for OpenVMS on a System Running Another Advanced Server Image If you attempt to install the Advanced Server for OpenVMS on a system (or anywhere in a cluster) on which a PATHWORKS for OpenVMS or Advanced Server for OpenVMS image is running, the installation procedure displays a message such as the following: Advanced Server V7.3 for OpenVMS cannot be installed while any PATHWORKS or Advanced Server processes are running. If this node is part of a cluster, no node of the cluster can be running any of those images. At least one of the preconditions for installation have not been met. Installing Advanced Server for OpenVMS Software 2-15 Installing Advanced Server for OpenVMS Software 2.2 Troubleshooting Installation Problems See the Installation Guide for more information %PCSI-E-S_OPFAIL, operation failed %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition _________What To Do If You See This Message _________ Stop these server images from running, and then restart the installation procedure. _____________________________________________________ 2.2.3 System Disk Restrictions If the installation procedure detects PATHWORKS (NetWare) files, the procedure will notify you and request that you remove those files and restart the installation 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 will continue, notifying you that a reboot is necessary before starting the Advanced Server for OpenVMS. 2.2.4 Installing Advanced Server for OpenVMS on a System with PATHWORKS for OpenVMS (Advanced Server), Version 6.0A or Earlier If the system has Version 6.0A or earlier of PATHWORKS for OpenVMS (Advanced Server) installed, the installation procedure displays the following message: The migration path from PATHWORKS V6.0 to the Advanced Server is valid, but not recommended. Do you want to continue with the installation? [YES]: Compaq recommends that you upgrade to Advanced Server V7.3 for OpenVMS from PATHWORKS for OpenVMS (Advanced Server), Version 6.0C or later. To upgrade from previous versions of the server, follow the migration path described in Section 1.1.2, Upgrading to Advanced Server for OpenVMS, before you install Advanced Server V7.3 for OpenVMS. 2-16 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.3 Next Steps 2.3 Next Steps To continue, depending on which server you are installing, do one of the following: ________________________________________________________________ If_you_are_._._.________Proceed_to_._._.________________________ Installing the Chapter 3, Configuring the Advanced complete Advanced Server Server Installing the Chapter 4, Configuring and Starting the standalone License Standalone License Server Server Installing the Section 5.7, Setting Up External standalone external Authentication, and refer to the OpenVMS authentication Guide to System Security. software________________________________________________________ Installing Advanced Server for OpenVMS Software 2-17 3 ________________________________________________________________ Configuring the Advanced Server This chapter describes how to configure the Advanced Server, and consists of the following sections: o Section 3.1, About the Advanced Server Configuration Procedure o Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry 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 Server Configuration Prompts o Section 3.6, How to Change Server Configuration Settings o Section 3.7, Configuring the Advanced Server Domain Role o Section 3.8, Configuring the Server Language o Section 3.9, Configuring Windows NT Printer Management o Section 3.10, Troubleshooting Configuration Procedure Problems o Section 3.11, The Advanced Server Network Adapter o Section 3.12, Next Steps Configuring the Advanced Server 3-1 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, PWRK$CONFIG.COM, is installed by the Advanced Server for OpenVMS installation procedure. Like the installation procedure, the configuration procedure asks you a series of questions (by displaying prompts). The procedure uses your answers to configure the Advanced Server. You can use the PWRK$CONFIG procedure to reconfigure the server at any time later. Note that the script contents change after the first configuration. 3.1.1 What the Configuration Procedure Does PWRK$CONFIG is a command procedure that: 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 and share databases, such as when upgrading the server from a previous version, or when the currently configured language is not compatible with the language used by the existing file server. o If configuring a previously configured server, stores the original accounts database in specially-created directories. (For more information, see Section 3.10.3, If Problems Occur When Reconfiguring the Advanced Server.) o Starts the Registry server if it is not already running. o If you are upgrading from a PATHWORKS for OpenVMS server to Advanced Server for OpenVMS, migrates server configuration parameters from the PATHWORKS for OpenVMS LANMAN.INI file to the OpenVMS Registry. (For more information, see Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry.) 3-2 Configuring the Advanced Server Configuring the Advanced Server 3.1 About the Advanced Server Configuration Procedure o Allows you to enter the Configuration Manager to modify configuration parameters that affect the system environment and to verify the configuration setting against the available system resources. For example, you can specify the transports the server will run and the maximum number of clients that can connect to the server simultaneously. For more information about the Configuration Manager, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide. o Allows you to modify server configuration default settings such as server role, domain name, and the services that are enabled. o On a server that will run as a primary domain controller or member server, allows you to specify the Administrator account password. o Gives you the option of starting the server. After you install the server, you must run the PWRK$CONFIG configuration procedure before you can start the server. In an OpenVMS Cluster, before you start the server, you must run PWRK$CONFIG on each node where you plan to run the server. Although the nodes in an OpenVMS Cluster function as a single unit in a domain, treat them as individual units for purposes of configuration. 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 The PATHWORKS for OpenVMS and Advanced Server for OpenVMS servers store server parameters in different locations. PATHWORKS for OpenVMS servers use the LANMAN.INI file to store server configuration parameters. The Advanced Server for OpenVMS uses the OpenVMS Registry, which is similar to the Windows NT registry. For information about managing the server configuration parameters in the OpenVMS Registry, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide. 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 migrated to the OpenVMS Registry when you run the PWRK$CONFIG.COM configuration procedure for the first time after installation. (The Advanced Server for OpenVMS does not read parameter settings from the LANMAN.INI file.) After they have been migrated to the OpenVMS Registry, you manage the parameters in the registry. The LANMAN.INI file is retained in case the system will run PATHWORKS for OpenVMS again later. The PWRK$CONFIG.COM configuration procedure performs a one-time migration of the parameters. At the time the parameters are migrated into the registry, the PWRK$CONFIG procedure sets the data associated with the LanmanIniMigrated value in the OpenVMS Registry. If this value exists and has data associated with it, the PWRK$CONFIG procedure will omit the parameter migration process. You can display the value and its associated data in the OpenVMS Registry using the following commands: $ REGUTL :== $SYS$SYSTEM:PWRK$REGUTL.EXE $ REGUTL SHOW VALUE * LANMANINIMIGRATED In the following example, the data displayed for the LanmanIniMigrated value indicates that the parameters were migrated on October 29, 2000: 3-4 Configuring the Advanced Server Configuring the Advanced Server 3.2 Migrating LANMAN.INI Parameters to the OpenVMS Registry Key: SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters Value: LanmanIniMigrated Type: String Current Data: LANMAN.INI migrated on 29-OCT-2000 15:31:48.90 The following example shows what data might be displayed for the LanmanIniMigrated value if you are configuring your Advanced Server for OpenVMS on a system that has not had PATHWORKS for OpenVMS configured on it (that is, you are not upgrading from PATHWORKS for OpenVMS): REGUTL> SHOW VALUE * LANMANINIMIGRATED Key: SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters Value: LanmanIniMigrated Type: String Current Data: No LANMAN.INI to migrate on 29-OCT-2000 15:31:48.90 Refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide for more information about using the PWRK$REGUTL utility to manage server configuration parameters in the OpenVMS Registry. 3.3 Before You Start the Advanced Server Configuration Procedure Before you start the PWRK$CONFIG command procedure, answer the questions discussed in the following sections. 3.3.1 On What OpenVMS Disk Device Do You Want to Store the Advanced Server Data Files? The data files include: 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 o Client-based server administration tools and license kits o Virtual memory section files Configuring the Advanced Server 3-5 Configuring the Advanced Server 3.3 Before You Start the Advanced Server Configuration Procedure By default, the configuration procedure copies the data files to the system device (SYS$SYSDEVICE). However, you can specify any existing OpenVMS disk device that has at least 85,000 free blocks of disk space. The amount needed depends on the components installed. 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, which generates input to and output from the disk. Having these operations occur on the system disk can degrade the performance of both the OpenVMS system and the Advanced Server. Therefore, Compaq recommends that you specify a disk device other than the system disk. o On an OpenVMS Cluster with multiple system disks, all nodes on which you plan to run the Advanced Server must use the same disk device to store and access Advanced Server data files. Using separate disks on separate cluster members is strictly prohibited. o You can run the PWRK$CONFIG command procedure at any time, to change the disk device where Advanced Server data files are stored. PWRK$CONFIG automatically copies the data files to the new location and deletes the data files from the current location. 3.3.2 Do You Want to Change the System Configuration Parameters Now? 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 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, and which network transports the server uses. You can change the system configuration parameter settings after starting the Advanced Server by using the Configuration Manager. For more information, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide. Section B.2, Sample Advanced Server Configuration 3-6 Configuring the Advanced Server Configuring the Advanced Server 3.3 Before You Start the Advanced Server Configuration Procedure Procedure, shows the basic Configuration Manager screen displayed when you opt to change the system configuration parameter settings during PWRK$CONFIG. 3.3.2.1 Configuring Transports for a Backup Domain Controller or Member Server If you are configuring a server as a backup domain controller (BDC) or a member server, you must select at least one transport that will also be run by the primary domain controller (P