Advanced_Server_for_OpenVMS___________________ Server Installation and Configuration Guide Order Number: AA-RFM3A-TE January 1999 This guide explains how to install and configure the Advanced Server for OpenVMS software. Revision/Update Information: This is a new manual. Operating System: OpenVMS Alpha Version 7.2 Software Version: Advanced Server V7.2 for OpenVMS Compaq Computer Corporation Houston, Texas __________________________________________________________ January 1999 Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Compaq Computer Corporation 1999. All rights reserved. The following are trademarks of Compaq Computer Corporation: Alpha, Compaq, DECdirect, DECnet-Plus, DECprint, DIGITAL, OpenVMS, PATHWORKS, VAX, VAX DOCUMENT, VAXcluster, VMS, and the Compaq logo. The following are third-party trademarks: AT&T is a registered trademark of American Telephone and Telegraph Company. Apple, AppleShare, LaserWriter, Macintosh, and TRUETYPE are registered trademarks of Apple Computer, Inc. DEC Rdb is a trademark of Oracle Corporation. Hewlett-Packard, HP, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company. IBM and OS/2 are registered trademarks of International Business Machines Corporation. Microsoft, MS-DOS, and Windows are registered trademarks, and Windows 95, Windows 98, and Windows NT are trademarks of Microsoft Corporation. MultiNet and TCPWARE are registered trademarks of Process Software Corporation. NetBIOS is a trademark of Micro Computer Systems, Inc. Novell and NetWare are registered trademarks of Novell, Inc. PostScript is a registered trademark of Adobe Systems Incorporated. ZK6540 The Advanced Server for OpenVMS documentation set is available on CD-ROM. ________________________________________________________________ Contents Preface.................................................. ix 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 If You Are Upgrading to Advanced Server ...... 1-2 1.1.2.1 Migrating the Server....................... 1-2 1.1.2.2 Migrating LANMAN.INI Parameters............ 1-3 1.1.2.3 Upgrading OpenVMS Clusters................. 1-3 1.2 Installing DECprint Software.................... 1-4 1.3 About Licensing................................. 1-4 1.3.1 License Requirements ......................... 1-4 1.3.2 About the License Server ..................... 1-5 1.4 About External Authentication................... 1-6 1.5 Reading the Release Notes....................... 1-6 1.5.1 About the Release Notes ...................... 1-7 1.5.2 How to Access the Release Notes .............. 1-7 1.6 Using the Installation Checklist................ 1-7 1.7 Requirements for Installing Advanced Server for OpenVMS Software................................ 1-8 1.7.1 Hardware Requirements ........................ 1-8 1.7.2 Software Requirements ........................ 1-8 1.7.3 Supported Client Software .................... 1-9 1.7.4 Memory Requirements .......................... 1-9 1.8 Pre-installation Tasks.......................... 1-9 1.8.1 Step 1: Check the Part Listing ............... 1-10 1.8.2 Step 2: Check the Network Hardware ........... 1-11 1.8.3 Step 3: Check the Required Software .......... 1-11 1.8.4 Step 4: Start the OpenVMS Registry Server .... 1-11 1.8.5 Step 5: Log In to the SYSTEM Account ......... 1-12 iii 1.8.6 Step 6: Back Up the System ................... 1-12 1.8.7 Step 7: Print and Read the Release Notes ..... 1-12 1.8.8 Step 8: Check Disk Space Requirements ........ 1-13 1.8.9 Step 9: Check System Parameters .............. 1-13 1.8.9.1 GBLPAGES Parameter......................... 1-13 1.8.9.2 GBLSECTIONS Parameter...................... 1-14 1.8.9.3 PROCSECTCNT Parameter...................... 1-14 1.8.9.4 SCSNODE Parameter.......................... 1-15 1.8.10 Step 10: Check the Queue Manager ............. 1-16 1.8.11 Step 11: Check Time Zone and TDF ............. 1-16 1.8.12 Step 12: Check DECnet Status ................. 1-17 1.8.12.1 Checking DECnet (Phase IV) Status.......... 1-17 1.8.12.2 Checking DECnet-Plus Status................ 1-18 1.8.13 Step 13: Check TCP/IP Status ................. 1-18 1.8.14 Step 14: Check OpenVMS Cluster Configuration................................. 1-19 1.9 Next Step....................................... 1-19 2 Installing Advanced Server for OpenVMS Software 2.1 About the Installation Procedure................ 2-1 2.1.1 What is VMSINSTAL? ........................... 2-1 2.1.2 VMSINSTAL Installation Kit ................... 2-2 2.1.3 What VMSINSTAL does .......................... 2-2 2.2 Installing the Server........................... 2-2 2.2.1 Before You Start VMSINSTAL ................... 2-3 2.2.2 How to Start VMSINSTAL ....................... 2-5 2.2.3 How to Respond to Prompts .................... 2-6 2.2.4 How to Interrupt the Installation ............ 2-6 2.2.5 How to Answer Installation Questions ......... 2-7 2.3 Troubleshooting Installation Problems........... 2-12 2.3.1 Installing Advanced Server for OpenVMS Software on a VAX System...................... 2-12 2.3.2 Installing Advanced Server for OpenVMS on a System with PATHWORKS for OpenVMS (Advanced Server)....................................... 2-12 2.3.3 Installing the Standalone License Server on a System Where the Advanced Server Has Been Installed..................................... 2-13 2.3.4 Installing the External Authentication Software...................................... 2-13 2.4 Next Steps...................................... 2-14 iv 3 Configuring the Advanced Server 3.1 About the Advanced Server Configuration Procedure....................................... 3-1 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.4 How to Start the Advanced Server Configuration Procedure....................................... 3-10 3.5 How to Respond to Advanced Server Configuration Prompts......................................... 3-11 3.6 How to Change Configuration Settings............ 3-14 3.7 Troubleshooting Configuration Procedure Problems........................................ 3-17 3.7.1 Registry Server Startup Problems ............. 3-17 3.7.2 Ensuring Sufficient Resources to Support Clients....................................... 3-19 3.8 Selecting the Advanced Server Network Device.... 3-19 3.9 Defining Communications Devices................. 3-20 3.10 Next Steps...................................... 3-22 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-2 4.4 Configuring the Transports...................... 4-3 4.5 How to Respond to License Server Configuration Prompts......................................... 4-3 4.6 How to Start the Standalone License Server...... 4-5 4.6.1 How to Start the License Server Manually ..... 4-6 4.6.2 How to Start the License Server Automatically................................. 4-6 4.6.3 How to Start the License Server in an OpenVMS Cluster....................................... 4-6 v 5 After You Install the Advanced Server 5.1 Before You Begin Post-installation 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-3 5.4.2 How to Define Advanced Server Commands at Login......................................... 5-4 5.4.3 How to Start the Advanced Server Automatically................................. 5-4 5.4.4 How to Start the Advanced Server in an OpenVMS Cluster....................................... 5-4 5.4.5 Troubleshooting the Startup .................. 5-5 5.5 Stopping the Advanced Server.................... 5-7 5.6 Setting Up External Authentication.............. 5-7 5.6.1 Enabling External Authentication over a Network....................................... 5-8 5.6.2 Configuring Externally Authenticated Client Connections................................... 5-9 5.7 Converting Encoded File Names from ODS-2 to ODS-5........................................... 5-9 5.7.1 Using the Convert Utility .................... 5-10 5.7.2 Example of Converting an Encoded File Name ... 5-12 5.7.3 Example of Converting All Encoded File Names......................................... 5-13 5.8 Installing Optional Server Administration Tools........................................... 5-13 6 Implementing a Wide Area Network 6.1 Enabling Wide Area Networking................... 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-2 6.2.3 LMHOSTS File Syntax .......................... 6-3 6.2.4 Managing the LMHOSTS File .................... 6-4 6.2.5 Using the LMHOSTS Log File ................... 6-4 6.3 Using WINS in a Wide Area Network............... 6-5 6.3.1 Setting up WINS for OpenVMS Clusters ......... 6-5 vi 7 Removing Advanced Server for OpenVMS Software 7.1 The Advanced Server Deinstallation Procedure.... 7-2 7.2 Removing Advanced Server Configuration Parameters...................................... 7-2 7.3 Removing Advanced Server for OpenVMS Software... 7-3 7.4 Sample Advanced Server Removal Procedure........ 7-4 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-5 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-13 F Advanced Server Logical Names Index vii Figures E-1 On-Disk Structure Diagram .................... E-13 Tables 1-1 Pre-installation Checklist ................... 1-10 2-1 Installation Questions ....................... 2-7 3-1 Advanced Server Configuration Prompts ........ 3-11 3-2 Configuration Settings ....................... 3-15 3-3 OpenVMS Network Device Logicals .............. 3-20 3-4 Undefined Device Messages .................... 3-21 4-1 License Server Configuration Prompts ......... 4-4 5-1 PWCONVERT Qualifiers ......................... 5-11 7-1 PWRK$DEINSTAL Prompts ........................ 7-3 A-1 Installation and Upgrade Checklist ........... A-1 E-1 Files Installed for the Advanced Server ...... E-1 F-1 Advanced Server Logical Names ................ F-1 viii ________________________________________________________________ Preface This guide explains how to install and configure the 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 External authentication software only, which may be used to provide external authentication on OpenVMS cluster member nodes that are not running the Advanced Server. 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 OpenVMS operating system: o DIGITAL Command Language (DCL) o A text editor, such as EDT or EVE o VMSINSTAL command procedure This guide also assumes that you are familiar with basic Advanced Server concepts. ix 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 post-installation 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.______________________________ x Related Documents The following manuals provide more information about topics discussed in this guide: __________________________________________________________ Document______________Description_________________________ Advanced Server for Provides an overview of and OpenVMS Concepts and introduction to the Advanced Server Planning Guide software and associated networking concepts for system administrators and operators. Advanced Server Explains how to manage and customize for OpenVMS Server the Advanced Server software. Administrator's Guide Advanced Server for Provides command syntax descriptions OpenVMS Commands for all ADMINISTER commands and NET Reference Manual command equivalents. Advanced Server for Describes the license server OpenVMS Guide to software and how to manage Advanced Managing Advanced Server licenses. Server_Licenses___________________________________________ The following table lists related OpenVMS documents. xi __________________________________________________________ OpenVMS_Document___________Description____________________ OpenVMS Alpha V7.2 Describes how to install the Upgrade and Installation OpenVMS system software. Guide OpenVMS System Manager's A task-oriented guide to Manual managing an OpenVMS system. Describes how to set up the required system services, such as the OpenVMS Registry. OpenVMS System Management A reference guide to the Utilities Reference utilities and tools used in Manual 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 V7.2 Guide to Describes OpenVMS security System Security features, including procedures for enabling external ___________________________authentication.________________ xii Reader's Comments Compaq welcomes your comments on this manual. Print or edit the online form SYS$HELP:OPENVMSDOC_ COMMENTS.TXT and send us your comments by: Internet openvmsdoc@zko.mts.dec.com Fax 603-884-0120, Attention: OSSG Documentation, ZKO3-4/U08 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.digital.com:81/ If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). 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. While you hold down the Ctrl key, press another key or a pointing device button. Indicates a place where you should press the Return (or Enter) key. xiii __________________________________________________________ Convention____Meaning_____________________________________ Italic 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 also indicates new terms and the titles of other documentation referenced. monospace Indicates actual commands and characters that you enter, and the system display. Note: Provides information of special importance. Caution: Provides information to avoid damaging software or hardware. 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. ____._____________________________________________________ xiv 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, Reading 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, Pre-installation 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: o The Advanced Server file server o The Advanced Server standalone license server o The external authentication software only 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 server software, or upgrade to PATHWORKS V6 for OpenVMS (Advanced Server). 1.1.2 If You Are Upgrading to Advanced Server The Advanced Server for OpenVMS software runs only on OpenVMS V7.2 systems. Therefore, it may be necessary to upgrade the operating system as well as the server software. o If you are installing the Advanced Server for OpenVMS software on a system where PATHWORKS for OpenVMS has been installed, prepare the system by following the migration path described in Section 1.1.2.1, Migrating the Server. o If you are upgrading from PATHWORKS V6 for OpenVMS (Advanced Server), refer to Chapter 5, After You Install the Advanced Server, for information about the changes you will encounter in the server environment and operation. 1.1.2.1 Migrating the Server The Advanced Server for OpenVMS software can be installed on systems where PATHWORKS V6 for OpenVMS (Advanced Server) was installed. The configuration procedure (PWRK$CONFIG.COM) automatically upgrades server components and parameters. If the system is running a server version previous to PATHWORKS V6.0B for OpenVMS (Advanced Server), you should upgrade the operating system to OpenVMS Version 7.2, and then upgrade the server to V6.0B before you install Advanced Server for OpenVMS. Compaq recommends the following migration path for systems running the PATHWORKS V5 for OpenVMS (LAN Manager) file server on OpenVMS Version 6.2 systems: 1. Upgrade the operating system to OpenVMS Version 7.1. 2. Upgrade the V5 file server to PATHWORKS V6.0B for OpenVMS (Advanced Server). 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 3. Upgrade the operating system to OpenVMS Version 7.2. 4. Upgrade the V6.0B file server to Advanced Server V7.2 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.2 Migrating LANMAN.INI Parameters The Advanced Server relies on the OpenVMS Registry as the repository for server configuration parameters. In previous versions of the server software (for example, PATHWORKS for OpenVMS servers), the LANMAN.INI file is used to store server parameters. The Advanced Server 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.2 for OpenVMS, the parameters and settings in the existing LANMAN.INI file are migrated to registry parameters when you run the PWRK$CONFIG.COM initial configuration procedure. For more information, see Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry. 1.1.2.3 Upgrading OpenVMS Clusters You can install the Advanced Server on any OpenVMS cluster member running OpenVMS Alpha Version 7.2, as long as no other cluster members are running PATHWORKS for OpenVMS. If you are installing the Advanced Server on a cluster member node, you cannot run PATHWORKS V6 for OpenVMS (Advanced Server) or PATHWORKS V5 for OpenVMS (LAN Manager) on any other node in the same cluster. The Advanced Server runs on OpenVMS Alpha systems only. If you are installing the Advanced Server in a mixed- architecture cluster (a cluster containing both Alpha and VAX members), you cannot continue to run PATHWORKS for OpenVMS on VAX members. However, you can provide external authentication support on all nodes in the cluster by setting up external authentication on VAX nodes, as described in Section 5.6, Setting Up External Authentication. Before You Install Advanced Server for OpenVMS Software 1-3 Before You Install Advanced Server for OpenVMS Software 1.2 Installing DECprint Software 1.2 Installing DECprint Software DECprint Supervisor for OpenVMS is a printing system that provides queue management and printing features for PostScript printers. 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 have acquired a client-based license before connecting to an Advanced Server. 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.02. If you are upgrading from PATHWORKS V6 for OpenVMS (Advanced Server), refer to the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses for information about upgrading client license requests. 1-4 Before You Install Advanced Server for OpenVMS Software 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. Therefore, 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 reliability. 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 Before You Install Advanced Server for OpenVMS Software 1-5 Before You Install Advanced Server for OpenVMS Software 1.3 About Licensing __________________________________________________________ For more information about_._._.___________Refer_to_._._.______________________ Managing licenses 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 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, and you want to enable external authentication on OpenVMS cluster member nodes where the Advanced Server is not installed, you can install the external authentication software only. For more information about enabling external authen- tication, refer to Section 5.6, Setting Up External Authentication. 1.5 Reading the Release Notes The following sections describe the product release notes and how to extract them from the software kit before installing Advanced Server for OpenVMS. 1-6 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.5 Reading the Release Notes 1.5.1 About the Release Notes Compaq recommends that you print and read the release notes before starting the installation. The installation procedure copies the release notes into the SYS$HELP: area, where they are available after server installation. 1.5.2 How to Access the Release Notes o If you want to print the release notes before the installation, do the following: 1. Load the installation kit on a drive. 2. Enter the following commands, replacing device with the name of the device and the directory where you loaded the installation kit: $ MOUNT device: FPS $ BACKUP/SELECT=ASOVMS072.RELEASE_NOTES device:ASOVMS072.A/SAVE_SET * $ PRINT ASOVMS072.RELEASE_NOTES o If you want to print the release notes during the installation, do the following: 1. Load the installation kit on a drive. 2. Enter the following command to start the installa- tion procedure: $ @VMSINSTAL ASOVMS072 device_name: OPTIONS N The installation procedure prompts you to either print or display the release notes. In any case, the release notes are always copied to the SYS$HELP: area. 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. Before You Install Advanced Server for OpenVMS Software 1-7 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 For a list of 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 V7.2 The Advanced Server runs on OpenVMS Alpha V7.2 systems only, and requires the optional OpenVMS registry services. Refer to the OpenVMS System Manager's Manual for more information about the OpenVMS Registry. 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. See the Advanced Server for OpenVMS Software Product Description (SPD) for a list of supported TCP/IP products. 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.3 Supported Client Software Advanced Server for OpenVMS supports connections from the following types of clients: o Windows NT o Windows 98 o Windows 95 o Windows for Workgroups o PATHWORKS for DOS and Windows o PATHWORKS for Windows 95 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 Pre-installation Tasks Use the checklist in Table 1-1 to complete the pre- installation tasks that are described later in this section. Before You Install Advanced Server for OpenVMS Software 1-9 Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks Table_1-1_Pre-installation_Checklist______________________ < >1. Check the part listing. < >2. Make sure that the network hardware is installed and connected. < >3. Make sure that the required software is installed. < >4. Start the OpenVMS Registry Server. < >5. Log in to the SYSTEM account. < >6. Back up the system disks. < >7. Read the release notes. < >8. Make sure that you have adequate disk space for installation. < >9. Check system parameters. < >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 the DECnet transport. Refer to Section 1.8.12, Step 12: Check DECnet Status, for situations when DECnet is required. < >13. Make sure that TCP/IP is running, if you are planning to use the TCP/IP transport. < >14. Check the OpenVMS cluster configuration, if you __________are_installing_the_Advanced_Server_on_a_cluster. Before you install Advanced Server for OpenVMS software, perform the following steps. 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-10 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks 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 to the network 1.8.3 Step 3: Check the Required Software Advanced Server for OpenVMS software requires: o The OpenVMS Alpha operating system, Version 7.2 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 and configured a TCP/IP transport product, as described in the Advanced Server for OpenVMS Release Notes. 1.8.4 Step 4: Start the OpenVMS Registry Server The OpenVMS Registry is installed as part of the OpenVMS Version 7.2 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 SYS$REGISTRY DKA100:[SYS$REGISTRY] In an OpenVMS cluster, be sure to specify a disk and directory that is available to all cluster members running the Advanced Server. 2. Start the Registry Server. Before You Install Advanced Server for OpenVMS Software 1-11 Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks If you need to start the Registry Server manually, enter the following command: $ @SYS$STARTUP:REG$STARTUP.COM Compaq recommends that you add this command to the SYS$STARTUP_VMS.COM procedure before the command line that starts the Advanced Server. This will start the Registry Server with system startup, and ensures proper operation of any Advanced Server utilities that require the Registry (such as PWRK$REGUTL and the Configuration Manager). For complete information about managing the OpenVMS Registry, refer to the OpenVMS System Manager's Manual. 1.8.5 Step 5: Log In to the SYSTEM Account Before you install Advanced Server for OpenVMS software, log in to the SYSTEM account, or an account that has sufficient privileges to run the installation procedure. To log in to the SYSTEM account: 1. At the Username: prompt, enter SYSTEM: Username: SYSTEM 2. At the Password: prompt, enter the password to the SYSTEM account. The password you enter is not displayed. 1.8.6 Step 6: Back Up the System To safeguard against the loss of valuable data, Compaq recommends that you back up all disks on your system before you install any layered product. To do a system backup, use the OpenVMS BACKUP command. For information about the BACKUP command, see the OpenVMS System Management Utilities Reference Manual. 1.8.7 Step 7: Print and Read the Release Notes If you have not already read the release notes, you should do so before installing the software. See Section 1.5, Reading the Release Notes, for more information. 1-12 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks 1.8.8 Step 8: Check Disk Space Requirements The installation procedure requires at least 139,500 blocks of free disk space on the system disk. To check the number of free blocks on the system disk, enter: $ SHOW DEVICE SYS$SYSDEVICE 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.9 Step 9: Check System Parameters Make sure that the following OpenVMS system parameters are set properly. ________________________Note ________________________ If these parameters are not set properly, you cannot configure the server after you complete the installation procedure. _____________________________________________________ 1.8.9.1 GBLPAGES Parameter The minimum value of the GBLPAGES parameter must be at least 7500 pages. To ensure that your system has enough free global pages: 1. Enter the following: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") The value of the GBLPAGES parameter is displayed. For example: 7500 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: ADD_GBLPAGES = 7500 Before You Install Advanced Server for OpenVMS Software 1-13 Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks 1.8.9.2 GBLSECTIONS Parameter If you are going to install the Advanced Server, the minimum value of the GBLSECTIONS parameter is 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: 1. Enter the following: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") The value of the GBLSECTIONS parameter is displayed. For example: 75 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: ADD_GBLSECTIONS = 75 1.8.9.3 PROCSECTCNT Parameter If you are going to install the Advanced Server, the minimum value of the PROCSECTCNT parameter is 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") The value of the PROCSECTCNT parameter is displayed. For example: 40 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-14 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks 1.8.9.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 pre-installation 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, see 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 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. Before You Install Advanced Server for OpenVMS Software 1-15 Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks 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.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 uses Greenwich Mean Time (GMT) for internal time management. To properly represent the time in your local environment, the time zone information must be set up before the server is started. 1-16 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks You check the time zone and time differential factor (TDF) settings on your system by running the OpenVMS command procedure UTC$TIME_SETUP.COM. From the SYSTEM account, enter the following command to begin the procedure: $ @SYS$MANAGER:UTC$TIME_SETUP.COM o To set the time zone on your OpenVMS system, execute the following command procedure: @ SYS$MANAGER:UTC$TIMEZONE_SETUP.COM o To set up the time zone differential factor for your OpenVMS system, execute the following command procedure: @ SYS$MANAGER:UTC$CONFIGURE_TDF.COM If you change any time zone information, such as the daylight savings time setting, 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, see 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 system displays the following: Before You Install Advanced Server for OpenVMS Software 1-17 Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks Node Volatile Summary as of 1-NOV-1998 12:16:36 Executor node = 9.000 (BRUTUS) State = on Identification = DECnet-VAX V7.2, VMS V7.2 Active links = 2 o If DECnet is not running, enter the following command to start it: $ @SYS$MANAGER:STARTNET 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. Refer to the documentation for the TCP/IP product installed, for specific information. 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. 1-18 Before You Install Advanced Server for OpenVMS Software Before You Install Advanced Server for OpenVMS Software 1.8 Pre-installation Tasks 1.8.14 Step 14: Check OpenVMS Cluster Configuration You can run the Advanced Server on multiple OpenVMS Alpha cluster members. To do so, follow these steps: 1. On each system disk on which you want to run the Advanced Server, complete: o The tasks described in this chapter. o The VMSINSTAL command procedure described in Chapter 2, Installing Advanced Server for OpenVMS Software. In a cluster configuration that uses multiple system disks, the OpenVMS Registry Server must be configured to use a common registry database. Refer to Section 1.8.4, Step 4: Start the OpenVMS Registry Server, for more information. 2. On each cluster member that you want to use as a file and print server, run the Advanced Server configuration command procedure (PWRK$CONFIG.COM). This ensures that each node has its appropriate parameters set and enough resources to run the server. An OpenVMS cluster can include both VAX and Alpha members. The Advanced Server for OpenVMS software runs only on OpenVMS Alpha Version 7.2 members. An OpenVMS cluster cannot support a prior version of the file server in the same cluster with the Advanced Server. Therefore, to support this environment, run the Advanced Server on the Alpha members. On the VAX members, do not run a file and print server. However, to provide external authentication, Compaq recommends that you set up external authentication software on all the nodes in the cluster, as described in Section 5.6, Setting Up External Authentication 1.9 Next Step To install the Advanced Server, proceed to Chapter 2, Installing Advanced Server for OpenVMS Software. Before You Install Advanced Server for OpenVMS Software 1-19 2 ________________________________________________________________ Installing Advanced Server for OpenVMS Software This chapter describes how to install the Advanced Server for OpenVMS software. You must follow these procedures regardless of whether you are upgrading from a previous version of the server or installing the server for the first time. Before you begin the installation procedure, make sure that you have completed the pre-installation tasks listed in Chapter 1, Before You Install Advanced Server for OpenVMS Software. This chapter consists of the following sections: o Section 2.1, About the Installation Procedure o Section 2.2, Installing the Server o Section 2.3, Troubleshooting Installation Problems o Section 2.4, Next Steps 2.1 About the Installation Procedure The following sections describe the VMSINSTAL installation procedure and how it works. 2.1.1 What is VMSINSTAL? VMSINSTAL is a standard command procedure for installing software on the OpenVMS operating system. VMSINSTAL consists of a series of questions (prompts). Your answers to these questions provide VMSINSTAL with the information needed for installing Advanced Server for OpenVMS software. Installing Advanced Server for OpenVMS Software 2-1 Installing Advanced Server for OpenVMS Software 2.1 About the Installation Procedure 2.1.2 VMSINSTAL Installation Kit The VMSINSTAL installation kit includes several OpenVMS BACKUP save sets. The save set ASOVMS072.A contains the file KITINSTAL.COM and the release notes. 2.1.3 What VMSINSTAL does When you use VMSINSTAL, it: 1. Determines whether the installation is being done on a VAX system or an Alpha system. If it is a VAX system, the installation is terminated. The Advanced Server runs on Alpha systems only. 2. Creates Advanced Server accounts on the system, if necessary. 3. Restores the files from the save sets in the installa- tion kit. 4. Creates DECnet objects, if you are running DECnet or DECnet-Plus. 5. Installs the OpenVMS DCL command definition file, which facilitates management of the Advanced Server. 6. Installs the Advanced Server logical name definition file. 7. Deletes obsolete files. 8. Installs the Advanced Server files. 9. Verifies that the software has been installed successfully. (See Section 5.2, Verifying the Advanced Server Installation, for information on how to run the Installation Verification Procedure after installing the software.) 2.2 Installing the Server The following sections describe how to prepare information required by the installation procedure, and how to specify the required information during the procedure. 2-2 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.2 Installing the Server 2.2.1 Before You Start VMSINSTAL Before you start the VMSINSTAL command procedure, answer the following questions: 1. What is the product identifier? The product identifier tells VMSINSTAL which save sets to copy from the media to a disk on the system. The product identifier for the Advanced Server for OpenVMS software kit is ASOVMS072. 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. 3. Do you want to access the online release notes during the installation procedure? You can tell VMSINSTAL to ask you whether you want to display or print the online release notes during installation. Because the release notes may describe important changes to the installation procedure, Compaq recommends that you read them before you install Advanced Server for OpenVMS software. Procedures for obtaining the release notes are described in Section 1.5, Reading the Release Notes. 4. Do you want to install the Advanced Server? You can install the Advanced Server on any OpenVMS Alpha V7.2 system. If 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. 5. Do you want to install the standalone license server only? If the system is designated to run the standalone license server, you can install the license server software only. Compaq recommends that you run the standalone license server on a designated license server system. Installing Advanced Server for OpenVMS Software 2-3 Installing Advanced Server for OpenVMS Software 2.2 Installing the Server If you chose not to install the complete Advanced Server, the installation procedure gives you the option of installing the standalone license server software from the Advanced Server for OpenVMS software kit. In this case, the Advanced Server is not installed. If you chose to install the complete Advanced Server, you will not have the choice of installing the standalone license server. The license server will be installed as part of the complete Advanced Server installation. 6. Do you want to install the External Authentication software only? If you have installed the Advanced Server and enabled external authentication in an OpenVMS cluster, you can install only the external authentication software on the cluster members where the Advanced Server is not installed. For more information on setting up external authentication, refer to Section 5.6, Setting Up External Authentication. 2-4 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.2 Installing the Server 7. What is the User Identification Code (UIC) group number? 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.2.2 How to Start VMSINSTAL To start VMSINSTAL: 1. Ensure that you are logged in to the SYSTEM account. 2. Load the installation kit media onto a drive. (It is not necessary to mount the drive, but it must be on line so that the installation procedure can mount it.) 3. Enter the following command to check the status of the device on which you have loaded the installation kit, replacing device_name with the name of the applicable device: $ SHOW DEVICE device_name For example: $ SHOW DEVICE $1$DUS0: Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt $1$DUS0: (HSC001) Mounted 0 HUBSYS 347718 628 4 Installing Advanced Server for OpenVMS Software 2-5 Installing Advanced Server for OpenVMS Software 2.2 Installing the Server If the device status is Offline, enter the following command to place the device online, replacing device_ name with the name of your device: $ SET DEVICE/AVAILABLE device_name 4. Change your default directory to SYS$UPDATE: $ SET DEFAULT SYS$UPDATE 5. Start VMSINSTAL and specify the ASOVMS072 product identifier, the device name where the software kit is available, and whether you want access to the online release notes during the installation procedure: ________________________________________________________________ If_you_._._.______________Then_enter_._._.______________________ Want access to the @VMSINSTAL ASOVMS072 device_name release notes during the OPTIONS N installation procedure Do not want access @VMSINSTAL ASOVMS072 device_name to the release notes during the installation procedure_______________________________________________________ 2.2.3 How to Respond to Prompts An asterisk (*) at the beginning of a line in the installation procedure identifies a question you must answer. Usually, a question has a default answer, which the procedure displays within square brackets ([]) at the end of the question. To accept a default, press . For example: * Are you satisfied with the backup of your system disk [YES]? 2.2.4 How to Interrupt the Installation To interrupt the installation procedure, press at any time. Then you can restart the installation from the beginning. 2-6 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.2 Installing the Server 2.2.5 How to Answer Installation Questions Table 2-1, Installation Questions, tells you how to answer the questions displayed by VMSINSTAL. ________________________Note ________________________ Table 2-1 shows only the questions VMSINSTAL displays; it does not show any informational messages. For a complete sample installation script, see Appendix B, Sample Advanced Server Installation and Configuration. _____________________________________________________ Table_2-1_Installation_Questions________________________________ At this If you want the installa- question_._._._____tion_procedure_to_._._.______Enter_._._._____ Are you Continue satisfied with the backup of your system disk [YES]? Exit NO Select option Display the release notes 1 [2]:[1] on the screen To stop the display at any time, press . [1]This_question_is_displayed_only_if_you_specify_OPTIONS_N_when you start the VMSINSTAL command procedure or if there are active processes on the system. (continued on next page) Installing Advanced Server for OpenVMS Software 2-7 Installing Advanced Server for OpenVMS Software 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions________________________ At this If you want the installa- question_._._._____tion_procedure_to_._._.______Enter_._._._____ Print the release notes 2 (or press to accept this default) The release notes file is sent to the default print queue SYS$PRINT. You can enter the name of another print queue. Print the release notes 3 and display them on the To send the screen release notes to another print queue, enter the name of another print queue. To stop the screen display at any time, press . Continue without dis- 4 playing or printing the The release release notes notes are automatically copied to SYS$HELP. (continued on next page) 2-8 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions________________________ At this If you want the installa- question_._._._____tion_procedure_to_._._.______Enter_._._._____ Do you want Install the Advanced to install Server the complete Advanced Server for OpenVMS [YES]? Omit the Advanced Server NO Do you want to Install the standalone YES install only license server This option the Advanced installs the Server's license license server server [NO]?[2] and transport software without the Advanced Server. Refer to Chapter 4, Configuring and Starting the Standalone License Server, for more information. Omit the standalone license server. [2]This_question_is_displayed_only_if_you_chose_not_to_install__ the Advanced Server. (continued on next page) Installing Advanced Server for OpenVMS Software 2-9 Installing Advanced Server for OpenVMS Software 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions________________________ At this If you want the installa- question_._._._____tion_procedure_to_._._.______Enter_._._._____ Do you want Install only the External YES to install Authentication images This option the External installs Authentication the External images only Authentication [NO]?[2] images without the Advanced Server. Install the complete Advanced Server or install This option the standalone license causes the server installation procedure to repeat the previous questions so that you can select the complete Advanced Server. Is the selection Use the selection correct [YES]? Change the selection NO Terminate the installation Do you want Run the Installation to run the Verification Procedure IVP after the (IVP) automatically after installation is the installation procedure finished [YES]? completes [2]This_question_is_displayed_only_if_you_chose_not_to_install__ the Advanced Server. (continued on next page) 2-10 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions________________________ At this If you want the installa- question_._._._____tion_procedure_to_._._.______Enter_._._._____ Not run the IVP NO You can run the IVP independent of the installation procedure. For detailed information on running the IVP independently, see Section 5.2, Verifying the Advanced Server Installation. Do you want Purge all files it to purge files replaces replaced by this installation [YES]? Not purge any files it NO replaces Enter default Associate the newly UIC group created OpenVMS ac- number for counts PWRK$DEFAULT and PWRK$DEFAULT and PWRK$GUEST with the de- PWRK$GUEST[360][3]:fault user identification code (UIC) group number (for example, 360) [3]This_question_is_displayed_only_if_you_chose_to_install_the__ Advanced Server. (continued on next page) Installing Advanced Server for OpenVMS Software 2-11 Installing Advanced Server for OpenVMS Software 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions________________________ At this If you want the installa- question_._._._____tion_procedure_to_._._.______Enter_._._._____ Associate the newly A three-digit created accounts with UIC number. the UIC group number you ___________________specify______________________________________ 2.3 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.3.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 VMSINSTAL procedure displays the following error message and terminates the installation: Advanced Server V7.2 for OpenVMS does not run on OpenVMS VAX systems. You can install this product on OpenVMS Alpha systems only. For more information, refer to Section 1.1.1, About VAX Systems. 2.3.2 Installing Advanced Server for OpenVMS on a System with PATHWORKS for OpenVMS (Advanced Server) You can upgrade PATHWORKS V6.0B for OpenVMS (Advanced Server) to Advanced Server V7.2 for OpenVMS. If the system has a previous version of PATHWORKS V6 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]: 2-12 Installing Advanced Server for OpenVMS Software Installing Advanced Server for OpenVMS Software 2.3 Troubleshooting Installation Problems Compaq recommends that you upgrade from PATHWORKS V6.0B for OpenVMS (Advanced Server) to Advanced Server V7.2 for OpenVMS. To upgrade from previous versions of the server, follow the migration path described in Section 1.1.2.1, Migrating the Server, before you install Advanced Server V7.2 for OpenVMS. 2.3.3 Installing the Standalone License Server on a System Where the Advanced Server Has Been Installed If you install the standalone license server on a system where the Advanced Server has been installed, the installation procedure displays the following message: The Advanced Server was previously installed and you have selected to install the license server only. Because the Advanced Server includes the license server, the complete Advanced Server V7.2 for OpenVMS must also be installed. The installation procedure will choose to install the Advanced Server. You have the option of continuing with this installation, or you can terminate the installation procedure by pressing . To install the standalone license server on this system, you must first remove the Advanced Server software using the PWRK$DEINSTAL.COM command procedure, as described in Chapter 7, Removing Advanced Server for OpenVMS Software. For a sample installation and configuration script for the standalone license server, see Appendix C, Sample Standalone License Server Installation and Configuration. 2.3.4 Installing the External Authentication Software You cannot install only the external authentication software if you have previously installed the Advanced Server for OpenVMS. If you try to install the external authentication software where the Advanced Server has been installed, the installation procedure displays the following message: The Advanced Server was previously installed, and you have selected to install the External Authentication images only. Because the Advanced Server includes the External Authentication images, the complete Advanced Server V7.2 for OpenVMS must also be installed. Installing Advanced Server for OpenVMS Software 2-13 Installing Advanced Server for OpenVMS Software 2.3 Troubleshooting Installation Problems You must deinstall the Advanced Server to be able to select this option. For a sample script for the external authentication installation procedure, see Appendix D, Sample External Authentication Software Installation. 2.4 Next Steps To continue, depending on which server you are installing, do one of the following: ________________________________________________________________ Proceed Which tells you how If_you_are_._._.____to_._._._________to_._._.___________________ Installing the Chapter 3, Configure the Advanced complete Advanced Configuring the Server. Server Advanced Server Installing the Chapter 4, Configure the standalone standalone license Configuring license server. server and Starting the Standalone License Server Installing Section 5.6, Set up external authentica- the External Setting Up tion on the system. Authentication External software_only_______Authentication______________________________ 2-14 Installing Advanced Server for OpenVMS Software 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 Configuration Settings o Section 3.7, Troubleshooting Configuration Procedure Problems o Section 3.8, Selecting the Advanced Server Network Device o Section 3.9, Defining Communications Devices o Section 3.10, Next Steps 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. Configuring the Advanced Server 3-1 Configuring the Advanced Server 3.1 About the Advanced Server Configuration 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. 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 Figure E-1, On-Disk Structure Diagram). o If necessary, upgrades any existing file server user account and share databases. o Starts the Registry server if necessary. o Migrates the server configuration parameters from the LANMAN.INI file to the OpenVMS Registry, if necessary. (See Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry, for more information.) o Allows you to enter the Configuration Manager to modify system configuration parameters and to verify the configuration setting against the available system resources. For example, you can specify the transports the server will run, or the maximum number of clients that can connect to the server simultaneously. 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, 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.) 3-2 Configuring the Advanced Server Configuring the Advanced Server 3.1 About the Advanced Server Configuration Procedure For more information about the Configuration Manager, re- fer to the Advanced Server for OpenVMS Server Administrator's Guide. 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 On PATHWORKS for OpenVMS servers, the LANMAN.INI file is used to modify and store server parameters. The Advanced Server stores the server configuration parameters in the OpenVMS Registry, which is similar to the Windows NT registry. The Advanced Server does not read parameter settings from the LANMAN.INI file. For information about managing the server configuration parameters in the OpenVMS Registry, refer to the 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. 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 Key: SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters Value: LanmanIniMigrated Type: String Current Data: 29-OCT-1998 19:02:57.19 As shown in this example, the LanmanIniMigrated value's data is the time stamp indicating when the LANMAN.INI parameters were migrated. 3-4 Configuring the Advanced Server Configuring the Advanced Server 3.2 Migrating LANMAN.INI Parameters to the OpenVMS Registry Refer to the 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 following questions: 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 Virtual memory section files 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 84,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. Configuring the Advanced Server 3-5 Configuring the Advanced Server 3.3 Before You Start the Advanced Server Configuration Procedure o You can run the PWKR$CONFIG command procedure at any time, to change the disk device where Advanced Server data files are stored. 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 server configuration parameter settings, such as the maximum number of clients that can connect to the server 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 Advanced Server for OpenVMS Server Administrator's Guide. Configuring Transports for a Backup Domain Controller If you are configuring a server as a backup domain controller, you must select at least one transport that will also be run by the primary domain controller. Otherwise, the configuration will fail. When you select the transports to run on a server that will participate in wide area networking, keep the following in mind: o If you are configuring a backup domain controller to join an existing domain where the primary domain controller is on a different TCP/IP subnet, both the backup domain controller and the primary domain controller must be configured to use the TCP/IP transport, and you must set up wide area networking using either a WINS (Windows Internet Naming Service) Server or an LMHOSTS file for network name resolution, as described in Chapter 6, Implementing a Wide Area Network. o If you are using WINS for network name resolution, both the backup domain controller and the primary domain controller must use a WINS Server to provide NetBIOS name resolution. 3-6 Configuring the Advanced Server Configuring the Advanced Server 3.3 Before You Start the Advanced Server Configuration Procedure o If you are using the LMHOSTS file, it must be set up on both the backup domain controller and the primary domain controller. Make sure that the entry for the primary domain controller is in the LMHOSTS file on the backup domain controller before you configure the backup domain controller. If there is no entry for the primary domain controller in the LMHOSTS file on the backup domain controller when you configure it, the backup domain controller will not find the primary domain controller and will fail to join the existing domain. For more information, refer to Chapter 6, Implementing a Wide Area Network. To enable one or both of the wide area networking implementations, select them using the Configuration Manager, as described in the Advanced Server for OpenVMS Server Administrator's Guide. 3. Do you want to change any of the server configuration settings? These settings determine: o Whether the license server runs The license server is a software program that you can run on your OpenVMS system to grant client- based licenses. Any client that wants to use server resources must have a valid license. Each local area network (LAN) needs only one license server. The client 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 in a shared license database available to all cluster members. The license server runs only if you enable it with the configuration procedure. - If you are using client-based licensing, you must run the license server. Compaq recommends that you run the license server on a different system than the Advanced Server. See Section 1.3, About Licensing, for more information. Configuring the Advanced Server 3-7 Configuring the Advanced Server 3.3 Before You Start the Advanced Server Configuration Procedure - If you are using server-based licenses, you do not need to run the license server. By default, the license server does not run. o Whether the Timesource service runs The Timesource service allows your server to act as a time server. Other servers on the network can synchronize with the time server to coordinate network events (for example, running batch programs on all computers the same time each day). Each LAN needs only one time server. By default, the Timesource service does not run. o Whether the Alerter service runs The Alerter service sends messages called alerts to servers and clients that run the Messenger service. By default, the Alerter service runs. o Names of the users who receive alert messages By default, alert messages are sent to the Administrator account. o Whether the Netlogon service is enabled. In a domain, the Netlogon service distributes a domain-wide user accounts database to all servers running Netlogon. The service allows for single domain-wide logon that enables users to access resources on any server in the domain. The Netlogon service is required. Do not answer "NO" to this option. By default, the Netlogon service runs. o Domain name This is the domain in which your server is located. A domain is a subdivision of clients and servers on the network. The default domain name is LANGROUP. Compaq Computer Corporation recommends that you specify another name for your domain. o Role of the server 3-8 Configuring the Advanced Server Configuring the Advanced Server 3.3 Before You Start the Advanced Server Configuration Procedure This is the role of the server in the domain. You can designate an Advanced Server as either the primary domain controller or as a backup domain controller. In an OpenVMS cluster, all nodes on the cluster must have the same role. o Computer name This unique name identifies your server in the domain. You define this name or accept the default value when you run the configuration procedure. The PWRK$CONFIG procedure will not prevent you from specifying the same named primary domain controller if another node or cluster has previously been defined and is running in that role. However, on the new (duplicate) primary domain controller, the Netlogon service will not be started. The primary domain controller must be unique in the domain. The default computer name is the same as the server's SCSNODE name. o Advanced Server cluster alias If your server is a member of an OpenVMS cluster, this is the name that all servers in the cluster share. The alias lets remote nodes (including clients) treat the entire cluster as though it were a single server. For example, a client user can specify the cluster alias to connect to any server in the cluster; the user need not know the specific node in the cluster to which it is connected. If DECnet has been configured to run in the cluster, the default Advanced Server cluster alias is the same as the DECnet cluster alias. If DECnet has not been configured to run, the default Advanced Server cluster alias is nodename_alias. o Server announce comment This is the text that the Advanced Server displays when it announces its presence on the network and when you display a list of available servers. The default server announce comment is "Advanced Server V7.2 for OpenVMS." Configuring the Advanced Server 3-9 Configuring the Advanced Server 3.3 Before You Start the Advanced Server Configuration Procedure For more information about changing configuration settings, refer to Section 3.6, How to Change Configuration Settings. For more information about each server configuration setting, refer to the Advanced Server for OpenVMS Server Administrator's Guide. 4. What is the Administrator account password? If you are configuring a primary domain controller, the configuration procedure prompts you to specify a password for the Advanced Server Administrator account, from which you administer the domain. Passwords are case sensitive and can contain up to 14 alphanumeric characters as well as any of the following special characters: ! # $ % & () - . ^ _ ` { } ~ 5. Do you want to start the server? The configuration procedure asks you if you want to start the Advanced Server. If you do not want to start the Advanced Server at this time, you can do so later from the command line after the configuration procedure completes. Before you start the server on any OpenVMS cluster member, Compaq recommends that you configure the Advanced Server on each cluster member that you want to use as a server. You can then use the SYSMAN utility to start the server on all cluster members. If you choose to start the server individually on each cluster member, make sure that you do so from the SYSTEM account on each server node. For more information, refer to Section 5.4.4, How to Start the Advanced Server in an OpenVMS Cluster. 3.4 How to Start the Advanced Server Configuration Procedure After the installation procedure completes, the OpenVMS system prompt ($) is displayed. If the system was rebooted following installation: 1. Ensure that you are logged in to the SYSTEM account. 3-10 Configuring the Advanced Server Configuring the Advanced Server 3.4 How to Start the Advanced Server Configuration Procedure 2. Start the configuration procedure by entering: $ @SYS$UPDATE:PWRK$CONFIG 3.5 How to Respond to Advanced Server Configuration Prompts Table 3-1, Advanced Server Configuration Prompts, tells you how to respond to the prompts that PWRK$CONFIG displays. ________________________Note ________________________ Table 3-1 shows only the prompts PWRK$CONFIG displays; it does not show any informational messages. For a complete sample configuration script, see Appendix B, Sample Advanced Server Installation and Configuration. _____________________________________________________ Table_3-1_Advanced_Server_Configuration_Prompts_________________ At this If you want the configura- prompt_._._._______tion_procedure_to_._._.______Enter_._._._____ Do you want to Shut down the server or, continue with if your server is part of configuration an OpenVMS cluster, all [YES]:[1] servers in the cluster Abort the configuration NO procedure [1]This_prompt_is_displayed_only_if_the_server_is_running.______ (continued on next page) Configuring the Advanced Server 3-11 Configuring the Advanced Server 3.5 How to Respond to Advanced Server Configuration Prompts Table_3-1_(Cont.)_Advanced_Server_Configuration_Prompts_________ At this If you want the configura- prompt_._._._______tion_procedure_to_._._.______Enter_._._._____ Enter disk Copy the Advanced Server device name on-disk structure to the where Advanced default OpenVMS disk device Server data files displayed will be stored If you ran PWRK$CONFIG [default_device]: previously, the default disk device is the one you specified the last time you configured the server; otherwise, the default device is SYS$SYSDEVICE. Copy the Advanced Server device_name on-disk structure to an OpenVMS disk device different from the default displayed Do you want to Enter the Configuration change the server Manager tool For detailed configuration information parameters now? about using the [YES]: Configuration Manager, refer to the Advanced Server for OpenVMS Server Administrator's Guide. Complete the configuration NO without entering the Configuration Manager (continued on next page) 3-12 Configuring the Advanced Server Configuring the Advanced Server 3.5 How to Respond to Advanced Server Configuration Prompts Table_3-1_(Cont.)_Advanced_Server_Configuration_Prompts_________ At this If you want the configura- prompt_._._._______tion_procedure_to_._._.______Enter_._._._____ Enter item Accept the configuration number, or RETURN parameters displayed to use these values [DONE]: Change the configuration The number settings displayed associated with a setting you want to change. For detailed information on changing these default configuration settings, see Section 3.6, How to Change Configuration Settings. Do you want to Keep the existing enter a new Administrator account Administrator password account password [NO]:[2,3] Prompt you to enter a YES new Administrator account password [2]This_prompt_is_displayed_if_you_ran_PWRK$CONFIG_previously.__ [3]This prompt is displayed only if you are configuring a primary domain controller. (continued on next page) Configuring the Advanced Server 3-13 Configuring the Advanced Server 3.5 How to Respond to Advanced Server Configuration Prompts Table_3-1_(Cont.)_Advanced_Server_Configuration_Prompts_________ At this If you want the configura- prompt_._._._______tion_procedure_to_._._.______Enter_._._._____ Enter AdministratorAssociate a password with password network account the Administrator account If your server password[3]: will be part of a domain, enter the password to the domain's existing Administrator account. Re-enter password to verify password[3]: Do you want Start the server au- to start the tomatically after the Advanced Server configuration procedure V7.2 for OpenVMS completes on node node_name now [YES]:[4] Not start the server NO [3]This_prompt_is_displayed_only_if_you_are_configuring_a_______ primary domain controller. [4]This prompt is displayed only if the Advanced Server can be started without first executing AUTOGEN or rebooting the system. ________________________________________________________________ 3.6 How to Change Configuration Settings After you exit the Configuration Manager, the configura- tion procedure displays a list of server configuration settings and a prompt that lets you change them; for example: 3-14 Configuring the Advanced Server Configuring the Advanced Server 3.6 How to Change Configuration Settings Advanced Server for OpenVMS is presently configured to run as follows: 1. Run the license server: NO 2. Enable Timesource service: NO 3. Enable Alerter service: YES 3a. Alert user names: Administrator 4. Enable Netlogon service: YES 5. Advanced Server domain: LANGROUP 6. Advanced Server role: PRIMARY 7. Advanced Server computer name: COBRAZ 7a. Advanced Server OpenVMS cluster alias: COBRAZ_ALIAS 8. Server announce comment: Advanced Server V7.2 for OpenVMS Enter item number, or RETURN to use these values [DONE]: o To change a server configuration setting, enter the number of the setting you want to change. A prompt is then displayed that lets you change that setting. Table 3-2, Configuration Settings, describes possible values for each setting. o To save the settings after you complete your changes or to accept the settings displayed, press to use the default answer DONE. For more information about server configuration, refer to the Advanced Server for OpenVMS Server Administrator's Guide. Table_3-2_Configuration_Settings________________________________ Setting_________________________Possible_Values_________________ 1. Run the license server: YES, to run the license server. NO, to use the default and not run the license server. 2. Enable Timesource service: YES, to enable the Timesource service. NO, to use the default and not enable the Timesource service. 3. Enable Alerter service: YES, to accept the default and enable the Alerter service. NO, to disable the Alerter service. (continued on next page) Configuring the Advanced Server 3-15 Configuring the Advanced Server 3.6 How to Change Configuration Settings Table_3-2_(Cont.)_Configuration_Settings________________________ Setting_________________________Possible_Values_________________ 3a. Alert user names:[1] A comma-delimited list of user names (each containing up to 20 characters), who can receive alert messages. 4. Enable Netlogon service: YES, to accept the default and enable the Netlogon service. NO, to disable the Netlogon service. 5. Advanced Server domain: A domain name of up to 15 characters. Press to use the default. The default domain name is LANGROUP. Compaq recommends that you specify another name for the domain. 6. Advanced Server role: PRIMARY, to designate the server as the primary domain controller BACKUP, to designate the server as a backup domain controller. 7. Advanced Server computer A computer name of up to 15 name: characters. Press to use the default. If this is the first time running the configuration procedure, the default is your system's SCSNODE name. [1]Displayed_only_if_Alerter_service_is_enabled.________________ (continued on next page) 3-16 Configuring the Advanced Server Configuring the Advanced Server 3.6 How to Change Configuration Settings Table_3-2_(Cont.)_Configuration_Settings________________________ Setting_________________________Possible_Values_________________ 7a. Advanced Server for The Advanced Server cluster OpenVMS cluster alias:[2] alias for the OpenVMS cluster to which your server belongs. Press to use the default. If DECnet is configured to run, the default is the DECnet cluster alias. If DECnet is not configured to run, the default is nodename_alias. 8. Server announce comment: A text string of up to 48 characters that the server uses to announce its presence on the network. Press to use the default. [2]Displayed_only_in_an_OpenVMS_cluster.________________________ ________________________________________________________________ 3.7 Troubleshooting Configuration Procedure Problems This section describes how to: o Troubleshoot Registry Server startup problems o Ensure sufficient resources will be available to support clients 3.7.1 Registry Server Startup Problems For proper operation of the PWRK$CONFIG.COM configuration procedure and the file server, registry services must be available on the system running the Advanced Server. In an OpenVMS cluster environment, the OpenVMS Registry can be configured so that the Registry server does not run on the server node but rather on another node in the cluster. However, Compaq recommends that the OpenVMS Registry be configured to run the Registry server on every Advanced Server node. This ensures that registry services are available to the file server. For instructions on starting the Registry server and enabling registry Configuring the Advanced Server 3-17 Configuring the Advanced Server 3.7 Troubleshooting Configuration Procedure Problems services, refer to Section 1.8.4, Step 4: Start the OpenVMS Registry Server. o If registry services are not available, the PWRK$CONFIG.COM procedure attempts to start the OpenVMS Registry server. If the attempt is successful the procedure displays the following message: Checking to see if the OpenVMS Registry Services are available... %RUN-S-PROC_ID, identification of created process is 0000023B o If the SYS$REGISTRY logical is not defined, the OpenVMS Registry will not start. In this case, the PWRK$CONFIG.COM displays the following messages and terminates. Checking to see if OpenVMS Registry Services are available... SYS$REGISTRY must be defined to start the VMS Registry %PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for this system %PWRK-F-CONFIGERR, severe error encountered during configuration OpenVMS Registry Services are not available on this system. Some file server parameters are stored in the OpenVMS Registry. For the file server or file server utilities to be able to access these parameters, OpenVMS Registry Services must be available on this system. Since the file server requires access to the OpenVMS Registry, it is recommended that OpenVMS Registry Services be started as part of system start-up, before the file server is started. For instructions on how to start OpenVMS Registry Services please refer to the file server release notes. This configuration is incomplete and cannot continue. You must execute @SYS$UPDATE:PWRK$CONFIG again. Please configure and start the OpenVMS Registry Services before doing so. You must enable registry services and start the Registry Server, then run the PWRK$CONFIG.COM procedure again. For more information about enabling and starting the Registry Server, refer to the OpenVMS System Manager's Manual. 3-18 Configuring the Advanced Server Configuring the Advanced Server 3.7 Troubleshooting Configuration Procedure Problems 3.7.2 Ensuring Sufficient Resources to Support Clients The Advanced Server requests the resources that it needs using the OpenVMS AUTOGEN utility. If AUTOGEN underestimates the resources required for use by processes other than the Advanced Server, and these resources have already been consumed when the Advanced Server is started, there may be insufficient resources left for the Advanced Server to support the desired number of clients. To ensure sufficient resource allocation to support clients, make sure that all software that will run concurrently with the Advanced Server is installed and started before you run the the Advanced Server configuration procedure (PWRK$CONFIG.COM). If TCP/IP is selected as a transport, make sure that the TCP/IP product is loaded before you run the PWRK$CONFIG procedure. After you successfully configure the Advanced Server, it may not start, reporting that there are insufficient resources to support any clients. In this case, examine the following file to determine the system resource that needs to be increased: PWRK$LOGS:PWRK$CONFIG_ERROR_nodename.LOG To increase the resource, make the appropriate modifica- tions to the MODPARAMS.DAT file and then run AUTOGEN. 3.8 Selecting the Advanced Server Network Device The configuration procedure selects the network device depending on the transport you specify when you run the procedure. If the server has more than one network device, and you do not want to use the device selected, or if the server has a network device that is not recognized by the Advanced Server, you can manually select the network device to use with the transport you specified. Table 3-3, OpenVMS Network Device Logicals, lists OpenVMS logical names that you can use to control the network device over which the Advanced Server operates. You must add these logicals to SYS$MANAGER:SYLOGICALS.COM to have them available after rebooting. Configuring the Advanced Server 3-19 Configuring the Advanced Server 3.8 Selecting the Advanced Server Network Device Table_3-3_OpenVMS_Network_Device_Logicals_________________ Logical_Name____________________Transport_________________ NETBIOS$DEVICE DECnet PWRK$KNBDAEMON_DEVICE TCP/IP PWRK$NETBEUI_DEVICE_____________NetBEUI___________________ For example: o To select device EWA0: for DECnet transport, enter the following command before you start the server: $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: o To select device ESA0: for the TCP/IP transport, enter the following command before you start the server: $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE ESA0: o To select device ESA1: for the NetBEUI transport, enter the following command before you start the server: $ DEFINE/SYSTEM PWRK$NBDAEMON_DEVICE ESA1: ________________________Note ________________________ If TCP/IP is running on multiple network devices, and you select one of those devices for use by the Advanced Server, make sure the device you select corresponds to the first device listed in the TCP/IP local hosts database. _____________________________________________________ 3.9 Defining Communications Devices This section describes how to add new communications devices that are not automatically recognized by the Advanced Server, as well as restrictions and limitations on communications devices. The PWRK$KNBDAEMON, NETBIOS, and PWRK$NBDAEMON processes require the communications device to be defined in an internal device table. New communications devices can be released before updated Advanced Server software is available to customers. Therefore, this section describes 3-20 Configuring the Advanced Server Configuring the Advanced Server 3.9 Defining Communications Devices how to define the communications device you want the Advanced Server to use. If the communications device is not recognized by the Advanced Server, each failing process writes an error message to its log file. Table 3-4, Undefined Device Messages, shows each process, the log file that records the error message from the process, and examples of the text of the error message. In the examples in Table 3-4, the server node name is MYNODE. Table_3-4_Undefined_Device_Messages_____________________________ Process__________Log_File_Name__________________________________ PWRK$KNBDAEMON PWRK$LOGS:PWRK$KNBDAEMON_MYNODE.LOG Message: Tue Mar 24 13:13:50 1998 get_phys_addr: Failed to get Ethernet device_characteristics__________________________________________ PWRK$NBDAEMON PWRK$LOGS:PWRK$NBDAEMON_MYNODE.LOG Message: Tue_Mar_24_13:13:50_1998_Failed_to_open_datalink________________ NETBIOS PWRK$LOGS:NETBIOS_MYNODE.LOG Message: %NB-W-ERRSIGNAL, exceptional conditional detected at 24-Mar- 1998 13:13:50.00 -SYSTEM-W-NOSUCHDEV,_no_such_device_available___________________ The device tables include all known communications devices. However, if you are running the latest release and you find any of the messages listed in Table 3-4, you can explicitly specify the communications device for all three processes, using the following procedure: 1. Define the physical communications device type for the PWRK$KNBDAEMON, NETBIOS, and PWRK$NBDAEMON processes. For example, if EWA0 was an unknown physical communications device type, you would enter the following commands: Configuring the Advanced Server 3-21 Configuring the Advanced Server 3.9 Defining Communications Devices $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0: $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0: 2. Restart the server: $ @SYS$STARTUP:PWRK$STARTUP 3.10 Next Steps You can start the Advanced Server automatically as part of the configuration procedure. If you are ready to start the server, see Chapter 5, After You Install the Advanced Server, for instructions. 3-22 Configuring the Advanced Server 4 ________________________________________________________________ Configuring and Starting the Standalone License Server The license server is a software program that you can run on an OpenVMS system to grant licenses to clients. This chapter describes how to configure and start the standalone license server, and consists of the following sections: o Section 4.1, About the License Server o Section 4.2, Before You Begin to Configure the Standalone License Server o Section 4.3, Configuring the Standalone License Server o Section 4.4, Configuring the Transports o Section 4.5, How to Respond to License Server Configuration Prompts o Section 4.6, How to Start the Standalone License Server 4.1 About the License Server You can install the license server: o Separately from the Advanced Server o In conjunction with the Advanced Server Compaq recommends that you install the license server on a designated OpenVMS system without the Advanced Server. Therefore, 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 reliability. Configuring and Starting the Standalone License Server 4-1 Configuring and Starting the Standalone License Server 4.1 About the License Server The license server is required for client-based licensing. If you are using server-based licensing, you do not have to run the license server. Each LAN needs only one license server to support client- based licenses. The same license server can manage licenses for client access to any of the following types of file servers: o PATHWORKS V5 for OpenVMS (LAN Manager) o PATHWORKS V6 for OpenVMS (Advanced Server) o Advanced Server V7.2 for OpenVMS The license server included with Advanced Server for OpenVMS will not issue or manage PATHWORKS for OpenVMS (NetWare) licenses. If you have clients using NetWare networking software, maintain the existing version of the license server on a different system from the one that is running the Advanced Server. In an OpenVMS cluster, the PAKs must be loaded into a shared license database. For detailed information on managing licenses, see the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. 4.2 Before You Begin to Configure the Standalone License Server You install the standalone license server from the same software kit that you use to install the Advanced Server. The procedures are described in Chapter 2, Installing Advanced Server for OpenVMS Software. 4.3 Configuring the Standalone License Server You must configure the standalone license server to provide licenses to clients in the LAN. Therefore, you select the appropriate transports used by the clients. You can configure the license server to use the following transports: o DECnet o NetBEUI o TCP/IP 4-2 Configuring and Starting the Standalone License Server Configuring and Starting the Standalone License Server 4.4 Configuring the Transports 4.4 Configuring the Transports The following section describes how to use the configura- tion command procedure to configure the transports for the standalone license server. After the installation procedure completes, the OpenVMS system prompt ($) is displayed. If the system was rebooted following installation: 1. Ensure that you are logged in to the SYSTEM account. 2. Start the configuration procedure by entering: $ @SYS$UPDATE:PWRK$CONFIG 3. Respond to the configuration prompts. 4.5 How to Respond to License Server Configuration Prompts Table 4-1, License Server Configuration Prompts, tells you how to respond to the prompts displayed by PWRK$CONFIG when you configure the standalone license server. ________________________Note ________________________ Table 4-1 shows only the prompts that PWRK$CONFIG displays; it does not show any informational messages. For a complete sample configuration script, see Appendix C, Sample Standalone License Server Installation and Configuration. _____________________________________________________ Configuring and Starting the Standalone License Server 4-3 Configuring and Starting the Standalone License Server 4.5 How to Respond to License Server Configuration Prompts Table_4-1_License_Server_Configuration_Prompts__________________ At this If you want the configura- prompt_._._._______tion_procedure_to_._._.______Enter_._._._____ Enter disk device Copy the server on-disk name where structure to the default the Advanced OpenVMS disk device Server data files displayed will be stored (If you ran PWRK$CONFIG [default_device]: previously, the default disk device is the one you specified the last time you configured the server.) Copy the Advanced Server device_name on-disk structure to an OpenVMS disk device different from the default displayed Do you want to Allow licenses to be served serve client- over DECnet based licenses over DECnet [yes]:[1] Not allow licenses to be NO served over DECnet Do you want to Allow licenses to be served YES serve client- over NetBEUI based licenses over NetBEUI [no]:[1] Not allow licenses to be served over NetBEUI [1]Default_answers_may_differ_if_you_ran_the_license_server_____ configuration procedure previously. (continued on next page) 4-4 Configuring and Starting the Standalone License Server Configuring and Starting the Standalone License Server 4.5 How to Respond to License Server Configuration Prompts Table_4-1_(Cont.)_License_Server_Configuration_Prompts__________ At this If you want the configura- prompt_._._._______tion_procedure_to_._._.______Enter_._._._____ Do you want to Allow licenses to be served YES serve client- over TCP/IP based licenses over TCP/IP [no]:[1] Not allow licenses to be served over TCP/IP Do you want Start the server au- to start the tomatically after the Advanced Server configuration procedure license server completes now [YES]: Complete the configuration NO procedure without starting the server [1]Default_answers_may_differ_if_you_ran_the_license_server_____ configuration procedure previously. ________________________________________________________________ 4.6 How to Start the Standalone License Server You can start the license server in any of the following ways: o During the configuration procedure, as described in Section 4.3, Configuring the Standalone License Server. o Manually from the command line. o Automatically each time you reboot. Configuring and Starting the Standalone License Server 4-5 Configuring and Starting the Standalone License Server 4.6 How to Start the Standalone License Server 4.6.1 How to Start the License Server Manually If you did not start the license server during the configuration procedure, you can start it manually using the following command: $ @SYS$STARTUP:PWRK$STARTUP The license server will use DECnet, NetBEUI, TCP/IP. Process NETBIOS created with identification 0000011E Process PWRK$NBDAEMON created with identification 00000120 Process PWRK$KNBDAEMON created with identification 00000122 Process PWRK$LICENSE_S created with identification 00000124 $ 4.6.2 How to Start the License Server Automatically To make sure that the license server starts automatically each time you boot your OpenVMS system: 1. Edit the system startup file, SYS$STARTUP:SYSTARTUP_VMS.COM. 2. Add the startup command, as shown in the following example. Add the command to the file below all lines that start network transports. The following example shows how to edit the file. $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET . . . $ @SYS$STARTUP:PWRK$STARTUP 4.6.3 How to Start the License Server in an OpenVMS Cluster If you installed and configured the license server on multiple members of the same OpenVMS cluster, Compaq suggests that you use the SYSMAN utility to start the server manually and simultaneously on all cluster members. To do so: 1. Make sure that you are logged in to the SYSTEM account on one of the server nodes in the OpenVMS cluster. 2. Start the SYSMAN utility by entering: $ RUN SYS$SYSTEM:SYSMAN 4-6 Configuring and Starting the Standalone License Server Configuring and Starting the Standalone License Server 4.6 How to Start the Standalone License Server 3. Define all the cluster members on which you want to start the standalone license server. For example, if you want to start the license server on nodes SPEEDY, SPIN, and SPAN: SYSMAN> SET ENVIRONMENT/NODE=(SPEEDY,SPIN,SPAN) 4. Start the license server on the nodes you defined. At the SYSMAN> prompt, enter the following command: SYSMAN>DO @SYS$STARTUP:PWRK$STARTUP Configuring and Starting the Standalone License Server 4-7 5 ________________________________________________________________ After You Install the Advanced Server This chapter describes tasks you can perform after you install the Advanced Server and consists of the following sections: o Section 5.1, Before You Begin Post-installation Tasks o Section 5.2, Verifying the Advanced Server Installation o Section 5.3, Starting the Advanced Server o Section 5.4, Ways to Start the Advanced Server o Section 5.5, Stopping the Advanced Server o Section 5.6, Setting Up External Authentication o Section 5.7, Converting Encoded File Names from ODS-2 to ODS-5 o Section 5.8, Installing Optional Server Administration Tools 5.1 Before You Begin Post-installation Tasks Before you start the Advanced Server, make sure you have: o Installed the Advanced Server, as described in Chapter 2, Installing Advanced Server for OpenVMS Software. o Completed the configuration procedure, as described in Chapter 3, Configuring the Advanced Server. After You Install the Advanced Server 5-1 After You Install the Advanced Server 5.2 Verifying the Advanced Server Installation 5.2 Verifying the Advanced Server Installation If you did not run the IVP when you installed the Advanced Server, you can run it now to make sure that the server installed successfully. To run the IVP, enter the following command: $ @SYS$TEST:PWRK$IVP ________________________________________________________________ If the installa- Then the IVP tion_._._.__displays_._._.________And_you_should_._._.__________ Succeeded The message: %PWRK-I-NORMAL, IVP completed successfully Start the server, as described in Section 5.3, Starting the Advanced Server. Failed An error message, followed by: -PWRK-E-IVPFAIL, IVP has failed Reinstall the software, as described in Chapter 2, Installing Advanced Server __________________________________for_OpenVMS_Software._________ 5.3 Starting the Advanced Server The following sections describe how to start the Advanced Server and how to automate server startup. 5.3.1 When to Start the Advanced Server You must configure the Advanced Server before you can start it for the first time. After running the configuration procedure, you can start and stop the Advanced Server at any time. 5-2 After You Install the Advanced Server After You Install the Advanced Server 5.3 Starting the Advanced Server 5.3.2 What the Startup Procedure Does The startup procedure: 1. Checks for the required privileges. 2. Verifies that required configuration files are available. 3. Verifies that the server has been configured, and exits if it has not. 4. Loads transport drivers. 5. Installs images. 6. Starts transport support processes. 7. Starts the OpenVMS Registry Server, if necessary. 8. Starts each of the components: o License Registrar o License server (if configured) o File server 5.4 Ways to Start the Advanced Server You can start the Advanced Server: o During the configuration procedure, as described in Chapter 3, Configuring the Advanced Server. o Manually from the command line. o Automatically each time you reboot. 5.4.1 How to Start the Advanced Server Manually If you did not start the Advanced Server during the configuration procedure, you can start it now by entering: $ @SYS$STARTUP:PWRK$STARTUP The Advanced Server starts, and messages similar to the following are displayed: After You Install the Advanced Server 5-3 After You Install the Advanced Server 5.4 Ways to Start the Advanced Server The file server will use DECnet, NetBEUI, TCP/IP. Advanced Server mail notification will use DECnet. Process NETBIOS created with identification 00000248 Process PWRK$NBDAEMON created with identification 0000024A Process PWRK$KNBDAEMON created with identification 0000024C Process PWRK$LICENSE_R created with identification 0000024E Checking to see if the OpenVMS Registry Services are available... The Advanced Server is configured to support 20 PC clients. Process PWRK$MASTER created with identification 00000251 The master process will now start all other Advanced Server processes. 5.4.2 How to Define Advanced Server Commands at Login You can define Advanced Server management commands automatically when you log in to the privileged account that you use to manage the Advanced Server. To define Advanced Server commands at login, edit the LOGIN.COM file of the privileged account to add the following line: $ @SYS$STARTUP:PWRK$DEFINE_COMMANDS 5.4.3 How to Start the Advanced Server Automatically To make sure that the Advanced Server starts automatically each time you boot your OpenVMS system, edit the site- specific startup file, SYS$STARTUP:SYSTARTUP_VMS.COM. Add the Advanced Server startup command to the file below all lines that start network transports. For example: $ START/NETWORK DECNET . . . $ @SYS$STARTUP:PWRK$STARTUP 5.4.4 How to Start the Advanced Server in an OpenVMS Cluster If you installed and configured the Advanced Server on multiple members of the same OpenVMS cluster, Compaq recommends that you use the SYSMAN utility to start the Advanced Server manually and simultaneously on all cluster members. 5-4 After You Install the Advanced Server After You Install the Advanced Server 5.4 Ways to Start the Advanced Server To start the Advanced Server on all cluster members at the same time, make sure you are logged in to the SYSTEM account on one of the member nodes, then run SYSMAN as follows: ________________________________________________________________ Enter_this_command...___________To...___________________________ $ RUN SYS$SYSTEM:SYSMAN Start the SYSMAN utility. SYSMAN> SET ENVIRONMENT /NODE=(SPEEDY,SPIN,SPAN) Define the OpenVMS cluster members on which to start the server. For example, SPEEDY, SPIN, and SPAN. SYSMAN> DO @SYS$STARTUP:PWRK$STARTUPt the Advanced Server on all the nodes you defined in the previous command. SYSMAN>_EXIT____________________Exit_the_SYSMAN_utility.________ ________________________Note ________________________ If you are using the STARTUP feature of the SYSMAN utility to start Advanced Server, you must pass a P1 parameter of " ". For example: SYSMAN> STARTUP ADD FILE PWRK$STARTUP.COM/PARAMETER=P1:" " For more information on using the SYSMAN utility's STARTUP feature, see the OpenVMS System Management Utilities Reference Manual. _____________________________________________________ 5.4.5 Troubleshooting the Startup Some of the problems that prevent the Advanced Server from starting are: o SYLOGIN.COM contains commands that are not suitable for detached processes Advanced Server processes are detached processes. During startup, all detached processes must execute the site-specific system login procedure (by default, SYS$MANAGER:SYLOGIN.COM). After You Install the Advanced Server 5-5 After You Install the Advanced Server 5.4 Ways to Start the Advanced Server If Advanced Server startup does not complete suc- cessfully, check the SYLOGIN.COM procedure. Make sure that only commands that should be executed by detached processes are executed during Advanced Server startup. In SYLOGIN.COM, you can use the DCL lexical function F$MODE or F$GETJPI to conditionalize DCL commands, such as $SET TERM/INQUIRE, that should be executed only by nondetached processes, so that they are not executed during Advanced Server startup. See the OpenVMS DCL Dictionary for more information. o OpenVMS registry services are not available The Advanced Server will start only if the OpenVMS registry services are available. For information about starting the Registry Server, see the OpenVMS System Manager's Manual. - If the Registry Server is started as part of Advanced Server startup, a message similar to the following is displayed by the startup procedure: %RUN-S-PROC-ID, identification of created process is 0000023B - If the Registry Server cannot be started, the following message is displayed and the startup procedure is terminated: SYS$REGISTRY must be defined to start the VMS Registry. %PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for this system %PWRK-F-STARTERR, severe error encountered during start-up OpenVMS Registry Services are not available on this system. Some file server parameters are stored in the OpenVMS Registry. For the file server or file server utilities to be able to access these parameters, OpenVMS Registry Services must be available on this system. Without them the file server cannot start. $ 5-6 After You Install the Advanced Server After You Install the Advanced Server 5.5 Stopping the Advanced Server 5.5 Stopping the Advanced Server You can stop the Advanced Server at any time for any reason, which can include the following: o When you change server configuration parameters o As part of an orderly system shutdown To stop the Advanced Server, enter the following command: $ @SYS$STARTUP:PWRK$SHUTDOWN Shutting down the currently running server(s)... To stop the Advanced Server as part of an orderly system shutdown, add the shutdown command to the site-specific system shutdown procedure. 5.6 Setting Up External Authentication The OpenVMS operating system Versions 7.1 and higher provide support for external authentication. Advanced Server participates with the operating system to provide external authentication to allow Advanced Server users to log in to the OpenVMS operating system using the Advanced Server user name and password. External authentication provides automatic password synchronization between an OpenVMS account and a corre- sponding Windows NT account. With external authentication enabled, users who have both OpenVMS and Advanced Server user accounts can avoid having to maintain two different passwords. To provide external authentication on the system, perform the following procedures. After You Install the Advanced Server 5-7 After You Install the Advanced Server 5.6 Setting Up External Authentication __________________________________________________________ Step___Procedure_____________Refer_to_._._._______________ 1. Install one of the Chapter 2, Installing following: Advanced Server for OpenVMS o The Advanced Software. Server o The external authentication software only 2. Enable external OpenVMS V7.2 Guide to System authentication for Security the system. 3. Set the OpenVMS OpenVMS V7.2 Guide to System user account to Security allow external authentication. 4. Establish host Advanced Server for OpenVMS mapping between Server Administrator's Guide the Advanced Server user account and the OpenVMS user account, if _______necessary._________________________________________ 5.6.1 Enabling External Authentication over a Network External authentication cannot occur if a network connection is required and the network is down. However, privileged users can enter the /LOCAL_PASSWORD qualifier after the OpenVMS user name at the login prompt, to specify local authentication. Be sure to specify the OpenVMS user name and password when using the /LOCAL_PASSWORD qualifier. Because using the /LOCAL_PASSWORD qualifier effectively overrides the security policy established by the system manager, it is allowed only under the following conditions: o When the user's account has SYSPRV as an authorized privilege. This allows the system manager to gain access to the system when the network is down. 5-8 After You Install the Advanced Server After You Install the Advanced Server 5.6 Setting Up External Authentication o When Bit 1 is set in the SYS$SINGLE_SIGNON logical name, which allows nonprivileged users who are normally externally authenticated to log in locally. Refer to the OpenVMS System Management Utilities Reference Manual for more information about the /LOCAL_PASSWORD qualifier to the LOGIN command. 5.6.2 Configuring Externally Authenticated Client Connections By default, the Advanced Server supports the processing of up to 10 simultaneous external authentication requests. You can modify this maximum to suit the Advanced Server requirements, using the Configuration Manager. To start the Configuration Manager, enter the following command: $ ADMINISTER/CONFIGURATION The basic server parameters include the number of simultaneous activations for users with external authentication (also called "Single Sign-on"). For more information about using the Configuration Manager, refer to the Advanced Server for OpenVMS Server Administrator's Guide. 5.7 Converting Encoded File Names from ODS-2 to ODS-5 Existing Advanced Server shares may be converted from ODS-2 to ODS-5 to take advantage of the OpenVMS Version 7.2 support of extended file specifications. The Advanced Server for OpenVMS software provides a conversion utility for converting ODS-2 encoded file names on ODS-5 devices that have been converted from ODS-2. The conversion utility removes escape-encoded characters in file names, changing the file names to ISO Latin-1 characters. For example, if a file name is created on an ODS-2 disk containing the character-encoding sequence __E4, to represent the lowercase a-umlaut (ä), the conversion utility removes the encoding and replaces it with the ä character. You can convert ODS-2 file names to ODS-5 file names after: o The Advanced Server for OpenVMS has been installed and configured. After You Install the Advanced Server 5-9 After You Install the Advanced Server 5.7 Converting Encoded File Names from ODS-2 to ODS-5 o The disk device containing escape-encoded file names has been converted from ODS-2 to ODS-5. Refer to the OpenVMS Guide to Extended File Specifications for information about converting disk devices to ODS-5. 5.7.1 Using the Convert Utility The Advanced Server for OpenVMS software kit includes a file name conversion utility that allows you to convert file names from the encoding used on ODS-2 file systems to ISO Latin-1 file names. The file name conversion utility file is: SYS$SYSTEM:PWRK$CNVTOHFS.EXE When the Advanced Server commands have been defined, you can use the PWCONVERT command to invoke the Convert Utility. For information about defining Advanced Server commands, see Section 5.4.2, How to Define Advanced Server Commands at Login. For example, to define the PWCONVERT command, enter the following DCL command: $ PWCONVERT :== $SYS$SYSTEM:PWRK$CNVTOHFS.EXE The format of the PWCONVERT command is: $ PWCONVERT /qualifiers file-spec Where: o Qualifiers are optional. They are described in Table 5-1, PWCONVERT Qualifiers. The default setting is used if you omit the qualifier. o The file-spec argument is required, and may include the device name, directory name, and file name. - If you specify only a disk device, the conversion utility scans the entire device for file names that are encoded, and converts them if necessary. - If you specify a disk device and a directory, all the files in the specified directory are scanned and converted if necessary. You may include wildcard characters in directory names and file names. - If you specify a disk device, directory, and a single file name, only that file is converted. 5-10 After You Install the Advanced Server After You Install the Advanced Server 5.7 Converting Encoded File Names from ODS-2 to ODS-5 - If you enter the PWCONVERT command with no file specification, it prompts you for a file specification. For example: $ PWCONVERT FILENAME: In response to this prompt, you must supply a device name, and optionally a directory and file name to convert. You may include qualifiers. Table_5-1_PWCONVERT_Qualifiers__________________________________ Qualifier______Description_____________________Default__________ /CODE_PAGE=n The code page used to None translate encoded characters, where n is the code page. For more information about code pages, refer to the OpenVMS User's Guide. /DISABLE=keywordisables the function of the /NODISABLE conversion utility specified by the keyword. The keywords are: o ACE, which specifies that the conversion utility will not check for PATHWORKS ACEs on the files. o STRUCTURE_LEVEL, which specifies that the conversion utility will not check the file system type (ODS-2 or ODS-5). /LOG=log- Creates a log file containing /NOLOG. file- the file names converted. You Information is specification can specify the location and displayed and name of the log file using no log file is this qualifier. created. (continued on next page) After You Install the Advanced Server 5-11 After You Install the Advanced Server 5.7 Converting Encoded File Names from ODS-2 to ODS-5 Table_5-1_(Cont.)_PWCONVERT_Qualifiers__________________________ Qualifier______Description_____________________Default__________ /VERBOSE Displays all the file names /NOVERBOSE scanned during the conversion operation. /NOLIST Suppresses the display of /LIST all the file names that are converted. Only error messages _______________are_displayed.___________________________________ 5.7.2 Example of Converting an Encoded File Name In this example, the file named A FILE.TXT has been created by a Windows 95 client on DISKA, and has been encoded as A__20FILE.TXT. The device DISKA has been converted from ODS-2 to ODS-5. As viewed from OpenVMS, the file appears as follows: $ DIRECTORY DISKA:[FILES] Directory DISKA:[FILES] . . . A__20FILE.TXT $ Use the PWCONVERT command to convert this file name, as follows: $ PWCONVERT/VERBOSE DISKA:[FILES]A__20FILE.TXT Scanning file - DISKA:[FILES]A__20FILE.TXT;1 Renamed A__20FILE.TXT to A FILE.TXT Convert Utility Complete $ 5-12 After You Install the Advanced Server After You Install the Advanced Server 5.7 Converting Encoded File Names from ODS-2 to ODS-5 5.7.3 Example of Converting All Encoded File Names To convert all the encoded file names on a disk device and directory, enter the PWCONVERT command, specifying the disk device and directory without a file name. For example, to convert all the encoded file names stored on device DISK$USER1, enter the following: $ PWCONVERT FILENAME: DISK$USER1: Renamed A__20FILE.TXT to A FILE.TXT . . . Convert Utility Complete 5.8 Installing Optional Server Administration Tools The Advanced Server provides optional client-based server administration tools that allow you to manage the server from Windows 98, Windows 95, Windows for Workgroups, or Windows NT clients. These tools are available in the PWUTIL share after installing, configuring and starting the server. The SRVTOOLS directory in the PWUTIL share contains a subdirectory for each type of client computer. Refer to the README.TXT file in the appropriate subdirectory for instructions on installing the software on the client computer. Refer to the Windows NT Server documentation or use online Help for more information about how to use Windows NT server administration tools. After You Install the Advanced Server 5-13 6 ________________________________________________________________ Implementing a Wide Area Network This chapter describes how to set up a wide area network (WAN) using one of the TCP/IP transport software products supported by the Advanced Server for OpenVMS software. This chapter consists of the following sections: o Section 6.1, Enabling Wide Area Networking o Section 6.2, Using the LMHOSTS File in a Wide Area Network o Section 6.3, Using WINS in a Wide Area Network 6.1 Enabling Wide Area Networking The Advanced Server for OpenVMS software allows you to use one or both of the following methods for wide area networking name resolution: o LMHOSTS file for TCP/IP o Windows Internet Name Servers (WINS) In order to use them, they must be enabled using the Configuration Manager. You can enable them through the PWRK$CONFIG.COM command procedure, which provides access to the Configuration Manager when you answer YES to the question "Do you want to change server configuration parameters." To enable one or both of the wide area networking methods, select the Transports screen and select the appropriate checkbox. Alternatively, you can run the Configuration Manager after the server is configured and started, as described in the Advanced Server for OpenVMS Server Administrator's Guide. Implementing a Wide Area Network 6-1 Implementing a Wide Area Network 6.2 Using the LMHOSTS File in a Wide Area Network 6.2 Using the LMHOSTS File in a Wide Area Network The Advanced Server for OpenVMS software provides the ability to set up a wide area network with the TCP/IP transport through the use of the LMHOSTS file. This file contains a list of domain controllers and member servers that are not in the same TCP/IP subnet as the primary domain controller. The LMHOSTS file allows the Advanced Server to participate in a Windows NT wide area network as well. Unlike a Windows NT Server, the Advanced Server does not support remote LMHOSTS files (called into the Windows NT LMHOSTS file using #INCLUDE). To include the same host names as an existing LMHOSTS file on a Windows NT Server, copy the LMHOSTS file to the Advanced Server then manually insert the entries into the Advanced Server LMHOSTS file. 6.2.1 Setting Up a TCP/IP Wide Area Network To set up a TCP/IP wide area network, modify the LMHOSTS file, which consists of a list of the host names and TCP /IP addresses of the domain controllers and member servers in the wide area network that are in the same domain. When you include a node in the LMHOSTS file, the primary domain controller copies the user account database onto that node and keeps it up to date. If you omit a node, its user account database may become out of date. You can modify the LMHOSTS file at any time. As long as the LMHOSTS file exists, users can establish TCP/IP connections to any server listed in the file. 6.2.2 The LMHOSTS Directory You set up a wide area network by supplying the following file on all OpenVMS file servers that are in different subnets: PWRK$LMROOT:[LANMAN]LMHOSTS. (The LMHOSTS file has no file extension.) 6-2 Implementing a Wide Area Network Implementing a Wide Area Network 6.2 Using the LMHOSTS File in a Wide Area Network 6.2.3 LMHOSTS File Syntax In the LMHOSTS file, create a list of nodes by specifying the following line for each node: address nodename #PRE #DOM:domain_name Where: o address is an Internet address of form x.x.x.x, where x is a decimal number from 0 to 255. o nodename is a name from 1 to 16 characters long, and may include a control character. (The format of a control character is \0Xnn or \nn, where n is a hexadecimal digit.) To preserve the case of the characters, enclose the node name in double quotation marks. If the node name is not enclosed in quotation marks, the alphabetic characters are set to uppercase characters before the node name is loaded into cache (see parameter #PRE, below) or used for matching. If the node name includes a control character in the last byte, you should include blank characters to explicitly control the placement of the control character. When the node name has fewer than 16 characters, it is padded with blank characters. The following are some valid node names: 1. speedy 2. "speedy\0X03" 3. "speedy \0X03" In Example 1, the node name is interpreted as uppercase (SPEEDY) and will be padded with blank characters. In Example 2, the node name is not interpreted as uppercase, and will be padded with blank characters for bytes 8 through 16. In Example 3, the node name is not interpreted as uppercase, and no padding needs to be inserted because blank spaces are already included, in order to make the control character reside in byte 16. o #PRE is an optional tag that indicates that the entry should be preloaded into the cache. Implementing a Wide Area Network 6-3 Implementing a Wide Area Network 6.2 Using the LMHOSTS File in a Wide Area Network o #DOM:domain-name is an optional tag that associates the entry with the Windows NT domain specified by domain-name. It is required when the entry is a domain controller. This affects how the logon and browser services behave in routed environments. It is also used in user account management and in trust relationships. For example, the following entry might be included in the LMHOSTS file: 12.13.14.15 SERVER #PRE #DOM:VMSDOMAIN This entry results in NetBIOS name SERVER with Internet address 12.13.14.15 being preloaded into the cache. Both the NetBIOS name SERVER and the NetBIOS name VMSDOMAIN (the name of the domain) will be available for matching. 6.2.4 Managing the LMHOSTS File To change the list of available nodes, you can edit the file at any time. Domain names are resolved by checking the LMHOSTS file dynamically. To disable LMHOSTS name resolution, rename the LMHOSTS file to any name other than LMHOSTS. When you modify or disable the LMHOSTS file, it is not necessary to restart the Advanced Server. The change is effective immediately and is referenced at the next lookup. 6.2.5 Using the LMHOSTS Log File If errors occur when the LMHOSTS file is accessed, the errors are recorded in the following file: PWRK$LMROOT:[LOGS]PWRK$KNBDAEMON_nodename.LOG This file is open and being written to while the Advanced Server is running. To close the log file, you must stop the Advanced Server. To prevent the log file from becoming too large, each error is logged only once: the first time it occurs. If an error is found in the log file, it is not logged again. 6-4 Implementing a Wide Area Network Implementing a Wide Area Network 6.3 Using WINS in a Wide Area Network 6.3 Using WINS in a Wide Area Network You can configure the Advanced Server as a WINS client. This allows the Advanced Server to use a WINS server for NetBIOS name registration, resolution, renewal, and release in a wide area network configuration. For more information on how to use the Configuration Manager to configure the Advanced Server to use WINS, re- fer to the Advanced Server for OpenVMS Server Administrator's Guide. 6.3.1 Setting up WINS for OpenVMS Clusters To allow clients that are configured for WINS support to use an Advanced Server alias name to connect to a clustered PATHWORKS Advanced Server across a WAN, you must add to the WINS database a static multihomed entry for the Advanced Server alias name. The following is an example of an entry for the Advanced Server alias name alpha1_alias: alpha1_alias 16.20.240.24 When adding the static multihomed entry for the Advanced Server alias name, you should enter the TCP/IP address of each node in the OpenVMS cluster that is running the Advanced Server. ________________________Note ________________________ The TCP/IP address that you place at the top of the list in the WINS database should be that of the first node that will start the Advanced Server in the cluster. _____________________________________________________ For more information about adding static entries to the WINS database, refer to your WINS product documentation. Implementing a Wide Area Network 6-5 7 ________________________________________________________________ Removing Advanced Server for OpenVMS Software This chapter describes how to remove Advanced Server for OpenVMS software from your system. If you have to reinstall the Advanced Server for OpenVMS software, you may need to remove the Advanced Server for OpenVMS software. For example, if the Installation Verification Procedure indicated that the software installation procedure failed, you must reinstall the software. But first you might need to remove the Advanced Server software. o If the system has enough free disk space, you can install the server again without deinstalling the Advanced Server. o If the system does not have enough disk space, you must remove the Advanced Server before reinstalling it. For more information about disk space requirements, see Section 1.8.8, Step 8: Check Disk Space Requirements. This chapter consists of the following sections: o Section 7.1, The Advanced Server Deinstallation Procedure o Section 7.2, Removing Advanced Server Configuration Parameters o Section 7.3, Removing Advanced Server for OpenVMS Software o Section 7.4, Sample Advanced Server Removal Procedure Removing Advanced Server for OpenVMS Software 7-1 Removing Advanced Server for OpenVMS Software 7.1 The Advanced Server Deinstallation Procedure 7.1 The Advanced Server Deinstallation Procedure You remove the Advanced Server using a command procedure that is included when you install the Advanced Server for OpenVMS software. The deinstallation command procedure performs the following operations: o Shuts down the server automatically. o Prompts you to enter information necessary to complete the removal procedure. o Attempts to start the OpenVMS Registry server if registry services are not available. o Removes all Advanced Server for OpenVMS images, support files, and logical names that are created during the installation procedure. o Optionally removes the Advanced Server data from the system, including the user accounts database, the shares database, and the server configuration parameters. o Removes the Advanced Server user accounts. o Removes the NETBIOS$ACCESS OpenVMS identifier. o Removes Advanced Server DECnet objects. 7.2 Removing Advanced Server Configuration Parameters When you remove the Advanced Server data files, the dein- stallation procedure will remove the server configuration parameters that are stored as values, and their keys, from the OpenVMS Registry. To complete this operation, the deinstallation procedure: o Requires that registry services be available on the system. The Registry Server must be running on the system or in the cluster, and the registry database must be available on the system. If registry services are not available, the deinstallation procedure will attempt to start the Registry Server. Registry services must be enabled on the system in order to run the Registry Server. Refer to the OpenVMS System Manager's 7-2 Removing Advanced Server for OpenVMS Software Removing Advanced Server for OpenVMS Software 7.2 Removing Advanced Server Configuration Parameters Manual for more information about ensuring registry services are available. o Invokes the PWRK$REGUTL parameter management utility (described in the Server Administrator's Guide). 7.3 Removing Advanced Server for OpenVMS Software To start the deinstallation procedure and remove Advanced Server for OpenVMS software: 1. Ensure that you are logged in to the SYSTEM account. 2. Ensure that no processes are running the Advanced Server ADMINISTER command line interface. 3. Start the deinstallation command procedure, as follows: $ @SYS$UPDATE:PWRK$DEINSTAL Table 7-1, PWRK$DEINSTAL Prompts, tells you how to respond to the prompts the deinstallation procedure displays. Table_7-1_PWRK$DEINSTAL_Prompts_________________________________ If you want the removal Enter . . . At_this_prompt_._._.____procedure_to_._._.______________________ Are you sure you Continue YES want to deinstall Advanced Server for OpenVMS[no]: Exit Do you want to delete Save the Advanced Server on- the Advanced Server disk structure, including the data files [no]: user accounts database, the share files, and the server configuration parameters in the OpenVMS Registry Remove the Advanced Server on- YES disk structure, including the user accounts database, the share files, and the server ________________________configuration_parameters________________ Removing Advanced Server for OpenVMS Software 7-3 Removing Advanced Server for OpenVMS Software 7.4 Sample Advanced Server Removal Procedure 7.4 Sample Advanced Server Removal Procedure This is a sample of the removal procedure for Advanced Server software. This procedure shuts down all Advanced Server V7.2 for OpenVMS servers and deletes most Advanced Server V7.2 for OpenVMS images. Are you sure you want to deinstall Advanced Server V7.2 for OpenVMS? Deinstall? [no]: YES Do you want to delete the Advanced Server data files [no]: YES Shutting down the currently running server(s)... Removing Advanced Server registry parameter and keys Deleting Advanced Server for OpenVMS common images... Deleting Advanced Server for OpenVMS NETBIOS component... Deleting Advanced Server V7.2 for OpenVMS images... Deleting Advanced Server data files... Removing PWRK$DEFAULT and PWRK$GUEST VMS accounts... Removing Advanced Server for OpenVMS identifiers... Removing Advanced Server for OpenVMS DECnet objects... Deassigning Advanced Server for OpenVMS logical names... Advanced Server V7.2 for OpenVMS is now deinstalled. 7-4 Removing Advanced Server for OpenVMS Software A ________________________________________________________________ Installation and Upgrade Checklist Table A-1 summarizes the tasks that you need to perform to install and configure the Advanced Server. You can photocopy this table and use it as a checklist as you read about and complete the tasks in this book. Table_A-1_Installation_and_Upgrade_Checklist____________________ (continued on next page) Installation and Upgrade Checklist A-1 Installation and Upgrade Checklist Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________ < >1. Prepare for the installation by completing all pre- installation tasks on the checklist in Section 1.8, Pre-installation Tasks, including the following: a. Make sure that you have the required hardware and software. b. Log in to the SYSTEM account and back up the system disks. c. Make sure that you have enough disk space to install the software. d. Make sure that the system parameters GBLPAGES, GBLSECTIONS, PROCSECTCNT, and SCSNODE are set properly. e. Make sure that the queue manager is running and that the time zone is configured correctly. f. Verify that DECnet (or DECnet-Plus) and TCP/IP, if needed, are running. g. Check OpenVMS cluster configuration, if installing on a cluster. h. Check that OpenVMS registry services are available on the Advanced Server system. < >2. Start the installation procedure and respond to installation prompts. You may choose to install the following: o The complete Advanced Server. o The license server only (if you chose not to install the Advanced Server). o External authentication software only (if you chose not to install the Advanced Server). < >3. Start the configuration procedure and respond to configuration prompts. (continued on next page) A-2 Installation and Upgrade Checklist Installation and Upgrade Checklist Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________ < >4. Run the Installation Verification Procedure (if you did not do so when you installed the Advanced Server). < >5. Start the server (if you did not do so when you configured the Advanced Server). < >6. Install Windows NT server administration tools __________(optional).___________________________________________ Installation and Upgrade Checklist A-3 B ________________________________________________________________ Sample Advanced Server Installation and Configuration This appendix shows sample installation and configuration procedures for the Advanced Server. B.1 Sample Advanced Server Installation Procedure The following example shows a sample installation dialog for the Advanced Server. In this example, the installation takes place on a system where the Advanced Server has not been installed previously. If the Advanced Server had been installed previously on the system, the installation dialog would differ slightly. $ @SYS$UPDATE:VMSINSTAL ASOVMS072 SYS$DEVICE:[KITS.ASOVMS] OpenVMS AXP Software Product Installation Procedure V7.2 It is 3-NOV-1998 at 09:31. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: ASOVMS V7.2 Beginning installation of ASOVMS V7.2 at 09:31 Sample Advanced Server Installation and Configuration B-1 Sample Advanced Server Installation and Configuration B.1 Sample Advanced Server Installation Procedure %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Advanced Server V7.2 for OpenVMS Installation © Digital Equipment Corporation 1998. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Please select from the following install options: Advanced Server V7.2 for OpenVMS (complete) Advanced Server V7.2 for OpenVMS license server (only) External Authentication images (only) * Do you want to install the complete Advanced Server for OpenVMS [YES]? The following components will be installed: Advanced Server V7.2 for OpenVMS (complete) If the selection is correct, the installation will continue. If the selection is not correct, you can change your selection. Press CTRL/Y if you want to terminate the installation. * Is the selection correct [YES]? %ASOVMS-I-VERSION, Checking for OpenVMS version 7.2 ... * Do you want to run the IVP after the installation is finished [YES]? * Do you want to purge files replaced by this installation [YES]? %ASOVMS-I-FREEBLKS, Checking for 139500 free blocks User Accounts and User Identification Codes (UICs) -------------------------------------------------- The Advanced Server V7.2 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. B-2 Sample Advanced Server Installation and Configuration Sample Advanced Server Installation and Configuration B.1 Sample Advanced Server Installation Procedure o If there is an existing account PCFS$ACCOUNT, the default is the UIC group number associated with PCFS$ACCOUNT. o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, 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. Sample Advanced Server Installation and Configuration B-3 Sample Advanced Server Installation and Configuration B.1 Sample Advanced Server Installation Procedure For more information about UIC group numbers, see the OpenVMS System Manager's Manual. * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]: All questions have been answered. The installation of the Advanced Server for OpenVMS will continue. %ASOVMS-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$DEFAULT. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights database %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights database %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %ASOVMS-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %ASOVMS-I-DCLCMDS, Installing the Advanced Server DCL commands %ASOVMS-I-SPECIFY, Specifying target directories for the provided files %ASOVMS-I-OBSOLETE, Deleting obsolete files Next Steps ---------- To continue the installation procedure, enter the following command to execute the server configuration command procedure: $ @SYS$UPDATE:PWRK$CONFIG For information about the configuration command procedure, see the Advanced Server V7.2 for OpenVMS Installation and Configuration Guide. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... © Digital Equipment Corporation 1998. All rights reserved. Starting Installation Verification Procedure for Advanced Server V7.2 for OpenVMS %PWRK-I-NORMAL, IVP completed successfully Installation of ASOVMS V7.2 completed at 09:40 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]ASOVMS072.VMI_DATA VMSINSTAL procedure done at 09:40 B-4 Sample Advanced Server Installation and Configuration Sample Advanced Server Installation and Configuration B.2 Sample Advanced Server Configuration Procedure B.2 Sample Advanced Server Configuration Procedure The following example shows a sample configuration dialog for the Advanced Server. $ @SYS$UPDATE:PWRK$CONFIG Advanced Server V7.2 for OpenVMS Configuration Procedure The Advanced Server stores and accesses the following types of data files: o Configuration parameter files o License server data files o Log files o Printer spool files o Virtual memory section files You can specify any existing OpenVMS disk device that has at least 76500 free blocks of disk space to store these data files. Note: The server frequently accesses the data files stored on the disk. If these files are stored on the system disk, it can degrade the performance of both the OpenVMS system and the server. Therefore, Digital recommends that you specify a disk other than the system disk. Enter disk device name where the Advanced Server data files will be stored [PWROOT:]: Creating Advanced Server directory tree on PWROOT:... PWRK$LICENSE_SERVER_STATE.DAT already exists, not superseded. %CREATE-I-EXISTS, PWRK$COMMONROOT:[000000] already exists Checking to see if the OpenVMS Registry Services are available... %RUN-S-PROC_ID, identification of created process is 0000023B Populating OpenVMS Registry with required Advanced Server & NT parameters... Please wait, this may take one to two minutes to complete ... Required OpenVMS Registry file server keys and values have been created. Migrating LANMAN.INI parameters to the OpenVMS Registry... Verifying SAM database files... Creating Advanced Server directory tree... Copying client files to Advanced Server directory tree... Changing the server configuration parameters will allow you to modify this server's client capacity and select the transports to be used. SPEEDY is currently configured to + support 20 PC clients + use the following transport(s): DECnet Sample Advanced Server Installation and Configuration B-5 Sample Advanced Server Installation and Configuration B.2 Sample Advanced Server Configuration Procedure If you want this server to be the primary domain controller, you should configure it to use all the transports used by any of the backup servers in the domain. B-6 Sample Advanced Server Installation and Configuration Sample Advanced Server Installation and Configuration B.2 Sample Advanced Server Configuration Procedure If you want this server to be a backup domain controller, you should configure it to have at least one transport in common with the domain's primary domain controller, otherwise this configuration will fail. If you do not change the configuration parameters now, you may do so later by typing ADMIN/CONFIG. Do you want to change the server configuration parameters now? [YES]: NO Reading current configuration parameters ... Your Advanced Server for OpenVMS is presently configured to run as follows: 1. Run the license server: NO 2. Enable Timesource service: NO 3. Enable Alerter service: YES 3a. Alert user names: Administrator 4. Enable Netlogon service: YES 5. Advanced Server domain: LANGROUP 6. Advanced Server role: PRIMARY 7. Advanced Server computer name: SPEEDY 8. Server announce comment: Advanced Server V7.2 for OpenVMS Enter item number, or RETURN to use these values [DONE]: 5 An Advanced Server domain is a collection of computers that share a common security database and policy. Each domain has a unique name. A network can have many domains. The Advanced Server domain name can be up to 15 characters long. The domain name must be different than the computer name. Enter Advanced Server domain name for this system [5]: SPUNKY.DOM Your Advanced Server for OpenVMS is presently configured to run as follows: 1. Run the license server: NO 2. Enable Timesource service: NO 3. Enable Alerter service: YES 3a. Alert user names: Administrator 4. Enable Netlogon service: YES 5. Advanced Server domain: SPUNKY.DOM 6. Advanced Server role: PRIMARY 7. Advanced Server computer name: SPEEDY 8. Server announce comment: Advanced Server V7.2 for OpenVMS Enter item number, or RETURN to use these values [DONE]: Sample Advanced Server Installation and Configuration B-7 Sample Advanced Server Installation and Configuration B.2 Sample Advanced Server Configuration Procedure Saving parameters to the OpenVMS Registry... Creating SAM datafiles... Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB ... New sharefile has been created. ADMIN$ added IPC$ added PWUTIL added PWLICENSE added PWLIC added B-8 Sample Advanced Server Installation and Configuration Sample Advanced Server Installation and Configuration B.2 Sample Advanced Server Configuration Procedure The Advanced Server Administrator network account is used to administer the server. The Administrator network account is mapped by default to the OpenVMS SYSTEM account. The network account password can be up to 14 characters long and the case of the characters used will be preserved. Enter Administrator network account password: Re-enter to verify password: Changing password for Administrator network account... Checking system resources... The current system configuration for SPEEDY will support 20 PC clients. The Advanced Server is configured to use DECnet, NetBEUI, TCP/IP. To automatically start the Advanced Server V7.2 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 below the lines that start all network transports (such as DECnet). Do you want to start the Advanced Server V7.2 on node SPEEDY now [YES]: The file server will use DECnet, NetBEUI, TCP/IP. Advanced Server mail notification will use DECnet. Process NETBIOS created with identification 00000248 Process PWRK$NBDAEMON created with identification 0000024A Process PWRK$KNBDAEMON created with identification 0000024C Process PWRK$LICENSE_R created with identification 0000024E Checking to see if the OpenVMS Registry Services are available... The Advanced Server is configured to support 20 PC clients. Process PWRK$MASTER created with identification 00000251 The master process will now start all other Advanced Server processes. $ Sample Advanced Server Installation and Configuration B-9 C ________________________________________________________________ Sample Standalone License Server Installation and Configuration This appendix shows sample installation and configuration procedures for a standalone license server on an OpenVMS cluster. C.1 Sample Standalone License Server Installation Procedure The following example shows a sample installation dialog for the standalone license server. $ @SYS$UPDATE:VMSINSTAL OpenVMS AXP Software Product Installation Procedure V7.2 It is 1-DEC-1998 at 10:13. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: PWRK$KITS The following products will be processed: ASOVMS V7.2 Beginning installation of ASOVMS V7.2 at 10:14 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Advanced Server V7.2 for OpenVMS Installation © Digital Equipment Corporation 1998. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Sample Standalone License Server Installation and Configuration C-1 Sample Standalone License Server Installation and Configuration C.1 Sample Standalone License Server Installation Procedure This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Please select from the following install options: Advanced Server V7.2 for OpenVMS (complete) Advanced Server V7.2 for OpenVMS license server (only) External Authentication images (only) * Do you want to install the complete Advanced Server for OpenVMS [YES]? NO * Do you want to install only the Advanced Server's license server [NO]? YES * Do you want to install only the External Authentication images [NO]? The following components will be installed: Advanced Server V7.2 for OpenVMS license server (only) If the selection is correct, the installation will continue. If the selection is not correct, you can change your selection. Press CTRL/Y if you want to terminate the installation. * Is the selection correct [YES]? %ASOVMS-I-VERSION, Checking for OpenVMS version 7.2 ... * Do you want to run the IVP after the installation is finished [YES]? * Do you want to purge files replaced by this installation [YES]? %ASOVMS-I-FREEBLKS, Checking for 139500 free blocks All questions have been answered. The installation of the Advanced Server for OpenVMS will continue. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %ASOVMS-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %ASOVMS-I-DCLCMDS, Installing the Advanced Server DCL commands %ASOVMS-I-SPECIFY, Specifying target directories for the provided files %ASOVMS-I-OBSOLETE, Deleting obsolete files Next Steps ---------- To continue the installation procedure, enter the following command to execute the server configuration command procedure: $ @SYS$UPDATE:PWRK$CONFIG For information about the configuration command procedure, see the Advanced Server V7.2 for OpenVMS Installation and Configuration Guide. C-2 Sample Standalone License Server Installation and Configuration Sample Standalone License Server Installation and Configuration C.1 Sample Standalone License Server Installation Procedure %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... © Digital Equipment Corporation 1998. All rights reserved. Starting Installation Verification Procedure for Advanced Server V7.2 for OpenVMS %PWRK-I-NORMAL, IVP completed successfully Installation of ASOVMS V7.2 completed at 10:21 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]ASOVMS072.VMI_DATA VMSINSTAL procedure done at 10:28 C.2 Sample Configuration Dialog for Standalone License Server The following example shows a sample configuration dialog for the standalone license server. $ @SYS$UPDATE:PWRK$CONFIG Advanced Server V7.2 for OpenVMS Configuration Procedure The Advanced Server stores and accesses the following types of data files: o Configuration parameter files o License server data files o Log files o Printer spool files o Virtual memory section files You can specify any existing OpenVMS disk device that has at least 5500 free blocks of disk space to store these data files. Note: The server frequently accesses the data files stored on the disk. If these files are stored on the system disk, it can degrade the performance of both the OpenVMS system and the server. Therefore, Digital recommends that you specify a disk other than the system disk. Enter disk device name where the Advanced Server data files will be stored [SYS$SYSDEVICE:]: PWROOT Creating Advanced Server directory tree on PWROOT:... The license server can serve client-based licenses for Advanced Server clients over DECnet, NetBEUI, and TCP/IP. The Advanced Server need not be running for the license server to operate. Sample Standalone License Server Installation and Configuration C-3 Sample Standalone License Server Installation and Configuration C.2 Sample Configuration Dialog for Standalone License Server Do you want to serve client-based licenses over DECnet [yes]: Do you want to serve client-based licenses over NetBEUI [no]: YES Do you want to serve client-based licenses over TCP/IP [no]: YES Do you want to start the Advanced Server license server now [yes]: NO C-4 Sample Standalone License Server Installation and Configuration Sample Standalone License Server Installation and Configuration C.2 Sample Configuration Dialog for Standalone License Server To automatically start the license server at system startup, you should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file: $ @SYS$STARTUP:PWRK$LICENSE_STARTUP Note: Add this line below the lines that start all network transports (such as DECnet). $ Sample Standalone License Server Installation and Configuration C-5 D ________________________________________________________________ Sample External Authentication Software Installation The following example shows a sample installation dialog when you select to install the External Authentication software only. $ @SYS$UPDATE:VMSINSTAL.COM ASOVMS PWRK$KITS OpenVMS AXP Software Product Installation Procedure V7.2 It is 4-DEC-1998 at 19:22. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: ASOVMS V7.2 Beginning installation of ASOVMS V7.2 at 19:22 © Digital Equipment Corporation 1998. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Advanced Server V7.2 for OpenVMS Installation Please select from the following install options: Sample External Authentication Software Installation D-1 Sample External Authentication Software Installation Advanced Server V7.2 for OpenVMS (complete) Advanced Server V7.2 for OpenVMS license server (only) External Authentication images (only) * Do you want to install the complete Advanced Server for OpenVMS [YES]? NO * Do you want to install only the Advanced Server's license server [NO]? NO * Do you want to install only the External Authentication images [NO]? YES The following components will be installed: External Authentication images (only) If the selection is correct, the installation will continue. If the selection is not correct, you can change your selection. Press CTRL/Y if you want to terminate the installation. * Is the selection correct [YES]? %ASOVMS-I-VERSION, Checking for OpenVMS version 7.2 ... * Do you want to run the IVP after the installation is finished [YES]? * Do you want to purge files replaced by this installation [YES]? %ASOVMS-I-FREEBLKS, Checking for 139500 free blocks All questions have been answered. The installation of the Advanced Server for OpenVMS will continue. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %ASOVMS-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %ASOVMS-I-DCLCMDS, Installing the Advanced Server DCL commands %ASOVMS-I-SPECIFY, Specifying target directories for the provided files %ASOVMS-I-OBSOLETE, Deleting obsolete files Next Steps ---------- To continue the installation procedure, enter the following command to execute the server configuration command procedure: $ @SYS$UPDATE:PWRK$CONFIG For information about the configuration command procedure, see the Advanced Server V7.2 for OpenVMS Installation and Configuration Guide. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... © Digital Equipment Corporation 1998. All rights reserved. Starting Installation Verification Procedure for Advanced Server V7.2 for OpenVMS %PWRK-I-NORMAL, IVP completed successfully D-2 Sample External Authentication Software Installation Sample External Authentication Software Installation Installation of ASOVMS V7.2 completed at 19:28 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]ASOVMS072.VMI_DATA VMSINSTAL procedure done at 19:29 $ Sample External Authentication Software Installation D-3 E ________________________________________________________________ Advanced Server Files and On-Disk Structure This appendix includes the following sections: o Section E.1, Advanced Server Files o Section E.2, Advanced Server On-Disk Structure E.1 Advanced Server Files Table E-1 describes the files created during the installation of the Advanced Server. Table_E-1_Files_Installed_for_the_Advanced_Server_______________ File_________________________________Description________________ DCPS$EXAMPLES:PWRK$BORDER.LUP DECprint Supervisor printer layup for borders DCPS$EXAMPLES:PWRK$NOBORDER.LUP DECprint Supervisor printer layup for no borders DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_ DECprint Supervisor printer BORDER.LUP layup for borders with Windows DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_ DECprint Supervisor printer NOBORDER.LUP layup for no borders with Windows SYS$HELP:ASOVMS072.RELEASE_NOTES Advanced Server release notes SYS$HELP:PCDISKHLP.HLB DOS File Maintenance utility help library (continued on next page) Advanced Server Files and On-Disk Structure E-1 Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$HELP:PWRK$ADMIN_CFG.HLB Configuration Manager help library SYS$HELP:PWRK$ADMIN_LIC.HLB License Manager help library SYS$LIBRARY:NETBIOSSHR.EXE NetBIOS for DECnet shareable image SYS$LIBRARY:PCDISKSHR.EXE DOS File Maintenance utility shareable image SYS$LIBRARY:PCSA_MAILSHR.EXE Mail notification shareable image SYS$LIBRARY:PWRK$CMTLIBSHR.EXE Configurator, Monitor, and Tuner shareable library SYS$LIBRARY:PWRK$CMTSHR.EXE Configurator, Monitor, and Tuner shareable image SYS$LIBRARY:PWRK$CSSHR_V7.EXE Common services shareable image SYS$LIBRARY:PWRK$DEVCTL_LA51.TLB LA51 device control library SYS$LIBRARY:PWRK$DEVCTL_LA70.TLB LA70 device control library SYS$LIBRARY:PWRK$DEVCTL_LA75P.TLB LA75P device control library SYS$LIBRARY:PWRK$DEVCTL_LG01.TLB LG01 device control library SYS$LIBRARY:PWRK$DEVCTL_LG02.TLB LG02 device control library SYS$LIBRARY:PWRK$DEVCTL_LG06.TLB LG06 device control library SYS$LIBRARY:PWRK$DEVCTL_LG31.TLB LG31 device control library SYS$LIBRARY:PWRK$DEVCTL_DL1100.TLB DEClaser 1100 device control library SYS$LIBRARY:PWRK$DEVCTL_DL2100.TLB DEClaser 2100 device control library SYS$LIBRARY:PWRK$DEVCTL_DL2100P.TLB DEClaser 2100P device control library (continued on next page) E-2 Advanced Server Files and On-Disk Structure Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$LIBRARY:PWRK$DEVCTL_DL2200.TLB DEClaser 2200 device control library SYS$LIBRARY:PWRK$DEVCTL_DL2200P.TLB DEClaser 2200P device control library SYS$LIBRARY:PWRK$DEVCTL_DL3200.TLB DEClaser 3200 device control library SYS$LIBRARY:PWRK$DEVCTL_FX1050.TLB FX1050 device control library SYS$LIBRARY:PWRK$DEVCTL_FX850.TLB FX850 device control library SYS$LIBRARY:PWRK$DEVCTL_GENERIC.TLB Generic device control library SYS$LIBRARY:PWRK$DEVCTL_HP_ HP LaserJet device control LASERJET.TLB library SYS$LIBRARY:PWRK$DEVCTL_LA210.TLB LA210 device control library SYS$LIBRARY:PWRK$DEVCTL_LA324.TLB LA324 device control library SYS$LIBRARY:PWRK$DEVCTL_LA50.TLB LA50 device control library SYS$LIBRARY:PWRK$DEVCTL_LA75.TLB LA75 device control library SYS$LIBRARY:PWRK$DEVCTL_LJ250.TLB LJ250 device control library SYS$LIBRARY:PWRK$DEVCTL_LN03.TLB LN03 device control library SYS$LIBRARY:PWRK$DEVCTL_LN03P.TLB LN03 PLUS device control library SYS$LIBRARY:PWRK$DEVCTL_LN03R.TLB LN03R device control library SYS$LIBRARY:PWRK$DEVCTL_PROPRINTER.TLProprinter device control library SYS$LIBRARY:PWRK$DEVCTL_SILENTWRITER.SilentWriter device control library (continued on next page) Advanced Server Files and On-Disk Structure E-3 Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$LIBRARY:PWRK$FSLIB_ODS2.EXE ODS2/ODS5 addon library SYS$LIBRARY:PWRK$LICENSE_LIBSHR.EXE License shareable library SYS$LIBRARY:PWRK$LICENSE_ License management MGMTSHR.EXE shareable image SYS$LIBRARY:PWRK$MSV1_0_ACMESHR.EXE External authentication support library SYS$LIBRARY:PWRK$PCMSHR.EXE Cache manager shareable image SYS$LIBRARY:PWRK$PRINTER_ Printer information file INFORMATION.DAT SYS$LIBRARY:PWRK$SDA.EXE Extension for the System Dump Analyzer SYS$LIBRARY:PWRK$SDA_V1.EXE Original extension for the System Dump Analyzer SYS$LIBRARY:PWRK$STREAMSSHR_V7.EXE Streams shareable image SYS$LIBRARY:PWRK$WINLIBSHR.EXE Advanced Server character- cell user interface shareable image SYS$LIBRARY:PWRK$XTILIBSHR.EXE X/Open Transport Interface shareable library SYS$LIBRARY:PWRK$XTINETBIOSSHR.EXE X/Open Transport Interface shareable image for NetBIOS SYS$LIBRARY:PWRK$XTINSPNBSHR.EXE X/Open Transport Interface shareable image for DECnet SYS$LIBRARY:XTI.H X/Open Transport Interface header file SYS$LOADABLE_IMAGES:PCFSDRIVERDEF.STBData structure definitions for PCFSDRIVER SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_ Streams system loadable V7.EXE image SYS$LOADABLE_IMAGES:PWRK$STREAMSOS_ Symbol table for V7.STB PWRK$STREAMSOS_V7.EXE (continued on next page) E-4 Advanced Server Files and On-Disk Structure Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_ DECnet I/O and double V7.EXE mapping driver SYS$LOADABLE_IMAGES:SYS$PCFSDRIVER_ Symbol table for V7.STB SYS$PCFSDRIVER_V7.EXE SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_ Cluster Interconnect I/O V7.EXE driver SYS$LOADABLE_IMAGES:SYS$PCIDRIVER_ Symbol table for V7.STB SYS$PCIDRIVER_V7.EXE SYS$MANAGER:PWRK$DEFINE_COMMANDS.COM[Command procedure that defines symbols for commands that run Advanced Server utilities SYS$MANAGER:PWRK$DEFINE_ROOT.COM Directory tree logical SYS$MANAGER:PWRK$SHOWSYS.COM Command procedure that shows status of file server processes SYS$MESSAGE:PWRK$MSG.EXE Advanced Server for OpenVMS message file SYS$STARTUP:PWRK$CHECK_PARAMS.COM Command procedure that checks system resources SYS$STARTUP:PWRK$COMMON_LOGICALS.COM Command procedure that defines common logicals SYS$STARTUP:PWRK$COMMON_SHUTDOWN.COM Common shutdown command procedure SYS$STARTUP:PWRK$COMMON_STARTUP.COM Common startup command procedure SYS$STARTUP:PWRK$GATHER_INFO.COM Command procedure that gathers information into a save set for reporting problems [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) Advanced Server Files and On-Disk Structure E-5 Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$STARTUP:PWRK$LICENSE_R_ Startup for the License START.COM Registrar SYS$STARTUP:PWRK$LICENSE_S_ Startup for the license START.COM server SYS$STARTUP:PWRK$LICENSE_ License server shutdown SHUTDOWN.COM command procedure SYS$STARTUP:PWRK$LICENSE_ License server startup STARTUP.COM command procedure SYS$STARTUP:PWRK$LOGICALS.COM Command procedure that defines logical names SYS$STARTUP:PWRK$SHUTDOWN.COM Shutdown command procedure SYS$STARTUP:PWRK$STARTUP.COM Startup command procedure SYS$SYSTEM:NETBIOS.EXE NetBIOS for DECnet SYS$SYSTEM:PCDISK.EXE DOS File Maintenance utility SYS$SYSTEM:PCSA$MAIL_SERVER.EXE PATHWORKS client mail server SYS$SYSTEM:PCSA_CLAIM_NAME.EXE PCSA claim name utility SYS$SYSTEM:PCX$SERVER.COM Command procedure that starts the PC DECwindows X server SYS$SYSTEM:PWRK$ACLADM.EXE Server configuration tool SYS$SYSTEM:PWRK$BLOBADM.EXE Server configuration tool SYS$SYSTEM:PWRK$CHACL.EXE Server configuration tool SYS$SYSTEM:PWRK$CHDOMAIN.EXE Server configuration tool SYS$SYSTEM:PWRK$CNVTOHFS.EXE ODS-5 filename conversion utility SYS$SYSTEM:PWRK$DELETEACE.EXE File ACE utility SYS$SYSTEM:PWRK$ELFREAD.EXE Event log file reader utility (continued on next page) E-6 Advanced Server Files and On-Disk Structure Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$SYSTEM:PWRK$EVTREPORT.EXE Event logger report generator SYS$SYSTEM:PWRK$GETROLE.EXE Server configuration tool SYS$SYSTEM:PWRK$KNBDAEMON.EXE Kernel NETBIOS daemon process SYS$SYSTEM:PWRK$LICENSE_REGISTRAR.EXELicense Registrar SYS$SYSTEM:PWRK$LICENSE_SERVER.EXE License server SYS$SYSTEM:PWRK$LMECHO.EXE Debugging utility (unsupported) SYS$SYSTEM:PWRK$LMSTAT.EXE Debugging utility (unsupported) SYS$SYSTEM:PWRK$LOADSTREAMS_V7.EXE Loader for streams system loadable image SYS$SYSTEM:PWRK$LR_SHOW_USAGE.EXE[1] License count units utility SYS$SYSTEM:PWRK$LSACL.EXE Debugging utility (unsupported) SYS$SYSTEM:PWRK$MAKEMACH.EXE Server configuration tool SYS$SYSTEM:PWRK$MAPUNAME.EXE Debugging utility (unsupported) SYS$SYSTEM:PWRK$MASTER.EXE Master process and event logger SYS$SYSTEM:PWRK$MONITOR.EXE PATHWORKS Monitor utility SYS$SYSTEM:PWRK$NBDAEMON.EXE NetBIOS daemon process SYS$SYSTEM:PWRK$NBSHOW.EXE[1] NetBEUI show status utility SYS$SYSTEM:PWRK$NETEVENT.EXE Debugging utility (unsupported) SYS$SYSTEM:PWRK$PWMON.EXE[1] Host-based monitor utility SYS$SYSTEM:PWRK$REGUTL.EXE Registry parameter management utility SYS$SYSTEM:PWRK$RMACL.EXE Server configuration tool [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) Advanced Server Files and On-Disk Structure E-7 Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$SYSTEM:PWRK$SAMCHECK.EXE Server configuration tool SYS$SYSTEM:PWRK$SETSHO.EXE Set/Show Parameters utility SYS$SYSTEM:PWRK$SHOWQUOTA.EXE Show Disk Quota utility SYS$SYSTEM:PWRK$SRVCONFIG.EXE Debugging utility (unsupported) SYS$SYSTEM:PWRK$START.EXE Utility that starts detached master process SYS$SYSTEM:PWRK$STARTSVC.EXE Debugging utility (unsupported) SYS$SYSTEM:PWRK$STOP.EXE Utility that stops server processes SYS$SYSTEM:PWRK$VAPFADM.EXE Server configuration tool SYS$SYSTEM:PWRK$VERIFY.EXE Utility that verifies configuration parameters SYS$TEST:PWRK$IVP.COM Installation Verification Procedure (IVP) SYS$TEST:PWRK$IVP.DAT Installation Verification Procedure data file SYS$UPDATE:PWRK$COMMANDS.CLD Server command line definitions SYS$UPDATE:PWRK$COMMON.SAV[2] Backup saveset for the initial server directory tree SYS$UPDATE:PWRK$COMMON_CONFIG.COM Common configuration command procedure SYS$UPDATE:PWRK$CONFIG.COM One-time configuration command procedure SYS$UPDATE:PWRK$DEFINE_FORMS.COM[2] Command procedure that defines printer forms SYS$UPDATE:PWRK$DEINSTAL.COM Advanced Server removal command procedure [2]This_file_is_deleted_after_you_configure_the_server._________ (continued on next page) E-8 Advanced Server Files and On-Disk Structure Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$UPDATE:PWRK$GETPARAM.COM Command procedure that gets a parameter from PWRK.INI SYS$UPDATE:PWRK$INSTALL_COMMANDS.COM Command procedure that installs Advanced Server DCL commands SYS$UPDATE:PWRK$LICENSE_CONFIG.COM License server configura- tion command procedure SYS$UPDATE:PWRK$LICENSE.SAV PATHWORKS client licensing software BACKUP saveset SYS$UPDATE:PWRK$SETINI.COM Command procedure that updates server configuration parameters SYS$UPDATE:PWRK$SETPARAM.COM Command procedure that sets a parameter in PWRK.INI SYS$UPDATE:PWRK$VERSIONS.COM Command procedure that shows server image versions SYS$HELP:PWRK$MANAGER.HLB ADMINISTER commands help library SYS$HELP:PWRK$SHOWINI.HLB[1] Help file for PWRK$SHOWINI.EXE SYS$LIBRARY:PWRK$ACME_MODULE_ External authentication ALPHA.EXE Alpha image SYS$LIBRARY:PWRK$ACME_MODULE_ External authentication VAX VAX.EXE image SYS$LIBRARY:PWRK$CMT_LM.EXE Advanced Server interface to the Configurator, Monitor, and Tuner SYS$LIBRARY:PWRK$LMAPISHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$LMRPCAPISHR.EXE Advanced Server shareable image [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) Advanced Server Files and On-Disk Structure E-9 Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$LIBRARY:PWRK$LMRPCSHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$LMRPCXNPSHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$LMTASKSHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$MGTLIBSHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$NBLIB_DECNET.EXE Advanced Server network interface to DECnet SYS$LIBRARY:PWRK$NBLIB_NETBEUI.EXE Advanced Server network interface to NetBEUI SYS$LIBRARY:PWRK$NBLIB_TCPIP.EXE Advanced Server network interface to TCP/IP SYS$STARTUP:PCSA$MAIL_STARTUP.COM PCSAMAIL command for TCP /IP clients invoking the PATHWORKS mail server SYS$STARTUP:PWRK$ACME_STARTUP.COM External authentication startup file SYS$STARTUP:PWRK$LMBROWSER_ Browser startup file START.COM SYS$STARTUP:PWRK$LMDMN_START.COM Command procedure that runs the Advanced Server daemon SYS$STARTUP:PWRK$LMMCP_START.COM Command procedure that runs the Advanced Server controller SYS$STARTUP:PWRK$LMSRV_START.COM Command procedure that runs the Advanced Server SYS$STARTUP:PWRK$PCSA_SHUTDOWN.COM PATHWORKS for VMS V4.x shutdown command procedure SYS$SYSTEM:PWRK$ADMIN.COM Remote Net Admin command procedure (continued on next page) E-10 Advanced Server Files and On-Disk Structure Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$SYSTEM:PWRK$ADMIN_CFG.EXE Configuration Manager utility SYS$SYSTEM:PWRK$ADMIN_LIC.EXE License Manager utility SYS$SYSTEM:PWRK$BANNER.EXE Utility that collects system information and inserts it at top of log files SYS$SYSTEM:PWRK$CHGROUP.EXE[1] Standalone utility that manages the Advanced Server groups database SYS$SYSTEM:PWRK$CHUSER.EXE[1] Standalone utility that manages the Advanced Server user accounts database SYS$SYSTEM:PWRK$LMBROWSER.EXE Advanced Server browser image SYS$SYSTEM:PWRK$LMDMN.EXE Advanced Server daemon SYS$SYSTEM:PWRK$LMMCP.EXE Advanced Server controller SYS$SYSTEM:PWRK$LMSHARE.EXE[1] Standalone utility that manages the Advanced Server shares database SYS$SYSTEM:PWRK$LMSRV.EXE Advanced Server executable SYS$SYSTEM:PWRK$MANAGER.EXE ADMIN utility SYS$SYSTEM:PWRK$MODAL.EXE[1] Standalone utility that manages the Advanced Server modals database SYS$SYSTEM:PWRK$SHOWINI.EXE[1] Utility that displays server configuration parameters SYS$SYSTEM:PWRK$START_PRINTERS.EXE Utility that starts printer queues and printer destinations [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) Advanced Server Files and On-Disk Structure E-11 Advanced Server Files and On-Disk Structure E.1 Advanced Server Files Table_E-1_(Cont.)_Files_Installed_for_the_Advanced_Server_______ File_________________________________Description________________ SYS$UPDATE:PWRK$LANMAN.SAV[2] BACKUP saveset for the initial Advanced Server directory tree SYS$UPDATE:PWRK$LMCONFIG.COM Command procedure that sets up the initial Advanced Server directory tree SYS$UPDATE:PWRK$MIGRATE_INI.COM Command procedure that migrates LANMAN.INI parameters to the OpenVMS Registry SYS$UPDATE:PWRK$PWUTIL.SAV[2] BACKUP saveset for PATHWORKS client-based utilities [2]This_file_is_deleted_after_you_configure_the_server._________ ________________________________________________________________ E-12 Advanced Server Files and On-Disk Structure Advanced Server Files and On-Disk Structure E.2 Advanced Server On-Disk Structure E.2 Advanced Server On-Disk Structure Figure E-1 shows the Advanced Server on-disk structure. Note that only part of the substructure is shown. Figure E-1 On-Disk Structure Diagram pwrk$commonroot, pwrk$lmroot | |___datafiles | |___lanman | | ---.accounts | ---.datafiles | ---.debug | ---.domains | ---.logs | ---.repl | ---.samsave | ---.shares | ---.upgrade | |___license | |___logs | |___params | |___perfdata | |___print | |___section | |___spool | |___temp Advanced Server Files and On-Disk Structure E-13 F ________________________________________________________________ Advanced Server Logical Names Table F-1 describes the logical names that are created when you configure and start the Advanced Server. Table_F-1_Advanced_Server_Logical_Names_________________________ Logical_Name_______________Description__________________________ NETBIOS$DEVICE[2] DECnet device PWRK$ADDON_LIBRARY Location of file system shareable images PWRK$COMMON Top-level directory for Advanced Server PWRK$COMMONROOT[1] Root of the Advanced Server common directory tree PWRK$DATAFILES Character code page translation mapping data PWRK$KNBDAEMON_DEVICE[2] TCP/IP device PWRK$LANMAN Advanced Server area PWRK$LICENSE License area PWRK$LMDATAFILES Advanced Server data files area PWRK$LMDEBUG Area where trace files are written PWRK$LMDOMAINS Advanced Server domain database area PWRK$LMLOGS Advanced Server log file area [1]This_logical_name_requires_that_you_specify_the_directory____ with it. [2]This logical name is not defined during installation. It is used to define network adapters under certain circumstances. For more information, refer to Section 3.8, Selecting the Advanced Server Network Device. (continued on next page) Advanced Server Logical Names F-1 Advanced Server Logical Names Table_F-1_(Cont.)_Advanced_Server_Logical_Names_________________ Logical_Name_______________Description__________________________ PWRK$LMROOT[1] Root of the Advanced Server directory tree PWRK$LMMSGFILES Advanced Server message files PWRK$LMUPGRADE Advanced Server upgrade area PWRK$LOADSTREAMS Logical for LoadStreams image PWRK$LOGS Common log file area PWRK$NETBEUI_DEVICE[2] NetBEUI device PWRK$PARAMS Parameter area PWRK$PERFDATA Advanced Server monitor performance data directory PWRK$PRINT Advanced Server printer database directory PWRK$SAMSAVE SAMCHECK data area PWRK$SAMSAVEX SAMCHECK data area PWRK$SECTION Section file area PWRK$SPOOL Spool area PWRK$TEMP Advanced Server temporary area PWRK$VERSION Advanced Server version [1]This_logical_name_requires_that_you_specify_the_directory____ with it. [2]This logical name is not defined during installation. It is used to define network adapters under certain circumstances. For more information, refer to Section 3.8, Selecting the Advanced Server Network Device. ________________________________________________________________ F-2 Advanced Server Logical Names ________________________________________________________________ Index A__________________________ C__________________________ Administrator account Checklist for installation, setting password, 3-10 A-1 Advanced Server Client-based server cluster alias, 3-9 administration tools, files, E-1 5-13 logical names, F-1 Client software, 1-9 on-disk structure, E-13 sample deinstallation Clusters procedure, 7-4 See OpenVMS clusters sample installation and Computer name, 3-9 configuration, B-1 SCSNODE parameter and, starting, 5-2 1-15 starting during Configuration Manager, configuration, 3-10 1-12 startup, 5-3 Configuration procedure stopping, 5-7 Advanced Server, 3-1 Advanced Server disk disk space required, 3-5 changing the, 3-6 logical names created, Alerter service F-1 description of, 3-8 preparing for the Advanced Server, 3-5 B__________________________ prerequisites, 3-5 BACKUP command, 1-12 responding to prompts, Backup domain controllers 3-11, 4-3 configuring, 3-6 sample script for standalone license server, C-1, C-3 starting, 3-10 starting server during, 3-10, 3-14, 4-5 Index-1 Configuration settings Domain name changing, 3-14 term defined, 3-8 Configuring backup domain controllers E__________________________ , 3-6 External authentication wide area networks, 3-6 setting up, 5-7 Converting file names to External authentication ODS-5, 5-9 software Convert Utility, 5-10 installing, 2-13 D sample installation, D-1 ___________________________ separate installation, Data loss 2-4 preventing, 1-12 DECnet G__________________________ checking, 1-17 GBLPAGES parameter starting, 1-18 checking and defining, DECnet-Plus 1-13 checking, 1-18 GBLSECTIONS parameter starting, 1-18 checking and defining, DECnet transport, 1-8 1-14 checking status, 1-17 running during configuration, 1-17 H__________________________ DECprint Supervisor Hardware requirements, software, 1-4 1-8, 1-11 installing, 1-4 Default answers I__________________________ for installation Installation procedure, 2-6 checklist, A-1 Deinstallation procedure, Installation kit 7-2 contents of, 2-2 guidelines for, 7-1 Installation procedure Deinstalling description of, 2-1 Advanced Server for external authentication, OpenVMS, 7-3 D-1 Device name, 2-3 external authentication Disk space software, 2-13 determining, 1-13 files installed, E-1 requirement for interrupting, 2-6 configuration, 3-5 prerequisites, 2-3 Disk space requirements, questions in, 2-6 1-13 responding to prompts, 2-7 Index-2 Installation procedure Licensing requirements, (cont'd) 1-4 sample script for LMHOSTS Advanced Server, B-1 configuring to use, 6-5 sample script for transport configuration, standalone license 3-7 server, C-1 LMHOSTS name resolution, standalone license server 3-7 , 4-1 Logical names starting, 2-5 Advanced Server, F-1 Installation requirements startup procedure, 5-3 disk space, 1-13 M hardware, 1-8, 1-11 ___________________________ licensing, 1-4 Memory requirements, 1-9 memory, 1-9 Migrating software, 1-8, 1-11 LANMAN.INI parameters, Installation Verification 1-3 Procedure to Advanced Server, 1-2 See IVP IVP N__________________________ running after NetBIOS name resolution installation, 5-2 using LMHOSTS, 6-2 running automatically, using WINS, 6-5 2-10 Netlogon service, 3-8 Network transport K__________________________ requirements, 1-8 Kit contents O checking, 1-10 ___________________________ On-disk structure, E-13 L__________________________ OpenVMS clusters LANMAN.INI parameters checking configuration, migrating to OpenVMS 1-10 Registry, 3-4 cluster alias, 3-9, 3-17 LanmanIniMigrated parameter configuring nodes in, , 3-4 3-3, 3-17 License server, 3-7 disk device for Advanced configuration procedure, Server files, 3-5 4-1 installation in, 1-19, installation procedure, 3-10 4-1 loading client license standalone installation, PAKs on, 4-2 2-3, 2-13 loading PAKs on, 1-5 Index-3 OpenVMS clusters (cont'd) Product identifier, 2-3 running license server PWCONVERT command, 5-10 on, 1-5, 4-1 PWRK$CONFIG procedure sample standalone license See Configuration server installation and procedure configuration, C-1 PWRK$DEINSTAL procedure server role in, 3-9 See Deinstallation starting server in, 4-6, procedure 5-4 PWRK$REGUTL utility, 1-12, upgrading to Advanced 3-5 Server for OpenVMS, PWRK$STARTUP.COM 1-3 See Startup procedure WINS server setup for, 6-5 Q OpenVMS Registry, 3-4 ___________________________ removing server Queue manager parameters, 7-2 running during starting the, 1-11 configuration, 1-16 OpenVMS Registry Server, starting, 1-16 1-3 OpenVMS VAX systems, 2-12 R__________________________ Operating system Registry requirements, 1-8 See OpenVMS Registry Optional software, 5-13 Release notes, 1-7 P displaying, 2-7 ___________________________ printing, 1-7 Parameters Removing LanmanIniMigrated, 3-4 Advanced Server, 7-1 migrating, 3-4 server configuration removing, 7-2 parameters, 7-2 Part listing checking, 1-10 S__________________________ PATHWORKS Advanced Servers SCSNODE parameter installing on, 2-12 defining, 1-15 upgrading, 1-2 Server Postinstallation tasks, starting during 5-1 configuration, 3-14, Pre-installation tasks, 4-5 1-10, 2-3 Server administration tools checklist for, 1-9 installing, 5-13 PROCSECTCNT parameter checking and defining, 1-14 Index-4 Server announce comment, System parameters 3-9 checking and defining, SHOW QUEUE/MANAGER command, 1-13 1-16 Shutdown procedure, 5-7 T__________________________ Software requirements, TCP/IP, 1-8 1-8, 1-11 checking status, 1-18 Standalone license server, starting, 1-18 1-5, 4-1 TDF sample installation and See Time differential configuration procedure factor , C-1 Time differential factor startup, 4-5 setting, 1-17 Starting Timesource service Advanced Server, 5-2 description of, 3-8 Advanced Server during Time zone setting configuration, 3-10 changing, 1-17 DECnet, 1-18 checking, 1-16 license server Transports automatically, 4-6 for LMHOSTS, 3-7 license server manually, for WINS, 3-6 4-6 selecting, 3-6 OpenVMS Registry, 1-11 standalone license server U , 4-5 ___________________________ TCP/IP, 1-18 Upgrading START/QUEUE/MANAGER command file servers, 1-2 , 1-16 OpenVMS clusters, 1-3 Startup PATHWORKS Advanced Advanced Server, 5-3 Servers, 1-2 automatic, 5-4 in OpenVMS clusters, 5-4 V__________________________ manual, 5-3 VMSINSTAL procedure, 5-3 description of, 2-1 troubleshooting, 5-5 kit contents, 2-2 using the SYSMAN utility, VMSINSTAL procedure 5-5 See Installation SYSTEM account procedure logging in to, 1-12 System backup, 1-12 System disk space needed for installation, 1-13 Index-5 installing, 5-13 W__________________________ WINS Wide area domain, 6-1 configuring to use, 6-5 Wide area networking setup, 6-5 providing, 3-6 setup for OpenVMS Windows NT server clusters, 6-5 administration tools, transport configuration, 5-13 3-6 Index-6