_____________________________________________________ ALL-IN-1 PC Server for VMS Installation Guide AA-PAG7A-TE This guide describes how to install the ALL-IN-1 PC Server for VMS. Revision/Update Information: This is a new manual. Operating System Version: VMS Version 5.0-2 or higher Software Version: ALL-IN-1 PC Server for VMS - Version 1.0 digital equipment corporation maynard, massachusetts _____________________________________________________ May 1990 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1990. All rights reserved. Printed in U.S.A. The postpaid READER'S COMMENTS form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, DECnet, DECserver, FMS, PCSA, Scholar, VAX, VAXcluster, VMS, VT, and the DIGITAL Logo. 8086 is a trademark of Intel Corporation. 8088 is a registered trademark of Intel Corporation. Hayes is a registered trademark of Hayes Microcomputer Products, Inc. IBM is a registered trademark of International Business Machines Corporation. KEYpak is a trademark of Keyword Office Technologies, Ltd. WordPerfect is a trademark of WordPerfect Corporation. WordStar is a registered trademark of MicroPro International Corporation. This document was prepared using VAX DOCUMENT, Version 1.2. ________________________________________________________________ Contents Preface.................................................. v 1 Preparing to Install the ALL-IN-1 PC Server for VMS 1.1 Required Operating System Components............ 1-2 1.2 Prerequisite Software........................... 1-2 1.3 ALL-IN-1 Considerations......................... 1-2 1.4 VAXcluster Considerations....................... 1-2 1.4.1 Homogeneous VAXclusters ...................... 1-2 1.4.2 Heterogeneous VAXclusters .................... 1-3 1.4.3 Heterogeneous VAXcluster Parameters .......... 1-3 1.5 License Management Facility..................... 1-4 1.6 Installation Procedure Requirements............. 1-4 1.6.1 Time ......................................... 1-4 1.6.2 Privileges ................................... 1-4 1.6.3 Disk Space ................................... 1-5 1.6.4 System Parameters ............................ 1-5 1.6.4.1 Calculating the Values for GBLPAGES and GBLSECTIONS................................ 1-6 1.6.4.2 Changing System Parameter Values with AUTOGEN.................................... 1-6 iii 1.6.5 Process Account Quotas ....................... 1-7 1.6.6 VMSINSTAL Requirements ....................... 1-9 1.6.7 Backing Up Your System Disk .................. 1-9 2 Installing the ALL-IN-1 PC Server for VMS 2.1 General Information............................. 2-1 2.1.1 Accessing the Online Release Notes ........... 2-1 2.1.2 Determining the Files and Logical Names Added to the System................................ 2-1 2.1.3 Running the Installation Verification Procedure (IVP).............................. 2-2 2.1.4 Canceling the Installation ................... 2-2 2.2 The Installation Procedure...................... 2-3 2.2.1 Invoking VMSINSTAL ........................... 2-3 2.2.2 Installation Questions ....................... 2-4 2.2.3 Informational Messages ....................... 2-12 2.2.4 Running the Installation Verification Procedure.................................... 2-13 2.2.5 Completing the Installation Procedure ........ 2-13 2.3 Error Recovery.................................. 2-13 2.4 After Installing the VMS Server................. 2-14 2.4.1 Editing the System Files ..................... 2-14 2.4.2 Setting Up User Accounts ..................... 2-15 2.5 Determining and Reporting Problems.............. 2-15 A Sample Installation A.1 Installation Log................................ A-1 iv Tables 1-1 Disk Space Requirements......................... 1-5 1-2 Required System Parameter Values................ 1-5 1-3 Process Account Quotas for the Installing Account......................................... 1-7 v ________________________________________________________________ Preface Manual Objective The objective of this manual is to describe the procedure you must follow to install the ALL-IN-1 PC Server for VMS on a VAX host computer. Intended Audience This guide is intended for use by VAX system managers. Knowledge of the ALL-IN-1 installation procedure will be useful. Document Structure Chapter 1, Preparing to Install the ALL-IN-1 PC Server for VMS, provides information you need to know before performing the installation. Chapter 2, Installing the ALL-IN-1 PC Server for VMS, describes the procedure you will follow during the installa- tion. v Appendix A, Sample Installation, provides a sample output file created by an ALL-IN-1 PC Server for VMS installation. Related Documentation ALL-IN-1 DESKtop for PCs Management Guide ALL-IN-1 DESKtop for PCs Programmer's Reference Manual ALL-IN-1 Installation Guide VMS System Messages and Recovery Procedures Reference Manual Part I VMS System Messages and Recovery Procedures Reference Manual Part II VMS System Management Subkit Documentation Conventions _____________________________________________________________ Convention_______Meaning_____________________________________ VMS Server Throughout this manual the ALL-IN-1 PC Server for VMS is referred to as VMS Server. ALL-IN-1 Throughout this manual the ALL-IN-1 DESKtop DESKtop for PCs system is referred to as ALL-IN-1 DESKtop. CTRL/x Hold down the CTRL key while you press the _________________designated_letter_key.______________________ vi 1 ________________________________________________________________ Preparing to Install the ALL-IN-1 PC Server for VMS This chapter discusses the preparations and requirements necessary for installing the ALL-IN-1 PC Server for VMS (VMS Server). This manual applies to Version 1.0 of the VMS Server. The VMS Server is designed for use on VAX computers currently running ALL-IN-1 Version 2.3 or higher. Your bill of materials (BOM) specifies the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. VMS Server provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the online release notes, see Section 2.1.1. Preparing to Install the ALL-IN-1 PC Server for VMS 1-1 1.1 Required Operating System Components The VMS operating system comes with a variety of support options, or classes. Classes include such features as networking and RMS journaling. The VMS Server requires a full VMS operating system. For a complete list of the required classes, see the Software Support Addendum (SSA), which comes with the Software Product Description (SPD) for the VMS Server. 1.2 Prerequisite Software The following software products must be installed on your system before you install the VMS Server: _ VMS Version 5.0-2 or higher _ ALL-IN-1 Version 2.3 or higher 1.3 ALL-IN-1 Considerations During an installation of the VMS Server, neither shutting down ALL-IN-1 nor canceling all use of ALL-IN-1 is mandatory, although these steps are recommended. If ALL-IN-1 is active during the installation and ALL-IN-1 users are using their accounts, the libraries that require updating are copied to new versions. This results in increased overhead disk space, and it increases the installation time. 1.4 VAXcluster Considerations The VMS Server can run on homogeneous VAXclusters or on heterogeneous VAXclusters. For the purposes of the VMS Server, a homogeneous VAXcluster uses only one user authorization file (UAF), and a heterogeneous VAXcluster uses more than one UAF. Before you install the VMS Server, there are different considerations for homogeneous and heterogeneous VAXclusters that you must address. 1.4.1 Homogeneous VAXclusters When you install the VMS Server on a homogeneous VAXcluster, you only install it on one node. Make sure the disk where the VMS Server is installed is available to all nodes on the cluster. Also, make sure that the VMS Server startup command procedure, SYS$STARTUP:A1SVC$STARTUP.COM, is included in the startup procedure on each node in the cluster. 1-2 Preparing to Install the ALL-IN-1 PC Server for VMS 1.4.2 Heterogeneous VAXclusters When you install the VMS Server on a heterogeneous VAXcluster, you need to install it on each portion of the VAXcluster that contains a unique UAF. Make sure that the disk where the VMS Server is installed is available to all nodes on that section of the cluster. Also, make sure that the VMS Server startup command procedure, SYS$STARTUP:A1SVC$STARTUP.COM, is included in the system startup procedure of all of these nodes. When the VMS Server is installed on a heterogeneous VAXcluster, users only have access to the services provided by the VMS Server installed in their part of the VAXcluster. Users logged in to a node on a part of the VAXcluster that does not contain the VMS Server cannot use the services of the VMS Server. As a result, users (running interactively or running batch jobs) of a VMS Server must ensure that they access or run on that area of the VAXcluster that contains the VMS Server in which they are registered. 1.4.3 Heterogeneous VAXcluster Parameters The VMS Server uses several parameters to maintain the dis- tinct parts of a heterogeneous VAXcluster. These parameters must be set to values which reflect the distinctions between the different parts of the VAXcluster. The parameter values are contained in the file A1SVC$SITE:A1SVC$SITE_DEFNS.COM. During the installation procedure you will be prompted to supply the values for the following parameters: _ Queue Characteristics-Jobs submitted to the generic batch queue are sent to queues that are started by a specific queue characteristic. The queue characteristic must be different for each part of the heterogeneous VAXcluster to ensure that batch jobs are submitted to the correct nodes. _ Synchronization Lock Resource Name-Synchronization between the cluster members is determined by VMS locks. The resource identification must be different for each part of the heterogeneous VAXcluster. _ Communication Lock Resource Name-Communication to the Master Scheduler is based upon VMS locks. The resource identification must be different for each part of the heterogeneous VAXcluster. Preparing to Install the ALL-IN-1 PC Server for VMS 1-3 _ DECnet Object Name- Scheduler communication between the nodes is accomplished through DECnet. The Master Scheduler declares itself as a DECnet object. The DECnet object name must be different for each part of the heterogeneous VAXcluster. 1.5 License Management Facility License Management Facility (LMF) registration is not required with this product. Rights to use the VMS Server are included with the license for ALL-IN-1. 1.6 Installation Procedure Requirements The following sections discuss the requirements for installing the VMS Server. 1.6.1 Time The total installation takes approximately 10 to 25 minutes, depending on your type of media and system configuration, and whether or not you run the Installation Verification Procedure (IVP). Installing the VMS Server and running the IVP takes approximately 25 minutes on a standalone MicroVAX 3600 system and approximately 11 minutes on a VAX 8800. 1.6.2 Privileges To install the VMS Server, you must be logged in to an account that has SETPRV or at least the following privileges: _ CMKRNL _ WORLD _ SYSPRV Note that VMSINSTAL turns off the BYPASS privilege at the start of the installation. Use the following command to check the privileges for your current account: $ SHOW PROCESS/PRIVILEGE 1-4 Preparing to Install the ALL-IN-1 PC Server for VMS 1.6.3 Disk Space Table 1-1 lists the approximate disk space required to install the VMS Server. Table 1-1 Disk Space Requirements _____________________________________________________________ Blocks During Blocks After Kit______________Installation__________Installation__________ ALL-IN-1 PC 6000 3000 plus additional Server for VMS blocks due to SITE Version_1.0____________________________OAFORM_Library_changes To determine the number of free disk blocks on the target disk, enter the following command at the DCL prompt: $ SHOW DEVICE target_device 1.6.4 System Parameters Installing the VMS Server requires certain system parameter settings. Table 1-2 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. Table 1-2 Required System Parameter Values _____________________________________________________________ System_Parameter___________Value_____________________________ GBLPAGES[1] n + 750 GBLSECTIONS[1] n + 22 _____________________________________________________________ [1]The value n represents the number of free global pages and global sections you need to run your system and other software. The numeric values listed for these system parameters represent the additional number of free global pages and global sections required for the installation. _____________________________________________________________ The following sections show you how to: _ Calculate values for the GBLPAGES and GBLSECTIONS system parameters Preparing to Install the ALL-IN-1 PC Server for VMS 1-5 _ Change parameter values with the AUTOGEN command procedure 1.6.4.1 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run the VMS Server, you must have sufficient free global pages and global sections. You must first find out how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the GLBPAGES and GBLSECTIONS system parameters. Use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the total value for each parameter in Table 1-2, you do not need to increase the values for these parameters. If the value of free global pages or global sections is less than the value in Table 1-2, you must increase the system parameter setting. Section 1.6.4.2 describes the procedures for increasing these values using AUTOGEN. Refer to the VMS System Management Subkit for information on using AUTOGEN. 1.6.4.2 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, use an editor to access the following file: SYS$SYSTEM:MODPARAMS.DAT To change a parameter value that is already listed in this file, delete the current value associated with that parameter and enter the new value. To add a new parameter, add a line to the file that includes the name of the parameter and its value. For example: GBLSECTIONS=400 1-6 Preparing to Install the ALL-IN-1 PC Server for VMS To modify incremental parameters such as GBLPAGES and GBLSECTIONS, use ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 After you have made all your changes, exit from the editor and run the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged in to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN command procedure automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the VMS System Management Subkit. 1.6.5 Process Account Quotas The user account you use to install the VMS Server must have sufficient process quotas to enable you to perform the installation. Table 1-3 summarizes the minimum process quotas required for the installation. Table 1-3 Process Account Quotas for the Installing Account _____________________________________________________________ Account_Quota____Minimum_Value_______________________________ ASTLM 24 BIOLM 18 BYTLM 18,000 (continued on next page) Preparing to Install the ALL-IN-1 PC Server for VMS 1-7 Table 1-3 (Cont.) Process Account Quotas for the Installing Account _____________________________________________________________ Account_Quota____Minimum_Value_______________________________ DIOLM 18 ENQLM 30 FILLM____________20__________________________________________ Process quotas for users, including those for the installing account, are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE by entering the following commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the UAF> prompt, use the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, use the MODIFY command. MODIFY has the following format: MODIFY account-name /quota-name=NNN The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of AUTHORIZE in the VMS System Management Subkit. 1-8 Preparing to Install the ALL-IN-1 PC Server for VMS 1.6.6 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: _ Whether you have set your default device and directory to SYS$UPDATE _ Whether you are logged in to a privileged account _ Whether you have adequate quotas for installation _ Whether DECnet is running (VMS Versions 5.0-2 or 5.1 only, not VMS Version 5.2 or higher) _ Whether any users are logged in to the system If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press RETURN. Correct the problem and restart the installation. 1.6.7 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the VMS System Management Subkit. Preparing to Install the ALL-IN-1 PC Server for VMS 1-9 2 ________________________________________________________________ Installing the ALL-IN-1 PC Server for VMS This chapter describes how to install the ALL-IN-1 PC Server for VMS (VMS Server). Section 2.2 contains a step-by-step description of the installation procedure. Section 2.4 covers postinstallation considerations. 2.1 General Information This section includes general information which is useful to know before starting the installation procedure. 2.1.1 Accessing the Online Release Notes The VMS Server provides online release notes. You should review the release notes in case they contain any information about last-minute changes in the installation procedure. You must specify OPTIONS N when you invoke VMSINSTAL to see the question about online release notes. This question comes near the beginning of the installation. You can view the release notes before you proceed with a complete installation. See Section 2.2.1 and Section 2.2.2 for more details about OPTIONS N and release notes. 2.1.2 Determining the Files and Logical Names Added to the System During the installation, the VMS Server creates some directories and files on your system. To see the complete list of files, look in the following directories: _ disk:[A1SVC.LIB] _ disk:[A1SVC.SITE] _ disk:[A1SVC.DATA] Installing the ALL-IN-1 PC Server for VMS 2-1 _ disk:[A1SVC.LOG] _ disk:[A1SVC.SCRATCH] (disk: is your installation target disk.) The installation procedure creates the following logical names on your system by using the DEFINE command in the following manner: _ $ DEFINE/SYSTEM/EXEC A1SVC$SITE disk:[A1SVC.SITE] _ $ DEFINE/SYSTEM/EXEC A1SVC$ORIG disk:[A1SVC.LIB] _ $ DEFINE/SYSTEM/EXEC A1SVC$LIB A1SVC$SITE,A1SVC$ORIG _ $ DEFINE/SYSTEM/EXEC A1SVC$DATA disk:[A1SVC.DATA] _ $ DEFINE/SYSTEM/EXEC A1SVC$LOG disk:[A1SVC.LOG] _ $ DEFINE/SYSTEM/EXEC A1SVC$TMP disk:[A1SVC.SCRATCH] (A1SVC$LIB is a logical search list.) 2.1.3 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for the VMS Server verifies the installation. During the installation, you are asked if you want to run the IVP as part of the installation. If you respond YES, VMSINSTAL runs the IVP. It is recommended that you run the IVP to make sure that the VMS Server is installed correctly. After the VMS Server is installed, you can run the IVP independently to verify that the software is available on your system. You might need to run the IVP after a system failure to make sure that users can access the VMS Server. To run the IVP independently after the VMS Server is installed, enter the following command: $ @SYS$TEST:A1SVC$IVP 2.1.4 Canceling the Installation To cancel the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. 2-2 Installing the ALL-IN-1 PC Server for VMS 2.2 The Installation Procedure The VMS Server installation procedure consists of a series of questions and informational messages. 2.2.1 Invoking VMSINSTAL To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. Use the following syntax to invoke VMSINSTAL: $ @SYS$UPDATE:VMSINSTAL saveset-name device-name: OPTIONS N It is not necessary to include saveset-name, device-name, or OPTIONS N in the command. If you do not include this information, you are prompted for it during the installation procedure. An explanation of saveset-name, device-name, and OPTIONS N follows: saveset-name Saveset-name is the installation name for the component. For the VMS Server, use the following installation name: A1SVC010 The last three characters represent the version number and point release of the current VMS Server. These three characters are optional. You may also use the following installation name: A1SVC device-name Device-name is the name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete. OPTIONS N OPTIONS N is an optional parameter that indicates you want to see the release notes question. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. Review the release notes before proceeding with the installation in case they contain new information about the installation. Installing the ALL-IN-1 PC Server for VMS 2-3 If you are starting the installation over again and have already reviewed the release notes, you do not need to specify OPTIONS N. Once the VMS Server has been installed, the release notes are located in the following file: SYS$HELP:A1SVC$010.RELEASE_NOTES There are several other options you can select when you invoke VMSINSTAL. See the VMS documentation on software installation in the VMS System Management Subkit for information on these options. If you specify more than one option, separate the options with commas, for example, OPTIONS A,N. The following example invokes VMSINSTAL to install the VMS Server (installation name is A1SVC010) from tape drive MTA0: and shows the system response. This example includes the OPTIONS N release notes parameter. $ @SYS$UPDATE:VMSINSTAL A1SVC010 MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.1 It is 23-FEB-1990 at 11:14. Enter a question mark (?) at any time for help. 2.2.2 Installation Questions This section discusses questions that appear during an installation. The selection of questions you see during an installation on your system will vary depending on your system configuration and how you answer certain questions. Appendix A contains a sample installation procedure which includes examples of how the questions can be answered. Questions that are not included in the sample can be found in this section. Each question in the installation is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example [YES]. To use the default response, press the RETURN key. 1 DECnet status 2-4 Installing the ALL-IN-1 PC Server for VMS If you are installing the VMS Server on a VAX system run- ning either VMS Versions 5.0-2 or 5.1, it is recommended that DECnet be shut down, but it is not required. Once you have initiated the installation procedure, VMSINSTAL notifies you if DECnet is running and displays a list of all active processes. VMSINSTAL then asks if you want to continue the installation. NO is the default response to the question. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? If you are installing on VMS Version 5.2 or higher, VMSINSTAL does not check the DECnet status. You can install the VMS Server while DECnet is up and running. 2 System backup VMSINSTAL asks if you are satisfied with your system backup. It is recommended that you always back up your system disk before performing an installation. YES is the default response to the question. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? 3 Device name VMSINSTAL asks you where the distribution volume will be mounted. See Section 2.2.1 for more information about the device name. * Where will the distribution volumes be mounted: MTA1 4 Saveset name VMSINSTAL asks which products are to be processed from the distribution volume set. You will see a prompt for names of products. See Section 2.2.1 for more details about the saveset name. Enter A1SVC010 or A1SVC as the installation name for the VMS Server, Version 1.0. Enter the products to be processed from the first distribution volume set. * Products: A1SVC010 Installing the ALL-IN-1 PC Server for VMS 2-5 5 Options VMSINSTAL prompts you for options you want to invoke. See Section 2.2.1 for more details about options, specifically OPTIONS N, to see a release notes question during installation. Press RETURN if you do not want to specify any options. * Options: N You are now instructed to mount the first volume of the distribution set on the device you specified. You are asked if you are ready. If you respond YES, VMSINSTAL displays a message that the media containing the VMS Server has been mounted on the specified device and that the installation has begun. For example: Please mount the first volume of the set on MTA1:. * Are you ready? YES %MOUNT-I-MOUNTED, A1SVC mounted on _MTA1: The following products will be processed: A1SVC V1.0 Beginning installation of A1SVC V1.0 at 11:16 %VMSINSTAL-I-RESTORE, Restoring product saveset A... If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To cancel the installation for other reasons, press CTRL/Y. 6 Release Notes If you specified OPTIONS N when you started the installa- tion, VMSINSTAL displays release notes options. There are five options for release notes under VMS Versions 5.0-2 and 5.1. There are four options under VMS Version 5.2 or higher. For VMS Versions 5.0-2 and 5.1, you see the following display: 2-6 Installing the ALL-IN-1 PC Server for VMS Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [2]: For VMS Version 5.2 or higher the display is as follows: Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: Press RETURN to send the file to the default output print device or enter another queue name. If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. VMSINSTAL automatically selects option 4 under VMS Versions 5.0-2 and 5.1 to copy the release notes for the VMS Server to the SYS$HELP directory. Under VMS Version 5.2 or higher, release notes will continue to be automatically copied to SYS$HELP. Select option 5 (VMS Version 5.0-2 or 5.1) or option 4 (VMS Version 5.2 or higher) if you have already reviewed the release notes and are restarting the installation. Installing the ALL-IN-1 PC Server for VMS 2-7 VMSINSTAL lets you know the release notes have been moved to SYS$HELP by displaying the following message: %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. The release notes are located in the following file: SYS$HELP:A1SVC$010.RELEASE_NOTES The name of the release notes file installed by VMSINSTAL consists of the product name and version number. 7 Choosing to run the Installation Verification Procedure (IVP) The installation procedure now asks if you want to run the Installation Verification Procedure. The IVP for the VMS Server verifies the completeness and accuracy of the installation. It is recommended that you run the IVP. * Do you want to run the IVP after the installation [YES]? 8 Choosing to purge files You have the option to purge files from previous versions of the VMS Server that are superseded by this installation. Purging is recommended. If you need to keep files from the previous version, enter NO in response to the question. * Do you want to purge files replaced by this installation [YES]? Note Site modifications that have been stored in the A1SVC$SITE area are not purged. 9 Installing on what device VMSINSTAL asks on what device you want to install the VMS Server. %A1SVC-I-STARTER, this is an ALL-IN-1 Starter system * Install ALL-IN-1 PC Server for VMS on what device [SYS$SYSDEVICE:]: %A1SVC-I-NEWINSTALL, This is a new installation of ALL-IN-1 PC Server for VMS 10 VMS Server has been previously installed If the VMS Server has been previously installed on your system, you are notified with a message and asked if you want to continue with the installation. You are also asked 2-8 Installing the ALL-IN-1 PC Server for VMS if you want to preserve existing data. You may want to preserve site-specific information (such as user profiles) that already exists. If you do not preserve existing data, the remainder of the installation is treated as a new installation. For example, an empty user profile will be provided. %A1SVC-W-REINSTALL, VMS Server has been previously installed * Do you want to continue with this installation [NO]? YES * Do you want to preserve existing data [YES]? 11 Entering language code The VMS Server updates ALL-IN-1 form libraries with new forms. These forms are added to the language dependent areas of ALL-IN-1. You may update as many languages as needed at the prompt. The languages you specify must have already been created via ALL-IN-1. Some of the possibilities are: _ Danish _ Dutch _ English _ Finnish _ French _ German _ Hebrew _ Italian _ Japanese _ Norwegian _ Spanish _ Swedish Press RETURN at the prompt when you are finished entering languages. * Enter language code 1 [ENGLISH]: * Enter language code 2: %A1SVC-I-NUMLANG, installation of 1 language(s) has been requested Installing the ALL-IN-1 PC Server for VMS 2-9 12 Clustered environment You can run the VMS Server in homogeneous or heterogeneous VAXclusters. See Section 1.4 for more detail about these environments. * Will this be a clustered environment [NO]? YES * Is this a homogeneous or heterogeneous environment [HOMOGENEOUS]: 13 Define site-specific parameters The VMS Server has operating parameters that may be tailored for each site. You may install the VMS Server and use the defaults that are provided or define the parameters now. See the ALL-IN-1 DESKtop for PCs Management Guide for more information about parameters. * Do you want to define site specific parameters now [NO]? 14 VMS account for Scheduler The Scheduler uses a privileged VMS account as a processing account. * What privileged VMS account will the scheduler use? [SYSTEM] 15 Heterogeneous VAXcluster If you specified that you are installing the VMS Server on a heterogeneous VAXcluster, you will be prompted to supply values for parameters that maintain the distinct parts of the cluster. See the explanation of heterogeneous VAXcluster parameters in Section 1.4 for information about how to respond to the following installation questions: * What queue characteristic name should be used [A1SVC$QUEUE_node]:? During an installation, the word node shown here in the default choice is replaced by the name of the actual node where the VMS Server is being installed. The maximum length of the queue characteristic is 31 characters. * What DECnet object name should be used [A1SVC$nnnn]:? During an installation, the n shown here in the default choice represents a unique four-digit hexadecimal number. The maximum length of the DECnet object name is 10 characters. The default provided is sufficient for most installations. 2-10 Installing the ALL-IN-1 PC Server for VMS * What resource should be used for synchronization [A1SVC$SCHED_node]:? During an installation, the word node shown here in the default choice is replaced by the name of the actual node where the VMS Server is being installed. The maximum length of a resource name is 31 characters. The default provided is sufficient for most installations. * What resource should be used for communication [A1SVC$COMM_node]:? During an installation, the word node shown here in the default choice is replaced by the name of the actual node where the VMS Server is being installed. The maximum length of a resource name is 31 characters. The default provided is sufficient for most installations. 16 Scheduler errors Errors that are encountered by the Scheduler are sent by the VMS Server to the PC user designated by the VMS account experiencing the error. If the user has not been added to the user profile database through the Manager's Menu, the errors appear in the log files created by the Scheduler. * To what VMS account should scheduler errors be sent:? 17 Scheduler's interval The Scheduler runs periodically to watch for mail on behalf of the registered ALL-IN-1 DESKtop for PCs (ALL- IN-1 DESKtop) users. You may specify the interval between Scheduler runs as well as the time of day it will begin and the time of day it will end. * What is the Scheduler's interval? (HH:MM) [00:10]:? 00:12 * What time of day should the Scheduler start? (HH:MM) [06:00]:? 6:30 * What time of day should the Scheduler stop? (HH:MM) [19:00]:? 19:30 18 Default mail system and mail system list If a user is registered for the VMS Server but is not given a mail system, a default mail system list is needed for the Scheduler to process that user. If mail is sent or received and a mail system is not specified, a default mail system is required by the VMS Server to process the mail message. ALL-IN-1 serves as the default mail system list for users and as the default mail system for messages. The following messages are displayed to verify this: Installing the ALL-IN-1 PC Server for VMS 2-11 %A1SVC-I-DEFAULTED, using ALL-IN-1 as the default mail system list for users %A1SVC-I-DEFAULTED, using ALL-IN-1 as the default mail system for messages 19 Keeping Scheduler and user log files Since the VMS Server is driven by batch processes, the log files produced by the Scheduler and the user jobs may be preserved. It is recommended that log files be kept until the installation has been running successfully for some period of time. Log files are a means of tracking down system problems if necessary. The log files may be disabled by editing the site definitions file through the Manager's Menu. * Do you want to keep log files from the Scheduler [NO]? YES * Do you want to keep log files from user jobs [NO]? YES 2.2.3 Informational Messages At this point, you have answered all questions, and the installation procedure displays some instructions to be carried out after the installation has successfully completed. The following prompt and message are displayed: * Press RETURN to continue...: All questions regarding the installation have been asked. No further action is required. The remainder of this installation should take about: 20 minutes without IVP 25 minutes with IVP As the remainder of the installation completes, you will see a number of informational messages that report on the progress of the installation. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. 2-12 Installing the ALL-IN-1 PC Server for VMS 2.2.4 Running the Installation Verification Procedure If you chose to run the IVP, VMSINSTAL runs it after the installation is in place. When the IVP runs successfully, you see the following display: %A1SVC-I-IVPPHASE1, Installation Verification Procedure phase 1 %A1SVC-I-IVPDONE, Installation Verification Procedure complete If an error occurs during the installation, the same completion message is displayed along with an error message. 2.2.5 Completing the Installation Procedure The following messages indicate that the entire installation procedure is complete: Installation of A1SVC V1.0 completed at 11:41 VMSINSTAL procedure done at 11:41 You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 23-FEB-1990 11:50:22.16 Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. 2.3 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of A1SVC V1.0 has failed. If the IVP fails, you see these messages: The A1SVC V1.0 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for A1SVC V1.0 has failed. Installing the ALL-IN-1 PC Server for VMS 2-13 Errors can occur during the installation if any of the following conditions exist: _ The operating system version is incorrect. _ Quotas necessary for successful installation are insufficient. _ System parameter values for successful installation are insufficient. _ ALL-IN-1 Version 2.3 or higher has not been installed. For descriptions of the error messages generated by these conditions, see the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, take the appropriate action as described in the message. For example, you might need to change a system parameter or increase an authorized quota value. For information on installation requirements, see Chapter 1. 2.4 After Installing the VMS Server After installing the VMS Server, edit the system startup file and the syslogin file. 2.4.1 Editing the System Files Add the command line that starts the VMS Server to the system startup file. This provides for automatic startup of the VMS Server when the system is rebooted. The VMS Server startup command is: @SYS$STARTUP:A1SVC$STARTUP The VMS Server must be started after the network has started. Position the VMS Server startup command in the system startup file after the command that starts the network. To set up the required symbols for the VMS Server environ- ment, edit the system login file or the login of each user who be using ALL-IN-1 DESKtop to include the following line: @A1SVC$LIB:A1SVC$SYMBOLS Starting ALL-IN-1 and the Message Router before starting the VMS Server is not mandatory, although this is recommended. ALL-IN-1 and the Message Router must be running for the VMS Server Scheduler to deliver mail messages. 2-14 Installing the ALL-IN-1 PC Server for VMS 2.4.2 Setting Up User Accounts Specific instructions for setting up user accounts are included in the ALL-IN-1 DESKtop for PCs Management Guide. Each ALL-IN-1 DESKtop user must have standard personal ALL- IN-1 and VMS accounts. ALL-IN-1 DESKtop does not support multiple ALL-IN-1 accounts sharing one VMS account. 2.5 Determining and Reporting Problems If you encounter a problem while using the VMS Server, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: _ Call the Digital Customer Support Center if your service contract or warranty agreement entitles you to telephone support. _ Submit a Software Performance Report (SPR). _ Fill out and submit a Reader's Comments form if the problem has to do with the VMS Server documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. Include the section and page number. Review the Software Product Description (SPD) and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. Installing the ALL-IN-1 PC Server for VMS 2-15 A ________________________________________________________________ Sample Installation This appendix contains a sample installation of the ALL- IN-1 PC Server for VMS (VMS Server). This sample was run on a system that had no previous version of the VMS Server installed. Depending on the configuration of your system, you might see additional messages and questions when you perform your installation. Section 2.2 includes an explanation of how to start the installation and explanations of the questions you might see. A.1 Installation Log This section contains a sample installation for the VMS Server. Welcome to VAX/VMS V5.1 Username: SYSTEM Password: Welcome to VAX/VMS version V5.1 on node NAME1 Last interactive login on Tuesday, 23-FEB-1990 11:05 Last non-interactive login on Monday, 22-FEB-1990 10:39 The ClusterX Cluster now consists of the following systems: SYSTEMX (6000-420) 96 mg. NAME1 (8800) 104 mg. NODEX (11/785) 16 mg. $ @SYS$UPDATE:VMSINSTAL VAX/VMS Software Product Installation Procedure V5.1 It is 23-FEB-1990 at 11:14. Enter a question mark (?) at any time for help. Sample Installation A-1 %VMSINSTAL-W-DECNET, Your DECnet network is up and running. %VMSINSTAL-W-ACTIVE, The following processes are still active: PROCESS1 PROCESS2 * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? yes * Where will the distribution volumes be mounted: mta1 Enter the products to be processed from the first distribution volume set. * Products: a1svc * Options: N Please mount the first volume of the set on MTA1:. * Are you ready? yes %MOUNT-I-MOUNTED, A1SVC mounted on _MTA1: The following products will be processed: A1SVC V1.0 Beginning installation of A1SVC V1.0 at 11:16 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [2]: 4 %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. * Do you want to run the IVP after the installation [YES]? yes * Do you want to purge files replaced by this installation [YES]? yes %A1SVC-I-STARTER, this is an ALL-IN-1 Starter system * Install ALL-IN-1 PC Server for VMS on what device [SYS$SYSDEVICE:]: %A1SVC-I-NEWINSTALL, This is a new installation of ALL-IN-1 PC Server for VMS ALL-IN-1 PC Server for VMS updates ALL-IN-1 form libraries with new forms. These forms are added to the language dependent areas of ALL-IN-1. You may update as many languages as needed. These languages must have already been created via ALL-IN-1. Simply press RETURN at the prompt when finished entering languages. A-2 Sample Installation * Enter language code 1 [ENGLISH]: * Enter language code 2: %A1SVC-I-NUMLANG, installation of 1 language(s) has been requested * Will this be a clustered environment [NO]? yes * Is this a homogeneous or heterogeneous environment [HOMOGENEOUS]: homogeneous The ALL-IN-1 PC Server for VMS has operating parameters that may be tailored for each site. You may install the product and use the defaults provided or define the parameters now. If you choose to define the parameters now, see the ALL-IN-1 PC Server for VMS Installation Guide and the ALL-IN-1 DESKtop for PCs Management Guide before continuing. * Do you want to define site specific parameters now? [NO]? yes * What privileged VMS account will the scheduler use? [SYSTEM]: system * To what VMS account should scheduler errors be sent: system * What is the scheduler's interval? (HH:MM) [00:10]: 00:12 * What time of day should the scheduler start? (HH:MM) [06:00]: 06:30 * What time of day should the scheduler stop? (HH:MM) [19:00]: 19:30 %A1SVC-I-DEFAULTED, using ALL-IN-1 as the default mail system list for users %A1SVC-I-DEFAULTED, using ALL-IN-1 as the default mail system list for messages * Do you want to keep log files from the scheduler [NO]? yes * Do you want to keep log files from user jobs [NO]? yes Upon completion of this procedure, several post installation steps must be taken. The steps are documented in the release notes included with this kit. Refer to the ALL-IN-1 PC Server for VMS Installation Guide and the ALL-IN-1 DESKtop for PCs Management Guide for further information on these topics. - Insert the ALL-IN-1 PC Server for VMS startup command into the system startup file. Add the following command to SYS$STARTUP:SYSTARTUP_V5.COM: $ @SYS$STARTUP:A1SVC$STARTUP - Insert the ALL-IN-1 PC Server for VMS symbol definition command into the system login procedure. (This will allow user processes to access the ALL-IN-1 PC Server for VMS.) Add the following command to SYS$MANAGER:SYLOGIN.COM: $ @A1SVC$LIB:A1SVC$SYMBOLS * Press RETURN to continue...: Sample Installation A-3 All questions regarding the installation have been asked. No further action is required. This remainder of this installation should take about: 20 minutes without IVP 25 minutes with IVP %A1SVC-I-HOLDON, installing ALL-IN-1 PC Server for VMS on SYS$SYSDEVICE: %A1SVC-I-UPDLANG, updating ALL-IN-1 libraries for language ENGLISH %OA-I-LASTLINE, precompiling the ALL-IN-1 form library OA$SITE_LIB_ENGLISH:SITEOAFORM %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1SVC]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1SVC.LIB]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1SVC.DATA]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1SVC.DATA.ENGLISH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1SVC.SCRATCH]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1SVC.LOG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[A1SVC.SITE]. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %A1SVC-I-IVPPHASE1, Installation Verification Procedure phase 1 %A1SVC-I-IVPDONE, Installation Verification Procedure complete Installation of A1SVC V1.0 completed at 11:25 VMSINSTAL procedure done at 11:25 A-4 Sample Installation