AA-LP99B-TE ALL-IN-1_STARTER_____________________________________ Installation Guide Part 1 Base Installation digital equipment corporation maynard, massachusetts AA-LP99B-TE First Printing, October 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 be used or copied only in accordance with the terms of such license. Digital Equipment Corporation assumes no responsibility for the use or reliability of its software on equipment that is not supplied by Digital. 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. Copyright (c) Digital Equipment Corporation. 1990. All rights reserved. Please complete the reader's comments page at the end of the book. It will help us to keep improving our documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-1 EDT VAX DOCUMENT CDA MicroVAX VAX FMS DEC RSTS VAX Grammar Checker DECdx RSX VAXstation DECmail TK50 VMS DECnet/VAX TOPS-20 WPS-PLUS DECpage VAX +-+-+-+-+-+-+-+TM DECspell VAXcluster |d|i|g|i|t|a|l| DX VAX DECpage +-+-+-+-+-+-+-+ PostScript is a registered trademark of Adobe Systems, Inc. This document was prepared using VAX DOCUMENT, Version 1.2. ________________________________________________________________ Contents Preface.................................................. xiv 1 Preparing to Install ALL-IN-1 STARTER V2.4 1.1 Examining the Distribution Kit.................. 1-4 1.1.1 Magnetic Tape and TK50 Kits .................. 1-4 1.1.2 Compact Disk Consolidated Software Distribution Kits............................ 1-5 1.2 VMS License Management Facility................. 1-6 1.3 Required Operating System Components............ 1-7 1.4 Prerequisite Software........................... 1-8 1.4.1 Installed Images ............................. 1-9 1.5 Optional Software Products...................... 1-11 1.5.1 Initial CDA Support .......................... 1-13 1.5.2 Integrating Message Router and the Message Router VMSmail Gateway with ALL-IN-1 STARTER...................................... 1-14 1.5.2.1 The Mail Directory and the ALL-IN-1 Directory.................................. 1-15 1.5.3 Integrating WPS-PLUS with ALL-IN-1 STARTER ... 1-15 1.5.4 Installation Order ........................... 1-16 iii 1.5.5 Keeping a Record of the Installation ......... 1-17 1.6 Installing ALL-IN-1 STARTER on VAXcluster Systems......................................... 1-18 1.6.1 Installing ALL-IN-1 STARTER on a Common-Environment Cluster................... 1-18 1.6.1.1 Running ALL-IN-1 STARTER on a Common-Environment Cluster................. 1-18 1.6.2 Installing ALL-IN-1 STARTER on a Multiple-Environment Cluster................. 1-20 1.6.2.1 Running ALL-IN-1 STARTER on a Multiple-Environment Cluster............... 1-21 1.6.3 Installing ALL-IN-1 STARTER on a Local Area VAXcluster System............................ 1-22 1.7 Installing Additional Languages................. 1-23 1.8 Preparing the System for Installation........... 1-24 1.8.1 Time Needed to Install ALL-IN-1 STARTER Version 2.4.................................. 1-27 1.8.2 Privileges ................................... 1-27 1.8.3 Back Up Your System and Target Disks ......... 1-27 1.8.4 Ensure No Active Users on the System ......... 1-27 1.8.5 Performance Customizations of PROFILE.FDL and PROFILE.DAT.................................. 1-28 1.8.6 Register the Licenses for the Prerequisite Software..................................... 1-28 1.8.7 Ensure Message Router Directory Service is Running...................................... 1-29 1.8.8 Shut Down the OA$FORMATTER Batch Queue ....... 1-29 1.8.9 Start the Queue Manager ...................... 1-29 1.8.10 Run the Mail Sender and Fetcher .............. 1-29 1.8.11 Delete the ALL-IN-1 Housekeeping Jobs ........ 1-30 1.8.12 Calculate the Values for GBLPAGES, GBLSECTIONS and GBLPAGFIL.................... 1-30 1.8.13 Check the System Parameter Values ............ 1-35 1.8.14 Changing System Parameter Values with AUTOGEN...................................... 1-37 1.8.15 Process Account Quotas ....................... 1-38 iv 1.8.16 Disk Space ................................... 1-39 1.8.16.1 Installation Modes......................... 1-40 1.8.16.2 ALL-IN-1 Areas............................. 1-41 1.8.17 Check Your Site-Specific Startup Procedures .. 1-45 1.8.18 Checklist of Information Required for Installation................................. 1-46 1.8.19 License Management Utility Requirements ...... 1-46 2 Accessing the Online Release Notes 2.1 Accessing the Release Notes..................... 2-2 3 Installing a New ALL-IN-1 STARTER V2.4 System 3.1 Before You Start................................ 3-1 3.2 Overview of VMSINSTAL........................... 3-1 3.3 Determining the Files and Logical Names Added to the System...................................... 3-2 3.4 Running the Installation Verification Procedure (IVP)........................................... 3-2 3.5 Aborting the Installation....................... 3-2 3.6 Warning and Error Messages...................... 3-2 3.7 The Installation Procedure...................... 3-3 3.8 Error Recovery.................................. 3-6 3.8.1 Errors Found During the IVP .................. 3-7 4 Installing Additional Languages for ALL-IN-1 STARTER V2.4 4.1 Before You Start................................ 4-1 4.2 Overview of VMSINSTAL........................... 4-2 4.3 Determining the Files and Logical Names Added to the System...................................... 4-2 4.4 Running the Installation Verification Procedure (IVP)........................................... 4-2 v 4.5 Aborting the Installation....................... 4-3 4.6 Warning and Error Messages...................... 4-3 4.7 The Installation Procedure...................... 4-3 4.8 Error Recovery.................................. 4-4 4.8.1 Errors Found During the IVP .................. 4-5 5 Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 5.1 Before You Start................................ 5-1 5.2 Overview of VMSINSTAL........................... 5-2 5.3 Determining the Files and Logical Names Added to the System...................................... 5-3 5.4 Running the Installation Verification Procedure (IVP)........................................... 5-3 5.5 Aborting the Installation....................... 5-3 5.6 Warning and Error Messages...................... 5-3 5.7 The Installation Procedure...................... 5-4 5.8 Stop and Start the OA$FORMATTER Queue........... 5-6 5.9 Error Recovery.................................. 5-6 5.9.1 Errors Found During the IVP .................. 5-7 6 Upgrading ALL-IN-1 STARTER V1.0 Languages to ALL-IN-1 STARTER V2.4 Languages 6.1 Before You Start................................ 6-1 6.2 Overview of VMSINSTAL........................... 6-2 6.3 Determining the Files and Logical Names Added to the System...................................... 6-2 6.4 Running the Installation Verification Procedure (IVP)........................................... 6-2 6.5 Aborting the Installation....................... 6-3 6.6 Warning and Error Messages...................... 6-3 6.7 The Installation Procedure...................... 6-3 6.8 Error Recovery.................................. 6-4 6.8.1 Errors Found During the IVP .................. 6-5 vi 7 Updating an Existing ALL-IN-1 STARTER V2.4 System 7.1 Before You Start................................ 7-1 7.2 Overview of VMSINSTAL........................... 7-2 7.3 Determining the Files and Logical Names Added to the System...................................... 7-2 7.4 Running the Installation Verification Procedure (IVP)........................................... 7-2 7.5 Aborting the Installation....................... 7-2 7.6 Warning and Error Messages...................... 7-3 7.7 The Installation Procedure...................... 7-4 7.8 Start the OA$FORMATTER Queue.................... 7-5 7.9 Error Recovery.................................. 7-5 7.9.1 Errors Found During the IVP .................. 7-6 8 Updating an ALL-IN-1 STARTER V2.4 Language 8.1 Before You Start................................ 8-1 8.2 Overview of VMSINSTAL........................... 8-2 8.3 Determining the Files and Logical Names Added to the System...................................... 8-2 8.4 Running the Installation Verification Procedure (IVP)........................................... 8-2 8.5 Aborting the Installation....................... 8-3 8.6 Warning and Error Messages...................... 8-3 8.7 The Installation Procedure...................... 8-3 8.8 Error Recovery.................................. 8-4 8.8.1 Errors Found During the IVP .................. 8-5 9 Steps Required for Installing ALL-IN-1 STARTER V2.4 9.1 Installation Steps.............................. 9-1 vii 10 After Installing ALL-IN-1 STARTER V2.4 10.1 Replace the DCLTABLES on VAXcluster Systems..... 10-4 10.2 Convert the User Profiles....................... 10-5 10.3 Convert SM_ACCOUNT_TYPES.DAT.................... 10-5 10.4 Update the License Count and Subscriber Count for ALL-IN-1 STARTER............................ 10-5 10.5 CDA Support..................................... 10-6 10.6 Delete Files That Are No Longer Required........ 10-6 10.7 Considerations for the OA$MTI_ERR and OA$MTI_LOG Files........................................... 10-6 10.8 Convert the Format of OA$DATA_SHARE:SM_USED_UIC.DAT................... 10-7 10.9 Performance Customizations to PROFILE.FDL and PROFILE.DAT..................................... 10-7 10.10Execute the ALL-IN-1 STARTER Startup Command Procedure....................................... 10-7 10.10.1 After a New Installation ..................... 10-8 10.10.2 After an Upgrade Installation ................ 10-8 10.10.3 Site-Specific Startup Procedures ............. 10-9 10.10.4 How to Handle Errors Relating to Images Not Installed.................................... 10-11 10.11Compile and Install the TXLs.................... 10-12 10.12Compile and Install Your Form Libraries......... 10-13 10.13How to Set Up a Remote Message Router........... 10-14 10.14Setting Up the Message Router Transfer Service......................................... 10-15 10.14.1 Configuring the VMSmail Gateway .............. 10-16 10.15Diagnostic Tools................................ 10-16 10.16Set the Global Buffers.......................... 10-17 10.17Set the Terminal and Queue Characteristics for Printers........................................ 10-18 10.18Reschedule the ALL-IN-1 Housekeeping Procedures...................................... 10-18 10.19Mail Directory Setup............................ 10-18 10.20ALL-IN-1 STARTER Setup.......................... 10-21 10.21Convert WPS-PLUS/VMS Documents to ALL-IN-1 STARTER......................................... 10-22 viii 10.22DECpage Support................................. 10-24 10.23Determining and Reporting Problems.............. 10-26 A Files on the ALL-IN-1 STARTER V2.4 Distribution Media A.1 Magnetic Tape and TK50 Kits..................... A-1 A.2 Compact Disk Consolidated Software Distribution Kits............................................ A-2 A.3 List of Files in Each Saveset................... A-4 B Sample Installations B.1 Sample of a New Installation.................... B-1 B.2 Sample of an Upgrade Installation from ALL-IN-1 STARTER Version 1.0............................. B-24 B.3 Sample of an ALL-IN-1 STARTER Version 2.4 Update Installation.................................... B-47 B.4 Additional Language Installation................ B-69 C Files and Logical Names Installed on Your System C.1 Files Installed in Non-ALL-IN-1 STARTER Directories..................................... C-1 C.2 Logical Names................................... C-2 C.2.1 Logical Names Entered into the System Logical Name Table................................... C-2 C.2.2 Logical Names Entered into the Language Logical Name Table........................... C-4 C.3 Directory Structure of an ALL-IN-1 STARTER System Installed on Separate Disks.............. C-5 ix D Changing the Configuration of ALL-IN-1 STARTER V2.4 D.1 Change to Using WPS-PLUS........................ D-1 D.2 Change the Location of an ALL-IN-1 STARTER Version 2.4 Area................................ D-2 D.3 Moving ALL-IN-1 STARTER......................... D-3 Index Figures C-1 Directory Structure of the ALL-IN-1 STARTER Manager's Account............................... C-6 C-2 Directory Structure for the Library Files....... C-7 C-3 Directory Structure for the Language Files...... C-8 C-4 Directory Structure for the Data Files.......... C-9 C-5 Directory Structure for Mail Area E............. C-9 C-6 Directory Structure for the Shared Directories..................................... C-9 Tables 1-1 Section Reference Chart......................... 1-3 1-2 VMS Tailoring Classes........................... 1-7 1-3 Actions to Complete Before Installing ALL-IN-1........................................ 1-25 1-4 Required System Parameter Values................ 1-36 1-5 Process Account Quotas for the Installing Account......................................... 1-38 1-6 Disk Space Requirements for the ALL-IN-1 Areas........................................... 1-43 3-1 Steps Required to Install a New ALL-IN-1 Version 2.4 System...................................... 3-4 x 4-1 Steps Required for an ALL-IN-1 V2.4 Language Installation.................................... 4-4 5-1 Steps Required to Upgrade your ALL-IN-1 STARTER V1.0 System to ALL-IN-1 STARTER V2.4............ 5-4 6-1 Steps Required for Upgrading an ALL-IN-1 STARTER V1.0 Language................................... 6-4 7-1 Steps Required for Updating an Existing ALL-IN-1 STARTER V2.4 System............................. 7-4 8-1 Steps Required for Updating an Existing ALL-IN-1 STARTER V2.4 Language........................... 8-4 10-1 Section Reference Chart......................... 10-2 10-2 Global Buffer Allocations....................... 10-17 xi ________________________________________________________________ Preface Product: ALL-IN-1 STARTER Version 2.4 Purpose of This Guide This guide is Part 1 of three parts. See the section on Document Structure. This part describes how to: 1 Prepare the VMS system for the installation of ALL-IN-1 STARTER 2 Install ALL-IN-1 STARTER 3 Set up ALL-IN-1 STARTER so that the manager can log in to ALL-IN-1 STARTER and use ALL-IN-1 STARTER locally All other tasks required to complete the set up of ALL-IN-1 STARTER, and for ongoing management, are described in the ALL-IN-1 Management Guide and ALL-IN-1 Mail Management Guide, for example: o Printer set up o Creating accounts xiv o Setting up Message Router and Message Router VMSmail Gateway, if mail messages need to be sent to other systems or VMS users Audience This guide is primarily intended for: o Managers who want to install ALL-IN-1 STARTER Version 2.4 and set it up for use o Managers who want to upgrade to ALL-IN-1 STARTER Version 2.4 from ALL-IN-1 STARTER Version 1.0 o Managers who want to update their existing ALL-IN-1 STARTER Version 2.4 system How To Use This Guide Use this guide as follows: 1 Carry out the steps described in Chapter 2 to access the Release Notes. You must print and read the Release Notes before starting the installation as they may contain information which applies to installation. 2 Read Chapter 1 which describes the tasks you must do before installing ALL-IN-1 STARTER. 3 Read the chapter corresponding to the type of installation you are going to perform, (see Chapters 3 to 8). The chapter lists the steps required to perform the installation. 4 Carry out the steps required for the type of installation you are going to perform. These steps are described in Chapter 9. xv 5 Read Chapter 10 which describes the tasks required to set up ALL-IN-1 STARTER so that the usual management and mail management tasks can be performed (for example, creating user accounts) to allow your users to use ALL-IN-1 STARTER. Books in the Management Documentation Set The following documents make up the ALL-IN-1 STARTER Management documentation set: o ALL-IN-1 STARTER Installation Guide Part 1 Base Installation This part describes the steps required to install ALL-IN-1 STARTER and contains information specific to the base component. Although it is a large book, you need only refer to the chapters relating to the type of installation that you are going to perform. o ALL-IN-1 STARTER Installation Guide Part 2 Language Installation This part contains information specific to the language that you are installing; a version is supplied with each language component. Refer to this part as indicated in the ALL-IN-1 STARTER Installation Guide Part 1 Base Installation. o ALL-IN-1 STARTER Installation Guide Part 3 Market Installation This part contains information specific to your market component. Refer to this part as indicated in the ALL-IN-1 STARTER Installation Guide Part 1 Base Installation. Note that this document may not exist for all market components. o ALL-IN-1 STARTER Release Notes Part 1 Language xvi This part contains information about problems in the ALL-IN-1 STARTER Version 2.4 international base component and about problems that are specific to the language component that you install. Where possible, workarounds to the problems are also described. o ALL-IN-1 STARTER Release Notes Part 2 Market This part contains information about problems that are specific to the ALL-IN-1 STARTER Version 2.4 market component. Note that this document may not exist for all market components. o Differences Between ALL-IN-1 Version 2.3 and ALL-IN-1 Version 2.4 This document introduces the new and changed function- ality, and describes the problems that have been fixed, in ALL-IN-1 STARTER Version 2.4. In addition, there are answers to some common questions about the new version, and details of packaging, software requirements, and changes to the documentation. This document contains some information that is not relevant for ALL-IN-1 STARTER Version 2.4 (see the ALL-IN-1 STARTER Release Notes for details). o ALL-IN-1 Management Guide This guide describes the tasks for setting up and managing an ALL-IN-1 system, so that it operates efficiently. The guide also explains how to improve performance, and how the ALL-IN-1 files are organized within VMS. This document contains some information that is not relevant for ALL-IN-1 STARTER Version 2.4 (see the ALL-IN-1 STARTER Release Notes for details). o ALL-IN-1 Mail Management Guide This guide describes how to manage an ALL-IN-1 mail system. The major management concern is to ensure that all messages sent to and from local ALL-IN-1 users are delivered. xvii This document contains some information that is not relevant for ALL-IN-1 STARTER Version 2.4 (see the ALL-IN-1 STARTER Release Notes for details). o ALL-IN-1 Administration Guide This guide describes the ALL-IN-1 administration tasks, which include maintaining ALL-IN-1 on a day-to-day basis and supporting users. The administration tasks are defined by the ALL-IN-1 manager, and are available from the Administration menu. This document contains some information that is not relevant for ALL-IN-1 STARTER Version 2.4 (see the ALL-IN-1 STARTER Release Notes for details). Related Books In addition to the ALL-IN-1 STARTER Management documentation set, your ALL-IN-1 STARTER kit contains a user documentation set. The user documentation set contains: ALL-IN-1 STARTER Getting Started ALL-IN-1 STARTER Quick Lookup ALL-IN-1 STARTER User's Reference ALL-IN-1 STARTER User Changes ALL-IN-1 Keyboard Reference Cards ALL-IN-1 Keyboard Diagram Cards WPS-PLUS Quick Lookup WPS-PLUS Editor Functions WPS-PLUS List and Sort Processing You may also need to refer to the documentation on the following products: o VAX FMS Version 2.4 o VAX Message Router Version 3.1B o CDA Converter Library Version 1.0 xviii o VAX DECpage Version 3.1 o DECdx/VMS Version 1.2 You may need to refer to the VMS management books for the version of VMS running on your system. xix Document Structure ALL-IN-1 STARTER Installation Guide Part 1 Base Installation This part describes the installation of ALL-IN-1 STARTER Version 2.4. Chapter 1 Preparing to Install ALL-IN-1 STARTER V2.4 This chapter describes the steps to complete before beginning the installation, including how to prepare the system if you want to integrate ALL-IN-1 STARTER with optional software products. Chapter 2 Accessing the Online Release Notes This chapter describes how to access and print the online Release Notes Chapter 3 Installing a New ALL-IN-1 STARTER V2.4 System This chapter describes the steps to perform to install a new ALL-IN-1 STARTER Version 2.4 system. xx Chapter 4 Installing Additional Languages for ALL-IN-1 STARTER V2.4 This chapter describes the steps to perform to install additional languages for ALL-IN-1 STARTER Version 2.4. Chapter 5 Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 This chapter describes the steps to perform to upgrade from ALL-IN-1 STARTER Version 1.0 to ALL-IN-1 STARTER Version 2.4. Chapter 6 Upgrading ALL-IN-1 STARTER V1.0 Additional Languages to ALL-IN-1 STARTER V2.4 Additional Languages This chapter describes the steps to perform to upgrade ALL-IN-1 STARTER Version 1.0 additional languages to ALL-IN-1 STARTER Version 2.4 additional languages. xxi Chapter 7 Updating an Existing ALL-IN-1 STARTER V2.4 System This chapter describes the steps to perform to update your existing ALL-IN-1 STARTER Version 2.4 system. You can update your ALL-IN-1 STARTER Version 2.4 system if you decide to change the configuration, or an ALL-IN-1 STARTER component is revised by Digital. Chapter 8 Updating an ALL-IN-1 STARTER V2.4 Language This chapter describes the steps to perform to update ALL-IN-1 STARTER Version 2.4 additional language. Chapter 9 Steps Required for Installing ALL-IN-1 STARTER V2.4 This chapter contains a complete list of the steps required for installing ALL-IN-1 STARTER Version 2.4. Chapter 10 After Installing ALL-IN-1 STARTER V2.4 This chapter describes the tasks to complete so that ALL-IN-1 STARTER can be run by users. Appendix A Files on the ALL-IN-1 STARTER V2.4 Distribution Media This appendix lists the files contained on the distribution media. Appendix B Sample Installation xxii This appendix contains computer listings of a new ALL-IN-1 STARTER Version 2.4 installation, an upgrade installation from ALL-IN-1 STARTER Version 1.0, and an additional language installation. Appendix C Files and Logical Names Installed on Your System This appendix lists the directories, and the files in each directory, of an installed ALL-IN-1 STARTER Version 2.4 system. Appendix D Changing the Configuration of ALL-IN-1 STARTER V2.4 This appendix describes how to change the configuration of an installed ALL-IN-1 STARTER Version 2.4 system. ALL-IN-1 STARTER Installation Guide Part 2 Language Installation This part contains language-specific information, for the language you are installing. There is a version of this part for each language supported by ALL-IN-1 STARTER Version 2.4. Your ALL-IN-1 STARTER Version 2.4 kit contains a version of this part for each language included with the kit. ALL-IN-1 STARTER Installation Guide Part 3 Market Installation This part contains market-specific information, where a market may be specific to a single country. Your ALL-IN-1 STARTER Version 2.4 kit contains the version specific to your market. xxiii Conventions The following conventions are used throughout this document: Messages Indicates prompts and messages from the computer. Red Print Indicates entries you make at the terminal. lowercase Lowercase text in an ALL-IN-1 STARTER function call, or in a DCL command or command procedure, indicates that you substitute a valid expression in that place. [] Brackets in an ALL-IN-1 STARTER function, or in a DCL command or command procedure, indicate an optional entry, or a DCL directory specification. . . . Horizontal ellipses indicate that additional data or text can be entered. . Vertical ellipses indicate that the example can . or does contain more data or text than is shown. . 1 Marks the order of the steps to complete a 2 procedure. 3 a. Marks steps within a major step in a procedure. b. c. Press Indicates that you make one keystroke with an editing or command key. For example, press RETURN. xxiv Enter Means type a command or response, or type information into a menu or form, and then press a terminator key such as RETURN. UPPERCASE Indicates keyboard keys and GOLD functions. < > Indicates a display that is variable. CTRL/z Indicates that you hold down the CTRL key while pressing the other key (z). GOLD x Means press the GOLD key, labeled PF1 on some keyboards, then press the key for the function. For example, GOLD TOP. STEP n Indicates step n of the ALL-IN-1 STARTER installation procedure. step n Indicates step n of a pre-installation or post- installation task. ALL-IN-1 Means ALL-IN-1[TM] STARTER office automation system DECnet Means DECnet[TM] software Message Means Message Router[TM] software Router WPS-PLUS Means WPS-PLUS[TM] software xxv 1 ________________________________________________________________ Preparing to Install ALL-IN-1 STARTER V2.4 You install ALL-IN-1 STARTER Version 2.4 using VMSINSTAL, from the SYSTEM account. VMSINSTAL is a command procedure used to install optional software products on the VMS operating system. o You can install ALL-IN-1 STARTER Version 2.4 if you are not currently running ALL-IN-1 STARTER, or you can upgrade your ALL-IN-1 STARTER Version 1.0 system to ALL-IN-1 STARTER Version 2.4. You must also upgrade your additional languages to the corresponding ALL-IN-1 STARTER Version 2.4 languages. o You can also install additional languages, or update the language(s) currently being used by your ALL-IN-1 STARTER Version 2.4 system. o If you decide to change the configuration of your existing ALL-IN-1 STARTER Version 2.4 system, or an ALL-IN-1 STARTER component is revised by Digital, you can update your ALL-IN-1 STARTER Version 2.4 system. o If you are currently using WPS-PLUS/VMS, and you do not have a previous version of ALL-IN-1 STARTER, you can install ALL-IN-1 STARTER Version 2.4 and optionally Preparing to Install ALL-IN-1 STARTER V2.4 1-1 convert your WPS-PLUS/VMS users to ALL-IN-1 STARTER. See Section 10.21 for details. o For certain changes to your existing ALL-IN-1 STARTER Version 2.4 system you need not perform an update installation (for example, if you want to reconfigure ALL-IN-1 STARTER to use WPS-PLUS). These changes are described in Appendix D. To prepare for installation: 1 Check that the distribution kit is complete and correct according to the bill of materials included with the kit. See Section 1.1. 2 Make sure that your system has the prerequisite software. See Section 1.4. 3 Determine what other products you need to install before installing ALL-IN-1 STARTER. See Section 1.5. 4 If you are intending to install ALL-IN-1 STARTER on a VAXcluster, see Section 1.6. 5 If you are intending to install additional languages, see Section 1.7. 6 Set up your system so that it is ready for the installa- tion. See Section 1.8. 7 Complete the checklist of information appropriate to the type of installation you are going to perform. See Section 1.8.18. 8 If you are unfamiliar with ALL-IN-1 STARTER, see the first chapter of the ALL-IN-1 STARTER User's Reference before starting installation. Table 1-1 indicates the sections that you need to refer to in this chapter for the type of installation that you are going to perform. 1-2 Preparing to Install ALL-IN-1 STARTER V2.4 Table 1-1 Section Reference Chart _____________________________________________________________ Installation Sections Type ____________________________________________ _________________1.1__1.2__1.3__1.4__1.5__1.6__1.7__1.8______ New ALL-IN-1 * * * * * * * V2.4 installa- tion New additional * * * * * * * language installation Upgrade from * * * * * * * ALL-IN-1 V2.3 Upgrade of an * * * * * * * ALL-IN-1 V2.3 language Upgrade from * * * * * * * ALL-IN-1 STARTER V1.0 Upgrade of * * * * * * * an ALL-IN-1 STARTER V1.0 language Update from * * * * * * * ALL-IN-1 STARTER V2.4 Update of * * * * * * * an ALL-IN-1 STARTER V2.4 language Update of * * * * * * * ALL-IN-1 V2.4 _____________________________________________________________ * Indicates that you need to refer to this section (continued on next page) Preparing to Install ALL-IN-1 STARTER V2.4 1-3 Table 1-1 (Cont.) Section Reference Chart _____________________________________________________________ Installation Sections Type ____________________________________________ _________________1.1__1.2__1.3__1.4__1.5__1.6__1.7__1.8______ Update of an * * * * * * * additional language _____________________________________________________________ * Indicates that you need to refer to this section _____________________________________________________________ 1.1 Examining the Distribution Kit To make sure that you have a complete kit, check the contents of the kit against the bill of materials. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. 1.1.1 Magnetic Tape and TK50 Kits All full ALL-IN-1 STARTER Version 2.4 kits (that is, as opposed to an additional language kit) should contain: o Three magnetic tapes or TK50 cartridges containing all the files listed in Appendix A of this book, the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation and the ALL-IN-1 STARTER Installation Guide Part 3 Market Installation. The VAX FMS Version 2.4 software is also contained on the tape or TK50 cartridge labeled: ALL-IN-1 STARTER V2.4 BASE BIN media_type INTERNATIONAL BASE (c) 1990 Digital Equipment Corp. media_type is 16MT9 for tape or TK50 for a TK50 cartridge. o One magnetic tape or TK50 cartridge containing the Message Router VMSmail Gateway Version 3.1 kit. The kit contains Message Router Version 3.1B and Message Router VMSmail Gateway Version 3.1. o One magnetic tape or TK50 cartridge containing the Release Notes Part 1 Language, for the language component supplied with your kit. 1-4 Preparing to Install ALL-IN-1 STARTER V2.4 o One magnetic tape or TK50 cartridge containing the Release Notes Part 2 Market, for the market component supplied with your kit. (This document may not exist for all market components.) o A Software Product Description (SPD). o A System Support Addendum (SSA). o The ALL-IN-1 STARTER Installation Guide Part 1 Base Installation (this book) o The ALL-IN-1 STARTER Installation Guide Part 2 Language Installation, for the language component supplied with your kit. o The ALL-IN-1 STARTER Installation Guide Part 3 Market Installation, for the market component supplied with your kit. If you are installing an additional language you should have: o A magnetic tape or TK50 cartridge containing the files for the language that you are installing (see Appendix A of the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation) o A magnetic tape or TK50 cartridge containing the Release Notes Part 1 Language, for the additional language o The ALL-IN-1 STARTER Installation Guide Part 2 Language Installation, for the additional language 1.1.2 Compact Disk Consolidated Software Distribution Kits All full ALL-IN-1 STARTER Version 2.4 kits (that is, as opposed to an additional language kit) should contain one compact disk (CD) containing all the files listed in Appendix A of this book. The CD also contains the following products in the same directory as the ALL-IN-1 STARTER kit: _ VAX FMS Version 2.4 _ Message Router VMSmail Gateway Version 3.1 which contains Message Router Version 3.1B and Message Router VMSmail Gateway Version 3.1. _ CDA Patch Kit for VMS Version 5.3. This kit is required only for systems running CDA with VMS Version 5.3. Preparing to Install ALL-IN-1 STARTER V2.4 1-5 _ CDA Converter Library Version 1.0 The following documentation (in ASCII text format) is also included on the CD: o A Read Me First o The ALL-IN-1 STARTER Installation Guide Part 1 Base Installation (this book) o The ALL-IN-1 STARTER Installation Guide Part 2 Language Installation, for the language component supplied with your kit. o The ALL-IN-1 STARTER Installation Guide Part 3 Market Installation, for the market component supplied with your kit. o A Software Product Description (SPD) o A System Support Addendum (SSA) o A Software Warranty Addendum (SWA) If you are installing an additional language, you should have a CD containing the files for the language that you are installing (see Appendix A of the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation). The CD also includes (in ASCII text format): o The ALL-IN-1 STARTER Installation Guide Part 2 Language Installation, for the additional language 1.2 VMS License Management Facility The VMS License Management Facility (LMF) is available with Version 5.1, or higher, of the VMS operating system. If you are installing ALL-IN-1 STARTER Version 2.4 on a VMS V5.1 (or higher) system, you must register your software license. The license registration information you need is contained in the Product Authorization Key (PAK) that comes with ALL-IN-1 STARTER Version 2.4. The PAK is a paper certificate that contains information about the license you must have in order to run a particular piece of software. 1-6 Preparing to Install ALL-IN-1 STARTER V2.4 You must register your ALL-IN-1 STARTER Version 2.4 license before you perform the installation. During the installation, you are asked if you have registered the ALL-IN-1 STARTER Version 2.4 license and loaded the appropriate authorization key. To register a license under VMS V5.1, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your Product Authorization Key (PAK). o Issue the DCL command, LICENSE REGISTER, together with the appropriate qualifiers that correspond to information on the PAK. For complete information on using LMF, see the manual on the License Management Utility in the VMS V5.1 documentation set. 1.3 Required Operating System Components For VMS Version 5.1, or higher, systems, ALL-IN-1 STARTER Version 2.4 requires that your system is running the VMS classes listed in Table 1-2. Table 1-2 VMS Tailoring Classes _____________________________________________________________ Class_________________Required_File(s)_______________________ Network Support NMLSHR.EXE Programming Support IMAGELIB.OLB System Programming SYS.STB Secure User's SUBMIT.EXE Environment Utilities RUNOFF.EXE RMS Journaling File None (continued on next page) Preparing to Install ALL-IN-1 STARTER V2.4 1-7 Table 1-2 (Cont.) VMS Tailoring Classes _____________________________________________________________ Class_________________Required_File(s)_______________________ VMS Workstation None Support Miscellaneous Files None BLISS Required Files STARLET.REQ Example Files None User Environment None Test_Package_________________________________________________ 1.4 Prerequisite Software The following software must be installed on your system: o VMS Version 5.1, or higher o VAX Forms Management System (FMS) Version 2.4. Note ALL-IN-1 STARTER must have the form driver (FDVSHR) installed as a known shareable image. See Section 1.4.1. See the VAX FMS Installation Guide and Release Notes for details of installing VAX FMS. (If you want to run the sample programs supplied with VAX FMS you must have at least one compiler installed on your system.) Digital does not recommend the use of any earlier version of FMS with ALL-IN-1 STARTER Version 2.4. If you install VAX FMS from the kit supplied with ALL-IN-1 STARTER Version 2.4, you must register the license before you can run FMS. FMS must be running before you install ALL-IN-1 STARTER. 1-8 Preparing to Install ALL-IN-1 STARTER V2.4 1.4.1 Installed Images Make sure that the following shareable image and message files are installed on your system before installing ALL-IN-1 STARTER: o SYS$MESSAGE:FDVMSG.EXE o SYS$SHARE:CONVSHR.EXE o SYS$SHARE:FDLSHR.EXE o SYS$SHARE:FDVSHR.EXE o SYS$SHARE:LBRSHR.EXE o SYS$SHARE:MTHRTL.EXE For a MicroVAX II, or a MicroVAX 2000, the file is SYS$SHARE:UVMTHRTL.EXE o SYS$SHARE:NMLSHR.EXE o SYS$SHARE:PASRTL.EXE o SYS$SHARE:SCNRTL.EXE o SYS$SHARE:SCRSHR.EXE o SYS$SHARE:VMSRTL.EXE o SYS$SHARE:VAXCRTL.EXE To check whether or not these images are installed on your system, enter the following: $ INSTALL INSTALL> LIST image image is the image to be checked. For example, SYS$SHARE:CONVSHR. If the Install Utility cannot find an entry for an image, install the image as follows: INSTALL> CREATE image /OPEN /SHARED /HEADER_RES INSTALL> EXIT Note If the images FDVMSG.EXE and FDVSHR.EXE are not installed, edit the command procedure SYS$STARTUP:FMSTARTUP.COM, remove the EXIT command before the entry RUN SYS$SYSTEM:INSTALL, and then execute the command procedure. Preparing to Install ALL-IN-1 STARTER V2.4 1-9 If there is an entry for the image, check that the display shows the following information: imagename.EXE Open Hdr Shar imagename is the name of the image. For example, CONVSHR. If the display does not show this information, change the way that the image is installed as follows: INSTALL> REPLACE image /OPEN /SHARED /HEADER_RES INSTALL> EXIT For details of installing shareable image files, see the VMS manual describing the Install Utility. Note that the following images are temporarily installed during the installation of ALL-IN-1 STARTER: o If you integrated WPS-PLUS: - SYS$SHARE:LNGSPLCOM.EXE - SYS$SHARE:LNGOSENVR.EXE - SYS$SHARE:LNGSPLMSG.EXE - SYS$SHARE:LNGSPLlang.EXE, for all languages with DECspell support (see the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation) - SYS$SHARE:LNGSPLSHR.EXE o If standalone DECspell is installed on your system: - SYS$SYSTEM:LNGSPLCOR.EXE - SYS$SYSTEM:LNGSPLNDX.EXE - SYS$SYSTEM:LNGSPLFOR.EXE The ALL-IN-1 STARTER startup command procedure A1V24START.COM installs all these as known images at system startup. This command procedure is in SYS$MANAGER. 1-10 Preparing to Install ALL-IN-1 STARTER V2.4 1.5 Optional Software Products Message Router Version 3.1B is supplied with ALL-IN-1 STARTER Version 2.4 (see Section 1.5.2). If you want to use Mail directory addressing you must install Message Router Version 3.1B on the same node as ALL-IN-1 STARTER. Digital does not recommend the use of any earlier version of Message Router with ALL-IN-1 STARTER Version 2.4. Message Router VMSmail Gateway (MRGATE) Version 3.1 is sup- plied with ALL-IN-1 STARTER Version 2.4 (see Section 1.5.2). If you want to install Message Router on the same node as ALL-IN-1 STARTER, Digital does not recommend the use of any earlier version of MRGATE with ALL-IN-1 STARTER Version 2.4. Note If you install Message Router and Message Router VMSmail Gateway from the kit supplied with ALL-IN-1 STARTER Version 2.4, you must register the licenses for both products before you can run them. Message Router and, if installed, Message Router VMSmail Gateway must be running before you install ALL-IN-1 STARTER. If you want to use any of these products with ALL-IN-1 STARTER, see the order of installation listed in Section 1.5.4. In addition, the following products can be integrated with ALL-IN-1 STARTER: o VAX DECpage Version 3.1 DECpage is an ALL-IN-1 STARTER option that you install separately. When VAX DECpage Version 3.1 is installed after ALL-IN-1 STARTER, it is accessible from the Word and Document Processing (WP) menu within ALL-IN-1 STARTER. It is not necessary to link the VAX DECpage software to ALL-IN-1 STARTER. If you want to integrate DECpage with ALL-IN-1 STARTER, there is a post-installation task you must perform after you have installed ALL-IN-1 STARTER Version 2.4 (see Section 10.22). o Language and Specialized Lexicons. See the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation for the language and specialized lexicons supported. (The language and specialized lexicons are only available for certain languages.) o DECdx/VMS Version 1.2 Preparing to Install ALL-IN-1 STARTER V2.4 1-11 DECdx/VMS is required only to allow users to transfer DX documents between Digital's mainframe computers (in conjunction with DECdx/RSTS, DECdx/RSX and DECdx/TOPS-20) DECnet/VAX Version 5.1 can be purchased separately. If you want to exchange mail with other systems you must install DECnet/VAX Version 5.1 on your system. If you are upgrading to ALL-IN-1 STARTER Version 2.4, and you are currently running any ALL-IN-1 STARTER layered products, you may need to prepare the layered product(s) before you install ALL-IN-1 STARTER Version 2.4 (see your layered product documentation). 1-12 Preparing to Install ALL-IN-1 STARTER V2.4 1.5.1 Initial CDA Support ALL-IN-1 STARTER provides users with the ability to manipulate CDA documents, for example, documents produced by DECwrite. You can: o Send or forward CDA documents by mail as attachments between ALL-IN-1 STARTER users on the same or remote nodes o You can store the CDA documents directly in the ALL-IN-1 STARTER File Cabinet and read them (display on the screen) using the Word and document processing Read (WP R) option. When in the ALL-IN-1 STARTER File Cabinet you can manipulate the CDA documents using any of the File Cabinet (FC) functions such as Delete and Archive. o Edit CDA documents by using either the EDT or WPS-PLUS editors o Print CDA documents either on PostScript capable printers or on ASCII printers Export CDA documents from the ALL-IN-1 STARTER File Cabinet to VMS where they reside as VMS files o Convert CDA documents to ASCII, DX, WPS-PLUS, or Alternate Format Syntax (AFS) o Create CDA documents by converting documents in ASCII, DX, WPS-PLUS, or AFS to CDA The following software must be installed, before you can use CDA with ALL-IN-1 STARTER. o DECwindows Version 1.0, or higher Note You must have both the DECwindows base kit and the DECwindows application files are installed on your system. o CDA Patch Kit for VMS Version 5.3. This kit is required only for systems running CDA with VMS Version 5.3. If your system is running VMS Version 5.3, you must install this kit before installing the CDA Converter Library o CDA Converter Library Version 1.0 The installation checks to see if the following files are present: - OA$SHARE:DDIF$READ_DX.EXE Preparing to Install ALL-IN-1 STARTER V2.4 1-13 - OA$SHARE:DDIF$WRITE_DX.EXE - OA$SHARE:DTIF$READ_ASCII_TABULAR.EXE - OA$SHARE:DTIF$WRITE_ASCII_TABULAR.EXE The files for CDA support are installed during the instal- lation of ALL-IN-1 STARTER Version 2.4. However, your users will be unable to convert CDA documents to ALL-IN-1 documents until the prerequisite software is installed. 1.5.2 Integrating Message Router and the Message Router VMSmail Gateway with ALL-IN-1 STARTER The ALL-IN-1 STARTER installation procedure asks if you want to send and receive remote mail. o Install and configure Message Router before you install ALL-IN-1 STARTER, if you want to send and receive remote mail o Install and configure Message Router and the Message Router VMSmail Gateway before you install ALL-IN-1 STARTER, if you want to send mail to VMSmail users, either on the local system or remotely o If you want to install Message Router on the local system (that is, the system on which you are installing ALL-IN-1 STARTER) then you must install Message Router Version 3.1B. The Message Router on the local system is referred to as a local Message Router. Both Message Router Version 3.1B and the Message Router VMSmail Gateway Version 3.1 are provided in the ALL-IN-1 STARTER kit. o If you want to use the Message Router Directory Service (referred to as the Mail directory), you must install Message Router Version 3.1B on the local system before you install ALL-IN-1 STARTER. o If you already have Message Router Version 3.1B installed on your system, make sure that it is configured before you install ALL-IN-1 STARTER Version 2.4. o If ALL-IN-1 STARTER Version 2.4 is already installed, and you want to install Message Router on the local system, you must install and configure Message Router Version 3.1B and then perform an update installation of ALL-IN-1 STARTER Version 2.4. 1-14 Preparing to Install ALL-IN-1 STARTER V2.4 You can also integrate ALL-IN-1 STARTER with Message Router on a remote system (that is, a system other than the one on which you are installing ALL-IN-1 STARTER). See Section 10.13 for more information. You may want to do this if you do not have enough space on your own system to install Message Router. However, the Mail directory is not available when Message Router is remote, so you cannot use Mail directory addressing (see Section 1.5.2.1). The Message Router on the remote system is referred to as a remote Message Router. When you install Message Router the exception reporting routines for the ALL-IN-1 STARTER Electronic Messaging subsystem are installed. If you want to run the exception reporting routines, you must configure exception reporting for the ALL-IN-1 STARTER Electronic Messaging subsystem. See Section 1.6 for information on using ALL-IN-1 STARTER and Message Router on VAXcluster systems. For more information on installing and using Message Router and Message Router VMSmail Gateway, refer to the Message Router and Message Router VMSmail Gateway books, and the ALL-IN-1 Mail Management Guide. Before you install ALL-IN-1 STARTER, read the chapter on planning in the ALL-IN-1 Mail Management Guide, to decide how to set up the mail system. 1.5.2.1 The Mail Directory and the ALL-IN-1 Directory The Mail directory and the ALL-IN-1 directory are directories of users in the network. These directories hold the names and electronic mail addresses of users in the network. The Mail directory is provided by the Directory Service component of Message Router. Before deciding whether or not to use the Mail directory, see the Planning chapter in the ALL-IN-1 Mail Management Guide. 1.5.3 Integrating WPS-PLUS with ALL-IN-1 STARTER You can integrate WPS-PLUS Version 3.1 when you install ALL-IN-1 STARTER. An installation question asks whether you want to integrate WPS-PLUS. If you choose to integrate WPS-PLUS it is fully integrated with ALL-IN-1 STARTER and is available as the default editor. You do not need additional software to integrate WPS-PLUS, as everything required is provided in the ALL-IN-1 STARTER kit. After installation there are a number of tasks you must perform Preparing to Install ALL-IN-1 STARTER V2.4 1-15 before users can use WPS-PLUS, for example, setting terminal and queue characteristics (see Section 10.17 and the ALL-IN-1 Management Guide for details). If WPS-PLUS/VMS already exists on your system, you can still integrate and use WPS-PLUS with ALL-IN-1 STARTER (see Section 10.21 for details). If you integrate WPS-PLUS with ALL-IN-1 STARTER, you may be able to use various spell-checking lexicons. See the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation for the spell-checking lexicon that is supplied with your kit, and for any other optional products. Note Lexicons are only available for certain language versions of ALL-IN-1 STARTER Version 2.4. 1.5.4 Installation Order The following installation order is recommended: 1 Register the ALL-IN-1 STARTER Version 2.4 license. 2 Run the ALL-IN-1 STARTER installation procedure, and select option 7 to register the licenses for VAX FMS Version 2.4, Message Router Version 3.1B, Message Router VMSmail Gateway Version 3.1 and CDA Converter Library Version 1.0. 3 Install VAX FMS Version 2.4, if it is not already installed on your system. 4 Install Message Router Version 3.1B (unless it is already installed on your system), if you want to send and receive messages to and from other systems, or you want to use Mail directory addressing, or you want to send mail to VMSmail users, either on the local system or on remote systems. 5 Configure Message Router Version 3.1B, if it is installed and not yet configured. Note: If you want to install Message Router VMSmail Gateway Version 3.1, after you have installed Message Router Version 3.1B, you can defer the configuration of Message Router and configure both products together at step 7. 1-16 Preparing to Install ALL-IN-1 STARTER V2.4 6 Install Message Router VMSmail Gateway Version 3.1 (unless it is already installed on your system), if you want to send mail to VMSmail users, either on the local system or remotely. 7 Configure Message Router VMSmail Gateway Version 3.1, if it is installed and not yet configured. 8 Install CDA Converter Library Version 1.0 (unless it is already installed on your system). 9 Install CDA Patch kit for VMS Version 5.3. See the ALL-IN-1 STARTER Read Me First. 10 Install ALL-IN-1 STARTER Version 2.4. 11 Configure exception reporting routines for ALL-IN-1 STARTER Version 2.4 Electronic Messaging subsystem. Note WPS-PLUS is supplied with ALL-IN-1 STARTER. If you choose to integrate WPS-PLUS with ALL-IN-1 STARTER, it is available as the default editor in ALL-IN-1 STARTER. 1.5.5 Keeping a Record of the Installation When you install ALL-IN-1 STARTER Version 2.4, Digital recommends that you use a hard-copy terminal, so that you have a permanent record of the installation. Alternatively, you can keep a record of the installation in a log file if you enter the command: $ SET HOST /LOG=filename 0 where filename is the name of the log file. For example, you might use ALLIN1_INSTALL.LOG. The default is SETHOST.LOG, if filename is omitted. The log file is created in the directory where you entered the command. For example, if you enter the command in the directory SYS$SYSDEVICE:[SYSTEM.FRED] then this directory will contain the log file. To use the SET HOST command, DECnet must be running on your system. Make a note of the directory where you entered the SET HOST command. If you decide to keep a record of the installation in a log file, you need to allow at least 200 blocks, in addition to the space required for ALL-IN-1 STARTER (see Section 1.8.16). Preparing to Install ALL-IN-1 STARTER V2.4 1-17 If you have a VAXcluster system, and you are running the VAXcluster Console System (VCS), you can use this to record the installation of ALL-IN-1 STARTER Version 2.4. This does not require DECnet to be running, does not use any disk space on the system where the installation is performed, and does not echo any passwords that you enter during the installation. See the manual for the VAXcluster Console System. 1.6 Installing ALL-IN-1 STARTER on VAXcluster Systems ALL-IN-1 STARTER Version 2.4 can be installed on a common-environment cluster, a multiple-environment cluster or Local Area VAXcluster. 1.6.1 Installing ALL-IN-1 STARTER on a Common-Environment Cluster In a common-environment cluster, the operating environment is identical on each member node, because the nodes are run from the same system files. The nodes are set up with identical user accounts, the same known images (such as the ALL-IN-1 STARTER image) are installed, the same logical names are defined, and mass storage devices and queues are shared. In effect, users in a common-environment cluster can log in to any node and work in the same operating environment. For example, ALL-IN-1 STARTER will be installed on one node only, but will be available to users on all nodes. 1.6.1.1 Running ALL-IN-1 STARTER on a Common-Environment Cluster When running ALL-IN-1 STARTER on a common-environment cluster: o You must run the ALL-IN-1 STARTER startup command procedure, SYS$MANAGER:A1V24START.COM, on all nodes in the cluster on which you want to run ALL-IN-1 STARTER. (See Section 10.10 of this guide.) Note ALL-IN-1 STARTER Version 2.4 does not support rolling upgrades; that is, mixed VMS Version 4.7 and Version 5.0 clusters. All nodes in the cluster must be running VMS Version 5.1, or higher, before you install ALL-IN-1 STARTER Version 2.4. 1-18 Preparing to Install ALL-IN-1 STARTER V2.4 o You can spread the ALL-IN-1 STARTER areas around your VAXcluster disks, just as you would for a single-node system (see Section 1.8.16). o You must check the VMS system parameters, as described in Section 1.8, on each node in the VAXcluster on which you are going to run ALL-IN-1 STARTER. o The housekeeping procedure which creates new shared directories has to define new system logical names on each node in a VAXcluster. You must ensure that the new names are defined on every node in the cluster for which the new shared directories will be created. Use the Manage node specific batch queues (MNQ) option on the Manage Mail Areas menu to do this. See the ALL-IN-1 Management Guide for details. o The default value of the logical name OA$PRIMARY_NODE is set by A1V24START.COM after the installation has completed, as follows: - If you are using a remote Message Router, OA$PRIMARY_NODE is set to the name of the node on which the Message Router is resident. - If you are installing ALL-IN-1 STARTER on a VAXcluster, and cluster aliasing is enabled, OA$PRIMARY_NODE is set to the cluster alias. - If you are using a local Message Router and cluster aliasing is not enabled, OA$PRIMARY_NODE is the name of the node on which the Message Router is resident. The node name represented by this logical name is used in ALL-IN-1 directory addressing as the node name for all users on the cluster. It is also used by Electronic Messaging in the return address for all mail sent to other computer systems via Message Router. For further information about clusters, see the VMS VAXcluster documentation. Preparing to Install ALL-IN-1 STARTER V2.4 1-19 1.6.2 Installing ALL-IN-1 STARTER on a Multiple-Environment Cluster In a multiple-environment cluster, the environment varies from node to node, and users can work in environments that are specific to the node that they are logged in to. A multiple-environment cluster is effective when you want to share data among member nodes, but when you want certain nodes to serve specialized needs. A multiple-environment cluster can be considered as having different parts, each part providing a different environment. For example, you might want to set up a three-node cluster in which ALL-IN-1 STARTER can be used on two nodes, while the third node is set up exclusively for batch processing of large inventory jobs. In this case, the nodes from which ALL-IN-1 STARTER is available are set up with a common environment, sharing users, queues, and access to mass storage devices, while the the third node runs in its own restricted environment and ALL-IN-1 STARTER is unavailable. However, you must run the ALL-IN-1 STARTER startup command procedure, SYS$MANAGER:A1V24START.COM, on all the nodes in the part of the cluster with the common environment. Another configuration might have four nodes split into two parts (two nodes in each part), with both parts providing distinct common environments. If you want to run ALL-IN-1 STARTER on all four nodes, you must install ALL-IN-1 STARTER in each part. However, the ALL-IN-1 STARTER system on one part is available only to users logged in to that part of the cluster. The two ALL-IN-1 STARTER systems are managed separately. CAUTION If you are installing ALL-IN-1 STARTER Version 2.4 on one part of a multiple-environment cluster with a common system disk, and you want to install a full ALL-IN-1 Version 2.4 system on the another part of the cluster, you must do the following before installing ALL-IN-1 Version 2.4: 1 Copy the startup command procedure A1V24START.COM to the SYS$SPECIFIC:[SYSMGR] directory of each node in the part of the cluster running the ALL-IN-1 STARTER Version 2.4 system. 2 Delete the A1V24START.COM file in the SYS$COMMON:[SYSMGR] directory. 1-20 Preparing to Install ALL-IN-1 STARTER V2.4 After installing ALL-IN-1 Version 2.4 system, repeat these steps for the part of the cluster that is to run the new ALL-IN-1 system. 1.6.2.1 Running ALL-IN-1 STARTER on a Multiple-Environment Cluster When running ALL-IN-1 STARTER on a multiple-environment cluster: o You must check the VMS system parameters, as described in Section 1.8, on each node in the part of the cluster on which you are going to run ALL-IN-1 STARTER. o ALL-IN-1 STARTER is only available to users that are logged in to the part on which ALL-IN-1 STARTER is installed. If a part of the cluster does not have ALL-IN-1 STARTER installed, users logged in to a node in that part of the cluster cannot use ALL-IN-1 STARTER. Therefore, users (including batch jobs) of an ALL-IN-1 STARTER system must make sure that they are running on the part of the cluster containing the ALL-IN-1 STARTER system that they want to use. The ALL-IN-1 STARTER housekeeping procedures must be assigned to a batch queue. You must use a queue specific to the part of the cluster on which the ALL-IN-1 STARTER system is running. If your system has a cluster-wide generic queue which points to all queues in the cluster you must not use that queue. The housekeeping procedure which creates new shared directories has to define new system logical names on each node in a VAXcluster. You must ensure that the new names are defined on every node in the part of the cluster containing the ALL-IN-1 STARTER system for which the new shared directories will be created. Use the Manage node specific batch queues (MNQ) option on the Manage Mail Areas menu to do this. See the ALL-IN-1 Management Guide for details. o You must install Message Router, if you want to send and receive remote mail. If you want to use Mail directory addressing, you must install Message Router Version 3.1B on the same part of the cluster on which you are going to install the ALL-IN-1 STARTER system. In this case, Message Router is referred to as a local Message Router. Preparing to Install ALL-IN-1 STARTER V2.4 1-21 Note Mail directory addressing can only be used on certain multiple-environment cluster configurations. See the Message Router Installation Guide for details. You can use Message Router on another part of the cluster, or on another system, if you do not have enough disk space on the part that you are going to install ALL-IN-1 STARTER. In this case, Message Router is referred to as a remote Message Router. You cannot use Mail directory addressing with a remote Message Router. The main points to remember when running ALL-IN-1 STARTER in a multiple-environment cluster are: o Users must log in to the right part of the cluster to use ALL-IN-1 STARTER. o Batch queue names should be specific to the part of the cluster running ALL-IN-1 STARTER. o You must run A1V24START.COM on every node in the part of the cluster running ALL-IN-1 STARTER. This command procedure is in SYS$MANAGER. o To use the Mail directory, you must install Message Router Version 3.1B in the same part as ALL-IN-1 STARTER. However, the Mail directory can only be used on certain multiple-environment cluster configurations (see the Message Router Installation Guide for details). You can use a remote Message Router, but you cannot use the Mail directory. For further information about clusters, see the VMS VAXcluster documentation. 1.6.3 Installing ALL-IN-1 STARTER on a Local Area VAXcluster System You can install ALL-IN-1 STARTER Version 2.4 on a local area VAXcluster system. A local area VAXcluster system consists of a boot node (a VAX system or MicroVAX system containing all the disks from which ALL-IN-1 STARTER is run) connected by Ethernet to a number of satellite nodes, usually MicroVAX systems. If you are using a local area VAXcluster system, Digital recommends that you install ALL-IN-1 STARTER on the boot node. This node is likely to be the only node where disk space is available to run ALL-IN-1 STARTER. The satellite 1-22 Preparing to Install ALL-IN-1 STARTER V2.4 nodes are for the individual work groups only, and they use the boot node to access ALL-IN-1 STARTER files. You must check the VMS system parameters as described in Section 1.8, on each node in the local area VAXcluster system on which you are going to run ALL-IN-1 STARTER. Note If you intend to install ALL-IN-1 STARTER on a local area VAXcluster system, Digital recommends that you contact your local Software Services representative. 1.7 Installing Additional Languages Your basic ALL-IN-1 STARTER Version 2.4 kit is supplied with a specific language component for your market. You can use other languages with your ALL-IN-1 STARTER Version 2.4 system, in addition to the one supplied with your kit. If you want to install additional languages, you must have specified that you wanted to build a multi-language system when you installed the original language. See the System Support Addendum for a list of the languages supported by your ALL-IN-1 STARTER Version 2.4 system. If, during the installation of the original language, you answered NO to the prompt Do you want to build a multi-language system?, you must re-link ALL-IN-1 STARTER Version 2.4 and answer YES to this prompt. See the ALL-IN-1 Management Guide for details on linking the ALL-IN-1 STARTER image. You can install the languages (if available), including the one supplied with your kit, in any order. However, the language that you install when the main ALL-IN-1 STARTER Version 2.4 kit is installed is the default language. That is, it is the language indicated in the language field of the user's account details, and is used by ALL-IN-1 STARTER if you do not use the /LANGUAGE qualifier (see Section 10.10) when logging in to ALL-IN-1 STARTER. You install other laguages separately by performing an additional language installation (see Chapter 4). These languages are additional to the default language. See the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation of the language you want to install for: o The language name used for language-specific file, directory, and logical names. Preparing to Install ALL-IN-1 STARTER V2.4 1-23 o The size of the ALL-IN-1 STARTER Version 2.4 language component. You need this information to determine the disk space required for installing that language (see Section 1.8.16). 1.8 Preparing the System for Installation To prepare your system for the installation of ALL-IN-1 STARTER Version 2.4, carry out the steps listed in Table 1-3, and mark off each action as you complete it, before starting the installation. You must carry out these actions from a privileged SYSTEM account. Note o Digital recommends using logical names wherever possible. For example, assign logical names to your disks. The logical names must not start with A1$ or OA$. For example, you must not use A1$DEVICE. If your system uses logical names with prefixes A1$ or OA$, other than those defined by the ALL-IN-1 STARTER installation (see Appendix C), you must rename them. o ALL-IN-1 STARTER must not be used by any batch jobs or users during the installation, or the installation will fail. Therefore, you must remove the mail Sender and Fetcher from the batch queue if you are going to perform an upgrade installation. The values for the various system parameters and quotas given in Table 1-3 are those specific to ALL-IN-1 STARTER and are acceptable for most systems. The ALL-IN-1 Management Guide describes how to set system parameters for ALL-IN-1 STARTER. Also, see the VMS books for guidelines on the setting of system parameters. 1-24 Preparing to Install ALL-IN-1 STARTER V2.4 Table 1-3 Actions to Complete Before Installing ALL-IN-1 ________________________________________________________________ Step__Section__Action___________________________Completed_______ 1 1.8.3 Backup the system disk 1 1.8.3 Backup any target disks (if applicable) 2 1.8.4 Make sure that there are no active users on the system 3 1.8.5 Performance Customizations of PROFILE.FDL and PROFILE.DAT (Ug, Ud) 4 1.8.6 Register and load the licenses for the prerequisite software 5 1.8.7 Ensure that the Message Router Directory Service is running if you want to use the Mail directory 6 1.8.8 Stop the OA$FORMATTER queue (Ug, Ud) 7 1.8.9 Ensure the queue manager is started 8 1.8.10 Run the mail Sender and Fetcher (Ug, Ud) 9 1.8.11 Remove the ALL-IN-1 housekeep- ing jobs from the batch queue (Ug, Ud) 10 1.8.12 Check for adequate: global pages global sections global page file sections 11 1.8.13 Check system parameter values: LOCKIDTBL 340 MAXBUF 5000 PIOPAGES 350 PQL_DENQLM 150 PQL_MENQLM 150 PROCSECTCNT 45 ________________________________________________________________ + The values for WSEXTENT and WSQUOTA must be greater than the WSDEFAULT value. Ug Upgrade installations Ud Update installations (continued on next page) Preparing to Install ALL-IN-1 STARTER V2.4 1-25 Table 1-3 (Cont.) Actions to Complete Before Installing ALL- IN-1 ________________________________________________________________ Step__Section__Action___________________________Completed_______ RESHASHTBL 85 RMS_DFMBC 16 RMS_DFMBFIDX 2 STARTUP_P1 null TTY_TYPAHDSZ 1500 VIRTUALPAGECNT 16385 12 1.8.14 Recompute system parameters 13 1.8.15 Check process quotas: ASTLM 100 BIOLM 50 BYTLM 36000 DIOLM 50 ENQLM 200 FILLM 100 JTQUOTA 1024 PGFLQUOTA 20000 PRCLM 10 TQELM 50 WSDEFAULT 600+ WSEXTENT 2048 WSQUOTA 800 14 1.8.16 Check disk space 15 1.8.17 Check your site-specific startup procedures (Ug) 16 1.8.18 Complete checklist 17 1.8.19 Check the License Management Utility requirements ________________________________________________________________ + The values for WSEXTENT and WSQUOTA must be greater than the WSDEFAULT value. Ug Upgrade installations Ud Update installations ________________________________________________________________ 1-26 Preparing to Install ALL-IN-1 STARTER V2.4 1.8.1 Time Needed to Install ALL-IN-1 STARTER Version 2.4 The installation of ALL-IN-1 STARTER Version 2.4 can take from two to five hours, depending on the configuration of your system. For example, the installation will take longer on a MicroVAX system than on a VAX system. This does not include the time taken to install and configure Message Router and to set up your system. The installation of an additional language takes approxi- mately 1 to 2.5 hours. 1.8.2 Privileges Install ALL-IN-1 STARTER Version 2.4 from the VMS system manager's account, with full privileges. Note that the VMSINSTAL turns off the BYPASS privilege at the start of the installation. 1.8.3 Back Up Your System and Target Disks If possible, back up your system disk and use this backup copy for installation. If you are going to install ALL-IN-1 STARTER Version 2.4 on more than one disk, back up those disks that are to be used during the installation. Do this because: o If a system failure occurs at a critical point during installation, some files could be left in an inconsistent state o You can verify that the backup copy contains a working system image and then replace the system disk with it o There is more contiguous free space, which may be needed for installation 1.8.4 Ensure No Active Users on the System Ensure that there are no active users on the system. Ask users currently on the system to log off, and then disable logins, by entering the following: $ SET LOGINS /INTERACTIVE=0 Preparing to Install ALL-IN-1 STARTER V2.4 1-27 1.8.5 Performance Customizations of PROFILE.FDL and PROFILE.DAT If you have made any performance customizations to PROFILE.FDL or PROFILE.DAT, make sure that you save these files before you start the installation procedure. A new PROFILE.FDL file is provided during installation, and this is used to create a new PROFILE.DAT. You will need to reapply any customizations to the new files after the installation is complete. 1.8.6 Register the Licenses for the Prerequisite Software If you install VAX FMS, Message Router and Message Router VMSmail Gateway, CDA Converter Library, and VAX Notes from the kits supplied with ALL-IN-1 STARTER, register the licenses for these products as follows: 1 Invoke VMSINSTAL: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL AS024 device: where device: is the device on which the distribution media are to be mounted. You can use either a physical or logical device name. Logical device names must not begin with either A1$, OA$ or OA1$. 2 If your system is running VMS Version 5.1, answer YES to the prompt: %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? 3 Answer YES to the prompt: * Are you satisfied with the backup of your system disk [YES]? 4 VMSINSTAL subsequently displays a list of installation types. Enter 7 at the prompt: * What type of installation do you wish to perform [1]: VMSINSTAL checks the licenses, and if necessary installs and loads the appropriate licenses. VMSINSTAL then exits. 1-28 Preparing to Install ALL-IN-1 STARTER V2.4 1.8.7 Ensure Message Router Directory Service is Running If you want to use Mail directory addressing (see Section 1.5.2.1), make sure that the Message Router Directory Service is running. If you are installing ALL-IN-1 STARTER on a multiple- environment cluster, the Message Router Directory Service must be running on the part on which you are installing ALL-IN-1 STARTER (see Section 1.6.2.1). 1.8.8 Shut Down the OA$FORMATTER Batch Queue If you are performing an upgrade or update installation, shut down the OA$FORMATTER batch queue using the following command: $ STOP /QUEUE /NEXT OA$FORMATTER 1.8.9 Start the Queue Manager If your queue manager is not running, start it by entering the following command: $ START /QUEUE /MANAGER 1.8.10 Run the Mail Sender and Fetcher If you are performing an upgrade or update installation, run the mail Sender and Fetcher to read all the mail: 1 Enter the ALL-IN-1 manager's ALL-IN-1 account: $ ALLIN1 /USERNAME=MANAGER 2 Enter MGT to display the ALL-IN-1 Management menu. 3 Enter MM to display the Manage Messaging menu. 4 Enter RF (Run Fetcher) to run the Fetcher to fetch all received messages from the queue. 5 Enter RS (Run Sender) to run the Sender to clear all messages that are waiting to be sent from the queue. 6 Enter EXIT to exit the ALL-IN-1 manager's account. Preparing to Install ALL-IN-1 STARTER V2.4 1-29 1.8.11 Delete the ALL-IN-1 Housekeeping Jobs If you are performing an upgrade or update installation, you must delete all the ALL-IN-1 houskeeping jobs from the batch queue. This is because the batch jobs run an existing version of a command procedure, which may be updated during the installation. To delete the housekeeping procedures, do the following: 1 Enter the ALL-IN-1 manager's ALL-IN-1 account: $ ALLIN1 /USERNAME=MANAGER 2 Enter the following command to find out the entry numbers of the housekeeping jobs: $ SHOW QUEUE/BATCH Make a note of the entry numbers. 3 Enter the following command to delete each of the ALL-IN-1 housekeeping jobs: $ DELETE/ENTRY=entry_number queue_name where entry_number is the entry number of each housekeep- ing job, and queue_name is the name of the batch queue running the housekeeping jobs. You must not use the the MGT MHP D option to delete the housekeeping jobs, as this will delete the jobs from the database of housekeeping jobs. After ALL-IN-1 STARTER is installed, the installation procedure checks the database of housekeeping jobs, and reschedules them. 1.8.12 Calculate the Values for GBLPAGES, GBLSECTIONS and GBLPAGFIL Make sure that you have enough global pages, global sections, and global page file sections available. Also, follow the steps described in this section to check that certain system parameters are set to adequate values. For more information on SYSGEN parameters refer to the VMS manual describing the SYSGEN utility. Note If you are running a VAXcluster system, you must ensure that these parameters are large enough on each node in the cluster on which you are going to run ALL-IN-1 STARTER. 1-30 Preparing to Install ALL-IN-1 STARTER V2.4 These checks only ensure that the system is adequately configured for ALL-IN-1 STARTER, and do not allow for the requirements of any other layered product. 1 Run the Install Utility and display the currently active values for the system parameters GBLSECTIONS and GBLPAGES: $ INSTALL INSTALL> LIST /GLOBAL /SUMMARY A message similar to the following will be displayed: 160 global sections used, 9867/985 global pages used/unused The number of unused global pages required for the different installations is: GBLPAGES (Global Pages Unused) for a new 9000 installation for an upgrade 5000 installation If you want to take advantage of the CDA support provided in ALL-IN-1 STARTER Version 2.4, you need to ensure that you have an extra 750 unused global pages, for both new and upgrade installation. If the number of unused global pages shown in the display is less than the required amount, increase it as follows: a Calculate the value of GBLPAGES as follows: o If you install ALL-IN-1 STARTER Version 2.4 but do not install Message Router, the number of global pages is: 9000 + the allowance for global buffers For each system file, calculate the allowance for global buffers as follows: number of global buffers x maximum bucket size See the chapter on ALL-IN-1 STARTER tuning in the ALL-IN-1 Management Guide for the formulas used to determine the global buffer counts. Preparing to Install ALL-IN-1 STARTER V2.4 1-31 On a default system, the ATTENDEE.DAT file has a bucket size of 2. Other system files have a bucket size of 4. Thus, for an installation that uses these default values, the formula for calculating the allowance for global buffers is as follows: 4(n+1) + 4(n+1) + 4(n+1) + 2(n+1) + 4(5) n is the number of ALL-IN-1 STARTER users. For example, for an installation using the default values on a system with 100 users, the number of global pages is: 9000 + 4(101) + 4(101) + 4(101) + 2(101) + 20 = 9000 + 404 + 404 + 404 + 202 + 20 = 10434 o If you install Message Router as well as ALL-IN-1 STARTER, add an extra 3500 blocks to the result of this calculation b Edit the file SYS$SYSTEM:MODPARAMS.DAT, and include the following line: ADD_GBLPAGES = increase-value increase-value is the amount by which you want to increase the setting of this parameter. For example, if you want to increase the value by 60, enter: ADD_GBLPAGES = 60 2 Exit from the Install Utility as follows: INSTALL> EXIT 3 Run the System Generation Utility as follows: $ RUN SYS$SYSTEM:SYSGEN 1-32 Preparing to Install ALL-IN-1 STARTER V2.4 4 Display the current value of global sections as follows: SYSGEN> USE CURRENT SYSGEN> SHOW GBLSECTIONS The system displays the current value of global sections in the first column. To find the number of unused global sections, subtract the number of global sections used (as shown by the Install Utility) from the current value (as shown by the System Generation Utility). The number of global sections required for the different installations is: for a new installa- 45 tion for an upgrade 30 installation If you want to take advantage of the CDA support provided in ALL-IN-1 STARTER Version 2.4, you need to ensure that you have an extra 25 unused global sections, for both new and upgrade installation. To increase the value of global sections, edit the file SYS$SYSTEM:MODPARAMS.DAT, and include the following line: ADD_GBLSECTIONS = increase-value increase-value is the amount by which you want to increase the setting of this parameter. For example, if you want to increase the value by 10, enter: ADD_GBLSECTIONS=10 5 Check the number of global page-file sections as follows: SYSGEN> SHOW GBLPAGFIL The current value for GBLPAGFIL should be high enough to allow for the maximum number of global buffers allocated on the system. It is not possible to display the current value for GBLPAGFIL. The value displayed by entering the SHOW command is the value at the last reboot. Preparing to Install ALL-IN-1 STARTER V2.4 1-33 If the value of GBLPAGFIL is not high enough, it causes the Fetcher and Sender jobs of Electronic Messaging, or other parts of ALL-IN-1 STARTER, to fail. 1-34 Preparing to Install ALL-IN-1 STARTER V2.4 If the Sender and Fetcher jobs fail, the following error message is placed in the Sender and Fetcher log file: System Service $CRMPSC failed to map global buffers If other parts of ALL-IN-1 STARTER fail, this error message may be displayed on your screen. To increase the value of GBLPAGFIL, edit the file SYS$SYSTEM:MODPARAMS.DAT and include the following line: ADD_GBLPAGFIL = increase-value increase-value is the amount by which you want to increase the setting of this parameter. For example, if you want to increase the value by 60, enter: ADD_GBLPAGFIL = 60 1.8.13 Check the System Parameter Values Display the current system parameter settings using the following command: SYSGEN> SHOW /ALL Alternatively, show each system parameter setting separately using the following command: SYSGEN> SHOW parameter parameter is the parameter you want to examine. Table 1-4 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. If necessary, modify the parameters (as described in Step 2 or 3 of this section) to at least these values. Preparing to Install ALL-IN-1 STARTER V2.4 1-35 Table 1-4 Required System Parameter Values _____________________________________________________________ System_Parameter_____________Value___________________________ LOCKIDTBL 340 MAXBUF (D) 5000 PIOPAGES 350 PQL_DENQLM (D) 150 PQL_MENQLM (D) 150 PROCSECTCNT 45 RESHASHTBL 85 RMS_DFMBC (D) 16 RMS_DFMBFIDX (D) 2 STARTUP_P1 null TTY_TYPAHDSZ 1500 VIRTUALPAGECNT 16385 _____________________________________________________________ (D) Dynamic system parameters _____________________________________________________________ You must ensure that the system parameter STARTUP_P1 is null before installing ALL-IN-1 STARTER Version 2.4. You need not modify the MAXBUF parameter at this point. If this parameter is too low, the installation displays an appropriate message and then continues. However, you must set MAXBUF to at least the value given in Table 1-4 before ALL-IN-1 STARTER is used. Note If you integrate any other software with ALL-IN-1 STARTER, you must increase the SYSGEN parameter PROCSECTCNT by at least five. This makes sure that shared images are accessible during installation. 1 Press CTRL/Z to leave SYSGEN. 2 Modify the following parameters as necessary: PQL_DENQLM PQL_MENQLM RMS_DFMBC RMS_DFMBFIDX TTY_TYPAHDSZ To modify these system parameters edit the file SYS$SYSTEM:MODPARAMS.DAT and specify new parameter values. Use assignment statements of the form: parameter = parameter-value 1-36 Preparing to Install ALL-IN-1 STARTER V2.4 parameter is the name of the parameter you want to change and parameter-value is the setting you want to change it to. For example, if RMS_DFMBFIDX is currently set to 1, which is not sufficient for running ALL-IN-1 STARTER, you must increase it as follows: RMS_DFMBFIDX = 2 3 Change the the following parameters, as necessary: LOCKIDTBL MAXBUF PIOPAGES PROCSECTCNT RESHASHTBL VIRTUALPAGECNT To modify these system parameters edit the file SYS$SYSTEM:MODPARAMS.DAT. Include a line of the following format for each parameter to be changed: ADD_parameter = increase-value o parameter is the name of the parameter you want to change o increase-value is the amount by which you want to increase the setting of this parameter. For example, if you want to increase the value of LOCKIDTBL by 60, enter: ADD_LOCKIDTBL=60 1.8.14 Changing System Parameter Values with AUTOGEN If you have changed only dynamic system parameters, you need not reboot your system. In this case, do the following: 1 Run AUTOGEN as follows: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS 2 Write the changes to the current system: $ @SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> WRITE ACTIVE Preparing to Install ALL-IN-1 STARTER V2.4 1-37 If you changed the values of any of your non-dynamic system parameters in the previous steps, do the following: 1 Set AGEN$SHUTDOWN_TIME to a value greater than SHUTDOWN$MINIMUM_MINUTES: $ DEFINE/SYSTEM/EXECUTIVE_MODE AGEN$SHUTDOWN_TIME shutdown_time 2 Run AUTOGEN to recompute the system parameters: $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT AUTOGEN performs an automatic shutdown and reboot when it has finished. See the VMS manual describing the Autogen Utility. Note The system must have been running at least 24 hours for these commands to work. If your system has been running for less than 24 hours add the parameter NOFEEDBACK at the end of each AUTOGEN command. 1.8.15 Process Account Quotas Ensure that process quotas are adequate. The account you use to install ALL-IN-1 STARTER Version 2.4 must have sufficient quotas to allow you to perform the installation. Table 1-5 summarizes the process quotas required to perform the installation. Table 1-5 Process Account Quotas for the Installing Account _____________________________________________________________ Account_Quota_________Value__________________________________ ASTLM 100 BIOLM 50 BYTLM 36000 DIOLM 50 ENQLM 200 FILLM 100 JTQUOTA 1024 PGFLQUOTA 20000 _____________________________________________________________ + The values for WSEXTENT and WSQUOTA must be greater than the WSDEFAULT value. (continued on next page) 1-38 Preparing to Install ALL-IN-1 STARTER V2.4 Table 1-5 (Cont.) Process Account Quotas for the Installing Account _____________________________________________________________ Account_Quota_________Value__________________________________ PRCLM 10 TQELM 50 WSDEFAULT 600+ WSEXTENT 2048 WSQUOTA 800 _____________________________________________________________ + The values for WSEXTENT and WSQUOTA must be greater than the WSDEFAULT value. _____________________________________________________________ When you create user accounts for ALL-IN-1 STARTER Version 2.4 the process quotas are set to the appropriate values. See the ALL-IN-1 Management Guide for details. If you are upgrading from ALL-IN-1 STARTER Version 1.0, you must set the process quotas to at least the values listed in Table 1-5 for all the users on your current ALL-IN-1 STARTER system. To increase the process account quotas use the Authorize Utility. Note If you integrate any other software with ALL-IN-1 STARTER, you must increase the quota values according to the requirements of the software. You can change the process quotas for an account even if a user is logged in to the account. However, if a user is logged in, that user must log out and log back in again for the process quotas to become active. 1.8.16 Disk Space Installing ALL-IN-1 STARTER Version 2.4 requires a certain amount of free storage space during the installation. Once ALL-IN-1 STARTER Version 2.4 is installed, less storage space is required. The amount of disk space available on the system disk determines the mode of installation. The installation runs in either Safety or Non-Safety mode (see Section 1.8.16.1). Preparing to Install ALL-IN-1 STARTER V2.4 1-39 The minimum disk space required on the system disk during installation depends on whether you are installing ALL-IN-1 STARTER Version 2.4 on the system disk only, or across several disks. To determine the minimum disk space required on the system disk, add together the values given in the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation and ALL-IN-1 STARTER Installation Guide Part 3 Market Installation. 1.8.16.1 Installation Modes The installation runs in one of two modes, depending on how many blocks are available on the system disk: o Safety mode If you have a minimum of 75,000 free blocks on your system disk, the installation is performed in Safety mode. All the files are transferred from the media to a working area on the system disk before they are moved to their target directories. If you are performing a system disk installation, the installation is always carried out in Safety mode. If a failure occurs before the files start to be moved to target directories, VMSINSTAL deletes the working area so that you can restart the installation. Note VMSINSTAL does not delete any accounts or directory structures that are created. 1-40 Preparing to Install ALL-IN-1 STARTER V2.4 o Non-Safety mode In Non-Safety mode each file is transferred from the media to a working directory on the system disk. After each file is transferred it is moved to its target directory, before the next file is transferred. If you choose to install in Non-safety mode, the minimum required free blocks during installation on your system disk is 15,000 free blocks. This space is required to restore savesets. If a failure occurs during a Non-Safety mode installation, some files have already been copied to their target directories. Therefore, cleaning up the target disks involves more work than for Safety mode. 1.8.16.2 ALL-IN-1 Areas To ease the management of ALL-IN-1 STARTER you can choose to split ALL-IN-1 STARTER across several disks; each disk containing an ALL-IN-1 area. The ALL-IN-1 areas are: o ALL-IN-1 manager's account. This account includes the IVPUSER, MGR, POSTMASTE, TRANSFER_INCOMING and TRANSFER_OUTGOING directories o Shared library files o Shared data files o Language files o Mail area shared document attributes file SDAF file OA$SHARE:OA$DAF_E.DAT. Mail area E is created during a new installation. o Shared directories SHAREnnnn, where nnnn is a number in the range 1 to 9999. Shared directories for Mail area E are created during a new installation. An example of the directory structure for a multiple-disk ALL-IN-1 STARTER system is given in Appendix C. Space is provided in Table 1-6 for you to enter the disk space requirements of each ALL-IN-1 area. See the ALL-IN-1 STARTER Installation Guide Part 3 Market Installation for the disk space required by all areas except for the language files. See the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation for the disk space required by the language files. Preparing to Install ALL-IN-1 STARTER V2.4 1-41 Note The ALL-IN-1 STARTER Installation Guide Part 2 Language Installation and ALL-IN-1 STARTER Installation Guide Part 3 Market Installation also give the disk space requirements if WPS-PLUS is incorporated and if WPS-PLUS is not incorporated. If you want more than one area on the same disk, the disk space required is the total for those areas. 1-42 Preparing to Install ALL-IN-1 STARTER V2.4 Table 1-6 Disk Space Requirements for the ALL-IN-1 Areas ________________________________________________________________ ALL-IN-1 Area _______Disk_Space_Requirements_(blocks)_______ Upgrade from Update of New ALL-IN-1 ALL-IN-1 ALL-IN-1 __________________STARTER_V2.4_____STARTER_V1.0_____STARTER_V2.4 System files* Manager's account+ Shared library files Shared data files Mail area SDAF 1,000 file Shared n x 1000 directories Language files++: (1) (2) ________________________________________________________________ * These are the files that are installed in the SYS$MANAGER, SYS$LIBRARY, SYS$MESSAGE and SYS$HELP directories (see Appendix C) + This figure includes the [.IVPUSER], [.MGR], [.POSTMASTE], [.TRANSFER_INCOMING] and [.TRANSFER_OUTGOING] directories. n is the number of shared directories specified during the installation. ++ See the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation for the language(s) that you are installing (continued on next page) Preparing to Install ALL-IN-1 STARTER V2.4 1-43 Table 1-6 (Cont.) Disk Space Requirements for the ALL-IN-1 Areas ________________________________________________________________ ALL-IN-1 Area _______Disk_Space_Requirements_(blocks)_______ Upgrade from Update of New ALL-IN-1 ALL-IN-1 ALL-IN-1 __________________STARTER_V2.4_____STARTER_V1.0_____STARTER_V2.4 (3) (4) (5) (6) (7) (8) (9) (10) ________________________________________________________________ * These are the files that are installed in the SYS$MANAGER, SYS$LIBRARY, SYS$MESSAGE and SYS$HELP directories (see Appendix C) + This figure includes the [.IVPUSER], [.MGR], [.POSTMASTE], [.TRANSFER_INCOMING] and [.TRANSFER_OUTGOING] directories. n is the number of shared directories specified during the installation. ++ See the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation for the language(s) that you are installing ________________________________________________________________ If you decide to keep a record of the installation in a log file, add at least 200 blocks to the disk space determined in steps 1 to 3. If you are installing an additional language you need the minimum amount of free blocks given in the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation for that language. 1-44 Preparing to Install ALL-IN-1 STARTER V2.4 If you want more than one ALL-IN-1 area on the same disk, the minimum disk space required is the total for those areas. Note If you only have the minimum amount of recommended free space, and your system crashes during installation, or if the installation fails, the software will be only partially installed. For this reason, Digital recommends that you back up your system disk, and all target disks for a multiple disk installation, before installing ALL-IN-1 STARTER Version 2.4. If all areas of ALL-IN-1 STARTER are going to be installed on the system disk, ensure that there are enough free blocks on the system disk by issuing the SHOW DEVICE command, for example: $ SHOW DEVICE SYS$SYSDEVICE If the areas of ALL-IN-1 STARTER are to be installed on a disk or disks other than the system disk, ensure that these disks have enough free blocks by issuing the SHOW DEVICE command. For example: $ SHOW DEVICE disk where disk is the name of the disk that will hold the ALL-IN-1 areas. 1.8.17 Check Your Site-Specific Startup Procedures If you are upgrading from ALL-IN-1 STARTER Version 1.0, and you have created site-specific startup procedures (that is, AS010_SITE_START.COM and OA$SITE_language_START.COM), do the following: 1 Check your site-specific startup command procedure(s) for any commands that change the configuration of ALL-IN-1 STARTER. You may wish to change the configuration during the installation of ALL-IN-1 STARTER Version 2.4, for example, if you re-link ALL-IN-1 STARTER to incorporate WPS-PLUS and so on. 2 If you want to keep your site-specific startup command procedure A1V23_SITE_START.COM, you must rename it to A1V24_SITE_START.COM after the installation (see Section 10.10.3). Preparing to Install ALL-IN-1 STARTER V2.4 1-45 1.8.18 Checklist of Information Required for Installation Before you install ALL-IN-1 STARTER Version 2.4 you should know what answers you are going to give to the questions asked during the installation. Refer to the table of steps in the chapter appropriate to the installation you are going to perform. This table indicates which steps are required for that installation. Full descriptions of the steps are described in Chapter 9. Place a tick in the box for each of the steps required by your installation and enter your answer to the prompt(s) in that step in the space provided. o If you are installing ALL-IN-1 STARTER Version 2.4, and you do not have any other version of ALL-IN-1 STARTER, see Chapter 3 o If you are installing an additional language, see Chapter 4 o If you are upgrading your ALL-IN-1 STARTER Version 1.0 system to ALL-IN-1 STARTER Version 2.4, see Chapter 5 o If you are upgrading an ALL-IN-1 STARTER Version 1.0 additional language to an ALL-IN-1 STARTER Version 2.4 additional language, see Chapter 6 o If you are updating your existing ALL-IN-1 STARTER Version 2.4 system, see Chapter 7 o If you are updating an ALL-IN-1 STARTER Version 2.4 additional language, see Chapter 8 1.8.19 License Management Utility Requirements You must register and load your license for ALL-IN-1 STARTER Version 2.4 before you start the installation in order to install ALL-IN-1 STARTER Version 2.4. For more information on the VMS License Management Facility, see the VMS License Management Facility documentation. 1-46 Preparing to Install ALL-IN-1 STARTER V2.4 2 ________________________________________________________________ Accessing the Online Release Notes ALL-IN-1 STARTER Version 2.4 provides online Release Notes. The Release Notes contain information that was unavailable before the books went to print. It is important to read the Release Notes, because they may contain information relating to the installation. There are two parts to the Release Notes: o Release Notes Part 1 Language This part contains the release notes specific to the ALL-IN-1 STARTER Version 2.4 international base component and to the language being installed, and is on the tape labeled: ALL-IN-1 STARTER V2.4 language BIN media_type Release Notes Part 1 (c) 1990 Digital Equipment Corp. language is the name of the ALL-IN-1 STARTER Version 2.4 language component to be installed, and media_type is 16MT9 for tape and TK50 for a TK50 cartridge. Accessing the Online Release Notes 2-1 o Release Notes Part 2 Market This part contains the release notes specific to your ALL-IN-1 STARTER Version 2.4 market component, and is on the tape labeled: ALL-IN-1 STARTER V2.4 market BIN media_type Release Notes Part 2 (c) 1990 Digital Equipment Corp. market is the name of the ALL-IN-1 STARTER Version 2.4 Market component to be installed. Note This document may not exist for all market components. 2.1 Accessing the Release Notes To access the Release Notes: 1 Log in to the privileged VMS system manager's account. 2 Establish the following default directory: $ SET DEFAULT SYS$UPDATE 3 Enter the following command: $ @VMSINSTAL product device: OPTIONS N product is the product code: ASLRlang024 for the Release Notes Part 1 Language or ASCRmarket024 for the Release Notes Part 2 Market device is the device on which the tape containing the appropriate version of the Release Notes is mounted. The following message is displayed: VAX/VMS Software Product Installation Procedure V. It is at . and are the current date and time, and is the version of VMS that your system is running. Enter a question mark (?) at any time for help. 2-2 Accessing the Online Release Notes 4 If your system is running VMS Version 5.1, and your DECnet network is running, the following message is displayed: %VMSINSTAL-W-DECNET, your DECnet network is up and running. * Do you want to continue anyway [NO]? Enter YES and press RETURN. 5 If other users are accessing the system, the following message appears: %VMSINSTAL-W-ACTIVE,The following processes are still active . . . * Do you want to continue anyway [NO]? refers to the process name of a user logged in to the system. As you are only printing the Release Notes, it is safe to continue. Enter YES and press RETURN. 6 VMSINSTAL displays: * Are you satisfied with the backup of your system disk [YES]? As you are only printing the Release Notes, it is safe to continue, so press RETURN. 7 VMSINSTAL then prompts you to mount the distribution media: Please mount the first volume of the set on : where is the device you specified. The Release Notes are in two parts, one part on each of the distribution media labeled as follows: ALL-IN-1 STARTER V2.4 language BIN media_type Release Notes Part 1 (c) 1990 Digital Equipment Corp. and ALL-IN-1 STARTER V2.4 market BIN media_type Release Notes Part 2 (c) 1990 Digital Equipment Corp. Accessing the Online Release Notes 2-3 where language is the name of the ALL-IN-1 STARTER Version 2.4 language component to be installed, market is the name of the ALL-IN-1 STARTER Version 2.4 Market component to be installed, and media_type is 16MT9 for tape and TK50 for a TK50 cartridge. If you are performing an additional language installation, you need only print the ALL-IN-1 STARTER Release Notes Part 1 Language that is supplied with your kit. VMSINSTAL displays: * Are you ready? At this prompt, mount the first volume of the distribution medium. (If you are unfamiliar with the loading of media, refer to the VMS software intsallation documentation.) When you have mounted the volume, enter YES and press RETURN. VMSINSTAL tries to mount the distribution volume. If it succeeds, a message is displayed, for example: %MOUNT-I-MOUNTED, AS024 mounted on : where is 3 for the ALL-IN-1 STARTER Release Notes Part 1 Language and 2 for the ALL-IN-1 STARTER Release Notes Part 2 Market, and is the device where the media is mounted. The following message is then displayed: The following products will be processed: V2.4 Beginning installation of V2.4 at where is the current time and is: o ASLRlanguage for the ALL-IN-1 STARTER Release Notes Part 1 Language o ASCRmarket for the ALL-IN-1 STARTER Release Notes Part 2 Market 8 VMSINSTAL displays: %VMSINSTAL-I-RESTORE, Restoring product saveset A... Release Notes Options: 2-4 Accessing the Online Release Notes 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 the release notes * Select option [3]: Enter the number of the option that you require. If you enter 2, or 3, to print the Release Notes, the following message is displayed: * Queue name [SYS$PRINT]: Press RETURN if you want to print the Release Notes on SYS$PRINT. If you do not want to print on SYS$PRINT, enter the name of the printer queue you want to use. The following message is then displayed: * Do you want to continue the installation [N]? Press RETURN to accept the default answer of NO. The following messages are displayed: %VMSINSTAL-I-RELMOVED, The product Release Notes have been successfully moved to SYS$HELP. Installation of V2.4 completed at VMSINSTAL procedure done at where is the current time and is: ASLRlanguage for the ALL-IN-1 STARTER Release Notes Part 1 Language ASCRmarket for the ALL-IN-1 STARTER Release Notes Part 2 Market If you have accessed only one part of the Release Notes, repeat steps 3 to 8 for the other part. If you chose to print the Release Notes, or copy them to SYS$HELP, the following files are placed in SYS$HELP: o ASLRlang024.RELEASE_NOTES, for the Release Notes Part 1 Language Accessing the Online Release Notes 2-5 o ASCRmarket024.RELEASE_NOTES, for the Release Notes Part 2 Market Note It is important to read the Release Notes before installing ALL-IN-1 STARTER. 2-6 Accessing the Online Release Notes 3 ________________________________________________________________ Installing a New ALL-IN-1 STARTER V2.4 System This chapter explains how to install ALL-IN-1 STARTER Version 2.4 if you are installing ALL-IN-1 STARTER as a new system. 3.1 Before You Start Before you start the installation procedure: 1 Make sure that you have made all the necessary prepara- tions (see Section 1.8). 2 Complete the checklist of information required for installation (see Section 1.8.18). Refer to this checklist during the installation. You must have the base, language, and market components to install ALL-IN-1 STARTER Version 2.4. 3.2 Overview of VMSINSTAL VMSINSTAL is a DCL command procedure that is used to install optional software products on the VMS operating system. VMSINSTAL requires at least two parameters: o The name of the product(s) being installed. o The name of the device where the distribution media are to be mounted or loaded. You can use either a physical or logical device name. VMSINSTAL invokes a command procedure on the distribution media and that command procedure controls the rest of the installation. Installing a New ALL-IN-1 STARTER V2.4 System 3-1 3.3 Determining the Files and Logical Names Added to the System A list of the files, and their directories, of an installed ALL-IN-1 STARTER Version 2.4 system is given in Appendix C. A list of the logical names added to your system is given in Appendix C. 3.4 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for ALL-IN-1 STARTER Version 2.4 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. Digital recommends that you run the IVP to ensure that ALL-IN-1 STARTER Version 2.4 is installed correctly. After ALL-IN-1 STARTER Version 2.4 is installed, you can run the IVP independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to ensure that users can access ALL-IN-1 STARTER Version 2.4. Instructions on running the IVP are given in the ALL-IN-1 Management Guide. 3.5 Aborting the Installation To abort the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, and the installation is being performed in Safety mode (see Section 1.8.16.1), the installation procedure deletes all files it has created up to that point and exits. You must restart the installation from the beginning. Note VMSINSTAL does not delete any accounts or directory structures that are created. 3.6 Warning and Error Messages The following warning and error messages may be displayed during the installation: o %INSTALL-W-NOPREV, no previous entry exists - new entry created for where is the full file specification for the image that is to be created. o %SYSTEM-E-NOSUCHSEC, no such (global) section 3-2 Installing a New ALL-IN-1 STARTER V2.4 System o %UAF-E-RDBADDERRU, unable to add A1$XFER_IN value: [000001,000100] to RIGHTSLIST.DAT -SYSTEM-F-DUPIDENT, duplicate identifier o %UAF-E-RDBADDERRU, unable to add A1$XFER_OUT value [000001,000100] to RIGHTSLIST.DAT -SYSTEM-F-DUPIDENT, duplicate identifier These messages can be ignored. The following informational and error messages are displayed when the IVP is run: o %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found o %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found o %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library These messages are due to various tests being performed by the IVP. ALL-IN-1 STARTER Version 2.4 can be installed only on systems running VMS Version 5.1, or higher. If your system does not have the correct version of VMS an error message is displayed as follows: $A1-F-V50VMS-1, Incorrect VMS version. Please upgrade to VMS Version 5.1 $A1-F-V50VMS-2, before installing ALL-IN-1 STARTER version 2.4. Upgrade your system to VMS Version 5.1, or higher, before installing ALL-IN-1 STARTER Version 2.4. 3.7 The Installation Procedure Table 3-1 lists the steps required for a new installation of ALL-IN-1 STARTER Version 2.4. Installing a New ALL-IN-1 STARTER V2.4 System 3-3 Table 3-1 Steps Required to Install a New ALL-IN-1 Version 2.4 System _____________________________________________________________ STEP__Title__________________________________________________ 1 Invoke VMSINSTAL 2 DECnet status 3 Active processes 4 System backup 5 Load the distribution media - Sequence 1 6 Indicate which type of installation you wish to perform 7 Load the Distribution Media - Sequence 2 8 Specify the market code required by this installation 9 Specify the language code required by this installation 10 Indicate whether you have registered and loaded your ALL-IN-1 Product Authorization Key 12 Indicate whether or not you want to incorporate WPS- PLUS 13 Check to see if the CDA Converter Library is installed 14 Indicate whether or not you want to build a multi- language system 15 Select the date format to use with ALL-IN-1 16 Specify the greatest number of simultaneous ALL-IN-1 users 17 Specify the batch queue to run the Sender and Fetcher 18 Indicate whether or not you want to send and receive messages to and from other systems 19 Indicate whether the Message Router you want ALL-IN-1 to use is on this node or another node 20 Specify the node whose Message Router you want to use 21 Specify the level of use of the Mail directory 22 Specify the password for the ALL-IN-1 Message Router mailbox 23 Indicate whether or not you want to translate outgoing WPS-PLUS and DX messages to ASCII 24 Check the mandatory and optional software prerequisites (continued on next page) 3-4 Installing a New ALL-IN-1 STARTER V2.4 System Table 3-1 (Cont.) Steps Required to Install a New ALL-IN-1 Version 2.4 System _____________________________________________________________ STEP__Title__________________________________________________ 25 Specify the device to hold the ALL-IN-1 shared library files 26 Specify the device to hold the ALL-IN-1 shared data files 27 Specify the device to hold the ALL-IN-1 language files 28 Specify the device to use for the ALL-IN-1 mail area SDAF file 29 Indicate how many shared directories you would like 30 Specify a device for each shared directory 31 Identify or create the VMS account for ALL-IN-1 33 Specify the password for the ALL-IN-1 manager's VMS account 34 Specify the password for the ALL-IN-1 transfer user accounts 35 Specify the UIC for the ALL-IN-1 manager's VMS account 36 Specify the device and directory for the ALL-IN-1 manager's VMS account 37 Specify the UICs for the ALL-IN-1 transfer user accounts 38 Specify the directory to hold the shared library files, in OA$LIB 39 Specify the directory to hold the shared data files, in OA$DATA 40 Specify the directory to hold the language files 41 Specify the directory to hold the mail area SDAF file OA$DATA:OA$DAF_E.DAT 42 Specify the directory to hold the shared directories, OA$SHAREnnn 43 Indicate whether or not you want to run the IVPs 44 Load the Distribution Media - Sequence 3 45 Wait for the installation to complete 46____Complete_installation__________________________________ The steps are described in Chapter 9. Before starting the installation, indicate the steps required for your Installing a New ALL-IN-1 STARTER V2.4 System 3-5 installation by placing a tick in the box for each of the steps. 3.8 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of AS V2.4 has failed. If the IVP fails, the following messages are displayed: The AS V2.4 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for AS V2.4 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o A prerequisite software version is incorrect o Quotas necessary for successful installation are insufficient o System parameter values for successful installation are insufficient o The VMS help library is currently in use o The product is not properly licensed o SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB are not present. These files are removed if you tailor VMS. For descriptions of the error messages generated by these conditions, see the VMS books on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. (You might need to change a system parameter or increase an authorized quota value.) For information on installation requirements, see Chapter 1. Note If the installation fails, you must restart the installa- tion from the beginning. 3-6 Installing a New ALL-IN-1 STARTER V2.4 System 3.8.1 Errors Found During the IVP If any error messages occur during the IVP, do the following: o Check the log of the installation for any errors that may have occurred during installation. o Check the file ALLIN1_IVP.LOG. This file does not contain the results of the IVP, but the results of invoking ALL-IN-1 STARTER when running the IVPs. This file is in the directory where you run the installation, usually SYS$MANAGER. o Make sure you have executed the startup command file SYS$MANAGER:A1V24START.COM so that all image files, logical names and form libraries have been successfully installed. o Make sure that the ALL-IN-1 TXL is compiled and installed successfully and recompile it if you received any error messages when the startup command file was run. o Check that you have not run out of quota on the disk(s) containing the OA$SHAREnnnn directories (refer to the manual describing VMS utilities). o Check that the details for the IVP account are completed correctly, as follows: - All the ALL-IN-1 privileges are set to YES. - The IVP user directory points to the disk and subdirectory that you specified for the ALL-IN-1 manager's account. For example, using the installation defaults would give: SYS$SYSDEVICE:[ALLIN1.IVPUSER] - The ALL-IN-1 account, IVP, is accessed from the ALL-IN-1 manager's VMS account. Installing a New ALL-IN-1 STARTER V2.4 System 3-7 o Run ALL-IN-1 STARTER and try to use those areas that failed during the IVP to find more information on the error. Log in to the ALL-IN-1 manager's IVP account: $ ALLIN1 /USERNAME=IVP Manually execute each IVP test as described in the ALL-IN-1 Management Guide. 3-8 Installing a New ALL-IN-1 STARTER V2.4 System 4 ________________________________________________________________ Installing Additional Languages for ALL-IN-1 STARTER V2.4 This chapter explains how to install a new additional language. 4.1 Before You Start Before you start the installation procedure: 1 Print and read the ALL-IN-1 STARTER Release Notes Part 1 Language (see Section 2.1) 2 Make sure that you have made all the necessary prepara- tions (see Section 1.8). 3 Make sure that no ALL-IN-1 STARTER logical names point to system root directories, for example, OA$LIB must not be defined as SYS$SYSROOT:[ALLIN1.LIB]. 4 Complete the checklist of information required for installation given in Section 1.8.18. Refer to this checklist during the installation. 5 If you have rebooted your system prior to starting the installation, make sure that you have run the ALL-IN-1 STARTER startup command file (SYS$MANAGER:A1V24START.COM) before you start the installation. You need only the required language component to install an additional ALL-IN-1 STARTER Version 2.4 language. Installing Additional Languages for ALL-IN-1 STARTER V2.4 4-1 4.2 Overview of VMSINSTAL VMSINSTAL is a DCL command procedure that is used to install optional software products on the VMS operating system. VMSINSTAL requires at least two parameters: o The name of the product(s) being installed. o The name of the device where the distribution medium is mounted or loaded. You can use either a physical or logical device name. VMSINSTAL invokes a command procedure on the distribution medium and that command procedure controls the rest of the installation. 4.3 Determining the Files and Logical Names Added to the System A list of the files, and their directories, of an installed ALL-IN-1 STARTER Version 2.4 system is given in Appendix C. A list of the logical names added to your system is given in Appendix C. 4.4 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for ALL-IN-1 STARTER Version 2.4 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. Digital recommends that you run the IVP to ensure that ALL-IN-1 STARTER Version 2.4 is installed correctly. After ALL-IN-1 STARTER Version 2.4 is installed, you can run the IVP independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to ensure that users can access ALL-IN-1 STARTER Version 2.4. Instructions on running the IVP are given in the ALL-IN-1 Management Guide. 4-2 Installing Additional Languages for ALL-IN-1 STARTER V2.4 4.5 Aborting the Installation To abort the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, and the installation is being performed in Safety mode (see Section 1.8.16.1), the installation procedure deletes all files it has created up to that point and exits. You must restart the installation from the beginning. Note VMSINSTAL does not delete any accounts or directory structures that are created. 4.6 Warning and Error Messages The following warning and error messages may be displayed during the installation: o %INSTALL-W-NOPREV, no previous entry exists - new entry created for where is the full file specification for the image that is to be created. o %SYSTEM-E-NOSUCHSEC, no such (global) section These messages can be ignored. The following informational and error messages are displayed when the IVP is run: o %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found o %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found o %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library These messages are due to various tests being performed by the IVP. 4.7 The Installation Procedure Table 4-1 lists the steps required for an additional language installation. Installing Additional Languages for ALL-IN-1 STARTER V2.4 4-3 Table 4-1 Steps Required for an ALL-IN-1 V2.4 Language Installation _____________________________________________________________ STEP__Title__________________________________________________ 1 Invoke VMSINSTAL 2 DECnet status 3 Active processes 4 System backup 5 Load the distribution media - Sequence 1 6 Indicate which type of installation you wish to perform 10 Indicate whether you have registered and loaded your ALL-IN-1 Product Authorization Key 15 Select the date format to use with ALL-IN-1 27 Specify the device to hold the ALL-IN-1 language files 32 Indicate the existing VMS username for the ALL-IN-1 account 40 Specify the directory to hold the language files 43 Indicate whether or not you want to run the IVPs 45 Wait for the installation to complete 46____Complete_installation__________________________________ The steps are described in Chapter 9. Before starting the installation, indicate the steps required for your installation by placing a tick in the box for each of the steps. 4.8 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of ASL V2.4 has failed. If the IVP fails, the following messages are displayed: The A1L V2.4 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for A1L V2.4 has failed. where is the name of the language being installed. 4-4 Installing Additional Languages for ALL-IN-1 STARTER V2.4 Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o A prerequisite software version is incorrect o Quotas necessary for successful installation are insufficient o System parameter values for successful installation are insufficient o The VMS help library is currently in use o The product is not properly licensed o SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB are not present. These files are removed if you tailor VMS. For descriptions of the error messages generated by these conditions, see the VMS books on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. (You might need to change a system parameter or increase an authorized quota value.) For information on installation requirements, see Chapter 1. Note If the installation fails, you must restart the installa- tion from the beginning. 4.8.1 Errors Found During the IVP If any error messages occur during the IVP, do the following: o Check the log of the installation for any errors that may have occurred during installation. o Check the file ALLIN1_IVP.LOG. This file does not contain the results of the IVP, but the results of invoking ALL-IN-1 STARTER when running the IVPs. This file is in the directory where you run the installation, usually SYS$MANAGER. o Make sure you have executed the startup command procedure SYS$MANAGER:A1V24START.COM so that all image files, logical names and form libraries have been successfully installed. Installing Additional Languages for ALL-IN-1 STARTER V2.4 4-5 o Make sure that the ALL-IN-1 TXL and your site-specific TXL, if there is one, were compiled and installed successfully and recompile them if you received any error messages when the startup command procedure was run. o Check that you have not run out of quota on the disk(s) containing the OA$SHAREnnnn directories (refer to the manual describing VMS utilities). o Check that the details for the IVP account are completed correctly, as follows: - All the ALL-IN-1 privileges are set to YES. - The IVP user directory points to the disk and subdirectory that you specified for the ALL-IN-1 manager's account. For example, using the installation defaults would give: SYS$SYSDEVICE:[ALLIN1.IVPUSER] - The ALL-IN-1 account, IVP, is accessed from the ALL-IN-1 manager's VMS account. o Run ALL-IN-1 STARTER and try to use those areas that failed during the IVP to find more information on the error. Log in to the ALL-IN-1 manager's IVP account: $ ALLIN1 /USERNAME=IVP /LANGUAGE=lang where lang is the name of the language being installed. Manually execute each IVP as described in the ALL-IN-1 Management Guide. Note The IVP runs in the language context of the current optional language being installed and also tests the international base system. 4-6 Installing Additional Languages for ALL-IN-1 STARTER V2.4 5 ________________________________________________________________ Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 This chapter explains how to upgrade from ALL-IN-1 STARTER Version 1.0 to ALL-IN-1 STARTER Version 2.4. 5.1 Before You Start Before you start the installation procedure: 1 Make sure that you have made all the necessary prepara- tions (see Section 1.8). 2 Make sure that no ALL-IN-1 STARTER logical names point to system root directories, for example, OA$LIB must not be defined as SYS$SYSROOT:[ALLIN1.LIB]. 3 If you have carried out any permitted modifications (for example, to template files) to your ALL-IN-1 STARTER Version 1.0 system, save the modifications in an area that is not used by ALL-IN-1 STARTER. 4 Complete the checklist of information required for installation given in Section 1.8.18. Refer to this checklist during the installation. 5 Rename the training file OA$CBI_language:CBIMGSFIF.DAT to OA$CBI_language:CBIAGSFIF.DAT, for each language component installed on your system. Otherwise, the IVPs will fail. 6 Run the following command procedure to set up the correct environment for the upgrade installation: SYS$MANAGER:AS010_PRE_V23UPGRADE.COM Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 5-1 7 To allow for a future upgrade to the full ALL-IN-1 Version 2.4 system, modify the ALL-IN-1 manager's account details to include access to OA$LIB:CM as follows: a Create a script, for example STARTER_MODIFY.SCP, containing the following: WRITE CHANGE PROFIL USER='MANAGER', - FRMLIB='OA$LIB:MANAGER,OA$LIB:ADMIN,OA$LIB:CM' b Enter the ALL-IN-1 manager's account, and enter the following command: where is the full file specification for the image that is to be created. o %SYSTEM-E-NOSUCHSEC, no such (global) section o %UAF-E-RDBADDERRU, unable to add A1$XFER_IN value: [000001,000100] to RIGHTSLIST.DAT -SYSTEM-F-DUPIDENT, duplicate identifier Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 5-3 o %UAF-E-RDBADDERRU, unable to add A1$XFER_OUT value: [000001,000100] to RIGHTSLIST.DAT -SYSTEM-F-DUPIDENT, duplicate identifier These messages can be ignored. The following informational and error messages are displayed when the IVP is run: o %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found o %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found o %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library These messages are due to various tests being performed by the IVP. 5.7 The Installation Procedure Table 5-1 lists the step required to upgrade your ALL-IN-1 STARTER Version 1.0 system to ALL-IN-1 STARTER Version 2.4. Table 5-1 Steps Required to Upgrade your ALL-IN-1 STARTER V1.0 System to ALL-IN-1 STARTER V2.4 _____________________________________________________________ STEP__Title__________________________________________________ 1 Invoke VMSINSTAL 2 DECnet status 3 Active processes 4 System backup 5 Load the distribution media - Sequence 1 6 Indicate which type of installation you wish to perform 7 Load the Distribution Media - Sequence 2 8 Specify the market code required by this installation 9 Specify the language code required by this installation 10 Indicate whether you have registered and loaded your ALL-IN-1 Product Authorization Key 11 Indicate whether or not you want to purge files replaced by the installation (continued on next page) 5-4 Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 Table 5-1 (Cont.) Steps Required to Upgrade your ALL-IN-1 STARTER V1.0 System to ALL-IN-1 STARTER V2.4 _____________________________________________________________ STEP__Title__________________________________________________ 12 Indicate whether or not you want to incorporate WPS- PLUS 13 Check to see if the CDA Converter Library is installed 14 Indicate whether or not you want to build a multi- language system 15 Select the date format to use with ALL-IN-1 16 Specify the greatest number of simultaneous ALL-IN-1 users 17 Specify the batch queue to run the Sender and Fetcher 18 Indicate whether or not you want to send and receive messages to and from other systems 19 Indicate whether the Message Router you want ALL-IN-1 to use is on this node or another node 20 Specify the node whose Message Router you want to use 21 Specify the level of use of the Mail directory 22 Specify the password for the ALL-IN-1 Message Router mailbox 23 Indicate whether or not you want to translate outgoing WPS-PLUS and DX messages to ASCII 24 Check the mandatory and optional software prerequisites 32 Indicate the existing VMS username for the ALL-IN-1 account 34 Specify the password for the ALL-IN-1 Transfer User accounts 37 Specify the UICs for the ALL-IN-1 transfer user accounts 43 Indicate whether or not you want to run the IVPs 44 Load the Distribution Media - Sequence 3 45 Wait for the installation to complete 46____Complete_installation__________________________________ The steps are described in Chapter 9. Before starting the installation, indicate the steps required for your installation by placing a tick in the box for each of the steps. Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 5-5 You must now upgrade any additional languages that were installed with your (ALL-IN-1) STARTER Version 1.0 system. A separate installation is required for each of the additional languages on your system (see Chapter 6). 5.8 Stop and Start the OA$FORMATTER Queue You must stop and restart the OA$FORMATTER queue by entering the following commands: $ STOP /QUEUE /NEXT OA$FORMATTER $ START /QUEUE OA$FORMATTER 5.9 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of AS V2.4 has failed. If the IVP fails, the following messages are displayed: The AS V2.4 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for AS V2.4 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o A prerequisite software version is incorrect o Quotas necessary for successful installation are insufficient o System parameter values for successful installation are insufficient o The VMS help library is currently in use o The product is not properly licensed o SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB are not present. These files are removed if you tailor VMS. For descriptions of the error messages generated by these conditions, see the VMS books on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. 5-6 Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 (You might need to change a system parameter or increase an authorized quota value.) For information on installation requirements, see Chapter 1. Note If the installation fails, you must restart the installa- tion from the beginning. 5.9.1 Errors Found During the IVP If any error messages occur during the IVP, do the following: o Check the log of the installation for any errors that may have occurred during installation. o Check the file ALLIN1_IVP.LOG. This file does not contain the results of the IVP, but the results of invoking ALL-IN-1 STARTER when running the IVPs. This file is in the directory where you run the installation, usually SYS$MANAGER. o Make sure you have executed the startup command procedure SYS$MANAGER:A1V24START.COM so that all image files, logical names and form libraries have been successfully installed. o Make sure that the ALL-IN-1 TXL is compiled and installed successfully and recompile it if you received any error messages when the startup command procedure was run. o Check that you have not run out of quota on the disk(s) containing the OA$SHAREnnnn directories (refer to the manual describing VMS utilities). o Check that the details for the IVP account are completed correctly, as follows: - All the ALL-IN-1 privileges are set to YES. - The IVP user directory points to the disk and subdirectory that you specified for the ALL-IN-1 manager's account. For example, using the installation defaults would give: SYS$SYSDEVICE:[ALLIN1.IVPUSER] - The ALL-IN-1 account, IVP, is accessed from the ALL-IN-1 manager's VMS account. o Run ALL-IN-1 STARTER and try to use those areas that failed during the IVP to find more information on the error. Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 5-7 Log in to the ALL-IN-1 manager's IVP account: $ ALLIN1 /USERNAME=IVP Manually execute each IVP test as described in the ALL-IN-1 Management Guide. 5-8 Upgrading from ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 6 ________________________________________________________________ Upgrading ALL-IN-1 STARTER V1.0 Languages to ALL-IN-1 STARTER V2.4 Languages This chapter explains how to upgrade an ALL-IN-1 STARTER Version 1.0 additional language to an ALL-IN-1 STARTER Version 2.4 additional language 6.1 Before You Start Before you start the installation procedure: 1 Print and read the ALL-IN-1 STARTER Release Notes Part 1 Language (see Section 2.1) 2 Make sure that you have made all the necessary prepara- tions (see Section 1.8). 3 Make sure that no ALL-IN-1 STARTER logical names point to system root directories, for example, OA$LIB must not be defined as SYS$SYSROOT:[ALLIN1.LIB]. 4 Complete the checklist of information required for installation given in Section 1.8.18. Refer to this checklist during the installation. 5 If you have rebooted your system prior to starting the installation, make sure that you have run the ALL-IN-1 STARTER startup command procedure (SYS$MANAGER:A1V24START.COM) before you start the installation. You need only the required language component to upgrade an ALL-IN-1 STARTER Version 1.0 additional language to an ALL-IN-1 STARTER Version 2.4 additional language. STARTER V1.0 Languages to ALL-IN-1 STARTER V2.4 Languages 6-1 Note You must upgrade your main ALL-IN-1 STARTER Version 1.0 system to ALL-IN-1 STARTER Version 2.4 before upgrading the languages. See Chapter 5. 6.2 Overview of VMSINSTAL VMSINSTAL is a DCL command procedure that is used to install optional software products on the VMS operating system. VMSINSTAL requires at least two parameters: o The name of the product(s) being installed. o The name of the device where the distribution medium is mounted or loaded. You can use either a physical or logical device name. VMSINSTAL invokes a command procedure on the distribution medium and that command procedure controls the rest of the installation. 6.3 Determining the Files and Logical Names Added to the System A list of the files, and their directories, of an installed ALL-IN-1 STARTER Version 2.4 system is given in Appendix C. A list of the logical names added to your system is given in Appendix C. 6.4 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for ALL-IN-1 STARTER Version 2.4 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. Digital recommends that you run the IVP to ensure that ALL-IN-1 STARTER Version 2.4 is installed correctly. After ALL-IN-1 STARTER Version 2.4 is installed, you can run the IVP independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to ensure that users can access ALL-IN-1 STARTER Version 2.4. Instructions on running the IVP are given in the ALL-IN-1 Management Guide. 6-2 Upgrading ALL-IN-1 STARTER V1.0 Languages to ALL-IN-1 STARTER V2.4 Languages 6.5 Aborting the Installation To abort the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, and the installation is being performed in Safety mode (see Section 1.8.16.1), the installation procedure deletes all files it has created up to that point and exits. You must restart the installation from the beginning. Note VMSINSTAL does not delete any accounts or directory structures that are created. 6.6 Warning and Error Messages The following warning and error messages may be displayed during the installation: o %INSTALL-W-NOPREV, no previous entry exists - new entry created for where is the full file specification for the image that is to be created. o %SYSTEM-E-NOSUCHSEC, no such (global) section These messages can be ignored. The following informational and error messages are displayed when the IVP is run: o %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found o %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found o %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library These messages are due to various tests being performed by the IVP. 6.7 The Installation Procedure Table 6-1 lists the steps required for upgrading an ALL-IN-1 STARTER Version 1.0 additional language to an ALL-IN-1 STARTER Version 2.4 additional language. STARTER V1.0 Languages to ALL-IN-1 STARTER V2.4 Languages 6-3 Table 6-1 Steps Required for Upgrading an ALL-IN-1 STARTER V1.0 Language _____________________________________________________________ STEP__Title__________________________________________________ 1 Invoke VMSINSTAL 2 DECnet status 3 Active processes 4 System backup 5 Load the distribution media - Sequence 1 6 Indicate which type of installation you wish to perform 10 Indicate whether you have registered and loaded your ALL-IN-1 Product Authorization Key 11 Indicate whether or not you want to purge files replaced by the installation 15 Select the date format to use with ALL-IN-1 24 Check the mandatory and optional software prerequisites 32 Indicate the existing VMS username for the ALL-IN-1 account 43 Indicate whether or not you want to run the IVPs 45 Wait for the installation to complete 46____Complete_installation__________________________________ The steps are described in Chapter 9. Before starting the installation, indicate the steps required for your installation by placing a tick in the box for each of the steps. 6.8 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of ASL V2.4 has failed. If the IVP fails, the following messages are displayed: where is the name of the language being installed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o A prerequisite software version is incorrect 6-4 Upgrading ALL-IN-1 STARTER V1.0 Languages to ALL-IN-1 STARTER V2.4 Languages o Quotas necessary for successful installation are insufficient o System parameter values for successful installation are insufficient o The VMS help library is currently in use o The product is not properly licensed o SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB are not present. These files are removed if you tailor VMS. For descriptions of the error messages generated by these conditions, see the VMS books on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. (You might need to change a system parameter or increase an authorized quota value.) For information on installation requirements, see Chapter 1. Note If the installation fails, you must restart the installa- tion from the beginning. 6.8.1 Errors Found During the IVP If any error messages occur during the IVP, do the following: o Check the log of the installation for any errors that may have occurred during installation. o Check the file ALLIN1_IVP.LOG. This file does not contain the results of the IVP, but the results of invoking ALL-IN-1 STARTER when running the IVPs. This file is in the directory where you run the installation, usually SYS$MANAGER. o Make sure you have executed the startup command procedure SYS$MANAGER:A1V24START.COM so that all image files, logical names and form libraries have been successfully installed. o Make sure that the ALL-IN-1 TXL is compiled and installed successfully and recompile it if you received any error messages when the startup command procedure was run. o Check that you have not run out of quota on the disk(s) containing the OA$SHAREnnnn directories (refer to the manual describing VMS utilities). STARTER V1.0 Languages to ALL-IN-1 STARTER V2.4 Languages 6-5 o Check that the details for the IVP account are completed correctly, as follows: - All the ALL-IN-1 privileges are set to YES. - The IVP user directory points to the disk and subdirectory that you specified for the ALL-IN-1 manager's account. For example, using the installation defaults would give: SYS$SYSDEVICE:[ALLIN1.IVPUSER] - The ALL-IN-1 account, IVP, is accessed from the ALL-IN-1 manager's VMS account. o Run ALL-IN-1 STARTER and try to use those areas that failed during the IVP to find more information on the error. Log in to the ALL-IN-1 manager's IVP account: $ ALLIN1 /USERNAME=IVP /LANGUAGE=lang where lang is the name of the language being installed. Manually execute each IVP test as described in the ALL-IN-1 Management Guide. Note The IVP runs in the language context of the current optional language being installed and also tests the international base system. 6-6 Upgrading ALL-IN-1 STARTER V1.0 Languages to ALL-IN-1 STARTER V2.4 Languages 7 ________________________________________________________________ Updating an Existing ALL-IN-1 STARTER V2.4 System This chapter explains how to update your existing ALL-IN-1 STARTER Version 2.4 system. You can update your ALL-IN-1 STARTER Version 2.4 system if you decide to change the configuration, or an ALL-IN-1 STARTER component is revised by Digital. 7.1 Before You Start Before you start the installation procedure: 1 Make sure that you have made all the necessary prepara- tions (see Section 1.8). 2 Make sure that no ALL-IN-1 STARTER logical names point to system root directories, for example, OA$LIB must not be defined as SYS$SYSROOT:[ALLIN1.LIB]. 3 Complete the checklist of information required for installation given in Section 1.8.18. Refer to this checklist during the installation. 4 If you have rebooted your system prior to starting the installation, make sure that you have run the ALL-IN-1 STARTER startup command procedure (SYS$MANAGER:A1V24START.COM) before you start the installation. You must have the base, language, and market components to update ALL-IN-1 STARTER Version 2.4. Updating an Existing ALL-IN-1 STARTER V2.4 System 7-1 7.2 Overview of VMSINSTAL VMSINSTAL is a DCL command procedure that is used to install optional software products on the VMS operating system. VMSINSTAL requires at least two parameters: o The name of the product(s) being installed o The name of the device where the distribution media are to be mounted or loaded. You can use either a physical or logical device name. VMSINSTAL invokes a command procedure on the distribution media and that command procedure controls the rest of the installation. 7.3 Determining the Files and Logical Names Added to the System A list of the files, and their directories, of an installed ALL-IN-1 STARTER Version 2.4 system is given in Appendix C. A list of the logical names added to your system is given in Appendix C. 7.4 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for ALL-IN-1 STARTER Version 2.4 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. Digital recommends that you run the IVP to ensure that ALL-IN-1 STARTER Version 2.4 is installed correctly. After ALL-IN-1 STARTER Version 2.4 is installed, you can run the IVP independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to ensure that users can access ALL-IN-1 STARTER Version 2.4. Instructions on running the IVP are given in the ALL-IN-1 Management Guide. 7.5 Aborting the Installation To abort the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, and the installation is being performed in Safety mode (see Section 1.8.16.1), the installation procedure deletes all files it has created up to that point and exits. You must restart the installation from the beginning. 7-2 Updating an Existing ALL-IN-1 STARTER V2.4 System 7.6 Warning and Error Messages The following warning and error messages may be displayed during the installation: o %INSTALL-W-NOPREV, no previous entry exists - new entry created for where is the full file specification for the image that is to be created. o %SYSTEM-E-NOSUCHSEC, no such (global) section o %UAF-E-RDBADDERRU, unable to add A1$XFER_IN value: [000001,000100] to RIGHTSLIST.DAT -SYSTEM-F-DUPIDENT, duplicate identifier o %UAF-E-RDBADDERRU, unable to add A1$XFER_OUT value: [000001,000100] to RIGHTSLIST.DAT -SYSTEM-F-DUPIDENT, duplicate identifier These messages can be ignored. The following informational and error messages are displayed when the IVP is run: o %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found o %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found o %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library These messages are due to various tests being performed by the IVP. Updating an Existing ALL-IN-1 STARTER V2.4 System 7-3 7.7 The Installation Procedure Table 7-1 lists the step required to update your existing ALL-IN-1 STARTER Version 2.4 system. Table 7-1 Steps Required for Updating an Existing ALL-IN-1 STARTER V2.4 System _____________________________________________________________ STEP__Title__________________________________________________ 1 Invoke VMSINSTAL 2 DECnet status 3 Active processes 4 System backup 5 Load the distribution media - Sequence 1 6 Indicate which type of installation you wish to perform 7 Load the Distribution Media - Sequence 2 8 Specify the market code required by this installation 9 Specify the language code required by this installation 10 Indicate whether you have registered and loaded your ALL-IN-1 Product Authorization Key 12 Indicate whether or not you want to incorporate WPS- PLUS 14 Indicate whether or not you want to build a multi- language system 15 Select the date format to use with ALL-IN-1 16 Specify the greatest number of simultaneous ALL-IN-1 users 17 Specify the batch queue to run the Sender and Fetcher 18 Indicate whether or not you want to send and receive messages to and from other systems 19 Indicate whether the Message Router you want ALL-IN-1 to use is on this node or another node 20 Specify the node whose Message Router you want to use 21 Specify the level of use of the Mail directory 23 Indicate whether or not you want to translate outgoing WPS-PLUS and DX messages to ASCII 24 Check the mandatory and optional software prerequisites (continued on next page) 7-4 Updating an Existing ALL-IN-1 STARTER V2.4 System Table 7-1 (Cont.) Steps Required for Updating an Existing ALL-IN-1 STARTER V2.4 System _____________________________________________________________ STEP__Title__________________________________________________ 32 Indicate the existing VMS username for the ALL-IN-1 account 43 Indicate whether or not you want to run the IVPs 44 Load the Distribution Media - Sequence 3 45 Wait for the installation to complete 46____Complete_installation__________________________________ The steps are described in Chapter 9. Before starting the installation, indicate the steps required for your installation by placing a tick in the box for each of the steps. 7.8 Start the OA$FORMATTER Queue The OA$FORMATTER queue is restarted if you elected to run the IVP during the installation. If you did not elect to run the IVP, you must restart the OA$FORMATTER queue by entering the following command: $ START /QUEUE OA$FORMATTER 7.9 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of AS V2.4 has failed. If the IVP fails, the following messages are displayed: The AS V2.4 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for AS V2.4 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o A prerequisite software version is incorrect o Quotas necessary for successful installation are insufficient Updating an Existing ALL-IN-1 STARTER V2.4 System 7-5 o System parameter values for successful installation are insufficient o The VMS help library is currently in use o The product is not properly licensed o SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB are not present. These files are removed if you tailor VMS. For descriptions of the error messages generated by these conditions, see the VMS books on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. (You might need to change a system parameter or increase an authorized quota value.) For information on installation requirements, see Chapter 1. Note If the installation fails, you must restart the installa- tion from the beginning. 7.9.1 Errors Found During the IVP If any error messages occur during the IVP, do the following: o Check the log of the installation for any errors that may have occurred during installation. o Check the file ALLIN1_IVP.LOG. This file does not contain the results of the IVP, but the results of invoking ALL-IN-1 STARTER when running the IVPs. This file is in the directory where you run the installation, usually SYS$MANAGER. o Make sure you have executed the startup command procedure SYS$MANAGER:A1V24START.COM so that all image files, logical names and form libraries have been successfully installed. o Make sure that the ALL-IN-1 TXL is compiled and installed successfully and recompile it if you received any error messages when the startup command procedure was run. o Check that you have not run out of quota on the disk(s) containing the OA$SHAREnnnn directories (refer to the manual describing VMS utilities). 7-6 Updating an Existing ALL-IN-1 STARTER V2.4 System o Check that the details for the IVP account are completed correctly, as follows: - All the ALL-IN-1 privileges are set to YES. - The IVP user directory points to the disk and subdirectory that you specified for the ALL-IN-1 manager's account. For example, using the installation defaults would give: SYS$SYSDEVICE:[ALLIN1.IVPUSER] - The ALL-IN-1 account, IVP, is accessed from the ALL-IN-1 manager's VMS account. o Run ALL-IN-1 STARTER and try to use those areas that failed during the IVP to find more information on the error. Log in to the ALL-IN-1 manager's IVP account: $ ALLIN1 /USERNAME=IVP Manually execute each IVP test as described in the ALL-IN-1 Management Guide. Updating an Existing ALL-IN-1 STARTER V2.4 System 7-7 8 ________________________________________________________________ Updating an ALL-IN-1 STARTER V2.4 Language This chapter explains how to update an ALL-IN-1 STARTER Version 2.4 language. 8.1 Before You Start Before you start the installation procedure: 1 Print and read the ALL-IN-1 STARTER Release Notes Part 1 Language (see Section 2.1) 2 Make sure that you have made all the necessary prepara- tions (see Section 1.8). 3 Make sure that no ALL-IN-1 STARTER logical names point to system root directories, for example, OA$LIB must not be defined as SYS$SYSROOT:[ALLIN1.LIB]. 4 Complete the checklist of information required for installation given in Section 1.8.18. Refer to this checklist during the installation. 5 If you have rebooted your system prior to starting the installation, make sure that you have run the ALL-IN-1 STARTER startup command procedure (SYS$MANAGER:A1V24START.COM) before you start the installation. You need only the required language component to update an ALL-IN-1 STARTER Version 2.4 additional language. Updating an ALL-IN-1 STARTER V2.4 Language 8-1 8.2 Overview of VMSINSTAL VMSINSTAL is a DCL command procedure that is used to install optional software products on the VMS operating system. VMSINSTAL requires at least two parameters: o The name of the product(s) being installed. o The name of the device where the distribution medium is mounted or loaded. You can use either a physical or logical device name. VMSINSTAL invokes a command procedure on the distribution medium and that command procedure controls the rest of the installation. 8.3 Determining the Files and Logical Names Added to the System A list of the files, and their directories, of an installed ALL-IN-1 STARTER Version 2.4 system is given in Appendix C. A list of the logical names added to your system is given in Appendix C. 8.4 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for ALL-IN-1 STARTER Version 2.4 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. Digital recommends that you run the IVP to ensure that ALL-IN-1 STARTER Version 2.4 is installed correctly. After ALL-IN-1 STARTER Version 2.4 is installed, you can run the IVP independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to ensure that users can access ALL-IN-1 STARTER Version 2.4. Instructions on running the IVP are given in the ALL-IN-1 Management Guide. 8-2 Updating an ALL-IN-1 STARTER V2.4 Language 8.5 Aborting the Installation To abort the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, and the installation is being performed in Safety mode (see Section 1.8.16.1), the installation procedure deletes all files it has created up to that point and exits. You must restart the installation from the beginning. Note VMSINSTAL does not delete any accounts or directory structures that are created. 8.6 Warning and Error Messages The following warning and error messages may be displayed during the installation: o %INSTALL-W-NOPREV, no previous entry exists - new entry created for where is the full file specification for the image that is to be created. o %SYSTEM-E-NOSUCHSEC, no such (global) section These messages can be ignored. The following informational and error messages are displayed when the IVP is run: o %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found o %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found o %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library These messages are due to various tests being performed by the IVP. 8.7 The Installation Procedure Table 8-1 lists the steps required for updating an existing language. Updating an ALL-IN-1 STARTER V2.4 Language 8-3 Table 8-1 Steps Required for Updating an Existing ALL-IN-1 STARTER V2.4 Language _____________________________________________________________ STEP__Title__________________________________________________ 1 Invoke VMSINSTAL 2 DECnet status 3 Active processes 4 System backup 5 Load the distribution media - Sequence 1 6 Indicate which type of installation you wish to perform 10 Indicate whether you have registered and loaded your ALL-IN-1 Product Authorization Key 11 Indicate whether or not you want to purge files replaced by the installation 15 Select the date format to use with ALL-IN-1 24 Check the mandatory and optional software prerequisites 32 Indicate the existing VMS username for the ALL-IN-1 account 43 Indicate whether or not you want to run the IVPs 45 Wait for the installation to complete 46____Complete_installation__________________________________ The steps are described in Chapter 9. Before starting the installation, indicate the steps required for your installation by placing a tick in the box for each of the steps. 8.8 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of ASL V2.4 has failed. where is the name of the language being installed. If the IVP fails, the following messages are displayed: The ASL V2.4 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for ASL V2.4 has failed. 8-4 Updating an ALL-IN-1 STARTER V2.4 Language Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o A prerequisite software version is incorrect o Quotas necessary for successful installation are insufficient o System parameter values for successful installation are insufficient o The VMS help library is currently in use o The product is not properly licensed o SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB are not present. These files are removed if you tailor VMS. For descriptions of the error messages generated by these conditions, see the VMS books on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. (You might need to change a system parameter or increase an authorized quota value.) For information on installation requirements, see Chapter 1. Note If the installation fails, you must restart the installa- tion from the beginning. 8.8.1 Errors Found During the IVP If any error messages occur during the IVP, do the following: o Check the log of the installation for any errors that may have occurred during installation. o Check the file ALLIN1_IVP.LOG. This file does not contain the results of the IVP, but the results of invoking ALL-IN-1 STARTER when running the IVPs. This file is in the directory where you run the installation, usually SYS$MANAGER. o Make sure you have executed the startup command procedure SYS$MANAGER:A1V24START.COM so that all image files, logical names and form libraries have been successfully installed. Updating an ALL-IN-1 STARTER V2.4 Language 8-5 o Make sure that the ALL-IN-1 TXL is compiled and installed successfully and recompile it if you received any error messages when the startup command procedure was run. o Check that you have not run out of quota on the disk(s) containing the OA$SHAREnnnn directories (refer to the manual describing VMS utilities). o Check that the details for the IVP account are completed correctly, as follows: - All the ALL-IN-1 STARTER privileges are set to YES. - The IVP user directory points to the disk and subdirectory that you specified for the ALL-IN-1 manager's account. For example, using the installation defaults would give: SYS$SYSDEVICE:[ALLIN1.IVPUSER] - The ALL-IN-1 account, IVP, is accessed from the ALL-IN-1 manager's VMS account. o Run ALL-IN-1 STARTER and try to use those areas that failed during the IVP to find more information on the error. Log in to the ALL-IN-1 manager's IVP account: $ ALLIN1 /USERNAME=IVP /LANGUAGE=lang where lang is the name of the language being installed. Manually execute each IVP test as described in the ALL-IN-1 Management Guide. Note The IVP runs in the language context of the current optional language being installed and also tests the international base system. 8-6 Updating an ALL-IN-1 STARTER V2.4 Language 9 ________________________________________________________________ Steps Required for Installing ALL-IN-1 STARTER V2.4 This chapter contains a complete list of the steps required for installing ALL-IN-1 STARTER Version 2.4. The steps required depend on the type of installation you are performing (see the chapter for the type of installation you are going to perform (Chapters 3 to 8). Indicate the steps required for your type of installation by placing a tick in the box for each of those steps. For those steps that require you to input information, enter the information in the space provided, before you start the installation. 9.1 Installation Steps During the installation procedure a number of cautionary messages and general information messages, which are not documented here, are displayed. Read all messages carefully and follow the advice they offer. Each question in the installation is marked with an asterisk (*) at the beginning of the line. If you are unsure how to answer a question, enter a question mark (?). The installation procedure displays explanatory text. Note If the installation fails, you must restart the installa- tion from the beginning. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-1 STEP 1: Invoke VMSINSTAL To start the installation, log in to the privileged VMS system manager's account, and enter the following command: $ SET DEFAULT SYS$UPDATE If you are performing a new, upgrade, or update installation, enter: $ @VMSINSTAL AS024 device: If you are installing an additional language, or upgrading or updating an existing language, enter: $ @VMSINSTAL ASLlang024 device: device is the device on which the distribution media are to be mounted. You can use either a physical or logical device name. Logical device names must not begin with A1$ or OA$. AS024 is the product identifier for the full ALL-IN-1 STARTER Version 2.4 system. ASLlang024 is the product identifier for the language to be installed. For example, enter the following command if you are performing a new, upgrade or update installation: $ @VMSINSTAL AS024 TAPE0 Note Do not use the command @VMSINSTAL * device:, since this causes VMSINSTAL to install the products from the kit in the incorrect order. If you omit these items, you are prompted for the product identifier and device. The following messages are displayed: VAX/VMS Software Product Installation Procedure V It is at Enter a question mark (?) at any time for help. is the version of VMS that you are running on your system and are the current date and time 9-2 Steps Required for Installing ALL-IN-1 STARTER V2.4 If your system is running VMS Version 5.2, or higher, and any users are logged in to your system, VMSINSTAL goes to STEP 3. If your system is running VMS Version 5.2, or higher, and no users are logged in to your system, VMSINSTAL goes to STEP 4. STEP 2: DECnet status If your system is running VMS Verison 5.1, and your DECnet network is running, the following message is displayed: %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? Enter YES to continue. If you want to use a local Message Router and it is not running, press RETURN. VMSINSTAL aborts. Start the Message Router and restart the installation. Note If you want to use Mail directory addressing, make sure that the Message Router Directory Service is running on your system. If you are installing ALL-IN-1 STARTER on a multiple- environment cluster, the Message Router Directory Service must be running on the part on which you are installing ALL-IN-1 STARTER (see Section 1.6.2.1). STEP 3: Active Processes If no users are accessing the system, or you respond YES to the prompt in STEP 2, VMSINSTAL goes to STEP 4. If other users are accessing the system, the following message appears: Steps Required for Installing ALL-IN-1 STARTER V2.4 9-3 %VMSINSTAL-W-ACTIVE, The following processes are still active . . . * Do you want to continue anyway [NO]? refers to the process name of a user logged in to the system. If the Message Router Version 3.1B software is installed on your system, some Message Router processes will be active, for example, MRLOGGER and MR$T_N_1. If you intend to use Message Router with ALL-IN-1 STARTER, do not stop these processes. If any active processes are due to users logged in to the system, it is not advisable to continue, so press RETURN to halt VMSINSTAL, and ask the users to log out. Once the users have logged out, restart the installation procedure. STEP 4: System Backup VMSINSTAL displays: * Are you satisfied with the backup of your system disk [YES]? If you are not satisfied, enter NO, carry out a disk backup and restart the installation. If you are satisfied, press RETURN. STEP 5: Load the distribution media-Sequence 1 If you did not specify a device when invoking VMSINSTAL, the following message is displayed: * Where will the distribution volumes be mounted: Enter the device on which the media are to be mounted. You can use either a physical or logical device name. Logical device names must not begin with A1$ or OA$. 9-4 Steps Required for Installing ALL-IN-1 STARTER V2.4 If you did not specify the product identifier when invoking VMSINSTAL, the following message is displayed: Enter the products to be processed from the first distribution volume set: * Products: If you are performing a new, upgrade or update installation, enter the product identifier, AS024. If you are installing an additional language, or upgrading or updating an existing language, enter the product identifier, ASLlang024. If your system is running VMS Version 5.1, VMSINSTAL displays: * Options: If your system is running VMS Version 5.2 (or higher), VMSINSTAL displays: * Enter installation options you wish to use (none): Press RETURN to continue. If you are installing ALL-IN-1 STARTER Version 2.4 from magnetic tape or TK50 cartridge, VMSINSTAL displays: Please mount the first volume of the set on : * Are you ready? where : is the device you specified. Mount the first volume of the distribution media. _ For a new, upgrade or update installation, this is the volume labeled: ALL-IN-1 STARTER V2.4 BASE BIN media_type INTERNATIONAL BASE (c) 1990 Digital Equipment Corp. _ For an additional language installation, or an update of an existing language, this is the volume labeled: ALL-IN-1 STARTER V2.4 language BIN media_type LANGUAGE COMPONENT (c) 1990 Digital Equipment Corp. media_type is 16MT9 for tape and TK50 for a TK50 cartridge. (If you are unfamiliar with the loading of media, refer to the VMS software installation documentation.) Steps Required for Installing ALL-IN-1 STARTER V2.4 9-5 When you have mounted the volume, enter YES. VMSINSTAL tries to mount the distribution volume. If it succeeds, the following messages are displayed: _ If you are performing a new, upgrade or update installa- tion: %MOUNT-I-MOUNTED, AS1024 mounted on : The following products will be processed: AS V2.4 Beginning installation of AS V2.4 at %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. This is LOCAL ALL-IN-1 STARTER V2.4 BASE kit is the current time. _ If you are installing an additional language, upgrading or updating an existing language: %MOUNT-I-MOUNTED, AS3024 mounted on : The following products will be processed: ASL V2.4 Beginning installation of ASL V2.4 at %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. This is the LOCAL ALL-IN-1 STARTER V2.4 LANGUAGE-only kit is the current time. STEP 6: Indicate which type of installation you wish to perform Installation type: ...... _ If you are performing a new, upgrade or update installa- tion, VMSINSTAL displays: 9-6 Steps Required for Installing ALL-IN-1 STARTER V2.4 Using the FULL ALL-IN-1 STARTER V2.4 KIT, the following types of installation can be performed :- (1) First full installation of ALL-IN-1 STARTER (2) Upgrade of ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 (3) Update of ALL-IN-1 STARTER V2.4 (4) Installation of an additional language only (5) Upgrade of an additional existing ALL-IN-1 STARTER V1.0 language (6) Update of an additional existing ALL-IN-1 STARTER V2.4 language (7) Register licenses for pre-requisite software * What type of installation do you wish to perform [1]: Press RETURN to indicate a full installation of ALL-IN-1 STARTER Version 2.4. Otherwise, enter the number corresponding to the type of installation you want to perform. If you are upgrading or updating a multilingual ALL-IN-1 STARTER system, VMSINSTAL displays: ***CAUTION*** Your system has been configured as a MULTI-LINGUAL system. After you have upgraded your base system, you must also upgrade all additional language systems. You will not be able to use your additional language systems until they have been upgraded to the same version as your base system. The installation continues at STEP 7. However, you can use only the language that is being installed at this time. You must upgrade or update the remaining languages before you can use them. Also, you cannot run the Installation Verification Procedure for the additional languages until you have upgraded or updated them. If you are performing an upgrade or update installation, and the installation procedure could not find the file A1LINK.ANS, VMSINSTAL displays: %AS-E-NOANS, Could not find OA$BUILD:A1LINK.ANS ***CAUTION*** The installation could not determine the state of your system. If you have a MULTI-LINGUAL system you must upgrade all additional languages after you have upgraded your base system. You will not be able to use your additional language systems until they have been upgraded to the same version as your base system Steps Required for Installing ALL-IN-1 STARTER V2.4 9-7 The installation continues at STEP 7. However, if you are upgrading or updating from a multilingual system, you can use only the language that is being installed at this time. You must upgrade or update the remaining languages before you can use them. Also, you cannot run the Installation Verification Procedure for the additional languages until you have upgraded or updated them. Enter 7 to register the licenses. This option registers and loads the licenses for VAX FMS Version 2.4, Message Router Version 3.1B, Message Router VMSmail Gateway Version 3.1, CDA Converter Library Version 1.0, and VAX Notes Version 2.0. VMSINSTAL displays: %AS-I-CHKSWLIC, Checking licenses for prerequisite software %AS-I-CONFLICENSE. All necessary licenses are installed and loaded %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of AS V2.4 completed at VMSINSTAL procedure done at VMSINSTAL exits after registering the licenses. Before you install ALL-IN-1 STARTER Version 2.4, make sure that FMS, and if necessary, Message Router and Message Router VMSmail Gateway are running. _ If you are performing an additional language installation or updating an existing language, VMSINSTAL displays: Using the LANGUAGE only ALL-IN-1 STARTER V2.4 KIT, the following types of installation can be performed :- (1) Installation of an additional language only (2) Upgrade of an additional existing ALL-IN-1 STARTER V1.0 language (3) Update of an additional existing ALL-IN-1 STARTER V2.4 language * What type of installation do you wish to perform [1]: Press RETURN to indicate an additional language installa- tion. Otherwise, enter 2 to upgrade an existing ALL-IN-1 STARTER Version 1.0 additional language, or enter 3 to update an existing ALL-IN-1 STARTER Version 2.4 language. 9-8 Steps Required for Installing ALL-IN-1 STARTER V2.4 If you are performing an upgrade or update installation, VMSINSTAL searches for the default ALL-IN-1 STARTER image, OA$LIB_SHARE:OA$MAIN.EXE. If it does not find this image (because you have renamed the image), VMSINSTAL displays: The main ALL-IN-1 image OA$MAIN.EXE cannot be found using its default specification * Can you provide the full file specification of the main ALL-IN-1 image [YES]? Press RETURN if you know the full file specification of the main ALL-IN-1 STARTER image. VMSINSTAL displays: * What is the full file specification of the main ALL-IN-1 image: Enter the full file specification of the image (including the device and directory). If you do not know the full file specification, enter NO. VMSINSTAL exits. Find out the full file specification of your ALL-IN-1 STARTER image and start the installation again. If you are installing a full ALL-IN-1 STARTER Version 2.4 system, or are upgrading or updating an existing ALL-IN-1 STARTER system, you may be prompted to enter a market code at this point if you are installing ALL-IN-1 STARTER from disk. If you see this prompt go to STEP 8. If you are installing an additional language, you may be prompted to enter a language code at this point if you are installing the ALL-IN-1 STARTER language from disk. If you see this prompt go to STEP 9. If you are updating an existing language, you may be prompted to enter a language code at this point if you are installing the ALL-IN-1 STARTER language from disk. If you see this prompt go to STEP 9. STEP 7: Load the distribution media-Sequence 2 Mount the second volume of the distribution media. This is the volume labeled: Steps Required for Installing ALL-IN-1 STARTER V2.4 9-9 ALL-IN-1 STARTER V2.4 market BIN media_type MARKET COMPONENT (c) 1990 Digital Equipment Corp. _ market is the market name _ media_type is 16MT9 for tape and TK50 for a TK50 cartridge. See the ALL-IN-1 STARTER Installation Guide Part 3 Market Installation. The following messages are displayed: Media :AS1024 dismounted. (MEDIA CHANGE REQUIRED): Dismounted media labeled AS1024. Please mount the MARKET kit media which is labeled AS2024 and reply to the prompt below. (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? When you have mounted the volume, enter YES. VMSINSTAL tries to mount the distribution volume. If the distribution volume is mounted, the following messages are displayed: %MOUNT-I-MOUNTED, AS2024 mounted on : %ASC-I-RECOUK, Restoring the MARKET kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B . . . where is the market code (see the ALL-IN-1 STARTER Installation Guide Part 3 Market Installation). Mount the third volume of the distribution media. This is the volume labeled: ALL-IN-1 STARTER V2.4 language BIN media_type LANGUAGE COMPONENT (c) 1990 Digital Equipment Corp. _ language is the language name _ media_type is 16MT9 for tape and TK50 for a TK50 cartridge See the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation. The following messages are displayed: 9-10 Steps Required for Installing ALL-IN-1 STARTER V2.4 Media :AS2024 dismounted. (MEDIA CHANGE REQUIRED): Dismounted media labeled AS2024. Please mount the LANGUAGE kit media which is labeled AS3024 and reply to the prompt below. (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? When you have mounted the volume, enter YES. VMSINSTAL tries to mount the distribution volume. If the distribution volume is mounted, the following messages are displayed: %MOUNT-I-MOUNTED, AS3024 mounted on : %ASL-I-RELANK, Restoring the LANGUAGE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B . . . This is the version of ALL-IN-1 V2.4 where is the language being installed (see the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation). VMSINSTAL goes to STEP 10. STEP 8: Specify the market code required by this installation Market code: ...................... VMSINSTAL displays: * Enter market code for this installation (up to 3 characters) [US]: Press RETURN to accept the default, US. Otherwise, enter the market code required for your installation (see the ALL-IN-1 STARTER Installation Guide Part 3 Market Installation). VMSINSTAL displays the following: %ASC-I-RECOUK, Restoring the MARKET kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B . . . Steps Required for Installing ALL-IN-1 STARTER V2.4 9-11 STEP 9: Specify the language code required by this installation Language code: .............................. VMSINSTAL displays: *Enter language code for this installation (up to 9 characters) [ENGLISH]: Press RETURN to accept the default, ENGLISH. Otherwise, enter the language code required for your installation (see the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation). VMSINSTAL displays the following: %ASL-I-RELANK, Restoring the LANGUAGE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B . . . This is the version of ALL-IN-1 STARTER V2.4 STEP 10: Indicate whether you have registered and loaded your ALL-IN-1 STARTER Product Authorization Key Have you registered and loaded the PAK? ......... _ If you are installing ALL-IN-1 STARTER for the first time, or updating or upgrading a an ALL-IN-1 STARTER system, you must have a capacity or personal (subscriber) license registered _ If you have a capacity (ALLIN1-STARTER) license, and you want to install, update or upgrade an additional language, you must also have a language-specific capacity license, AI1-START-UI-language, where language is the name of the language you want to install _ If you have a personal (ALLIN1-STARTER-PERSONAL) license, you can install, update or upgrade an additional language, without a language-specific license VMSINSTAL displays: * Does this product have an authorization key registered and loaded [YES]? 9-12 Steps Required for Installing ALL-IN-1 STARTER V2.4 If you have not registered and loaded your product authoriza- tion key, you must answer NO to this question. VMSINSTAL then exits. A successful installation of ALL-IN-1 STARTER depends on a product authorization key being registered and loaded. Please be certain that this has been completed before proceeding with the installation. Press RETURN if you have a product authorization key registered and loaded for ALL-IN-1 STARTER Version 2.4. If the appropriate licenses are registered and loaded, VMSINSTAL displays: %LMF-I-GOTLICENSE, An license is installed and loaded where is: _ ALLIN1-STARTER or ALLIN1-STARTER-PERSONAL if you are installing ALL-IN-1 STARTER for the first time, or you are updating or upgrading a previous version of ALL-IN-1 STARTER. _ ALLIN1-STARTER-PERSONAL or AI1-START-UI-language if you are installing, updating, or upgrading an additional language VMSINSTAL then checks for all prerequisite software licenses: %LMF-I-CHKSWLIC, Checking licenses for prerequisite software If a license already exists, and the installation updates the license with a more up-to-date version, the following message is displayed: %LICENSE-I-ALREADYLOADED, has already been loaded is the name of the license that has been updated. If a license is not found, the license is registered then loaded, and the following message is displayed: %LICENSE-I-LOADED, was successfully loaded with units is the name of the license that has been updated and is the number of units for the license. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-13 When the licenses for all the prerequisite software have been checked and, if necessary, loaded, the following message is then displayed: %LMF-I-CONFLICENSE, All necessary licenses are installed and loaded If one or more of the required licenses are not registered and loaded, VMSINSTAL displays: %LMF-S-NOLICENSE, This product requires a license to install %LMF-S-NOLICENSE, Please refer to the ALL-IN-1 Installation Guide %LMF-E-RETRY1, Please correct any reported problem(s) before attempting %LMF-E-RETRY2, to install ALL-IN-1. %VMSINSTAL-E-INSFAIL, The installation of AS V2.4 has failed. VMSINSTAL procedure done at If you are performing a new installation, VMSINSTAL goes to STEP 12. If you are installing a new additional language, VMSINSTAL goes to STEP 15. STEP 11: Indicate whether or not you want to purge files replaced by this installation Do you want to purge files? ......... You can choose to have the files of your existing ALL-IN-1 STARTER system purged to save space on the disk(s) on which ALL-IN-1 STARTER Version 2.4 is being installed. If you are performing an upgrade or update installation, VMSINSTAL displays: * Do you want to purge files replaced by this installation? This installation creates new copies of ALL-IN-1 STARTER language files. You can purge the old copies of these files. Enter YES if you want to purge the old copies of these files. Otherwise, enter NO. If you are upgrading or updating an existing language, VMSINSTAL goes to STEP 17. 9-14 Steps Required for Installing ALL-IN-1 STARTER V2.4 STEP 12: Indicate whether or not you want to incorporate WPS-PLUS Do you want to incorporate WPS-PLUS? .......... VMSINSTAL displays: If you wish to have the WPS-PLUS editor available then answer YES to the following question. If you answer NO, then your users will not be able to access the WPS-PLUS editor. Note this will also impact SPELL and MERGE functions. NOTE: You will be able to link WPS-PLUS in at a later time, should you choose not to link it now. * Do you want to incorporate WPS-PLUS [YES]? If you want to incorporate WPS-PLUS (see Section 1.5.3), press RETURN. Otherwise, enter NO. Note If you decide not to incorporate WPS-PLUS at this time, you can incorporate WPS-PLUS at a later date by performing an update installation (see Appendix D for details). STEP 13: Check to see if the CDA Converter Library is installed VMSINSTAL displays: %ASL-I-DDIF, Checking CDA support software prerequisites If the logical name CDA$LIBRARY is defined and the CDA converter files are present (see Section 1.5.1), VMSINSTAL displays: %ASL-I-DDIF, CDA integration will be supported If the logical name CDA$LIBRARY does not exist, VMSINSTAL displays: %ASL-W-NOCDALIB, No CDA$LIBRARY logical was found * Do you want to continue anyway (without CDA support) [YES]? Press RETURN to continue the installation. Otherwise, enter NO. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-15 If the CDA Converter Library files are not installed, VMSINSTAL displays: %ASL-I-MISSING_CDA, The CDA converter files are not installed * Do you want to continue anyway (without CDA support) [YES]? Press RETURN to continue the installation. Otherwise, enter NO. If you want to have full CDA integration, the CDA library must be set up and the converter files installed. If they are not set up, and you require full integration, you may continue and install them after the installation of ALL-IN-1 STARTER. STEP 14: Indicate whether or not you want to build a multilingual system Do you want to build a multilingual system? .......... You can install an additional language to build a multilin- gual ALL-IN-1 STARTER system. See Section 1.7 for details. VMSINSTAL displays: If you answer YES to this then you will produce TWO images - OA$MAIN.EXE and OA$LLVlanguage.EXE. This will allow more than one language to be installed. * Do you want to build a MULTI-LANGUAGE system [NO]? Press RETURN if you do not want to install other languages. Otherwise, enter YES. You install each additional language after ALL-IN-1 STARTER Version 2.4 is installed, by performing an additional language installation (see Chapter 4). If you elect to build a multilingual system, the installation creates a language-specific image file, SYS$LIBRARY:OA$LLVlang.EXE, in addition to the OA$LIB_SHARE:OA$MAIN.EXE image file. Note The performance of ALL-IN-1 STARTER will suffer slightly if you configure ALL-IN-1 STARTER as a multilingual system (that is, if you enter YES at the prompt). If you are not sure whether or not you want to run a multilingual ALL-IN-1 STARTER system, you can choose to install ALL-IN-1 STARTER Version 2.4 as a single language system, and relink the 9-16 Steps Required for Installing ALL-IN-1 STARTER V2.4 ALL-IN-1 STARTER image at a later date for multilingual operation (see the ALL-IN-1 Management Guide for details). STEP 15: Select the date format to use with ALL-IN-1 STARTER Date format to use with ALL-IN-1 STARTER: .......... VMSINSTAL displays: ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis). This may be changed by user through the Set Working Conditions option. Alphanumeric Date Numeric Date 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD * Which date format do you require [1]: Press RETURN to select the default date format DD-MMM-YYYY MM/DD/YY. Otherwise, enter the number of the desired date format. See the ALL-IN-1 STARTER Installation Guide Part 3 Market Installation. If you are performing an additional language installation, VMSINSTAL goes to STEP 24. STEP 16: Specify the greatest number of simultaneous ALL-IN-1 STARTER users Greatest number of simultaneous ALL-IN-1 STARTER users: ............. VMSINSTAL displays: * What will be the greatest number of simultaneous ALL-IN-1 users: Steps Required for Installing ALL-IN-1 STARTER V2.4 9-17 Enter the number of users that you expect to use ALL-IN-1 STARTER at the same time. In a VAXcluster, this is the number of users on the node which has the greatest number of users. For example, if one node has 10 users and another node has 4 users, you should enter 10. VMSINSTAL then checks that the system parameter settings are sufficient. If your node is not on a cluster, simply enter the greatest number of users on the node. Note This will affect the system parameters (see Section 1.8). VMSINSTAL uses this information to allocate the correct number of global buffers to certain files in OA$DATA_SHARE (see Section 10.16). VMSINSTAL checks that the values of certain parameters are suitable. If the following system parameters are not adequate, you can complete the installation, but you may have to increase them, depending on the maximum number of simultaneous ALL-IN-1 STARTER users per node or satellite node (see the chapter on tuning ALL-IN-1 STARTER in the ALL-IN-1 Management Guide): _ LOCKIDTBL _ RESHASHTBL _ GBLPAGFIL If the following parameters are not adequate, you cannot proceed with the installation and must use the SYSGEN utility (see Section 1.8) to increase them, before attempting installation again: _ Number of unused global sections _ Number of unused global pages Note If you are running on a VAXcluster, the installation procedure can only check the SYSGEN parameters on the node on which it is running. You must ensure that they are large enough on all nodes in the cluster on which you intend to run ALL-IN-1 STARTER. 9-18 Steps Required for Installing ALL-IN-1 STARTER V2.4 STEP 17: Specify the batch queue to run the Sender and Fetcher Batch queue for sending and receiving mail: .......................... VMSINSTAL displays: * Which batch queue would you like to use for sending/receiving mail [SYS$BATCH]: If you are installing ALL-IN-1 STARTER on a multiple- environment cluster you must use a batch queue that runs only on the part of the cluster on which you are installing ALL-IN-1 STARTER (see Section 1.6.2). ALL-IN-1 STARTER uses one of your system batch queues to run the mail Sender and Fetcher. Press RETURN to use SYS$BATCH. Otherwise, specify the name of another batch queue that exists already or that you will create before you run ALL-IN-1 STARTER. If your system runs a local Message Router, you may consider using the Message Router queue MB$BATCH. Note Digital recommends that you use a dedicated batch queue for the mail Sender and Fetcher. STEP 18: Indicate whether or not you want to send and receive messages to and from other systems Do you want to send and receive messages to and from other systems? .......... See Section 1.5.2 to help you decide whether or not to integrate ALL-IN-1 STARTER with Message Router. VMSINSTAL displays: * Do you want to use Message Router to send/receive messages to/from other systems [NO]? Press RETURN if you do not want to send and receive electronic messages to and from other computer systems, or by way of the Message Router VMSmail Gateway to and from VMSmail. Otherwise, enter YES. If you respond NO to this prompt, VMSINSTAL goes to STEP 24. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-19 STEP 19: Indicate whether the Message Router you want ALL-IN-1 STARTER to use is on this node or another node Do you want to use a remote Message Router? .......... Note If you want to use Mail directory addressing (see Section 1.5.2.1), you must have Message Router Version 3.1B installed locally. VMSINSTAL displays: * Do you want to use a remote Message Router [NO]? If the Message Router you want to use is on another system (that is, you want to use a remote Message Router), enter YES. VMSINSTAL goes to STEP 20. Press RETURN if the Message Router you want to use is on this system. (This is normally the case.) If you press RETURN, and Message Router Version 3.1B is installed on this system, VMSINSTAL goes to STEP 21. Otherwise, VMSINSTAL goes to STEP 24 after displaying the following message: Message Router version incorrect or Message Router missing. Further Message Router questions will be omitted. If you did not start DECnet before starting the installation, VMSINSTAL displays: %AS-I-DCNTNOTINSTD1, DECNET has not been installed. %AS-I-DCNTNOTINSTD2, It must be installed for Mail directory support. %AS-I-DDSNOTSTRTD1, Mail directory service has not been started /or installed. %AS-I-DDSNOTSTRTD2, You cannot therefore use the Mail directory service. * Do you wish to continue without Mail directory support [YES]? Press RETURN if you want to continue. VMSINSTAL goes to STEP 22. Enter NO if you want to use the Mail directory. VMSINSTAL displays: * You are halting the installation - is this correct [NO]? Enter YES to abort the installation. Otherwise, press RETURN to continue. 9-20 Steps Required for Installing ALL-IN-1 STARTER V2.4 STEP 20: Specify the node whose Message Router you want to use Message Router node name: .................................... If you want to use a Message Router on another system, VMSINSTAL displays: * What node is the Message Router on: Enter the node name of the computer system whose Message Router you want to use. The following message is displayed: The Message Router mailbox name has been set up to be . If you wish to change the name you must create the file : OA$SITE_BUILD_SHARE:A1V24_SITE_START.COM Change the definition of the logical name OA$MTI_MAILBX and then when you run the MRMAN utility use this new name to define the mailbox. where is the name of ALL-IN-1 STARTER Message Router mailbox (usually A1). VMSINSTAL goes to STEP 23. STEP 21: Specify the level of use of the Mail directory Level of use of Mail directory: ........... To help you decide on the level of Mail directory support, see Section 1.5.2.1. If you chose to integrate with Message Router, and it is on this system, VMSINSTAL displays: * What level of Mail directory support do you want [0/1/2] [0]: Enter 0 if you do not want to use Mail directory addressing. VMSINSTAL goes to STEP 22. Enter 1 if you want to use ALL-IN-1 STARTER directory addressing as the primary directory. The Mail directory can still be accessed from the Message Header menu. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-21 Enter 2 if you want to use Mail directory addressing as the primary directory. ALL-IN-1 STARTER directory addressing can still be accessed from the Message Header menu. If you are performing an update installation, and your ALL-IN-1 STARTER system currently uses a local Message Router with Mail directory support (that is, OA$DDS_PRIME is set to 1 or 2), VMSINSTAL displays the following message, and then continues at STEP 22: As this is an update you will not be asked for a Mail directory password If you are performing a new installation, or your ALL-IN-1 STARTER system currently uses a local Message Router without Mail directory support (that is, OA$DDS_PRIME is set to 0), VMSINSTAL displays: * Enter password for the Mail directory user agent account: Enter the password for the Mail directory user agent entry (minimum six characters, maximum eight characters). VMSINSTAL asks you to confirm the password: * Please confirm the Mail directory password specified: Enter the password again. STEP 22: Specify the password for the ALL-IN-1 STARTER Message Router mailbox If you are performing an upgrade or update installation, and your ALL-IN-1 STARTER system currently uses a local Message Router, VMSINSTAL displays the following message, and then continues at STEP 23: As this is an update you will not be asked for a Message Router password If you are performing a new installation, or your ALL-IN-1 STARTER system does not currently use a local Message Router, VMSINSTAL displays: * What password do you want to use for the Message Router mailbox: 9-22 Steps Required for Installing ALL-IN-1 STARTER V2.4 Enter the password (minimum 8 characters, maximum 32 characters). VMSINSTAL asks you to confirm this password: * Please confirm the password you have specified: Enter the password again. VMSINSTAL sets up this password. This password must then be supplied by any processes that want to connect to the ALL-IN-1 Message Router mailbox. When VMSINSTAL sets up this password, the following message may be displayed: %Could not add entry from MRMAN where is the name of ALL-IN-1 STARTER Message Router mailbox (usually A1). This message means that the mailbox for ALL-IN-1 STARTER is already set up in the Message Router Transfer Service database, and although the mailbox password has been changed in your ALL-IN-1 STARTER database, it has not been changed in the Message Router Transfer Service database. If this happens, you must run the Transfer Service Management utility, MRMAN, to change the mailbox password in the Message Router Transfer Service database (see the ALL-IN-1 Mail Management Guide) after the installation has completed. STEP 23: Indicate whether or not you want to translate outgoing WPS-PLUS and DX messages to ASCII Translate outgoing WPS-PLUS and DX messages to ASCII? ............ VMSINSTAL displays: * Do you want to translate outgoing WPS-PLUS and DX messages to ASCII [NO]? Enter YES if: Your users will be sending messages to DECmail. However, if your users send messages to DECmail users occasionally, you may want to enter NO, and ask your users to use EDT to send to DECmail if necessary. If you answer YES to this prompt, all messages will be translated to ASCII, whether or not they are sent to DECmail users. or: Steps Required for Installing ALL-IN-1 STARTER V2.4 9-23 Your users will be sending messages to VMSmail through Version 2.0 or an earlier version of the Message Router VMSmail Gateway. This situation may occur if you are using a remote Message Router VMSmail Gateway. ALL-IN-1 STARTER will then convert any outgoing messages to ASCII. If your users will not be sending messages to DECmail, or your ALL-IN-1 STARTER system will use Version 2.1 of the Message Router VMSmail Gateway, or higher, press RETURN. ALL-IN-1 STARTER will then exchange any messages in the same form in which they were created. STEP 24: Check the Mandatory and Optional Software Prerequisites VMSINSTAL carries out various checks at this stage. If you are not installing an additional language, VMSINSTAL displays: %ASL-I-CHKSWPR, Checking MANDATORY and OPTIONAL SW prerequisites %ASL-I-CHKQUOT, Checking process quotas for the current process If you are installing an additional language, VMSINSTAL displays: %ASL-I-CHKSWPR, Checking MANDATORY SW prerequisites If you are performing an upgrade or update installation, VMSINSTAL displays: %ASL-I-CHKLNAM, Checking ALL-IN-1 logical names If you are not installing an additional language, VMSINSTAL displays: %ASL-I-CHKIDNT, Checking ALL-IN-1 general identifiers VMSINSTAL checks that the identifier OA$ADMIN does not exist. This identifier is used for the ALL-IN-1 STARTER administrator and must be used only with ALL-IN-1 STARTER. If you have created this identifier for something other than ALL-IN-1 STARTER, you must rename your existing OA$ADMIN identifier. 9-24 Steps Required for Installing ALL-IN-1 STARTER V2.4 Note OA$ADMIN allows access to ALL-IN-1 STARTER files that are not normally accessible to non-privileged users. VMSINSTAL also checks that the identifier OA$PRVAPP does not exist. This identifier is used for ALL-IN-1 STARTER application programmers and must be used only with ALL-IN-1 STARTER. If you have created this identifier for something other than ALL-IN-1 STARTER, you must rename your existing OA$PRVAPP identifier. If the OA$ADMIN identifier exists, and you are performing an upgrade or update installation, VMSINSTAL displays: %ASL-I-GENIDOK, General identifier OA$ADMIN will be used from the previous installation. If the OA$ADMIN identifier exists, and you are performing a new installation, VMSINSTAL displays information relating to OA$ADMIN, together with the prompt: * Do you want to use the existing general identifier OA$ADMIN [YES]? Enter NO if your existing OA$ADMIN identifier is used for something other than ALL-IN-1 STARTER. In this case, the installation will fail after all other checks have been made. Press RETURN if you are sure that: _ The OA$ADMIN identifier is created only for ALL-IN-1 STARTER _ There are no holders of this identifier outside ALL-IN-1 STARTER _ This identifier is not specified in any Access Control List (ACL) outside ALL-IN-1 STARTER If the OA$PRVAPP identifier exists, and you are performing an upgrade or update installation, VMSINSTAL displays: %ASL-I-GENIDOK, General identifier OA$PRVAPP will be used from the previous installation. If the OA$PRVAPP identifier exists, and you are performing a new installation, VMSINSTAL displays information relating to OA$PRVAPP, together with the prompt: * Do you want to use the existing general identifier OA$PRVAPP [YES]? Steps Required for Installing ALL-IN-1 STARTER V2.4 9-25 Enter NO if your existing OA$PRVAPP identifier is used for something other than ALL-IN-1 STARTER. In this case, the installation will fail after all other checks have been made. Press RETURN if you are sure that: _ The OA$PRVAPP identifier is created only for ALL-IN-1 STARTER _ There are no holders of this identifier outside ALL-IN-1 STARTER _ This identifier is not specified in any ACL outside ALL-IN-1 STARTER If you are not installing an additional language, VMSINSTAL displays: %ASL-I-CHKTRAC, Checking ALL-IN-1 transfer accounts If you are performing an installation, and the accounts A1$XFER_IN and A1$XFER_OUT already exist, the following is displayed: VMS account named A1$XFER_IN, which should be used for ALL-IN-1 purposes only, was already created before this installation. You have two options: 1. Answer YES if you want the existing A1$TRANSFER account to be used for ALL-IN-1 pruposes ONLY. Note that in this case, some characterists of the account (e.g. UIC, PASSWORD, ACCESS type) may be changed during the installation. 2. Answer NO to stop the installation, correct the problem and then start again. * Do you want to use the existing A1$XFER_IN account [YES]? Press RETURN if you do not want to use the existing TRANSFER_ INCOMING account. Enter YES to continue. VMSINSTAL displays: VMS account named A1$XFER_OUT, which should be used for ALL-IN-1 purposes only, was already created before this installation. You have two options: 9-26 Steps Required for Installing ALL-IN-1 STARTER V2.4 1. Answer YES if you want the existing A1$TRANSFER account to be used for ALL-IN-1 pruposes ONLY. Note that in this case, some characterists of the account (e.g. UIC, PASSWORD, ACCESS type) may be changed during the installation. 2. Answer NO to stop the installation, correct the problem and then start again. * Do you want to use the existing A1$XFER_OUT account [YES]? Press RETURN if you do not want to use the existing TRANSFER_ OUTGOING account. Enter YES to continue. VMSINSTAL displays: %ASL-I-CHKVMSV, Checking VAX/VMS version %ASL-I-CHKLIBS, Checking required shareable libraries are installed %ASL-I-CHKFMSV, Checking VAX/FMS version %ASL-I-CHKMROV, Checking Message Router version For all installations, VMSINSTAL displays: %ASL-I-CHKPARA, Checking system parameters If no errors are detected, the installation continues. If you are upgrading your current ALL-IN-1 STARTER system to ALL-IN-1 STARTER Version 2.4, VMSINSTAL goes to STEP 32. If you are updating your existing ALL-IN-1 STARTER Version 2.4 system, or ALL-IN-1 STARTER Version 2.4 system to ALL-IN- 1 STARTER Version 2.4, VMSINSTAL goes to STEP 32. If you are performing an additional language installation, VMSINSTAL goes to STEP 27. If any software checks fail, VMSINSTAL displays: During the check phase following errors are discovered: SHAREABLE LIBRARY FILES: Shareable library file is NOT installed. . . . MESSAGE FILES: Message file is NOT installed. . . . Steps Required for Installing ALL-IN-1 STARTER V2.4 9-27 This installation will fail due to mismatched software prerequisites. However, you may continue and check the DISK SPACE requirements before the installation procedure terminates. Otherwise, stop the installation here and correct the reported problems before starting again. * Do you want to continue [YES]? is the number of sofware errors detected, and is the name of the file that is not installed. Press RETURN to continue to check the disk space require- ments. VMSINSTAL goes to STEP 27, after which VMSINSTAL aborts. Enter NO if you do not want to continue. VMSINSTAL displays: %ASL-E-RETRY1, Please correct any reported problem(s) before attempting %ASL-E-RETRY2, to install ALL-IN-1. %VMSINSTAL-E-INSFAIL, The installation of AS V2.4 has failed. VMSINSTAL procedure done at You must correct the error(s) and install ALL-IN-1 STARTER Version 2.4 again. Check the prerequisites given in Chapter 1. STEP 25: Specify the device to hold the ALL-IN-1 STARTER shared library files Device to hold shared library files: ................................. VMSINSTAL displays: * Which device will hold the ALL-IN-1 shared library files [SYS$SYSDEVICE:]: Enter the logical name of the device to hold the ALL-IN-1 STARTER shared library files in OA$LIB. Press RETURN to accept the default of SYS$SYSDEVICE:. You can use either a physical or logical device name. Digital recommends that you use a logical name for the device as users do not have to be concerned with the physical location of the volumes. Do not use a logical name that points to a search list. For example, do not use SYS$SYSROOT, SYS$SPECIFIC, or SYS$COMMON. Also, logical device names must not begin with A1$ or OA$. 9-28 Steps Required for Installing ALL-IN-1 STARTER V2.4 If you enter an incorrect device specification, the following prompt is displayed: %ASL-W-NODEVICE, That device doesn't exist on your system * Do you want to select another device to hold the ALL-IN-1 LIB_SHARE files ? [NO]? If you answer YES, VMSINSTAL displays: * Which device will hold the ALL-IN-1 shared library files : Enter the logical name of the device to hold the ALL-IN-1 STARTER shared library files in OA$LIB. If there is insufficient disk space for the shared library files, VMSINSTAL displays: There is NOT enough diskspace on : to provide LIB_SHARE files. Please provide AT LEAST free blocks more on : and restart the installation, or choose another device to transfer LIB_SHARE files. * Do you want to select another device to hold the ALL-IN-1 LIB_SHARE files ? [NO]? Enter YES to select another device. VMSINSTAL prompts you to enter the logical name of the device. Press RETURN if you do not want to select another device. STEP 26: Specify the device to hold the ALL-IN-1 STARTER shared data files Device to hold shared data files: .................................. VMSINSTAL displays: * Which device will hold the ALL-IN-1 shared data files [:]: Enter the logical name of the device to hold the ALL-IN-1 STARTER shared data files in OA$DATA. Press RETURN to accept the default device which you specified at STEP 25. You can use either a physical or logical device name. Digital recommends that you use a logical name for the device as users do not have to be concerned with the physical location of the volumes. Do not use a logical name that points to a search list. For example, do not use SYS$SYSROOT, Steps Required for Installing ALL-IN-1 STARTER V2.4 9-29 SYS$SPECIFIC, or SYS$COMMON. Also, logical device names must not begin with A1$ or OA$. If you enter an incorrect device specification, the following prompt is displayed: %ASL-W-NODEVICE, That device doesn't exist on your system * Do you want to select another device to hold the ALL-IN-1 DATA_SHARE files ? [NO]? Enter YES to select another device. VMSINSTAL displays: * Which device will hold the ALL-IN-1 shared data files : Enter the logical name of the device to hold the ALL-IN-1 STARTER shared data files in OA$DATA. If there is insufficient disk space for the shared data files, VMSINSTAL displays: There is NOT enough diskspace on : to provide DATA_SHARE files. Please provide AT LEAST free blocks more on : and restart the installation, or choose another device to transfer DATA_SHARE files. * Do you want to select another device to hold the ALL-IN-1 DATA_SHARE files ? [NO]? Enter YES to select another device. VMSINSTAL prompts you to enter the logical name of the device. Press RETURN if you do not want to select another device. STEP 27: Specify the device to hold the ALL-IN-1 STARTER language files Device to hold the language files: .................................. VMSINSTAL displays: * Which device will hold the ALL-IN-1 language files [:]: Enter the logical name of the device to hold the ALL-IN-1 STARTER language files for the language being installed. Otherwise, press RETURN to accept the default: If you are performing a new installation, the default device is that which you specified at STEP 26. 9-30 Steps Required for Installing ALL-IN-1 STARTER V2.4 If you are performing an additional language installation, the default device is SYS$SYSDEVICE. You can use either a physical or logical device name. Digital recommends that you use a logical name for the device as users do not have to be concerned with the physical location of the volumes. Do not use a logical name that points to a search list. For example, do not use SYS$SYSROOT, SYS$SPECIFIC, or SYS$COMMON. Also, logical device names must not begin with A1$ or OA$. If you enter an incorrect device specification, the following prompt is displayed: %ASL-W-NODEVICE, That device doesn't exist on your system * Do you want to select another device to hold the ALL-IN-1 LLV files ? [NO]? Enter YES to select another device. VMSINSTAL displays: * Which device will hold the ALL-IN-1 language files : Enter the logical name of the device to hold the ALL-IN-1 STARTER language files for the language being installed. If you are performing an additional language installation, VMSINSTAL goes to STEP 32. If there is insufficient disk space for the language files, VMSINSTAL displays: There is NOT enough diskspace on : to provide LLV files. Please provide AT LEAST free blocks more on : and restart the installation, or choose another device to transfer LLV files. * Do you want to select another device to hold the ALL-IN-1 LLV files ? [NO]? Enter YES to select another device. VMSINSTAL prompts you to enter the logical name of the device. Press RETURN if you do not want to select another device. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-31 STEP 28: Specify the device to use for the ALL-IN-1 STARTER mail area SDAF file, OA$DATA:OA$DAF_E.DAT Device to hold Mail area SDAF file: .................................. ALL-IN-1 STARTER Version 2.4 allows you to have up to five mail areas (A to E). Each mail area consists of an SDAF and a number of shared directories. The installation of ALL-IN-1 STARTER Version 2.4 creates mail area E. That is, the SDAF file OA$DAF_E.DAT and shared directories SHAREnnnn are created, where nnnn is a number in the range 1 to 9999. VMSINSTAL displays: * Which device will hold the ALL-IN-1 mail area SDAF file [:]: Enter the logical name of the device you would like to use for the ALL-IN-1 STARTER mail area SDAF file. Press RETURN to accept the default device which you specified at STEP 27. You can use either a physical or logical device name. Digital recommends that you use a logical name for the device as users do not have to be concerned with the physical location of the volumes. Do not use a logical name that points to a search list. For example, do not use SYS$SYSROOT, SYS$SPECIFIC, or SYS$COMMON. Also, logical device names must not begin with A1$ or OA$. If you enter an incorrect device specification, the following prompt is displayed: %ASL-W-NODEVICE, That device doesn't exist on your system * Do you want to select another device to hold the ALL-IN-1 mail area SDAF file ? [NO]? Enter YES to select another device. VMSINSTAL displays: * Which device will hold the ALL-IN-1 mail area SDAF file : Enter the logical name of the device you would like to use for the ALL-IN-1 STARTER mail area SDAF file. If there is insufficient disk space for the mail area SDAF file, VMSINSTAL displays: 9-32 Steps Required for Installing ALL-IN-1 STARTER V2.4 There is NOT enough diskspace on : to provide SDAF files. Please provide AT LEAST free blocks more on : and restart the installation, or choose another device to transfer SDAF files. * Do you want to select another device to hold the ALL-IN-1 mail area SDAF file ? [NO]? Enter YES to select another device. VMSINSTAL prompts you to enter the logical name of the device. Press RETURN if you do not want to select another device. STEP 29: Indicate how many shared directories you would like Number of shared directories: ............... If you want to create more than 10 shared directories, Digital recommends that you select the default of 1. You can create the remaining number of shared directories after ALL-IN-1 STARTER Version 2.4 is installed (see the chapter on managing mail areas in the ALL-IN-1 Management Guide). The reason for this is that it is much quicker to create additional shared directories using the option provided in the management subsystem of ALL-IN-1 STARTER Version 2.4. Note that the number of shared directories cannot exceed 9999. ALL-IN-1 STARTER uses the shared directories in rotation. VMSINSTAL displays: * How many shared directories do you want to create [1]: Enter the number of shared directories you would like to create. If you want to use only one directory, press RETURN. STEP 30: Specify a device for each shared directory Device for each shared directory: Steps Required for Installing ALL-IN-1 STARTER V2.4 9-33 ........................... .............................. ........................... .............................. ........................... .............................. ........................... .............................. ........................... .............................. If possible, Digital recommends that you spread the shared directories across several disks. This improves the performance of ALL-IN-1 STARTER. VMSINSTAL asks for the device name for each shared directory as follows: * What device would you like to use for shared directory SHARE []: is in the range one to the number you specified in STEP 29, and represents the device you entered either in STEP 28 or for the previous shared directory. Enter the device required. This question is repeated until you have answered it for all the shared directories you specified. You can use either a physical or logical device name. Digital recommends that you use a logical name for the device as users do not have to be concerned with the physical location of the volumes. Logical device names must not begin with A1$ or OA$. If you enter an incorrect device specification, the following prompt is displayed: %ASL-W-NODEVICE, That device doesn't exist on your system * Do you want to select another device to hold the shared file cabinet SHARE ? [NO]? Enter YES to select another device. VMSINSTAL displays: * Which device will hold the ALL-IN-1 shared directory SHARE : Enter the device required. This question is repeated until you have answered it for all the shared directories you specified. 9-34 Steps Required for Installing ALL-IN-1 STARTER V2.4 If there is insufficient disk space for the shared directo- ries, VMSINSTAL displays: There is NOT enough diskspace on : to create shared area SHARE please provide AT LEAST free blocks more on : and restart the installation, or choose another device to create shared area SHARE. * Do you want to select another device to create shared file cabinet SHARE [NO]? Enter YES to select another device. VMSINSTAL prompts you to enter the logical name of the device. Press RETURN if you do not want to select another device. If all disk space prerequisites are satisfied, VMSINSTAL displays: NO missing DISK SPACE prerequisites discovered. If any errors were found during the software checks (STEP 24), VMSINSTAL displays: %ASL-E-RETRY1, Please correct any reported problem(s) before attempting %ASL-E-RETRY2, to install ALL-IN-1. %VMSINSTAL-E-INSFAIL, The installation of AS V2.4 has failed. VMSINSTAL procedure done at STEP 31: Identify or create a VMS account for ALL-IN-1 STARTER VMS user name for ALL-IN-1 STARTER manager's account: .......................... ALL-IN-1 STARTER needs a VMS account for running the ALL-IN-1 STARTER management batch jobs. This VMS account has three ALL-IN-1 STARTER accounts: _ MANAGER This account allows you to perform the ALL-IN-1 STARTER management tasks. _ POSTMASTER This account is used for running the mail Sender and Fetcher. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-35 _ IVP This account allows you or the installation procedures to run the installation verification procedures (IVPs). The ALL-IN-1 STARTER VMS account must have the following privileges: SYSPRV, SYSNAM, NETMBX, GRPNAM, OPER, TMPMBX, CMKRNL, EXQUOTA, WORLD, PRMMBX, PRMGBL, and SYSGBL. In addition, the account must have the same VMS process quotas as other ALL-IN-1 STARTER users (see Section 1.8). Note If your system is running VMS Version 5.2, or higher, the ALL-IN-1 STARTER manager's VMS account is created with the NODISUSER flag. If you are performing a new installation, VMSINSTAL displays: * What VMS username do you want to use for ALL-IN-1 MANAGER account? []: Press RETURN to use the default name ALLIN1. Otherwise, enter the name you want to use. Refer to the VMS manual describing the Authorize Utility for a list of valid characters that can be used for the user name. If the account does not exist, VMSINSTAL goes to STEP 33. STEP 32: Indicate the existing VMS username for the ALL-IN-1 STARTER account If you are performing an upgrade or update installation, or an additional language installation, VMSINSTAL displays: * What is the existing VMS username for the ALL-IN-1 MANAGER account [ALLIN1]: Press RETURN to use the default name ALLIN1. Otherwise, enter the name you want to use. Refer to the VMS manual describing the Authorize Utility for a list of valid characters that can be used for the user name. Details of the ALL-IN-1 STARTER account are displayed if you are: _ Performing a new installation and the account already exists _ Performing an upgrade installation 9-36 Steps Required for Installing ALL-IN-1 STARTER V2.4 _ Performing an update installation _ Installing an additional language _ Updating an existing language The details displayed are as follows: OWNER = USERNAME = UIC = ACCOUNT = PRIVS = PRIORITY = DIRECTORY = Also, the following prompt is displayed: * Are you sure all the specified account's characteristics are correct? [YES]? Press RETURN if you want to use this account. VMSINSTAL: _ Goes to STEP 34 if you are performing a new installation, and you created an ALL-IN-1 STARTER account before starting the installation _ Goes to STEP 34 if you are performing an upgrade installation _ Goes to STEP 43 if you are performing an update installa- tion _ Goes to STEP 40 if you are installing an additional language _ Goes to STEP 43 if you are updating an existing language Enter NO if you do not want to use this account. VMSINSTAL prompts you again for the username. Enter the username. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-37 STEP 33: Specify the password for the ALL-IN-1 STARTER manager's VMS account If VMSINSTAL is to create a VMS account for ALL-IN-1 STARTER, it prompts you for a password: * What password do you want to use for ALL-IN-1 MANAGER account: Since this account is privileged, choose a password that is not easy to guess. The password you specify is checked by VMSINSTAL to ensure that it does not contain any obvious character strings; for example "ALLIN1". (Two VMS accounts, A1$XFER_IN and A1$XFER_OUT, are created during the installation with the password that you specify here.) You are then asked to confirm the password. Enter your password again. VMSINSTAL goes to STEP 35. STEP 34: Specify the password for the ALL-IN-1 STARTER transfer user accounts Two VMS accounts, A1$XFER_IN and A1$XFER_OUT, are created. These accounts are used for transferring users to other systems. ALL-IN-1 STARTER logs in to these accounts, which are on the same disk as the ALL-IN-1 STARTER manager's account. VMSINSTAL displays: * What password do you want to use for the ALL-IN-1 TRANSFER accounts: Enter the password that you want to use for the Transfer User accounts. (The password is used for both accounts.) You are asked to confirm the password as follows: * Please confirm the password you have specified: Enter the password again. If you are performing an upgrade installation, VMSINSTAL goes to STEP 37. 9-38 Steps Required for Installing ALL-IN-1 STARTER V2.4 STEP 35: Specify the UIC for the ALL-IN-1 STARTER manager's VMS account UIC: [___________ , ___________] VMSINSTAL displays: * What UIC do you want to use for ALL-IN-1 MANAGER account : where is the name of the ALL-IN-1 STARTER manager's VMS account that you specified in STEP 31. You must enter a unique UIC, with a system group number. Note All the ALL-IN-1 STARTER shared library files, shared data files, and shared documents are owned by this UIC. Therefore, if disk quota checking is enabled on any of the devices used for ALL-IN-1 STARTER areas, this UIC must have a suitably large quota. If you enter an invalid UIC, VMSINSTAL displays: To be classified as a System UIC group member, the ALL-IN-1 manager's account must have the group number in the range 1 through . If you do not want to continue with this installation then answer NO to the next question. * Do you want to select another UIC value: where is the maximum group number for a system UIC (MAXSYSGROUP) defined on your system. The default is 10. Enter NO if you do not want to enter another UIC value. VMSINSTAL aborts. Enter YES if you want to enter another UIC value. VMSINSTAL prompts you to enter another UIC. STEP 36: Specify the device and directory for the ALL-IN-1 STARTER manager's VMS account Device for the ALL-IN-1 STARTER manager's account: ............................... Directory for the ALL-IN-1 STARTER manager's account: .................................. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-39 VMSINSTAL displays: * What default device do you want for the ALL-IN-1 Manager's account? [SYS$SYSDEVICE:]: Press RETURN to use the default SYS$SYSDEVICE:. Otherwise, enter the name. You can use either a physical or logical device name. Logical device names must not begin with A1$ or OA$. The following prompt is displayed: * What default directory do you want to use for ALL-IN-1 Manager's account? []: Press RETURN to use the default directory [ALLIN1]. If you want to use a different directory, enter the name of the directory. STEP 37: Specify the UICs for the ALL-IN-1 STARTER transfer user accounts A1$XFER_IN UIC: [___________ , ___________] A1$XFER_OUT UIC: [___________ , ___________] If the transfer user accounts do not exist, VMSINSTAL displays: * What UIC do you want for the A1$XFER_IN account?: Enter a non-system UIC for the account. If you enter an unacceptable UIC, the following message is displayed: %ASLlang-I-GRPLIM1, User Interface Component group number must be an octal number greater %ASLlang-I-GRPLIM2, than and less than 37776. where is the value that you entered and is the maximum group number for a system User Interface Component (SYSGEN parameter MAXSYSGROUP) defined on your system. You are prompted to enter the User Interface Component again. 9-40 Steps Required for Installing ALL-IN-1 STARTER V2.4 VMSINSTAL displays: * What UIC do you want for the A1$XFER_OUT account?: Enter a non-system UIC for the account. If you enter an unacceptable UIC, the following message is displayed: %ASLlang-I-GRPLIM1, User Interface Component group number must be an octal number greater %ASLlang-I-GRPLIM2, than and less than 37776. where is the value that you entered and is the maximum group number for a system User Interface Component (SYSGEN parameter MAXSYSGROUP) defined on your system. You are prompted to enter the User Interface Component again. The UIC for each of these accounts need not have the same system group number. If the transfer user accounts already exist, the UICs of the transfer user accounts are checked. If the UICs are system UICs, the following prompt is displayed: UIC must be between and 377776 * Do you want to select another UIC for account [YES]? where is the UIC of the existing transfer user account, is max_sys_group + 1 (max_sys_group is the highest system group UIC), and is the name of the transfer user account (that is, A1$XFER_IN or A1$XFER_OUT). If you are performing a new installation, and you created an ALL-IN-1 STARTER account before starting the installation, VMSINSTAL goes to STEP 43. If you are performing an upgrade installation, VMSINSTAL goes to STEP 43. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-41 STEP 38: Specify the directory to hold the shared library files, in OA$LIB Directory for the shared library files: .............................. VMSINSTAL asks you for the name of the directory to hold the shared library files: * Enter ALL-IN-1 top-level directory required for the shared library files []: Press RETURN to use the default directory , where is the name of the ALL-IN-1 STARTER account you specified at STEP 36. Otherwise, enter the name of the directory. STEP 39: Specify the directory to hold the shared data files, in OA$DATA Directory for the shared data files: ................................. VMSINSTAL asks you for the name of the directory to hold the shared data files: * Enter ALL-IN-1 top-level directory required for the shared data files []: Press RETURN to use the default directory which you specified at STEP 38. Otherwise, enter the name of the directory. STEP 40: Specify the directory to hold the language files Directory for the language files: .................................. VMSINSTAL asks you for the name of the directory to hold the language files, where is the language that you are installing. _ If you are performing a new installation, VMSINSTAL displays: * Enter ALL-IN-1 top-level directory required for all language files []: 9-42 Steps Required for Installing ALL-IN-1 STARTER V2.4 Press RETURN to use the default directory which you specified at STEP 39. Otherwise, enter the name of the directory. _ If you are performing an additional language installation, VMSINSTAL displays: * Enter ALL-IN-1 sub-directory required for the language files []: Press RETURN to use the default directory [ALLIN1]. Otherwise, enter the name of the directory. VMSINSTAL goes to STEP 43. STEP 41: Specify the directory to hold the mail area SDAF file OA$DATA:OA$DAF_E.DAT Directory for the Mail area SDAF file: .............................. VMSINSTAL asks you for the name of the directory to hold the SDAF file: * Enter ALL-IN-1 top-level directory required for the mail area SDAF file []: Press RETURN to use the default directory which you specified at STEP 40. Otherwise, enter the name of the directory. STEP 42: Specify the directory to hold the shared directories Directory to hold the shared directories on each device: Device Directory ........................... .............................. ........................... .............................. ........................... .............................. ........................... .............................. ........................... .............................. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-43 VMSINSTAL asks for the directory names to hold the shared directories on each device specified in STEP 30: * Enter the name required for the SHARED DIRECTORY on :? []: Press RETURN to select the default directory. Otherwise, enter the directory required. This question is repeated until you have answered it for all the devices you specified. STEP 43: Indicate whether or not you want to run the IVPs Do you want to run the IVPs? .......... VMSINSTAL displays: * Do you want to run the IVP after the installation [YES]? Enter NO if you do not want to run the IVP after the installation. Press RETURN if you want to run the IVP after the instal- lation. The IVP is run automatically at the end of the installation. Any messages output by the IVP are either printed on your hardcopy terminal or inserted into the log file, depending on your choice of media for the log of the installation. Note Digital recommends that you run the IVP after installation. VMSINSTAL displays the following message: %ASL-I-ASKDONE, All questions have now been completed. %ASL-I-SOMTIME, The installation will now continue for some time. No further action is required. If you are upgrading from ALL-IN-1 STARTER Version 1.0, and the installation is being performed in Safety mode, the following message is displayed: File [.DATA_SHARE]PROFILE.DAT prepared to be renamed to [.DATA_SHARE]V23_PROFILE.DAT The ALL-IN-1 STARTER Version 1.0 file, PROFILE.DAT, is renamed to V23_PROFILE.DAT at a later stage of the installation. 9-44 Steps Required for Installing ALL-IN-1 STARTER V2.4 If you are upgrading from ALL-IN-1 STARTER Version 1.0, and the installation is being performed in Non-Safety mode, the ALL-IN-1 STARTER Version 1.0 file, PROFILE.DAT, is renamed to V23_PROFILE.DAT and the following message is displayed: File [.DATA_SHARE]PROFILE.DAT renamed to [.DATA_SHARE]V23_PROFILE.DAT If you were asked to enter a language code (see STEP 10), VMSINSTAL goes to STEP 45. If you are installing an additional language, or upgrading or updating an existing language, VMSINSTAL goes to STEP 45. STEP 44: Load the distribution media-Sequence 3 VMSINSTAL displays: %ASL-I-ONEMEDEX, One more media exchange required, before installation can continue unaided. %VMSINSTAL-I-RESTORE, Restoring product saveset C . . . . . . There may be a delay of up to two hours, depending on the configuration of your system, before the media change is required. VMSINSTAL then displays the following: Media :AS3024 dismounted. (MEDIA CHANGE REQUIRED): Dismounted media labeled AS3024. Please mount the BASE kit media which is labeled AS1024 and reply to the prompt below. (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? Mount the first volume of the distribution media again. This is the volume labeled: ALL-IN-1 STARTER V2.4 BASE BIN media_type INTERNATIONAL BASE (c) 1990 Digital Equipment Corp. media_type is 16MT9 for tape and TK50 for a TK50 cartridge. When you have mounted the volume, enter YES. VMSINSTAL tries to mount the distribution volume. If it succeeds, the following message is displayed: Steps Required for Installing ALL-IN-1 STARTER V2.4 9-45 %MOUNT-I-MOUNTED, AS1024 mounted on : %AS-I-MEDEXCH, Media changed from ASL024, to AS024 %VMSINSTAL-I-RESTORE, Restoring product saveset B . . . . . . where is the language being installed. STEP 45: Wait for the installation to complete VMSINSTAL has now obtained all the information it requires. VMSINSTAL displays: %AS-I-A1LINK, Starting to link images The installation proceeds unassisted. It displays messages as it completes tasks or runs into difficulties. The installation may take several hours, depending on the size and load of the system you are using. If you chose to run the IVPs, the IVPs run at the end of the installation. If you chose to integrate WPS-PLUS, the spell check facility is installed with it. If you also chose to run the IVP for this facility, the IVP runs at the end of the installation. If the IVPs are run at the end of the installation, and they are successful, the following message is displayed: %ASIVP-I-IVPPASS, The IVPs for A1STARTER V2.4 have passed. STEP 46: Complete installation When VMSINSTAL has finished installing ALL-IN-1 STARTER, it displays: Installation of AS V2.4 completed at 9-46 Steps Required for Installing ALL-IN-1 STARTER V2.4 If you invoked VMSINSTAL without specifying any parameters (see STEP 1), VMSINSTAL displays: Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at is the current time. Enter EXIT, or press CTRL/Z to exit from VMSINSTAL. 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 must log out and log in again. Carry out the tasks described in Chapter 10 to set up ALL-IN-1 STARTER ready for use. Steps Required for Installing ALL-IN-1 STARTER V2.4 9-47 10 ________________________________________________________________ After Installing ALL-IN-1 STARTER V2.4 This chapter describes the tasks to complete so that ALL-IN-1 STARTER can be run by users. Table 10-1 indicates the sections that you need to refer to in this chapter for the type of installation that you are performing. After Installing ALL-IN-1 STARTER V2.4 10-1 Table 10-1 Section Reference Chart ________________________________________________________________ Installation Type _______________Sub-sections_______________ ________________________________________________________________ ______________________1__2,3__4__5___6,7_&_8__9,10___11_________ New ALL-IN-1 V2.4 * * * * installation ALL-IN-1 V2.4 * * additional language installation Upgrade from * * * * * * ALL-IN-1 V2.3 Upgrade of an * * ALL-IN-1 V2.3 language Upgrade from * * * * * * ALL-IN-1 STARTER V1.0 Upgrade of an * * ALL-IN-1 STARTER V1.0 language Update of ALL-IN-1 * * * * STARTER V2.4 Update of an * * ALL-IN-1 STARTER V2.4 language Update of ALL-IN-1 * * * V2.4 ________________________________________________________________ * Indicates that you need to refer to this section + refer to this section if your users are currently using WPS-PLUS/VMS (continued on next page) 10-2 After Installing ALL-IN-1 STARTER V2.4 Table 10-1 (Cont.) Section Reference Chart ________________________________________________________________ Installation Type _______________Sub-sections_______________ ________________________________________________________________ ______________________1__2,3__4__5___6,7_&_8__9,10___11_________ Update of an * * ALL-IN-1 V2.4 language ________________________________________________________________ ______________________12,13___14_____15,16____17_18__19,20+__21_ New ALL-IN-1 V2.4 * * * * installation ALL-IN-1 V2.4 * additional language installation Upgrade from * * * * * * * ALL-IN-1 V2.3 Upgrade of an * ALL-IN-1 V2.3 language Upgrade from * * * * * ALL-IN-1 STARTER V1.0 Upgrade of an * ALL-IN-1 STARTER V1.0 language Update of ALL-IN-1 * * * * STARTER V2.4 ________________________________________________________________ * Indicates that you need to refer to this section + refer to this section if your users are currently using WPS-PLUS/VMS (continued on next page) After Installing ALL-IN-1 STARTER V2.4 10-3 Table 10-1 (Cont.) Section Reference Chart ________________________________________________________________ Installation Type _______________Sub-sections_______________ ________________________________________________________________ ______________________12,13___14_____15,16____17_18__19,20+__21_ Update of an * ALL-IN-1 STARTER V2.4 language Update of ALL-IN-1 * * * * * V2.4 Update of an * ALL-IN-1 V2.4 language ________________________________________________________________ * Indicates that you need to refer to this section + refer to this section if your users are currently using WPS-PLUS/VMS ________________________________________________________________ 10.1 Replace the DCLTABLES on VAXcluster Systems If you are installing ALL-IN-1 STARTER Version 2.4 on a VAXcluster system, you must replace the DCLTABLES on the nodes in the cluster that are not being used to install ALL-IN-1 STARTER Version 2.4. Enter the following commands on each of these nodes: $ INSTALL INSTALL> REPLACE SYS$SHARE:DCLTABLES /OPEN /SHARE - _INSTALL> /HEAD_RES INSTALL> EXIT You need only do this once after you have installed ALL-IN-1 STARTER Version 2.4. The ALL-IN-1 STARTER installation procedure does this automatically for the node on which you are installing ALL-IN-1 STARTER Version 2.4. 10-4 After Installing ALL-IN-1 STARTER V2.4 10.2 Convert the User Profiles An extra field has been added to the ALL-IN-1 STARTER Version 2.4 user profile master file. During installation the ALL-IN-1 STARTER Version 1.0 file, PROFILE.DAT, is renamed to V23_PROFILE.DAT, and a new PROFILE.DAT file is created. Therefore, you must convert entries in V23_PROFILE.DAT to entries in the new PROFILE.DAT. Do this by entering the following commands: $ ALLIN1/NOINITIALIZATION Enter CMD: OA$FLO_OPEN OA$LIB:MANAGER Enter CMD: OA$CNV_CONVERT V23_PROFIL, PROFIL Enter CMD: EXIT OA$CNV_CONVERT does not preserve access control lists (ACLs), so after you have converted the profiles, enter the following command: $ SET FILE /ACL /LIKE=OA$DATA:V23_PROFILE.DAT OA$DATA:PROFILE.DAT 10.3 Convert SM_ACCOUNT_TYPES.DAT During installation the ALL-IN-1 STARTER Version 1.0 file, SM_ACCOUNT_TYPES.DAT, is renamed to V23_SM_ACCOUNT_TYPES.DAT, and a new SM_ACCOUNT_TYPES.DAT is created. Therefore, you must convert entries in V23_SM_ACCOUNT_TYPES.DAT to entries in the new SM_ACCOUNT_TYPES.DAT. Do this by entering the following: $ ALLIN1 /NOINITIALIZATION Enter CMD: OA$FLO_OPEN OA$LIB:MANAGER Enter CMD: OA$CNV_CONVERT V23_SMTEMPLATE SMTEMPLATE Enter CMD: EXIT 10.4 Update the License Count and Subscriber Count for ALL-IN-1 STARTER If you have a subscriber license (ALLIN1-PERSONAL), you must initialize the license count and subscriber count for ALL-IN-1 STARTER. Do this as follows: 1 Enter the ALL-IN-1 manager's ALL-IN-1 account: $ ALLIN1 /USERNAME=MANAGER /LANGUAGE=language 2 Enter MGT MAL After Installing ALL-IN-1 STARTER V2.4 10-5 3 Enter UCL to initialize the license count 4 Enter UNA to initialize the subscriber count 5 Enter EXIT 10.5 CDA Support If you want to take advantage of CDA support in ALL-IN-1 STARTER, add a line to your ALL-IN-1 site startup file, OA$SITE_BUILD_SHARE:A1V24_SITE_START.COM to call the command file OA$LIB:OA$CDA_STARTUP.COM. This installs the CDA shareable image, without which you cannot work with CDA documents. 10.6 Delete Files That Are No Longer Required If you upgraded from ALL-IN-1 STARTER Version 1.0, various files remain in the SYSTEM directories. You can delete these files to increase your disk space. The files are: o SYS$HELP:AS010.RELEASE_NOTES o SYS$HELP:ASLlang010.RELEASE_NOTES o SYS$HELP:ASCmarket010.RELEASE_NOTES (if available) o SYS$MANAGER:AS010START.COM o SYS$MANAGER:AS010_PRE_V23UPGRADE.COM o SYS$MANAGER:OA$FORMATTER_START.COM o OA$CBI_language:CBIMGS*.SCP;* 10.7 Considerations for the OA$MTI_ERR and OA$MTI_LOG Files The protection on the ALL-IN-1 Mail Traffic Log file, OA$MTI_LOG, and the ALL-IN-1 Mail Error Log file, OA$MTI_ERR, has changed for ALL-IN-1 STARTER Version 2.4 from that in previous versions. These files no longer have GROUP or WORLD access. To access these files, you must have the SYSPRV privilege, or use the ALL-IN-1 manager's account. You may need to modify any procedures that you have written to access these files so that they work in ALL-IN-1 STARTER Version 2.4. 10-6 After Installing ALL-IN-1 STARTER V2.4 10.8 Convert the Format of OA$DATA_SHARE:SM_USED_UIC.DAT The format of the data file OA$DATA_SHARE:SM_USED_UIC.DAT has changed from ALL-IN-1 STARTER Version 1.0. If you are upgrading from one of these ALL-IN-1 STARTER systems, convert the data file as follows: $ CONVERT/FDL=OA$LIB_SHARE:SM_USED_UIC - OA$DATA_SHARE:SM_USED_UIC.DAT OA$DATA_SHARE:SM_USED_UIC.DAT $ PURGE OA$DATA_SHARE:SM_USED_UIC.DAT 10.9 Performance Customizations to PROFILE.FDL and PROFILE.DAT If you have customized either of the two files PROFILE.FDL or PROFILE.DAT, you need to reapply your customizations, as new versions of these files have been created during the installation of ALL-IN-1 STARTER Version 2.4. 10.10 Execute the ALL-IN-1 STARTER Startup Command Procedure The ALL-IN-1 STARTER startup command procedure, SYS$MANAGER: A1V24START.COM, is supplied with ALL-IN-1 STARTER. This startup command procedure must be executed before using ALL-IN-1 STARTER. If you are running ALL-IN-1 STARTER on a VAXcluster system, you must execute the startup command procedure on every node in the cluster. CAUTION If you are installing ALL-IN-1 STARTER Version 2.4 on one part of a multiple-environment cluster with a common system disk, and you want to install a full ALL-IN-1 Version 2.4 system on the another part of the cluster, you must do the following before installing ALL-IN-1 Version 2.4: 1 Copy the startup command procedure A1V24START.COM to the SYS$SPECIFIC:[SYSMGR] directory of each node in the part of the cluster running the ALL-IN-1 STARTER Version 2.4 system. 2 Delete the A1V24START.COM file in the SYS$COMMON:[SYSMGR] directory. After installing the second ALL-IN-1 system, repeat these steps for the part of the cluster that is to run the new ALL-IN-1 system. After Installing ALL-IN-1 STARTER V2.4 10-7 10.10.1 After a New Installation If you are performing a new installation add the following command to the VMS system manager's site startup command procedure: $ @SYS$MANAGER:A1V24START.COM device:[directory.DATA_SHARE] where device:[directory.DATA_SHARE] is the location of the ALL-IN-1 STARTER Version 2.4 configuration file: o device is the device that you specified for the ALL-IN-1 STARTER data files o directory is the top-level directory that you specified for the ALL-IN-1 STARTER data files You must include the location as part of the command. This entry must be entered after the SYS$MANAGER:STARTNET.COM and SYS$MANAGER:MB$CONTROL START=(DDS,TS,...,ER) entries. If you run A1V24START.COM from the DCL prompt, you need not enter the location. In this case you are prompted for the location as follows: Enter the location of the file A1CONFIG.DAT: Enter the location of the ALL-IN-1 STARTER Version 2.4 configuration file, A1CONFIG.DAT. Refer to the log of the installation for the location of A1CONFIG.DAT. Note If you are running ALL-IN-1 STARTER on a VAXcluster system, you must execute the ALL-IN-1 STARTER startup command proce- dure on each node in the cluster. Therefore, you must modify the entry in the startup command procedure on each node. You must also edit OA$BUILD_SHARE: OA$FORMATTER_START.COM, as specified in the command file itself. 10.10.2 After an Upgrade Installation If you are upgrading from ALL-IN-1 STARTER Version 1.0, make sure that the ALL-IN-1 STARTER environment is established after the system is shut down by replacing the following entry in the VMS system manager's site startup procedure: $ @SYS$MANAGER:A1S010START.COM location Change the entry to: $ @SYS$MANAGER:A1V24START.COM device:[directory.DATA_SHARE] 10-8 After Installing ALL-IN-1 STARTER V2.4 where device:[directory.DATA_SHARE] is the location of the ALL-IN-1 STARTER Version 2.4 configuration file: o device is the device that you specified for the ALL-IN-1 STARTER data files o directory is the top-level directory that you specified for the ALL-IN-1 STARTER data files The location of A1CONFIG.DAT, is given in the log of the installation. You must include the location as part of the command. This entry must be entered after the SYS$MANAGER:STARTNET.COM and SYS$MANAGER:MB$CONTROL START=(DDS,TS,...,ER) entries. If you run A1V24START.COM from the DCL prompt, you need not enter the location. In this case you are prompted for the location as follows: Enter the location of the file A1CONFIG.DAT: Enter the location of the ALL-IN-1 STARTER Version 2.4 configuration file, A1CONFIG.DAT. Refer to the log of the installation for the location of A1CONFIG.DAT. Note If you are running ALL-IN-1 STARTER on a VAXcluster system, you must execute the ALL-IN-1 STARTER startup command procedure on each node in the cluster. Therefore, you must modify the entry in the startup command procedure on each node. One of the tasks performed by the startup command procedure is to start the mail Sender and Fetcher. 10.10.3 Site-Specific Startup Procedures You must not edit the ALL-IN-1 STARTER startup command procedure A1V24START.COM. Instead, you must create your own startup command procedures: o A1V24_SITE_START.COM This is the site-specific startup command procedure and must be placed in the OA$SITE_BUILD_SHARE directory. This command procedure is called by A1V24START.COM after all language-specific startup command procedures, if any. After Installing ALL-IN-1 STARTER V2.4 10-9 If you are upgrading from ALL-IN-1 STARTER Version 1.0, and you have a site-specific startup command procedure that you want to keep, rename it from AS010_SITE_START.COM to A1V24_SITE_START.COM (see Section 1.8.17). You may also need to check the command procedure to ensure that it reflects the configuration of your ALL-IN-1 STARTER Version 2.4 system. 10-10 After Installing ALL-IN-1 STARTER V2.4 o OA$SITE_language_START.COM This is the language-specific startup command procedure and must be placed in the directory device:[directory.SITE.SOURCES_ language] for the language concerned, where device is the device containing the language files, and directory is the name of the top-level directory of your ALL-IN-1 STARTER Version 2.4 system. If you are running a multilingual ALL-IN-1 STARTER system, you can have one of these command procedures for each language installed. Note You can specify the directory for your default language using the logical name OA$SITE_BUILD_LLV. If you are upgrading from ALL-IN-1 STARTER Version 1.0, you may also need to check the command procedure to ensure that it reflects the configuration of your ALL-IN-1 STARTER Version 2.4 system. These command procedures, if present, are executed by the ALL-IN-1 STARTER startup command procedure, A1V24START.COM. 10.10.4 How to Handle Errors Relating to Images Not Installed On startup, if any error messages are displayed relating to images that are not installed, use the Install Utility to install those images before executing this procedure again. For example: $ INSTALL INSTALL> ADD SYS$SHARE:RDBSHR /OPEN /HEAD_RES /SHARED The images that you must install in this way are those referenced by optional products that you have integrated with the ALL-IN-1 STARTER image. For more details of the Install Utility, see the VMS manual describing the Install Utility. ALL-IN-1 STARTER can now be run with the ALLIN1 command qualifiers as follows: $ ALLIN1[/qualifier[=argument][/qualifier[=argument]] ...] There are a number of command-line qualifiers that you can use with the ALLIN1 command. These are described in the ALL-IN-1 Management Guide. After Installing ALL-IN-1 STARTER V2.4 10-11 If you have installed an additional language, run ALL-IN-1 STARTER using the qualifier /LANGUAGE, where language is the name of the language that you have just installed (see the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation for this language). 10.11 Compile and Install the TXLs A text library (TXL) contains the most frequently used scripts and document templates. The TXL is installed as a VMS global section. This makes access faster and uses memory more efficiently. After installing ALL-IN-1 STARTER, you must compile and install the ALL-IN-1 TXL. If you chose to run the IVPs automatically after instal- lation, and the IVPs complete successfully, the ALL-IN-1 TXL is already compiled and installed on the node that you used to install ALL-IN-1 STARTER. If you installed ALL-IN-1 STARTER on a VAXcluster system, you must install the TXL on the remaining nodes in the cluster. If you need to compile and install the ALL-IN-1 TXL, do the following: 1 Enter the DCL command: $ DIRECTORY /SECURITY OA$LIB:A1TXL.TXL If the file does not exist carry out steps 2 to 5. Check that the protection of the TXL is set to: SYSTEM:RWED, OWNER:RWED, GROUP:RE, WORLD:RE If the protection is not set to this, use the SET FILE /PROTECTION command to change the protection. 2 Log in to the VMS account belonging to the ALL-IN-1 manager. 3 Enter the following commands: $ ALLIN1 /NOINITIALIZE /LANGUAGE=language Enter CMD: DO OA$LIB:CM_CTX where language is the language associated with the TXL to be compiled. 10-12 After Installing ALL-IN-1 STARTER V2.4 The following prompt is displayed: Do you really want to compile the ALL-IN-1 TXL? [Y/N]? If you want to compile and install the TXL, enter YES. The following message is subsequently displayed: ALL-IN-1 TXL compiled and installed. If you do not want to compile and install the TXL, enter NO. 4 When the script has finished, enter: Enter CMD: EXIT 5 Check the protection of the TXL as described in step 1. If ALL-IN-1 STARTER is later shut down you do not need to install the TXL again, as it is automatically installed when ALL-IN-1 STARTER starts up. However, if you need to install ALL-IN-1 STARTER again, you must also install the TXL(s) again. If you have installed more than one language, you must compile and install the TXLs once for each language. For details of the TXLs, see the ALL-IN-1 Management Guide. 10.12 Compile and Install Your Form Libraries Digital recommends that you always compile form libraries, as this lessens the demand on the system. However, this uses extra disk space because there are two versions of the library on disk-a compiled version and an uncompiled version. Both versions are needed for the forms to display. The ALL-IN-1 STARTER startup command procedure, A1V24START.COM, installs the following form libraries as global sections in memory: o OA$LIB_language:MEMRES o OA$LIB_language:OAFORM If you have any application-specific form libraries, see the ALL-IN-1 Management Guide for details of how to compile and, optionally, install them. If you are installing ALL-IN-1 STARTER on a VAXcluster system, you must install the form libraries on the remaining nodes in the cluster. After Installing ALL-IN-1 STARTER V2.4 10-13 10.13 How to Set Up a Remote Message Router If you want to use a remote Message Router, you must do the following: 1 On the node where Message Router is installed, add a mailbox entry for the ALL-IN-1 STARTER system that you have just installed (see the Message Router books for more information about mailboxes). To set up a mailbox, log in to the MBMANAGER account on the node where Message Router is running, and enter the following commands: $ RUN SYS$SYSTEM:MRMAN Enter the following: MRM> ADD name /REMOTE_RESTRICTION=nodename /PASSWORD=password /SYSTEM where: - name is the mailbox name displayed during ALL-IN-1 STARTER installation; that is, A1, where is the name of the node where you have installed ALL-IN-1 STARTER Version 2.4. The name must be unique to the Message Router system. - nodename is the DECnet nodename where ALL-IN-1 STARTER is installed. - password is the mailbox password you specified during the ALL-IN-1 STARTER installation. If you cannot remember this password, you must change it here, and also in ALL-IN-1 STARTER, using the Manage Messaging menu. The password must be the same in the Message Router mailbox directory and in ALL-IN-1 STARTER. To change the mailbox password use the Change mailbox password (CMP) option on the Manage Messaging menu. See the ALL-IN-1 Mail Management Guide for details. 2 Exit from the Message Router management utility: MRM> EXIT 10-14 After Installing ALL-IN-1 STARTER V2.4 10.14 Setting Up the Message Router Transfer Service To send mail to remote nodes, each node that runs ALL-IN-1 STARTER must have access to Message Router Version 3.1B or later. If Message Router is not installed at the local node, ALL-IN-1 STARTER can use the Message Router on another node. You must also define the logical name MR$NODE. This informs ALL-IN-1 STARTER whether or not Message Router is available. Set this logical name and redefine it in the ALL-IN-1 STARTER startup file to: nodename::"22=" where nodename is the name of the node on which Message Router is installed. This must be defined whether you have Message Router on the same node as ALL-IN-1 STARTER or on a remote node. If your system does not use the Mail directory, and does use area routing, you must define the logical name OA$MTI_AREA. This defines the area code for your system. You must define this logical name to enable users on other systems to reply to mail from your system. This logical name is not defined at installation, so if you do need it, you must define it afterward. Set this logical name OA$MTI_AREA, and redefine it in the ALL-IN-1 STARTER startup file to: mailbox @primary_node @area_name where: o mailbox is the same as defined for the logical name OA$MTI_MAILBX o primary_node is the same as defined for the logical name OA$PRIMARY_NODE o area_name is the area code for your system. After Installing ALL-IN-1 STARTER V2.4 10-15 10.14.1 Configuring the VMSmail Gateway To enable all the nodes in a common-environment cluster to access a Message Router VMSmail Gateway started on one of the nodes only, define the logical name MRGATE to the following on each of the nodes that does not have the gateway started: node::MR% where node is the node where the gateway is running. If the VMSmail Gateway is not installed on your node or cluster, users can use one that is installed on another node. To hide this from your users, so that they do not need to know where the gateway is, make an entry for the remote gateway in the mailbox directory of the Message Router Transfer Service. To do this, use the Message Router Utility, MRMAN, from the MB manager's account and enter the command: MRM> ADD MRGATE="MRGATE @node" where node is the node where the gateway is installed. See the Message Router documentation for more information. 10.15 Diagnostic Tools The following tools are available with ALL-IN-1 STARTER for diagnosing problems: o Verify Mode Verify mode lets you look at DCL subcommands. To turn Verify Mode on, press GOLD VERIFY ON. To turn Verify Mode off, press GOLD VERIFY OFF. o Trace Utility The Trace Utility lets you set or clear trace mode flags that govern the areas and extents of tracing and the destination of trace output. You can use the Trace Utility in one of two ways, as follows: 1 Within ALL-IN-1 STARTER press GOLD TRACE. The Trace Flag Argument Form is displayed. See the Application Programming books for details. 2 Within ALL-IN-1 STARTER use the OA$TRA_SET function. See the Application Programming books for details. 10-16 After Installing ALL-IN-1 STARTER V2.4 The keys are defined in the ALL-IN-1 Management Guide. 10.16 Set the Global Buffers During the installation of ALL-IN-1 STARTER Version 2.4, global buffers are allocated to the data files shown in Table 10-2: Table 10-2 Global Buffer Allocations _____________________________________________________________ System_File________________Number_of_Global_Buffers__________ OA$DATA:PROFILE.DAT n + 1 OA$SHARE:OA$DAF_E.DAT n + 1 OA$DATA:MEETING.DAT 5 OA$DATA:ATTENDEE.DAT n + 1 OA$DATA:PENDING.DAT n + 1 _____________________________________________________________ n is the maximum number of users _____________________________________________________________ During the installation of ALL-IN-1 STARTER Version 2.4, the number you enter at the prompt "What will be the greatest number of simultaneous ALL-IN-1 users" is used to calculate initial values for these global buffers. If you later increase this value, you should recalculate the global buffers using the table; change them using the DCL command: $ SET FILE /GLOBAL_BUFFER filename Note ALL-IN-1 STARTER must be shut down first. To save these values permanently edit the appropriate FDL files for these files. You may also need to increase values of certain SYSGEN parameters, notably GBLPAGFIL and GBLPAGES. GBLPAGES is calculated as described in Section 1.8. After Installing ALL-IN-1 STARTER V2.4 10-17 10.17 Set the Terminal and Queue Characteristics for Printers For most of the supported system printers, you can use the default VMS queue characteristics. However, if you have one or more LQP02, LQP03, or LN03 printers on your system, you must set the terminal and queue characteristics for each of these printers. Note If you have DECpage on your system, see the DECpage Installation Guide for the printer settings required for DECpage. See the ALL-IN-1 Management Guide for details of how to set up the printers. 10.18 Reschedule the ALL-IN-1 Housekeeping Procedures If you are performing an upgrade or update installation, you must reschedule your ALL-IN-1 housekeeping procedures. See the the chapter on ALL-IN-1 housekeeping in the ALL-IN-1 Management Guide. 10.19 Mail Directory Setup If you chose to use either the ALL-IN-1 directory (that is, OA$DDS_PRIME equal to 1) or the Mail directory (that is, OA$DDS_PRIME equal to 2) as the primary mail directory, then after installation you have: o A user agent entry name and password. The user agent entry name is OA$node$ALLIN1 for a new or upgrade installation, where node is either the node name or the cluster alias for the system on which you are installing ALL-IN-1 STARTER. For example, OA$LYNX$ALLIN1. The user agent entry password is the Mail directory password that you entered during the installation (see STEP 23 in Chapter 9). o A subscriber entry for the ALL-IN-1 manager. The proxy attribute of the subscriber entry is the name of the local ALL-IN-1 user agent entry (OA$node$ALLIN1). This attribute gives ALL-IN-1 proxy access to the manager's entry, so that ALL-IN-1 STARTER can update and access the entry. o UAPASSWRD.DAT which contains the name of the user agent object and the user agent password, from the first item in this list. 10-18 After Installing ALL-IN-1 STARTER V2.4 Before you can use the Mail directory you must perform the actions described in the following steps: 1 If area routing is in use at your site, you need to know the area code for use at step 3. Run the MAILbus Configuration Procedure to display the current Transfer Service settings in use at your site. Enter the DCL command: $ @SYS$MANAGER:MB$CONFIG To list the current settings of the configuration parameters, enter: MBC> SHOW TS The area code is displayed, along with other settings, as follows: . . . Transfer Service uses area routing Area Code : . . . is the area code in use at your site. Enter EXIT, or press CTRL/Z, to exit from the MAILbus Configuration Procedure. For more details of this command, see the Message Router books. 2 Log in to the ALL-IN-1 manager's ALL-IN-1 account as follows: $ ALLIN1 /USERNAME=MANAGER 3 Enter the following commands from ALL-IN-1 STARTER: : When conversion is complete, ALL-IN-1 STARTER returns you to the Word and Document Processing menu. After Installing ALL-IN-1 STARTER V2.4 10-23 10 To convert your User Defined Process [.UDP] files, do the following: a From the Word and Document Processing menu, enter $. ALL-IN-1 STARTER places you in the subprocess. b Enter the following command: $ COPY /LOG [username.WPSPLUS.UDP]*.UDP [.UDP]*.* where username is the user's top-level VMS directory, as recorded in the SYS$SYSTEM:SYSUAF.DAT file. c When the copying is finished, press EXIT to return to ALL-IN-1 STARTER. Note If you want to use the converted documents when using ALL-IN-1 STARTER, your default editor must be WPS-PLUS. 10.22 DECpage Support If you install DECpage, and follow the post-installation instructions for integrating DECpage with an existing ALL-IN-1 system (that is, ALL-IN-1 STARTER Version 2.4), the procedure START_DECPAGE:ON_A1_23.COM will fail. To fix this problem, do the following: 1 In directory DECPAGE$INSTALL$LLV, copy the command file ON_A1_23.COM to ON_A1STARTER.COM, and edit ON_A1STARTER.COM to change: 10-24 After Installing ALL-IN-1 STARTER V2.4 $ WRITE OAMAILBOX "OA LOGICAL OA$SITE_LIB_LLV" $ @DCLMAILBOX: $ ! $ IF "''RESULT'" .EQS. "" THEN GOTO BOOBOO $ ! $ DEFINE/SYSTEM DECPAGE$LIB$LLV 'RESULT' $ DEFINE/SYSTEM DECPAGE$FORM 'RESULT' $ ! $ WRITE OAMAILBOX "OA LOGICAL OA$LIB_LLV" $ @DCLMAILBOX: $ ! $ IF "''RESULT'" .EQS. "" THEN GOTO BOOBOO $ ! $ DEFINE/SYSTEM DECPAGE$HELP 'RESULT' $ ! $ FORMNAME :== "DECPA3.FRM" $ !>>>FORMLIBRARY :== "OAFORM" $ FORMLIBRARY :== "SITEOAFORM" $ ! $ WRITE OAMAILBOX "OA GET #STATUS = ""SUCCESS""" $ @DCLMAILBOX: $ ! $ EXIT to the following: After Installing ALL-IN-1 STARTER V2.4 10-25 $ WRITE OAMAILBOX "OA LOGICAL OA$SITE_LIB_LLV" $ @DCLMAILBOX: $ ! $ IF "''RESULT'" .EQS. "" THEN GOTO BOOBOO $ ! $ DEFINE/SYSTEM DECPAGE$LIB$LLV 'RESULT' $ ! $ WRITE OAMAILBOX "OA LOGICAL OA$LIB_LLV" $ @DCLMAILBOX: $ ! $ IF "''RESULT'" .EQS. "" THEN GOTO BOOBOO $ ! $ DEFINE/SYSTEM DECPAGE$HELP 'RESULT' $ DEFINE/SYSTEM DECPAGE$FORM 'RESULT' $ ! $ FORMNAME :== "DECPA3.FRM" $ FORMLIBRARY :== "OAFORM" $ ! FORMLIBRARY :== "SITEOAFORM" $ ! $ WRITE OAMAILBOX "OA GET #STATUS = ""SUCCESS""" $ @DCLMAILBOX: $ ! $ EXIT 2 Follow the post-installation instructions in your DECpage Installation Guide for integrating DECpage into ALL-IN-1, using the command: . For example, AS024BASEA.REV_A. A.2 Compact Disk Consolidated Software Distribution Kits The compact disk (CD) for your market contains directories of the form [ASlang024], where lang is the ALL-IN-1 STARTER language available to you. For example, [ASENGLISH024]. This directory contains two subdirectories; one containing the savesets for the ALL-IN-1 STARTER Version 2.4 kit, the other containing various documentation (in ASCII text format). All the savesets required to install the base, language, and market components for your kit are in the directory [ASlang024.KIT]. The documentation is in the directory [ASlang024.LINE_DOCS]. The savesets of the base component are: AS024.A AS024.B AS024.C AS024.D AS024.E A list of the files in these savesets is given in Section A.3. The savesets of the language component are: ASLlang024.A ASLlang024.B ASLlang024.C ASLlang024.D ASLlang024.E ASLlang024.F ASLlang024.G ASLlang024.H ASLRlang024.A (Release Notes Part 1 Language) A-2 Files on the ALL-IN-1 STARTER V2.4 Distribution Media A list of the files in these savesets is given in the ALL-IN-1 STARTER Installation Guide Part 2 Language Installation. A list of the files in these savesets is given in Section A.3. The savesets of the market component are: ASCmarket024.A ASCmarket024.B ASCRmarket024.A (Release Notes Part 2 Market) A list of the files in these savesets is given in the ALL-IN- 1 STARTER Installation Guide Part 3 Market Installation. This directory also contains the following: o VAX Forms Management System (FMS) Version 2.4 FMS024.A FMS024.B o Message Router Version 3.1B MR031.A MR031.B o Message Router VMSmail Gateway Version 3.1 MRGATE031.A MRGATE031.B o CDA Patch Kit for VMS Version 5.3 CDAPAT010.A See the ALL-IN-1 STARTER Read Me First for details on how to install this kit. o CDA Converter Library Version 1.0 CDACVTLIB010.A CDACVTLIB010.B The documentation directory contains the following: o The ALL-IN-1 STARTER Installation Guide: AS024_INSTALL_GUIDE.TXT and AS024_INSTALL_GUIDE.PS ASLlang024_INSTALL_GUIDE.TXT and ASLlang024_INSTALL_ GUIDE.PS ASCmarket024_INSTALL_GUIDE.TXT and ASCmarket024_ INSTALL_GUIDE.PS Files on the ALL-IN-1 STARTER V2.4 Distribution Media A-3 o The Read Me First: AS024_READ_ME_FIRST.TXT and AS024_READ_ME_FIRST.PS o A Software Product Description (SPD): AS024_SPD.TXT and AS024_SPD.PS o A System Support Addendum (SSA): AS024_SSA.TXT and AS024_SSA.PS o A Software Warranty Addendum (SWA): AS024_SWA.TXT and AS024_SWA.PS A.3 List of Files in Each Saveset Saveset: AS024.A A1LINK.COM;1 A1LNKASK.COM;1 A1LNKDRV.COM;1 AS024.RELEASE_NOTES;1 AS024BASEA.REV_;1 DIRBASEA.ELE;1 KICHECKS.COM;1 KICHKDEV.COM;1 KICHKFMS.COM;1 KICHKINIT.COM;1 KICHKMR.COM;1 KICHKPARAMS.COM;1 KICHKSHR.COM;1 KICHKSPACE.COM;1 KICREACC.COM;1 KICREDIR.COM;1 KICURRENCY.COM;1 KIDATES.COM;1 KIIMAGES.COM;1 KIIVP.COM;1 KIIVP.SCP;1 KIIVP_FILE_LIST.COM;1 KIKEYBOARD.COM;1 KILMF.COM;1 KILOGICALS.COM;1 KINEWDB.COM;1 KIPOSTINSTALL.COM;1 KIPREFIX.COM;1 KIQUESTIONS.COM;1 KIQUOTA.COM;1 KIRECOG.COM;1 KISPELL.COM;1 KISPLIT.COM;1 KITINSTAL.COM;1 KIUPDATE.COM;1 KIUPGET.COM;1 LLVDATALIST.DAT;1 LLVLIBLIST.DAT;1 PARAMETERS.DAT;1 Total of 39 files. A-4 Files on the ALL-IN-1 STARTER V2.4 Distribution Media Saveset: AS024.B A1CONFIG_BASE_PREPOP.SCP;1 A1CONFIG_LANGUAGE_PREPOP.SCP;1 A1ENCODE.CLD;1 A1ENCODE.EXE;1 A1IVP.OBJ;1 A1SUBMIT.CLD;1 A1V24START.COM;1 ACTITEM.FDL;1 ALLFORMS.COM;1 ALLIN1.HLP;1 APPL_INT.SCP;1 ARCHIVE_CREATE_AREA.COM;1 ARCHIVE_CREATE_AREA.SCP;1 ARCHIVE_DELETE_AREA.COM;1 ARCHIVE_DIR_OWN.COM;1 ARCHIVE_DOCS_PENDING_RECOVERY.FDL;1 ARCHIVE_DOCUMENTS.SCP;1 ARCHIVE_EDIT_AREA.SCP;1 ARCHIVE_EXCLUDE_FOLDERS.FDL;1 ARCHIVE_EXCLUDE_USERS.FDL;1 ARCHIVE_INCLUDE_FOLDERS.FDL;1 ARCHIVE_INCLUDE_USERS.FDL;1 ARCHIVE_MARK_DOCUMENT_PENDING.SCP;1 ARCHIVE_MOVE_AREA_TO_TAPE.COM;1 ARCHIVE_MOVE_AREA_TO_TAPE.SCP;1 ARCHIVE_MOVE_TAPE_TO_AREA.COM;1 ARCHIVE_MOVE_TAPE_TO_AREA.SCP;1 ARCHIVE_PENDING_DOCUMENTS.SCP;1 ARCHIVE_PROCESS_RESTORE_REQS.SCP;1 ARCHIVE_RESTORE_USER_DOCUMENTS.SCP;1 ARCHIVE_RESTORE_USER_REQUEST.SCP;1 ARCHIVE_SCHEDULE_ARCHIVE.SCP;1 ARCHIVE_SETS_DATA.FDL;1 ARCHIVE_SET_AREA_ACTIVE.SCP;1 ARCHIVE_SET_AREA_ONLINE.SCP;1 ARCHIVE_SET_DOCUMENT_PENDING.SCP;1 ARCHIVE_SYS_EXCLUDE_FOLDERS.FDL;1 ARCHIVE_SYS_INCLUDE_FOLDERS.FDL;1 ARCHIVE_UNSET_DOCUMENT_PENDING.SCP;1 ARCHIVE_USER_DOCUMENT.SCP;1 AS024BASEB.REV_;1 ATTENDEE.FDL;1 CALACCESS.FDL;1 CALENDAR.A1CAL;1 CALENDAR.FDL;1 CM_CONVERT_FLB_LOCK.SCP;1 CM_CTX.SCP;1 CM_ELEMENTS.SCP;1 CM_FORM_LIBS.SCP;1 CM_SDC_ELEMENTS.FDL;1 CM_SITEHIST.FDL;1 CM_SITELOG.FDL;1 CNVPRTUIC.COM;1 COPYDOC.SCP;1 CORPHONE.FDL;1 CREATE_DATA_CBI_FILES.SCP;1 CREATE_DATA_FILES.SCP;1 CREATE_DATA_FILES_2.SCP;1 CREATE_DATA_LLV_FILES.SCP;1 CREATE_DATA_WPS_FILES.SCP;1 CREATE_FILE.SCP;1 CREATE_PROFILE.SCP;1 CVTDDIFDX.SCP;1 CVTDDIFPS.SCP;1 CVTDDIFTEXT.SCP;1 CVTDDIFWPL.SCP;1 CVTDOTSDX.SCP;1 CVTDOTSPS.SCP;1 CVTDOTSTEXT.SCP;1 CVTDOTSWPL.SCP;1 CVTDTIFDX.SCP;1 CVTDTIFPS.SCP;1 CVTDTIFTEXT.SCP;1 CVTDTIFWPL.SCP;1 CVTDXDDIF.SCP;1 CVTDXPS.SCP;1 CVTTEXTDDIF.SCP;1 CVTTEXTDTIF.SCP;1 CVTTEXTPS.SCP;1 CVTWPLDDIF.SCP;1 CVTWPLDTIF.SCP;1 CXLIB.OLB;1 DECSPELL.FDL;1 DIRALLDWN.SCP;1 DIRALLUP.SCP;1 DIRBASEB.ELE;1 DIRBASEEXE.ELE;1 DIRCORDWN.SCP;1 DIRCORUP.SCP;1 DIRINDEXPRINT.SCP;1 DIRPERDWN.SCP;1 DIRPERUP.SCP;1 DIRPRINT.SCP;1 DISPLAY.EXE;1 DOCCREATE.SCP;1 DOCDB.FDL;1 DOCSELECT.SCP;1 DPESHR.EXE;1 DSABCONV.FDL;1 DSABCONV_PREPOP.SCP;1 DXRD.SCP;1 DXRV.SCP;1 DXRX.SCP;1 DXSD.SCP;1 DXSV.SCP;1 DXSX.SCP;1 Files on the ALL-IN-1 STARTER V2.4 Distribution Media A-5 DXXM.SCP;1 EDITORAPP.SCP;1 EDIT_WRITE.COM;1 EDTGOLDG.SCP;1 EMCONTROL_RS_RF.COM;1 EMCONTROL_RS_RF.SCP;1 EMDDSADDR.SCP;1 EMEMD_PROFIL_UPDATE.SCP;1 EMLOGCTRL.COM;1 EMNXTLIST.SCP;1 EMSMFLUSH.COM;1 FCDELFDR.SCP;1 FCDIR.SCP;1 FCEW.SCP;1 FDNDEDT1.EXE;1 FDNDEDT2.EXE;1 FDNDREORG.EXE;1 FDVDEF.REQ;1 FETCHCHECK.EXE;1 FF.LIS;1 FF.MEM;1 FILECAB_REORG.SCP;1 FLUSHDM.EXE;1 FLUSHUSER.EXE;1 FOLCOUNT.SCP;1 FOLDER.SCP;1 FOLPRINT.SCP;1 FOLPRINTXP.SCP;1 FORMAT.FDL;1 GET_SIZE.COM;1 GLOBAL.FDL;1 GLOBAL_EDIT_TEMPLATE_INTER.COM;1 GLOBAL_TEMPLATES.FDL;1 GLOBAL_USERS.FDL;1 GRAMCHECK.SCP;1 GTEMPLATE_DETAILS.FDL;1 INDEX.DX;1 IVP.A1CAL;1 IVPUSER.PST;1 LANGUAGES.FDL;1 LIST_VIEW.COM;1 LNGSPL_CHANGE_CURRENT_DIC.SCP;1 LNGSPL_CHECK_PERS_OPEN.SCP;1 LNGSPL_CMD_RECOG.SCP;1 LNGSPL_FREE_SLOT.SCP;1 LNGSPL_OPEN_CHECK.SCP;1 LNGSPL_OPEN_GLOBAL_DIC_CHECK.SCP;1 LNGSPL_PERS_DIC_CHECK.SCP;1 LNGSPL_POST_LISTOPEN.SCP;1 LNGSPL_PRE_LISTOPEN.SCP;1 LNGSPL_WPL_SEARCH.SCP;1 LOGIN.COM;1 MAILCOUNT.OBJ;1 MAIL_DIR_CONVERT.SCP;1 MANAGER.A1CAL;1 MANAGER.PST;1 MASTERB.BLP;1 MEETING.FDL;1 METER.SCP;1 MNODES.BLP;1 MNODES.FDL;1 MOVEDISK.FDL;1 MR_CHANGEPASS.COM;1 MUA_CANCEL_TRANSFER.COM;1 MUA_CHANGEPW.COM;1 MUA_CHANGEPW_INTER.COM;1 MUA_CHECK_NOT_LOCKED.COM;1 MUA_COPY_TPL.SCP;1 MUA_CREATE.COM;1 MUA_CREATE_WORKFILE.SCP;1 MUA_CR_INFO.FDL;1 MUA_CTN_INTER.COM;1 MUA_CTN_RESTORE_DOCS.SCP;1 MUA_CTN_TRANSFER_UPDATE.COM;1 MUA_DELETE_INTER.COM;1 MUA_DEL_ACCOUNT.COM;1 MUA_DEL_CAB.SCP;1 MUA_DEL_DIR.COM;1 MUA_DEL_VMS.COM;1 MUA_GLOBAL_EDIT.COM;1 MUA_GLOBAL_EDIT.SCP;1 MUA_LOAD_USER.COM;1 MUA_MAS_ARCHIVE.SCP;1 MUA_MAS_DOCINDEX.FDL;1 MUA_MAS_INTER.COM;1 MUA_MAS_LOADUSER.FDL;1 MUA_MOVEDISK_INTER.COM;1 MUA_NOMINATE.COM;1 MUA_NOMINATE_INTER.COM;1 MUA_PAT.COM;1 MUA_PAT_ARCHIVE.SCP;1 MUA_PAT_FIND_ACCOUNT.SCP;1 MUA_PAT_INTER.COM;1 MUA_PAT_SELECT_FILE.FDL;1 MUA_REMOVE_ADMIN.COM;1 MUA_REMOVE_ADMIN_INTER.COM;1 MUA_RENAME.COM;1 MUA_RENAME_INTER.COM;1 MUA_RENAME_PENDING.EXE;1 MUA_SAVE_UNREAD_MAIL.SCP;1 MUA_SWITCH_APP_PRV.COM;1 MUA_TRANSFER.FDL;1 MUA_UTILITY.FDL;1 MUA_VMS_CHK.SCP;1 MUA_XFER_DOCLIST.FDL;1 NAME_CONVERT.COM;1 NETWORK.FDL;1 NETWORKB.BLP;1 A-6 Files on the ALL-IN-1 STARTER V2.4 Distribution Media NEWDOCDB.COM;1 NEXTLIST.SCP;1 NICKNAMES.FDL;1 OA$APPL_INTMENU.SCP;1 OA$APPL_SPMENU.SCP;1 OA$CDA_STARTUP.COM;1 OA$FORMATTER_START.COM;1 OA$PRINTERS.FDL;1 OA$PRINTERTYPES.FDL;1 OA$SAM_BALANCE_USERS.EXE;1 OA$SAM_CHECK_MAIL_AREA_DELETE.EXE;1 OA$SAM_REORG_SHARED_DIRS.EXE;1 OA$SHARED_DAF_MASTER.FDL;1 OA$SHARED_DIRECTORY_MASTER.FDL;1 OA$SHARE_DEVICE_MASTER.FDL;1 OA$SM_DTC_VALIDATE_UIC.COM;1 OA$SM_FCVR.EXE;1 OA$SM_FCVR_PRE_PHASE1.EXE;1 OA$SM_RECOG_MAIL_AREA.SCP;1 OA$SUBMIT.OBJ;1 OACMSV.OBJ;1 OADDIF_INSTALL.SCP;1 OAFCV.EXE;1 OAFORMATTER.OBJ;1 OAFORMATTERX.OBJ;1 OAINI.COM;1 OALNM.COM;1 OASHRBLD.EXE;1 OASYMMSG.MAR;1 PARANUM.SCP;1 PDAF.FDL;1 PENDING.FDL;1 PERPHONE.FDL;1 PHALLB.BLP;1 PHPERB.BLP;1 POSTMASTE.A1CAL;1 POSTMASTE.PST;1 PRINTER_TYPESB.BLP;1 PRINT_CDA.SCP;1 PRINT_PS.SCP;1 PROFILE.FDL;1 PROFILE_PRINT.FDL;1 PROVIDE_DATA_CBI_FILES.SCP;1 PROVIDE_DATA_FILES.SCP;1 PROVIDE_DATA_FILES_2.SCP;1 PROVIDE_DATA_LLV_FILES.SCP;1 PROVIDE_DATA_WPS_FILES.SCP;1 PTU.EXE;1 QUOTA.COM;1 QUOTA.EXE;1 QUOTA_CHECK.COM;1 REMOVEND.EXE;1 RENAME.FDL;1 REORDER.COM;1 RMSANLZ.COM;1 SA_CHANGE_PASSWORDS.SCP;1 SA_DELETE_ACCOUNT.SCP;1 SA_MULT_DELETE_ACCOUNT.SCP;1 SA_PLM_AVAIL.SCP;1 SA_PREPARE_MAS_NETWORK.COM;1 SA_PREPARE_MAS_TAPE.COM;1 SA_PROFILEB.BLP;1 SA_SUBMIT_CREATE.SCP;1 SA_SUBMIT_GE.SCP;1 SDAF.FDL;1 SELECTIONLIST.BLP;1 SELECTIONLIST1.BLP;1 SELECTIONLIST_RFA.BLP;1 SENDCHECK.EXE;1 SHARED_DOC.BLP;1 SITE_PRINTERSB.BLP;1 SM$SHARE$SCROLL$PREPOP.SCP;1 SMBKUSER.COM;1 SMJACKET.SCP;1 SMNETINIT.COM;1 SMNETINIT.SCP;1 SMNETPRGE.COM;1 SMNETPRGE.EXE;1 SMNETUPDT.EXE;1 SMNETUPDT.SCP;1 SMONOFF.COM;1 SMREORG.SCP;1 SMREORG_DEPT.SCP;1 SMSREORG.COM;1 SMTRLU.SCP;1 SMUNSHARE.SCP;1 SM_CANCEL_TRANSFER.SCP;1 SM_CHANGE_PASSWORDS.SCP;1 SM_CHECK_GROUP_DIR.SCP;1 SM_CTN_BACKUP.COM;1 SM_DELETE_ACCOUNT.SCP;1 SM_DELETE_FROM_QUEUE.SCP;1 SM_DOC_ATTRIBS.COM;1 SM_FIND_FILE_SIZE.COM;1 SM_GET_QUOTA_DETAILS.COM;1 SM_ISSUE_MGR_MAIL.SCP;1 SM_MOVEDISK.COM;1 SM_MOVEDISK.SCP;1 SM_MULT_DELETE_ACCOUNT.SCP;1 SM_NEXT_SAVESET.COM;1 SM_PAT_SWITCH_SAVESET.COM;1 SM_PAT_VALIDATE_NODE.COM;1 SM_PAT_VALIDATE_TAPE.COM;1 SM_PLM_AVAIL.SCP;1 SM_PLM_COUNT.SCP;1 SM_PLM_UPDATE_LIMIT.COM;1 Files on the ALL-IN-1 STARTER V2.4 Distribution Media A-7 SM_POLICIES_PREPOP.SCP;1 SM_PREPARE_MAS_NETWORK.COM;1 SM_PREPARE_MAS_TAPE.COM;1 SM_RESTART.COM;1 SM_SELECT_DISK.SCP;1 SM_SHUTDOWN_RESTART_INTER.SCP;1 SM_SKEDSCRIPT_DEFAULT.SCP;1 SM_SUBMIT_CREATE.SCP;1 SM_SUBMIT_GE.SCP;1 SM_TPL_CLEAR_SYMBOLS.SCP;1 SM_TPL_GLOBAL_EDIT.SCP;1 SM_TPL_TO_PROFILE.SCP;1 SM_TRANSFER_UPGRADE.SCP;1 SM_USED_UIC.FDL;1 SM_XLATE_DEVICE.SCP;1 SPECIAL.COM;1 SPELL.CLD;1 SPFILE.SCP;1 SPNULL.TXT;1 SPSEND.SCP;1 START_TM_SERVER.COM;1 SUBSCRIBER.SCP;1 SUBSCRIBER_ADD.SCP;1 SUBSCRIBER_ADD_INTERACTIVE.SCP;1 SUBSCRIBER_CHANGE.SCP;1 SUBSCRIBER_CHANGE_INTERACTIVE.SCP;1 SUBSCRIBER_DELETE.SCP;1 SYMBOLS.PST;1 TAG.COM;1 TAG.EXE;1 TEMPLATE_PRINT.FDL;1 TIME_DIFF.EXE;1 TMINITFORM.SCP;1 TMMENU_VALID.SCP;1 TRACESET.SCP;1 TRIM.EXE;1 USER.FLB;1 USERAGENT_POST.SCP;1 V.COM;1 VAXMAIL.COM;1 VMNXTLIST.SCP;1 VMSMAIL.COM;1 WPCOPYCAB.BLP;1 WPCOPYDX.BLP;1 WPEDADDMEN_POST.SCP;1 X400COUNTRY_CODES.FDL;1 XPORTMSG.EXE;1 Total of 367 files. Saveset: AS024.C A-8 Files on the ALL-IN-1 STARTER V2.4 Distribution Media ACMSA1MSG.MSG;1 AS024BASEC.REV_;1 DIRBASEC.ELE;1 FINDFILE.OBJ;1 IMAGEID.OPT;1 OA$CNV_TIMEZONE_CONVERT.SCP;1 OA$SM_CHECK_CLUSTER.COM;1 OA$SM_DEFINE_SHARED_LOGICALS.COM;1 OA$SM_DEFINE_SHARED_LOGICALS.SCP;1 OA$SM_FCVR_PRE_PHASE1_SCHEDULE.COM;1 OA$SM_FCVR_PRE_PHASE1_SCHEDULE.SCP;1 OA$SM_FCVR_SCHEDULE.COM;1 OA$SM_FCVR_SLAVE1.COM;1 OA$SM_FIELD_OFFSETS.COM;1 OA$SM_SAM_BA_SCHEDULE.COM;1 OA$SM_SAM_BSD_SCHEDULE.COM;1 OA$SM_SAM_SCHEDULE.SCP;1 OA$SM_SET_WRITE_WINDOW.COM;1 OA$SM_SHARED_DAF_MASTER.SCP;1 OA$SM_UTILITY_MASTER.FDL;1 OA$SM_UTIL_SCHEDULE.FDL;1 OA$SM_WRITE_DIR_MASTER_INSTALL.SCP;1 OA.BLI;1 OAET.MAR;1 OAGBL.BLI;1 OALIBR.OLB;1 OAMAC.REQ;1 OASDF.BLI;1 SCPTABLE.TXT;1 SYSTEM_PST.COM;1 SYSTEM_PST.FDL;1 WPDELETE.SCP;1 WPDOUDP.SCP;1 WPDUMPUDP.SCP;1 WPEDADDMEN.SCP;1 WPEDIT.SCP;1 WPFCFDROP.SCP;1 WPFCFOLD.SCP;1 WPFOLDER.SCP;1 WPLIST.SCP;1 WPNEXTL.SCP;1 WPNEXTNUM.SCP;1 WPPAFOLDER.SCP;1 WPPALTERN.SCP;1 WPPBGFORMAT.SCP;1 WPPFILE.SCP;1 WPPOUTDOC.SCP;1 WPPPORT.SCP;1 WPPRINT.SCP;1 WPPSCRPD.SCP;1 WPPSYSTEM.SCP;1 WPPTERMIN.SCP;1 WPPTYPEIT.SCP;1 WPSLPS.SCP;1 WPSMAIL.COM;1 WPSTSTSPC.SCP;1 X400.CMU;1 Total of 57 files. Saveset: AS024.D ACMSALLIN1.OLB;1 AS024BASED.REV_;1 DIRBASED.ELE;1 DMPLUS.OLB;1 DXLIB.OLB;1 KOAVMS.OLB;1 KOFORM.OLB;1 MRMIS.OLB;1 MRVMS.OLB;1 MRVMS4.OLB;1 MTILIB.OLB;1 OATALKLIB.OLB;1 OAVOICE.OLB;1 SIL.OLB;1 TMSERVER.OLB;1 WPADOC.OLB;1 WPADSA.OLB;1 WPAPRINT.OLB;1 WPARVMS.OLB;1 XPORT.L32;1 XPORT.OLB;1 XPORT.REQ;1 Total of 22 files. Saveset: AS024.E Files on the ALL-IN-1 STARTER V2.4 Distribution Media A-9 AS024BASEE.REV_;1 DIRBASEE.ELE;1 LNGOSENVR.EXE;1 LNGSPLCOM.EXE;1 LNGSPLCRE.SCP;1 LNGSPLCSY.SCP;1 LNGSPLFMT.SCP;1 LNGSPLFOR.EXE;1 LNGSPLIST.SCP;1 LNGSPLMNU.SCP;1 LNGSPLMSG.EXE;1 LNGSPLSC2.SCP;1 LNGSPLSEL.SCP;1 LNGSPLSHR.EXE;1 LOADTCS.TXT;1 PTU.OBJ;1 PTULIB.OLB;1 SPLMSGREF.OBJ;1 WPABASE.OLB;1 WPAEDIT.OLB;1 WPALIPS.OLB;1 WPAPECO.OLB;1 WPASORT.OLB;1 WPCOPY.SCP;1 WPDDXSEND.COM;1 WPDECDX.COM;1 WPPRTEXIT.SCP;1 WPPRUNOFF.COM;1 WPPSPEC.COM;1 WPSDECGET.SCP;1 WPSDECWRT.SCP;1 WPSFNATT.SCP;1 WPSFNPOS.SCP;1 WPSFNSEPS.SCP;1 Total of 34 files. A-10 Files on the ALL-IN-1 STARTER V2.4 Distribution Media B ________________________________________________________________ Sample Installations This appendix contains sample installations of ALL-IN-1 STARTER Version 2.4. _ Section B.1 is a sample listing of a new installation, with no previous version of ALL-IN-1 STARTER installed _ Section B.2 is a sample listing of an upgrade from a multilingual ALL-IN-1 STARTER Version 1.0 system to ALL-IN-1 STARTER Version 2.4 _ Section B.3 is a sample listing of an update of ALL-IN-1 STARTER Version 2.4 _ Section B.4 is a sample listing of an additional language installation B.1 Sample of a New Installation This section contains a sample listing of all the output and input when the American English version of ALL-IN-1 STARTER Version 2.4 was installed on a system running VMS Version 5.2. The sample was run on a system that had no previous version of ALL-IN-1 STARTER installed. The installer chose to: _ Install ALL-IN-1 STARTER from magnetic tape _ Integrate WPS-PLUS _ Create three shared directories _ Use the ALL-IN-1 directory as the primary directory _ Run the IVPs automatically at the end of the installation Sample Installations B-1 The revision identifier, , indicates the revision of your ALL-IN-1 STARTER Version 2.4 kit. Username: SYSTEM Password: Welcome to VAX/VMS Version V5.2 on node LYNX Last interactive login on Monday, 7-AUG-1990 08:47 Last non-interactive login on Monday, 7-AUG-1990 08:25 $ set default sys$update $ @vmsinstal VAX/VMS Software Product Installation Procedure V5.2 It is 8-AUG-1990 at 10:26. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES * Where will the distribution volumes be mounted: TAPE0 Enter the products to be processed from the first distribution volume set. * Products: AS024 * Enter installation options you wish to use (none): Please mount the first volume of the set on TAPE0:. * Are you ready? YES %MOUNT-I-MOUNTED, AS1024 mounted on _LYNX$TAPE0: The following products will be processed: AS V2.4 Beginning installation of AS V2.4 at 10:26 %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. This is the BASE component of the ALL-IN-1 STARTER V2.4 SDC multiple-media kit Using the FULL ALL-IN-1 STARTER V2.4 kit, the following types of installation can be performed :- B-2 Sample Installations (1) First full installation of ALL-IN-1 STARTER (2) Upgrade of ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 (3) Update of ALL-IN-1 STARTER V2.4 (4) Installation of an additional language (5) Upgrade of an additional existing ALL-IN-1 STARTER V1.0 language (6) Update of an additional existing ALL-IN-1 STARTER V2.4 language (7) Register licenses for pre-requisite software * What type of installation do you wish to perform [1]: 1 This is a FULL ALL-IN-1 STARTER V2.4 installation on a clean machine. Media TAPE0:AS1024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted media labeled AS1024. Please mount the MARKET kit media which is labeled AS2024 and reply to the prompt below (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? YES %MOUNT-I-MOUNTED, AS2024 mounted on _LYNX$TAPE0: %ASCUS-I-RECOUK, Restoring the MARKET kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... Media TAPE0:AS2024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted media labeled AS2024. Please mount the LANGUAGE kit media which is labeled AS3024 and reply to the prompt below (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? YES %MOUNT-I-MOUNTED, AS3024 mounted on _LYNX$TAPE0: %ASLENGLISH-I-RELANK, Restoring the LANGUAGE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... This is the ENGLISH version of ALL-IN-1 STARTER V2.4 * Does this product have an authorization key registered and loaded [YES]? YES %LMF-I-GOTLICENSE, An ALLIN1-STARTER license is installed and loaded %LMF-I-CHKSWLIC, Checking licenses for prerequisite software %LMF-I-CONFLICENSE, All necessary licenses are installed and loaded If you wish to have the WPS-PLUS editor available then answer YES to the following question. If you answer NO, then your users will not be able to access the WPS-PLUS editor. Note this will also impact SPELL and MERGE functions. NOTE: You will be able to link WPS-PLUS in at a later time, should you choose not to link it now. Sample Installations B-3 * Do you want to incorporate WPS-PLUS [YES]? YES %ASLENGLISH-I-WPSLINK, The WPS-PLUS editor will be linked with ALL-IN-1 %ASLENGLISH-I-DDIF, Checking CDA support software prerequisites %ASLENGLISH-I-DDIF, CDA integration will be supported If you answer YES to this then you will produce TWO images - OA$MAIN.EXE and OALLVlanguage.EXE. This will allow more than one image to be installed. * Do you want to build a MULTI-LANGUAGE system [NO]? NO %ASLENGLISH-I-NOMLLINK, ALL-IN-1 will be linked as a single language system ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis). This may be changed by user through the Set Working Conditions option. Alphanumeric Date Numeric Date 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD * Which date format do you require [1]: 1 %ASLENGLISH-I-DATEFORMAT, Date format DD-MMM-YYYY and MM/DD/YY (1) has been selected * What will be the greatest number of simultaneous ALL-IN-1 users: 5 * Which batch queue would you like to use for sending/receiving mail [SYS$BATCH]: SYS$BATCH * Do you want to use Message Router to send/receive messages to/from other systems [NO]? YES * Do you want to use a Message Router on another node [NO]? NO * What level of Mail directory support do you want [0/1/2] [0]: 1 * Enter password for the Mail directory user agent account: A1MAIL * Please confirm the Mail directory password specified: A1MAIL * What password do you want to use for the ALL-IN-1 Message Router mailbox: LYNX_A1 * Please confirm the password you have specified: LYNX_A1 B-4 Sample Installations * Do you want to translate outgoing WPS-PLUS and DX messages to ASCII [NO]? NO %ASLENGLISH-I-CHKSWPR, Checking MANDATORY and OPTIONAL SW prerequisites %ASLENGLISH-I-CHKQUOT, Checking process quotas for the current process %ASLENGLISH-I-CHKIDNT, Checking ALL-IN-1 general identifiers %ASLENGLISH-I-CHKTRAC, Checking ALL-IN-1 transfer accounts %ASLENGLISH-I-CHKVMSV, Checking VAX/VMS version %ASLENGLISH-I-CHKLIBS, Checking required shareable libraries are installed %ASLENGLISH-I-CHKFMSV, Checking VAX/FMS version %ASLENGLISH-I-CHKMROV, Checking Message Router version %ASLENGLISH-I-CHKPARA, Checking system parameters All software checks have been successful. Installation will continue. %ASLENGLISH-I-CHKDISK, Checking DISK SPACE * Which device will hold the ALL-IN-1 shared library files [SYS$SYSDEVICE:]: SYS$SYSDEVICE * Which device will hold the ALL-IN-1 shared data files [SYS$SYSDEVICE:]: SYS$SYSDEVICE * Which device will hold the ALL-IN-1 ENGLISH language files [SYS$SYSDEVICE:]: SYS$SYSDEVICE * Which device will hold the ALL-IN-1 mail area SDAF file [SYS$SYSDEVICE:]: SYS$SYSDEVICE * How many shared directories do you want to create [1]: 3 * Which device will hold the ALL-IN-1 shared directory SHARE1 [SYS$SYSDEVICE:]: SYS$SYSDEVICE * Which device will hold the ALL-IN-1 shared directory SHARE2 [SYS$SYSDEVICE:]: SYS$SYSDEVICE * Which device will hold the ALL-IN-1 shared directory SHARE3 [SYS$SYSDEVICE:]: SYS$SYSDEVICE NO missing DISK SPACE prerequisites discovered. The installation will continue. * What VMS username do you want to use for ALL-IN-1 MANAGER account [ALLIN1]: ALLIN1 * What password do you want to use ALL-IN-1 MANAGER account: LYNX_SAMPLE * Please confirm the password you have specified: LYNX_SAMPLE Sample Installations B-5 * What UIC do you want to use for account ALLIN1: 1,100 * What default device you want to use for ALL-IN-1 manager's account [SYS$SYSDEVICE:]: SYS$SYSDEVICE * What default directory do you want to use for ALL-IN-1 manager's account? [ALLIN1]: ALLIN1 A DISKQUOTA entry will be added for UIC [1,100] on SYS$SYSDEVICE:. The DISKQUOTA entry has been added, with a PERMANENT quota of 10000 and an OVERDRAFT quota of 1000. A DISKQUOTA entry on SYS$SYSDEVICE: for UIC [1,100] will now be modified. The DISKQUOTA entry has been modified to: PERMANENT quota of 62500 and OVERDRAFT quota of 5000. %VMSINSTAL-I-SYSDISK, This product creates system disk directory SYS$SYSDEVICE:[ALLIN1]. %VMSINSTAL-I-ACCOUNT, This installation creates an account named ALLIN1. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier ALLIN1 value: [000001,000100] added to RIGHTSLIST.DAT %VMSINSTAL-I-ACCOUNT, This installation updates an account named ALLIN1. %UAF-I-MDFYMSG, user record(s) updated * What UIC do you want for the A1$XFER_IN account?: [500,1] * What UIC do you want for the A1$XFER_OUT account?: [500,2] %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named A1$XFER_IN. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier A1$XFER_IN value [00500,000001] added to RIGHTSLIST A DISKQUOTA entry will be added for UIC [500,1] on SYS$SYSDEVICE:. The DISKQUOTA entry has been added, with a PERMANENT quota of 50000 and an OVERDRAFT quota of 5000 %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named A1$XFER_OUT. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier A1$XFER_OUT value [00500,000002] added to RIGHTSLIST A DISKQUOTA entry will be added for UIC [500,2] on SYS$SYSDEVICE:. The DISKQUOTA entry has been added, with a PERMANENT quota of 50000 and an OVERDRAFT quota of 5000 %ASLENGLISH-I-CREATID, Create ALL-IN-1 RIGHTS identifiers ... A DISKQUOTA entry will be added for UIC OA$PRVAPP on SYS$SYSDEVICE:. The DISKQUOTA entry has been added, with a PERMANENT quota of 1000 and an OVERDRAFT quota of 1000. B-6 Sample Installations A DISKQUOTA entry on SYS$SYSDEVICE: for UIC OA$PRVAPP will now be modified. The DISKQUOTA entry has been modified to: PERMANENT quota of 1000 and OVERDRAFT quota of 1000. %ASLENGLISH-I-GRANTID, Grant ALL-IN-1 general identifiers to UIC [1,100] ... * Enter ALL-IN-1 top-level directory required for the shared library files [ALLIN1]: ALLIN1 * Enter ALL-IN-1 top-level directory required for the shared data files [ALLIN1]: ALLIN1 * Enter ALL-IN-1 top-level directory required for all ENGLISH language files [ALLIN1]: ALLIN1 * Enter ALL-IN-1 top-level directory required for the mail area SDAF file [ALLIN1]: ALLIN1 * What directory will hold the shares directories on SYS$SYSDEVICE: [ALLIN1]: ALLIN1 * Do you want to run the IVP after the installation [YES]? YES %ASLENGLISH-I-KITREVS, The following items will be installed: %ASLENGLISH-I-BASEREV, ALL-IN-1 STARTER BASE kit - Revision %ASLENGLISH-I-CTRYREV, ALL-IN-1 STARTER US MARKET kit - Revision %ASLENGLISH-I-LANGREV, ALL-IN-1 STARTER ENGLISH LANGUAGE kit - Revision %ASLENGLISH-I-ASKDONE, All questions have now been completed. %ASLENGLISH-I-ONEMEDEX, One more media change required before installation can continue unaided. VMSINSTAL-I-RESTORE, Restoring product saveset C... VMSINSTAL-I-RESTORE, Restoring product saveset D... VMSINSTAL-I-RESTORE, Restoring product saveset E... VMSINSTAL-I-RESTORE, Restoring product saveset F... VMSINSTAL-I-RESTORE, Restoring product saveset G... VMSINSTAL-I-RESTORE, Restoring product saveset H... Tape TAPE0:AS3024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted tape labeled AS3024. Please mount the BASE kit tape which is labeled AS1024 and reply to the prompt below (Answer NO to exit). * Type YES when correct tape mounted, NO to terminate installation? YES %MOUNT-I-MOUNTED, AS1024 mounted on _LYNX$TAPE0: %AS-I-REMBKSS, Restoring any remaining BASE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... %VMSINSTAL-I-RESTORE, Restoring product saveset C... %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %AS-I-A1LINK, Starting to link images Sample Installations B-7 Building shared image modules Shared image modules built Linking the OA$MAIN image . . . %AS-I-A1LINKED, Finished linking images During the installation, a file called A1V24START.COM has been added to SYS$MANAGER: A document outlining the changes affecting your users has been added to the MANAGER'S directory. Please distribute USERCHANGES.WPL to your users after installation. **************************************************************************** **************************************************************************** * * *The VMS site-dependent start-up file should have the following line added:* * * * $ @SYS$MANAGER:A1V24START SYS$SYSDEVICE:[ALLIN1.DATA_SHARE] * * * * where SYS$SYSDEVICE:[ALLIN1.DATA_SHARE] is the location of the * * ALL-IN-1 configuration file -- A1CONFIG.DAT * * * *This procedure must be invoked before users can successfully use ALL-IN-1 * * * **************************************************************************** **************************************************************************** During the installation, a second file called A1WPSPLUS_LOGIN.COM, has been added to SYS$MANAGER. This file must be run at system login time OR from each user's LOGIN.COM. Please refer to the Installation Guide for details. %AS-I-RNEPROF, Running command procedure EPROFIL.CA1 %OA-I-LASTLINE, "ALL-IN-1 running -- opening form libraries" %OA-I-LASTLINE, "ALL-IN-1 running -- creating BASE data files" %OA-I-LASTLINE, "ALL-IN-1 running -- creating PROFILE.DAT" %OA-I-LASTLINE, "ALL-IN-1 running -- populating BASE data files" %OA-I-LASTLINE, "ALL-IN-1 running -- creating LANGUAGE data files" %OA-I-LASTLINE, "ALL-IN-1 running -- creating WPS-PLUS data files" %OA-I-LASTLINE, "ALL-IN-1 running -- creating CBI data files" %OA-I-LASTLINE, "ALL-IN-1 running -- removing any old form libraries and TXLs" %OA-I-LASTLINE, "You may ignore any NO SUCH GLOBAL SECTION messages" B-8 Sample Installations SYSTEM finished using ALL-IN-1 at 8-Sep-1990 11:40 %OA-I-LASTLINE, "ALL-IN-1 running -- compiling form libraries..." %OA-I-LASTLINE, "ALL-IN-1 running -- compiling OAFORM..." %OA-I-LASTLINE, "ALL-IN-1 running -- compiling MEMRES..." %OA-I-LASTLINE, "ALL-IN-1 running -- form libraries compiled" %OA-I-LASTLINE, "ALL-IN-1 running -- data file and form processing complete" SYSTEM finished using ALL-IN-1 at 8-Sep-1990 11:44 %AS-I-SETACL, Setting ACL's %AS-I-SETACL, Setting global buffers When the VMSINSTAL procedure terminates, remember to attend to the POST-INSTALLATION tasks described in the Installation Guide. Failure to do this will result in ALL-IN-1 not working correctly. "Spelling Corrector licensed from Houghton Mifflin Company (c) 1987, 1985 by Houghton Mifflin Company. All rights reserved. U.S.PAT. Nos. 4,580,241, 4,730,269, and 4,771,401, Canadian Pat. No. 1,203,916. Houghton Mifflin Usage Alert (c) 1984 Houghton Mifflin. All rights reserved. Roget's II Electronic Thesaurus (c) 1984 Houghton Mifflin. All rights reserved. Based on "Roget's II: The New Thesaurus." (c) Digital Equipment Corporation. 1990. All rights reserved. The installation procedure for ALL-IN-1 STARTER V2.4 has now completed %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... The IVP for ALL-IN-1 STARTER V2.4 takes about 30 minutes to run. This will vary according to the system that it is running on. It will first of all run SYS$MANAGER:A1V24START to initialise ALL-IN-1 logical names and to install the various images required. It also will clear the VMS account name associated with the ALL-IN-1 IVP account. Should the IVPs fail to reset the VMS username in the PROFILE, then please reset it to the same as the MANAGER vms username as soon as possible, by doing the following: $ALLIN1/NOINIT Enter CMD: WRITE CHANGE PROFIL USER="IVP",VMSUSR="ALLIN1" Sample Installations B-9 If the IVPs fail then please investigate the log files found in OA$IVP. There is an additional log file in SYS$MANAGER called ALLIN1IVP.LOG containing the messages from running ALL-IN-1 IVPs. This may sometimes prove useful, for instance if ALL-IN-1 fails to run, it can be seen in this file. To run the IVPs again type: $SET PROC/PRIV=(NOBYPASS,ALL) $ALLIN1/USER=IVP Use the various options on the menu that is presented to run parts of the IVP or all of it. The "ALL" option is what is run during the installation phase IVPs. See the System Management Guide for more details. As an aid to finding problems then please read IVPHINTS.MEM in OA$IVP: %ASIVP-I-IVPSTART,Running startup for ALL-IN-1 . Starting ALL-IN-1 Installing ALL-IN-1 images %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGSPLCOM.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGOSENVR.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:MAILCOUNT.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$MAIN.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$SUBMIT.EXE Defining language independent logical names Defining ENGLISH language logical names %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$LLVENGLISH.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGSPLENG.EXE Running ALL-IN-1 to install the ENGLISH FORM LIBRARIES %OA-I-LASTLINE, "" ALL-IN-1 is RUNNING"" Running ALL-IN-1 to define SHARED AREA logicals %OA-I-LASTLINE, "" ALL-IN-1 is RUNNING"" Starting OA$FCV Starting the MAIL Sender and Fetcher ALL-IN-1 startup procedure completed B-10 Sample Installations %ASIVP-I-IVPFINISH,Finished running startup for ALL-IN-1 . %ASIVP-I-IVPSTART,Running IVPs for ALL-IN-1 . %ASIVP-I-IVPFINISH,The IVPs for ALL-IN-1 have finished . Log File for ALL option ----------------------- ! Starting verification of interface with VMS. ! ! Starting verification of form library compilation. ! Checksum of FLC should be (6D4C620C). ! Test of form library compilation has passed. ! IVP checksum of form library = 6D4C620C. ! Finished verifying form library compilation. ! ! Starting verification of CLI interface. ! CLI symbol ivpclistatus = A1STARTER V2.4. ! verification of CLI interface has passed. ! Finished verifying CLI interface. ! ! Verification of interface with VMS has PASSED. ! ! Verification of interface with VMS has finished. Sample Installations B-11 %OAIVP-I-PASSED, File check for ALL-IN-1 has passed. B-12 Sample Installations 0 ! "Running editor check" 23 ! "EDT/WPS test." 252 ! " first address line check" 258 ! " second address line check" 265 ! " third address line check" 270 ! " fourth address line check" 275 ! " date check" 282 ! " day check" 286 ! " ALL-IN-1 username check" 289 ! " job title check" 293 ! "EDT/WPS check PASSED." 498 ! "WPS-PLUS check starting." 935 ! "WPS-PLUS check finished." ! Merged list checksum is 805719118 ! Correct checksum is 805719118 951 ! "WPS-PLUS check PASSED" 955 ! "Editor check PASSED." 960 ! "Editor check finished." Sample Installations B-13 IWP output files follow... B-14 Sample Installations Text created by EDT/WPS check ----------------------------- DECPARK, WORTON GRANGE, READING, BERKSHIRE. Thursday, 28-Jul-1990. Dear IVP user, This is a test of the integration of EDT with ALL-IN-1. If the address,day,date, and name and job title have been substituted with the values of the IVP account then ALL-IN-1 and EDT are interacting correctly. Yours Sincerely, IVP USER, INSTALLATION VERIFICATION Sample Installations B-15 Text created by WPS-PLUS check ------------------------------ OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Kate Jelly, Office Equipment Ltd, 666 London Rd, Reading. (0734) 663666. Dear Kate, As a user of ALL-IN-1 V2.2 on your VAX/VMS 8800, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. B-16 Sample Installations OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Susie Coggles, Art Equipment Ltd, 69 London Rd, Reading. (0734) 696969. Dear Susie, As a user of ALL-IN-1 V2.1/BEV on your VAX/VMS 8650, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. Sample Installations B-17 OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Jenny Dagleish, Art Equipment Ltd, 31 Reading Gardens, Reading. (0734) 251017. Dear Jenny, As a user of ALL-IN-1 V2.2 on your VaxStation 2000, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. B-18 Sample Installations OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Ruth Calladine , Nutters Catering Compnay, 73 Watlington Street, Reading. (0734) 956435. Dear Ruth, As a user of ALL-IN-1 V2.1/BEV on your VaxStation/GPX, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711) Yours faithfully, Alain M. Cleaner, Office Products Manager. Sample Installations B-19 %OAIVP-I-INST, SYS$SYSDEVICE:[ALLIN1.LIB_SHARE]OA$MAIN.EXE;1 is installed. %OAIVP-I-INST, SYS$SYSDEVICE:[ALLIN1.LIB_SHARE]OA$SUBMIT.EXE;1 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSEXE]OA$FORMATTER.EXE;25 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]FDVMSG.EXE;1 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]DPEMSG.EXE;17 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]XPORTMSG.EXE;74 is installed. %OAIVP-I-PASSED, Message check for ALL-IN-1 has passed. LOG OF THE VERIFICATION OF ALL-IN-1 MESSAGES: --------------------------------------------- This should contain the string V2.4... Enter CMD: VERSION %OA-I-VERSION, ALL-IN-1 STARTER Version 2.4 8-Sep-1990 This should produce an Informational level message, and an RMS-E-FNF error Enter CMD: OA$FLO_OPEN THIS_IS_A_TEST %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found This should produce a Warning level message... Enter CMD: OA$SYM_GET_SYMBOL THIS_IS_A_TEST %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found This should produce a Error level message... Enter CMD: OA$FBT_WRITE_LIBRARY THIS_IS_A.TEST %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library FATAL level error messages cause the image to stop, so they are not tested. B-20 Sample Installations ! Demonstrating directory application. ! Verifying directory application. ! Demonstration of application has passed. ! Finished demonstrating application Personal Phone Directory Full Listing Date: 07/28/88 Page:1 . . . ! Running create account check 3801 ! "Running create account check" 4105 ! "Flushing unread mail " 4111 ! "Deleting profile and template " 4114 ! "Deleted profile and template" 4114 ! "Deleting VMS account and identifier" 4118 ! "Deleted VMS account" 4122 ! "Account is clean" 4138 ! "Creating account" ! Batch job creating account has finished 4809 ! "Finished creating account" 4810 ! "Starting mail send check" ! The user agent is unknown in the mail directory 5694 ! "Sent message checksum: 1835745907" 5696 ! "Received message checksum: 1835745907" ! Account create check has passed, checksums match 5704 ! "Account create check has passed, checksums match" 5799 ! "Deleting account" 6022 ! "Finished deleting account" 6030 ! "Create account check finished" ! Create account check finished ! Verifying Mail directory ! ALL-IN-1 Mail directory useragent name should be OA$LYNX$ALLIN1 ! The following Mail directory useragent entries exist: ! ( DIGITAL MBMAN MASTER OBJECT ) ! ( OA$LYNX$ALLIN1 ) ! The Mail directory useragent entry for ALL-IN-1 which matched is OA$LYNX$ALLIN1 ! Mail directory verification has PASSED. ! Starting MR verification. ! MR verification has PASSED. ! ! Both tests have passed. Verifying ALL-IN-1's interface with Message Router. --------------------------------------------------- Lowest valid version of MR is V3. Sample Installations B-21 Your current version of MR is MR V3.0-044. MR version correct. MR Mailbox entry for ALL-IN-1 verified to be A1. Message Router IVP has PASSED. End of Message Router IVP. ! Finished verifying Mail directory and MR. B-22 Sample Installations ! Running electronic mail check 6592 ! "Running electronic mail check" 7115 ! " Sent message checksum: 1835680371 " 7117 ! " Received message checksum: 1835680371 " 7123 ! "Electronic mail check has PASSED, checksums match." 7193 ! "Electronic mail check finished." ! Electronic mail check finished. %ASIVP-I-IVPPASS,The IVPs for A1STARTER V2.4 have passed. Installation of AS V2.4 completed at 12:34 Enter the products to be processed from the next distribution volume set. * Products: RETURN VMSINSTAL procedure done at 12:35 Sample Installations B-23 B.2 Sample of an Upgrade Installation from ALL-IN-1 STARTER Version 1.0 This section contains a sample listing of all the output and input when the American English version of ALL-IN-1 STARTER Version 1.0 was upgraded to ALL-IN-1 STARTER Version 2.4, on a system running VMS Version 5.1. The ALL-IN-1 STARTER Version 1.0 system had WPS-PLUS integrated. The installer chose to: _ Install ALL-IN-1 STARTER from magnetic tape _ Integrate WPS-PLUS _ Create three shared directories _ Use the ALL-IN-1 directory as the primary directory _ Run the IVPs automatically at the end of the installation The revision identifier, , indicates the revision of your ALL-IN-1 STARTER Version 2.4 kit. Username: SYSTEM Password: Welcome to VAX/VMS Version V5.1 on node LYNX Last interactive login on Monday, 7-AUG-1990 08:47 Last non-interactive login on Monday, 7-AUG-1990 08:25 $ set default sys$update $ @vmsinstal VAX/VMS Software Product Installation Procedure V5.1 It is 8-AUG-1990 at 10:26. Enter a question mark (?) at any time for help. %VMSINMSTAL-W-DECNET, Your DECnet network is up and running. * 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: TAPE0 Enter the products to be processed from the first distribution volume set. * Products: AS024 * Enter installation options you wish to use (none): Please mount the first volume of the set on TAPE0:. * Are you ready? YES %MOUNT-I-MOUNTED, AS1024 mounted on _LYNX$TAPE0: The following products will be processed: B-24 Sample Installations AS V2.4 Beginning installation of AS V2.4 at 10:26 %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. This is the BASE component of the ALL-IN-1 STARTER V2.4 SDC multiple-media kit Using the FULL ALL-IN-1 STARTER V2.4 kit, the following types of installation can be performed :- (1) First full installation of ALL-IN-1 STARTER (2) Upgrade of ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 (3) Update of ALL-IN-1 STARTER V2.4 (4) Installation of an additional language (5) Upgrade of an additional existing ALL-IN-1 STARTER V1.0 language (6) Update of an additional existing ALL-IN-1 STARTER V2.4 language (7) Register licenses for pre-requisite software * What type of installation do you wish to perform [1]: 2 This is an UPGRADE from A1STARTER V1.0 to ALL-IN-1 STARTER V2.4 ***CAUTION*** Your system has been configured as a MULTI-LINGUAL system. After you have upgraded your base system, you must also upgrade all additional language systems. You will not be able to use your additional language systems until they have been upgraded to the same version as your base system. Media TAPE0:AS1024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted media labeled AS1024. Please mount the MARKET kit media which is labeled AS2024 and reply to the prompt below (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? YES %MOUNT-I-MOUNTED, AS2024 mounted on _LYNX$TAPE0: %ASCUS-I-RECOUK, Restoring the MARKET kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... Media TAPE0:AS2024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted media labeled AS2024. Please mount the LANGUAGE kit media which is labeled AS3024 and reply to the prompt below (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? YES Sample Installations B-25 %MOUNT-I-MOUNTED, AS3024 mounted on _LYNX$TAPE0: %ASLENGLISH-I-RELANK, Restoring the LANGUAGE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... This is the ENGLISH version of ALL-IN-1 STARTER V2.4 * Does this product have an authorization key registered and loaded [YES]? YES %LMF-I-GOTLICENSE, An ALLIN1-STARTER license is installed and loaded %LMF-I-CHKSWLIC, Checking licenses for prerequisite software %LMF-I-CONFLICENSE, All necessary licenses are installed and loaded * Do you want to purge files replaced by this installation? YES If you wish to have the WPS-PLUS editor available then answer YES to the following question. If you answer NO, then your users will not be able to access the WPS-PLUS editor. Note this will also impact SPELL and MERGE functions. NOTE: You will be able to link WPS-PLUS in at a later time, should you choose not to link it now. * Do you want to incorporate WPS-PLUS [YES]? YES %ASLENGLISH-I-WPSLINK, The WPS-PLUS editor will be linked with ALL-IN-1 %ASLENGLISH-I-DDIF, Checking CDA support software prerequisites %ASLENGLISH-I-DDIF, CDA integration will be supported If you answer YES to this then you will produce TWO images - OA$MAIN.EXE and OALLVlanguage.EXE. This will allow more than one image to be installed. * Do you want to build a MULTI-LANGUAGE system [NO]? YES %ASLENGLISH-I-MLLINK, ALL-IN-1 will be linked as a multi-language system ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis). This may be changed by user through the Set Working Conditions option. Alphanumeric Date Numeric Date 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD B-26 Sample Installations * Which date format do you require [1]: 1 %ASLENGLISH-I-DATEFORMAT, Date format DD-MMM-YYYY and MM/DD/YY (1) has been selected * What will be the greatest number of simultaneous ALL-IN-1 users: 5 * Which batch queue would you like to use for sending/receiving mail [SYS$BATCH]: SYS$BATCH * Do you want to use Message Router to send/receive messages to/from other systems [NO]? YES * Do you want to use a Message Router on another node [NO]? NO * What level of Mail directory support do you want [0/1/2] [0]: 1 * Enter password for the Mail directory user agent account: A1MAIL * Please confirm the Mail directory password specified: A1MAIL * What password do you want to use for the ALL-IN-1 Message Router mailbox: LYNX_A1 * Please confirm the password you have specified: LYNX_A1 * Do you want to translate outgoing WPS-PLUS and DX messages to ASCII [NO]? NO %ASLENGLISH-I-CHKSWPR, Checking MANDATORY and OPTIONAL SW prerequisites %ASLENGLISH-I-CHKQUOT, Checking process quotas for the current process %ASLENGLISH-I-CHKIDNT, Checking ALL-IN-1 general identifiers %ASLENGLISH-I-CHKTRAC, Checking ALL-IN-1 transfer accounts VMS account named A1$XFER_IN, which should be used for ALL-IN-1 purposes only, was already created before this installation. You have two options: 1. Answer YES if you want the existing A1$TRANSFER account to be used for ALL-IN-1 purposes ONLY. Note that in this case, some characteristics of the account (e.g. UIC, PASSWORD, ACCESS type) may be changed during the installation. 2. Answer NO to stop the installation, correct the problem and then start again. * Do you want to use the existing A1$XFER_IN account [NO]? YES VMS account named A1$XFER_OUT, which should be used for ALL-IN-1 purposes only, was already created before this installation. You have two options: Sample Installations B-27 1. Answer YES if you want the existing A1$TRANSFER account to be used for ALL-IN-1 purposes ONLY. Note that in this case, some characteristics of the account (e.g. UIC, PASSWORD, ACCESS type) may be changed during the installation. 2. Answer NO to stop the installation, correct the problem and then start again. * Do you want to use the existing A1$XFER_OUT account [NO]? YES %ASLENGLISH-I-CHKVMSV, Checking VAX/VMS version %ASLENGLISH-I-CHKLIBS, Checking required shareable libraries are installed %ASLENGLISH-I-CHKFMSV, Checking VAX/FMS version %ASLENGLISH-I-CHKMROV, Checking Message Router version %ASLENGLISH-I-CHKPARA, Checking system parameters All software checks have been successful. Installation will continue. %ASLENGLISH-I-CHKDISK, Checking DISK SPACE NO missing DISK SPACE prerequisites discovered. The installation will continue. * What is the existing VMS username for the ALL-IN-1 MANAGER account [ALLIN1]: ALLIN1 OWNER = ALLIN1 USERNAME = ALLIN1 UIC = [000001,000100] ACCOUNT = ALLIN1 PRIVS = PRIORITY = DIRECTORY = [ALLIN1] * Are you sure all the specified account's characteristics are correct [YES]? YES * What password do you want to use for the ALL-IN-1 TRANSFER accounts: A1TRANSFER * Please confirm the password you have specified: A1TRANSFER A DISKQUOTA entry will be added for UIC [1,100] on SYS$SYSDEVICE:. The DISKQUOTA entry has been added, with a PERMANENT quota of 10000 and an OVERDRAFT quota of 1000. B-28 Sample Installations A DISKQUOTA entry on SYS$SYSDEVICE: for UIC [1,100] will now be modified. The DISKQUOTA entry has been modified to: PERMANENT quota of 62500 and OVERDRAFT quota of 5000. %VMSINSTAL-I-SYSDISK, This product creates system disk directory SYS$SYSDEVICE:[ALLIN1]. %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named ALLIN1. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier ALLIN1 value: [000001,000100] added to RIGHTSLIST.DAT %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ALLIN1. %UAF-I-MDFYMSG, user record(s) updated * What UIC do you want for the A1$XFER_IN account?: [500,1] * What UIC do you want for the A1$XFER_OUT account?: [500,2] %VMSINSTAL-I-ACCOUNT, This installation creates an account named A1$XFER_IN. %UAF-I-ADDMSG, user record successfully added A DISKQUOTA on SYS$SYSDEVICE: for UIC [500,1] will now be modified. The DISKQUOTA entry has been modified to: PERMANENT quota of 50000 and OVERDRAFT quota of 5000 %VMSINSTAL-I-ACCOUNT, This installation creates an account named A1$XFER_OUT. %UAF-I-ADDMSG, user record successfully added A DISKQUOTA on SYS$SYSDEVICE: for UIC [500,2] will now be modified. The DISKQUOTA entry has been modified to: PERMANENT quota of 50000 and OVERDRAFT quota of 5000 %ASLENGLISH-I-CREATID, Create ALL-IN-1 RIGHTS identifiers ... A DISKQUOTA entry will be added for UIC OA$PRVAPP on SYS$SYSDEVICE:. The DISKQUOTA entry has been added, with a PERMANENT quota of 1000 and an OVERDRAFT quota of 1000. A DISKQUOTA entry on SYS$SYSDEVICE: for UIC OA$PRVAPP will now be modified. The DISKQUOTA entry has been modified to: PERMANENT quota of 1000 and OVERDRAFT quota of 1000. %ASLENGLISH-I-GRANTID, Grant ALL-IN-1 general identifiers to UIC [1,100] ... * Do you want to run the IVP after the installation [YES]? YES %ASLENGLISH-I-KITREVS, The following items will be installed: Sample Installations B-29 %ASLENGLISH-I-BASEREV, ALL-IN-1 STARTER BASE kit - Revision %ASLENGLISH-I-CTRYREV, ALL-IN-1 STARTER US MARKET kit - Revision %ASLENGLISH-I-LANGREV, ALL-IN-1 STARTER ENGLISH LANGUAGE kit - Revision %ASLENGLISH-I-ASKDONE, All questions have now been completed. %ASLENGLISH-I-ONEMEDEX, One more media change required before installation can continue unaided. VMSINSTAL-I-RESTORE, Restoring product saveset C... VMSINSTAL-I-RESTORE, Restoring product saveset D... VMSINSTAL-I-RESTORE, Restoring product saveset E... VMSINSTAL-I-RESTORE, Restoring product saveset F... VMSINSTAL-I-RESTORE, Restoring product saveset G... VMSINSTAL-I-RESTORE, Restoring product saveset H... Tape TAPE0:AS3024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted tape labeled AS3024. Please mount the BASE kit tape which is labeled AS1024 and reply to the prompt below (Answer NO to exit). * Type YES when correct tape mounted, NO to terminate installation? YES %MOUNT-I-MOUNTED, AS1024 mounted on _LYNX$TAPE0: %AS-I-REMBKSS, Restoring any remaining BASE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... %VMSINSTAL-I-RESTORE, Restoring product saveset C... %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %AS-I-A1LINK, Starting to link images Building shared image modules Shared image modules built Linking the OA$MAIN image . . . %AS-I-A1LINKED, Finished linking images During the installation, a file called A1V24START.COM has been added to SYS$MANAGER: A document outlining the changes affecting your users has been added to the MANAGER'S directory. Please distribute USERCHANGES.WPL to your users after installation. B-30 Sample Installations **************************************************************************** **************************************************************************** * * *The VMS site-dependent start-up file should have the following line added:* * * * $ @SYS$MANAGER:A1V24START SYS$SYSDEVICE:[ALLIN1.DATA_SHARE] * * * * where SYS$SYSDEVICE:[ALLIN1.DATA_SHARE] is the location of the* * ALL-IN-1 configuration file -- A1CONFIG.DAT * * * *This procedure must be invoked before users can successfully use ALL-IN-1 * * * **************************************************************************** **************************************************************************** During the installation, a second file called A1WPSPLUS_LOGIN.COM, has been added to SYS$MANAGER. This file must be run at system login time OR from each user's LOGIN.COM. Please refer to the Installation Guide for details. %AS-I-RNEPROF, Running command procedure EPROFIL.CA1 %OA-I-LASTLINE, "ALL-IN-1 running -- opening form libraries" %OA-I-LASTLINE, "ALL-IN-1 running -- creating BASE data files" %OA-I-LASTLINE, "ALL-IN-1 running -- creating PROFILE.DAT" %OA-I-LASTLINE, "ALL-IN-1 running -- populating BASE data files" %OA-I-LASTLINE, "ALL-IN-1 running -- creating LANGUAGE data files" %OA-I-LASTLINE, "ALL-IN-1 running -- creating WPS-PLUS data files" %OA-I-LASTLINE, "ALL-IN-1 running -- creating CBI data files" %OA-I-LASTLINE, "ALL-IN-1 running -- removing any old form libraries and TXLs" %OA-I-LASTLINE, "You may ignore any NO SUCH GLOBAL SECTION messages" SYSTEM finished using ALL-IN-1 at 8-Sep-1990 11:40 %OA-I-LASTLINE, "ALL-IN-1 running -- compiling form libraries..." %OA-I-LASTLINE, "ALL-IN-1 running -- compiling OAFORM..." %OA-I-LASTLINE, "ALL-IN-1 running -- compiling MEMRES..." %OA-I-LASTLINE, "ALL-IN-1 running -- form libraries compiled" %OA-I-LASTLINE, "ALL-IN-1 running -- data file and form processing complete" SYSTEM finished using ALL-IN-1 at 8-Sep-1990 11:44 When the VMSINSTAL procedure terminates, remember to attend to the POST-INSTALLATION tasks described in the Installation Guide. Failure to do this will result in ALL-IN-1 not working correctly. Sample Installations B-31 "Spelling Corrector licensed from Houghton Mifflin Company (c) 1987, 1985 by Houghton Mifflin Company. All rights reserved. U.S.PAT. Nos. 4,580,241, 4,730,269, and 4,771,401, Canadian Pat. No. 1,203,916. Houghton Mifflin Usage Alert (c) 1984 Houghton Mifflin. All rights reserved. Roget's II Electronic Thesaurus (c) 1984 Houghton Mifflin. All rights reserved. Based on "Roget's II: The New Thesaurus." (c) Digital Equipment Corporation. 1990. All rights reserved. The installation procedure for ALL-IN-1 STARTER V2.4 has now completed %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... The IVP for ALL-IN-1 STARTER V2.4 takes about 30 minutes to run. This will vary according to the system that it is running on. It will first of all run SYS$MANAGER:A1V24START to initialise ALL-IN-1 logical names and to install the various images required. It also will clear the VMS account name associated with the ALL-IN-1 IVP account. Should the IVPs fail to reset the VMS username in the PROFILE, then please reset it to the same as the MANAGER vms username as soon as possible, by doing the following: $ALLIN1/NOINIT Enter CMD: WRITE CHANGE PROFIL USER="IVP",VMSUSR="ALLIN1" If the IVPs fail then please investigate the log files found in OA$IVP. There is an additional log file in SYS$MANAGER called ALLIN1IVP.LOG containing the messages from running ALL-IN-1 IVPs. This may sometimes prove useful, for instance if ALL-IN-1 fails to run, it can be seen in this file. To run the IVPs again type: $SET PROC/PRIV=(NOBYPASS,ALL) $ALLIN1/USER=IVP Use the various options on the menu that is presented to run parts of the IVP or all of it. The "ALL" option is what is run during the installation phase IVPs. See the System Management Guide for more details. As an aid to finding problems then please read IVPHINTS.MEM in OA$IVP: %ASIVP-I-IVPSTART,Running startup for ALL-IN-1 . B-32 Sample Installations Starting ALL-IN-1 Installing ALL-IN-1 images %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGSPLCOM.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGOSENVR.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:MAILCOUNT.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$MAIN.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$SUBMIT.EXE Defining language independent logical names Defining ENGLISH language logical names %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$LLVENGLISH.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGSPLENG.EXE Running ALL-IN-1 to install the ENGLISH FORM LIBRARIES %OA-I-LASTLINE, "" ALL-IN-1 is RUNNING"" Running ALL-IN-1 to define SHARED AREA logicals %OA-I-LASTLINE, "" ALL-IN-1 is RUNNING"" Starting OA$FCV Starting the MAIL Sender and Fetcher ALL-IN-1 startup procedure completed %ASIVP-I-IVPFINISH,Finished running startup for ALL-IN-1 . %ASIVP-I-IVPSTART,Running IVPs for ALL-IN-1 . %ASIVP-I-IVPFINISH,The IVPs for ALL-IN-1 have finished . Sample Installations B-33 Log File for ALL option ----------------------- ! Starting verification of interface with VMS. ! ! Starting verification of form library compilation. ! Checksum of FLC should be (6D4C620C). ! Test of form library compilation has passed. ! IVP checksum of form library = 6D4C620C. ! Finished verifying form library compilation. ! ! Starting verification of CLI interface. ! CLI symbol ivpclistatus = A1STARTER V2.4. ! verification of CLI interface has passed. ! Finished verifying CLI interface. ! ! Verification of interface with VMS has PASSED. ! ! Verification of interface with VMS has finished. B-34 Sample Installations %OAIVP-I-PASSED, File check for ALL-IN-1 has passed. Sample Installations B-35 0 ! "Running editor check" 23 ! "EDT/WPS test." 252 ! " first address line check" 258 ! " second address line check" 265 ! " third address line check" 270 ! " fourth address line check" 275 ! " date check" 282 ! " day check" 286 ! " ALL-IN-1 username check" 289 ! " job title check" 293 ! "EDT/WPS check PASSED." 498 ! "WPS-PLUS check starting." 935 ! "WPS-PLUS check finished." ! Merged list checksum is 805719118 ! Correct checksum is 805719118 951 ! "WPS-PLUS check PASSED" 955 ! "Editor check PASSED." 960 ! "Editor check finished." B-36 Sample Installations IWP output files follow... Sample Installations B-37 Text created by EDT/WPS check ----------------------------- DECPARK, WORTON GRANGE, READING, BERKSHIRE. Thursday, 28-Jul-1990. Dear IVP user, This is a test of the integration of EDT with ALL-IN-1. If the address,day,date, and name and job title have been substituted with the values of the IVP account then ALL-IN-1 and EDT are interacting correctly. Yours Sincerely, IVP USER, INSTALLATION VERIFICATION B-38 Sample Installations Text created by WPS-PLUS check ------------------------------ OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Kate Jelly, Office Equipment Ltd, 666 London Rd, Reading. (0734) 663666. Dear Kate, As a user of ALL-IN-1 V2.2 on your VAX/VMS 8800, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. Sample Installations B-39 OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Susie Coggles, Art Equipment Ltd, 69 London Rd, Reading. (0734) 696969. Dear Susie, As a user of ALL-IN-1 V2.1/BEV on your VAX/VMS 8650, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. B-40 Sample Installations OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Jenny Dagleish, Art Equipment Ltd, 31 Reading Gardens, Reading. (0734) 251017. Dear Jenny, As a user of ALL-IN-1 V2.2 on your VaxStation 2000, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. Sample Installations B-41 OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Ruth Calladine , Nutters Catering Compnay, 73 Watlington Street, Reading. (0734) 956435. Dear Ruth, As a user of ALL-IN-1 V2.1/BEV on your VaxStation/GPX, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. B-42 Sample Installations %OAIVP-I-INST, SYS$SYSDEVICE:[ALLIN1.LIB_SHARE]OA$MAIN.EXE;1 is installed. %OAIVP-I-INST, SYS$SYSDEVICE:[ALLIN1.LIB_SHARE]OA$SUBMIT.EXE;1 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSEXE]OA$FORMATTER.EXE;25 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]FDVMSG.EXE;1 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]DPEMSG.EXE;17 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]XPORTMSG.EXE;74 is installed. %OAIVP-I-PASSED, Message check for ALL-IN-1 has passed. LOG OF THE VERIFICATION OF ALL-IN-1 MESSAGES: --------------------------------------------- This should contain the string V2.4... Enter CMD: VERSION %OA-I-VERSION, ALL-IN-1 STARTER Version 2.4 8-Sep-1990 This should produce an Informational level message, and an RMS-E-FNF error Enter CMD: OA$FLO_OPEN THIS_IS_A_TEST %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found This should produce a Warning level message... Enter CMD: OA$SYM_GET_SYMBOL THIS_IS_A_TEST %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found This should produce a Error level message... Enter CMD: OA$FBT_WRITE_LIBRARY THIS_IS_A.TEST %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library FATAL level error messages cause the image to stop, so they are not tested. Sample Installations B-43 ! Demonstrating directory application. ! Verifying directory application. ! Demonstration of application has passed. ! Finished demonstrating application Personal Phone Directory Full Listing Date: 07/28/88 Page:1 . . . ! Running create account check 3801 ! "Running create account check" 4105 ! "Flushing unread mail " 4111 ! "Deleting profile and template " 4114 ! "Deleted profile and template" 4114 ! "Deleting VMS account and identifier" 4118 ! "Deleted VMS account" 4122 ! "Account is clean" 4138 ! "Creating account" ! Batch job creating account has finished 4809 ! "Finished creating account" 4810 ! "Starting mail send check" ! The user agent is unknown in the mail directory 5694 ! "Sent message checksum: 1835745907" 5696 ! "Received message checksum: 1835745907" ! Account create check has passed, checksums match 5704 ! "Account create check has passed, checksums match" 5799 ! "Deleting account" 6022 ! "Finished deleting account" 6030 ! "Create account check finished" ! Create account check finished ! Verifying Mail directory ! ALL-IN-1 Mail directory useragent name should be OA$LYNX$ALLIN1 ! The following Mail directory useragent entries exist: ! ( DIGITAL MBMAN MASTER OBJECT ) ! ( OA$LYNX$ALLIN1 ) ! The Mail directory useragent entry for ALL-IN-1 which matched is OA$LYNX$ALLIN1 ! Mail directory verification has PASSED. ! Starting MR verification. ! MR verification has PASSED. ! ! Both tests have passed. Verifying ALL-IN-1's interface with Message Router. --------------------------------------------------- Lowest valid version of MR is V3. B-44 Sample Installations Your current version of MR is MR V3.0-044. MR version correct. MR Mailbox entry for ALL-IN-1 verified to be A1. Message Router IVP has PASSED. End of Message Router IVP. ! Finished verifying Mail directory and MR. Sample Installations B-45 ! Running electronic mail check 6592 ! "Running electronic mail check" 7115 ! " Sent message checksum: 1835680371 " 7117 ! " Received message checksum: 1835680371 " 7123 ! "Electronic mail check has PASSED, checksums match." 7193 ! "Electronic mail check finished." ! Electronic mail check finished. %ASIVP-I-IVPPASS,The IVPs for A1STARTER V2.4 have passed. Installation of AS V2.4 completed at 12:34 Enter the products to be processed from the next distribution volume set. * Products: RETURN VMSINSTAL procedure done at 12:35 B-46 Sample Installations B.3 Sample of an ALL-IN-1 STARTER Version 2.4 Update Installation This section contains a sample listing of all the output and input when a multilingual ALL-IN-1 STARTER Version 2.4 system was updated, on a system running VMS Version 5.2. The update installation was performed to include Message Router Version 3.1B and Message Router VMSmail Gateway Version 3.1. The ALL-IN-1 STARTER Version 2.4 system had WPS-PLUS integrated. The installer chose to: _ Install ALL-IN-1 STARTER from magnetic tape _ Integrate WPS-PLUS _ Use the ALL-IN-1 directory as the primary directory _ Run the IVPs automatically at the end of the installation The revision identifier, , indicates the revision of your ALL-IN-1 STARTER Version 2.4 kit. Username: SYSTEM Password: Welcome to VAX/VMS Version V5.2 on node LYNX Last interactive login on Monday, 7-AUG-1990 08:47 Last non-interactive login on Monday, 7-AUG-1990 08:25 $ set default sys$update $ @vmsinstal VAX/VMS Software Product Installation Procedure V5.1 It is 8-AUG-1990 at 10:26. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES * Where will the distribution volumes be mounted: TAPE0 Enter the products to be processed from the first distribution volume set. * Products: AS024 * Enter installation options you wish to use (none): Please mount the first volume of the set on TAPE0:. * Are you ready? YES %MOUNT-I-MOUNTED, AS1024 mounted on _LYNX$TAPE0: The following products will be processed: AS V2.4 Beginning installation of AS V2.4 at 10:26 Sample Installations B-47 %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. This is the BASE component of the ALL-IN-1 STARTER V2.4 SDC multiple-media kit Using the FULL ALL-IN-1 STARTER V2.4 kit, the following types of installation can be performed :- (1) First full installation of ALL-IN-1 STARTER (2) Upgrade of ALL-IN-1 STARTER V1.0 to ALL-IN-1 STARTER V2.4 (3) Update of ALL-IN-1 STARTER V2.4 (4) Installation of an additional language (5) Upgrade of an additional existing ALL-IN-1 STARTER V1.0 language (6) Update of an additional existing ALL-IN-1 STARTER V2.4 language (7) Register licenses for pre-requisite software * What type of installation do you wish to perform [1]: 3 This is an UPDATE of A1STARTER V2.4 to ALL-IN-1 STARTER V2.4. ***CAUTION*** Your system has been configured as a MULTI-LINGUAL system. After you have upgraded your base system, you must also upgrade all additional language systems. You will not be able to use your additional language systems until they have been upgraded to the same version as your base system. Media TAPE0:AS1024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted media labeled AS1024. Please mount the MARKET kit media which is labeled AS2024 and reply to the prompt below (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? YES %MOUNT-I-MOUNTED, AS2024 mounted on _LYNX$TAPE0: %ASCUS-I-RECOUK, Restoring the MARKET kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... Media TAPE0:AS2024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted media labeled AS2024. Please mount the LANGUAGE kit media which is labeled AS3024 and reply to the prompt below (Answer NO to exit). * Type YES when correct media mounted, NO to terminate installation? YES %MOUNT-I-MOUNTED, AS3024 mounted on _LYNX$TAPE0: %ASLENGLISH-I-RELANK, Restoring the LANGUAGE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... B-48 Sample Installations This is the ENGLISH version of ALL-IN-1 STARTER V2.4 * Does this product have an authorization key registered and loaded [YES]? YES %LMF-I-GOTLICENSE, An ALLIN1-STARTER license is installed and loaded %LMF-I-CHKSWLIC, Checking licenses for prerequisite software %LMF-I-CONFLICENSE, All necessary licenses are installed and loaded * Do you want to purge files replaced by this installation? YES If you wish to have the WPS-PLUS editor available then answer YES to the following question. If you answer NO, then your users will not be able to access the WPS-PLUS editor. Note this will also impact SPELL and MERGE functions. NOTE: You will be able to link WPS-PLUS in at a later time, should you choose not to link it now. * Do you want to incorporate WPS-PLUS [YES]? YES %ASLENGLISH-I-WPSLINK, The WPS-PLUS editor will be linked with ALL-IN-1 %ASLENGLISH-I-DDIF, Checking CDA support software prerequisites %ASLENGLISH-I-DDIF, CDA integration will be supported If you answer YES to this then you will produce TWO images - OA$MAIN.EXE and OALLVlanguage.EXE. This will allow more than one image to be installed. * Do you want to build a MULTI-LANGUAGE system [NO]? YES %ASLENGLISH-I-MLLINK, ALL-IN-1 will be linked as a multi-language system ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis). This may be changed by user through the Set Working Conditions option. Alphanumeric Date Numeric Date 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD * Which date format do you require [1]: 1 %ASLENGLISH-I-DATEFORMAT, Date format DD-MMM-YYYY and MM/DD/YY (1) has been selected Sample Installations B-49 * What will be the greatest number of simultaneous ALL-IN-1 users: 5 * Which batch queue would you like to use for sending/receiving mail [SYS$BATCH]: SYS$BATCH * Do you want to use Message Router to send/receive messages to/from other systems [NO]? YES * Do you want to use a Message Router on another node [NO]? NO * What level of Mail directory support do you want [0/1/2] [0]: 1 * Enter password for the Mail directory user agent account: A1MAIL * Please confirm the Mail directory password specified: A1MAIL * What password do you want to use for the ALL-IN-1 Message Router mailbox: LYNX_A1 * Please confirm the password you have specified: LYNX_A1 * Do you want to translate outgoing WPS-PLUS and DX messages to ASCII [NO]? NO %ASLENGLISH-I-CHKSWPR, Checking MANDATORY and OPTIONAL SW prerequisites %ASLENGLISH-I-CHKQUOT, Checking process quotas for the current process %ASLENGLISH-I-CHKLNAM, Checking ALL-IN-1 logical names %ASLENGLISH-I-CHKIDNT, Checking ALL-IN-1 general identifiers %ASLENGLISH-I-GENIDOK, General identifier OA$ADMIN will be used from the previous installation. %ASLENGLISH-I-GENIDOK, General identifier OA$PRVAPP will be used from the previous installation. %ASLENGLISH-I-CHKTRAC, Checking ALL-IN-1 transfer accounts VMS account named A1$XFER_IN, which should be used for ALL-IN-1 purposes only, was already created before this installation. You have two options: 1. Answer YES if you want the existing A1$TRANSFER account to be used for ALL-IN-1 purposes ONLY. Note that in this case, some characteristics of the account (e.g. UIC, PASSWORD, ACCESS type) may be changed during the installation. 2. Answer NO to stop the installation, correct the problem and then start again. * Do you want to use the existing A1$XFER_IN account [NO]? yes VMS account named A1$XFER_OUT, which should be used for ALL-IN-1 purposes only, was already created before this installation. B-50 Sample Installations You have two options: 1. Answer YES if you want the existing A1$TRANSFER account to be used for ALL-IN-1 purposes ONLY. Note that in this case, some characteristics of the account (e.g. UIC, PASSWORD, ACCESS type) may be changed during the installation. 2. Answer NO to stop the installation, correct the problem and then start again. * Do you want to use the existing A1$XFER_OUT account [NO]? yes %ASLENGLISH-I-CHKVMSV, Checking VAX/VMS version %ASLENGLISH-I-CHKLIBS, Checking required shareable libraries are installed %ASLENGLISH-I-CHKFMSV, Checking VAX/FMS version %ASLENGLISH-I-CHKMROV, Checking Message Router version %ASLENGLISH-I-CHKPARA, Checking system parameters All software checks have been successful. Installation will continue. %ASLENGLISH-I-CHKDISK, Checking DISK SPACE NO missing DISK SPACE prerequisites discovered. The installation will continue. * What is the existing VMS username for the ALL-IN-1 MANAGER account [ALLIN1]: ALLIN1 OWNER = ALLIN1 USERNAME = ALLIN1 UIC = [000001,000100] ACCOUNT = ALLIN1 PRIVS = PRIORITY = DIRECTORY = [ALLIN1] * Are you sure all the specified account's characteristics are correct [YES]? YES A DISKQUOTA entry on SYS$SYSDEVICE: for UIC [1,100] will now be modified. The DISKQUOTA entry has been modified to: PERMANENT quota of 62500 and OVERDRAFT quota of 5000. %VMSINSTAL-I-ACCOUNT, This installation update an ACCOUNT named ALLIN1. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ALLIN1. %UAF-I-MDFYMSG, user record(s) updated %ASLENGLISH-I-CREATID, Create ALL-IN-1 RIGHTS identifiers ... %ASLENGLISH-I-GRANTID, Grant ALL-IN-1 general identifiers to UIC [1,100] ... * Do you want to run the IVP after the installation [YES]? YES %ASLENGLISH-I-KITREVS, The following items will be installed: Sample Installations B-51 %ASLENGLISH-I-BASEREV, ALL-IN-1 STARTER BASE kit - Revision %ASLENGLISH-I-CTRYREV, ALL-IN-1 STARTER US MARKET kit - Revision %ASLENGLISH-I-LANGREV, ALL-IN-1 STARTER ENGLISH LANGUAGE kit - Revision %ASLENGLISH-I-ASKDONE, All questions have now been completed. %ASLENGLISH-I-ONEMEDEX, One more media change required before installation can continue unaided. VMSINSTAL-I-RESTORE, Restoring product saveset C... VMSINSTAL-I-RESTORE, Restoring product saveset D... VMSINSTAL-I-RESTORE, Restoring product saveset E... VMSINSTAL-I-RESTORE, Restoring product saveset F... VMSINSTAL-I-RESTORE, Restoring product saveset G... VMSINSTAL-I-RESTORE, Restoring product saveset H... Tape TAPE0:AS3024 dismounted. (MEDIA CHANGE REQUIRED ) : Dismounted tape labeled AS3024. Please mount the BASE kit tape which is labeled AS1024 and reply to the prompt below (Answer NO to exit). * Type YES when correct tape mounted, NO to terminate installation? YES %MOUNT-I-MOUNTED, AS1024 mounted on _LYNX$TAPE0: %AS-I-REMBKSS, Restoring any remaining BASE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... %VMSINSTAL-I-RESTORE, Restoring product saveset C... %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %AS-I-A1LINK, Starting to link images Building shared image modules Shared image modules built Linking the OA$MAIN image . . . %AS-I-A1LINKED, Finished linking images During the installation, a file called A1V24START.COM has been added to SYS$MANAGER: A document outlining the changes affecting your users has been added to the MANAGER'S directory. Please distribute USERCHANGES.WPL to your users after installation. B-52 Sample Installations **************************************************************************** **************************************************************************** * * *The VMS site-dependent start-up file should have the following line added:* * * * $ @SYS$MANAGER:A1V24START SYS$SYSDEVICE:[ALLIN1.DATA_SHARE] * * * * where SYS$SYSDEVICE:[ALLIN1.DATA_SHARE] is the location of the* * ALL-IN-1 configuration file -- A1CONFIG.DAT * * * *This procedure must be invoked before users can successfully use ALL-IN-1 * * * **************************************************************************** **************************************************************************** During the installation, a second file called A1WPSPLUS_LOGIN.COM, has been added to SYS$MANAGER. This file must be run at system login time OR from each user's LOGIN.COM. Please refer to the Installation Guide for details. %OA-I-LASTLINE, "ALL-IN-1 running -- removing form libraries & TXL" %OA-E-NOSUCHSEC, no such (global) section %OA-E-NOSUCHSEC, no such (global) section SYSTEM finished using ALL-IN-1 at 8-Sep-1990 11:38 %AS-I-RNEPROF, Running command procedure EPROFIL.CA1 %OA-I-LASTLINE, "ALL-IN-1 running -- opening form libraries" %OA-I-LASTLINE, "ALL-IN-1 running -- updating A1CONFIG data file" SYSTEM finished using ALL-IN-1 at 8-Sep-1990 11:40 %OA-I-LASTLINE, "ALL-IN-1 running -- compiling form libraries..." %OA-I-LASTLINE, "ALL-IN-1 running -- compiling OAFORM..." %OA-I-LASTLINE, "ALL-IN-1 running -- compiling MEMRES..." %OA-I-LASTLINE, "ALL-IN-1 running -- form libraries compiled" %OA-I-LASTLINE, "ALL-IN-1 running -- data file and form processing complete" SYSTEM finished using ALL-IN-1 at 8-Sep-1990 11:44 Sample Installations B-53 %AS-I-CREMBX, Creating mailbox entry A1 This is MRMAN V3.1B %Added A1, Owner=ALLIN1 Complete_Messages Ignore_Sender Grant_Id Service_Messages %AS-I-DDSUA, Creating DDS UA entry for OA$LYNX$ALLIN1 MBMAN V3.1B (BL5.17) Name : OA$LYNX$ALLIN1 Master copy owning node : LYNX %AS-I-DDSSUB, Creating DDS subscriber entry for MANAGER MBMAN V3.1B (BL5.17) Surname : MANAGER Name : MANAGER Unique subscriber identifier : OA$LYNX$ALLIN1 Proxy user agent : OA$LYNX$ALLIN1 Master copy owning node : LYNX When the VMSINSTAL procedure terminates, remember to attend to the POST-INSTALLATION tasks described in the Installation guide. Failure to do this will result in ALL-IN-1 not working correctly "Spelling Corrector licensed from Houghton Mifflin Company (c) 1987, 1985 by Houghton Mifflin Company. All rights reserved. U.S.PAT. Nos. 4,580,241, 4,730,269, and 4,771,401, Canadian Pat. No. 1,203,916. Houghton Mifflin Usage Alert (c) 1984 Houghton Mifflin. All rights reserved. Roget's II Electronic Thesaurus (c) 1984 Houghton Mifflin. All rights reserved. Based on "Roget's II: The New Thesaurus." (c) Digital Equipment Corporation. 1990. All rights reserved. The installation procedure for ALL-IN-1 STARTER V2.4 has now completed %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... The IVP for ALL-IN-1 STARTER V2.4 takes about 30 minutes to run. This will vary according to the system that it is running on. It will first of all run SYS$MANAGER:A1V24START to initialise ALL-IN-1 logical names and to install the various images required. It also will clear the VMS account name associated with the ALL-IN-1 IVP account. Should the IVPs fail to reset the VMS username in the PROFILE, then please reset it to the same as the MANAGER vms username as soon as possible, by doing the following: B-54 Sample Installations $ALLIN1/NOINIT Enter CMD: WRITE CHANGE PROFIL USER="IVP",VMSUSR="ALLIN1" If the IVPs fail then please investigate the log files found in OA$IVP. There is an additional log file in SYS$MANAGER called ALLIN1IVP.LOG containing the messages from running ALL-IN-1 IVPs. This may sometimes prove useful, for instance if ALL-IN-1 fails to run, it can be seen in this file. To run the IVPs again type: $SET PROC/PRIV=(NOBYPASS,ALL) $ALLIN1/USER=IVP Use the various options on the menu that is presented to run parts of the IVP or all of it. The "ALL" option is what is run during the installation phase IVPs. See the System Management Guide for more details. As an aid to finding problems then please read IVPHINTS.MEM in OA$IVP: %ASIVP-I-IVPSTART,Running startup for ALL-IN-1 . Starting ALL-IN-1 Installing ALL-IN-1 images %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGSPLCOM.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGOSENVR.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:MAILCOUNT.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$MAIN.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$SUBMIT.EXE Defining language independent logical names Defining ENGLISH language logical names %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:OA$LLVENGLISH.EXE %INSTALL-W-NOPREV, no previous entry exists - new entry created for SYS$SYSDEVICE:LNGSPLENG.EXE Running ALL-IN-1 to install the ENGLISH FORM LIBRARIES %OA-I-LASTLINE, "" ALL-IN-1 is RUNNING"" Running ALL-IN-1 to define SHARED AREA logicals %OA-I-LASTLINE, "" ALL-IN-1 is RUNNING"" Sample Installations B-55 Starting OA$FCV Starting the MAIL Sender and Fetcher ALL-IN-1 startup procedure completed %ASIVP-I-IVPFINISH,Finished running startup for ALL-IN-1 . %ASIVP-I-IVPSTART,Running IVPs for ALL-IN-1 . %ASIVP-I-IVPFINISH,The IVPs for ALL-IN-1 have finished . Log File for ALL option ----------------------- ! Starting verification of interface with VMS. ! ! Starting verification of form library compilation. ! Checksum of FLC should be (6D4C620C). ! Test of form library compilation has passed. ! IVP checksum of form library = 6D4C620C. ! Finished verifying form library compilation. ! ! Starting verification of CLI interface. ! CLI symbol ivpclistatus = A1STARTER V2.4. ! verification of CLI interface has passed. ! Finished verifying CLI interface. ! ! Verification of interface with VMS has PASSED. ! ! Verification of interface with VMS has finished. B-56 Sample Installations %OAIVP-I-PASSED, File check for ALL-IN-1 has passed. Sample Installations B-57 0 ! "Running editor check" 23 ! "EDT/WPS test." 252 ! " first address line check" 258 ! " second address line check" 265 ! " third address line check" 270 ! " fourth address line check" 275 ! " date check" 282 ! " day check" 286 ! " ALL-IN-1 username check" 289 ! " job title check" 293 ! "EDT/WPS check PASSED." 498 ! "WPS-PLUS check starting." 935 ! "WPS-PLUS check finished." ! Merged list checksum is 805719118 ! Correct checksum is 805719118 951 ! "WPS-PLUS check PASSED" 955 ! "Editor check PASSED." 960 ! "Editor check finished." B-58 Sample Installations IWP output files follow... Sample Installations B-59 Text created by EDT/WPS check ----------------------------- DECPARK, WORTON GRANGE, READING, BERKSHIRE. Thursday, 28-Jul-1990. Dear IVP user, This is a test of the integration of EDT with ALL-IN-1. If the address,day,date, and name and job title have been substituted with the values of the IVP account then ALL-IN-1 and EDT are interacting correctly. Yours Sincerely, IVP USER, INSTALLATION VERIFICATION B-60 Sample Installations Text created by WPS-PLUS check ------------------------------ OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Kate Jelly, Office Equipment Ltd, 666 London Rd, Reading. (0734) 663666. Dear Kate, As a user of ALL-IN-1 V2.2 on your VAX/VMS 8800, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. Sample Installations B-61 OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Susie Coggles, Art Equipment Ltd, 69 London Rd, Reading. (0734) 696969. Dear Susie, As a user of ALL-IN-1 V2.1/BEV on your VAX/VMS 8650, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. B-62 Sample Installations OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Jenny Dagleish, Art Equipment Ltd, 31 Reading Gardens, Reading. (0734) 251017. Dear Jenny, As a user of ALL-IN-1 V2.2 on your VaxStation 2000, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. Sample Installations B-63 OA Sales Department, Digital Equip. Corp., DECpark, Worton Grange, Reading,Berks. (0734) 868711 Ruth Calladine , Nutters Catering Compnay, 73 Watlington Street, Reading. (0734) 956435. Dear Ruth, As a user of ALL-IN-1 V2.1/BEV on your VaxStation/GPX, you may be interested to know that Digital's OA engineering group has just announced the availability of ALL-IN-1 V2.3 - a huge step forward for the future of office automation. It's many *NEW* features include multiple select options for the File Cabinet, forward and backward scrolling on Read, as well as the capacity for multiple languages. All this together with the advanced WP Grammar Checker option, make this THE OFFICE PRODUCT OF 1990. Phone NOW for a demonstration - on (0734) 868711 Yours faithfully, Alain M. Cleaner, Office Products Manager. B-64 Sample Installations %OAIVP-I-INST, SYS$SYSDEVICE:[ALLIN1.LIB_SHARE]OA$MAIN.EXE;1 is installed. %OAIVP-I-INST, SYS$SYSDEVICE:[ALLIN1.LIB_SHARE]OA$SUBMIT.EXE;1 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSEXE]OA$FORMATTER.EXE;25 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]FDVMSG.EXE;1 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]DPEMSG.EXE;17 is installed. %OAIVP-I-INST, SYS$COMMON:[SYSMSG]XPORTMSG.EXE;74 is installed. %OAIVP-I-PASSED, Message check for ALL-IN-1 has passed. LOG OF THE VERIFICATION OF ALL-IN-1 MESSAGES: --------------------------------------------- This should contain the string V2.4... Enter CMD: VERSION %OA-I-VERSION, ALL-IN-1 STARTER Version 2.4 8-Sep-1990 This should produce an Informational level message, and an RMS-E-FNF error Enter CMD: OA$FLO_OPEN THIS_IS_A_TEST %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found This should produce a Warning level message... Enter CMD: OA$SYM_GET_SYMBOL THIS_IS_A_TEST %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found This should produce a Error level message... Enter CMD: OA$FBT_WRITE_LIBRARY THIS_IS_A.TEST %OA-E-BADLIB, Error occurred while pre-compiling THIS_IS_A.TEST form library FATAL level error messages cause the image to stop, so they are not tested. Sample Installations B-65 ! Demonstrating directory application. ! Verifying directory application. ! Demonstration of application has passed. ! Finished demonstrating application Personal Phone Directory Full Listing Date: 07/28/88 Page:1 . . . ! Running create account check 3801 ! "Running create account check" 4105 ! "Flushing unread mail " 4111 ! "Deleting profile and template " 4114 ! "Deleted profile and template" 4114 ! "Deleting VMS account and identifier" 4118 ! "Deleted VMS account" 4122 ! "Account is clean" 4138 ! "Creating account" ! Batch job creating account has finished 4809 ! "Finished creating account" 4810 ! "Starting mail send check" ! The user agent is unknown in the mail directory 5694 ! "Sent message checksum: 1835745907" 5696 ! "Received message checksum: 1835745907" ! Account create check has passed, checksums match 5704 ! "Account create check has passed, checksums match" 5799 ! "Deleting account" 6022 ! "Finished deleting account" 6030 ! "Create account check finished" ! Create account check finished ! Verifying Mail directory ! ALL-IN-1 Mail directory useragent name should be OA$LYNX$ALLIN1 ! The following Mail directory useragent entries exist: ! ( DIGITAL MBMAN MASTER OBJECT ) ! ( OA$LYNX$ALLIN1 ) ! The Mail directory useragent entry for ALL-IN-1 which matched is OA$LYNX$ALLIN1 ! Mail directory verification has PASSED. ! Starting MR verification. ! MR verification has PASSED. ! ! Both tests have passed. Verifying ALL-IN-1's interface with Message Router. --------------------------------------------------- Lowest valid version of MR is V3. B-66 Sample Installations Your current version of MR is MR V3.0-044. MR version correct. MR Mailbox entry for ALL-IN-1 verified to be A1. Message Router IVP has PASSED. End of Message Router IVP. ! Finished verifying Mail directory and MR. Sample Installations B-67 ! Running electronic mail check 6592 ! "Running electronic mail check" 7115 ! " Sent message checksum: 1835680371 " 7117 ! " Received message checksum: 1835680371 " 7123 ! "Electronic mail check has PASSED, checksums match." 7193 ! "Electronic mail check finished." ! Electronic mail check finished. %ASIVP-I-IVPPASS,The IVPs for A1STARTER V2.4 have passed. Installation of AS V2.4 completed at 12:34 Enter the products to be processed from the next distribution volume set. * Products: RETURN VMSINSTAL procedure done at 12:35 B-68 Sample Installations B.4 Additional Language Installation This section contains a sample listing of all the output and input when the GERMAN language was installed as an additional language on a system running VMS Version 5.2. The ALL-IN- 1 STARTER Version 2.4 system has WPS-PLUS integrated. The installer chose to install the additional language from magnetic tape. Username: SYSTEM Password: Welcome to VAX/VMS Version V5.2 on node LYNX Last interactive login on Monday, 15-AUG-1990 08:47 Last non-interactive login on Monday, 15-AUG-1990 08:25 $ set default sys$update $ @vmsinstal VAX/VMS Software Product Installation Procedure V5.2 It is 15-AUG-1990 at 09:11. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES * Where will the distribution volumes be mounted: TAPE0 Enter the products to be processed from the first distribution volume set. * Products: ASLGERMAN024 * Enter installation options you wish to use (none): Please mount the first volume of the set on TAPE0:. * Are you ready? YES %MOUNT-I-MOUNTED, AS3024 mounted on _LYNX$TAPE0: The following products will be processed: ASLGERMAN V2.4 Beginning installation of ASLGERMAN V2.4 at 09:11 %VMSINSTAL-I-RESTORE, Restoring product saveset A... This is a LOCAL ALL-IN-1 STARTER V2.4 LANGUAGE-only kit (GERMAN) Using the LANGUAGE only ALL-IN-1 STARTER V2.4 kit, the following types of installation can be performed :- Sample Installations B-69 (1) Installation of an additional language (2) Upgrade of an additional existing ALL-IN-1 STARTER V1.0 language (3) Update of an additional existing ALL-IN-1 STARTER V2.4 language * Do you want to continue [YES]? YES * What type of installation do you wish to perform [1]: 1 This is the GERMAN Additional Language installation %ASLGERMAN-I-RELANK, Restoring the LANGUAGE kit savesets. %VMSINSTAL-I-RESTORE, Restoring product saveset B... This is the GERMAN version of ALL-IN-1 STARTER V2.4 * Does this product have an authorization key registered and loaded [YES]? YES %LMF-I-GOTLICENSE, An AI1-START-UI-GERMAN license is installed and loaded %LMF-I-CHKSWLIC, Checking licenses for prerequisite software %LMF-I-CONFLICENSE, All necessary licenses are installed and loaded During your first language installation you elected to integrate WPS-PLUS. It means that you can access WPS-PLUS as an additional editor from your GERMAN ALL-IN-1 as well. %ASLGERMAN-I-CHKSWPR, Checking MANDATORY SW prerequisites %ASLGERMAN-I-CHKMROV, Checking the existence of ALL-IN-1 logical names %ASLGERMAN-I-CHKPARA, Checking system parameters All S/W checks have been successful. Installation will continue. %ASLGERMAN-I-CHKDISK, Checking DISK SPACE ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis). This may be changed by user through the Set Working Conditions option. Alphanumeric Date Numeric Date 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD B-70 Sample Installations * Which date format do you require [1]: 1 %ASLGERMAN-I-DATEFORMAT, Date format DD-MMM-YYYY and DD/MM/YY (2) has been selected * Which device will hold the ALL-IN-1 GERMAN language files [SYS$SYSDEVICE:]: SYS$SYSDEVICE NO missing DISK SPACE prerequisites discovered. The installation will continue. * What is the existing VMS username for the ALL-IN-1 MANAGER account [ALLIN1]: ALLIN1 OWNER = USERNAME = ALLIN1 UIC = [1,100] ACCOUNT = PRIVS = All PRIORITY = 4 DIRECTORY = SYS$SYSDEVICE:[ALLIN1] * Are you sure all the specified account's characteristics are correct [YES]? YES A DISKQUOTA entry on SYS$SYSDEVICE: for UIC [1,100] will now be modified. %DISKQ-I-INUSE, [000001,000100] has 96395 blocks in use The DISKQUOTA entry has been modified to: PERMANENT quota of 87904 and OVERDRAFT quota of 5000. * Enter ALL-IN-1 top-level directory required for all GERMAN files [GERMAN]: GERMAN * Do you want to run the IVP after the installation [YES]? YES %ASLGERMAN-I-ASKDONE, All questions have now been completed. %ASLGERMAN-I-SOMTIME, Installation will now continue for some time. No further action required. %VMSINSTAL-I-RESTORE, Restoring product saveset C... %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %VMSINSTAL-I-RESTORE, Restoring product saveset F... %VMSINSTAL-I-RESTORE, Restoring product saveset G... %VMSINSTAL-I-RESTORE, Restoring product saveset H... %ASLGERMAN-I-A1LINK, Starting to link images Linking the OA$LLVGERMAN.EXE Sample Installations B-71 %ASLGERMAN-I-A1LINKED, Finished linking images %ASLGERMAN-I-RNEPROF, Running command procedure EPROFIL.CA1 . . . The installation procedure for ALL-IN-1 STARTER V2.4 has now completed %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of ASLGERMAN V2.4 completed at 11:47 Enter the products to be processed from the next distribution volume set. * Products: RETURN VMSINSTAL procedure done at 11:48 B-72 Sample Installations C ________________________________________________________________ Files and Logical Names Installed on Your System The ALL-IN-1 STARTER Version 2.4 installation procedure installs a number of files on your system and defines some logical names. Section C.1 lists the files installed in directories other than the main ALL-IN-1 STARTER directories (for example, SYS$COMMON:[SYSLIB]). Section C.2 lists the logical names that are added to the system logical name table. Section C.3 shows the directory structure of an ALL- IN-1 STARTER system installed on separate disks. C.1 Files Installed in Non-ALL-IN-1 STARTER Directories The following list shows the files that are installed in directories other than the ALL-IN-1 STARTER directories. Directory SYS$SYSROOT:[SYSMGR] ALLIN1_IVP.LOG;1 Directory SYS$COMMON:[SYSMGR] A1V24START.COM;1 A1WPSPLUS_LOGIN.COM;1 Directory SYS$COMMON:[SYSHLP] AS024.RELEASE_NOTES;1 ASLRlang024.RELEASE_NOTES;1 ASCRmarket024.RELEASE_NOTES;1 Note AS024.RELEASE_NOTES does not contain any release notes. To access the Release Notes, that is the files ASLRlang024.RELEASE_NOTES and ASCRmarket024.RELEASE_NOTES, Files and Logical Names Installed on Your System C-1 carry out the steps described in Chapter 2. Directory SYS$COMMON:[SYSLIB] DPESHR.EXE;1 FDVSHR.EXE;1 LNGOSENVR.EXE;1 LNGSPLAE2.LGS;1 LNGSPLAET.LGM;1 LNGSPLAET.LGS;1 LNGSPLAEU.LGM;1 LNGSPLAEU.LGS;1 LNGSPLCOM.EXE;1 LNGSPLlang.EXE;1 LNGSPLSHR.EXE;1 OA$LLVlanguage.EXE;1 XPORT.L32;1 XPORT.OLB;1 XPORT.REQ;1 lang is a three-letter code identifying the language installed, and language is the language name. You may have more than one version if you have installed additional languages. Note that OA$LLVlanguage.EXE is created only if you install ALL-IN-1 STARTER as a multilanguage system. Directory SYS$COMMON:[SYSMSG] DPEMSG.EXE;1 FDVMSG.EXE;1 LNGSPLMSG.EXE;1 XPORTMSG.EXE;1 C.2 Logical Names The following logical names are defined when ALL-IN-1 STARTER Version 2.4 is installed. These names are stored in the startup file, A1V24START.COM. They are automatically defined whenever the system reboots or whenever the software is invoked. C.2.1 Logical Names Entered into the System Logical Name Table The following logical names are entered into the system logical name table, LNM$SYSTEM_TABLE. Note Copies of all logical names that end in _LLV exist in both the system logical name table and the logical name table for the default language. C-2 Files and Logical Names Installed on Your System DX$PRINT FAC$COMMON KOA$HEAP_SIZE KOA$PRINT_DIR KOA$PRINT_SHARE OA$ADMIN_DATA OA$BLP OA$BLP_lang OA$BLP_LLV OA$BLP_SHARE OA$BUILD OA$BUILD_SHARE OA$DATA OA$DATA_LLV OA$DATA_SHARE OA$DDS_PRIME OA$DEFAULT_LANGUAGE OA$DO OA$DO_lang OA$DO_LLV OA$DO_SHARE OA$IMAGE OA$LIB OA$LIB_lang OA$LIB_LLV OA$LIB_SHARE OA$LLV OA$LOADUSER OA$LOG OA$MAIL_NUM_ADDRESSES OA$MTI_AREA OA$MTI_DATA OA$MTI_ERR OA$MTI_LOG OA$MTI_MAILBX OA$MTI_MR_NODE (If you are using a remote Message Router) OA$MTI_OPER OA$MTI_QUEUE OA$MTI_TRNS OA$PRIMARY_NODE OA$SCP OA$SCP_lang OA$SCP_LLV OA$SCP_SHARE OA$SHARE (The logical names OA$SHARE* refer to Mail Files and Logical Names Installed on Your System C-3 area E which is created during the installation of ALL-IN-1 STARTER Version 2.4) OA$SHAREn (n is from 1 to the number of shared directories specified during the installation) OA$SHARE_HIGH OA$SHARE_LOW OA$SITE_BLP_lang OA$SITE_BLP_LLV OA$SITE_BLP_SHARE OA$SITE_BUILD_LLV OA$SITE_BUILD_SHARE OA$SITE_DATA OA$SITE_DATA_LLV OA$SITE_DATA_SHARE OA$SITE_DEV OA$SITE_DEV_lang OA$SITE_DEV_LLV OA$SITE_DEV_SHARE OA$SITE_DO_lang OA$SITE_DO_LLV OA$SITE_DO_SHARE OA$SITE_LIB OA$SITE_LIB_lang OA$SITE_LIB_LLV OA$SITE_LIB_SHARE OA$SITE_SCP_lang OA$SITE_SCP_LLV OA$SITE_SCP_SHARE OA$STARTER OA$SUBMIT_IMAGE OA$SUBSCRIBER_MAIL OA$SYSTEM_LISTS OA$TRANSFER C.2.2 Logical Names Entered into the Language Logical Name Table The following logical names are entered into a language- specific logical name table for the language installed, OA$lang_TABLE. The same logical names are used for all languages although their definitions are different. Note Copies of all logical names that end in _LLV exist in both the system logical name table and the logical name table for the default language. C-4 Files and Logical Names Installed on Your System OA$BLP_LLV OA$DATA_LLV OA$DO_LLV OA$LIB_LLV OA$LLV OA$SCP_LLV OA$SITE_BLP_LLV OA$SITE_BUILD_LLV OA$SITE_DATA_LLV OA$SITE_DEV_LLV OA$SITE_DO_LLV OA$SITE_LIB_LLV OA$SITE_SCP_LLV C.3 Directory Structure of an ALL-IN-1 STARTER System Installed on Separate Disks Figures C-1 to C-6 show the directory structure of an ALL- IN-1 STARTER Version 2.4 system installed on the system disk and disks DISK0 to DISK4. Each area of ALL-IN-1 STARTER (see Section 1.8.16) was installed on a different disk, with a different directory specified for each area: o The ALL-IN-1 STARTER manager's account was installed on the system disk SYS$SYSDEVICE: using the account name MANAGER. o The shared library files were installed on disk DISK0 using the directory name LIBRARY. o The language files were installed on disk DISK1 using the directory name LANGUAGE. o The shared data files were installed on disk DISK2 using the directory name DATA. o The mail area SDAF file was installed on disk DISK3 using the directory name MAIL. o The shared directories were installed on disk DISK4 using the directory name SHARED. If you want to move an ALL-IN-1 area to another disk, copy the directories in that area as shown in Figures C-1 to C-5 (the shared directories cannot be moved once they are created). See Appendix D for details. Files and Logical Names Installed on Your System C-5 Figure C-1 Directory Structure of the ALL-IN-1 STARTER Manager's Account +--+[.IVPUSER]+-------+-------+[.DOC0] | | . | | . | | . | +-------+[.DOC9] | | | +-------+[.MSG] | | | +-------+[.UDP] | | +--+[.MGR]+-----------+-------+[.DOC0] | | . | | . | | . | +-------+[.DOC9] | | SYS$SYSDEVICE:[MANAGER]+--+ +-------+[.MSG] | | | +-------+[.UDP] | | +--+[.POSTMASTE]+-----+-------+[.DOC0] | | . | | . | | . | +-------+[.DOC9] | | | +-------+[.MSG] | | | +-------+[.UDP] | | | +---+[.TRANSFER_INCOMING] | +---+[.TRANSFER_OUTGOING] C-6 Files and Logical Names Installed on Your System Figure C-2 Directory Structure for the Library Files +----+[.ADMIN_DATA] | | +----+[.BLP_SHARE] | | +----+[.DO_SHARE] | | +----+[.LIB_SHARE]+----------[.USER] | | DISK0:[LIBRARY]+---+----+[.LOG] | | +---+[.BLP_SHARE] +----+[.PRINT] | | | | +---+[.DEV_SHARE] +----+[SCP_SHARE] | | | | +---+[.DO_SHARE] +----+[.SITE]+----------+ | | | +---+[.LIB_SHARE] +----+[.SOURCES] | | | | +---+[.SCP_SHARE] +----+[.SYSTEM_LISTS] | | +---+[.SOURCES_SHARE] Files and Logical Names Installed on Your System C-7 Figure C-3 Directory Structure for the Language Files +-----[.BLP_lang] | | +----+[.CBI_lang] | | +----+[.DATA_lang] | | +----+[.DO_lang] | | DISK1:[LANGUAGES]+-+----+[.IVP_lang] | | +----+[.LIB_lang] +---+[.BLP_lang] | | | | +----+[.LLV_lang] +---+[.DATA_lang] | | | | +----+[.SCP_lang] +---+[.DEV_lang] | | | | +----+[.SITE]+----------+---+[.DO_lang] | +---+[.LIB_lang] | | +---+[.SCP_lang] | | +---+[.SOURCES_lang] C-8 Files and Logical Names Installed on Your System Figure C-4 Directory Structure for the Data Files +---+[.DATA_SHARE] | | DISK2:[DATA]+-----+ | | +---+[.SITE]+---------+[.DATA_SHARE] Figure C-5 Directory Structure for Mail Area E DISK3:[MAIL]+----+[.SHARE_E] Figure C-6 Directory Structure for the Shared Directories +---+[.SHARED1] | | DISK4:[SHARED]+----+---+[.SHARED2] | | +---+[.SHARED3] Files and Logical Names Installed on Your System C-9 D ________________________________________________________________ Changing the Configuration of ALL-IN-1 STARTER V2.4 This appendix describes changes to the configuration of ALL-IN-1 STARTER Version 2.4 that do not require an update installation to be performed. You can: o Change the configuration to incorporate WPS-PLUS with ALL-IN-1 STARTER o Change the location of the ALL-IN-1 STARTER Version 2.4 areas CAUTION This task involves modifying the ALL-IN-1 STARTER Version 2.4 configuration database. This database is crucial to the operation of ALL-IN-1 STARTER and changes must be made with extreme care. Digital recommends that you take a backup copy of OA$DATA_SHARE:A1CONFIG.DAT before making any changes. If you want to change to using WPS-PLUS or Message Router for the first time, you must perform an update installation (see Chapter 7). D.1 Change to Using WPS-PLUS If you installed ALL-IN-1 STARTER Version 2.4 without incorporating WPS-PLUS, the WPS-PLUS files were not installed during the installation. Therefore, if you want to use WPS- PLUS with ALL-IN-1 STARTER, you must perform an update installation (see Chapter 7) to install these files, and answer YES to the prompt: Do you want to incorporate WPS-PLUS [YES]? Changing the Configuration of ALL-IN-1 STARTER V2.4 D-1 D.2 Change the Location of an ALL-IN-1 STARTER Version 2.4 Area If you want to move an ALL-IN-1 area to another disk, do the following: 1 Shut down ALL-IN-1 STARTER (see the ALL-IN-1 Management Guide). 2 Copy the directories in that area to the appropriate disk. A list of ALL-IN-1 areas is given in the ALL-IN-1 STARTER Installation Guide Part 3 Market Installation. For a list of the directories in each area see Appendix C, Section C.3. 3 Enter the ALL-IN-1 manager's ALL-IN-1 account: $ ALLIN1 /USERNAME=MANAGER /OVERRIDE=SHUTDOWN 4 Change the ALL-IN-1 STARTER configuration file as follows: a Enter A1CONFIG. The ALL-IN-1 System Configuration Information form is displayed. b Enter the key of the component required: o Enter A1BASE for the base component. The base component description record is displayed. o Enter language name for the appropriate language component. The language component description record is displayed. c Enter C to change the record. d Move the cursor to the field relating to the files that are to be moved. For the base system the fields are: o "File Location" for the ALL-IN-1 STARTER library files o "Data Location" for the ALL-IN-1 STARTER data files o "Site File Loc" for the ALL-IN-1 STARTER site library files o "Site Data Loc" for the ALL-IN-1 STARTER site data files o "ALL-IN-1 Mgr's Dir" for the ALL-IN-1 STARTER manager's directory D-2 Changing the Configuration of ALL-IN-1 STARTER V2.4 Enter the new location of the files. For the language system the fields are: o "File Location" for the ALL-IN-1 STARTER language files o "Site File Loc" for the ALL-IN-1 STARTER site language files Enter the new location of the files. e Press RETURN. f Press EXIT. g Ensure that Message Router is started (see the Message Router books). h Run the ALL-IN-1 STARTER Version 2.4 startup command procedure (see Section 10.10). If you are running ALL- IN-1 STARTER on a VAXcluster system you must run the startup command procedure on all nodes in the cluster. D.3 Moving ALL-IN-1 STARTER If you want to move part or all of your ALL-IN-1 STARTER system to other disks, do the following: 1 Shut down ALL-IN-1 STARTER. 2 Move each area of ALL-IN-1 STARTER (as described in Section D.2). 3 If you want to move mail areas, you must edit the information that is held in the mail area master files. Do this as follows: a Use form SM_SDAF_MASTER to update the location of any SDAFs that you move. b Use form SM_SHARED_DIR_MASTER to update the location of any shared directories that you move. 4 If you use Message Router, ensure that Message Router is started. Changing the Configuration of ALL-IN-1 STARTER V2.4 D-3 5 Run the ALL-IN-1 STARTER startup command procedure, A1V24START.COM, to allow the changes to take effect. If you are running ALL-IN-1 STARTER on a VAXcluster system, you must run the startup command procedure on all nodes in the cluster. D-4 Changing the Configuration of ALL-IN-1 STARTER V2.4 ___________________________________________________________ Index A Build a multilingual system Active processes, 9-3 , 9-16 Additional languages C installation procedure, CDA 4-3, 6-3, 8-3 Converter Library, 1-13 installing, 1-23 patch kit, 1-13 ALL-IN-1 CDA, 1-13 patch Kit, A-3 ALL-IN-1 STARTER CDA Converter Library, invoking, 10-11 1-13, A-3 setup, 10-21 checks, 9-15 Area routing CDA patch kit, 1-13, A-3 define logical OA$MTI_ Checking AREA, 10-15 global page file sections B , 1-30 Backup, 9-4 global pages, 1-30 Batch queue global sections, 1-30 for sending mail, 9-19 Checklist, 1-46 Boot node, 1-22 Cluster See also VAXcluster Index-1 Cluster (Cont.) Directories (Cont.) VMSmail Gateway shared directories, 9-44 configuration, 10-16 Directory Common-environment cluster for ALL-IN-1 STARTER running ALL-IN-1 STARTER, manager's VMS account, 1-18 9-39 Configuration for language files, 9-42 changes, D-1 for mail area SDAF file, changing, 1-1, 1-2 9-43 Configuring for shared data files, VMSmail Gateway, 10-16 9-42 Conventions for shared directories, used in this guide, xxiv 9-43 D for shared library files, 9-42 Date format Disk space requirements selecting, 9-17 for each area, 1-42 DCLTABLES free blocks required, replacing, 10-4 1-45 DECdx/VMS, 1-11 Distribution kit DECnet status, 9-3 examining the, 1-4 DECpage, 1-11 Distribution media Device mounting the, 2-3, 9-5 for ALL-IN-1 STARTER Document structure, xx manager's VMS account, E 9-39 for language files, 9-30 Error messages, 3-2, 4-3, for mail area SDAF file, 5-3, 6-3, 7-3, 8-3 9-32 Errors for shared data files, Sender/Fetcher, 1-35 9-29 H for shared directory, 9-33 Heterogeneous cluster for shared library files, See Multiple-environment 9-28 cluster Directories Homogeneous cluster Index-2 Homogeneous cluster (Cont.) Installation procedure See Common-environment (Cont.) cluster upgrading ALL-IN-1 Housekeeping procedures STARTER V1.0 additional rescheduling, 10-18 languages, 6-3 I Installation requirements number of global buffers, Installation 1-31 aborting, 3-2, 4-3, 5-3, number of global page- 6-3, 7-2, 8-3 file sections, 1-33 checklist, 1-46 number of global pages, completing, 9-46 1-31 disk space required, 1-39 number of global sections keeping a record of, 1-17 , 1-33 linking images, 9-46 process account quotas, modes, 1-40 1-38 Non-Safety mode, 1-41 unused global pages, 1-31 on a VAXcluster system, Installation steps, 9-1 1-18 Installation Verification order of, 1-16 Procedure preparing for, 1-1, 1-24 running, 3-2, 4-2, 5-3, Safety mode, 1-40 6-2, 7-2, 8-2 time required, 1-27 Installed images Installation options, 9-6 required, 1-9 Installation procedure Invoke VMSINSTAL, 9-2 first full installation, IVP 3-3 running, 3-2, 4-2, 5-3, new additional languages, 6-2, 7-2, 8-2, 9-44 4-3 L update of ALL-IN-1 STARTER V2.4, 7-4 Language code, 9-12 update of ALL-IN-1 License Management Facility STARTER V2.4 additional , 1-6 languages, 8-3 License Management Utility upgrade from ALL-IN-1 requirements, 1-46 STARTER V1.0, 5-4 Limiting addressees Index-3 Limiting addressees (Cont.) Message Router (Cont.) in a mail message, 10-22 integrating with, 1-14 LN03 Printer mailbox password, 9-22 setting terminal setting up, 10-14 characteristics for, specifying the node, 9-21 10-18 Message Router VMSmail Load distribution media, Gateway, A-3 9-4, 9-9, 9-45 Messages Local error, 3-2, 4-3, 5-3, Message Router, 1-14, 6-3, 7-3, 8-3 1-21 warning, 3-2, 4-3, 5-3, system, 1-14 6-3, 7-3, 8-3 Log files MR$NODE, 10-15 Mail Error Log, 10-6 Multiple-environment Mail Traffic Log, 10-6 cluster LQP02 Printer running ALL-IN-1 STARTER, setting terminal 1-20 characteristics for, N 10-18 LQP03 Printer New installation, 3-3 setting terminal O characteristics for, 10-18 OA$DDS_PRIME, 10-18 M OA$MTI_AREA, 10-15 Optional software checks, Mail directory 9-24 setup, 10-18 Optional software products, specify level of use, 1-11 9-21 P user agent password, 9-22 Mandatory software checks, PAK 9-24 registering and loading, Market code, 9-11 9-12 Message Router, 1-11, 9-19, Password A-3 configuring, 10-15 Index-4 Password (Cont.) Remote (Cont.) for ALL-IN-1 STARTER VMSmail Gateway manager's VMS account, configuration, 10-16 9-38 Reporting problems, 10-26 for Message Router Required operating system mailbox, 9-22 components, 1-7 Mail directory user agent S , 9-22 Post-installation Satellite node, 1-22, 9-18 terminal characteristics Shared directories, 9-33 for LN03, 10-18 number of, 9-33 terminal characteristics Software Product for LQP02, 10-18 Description, 1-5, 1-6, terminal characteristics A-4 for LQP03, 10-18 Software Warranty Addendum, Preparing for 1-6, A-4 installation, 1-1 SPD, 1-5, 1-6, A-4 Prerequisite SSA, 1-6, A-4 software, 1-8 Startup command procedure Product Authorization Key, executing, 10-7 1-6 Structure registering and loading, of this guide, xx 9-12 SWA, 1-6, A-4 Product identifier, 9-2 SYSGEN, 1-36 Purge System backup, 9-4 files during installation System parameters, 1-36, , 9-14 9-18 R System Support Addendum, 1-6, A-4 Release Notes, 2-1 T accessing, 2-2 printing, 2-2 Terminal characteristics Remote LN03 printer, 10-18 Message Router, 1-15, LQP02 printer, 10-18 1-22 LQP03 printer, 10-18 system, 1-15 Text library Index-5 Text library (Cont.) VMS user name (Cont.) compiling, 10-12 for ALL-IN-1 STARTER installing, 10-12 manager's account, Transfer user accounts 9-35, 9-36 password, 9-38 W Translate WPS-PLUS and DX messages to ASCII, 9-23 Warning messages, 3-2, 4-3, TXL 5-3, 6-3, 7-3, 8-3 compiling, 10-12 WPS-PLUS installing, 10-12 incorporating, 9-15 U integrating, 1-15 WPS-PLUS/VMS UIC converting documents to for ALL-IN-1 STARTER ALL-IN-1 STARTER, 10-22 manager's VMS account, 9-39 for the transfer user accounts, 9-40 Users number of simultaneous, 9-17 V VAXcluster Local Area, 1-22 running ALL-IN-1 STARTER, 1-18, 1-20 VAX FMS, A-3 VMS required version, 1-8 VMSINSTAL, 1-1, 3-1, 4-2, 5-2, 6-2, 7-2, 8-2 invoking, 9-2 VMSmail Gateway configuring, 10-16 VMS user name Index-6