DIGITAL_PATHWORKS_for_OpenVMS_________________ Server Installation and Configuration Guide AA-R6G1A-TE August 1997 This guide explains how to install and configure all of the components of DIGITAL PATHWORKS for OpenVMS (Advanced Server) software including the Advanced Server, the NetWare server, the license server, and the Upgrade utility. Revision/Update Information: This guide supersedes PATHWORKS for OpenVMS Server Installation and Upgrade Guide, AA-LB63G-TE. Operating System: DIGITAL OpenVMS V7.1 Software Version: DIGITAL PATHWORKS V6 for OpenVMS (Advanced Server) DIGITAL PATHWORKS V1.0G for OpenVMS (NetWare) Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Printing, May 1988 Revised, August 1997 Digital Equipment 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 Digital Equipment Corporation or an authorized sublicensor. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation and other parties. © Digital Equipment Corporation 1988, 1997. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha, DEC, DEClaser, DECnet-Plus, DECprint, DIGITAL, LA50, LN03, LN03 PLUS, OpenVMS, PATHWORKS, VAX, and the DIGITAL logo. The following are third-party trademarks: AT&T is a registered trademark of American Telephone and Telegraph Corporation. Apple and Macintosh are registered trademarks of Apple Computer, Inc. Epson is a registered trademark of Seiko Epson Kabushiki Kaisha. Hewlett-Packard, HP, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company. IBM, OS/2, and ProPrinter are registered trademarks of International Business Machines Corporation. Intel is a registered trademark of Intel Corporation. Microsoft, MS-DOS, Windows, and Windows 95 are registered trademarks and Windows NT is a trademark of Microsoft Corporation. NetWare and Novell are registered trademarks of Novell, Inc. PostScript is a registered trademark of Adobe Systems Incorporated. SilentWriter is a registered trademark of NEC Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. Xerox is a trademark of Xerox Corporation. X/Open is a trademark of X/Open Company Limited. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. xi 1 Before You Install DIGITAL PATHWORKS for OpenVMS About DIGITAL PATHWORKS for OpenVMS Servers........ 1-1 Installing DIGITAL DECprint Software............... 1-2 About Licensing.................................... 1-3 License requirements............................... 1-3 About the license server........................... 1-3 For more licensing information..................... 1-4 Reading the Release Notes.......................... 1-4 About the release notes............................ 1-4 How to access the release notes.................... 1-5 Using the Summary Checklist........................ 1-6 What You Need...................................... 1-7 Hardware requirements.............................. 1-7 Software Requirements.............................. 1-7 PATHWORKS Advanced Server client software.......... 1-7 NetWare client software............................ 1-8 Memory requirements................................ 1-8 Preinstallation Tasks.............................. 1-8 Step 1: Check the part listing..................... 1-9 Step 2: Check the network hardware................. 1-10 Step 3: Check the required software................ 1-10 Step 4: Log in to the SYSTEM account............... 1-10 Step 5: Back up the system......................... 1-10 Step 6: Print and read the Release Notes........... 1-11 Step 7: Check disk space requirements.............. 1-11 Step 8: Check system parameters.................... 1-12 Step 9: Check the queue manager.................... 1-15 Step 10: Check Time Zone and TDF................... 1-16 Step 11: Check DECnet status....................... 1-16 iii Step 12: Check TCP/IP status....................... 1-18 OpenVMS Cluster Considerations..................... 1-18 Step 13: Check OpenVMS cluster configuration....... 1-18 Next Step.......................................... 1-19 2 Installing DIGITAL PATHWORKS for OpenVMS About the Installation Procedure................... 2-1 What is VMSINSTAL?................................. 2-1 VMSINSTAL installation kit......................... 2-2 What VMSINSTAL does................................ 2-2 Determining What Software to Install............... 2-2 Installing the Server.............................. 2-4 Before you start VMSINSTAL......................... 2-4 How to start VMSINSTAL............................. 2-6 How installation questions work.................... 2-8 How to interrupt the installation.................. 2-8 How to respond to prompts.......................... 2-8 Next Steps......................................... 2-18 What to do next.................................... 2-18 Install optional server administration tools....... 2-19 3 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server About the PATHWORKS Advanced Server Configuration Procedure.......................................... 3-1 What is the configuration procedure?............... 3-2 What the configuration procedure does.............. 3-2 Before You Start the PATHWORKS Advanced Server Configuration Procedure............................ 3-3 How to Start the PATHWORKS Advanced Server Configuration Procedure............................ 3-9 How to Respond to PATHWORKS Advanced Server Configuration Prompts.............................. 3-9 How to Change PATHWORKS Advanced Server Configuration Default Settings..................... 3-13 Selecting the PATHWORKS Advanced Server Network Device............................................. 3-16 Next Steps......................................... 3-17 iv 4 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server About the NetWare Configuration Procedure.......... 4-1 What is the configuration procedure?............... 4-1 What the configuration procedure does.............. 4-2 When to configure the server....................... 4-2 NetWare Configuration Information.................. 4-2 About network numbers.............................. 4-3 Types of network numbers........................... 4-3 Types of external networks......................... 4-4 Number and types of networks you can configure..... 4-4 About Token Ring and FDDI Support.................. 4-4 Running the NetWare Configuration Procedure........ 4-5 When to run the configuration procedure............ 4-5 How to run the configuration procedure............. 4-5 How configuration questions work................... 4-6 How to get online help............................. 4-6 How to interrupt the configuration................. 4-6 How to respond to prompts.......................... 4-6 How to confirm your answers........................ 4-12 Reconfiguring the NetWare Server................... 4-12 How to reconfigure the server...................... 4-12 New configuration value location................... 4-13 5 Configuring and Starting the Standalone License Server Before You Begin to Configure the Standalone License Server..................................... 5-2 Configuring the Standalone License Server.......... 5-2 Configuring the PATHWORKS Advanced Server Transports......................................... 5-3 How to Respond to PATHWORKS Advanced Server Configuration Prompts.............................. 5-4 Configuring the NetWare Transport.................. 5-6 How to Respond to NetWare Configuration Prompts.... 5-7 How to Start the Standalone License Server......... 5-11 How to start the license server manually........... 5-12 How to start the license server automatically...... 5-12 How to start the license server in an OpenVMS cluster............................................ 5-13 v 6 After You Install the DIGITAL PATHWORKS for OpenVMS Servers Before You Begin Postinstallation Tasks............ 6-2 Have you done?..................................... 6-2 Verifying the Server Installation.................. 6-2 How to run the IVP................................. 6-2 Starting the DIGITAL PATHWORKS for OpenVMS File Servers............................................ 6-4 When to start the server........................... 6-4 What the startup procedure does.................... 6-4 Troubleshooting the startup........................ 6-5 Starting the File Servers.......................... 6-5 Ways to start the server........................... 6-5 How to start the PATHWORKS Advanced Server manually........................................... 6-5 How to define LAN Manager server commands at login.............................................. 6-6 How to start the NetWare server manually........... 6-6 How to define NetWare server commands at login..... 6-6 How to start the server automatically.............. 6-7 How to start the server in an OpenVMS cluster...... 6-7 Stopping the Server................................ 6-8 When to stop the server............................ 6-8 How to stop the server............................. 6-9 How to stop the server on system shutdown.......... 6-9 Enabling External Authentication................... 6-9 Enabling External Authentication for VAX Systems... 6-10 Enabling External Authentication for a User........ 6-11 Establishing User Host Mapping..................... 6-12 Synchronizing Passwords............................ 6-13 External Authentication Over a Network............. 6-13 Configuring Externally Authenticated Clients....... 6-14 Setting up Shares.................................. 6-14 7 Implementing a Wide Area Network Implementing a Wide Area Network Using TCP/IP...... 7-1 Planning and Setup................................. 7-2 LMHOSTS Directory.................................. 7-2 LMHOSTS Syntax..................................... 7-2 Managing the LMHOSTS File.......................... 7-4 LMHOSTS Log File................................... 7-4 vi Using a WINS Server in a Wide Area Network......... 7-4 8 Removing DIGITAL PATHWORKS for OpenVMS Reasons for Removing the Server.................... 8-1 Why remove the server?............................. 8-1 Removing the Server................................ 8-2 About the deinstallation command procedure......... 8-2 How to run the deinstallation procedure............ 8-2 How to respond to prompts.......................... 8-3 Sample PATHWORKS Advanced Server and NetWare Removal Procedures................................. 8-4 Sample PATHWORKS Advanced Server removal procedure.......................................... 8-4 Sample NetWare removal procedure................... 8-5 A Summary Checklist of Installation and Upgrade Tasks B Sample PATHWORKS Advanced Server Installation and Configuration Procedure Sample PATHWORKS Advanced Server Installation Procedure.......................................... B-1 Sample PATHWORKS Advanced Server Configuration Procedure.......................................... B-4 C Sample NetWare Server Installation and Configuration Procedure Sample NetWare Server Installation Procedure....... C-1 Sample NetWare Server Configuration Procedure...... C-4 D Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration Sample Combined PATHWORKS Advanced Server and NetWare Server Installation Procedure.............. D-1 Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedures................... D-5 vii E Sample Standalone License Server Installation and Configuration Procedure Sample Standalone License Server Installation Procedure.......................................... E-1 Sample PATHWORKS Advanced Server Configuration Procedure for the Standalone License Server........ E-3 Sample NetWare Configuration Procedure for the Standalone License Server.......................... E-4 F Upgrade Utility Installation Installing the Upgrade Utility..................... F-1 Sample Upgrade Utility Installation Procedure...... F-2 G Files Installed Files Common to PATHWORKS Advanced Server and NetWare............................................ G-1 Files Created During the PATHWORKS Advanced Server Installation....................................... G-11 Files Created During the NetWare Installation...... G-15 PATHWORKS Advanced Server and NetWare Disk Structure.......................................... G-17 H PATHWORKS Advanced Server and NetWare Server Logical Names I NetWare Server Logical Names How NetWare Logical Names Are Created.............. I-1 Types of NetWare Logical Names..................... I-1 Common NetWare Logical Names....................... I-2 Private NetWare Logical Names...................... I-3 Index viii Figures G-1 Server On-Disk Structure Diagram......... G-18 Tables 1-1 Preinstallation Checklist................ 1-9 1-2 keep..................................... 1-17 2-1 Installation Options..................... 2-3 2-2 Installation Prompts..................... 2-9 3-1 PATHWORKS Advanced Server Configuration Prompts.................................. 3-10 3-2 PATHWORKS Advanced Server Configuration Settings................................. 3-15 3-3 OpenVMS Network Device Logicals.......... 3-17 4-1 NetWare Configuration Network Numbers.... 4-3 4-2 External Network Types................... 4-4 4-3 Types of Physical Network Media and NetWare Frame Types They Support......... 4-5 4-4 Configuration Prompts.................... 4-6 5-1 PWRK$CONFIG Configuration Prompts........ 5-4 5-2 PWVN$CONFIG Configuration Prompts........ 5-7 8-1 PWRK$DEINSTAL Prompts.................... 8-3 8-2 PWVN$DEINSTAL Prompts.................... 8-4 A-1 Installation and Upgrade Checklist....... A-1 G-1 Files Common to PATHWORKS Advanced Server and NetWare Server....................... G-2 G-2 PATHWORKS Advanced Server Files.......... G-11 G-3 NetWare Files............................ G-15 H-1 DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server) Logical Names.......... H-1 I-1 Types of NetWare Logical Names........... I-2 I-2 Common NetWare Logical Names............. I-2 I-3 Private NetWare Logical Names............ I-3 ix ________________________________________________________________ Preface About This Guide This guide explains how to install and configure one or more of the following PATHWORKS servers: o DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server) file server o DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare) file server o PATHWORKS standalone license server Audience This guide is written for the network server administrator. It assumes that the administrator is 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 appropriate for the applicable DIGITAL PATHWORKS for OpenVMS server. xi Organization of This Guide The following list can help you find information in this guide: Chapter 1 Describes prerequisites to 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 NetWare server. Chapter 5 Describes the configuration procedure for the standalone license server. Chapter 6 Describes postinstallation tasks, such as running the Installation Verification Procedure and starting the server independent of the installation and configuration procedures. Chapter 7 Describes how to set up Wide Area Networks. Chapter 8 Describes how to remove DIGITAL PATHWORKS for OpenVMS from your system. Appendix A Provides a summary of installation and configuration tasks. You can photocopy Appendix A and use it as a checklist as you read this guide. Appendix B Shows a sample installation and configuration procedure for the PATHWORKS Advanced Server. Appendix C Shows a sample installation and configuration procedure for the NetWare server. Appendix D Shows a sample installation and configuration procedure for a system running both the PATHWORKS Advanced Server and the NetWare server. Appendix E Shows a sample installation and configuration procedure for the standalone license server. xii Appendix F Explains how to install the Upgrade utility without installing any servers; shows a sample installation of the Upgrade utility. Appendix G Lists the files that are installed with DIGITAL PATHWORKS for OpenVMS. Appendix H Lists the logical names created for the Advanced Server and the NetWare server. Appendix I Lists the logical names created for the NetWare server only. Index Related Documents The following manuals provide more information about topics discussed in this guide: __________________________________________________________ Document_Title________Description_________________________ DECprint Supervisor Describes how to load the DECprint for OpenVMS Software Supervisor software, install the Installation Guide printing system, and test printing operations. OpenVMS System Describes the VMSINSTAL command Manager's Manual procedure, UIC group numbers, and how to back up your OpenVMS system, requeue print and batch jobs, and run the AUTOGEN utility. OpenVMS System Describes how to back up your Management Utilities OpenVMS system. Reference Manual DIGITAL PATHWORKS Explains how to upgrade the for OpenVMS PATHWORKS for OpenVMS (LAN Manager) (Advanced Server) software to DIGITAL PATHWORKS Server Migration V6.0 for OpenVMS (Advanced Server) Guide software. xiii __________________________________________________________ Document_Title________Description_________________________ DIGITAL PATHWORKS Explains how to manage and customize for OpenVMS the DIGITAL PATHWORKS for OpenVMS (Advanced (Advanced Server) software. Server) Server Administrator's Guide DIGITAL PATHWORKS Provides command syntax descriptions for OpenVMS for all ADMINISTER commands (Advanced Server) available with DIGITAL PATHWORKS Commands Reference for OpenVMS (Advanced Server), and Manual Net command equivalences. DIGITAL PATHWORKS Provides an overview and for OpenVMS introduction to the DIGITAL (Advanced Server) PATHWORKS for OpenVMS (Advanced Concepts and Server) software and associated Planning Guide networking concepts for system administrators and operators. PATHWORKS Describes how to manage the for OpenVMS PATHWORKS for OpenVMS (NetWare) (NetWare) System software. Administration Guide DIGITAL PATHWORKS Describes the license server for OpenVMS Guide to software and how to manage PATHWORKS Managing PATHWORKS licenses. Licenses__________________________________________________ Conventions The following conventions are used in the Advanced Server documentation set. __________________________________________________________ Convention____Meaning_____________________________________ While you hold down the Ctrl key, press another key or a pointing device button. xiv __________________________________________________________ Convention____Meaning_____________________________________ Italic Indicates a place holder for information or parameters that you must provide. For example, if the procedure asks you to type file name, you must type the actual name of a file. Italic also indicates new terms and the titles of other documentation referenced. monospace Indicates 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. ._________________________________________________________ xv 1 ________________________________________________________________ Before You Install DIGITAL PATHWORKS for OpenVMS This chapter describes the hardware and software you must have and the tasks you need to complete before you install DIGITAL PATHWORKS for OpenVMS. This chapter consists of the following sections: o About DIGITAL PATHWORKS for OpenVMS Servers o About Licensing o Reading the Release Notes o What You Need o Preinstallation Tasks o OpenVMS Cluster Considerations o Next Step ________________________________________________________________ About DIGITAL PATHWORKS for OpenVMS Servers The DIGITAL PATHWORKS for OpenVMS kit contains the software required to run the following server software: o DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server), the PATHWORKS Advanced Server file server o DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare), the NetWare file server o PATHWORKS standalone license server Before You Install DIGITAL PATHWORKS for OpenVMS 1-1 About DIGITAL PATHWORKS for OpenVMS Servers In addition, the kit includes an Upgrade utility that helps you to migrate from PATHWORKS LAN Manager to PATHWORKS Advanced Server. The VMSINSTAL procedure allows you to install either of the file servers, both of the file servers, the standalone license server, or only the PATHWORKS Advanced Server Upgrade utility. If you have PATHWORKS 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 DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for more information. If you have any version of DIGITAL PATHWORKS for OpenVMS (NetWare) installed, you must install the new NetWare server. The license server is installed when you install either PATHWORKS Advanced Server or the NetWare server. If you choose not to install either file server, you can still install the standalone license server. ________________________________________________________________ Installing DIGITAL DECprint Software DIGITAL DECprint Supervisor for OpenVMS, which is included in your software kit, is a printing system that provides queue management and printing features for PostScript printers. If you plan to use DIGITAL DECprint Supervisor for OpenVMS on your system, Digital Equipment 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, but before you configure, PATHWORKS Advanced Server. 1-2 Before You Install DIGITAL PATHWORKS for OpenVMS About Licensing ________________________________________________________________ About Licensing LICENSE REQUIREMENTS The DIGITAL PATHWORKS for OpenVMS (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 both cases, 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 DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for information about upgrading client license requests. 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 Separately from the file server (called the "standalone license server") o In conjunction with the file server (automatically included with your file server installation) In either case, you can configure the license server to support: o LAN Manager clients o NetWare clients Before You Install DIGITAL PATHWORKS for OpenVMS 1-3 About Licensing Digital Equipment Corporation recommends that you install the license server on a designated OpenVMS system without the PATHWORKS file server, to ensure smooth and continuous operation of the license server. Therefore, the DIGITAL PATHWORKS for OpenVMS kit allows you to install the standalone license server separately from the file server. Alternatively, you can run the license server on an OpenVMS cluster with 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. FOR MORE_LICENSING_INFORMATION__________________________________ For more information about_._._.___________Refer_to_._._.______________________ Loading licenses OpenVMS License Management Utility Manual Managing PATHWORKS DIGITAL PATHWORKS for OpenVMS Guide licenses______________to_Managing_PATHWORKS_Licenses______ ________________________________________________________________ Reading the Release Notes ABOUT THE RELEASE NOTES The DIGITAL PATHWORKS for OpenVMS installation kit includes two sets of release notes: o DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server) Release Notes 1-4 Before You Install DIGITAL PATHWORKS for OpenVMS Reading the Release Notes o DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare) Release Notes Digital Equipment Corporation recommends that you print and read the appropriate release notes before starting the installation. Note The installation procedure moves the release notes into the SYS$HELP: area, where you can always locate them after server installation for future reference. 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: DIGITAL 1. Load the installation kit on a drive. PATHWORKS Advanced 2. Enter the following commands, replacing Server device with the name of the device (and Release if the device is a disk, also designate Notes the directory) where you loaded the before the installation kit: installation $ MOUNT device: PWRK $ BACKUP/SELECT=PWRK060.RELEASE_NOTES - _$ device:PWRK060.A/SAVE_SET * $ PRINT PWRK060.RELEASE_NOTES Before You Install DIGITAL PATHWORKS for OpenVMS 1-5 Reading the Release Notes __________________________________________________________ If you want to_._._.______Then_._._.__________________________________ Print the Do the following: NetWare 1. Load the installation kit on a drive. Release Notes 2. Enter the following commands, replacing before the device with the name of the device on installation which you loaded the installation kit: $ MOUNT device: PWRKN $ BACKUP/SELECT=PWVNV10G.RELEASE_NOTES - _$ device:PWRK060.A/SAVE_SET * $ PRINT PWVNV10G.RELEASE_NOTES 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 PWRK060 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._______________ ________________________________________________________________ Using the Summary Checklist Appendix A of this guide 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-6 Before You Install DIGITAL PATHWORKS for OpenVMS What You Need ________________________________________________________________ What You Need 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) that is appropriate to your file server. SOFTWARE REQUIREMENTS To install DIGITAL PATHWORKS for OpenVMS successfully, you must have the following software properly installed and configured on your system: o OpenVMS V7.1 o DECnet DECnet is installed automatically with the OpenVMS operating system. o TCP/IP (optional) DIGITAL TCP/IP Services for OpenVMS and a number of third-party TCP/IP products on OpenVMS can be used to provide IP support. See the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Release Notes for a list of supported TCP/IP vendors and product version numbers. PATHWORKS ADVANCED SERVER CLIENT SOFTWARE DIGITAL PATHWORKS for OpenVMS (Advanced Server) supports connections from the following types of clients: o Windows NT o Windows 95 o Windows for Workgroups o PATHWORKS for DOS and Windows o PATHWORKS for Windows 95 o PATHWORKS 32 Before You Install DIGITAL PATHWORKS for OpenVMS 1-7 What You Need NETWARE CLIENT SOFTWARE DIGITAL PATHWORKS for OpenVMS (NetWare) supports connections from the following types of clients: o PATHWORKS for DOS and Windows, Version 5.0 or higher o NetWare clients using NETX shell (V3.x,2.x) o NetWare clients using VLMS (V3.12,4.x) MEMORY REQUIREMENTS The minimum amount of physical memory required to run PATHWORKS Advanced Server on Alpha systems is 64 MB. ________________________________________________________________ Preinstallation Tasks Use the checklist in Table 1-1 to complete the preinstallation tasks that are described later in this section. 1-8 Before You Install DIGITAL PATHWORKS for OpenVMS Preinstallation Tasks Table_1-1_Preinstallation_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 PATHWORKS over DECnet. < >12. Make sure that TCP/IP is running, if you are planning to use PATHWORKS over TCP/IP. < >13. Check the OpenVMS cluster configuration, if you __________are_installing_PATHWORKS_on_a_cluster.__________ Before you install DIGITAL PATHWORKS for OpenVMS, perform these tasks: 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 Digital Equipment Corporation representative. Before You Install DIGITAL PATHWORKS for OpenVMS 1-9 Preinstallation Tasks STEP 2: CHECK THE NETWORK HARDWARE DIGITAL PATHWORKS for OpenVMS runs on OpenVMS Alpha systems that meet the software requirements. The PC local area network (LAN) requires: o A supported network controller board in the server and in each client o The cables to connect each client to the network STEP 3: CHECK THE REQUIRED SOFTWARE DIGITAL PATHWORKS for OpenVMS requires the OpenVMS operating system, Version 7.1 or higher. If you are going to use the PATHWORKS Advanced Server over DECnet, the license server over DECnet, the mail server, or IPX tunneling, you also need the DECnet network transport. If you are going to use the TCP/IP transport, you must have a TCP/IP transport product, as described in the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Release Notes. STEP 4: LOG IN TO THE SYSTEM ACCOUNT Before you install DIGITAL PATHWORKS for OpenVMS, log in to the SYSTEM account, which has sufficient privileges to start the installation procedure. To log in to the SYSTEM account: 1. At the Username: prompt, enter SYSTEM: Username: SYSTEM 2. At the Password: prompt, enter the password to the SYSTEM account. The password you enter is not displayed. STEP 5: BACK UP THE SYSTEM To safeguard against the loss of valuable data, Digital Equipment 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 and the OpenVMS System Manager's Manual. 1-10 Before You Install DIGITAL PATHWORKS for OpenVMS Preinstallation Tasks 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 the section Reading the Release Notes for more information. STEP 7: CHECK DISK SPACE REQUIREMENTS On your OpenVMS Alpha system, the following amount of free disk space on the system disk is required during the installation procedure. (The disk space requirements shown include provision for the integrated license server.) __________________________________________________________ With these components_._._.______You_need_this_number_of_blocks_._._. PATHWORKS Advanced 104,600 Server only NetWare server only 39,600 PATHWORKS Advanced 110,600 Server and NetWare server Standalone license 104,600 server Upgrade_utility_only__27,100______________________________ To check the number of free blocks on the system disk, enter: $ SHOW DEVICE SYS$SYSDEVICE Result The OpenVMS system displays information about the system disk, including the number of free blocks: Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DUA0: Mounted 0 AXP062 724856 280 1 Before You Install DIGITAL PATHWORKS for OpenVMS 1-11 Preinstallation Tasks 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 on an Alpha system must be at least 7500 pages. To ensure that your system has enough free global pages: 1. Enter the following: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") Result The value of the GBLPAGES parameter is displayed. For example: 7500 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 servers are to be installed: __________________________________________________________ For the standalone license server only, or the NetWare server only, the If the PATHWORKS Advanced Server is value must be at to be installed, the value must be least_._._.___________at_least_._._.______________________ 50____________________75__________________________________ To ensure that your system has enough free global sections: 1-12 Before You Install DIGITAL PATHWORKS for OpenVMS Preinstallation Tasks 1. Enter the following: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") Result 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 servers are to be installed: __________________________________________________________ For the standalone license server only, or the NetWare server only, the If the PATHWORKS Advanced Server is value must be at to be installed, the value must be least_._._.___________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") Result 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 Before You Install DIGITAL PATHWORKS for OpenVMS 1-13 Preinstallation Tasks 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") Result One of the following occurs: o If SCSNODE is defined, the computer name is displayed. For example, if your system's computer name is HYDRAC: NAME = "HYDRAC " o If SCSNODE is not defined, the computer name is not displayed. For example: NAME = " " 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 HYDRAC, edit the file so that it contains the following line: SCSNODE = "HYDRAC" If you edit the file SYS$SYSTEM:MODPARAMS.DAT, you must run the OpenVMS command procedure AUTOGEN and reboot the system either now or at some time before configuring the server. For example: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK For more information For information about running AUTOGEN, see the OpenVMS System Manager's Manual. The SCSNODE parameter's preinstallation status affects what happens after you install and configure the server and reboot the system, as follows: 1-14 Before You Install DIGITAL PATHWORKS for OpenVMS Preinstallation Tasks ________________________________________________________________ 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.____________ 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 Result If the queue manager is running, your OpenVMS system displays a message similar to the following: Queue manager SYS$QUEUE_MANAGER, running, on HYDRAC:: If the queue manager is not running, you can use the following command to start it: $ START/QUEUE/MANAGER Before You Install DIGITAL PATHWORKS for OpenVMS 1-15 Preinstallation Tasks STEP 10: CHECK TIME ZONE AND TDF You check the time zone and time differential factor settings on your system by running 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 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:Essentials. 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. DECnet is required in the following configurations: o If you plan to use the Mail Server over DECnet o If clients will need to use eXcursion o If you are configuring the server as a Backup Domain Controller 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: 1-16 Before You Install DIGITAL PATHWORKS for OpenVMS Preinstallation Tasks $ MCR NCP SHOW EXECUTOR Table_1-2_keep____________________________________________ If DECnet (Phase IV) is_._._._____Then_._._.___________________________________ Running The system displays State = on as shown below: Node Volatile Summary as of 16-SEP-1996 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 __________________________________________________________ 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: $ 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 ________________________________________________________________ Before You Install DIGITAL PATHWORKS for OpenVMS 1-17 Preinstallation Tasks STEP 12: CHECK TCP/IP STATUS If you are planning to use PATHWORKS over TCP/IP, make sure that TCP/IP is running and that the PATHWORKS IP driver has been loaded. See the documentation for your TCP/IP product for information on how to check the status of TCP/IP and the PATHWORKS IP driver on your system. ________________________________________________________________ OpenVMS Cluster Considerations STEP 13: CHECK OPENVMS CLUSTER CONFIGURATION You can run DIGITAL PATHWORKS for OpenVMS on multiple OpenVMS cluster members (server nodes). To do so, follow these steps: 1. On each system disk on which you want to run DIGITAL PATHWORKS for OpenVMS, complete: o The tasks described in this chapter o The VMSINSTAL command procedure described in Chapter 2 2. On each cluster member that you want to use as a PATHWORKS server, run the configuration command procedure (PWRK$CONFIG). This ensures that each node has enough resources to run the server. Note An OpenVMS cluster cannot support both PATHWORKS LAN Manager and PATHWORKS Advanced Server. An OpenVMS cluster can include both VAX and Alpha member nodes. However, in order to enable external authentication on a VAX node, you must perform additional steps, as described in Enabling External Authentication , in this guide. 1-18 Before You Install DIGITAL PATHWORKS for OpenVMS Next Step ________________________________________________________________ Next Step To install DIGITAL PATHWORKS for OpenVMS, proceed to Chapter 2. Before You Install DIGITAL PATHWORKS for OpenVMS 1-19 2 ________________________________________________________________ Installing DIGITAL PATHWORKS for OpenVMS This chapter describes how to install the DIGITAL PATHWORKS for OpenVMS software. You must follow these procedures regardless of whether you are upgrading from a previous version of the server or installing the server for the first time. Before you begin the installation procedure, make sure that you have completed the preinstallation tasks listed in Chapter 1. This chapter consists of the following sections: o About the Installation Procedure o Determining What Software to Install o Installing the Server o Next Steps ________________________________________________________________ About the Installation Procedure 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 DIGITAL PATHWORKS for OpenVMS. Installing DIGITAL PATHWORKS for OpenVMS 2-1 About the Installation Procedure VMSINSTAL INSTALLATION KIT The VMSINSTAL installation kit includes several OpenVMS BACKUP save sets. The save set PWRK060.A always contains the file KITINSTAL.COM and the release notes. WHAT VMSINSTAL DOES When you use VMSINSTAL, it: 1. Creates DIGITAL PATHWORKS for OpenVMS accounts on the file server, if necessary. 2. Restores the files from the save sets in the installation kit. 3. Creates DECnet objects, if you are running DECnet Phase IV. 4. Installs PATHWORKS DCL commands. 5. Creates DIGITAL PATHWORKS for OpenVMS logical names definition files. 6. Deletes obsolete files. 7. Places the files in the directories that you specify during the procedure. 8. Verifies that the software has been installed successfully. (See Verifying the Server Installation for information on how to run the Installation Verification Procedure after installing the software.) ________________________________________________________________ Determining What Software to Install DIGITAL PATHWORKS for OpenVMS (Advanced Server) includes PATHWORKS Advanced Server and PATHWORKS NetWare options. The software you install depends upon the clients in your configuration. o If your configuration includes PATHWORKS LAN Manager clients or retail LAN Manager clients, install PATHWORKS Advanced Server software. 2-2 Installing DIGITAL PATHWORKS for OpenVMS Determining What Software to Install o If your configuration includes PATHWORKS NetWare clients or retail NetWare clients and you want to use your PATHWORKS server to support them, install PATHWORKS NetWare software. o If your configuration includes both PATHWORKS LAN Manager or retail LAN Manager clients and PATHWORKS NetWare clients or retail NetWare clients, and you want to use your PATHWORKS server to support the NetWare as well as LAN Manager clients, install both PATHWORKS Advanced Server and PATHWORKS NetWare software. Depending upon the software on your existing system, you can install the license server only. If you install the NetWare server only, the license server is included. If you install the Advanced Server only, or Advanced Server and NetWare server, the license server is included. Table 2-1, Installation Options, indicates which options you can choose. Note If you are running the NetWare server and the Advanced Server, you must upgrade both servers. If you are running V4.x, you must upgrade to V5.0 before installing V6.0. Table_2-1_Installation_Options__________________________________ License Advanced Advanced Existing Upgrade Server Server NetWare Server and System________Only______Only______Only______Only______NetWare___ LAN Manager Yes No Yes No[1] Yes server V5.0x NetWare No No No[2] Yes Yes server V1.0F and earlier [1]You_must_upgrade_to_Advanced_Server._________________________ [2]You must upgrade the NetWare server. (continued on next page) Installing DIGITAL PATHWORKS for OpenVMS 2-3 Determining What Software to Install Table_2-1_(Cont.)_Installation_Options__________________________ License Advanced Advanced Existing Upgrade Server Server NetWare Server and System________Only______Only______Only______Only______NetWare___ LAN Manager Yes No No[2] No[1] Yes server V5.0x and NetWare server V1.0F or earlier PATHWORKS No No No No No V4.x for OpenVMS[3] [1]You_must_upgrade_to_Advanced_Server._________________________ [2]You must upgrade the NetWare server. [3]You must upgrade to PATHWORKS V5 for OpenVMS first. ________________________________________________________________ ________________________________________________________________ Installing the Server 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 DIGITAL PATHWORKS for OpenVMS is: PWRK060 2. What is the name of the device on which you want to mount the media? 2-4 Installing DIGITAL PATHWORKS for OpenVMS Installing the Server 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, Digital Equipment Corporation recommends that you read them. Procedures for obtaining the release notes are described in Chapter 1. 4. 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. Digital Equipment Corporation recommends that you run the license server on a designated license server system. The installation procedure gives you the option to install the standalone license server software from the DIGITAL PATHWORKS for OpenVMS kit. In this case, the DIGITAL PATHWORKS for OpenVMS file servers are not installed. If any PATHWORKS file server software is installed, you cannot install the standalone license server. 5. Do you want to install DIGITAL PATHWORKS for OpenVMS (Advanced Server) server software? If you have V5.0 of PATHWORKS for OpenVMS (LAN Manager) installed, you must install V6.0. See the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for more information. If you have V4.x of PATHWORKS for OpenVMS, you must upgrade to V5.0 before installing V6.0. For instructions on upgrading from V4.x to V5.0, see the PATHWORKS for OpenVMS Server Migration Guide for OpenVMS V5. 6. Do you want to install the DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare) server software? Installing DIGITAL PATHWORKS for OpenVMS 2-5 Installing the Server If you have a previous version of PATHWORKS for OpenVMS (NetWare), you must upgrade to V1.0G. 7. Do you want to install just the Upgrade utility? To migrate to the Advanced Server, you must upgrade your LAN Manager databases. If you choose to install just the Upgrade utility, you can install the Advanced Server later, after you upgrade your databases. If you install the Advanced Server software, the Upgrade utility is also installed. 8. Do you want to preserve the PATHWORKS V5 for OpenVMS (LAN Manager) environment, and if so, where? 9. What is the User Identification Code (UIC) group number? The DIGITAL PATHWORKS for OpenVMS installation procedure creates an OpenVMS account, PWRK$DEFAULT, if necessary. The default selection displayed in the installation dialog is determined as follows: _______________________________________________________ If_._._.______________The_default_is_._._._____________ You are installing The first available unused UIC DIGITAL PATHWORKS group number, starting with 360. for OpenVMS for the first time An account named The same group number as that PCFS$ACCOUNT already associated with the existing exists account PCFS$ACCOUNT. An account named The same group number as PWRK$DEFAULT already the existing PWRK$DEFAULT exists and PWRK$GUEST accounts, in ______________________preference_to_PCFS$ACCOUNT.______ 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.) 2-6 Installing DIGITAL PATHWORKS for OpenVMS Installing the Server 3. Enter the following command to check the status of the device on which you have loaded the installation kit, replacing device_name with the name of the applicable device: $ SHOW DEVICE device_name For example: $ SHOW DEVICE $1$DUS0: Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt $1$DUS0: (HSC001) Mounted 0 HUBSYS 347718 628 4 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 the default directory to SYS$UPDATE: $ SET DEFAULT SYS$UPDATE 5. Start VMSINSTAL and specify the PWRK060 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 PWRK060 device_name OPTIONS release notes during the N installation procedure Do not want access @VMSINSTAL PWRK060 device_name to the release notes during the installation procedure_______________________________________________________ Installing DIGITAL PATHWORKS for OpenVMS 2-7 Installing the Server HOW INSTALLATION QUESTIONS WORK An asterisk (*) at the beginning of a line in the installation procedure identifies a question you must answer. Usually, a question has a default answer, which the procedure displays within square brackets ([]) at the end of the question. To accept a default, press . For example: * Are you satisfied with the backup of your system disk [YES]? HOW TO INTERRUPT THE INSTALLATION To interrupt the installation procedure, press at any time. Then you can restart the installation from the beginning. HOW TO RESPOND TO PROMPTS Table 2-2 tells you how to respond to the prompts VMSINSTAL displays. Note Table 2-2 shows only the prompts VMSINSTAL displays; it does not show any informational messages. For a complete sample installation script, see Appendix D, Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration. 2-8 Installing DIGITAL PATHWORKS for OpenVMS Installing the Server Table_2-2_Installation_Prompts__________________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Are you Continue satisfied with the backup of your system disk [YES]? Exit NO Select option Display the release notes 1 [2]:[1] on the screen To stop the display at any time, press . 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_prompt_is_displayed_only_if_you_specify_OPTIONS_N_when__ you start the VMSINSTAL command procedure or if there are active processes on the system. (continued on next page) Installing DIGITAL PATHWORKS for OpenVMS 2-9 Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Print the release notes 3 and display them on the To send the screen release notes to another print queue, enter the name of another print queue. To stop the screen display at any time, press . Continue without 4 displaying or printing The release the release notes notes are automatically copied to SYS$HELP. Do you want Install one or more to install the servers Upgrade utility only [NO]?[2] Install only the Upgrade YES utility [2]This_prompt_is_displayed_only_if_your_system_is_currently____ running the previous version of PATHWORKS for OpenVMS. (continued on next page) 2-10 Installing DIGITAL PATHWORKS for OpenVMS Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want to Continue YES continue the installation [NO]?[1] Exit Do you want Install the Advanced YES to install Server the DIGITAL PATHWORKS for OpenVMS (Advanced Server) [NO]? Omit the Advanced Server Do you want to Retain the V5 (LAN preserve the V5 Manager) environment (LAN Manager) so that you can use environment the rollback procedures [YES]?[2] described in the Server Migration Guide Not retain the V5 NO environment [1]This_prompt_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 prompt is displayed only if your system is currently running the previous version of PATHWORKS for OpenVMS. (continued on next page) Installing DIGITAL PATHWORKS for OpenVMS 2-11 Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Enter the Preserve the environment directory to in the default directory preserve the shown V5 environment [SYS$SYSDEVICE:[000000]]:[3] Preserve the V5 A different environment on another device and/or device and/or in another directory. directory Do you want Install the NetWare server YES to install the NetWare server [NO]? Omit the NetWare server [3]This_prompt_is_displayed_only_if_you_chose_to_preserve_the___ PATHWORKS V5 for OpenVMS (LAN Manager) environment. (continued on next page) 2-12 Installing DIGITAL PATHWORKS for OpenVMS Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want Install the standalone to install license server This option the PATHWORKS installs the license server license server [YES]?[4] and transport software without a DIGITAL PATHWORKS for OpenVMS file server. Refer to Chapter 5 for more information. Install a PATHWORKS file NO server with the license This option server causes the installation procedure to repeat the previous questions about installing the file servers, so that you can select one or both file servers. Is the selection Use the selection correct [YES]? [4]This_prompt_is_displayed_only_if_you_chose_to_install_neither the PATHWORKS Advanced Server nor the NetWare server. (continued on next page) Installing DIGITAL PATHWORKS for OpenVMS 2-13 Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ 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]? Complete the installation NO procedure without shutting System shutdown down the system is required for the product installation. If you answer NO, you must shut down the system manually after the installation 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 Run the Installation to run the Verification Procedure IVP after the (IVP) automatically after installation is the installation procedure finished [YES]? completes (continued on next page) 2-14 Installing DIGITAL PATHWORKS for OpenVMS Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Not run the IVP NO You can run the IVP independent of the installation procedure. For detailed information on running the IVP independently, see How to run the IVP, in Chapter 6. Do you want Purge all files it to purge files replaces replaced by this installation [YES]? Not purge any files it NO replaces 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 [5]This_question_is_displayed_only_if_there_are_PATHWORKS_files_ in system-specific directories. (continued on next page) Installing DIGITAL PATHWORKS for OpenVMS 2-15 Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want Shut down the license to shut down server and continue the the PATHWORKS installation license server [YES]?[6] Keep the server running NO and 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 NO and terminate the installation Do you want Shut down the server and to shut down continue the installation the PATHWORKS NetWare server [YES]?[6] Keep the server running NO and terminate the installation [6]This_question_is_displayed_only_if_a_server_is_running.______ (continued on next page) 2-16 Installing DIGITAL PATHWORKS for OpenVMS Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Enter default Associate the newly UIC group created OpenVMS number for accounts PWRK$DEFAULT PWRK$DEFAULT and and PWRK$GUEST with PWRK$GUEST[nnn]: the default user identification code (UIC) group number (nnn) Associate the newly A three-digit created accounts with UIC number. the UIC group number you For detailed specify information about UIC group numbers, see the OpenVMS System Manager's Manual. NetWare SYS Keep the same SYS volume volume location location [device:[PWVN$SYSVOL]]:[7] Specify a different A different SYS volume location for disk device or NetWare directory. [7]This_question_is_displayed_only_if_NetWare_is_being__________ installed. (continued on next page) Installing DIGITAL PATHWORKS for OpenVMS 2-17 Installing the Server Table_2-2_(Cont.)_Installation_Prompts__________________________ If you want the At this installation procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want Copy new files onto the to copy new existing SYS volume files onto the existing NetWare SYS volume [YES]?[8] Leave the existing SYS NO volume as it is [8]This_question_is_displayed_only_if_NetWare_is_being_installed and there is an existing SYS volume. ________________________________________________________________ ________________________________________________________________ Next Steps WHAT TO DO NEXT To continue, depending on which servers 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 PATHWORKS Advanced Advanced Server. Server Installing the Chapter 4 Configure the NetWare NetWare server server. 2-18 Installing DIGITAL PATHWORKS for OpenVMS Next Steps ________________________________________________________________ Which tells you how If_you_are_._._.____Proceed_to_._._.____to_._._.________________ Installing the Chapter 5 Configure the standalone standalone license license server. server Upgrading from DIGITAL PATHWORKS Use the Upgrade utility PATHWORKS V5 for OpenVMS to create and edit for OpenVMS (LAN (Advanced Server) upgrade reports. Manager) Server Migration Guide Upgrading from PATHWORKS V5 Install the PATHWORKS PATHWORKS V4 for for OpenVMS V5 for OpenVMS (LAN OpenVMS Installation and Manager) server. ____________________Upgrade_____________________________________ INSTALL OPTIONAL SERVER ADMINISTRATION TOOLS After you install and configure the server, you can install client-based server management tools that allow you to manage the server from Windows 95, Windows for Workgroups, and Windows NT clients. After you install and configure the PATHWORKS Advanced Server, these tools are available in the pwutil share in the svrtools subdirectory (SYS$UPDATE:PWRK$PWUTIL.SAV). For information on installing client-based server management tools, refer to the README.TXT file supplied with the tools. After you configure the server, you may need to reboot the system for the configuration to take effect. If you have installed the optional server administration tools, this system reboot activates the server and the optional software simultaneously. Installing DIGITAL PATHWORKS for OpenVMS 2-19 3 ________________________________________________________________ Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server This chapter describes how to configure the PATHWORKS Advanced Server and consists of the following sections: o About the PATHWORKS Advanced Server Configuration Procedure o Before You Start the PATHWORKS Advanced Server Configuration Procedure o How to Start the PATHWORKS Advanced Server Configuration Procedure o How to Respond to PATHWORKS Advanced Server Configuration Prompts o How to Change PATHWORKS Advanced Server Configuration Default Settings o Selecting the PATHWORKS Advanced Server Network Device o Next Steps ________________________________________________________________ About the PATHWORKS Advanced Server Configuration Procedure the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-1 About the PATHWORKS Advanced Server Configuration Procedure WHAT IS THE CONFIGURATION PROCEDURE? The PATHWORKS Advanced Server initial configuration procedure, PWRK$CONFIG.COM, is installed by the DIGITAL PATHWORKS for OpenVMS installation procedure. Like the installation procedure, the configuration procedure asks you a series of questions (by displaying prompts). The procedure uses your answers to configure the PATHWORKS Advanced Server. WHAT THE CONFIGURATION PROCEDURE DOES PWRK$CONFIG is a command procedure that: o Creates the PATHWORKS on-disk structure. o Creates the PATHWORKS Advanced Server user accounts and shares databases (that is, access control lists (ACLs)). 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 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 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 Server Administrator's Guide. 3-2 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Before You Start the PATHWORKS Advanced Server Configuration Procedure ________________________________________________________________ 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 12,000 free blocks of disk space. Note The 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, Digital Equipment 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 PATHWORKS must use the same disk device to store and access PATHWORKS files. 2. Do you want to change the system configuration parameters now? If you respond "yes" to the prompt to change the system configuration parameters, you enter the Configuration Manager. The Configuration Manager is a utility that allows you to modify server configuration parameters, such as the maximum number of clients that can connect the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-3 Before You Start the PATHWORKS Advanced Server Configuration Procedure to the server and which network transports the server uses. For more information For detailed information about using the Configuration Manager, refer to the Configuration Manager chapter in the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. For more information about transports, refer to Network Protocols chapter in the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 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 Note 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 PDC. Otherwise the configuration will fail. If you are configuring a BDC to join an existing domain, and the PDC of the domain is on a different IP subnet, with both BDC and PDC configured to use the TCP/IP transport, you have two options: - Configure both the BDC and PDC to use a WINS Server for NetBIOS name registration and resolution. This is the most straightforward method. - Configure the BDC and PDC to use LMHOSTS for NetBIOS name resolution. If you choose this option, you must ensure that the entry for the PDC exists in the LMHOSTS file on the BDC before you run PWRK$CONFIG.COM. If there is no entry for the PDC in the LMHOSTS file on the BDC when you configure the BDC, the BDC will fail to find the PDC and hence fail to join the existing domain. 3-4 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Before You Start the PATHWORKS Advanced Server Configuration Procedure The LMHOSTS file, or in the case of a new installation, an LMHOSTS template file, will be available in the PWRK$LANMAN: directory on the server. For more information on adding entries to the LMHOSTS FILE, see Chapter 7. For more information on configuring PATHWORKS Advanced Server to use WINS or LMHOSTS, see the Configuration Manager section in the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 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 licenses to clients. Any client that wants to use server resources must have a valid license. Each LAN needs only one PATHWORKS license server. The client 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 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. For more information For detailed information on managing PATHWORKS licenses, see the Guide to Managing PATHWORKS 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. the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-5 Before You Start the PATHWORKS Advanced Server Configuration Procedure 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. By default, the Netlogon service runs. o PATHWORKS Advanced Server domain name This is the PATHWORKS Advanced Server domain in which your server is located. A domain is a subdivision of clients and servers on the network. The default Advanced Server domain is LANGROUP. o Role of the server 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 PATHWORKS Advanced Server computer name This is the unique name that identifies your server in a PATHWORKS Advanced Server domain. You define this name or accept the default value when you run the configuration procedure. By default, the Advanced Server computer name is the server's DECnet network name. o PATHWORKS cluster alias 3-6 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Before You Start the PATHWORKS Advanced Server Configuration Procedure 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. The default PATHWORKS cluster alias is the DECnet cluster alias. o Server announce comment This is the comment the PATHWORKS Advanced Server sends out when it announces its presence on the network. This comment may also be shown when you use an interface to display a list of available servers. The default server announce comment is "DIGITAL PATHWORKS V6 for OpenVMS (Advanced Server)." For more information Unless otherwise specified, you can find more detailed information on any of the services or concepts listed above in the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. For detailed information on changing default server configuration settings, see How to Change PATHWORKS Advanced Server Configuration Default Settings , in this chapter. 4. What is the Administrator account password? The configuration procedure prompts you to define a password 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: ! # $ % & () - . ^ _ ` { } ~ the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-7 Before You Start the PATHWORKS Advanced Server Configuration Procedure Note If your server will be a primary domain controller, enter the password to the domain's existing Administrator account. 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. Note Do not start the server during the configuration procedure if any of the following are true: o You still need to run the PATHWORKS V5 (LAN Manager) server. The configuration procedure shuts down the server. o You may need to run the PATHWORKS V5 (LAN Manager) server again for any reason. File access problems may occur if you stop the PATHWORKS Advanced Server and restart the PATHWORKS V5 (LAN Manager) server. o You are installing the server on multiple OpenVMS cluster members. Before you start the server on any OpenVMS cluster member, Digital Equipment Corporation recommends that you configure DIGITAL PATHWORKS for OpenVMS on each cluster member that you want to use as a server. You can then use the SYSMAN utility to start the server simultaneously on all cluster members. If you choose to start the server individually on each cluster member, make sure that you do so from the SYSTEM account on each server node. For more information For detailed information on alternate ways to start the server, see Starting the File Servers in Chapter 6. 3-8 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server How to Start the PATHWORKS Advanced Server Configuration Procedure ________________________________________________________________ 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 ________________________________________________________________ How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 3-1 tells you how to respond to the prompts that PWRK$CONFIG displays. Note Table 3-1 shows only the prompts PWRK$CONFIG displays; it does not show any informational messages. For a complete sample configuration script, see Appendix B, Sample PATHWORKS Advanced Server Installation and Configuration Procedure. the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-9 How to Respond to PATHWORKS Advanced Server Configuration Prompts Table_3-1_PATHWORKS_Advanced_Server_Configuration_Prompts_______ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want to Shut down the server or, continue with if your server is part of configuration an OpenVMS cluster, all [YES]:[1] servers in the cluster Abort the configuration NO procedure Enter disk Copy the PATHWORKS on- device name disk structure to the where PATHWORKS default OpenVMS disk data files device displayed will be stored If you ran PWRK$CONFIG or [default_device]: PWVN$CONFIG previously, the default disk device is the one you specified the last time you configured the server. Copy the PATHWORKS on-disk device_name structure to an OpenVMS disk device different from the default displayed Keep the existing Administrator account password [1]This_prompt_is_displayed_only_if_the_server_is_running.______ (continued on next page) 3-10 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 3-1 (Cont.) PATHWORKS Advanced Server Configuration __________________Prompts_______________________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want Enter the Configuration to change Manager tool For detailed the server information configuration about using the parameters now? Configuration [YES]: Manager, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. Not enter the NO Configuration Manager Enter item Accept the configuration number, or parameters displayed RETURN to use these values [DONE]: (continued on next page) the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-11 How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 3-1 (Cont.) PATHWORKS Advanced Server Configuration __________________Prompts_______________________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Change the default The number configuration settings associated with displayed a setting you want to change. For detailed information on changing these default configuration settings, see How to Change PATHWORKS Advanced Server Configuration Default Settings , in this chapter. Enter Associate a password with password Administrator the Administrator account If your server network account will be part of password: a domain, enter the password to the domain's existing Administrator account. Re-enter to password verify password: (continued on next page) 3-12 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 3-1 (Cont.) PATHWORKS Advanced Server Configuration __________________Prompts_______________________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want Prompt you to enter a YES to enter a new new Administrator account Administrator password account password [NO]:[2] Do you want to Start the server start DIGITAL automatically after the PATHWORKS V6 for installation procedure OpenVMS on node completes node_name now [YES]:[3] Not start the server NO [2]This_prompt_is_displayed_if_you_ran_PWRK$CONFIG_previously.__ [3]This prompt is displayed only if the PATHWORKS Advanced Server can be started without first executing AUTOGEN or rebooting the system. ________________________________________________________________ ________________________________________________________________ How to Change PATHWORKS Advanced Server Configuration Default Settings After you change system configuration parameters during the configuration procedure, you exit the Configuration Manager. The configuration procedure then displays a list of server configuration default settings and a prompt that lets you change them; for example: the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-13 How to Change PATHWORKS Advanced Server Configuration Default Settings 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.0 for OpenVMS (Advanced Server) Enter item number, or RETURN to use these values [DONE]: To change a server configuration default 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 describes possible values for each setting. 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 How to Respond to PATHWORKS Advanced Server Configuration Prompts , in this chapter. Note Item 3a is displayed only if your response to item 3 is YES. For more information For a description of each server configuration setting, see Before You Start the PATHWORKS Advanced Server Configuration Procedure , in this chapter. 3-14 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server How to Change PATHWORKS Advanced Server Configuration Default Settings Table_3-2_PATHWORKS_Advanced_Server_Configuration_Settings______ Setting_________________________Possible_Values_________________ 1. Run the license server: Enter YES to run the license server, or press to use the default NO. 2. Enable Timesource service: Enter YES to enable the Timesource service, or press to use the default NO. 3. Enable Alerter service: Enter NO to disable the Alerter service, or press to use the default YES. 3a. Alert user names:[1] Enter the names of users, each containing up to 20 characters, who can receive alert messages, and separate them with commas. 4. Enable Netlogon service: Enter NO to disable the Netlogon service, or press to use the default YES. 5. Advanced Server domain: Enter a domain name of up to 15 characters, or press to use the default. The default domain name is LANGROUP. You must supply a unique domain name within your LAN. 6. Advanced Server role: Enter PRIMARY to designate the server as the primary domain controller or BACKUP to designate the server as a backup domain controller. [1]Displayed_only_if_Alerter_service_is_enabled.________________ (continued on next page) the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-15 How to Change PATHWORKS Advanced Server Configuration Default Settings Table 3-2 (Cont.) PATHWORKS Advanced Server Configuration __________________Settings______________________________________ Setting_________________________Possible_Values_________________ 7. Advanced Server computer Enter a computer name of up name: to 15 characters, or press to use the default. The default displayed is your system's DECnet name. However, if your system's DECnet and NETBIOS names are different and the NETBIOS name is the node name, enter the NETBIOS name. 7a. PATHWORKS OpenVMS cluster Enter a PATHWORKS cluster alias alias:[2] for the OpenVMS cluster to which your server belongs, or press to use the default, the OpenVMS cluster alias. 8. Server announce comment: Enter the text of up to 48 characters that you want the server to send out when it announces its presence on the network, or press to use the default. [2]Displayed_only_in_an_OpenVMS_cluster.________________________ ________________________________________________________________ ________________________________________________________________ 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. 3-16 Configuring the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Selecting the PATHWORKS Advanced Server Network Device Table 3-3 lists OpenVMS logical names that you can use to control the network device over which the PATHWORKS 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 PWRK$NETBEUI_DEVICE_____________NetBEUI___________________ For example, to select device EWA0: for DECnet transport, enter the following command before you start the server: $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: ________________________________________________________________ Next Steps You can start the PATHWORKS Advanced Server automatically as part of the configuration procedure. However, if you are installing the NetWare server as well, you can complete the NetWare configuration procedure before rebooting the system and starting the servers. NetWare configuration is described in Chapter 4. If you are upgrading from PATHWORKS LAN Manager, perform the upgrade procedures described in the Server Migration Guide. If you are ready to start the server, see Chapter 6, After You Install the DIGITAL PATHWORKS for OpenVMS Servers for instructions. the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server 3-17 4 ________________________________________________________________ Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server This chapter describes how to configure the NetWare server and consists of the following sections: o About the NetWare Configuration Procedure o NetWare Configuration Information o Running the NetWare Configuration Procedure o Reconfiguring the NetWare Server For an example of a complete configuration, see Appendix C, Sample NetWare Server Installation and Configuration Procedure. ________________________________________________________________ About the NetWare Configuration Procedure WHAT IS THE CONFIGURATION PROCEDURE? The NetWare configuration procedure, SYS$UPDATE:PWVN$CONFIG.COM, is installed by the DIGITAL PATHWORKS for OpenVMS installation procedure. Like the installation procedure, the configuration procedure asks you a series of questions. The procedure then uses your answers to configure the PATHWORKS for OpenVMS (NetWare) file server. Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-1 About the NetWare Configuration Procedure WHAT THE CONFIGURATION PROCEDURE DOES The configuration procedure: o Creates the PATHWORKS on-disk structure. o Allows you to specify a NetWare file server name and checks the file server name you provide for conformance with NetWare naming syntax. o Allows you to specify an alternate location for the NetWare configuration files. o Allows you to configure the NetWare Virtual Terminal (NVT). o Allows you to run the license server on the system. o Allows you to configure up to eight NetWare networks and verifies that the network numbers you provide are valid (8-digit) hexadecimal numbers. o Writes your answers into configuration files and logical name command procedures. For the logical names and their definitions, see Appendix H, PATHWORKS Advanced Server and NetWare Server Logical Names and Appendix I, NetWare Server Logical Names. WHEN TO CONFIGURE THE SERVER You must configure the NetWare server after you install it and before you start it for the first time. In an OpenVMS cluster, you must configure the server on each node that will run the PATHWORKS server. ________________________________________________________________ NetWare Configuration Information 4-2 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server NetWare Configuration Information ABOUT NETWORK NUMBERS A network number (address) is a unique 8-digit hexadecimal number used by the NetWare operating system to identify a network. When you configure the server, the configuration procedure asks you to specify network numbers for your internal network (LAN) and external networks. TYPES OF NETWORK NUMBERS Table 4-1 describes the two types of configuration network numbers. Table_4-1_NetWare_Configuration_Network_Numbers___________ Number________Description_________________________________ Internal The internal network number is the 8-digit network hexadecimal number that you assign to your number file server. This number must be unique for each file server on a LAN. If you do not enter an internal network number, the configuration procedure calculates one from the DECnet node number for the OpenVMS system. If the system is not running DECnet, the default value is 00000DEC. External Also called the IPX network number, the network external network number is a unique number number that is used by the file server to route IPX packets. All the file servers on one LAN share the same network number. This number is a hexadecimal number that corresponds to a ______________physical_network_interface_and_a_frame_type. Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-3 NetWare Configuration Information TYPES OF EXTERNAL NETWORKS Table 4-2 describes the two types of external networks, tunnel and local. Table_4-2_External_Network_Types__________________________ Type__________Description_________________________________ Tunnel Also called an IPX DECnet tunnel in the network PWVN$CONFIG.COM procedure, a tunnel is a point-to-point connection between two servers on different networks. The tunnel connects two or more IPX networks over an existing DECnet network that carries only DECnet traffic. This is often used for Wide Area connectivity. Each tunnel network must be identified by a number different from the internal network number and unique among NetWare external network numbers in the LAN environment. Local A local network is a group of file servers, network workstations, and peripheral devices, such as printers, that share the same physical network media in a local area. You can have only one local network per ______________physical_network_interface._________________ NUMBER AND TYPES OF NETWORKS YOU CAN CONFIGURE You can configure a maximum of eight external networks for any one NetWare server. The external networks can contain any combination of local networks and tunnels up to a total of eight. ABOUT TOKEN RING AND FDDI SUPPORT If you have Token Ring or FDDI interfaces, the configuration procedure detects them and allows you to configure them for the NetWare server. Table 4-3 shows the physical network media that are supported and the frame types they support. Frame types define how data is encapsulated at the data-link level of the OSI model. The frame type you select during configuration must be 4-4 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server NetWare Configuration Information compatible with the physical network media in use in your current configuration. Table 4-3 Types of Physical Network Media and NetWare __________Frame_Types_They_Support________________________ IEEE-802.2 Media_______DIX_SNAP____(SAP_E0)____RAW-802.3_____________ Token Ring Supported Supported Not Supported FDDI Supported Supported Not Supported Ethernet____Supported___Supported___Supported_____________ ________________________________________________________________ Running the NetWare Configuration Procedure WHEN TO RUN THE CONFIGURATION PROCEDURE You need to run the configuration procedure if you have: o Turned the system into an OpenVMS cluster. In this case, you must run the configuration procedure on each node in the cluster that will be running the NetWare server. o Altered the external network by adding network interface cards or changing frame types. HOW TO RUN THE CONFIGURATION PROCEDURE To run the configuration procedure: 1. Enter the following command: $ @SYS$UPDATE:PWVN$CONFIG 2. Respond to the configuration questions as shown in How to respond to prompts, in this chapter. Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-5 Running the NetWare Configuration Procedure HOW CONFIGURATION QUESTIONS WORK An asterisk (*) at the beginning of a line in the configuration procedure identifies a question you must answer to configure the server. Usually, a question has a default answer, which the procedure displays within square brackets ([]) at the end of the question. To accept a default, press . HOW TO GET ONLINE HELP To get online help on a specific configuration question, enter a question mark (?) after the question. HOW TO INTERRUPT THE CONFIGURATION You can interrupt the configuration procedure at any time. To interrupt the configuration procedure, press . HOW TO RESPOND TO PROMPTS Table 4-4 tells you how to respond to the prompts PWVN$CONFIG displays. Note Table 4-4 shows only the prompts; it does not show any informational messages. For a complete sample configuration script, see Appendix C, Sample NetWare Server Installation and Configuration Procedure. Table_4-4_Configuration_Prompts_________________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want to Shut down the server or, continue with if your server is part of configuration an OpenVMS cluster, all [YES]:[1] servers in the cluster [1]This_prompt_is_displayed_only_if_you_started_the_server______ previously. (continued on next page) 4-6 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server Running the NetWare Configuration Procedure Table_4-4_(Cont.)_Configuration_Prompts_________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Abort the configuration NO procedure Enter disk Copy the PATHWORKS on- device name disk structure to the where PATHWORKS default OpenVMS disk data files device displayed will be stored If you ran PWRK$CONFIG or [default_device]: PWVN$CONFIG previously, the default disk device is the one you specified the last time you configured the server. Copy the PATHWORKS on-disk device_name structure to an OpenVMS disk device different from the default displayed Name of DIGITAL Use the default server PATHWORKS name for OpenVMS (NetWare) file server [server- name]: Use another server name Server name to use (continued on next page) Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-7 Running the NetWare Configuration Procedure Table_4-4_(Cont.)_Configuration_Prompts_________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ System-specific directory [SYS$SPECIFIC:[PWVN$PRIVATE]]: Use the default device and directory Use another device or Device and directory directory to use Do you want to Not allow clients using configure NVT the Novell Virtual on this system Terminal protocol [NO]? Allow clients using the YES Novell Virtual Terminal protocol Do you want to Not run the license server run a License Server on this system [NO]? Run the license server YES Internal Use the default internal network number network number (hexadecimal) [network_ number]: (continued on next page) 4-8 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server Running the NetWare Configuration Procedure Table_4-4_(Cont.)_Configuration_Prompts_________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Use another internal Correct network network number number Maximum SPX Use no more than 50 sockets [50]: sockets Use a greater number of 50, 200, 500, or sockets 1000 Network Allow you to enter a new Configuration network configuration Action (ADD) [ADD]:[2] To proceed, at least one network must be configured. A maximum of eight networks can be configured. Network Type Configure a new local (LOCAL, network TUNNEL,NONE) [L]:[3] Configure a new tunnel T network Not configure a new NONE network [2]This_prompt_is_displayed_only_if_there_are_no_NetWare________ networks configured already. [3]This prompt is displayed only if you are configuring a new network. (continued on next page) Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-9 Running the NetWare Configuration Procedure Table_4-4_(Cont.)_Configuration_Prompts_________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Choose a Network Configure a new network controller from based on controller above listing [controller]:[3] Not configure a new NONE network When you select NONE, the dialog returns to the Network Configuration Action prompt Enter 5 for Use the default frame type Ethernet_II (DIX/SNAP) (DIX), 6 for 802.2 (Sap E0), or 7 for RAW- 802.3 [5]:[3] Use the IEEE-802.2 frame 6 type Use the RAW-802.3 type 7 Network Number Use the unique network n, a hexadecimal [0]:[3] number value greater than 0 Network Store the displayed Configuration configuration and Action finish the configuration (ADD,DELETE, procedure MODIFY,NONE) [NONE]: [3]This_prompt_is_displayed_only_if_you_are_configuring_a_new___ network. (continued on next page) 4-10 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server Running the NetWare Configuration Procedure Table_4-4_(Cont.)_Configuration_Prompts_________________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Add a new network ADD Delete a network DELETE Modify the configuration MODIFY of an existing network Do you want Reboot the system to reboot the automatically after the system now configuration procedure [YES][4]: completes Not reboot the system NO After the configuration procedure completes, you must reboot the system before you can start the NetWare server. Do you want to Start the server start DIGITAL automatically after the PATHWORKS configuration procedure for OpenVMS completes (NetWare) now [YES]: Not start the server NO Is this Retain the settings configuration displayed satisfactory [YES]? Change the configuration NO [4]This_prompt_is_displayed_only_if_it_is_necessary_to_reboot___ the system to reload the streams execlet or the PCFS driver. ________________________________________________________________ Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-11 Running the NetWare Configuration Procedure HOW TO CONFIRM YOUR ANSWERS After you have answered all the questions, the configuration procedure displays a summary of your choices and prompts you to confirm your choices. It then asks you: * Is this configuration satisfactory [YES]? __________________________________________________________ If_you_are_._._.___Then_._._._____________________________ Satisfied with Press to answer YES. the configuration summary Not satisfied Answer NO to change any of the values. with the The configuration procedure prompts you configuration for each value. summary___________________________________________________ When you are done with the configuration procedure, start the server, as described in Chapter 6, After You Install the DIGITAL PATHWORKS for OpenVMS Servers. ________________________________________________________________ Reconfiguring the NetWare Server HOW TO RECONFIGURE THE SERVER You can reconfigure the server at any time after the installation. To reconfigure the server: 1. Stop the server and transports. 2. Run the configuration procedure. 3. Start the server and transports. For information about starting and stopping the servers, see Chapter 6, After You Install the DIGITAL PATHWORKS for OpenVMS Servers. 4-12 Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server Reconfiguring the NetWare Server NEW CONFIGURATION VALUE LOCATION When you enter new configuration values, some of them are stored as new logical name definitions in the logical name command procedure. The new definitions supersede the previous definitions. However, the previous logical name definitions remain in the files, thus providing a history of the configuration changes. Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server 4-13 5 ________________________________________________________________ Configuring and Starting the Standalone License Server The PATHWORKS license server is a software program that you can run on your OpenVMS system to grant licenses to clients. You can install the license server: o Separately from the file server o In conjunction with the file server In either case, you can configure the license server to support: o LAN Manager clients o NetWare clients Digital Equipment Corporation recommends that you install the license server on a designated OpenVMS system without the PATHWORKS file server, to ensure smooth and continuous operation of the license server. Therefore, the DIGITAL PATHWORKS for OpenVMS kit allows you to install the standalone license server separately from the file server. Alternatively, you can run the license server on an OpenVMS cluster with PATHWORKS file servers, where cluster failover provides reliability. Typically, each LAN needs only one PATHWORKS license server. (The same license server can support both PATHWORKS LAN Manager and PATHWORKS Advanced Server clients.) The client 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. For detailed information on managing PATHWORKS licenses, see the Guide to Managing PATHWORKS Licenses. Configuring and Starting the Standalone License Server 5-1 This chapter describes how to configure and start up the standalone license server, and consists of the following sections: o Before You Begin to Configure the Standalone License Server o Configuring the Standalone License Server o Configuring the PATHWORKS Advanced Server Transports o How to Respond to PATHWORKS Advanced Server Configuration Prompts o Configuring the NetWare Transport o How to Respond to NetWare Configuration Prompts o How to Start the Standalone License Server ________________________________________________________________ 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 file server. The procedures are described in Chapter 2, Installing DIGITAL PATHWORKS for OpenVMS. ________________________________________________________________ Configuring the Standalone License Server You must configure the standalone license server to provide license information to clients in the PATHWORKS LAN. Therefore, you select the appropriate transports used by the PATHWORKS clients. For PATHWORKS Advanced Server clients, you can configure the license server to use the following transports: o DECnet o NetBEUI 5-2 Configuring and Starting the Standalone License Server Configuring the Standalone License Server o TCP/IP Note TCP/IP requires a TCP/IP transport product. Suggested products are listed in the DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server) Release Notes. To configure the standalone license server to use one or more of these transports, use the PWRK$CONFIG.COM command procedure, as described in "Configuring the PATHWORKS Advanced Server Transports " in this guide. For NetWare clients, you can also configure the license server to use the IPX transport. To configure the standalone license server to use IPX, use the PWVN$CONFIG.COM command procedure, described in the "Configuring the NetWare Transport " section. ________________________________________________________________ Configuring the PATHWORKS Advanced Server Transports The following section describes how to use the PATHWORKS Advanced Server's configuration 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. Configuring and Starting the Standalone License Server 5-3 How to Respond to PATHWORKS Advanced Server Configuration Prompts ________________________________________________________________ How to Respond to PATHWORKS Advanced Server Configuration Prompts Table 5-1 tells you how to respond to the prompts that PWRK$CONFIG displays. Note Table 5-1 shows only the prompts that PWRK$CONFIG displays; it does not show any informational messages. For a complete sample configuration script, see Appendix E, Sample Standalone License Server Installation and Configuration Procedure. Table_5-1_PWRK$CONFIG_Configuration_Prompts_____________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Enter disk Copy the PATHWORKS on- device name disk structure to the where PATHWORKS default OpenVMS disk data files device displayed will be stored (If you ran PWRK$CONFIG [default_device]: or PWVN$CONFIG previously, the default disk device is the one you specified the last time you configured the server) Copy the PATHWORKS on-disk device_name structure to an OpenVMS disk device different from the default displayed (continued on next page) 5-4 Configuring and Starting the Standalone License Server How to Respond to PATHWORKS Advanced Server Configuration Prompts Table_5-1_(Cont.)_PWRK$CONFIG_Configuration_Prompts_____________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want to Allow licenses to be serve PATHWORKS served over DECnet licenses over DECnet [YES]:[1,2] Not allow licenses to be NO served over DECnet Do you want to Allow licenses to be YES serve PATHWORKS served over NetBEUI licenses over NetBEUI [NO]:[1,2] Not allow licenses to be served over NetBEUI Do you want to Allow licenses to be YES serve PATHWORKS served over TCP/IP licenses over TCP/IP [NO]:[1] Not allow licenses to be served over TCP/IP [1]Default_answers_may_differ_if_you_have_run_the_PWRK$CONFIG___ procedure previously. [2]This prompt appears only if the PATHWORKS license server was not previously installed. (continued on next page) Configuring and Starting the Standalone License Server 5-5 How to Respond to PATHWORKS Advanced Server Configuration Prompts Table_5-1_(Cont.)_PWRK$CONFIG_Configuration_Prompts_____________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want Start the server to start the automatically after the PATHWORKS configuration procedure license server completes now [YES]: Complete the configuration NO procedure without starting ___________________the_server___________________________________ ________________________________________________________________ Configuring the NetWare Transport The following section describes how to use the NetWare configuration command procedure to configure the IPX transport so that the standalone license server can support NetWare client license verification. 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:PWVN$CONFIG 3. Respond to the configuration prompts. For descriptions of the types of information required in the configuration procedure, see Chapter 4, Configuring the DIGITAL PATHWORKS for OpenVMS (NetWare) Server. 5-6 Configuring and Starting the Standalone License Server How to Respond to NetWare Configuration Prompts ________________________________________________________________ How to Respond to NetWare Configuration Prompts Table 5-2 tells you how to respond to the prompts that PWVN$CONFIG displays. For a complete example of the configuration dialog, refer to Appendix E, Sample Standalone License Server Installation and Configuration Procedure. Table_5-2_PWVN$CONFIG_Configuration_Prompts_____________________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Enter disk Copy the PATHWORKS on- device name disk structure to the where PATHWORKS default OpenVMS disk data files device displayed will be stored (If you ran PWRK$CONFIG [default_device]: or PWVN$CONFIG previously, the default disk device is the one you specified the last time you configured the server) Copy the PATHWORKS on-disk device_name structure to an OpenVMS disk device different from the default displayed System-specific directory [SYS$SPECIFIC:[PWVN$PRIVATE]]: Use the default device and directory Use another device or Device and directory directory to use. (continued on next page) Configuring and Starting the Standalone License Server 5-7 How to Respond to NetWare Configuration Prompts Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Do you want to Allow licenses to be serve PATHWORKS served over IPX licenses over IPX [YES]? Not allow licenses to be NO served over IPX Internal Use the default internal network number network number (hexadecimal) [network_ number]: Use another internal Correct network network number number Maximum SPX Use no more than 50 sockets [50]: sockets Use a greater number of 50, 200, 500, or sockets 1000 Network Allow you to enter a new Configuration network configuration Action (ADD) [ADD]:[1] [1]This_prompt_is_displayed_only_if_there_are_no_NetWare________ networks configured already. At least one network must be configured in order to complete the configuration procedure. (continued on next page) 5-8 Configuring and Starting the Standalone License Server How to Respond to NetWare Configuration Prompts Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ At least one network must be configured in order to proceed. A maximum of eight networks can be configured. Network Type Configure a new local (LOCAL, network TUNNEL,NONE) [L]:[2] Configure a new tunnel T network Not configure a new NONE network Choose a Network Configure a new network controller from based on controller above listing [controller]:[2] Not configure a new NONE network When you select NONE, the dialog returns to the Network Configuration Action prompt [2]This_prompt_is_displayed_only_if_you_are_configuring_a_new___ network. (continued on next page) Configuring and Starting the Standalone License Server 5-9 How to Respond to NetWare Configuration Prompts Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Enter 5 for Use the default frame type Ethernet_II (DIX/SNAP) (DIX), 6 for 802.2 (Sap E0), or 7 for Raw- 802.3:[5]:[2] Use the IEEE-802.2 frame 6 type Use the Raw-802.3 frame 7 type Network Number Use the unique network n, a hexadecimal [0]:[2] number value greater than 0 Network Store the displayed Configuration configuration and Action finish the configuration (ADD,DELETE, procedure MODIFY,NONE) [NONE]: Add a new network ADD Delete a network DELETE Modify the configuration MODIFY of an existing network Do you want Reboot the system to reboot the automatically after the system now configuration procedure [YES][3]: completes [2]This_prompt_is_displayed_only_if_you_are_configuring_a_new___ network. [3]This prompt is displayed only if it is necessary to reboot the system to reload the streams execlet or the PCFS driver. (continued on next page) 5-10 Configuring and Starting the Standalone License Server How to Respond to NetWare Configuration Prompts Table_5-2_(Cont.)_PWVN$CONFIG_Configuration_Prompts_____________ If you want the At this configuration procedure prompt_._._._______to_._._._____________________Enter_._._._____ Not reboot the system NO (Note that after the configuration procedure completes, you must reboot the system before you can start PATHWORKS) Do you want Start the server to start the automatically after the PATHWORKS configuration procedure license server completes now [YES]: Not start the server NO Is this Continue with the configuration configuration procedure satisfactory [YES]? Prompt you for another NO Network Configuration ___________________Action_______________________________________ ________________________________________________________________ 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 the "Configuring the Standalone License Server " section. o Manually from the command line. o Automatically each time you reboot. Configuring and Starting the Standalone License Server 5-11 How to Start the Standalone License Server 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 commands: __________________________________________________________ To_serve_._._.________Enter_._._._________________________ Advanced Server $ @SYS$STARTUP:PWRK$STARTUP licenses NetWare licenses $ @SYS$STARTUP:PWVN$STARTUP NetWare and $ @SYS$STARTUP:PWRK$STARTUP Advanced Server $ @SYS$STARTUP:PWVN$STARTUP licenses__________________________________________________ Example $ @SYS$STARTUP:PWVN$STARTUP Result The license server starts, and messages similar to the following are displayed: $ @SYS$STARTUP:PWVN$STARTUP PATHWORKS license server will use DECnet, IPX. PATHWORKS mail notification will use DECnet. Process NETBIOS created with identification 0000012C Starting IPX Daemon (NPSD)...OK Process PWRK$LICENSE_S created with identification 00000135 $ 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 appropriate startup commands, 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 to serve both LAN Manager and NetWare licenses. 5-12 Configuring and Starting the Standalone License Server How to Start the Standalone License Server Example $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET . . . $ @SYS$STARTUP:PWRK$STARTUP $ @SYS$STARTUP:PWVN$STARTUP HOW TO START THE LICENSE SERVER IN AN OPENVMS CLUSTER If you installed and configured the PATHWORKS license server on multiple members of the same OpenVMS cluster, Digital Equipment Corporation 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 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, do the following: _______________________________________________________ To_serve_._._.___Enter_._._.___________________________ Advanced SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP Server licenses NetWare SYSMAN> DO @SYS$STARTUP:PWVN$STARTUP licenses Configuring and Starting the Standalone License Server 5-13 How to Start the Standalone License Server _______________________________________________________ To_serve_._._.___Enter_._._.___________________________ NetWare and SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP Advanced SYSMAN> DO @SYS$STARTUP:PWVN$STARTUP Server licenses_______________________________________________ 5-14 Configuring and Starting the Standalone License Server 6 ________________________________________________________________ After You Install the DIGITAL PATHWORKS for OpenVMS Servers This chapter describes tasks you can perform after you install the servers. This chapter consists of the following sections: o Before You Begin Postinstallation Tasks o Verifying the Server Installation o Starting the File Servers o Enabling External Authentication o Setting up Shares After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-1 Before You Begin Postinstallation Tasks ________________________________________________________________ Before You Begin Postinstallation Tasks HAVE YOU_DONE?__________________________________________________ If_you_are_._._.______Make_sure_that_you_have_._._._______ Installing the Completed the installation DIGITAL PATHWORKS procedures described in Chapter 2, for OpenVMS Advanced Installing DIGITAL PATHWORKS for Server OpenVMS. Completed the configuration procedures appropriate to the servers you have installed. Upgrading the LAN Completed the upgrade procedure Manager server to described in DIGITAL PATHWORKS for PATHWORKS Advanced OpenVMS (Advanced Server) Server Server Migration Guide. Upgrading the Completed the configuration NetWare server from procedure described in Chapter 4, a previous version. Configuring the DIGITAL PATHWORKS ______________________for_OpenVMS_(NetWare)_Server._______ ________________________________________________________________ Verifying the Server Installation HOW TO RUN THE IVP If you did not run the IVP when you installed the DIGITAL PATHWORKS kit, you can run it now to make sure that the server installed successfully. 6-2 After You Install the DIGITAL PATHWORKS for OpenVMS Servers Verifying the Server Installation Verifying the DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server) Installation To run the IVP for DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server), enter: $ @SYS$TEST:PWRK$IVP ________________________________________________________________ If the installa- Then the IVP tion_._._.__displays_._._.________And_you_should_._._.__________ Succeeded The message Start the server, as described %PWRK-I-NORMAL, in Starting the File Servers , IVP completed in this chapter. successfully Failed An error message, Reinstall the software, as followed by -PWRK- described in Chapter 2, in E-IVPFAIL, IVP has this guide. ____________failed______________________________________________ Verifying the DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare) Installation To run the IVP for DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare), enter: $ @SYS$TEST:PWVN$IVP ________________________________________________________________ If the installa- Then the IVP tion_._._.__displays_._._.________And_you_should_._._.__________ Succeeded The message Start the server, as described %PWVN-I-NORMAL, in Starting the File Servers , IVP completed in this chapter. successfully Failed An error message, Reinstall the software, as followed by -PWVN- described in Chapter 2 in this E-IVPFAIL, IVP has guide. ____________failed______________________________________________ After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-3 Starting the DIGITAL PATHWORKS for OpenVMS File Servers ________________________________________________________________ Starting the DIGITAL PATHWORKS for OpenVMS File Servers WHEN TO START THE 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. WHAT THE STARTUP PROCEDURE DOES The startup procedure: 1. Checks for the required privileges. 2. Checks for enough available processes (for the NetWare server only). 3. Looks for the logical names files and, if it does not find the files, exits the startup procedure. 4. Verifies that the server has been configured, and ends if it has not. 5. Makes sure that the value for VIRTUALPAGECNT is greater than 20,000 (for the NetWare server only). 6. Loads drivers. 7. Loads streams. 8. Installs images. 9. Starts transport support processes. 10.Starts each of the components: o License Registrar o Novell Virtual Terminal (NVT) (if configured) for the NetWare server o File server o Print servers (if configured) for the NetWare server o License server (if configured) 6-4 After You Install the DIGITAL PATHWORKS for OpenVMS Servers Starting the DIGITAL PATHWORKS for OpenVMS File Servers TROUBLESHOOTING THE STARTUP PATHWORKS processes are detached processes. During startup, all detached processes must execute the site-specific system login procedure (by default, SYS$MANAGER:SYLOGIN.COM). If your PATHWORKS 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 PATHWORKS 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 non- detached processes, so that they are not executed during PATHWORKS startup. See the OpenVMS DCL Dictionary for more information. ________________________________________________________________ Starting the File Servers WAYS TO START THE SERVER You can start the server: o During the configuration procedure, as described in Chapter 2, Installing DIGITAL PATHWORKS for OpenVMS. o Manually from the command line. o Automatically each time you reboot. 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 After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-5 Starting the File Servers Result The PATHWORKS Advanced Server starts, and messages similar to the following are displayed: PATHWORKS file server will use DECnet. PATHWORKS mail notification will use DECnet. Process NETBIOS created with identification 0000009A Process PWRK$LICENSE_R created with identification 0000009D The PATHWORKS V6.0 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. HOW TO DEFINE LAN MANAGER SERVER COMMANDS AT LOGIN 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 HOW TO START THE NETWARE SERVER MANUALLY If you did not start the DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare) server during the configuration procedure, you can start it now by entering: $ @SYS$STARTUP:PWVN$STARTUP HOW TO DEFINE NETWARE SERVER COMMANDS AT LOGIN You can define server commands automatically when you log in to the privileged account that you use to manage the NetWare server. To define server commands at login, edit the LOGIN.COM file of the privileged account to add the following line: $ @SYS$STARTUP:PWVN$COMMANDS 6-6 After You Install the DIGITAL PATHWORKS for OpenVMS Servers Starting the File Servers HOW TO START THE 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. For the PATHWORKS Advanced Server, add the @SYS$STARTUP:PWRK$STARTUP command to the file below all lines that start network transports. Example $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET . . . $ @SYS$STARTUP:PWRK$STARTUP 3. For the NetWare server, add the @SYS$STARTUP:PWVN$STARTUP command to the file below all lines that start network transports. Example $ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET . . . $ @SYS$STARTUP:PWVN$STARTUP HOW TO START THE SERVER IN AN OPENVMS CLUSTER If you installed and configured DIGITAL PATHWORKS for OpenVMS on multiple members of the same OpenVMS cluster, Digital Equipment 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 into the SYSTEM account on one of the server nodes, then run SYSMAN as follows: After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-7 Starting the File Servers ________________________________________________________________ Enter_this_command...___________To...___________________________ $ RUN SYS$SYSTEM:SYSMAN Start the SYSMAN utility. SYSMAN> SET ENVIRONMENT Define the OpenVMS cluster /NODE=(HYDRA,HYDRAB,HYDRAC) members on which to start the server. For example, HYDRA, HYDRAB, HYDRAC. SYSMAN> DO Start the PATHWORKS Advanced @SYS$STARTUP:PWRK$STARTUP Server server on all the nodes you defined in the previous command. SYSMAN> DO Start the NetWare server on all @SYS$STARTUP:PWVN$STARTUP the nodes you defined in the previous command. SYSMAN>_EXIT____________________Exit_the_SYSMAN_utility.________ Note If you are using the STARTUP feature of the SYSMAN utility to start PATHWORKS, 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 Manager's Manual: Essentials. ________________________________________________________________ Stopping the Server WHEN TO STOP THE 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 6-8 After You Install the DIGITAL PATHWORKS for OpenVMS Servers Stopping the Server HOW TO STOP THE SERVER To stop the server, enter the following command, as appropriate: To stop the PATHWORKS Advanced Server, enter: $ @SYS$STARTUP:PWRK$SHUTDOWN To stop the NetWare server, enter: $ @SYS$STARTUP:PWVN$SHUTDOWN HOW TO STOP THE SERVER ON SYSTEM SHUTDOWN To stop the servers as part of an orderly system shutdown, add the shutdown command to the site-specific system shutdown procedure. ________________________________________________________________ Enabling External Authentication The OpenVMS operating system versions 7.1 and higher provide support for external authentication. PATHWORKS Advanced Server takes advantage of external authentication to allow Advanced Server users to log in to the OpenVMS operating system using the Advanced Server user name and password. External authentication provides automatic password synchronization between an OpenVMS account and a corresponding NT account. With external authentication enabled, users who have both OpenVMS and Advanced Server user accounts can avoid having to maintain two different passwords. To provide external authentication for a user, perform the following procedures. Each procedure is described in the section listed below. After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-9 Enabling External Authentication __________________________________________________________ Step___Procedure___________Section________________________ 1. Enable external Enabling External authentication Authentication for VAX Systems for the system, if necessary. 2. Set the OpenVMS Enabling External user account to Authentication for a User allow external authentication. 3. Establish host Establishing User Host Mapping mapping between the PATHWORKS Advanced Server user account and the OpenVMS operating system _______user_account.______________________________________ ENABLING EXTERNAL AUTHENTICATION FOR VAX SYSTEMS On Alpha systems, external authentication is automatically enabled when the PATHWORKS Advanced Server starts up. However, when the server is running on a mixed- architecture OpenVMS cluster (that is, a cluster with both VAX and Alpha members), you must perform the following additional steps on VAX members to ensure that external authentication is enabled across the entire cluster. 1. Copy the following files to the VAX member's system disk from the Alpha member's system disk: _______________________________________________________ Copy this File from the To this Location on the VAX Alpha_System______________System_______________________ SYS$STARTUP:PWRK$ACME_ SYS$COMMON:[SYS$STARTUP] STARTUP.COM SYS$LIBRARY:PWRK$ACME_ SYS$COMMON:[SYSLIB] MODULE_VAX.EXE_________________________________________ 6-10 After You Install the DIGITAL PATHWORKS for OpenVMS Servers Enabling External Authentication 2. Run the PWRK$ACME_STARTUP command procedure on the VAX machine: $ @SYS$STARTUP:PWRK$ACME_STARTUP.COM 3. Define the following logicals in the VAX local startup file, where the scs_node is the SCS node name that is running the PATHWORKS server: $ DEFINE/SYSTEM/EXE SYS$ACME_SERVER scs_node ________________________Note ________________________ You may include steps 2 and 3 as commands in the system startup procedure for the VAX system. _____________________________________________________ Failure to enable external authentication on the VAX member of an OpenVMS cluster can result in unpredictable login failures on the cluster. ENABLING EXTERNAL AUTHENTICATION FOR A USER To enable the optional external authentication feature for a user, set the EXTAUTH flag in the user's SYSUAF record. When set, the EXTAUTH flag denotes that the user is to be externally authenticated at OpenVMS logon. You can modify this flag using the AUTHORIZE utility. For example, to create a user account with external authentication enabled, enter the following commands, where [nnn,nnn] is the UIC for the user account: $ MCR AUTHORIZE UAF> ADD username /FLAG=(EXTAUTH,NODISUSER) /UIC=[nnn,nnn] To modify an existing user account to allow external authentication, enter the following commands: $MCR AUTHORIZE UAF> MODIFY username /FLAG=(EXTAUTH) After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-11 Enabling External Authentication Note By default, the EXTAUTH flag in the AUTHORIZE utility is not set. Refer to the OpenVMS System Management Utilities Reference Manual for more information on the AUTHORIZE utility EXTAUTH flag. ESTABLISHING USER HOST MAPPING After you enable external authentication for a user, you must establish the host mapping for the corresponding PATHWORKS Advanced Server user account. Host mapping identifies an Advanced Server user with an OpenVMS user. Host mapping can serve two purposes. It can be used both to enable external authentication and to enforce resource access restrictions. Default host mapping is provided by the system. Explicit host mapping, done to enable external authentication or to enhance OpenVMS security, overrides the default mapping. To establish the host mapping for an existing PATHWORKS Advanced Server user, use the ADMINISTER command ADD HOSTMAP, as follows: $ADMINISTER ADD HOSTMAP pw-user-name OpenVMS-user-name After you complete these steps, the user identified as externally authenticated can use the PATHWORKS Advanced Server user name and password to log in to OpenVMS at the login prompt. If the verification is successful, the appropriate OpenVMS user name and profile is obtained and used. For more information about user account host mapping, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 6-12 After You Install the DIGITAL PATHWORKS for OpenVMS Servers Enabling External Authentication SYNCHRONIZING PASSWORDS The password of an externally authenticated OpenVMS user is automatically synchronized with the hostmapped PATHWORKS Advanced Server user, regardless of the role of the PATHWORKS Advanced Server in the domain. When the user changes the OpenVMS password using the SET PASSWORD command, if external authentication is set for the user, OpenVMS forwards the password change request to the PATHWORKS Advanced Server. When the password change request is successfully processed, OpenVMS updates the OpenVMS user password. When the user changes the PATHWORKS Advanced Server password using the NET PASSWORD command, or the server administrator changes it with the ADMINISTER SET PASSWORD command, the PATHWORKS Advanced Server processes the password change as usual. Note Password synchronization may fail due to differences in the sets of valid characters allowed by OpenVMS and PATHWORKS Advanced Server. Keep this in mind when changing the password of an externally authenticated hostmapped user. Password synchronization is enabled by default for externally authenticated OpenVMS users. You can selectively disable it. Refer to the section "Managing System Access" in the OpenVMS Guide to System Security, for more information on how to selectively disable this feature. 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. After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-13 Enabling External Authentication 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 Utility Routines Manual for more information about the /LOCAL_PASSWORD qualifier to the LOGINOUT command. CONFIGURING EXTERNALLY AUTHENTICATED CLIENTS By default, the PATHWORKS Advanced Server supports 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 DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. ________________________________________________________________ Setting up Shares After installing and configuring your servers, you can set up directory shares to enable users to share file resources and print shares to enable them to share printer queues. 6-14 After You Install the DIGITAL PATHWORKS for OpenVMS Servers Setting up Shares You can photocopy and use the Shares Worksheet in the Worksheets Appendix of the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Concepts and Planning Guide to record the decisions you make as you plan your shares. Read the following chapters of the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for information on setting up shares: o Managing Directory and File Sharing for information on setting up and managing directory shares o Managing Shared Printers for information on setting up and managing print shares After You Install the DIGITAL PATHWORKS for OpenVMS Servers 6-15 7 ________________________________________________________________ Implementing a Wide Area Network This chapter describes how to set up a wide area network (WAN) using the TCP/IP transport supported by the PATHWORKS Advanced Server software. This chapter consists of the following sections: o Implementing a Wide Area Network Using TCP/IP o Using a WINS Server in a Wide Area Network ________________________________________________________________ Implementing a Wide Area Network Using TCP/IP The DIGITAL PATHWORKS for OpenVMS software provides the ability to set up a wide area network with the TCP/IP transport through the use of the LMHOSTS file. This file contains a list of domain controllers and member servers that are not in the same TCP/IP subnet as the primary domain controller. The LMHOSTS file allows the PATHWORKS Advanced Server to participate in a Windows NT wide area network as well. Unlike a Windows NT Server, DIGITAL PATHWORKS for OpenVMS 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. Implementing a Wide Area Network 7-1 Implementing a Wide Area Network Using TCP/IP PLANNING AND SETUP To implement 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. LMHOSTS DIRECTORY You implement a wide area network by supplying the following file on all DIGITAL PATHWORKS for OpenVMS Advanced Servers that are in different subnets: PWRK$LMROOT:[LANMAN]LMHOSTS. Note The LMHOSTS file has no file extension. LMHOSTS 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.) 7-2 Implementing a Wide Area Network Implementing a Wide Area Network Using TCP/IP To preserve the case of the characters, enclose the node name in double quotation marks. If the node name is not enclosed in quotes, the alphabetic characters are set to uppercase before the node name is loaded into cache (see parameter #PRE) 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 out with blank characters. Examples of 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. In Example 2, the node name is not interpreted as uppercase, and will be padded with blank characters for bytes 8 through 16. In Example 3, the node name is not interpreted as uppercase, and no padding needs to be inserted because blank spaces are already included in order to make the control character reside in byte 16. o #PRE is an optional tag that indicates that the entry should be preloaded into the cache. o #DOM:domainname is an optional tag that associates the entry with the LAN Manager domain specified by domainname. 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:PATHWORKS Implementing a Wide Area Network 7-3 Implementing a Wide Area Network Using TCP/IP 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 PATHWORKS (the name of the domain) will be available for matching. 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 wide area networking capabilities, 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. 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. ________________________________________________________________ Using a WINS Server in a Wide Area Network You can configure the PATHWORKS Advanced Server as a WINS client. This allows the PATHWORKS server to use a WINS server for NETBIOS name registration, resolution, renewal, and release in a wide area network configuration. 7-4 Implementing a Wide Area Network Using a WINS Server in a Wide Area Network For more information on how to use the Configuration Manager to configure the PATHWORKS Advanced Server to use WINS, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. Implementing a Wide Area Network 7-5 8 ________________________________________________________________ Removing DIGITAL PATHWORKS for OpenVMS This chapter describes how to remove DIGITAL PATHWORKS for OpenVMS servers from your system. This chapter consists of the following sections: o Reasons for Removing the Server o Removing the Server o Sample PATHWORKS Advanced Server and NetWare Removal Procedures ________________________________________________________________ Reasons for Removing the Server WHY REMOVE THE SERVER? If the IVP indicates that the software installation procedure failed, you must reinstall the DIGITAL PATHWORKS for OpenVMS software. Note If your system has enough free disk space, you can install the server again without deinstalling PATHWORKS servers. If you do not have enough disk space, however, you must remove DIGITAL PATHWORKS for OpenVMS before reinstalling it. For more information For detailed information about disk space requirements, see Step 7: Check disk space requirements, in Chapter 1. Removing DIGITAL PATHWORKS for OpenVMS 8-1 Removing the Server ________________________________________________________________ Removing the Server ABOUT THE DEINSTALLATION COMMAND PROCEDURE You remove a server using a command procedure that: o Is installed with DIGITAL PATHWORKS for OpenVMS. o Shuts down the server automatically. o Prompts you to enter information necessary to complete the removal procedure. o Removes all DIGITAL PATHWORKS for OpenVMS images, support files, and logical names that are created during the installation procedure. Optionally removes the PATHWORKS data files. o Removes the PATHWORKS Advanced Server accounts. o Removes the NETBIOS$ACCESS OpenVMS identifier if PATHWORKS V5.x for OpenVMS was not installed previously. o Removes PATHWORKS DECnet objects. HOW TO RUN THE DEINSTALLATION PROCEDURE To start the deinstallation procedure and remove DIGITAL PATHWORKS for OpenVMS server: 1. Ensure that you are logged in to the SYSTEM account. 2. Start the deinstallation command procedure: ________________________________________________________________ To remove DIGITAL PATHWORKS V6.0 To remove DIGITAL for OpenVMS (Advanced Server), PATHWORKS V1.0F for OpenVMS enter:_______________________________(NetWare),_enter:__________ $_@SYS$UPDATE:PWRK$DEINSTAL__________$_@SYS$UPDATE:PWVN$DEINSTAL 8-2 Removing DIGITAL PATHWORKS for OpenVMS Removing the Server HOW TO RESPOND TO PROMPTS Table 8-1 tells you how to respond to the prompts the PATHWORKS Advanced Server deinstallation procedure displays. Table_8-1_PWRK$DEINSTAL_Prompts_________________________________ If you want the removal Enter . . . At_this_prompt_._._.____procedure_to_._._.______________________ Are you sure you Continue YES want to deinstall DIGITAL PATHWORKS V6 for OpenVMS (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 files [no]: Authorization file and the Share file Remove the PATHWORKS YES Advanced Server on-disk structure, including the User Authorization file and the ________________________Share_file______________________________ Table 8-2 tells you how to respond to the prompts the DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare) deinstallation procedure displays. Removing DIGITAL PATHWORKS for OpenVMS 8-3 Removing the Server Table_8-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.0G for OpenVMS (NetWare) [no]: Exit Do you want to delete Save the NetWare on-disk the NetWare data structure, including the files [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___ ________________________________________________________________ Sample PATHWORKS Advanced Server and NetWare Removal Procedures SAMPLE PATHWORKS ADVANCED SERVER REMOVAL PROCEDURE This is a sample of the removal procedure for PATHWORKS Advanced Server from a system that is also running DIGITAL PATHWORKS V1.0x for OpenVMS (NetWare). $ @SYS$UPDATE:PWRK$DEINSTAL This procedure shuts down all PATHWORKS V6.0 for OpenVMS servers, and deletes all PATHWORKS V6.0 for OpenVMS (Advanced Server) images. 8-4 Removing DIGITAL PATHWORKS for OpenVMS Sample PATHWORKS Advanced Server and NetWare Removal Procedures Are you sure you want to deinstall PATHWORKS V6.0 for OpenVMS (Advanced Server) [no]: Y Do you want to delete the Advanced Server data files [no]: Y PATHWORKS V1.0x for OpenVMS (NetWare) is installed on this system. There are many images that are common between Advanced Server and NetWare. These images will not be deleted unless you also deinstall NetWare. Shutting down the currently running server(s)... Deleting PATHWORKS V6.0 for OpenVMS (Advanced Server) images... Deleting Advanced Server data files... Deassigning PATHWORKS V6.0 for OpenVMS logical names... PATHWORKS V6.0 for OpenVMS (Advanced Server) is now deinstalled. SAMPLE NETWARE 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.0G for OpenVMS servers, and deletes all PATHWORKS V1.0G for OpenVMS (NetWare) images. Are you sure you want to deinstall PATHWORKS V1.0G for OpenVMS (NetWare) [no]: Y Do you want to delete the NetWare SYS Volume [no]: Y Stopping PATHWORKS for OpenVMS (NetWare) Server... Process NETBIOS stopped Process PWRK$LICENSE_R stopped Stopping IPX Daemon (NPSD)... Deleting PATHWORKS for OpenVMS common images... Deleting PATHWORKS for OpenVMS NETBIOS component... Deleting PATHWORKS V1.0G for OpenVMS (NetWare) images... Deleting NetWare data files... Deleting NetWare SYS Volume... Removing PWRK$DEFAULT and PWRK$GUEST VMS accounts... Removing PATHWORKS V1.0G for OpenVMS identifiers... Removing PATHWORKS V1.0G for OpenVMS DECnet objects... Deassigning PATHWORKS V1.0G for OpenVMS logical names... PATHWORKS V1.0G for OpenVMS (NetWare) is now deinstalled. Removing DIGITAL PATHWORKS for OpenVMS 8-5 A ________________________________________________________________ Summary Checklist of Installation and Upgrade Tasks Table A-1 summarizes the tasks that you need to perform to install and configure your 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____________________ (continued on next page) Summary Checklist of Installation and Upgrade Tasks A-1 Summary Checklist of Installation and Upgrade Tasks Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________ < >1. Prepare for the installation by completing all preinstallation tasks on the checklist in Preinstallation Tasks in Chapter 1, 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. < >2. Start the installation procedure and respond to installation prompts. You may choose to install: o The Advanced Server o The NetWare server o The Upgrade utility only (if you chose to install neither the Advanced Server nor the NetWare server) o The license server only (if you chose not to install the Advanced Server, the NetWare server, and the Upgrade utility) (continued on next page) A-2 Summary Checklist of Installation and Upgrade Tasks Summary Checklist of Installation and Upgrade Tasks Table_A-1_(Cont.)_Installation_and_Upgrade_Checklist____________ < >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 DIGITAL 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).___________________________________________ Summary Checklist of Installation and Upgrade Tasks A-3 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. ________________________________________________________________ Sample PATHWORKS Advanced Server Installation Procedure The following example shows a sample installation dialog for the PATHWORKS Advanced Server. $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V6.2 It is 16-MAY-1997 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: PWRK V6.0 Beginning installation of PWRK 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 Please select which components to install: PATHWORKS V6.0 for OpenVMS (Advanced Server) PATHWORKS V1.0G for OpenVMS (NetWare) * Do you want to install the PATHWORKS for OpenVMS (Advanced Server) [NO]? Y * Do you want to install the NetWare server [NO]? PATHWORKS Advanced Server Installation and Configuration Procedure B-1 Sample PATHWORKS Advanced Server Installation Procedure The following components will be installed: PATHWORKS V6.0 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, TCP/IP, IPX, and SPX, 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]? N * 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 104600 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. 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. For more information about UIC group numbers, see the OpenVMS System Manager's Manual. B-2 Sample PATHWORKS Advanced Server Installation and Configuration Procedure Sample PATHWORKS Advanced Server Installation Procedure * Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]: Optional DECprint Supervisor Available -------------------------------------- The PATHWORKS for OpenVMS distribution media includes two kits for the DECprint Supervisor for OpenVMS: VAX and Alpha. DECprint Supervisor for OpenVMS is a family of layered products that runs on OpenVMS VAX and Alpha to provide access through the OpenVMS queueing system to selected PostScript printers. To use DECprint Supervisor for OpenVMS, you must install the kit for either VAX or Alpha accordingly. You do not need a separate license to use DECprint Supervisor for OpenVMS with Advanced Server clients. * Press RETURN to continue: 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-SKIPSET, Skipping product save set G (Alpha NetWare only) ... %PWRK-I-SKIPSET, Skipping product save set H (NetWare SYS Volume) ... %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands %PWRK-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COM %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. PATHWORKS Advanced Server Installation and Configuration Procedure B-3 Sample PATHWORKS Advanced Server Installation Procedure %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting Installation Verification Procedure for PATHWORKS V6.0 for OpenVMS (Advanced Server) %PWRK-I-NORMAL, IVP completed successfully Installation of PWRK V6.0 completed at 15:36 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA VMSINSTAL procedure done at 15:36 ________________________________________________________________ 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.0 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 12000 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: B-4 Sample PATHWORKS Advanced Server Installation and Configuration Procedure Sample PATHWORKS Advanced Server Configuration Procedure 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 ... 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]: N Reading current configuration parameters ... PATHWORKS V6.0 for OpenVMS is presently configured to run as follows: PATHWORKS Advanced Server Installation and Configuration Procedure B-5 Sample PATHWORKS Advanced Server Configuration Procedure 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.0 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 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.0 for OpenVMS at system startup, you should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file. $ @SYS$STARTUP:PWRK$STARTUP B-6 Sample PATHWORKS Advanced Server Installation and Configuration Procedure Sample PATHWORKS Advanced Server Configuration Procedure Note: Add this line below the lines that start all network transports (such as DECnet). Before starting PATHWORKS V6.0 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.0 for OpenVMS on node COBRAZ now [yes]: %PWRK-F-REBOOT, system must be rebooted before starting PATHWORKS PATHWORKS Advanced Server Installation and Configuration Procedure B-7 C ________________________________________________________________ Sample NetWare Server Installation and Configuration Procedure This appendix shows sample installation and configuration procedures for the NetWare server on an OpenVMS cluster. ________________________________________________________________ Sample NetWare Server Installation Procedure The following example shows a sample installation dialog for the NetWare server. $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V6.2 It is 16-MAY-1997 at 15:50. 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: PWRK V6.0 Beginning installation of PWRK V6.0 at 15:50 %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 Please select which components to install: PATHWORKS V6.0 for OpenVMS (Advanced Server) PATHWORKS V1.0G for OpenVMS (NetWare) * Do you want to install the PATHWORKS for OpenVMS (Advanced Server) [NO]? * Do you want to install the NetWare server [NO]? Y The following components will be installed: Sample NetWare Server Installation and Configuration Procedure C-1 Sample NetWare Server Installation Procedure PATHWORKS V1.0G for OpenVMS (NetWare) 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, TCP/IP, IPX, and SPX, 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]? N * 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 39600 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. 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. 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]: C-2 Sample NetWare Server Installation and Configuration Procedure Sample NetWare Server Installation Procedure The PATHWORKS for OpenVMS (NetWare) product comes with a SYS volume containing client files used by the file server. These files require a minimum of 34000 free disk blocks. However, if the disk cluster size is greater than 3, more space will be required. The file server uses the SYS volume location you specify as the top level directory for the SYS volume. SYS volume subdirectories include SYSTEM, MAIL, PUBLIC, and LOGIN. Client utilities such as SYSCON and FILER are placed in these subdirectories during installation. Note: the server frequently accesses the data files stored on the SYS volume. 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. * NetWare SYS volume location [SYS$SYSDEVICE:[PWVN$SYSVOL]]: PWRK$DISK:[PWVN$SYSVOL] 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 ... %PWRK-I-SKIPSET, Skipping product save set E (Alpha Advanced Server only) ... %VMSINSTAL-I-RESTORE, Restoring product save set G ... %PWRK-I-RESTORE, Restoring product save set H (NetWare SYS Volume) ... %PWRK-I-PURGING, Purging PATHWORKS for OpenVMS (NetWare) files moved to SYS Volume %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PWVN]. %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands %PWRK-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COM %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: Sample NetWare Server Installation and Configuration Procedure C-3 Sample NetWare Server Installation Procedure $ @SYS$UPDATE:PWVN$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... Starting Installation Verification Procedure for PATHWORKS V1.0G for OpenVMS (NetWare) %PWVN-I-NORMAL, IVP completed successfully Installation of PWRK V6.0 completed at 15:55 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA VMSINSTAL procedure done at 15:56 ________________________________________________________________ Sample NetWare Server Configuration Procedure The following example shows a sample configuration dialog for the NetWare server. $ @SYS$UPDATE:PWVN$CONFIG ***************************************************************** * PATHWORKS V1.0G for OpenVMS (NetWare) Configuration Procedure * ***************************************************************** * * * Copyright (C) 1992, 1997 by * * Digital Equipment Corporation, Maynard, Massachusetts * * and * * Novell, Incorporated * * All rights reserved. * * * ***************************************************************** This procedure will help you to set up and configure your PATHWORKS for OpenVMS (NetWare) installation. C-4 Sample NetWare Server Installation and Configuration Procedure Sample NetWare Server Configuration Procedure If you need help with any question asked by this procedure, reply to the question with a question mark (?). * Press RETURN to continue: Defining PATHWORKS for OpenVMS (NetWare) logical names. 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 12000 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 NetWare directory tree... Scanning for supported Ethernet/TokenRing/FDDI controllers. Please wait... PATHWORKS for OpenVMS (NetWare) has never been configured on this system. * Press RETURN to continue: Sample NetWare Server Installation and Configuration Procedure C-5 Sample NetWare Server Configuration Procedure +-----------------------------------+ | Current Configuration Information | +-----------------------------------+ Type Control-Y to abort configuration. Server name : COBRAZ_PNW NVT Server name : NONE System-specific directory : SYS$SPECIFIC:[PWVN$PRIVATE] Run License Server : NO Internal Network Number : 000032B3 Maximum SPX sockets : 50 Network Type : Connection : DLPI type : Network Number : Reboot system when done : YES Perform Bindup : N/A Start Server when done : N/A There are no networks configured yet. * Press RETURN to continue: PATHWORKS for OpenVMS (NetWare) File Server name must be unique on all known IPX networks. * Name of PATHWORKS for OpenVMS (NetWare) file server [COBRAZ_PNW]: The PATHWORKS for OpenVMS (NetWare) product requires a system-specific directory to hold configuration information for the file server, and print server. It needs to be on a disk with at least 3000 free disk blocks. * System-specific directory [SYS$SPECIFIC:[PWVN$PRIVATE]]: Novell Virtual Terminal (NVT) allows NetWare clients to log into this node using terminal emulation software that supports the NVT protocol. * Do you want to configure NVT on this system [NO]? PATHWORKS for OpenVMS (NetWare) client licenses are granted by the License Server. In order to run a License Server, you must have a loaded PAK of client licenses. C-6 Sample NetWare Server Installation and Configuration Procedure Sample NetWare Server Configuration Procedure In an OpenVMS cluster, all members either do or do not run the license server, even though only one member actively serves licenses. However, if this member fails and stops serving licenses, another member takes over automatically. * Do you want to run a License Server on this system [NO]? This is the internal network number used by the file server. It should be unique on your network (i.e. there should be no other NetWare File Server with this same internal network number). If you are running DECnet, the default value is your DECnet address converted to hex and padded with leading zeros. e.g.: node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864" If you are not running DECnet, the default value is "00000DEC" (which just happens to be a valid hexadecimal number). * Internal network number (hexadecimal) [000032B3]: Maximum SPX sockets is the maximum number of SPX sockets available to processes using the IPX/SPX stack provided with PATHWORKS for OpenVMS (NetWare). If you plan to only use PATHWORKS for OpenVMS (NetWare), then you need not set SPX sockets any larger than max NVT connections. If, however, you are planning on using other products that use the IPX stack, then you should consult the documentation for those products when configuring this parameter. Valid values for SPX sockets are 50, 200, 500 and 1000 (but no smaller than max NVT connections). If you change this parameter, you must reboot for it to take effect. * Maximum SPX sockets [50]: Network Type : Connection : DLPI type : Network Number : There are no networks configured yet. At least one network must be configured in order to proceed. * Network Configuration Action (ADD) [ADD]: Configuring a new network. Sample NetWare Server Installation and Configuration Procedure C-7 Sample NetWare Server Configuration Procedure There are two types of networks that can be configured. "LOCAL" networks are networks that have direct connections to an physical Network controller. There can only be as many "LOCAL" networks as there are physical Network controllers on this system. "TUNNEL" networks connect to another node also running the IPX DECnet Tunnel. The total number of "TUNNEL" networks is eight, minus however many "LOCAL" networks are configured (i.e. if 2 "LOCAL" networks are configured, then there can be up to 6 "TUNNEL" networks"). There can only be one "TUNNEL" network for each remote DECnet node name. "NONE" returns you to Network Configuration Action prompt. * Network Type (LOCAL,TUNNEL,NONE) [L]: Currently available Network controller list: EZA(Ethernet), FAA(FDDI), NONE "NONE" will return you to the Network Configuration Action prompt. * Choose a Network controller from above listing [EZA]: Input values for selecting a frame-type (DLPI-type) are: DIX/SNAP IEEE-802.2 Raw-802.3 Media: (Sap E0) (Old: Novell) ----- -------- ---------- ------------- Token Ring: (1) (2) FDDI: (3) (4) Ethernet: (5) (6) (7) Select a frame type for this >>>ETHERNET<<< device. * Enter 5 if Ethernet_II(DIX), 6 if 802.2(Sap E0), or 7 if Raw-802.3 [5]: Each configured network must have a unique Network Number. This is a hexadecimal (0-9,A-F) number that can be up to 8 digits long. For more information on choosing a Network Number, see the PATHWORKS for OpenVMS (NetWare) Server Installation Guide. "NONE" will return you to the Network Configuration Action prompt. * Network Number [0]: 2100001 #1 --- Network Type : Local Connection : EZA DLPI type : ETH_II_DIX Network Number : 02100001 C-8 Sample NetWare Server Installation and Configuration Procedure Sample NetWare Server Configuration Procedure A maximum of eight (8) networks can be configured. If the above networks are configured correctly, then enter NONE. * Network Configuration Action (ADD,DELETE,MODIFY,NONE) [NONE]: This configuration procedure can reboot the system automatically when it completes. If you do not answer YES, you must reboot the system by hand before starting the PATHWORKS for OpenVMS (NetWare) file server. * Do you want to reboot the system now [YES]? +-----------------------------------+ | Current Configuration Information | +-----------------------------------+ Type Control-Y to abort configuration. Server name : COBRAZ_PNW NVT Server name : NONE System-specific directory : SYS$SPECIFIC:[PWVN$PRIVATE] Run License Server : NO Internal Network Number : 000032B3 Maximum SPX sockets : 50 #1 --- Network Type : Local Connection : EZA DLPI type : ETH_II_DIX Network Number : 02100001 Reboot system when done : YES Perform Bindup : N/A Start Server when done : N/A Sample NetWare Server Installation and Configuration Procedure C-9 Sample NetWare Server Configuration Procedure * Is this configuration satisfactory [YES]? Writing PWVN$CONF_DIR:PWVN$NWCONFIG.CFG file Writing PWVN$CONF_DIR:PWVN$NPSCONFIG.CFG file Writing PWVN$CONF_DIR:PWVN$CONF_SYMBOLS.COM file Writing Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$MSGS.DAT Writing Sconsole Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$SCONSOLE.HELP Writing Config Help file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$CONFIG.HELP Writing NetWare printer config file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$NWPRINT.CFG Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM file Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM file Setting file ownership in SYS$SYSDEVICE:[PWVN$SYSVOL] to user PWRK$DEFAULT Ignore any "SYSTEM-W-ACCONFLICT, file access conflict." warnings. To start PATHWORKS for OpenVMS (NetWare), issue the following command: @SYS$STARTUP:PWVN$STARTUP.COM DIGITAL recommends that the above command be placed in your site-specific system startup file in the SYS$MANAGER directory to automatically start PATHWORKS for OpenVMS (NetWare) each time the system is re-booted. IMPORTANT: Some sites use OpenVMS disk quotas. If your site does so, then you may need to use the DISKQUOTA utility and enter a record for the PATHWORKS for OpenVMS (NetWare) Guest Account. IMPORTANT: By default the PATHWORKS for OpenVMS (NetWare) SUPERVISOR account does not have a password. It is suggested that after the file server is running that you change the SUPERVISOR password. Note that this must be done from a PC client logged in to this file server using the client utility SYSCON. The configuration of PATHWORKS for OpenVMS (NetWare) is complete. C-10 Sample NetWare Server Installation and Configuration Procedure D ________________________________________________________________ Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration This appendix shows a sample installation and a sample configuration procedure on an OpenVMS cluster for the PATHWORKS Advanced Server and NetWare servers combined. ________________________________________________________________ Sample Combined PATHWORKS Advanced Server and NetWare Server Installation Procedure The following example shows a sample installation dialog for both the PATHWORKS Advanced Server and NetWare servers. $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V6.2 It is 16-MAY-1997 at 14:56.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: PWRK V6.0 Beginning installation of PWRK V6.0 at 14:56 %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 Please select which components to install: PATHWORKS V6.0 for OpenVMS (Advanced Server) PATHWORKS V1.0G for OpenVMS (NetWare) * Do you want to install the PATHWORKS for OpenVMS (Advanced Server) [NO]? Y * Do you want to install the NetWare server [NO]? Y Advanced Server and NetWare Server Installation and Configuration D-1 Sample Combined PATHWORKS Advanced Server and NetWare Server Installation Procedure The following components will be installed: PATHWORKS V6.0 for OpenVMS (Advanced Server) PATHWORKS V1.0G for OpenVMS (NetWare) 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]? * 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 110600 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. 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. 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]: The PATHWORKS for OpenVMS (NetWare) product comes with a SYS volume containing client files used by the file server. These files require a minimum of 34000 free disk blocks. However, if the disk cluster size is greater than 3, more space will be required. The file server uses the SYS volume location you specify as the top level directory for the SYS volume. SYS volume subdirectories include SYSTEM, MAIL, PUBLIC, and LOGIN. Client utilities such as SYSCON and FILER are placed in these subdirectories during installation. D-2 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration PATHWORKS Advanced Server and NetWare Server Installation Procedure Note: the server frequently accesses the data files stored on the SYS volume. 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. * NetWare SYS volume location [SYS$SYSDEVICE:[PWVN$SYSVOL]]: DISK$PWRK:[PWVN$SYSVOL] Optional DECprint Supervisor Available -------------------------------------- The PATHWORKS for OpenVMS distribution media includes two kits for the DECprint Supervisor for OpenVMS: VAX and Alpha. DECprint Supervisor for OpenVMS is a family of layered products that runs on OpenVMS VAX and Alpha to provide access through the OpenVMS queueing system to selected PostScript printers. To use DECprint Supervisor for OpenVMS, you must install the kit for either VAX or Alpha accordingly. You do not need a separate license to use DECprint Supervisor for OpenVMS with Advanced Server clients. * Press RETURN to continue: 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 ... %VMSINSTAL-I-RESTORE, Restoring product save set G ... %PWRK-I-RESTORE, Restoring product save set H (NetWare SYS Volume) ... %PWRK-I-PURGING, Purging PATHWORKS for OpenVMS (NetWare) files moved to SYS Volume %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PWVN]. %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands %PWRK-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COM %PWRK-I-SPECIFY, Specifying target directories for the provided files %PWRK-I-OBSOLETE, Deleting obsolete files Advanced Server and NetWare Server Installation and Configuration D-3 Sample Combined PATHWORKS Advanced Server and NetWare Server Installation Procedure Next Steps ---------- To continue the installation procedure, enter the following commands to execute the server configuration command procedures: $ @SYS$UPDATE:PWRK$CONFIG $ @SYS$UPDATE:PWVN$CONFIG For information about the configuration command procedures, see the PATHWORKS (Advanced Server) Installation and Configuration Guide. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting Installation Verification Procedure for PATHWORKS V6.0 for OpenVMS (Advanced Server) %PWRK-I-NORMAL, IVP completed successfully Starting Installation Verification Procedure for PATHWORKS V1.0G for OpenVMS (NetWare) %PWVN-I-NORMAL, IVP completed successfully Installation of PWRK V6.0 completed at 15:05 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA VMSINSTAL procedure done at 15:05 D-4 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration Combined PATHWORKS Advanced Server and NetWare Configuration Procedures ________________________________________________________________ Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedures The following example shows sample configuration dialogs for the PATHWORKS Advanced Server and NetWare servers. $ @SYS$UPDATE:PWRK$CONFIG PATHWORKS V6.0 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 12000 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 ... Advanced Server and NetWare Server Installation and Configuration D-5 Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedures 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]: N 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.0 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 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. D-6 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration Combined PATHWORKS Advanced Server and NetWare Configuration Procedures 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.0 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.0 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.0 for OpenVMS on node COBRAZ now [yes]: Y PATHWORKS file server will use DECnet. PATHWORKS mail notification will use DECnet. Process NETBIOS created with identification 202000AB Process PWRK$LICENSE_R created with identification 202000AE The PATHWORKS V6.0 server is configured to support 20 PC clients. Process PWRK$MASTER created with identification 202000B3 The master process will now start all other PATHWORKS processes. Advanced Server and NetWare Server Installation and Configuration D-7 Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedures $ @SYS$UPDATE:PWVN$CONFIG ***************************************************************** * PATHWORKS V1.0G for OpenVMS (NetWare) Configuration Procedure * ***************************************************************** * * * Copyright (C) 1992, 1997 by * * Digital Equipment Corporation, Maynard, Massachusetts * * and * * Novell, Incorporated * * All rights reserved. * * * ***************************************************************** This procedure will help you to set up and configure your PATHWORKS for OpenVMS (NetWare) installation. If you need help with any question asked by this procedure, reply to the question with a question mark (?). * Press RETURN to continue: Defining PATHWORKS for OpenVMS (NetWare) logical names. 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 12000 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. D-8 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration Combined PATHWORKS Advanced Server and NetWare Configuration Procedures 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 The PATHWORKS directory tree already exists on SYS$SYSDEVICE:. If you specify a different disk device, the PATHWORKS directory tree will be moved to the new device. * Enter disk device name where PATHWORKS data files will be stored [SYS$SYSDEVICE:]: DISK$PWRK: Creating NetWare directory tree... Scanning for supported Ethernet/TokenRing/FDDI controllers. Please wait... PATHWORKS for OpenVMS (NetWare) has never been configured on this system. * Press RETURN to continue: +-----------------------------------+ | Current Configuration Information | +-----------------------------------+ Type Control-Y to abort configuration. Server name : COBRAZ_PNW NVT Server name : NONE System-specific directory : SYS$SPECIFIC:[PWVN$PRIVATE] Run License Server : NO Internal Network Number : 000032B3 Maximum SPX sockets : 50 Network Type : Connection : DLPI type : Network Number : Perform Bindup : N/A Start Server when done : YES There are no networks configured yet. * Press RETURN to continue: Advanced Server and NetWare Server Installation and Configuration D-9 Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedures PATHWORKS for OpenVMS (NetWare) File Server name must be unique on all known IPX networks. * Name of PATHWORKS for OpenVMS (NetWare) file server [COBRAZ_PNW]: The PATHWORKS for OpenVMS (NetWare) product requires a system-specific directory to hold configuration information for the file server, and print server. It needs to be on a disk with at least 3000 free disk blocks. * System-specific directory [SYS$SPECIFIC:[PWVN$PRIVATE]]: Novell Virtual Terminal (NVT) allows NetWare clients to log into this node using terminal emulation software that supports the NVT protocol. * Do you want to configure NVT on this system [NO]? PATHWORKS for OpenVMS (NetWare) client licenses are granted by the License Server. In order to run a License Server, you must have a loaded PAK of client licenses. In an OpenVMS cluster, all members either do or do not run the license server, even though only one member actively serves licenses. However, if this member fails and stops serving licenses, another member takes over automatically. If you choose to run the license server, then the LAN Manager startup command procedure will also start the license server. If you choose not to run the license server, then the LAN Manager startup command procedure will also not start the license server. * Do you want to run a License Server on this system [NO]? This is the internal network number used by the file server. It should be unique on your network (i.e. there should be no other NetWare File Server with this same internal network number). If you are running DECnet, the default value is your DECnet address converted to hex and padded with leading zeros. e.g.: node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864" If you are not running DECnet, the default value is "00000DEC" (which just happens to be a valid hexadecimal number). * Internal network number (hexadecimal) [000032B3]: D-10 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration Combined PATHWORKS Advanced Server and NetWare Configuration Procedures Maximum SPX sockets is the maximum number of SPX sockets available to processes using the IPX/SPX stack provided with PATHWORKS for OpenVMS (NetWare). If you plan to only use PATHWORKS for OpenVMS (NetWare), then you need not set SPX sockets any larger than max NVT connections. If, however, you are planning on using other products that use the IPX stack, then you should consult the documentation for those products when configuring this parameter. Valid values for SPX sockets are 50, 200, 500 and 1000 (but no smaller than max NVT connections). If you change this parameter, you must reboot for it to take effect. * Maximum SPX sockets [50]: Network Type : Connection : DLPI type : Network Number : There are no networks configured yet. At least one network must be configured in order to proceed. * Network Configuration Action (ADD) [ADD]: Configuring a new network. There are two types of networks that can be configured. "LOCAL" networks are networks that have direct connections to an physical Network controller. There can only be as many "LOCAL" networks as there are physical Network controllers on this system. "TUNNEL" networks connect to another node also running the IPX DECnet Tunnel. The total number of "TUNNEL" networks is eight, minus however many "LOCAL" networks are configured (i.e. if 2 "LOCAL" networks are configured, then there can be up to 6 "TUNNEL" networks"). There can only be one "TUNNEL" network for each remote DECnet node name. "NONE" returns you to Network Configuration Action prompt. * Network Type (LOCAL,TUNNEL,NONE) [L]: Currently available Network controller list: EZA(Ethernet), FAA(FDDI), NONE "NONE" will return you to the Network Configuration Action prompt. * Choose a Network controller from above listing [EZA]: Input values for selecting a frame-type (DLPI-type) are: Advanced Server and NetWare Server Installation and Configuration D-11 Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedures DIX/SNAP IEEE-802.2 Raw-802.3 Media: (Sap E0) (Old: Novell) ------ -------- ---------- ------------- Token Ring: (1) (2) FDDI: (3) (4) Ethernet: (5) (6) (7) Select a frame type for this >>>ETHERNET<<< device. * Enter 5 if Ethernet_II(DIX), 6 if 802.2(Sap E0), or 7 if Raw-802.3 [5]: Each configured network must have a unique Network Number. This is a hexadecimal (0-9,A-F) number that can be up to 8 digits long. For more information on choosing a Network Number, see the PATHWORKS for OpenVMS (NetWare) Server Installation Guide. "NONE" will return you to the Network Configuration Action prompt. * Network Number [0]: 2100001 #1 --- Network Type : Local Connection : EZA DLPI type : ETH_II_DIX Network Number : 02100001 A maximum of eight (8) networks can be configured. If the above networks are configured correctly, then enter NONE. * Network Configuration Action (ADD,DELETE,MODIFY,NONE) [NONE]: This configuration procedure can start PATHWORKS for OpenVMS (NetWare) when it completes. If you do not answer YES, then BINDUP will not be run, even if you have chosen to do so. * Do you want to start PATHWORKS for OpenVMS (NetWare) now [YES]? +-----------------------------------+ | Current Configuration Information | +-----------------------------------+ Type Control-Y to abort configuration. D-12 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration Combined PATHWORKS Advanced Server and NetWare Configuration Procedures Server name : COBRAZ_PNW NVT Server name : NONE System-specific directory : SYS$SPECIFIC:[PWVN$PRIVATE] Run License Server : NO Internal Network Number : 000032B3 Maximum SPX sockets : 50 #1 --- Network Type : Local Connection : EZA DLPI type : ETH_II_DIX Network Number : 02100001 Perform Bindup : N/A Start Server when done : YES * Is this configuration satisfactory [YES]? Writing PWVN$CONF_DIR:PWVN$NWCONFIG.CFG file Writing PWVN$CONF_DIR:PWVN$NPSCONFIG.CFG file Writing PWVN$CONF_DIR:PWVN$CONF_SYMBOLS.COM file Writing Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$MSGS.DAT Writing Sconsole Message file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$SCONSOLE.HELP Writing Config Help file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$CONFIG.HELP Writing NetWare printer config file SYS$SPECIFIC:[PWVN$PRIVATE]PWVN$NWPRINT.CFG Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM file Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM file Setting file ownership in SYS$SYSDEVICE:[PWVN$SYSVOL] to user PWRK$DEFAULT Ignore any "SYSTEM-W-ACCONFLICT, file access conflict." warnings. Defining logical names for PATHWORKS V1.0G for OpenVMS (NetWare) Begin verifying minimum resources...OK Complete verifying minimum resources...OK PATHWORKS file server will use IPX. PATHWORKS mail notification will use DECnet. Process NETBIOS already created Process PWRK$LICENSE_R already created Starting IPX Daemon (NPSD)... Starting PATHWORKS for OpenVMS (NetWare) Server... Advanced Server and NetWare Server Installation and Configuration D-13 Sample Combined PATHWORKS Advanced Server and NetWare Configuration Procedures OK Purging old server logs... Purging old config files... IPX/DECnet Tunnel Daemon (STU) : INACTIVE IPX Daemon (NPSD) : ACTIVE PATHWORKS for OpenVMS (NetWare) Server : ACTIVE Print Services : INACTIVE NVT Daemon (NVT) : INACTIVE PATHWORKS for OpenVMS (NetWare) has been started with the command: @SYS$STARTUP:PWVN$STARTUP.COM DIGITAL recommends that the above command be placed in your site-specific system startup file in the SYS$MANAGER directory to automatically start PATHWORKS for OpenVMS (NetWare) each time the system is re-booted. IMPORTANT: Some sites use OpenVMS disk quotas. If your site does so, then you may need to use the DISKQUOTA utility and enter a record for the PATHWORKS for OpenVMS (NetWare) Guest Account. IMPORTANT: By default the PATHWORKS for OpenVMS (NetWare) SUPERVISOR account does not have a password. It is suggested that after the file server is running that you change the SUPERVISOR password. Note that this must be done from a PC client logged in to this file server using the client utility SYSCON. The configuration of PATHWORKS for OpenVMS (NetWare) is complete. D-14 Sample PATHWORKS Advanced Server and NetWare Server Installation and Configuration E ________________________________________________________________ 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. ________________________________________________________________ Sample Standalone License Server Installation Procedure The following example shows a sample installation dialog for the standalone license server. $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure V6.2 It is 16-MAY-1997 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: PWRK V6.0 Beginning installation of PWRK 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 Please select which components to install: PATHWORKS V6.0 for OpenVMS (Advanced Server) PATHWORKS V1.0G for OpenVMS (NetWare) * Do you want to install the PATHWORKS for OpenVMS (Advanced Server) [NO]? * Do you want to install the NetWare server [NO]? * Do you want to install the PATHWORKS license server [YES]? Standalone License Server Installation and Configuration Procedure E-1 Sample Standalone License Server Installation Procedure The following components will be installed: PATHWORKS V6.0 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]? NOTE ---- Because this kit provides a new streams execlet for NetBEUI, TCP/IP, IPX, and SPX, 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]? N * 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 104600 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 ... %PWRK-I-SKIPSET, Skipping product save set G (Alpha NetWare only) ... %PWRK-I-SKIPSET, Skipping product save set H (NetWare SYS Volume) ... %PWRK-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL %PWRK-I-DCLCMDS, Installing PATHWORKS DCL commands %PWRK-I-WRTLOGICAL, Creating PWVN$COMMON_LOGICALS.COM %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 commands to execute the server configuration command procedures: E-2 Sample Standalone License Server Installation and Configuration Procedure Sample Standalone License Server Installation Procedure $ @SYS$UPDATE:PWRK$CONFIG $ @SYS$UPDATE:PWVN$CONFIG For information about the configuration command procedures, see the PATHWORKS (Advanced Server) Installation and Configuration Guide. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting Installation Verification Procedure for PATHWORKS V6.0 for OpenVMS (Advanced Server) %PWRK-I-NORMAL, IVP completed successfully Installation of PWRK V6.0 completed at 16:15 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA VMSINSTAL procedure done at 16:15 ________________________________________________________________ Sample PATHWORKS Advanced Server Configuration Procedure for the Standalone License Server The following is a sample PATHWORKS Advanced Server configuration procedure for the standalone license server. $ @SYS$UPDATE:PWRK$CONFIG PATHWORKS V6.0 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 12000 free blocks of disk space to store these data files. Standalone License Server Installation and Configuration Procedure E-3 Sample PATHWORKS Advanced Server Configuration Procedure for the Standalone License Server 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, and NetWare clients over IPX. The Advanced Server and NetWare file servers do not need to be running for the license server to operate. If you want to serve PATHWORKS licenses for NetWare clients over IPX, you must later execute @SYS$UPDATE:PWVN$CONFIG.COM. Do you want to serve PATHWORKS licenses over DECnet [yes]: Do you want to serve PATHWORKS licenses over NetBEUI [no]: Do you want to serve PATHWORKS licenses over TCP/IP [no]: Do you want to start the PATHWORKS license server now [yes]: %PWRK-F-REBOOT, system must be rebooted before starting PATHWORKS ________________________________________________________________ Sample NetWare Configuration Procedure for the Standalone License Server The following is a sample NetWare configuration procedure for the standalone license server. E-4 Sample Standalone License Server Installation and Configuration Procedure NetWare Configuration Procedure for the Standalone License Server $ @SYS$UPDATE:PWVN$CONFIG ***************************************************************** * PATHWORKS V1.0G for OpenVMS (NetWare) Configuration Procedure * ***************************************************************** * * * Copyright (C) 1992, 1997 by * * Digital Equipment Corporation, Maynard, Massachusetts * * and * * Novell, Incorporated * * All rights reserved. * * * ***************************************************************** This procedure will help you to set up and configure your PATHWORKS for OpenVMS (NetWare) installation. If you need help with any question asked by this procedure, reply to the question with a question mark (?). * Press RETURN to continue: Defining PATHWORKS for OpenVMS (NetWare) logical names. 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 12000 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. Standalone License Server Installation and Configuration Procedure E-5 Sample NetWare Configuration Procedure for the Standalone License Server 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 The PATHWORKS directory tree already exists on SYS$SYSDEVICE:. If you specify a different disk device, the PATHWORKS directory tree will be moved to the new device. * Enter disk device name where PATHWORKS data files will be stored [SYS$SYSDEVICE:]: DISK$PWRK: Scanning for supported Ethernet/TokenRing/FDDI controllers. Please wait... PATHWORKS for OpenVMS (NetWare) has never been configured on this system. * Press RETURN to continue: +-----------------------------------+ | Current Configuration Information | +-----------------------------------+ Type Control-Y to abort configuration. System-specific directory : SYS$SPECIFIC:[PWVN$PRIVATE] Serve licenses over IPX : YES Internal Network Number : 000032B3 Maximum SPX sockets : 50 Network Type : Connection : DLPI type : Network Number : Reboot system when done : YES Start Server when done : N/A There are no networks configured yet. * Press RETURN to continue: The PATHWORKS for OpenVMS (NetWare) product requires a system-specific directory to hold configuration information for the file server, and print server. It needs to be on a disk with at least 3000 free disk blocks. E-6 Sample Standalone License Server Installation and Configuration Procedure NetWare Configuration Procedure for the Standalone License Server * System-specific directory [SYS$SPECIFIC:[PWVN$PRIVATE]]: PATHWORKS for OpenVMS (NetWare) client licenses are granted by the License Server, provided the License Server is configured to serve licenses over IPX. In order to run a License Server, you must have a loaded PAK of client licenses. * Do you want to serve PATHWORKS licenses over IPX [YES]? This is the internal network number used by the file server. It should be unique on your network (i.e. there should be no other NetWare File Server with this same internal network number). If you are running DECnet, the default value is your DECnet address converted to hex and padded with leading zeros. e.g.: node 62.100 becomes: (62 x 1024) + 100 = 63588 = "0000F864" If you are not running DECnet, the default value is "00000DEC" (which just happens to be a valid hexadecimal number). * Internal network number (hexadecimal) [000032B3]: Maximum SPX sockets is the maximum number of SPX sockets available to processes using the IPX/SPX stack provided with PATHWORKS for OpenVMS (NetWare). If you plan to only use PATHWORKS for OpenVMS (NetWare), the default value of 50 is acceptable. If, however, you are planning on using other products that use the IPX stack, then you should consult the documentation for those products when configuring this parameter. Valid values for SPX sockets are 50, 200, 500 and 1000. If you change this parameter, you must reboot for it to take effect. * Maximum SPX sockets [50]: Network Type : Connection : DLPI type : Network Number : There are no networks configured yet. At least one network must be configured in order to proceed. * Network Configuration Action (ADD) [ADD]: Configuring a new network. Standalone License Server Installation and Configuration Procedure E-7 Sample NetWare Configuration Procedure for the Standalone License Server There are two types of networks that can be configured. "LOCAL" networks are networks that have direct connections to an physical Network controller. There can only be as many "LOCAL" networks as there are physical Network controllers on this system. "TUNNEL" networks connect to another node also running the IPX DECnet Tunnel. The total number of "TUNNEL" networks is eight, minus however many "LOCAL" networks are configured (i.e. if 2 "LOCAL" networks are configured, then there can be up to 6 "TUNNEL" networks"). There can only be one "TUNNEL" network for each remote DECnet node name. "NONE" returns you to Network Configuration Action prompt. * Network Type (LOCAL,TUNNEL,NONE) [L]: Currently available Network controller list: EZA(Ethernet), FAA(FDDI), NONE "NONE" will return you to the Network Configuration Action prompt. * Choose a Network controller from above listing [EZA]: Input values for selecting a frame-type (DLPI-type) are: DIX/SNAP IEEE-802.2 Raw-802.3 Media: (Sap E0) (Old: Novell) ----- -------- ---------- ------------- Token Ring: (1) (2) FDDI: (3) (4) Ethernet: (5) (6) (7) Select a frame type for this >>>ETHERNET<<< device. * Enter 5 if Ethernet_II(DIX), 6 if 802.2(Sap E0), or 7 if Raw-802.3 [5]: Each configured network must have a unique Network Number. This is a hexadecimal (0-9,A-F) number that can be up to 8 digits long. For more information on choosing a Network Number, see the PATHWORKS for OpenVMS (NetWare) Server Installation Guide. "NONE" will return you to the Network Configuration Action prompt. * Network Number [0]: 2100001 #1 --- Network Type : Local Connection : EZA DLPI type : ETH_II_DIX Network Number : 02100001 E-8 Sample Standalone License Server Installation and Configuration Procedure NetWare Configuration Procedure for the Standalone License Server A maximum of eight (8) networks can be configured. If the above networks are configured correctly, then enter NONE. * Network Configuration Action (ADD,DELETE,MODIFY,NONE) [NONE]: This configuration procedure can reboot the system automatically when it completes. If you do not answer YES, you must reboot the system by hand before starting the PATHWORKS for OpenVMS (NetWare) file server. * Do you want to reboot the system now [YES]? +-----------------------------------+ | Current Configuration Information | +-----------------------------------+ Type Control-Y to abort configuration. System-specific directory : SYS$SPECIFIC:[PWVN$PRIVATE] Serve licenses over IPX : YES Internal Network Number : 000032B3 Maximum SPX sockets : 50 #1 --- Network Type : Local Connection : EZA DLPI type : ETH_II_DIX Network Number : 02100001 Reboot system when done : YES Start Server when done : N/A * Is this configuration satisfactory [YES]? Writing PWVN$CONF_DIR:PWVN$NPSCONFIG.CFG file Writing PWVN$CONF_DIR:PWVN$CONF_SYMBOLS.COM file Writing SYS$COMMON:[SYS$STARTUP]PWVN$COMMON_LOGICALS.COM file Writing SYS$SPECIFIC:[SYS$STARTUP]PWVN$PRIVATE_LOGICALS.COM file To start PATHWORKS for OpenVMS (NetWare), issue the following command: @SYS$STARTUP:PWVN$STARTUP.COM DIGITAL recommends that the above command be placed in your site-specific system startup file in the SYS$MANAGER directory to automatically start PATHWORKS for OpenVMS (NetWare) each time the system is re-booted. The configuration of PATHWORKS for OpenVMS (NetWare) is complete. Standalone License Server Installation and Configuration Procedure E-9 F ________________________________________________________________ Upgrade Utility Installation This appendix shows a sample installation of the Upgrade utility. ________________________________________________________________ Installing the Upgrade Utility As a first step in upgrading a system that is running a previously released version of DIGITAL PATHWORKS for OpenVMS, you can install the Upgrade utility without installing the server. Doing this allows you to run your V5 servers 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 Version 5 executables are not replaced. When you execute the installation procedure on a system that is running PATHWORKS Version 5, 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 F-1 Sample Upgrade Utility Installation Procedure ________________________________________________________________ Sample Upgrade Utility Installation Procedure The following example shows a sample procedure for installation of the Upgrade utility only. $ @SYS$UPDATE:VMSINSTAL PWRK060 SYS$DEVICE:[KITS.PWRK] OpenVMS AXP Software Product Installation Procedure E7.1 It is 22-MAY-1997 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: PWRK V6.0 Beginning installation of PWRK 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 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: * Do you want to install the upgrade utility only [NO]? Y %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 27100 free blocks %VMSINSTAL-I-RESTORE, Restoring product save set C ... Next Step --------- F-2 Upgrade Utility Installation Sample Upgrade Utility Installation Procedure 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... Installation of PWRK V6.0 completed at 15:15 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]PWRK060.VMI_DATA VMSINSTAL procedure done at 15:16 Upgrade Utility Installation F-3 G ________________________________________________________________ Files Installed This appendix lists the files that are created during the installation procedure and includes the following information: o Table G-1 lists files common to both the PATHWORKS Advanced Server and NetWare servers. o Table G-2 lists the files installed for the PATHWORKS Advanced Server only. o Table G-3 lists the files installed for the NetWare server only. This appendix also shows the on-disk structure of the PATHWORKS Advanced Server and NetWare server. ________________________________________________________________ Files Common to PATHWORKS Advanced Server and NetWare Table G-1 describes the files created during the installation of either the PATHWORKS Advanced Server, the NetWare server, or both. Files Installed G-1 Files Common to PATHWORKS Advanced Server and NetWare Table G-1 Files Common to PATHWORKS Advanced Server and NetWare __________Server________________________________________________ File_________________________________Description________________ DCPS$EXAMPLES:PWRK$BORDER.LUP DECprint Supervisor printer layup for borders DCPS$EXAMPLES:PWRK$NOBORDER.LUP DECprint Supervisor printer layup for no borders DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_ DECprint Supervisor printer BORDER.LUP layup for borders with Windows DCPS$EXAMPLES:PWRK$REV_LANDSCAPE_ DECprint Supervisor printer NOBORDER.LUP layup for no borders with Windows SYS$HELP:PCDISKHLP.HLB DOS File Maintenance utility help library SYS$HELP:PWRK$ADMIN_LIC.HLB License Manager help library SYS$HELP:PWRK060.RELEASE_NOTES DIGITAL PATHWORKS for OpenVMS (Advanced Server) Release Notes SYS$HELP:PWVNV10G.RELEASE_NOTES DIGITAL PATHWORKS for OpenVMS (NetWare) Release Notes 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 (continued on next page) G-2 Files Installed Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$LIBRARY:PWRK$CSSHR_V7.EXE Common services shareable image 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) Files Installed G-3 Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$LIBRARY:PWRK$DEVCTL_LN03P.TLB LN03 PLUS device control library SYS$LIBRARY:PWRK$DEVCTL_ Proprinter device control PROPRINTER.TLB library SYS$LIBRARY:PWRK$DEVCTL_ Silentwriter device control SILENTWRITER.TLB library SYS$LIBRARY:PWRK$FSLIB_ODS2.EXE ODS2 addon library SYS$LIBRARY:PWRK$LICENSE_LIBSHR.EXE License shareable library SYS$LIBRARY:PWRK$LICENSE_ License management MGMTSHR.EXE shareable image SYS$LIBRARY:PWRK$PCMALTSHR.EXE Alternative PATHWORKS cache manager shareable image SYS$LIBRARY:PWRK$PCMSHR.EXE PATHWORKS cache manager shareable image SYS$LIBRARY:PWRK$PRINTER_ Printer information file INFORMATION.DAT SYS$LIBRARY:PWRK$SDA.EXE PATHWORKS extension for the System Dump Analyzer SYS$LIBRARY:PWRK$STREAMSSHR_V7.EXE Streams shareable image SYS$LIBRARY:PWRK$VVTERMCAP.DAT License manager terminal capability data file SYS$LIBRARY:PWRK$WINLIBSHR.EXE Advanced Server character- cell user interface shareable image SYS$LIBRARY:PWRK$XTILIBSHR.EXE X/Open Transport Interface shareable library SYS$LIBRARY:PWRK$XTINETBIOSSHR.EXE X/Open Transport Interface shareable image for NETBIOS (continued on next page) G-4 Files Installed Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$LIBRARY:PWRK$XTINSPNBSHR.EXE X/Open Transport Interface shareable image for DECnet SYS$LIBRARY:XTI.H X/Open Transport Interface header file SYS$LOADABLE_ Data structure definitions IMAGES:PCFSDRIVERDEF.STB 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_ Command procedure that COMMANDS.COM[1] defines foreign commands for PATHWORKS utilities SYS$MANAGER:PWRK$SHOWSYS.COM Command procedure that shows status of PATHWORKS V5 processes SYS$MANAGER:PWVN$COMMANDS.COM Command procedure that defines foreign commands for NetWare utilities [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) Files Installed G-5 Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$MANAGER:PWVN$COPY_CRASH.COM Command procedure that copies a system crash dump SYS$MESSAGE:PWRK$MSG.EXE DIGITAL PATHWORKS for OpenVMS message file SYS$STARTUP:PWRK$CHECK_PARAMS.COM Command procedure that checks system resources SYS$STARTUP:PWRK$COMMON_ Command procedure that LOGICALS.COM defines common logicals SYS$STARTUP:PWRK$COMMON_ Common shutdown command SHUTDOWN.COM procedure SYS$STARTUP:PWRK$COMMON_STARTUP.COM Common startup command procedure SYS$STARTUP:PWRK$GATHER_INFO.COM Gathers information into a save set for engineering debugging 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 (continued on next page) G-6 Files Installed Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$STARTUP:PWVN$COMMON_ Command procedure that LOGICALS.COM defines NetWare cluster- common logical names SYS$STARTUP:PWVN$LOGICALS.COM Command procedure that defines NetWare logical names SYS$STARTUP:PWVN$NPSD_START.COM Command procedure that runs the NetWare Protocol Suite Daemon SYS$STARTUP:PWVN$SHUTDOWN.COM NetWare shutdown command procedure SYS$STARTUP:PWVN$STARTUP.COM NetWare startup command procedure SYS$STARTUP:PWVN$TUNNEL_START.COM Command procedure that runs the NetWare DECnet tunnel SYS$SYSTEM:NETBIOS.EXE NETBIOS for DECnet SYS$SYSTEM:PCDISK.EXE DOS File Maintenance utility SYS$SYSTEM:PCSA$MAIL_SERVER.EXE PATHWORKS 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$EVTREPORT.EXE Event logger report generator SYS$SYSTEM:PWRK$KNBDAEMON.EXE Kernel NETBIOS daemon process (continued on next page) Files Installed G-7 Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$SYSTEM:PWRK$LICENSE_ License count units utility COUNTUNITS.EXE[1] SYS$SYSTEM:PWRK$LICENSE_MANAGER.EXE License manager user interface SYS$SYSTEM:PWRK$LICENSE_ License registrar REGISTRAR.EXE SYS$SYSTEM:PWRK$LICENSE_SERVER.EXE License server SYS$SYSTEM:PWRK$LOADSTREAMS_V7.EXE Loader for streams system loadable image SYS$SYSTEM:PWRK$MASTER.EXE Master process and event logger SYS$SYSTEM:PWRK$MONITOR.EXE PATHWORKS Monitor SYS$SYSTEM:PWRK$NBDAEMON.EXE NETBIOS daemon process SYS$SYSTEM:PWRK$NBSHOW.EXE[1] NetBEUI show status utility SYS$SYSTEM:PWRK$PWMON.EXE[1] PATHWORKS host-based monitor utility SYS$SYSTEM:PWRK$SETSHO.EXE PATHWORKS Set/Show Parameters utility SYS$SYSTEM:PWRK$SHOWQUOTA.EXE Show Disk Quota utility SYS$SYSTEM:PWRK$START.EXE Utility that starts detached master process SYS$SYSTEM:PWRK$STOP.EXE Utility that stops PATHWORKS processes SYS$SYSTEM:PWRK$VERIFY.EXE Utility that verifies configuration parameters SYS$SYSTEM:PWVN$DROUTER.EXE NetWare utility that dumps the router tables [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) G-8 Files Installed Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$SYSTEM:PWVN$GETLAN.EXE NetWare utility that shows this node's network SYS$SYSTEM:PWVN$MERGE.EXE NetWare utility that merges configuration files SYS$SYSTEM:PWVN$NPSD.EXE NetWare Protocol Suite Daemon (NPSD) SYS$SYSTEM:PWVN$NWCP.EXE NetWare control program SYS$SYSTEM:PWVN$RROUTER.EXE NetWare utility that resets the router tables SYS$SYSTEM:PWVN$SAPD.EXE Netware SAP Daemon SYS$SYSTEM:PWVN$STUACP.EXE NetWare DECnet tunnel SYS$TEST:PWRK$IVP.COM PATHWORKS Advanced Server Installation Verification Procedure (IVP) SYS$TEST:PWRK$IVP.DAT PATHWORKS Advanced Server Installation Verification Procedure data file SYS$TEST:PWVN$IVP.COM NetWare Installation Verification Procedure (IVP) SYS$TEST:PWVN$IVP.DAT NetWare Installation Verification procedure data file SYS$UPDATE:PWL$SERVER_STATE.DAT[2] NetWare license server state file SYS$UPDATE:PWRK$COMMANDS.CLD PATHWORKS command line definitions [2]This_file_is_installed_only_if_DIGITAL_PATHWORKS_V1.0G_for___ OpenVMS (NetWare) is being installed and you are upgrading from PATHWORKS V1.0C for OpenVMS (NetWare). (continued on next page) Files Installed G-9 Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$UPDATE:PWRK$COMMON.SAV[3] Backup saveset for the initial PATHWORKS common directory tree SYS$UPDATE:PWRK$COMMON_CONFIG.COM Common configuration command procedure SYS$UPDATE:PWRK$CONFIG.COM One-time configuration command procedure SYS$UPDATE:PWRK$DEFINE_FORMS.COM[3] Command procedure that defines printer forms for PATHWORKS SYS$UPDATE:PWRK$DEINSTAL.COM DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server) removal command procedure SYS$UPDATE:PWRK$GETPARAM.COM Command procedure that gets a parameter from LANMAN.INI SYS$UPDATE:PWRK$INSTALL_ Command procedure that COMMANDS.COM installs PATHWORKS DCL commands SYS$UPDATE:PWRK$LICENSE_CONFIG.COM License server configuration command procedure SYS$UPDATE:PWRK$SETINI.COM Command procedure that updates LANMAN.INI parameters SYS$UPDATE:PWRK$SETPARAM.COM Command procedure that sets a parameter in LANMAN.INI SYS$UPDATE:PWRK$VERSIONS.COM Command procedure that shows PATHWORKS image versions [3]This_file_is_deleted_after_you_configure_the_server._________ (continued on next page) G-10 Files Installed Files Common to PATHWORKS Advanced Server and NetWare Table G-1 (Cont.) Files Common to PATHWORKS Advanced Server and __________________NetWare_Server________________________________ File_________________________________Description________________ SYS$UPDATE:PWVN$CONFIG.COM NetWare configuration command procedure SYS$UPDATE:PWVN$DEINSTAL.COM NetWare product removal command procedure SYS$UPDATE:PWVN$RESIZE_STACK.COM Command procedure that configures the NetWare _____________________________________transports_________________ ________________________________________________________________ Files Created During the PATHWORKS Advanced Server Installation Table G-2 describes the files created during the PATHWORKS Advanced Server installation. Table_G-2_PATHWORKS_Advanced_Server_Files_______________________ File_________________________________Description________________ SYS$HELP:PWRK$ADMIN_CFG.HLB Configuration Manager tool help library SYS$HELP:PWRK$MANAGER.HLB ADMINISTER commands help library SYS$HELP:PWRK$SHOWINI.HLB[1] Show LANMAN.INI Parameters utility help library SYS$HELP:PWRK$V6UPGRADE.HLB Upgrade utility help library SYS$LIBRARY:PWRK$ACME_MODULE_ External authentication ALPHA.EXE ALPHA image [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) Files Installed G-11 Files Created During the PATHWORKS Advanced Server Installation Table_G-2_(Cont.)_PATHWORKS_Advanced_Server_Files_______________ File_________________________________Description________________ SYS$LIBRARY:PWRK$ACME_MODULE_ External authentication VAX VAX.EXE image SYS$LIBRARY:PWRK$CMT_LM.EXE Advanced Server interface to the Configurator, Monitor, and Tuner SYS$LIBRARY:PWRK$LMAPISHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$LMRPCAPISHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$LMRPCSHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$LMRPCXNPSHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$LMTASKSHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$MGTLIBSHR.EXE Advanced Server shareable image SYS$LIBRARY:PWRK$NBLIB_DECNET.EXE Advanced Server network interface to DECnet SYS$LIBRARY:PWRK$NBLIB_NETBEUI.EXE Advanced Server network interface to NetBEUI SYS$LIBRARY:PWRK$NBLIB_TCPIP.EXE Advanced Server network interface to TCP/IP SYS$STARTUP:PCSA$MAIL_STARTUP.COM "pcsamail" command for TCP /IP clients invoking the PATHWORKS mail server SYS$STARTUP:PWRK$ACME_STARTUP.COM Single signon startup file SYS$STARTUP:PWRK$LMBROWSER_ Browser startup file START.COM (continued on next page) G-12 Files Installed Files Created During the PATHWORKS Advanced Server Installation Table_G-2_(Cont.)_PATHWORKS_Advanced_Server_Files_______________ File_________________________________Description________________ SYS$STARTUP:PWRK$LMDMN_START.COM Command procedure that runs the Advanced Server daemon SYS$STARTUP:PWRK$LMMCP_START.COM Command procedure that runs the Advanced Server controller SYS$STARTUP:PWRK$LMSRV_START.COM Command procedure that runs the Advanced Server SYS$STARTUP:PWRK$PCSA_SHUTDOWN.COM PATHWORKS for VMS V4.x shutdown command procedure SYS$SYSTEM:PWRK$ADMIN.COM Remote Net Admin command procedure SYS$SYSTEM:PWRK$ADMIN.EXE Character-oriented, menu- driven Net Admin interface SYS$SYSTEM:PWRK$ADMIN_CFG.EXE Server configuration utility SYS$SYSTEM:PWRK$ADMIN_LIC.EXE License configuration utility SYS$SYSTEM:PWRK$BANNER.EXE Utility that collects system information and inserts it at top of log files SYS$SYSTEM:PWRK$CHGROUP.EXE[1] Standalone utility that manages the Advanced Server groups database SYS$SYSTEM:PWRK$CHUSER.EXE[1] Standalone utility that manages the Advanced Server user accounts database SYS$SYSTEM:PWRK$LMBROWSER.EXE Advanced Server browser image SYS$SYSTEM:PWRK$LMDMN.EXE Advanced Server daemon [1]This_file_is_(or_is_associated_with)_an_unsupported_utility__ or command procedure. (continued on next page) Files Installed G-13 Files Created During the PATHWORKS Advanced Server Installation Table_G-2_(Cont.)_PATHWORKS_Advanced_Server_Files_______________ File_________________________________Description________________ SYS$SYSTEM:PWRK$LMMCP.EXE Advanced Server controller SYS$SYSTEM:PWRK$LMSHARE.EXE[1] Standalone utility that manages the Advanced Server shares database SYS$SYSTEM:PWRK$LMSRV.EXE Advanced Server SYS$SYSTEM:PWRK$MANAGER.EXE ADMIN utility SYS$SYSTEM:PWRK$MODAL.EXE[1] Standalone utility that manages the Advanced Server modals database SYS$SYSTEM:PWRK$SHOWINI.EXE[1] Show LANMAN.INI Parameters utility 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 Advanced Server directory tree SYS$UPDATE:PWRK$LMCONFIG.COM Command procedure that sets up the initial Advanced Server directory tree SYS$UPDATE:PWRK$PWUTIL.SAV[2] Backup saveset for PATHWORKS client-based utilities SYS$UPDATE:PWRK$ROLLBACK.COM Used to restore V5 PATHWORKS environment SYS$UPDATE:PWRK$V6UPGRADE.COM Command procedure that runs the Upgrade utility SYS$UPDATE:PWRK$V6UPGRADE.EXE 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. ________________________________________________________________ G-14 Files Installed Files Created During the NetWare Installation ________________________________________________________________ Files Created During the NetWare Installation Table G-3 describes the files created during the NetWare installation. Table_G-3_NetWare_Files_________________________________________ File_________________________________Description________________ PWVN$EXAMPLES:EXAMPLE.C NetWare API program example in C PWVN$EXAMPLES:EXAMPLE.COM Command procedure that builds the example program PWVN$EXAMPLES:EXAMPLE.OPT Linker option file that links the program example PWVN$EXAMPLES:GETOPT.C Simple getopt routine for VMS PWVN$EXAMPLES:GETOPT.H Simple getopt routine header file SYS$LIBRARY:NWAPI.H NetWare API library header file SYS$LIBRARY:NWERRORS.H NetWare errors header file SYS$LIBRARY:PWVN$CACHE.EXE NetWare cache manager shareable image SYS$LIBRARY:PWVN$NWAPISHR.EXE NetWare APIs shareable image SYS$STARTUP:PWVN$NSSP_START.COM Startup for symbiont server SYS$STARTUP:PWVN$NVT_START.COM Command procedure that runs the NVT daemon SYS$STARTUP:PWVN$NWCP_START.COM Command procedure that runs the NetWare control program (continued on next page) Files Installed G-15 Files Created During the NetWare Installation Table_G-3_(Cont.)_NetWare_Files_________________________________ File_________________________________Description________________ SYS$STARTUP:PWVN$PSPAWNER_START.COM Command procedure that runs the NetWare print server spawner SYS$STARTUP:PWVN$SERVER_START.COM Command procedure that runs the NetWare server SYS$SYSTEM:PWVN$BANNER.EXE Utility that collects system information and inserts it at the top of log files SYS$SYSTEM:PWVN$BINDDOWN.EXE NetWare utility that downloads or uploads the bindery SYS$SYSTEM:PWVN$CLIENT.EXE Client print utility SYS$SYSTEM:PWVN$DOSLOGIN.EXE NetWare utility that does a login test from the host SYS$SYSTEM:PWVN$NETWARE.EXE NetWare file server SYS$SYSTEM:PWVN$NSSP.EXE Symbiont server SYS$SYSTEM:PWVN$NVTD.EXE NetWare Virtual Terminal (NVT) daemon SYS$SYSTEM:PWVN$PSERVER.EXE NetWare print server SYS$SYSTEM:PWVN$PSPAWNER.EXE NetWare print server spawner SYS$SYSTEM:PWVN$SCONSOLE.EXE NetWare system console SYS$SYSTEM:PWVN$SLIST.EXE NetWare utility that lists servers SYS$SYSTEM:PWVN$SMB.EXE Print symbiont SYS$SYSTEM:PWVN$TLIST.EXE NetWare utility that lists trustee rights SYS$SYSTEM:PWVN$ULIST.EXE NetWare utility that lists users (continued on next page) G-16 Files Installed Files Created During the NetWare Installation Table_G-3_(Cont.)_NetWare_Files_________________________________ File_________________________________Description________________ SYS$UPDATE:PWRK$NETWARE.SAV[1] Backup saveset for the initial NetWare directory tree SYS$UPDATE:PWRK$NWCONFIG.COM Command procedure that sets up the initial NetWare directory tree SYS$UPDATE:PWVN$CLD.CLD Command definition file [1]This_file_is_deleted_after_you_configure_the_server._________ ________________________________________________________________ ________________________________________________________________ PATHWORKS Advanced Server and NetWare Disk Structure Figure G-1 shows the PATHWORKS Advanced Server and NetWare on-disk structure. Note that only part of the substructure is shown. The LANMAN subdirectory is created only if you install and configure PATHWORKS Advanced Server. The NETWARE subdirectory is created only if you install and configure NetWare. Files Installed G-17 PATHWORKS Advanced Server and NetWare Disk Structure Figure G-1 Server On-Disk Structure Diagram pwrk$commonroot, pwrk$lmroot, pwrk$nwroot | |___lanman | : | :---accounts | :---addon | :---datafiles | :---logs | :---shares | :---upgrade | |___license | |___logs | |___print | |___NetWare | |___section | |___spool | |___temp G-18 Files Installed H ________________________________________________________________ PATHWORKS Advanced Server and NetWare Server Logical Names Table H-1 describes the logical names that are created when you configure or start either the PATHWORKS Advanced Server or NetWare server. Table H-1 DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server) __________Logical_Names_________________________________________ Logical_name__________Description_______________________________ PWRK$ADDON_LIBRARY Location of file system shareable images PWRK$COMMON Top level directory for PATHWORKS PWRK$COMMONROOT[1] Root of the PATHWORKS common directory tree PWRK$KNBDAEMON_ TCP/IP device DEVICE PWRK$LANMAN[2] Advanced Server area PWRK$LICENSE PATHWORKS license area PWRK$LMDATAFILES Advanced Server data files area PWRK$LMDEBUG Area where trace files are written PWRK$LMDOMAINS Advanced Server domain area PWRK$LMLOGS[2] Advanced Server log file area PWRK$LMROOT[1] Root of the Advanced Server directory tree PWRK$LMUPGRADE[2] Advanced Server upgrade area [1]This_logical_name_requires_that_you_specify_the_directory____ with it. [2]This logical name is defined for Advanced Server only. (continued on next page) PATHWORKS Advanced Server and NetWare Server Logical Names H-1 PATHWORKS Advanced Server and NetWare Server Logical Names Table H-1 (Cont.) DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced __________________Server)_Logical_Names_________________________ Logical_name__________Description_______________________________ PWRK$LOADSTREAMS Logical for LoadStreams image PWRK$LOGS Common log file area PWRK$NETBEUI_DEVICE NetBEUI device PWRK$NETWARE Top level NetWare area PWRK$NWROOT[1] Root of the NetWare directory tree PWRK$PARAMS Parameter area PWRK$PERFDATA PATHWORKS monitor performance data directory PWRK$PRINT PATHWORKS printer database directory PWRK$SECTION Section file area PWRK$SPOOL Spool area [1]This_logical_name_requires_that_you_specify_the_directory____ with it. ________________________________________________________________ H-2 PATHWORKS Advanced Server and NetWare Server Logical Names I ________________________________________________________________ NetWare Server Logical Names This appendix describes the logical names that are created only for the PATHWORKS for OpenVMS (NetWare) server. ________________________________________________________________ How NetWare Logical Names Are Created The installation procedure generates logical names for server directories and parameters. The configuration procedure modifies these names when you modify parameters. ________________________________________________________________ Types of NetWare Logical Names The configuration procedure, PWVN$CONFIG.COM, calls other command procedures to generate logical names. Table I-1 lists these command procedures and describes the types of logical names they generate. NetWare Server Logical Names I-1 Types of NetWare Logical Names Table_I-1_Types_of_NetWare_Logical_Names________________________ Type of Command_Procedure__________Name______Description________________ SYS$COMMON:[SYS$STARTUP] Common Shared by all configured - PWVN$COMMON_ NetWare servers on a LOGICALS.COM cluster. SYS$SPECIFIC:[SYS$STARTUP] Private Relevant only to the - PWVN$PRIVATE_ NetWare server on a LOGICALS.COM_________________________particular_node.___________ ________________________________________________________________ Common NetWare Logical Names Table I-2 describes common logical names defined by the PWVN$COMMON_LOGICALS.COM procedure. Table_I-2_Common_NetWare_Logical_Names__________________________ Logical_Name____________Description_____________________________ PWVN$CONFIGURED_LIST A list of the nodes that are configured on the cluster PWVN$EXAMPLES The directory location for example files PWVN$GUEST_ACCOUNT The name of the GUEST account on the file server PWVN$GUEST_UIC The User Identification Code (UIC) for the GUEST account on the file server PWVN$LANGUAGE The language (Version 1.0x supports English only) PWVN$SYSVOL_DIR The root directory for the PATHWORKS for OpenVMS (NetWare) SYS Volume PWVN$UPGRADE Obsolete (continued on next page) I-2 NetWare Server Logical Names Common NetWare Logical Names Table_I-2_(Cont.)_Common_NetWare_Logical_Names__________________ Logical_Name____________Description_____________________________ PWVN$IPX_SOCKETS[1] The number of available IPX sockets PWVN$SPX_SOCKETS[1] The number of available SPX sockets PWVN$NVT_USERS[1] The maximum number of users who can log in through Novell Virtual Terminal (NVT) [1]This_logical_name_is_added_by_the_configuration_procedure.___ ________________________________________________________________ ________________________________________________________________ Private NetWare Logical Names Table I-3 describes private logical names defined by the PWVN$PRIVATE_LOGICALS.COM procedure. Table_I-3_Private_NetWare_Logical_Names_________________________ Logical_Name_______Definition___________________________________ PWVN$CONF_DIR The directory location for the server configuration files PWVN$ENET_DEVS The names of the Ethernet controller devices used by the server PWVN$LOGFILES The directory location for the PATHWORKS for OpenVMS (NetWare) log files PWVN$NVT A flag that indicates whether Novell Virtual Terminal (NVT) is configured on the server PWVN$SERVER_NAME The name of the file server PWVN$TUNNEL A flag that indicates whether tunneling is ___________________enabled______________________________________ NetWare Server Logical Names I-3 ________________________________________________________________ Index A Cluster ___________________________ see OpenVMS cluster Administrator account Common logical names password on, 3-7 description of, I-2 Advanced Server Computer name computer name defined, SCSNODE parameter and, 3-6 1-14 domain name defined, 3-6 Configuration, Advanced on-disk structure, G-17 Server Advanced Server description of, 3-4 deinstallation procedure Configuration Manager, sample, 8-4 Advanced Server Alerter service running after description of, 3-6 configuration procedure alias, 3-7 , 3-4 Automatic shutdown Configuration procedure of file server, 6-9 for Advanced Server, term B defined, 3-1 ___________________________ for NetWare, term defined BACKUP command, 1-10 , 4-1 getting help for, 4-6 C__________________________ interrupting, 4-6 Checklist preparing for the summary, A-1 Advanced Server, 3-3 Client-based server preparing for the NetWare administration tools, , 4-5 2-19 prerequisites, 3-3 Client software questions in, 4-6 LAN Manager, 1-7 responding to prompts, NetWare, 1-8 3-9, 4-6, 5-4 running, 4-5 Index-1 Configuration procedure Deinstallation procedure (cont'd) description of, 8-2 sample script for NetWare guidelines for, 8-1 , C-4 responding to prompts, sample script for 8-3 PATHWORKS Advanced starting, 8-2 Server, B-4 Device name, 2-4 sample script for Disk space PATHWORKS Advanced determining, 1-11 Server and NetWare, Disk space requirements, D-5 1-11 sample script for E standalone license ___________________________ server, E-1, E-3 External network numbers starting, 3-9 configuration and, 4-3 starting server during, External network types 3-8, 3-13, 4-11, 5-6, configuration and, 4-4 5-11 F storage of old values in, ___________________________ 4-13 Files created by installation, D__________________________ G-1 Data loss File server preventing, 1-10 configuring, 4-1 DECnet (Phase IV) reconfiguring, 4-12 checking status, 1-16 starting, 6-4 DECnet-Plus stopping, 6-8 checking status, 1-17 G DECnet transport, 1-7 ___________________________ running during GBLPAGES parameter configuration, 1-16 checking and defining, status of, 1-16 1-12 DECprint Supervisor software, 1-2 H__________________________ installing, 1-2 Hardware requirements, Default answers 1-7, 1-10 for configuration Help procedure, 4-6 for configuration for installation procedure, 4-6 procedure, 2-8 Default settings changing, 3-13 Index-2 IPX DECnet tunnels I__________________________ term defined, 4-4 Installation IVP files created by, G-1 restriction when logical names created by, installing Upgrade H-1 utility only, F-1 Installation kit running after contents of, 2-2 installation, 6-2 Installation procedure running automatically, description of, 2-1 2-14 interrupting, 2-8 logical names and, I-1 K__________________________ prerequisites, 2-4 Kit contents questions in, 2-8 checking, 1-9 responding to prompts, 2-8 L sample script for NetWare ___________________________ , C-1 LAN sample script for number of networks on a PATHWORKS Advanced server, 4-4 Server, B-1 License server sample script for installation procedure, PATHWORKS Advanced 5-1 Server and NetWare, term defined, 3-5 D-1 Licensing, 1-3 sample script for LMHOSTS standalone license configuring to use, 7-5 server, E-1 Local networks sample script for Upgrade configuration and, 4-4 Logical names utility, F-2 common, I-2 standalone license server created by installation, , 5-1 H-1 starting, 2-6 creation of, I-1 Installation Verification private, I-3 Procedure redefined, 4-13 See IVP startup procedure, 6-4 Internal network numbers types of, I-1 configuration and, 4-3 IP subnets BDC and PDC on different subnets, 3-4 Index-3 OpenVMS cluster (cont'd) M__________________________ shutting down servers on, Memory requirements, 1-8 4-6 starting server in, 5-13, N__________________________ 6-7 NetBIOS name resolution Operating system using LMHOSTS for, 3-4, requirements, 1-7 7-1 Optional software, 2-19 using WINS server for, P 3-4, 7-4 ___________________________ Netlogon service, 3-6 Part listing NetWare deinstallation checking, 1-9 procedure PATHWORKS cluster alias sample, 8-5 term defined, 3-7 Network numbers Postinstallation tasks, configuration and, 4-3 6-1 Network transport configuration, 4-2 requirements, 1-7 Preinstallation tasks, 1-9, 2-4 O__________________________ checklist for, 1-8 OpenVMS cluster Private logical names checking configuration, description of, I-3 1-9 PROCSECTCNT parameter cluster alias, 3-16 checking and defining, configuring nodes in, 1-13 3-2, 4-2, 4-5 Product identifier, 2-4 disk device for PATHWORKS PWRK$CONFIG procedure files, 3-3 See Configuration installation in, 1-18, procedure 3-8 PWRK$DEINSTAL procedure loading client license See Deinstallation PAKs on, 5-1 procedure loading PAKs on, 1-4 PWVN$COMMON_LOGICALS.COM PATHWORKS cluster alias procedure for, 3-7 logical names created by, running license server I-2 on, 1-4, 5-1 PWVN$CONFIG.COM procedure sample configuration on, description of, 4-2 E-3 logical names and, I-1 sample installation on, E-1 server role in, 3-6 Index-4 PWVN$PRIVATE_LOGICALS.COM Server startup, 6-5 procedure SHOW QUEUE/MANAGER command, logical names created by, 1-15 I-3 Shutdown procedure PWVN$STARTUP.COM for file server, 6-9 description of, 6-4 Software requirements, PWVN$STARTUP.COM procedure 1-7, 1-10 logical names and, I-1 Standalone license server, 1-4, 5-1 Q__________________________ Standalone license server Queue manager configuration procedure running during sample, E-1 configuration, 1-15 Standalone license server starting, 1-15 startup, 5-11 Starting up the standalone R__________________________ license server, 5-11 Release notes, 1-11, 2-5, START/QUEUE/MANAGER command 2-9 , 1-15 in SYS$HELP: area, 1-5 STARTUP printing, 1-4 in SYSMAN utility, 6-8 Required hardware, 1-7 Startup procedure Required software, 1-7 for file server, 6-4 Requirements SYLOGIN.COM disk space, 1-11 conditionalizing, 6-5 hardware, 1-7, 1-10 SYSMAN utility memory, 1-8 using STARTUP, 6-8 software, 1-7, 1-10 SYSTEM account logging in to, 1-10 System backup, 1-10 S__________________________ System disk SCSNODE parameter input/output on, 3-3 defining, 1-14 space needed for Server installation, 1-11 starting during System parameters configuration, 3-8, checking and defining, 3-13, 4-11, 5-6, 5-11 1-12 Server administration tools System shutdown installing, 2-19 file server shutdown and, Server announce comment 6-9 term defined, 3-7 System startup Server commands defining server commands defining at system at, 6-6 startup, 6-6 troubleshooting, 6-5 Index-5 System startup file editing, 5-12, 6-7 V__________________________ VMSINSTAL T__________________________ description of, 2-1 Task summary, A-1 kit contents, 2-2 TCP/IP, 1-7 VMSINSTAL procedure status of, 1-18 See Installation Timesource service procedure description of, 3-5 Time zone W checking setting, 1-16 ___________________________ Transports, 3-4 Wide area domain, 7-1 selecting duringconfigu- Windows NT server ration, 3-4 administration tools, Tunnel networks 2-19 configuration and, 4-4 installing, 2-19 WINS U__________________________ configuring to use, 7-5 Upgrade utility, F-1 Index-6