______________________________________________ ALL-IN-1 DESKtop Server for VMS Installation Guide Order Number: AA-PAG7B-TE January 1992 This document contains instructions for installing the ALL-IN-1 DESKtop Server for VMS. It also explains how to read the online release notes before or after installing the product. Revision/Update Information: This revised manual supersedes the ALL- IN-1 PC Server for VMS Installation Guide Version 1.0. Operating System Version: VMS Version 5.3 or higher. ALL-IN-1 Version 2.4 ALL-IN-1 Starter Version 2.4. Software Version: ALL-IN-1 DESKtop Server for VMS Version 1.1 ALL-IN-1 DESKtop for DOS Version 1.0 or higher. ALL-IN-1 DESKtop for Macintosh Version 1.0. Digital Equipment Corporation Maynard, Massachusetts ________________________ First Printing, May 1990 Revised, January 1992 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, 1992. All rights reserved. The postpaid READER'S COMMENTS forms on the last two pages of this document request the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, DECnet, FMS, MicroVAX, VAX, VAXcluster, VAX RMS, VMS, and the DIGITAL logo. KEYpak is a registered trademark of Keyword Office Technologies, Ltd. Macintosh is a registered trademark of Apple Computer, Inc. ZK5806 This document was prepared using VAX DOCUMENT, Version 1.2 ________________________________________________________________ Contents Preface.................................................. v 1 Preparing to Install the ALL-IN-1 DESKtop Server for VMS............................... 1 1.1 Prerequisite Hardware.................... 1 1.2 Prerequisite Software.................... 1 1.3 Prerequisite Operating System Components. 1 1.4 Backing Up Your System Disk.............. 2 1.5 Accessing the Online Release Notes....... 2 1.6 Time Required for Installation........... 2 1.7 Privileges Required for Installation..... 2 1.8 Disk Space Required for Installation..... 3 1.9 System Parameter Settings Required for Installation............................. 3 1.9.1 Calculating the Values for GBLPAGES and GBLSECTIONS............................ 4 1.9.2 Changing System Parameter Values with AUTOGEN................................ 5 1.10 Process Account Quotas................... 6 1.11 Special Requirements..................... 7 1.12 Setting up ALL-IN-1 DESKtop Server Accounts................................. 7 1.13 Multiple Message Servers................. 10 2 Installing the ALL-IN-1 DESKtop Server....... 11 2.1 Using VMSINSTAL.......................... 11 2.2 Installation Procedure................... 13 2.3 Canceling the Installation............... 22 2.4 Running the Installation Verification Procedure Separately..................... 22 2.5 Error Recovery........................... 23 3 After Installing the ALL-IN-1 DESKtop Server. 23 3.1 Files and Logical Names Added to the System During Installation............... 24 iii 3.2 Editing the System Files................. 25 3.3 Recompiling and Reinstalling the ALL-IN-1 Text Library (TXL)....................... 26 3.4 Maintaining Modified Files in the A1SVC$SITE Directory..................... 28 3.5 Starting the Scheduler................... 28 3.6 Setting Up User Accounts................. 29 3.7 Suppressing Mail Messages................ 29 3.8 Shutting Down the ALL-IN-1 DESKtop Server................................... 29 4 Determining and Reporting Problems........... 30 5 Sample Installations of the ALL-IN-1 DESKtop Server for VMS............................... 30 5.1 A Log of a First Time Server Installation............................. 30 5.2 A Log of a Server Upgrade Installation... 35 5.3 A Log of a Forms/Customization Management Update................................... 39 6 Space Required for ALL-IN-1 DESKtop Server Form Libraries............................... 42 7 Space Required for ALL-IN-1 DESKtop Server Customization Management Datasets............ 42 Tables 1 Disk Space Requirements.................. 3 2 Required System Parameter Values......... 4 3 Process Account Quotas for the Installing Account.................................. 6 4 ALL-IN-1 DESKtop Server Account Quotas... 8 iv ________________________________________________________________ Preface This document describes how to install the ALL-IN-1[TM] DESKtop Server for VMS[TM] on the VMS operating system. It is intended for system managers. This document applies to the ALL-IN-1 DESKtop Server for VMS Version 1.1 and all maintenance updates in that version. A major version number is represented by the digits to the left of the decimal point, and the maintenance update version number is indicated by the digits to the right of the decimal point. Keep this document with your distribution kit. You will need it to install maintenance updates or to reinstall the ALL-IN-1 DESKtop Server for any other reason. At the back of this document are two Reader's Comments forms. If you have any comments about this document, please fill out one form and mail it; your comments will be considered for the next revision of the installation guide. For more information about installing the ALL-IN-1 DESKtop Server on VMS systems, refer to your processor-specific installation/operations guide. The installation procedure is described step-by-step and is, for the most part, self-explanatory. The system prompts you to answer questions and to change volumes, and waits for you to tell it to continue. v Conventions __________________________________________________________ Convention_______Meaning__________________________________ ALL-IN-1 Throughout this manual the ALL-IN-1 DESKtop DESKtop for DOS and ALL-IN-1 DESKtop for Macintosh[R] clients are referred to as ALL-IN-1 DESKtop. ALL-IN-1 Throughout this manual the ALL-IN-1 DESKtop Server DESKtop Server for VMS is referred to as the ALL-IN-1 DESKtop Server. CTRL/x Hold down the CTRL key while you press the designated letter key. [] Default replies to installation queries appear in brackets throughout the installation procedure. Color____________Color_in_examples_shows_user_input.______ vi 1 Preparing to Install the ALL-IN-1 DESKtop Server for VMS Your bill of materials (BOM) and Indented Bills Report (BIL) specify the number and contents of your media. Be sure to check the contents of your kit against this information. If your kit is damaged, or if you find that parts of it are missing, call your Digital representative. Distribution media must be mounted in numerical order. The installation procedure prompts you to mount the volumes. For more information on how to mount distribution media, refer to your processor-specific installation/operations guide. This guide also details several options to the installa- tion procedure. The following sections include general information that is useful to know before starting the installation procedure. 1.1 Prerequisite Hardware o VAX[TM] hardware 1.2 Prerequisite Software The following software products must be installed on your system before you install the ALL-IN-1 DESKtop Server. o VMS Version 5.3 or higher o ALL-IN-1 Version 2.4 o ALL-IN-1 Starter Version 2.4 1.3 Prerequisite Operating System Components The VMS operating system comes with a variety of support options, or classes. Classes include such features as networking and VAX RMS[TM] journaling. The ALL-IN-1 DESKtop 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 ALL-IN-1 DESKtop Server. 1 1.4 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, refer to your processor-specific installation/operations guide. 1.5 Accessing the Online Release Notes The ALL-IN-1 DESKtop Server provides online release notes. The prompt to display or print the release notes before installation appears in Step 5 of the installation procedure when you invoke VMSINSTAL with the OPTIONS N parameter (the OPTIONS N parameter is available only with Version 4.4 of VMS or higher). To obtain the release notes after the installation, type or print the file SYS$HELP:A1SVC011.RELEASE_NOTES. 1.6 Time Required for Installation The total installation takes approximately 10 minutes to one hour, depending on the type of media, your system configuration, and whether or not you run the Installation Verification Procedure (IVP). Installing the ALL-IN-1 DESKtop Server and running the IVP takes approximately 50 minutes on a standalone MicroVAX[TM] 3600 system and approximately 11 minutes on a VAX 8800. 1.7 Privileges Required for Installation To install the ALL-IN-1 DESKtop Server, you must be logged in to an account that has SETPRV or at least the following privileges: o CMKRNL o WORLD o SYSPRV o SYSNAM 2 o OPER 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.8 Disk Space Required for Installation Table 1 lists the approximate disk space required to install the ALL-IN-1 DESKtop Server. Table_1_Disk_Space_Requirements___________________________ Blocks During Blocks After Kit______________Installation__________Installation_______ ALL-IN-1 12000 9000 plus DESKtop Server additional blocks for VMS Version due to SITE OAFORM 1.1____________________________________Library_changes____ An installation can require more than 12000 blocks if the form libraries are on a separate disk and there is not enough quota on that disk or you have spread your current ALL-IN-1 files across multiple spindles on different disk drives. For the names and sizes of files added during installation, see Section 6 and Section 7. 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.9 System Parameter Settings Required for Installation Installing the ALL-IN-1 DESKtop Server requires certain system parameter settings. Table 2 lists the minimum required system parameter values for the installation. Depending on the kinds of applications running at your site, you might need higher values for some settings. 3 Table_2_Required_System_Parameter_Values__________________ System_Parameter___________Value__________________________ GBLPAGES n[1] + 400 GBLSECTIONS n[1] + 30 [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 and change the values for the GBLPAGES and GBLSECTIONS system parameters. 1.9.1 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run the ALL-IN-1 DESKtop 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 2, you do not need to increase the values for these parameters. If the value of free global pages or global sections is lower than the value in Table 2, you must increase the system parameter setting. 4 Section 1.9.2 describes how to increase these values using AUTOGEN. Refer to your processor-specific installation /operations guide for information on using AUTOGEN. 1.9.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 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. 5 For more information about using AUTOGEN, see the VMS System Management Subkit. 1.10 Process Account Quotas The user account you use to install the ALL-IN-1 DESKtop Server must have sufficient process quotas to enable you to perform the installation. Table 3 summarizes the minimum process quotas required for the installation. Table_3_Process_Account_Quotas_for_the_Installing_Account_ Account_Quota____Minimum_Value____________________________ ASTLM 10 BIOLM 18 BYTLM 18,000 DIOLM 18 ENQLM 30 FILLM 20 TQELM____________10_______________________________________ 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 6 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 VMS Authorize Utility Manual. 1.11 Special Requirements Before installing the ALL-IN-1 DESKtop Server, it is recommended but not necessary that you shut down ALL- IN-1. During installation, several ALL-IN-1 system form libraries are updated with new forms. The installation process requires exclusive access to these libraries in order to add the new forms. If exclusive access is not possible, extra copies of the form libraries are made so the forms can be inserted. This consumes extra time and disk space. 1.12 Setting up ALL-IN-1 DESKtop Server Accounts In order for the ALL-IN-1 DESKtop Server (that is, the ALL-IN-1 DESKtop scheduler and message servers) to operate properly, you must create one distinct privileged ALL-IN-1 account for each message server you intend to use. Before starting the ALL-IN-1 DESKtop Server, at least one message server must have been created as detailed below. If the ALL-IN-1 DESKtop Server is not configured properly, users will not be able to send or receive electronic mail. During the installation process, you will be asked the following two questions: 1. What privileged VMS username should the DESKtop Server use? [ALLIN1]: 7 Digital recommends that the ALL-IN-1 DESKtop scheduler and message servers run within the VMS account ALLIN1. If you choose to use some other VMS account, it must be set up as follows: o Assign appropriate privileges to the VMS account: EXQUOTA, WORLD, SYSGBL, PRMGBL, PRMMBX, SYSPRV, SYSNAM, NETMBX, GRPNAM, OPER, TMPMBX, CMKRNL, SYSLCK, VOLPRO o Ensure that the quotas for the ALL-IN-1 DESKtop Server account are sufficient as shown in Table 4: Table_4_ALL-IN-1_DESKtop_Server_Account_Quotas____________ Account_Quota____Minimum_Value____________________________ ASTLM 10 + the number of users specifying a minimum interval BIOLM 18 BYTLM 18,000 DIOLM 18 ENQLM 30 FILLM 20 TQELM 10 + the number of users specifying a _________________minimum_interval_________________________ For information on determining and modifying account quotas, see Section 1.10. 2. What ALL-IN-1 account should the first message server use? Each ALL-IN-1 DESKtop message server must have its own distinct ALL-IN-1 account, which must be configured similarly to an ALL-IN-1 system manager's account. Each message server account must share the single VMS account you specified in answer to question 1. 8 Each ALL-IN-1 message server account must be unique when compared to all other ALL-IN-1 accounts. This includes their underlying VMS directory structures. Do not share or otherwise overlap the ALL-IN-1 directory structures among these accounts. Digital recommends a directory structure similar to the following example for each ALL-IN-1 message server account: VMS Username = ALLIN1 Site Configuration Parameter = ALLIN1_SERVER_ACCOUNT_1 = "DESKTOP_1" VMS Directory = LOGICAL$DEVICE_NAME:[ALLIN1.DESKTOP_1.A1] The following is an example of the User Profile entry for the ALL-IN-1 system manager account "DESKTOP_1". ------------------------------------------------------------------------------- Read Account Details ALL-IN-1 account details: Account name: DESKTOP_1 Template used: USER Directory: LOGICAL$DEVICE_NAME:[ALLIN1.DESKTOP_1.A1] Form libr: OA$LIB:MANAGER VMS account details: Account name: ALLIN1 User details: Surname: DESKTOP_1 Given name: JOE Initials: JD Full name: JOE DESKTOP_1 ------------------------------------------------------------------------------- 9 1.13 Multiple Message Servers To improve your ALL-IN-1 DESKtop Server's performance you might require more than one message server. For each message server you specify, an ALL-IN-1 DESKtop site configuration parameter must be created and specified. These parameters tell the scheduler which ALL-IN-1 accounts to use for the different message servers. Your first and, therefore, primary message server will have a site configuration parameter called ALLIN1_SERVER_ ACCOUNT_1 and its value will be the username of the ALL- IN-1 account you created for it. Your secondary message server will have a site configuration parameter called ALLIN1_SERVER_ACCOUNT_2 and its value will be the username of the unique ALL-IN-1 account you created for it. Your remaining message servers follow the same pattern. The total number of these parameters depends on the number of message servers you want to use. If you want just one message server, then you need only one site configuration parameter called ALLIN1_SERVER_ACCOUNT_1. Its value is the single ALL-IN-1 account that you designated for this purpose. This first parameter is created for you during the installation process. You can create additional parameters using the ALL-IN-1 DESKtop System Management screen's Manage DESKtop Site Configuration Details option. For information about creating site configuration parameters with this option, see the ALL-IN-1 DESKtop Server for VMS Management Guide. ________________________Note ________________________ You do not need to nominate the ALL-IN-1 message server accounts as ALL-IN-1 Administrator accounts. _____________________________________________________ The following example shows how multiple ALL-IN-1 accounts would relate to multiple Site Configuration Parameters: 10 VMS Username = ALLIN1 Site Configuration Parameter = ALLIN1_SERVER_ACCOUNT_1 = "DESKTOP_1" VMS Directory = LOGICAL$DEVICE_NAME:[ALLIN1.DESKTOP_1.A1] VMS Username = ALLIN1 Site Configuration Parameter = ALLIN1_SERVER_ACCOUNT_2 = "DESKTOP_2" VMS Directory = LOGICAL$DEVICE_NAME:[ALLIN1.DESKTOP_2.A1] VMS Username = ALLIN1 Site Configuration Parameter = ALLIN1_SERVER_ACCOUNT_3 = "DESKTOP_3" VMS Directory = LOGICAL$DEVICE_NAME:[ALLIN1.DESKTOP_3.A1] For more information about managing the ALL-IN-1 DESKtop site configuration database, see the ALL-IN-1 DESKtop Server for VMS Management Guide. For information about creating ALL-IN-1 accounts with system manager rights and privileges, see the ALL-IN-1 Management Guide. 2 Installing the ALL-IN-1 DESKtop Server The following sections provide information on using the VMSINSTAL procedure and the steps to follow when performing an installation, including installation questions that appear when you install the ALL-IN-1 DESKtop Server. 2.1 Using VMSINSTAL To start the installation, log in to a privileged account, set the default to SYS$UPDATE:, and then invoke VMSINSTAL, the command procedure that installs this product: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL saveset-name device-name: OPTIONS N If you do not supply the first two parameters, VMSINSTAL prompts you for the product and device names. If you want to be prompted for the product and device names and to display or print the release notes, type the following. $ @SYS$UPDATE:vmsinstal "" "" OPTIONS N The command parameters are described in the next paragraphs. 11 saveset-name Saveset-name is the installation name for the component. For the ALL-IN-1 DESKtop Server, use the following installation name: A1SVC011 The last three characters represent the version number and point release of the current ALL-IN-1 DESKtop Server. These three characters are optional. You can 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 allows you to display or print the release notes. If you do not include the OPTIONS N parameter in the command line, VMSINSTAL does not prompt you to display or print the release notes. Review the release notes before proceeding with the installation for new information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. Once the ALL-IN-1 DESKtop Server has been installed, the release notes are located in the file SYS$HELP:A1SVC011.RELEASE_NOTES. There are several other options you can select when you invoke VMSINSTAL. For information on these options refer to your processor-specific installation/operations guide. When you invoke VMSINSTAL, it checks the following: o Whether you logged in to a privileged account. Digital recommends that you install software from the system manager's account with your default device and directory set to SYS$UPDATE. 12 o Whether you have adequate quotas for installation. See Table 3 for a list of process account quotas. VMSINSTAL then checks whether the following conditions exist. If so, discontinue the conditions before resuming the installation procedure. o Whether DECnet[TM] is up and running o Whether any users are logged in to the system If VMSINSTAL detects either of these conditions, you will be asked whether you want to continue the installation. If you want to continue, type YES. If you want to stop the installation, press Return. As of VMS Version 5.0, some products use the VMS License Management Facility (LMF) to automatically register the product on line. The ALL-IN-1 DESKtop Server does not use the LMF for licensing. 2.2 Installation Procedure The ALL-IN-1 DESKtop Server installation procedure consists of a series of questions and informational messages. This section contains excerpts from the installation procedure and explains each step. 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. Section 5 contains sample installation procedures that show how the questions can be answered. Questions that are not included in the samples can be found in the Installation Procedure 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. To abort 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 then returns you to DCL level. If you want to retry the installation procedure after pressing Ctrl/Y, you must proceed from Step 2. 13 Step 1: Log in to a privileged account and set your default device and directory to SYS$UPDATE. Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE Step 2: Invoke VMSINSTAL. $ @VMSINSTAL A1SVC011 CSA1: OPTIONS N VAX/VMS Software Product Installation Procedure VX.X It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? It is recommended that you always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press Return. Otherwise, type NO and press Return to discontinue the installation. After you back up your system disk, you can restart the installation. Step 3: Insert the first installation kit volume. Please mount the first volume of the set on CSA1:. * Are you ready? YES The following products will be processed: A1SVC V1.1 Beginning installation of A1SVC V1.1 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product saveset A... To indicate that you want to continue the installation, mount volume 1, type YES, and then press Return. 14 Step 4: Insert the subsequent installation kit volumes. %BACKUP-I-READYREAD, mount volume 2 on _CSA1: for reading Enter "YES" when ready: YES VMSINSTAL prompts you to insert the next volume and waits for you to type YES after inserting it. If you type NO, VMSINSTAL displays the prompt again. This prompt is displayed only if your installation kit contains more than one volume. Step 5: Select a release notes option. This step applies only if you specified OPTIONS N in Step 2. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 * Select option [3]: If you select option 1, VMSINSTAL displays the release notes on line immediately. You can terminate the display at any time by pressing Ctrl/C. If you select option 2, VMSINSTAL prompts you for a queue name. Either type a queue name or press Return to send the file to the default output print device. * Queue name [SYS$PRINT]: If you select option 3, VMSINSTAL displays the release notes on line immediately and then prompts you for a queue name. The ALL-IN-1 DESKtop Server release notes are then copied to SYS$HELP:A1SVC$011.RELEASE_NOTES. Next, VMSINSTAL displays the following prompt: * Do you want to continue the installation [N]?: Y %VMSINSTAL-I-RELMOVED, The product release notes have been successfully moved to SYS$HELP. 15 If you want to continue the installation, type YES and press Return. If you type NO or press Return, VMSINSTAL discontinues the installation. In either case, VMSINSTAL moves the release notes to SYS$HELP. Step 6: Select installation options. * Do you want to run the IVP after the installation [YES]? The IVP runs tests to check whether the installation procedure was successful. It is recommended that you run the IVP to make sure that the ALL-IN-1 DESKtop Server is installed correctly. Press Return to run the IVP after the installation is in place. If you do not want to run the IVP, type NO in response to the prompt. * Do you want to purge files replaced by this installation [YES]? The directories SYS$EXAMPLES, SYS$HELP, SYS$LIBRARY, SYS$MANAGER, and SYS$SYSTEM could contain previous versions of the ALL-IN-1 DESKtop Server files. These files are replaced during the installation with new files, but the old files are not automatically purged. Purging is recommended. In response to the purging prompt, press Return to purge the files or type NO to keep them. Step 7: Install on what device * Install DESKtop Server on what device [SYS$SYSDEVICE:]: VMSINSTAL asks on what device you want to install the ALL-IN-1 DESKtop Server. Step 8: ALL-IN-1 DESKtop Server has been previously installed %A1SVC-I-INSTALLED, a version of DESKtop Server is currently installed on SYS$SYSDEVICE: * Do you want to continue with this installation [NO]? YES * Do you want to preserve existing data [YES]? 16 If the ALL-IN-1 DESKtop Server Version 1.0 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 if you want to preserve existing data. You can 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. If the ALL-IN-1 DESKtop Server Version 1.1 has been previously installed on your system and you have subsequently updated ALL-IN-1, you are notified with a message and asked if you want to continue with a full product reinstallation or reinstall the FMS forms only. An initial ALL-IN-1 DESKtop Server installation updates the ALL-IN-1 form libraries OAFORM, MEMRES and MANAGER for each language with its own system management forms. Normally these libraries are not updated by any other products and are considered by ALL-IN-1 to be wholly replaceable when ALL-IN-1 is subsequently upgraded. However, when ALL-IN-1 is upgraded and the ALL-IN-1 form libraries are replaced, the existing ALL-IN-1 DESKtop system management forms are lost. To avoid this form library conflict after an ALL-IN-1 upgrade, ALL-IN-1 DESKtop provides a reinstallation option that allows you to reinstall the forms for each language variant without having to reinstall the whole ALL-IN-1 DESKtop Server. This also preserves the existing data files for registered users. You must run the ALL-IN- 1 DESKtop Server forms reinstallation option after an upgrade of ALL-IN-1 or the ALL-IN-1 DESKtop Server will not function properly. The forms reinstallation tells you what languages you originally chose. You must reinstall the same languages, but you can add more languages to the ones you originally installed. See Section 5.3 for a sample installation log. 17 Step 9: Entering language code * Enter language code 1 [ENGLISH]: * Enter language code 2: %A1SVC-I-NUMLANG, installation of 1 language has been requested The ALL-IN-1 DESKtop Server updates ALL-IN-1 form libraries with new forms. These forms are added to the language dependent areas of ALL-IN-1. You can select as many languages as needed at the prompt. The languages you specify must have already been created via ALL-IN-1. The language choices are as follows: o English o German o French o Italian o Danish o Portuguese o Swedish o Hungarian o Dutch o Spanish o Norwegian o Hebrew For each language chosen, the language dependent version of each of the three ALL-IN-1 form libraries is updated to include the necessary VMS Server forms. For example, if the language chosen is ENGLISH, the libraries that are updated are OA$LIB_ENGLISH:MANAGER.FLB, OA$LIB_ ENGLISH:MEMRES.FLB, and OA$LIB_ENGLISH:OAFORM.FLB. Press Return at the prompt when you are finished entering languages. 18 Step 10: Clustered environment * Will this be a clustered environment [NO]? YES You can run the ALL-IN-1 DESKtop Server on a VAXcluster[TM]. Answer YES to this question if you want load balancing of server processes across your cluster. Step 11: VMS account for ALL-IN-1 DESKtop Server * What privileged VMS username will the DESKtop Server use? [ALLIN1]: The ALL-IN-1 DESKtop Server uses a privileged VMS account as a processing account for its components, the scheduler and task servers. The scheduler requires that the SYSUAF entry for its VMS account specify minimum values for ASTLM and TQELM. The recommended minimum values can be calculated by adding 10 to the total number of registered DESKtop users. For example, if the number of DESKtop users will be 55, then the minimum recommended ASTLM and TQELM for the scheduler's VMS account should be 65 each. Any necessary changes must be made to the SYSUAF prior to executing the DESKtop startup procedure A1SVC$STARTUP.COM. %A1SVC-I-ASTLM, current ASTLM of 100 for ALLIN1 creates a limit of 94 users %A1SVC-I-TQELM, current TQELM of 50 for ALLIN1 creates a limit of 43 users For more information about setting up ALL-IN-1 DESKtop Server accounts see Section 1.12. Step 12: VMS account for First ALL-IN-1 DESKtop Server Message Server What ALL--IN--1 account should the first Message Server use? Each ALL-IN-1 DESKtop message server must have its own distinct ALL-IN-1 account and must share the VMS account you specified in Step 11. For more information see Section 1.12. 19 Step 13: Scheduler's interval * What time of day should the Scheduler start? (HH:MM) [06:00]: 6:30 * What time of day should the Scheduler stop? (HH:MM) [22:00]: 19:30 You can specify the time of day the scheduler begins operation and ends operation. For information about specifying the scheduler's interval, see the ALL-IN-1 DESKtop Server for VMS Management Guide. Step 14: Read 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: %A1SVC-I-VERSION, installing V1.1 Upon completion of this procedure, the POST INSTALLATION procedure below must be performed and two system command procedures must be changed to complete the installation: o SYS$STARTUP:SYSTARTUP_V5.COM Edit this file to invoke the ALL-IN-1 DESKtop Server for VMS startup procedure, SYS$STARTUP:A1SVC$STARTUP.COM. Include the startup procedure after your system applications (DECnet, FMS[TM], Message Router, ALL-IN-1, etc.) have been started. o SYS$MANAGER:SYLOGIN.COM Edit this file to invoke A1SVC$LIB:A1SVC$SYMBOLS.COM on behalf of ALL-IN-1 DESKtop users during interactive login. Optionally, this file can be invoked by individual users through their own LOGIN.COM file. (Note that the logical A1SVC$LIB must be defined prior to calling this command procedure.) o Post Installation Procedures In order for the ALL-IN-1 DESKtop Server to work properly the ALL-IN-1 TXL must be recompiled so that it includes the ALL-IN-1 DESKtop Scripts. STEP 1. When this procedure finishes, enter 20 @SYS$STARTUP:A1SVC$STARTUP NOSTART to define the logical names needed for Step 2. STEP 2. Log in to the ALL-IN-1 Managers account, usually named ALLIN1, and run ALL-IN-1. Enter into the SM menu, choose the CSZ option then choose CTX. This will recompile the TXL. Please refer to the POST INSTALLATION PROCEDURE in the Installation Guide. After the instructions, the following prompt and message are displayed: * Press Return to continue...: All questions regarding the installation have been asked. No further responses will be required. The remainder of this installation can take between 20 and 60 minutes depending on the system resources available. As the remainder of the installation completes, you will see a number of informational messages that report on the progress of the installation. If you typed YES in response to the prompt that requests a file purge at Step 6, previous versions of the ALL-IN-1 DESKtop Server files are now purged. Step 15: Observe the Installation Verification Procedure. If you chose to run the IVP in Step 6, VMSINSTAL now calls the IVP to verify that the ALL-IN-1 DESKtop Server was installed successfully. When the IVP runs successfully, you see the following display: %A1SVC-I-IVPPHASE1, Installation Verification Procedure phase 1 %A1SVC-I-IVPOK, installation verification procedure completed successfully If an error occurs during the installation, the same completion message is displayed along with an error message. 21 Step 16: End the installation procedure. The following messages indicate that the entire installa- tion procedure is complete: Installation of A1SVC V1.1 completed at 11:41 VMSINSTAL procedure done at 11:41 $ LOGOUT SYSTEM logged out at 23-SEP-1991 11:50:22.16 When the product installation procedure is complete, you can choose to install more products, or to log out (as shown here.) If you removed any media from the console drive before beginning the installation, you should replace it now. 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 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.4 Running the Installation Verification Procedure Separately After the ALL-IN-1 DESKtop 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 ALL-IN-1 DESKtop Server. To run the IVP independently after the ALL-IN-1 DESKtop Server is installed, enter the following command: $ @SYS$TEST:A1SVC$IVP 22 2.5 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.1 has failed. If the IVP fails, you see these messages: The A1SVC V1.1 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for A1SVC V1.1 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o ALL-IN-1 Version 2.4 or ALL-IN-1 Starter Version 2.4 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 Section 1. 3 After Installing the ALL-IN-1 DESKtop Server The following sections describe how to determine what files and logical names were created during the installation, how to edit the system startup file and the syslogin file, start the scheduler, set up user accounts, and shut down the ALL-IN-1 DESKtop Server. 23 3.1 Files and Logical Names Added to the System During Installation The ALL-IN-1 DESKtop Server installation process creates some directories and files on your system. For a complete list of files, look in the following directories: disk:[A1SVC.LIB] disk:[A1SVC.LIB.DO_SHARE] disk:[A1SVC.LIB.SCP_SHARE] disk:[A1SVC.LIB.BLP_SHARE] disk:[A1SVC.LIB.DO_LLV] disk:[A1SVC.LIB.SCP_LLV] disk:[A1SVC.LIB.BLP_LLV] disk:[A1SVC.SITE] disk:[A1SVC.SITE.DO_SHARE] disk:[A1SVC.SITE.SCP_SHARE] disk:[A1SVC.SITE.BLP_SHARE] disk:[A1SVC.SITE.DO_LLV] disk:[A1SVC.SITE.SCP_LLV] disk:[A1SVC.SITE.BLP_LLV] disk:[A1SVC.DATA] 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 OA$A1SVC$LIB disk:[A1SVC.LIB] $ DEFINE/SYSTEM/EXEC OA$SITE_A1SVC$LIB disk:[A1SVC.SITE] $ DEFINE/SYSTEM/EXEC A1SVC$ORIG disk:[A1SVC.LIB] $ DEFINE/SYSTEM/EXEC A1SVC$LIB_DO_SHARE disk:[A1SVC.LIB.DO_SHARE] $ DEFINE/SYSTEM/EXEC A1SVC$LIB_SCP_SHARE disk:[A1SVC.LIB_SCP_SHARE $ DEFINE/SYSTEM/EXEC A1SVC$LIB_BLP_SHARE disk:[A1SVC.LIB_BLP_SHARE $ DEFINE/SYSTEM/EXEC A1SVC$LIB_DO_LLV disk:[A1SVC.LIB.DO_LLV] $ DEFINE/SYSTEM/EXEC A1SVC$LIB_SCP_LLV disk:[A1SVC.LIB_SCP_LLV $ DEFINE/SYSTEM/EXEC A1SVC$LIB_BLP_LLV disk:[A1SVC.LIB_BLP_LLV 24 $ DEFINE/SYSTEM/EXEC A1SVC$SITE disk:[A1SVC.SITE] $ DEFINE/SYSTEM/EXEC A1SVC$SITE_DO_SHARE disk:[A1SVC.SITE.DO_SHARE] $ DEFINE/SYSTEM/EXEC A1SVC$SITE_SCP_SHARE disk:[A1SVC.SITE_SCP_SHARE $ DEFINE/SYSTEM/EXEC A1SVC$SITE_BLP_SHARE disk:[A1SVC.SITE_BLP_SHARE $ DEFINE/SYSTEM/EXEC A1SVC$SITE_DO_LLV disk:[A1SVC.SITE.DO_LLV] $ DEFINE/SYSTEM/EXEC A1SVC$SITE_SCP_LLV disk:[A1SVC.SITE_SCP_LLV $ DEFINE/SYSTEM/EXEC A1SVC$SITE_BLP_LLV disk:[A1SVC.SITE_BLP_LLV $ DEFINE/SYSTEM/EXEC A1SVC$DATA disk:[A1SVC.DATA] $ DEFINE/SYSTEM/EXEC A1SVC$LOG disk:[A1SVC.LOG] $ DEFINE/SYSTEM/EXEC A1SVC$LIB A1SVC$SITE, A1SVC$SITE_DO_SHARE, - A1SVC$SITE_SCP_SHARE, - A1SVC$SITE_BLP_SHARE, - A1SVC$SITE_DO_LLV, - A1SVC$SITE_SCP_LLV, - A1SVC$SITE_BLP_LLV, - A1SVC$ORIG, - A1SVC$LIB_DO_SHARE, - A1SVC$LIB_SCP_SHARE, - A1SVC$LIB_BLP_SHARE, - A1SVC$LIB_DO_LLV, - A1SVC$LIB_SCP_LLV, - A1SVC$LIB_BLP_LLV $ DEFINE/SYSTEM/EXEC A1SVC$TMP SYS$SCRATCH A1SVC$LIB is a logical search list. 3.2 Editing the System Files Edit the system startup file SYS$STARTUP:SYSTARTUP_V5.COM to add the command line that starts the ALL-IN-1 DESKtop Server. This command provides for automatic startup of the ALL-IN-1 DESKtop Server when the system is rebooted. The ALL-IN-1 DESKtop Server startup command is: @SYS$STARTUP:A1SVC$STARTUP The ALL-IN-1 DESKtop Server must be started after the network and your system applications (DECnet, FMS, Message Router, ALL-IN-1) have been started. Position the ALL-IN-1 DESKtop Server startup command in the system startup file after the commands that start the network and applications. 25 A1SVC$STARTUP must be executed on each node in your cluster that you want to have the scheduler, message server, or MBA server running. This provides for cluster load balancing and failover through the creation and use of generic and execution batch queues for starting server processes. To set up the required symbols for the ALL-IN-1 DESKtop client environment, add the VMS Server symbol definition command into the system login procedure. This allows interactive user processes to access the ALL-IN-1 DESKtop Server. Edit the system login file SYLOGIN.COM or the LOGIN.COM file of each user who will be using ALL-IN-1 DESKtop to include the following line: @A1SVC$LIB:A1SVC$SYMBOLS ______________________ Caution ______________________ Placing A1SVC$LIB:A1SVC$SYMBOLS.COM in the sys- temwide login file can cause batch jobs to terminate abnormally if ALL-IN-1 DESKtop is not yet started. Execution of this command file is only necessary for interactive ALL-IN-1 DESKtop clients. The command added should be: $ IF F$MODE().EQS."INTERACTIVE" THEN @A1SVC$LIB:A1SVC$SYMBOLS _____________________________________________________ 3.3 Recompiling and Reinstalling the ALL-IN-1 Text Library (TXL) After you have installed the Server, you must recompile and reinstall the ALL-IN-1 Text Library (TXL) on your system. You only need to recompile the TXL once. But if the Server is running in a VAXcluster environment then you must install the TXL on each VAX system of the cluster. To recompile the TXL, use the ALL-IN-1 System Manager's menu. From the ALL-IN-1 Manager's account, type SM. From this menu, access the CSZ option, Manage a Customized System. Use the CTX option on the CSZ menu to compile the TXL. 26 Once you have recompiled the ALL-IN-1 TXL, you can reinstall the TXL on the remaining nodes without recompiling. There is no menu option to do this; however, you can install the updated TXL on each machine by doing the following: 1. Log in to the ALL-IN-1 Manager's account on the node 2. Execute the Server Startup command procedure using the NOSTART parameter: $ @SYS$STARTUP:A1SVC$STARTUP NOSTART 3. Bring up ALL-IN-1 by typing ALLIN1/USER=MANAGER 4. Type: