PATHWORKS_for_OpenVMS_________________________ Server Installation and Configuration Guide Order Number: AA-R6G1B-TE January 1999 This guide explains how to install and configure the components of PATHWORKS for OpenVMS software, including the PATHWORKS Advanced Server and the standalone license server. Revision/Update Information: This guide supersedes the DIGITAL Advanced Server for OpenVMS Server Installation and Configuration Guide, AA-R6G1A-TE. Operating System: OpenVMS Alpha Version 7.1 OpenVMS VAX Version 7.1 OpenVMS Alpha Version 7.2 OpenVMS VAX Version 7.2 Software Version: PATHWORKS V6.0B for OpenVMS (Advanced Server) Compaq Computer Corporation Houston, Texas __________________________________________________________ First Printing, May 1988 Revised, 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 community. © Compaq Computer Corporation 1998, 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. All other trademarks and registered trademarks are the property of their respective holders. ZK6555 The PATHWORKS for OpenVMS (Advanced Server) documentation set is available on CD-ROM. ________________________________________________________________ Contents Preface.................................................. ix 1 Before You Install PATHWORKS Advanced Server 1.1 About the Advanced Server for OpenVMS Software Kit............................................. 1-1 1.1.1 About the PATHWORKS for OpenVMS (NetWare) Server........................................ 1-2 1.2 If You Are Upgrading from PATHWORKS V5 for OpenVMS (LAN Manager)........................... 1-2 1.3 Installing DECprint Software.................... 1-2 1.4 About Licensing................................. 1-3 1.4.1 License Requirements ......................... 1-3 1.4.2 About the License Server ..................... 1-4 1.5 About External Authentication................... 1-5 1.6 Reading the Release Notes....................... 1-6 1.6.1 How to Access the Release Notes .............. 1-6 1.7 Using the Installation Checklist................ 1-7 1.8 Requirements for Installing PATHWORKS Advanced Server Software................................. 1-7 1.8.1 Hardware Requirements ........................ 1-7 1.8.2 Software Requirements ........................ 1-8 1.8.3 Client Software .............................. 1-8 1.8.4 Memory Requirements .......................... 1-8 1.9 Pre-installation Tasks.......................... 1-8 1.9.1 Step 1: Check the Part Listing ............... 1-10 1.9.2 Step 2: Check the Network Hardware ........... 1-10 1.9.3 Step 3: Check the Required Software .......... 1-10 1.9.4 Step 4: Log In to the SYSTEM Account ......... 1-10 1.9.5 Step 5: Back Up the System ................... 1-11 1.9.6 Step 6: Print and Read the Release Notes ..... 1-11 1.9.7 Step 7: Check Disk Space Requirements ........ 1-11 iii 1.9.8 Step 8: Check System Parameters .............. 1-12 1.9.9 Step 9: Check the Queue Manager .............. 1-16 1.9.10 Step 10: Check Time Zone and TDF ............. 1-16 1.9.11 Step 11: Check DECnet Status ................. 1-17 1.9.11.1 Checking DECnet (Phase IV) Status.......... 1-17 1.9.11.2 Checking DECnet-Plus Status................ 1-17 1.9.12 Step 12: Check TCP/IP Status ................. 1-18 1.9.13 Step 13: Check OpenVMS Cluster Configuration................................. 1-19 1.10 Next Step....................................... 1-20 2 Installing the PATHWORKS Advanced Server 2.1 About the Installation Procedure................ 2-1 2.1.1 What is VMSINSTAL? ........................... 2-1 2.1.2 PATHWORKS Advanced Server 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-7 2.2.5 How to Answer Installation Questions ......... 2-7 2.3 Troubleshooting Installation Problems........... 2-18 2.3.1 Installing the PATHWORKS Advanced Server on a System with the NetWare Server................ 2-18 2.3.2 Installing PATHWORKS Advanced Server on a System with PATHWORKS V5 for OpenVMS (LAN Manager)...................................... 2-19 2.3.3 Installing the Standalone License Server on a System Where the PATHWORKS Advanced Server Has Been Installed................................ 2-19 2.3.4 Installing the External Authentication Software...................................... 2-20 2.4 Next Steps...................................... 2-20 iv 3 Configuring the PATHWORKS Advanced Server 3.1 About the PATHWORKS Advanced Server Configuration Procedure......................... 3-1 3.1.1 What Is the Configuration Procedure? ......... 3-2 3.1.2 What the Configuration Procedure Does ........ 3-2 3.2 Before You Start the PATHWORKS Advanced Server Configuration Procedure......................... 3-3 3.3 How to Start the PATHWORKS Advanced Server Configuration Procedure......................... 3-8 3.4 How to Respond to PATHWORKS Advanced Server Configuration Prompts........................... 3-8 3.5 How to Change Default Configuration Settings.... 3-13 3.6 Troubleshooting Configuration Procedure Problems........................................ 3-15 3.6.1 Ensuring Sufficient Resources to Support Clients....................................... 3-15 3.7 Selecting the PATHWORKS Advanced Server Network Device.......................................... 3-16 3.8 Defining Communications Devices................. 3-17 3.9 Next Steps...................................... 3-19 4 Configuring and Starting the Standalone License Server 4.1 About the License Server........................ 4-1 4.2 Before You Begin to Configure the Standalone License Server.................................. 4-2 4.3 Configuring the Standalone License Server....... 4-3 4.4 Configuring the Transports...................... 4-4 4.5 How to Respond to Configuration Prompts......... 4-4 4.6 How to Start the Standalone License Server...... 4-6 4.6.1 How to Start the License Server Manually ..... 4-7 4.6.2 How to Start the License Server Automatically................................. 4-7 4.6.3 How to Start the License Server in an OpenVMS Cluster....................................... 4-7 v 5 After You Install the PATHWORKS Advanced Server 5.1 Before You Begin Post-installation Tasks........ 5-1 5.2 Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation............................ 5-3 5.3 Starting the PATHWORKS Advanced Server.......... 5-3 5.3.1 When to Start the PATHWORKS Advanced Server .. 5-4 5.3.2 What the Startup Procedure Does .............. 5-4 5.3.3 Troubleshooting the Startup .................. 5-4 5.3.4 Starting the File Server ..................... 5-5 5.3.5 How to Start the PATHWORKS Advanced Server Manually...................................... 5-5 5.3.6 How to Define PATHWORKS Advanced Server Commands When You Log In...................... 5-5 5.3.7 How to Start the PATHWORKS Advanced Server Automatically................................. 5-6 5.3.8 How to Start the PATHWORKS Advanced Server in an OpenVMS Cluster............................ 5-6 5.4 Stopping the PATHWORKS Advanced Server.......... 5-7 5.4.1 When to Stop the PATHWORKS Advanced Server ... 5-7 5.4.2 How to Stop the PATHWORKS Advanced Server .... 5-7 5.4.3 How to Stop the PATHWORKS Advanced Server on System Shutdown............................... 5-7 5.5 Setting Up External Authentication.............. 5-8 5.5.1 Setting Up External Authentication in OpenVMS Clusters...................................... 5-9 5.5.2 Enabling External Authentication over a Network....................................... 5-10 5.5.3 Configuring Externally Authenticated Client Connections................................... 5-11 5.6 Installing Optional Server Administration Tools........................................... 5-11 6 Implementing a Wide Area Network 6.1 Enabling Wide Area Networking................... 6-1 6.2 Using the LMHOSTS File for Wide Area Networking...................................... 6-2 6.2.1 Setting up a TCP/IP Wide Area Network ........ 6-2 6.2.2 Enabling LMHOSTS Name Resolution ............. 6-2 6.2.3 The LMHOSTS Directory ........................ 6-3 6.2.4 LMHOSTS File Syntax .......................... 6-3 6.2.5 Managing the LMHOSTS File .................... 6-4 vi 6.2.6 Using the LMHOSTS Log File ................... 6-5 6.3 Using WINS in a Wide Area Network............... 6-5 6.3.1 Setting up WINS Support for OpenVMS Clusters...................................... 6-5 7 Removing PATHWORKS Advanced Server Software 7.1 Removing the PATHWORKS Advanced Server.......... 7-1 7.1.1 About the PATHWORKS Advanced Server Deinstallation Command Procedure.............. 7-2 7.1.2 Using the PATHWORKS Advanced Server Deinstallation Procedure...................... 7-2 7.1.3 Sample PATHWORKS Advanced Server Removal Procedure..................................... 7-3 7.2 Removing the PATHWORKS NetWare Server........... 7-4 7.2.1 Sample NetWare Server Removal Procedure ...... 7-5 A Installation and Upgrade Checklist B Sample PATHWORKS Advanced Server Installation and Configuration Procedure B.1 Sample PATHWORKS Advanced Server Installation Procedure....................................... B-1 B.2 Sample PATHWORKS Advanced Server Configuration Procedure....................................... B-5 C Sample Standalone License Server Installation and Configuration Procedure C.1 Sample Standalone License Server Installation Procedure....................................... C-1 C.2 Sample Standalone License Server Configuration Procedure....................................... C-3 vii D Upgrade Utility Installation D.1 Installing the Upgrade Utility.................. D-1 D.2 Sample Upgrade Utility Installation Procedure... D-2 E Sample External Authentication Installation Procedure E.1 Sample External Authentication Software Installation Procedure.......................... E-1 F PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files................. F-1 F.2 PATHWORKS Advanced Server On-Disk Structure..... F-13 G PATHWORKS Advanced Server Logical Names Index Figures F-1 PATHWORKS Advanced Server On-Disk Structure Diagram....................................... F-14 Tables 1-1 Pre-installation Checklist ................... 1-9 1-2 GBLPAGES Parameter Minimum Value ............. 1-12 1-3 GBLSECTIONS Parameter Minimum Value .......... 1-13 1-4 PROCSECTCNT Parameter Minimum Value .......... 1-14 2-1 Installation Questions ....................... 2-7 3-1 PATHWORKS Advanced Server Configuration Prompts....................................... 3-9 3-2 Configuration Settings ....................... 3-14 3-3 OpenVMS Network Device Logicals .............. 3-16 3-4 Undefined Device Messages .................... 3-18 4-1 Standalone License Server Configuration Prompts....................................... 4-5 5-1 Have You Done . . . ........................... 5-2 7-1 PWRK$DEINSTAL Prompts ........................ 7-3 viii 7-2 PWVN$DEINSTAL Prompts ........................ 7-5 A-1 Installation and Upgrade Checklist ........... A-1 F-1 Files Installed for the PATHWORKS Advanced Server........................................ F-1 G-1 PATHWORKS Advanced Server Logical Names ...... G-1 ix ________________________________________________________________ Preface This guide explains how to install and configure the following PATHWORKS servers: o PATHWORKS for OpenVMS (Advanced Server) file server o PATHWORKS standalone license server o Upgrade utility only o External Authentication software only Intended Audience This guide is written for the network server administra- tor. The administrator is assumed to be 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 the administrator is familiar with the networking concepts for the PATHWORKS Advanced Server. Document Structure The following list can help you find information in this guide: ix __________________________________________________________ Chapter_____Description___________________________________ Chapter 1 Describes prerequisites for the installation procedure. Chapter 2 Describes the installation procedure. Chapter 3 Describes the configuration procedure for the PATHWORKS 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 the PATHWORKS Advanced Server from your system. Appendix A Provides a checklist of installation and configuration tasks. You can photocopy Appendix A, Installation and Upgrade Checklist, and use it as a checklist as you read this guide. Appendix B Shows a sample installation and configuration procedure for the PATHWORKS 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 Upgrade utility. Appendix E Shows a sample installation procedure for external authentication software only Appendix F Lists the files that are installed with PATHWORKS Advanced Server and shows the on- disk structure. Appendix G Lists the logical names created for the ____________PATHWORKS_Advanced_Server.____________________ x Related Documents The following manuals provide more information about topics discussed in this guide: __________________________________________________________ Document______________Description_________________________ PATHWORKS for Explains how to upgrade a PATHWORKS OpenVMS (Advanced V5 for OpenVMS (LAN Manager) Server) Server server to PATHWORKS V6 for OpenVMS Migration Guide (Advanced Server). Advanced Server for Provides an overview of and OpenVMS Concepts and introduction to the PATHWORKS Planning Guide Advanced Server software and associated networking concepts for system administrators and operators. PATHWORKS for Explains how to manage and customize OpenVMS (Advanced the PATHWORKS Advanced Server Server) 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 PATHWORKS Managing Advanced for OpenVMS (Advanced Server) Server_Licenses_______licenses.___________________________ The following table lists related OpenVMS documents. xi __________________________________________________________ OpenVMS_Document___________Description____________________ OpenVMS Alpha V7.1 Describes how to install the Upgrade and Installation OpenVMS Alpha V7.1 system Manual software. OpenVMS Alpha V7.2 Describes how to install the Upgrade and Installation OpenVMS Alpha V7.2 system Manual software. OpenVMS VAX V7.1 Upgrade Describes how to install and Installation Manual the OpenVMS VAX V7.1 system software. OpenVMS VAX V7.2 Upgrade Describes how to install and Installation Manual the OpenVMS VAX V7.2 system software. OpenVMS System Manager's A task-oriented guide to Manual managing an OpenVMS system. 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 V7.1 New Features Describes the new features of Manual OpenVMS Version 7.1, including procedures for enabling external authentication. OpenVMS V7.2 Guide to Describes the system security System Security features of OpenVMS Version 7.2, including procedures for enabling external ___________________________authentication.________________ 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 xii 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 PATHWORKS Advanced Server documentation set. __________________________________________________________ Convention____Meaning_____________________________________ "PATHWORKS Refers to the PATHWORKS for OpenVMS Advanced (Advanced Server) file and print server. Server" DECnet Applies to both DECnet Phase IV and DECnet- Plus, unless otherwise specified. While you hold down the Ctrl key, press another key or a pointing device button. Indicates a place to press the Return (or Enter) key. 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. xiii __________________________________________________________ Convention____Meaning_____________________________________ monospace Indicates the actual commands, words, or characters that you type in a dialog box or at a command prompt or system output. 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 forward slash in command descriptions indicates that a command qualifier follows. . . . 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 PATHWORKS Advanced Server This chapter describes the hardware and software you must have and the tasks you need to complete before you install PATHWORKS Advanced Server software. This chapter consists of the following sections: o Section 1.1, About the Advanced Server for OpenVMS Software Kit o Section 1.2, If You Are Upgrading from PATHWORKS V5 for OpenVMS (LAN Manager) o Section 1.3, Installing DECprint Software o Section 1.4, About Licensing o Section 1.5, About External Authentication o Section 1.6, Reading the Release Notes o Section 1.7, Using the Installation Checklist o Section 1.8, Requirements for Installing PATHWORKS Advanced Server Software o Section 1.9, Pre-installation Tasks o Section 1.10, Next Step 1.1 About the Advanced Server for OpenVMS Software Kit The PATHWORKS for OpenVMS (Advanced Server) kit contains the software required to run the following server software: o PATHWORKS Advanced Server file server o PATHWORKS standalone license server Before You Install PATHWORKS Advanced Server 1-1 Before You Install PATHWORKS Advanced Server 1.1 About the Advanced Server for OpenVMS Software Kit In addition, the kit includes an Upgrade utility that helps you to migrate from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6 for OpenVMS (Advanced Server). The Upgrade utility may be installed separately. The installation procedure also allows you to install only External Authentication software. 1.1.1 About the PATHWORKS for OpenVMS (NetWare) Server The PATHWORKS for OpenVMS (NetWare) server is no longer supported. PATHWORKS for OpenVMS (Advanced Server) cannot be installed on a system where the PATHWORKS for OpenVMS (NetWare) server is installed. If the installation procedure finds the PATHWORKS for OpenVMS (NetWare) server, it optionally invokes the PATHWORKS for OpenVMS (NetWare) removal procedure (PWVN$DEINSTAL), to remove the NetWare server software before installing the PATHWORKS Advanced Server software. For more information about the NetWare server removal procedure, refer to Section 7.2, Removing the PATHWORKS NetWare Server. If your clients continue to depend on NetWare software to connect to the system, or if you need the IPX/SPX transport for any reason, you should designate a system to run the PATHWORKS for OpenVMS (NetWare) server. 1.2 If You Are Upgrading from PATHWORKS V5 for OpenVMS (LAN Manager) If you have PATHWORKS V5 for OpenVMS (LAN Manager) installed, you must install the new PATHWORKS Advanced Server. You can choose to install just the Upgrade utility initially, and install the PATHWORKS Advanced Server later. See the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for more information. 1.3 Installing DECprint Software DECprint Supervisor for OpenVMS is a printing system that provides queue management and printing features for PostScript printers. 1-2 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.3 Installing DECprint Software If you plan to use DECprint Supervisor for OpenVMS on your system, Compaq Computer Corporation recommends that you install it before installing PATHWORKS 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 PATHWORKS Advanced Server. However, DECprint Supervisor software must be installed before you configure and start PATHWORKS Advanced Server. 1.4 About Licensing The following sections describe the way the PATHWORKS Advanced Server software is licensed, and how to ensure clients accessing the server are properly licensed. 1.4.1 License Requirements The PATHWORKS 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 a PATHWORKS Advanced Server. o The PATHWORKS Advanced Server must have a server-based license available to assign to an unlicensed client attempting to use services of the PATHWORKS Advanced Server. In either case, the license required to access PATHWORKS Advanced Server services is the PATHWORKS Client-Access license: PWLMXXXCA06.00. If you are upgrading from PATHWORKS LAN Manager, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for information about upgrading client license requests. Before You Install PATHWORKS Advanced Server 1-3 Before You Install PATHWORKS Advanced Server 1.4 About Licensing 1.4.2 About the License Server The PATHWORKS license server is a 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 network protocols: o DECnet o LAN Manager (NetBEUI) o TCP/IP Compaq Computer Corporation recommends that you install the license server on a designated OpenVMS system without the PATHWORKS file server. Therefore, the PATHWORKS for OpenVMS (Advanced Server) software 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 PATHWORKS file servers, where cluster failover provides reliability. Each LAN needs only one active PATHWORKS license server. (The same license server can support both PATHWORKS LAN Manager and PATHWORKS Advanced Server clients.) The license product authorization keys (PAKs) must be loaded on the system that runs the PATHWORKS license server. In an OpenVMS cluster, the PAKs must be loaded into a shared license database. 1-4 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.4 About Licensing __________________________________________________________ For more information about_._._.___________Refer_to_._._.______________________ Loading licenses OpenVMS License Management Utility Manual Managing PATHWORKS Advanced Server for OpenVMS Guide to Advanced Server Managing Advanced Server Licenses licenses__________________________________________________ 1.5 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 PATHWORKS Advanced Server takes advantage of this feature by providing the ability to use the PATHWORKS 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 PATHWORKS Advanced Server user name and password. In addition, it provides automatic password synchronization for user accounts. When you install PATHWORKS Advanced Server, the files required to support external authentication are automati- cally included in the installation process. If you want to enable external authentication on a different node in an OpenVMS cluster), you may choose to install the External Authentication software only. For more information about enabling external authen- tication, refer to Section 5.5, Setting Up External Authentication. Before You Install PATHWORKS Advanced Server 1-5 Before You Install PATHWORKS Advanced Server 1.6 Reading the Release Notes 1.6 Reading the Release Notes The PATHWORKS Advanced Server installation kit includes the PATHWORKS for OpenVMS (Advanced Server) Release Notes. Compaq Computer Corporation recommends that you print and read the appropriate release notes before starting the installation. ________________________Note ________________________ The installation procedure copies the release notes into the SYS$HELP: area, where they are available after server installation. _____________________________________________________ 1.6.1 How to Access the Release Notes Use the following table to decide how to print the release notes: ________________________________________________________________ If you want to_._._.______Then_._._.________________________________________ Print the Do the following: release 1. Load the installation kit on a drive. notes before the 2. Enter the following commands, replacing device installation with the name of the device (and if the device is a disk, also designate the directory) where you loaded the installation kit: $ MOUNT device: PWRK $ BACKUP/SELECT=PWRKV60B060.RELEASE_NOTES device:PWRKV60B060.A/SAVE_SET * $ PRINT PWRKV60B060.RELEASE_NOTES 1-6 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.6 Reading the Release Notes ________________________________________________________________ If you want to_._._.______Then_._._.________________________________________ Print the Do the following: release 1. Load the installation kit on a drive. notes during the 2. Enter the following command to start the installation installation procedure: $ @VMSINSTAL PWRKV60B060 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.7 Using the Installation Checklist Appendix A, Installation and Upgrade Checklist, provides an installation and configuration summary checklist. You can photocopy the summary checklist and use it to track the completion of the installation and configuration tasks described in this guide. 1.8 Requirements for Installing PATHWORKS Advanced Server Software The following sections describe the hardware and software that may be required to install PATHWORKS Advanced Server on the system. 1.8.1 Hardware Requirements Make sure that the network (including cables, PCs, servers, and other hardware) is connected. For a list of the hardware that the server supports, refer to the Software Product Description (SPD). Before You Install PATHWORKS Advanced Server 1-7 Before You Install PATHWORKS Advanced Server 1.8 Requirements for Installing PATHWORKS Advanced Server Software 1.8.2 Software Requirements To install PATHWORKS Advanced Server successfully, you must have the following software properly installed and configured on your system: o OpenVMS V7.1 or V7.2 o DECnet or DECnet-Plus (optional) DECnet can be installed automatically with the OpenVMS operating system. o TCP/IP (optional) TCP/IP Services for OpenVMS and a selection of third- party TCP/IP products on OpenVMS can be used to provide TCP/IP support. 1.8.3 Client Software PATHWORKS Advanced Server supports connections from the following types of clients: o Windows NT o Windows 95 o Windows 98 o Windows for Workgroups o PATHWORKS for DOS and Windows o PATHWORKS for Windows 95 o PATHWORKS 32 1.8.4 Memory Requirements The system must have at least 64 MB of physical memory to run the PATHWORKS Advanced Server. 1.9 Pre-installation Tasks Use the following checklist to make sure you have completed all the tasks you should perform before you install the software. Each task is described later in this section. 1-8 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.9 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. Log in to the SYSTEM account. < >5. Back up the system disks. < >6. Read the release notes. < >7. Make sure that you have adequate disk space for installation. < >8. Check system parameters. < >9. Check the queue manager. < >10. Check the time zone configuration. < >11. Make sure that DECnet is running, if you are planning to use the DECnet transport. < >12. Make sure that TCP/IP is running, if you are planning to use the TCP/IP transport. < >13. Check the OpenVMS cluster configuration, if you are installing PATHWORKS Advanced Server on a __________cluster.________________________________________ Before You Install PATHWORKS Advanced Server 1-9 Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks Before you install PATHWORKS Advanced Server, perform these tasks: 1.9.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 Computer Corporation representative. 1.9.2 Step 2: Check the Network Hardware PATHWORKS Advanced Server runs on OpenVMS 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.9.3 Step 3: Check the Required Software PATHWORKS Advanced Server requires the following: o OpenVMS operating system, Version 7.1 or Version 7.2. o DECnet or DECnet-Plus, if you are going to use the DECnet transport, the mail server, or the license server over DECnet. o A TCP/IP product, if you are going to use the TCP/IP transport. Supported TCP/IP products are described in the PATHWORKS for OpenVMS (Advanced Server) Release Notes. 1.9.4 Step 4: Log In to the SYSTEM Account Before you install PATHWORKS Advanced Server, log in to the SYSTEM account, which has sufficient privileges to run the installation procedure. To log in to the SYSTEM account: 1. At the Username: prompt, enter SYSTEM: Username: SYSTEM 1-10 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks 2. At the Password: prompt, enter the password to the SYSTEM account. The password you enter is not displayed. 1.9.5 Step 5: Back Up the System To safeguard against the loss of valuable data, Compaq Computer Corporation 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.9.6 Step 6: Print and Read the Release Notes If you have not already read the release notes, you should do so before installing the software. See Section 1.6, Reading the Release Notes, for more information. 1.9.7 Step 7: Check Disk Space Requirements On your OpenVMS system, the following amount of free disk space on the system disk is required during the installation procedure. ________________________________________________________________ You need this number of blocks You need this number To install these on an Alpha of blocks on a VAX components_._._.______system_._._._______system_._._.___________ PATHWORKS Advanced 144,500[1] 125,000[1] Server Standalone license 144,500 125,000 server Upgrade utility only 30,000 25,500 External authen- 144,500 125,000 tication images only [1]The_disk_space_requirements_shown_include_provision_for_the__ integrated_license_server.______________________________________ To check the number of free blocks on the system disk, enter: Before You Install PATHWORKS Advanced Server 1-11 Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks $ SHOW DEVICE SYS$SYSDEVICE Result 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 AXPVMSSYS 1724856 280 1 1.9.8 Step 8: 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. _____________________________________________________ GBLPAGES parameter The minimum value of this parameter is listed in Table 1-2, GBLPAGES Parameter Minimum Value. Table_1-2_GBLPAGES_Parameter_Minimum_Value________________ For a VAX system, the value must be at For an Alpha system, the value least_._._.________________must_be_at_least_._._._________ 3500_pages_________________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 1-12 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks 2. If the value is less than required, edit the file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following: ADD_GBLPAGES = 7500 GBLSECTIONS parameter The minimum value of this parameter differs depending on which server is to be installed, as described in Table 1-3, GBLSECTIONS Parameter Minimum Value. Table_1-3_GBLSECTIONS_Parameter_Minimum_Value_____________ For the standalone license server only, If the PATHWORKS Advanced the value must be at Server is to be installed, the least_._._.________________value_must_be_at_least_._._.___ 50_________________________75_____________________________ 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 file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following: ADD_GBLSECTIONS = 75 PROCSECTCNT parameter The minimum value of this parameter differs depending on which server is to be installed, as described in Table 1-4, PROCSECTCNT Parameter Minimum Value. Before You Install PATHWORKS Advanced Server 1-13 Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks Table_1-4_PROCSECTCNT_Parameter_Minimum_Value_____________ For the standalone license server only If the PATHWORKS Advanced the value must be at Server is to be installed, the least_._._.________________value_must_be_at_least_._._.___ 32_________________________40_____________________________ 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 file SYS$SYSTEM:MODPARAMS.DAT and add a line similar to the following: MIN_PROCSECTCNT = 40 SCSNODE parameter This 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. To check whether the system parameter SCSNODE is defined as your system's computer name: 1. Enter the following command at the system prompt: $ WRITE SYS$OUTPUT F$GETSYI("SCSNODE") 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: $ WRITE SYS$OUTPUT F$GETSYI("SCSNODE") SPEEDY o If SCSNODE is not defined, the computer name is not displayed. 1-14 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks 2. 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 information about running AUTOGEN, see the OpenVMS System Manager's Manual. The SCSNODE parameter's pre-installation status affects what happens after you install and configure the server and reboot the system, 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.____________ Before You Install PATHWORKS Advanced Server 1-15 Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks 1.9.9 Step 9: 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, your OpenVMS system displays a message similar to the following: Queue manager SYS$QUEUE_MANAGER, running, on CPEEDY:: If the queue manager is not running, you can use the following command to start it: $ START/QUEUE/MANAGER 1.9.10 Step 10: Check Time Zone and TDF To check the time zone and time differential factor (TDF) settings on the system, run the OpenVMS command procedure SYS$MANAGER:UTC$TIME_SETUP.COM. From the SYSTEM account, enter the following command to begin the procedure: $ @SYS$MANAGER:UTC$TIME_SETUP.COM PATHWORKS Advanced Server's internal time management uses Greenwich Mean Time (GMT). To properly represent the time in the local environment, the time zone information must be set up before the server is started. To set the time zone on your OpenVMS system, execute the following command procedure: @ SYS$MANAGER:UTC$TIMEZONE_SETUP.COM To set the time zone differential factor for the 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 time zone and TDF, see the section on setting time zone information in the OpenVMS System Manager's Manual. 1-16 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks 1.9.11 Step 11: Check DECnet Status It is not necessary to have DECnet running during the installation, but DECnet must be running on the system before you can configure the server, if you are planning to enable the DECnet transport. 1.9.11.1 Checking DECnet (Phase IV) Status If you use DECnet (Phase IV), enter the following command to see whether it is running on the system where you are planning to install the server software: $ MCR NCP SHOW EXECUTOR ________________________________________________________________ If DECnet (Phase IV) is_._._.______________Then_._._.________________________________ Running The system displays State = on as shown below: Node Volatile Summary as of 16-SEP-1998 12:16:36 Executor node = 12.691 (COBRAZ) State = on Identification = DECnet for OpenVMS AXP V7.1 Not running You can enter the following command to start it: $ @SYS$MANAGER:STARTNET ________________________________________________________________ 1.9.11.2 Checking DECnet-Plus Status If you use DECnet-Plus (formerly DECnet/OSI for OpenVMS), enter the following command to see whether it is running on the system where you are planning to install the server software: Before You Install PATHWORKS Advanced Server 1-17 Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks $ SHOW LOGICAL NET$STARTUP_STATUS ________________________________________________________________ If DECnet is_._._._____Then_._._._________________________________________ Running The system displays: "NET$STARTUP_STATUS" = "RUNNING-ALL" (LNM$SYSTEM_TABLE) Not running You can enter the following command to start it: $ @SYS$STARTUP:NET$STARTUP ________________________________________________________________ 1.9.12 Step 12: Check TCP/IP Status If you are planning to use the TCP/IP transport, make sure that TCP/IP is running and that the PATHWORKS IP (PWIP) driver has been loaded. The procedure for starting the TCP/IP product and the PWIP driver differs depending on the TCP/IP product running on the system. Refer to the documentation for your TCP/IP product for information on how to start TCP/IP and the PWIP driver. For example, for TCP/IP Services for OpenVMS V4.x, use the configuration procedure UCX$CONFIG.COM to enable the PWIP driver on TCP/IP startup, or enter the following OpenVMS commands: $ @SYS$STARTUP:UCX$STARTUP $ @SYS$STARTUP:UCX$PWIP_STARTUP You can add these commands to the system startup procedure. For TCP/IP Services for OpenVMS V5, enable the PWIP driver using the configuration procedure TCPIP:CONFIG.COM, or enter the following OpenVMS commands: $ @SYS$STARTUP:TCPIP$STARTUP $ @SYS$STARTUP:TCPIP$PWIP_STARTUP 1-18 Before You Install PATHWORKS Advanced Server Before You Install PATHWORKS Advanced Server 1.9 Pre-installation Tasks 1.9.13 Step 13: Check OpenVMS Cluster Configuration You can run PATHWORKS Advanced Server on multiple OpenVMS cluster members (server nodes). To do so, follow these steps: 1. On each system disk on which you want to run PATHWORKS Advanced Server, complete: o The tasks described in this chapter o The VMSINSTAL command procedure described in Chapter 2, Installing the PATHWORKS Advanced Server 2. On each cluster member that you want to use as a PATHWORKS Advanced Server, run the configuration command procedure (PWRK$CONFIG). This ensures that each node has enough resources to run the server. ________________________Note ________________________ An OpenVMS cluster can include both VAX and Alpha member nodes. The PATHWORKS Advanced Server can run on any VAX or Alpha cluster member that is running OpenVMS Version 7.1 or OpenVMS Version 7.2. However, an OpenVMS cluster cannot support two different versions of the file and print server (for example, PATHWORKS V6 for OpenVMS (Advanced Server) and Advanced Server V7.2 for OpenVMS). If external authentication is enabled in an OpenVMS cluster where the file server is not running on all member nodes, you should set up the nodes that are not running the PATHWORKS Advanced Server to enable external authentication. To enable external authentication on a member node where you are not running the file and print server, perform the additional steps described in Section 5.5, Setting Up External Authentication. _____________________________________________________ Before You Install PATHWORKS Advanced Server 1-19 Before You Install PATHWORKS Advanced Server 1.10 Next Step 1.10 Next Step To install PATHWORKS Advanced Server, proceed to Chapter 2, Installing the PATHWORKS Advanced Server. 1-20 Before You Install PATHWORKS Advanced Server 2 ________________________________________________________________ Installing the PATHWORKS Advanced Server This chapter describes how to install the PATHWORKS for OpenVMS (Advanced Server) 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 PATHWORKS Advanced Server. 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 installation procedure and what it does. 2.1.1 What is VMSINSTAL? VMSINSTAL is the 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 PATHWORKS Advanced Server. Installing the PATHWORKS Advanced Server 2-1 Installing the PATHWORKS Advanced Server 2.1 About the Installation Procedure 2.1.2 PATHWORKS Advanced Server Installation Kit The VMSINSTAL installation kit includes several OpenVMS BACKUP save sets. The save set PWRKV60B060.A always contains the file KITINSTAL.COM and the release notes. The savesets included in the software kit are listed in the product release notes. 2.1.3 What VMSINSTAL Does When you use VMSINSTAL, it: 1. Determines whether the PATHWORKS for OpenVMS (NetWare) server is installed on the system, and if it is, optionally removes the NetWare server software. 2. Creates PATHWORKS Advanced Server accounts on the file server, 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 PATHWORKS Advanced Server DCL command definition file. 6. Installs the PATHWORKS Advanced Server logical names definition files. 7. Deletes obsolete files. 8. Installs the PATHWORKS Advanced Server files. 9. Verifies that the software has been installed successfully. (See Section 5.2, Verifying the PATHWORKS for OpenVMS (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 during the installation procedure, and how to specify the required information during the procedure. 2-2 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 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 PATHWORKS Advanced Server is: PWRKV60B060 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. Procedures for obtaining the release notes are described in Section 1.6, Reading the Release Notes. 4. Do you want to install just the Upgrade utility? If the PATHWORKS V5 for OpenVMS (LAN Manager) server is installed on the system, you are prompted to install the Upgrade utility separately, which allows you to upgrade server database files before you install the PATHWORKS for OpenVMS (Advanced Server). To install the PATHWORKS Advanced Server, you must upgrade the server databases. If you choose to install just the Upgrade utility, you can install the PATHWORKS Advanced Server later, after you upgrade your databases. If you install the PATHWORKS Advanced Server software, the Upgrade utility is also installed. 5. Do you want to preserve the PATHWORKS V5 for OpenVMS (LAN Manager) environment, and if so, where? Installing the PATHWORKS Advanced Server 2-3 Installing the PATHWORKS Advanced Server 2.2 Installing the Server If you are upgrading from PATHWORKS V5 for OpenVMS (LAN Manager), you can choose to have the PATHWORKS V5 for OpenVMS (LAN Manager) data files copied to the location you specify in the installation procedure. This allows you to roll back to PATHWORKS V5 for OpenVMS (LAN Manager) later, after configuring and starting the PATHWORKS Advanced Server. Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for more information about the PATHWORKS Rollback procedure. If you have V4.x of PATHWORKS for OpenVMS, you must upgrade to PATHWORKS V5 for OpenVMS (LAN Manager) before installing PATHWORKS V6 for OpenVMS (Advanced Server). For instructions on upgrading from V4.x to V5, see the PATHWORKS for OpenVMS Server Migration Guide. 6. Do you want to install PATHWORKS Advanced Server software? This option allows you to install the complete PATHWORKS for OpenVMS (Advanced Server) server, including the Upgrade utility and the integrated license server, 7. Do you want to install the standalone license server? 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. The installation procedure gives you the option to install the standalone license server software from the PATHWORKS for OpenVMS (Advanced Server) software kit. In this case, the PATHWORKS Advanced Server is not installed. If the PATHWORKS Advanced Server is installed, you cannot choose the standalone license server installation option. 8. Do you want to install PATHWORKS External Authentication software only? 2-4 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.2 Installing the Server On OpenVMS clusters, you can install the External Authentication software only. This is useful on cluster member nodes that are not going to run the PATHWORKS Advanced Server. For more information, see Section 1.5, About External Authentication. 9. What is the User Identification Code (UIC) group number? The PATHWORKS Advanced Server installation procedure creates the OpenVMS user accounts PWRK$DEFAULT and PWRK$GUEST, if they do not already exist. When an OpenVMS user account is created, it is assigned a UIC group number. The default selection displayed by the installation procedure is determined as follows: _______________________________________________________ If_._._.___________________The_default_is_._._.________ You are installing The first available unused PATHWORKS Advanced Server UIC group number, starting for the first time with 360. If PATHWORKS V5 for The same group number OpenVMS (LAN Manager) as that associated with is currently installed, the existing account an account named PCFS$ACCOUNT. PCFS$ACCOUNT already exists If 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: Installing the PATHWORKS Advanced Server 2-5 Installing the PATHWORKS Advanced Server 2.2 Installing the Server $ 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 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 PWRKV60B060 product identifier, the media device, and whether you want access to the online release notes during the installation procedure: ________________________________________________________________ If_you_._._.______________Then_enter_._._.______________________ Want access to the @VMSINSTAL PWRKV60B060 device_name release notes during the OPTIONS N installation procedure Do not want access @VMSINSTAL PWRKV60B060 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 prompt to which you must respond. Usually the prompt has a default answer, which the procedure displays in 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-6 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.2 Installing the Server 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.2.5 How to Answer Installation Questions Table 2-1 tells you how to respond to the questions VMSINSTAL displays. ________________________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 PATHWORKS Advanced Server Installation and Configuration Procedure. _____________________________________________________ Table_2-1_Installation_Questions__________________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Are you satisfied Continue with the backup of your system disk [YES]? Exit NO (continued on next page) Installing the PATHWORKS Advanced Server 2-7 Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Select option Display the release notes 1 [2]:[1] on the screen To stop the display at any time, press . Print the release notes The release notes file is sent to the default print queue SYS$PRINT. You can enter the name of another print queue. [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) 2-8 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Print the release notes and 3 display them on the screen To send the release notes to another print queue, enter the name of another print queue. To stop the screen display at any time, press . Continue without displaying 4 or printing the release The notes release notes are automat- ically copied to SYS$HELP. (continued on next page) Installing the PATHWORKS Advanced Server 2-9 Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Do you want Install one or more servers to install the upgrade utility only [NO]?[2] Install only the Upgrade YES utility Do you want to Continue YES continue the installation [NO]?[1] Exit Do you want Install the PATHWORKS YES to install Advanced Server the complete PATHWORKS V6.0B for OpenVMS [NO]? Omit the PATHWORKS Advanced Server [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. [2]This question is displayed only if your system is currently running the previous version of PATHWORKS for OpenVMS. (continued on next page) 2-10 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Do you want to Retain the PATHWORKS V5 preserve the V5 for OpenVMS (LAN Manager) (LAN Manager) environment so that you can environment use the rollback procedure [YES]?[2] described in the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide Not retain the V5 NO environment Enter the Preserve the V5 environment directory to in the default directory preserve the shown V5 environment [SYS$SYSDEVICE:[000000]]:[3] Preserve the V5 environment A on another device or in different another directory device or directory. [2]This_question_is_displayed_only_if_your_system_is______ currently running the previous version of PATHWORKS for OpenVMS. [3]This question is displayed only if you chose to preserve the PATHWORKS V5 for OpenVMS (LAN Manager) environment. (continued on next page) Installing the PATHWORKS Advanced Server 2-11 Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Do you want Install the standalone YES to install the license server This PATHWORKS license option server only installs [NO]?[4] the license server and transport software without the PATHWORKS Advanced Server. Refer to Chapter 4, Configuring and Starting the Standalone License Server for more in- ________________________________________________formation. [4]This question is displayed only if you chose not to install the PATHWORKS Advanced Server. (continued on next page) 2-12 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Install the PATHWORKS Advanced Server with the This license server option causes the in- stallation procedure to proceed to the next question. Do you want to Install only the external YES install only authentication software This the External option Authentication installs images [NO]?[4] the external authen- tication software without the PATHWORKS Advanced Server. [4]This_question_is_displayed_only_if_you_chose_not_to____ install the PATHWORKS Advanced Server. (continued on next page) Installing the PATHWORKS Advanced Server 2-13 Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Install the complete PATHWORKS Advanced Server This or install the standalone option license server causes the in- stallation procedure to repeat the previous questions so that you can select the complete PATHWORKS Advanced Server or only the license server. Is the selection Use the selection correct [YES]? Change the selection NO Terminate the installation Will you allow a Shut down the system system shutdown as part of the product after this installation procedure product is installed [YES]? (continued on next page) 2-14 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Complete the installation NO procedure without shutting System down the system shutdown is required, to complete the product installa- tion. If you answer NO, you must shut down the system manually after the instal- lation procedure is finished. Do you want to Reboot the system do an automatic automatically after system system reboot shutdown [YES]? Reboot the system manually NO Do you want to Run the Installation run the IVP after Verification Procedure the installation (IVP) automatically after is finished the installation procedure [YES]? completes (continued on next page) Installing the PATHWORKS Advanced Server 2-15 Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Not run the IVP NO You can run the IVP inde- pendent of the in- stallation procedure. For detailed informa- tion on running the IVP indepen- dently, see Section 5.2, Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation. Do you want Purge all files it replaces to purge files replaced by this installation [YES]? Not purge any files it NO replaces (continued on next page) 2-16 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Do you want to Delete the files and continue with continue the installation the installation [YES]?[5] Leave the files intact and NO terminate the installation Do you want to Shut down the license shut down the server and continue the PATHWORKS license installation server [YES]?[6] Keep the server running and NO terminate the installation Do you want Shut down the server and to shut down continue the installation the PATHWORKS Advanced Server [YES]?[6] Keep the server running and NO terminate the installation Enter default UIC Associate the newly group number for created OpenVMS accounts PWRK$DEFAULT and PWRK$DEFAULT and PWRK$GUEST PWRK$GUEST[nnn]: with the default user identification code (UIC) group number (nnn) [5]This_question_is_displayed_only_if_there_are_PATHWORKS_ files in system-specific directories. [6]This question is displayed only if a server is running. (continued on next page) Installing the PATHWORKS Advanced Server 2-17 Installing the PATHWORKS Advanced Server 2.2 Installing the Server Table_2-1_(Cont.)_Installation_Questions__________________ For this If you want the installa- Enter . . . question_._._._____tion_procedure_to_._._.________________ Associate the newly created A three- accounts with the UIC group digit UIC number you specify number. For detailed informa- tion about UIC group numbers, see the OpenVMS System Manager's ________________________________________________Manual.___ 2.3 Troubleshooting Installation Problems The following sections describe some problems you can encounter if you install the PATHWORKS Advanced Server in an environment that is not appropriate. 2.3.1 Installing the PATHWORKS Advanced Server on a System with the NetWare Server The PATHWORKS Advanced Server cannot be installed on a system where the NetWare server is installed. If you at- tempt to install the PATHWORKS Advanced Server on a system where the NetWare server is installed, the installation procedure optionally invokes the NetWare server software removal procedure (SYS$STARTUP:PWVN$DEINSTAL.COM). When the installation procedure detects the presence of the NetWare server, it displays the following message and question: 2-18 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.3 Troubleshooting Installation Problems %PWRKV60B-E-OLDVERPWNV, PATHWORKS V6.0-nnnx for OpenVMS (NetWare) was previously installed. This product is no longer supported. To install the PATHWORKS V6.0B for OpenVMS product, the NetWare product must be deinstalled. * Will you allow this installation procedure to deinstall * the NetWare product [NO]? To remove the NetWare server software, enter YES. To terminate the installation procedure without removing the NetWare server software, enter NO, or press . You can remove the NetWare server manually using the procedure in Section 7.2, Removing the PATHWORKS NetWare Server. Then start the VMSINSTAL procedure again after the NetWare server has been removed. 2.3.2 Installing PATHWORKS Advanced Server on a System with PATHWORKS V5 for OpenVMS (LAN Manager) You can upgrade PATHWORKS V5 for OpenVMS (Advanced Server) to PATHWORKS V6 for OpenVMS (Advanced Server). If the system has PATHWORKS V5 for OpenVMS (LAN Manager) installed, you can use the Upgrade utility, as described in the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide, to upgrade server information before you configure and start the PATHWORKS Advanced Server. 2.3.3 Installing the Standalone License Server on a System Where the PATHWORKS Advanced Server Has Been Installed If you install the standalone license server on a system where the PATHWORKS Advanced Server has been installed, the installation procedure displays the following message: The PATHWORKS Advanced Server was previously installed and you have selected to install the license server only. Because the PATHWORKS Advanced Server includes the license server, the complete PATHWORKS Advanced Server must be installed. The installation procedure will choose to install the PATHWORKS 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 PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2-19 Installing the PATHWORKS Advanced Server 2.3 Troubleshooting Installation Problems software using the PWRK$DEINSTAL.COM command procedure, as described in Chapter 7, Removing PATHWORKS Advanced Server Software. Then start the VMSINSTAL procedure again. For a sample installation and configuration script for the standalone license server, see Appendix C, Sample Standalone License Server Installation and Configuration Procedure. 2.3.4 Installing the External Authentication Software You cannot install the External Authentication software only, if you have previously installed the PATHWORKS Advanced Server. The installation procedure displays the following message if you try to install the External Authentication images under these circumstances: The PATHWORKS Advanced Server was previously installed, and you have selected to install the External Authentication images only. Because the PATHWORKS Advanced Server includes the External Authentication images, the complete PATHWORKS Advanced Server must also be installed. You must remove the PATHWORKS Advanced Server software to be able to select this option. To remove PATHWORKS Advanced Server software, run the PWRK$DEINSTAL procedure, as described in Chapter 7, Removing PATHWORKS Advanced Server Software. For a sample installation script for the External Authentication images, see Appendix E, Sample External Authentication Installation Procedure. 2.4 Next Steps To continue, depending on the software you are installing, do one of the following: ________________________________________________________________ Which tells you how If_you_are_._._.______Proceed_to_._._.______to_._._.____________ Installing the Chapter 3, Configure the PATHWORKS Advanced Configuring the PATHWORKS Advanced Server PATHWORKS Advanced Server. Server 2-20 Installing the PATHWORKS Advanced Server Installing the PATHWORKS Advanced Server 2.4 Next Steps ________________________________________________________________ Which tells you how If_you_are_._._.______Proceed_to_._._.______to_._._.____________ Installing the Chapter 4, Configure the standalone license Configuring and standalone license server Starting the server. Standalone License Server Upgrading from PATHWORKS for Use the Upgrade PATHWORKS V5 OpenVMS (Advanced utility to create for OpenVMS (LAN Server) Server and edit upgrade Manager) Migration Guide reports. Installing the Section 5.5, Set up PATHWORKS PATHWORKS External Setting Up External external authen- Authentication Authentication tication on the software_only_______________________________system._____________ Installing the PATHWORKS Advanced Server 2-21 3 ________________________________________________________________ Configuring the PATHWORKS Advanced Server This chapter describes how to configure the PATHWORKS Advanced Server and consists of the following sections: o Section 3.1, About the PATHWORKS Advanced Server Configuration Procedure o Section 3.2, Before You Start the PATHWORKS Advanced Server Configuration Procedure o Section 3.3, How to Start the PATHWORKS Advanced Server Configuration Procedure o Section 3.4, How to Respond to PATHWORKS Advanced Server Configuration Prompts o Section 3.5, How to Change Default Configuration Settings o Section 3.6, Troubleshooting Configuration Procedure Problems o Section 3.7, Selecting the PATHWORKS Advanced Server Network Device o Section 3.8, Defining Communications Devices o Section 3.9, Next Steps 3.1 About the PATHWORKS Advanced Server Configuration Procedure The following sections describe the PATHWORKS Advanced Server configuration procedure and what it does. Configuring the PATHWORKS Advanced Server 3-1 Configuring the PATHWORKS Advanced Server 3.1 About the PATHWORKS Advanced Server Configuration Procedure 3.1.1 What Is the Configuration Procedure? PWRK$CONFIG.COM, the PATHWORKS Advanced Server configu- ration procedure, is installed by the PATHWORKS Advanced Server installation procedure. Like the installation procedure, the configuration procedure asks you a series of questions (by displaying prompts). The procedure uses your answers to configure the PATHWORKS Advanced Server. 3.1.2 What the Configuration Procedure Does PWRK$CONFIG is a command procedure that: o Creates the PATHWORKS Advanced Server on-disk structure. (Refer to Appendix F, PATHWORKS Advanced Server Files and On-Disk Structure, for a list of files and a description of the on-disk structure). o Allows you to enter the Configuration Manager to modify system configuration parameters, such as the transports the server will run and the maximum number of clients that can connect to the server simultaneously. o Creates the PATHWORKS Advanced Server user account and share databases. o Allows you to modify server configuration default settings such as server role, domain name, and which services are enabled. o Allows you to set or change the Administrator account password. o Gives you the option of starting the server. After you install the server, you must run PWRK$CONFIG before you can start the server. In an OpenVMS cluster, you must run PWRK$CONFIG on each individual node where the PATHWORKS Advanced Server will run, before you can start the server. (Although the nodes in an OpenVMS cluster function as a single unit in a domain, you need to treat them as individual units for purposes of configuration.) For more information, read the information on the Configuration Manager in the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 3-2 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server Before You Start the PATHWORKS Advanced Server Configuration Procedure 3.2 Before You Start the PATHWORKS 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 following PATHWORKS data files? 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 disk device SYS$SYSDEVICE:. However, you can specify any existing OpenVMS disk device that has at least 79,500 free blocks of disk space. When you choose a disk device for the PATHWORKS data files, keep the following in mind: - The PATHWORKS 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 server. Therefore, Compaq Computer Corporation recommends that you specify a disk device other than the system disk. - On an OpenVMS cluster with multiple system disks, all nodes on which you plan to run the PATHWORKS Advanced Server must use the same disk device to store and access PATHWORKS Advanced Server files. - The configuration procedure may be run again after you complete the installation and initial configuration of the PATHWORKS Advanced Server. You may specify a different disk at that time to move the existing PATHWORKS Advanced Server data files to a different disk volume. Configuring the PATHWORKS Advanced Server 3-3 Configuring the PATHWORKS Advanced Server 3.2 Before You Start the PATHWORKS Advanced Server Configuration Procedure 2. Do you want to change the system configuration parameters now? If you enter YES to the prompt to change the system configuration parameters, the Configuration Manager is started. The Configuration Manager is a utility that allows you to modify server configuration parameters, such as the maximum number of clients that can connect to the server and which network transports the server uses. Whether or not you choose to change the system configuration at this time, you can change it later by entering the ADMINISTER/CONFIG command at the OpenVMS system prompt: $ ADMINISTER/CONFIG For more information about transports and about using the Configuration Manager, 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 (BDC), during the initial configuration you must select at least one transport for the BDC that will also be run by its primary domain controller (PDC). Otherwise, the configuration will fail. When you choose the transports to run, keep the following in mind if the system will support wide area networking: - 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. 3-4 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server Before You Start the PATHWORKS Advanced Server Configuration Procedure - If you are using a WINS server for network name resolution, both the backup domain controller and the primary domain controller must use a WINS Server to provide NetBIOS name resolution. - 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. To enable one or both of the wide area networking implementations, select them using the Configuration Manager. Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for more information. 3. Do you want to change any of the server configuration default 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 LAN needs only one PATHWORKS license server to serve client- based licenses. The product authorization keys (PAKs) must be loaded on the system that runs the PATHWORKS license server. If you are using server- based licensing, the license server is not required. In an OpenVMS cluster, the PAKs must be loaded on all nodes that run the PATHWORKS license server. This is best accomplished by adding the PAKs to a shared license database. By default, the license server does not run. Configuring the PATHWORKS Advanced Server 3-5 Configuring the PATHWORKS Advanced Server 3.2 Before You Start the PATHWORKS Advanced Server Configuration Procedure For detailed information on managing PATHWORKS licenses, see the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. 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 on all primary domain controllers and backup domain controllers. By default, the Netlogon service runs. o Domain name This is the name of the domain in which your server participates. A domain is a subdivision of clients and servers on the network. The default PATHWORKS Advanced Server domain name is LANGROUP. Compaq recommends that you choose another name for the domain. o Role of the server 3-6 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server Before You Start the PATHWORKS Advanced Server Configuration Procedure This is the server's role in the domain. You can designate a PATHWORKS 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 is the unique name that identifies your server in the domain. You define this name or accept the default value when you run the configuration procedure. By default, the PATHWORKS Advanced Server computer name is the same as the system's SCSNODE name. o PATHWORKS cluster alias If your server is a member of an OpenVMS cluster, this is the network name that all servers in the cluster use. The alias lets remote nodes (such as clients) treat the entire cluster as though it were a single server. For example, a client user can specify the PATHWORKS alias to connect to any server in the cluster; the user does not know (and does not need to know) to which server the client is connected. If DECnet is configured on the system, the default is the same as the DECnet alias name. If not, the default PATHWORKS Advanced Server cluster alias is same as the OpenVMS cluster alias. o Server announce comment This is the description of the server that the PATHWORKS Advanced Server broadcasts out when it announces its presence on the network. This description may also be displayed when you view a list of available servers. The default server announce comment is "PATHWORKS V6.0B for OpenVMS (Advanced Server)." For detailed information on changing default server configuration settings, see Section 3.5, How to Change Default Configuration Settings. 4. What is the Administrator account password? Configuring the PATHWORKS Advanced Server 3-7 Configuring the PATHWORKS Advanced Server 3.2 Before You Start the PATHWORKS Advanced Server Configuration Procedure If you are configuring a primary domain controller, the configuration procedure prompts you to define a pass- word for the PATHWORKS Advanced Server Administrator account, from which you administer the server. 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 server. If you do not want to start the server at this time, you can do so later from the command line after the configuration procedure completes. For detailed information on alternate ways to start the server, see Section 5.3.4, Starting the File Server. 3.3 How to Start the PATHWORKS 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. 2. Start the configuration procedure by entering: $ @SYS$UPDATE:PWRK$CONFIG 3.4 How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 3-1, PATHWORKS 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 3-8 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server 3.4 How to Respond to PATHWORKS Advanced Server Configuration Prompts script, see Appendix B, Sample PATHWORKS Advanced Server Installation and Configuration Procedure. _____________________________________________________ Table_3-1_PATHWORKS_Advanced_Server_Configuration_Prompts_ At this If you want the configura- Enter . . . prompt_._._._______tion_procedure_to_._._.________________ 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 Enter disk Copy the PATHWORKS on- device name disk structure to the where PATHWORKS default OpenVMS disk device 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 PATHWORKS on-disk device_ structure to an OpenVMS name disk device different from the default displayed [1]This_prompt_is_displayed_only_if_the_server_is_running. (continued on next page) Configuring the PATHWORKS Advanced Server 3-9 Configuring the PATHWORKS Advanced Server 3.4 How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 3-1 (Cont.) PATHWORKS Advanced Server Configuration __________________Prompts_________________________________ At this If you want the configura- Enter . . . prompt_._._._______tion_procedure_to_._._.________________ Do you want to Enter the Configuration change the server Manager tool For configuration detailed parameters now? informa- [YES]: tion about using the Configuration Manager, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. Continue the configuration NO procedure without entering the Configuration Manager Enter item Accept the configuration number, or RETURN parameters displayed to use these values [DONE]: (continued on next page) 3-10 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server 3.4 How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 3-1 (Cont.) PATHWORKS Advanced Server Configuration __________________Prompts_________________________________ At this If you want the configura- Enter . . . prompt_._._._______tion_procedure_to_._._.________________ Change the configuration The number settings displayed associated with a setting you want to change. For detailed informa- tion on changing these default config- uration settings, see Section 3.5, How to Change Default Configuration Settings. Do you want to Keep the existing enter a new Administrator account Administrator password account password [NO]:[2,3] [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 PATHWORKS Advanced Server 3-11 Configuring the PATHWORKS Advanced Server 3.4 How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 3-1 (Cont.) PATHWORKS Advanced Server Configuration __________________Prompts_________________________________ At this If you want the configura- Enter . . . prompt_._._._______tion_procedure_to_._._.________________ Prompt you to enter a YES new Administrator account password Enter AdministratorAssociate a password with password network account the Administrator account If your password:[3] server will be part of an existing domain, enter the password to the existing domain's Administrator account. Re-enter password to verify password:[3] Do you want to Start the server au- start PATHWORKS tomatically after the V6.0B for OpenVMS installation procedure on node node_name completes now [YES]:[3] Not start the server NO [3]This_prompt_is_displayed_only_if_you_are_configuring_a_ primary domain controller. __________________________________________________________ 3-12 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server 3.5 How to Change Default Configuration Settings 3.5 How to Change Default 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: PATHWORKS V6.0B 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. PATHWORKS OpenVMS cluster alias: COBRAZ_ALIAS 8. Server announce comment: PATHWORKS V6.0B for OpenVMS (Advanced Server) 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 information on completing the rest of the configuration procedure, see Section 3.4, How to Respond to PATHWORKS Advanced Server Configuration Prompts. For a description of each server configuration setting, see Section 3.2, Before You Start the PATHWORKS Advanced Server Configuration Procedure. Configuring the PATHWORKS Advanced Server 3-13 Configuring the PATHWORKS Advanced Server 3.5 How to Change Default Configuration Settings 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. 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. [1]Displayed_only_if_Alerter_service_is_enabled.________________ (continued on next page) 3-14 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server 3.5 How to Change Default Configuration Settings Table_3-2_(Cont.)_Configuration_Settings________________________ Setting_________________________Possible_Values_________________ 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. 7a. PATHWORKS OpenVMS cluster The PATHWORKS cluster alias for alias:[2] 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.6 Troubleshooting Configuration Procedure Problems The following section describes how to ensure sufficient resources will be available to support clients. 3.6.1 Ensuring Sufficient Resources to Support Clients PATHWORKS 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 PATHWORKS Advanced Server, and these resources have already been consumed when PATHWORKS Advanced Server is started, there may be insufficient resources left for PATHWORKS Advanced Server to support the desired number of clients. Configuring the PATHWORKS Advanced Server 3-15 Configuring the PATHWORKS Advanced Server 3.6 Troubleshooting Configuration Procedure Problems To ensure sufficient resource allocation to support clients, make sure that all software that will run concurrently with PATHWORKS Advanced Server is installed and started before you run the PATHWORKS Advanced Server configuration procedure, especially if you run TCP/IP. After you successfully configure the PATHWORKS 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_node.LOG To increase the resource allocation, make the appropriate modifications to the MODPARAMS.DAT file and then run AUTOGEN. Refer to Chapter 1, Before You Install PATHWORKS Advanced Server, for more information about the requirements for system parameter settings. 3.7 Selecting the PATHWORKS 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 PATHWORKS 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 PATHWORKS Advanced Server operates. You must add these logicals to SYS$MANAGER:SYLOGICALS.COM to have them available after rebooting. Table_3-3_OpenVMS_Network_Device_Logicals_________________ Logical_Name____________________Transport_________________ NETBIOS$DEVICE DECnet PWRK$KNBDAEMON_DEVICE TCP/IP (continued on next page) 3-16 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server 3.7 Selecting the PATHWORKS Advanced Server Network Device Table_3-3_(Cont.)_OpenVMS_Network_Device_Logicals_________ Logical_Name____________________Transport_________________ 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 PATHWORKS Advanced Server, make sure the device you select corresponds to the first device listed in the TCP/IP local hosts database. _____________________________________________________ 3.8 Defining Communications Devices This section describes how to add new communications devices that are not automatically recognized by the PATHWORKS 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 PATHWORKS Advanced Server images are available to customers. Therefore, this section describes how to define the communications device you want the PATHWORKS Advanced Server to use. Configuring the PATHWORKS Advanced Server 3-17 Configuring the PATHWORKS Advanced Server 3.8 Defining Communications Devices If the communications device is not recognized by PATHWORKS 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 following examples, 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: $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0: $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0: 3-18 Configuring the PATHWORKS Advanced Server Configuring the PATHWORKS Advanced Server 3.8 Defining Communications Devices 2. Restart the server: $ @SYS$STARTUP:PWRK$STARTUP 3.9 Next Steps You can start the PATHWORKS Advanced Server automatically as part of the configuration procedure. o If you are upgrading from PATHWORKS V5 for OpenVMS (LAN Manager) perform the upgrade procedures described in the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. o If you are ready to start the server, see Chapter 5, After You Install the PATHWORKS Advanced Server, for instructions. Configuring the PATHWORKS Advanced Server 3-19 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 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 PATHWORKS Advanced Server o In conjunction with the PATHWORKS Advanced Server Compaq recommends that you install the license server on a designated OpenVMS system without the PATHWORKS Advanced Server, to ensure smooth and continuous operation of the license server. Therefore, the PATHWORKS Advanced Server 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 PATHWORKS 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 ________________________Note ________________________ The license server is required for client-based licensing. For 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 ________________________Note ________________________ The license server included with PATHWORKS Advanced Server will not issue or manage PATHWORKS for OpenVMS (NetWare) licenses. If you have clients using NetWare networking software, maintain the existing version of the license server on a different system from the one that is running PATHWORKS 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 PATHWORKS Advanced Server. The procedures are described in Chapter 2, Installing the PATHWORKS Advanced Server. 4-2 Configuring and Starting the Standalone License Server Configuring and Starting the Standalone License Server 4.3 Configuring the Standalone License Server 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: Configuring and Starting the Standalone License Server 4-3 Configuring and Starting the Standalone License Server 4.3 Configuring the Standalone License Server o DECnet o NetBEUI o TCP/IP 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 Configuration Prompts Table 4-1, Standalone 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 Procedure. _____________________________________________________ 4-4 Configuring and Starting the Standalone License Server Configuring and Starting the Standalone License Server 4.5 How to Respond to Configuration Prompts Table_4-1_Standalone_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 PATHWORKS Advanced device_name Server on-disk structure to an OpenVMS disk device different from the default displayed Do you want to Allow licenses to be served serve PATHWORKS over DECnet 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 PATHWORKS over NetBEUI licenses over NetBEUI [NO]:[1] Not allow licenses to be served over NetBEUI [1]Default_answers_may_differ_if_you_ran_the_PWRK$CONFIG________ procedure previously. (continued on next page) Configuring and Starting the Standalone License Server 4-5 Configuring and Starting the Standalone License Server 4.5 How to Respond to Configuration Prompts Table 4-1 (Cont.) Standalone 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 PATHWORKS over TCP/IP 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 PATHWORKS license configuration procedure server now [YES]: completes Complete the configuration NO procedure without starting the server [1]Default_answers_may_differ_if_you_ran_the_PWRK$CONFIG________ 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. 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 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 Configuring and Starting the Standalone License Server 4-7 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 HYDRAA, HYDRAB, and HYDRAC: SYSMAN> SET ENVIRONMENT/NODE=(HYDRAA,HYDRAB,HYDRAC) 4. Start the license server on the nodes you defined. At the SYSMAN> prompt, enter the following command: SYSMAN>DO @SYS$STARTUP:PWRK$STARTUP 4-8 Configuring and Starting the Standalone License Server 5 ________________________________________________________________ After You Install the PATHWORKS Advanced Server This chapter describes tasks you can perform after you install the PATHWORKS Advanced Server software. This chapter consists of the following sections: o Section 5.1, Before You Begin Post-installation Tasks o Section 5.2, Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation o Section 5.3, Starting the PATHWORKS Advanced Server o Section 5.4, Stopping the PATHWORKS Advanced Server o Section 5.5, Setting Up External Authentication o Section 5.6, Installing Optional Server Administration Tools 5.1 Before You Begin Post-installation Tasks Make sure you have completed all the required steps in Table 5-1, Have You Done . . . , before proceeding. After You Install the PATHWORKS Advanced Server 5-1 After You Install the PATHWORKS Advanced Server 5.1 Before You Begin Post-installation Tasks Table_5-1_Have_You_Done_._._._____________________________ If_you_are_._._.______Make_sure_that_you_have_._._._______ Installing the PATHWORKS Advanced 1. Completed the installation Server procedure described in Chapter 2, Installing the PATHWORKS Advanced Server. 2. Completed the configuration procedure described in Chapter 3, Configuring the PATHWORKS Advanced Server. Upgrading a PATHWORKS V5 1. Completed the installation for OpenVMS (LAN procedures described in Manager) server to Chapter 2, Installing the PATHWORKS V6 for PATHWORKS Advanced Server. OpenVMS (Advanced Server) server 2. Completed the upgrade procedure described in the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. 3. Completed the configuration procedure described in Chapter 3, Configuring the PATHWORKS Advanced Server. Installing the Standalone License 1. Completed the installation Server procedures described in Chapter 2, Installing the PATHWORKS Advanced Server. 2. Completed the configuration and startup procedures described in Chapter 4, Configuring and Starting the Standalone License Server. Installing external authentication Completed the installation procedure software only described in Chapter 2, Installing ______________________the_PATHWORKS_Advanced_Server.______ 5-2 After You Install the PATHWORKS Advanced Server After You Install the PATHWORKS Advanced Server 5.2 Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation 5.2 Verifying the PATHWORKS for OpenVMS (Advanced Server) Installation If you did not run the IVP as part of the installation procedure, as described in Chapter 2, Installing the PATHWORKS Advanced Server, you can run it now to make sure that the server installed successfully. To run the IVP for PATHWORKS Advanced Server, enter: $ @SYS$TEST:PWRK$IVP ________________________________________________________________ If the instal- And you should . . . lation_._._.__Then_the_IVP_displays_._._._______________________ Succeeded The message %PWRK-I-NORMAL, IVP completed successfully Start the server, as described in Section 5.3.4, Starting the File Server. Failed An error message, followed by -PWRK-E-IVPFAIL, IVP has failed Reinstall the software, as described in Chapter 2, Installing the PATHWORKS Advanced ______________________________________________Server.___________ 5.3 Starting the PATHWORKS Advanced Server The following sections describe when and how to start the PATHWORKS Advanced Server. After You Install the PATHWORKS Advanced Server 5-3 After You Install the PATHWORKS Advanced Server 5.3 Starting the PATHWORKS Advanced Server 5.3.1 When to Start the PATHWORKS Advanced Server You must configure the server before you can start it for the first time. After running the configuration procedure, you can start and stop the server at any time. 5.3.2 What the Startup Procedure 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 ends if it has not. 4. Loads transport drivers. 5. Installs images. 6. Starts transport support processes. 7. Starts each of the components: o License Registrar o License server (if configured) o File server 5.3.3 Troubleshooting the Startup PATHWORKS 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). If the PATHWORKS Advanced Server startup does not complete successfully, check the SYLOGIN.COM procedure. Make sure that only commands that should be executed by detached processes are executed during the PATHWORKS Advanced Server startup. In SYSLOGIN.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 the PATHWORKS Advanced Server startup. See the OpenVMS DCL Dictionary for more information. 5-4 After You Install the PATHWORKS Advanced Server After You Install the PATHWORKS Advanced Server 5.3 Starting the PATHWORKS Advanced Server 5.3.4 Starting the File Server You can start the file server: o During the configuration procedure, as described in Chapter 3, Configuring the PATHWORKS Advanced Server. o Manually from the command line. o Automatically each time you reboot. 5.3.5 How to Start the PATHWORKS Advanced Server Manually If you did not start the PATHWORKS Advanced Server during the configuration procedure, you can start it now by entering: $ @SYS$STARTUP:PWRK$STARTUP The PATHWORKS Advanced Server starts, and messages similar to the following are displayed: PATHWORKS file server will use DECnet, TCP/IP. PATHWORKS mail notification will use DECnet. Process NETBIOS created with identification 0000009A Process PWRK$LICENSE_R created with identification 0000009D The PATHWORKS V6.0B server is configured to support 20 PC clients. Process PWRK$MASTER created with identification 000000A2 The master process will now start all other PATHWORKS processes. 5.3.6 How to Define PATHWORKS Advanced Server Commands When You Log In You can define server commands automatically when you log in to the privileged account that you use to manage the PATHWORKS Advanced Server. To define server commands at login, edit the LOGIN.COM file of the privileged account to add the following line: $ @SYS$STARTUP:PWRK$DEFINE_COMMANDS After You Install the PATHWORKS Advanced Server 5-5 After You Install the PATHWORKS Advanced Server 5.3 Starting the PATHWORKS Advanced Server 5.3.7 How to Start the PATHWORKS Advanced Server Automatically To make sure that the server starts automatically each time you boot your OpenVMS system: 1. Edit the system startup file, SYS$STARTUP:SYSTARTUP_VMS.COM. 2. Add the @SYS$STARTUP:PWRK$STARTUP command to the file below all lines that start network transports. For example: $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET . . . $ @SYS$STARTUP:PWRK$STARTUP 5.3.8 How to Start the PATHWORKS Advanced Server in an OpenVMS Cluster If you installed and configured the PATHWORKS Advanced Server on multiple members of the same OpenVMS cluster, Compaq Computer Corporation recommends that you use the SYSMAN utility to start the server manually and simultaneously on all cluster members. To start the servers at the same time, make sure you are logged in to the SYSTEM account on one of the server 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. (In this example, SPEEDY, SPIN, and SPAN.) SYSMAN> DO @SYS$STARTUP:PWRK$STARTUPt the PATHWORKS Advanced Server on all the nodes you defined in the previous command. 5-6 After You Install the PATHWORKS Advanced Server After You Install the PATHWORKS Advanced Server 5.3 Starting the PATHWORKS Advanced Server ________________________________________________________________ Enter_this_command...___________To...___________________________ SYSMAN>_EXIT____________________Exit_the_SYSMAN_utility.________ ________________________Note ________________________ If you are using the STARTUP feature of the SYSMAN utility to start the PATHWORKS 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 Stopping the PATHWORKS Advanced Server The following sections describe when and how you stop the PATHWORKS Advanced Server. 5.4.1 When to Stop the PATHWORKS Advanced Server You can stop the server at any time for any reason, which can include the following: o When you change server parameters o As part of an orderly system shutdown o As needed to troubleshoot server problems 5.4.2 How to Stop the PATHWORKS Advanced Server To stop the server, enter the following command: $ @SYS$STARTUP:PWRK$SHUTDOWN 5.4.3 How to Stop the PATHWORKS Advanced Server on System Shutdown To stop the server as part of an orderly system shutdown, add the shutdown command to the site-specific system shutdown procedure. After You Install the PATHWORKS Advanced Server 5-7 After You Install the PATHWORKS Advanced Server 5.5 Setting Up External Authentication 5.5 Setting Up External Authentication The OpenVMS operating system Versions 7.1 and higher provide support for external authentication. PATHWORKS Advanced Server participates with the operating system to provide external authentication, which allows PATHWORKS Advanced Server users to log in to the OpenVMS operating system using the PATHWORKS 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 PATHWORKS Advanced Server user accounts can avoid having to maintain two different passwords. To provide external authentication on the system, perform the following procedures. __________________________________________________________ Step___Procedure_____________Refer_to_._._._______________ 1. Install one of the Chapter 2, Installing the following: PATHWORKS Advanced Server o The PATHWORKS Advanced Server o PATHWORKS External Authentication images only 2. Copy the external Section 5.5.1, Setting Up authentication files External Authentication in to the system. OpenVMS Clusters 5-8 After You Install the PATHWORKS Advanced Server After You Install the PATHWORKS Advanced Server 5.5 Setting Up External Authentication __________________________________________________________ Step___Procedure_____________Refer_to_._._._______________ 3. Enable external The appropriate OpenVMS authentication for document, one of the the system. following: o For OpenVMS Version 7.1: OpenVMS V7.1 New Features Manual o For OpenVMS Version 7.2: OpenVMS V7.2 Guide to System Security 4. Set the OpenVMS The appropriate OpenVMS user account to document, one of the allow external following: authentication. o For OpenVMS Version 7.1: OpenVMS V7.1 New Features Manual o For OpenVMS Version 7.2: OpenVMS V7.2 Guide to System Security 5. Establish host PATHWORKS for OpenVMS mapping between the (Advanced Server) Server PATHWORKS Advanced Administrator's Guide Server user account and the OpenVMS user account, if _______necessary._________________________________________ 5.5.1 Setting Up External Authentication in OpenVMS Clusters If you are running PATHWORKS Advanced Server in an OpenVMS cluster, and you have enabled external authentication for PATHWORKS Advanced Server users, you should set up external authentication on all the member nodes in an OpenVMS cluster. If any nodes in the cluster are not running the PATHWORKS Advanced Server, you follow the procedure described in this section to set up external authentication on nodes that are not running the PATHWORKS Advanced Server. After You Install the PATHWORKS Advanced Server 5-9 After You Install the PATHWORKS Advanced Server 5.5 Setting Up External Authentication 1. Install PATHWORKS External Authentication images from the PATHWORKS for OpenVMS (Advanced Server) software kit, as described in Chapter 2, Installing the PATHWORKS Advanced Server, on the member node that is not running the PATHWORKS Advanced Server. 2. Enable external authentication on the member node. 3. Enable external authentication for host-mapped PATHWORKS Advanced Server users. For information about enabling external authentication, refer to the appropriate OpenVMS manual: o For OpenVMS Version 7.1, refer to the OpenVMS V7.1 New Features Manual. o For OpenVMS Version 7.2, refer to the OpenVMS V7.2 Guide to System Security. 5.5.2 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. 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-10 After You Install the PATHWORKS Advanced Server After You Install the PATHWORKS Advanced Server 5.5 Setting Up External Authentication 5.5.3 Configuring Externally Authenticated Client Connections By default, the PATHWORKS Advanced Server supports the processing of up to 10 simultaneous external authentication requests. You can modify this maximum to suit the 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 PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 5.6 Installing Optional Server Administration Tools The PATHWORKS Advanced Server provides optional client- based server administration tools that allow you to manage the server from Windows 95, Windows 98, 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 PATHWORKS Advanced Server 5-11 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 PATHWORKS Advanced Server. This chapter consists of the following sections: o Section 6.1, Enabling Wide Area Networking o Section 6.2, Using the LMHOSTS File for Wide Area Networking o Section 6.3, Using WINS in a Wide Area Network 6.1 Enabling Wide Area Networking The PATHWORKS Advanced Server 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. (Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for information about using the Configuration Manager.) Implementing a Wide Area Network 6-1 Implementing a Wide Area Network 6.2 Using the LMHOSTS File for Wide Area Networking 6.2 Using the LMHOSTS File for Wide Area Networking The PATHWORKS Advanced Server 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 PATHWORKS Advanced Server to participate in a Windows NT wide area network as well. Unlike a Windows NT Server, PATHWORKS 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 PATHWORKS Advanced Server, then manually insert the entries into the PATHWORKS 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 Enabling LMHOSTS Name Resolution To use LMHOSTS for name resolution, it must be enabled in the server configuration. Use the Configuration Manager when you run the PWRK$CONFIG initial configuration procedure, or run the Configuration Manager later, as described in PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 6-2 Implementing a Wide Area Network Implementing a Wide Area Network 6.2 Using the LMHOSTS File for Wide Area Networking 6.2.3 The LMHOSTS Directory You set up a wide area network by supplying the following file on all PATHWORKS Advanced Servers that are in different subnets: PWRK$LMROOT:[LANMAN]LMHOSTS. The LMHOSTS file has no file extension. 6.2.4 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 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 examples of valid node names: 1. hydra1 2. "hydra1\0X03" 3. "hydra1 \0X03" In Example 1, the node name is interpreted as uppercase (HYDRA1) and will be padded with blank characters. Implementing a Wide Area Network 6-3 Implementing a Wide Area Network 6.2 Using the LMHOSTS File for Wide Area Networking 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, 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. 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.5 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 PATHWORKS Advanced Server. The change is effective immediately and is referenced at the next lookup. 6-4 Implementing a Wide Area Network Implementing a Wide Area Network 6.2 Using the LMHOSTS File for Wide Area Networking 6.2.6 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 PATHWORKS Advanced Server is running. To close the log file, you must stop the PATHWORKS 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.3 Using WINS in a Wide Area Network You can configure the PATHWORKS Advanced Server as a WINS client. This allows the PATHWORKS Advanced Server to use WINS 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 PATHWORKS Advanced Server to use WINS, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 6.3.1 Setting up WINS Support for OpenVMS Clusters To allow clients that are configured for WINS support to use a PATHWORKS 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 PATHWORKS alias name. The following is an example of an entry for the PATHWORKS alias name alpha1_alias: alpha1_alias 16.20.240.24 When adding the static multihomed entry for the PATHWORKS alias name, you should enter the TCP/IP address of each node in the OpenVMS cluster that is running PATHWORKS 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 Implementing a Wide Area Network 6-5 Implementing a Wide Area Network 6.3 Using WINS in a Wide Area Network first node that will start PATHWORKS Advanced Server in the cluster. _____________________________________________________ For more information about adding static entries to the WINS database, refer to your WINS product documentation. 6-6 Implementing a Wide Area Network 7 ________________________________________________________________ Removing PATHWORKS Advanced Server Software This chapter describes how to remove the PATHWORKS Advanced Server software from your system. This chapter consists of the following sections: o Section 7.1, Removing the PATHWORKS Advanced Server o Section 7.2, Removing the PATHWORKS NetWare Server 7.1 Removing the PATHWORKS Advanced Server You may need to remove server software for one of the following reasons: o If the installation failed If the IVP indicates that the software installation procedure failed, you must reinstall the PATHWORKS Advanced Server software. If your system has enough free disk space, you can install the server again without deinstalling the PATHWORKS Advanced Server. If you do not have enough disk space, however, you must remove PATHWORKS Advanced Server before reinstalling it. For more information about disk space requirements, see Section 1.9.7, Step 7: Check Disk Space Requirements. o If you are upgrading If the system is running the PATHWORKS for OpenVMS (NetWare) server, the NetWare server software must be removed before you can install PATHWORKS Advanced Server. If the NetWare server is installed when you run the PATHWORKS Advanced Server installation procedure, it gives you the option of removing the NetWare server software (Section 2.3.1, Installing the PATHWORKS Advanced Server on a System with the NetWare Server). Removing PATHWORKS Advanced Server Software 7-1 Removing PATHWORKS Advanced Server Software 7.1 Removing the PATHWORKS Advanced Server Alternatively, you can manually remove the NetWare server using the procedure described in Section 7.2, Removing the PATHWORKS NetWare Server. 7.1.1 About the PATHWORKS Advanced Server Deinstallation Command Procedure You remove the PATHWORKS Advanced Server using a command procedure that is included when you install PATHWORKS Advanced Server. 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 Removes all PATHWORKS Advanced Server images, support files, and logical names that are created during the installation procedure. Optionally removes the Advanced Server data from the system. o Removes the PATHWORKS Advanced Server accounts. o Removes the NETBIOS$ACCESS OpenVMS identifier. o Removes PATHWORKS Advanced Server DECnet objects. 7.1.2 Using the PATHWORKS Advanced Server Deinstallation Procedure To start the deinstallation procedure and remove PATHWORKS Advanced Server software: 1. Ensure that you are logged in to the SYSTEM account. 2. 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. 7-2 Removing PATHWORKS Advanced Server Software Removing PATHWORKS Advanced Server Software 7.1 Removing the PATHWORKS Advanced Server 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 PATHWORKS Advanced Server[no]: Exit Do you want to Save the PATHWORKS Advanced delete the PATHWORKS Server on-disk structure, Advanced Server data including the user accounts files [no]: and share databases Remove the PATHWORKS Advanced YES Server on-disk structure, including the user accounts ________________________and_share_databases_____________________ 7.1.3 Sample PATHWORKS Advanced Server Removal Procedure This is a sample of the removal procedure for PATHWORKS Advanced Server software. This procedure shuts down all PATHWORKS V6.0B for OpenVMS servers and deletes all PATHWORKS V6.0B for OpenVMS (Advanced Server) images. Are you sure you want to deinstall PATHWORKS V6.0B for OpenVMS (Advanced Server)? [no]: YES Do you want to delete the Advanced Server data files [no]: YES Shutting down the currently running server(s)... Deleting PATHWORKS V6.0B for OpenVMS (Advanced Server) images... Deleting Advanced Server data files... Deassigning PATHWORKS V6.0B OpenVMS logical names... PATHWORKS V6.0B for OpenVMS (Advanced Server) is now deinstalled. Removing PATHWORKS Advanced Server Software 7-3 Removing PATHWORKS Advanced Server Software 7.2 Removing the PATHWORKS NetWare Server 7.2 Removing the PATHWORKS NetWare Server The PATHWORKS for OpenVMS (NetWare) software is no longer included with the PATHWORKS for OpenVMS software kit. Therefore, you must run the PATHWORKS for OpenVMS (NetWare) removal procedure before you install PATHWORKS for OpenVMS (Advanced Server). To start the deinstallation procedure and remove the PATHWORKS NetWare server: 1. Be sure you are logged in to the SYSTEM account. 2. Start the NetWare deinstallation procedure, as follows: $ @SYS$UPDATE:PWVN$DEINSTAL Table 7-2, PWVN$DEINSTAL Prompts, tells you how to respond to the prompts the NetWare server deinstallation procedure displays. 7-4 Removing PATHWORKS Advanced Server Software Removing PATHWORKS Advanced Server Software 7.2 Removing the PATHWORKS NetWare Server Table_7-2_PWVN$DEINSTAL_Prompts_________________________________ If you want the removal Enter . . . At_this_prompt_._._.____procedure_to_._._.______________________ Are you sure you want Continue YES to deinstall DIGITAL PATHWORKS V1.0H for OpenVMS (NetWare) [no][1]: Exit Do you want to delete Save the NetWare on-disk the NetWare data files structure, including the [no]: configuration Files Remove the NetWare on-disk YES structure, including the configuration files Do you want to delete Save the NetWare SYS volume the NetWare SYS Volume [no]: Remove the NetWare SYS volume YES [1]To_install_PATHWORKS_Advanced_Server,_you_must_respond_to____ this question with YES. ________________________________________________________________ 7.2.1 Sample NetWare Server Removal Procedure This is a sample of the removal procedure for DIGITAL PATHWORKS for OpenVMS (NetWare). $ @SYS$UPDATE:PWVN$DEINSTAL This procedure shuts down all PATHWORKS V1.0H for OpenVMS servers, and deletes all PATHWORKS V1.0H for OpenVMS (NetWare) images. Are you sure you want to deinstall PATHWORKS V1.0H for OpenVMS (NetWare) [no]: YES Do you want to delete the NetWare SYS Volume [no]: YES Stopping PATHWORKS for OpenVMS (NetWare) Server... Process NETBIOS stopped Process PWRK$LICENSE_R stopped Stopping IPX Daemon (NPSD)... Removing PATHWORKS Advanced Server Software 7-5 Removing PATHWORKS Advanced Server Software 7.2 Removing the PATHWORKS NetWare Server Deleting PATHWORKS for OpenVMS common images... Deleting PATHWORKS for OpenVMS NETBIOS component... Deleting PATHWORKS V1.0H for OpenVMS (NetWare) images... Deleting NetWare data files... Deleting NetWare SYS Volume... Removing PWRK$DEFAULT and PWRK$GUEST VMS accounts... Removing PATHWORKS V1.0H for OpenVMS identifiers... Removing PATHWORKS V1.0H for OpenVMS DECnet objects... Deassigning PATHWORKS V1.0H for OpenVMS logical names... PATHWORKS V1.0H for OpenVMS (NetWare) is now deinstalled. $ 7-6 Removing PATHWORKS Advanced Server Software A ________________________________________________________________ Installation and Upgrade Checklist Table A-1 summarizes the tasks that you need to perform to install and configure the PATHWORKS 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____________________ < >1. Prepare for the installation by completing all preinstallation tasks on the checklist in Section 1.9, 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 servers. 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 and TCP/IP, if needed, are running. g. Check OpenVMS cluster configuration, if installing on a cluster. (continued on next page) Installation and Upgrade Checklist A-1 Installation and Upgrade Checklist Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________ < >2. Start the installation procedure and respond to installation prompts. You may choose to install: o The complete PATHWORKS Advanced Server o The Upgrade utility only o The license server only o The PATHWORKS External Authentication software only < >3. Start the configuration procedure and respond to configuration prompts. < >4. If you are upgrading from PATHWORKS V5 for OpenVMS (LAN Manager), complete the upgrade procedure. Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for information about how to: a. Determine the role of the server b. Upgrade the server c. Upgrade OpenVMS clusters d. Create upgrade reports e. Upgrade users and groups f. Upgrade shares g. Upgrade security h. Upgrade server configuration parameters < >5. Run the Installation Verification Procedure (if you did not do so when you installed the server). < >6. Start the server (if you did not do so when you configured the server). < >7. Install Windows NT server administration tools __________(optional).___________________________________________ A-2 Installation and Upgrade Checklist B ________________________________________________________________ Sample PATHWORKS Advanced Server Installation and Configuration Procedure This appendix shows sample installation and configuration procedures for the PATHWORKS Advanced Server on an OpenVMS cluster. B.1 Sample PATHWORKS Advanced Server Installation Procedure The following example shows a sample installation dialog for the PATHWORKS Advanced Server. $ @SYS$UPDATE:VMSINSTAL PWRKV60B060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V7.1 It is 16-OCT-1998 at 15:29. 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: PWRKV60B V6.0 Beginning installation of PWRKV60B V6.0 at 15:29 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. PATHWORKS 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. PATHWORKS Advanced Server Installation and Configuration Procedure B-1 Sample PATHWORKS Advanced Server Installation and Configuration Procedure B.1 Sample PATHWORKS Advanced Server Installation Procedure Please select from the following install options: PATHWORKS V6.0B for OpenVMS (Advanced Server) PATHWORKS V6.0B for OpenVMS (Advanced Server) license server (only) External Authentication images (only) * Do you want to install the complete PATHWORKS V6.0B for OpenVMS [NO]? YES The following components will be installed: PATHWORKS V6.0B for OpenVMS (Advanced Server) 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]? NOTE ---- Because this kit provides a new streams execlet for NetBEUI and TCP/IP, you MUST reboot all nodes in the cluster that are now running or have run PATHWORKS to complete installation of PATHWORKS. If you do not reboot the nodes at this time, you must remember to reboot them later before starting PATHWORKS. To complete the installation of this product, you should reboot the system. If it is not convenient to reboot at this time, then enter NO to the following question. If you enter NO, the installation procedure will continue. * Will you allow a system shutdown after this product is installed [YES]? NO %PWRKV60B-I-VERSION, Checking for OpenVMS version 7.1, or later... * Do you want to run the IVP after the installation is finished [YES]? * Do you want to purge files replaced by this installation [YES]? %PWRK-I-FREEBLKS, Checking for 144500 free blocks User Accounts and User Identification Codes (UICs) -------------------------------------------------- PATHWORKS for OpenVMS creates two OpenVMS accounts: a default account, PWRK$DEFAULT, and a guest account, PWRK$GUEST. The default UIC group number for both these new accounts depends on the following: o If you are installing the server for the first time, the default is the first unused UIC group number, starting with 360. o If there is an existing account PCFS$ACCOUNT, the default is the UIC group number associated with PCFS$ACCOUNT. B-2 Sample PATHWORKS Advanced Server Installation and Configuration Procedure PATHWORKS Advanced Server Installation and Configuration Procedure B.1 Sample PATHWORKS Advanced Server Installation Procedure 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. PATHWORKS Advanced Server Installation and Configuration Procedure B-3 Sample PATHWORKS Advanced Server Installation and Configuration Procedure B.1 Sample PATHWORKS 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 PATHWORKS for OpenVMS will continue. %PWRK-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 C ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands %PWRK-I-SPECIFY, Specifying target directories for the provided files %PWRK-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 PATHWORKS (Advanced Server) 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 PATHWORKS V6.0B for OpenVMS (Advanced Server) %PWRK-I-NORMAL, IVP completed successfully Installation of PWRKV60B V6.0 completed at 15:36 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRKV60B060.VMI_DATA VMSINSTAL procedure done at 15:36 B-4 Sample PATHWORKS Advanced Server Installation and Configuration Procedure PATHWORKS Advanced Server Installation and Configuration Procedure B.2 Sample PATHWORKS Advanced Server Configuration Procedure B.2 Sample PATHWORKS Advanced Server Configuration Procedure The following example shows a sample configuration dialog for the PATHWORKS Advanced Server. $ @SYS$UPDATE:PWRK$CONFIG PATHWORKS V6.0B for OpenVMS (Advanced Server) Configuration Procedure PATHWORKS 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. Press RETURN to continue: If this OpenVMS cluster has multiple system disks, make sure that all nodes on which you plan to run PATHWORKS: o Use the same disk device to store and access PATHWORKS data files. o Share the same SYSUAF.DAT file. In each system disk's startup file, define a system logical name that points all nodes to the shared SYSUAF.DAT file. For example: $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM Enter disk device name where PATHWORKS data files will be stored [SYS$SYSDEVICE:]: DISK$PWRK: Creating PATHWORKS directory tree on DISK$PWRK:... Creating Advanced Server directory tree... Copying client files to Advanced Server directory tree... Creating PATHWORKS Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT ... PATHWORKS Advanced Server Installation and Configuration Procedure B-5 Sample PATHWORKS Advanced Server Installation and Configuration Procedure B.2 Sample PATHWORKS Advanced Server Configuration Procedure Changing the server configuration parameters will allow you to modify this server's client capacity and select the transports to be used. COBRAZ is currently configured to + support 20 PC clients + use the following transport(s): DECnet 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. 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 ... PATHWORKS V6.0 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. PATHWORKS OpenVMS cluster alias: COBRAZ_ALIAS 8. Server announce comment: PATHWORKS V6.0B for OpenVMS (Advanced Server) Enter item number, or RETURN to use these values [DONE]: Saving parameters ... Checking the access control list file ... Successfully created new ACL store Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB. ... New sharefile has been created. ADMIN$ added IPC$ added PWUTIL added B-6 Sample PATHWORKS Advanced Server Installation and Configuration Procedure PATHWORKS Advanced Server Installation and Configuration Procedure B.2 Sample PATHWORKS 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. If this server is to join an Advanced Server domain, the Administrator network account password should be the same as the password to the domain's existing Administrator network account. The network account password can be up to 14 characters long. Enter Administrator network account password: Re-enter to verify password: Changing password for Administrator network account... Checking system resources... The current system configuration for COBRAZ will support 20 PC clients. PATHWORKS is configured to use DECnet. To automatically start PATHWORKS V6.0B 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). Before starting PATHWORKS V6.0B for OpenVMS on this system, be sure to execute @SYS$UPDATE:PWRK$CONFIG on each node that will run PATHWORKS. Do you want to start PATHWORKS V6.0B for OpenVMS on node COBRAZ now [yes]: NO $ PATHWORKS Advanced Server Installation and Configuration Procedure B-7 C ________________________________________________________________ Sample Standalone License Server Installation and Configuration Procedure 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 PWRKV60B060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V7.1 It is 16-OCT-1998 at 16:08. 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: PWRKV60B V6.0 Beginning installation of PWRKV60B V6.0 at 16:08 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. PATHWORKS 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. Standalone License Server Installation and Configuration Procedure C-1 Sample Standalone License Server Installation and Configuration Procedure C.1 Sample Standalone License Server Installation Procedure Please select from the following install options: PATHWORKS V6.0B for OpenVMS (Advanced Server) PATHWORKS V6.0B for OpenVMS (Advanced Server) license server (only) External Authentication images (only) * Do you want to install the complete PATHWORKS V6.0B for OpenVMS [NO]? NO * Do you want to install only the PATHWORKS license server [NO]? YES * Do you want to install only the External Authentication images [NO]? NO The following components will be installed: PATHWORKS V6.0B license server 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]? %PWRKV60B-I-VERSION, Checking for OpenVMS version 7.1, or later... * Do you want to run the IVP after the installation is finished [YES]? * Do you want to purge files replaced by this installation [YES]? %PWRKV60B-I-FREEBLKS, Checking for 144500 free blocks All questions have been answered. The installation of PATHWORKS for OpenVMS will continue. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %PWRKV60B-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRKV60B-I-DCLCMDS, Installing PATHWORKS DCL commands %PWRKV60B-I-SPECIFY, Specifying target directories for the provided files %PWRKV60B-I-OBSOLETE, Deleting obsolete files %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... © Digital Equipment Corporation 1998. All rights reserved. Starting Installation Verification Procedure for PATHWORKS V6.0B for OpenVMS (Advanced Server) %PWRK-I-NORMAL, IVP completed successfully Installation of PWRKV60B V6.0 completed at 19:33 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRKV60B060.VMI_DATA VMSINSTAL procedure done at 19:34 C-2 Sample Standalone License Server Installation and Configuration Procedure Standalone License Server Installation and Configuration Procedure C.2 Sample Standalone License Server Configuration Procedure C.2 Sample Standalone License Server Configuration Procedure The following example shows a sample PATHWORKS Advanced Server configuration procedure for the standalone license server. $ @SYS$UPDATE:PWRK$CONFIG PATHWORKS V6.0B for OpenVMS (Advanced Server) Configuration Procedure PATHWORKS 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. Press RETURN to continue: If this OpenVMS cluster has multiple system disks, make sure that all nodes on which you plan to run PATHWORKS: o Use the same disk device to store and access PATHWORKS data files. o Share the same SYSUAF.DAT file. In each system disk's startup file, define a system logical name that points all nodes to the shared SYSUAF.DAT file. For example: $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM Enter disk device name where PATHWORKS data files will be stored [SYS$SYSDEVICE:]: DISK$PWRK: Creating PATHWORKS directory tree on DISK$PWRK:... The PATHWORKS license server can serve PATHWORKS licenses for Advanced Server clients over DECnet, NetBEUI, and TCP/IP. The Advanced Server file server does not need to be running for the license server to operate. Standalone License Server Installation and Configuration Procedure C-3 Sample Standalone License Server Installation and Configuration Procedure C.2 Sample Standalone License Server Configuration Procedure Do you want to serve PATHWORKS licenses over DECnet [yes]: Do you want to serve PATHWORKS licenses over NetBEUI [no]: YES Do you want to serve PATHWORKS licenses over TCP/IP [no]: YES Do you want to start the PATHWORKS license server now [yes]: NO C-4 Sample Standalone License Server Installation and Configuration Procedure Standalone License Server Installation and Configuration Procedure C.2 Sample Standalone License Server Configuration Procedure To automatically start the PATHWORKS license server 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). $ Standalone License Server Installation and Configuration Procedure C-5 D ________________________________________________________________ Upgrade Utility Installation This appendix shows a sample installation of the Upgrade utility. D.1 Installing the Upgrade Utility As a first step in upgrading a system that is running a previously released version of PATHWORKS Advanced Server, you can install the Upgrade utility without installing the server. Doing this allows you to run the PATHWORKS V5 for OpenVMS (LAN Manager) server while performing the upgrade procedure, avoiding any interruption of services to your users. If you install the Upgrade utility only, the on-disk structure and datafile format are not changed, and the PATHWORKS V5 for OpenVMS (LAN Manager) executables are not replaced. When you execute the installation procedure on a system that is running PATHWORKS V5 for OpenVMS (LAN Manager), the procedure offers you the option of installing the Upgrade utility only. To install the Upgrade utility only, select this option. ________________________Note ________________________ When you install the Upgrade utility only, you cannot run the Installation Verification Procedure (IVP); therefore, the prompt asking whether you want to run the IVP is not displayed during the installation. _____________________________________________________ Upgrade Utility Installation D-1 Upgrade Utility Installation D.2 Sample Upgrade Utility Installation Procedure D.2 Sample Upgrade Utility Installation Procedure The following example shows a sample procedure for installation of the Upgrade utility only. $ @SYS$UPDATE:VMSINSTAL PWRKV60B060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V7.1 It is 22-OCT-1998 at 15:14. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? y The following products will be processed: PWRKV60B V6.0 Beginning installation of PWRKV60B V6.0 at 15:14 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. PATHWORKS 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. You have the option to install only the PATHWORKS for OpenVMS Advanced Server upgrade utility, which upgrades your server environment from V5 to V6. If you choose to install only the upgrade utility, no file server components will be installed. The upgrade utility allows you to continue to run your V5 servers while you perform the upgrade. You may install the Advanced Server after your server environment has been upgraded. However, if you choose not to install the upgrade utility only, the installation will proceed with the regular kit installation. You may invoke the upgrade utility after the installation by typing @SYS$UPDATE:PWRK$V6UPGRADE. The following question allows you to install only the upgrade utility: D-2 Upgrade Utility Installation Upgrade Utility Installation D.2 Sample Upgrade Utility Installation Procedure * Do you want to install the upgrade utility only [NO]? YES %PWRK-I-VERSION, Checking for OpenVMS version 7.1, or later... * Do you want to purge files replaced by this installation [YES]? %PWRK-I-FREEBLKS, Checking for 30000 free blocks %VMSINSTAL-I-RESTORE, Restoring product save set C ... Upgrade Utility Installation D-3 Upgrade Utility Installation D.2 Sample Upgrade Utility Installation Procedure Next Step --------- To upgrade the server, enter the following command to invoke the server upgrade utility: $ @SYS$UPDATE:PWRK$V6UPGRADE For information about the upgrade utility, see the PATHWORKS (Advanced Server) Server Migration Guide. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... © Digital Equipment Corporation 1998. All rights reserved. Installation of PWRKV60B V6.0 completed at 15:15 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060B060.VMI_DATA VMSINSTAL procedure done at 15:16 $ D-4 Upgrade Utility Installation E ________________________________________________________________ Sample External Authentication Installation Procedure This appendix shows a sample procedure for installing the external authentication software only. E.1 Sample External Authentication Software Installation Procedure The following example shows a sample installation dialog for the external authentication software only. OpenVMS AXP Software Product Installation Procedure V7.1 It is 8-NOV-1998 at 19:48. 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: PWRKV60B V6.0 Beginning installation of PWRKV60B V6.0 at 19:48 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. PATHWORKS 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. Sample External Authentication Installation Procedure E-1 Sample External Authentication Installation Procedure E.1 Sample External Authentication Software Installation Procedure Please select from the following install options: PATHWORKS V6.0B for OpenVMS (Advanced Server) PATHWORKS V6.0B for OpenVMS (Advanced Server) license server (only) External Authentication images (only) * Do you want to install the complete PATHWORKS V6.0B for OpenVMS [NO]? * Do you want to install only the PATHWORKS license server [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]? %PWRKV60B-I-VERSION, Checking for OpenVMS version 7.1, or later... * Do you want to run the IVP after the installation is finished [YES]? * Do you want to purge files replaced by this installation [YES]? %PWRKV60B-I-FREEBLKS, Checking for 144500 free blocks All questions have been answered. The installation of PATHWORKS for OpenVMS will continue. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %PWRKV60B-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRKV60B-I-SPECIFY, Specifying target directories for the provided files %PWRKV60B-I-OBSOLETE, Deleting obsolete files %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... © Digital Equipment Corporation 1998. All rights reserved. Starting Installation Verification Procedure for PATHWORKS V6.0B for OpenVMS (Advanced Server) %PWRK-I-NORMAL, IVP completed successfully Installation of PWRKV60B V6.0 completed at 19:52 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRKV60B060.VMI_DATA Enter the products to be processed from the next distribution volume set. VMSINSTAL procedure done at 19:54 E-2 Sample External Authentication Installation Procedure F ________________________________________________________________ PATHWORKS Advanced Server Files and On-Disk Structure This appendix includes the following sections: o Section F.1, PATHWORKS Advanced Server Files, describes the files that are created during the installation procedure. o Section F.2, PATHWORKS Advanced Server On-Disk Structure, shows the on-disk structure of the PATHWORKS Advanced Server. F.1 PATHWORKS Advanced Server Files Table F-1, Files Installed for the PATHWORKS Advanced Server, describes the files created during the installa- tion of the PATHWORKS Advanced Server. Table_F-1_Files_Installed_for_the_PATHWORKS_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 (continued on next page) PATHWORKS Advanced Server Files and On-Disk Structure F-1 PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$HELP:PWRK$ADMIN_CFG.HLB Configuration Manager help file SYS$HELP:PWRKV60B060.RELEASE_NOTES PATHWORKS Advanced Server release notes SYS$HELP:PWRK$V6UPGRADE.HLB Upgrade utility help file SYS$HELP:PCDISKHLP.HLB DOS File Maintenance utility 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_GENERIC.TLB Generic device control library 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 (continued on next page) F-2 PATHWORKS Advanced Server Files and On-Disk Structure PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$LIBRARY:PWRK$DEVCTL_LG31.TLB LG31 device control library SYS$LIBRARY:PWRK$DEVCTL_LN03R.TLB LN03R 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 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_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 (continued on next page) PATHWORKS Advanced Server Files and On-Disk Structure F-3 PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$LIBRARY:PWRK$DEVCTL_LN03P.TLB LN03 PLUS device control library SYS$LIBRARY:PWRK$DEVCTL_PROPRINTER.TLProprinter device control library SYS$LIBRARY:PWRK$DEVCTL_SILENTWRITER.SilentWriter device control library 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$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 System Dump Analyzer SYS$LIBRARY:PWRK$STREAMSSHR_V7.EXE Streams shareable image SYS$LIBRARY:PWRK$WINLIBSHR.EXE PATHWORKS 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 (continued on next page) F-4 PATHWORKS Advanced Server Files and On-Disk Structure PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ 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 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 PATHWORKS 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 [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) PATHWORKS Advanced Server Files and On-Disk Structure F-5 PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ 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 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$CHANGEV5ROLE.EXE V5 to V6 Upgrade utility (continued on next page) F-6 PATHWORKS Advanced Server Files and On-Disk Structure PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$SYSTEM:PWRK$CHDOMAIN.EXE Server configuration tool SYS$SYSTEM:PWRK$DELETEACE.EXE File ACE utility SYS$SYSTEM:PWRK$ELFREAD.EXE Event log file reader utility 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 [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) PATHWORKS Advanced Server Files and On-Disk Structure F-7 PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$SYSTEM:PWRK$NETEVENT.EXE Debugging utility (unsupported) SYS$SYSTEM:PWRK$PWMON.EXE[1] Host-based monitor utility SYS$SYSTEM:PWRK$RMACL.EXE Server configuration tool 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 [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. [2]This file is deleted after you configure the server. (continued on next page) F-8 PATHWORKS Advanced Server Files and On-Disk Structure PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ 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 PATHWORKS Advanced Server removal command procedure SYS$UPDATE:PWRK$GETPARAM.COM Command procedure that gets a parameter from PWRK.INI SYS$UPDATE:PWRK$INSTALL_COMMANDS.COM Command procedure that installs server DCL commands SYS$UPDATE:PWRK$LICENSE_CONFIG.COM License server configura- tion command procedure SYS$UPDATE:PWRK$SETINI.COM Command procedure that updates file server 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 [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. [2]This file is deleted after you configure the server. (continued on next page) PATHWORKS Advanced Server Files and On-Disk Structure F-9 PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$LIBRARY:PWRK$CMT_LM.EXE User interface to the Configurator, Monitor, and Tuner utility SYS$LIBRARY:PWRK$LMAPISHR.EXE PATHWORKS Advanced Server shareable image SYS$LIBRARY:PWRK$LMRPCAPISHR.EXE PATHWORKS Advanced Server shareable image SYS$LIBRARY:PWRK$LMRPCSHR.EXE PATHWORKS Advanced Server shareable image SYS$LIBRARY:PWRK$LMRPCXNPSHR.EXE PATHWORKS Advanced Server shareable image SYS$LIBRARY:PWRK$LMTASKSHR.EXE PATHWORKS Advanced Server shareable image SYS$LIBRARY:PWRK$MGTLIBSHR.EXE PATHWORKS Advanced Server shareable image SYS$LIBRARY:PWRK$NBLIB_DECNET.EXE PATHWORKS Advanced Server network interface to DECnet SYS$LIBRARY:PWRK$NBLIB_NETBEUI.EXE PATHWORKS Advanced Server network interface to NetBEUI SYS$LIBRARY:PWRK$NBLIB_TCPIP.EXE PATHWORKS 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 PATHWORKS Advanced Server daemon (continued on next page) F-10 PATHWORKS Advanced Server Files and On-Disk Structure PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$STARTUP:PWRK$LMMCP_START.COM Command procedure that runs the PATHWORKS Advanced Server controller SYS$STARTUP:PWRK$LMSRV_START.COM Command procedure that runs the PATHWORKS 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 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 PATHWORKS Advanced Server groups database SYS$SYSTEM:PWRK$CHUSER.EXE[1] Standalone utility that manages the PATHWORKS Advanced Server user accounts database SYS$SYSTEM:PWRK$LMBROWSER.EXE PATHWORKS Advanced Server browser image SYS$SYSTEM:PWRK$LMDMN.EXE PATHWORKS Advanced Server daemon SYS$SYSTEM:PWRK$LMMCP.EXE PATHWORKS Advanced Server controller [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) PATHWORKS Advanced Server Files and On-Disk Structure F-11 PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$SYSTEM:PWRK$LMSHARE.EXE[1] Standalone utility that manages the PATHWORKS Advanced Server shares database SYS$SYSTEM:PWRK$LMSRV.EXE PATHWORKS Advanced Server SYS$SYSTEM:PWRK$MANAGER.EXE ADMINISTER command line user interface utility SYS$SYSTEM:PWRK$MODAL.EXE[1] Standalone utility that manages the PATHWORKS Advanced Server modals database SYS$SYSTEM:PWRK$SHOWINI.EXE[1] Utility that displays file server parameters SYS$SYSTEM:PWRK$START_PRINTERS.EXE Utility that starts printer queues and printer destinations SYS$UPDATE:PWRK$LANMAN.SAV[2] BACKUP saveset for the initial PATHWORKS Advanced Server directory tree SYS$UPDATE:PWRK$LICENSE.SAV PATHWORKS client license saveset SYS$UPDATE:PWRK$LMCONFIG.COM Command procedure that sets up the initial PATHWORKS Advanced Server directory tree SYS$UPDATE:PWRK$ROLLBACK.COM Command procedure for restoring the V5 environment SYS$UPDATE:PWRK$V6UPGRADE.EXE V5 to V6 Upgrade utility [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. [2]This file is deleted after you configure the server. (continued on next page) F-12 PATHWORKS Advanced Server Files and On-Disk Structure PATHWORKS Advanced Server Files and On-Disk Structure F.1 PATHWORKS Advanced Server Files Table F-1 (Cont.) Files Installed for the PATHWORKS Advanced __________________Server________________________________________ File_________________________________Description________________ SYS$UPDATE:PWRK$V6UPGRADE.COM V5 to V6 upgrade command procedure SYS$UPDATE:PWRK$PWUTIL.SAV[2] BACKUP saveset for PATHWORKS client-based utilities [2]This_file_is_deleted_after_you_configure_the_server._________ ________________________________________________________________ F.2 PATHWORKS Advanced Server On-Disk Structure Figure F-1, PATHWORKS Advanced Server On-Disk Structure Diagram, shows the PATHWORKS Advanced Server on-disk structure. Note that only a portion of the substructure is shown. PATHWORKS Advanced Server Files and On-Disk Structure F-13 PATHWORKS Advanced Server Files and On-Disk Structure F.2 PATHWORKS Advanced Server On-Disk Structure Figure F-1 PATHWORKS Advanced Server On-Disk Structure Diagram pwrk$commonroot, pwrk$lmroot | |___lanman | | ---.accounts | ---.datafiles | ---.debug | ---.domains | ---.logs | ---.repl | ---.samsave | ---.shares | ---.upgrade | |___license | |___logs | |___params | |___perfdata | |___print | |___section | |___spool | |___temp F-14 PATHWORKS Advanced Server Files and On-Disk Structure G ________________________________________________________________ PATHWORKS Advanced Server Logical Names Table G-1 describes the logical names that are created when you configure or start the PATHWORKS Advanced Server. Table_G-1_PATHWORKS_Advanced_Server_Logical_Names_________ Logical_Name__________Description_________________________ PWRK$ACME_MODULE System-specific external authen- tication software (either VAX or Alpha). PWRK$ADDON_LIBRARY Location of file system shareable images PWRK$COMMON Top-level directory for PATHWORKS Advanced Server PWRK$COMMONROOT[1] Root of the PATHWORKS Advanced Server common directory tree PWRK$CSSHR Common services module PWRK$KNBDAEMON_ TCP/IP device DEVICE PWRK$LANMAN PATHWORKS Advanced Server area PWRK$LANMAN_STARTED Indicates whether the PATHWORKS Advanced Server has been started. PWRK$LICENSE PATHWORKS Advanced Server license area PWRK$LMDATAFILES PATHWORKS Advanced Server data files area [1]This_logical_name_requires_that_you_specify_the________ directory with it. (continued on next page) PATHWORKS Advanced Server Logical Names G-1 PATHWORKS Advanced Server Logical Names Table_G-1_(Cont.)_PATHWORKS_Advanced_Server_Logical_Names_ Logical_Name__________Description_________________________ PWRK$LMDEBUG Area where trace files are written PWRK$LMDOMAINS PATHWORKS Advanced Server domain area PWRK$LMLOGS PATHWORKS Advanced Server log file area PWRK$LMROOT[1] Root of the PATHWORKS Advanced Server directory tree PWRK$LMUPGRADE PATHWORKS Advanced Server upgrade area PWRK$LMMSGFILES PATHWORKS Advanced Server message files area PWRK$LMREPLEXPORT Export replication files area PWRK$LMREPLIMPORT Import replication files area PWRK$LMSAMSAVE SAM database backup area PWRK$LMSAMSAVEX SAM database backup area PWRK$LOADSTREAMS Logical for LoadStreams image PWRK$LOGS Common log file area PWRK$NETBEUI_DEVICE NetBEUI device PWRK$PARAMS Parameter area PWRK$PCFSDRIVER PCFS driver PWRK$PCIDRIVER PCI driver PWRK$PERFDATA PATHWORKS monitor performance data directory PWRK$PRINT PATHWORKS Advanced Server printer database directory PWRK$ROOT Top-level directory for PATHWORKS Advanced Server PWRK$SHARED_IMAGES Indicates whether shared images have been loaded [1]This_logical_name_requires_that_you_specify_the________ directory with it. (continued on next page) G-2 PATHWORKS Advanced Server Logical Names PATHWORKS Advanced Server Logical Names Table_G-1_(Cont.)_PATHWORKS_Advanced_Server_Logical_Names_ Logical_Name__________Description_________________________ PWRK$STREAMSOS System-specific streams images PWRK$STREAMSSHR System-specific streams sharable image PWRK$SECTION Section file area PWRK$SPOOL Spool area PWRK$TEMP Temporary PATHWORKS Advanced Server files PWRK$VERSION__________File_server_version_number__________ PATHWORKS Advanced Server Logical Names G-3 ________________________________________________________________ Index A Configuration procedure ___________________________ changing default settings Administrator account , 3-13 password on, 3-7 for Advanced Server, 3-1 Alerter service preparing for the description of, 3-6 Advanced Server, 3-3 alias, 3-7 prerequisites, 3-3 Automatic shutdown responding to prompts, of file server, 5-7 3-8, 4-4 sample script for B__________________________ PATHWORKS Advanced BACKUP command, 1-11 Server, B-5 sample script for C__________________________ standalone license Checklist server, C-3 summary, A-1 starting, 3-8 Client-based server starting server during, administration tools, 3-8, 3-12 5-11 starting standalone Client software license server during, LAN Manager, 1-8 4-6 Clusters D See OpenVMS clusters ___________________________ Computer name, 3-7 Data loss SCSNODE parameter and, preventing, 1-11 1-14 DECnet (Phase IV) Configuration (Advanced checking status, 1-17 Server) DECnet-Plus description of, 3-4 checking status, 1-17 Configuration Manager DECnet transport, 1-8 running after running during configuration, 3-4 configuration, 1-17 Index-1 DECnet transport (cont'd) status of, 1-17 G__________________________ DECprint Supervisor GBLPAGES parameter software, 1-2 checking and defining, installing, 1-3 1-12 Deinstallation procedure GBLSECTIONS parameter description of, 7-2 checking and defining, guidelines for, 7-1 1-13 Deinstalling PATHWORKS Advanced Server H__________________________ , 7-2 Hardware requirements, PATHWORKS for OpenVMS 1-7, 1-10 (NetWare), 7-4 Device name, 2-3 Disk space I__________________________ determining, 1-11 Installation kit requirements, 1-11 contents of, 2-2 Domain name, 3-6 Installation procedure, 2-1 E__________________________ description of, 2-1 External authentication files created by, F-1 network, 5-10 interrupting, 2-7 setting up OpenVMS logical names created by, clusters, 5-9 G-1 External authentication prerequisites, 2-3 software questions in, 2-6 installing, 2-20 responding to prompts, sample installation 2-7 script, E-1 sample script for separate installation, external authentication 2-5 software, E-1 sample script for F__________________________ PATHWORKS Advanced Files Server, B-1 created by installing sample script for PATHWORKS Advanced standalone license Server, F-1 server, C-1 File servers sample script for Upgrade NetWare, 1-2 utility, D-2 starting, 5-3 standalone license server stopping, 5-7 , 4-1 starting, 2-5 Index-2 Installation Verification Procedure N__________________________ See IVP NetBIOS name resolution IVP using LMHOSTS for, 6-2 restriction when using WINS server for, installing Upgrade 6-5 utility only, D-1 Netlogon service, 3-6 running after NetWare server installation, 5-3 See PATHWORKS for OpenVMS running automatically, (NetWare) 2-15 Network transport K requirements, 1-8 ___________________________ Kit contents O__________________________ checking, 1-10 OpenVMS cluster alias, 3-7 L OpenVMS clusters ___________________________ checking configuration, License server, 3-5 1-9 configuration procedure, cluster alias, 3-15 4-1 configuring nodes in, 3-2 installation procedure, disk device for PATHWORKS 4-1 Advanced Server files, standalone installation, 3-3 2-4, 2-19 installation in, 1-19 Licensing loading client license requirements, 1-3 PAKs on, 4-2 LMHOSTS loading PAKs on, 1-4 configuring to use, 6-2 PATHWORKS cluster alias name resolution, 3-5 for, 3-7 Logical names running license server created by PATHWORKS on, 1-4, 4-1 Advanced Server sample installation on, installation, G-1 C-1 startup procedure, 5-4 sample standalone configuration procedure M__________________________ , C-3 Memory requirements, 1-8 server role in, 3-7 setting up external authentication, 5-9 starting server in, 5-6 starting standalone license server in, 4-7 Index-3 OpenVMS clusters (cont'd) PWRK$DEINSTAL procedure WINS setup for, 6-5 See Deinstallation Operating system procedure requirements, 1-8 PWVN$STARTUP.COM Optional software, 5-11 description of, 5-4 P__________________________ Q__________________________ Part listing Queue manager checking, 1-10 running during PATHWORKS Advanced Server configuration, 1-16 configuring, 3-1 starting, 1-16 files installed for, F-1 installing, 2-2 R__________________________ kit contents, 2-2 Release notes, 1-11, 2-3, logical names, G-1 2-8 sample deinstallation in SYS$HELP: area, 1-6 procedure, 7-3 printing, 1-6 sample installation and Required hardware, 1-7 configuration, B-5 Required software, 1-8 starting, 5-5 Requirements starting during disk space, 1-11 configuration, 3-8, hardware, 1-7, 1-10 3-12 licensing, 1-3 PATHWORKS cluster alias, memory, 1-8 3-7 software, 1-8, 1-10 PATHWORKS for OpenVMS (NetWare), 1-2, 2-18 S__________________________ removal procedure, 7-4 SCSNODE sample deinstallation name, 3-7 procedure, 7-5 parameter definition, Post-installation tasks, 1-14 5-1 Server Pre-installation tasks, on-disk structure, F-13 2-3 Server administration tools checklist, 1-8 installing, 5-11 PROCSECTCNT parameter Server announce comment, checking and defining, 3-7 1-13 SHOW QUEUE/MANAGER command, Product identifier, 2-3 1-16 PWRK$CONFIG procedure Shutdown procedure See Configuration for file server, 5-7 procedure Index-4 Software requirements, SYSMAN utility 1-8, 1-10 using STARTUP, 5-7 Standalone license server, SYSTEM account 1-4, 4-1 logging in to, 1-10 sample installation and System disk configuration procedure changing the, 3-3 , C-1 space needed for starting during installation, 1-11 configuration, 4-6 specifying the, 3-3 startup, 4-6 System parameters Starting checking and defining, PATHWORKS Advanced Server 1-12 , 5-5 System shutdown PATHWORKS Advanced Server file server shutdown and, automatically, 5-6 5-7 PATHWORKS Advanced Server System startup during configuration, troubleshooting, 5-4 3-8 System startup file PATHWORKS Advanced Server editing, 5-6 in OpenVMS clusters, T 5-6 ___________________________ PATHWORKS Advanced Server Task summary, A-1 manually, 5-5 TCP/IP, 1-8 standalone license server status of, 1-18 , 4-6 Timesource service standalone license server description of, 3-6 automatically, 4-7 Time zone standalone license server checking setting, 1-16 during configuration, Transports, 3-4 4-6 selecting during standalone license server configuration, 3-4 in a cluster, 4-7 U standalone license server ___________________________ manually, 4-7 Upgrade utility, D-1 START/QUEUE/MANAGER command Upgrading PATHWORKS V5 for , 1-16 OpenVMS (LAN Manager), STARTUP 2-19 in SYSMAN utility, 5-7 Startup procedure for file server, 5-4 SYLOGIN.COM conditionalizing, 5-4 Index-5 See Installation V__________________________ procedure VMSINSTAL procedure W__________________________ Wide area domains setting up, 6-1 Windows NT server administration tools installing, 5-11 WINS configuring to use, 6-5 setup for OpenVMS clusters, 6-5 Index-6