ALL-IN-1____________________________________________ Installation: Guide Order Number: AA-N323J-TE Revision/Update Information: Revised for ALL-IN-1 Version 3.1 Operating system: OpenVMS VAX Version 5.5-2 and higher and OpenVMS AXP Version 6.1 Software version: Version 3.1 ________________________________________________________________ June 1994 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1994. All Rights Reserved. We welcome your comments on this book. Please use one of the following ways to send your comments: o Send an electronic mail message to books@reo.mts.dec.com o Send an electronic mail message to S=IDC BOOKS; O=digital; OU1=reo; P=digital; A=CWMail; C=gb o Send a fax to (+44) 1734 206018 The following are trademarks of Digital Equipment Corporation: ACMS, ALL-IN-1, Alpha AXP, CDA, DDIF, DECnet, DEC FMS, DEC Notes, DECtrace, DECwindows, EDT, MAILbus, OpenVMS, TeamLinks, TeamRoute, VAX, VAXcluster, VAX DATATRIEVE, VAX FMS, VAX Notes, VMS, VMScluster, WPS-PLUS, the AXP logo and the DIGITAL logo. Calendar Manager is a trademark of Russell Information Sciences, Inc. DIF is a trademark of Software Arts Production Corporation. Ethernet is a trademark of Xerox Corporation. Lotus 1-2-3 is a registered trademark of Lotus Development Corporation. MacWrite and MacDraw are registered trademarks of Claris Corporation. Macintosh is a registered trademark of Apple Computer Inc. Microsoft is a registered trademark of Microsoft Corporation. Motif is a registered trademark of Open Software Foundation, Inc. PostScript is a registered trademark of Adobe Systems, Inc. WordPerfect is a registered trademark of WordPerfect Corporation. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... xi 1 Planning an ALL-IN-1 Version 3.1 Installation 1.1 Checklist of Installation Decisions and Information................................... 1-2 1.2 General Information About Installing ALL-IN-1 Version 3.1 .................................. 1-7 1.2.1 Support for Different Architectures....... 1-7 1.2.2 Version 3.1 Architecture-Dependent Files and Directories........................... 1-8 1.2.3 Components of ALL-IN-1 Version 3.1........ 1-8 1.2.4 Additional Languages...................... 1-9 1.2.5 Accounts Needed for ALL-IN-1.............. 1-9 1.2.6 Use of ALL-IN-1 Areas..................... 1-10 1.3 Installation Paths............................ 1-10 1.4 Installing on More Than One Architecture in a VMScluster.................................... 1-14 1.4.1 Installing AXP Architecture Support....... 1-16 1.4.2 Installing VAX Architecture Support....... 1-17 1.4.3 Replacing a VAX System with an AXP System.................................... 1-18 1.5 Mail System Planning.......................... 1-19 1.5.1 Batch Queue for Mail...................... 1-20 1.5.2 Using Message Router...................... 1-20 1.5.3 Level of Mail Directory Support........... 1-21 1.5.4 Setting up a Remote Directory Service..... 1-23 1.5.5 Translating Outgoing Mail Messages to ASCII..................................... 1-24 1.6 Other Software Referenced by the Installation Procedure..................................... 1-25 1.6.1 Software Which can be Integrated During the Installation.......................... 1-25 iii 1.6.2 Compound Document Architecture (CDA) Support................................... 1-26 1.6.3 Installing WPS-PLUS as the Default Editor.................................... 1-27 1.6.4 Using TCP/IP to Communicate With Client Applications.............................. 1-28 1.7 Running the IVP (Installation Verification Procedure).................................... 1-29 1.8 Planning an Upgrade Installation.............. 1-29 1.9 What to do Next............................... 1-30 2 Preparing to Upgrade a Customized System 2.1 Overview of the CART.......................... 2-2 2.2 Modified ALL-IN-1 Systems..................... 2-5 2.3 Understanding the CART Reports................ 2-6 2.3.1 Types of CART Report...................... 2-6 2.3.2 Format of the CART Reports................ 2-8 2.3.3 CART Status Codes and the Severity of Conflict.................................. 2-9 2.4 Preparing to Run the CART..................... 2-11 2.4.1 Printing a System Modification Report..... 2-11 2.4.2 Importing Elements from Outside Customization Management.................. 2-11 2.4.3 Customized Help Modules................... 2-11 2.4.4 Customized Message Files.................. 2-12 2.5 Running the CART.............................. 2-12 2.6 What to do After Running the CART............. 2-14 2.6.1 Checking the Site Elements Report......... 2-14 2.6.2 Checking for Missing Elements (Status Codes B and C)............................ 2-14 2.6.3 Rerunning the CART........................ 2-16 2.6.4 Preparing Your Upgrade Plan............... 2-16 2.6.5 Guidelines for Resolving Conflicts........ 2-18 2.6.6 CART Resolution Procedure................. 2-18 2.6.7 Planning Postinstallation Tasks........... 2-19 2.7 Mandatory Status Codes (I, K, L, M and N)..... 2-20 2.8 Recommended Status Codes (D, E, O, P and Q)... 2-24 2.9 Informational Status Codes (A, F, G, H and R)............................................ 2-27 iv 3 Preparing Your System for Installation 3.1 Preinstallation Checklist..................... 3-1 3.2 Reading and Printing the Online Release Notes......................................... 3-5 3.3 Checking Prerequisite and Optional Software... 3-6 3.4 Linking Software Products During the Installation.................................. 3-9 3.5 Checking the Licence for the Installing Account....................................... 3-10 3.6 Registering License Product Authorization Keys (PAKs)........................................ 3-10 3.6.1 Registering Before a Full Installation.... 3-11 3.6.2 Registering License PAKs for Software Provided with ALL-IN-1 Version 3.1........ 3-11 3.7 Example Order for Installing Optional Software...................................... 3-12 3.8 Installation Procedure Requirements........... 3-13 3.8.1 Installing Account Requirements........... 3-13 3.8.2 System Parameters......................... 3-14 3.8.3 Displaying Current System Parameters...... 3-17 3.8.4 Changing System Parameter Values.......... 3-17 3.8.4.1 Updating Dynamic System Parameters with AUTOGEN................................. 3-19 3.8.4.2 Updating Non-Dynamic System Parameter with AUTOGEN............................ 3-19 3.8.5 Disk Space on Your System Disk or Alternate Working Device.................. 3-20 3.8.6 Using the OA$LIB_SHARE Disk as the AWD.... 3-21 3.8.7 Disk Space for ALL-IN-1 Areas on Target Disks..................................... 3-21 3.8.8 Assigning Logical Names to Your Disks..... 3-22 3.8.9 Full Installation: Disk Space for ALL-IN-1 Areas..................................... 3-23 3.8.10 Upgrade Installation: Disk Space for ALL-IN-1 Areas............................ 3-24 3.8.11 Addition of Architecture Support: Disk Space for ALL-IN-1 areas.................. 3-25 3.8.12 Disk Quota Allocation..................... 3-26 3.8.13 Installed Images.......................... 3-26 3.8.14 Installing FDVMSG.EXE and FDVSHR.EXE Images.................................... 3-27 3.8.15 Installing Other Images................... 3-27 3.8.16 Checking The Location of DCLTABLES.EXE.... 3-28 v 3.9 Additional Tasks for Upgrade Installations.... 3-28 3.9.1 Copying Customized Data Files............. 3-29 3.10 Using a Remote Message Router................. 3-30 3.10.1 Create an ALL-IN-1 Mailbox on the Remote Message Router Node ...................... 3-30 3.11 Preinstallation System Check.................. 3-31 3.11.1 Types of Errors Reported.................. 3-32 3.11.2 Running the Perform all Preinstallation Checks (PC) Option........................ 3-32 3.12 System Preparation Tasks...................... 3-33 3.12.1 Shut Down ALL-IN-1........................ 3-34 3.12.2 Deinstall Files Installed in Memory....... 3-35 3.12.3 Back Up Your System and Target Disks...... 3-35 4 Planning and Implementing a Minimal Shutdown Upgrade 4.1 How the Minimal Shutdown Upgrade Works........ 4-2 4.1.1 Explanation of Phase 1.................... 4-3 4.1.2 Files and Directories Involved in Phase 1......................................... 4-4 4.1.3 Explanation of Phase 2.................... 4-6 4.2 Disadvantages of a Minimal Shutdown Upgrade... 4-8 4.3 Installation Planning Decisions............... 4-8 4.4 Preparing Your System for a Minimal Shutdown Upgrade....................................... 4-9 4.5 Installation Procedure for Minimal Shutdown Upgrade....................................... 4-10 4.5.1 Procedure for Phase 1..................... 4-11 4.5.2 Phase 2 Procedure......................... 4-14 4.6 Manual Postinstallation Procedures............ 4-16 4.6.1 Running the Postinstallation Procedures... 4-19 5 Installation Procedure: Full, Upgrade and Addition of Architecture Support 5.1 Keeping a Record of the Installation.......... 5-3 5.2 Installation Procedure for Full and Upgrade Installations................................. 5-3 5.3 Adding Architecture Support................... 5-23 5.3.1 Before You Start.......................... 5-24 5.3.2 Installation Procedure for Adding Architecture Support...................... 5-25 5.4 Automatic Postinstallation Tasks.............. 5-34 vi 5.5 Manual Postinstallation Tasks................. 5-35 6 Installation Procedure: Additional Languages 6.1 Keeping a Record of the Installation.......... 6-2 6.2 Installation Procedure for Additional Language Installations................................. 6-2 6.3 Installing Architecture Support for an Additional Language........................... 6-11 7 Installation Errors and Failure 7.1 Common Error Message That Does Not Require Action........................................ 7-1 7.2 Common Errors Which Require Action............ 7-1 7.3 Failure During Postinstallation............... 7-2 7.4 Installation Failure.......................... 7-3 7.4.1 Failure of Upgrade Installations in Safety Mode...................................... 7-3 7.4.2 Failure of Upgrade Installations in Non-Safety Mode........................... 7-3 7.4.3 Full Installations........................ 7-4 7.4.4 Failure Due to Insufficient Dynamic Memory.................................... 7-4 7.5 Error Messages when Running the IVP........... 7-4 7.6 IVP Failure................................... 7-6 8 Postinstallation Tasks 8.1 Checklist of Manual Postinstallation Tasks.... 8-1 8.2 Start ALL-IN-1 on all Nodes in a VMScluster System........................................ 8-6 8.3 Create or Modify the Site-specific ALL-IN-1 Startup Procedure............................. 8-6 8.4 Edit the Site-specific Startup Procedure...... 8-7 8.5 Replace the DCLTABLES on Cluster Systems...... 8-9 8.6 Delete Files That Are No Longer Required...... 8-10 8.7 Install Missing Images........................ 8-10 8.8 Recompile Form Libraries...................... 8-11 8.9 Migrate SITELINK30 Using Customization Management.................................... 8-11 8.10 Migrating Your Customizations After Upgrading..................................... 8-12 vii 8.10.1 Running the CART Resolution Procedure..... 8-13 8.10.2 Deleting Obsolete Files................... 8-14 8.10.3 Restoring Customizations to Data Files.... 8-15 8.10.4 Replacing the Help Modules for Your Application............................... 8-16 8.11 Link ALL-IN-1 to Include Code-level Customizations................................ 8-17 8.12 Check Entries in RIGHTSLIST.DAT............... 8-17 8.13 Setting up Remote Mail........................ 8-17 8.13.1 Create a Mailbox for ALL-IN-1............. 8-19 8.13.2 Modifying the Message Router Mailbox Entry..................................... 8-20 8.13.3 Setting Up Area Routing................... 8-20 8.13.4 Configuring the VMSmail Gateway for Remote Access.................................... 8-22 8.13.5 Setting Up the Mail Directory............. 8-22 8.13.5.1 Message Router is in the Same VMScluster.............................. 8-23 8.13.5.2 Message Router is not in the Same VMScluster.............................. 8-25 8.13.6 Remote Mail Directory Startup Procedure... 8-27 8.14 Restoring Your Sender and Fetcher Environment................................... 8-28 8.15 Delete or Remove Old Mail Log Files........... 8-28 8.16 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1 ..................................... 8-28 8.17 WPS-PLUS Login Command Procedure.............. 8-30 8.18 Install the File Cabinet Server Distributed License....................................... 8-31 8.19 Moving the CDA DOC_STYLE Files................ 8-31 8.20 Update the Facility Definition to Use DECtrace...................................... 8-31 A ALL-IN-1 Version 3.1 Distribution Media A.1 Magnetic Tape and TK50 Kits (for VAX Installations)................................ A-1 A.2 Compact Disc Distribution Kits (VAX or AXP Installations)................................ A-3 viii B ALL-IN-1 Version 3.1 Files and Directories B.1 New Directories Created in ALL-IN-1 Version 3.1........................................... B-1 B.2 Files in the ALL-IN-1 Kit..................... B-2 B.3 Files Installed in Non- ALL-IN-1 Directories................................... B-2 Index Figures 1-1 Installing AXP Architecture Support....... 1-17 1-2 Installing VAX Architecture Support....... 1-18 2-1 What the CART Does........................ 2-4 4-1 Minimal Shutdown Upgrade: Phase 1......... 4-3 4-2 Minimal Shutdown Postinstallation Phase... 4-17 Tables 1-1 Checklist of Installation Decisions and Information Required...................... 1-2 1-2 Installation Paths........................ 1-12 1-3 Strategy for Adding Architecture Support................................... 1-15 1-4 Mail System Planning Decisions............ 1-19 1-5 Installation Options for Levels of Mail Directory Support......................... 1-22 1-6 Questions Asked During a Customized Configuration............................. 1-24 1-7 TCP/IP Service Information................ 1-28 1-8 What To Do Next........................... 1-30 2-1 Terminology used by the CART.............. 2-2 2-2 CART Reports.............................. 2-7 2-3 CART Conflict Severity, Status Codes and Actions................................... 2-10 2-4 CART Status Codes B and C................. 2-15 2-5 Mandatory Status Codes (I, K, L, M and N)........................................ 2-21 ix 2-6 Recommended Status Codes (D, E, O, P, Q).. 2-25 2-7 Informational Status Codes (A, F, G, H, R) 2-28 3-1 Preinstallation Checklist................. 3-1 3-2 Prerequisite and Optional Software........ 3-7 3-3 Process Account Quotas for the Installing Account................................... 3-14 3-4 Minimum System Parameter Values Required.................................. 3-15 3-5 Changing System Parameter Values.......... 3-18 3-6 Full Installation: Disk Space for ALL-IN-1 Areas..................................... 3-23 3-7 Upgrade Installations: Disk Space for ALL-IN-1 Areas ........................... 3-25 3-8 Addition of Architecture Support: Disk Space for ALL-IN-1 Areas.................. 3-26 4-1 Minimal Shutdown Upgrade: Disk Space for ALL-IN-1 Areas ........................... 4-10 4-2 Installation Procedure for Phase 1 of the Minimal Shutdown Upgrade ................. 4-11 4-3 Installation Procedure for Phase 2 of the Minimal Shutdown Upgrade ................. 4-14 4-4 Minimal Shutdown Postinstallation Procedures................................ 4-17 5-1 Information About the Installation Procedure................................. 5-2 5-2 Installation Procedure for Full and Upgrade Installations..................... 5-4 5-3 When to Install VAX or AXP Architecture Support................................... 5-24 5-4 Installation Procedure for Adding Architecture Support...................... 5-25 6-1 Installation Procedure for An Additional Language ................................. 6-3 6-2 Installation Procedure for Addition of Architecture Support for an Additional Language.................................. 6-11 8-1 Postinstallation Tasks.................... 8-1 x 8-2 Editing the OpenVMS Site-specific Startup File...................................... 8-8 8-3 Tasks for Setting up Remote Mail.......... 8-18 B-1 New ALL-IN-1 Directories for Architecture Dependent Files........................... B-1 xi _________________________________________________________________ Preface About This Book This guide describes how to do the following: 1. Plan an ALL-IN-1 Version 3.1 installation on: - An OpenVMS AXP system (standalone or in a VMScluster) - An OpenVMS VAX system (standalone or in a VMScluster) 2. Prepare your system for an ALL-IN-1 Version 3.1 installation. 3. Install ALL-IN-1 Version 3.1. 4. Set up ALL-IN-1 Version 3.1 so that the ALL-IN-1 manager can log in and use it locally. ALL-IN-1 Installation: Language and Market Supplement The ALL-IN-1 Installation: Language and Market Supplement is provided with your language and market kit. It provides the disk space values for installing the ALL-IN-1 Version 3.1 kit, and information on the language and market components that you will need during the installation. Prerequisite Knowledge In order to use this guide, you need the following experience: o To install ALL-IN-1 Version 3.1 you must be familiar with the VMSINSTAL utility. xi o To run the Conflict Checking and Resolution Tool you must be familiar with ALL-IN-1 application programming, Customization Management, and ideally, the customizations at your site. Management Documentation Set In addition to the ALL-IN-1 Installation: Guide and the ALL-IN-1 Installation: Language and Market Supplement, the Management documentation set contains the following: o ALL-IN-1 Version 3.1 Release Notes o ALL-IN-1 Management Guide This guide describes the tasks for setting up and managing an ALL-IN-1 Version 3.1 system, so that it operates efficiently. o ALL-IN-1 Mail Management Guide This guide describes how to plan and manage an ALL-IN-1 Version 3.1 mail system. o Differences Between ALL-IN-1 Version 3.0 and ALL-IN-1 Version 3.1. This document introduces the new and changed functionality in ALL-IN-1 Version 3.1. In addition, there are answers to some common questions about the new version. o ALL-IN-1 WPS-PLUS Printer Characteristics This guide describes the use of printer tables, and teaches you how to use the printer table utility to customize existing printer tables to meet your needs. Related Documents You may also need to refer to the documentation on the following products: o VAX Message Router o DEC Notes[TM] o OpenVMS system management xii Conventions The following conventions are used throughout this guide: ___________________________________________________________ Convention__Description____________________________________ AIDA Means ALL-IN-1[TM] Distributed Access Server Server ALL-IN-1 Means the ALL-IN-1[TM] software that is installed on your system, for example, ALL-IN-1 Integrated Office System (IOS) Server or ALL-IN-1 Core Services for OpenVMS[TM] AXP[TM] and OpenVMS VAX[TM]. OpenVMS Means the OpenVMS AXP operating system AXP OpenVMS Means the OpenVMS VAX operating system VAX TLC Means TeamLinks[TM] Connection to ALL-IN-1 IOS for OpenVMS VMScluster Discussions that refer to VMScluster systems environments apply to both VAXcluster systems that include only VAX nodes and VMScluster systems that include at least one AXP node. Any differences are noted in the text. WPS-PLUS Means WPS-PLUS[TM] software [] In the installation description, this indicates a default value. Press Return to use the default value CTRL/Z Indicates that you hold down the CTRL key while ____________pressing_the_other_key_(Z).____________________ Returning Comments About this Documentation We would like to know what you think about the ALL-IN-1 documentation set. If you have any comments, or suggestions, please return them in any of the following ways: o Fill out and submit the Reader's Comments form at the back of the printed book o Send an electronic mail message to books@reo.mts.dec.com xiii o Send an electronic mail message to S=IDC BOOKS; O=digital; OU1=reo; P=digital; A=CWMail; C=gb o Send a fax to (+44) 1734 206018 xiv 1 _________________________________________________________________ Planning an ALL-IN-1 Version 3.1 Installation This chapter contains background information about installing ALL-IN-1 Version 3.1 and covers the following topics: o Installation paths o Installing on a VMScluster o Preinstallation planning decisions o Information required during the installation If ALL-IN-1 Version 3.0 is already installed on your system and you have customized it, you must also read Chapter 2 which explains how to prepare your customized system for an upgrade installation. Allow enough time for planning before you intend to install ALL-IN-1 Version 3.1 as the planning will take some time, especially if you are upgrading from a previous version of ALL-IN-1. In addition to this installation guide, you should also read the ALL-IN-1 Installation: Language and Market Supplement that is supplied with your kit. This provides the language and market-specific information that you need to know when installing ALL-IN-1 Version 3.1. Section 1.1 gives a list of all the questions that you will be asked during the installation. Planning an ALL-IN-1 Version 3.1 Installation 1-1 Planning an ALL-IN-1 Version 3.1 Installation 1.1 Checklist of Installation Decisions and Information 1.1 Checklist of Installation Decisions and Information Table 1-1 lists the questions that you will be asked during an ALL-IN-1 Version 3.1 installation and gives you references to additional information in this chapter where appropriate. The table follows the order of questions in the installation script. Table 1-1 Checklist of Installation Decisions and __________Information_Required_____________________________ Decision___________________Where_to_Find_Information_______ What type of installation Section 1.2 gives general do you want to perform? information about installing on OpenVMS VAX and OpenVMS AXP. Section 1.3 describes the installation options and explains how to plan an ALL-IN-1 installation on a VMScluster consisting of both VAX and AXP nodes. Section 1.8 and Chapter 2 explain how to plan an upgrade installation. ___________________________________________________________ Do you want to integrate Section 1.6.1 DATATRIEVE during the installation? ___________________________________________________________ Do you want to install Section 1.6.3 WPS-PLUS with ALL-IN-1? ___________________________________________________________ Do you want to integrate Section 1.6.1 ACMS (Application Control and Management System) during the installation? (continued on next page) 1-2 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.1 Checklist of Installation Decisions and Information Table 1-1 (Cont.) Checklist of Installation Decisions and __________________Information_Required_____________________ Decision___________________Where_to_Find_Information_______ ___________________________________________________________ Do you want to build a Section 1.3 multilanguage ALL-IN-1 system? ___________________________________________________________ Which ALL-IN-1 date A list of date formats format do you want to is displayed during the use? installation. See the ALL-IN-1 Installation: Language and Market Supplement for the default. ___________________________________________________________ What will be the greatest This is the number of users that number of simultaneous you expect to use ALL-IN-1 at ALL-IN-1 users? the same time. Identify which node on the cluster has the most users, and use that value during the installation. On which batch queue Section 1.5.1 should the Sender/Fetcher check job run? ___________________________________________________________ (continued on next page) Planning an ALL-IN-1 Version 3.1 Installation 1-3 Planning an ALL-IN-1 Version 3.1 Installation 1.1 Checklist of Installation Decisions and Information Table 1-1 (Cont.) Checklist of Installation Decisions and __________________Information_Required_____________________ Decision___________________Where_to_Find_Information_______ Do you want ALL-IN-1 Section 1.5 and Chapters 1 and 2 to be configured to use in the ALL-IN-1 Mail Management Message Router? Guide. If you do, you will be asked the following: o Do you want to use a remote Message Router? o What node is the Message Router on? o What level of Mail directory support do you want? ___________________________________________________________ Do you want to translate Section 1.5.5 outgoing WPS-PLUS messages to ASCII? ___________________________________________________________ Do you want to use TCP Section 1.6.4 /IP? If you answer yes, you will be prompted for the port numbers for the AIDA and File Cabinet servers if they do not already exist. ___________________________________________________________ (continued on next page) 1-4 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.1 Checklist of Installation Decisions and Information Table 1-1 (Cont.) Checklist of Installation Decisions and __________________Information_Required_____________________ Decision___________________Where_to_Find_Information_______ What is the language ALL-IN-1 Installation: Language code? and Market Supplement If your language includes a dialect code, you also need to supply the dialect code. ___________________________________________________________ For full installations, Section 1.2.6 you will be asked for the name of the device that will hold the ALL-IN-1: o Shared library files o Shared data files o Language files o Mail area SDAF (Shared Document Attributes File) file ___________________________________________________________ How many shared If you want to create more than directories do you want 2 or 3 shared directories, it is to create? recommended that you enter 1 at the installation prompt and then create the shared directories from the Management subsystem after installation is complete. See Chapter 7 in the ALL-IN-1 Management Guide. ___________________________________________________________ What is the market code ALL-IN-1 Installation: Language for the installation? and Market Supplement (continued on next page) Planning an ALL-IN-1 Version 3.1 Installation 1-5 Planning an ALL-IN-1 Version 3.1 Installation 1.1 Checklist of Installation Decisions and Information Table 1-1 (Cont.) Checklist of Installation Decisions and __________________Information_Required_____________________ Decision___________________Where_to_Find_Information_______ ___________________________________________________________ For full installations, See Section 1.2.5. you are asked to supply the following details for the ALL-IN-1 MANAGER account: o OpenVMS username o Password o UIC o Default device o Default directory You are also asked to supply a different UIC for each ALL-IN-1 utility account. ___________________________________________________________ For full installations, Section 1.2.6 and Section 3.8.7 you are asked to supply a top-level directory specification for the following: o Shared library files o Shared data files o Language files o Mail area SDAF file o Shared directories ___________________________________________________________ (continued on next page) 1-6 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.1 Checklist of Installation Decisions and Information Table 1-1 (Cont.) Checklist of Installation Decisions and __________________Information_Required_____________________ Decision___________________Where_to_Find_Information_______ Do you want to run See Section 1.7. the IVP after the installation? ___________________________________________________________ What to do after reading See Section 1.9 this chapter . ___________________________________________________________ 1.2 General Information About Installing ALL-IN-1 Version 3.1 This section gives some background information about installing ALL-IN-1 Version 3.1. Note that the ALL-IN-1 Version 3.1 base kit provides all the files required to install ALL-IN-1 Version 3.1 on a VAX system or an AXP system. In this book, the term architecture is used to differentiate between OpenVMS VAX systems and OpenVMS AXP systems. For example, architecture-independent files, means files that can be used on both VAX and AXP systems. If ALL-IN-1 is already installed on an OpenVMS VAX system in a VMScluster, then architecture support for ALL-IN-1 can be installed on an AXP system in the same cluster. The term mixed architecture cluster means a VMScluster that contains both AXP and VAX nodes. 1.2.1 Support for Different Architectures The ALL-IN-1 Version 3.1 kit contains all the software that is required to install ALL-IN-1 on an OpenVMS VAX system or an OpenVMS AXP system. You can install and run ALL-IN-1 Version 3.1 on a VMScluster consisting of both VAX and AXP nodes. The majority of the ALL-IN-1 Version 3.1 files are architecture-independent and common to both VAX and Alpha AXP architectures. Separate ALL-IN-1 system files are provided for each architecture. Planning an ALL-IN-1 Version 3.1 Installation 1-7 Planning an ALL-IN-1 Version 3.1 Installation 1.2 General Information About Installing ALL-IN-1 Version 3.1 For more information about installing on a VMScluster, see Section 1.4. 1.2.2 Version 3.1 Architecture-Dependent Files and Directories The majority of ALL-IN-1 Version 3.1 files are architecture-independent and shared by both AXP and VAX systems. The shared ALL-IN-1 Version 3.1 files are installed during an installation on either a VAX system or an AXP system. There are some architecture specific files which are only installed when the installation procedure is run on that architecture, for example, executable and shareable images. When the ALL-IN-1 startup command procedure is run on each node to start up ALL-IN-1, it uses the information in the data file, OA$DATA_SHARE:A1CONFIG.DAT to define the logicals for the VAX-specific and AXP-specific directories. For example, on a VAX system OA$EXE_SHARE is defined to point to the directory, OA$EXE_VAX_SHARE. On an AXP system, OA$EXE_SHARE is defined to point to the directory OA$EXE_ AXP_SHARE. 1.2.3 Components of ALL-IN-1 Version 3.1 The ALL-IN-1 Version 3.1 kit has the following components: o International base component which is common to all installations and which is country and language independent. o Language component. The language supplied with your ALL-IN-1 Version 3.1 kit is the default (or primary) language that is provided in the language field of a user's account details. Some languages may also have a dialect component. A dialect component may be required when a language is spoken in more than one country. There may be some differences in the language, depending on which country it is being used in. o Market component. The market component provides market-specific features such as currency, date formats, address formats and keyboard support. 1-8 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.2 General Information About Installing ALL-IN-1 Version 3.1 The installation procedure in Chapter 5 describes how to install all of these components. During the installation, you will be asked to supply information about the language and market components that you are installing with your base system. See the ALL-IN-1 Installation: Language and Market Supplement. 1.2.4 Additional Languages In addition to the primary language supplied with your kit, you can install and use other languages with ALL-IN-1 Version 3.1. You must, however, install each language separately using the additional language installation procedure. See Chapter 6. ________________________ Note ________________________ You must upgrade all additional languages to Version 3.1 before you can use them with ALL-IN-1 Version 3.1. Earlier versions of additional languages are not supported. ______________________________________________________ During the ALL-IN-1 Version 3.1 installation you will be asked if you want to build a multilanguage system. Answer yes to this prompt if you want to install additional languages. You can build a multilanguage system at any time after the installation by relinking ALL-IN-1 Version 3.1 and answering yes when you are prompted with the question again. See the ALL-IN-1 Management Guide for details on linking the ALL-IN-1 image. 1.2.5 Accounts Needed for ALL-IN-1 ALL-IN-1 needs an OpenVMS account for running the ALL-IN-1 management batch jobs. This OpenVMS account has four ALL-IN-1 accounts: o MANAGER account for running ALL-IN-1 management tasks. o POSTMASTER account for running the mail Sender and Fetcher. o IVP account for running the installation verification procedure. Planning an ALL-IN-1 Version 3.1 Installation 1-9 Planning an ALL-IN-1 Version 3.1 Installation 1.2 General Information About Installing ALL-IN-1 Version 3.1 o A1$SCRIPT account for running the script symbiont. See Chapter 19 in the ALL-IN-1 Management Guide for more information about ALL-IN-1 accounts. 1.2.6 Use of ALL-IN-1 Areas You can install ALL-IN-1 Version 3.1 in the following ways: o On a single target disk o Across several target disks by installing ALL-IN-1 areas on separate disks. The areas are: o Shared library files, for example, OA$LIB_SHARE and OA$BLP_SHARE. This area contains language-independent files, scripts, templates and form libraries. o Shared data files, for example, OA$DATA_SHARE. This area contains shared data files, for example printer management files. o Language files, for example, OA$LIB_language. This area contains form libraries and similar language-specific files. For more information about the ALL-IN-1 files and directories, see Chapter 19 in the ALL-IN-1 Management Guide. 1.3 Installation Paths The following types of installation are provided for ALL-IN-1 Version 3.1: o A full installation which installs a new ALL-IN-1 system. o An upgrade installation which upgrades an existing ALL-IN-1 Version 3.0 system. o The addition of architecture support. This adds support for an additional architecture where a full ALL-IN-1 Version 3.1 system is already installed on a different architecture in the same VMScluster. For example, you can use this option when you are installing ALL-IN-1 Version 3.1 in a VMScluster consisting of both AXP and 1-10 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.3 Installation Paths VAX systems. You can do an upgrade installation on the VAX system and then add AXP support on the AXP system. o An additional language installation. If you want to run your ALL-IN-1 system as a multilanguage system, you can install other languages in addition to your primary language. See Chapter 6. o The addition of architecture support for an additional language. This adds support for an additional architecture where the additional language is already installed on a different architecture in the same VMScluster. o A minimal shutdown upgrade. This option is provided for sites where system downtime is critical. The implications of using this option are discussed in Chapter 4. o An update installation. This option updates the files for an existing ALL-IN-1 Version 3.1 system. Table 1-2 gives a complete list of supported installation paths for ALL-IN-1 Version 3.1. Planning an ALL-IN-1 Version 3.1 Installation 1-11 Planning an ALL-IN-1 Version 3.1 Installation 1.3 Installation Paths Table_1-2_Installation_Paths_______________________________ Type_of_Installation__Use_When_____________________________ Full You do not have a version of ALL-IN-1 installed. You can install a new ALL-IN-1 Version 3.1 system on a VAX system or an AXP system. Upgrade One of the following versions of ALL-IN-1 is already installed on a VAX system: o ALL-IN-1 Version 3.0[1] o ALL-IN-1 STARTER Version 3.0 Minimal shutdown ALL-IN-1 Version 3.0 is already upgrade installed and system downtime is critical for your organization. See Chapter 4. Update ALL-IN-1 Version 3.1 is already installed Add VAX architecture ALL-IN-1 Version 3.1 is already support installed on an AXP system in a VMScluster. Add AXP architecture ALL-IN-1 Version 3.1 is already support installed on a VAX system in a VMScluster. Additional language You want to add a new additional language to an existing ALL-IN-1 Version 3.1 multilanguage system. Upgrade additional Version 3.0 of an additional language language is already installed and you have upgraded your primary language to Version 3.1 Update additional Version 3.1 of an additional language language is already installed. [1]Optionally_with_ALL-IN-1_Version_3.0A_installed_and_____ TeamLinks Connection Version 2.0 or Version 2.1. (continued on next page) 1-12 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.3 Installation Paths Table_1-2_(Cont.)_Installation_Paths_______________________ Type_of_Installation__Use_When_____________________________ Add VAX architecture ALL-IN-1 Version 3.1 and Version support for an 3.1 of the additional language are additional language already installed on an AXP system in the same VMScluster. Add AXP architecture ALL-IN-1 Version 3.1 and Version support for an 3.1 of the additional language are additional language already installed on a VAX system in ______________________the_same_VMScluster._________________ Planning an ALL-IN-1 Version 3.1 Installation 1-13 Planning an ALL-IN-1 Version 3.1 Installation 1.4 Installing on More Than One Architecture in a VMScluster 1.4 Installing on More Than One Architecture in a VMScluster If you want to install ALL-IN-1 Version 3.1 on a VMScluster with both VAX and AXP nodes, you must consider the following: o Each architecture requires its own system disk. This means that you must not use SYS$SYSDEVICE in ALL-IN-1 directory locations as SYS$SYSDEVICE cannot be the same for both the the VAX system and the AXP system. o VAX images can only be linked on a VAX system and AXP images can only be linked on an AXP system. o All existing ALL-IN-1 systems on VAX must be upgraded to Version 3.1 before you can add AXP support. o The VAX and the AXP must have a common user environment. This means that the VAX and AXP both reference the same data files for the AUTHORIZE utility. o You can spread the ALL-IN-1 areas around your cluster disks, just as you would for a single-node system. See Section 3.8.7. o You must run the ALL-IN-1 startup command procedure on all nodes in the part of the cluster with the common ALL-IN-1 user environment. You do not need to perform a full ALL-IN-1 Version 3.1 installation on both AXP and VAX machines in the same VMScluster. Once you have installed a full ALL-IN-1 Version 3.1 system on either VAX or AXP, you can then add architecture support for ALL-IN-1 on the second architecture. Table 1-3 shows the strategy to follow when you want to install ALL-IN-1 on both VAX and AXP nodes in a VMScluster. 1-14 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.4 Installing on More Than One Architecture in a VMScluster Table_1-3_Strategy_for_Adding_Architecture_Support_________ If_________________________Then____________________________ ALL-IN-1 Version 3.0 or Do the following: ALL-IN-1 STARTER Version 1. Do an upgrade installation to 3.0 is already installed ALL-IN-1 Version 3.1 on the on a VAX system VAX 2. Add AXP architecture support on the AXP ALL-IN-1 is not installed Do the following: on your VMScluster 1. Do a full ALL-IN-1 Version 3.1 installation on the AXP system 2. Add VAX architecture support on the VAX This order of installation gives ___________________________you_the_best_performance._______ For general information about running ALL-IN-1 on a VMScluster, see Chapter 5 in the ALL-IN-1 Management Guide. Planning an ALL-IN-1 Version 3.1 Installation 1-15 Planning an ALL-IN-1 Version 3.1 Installation 1.4 Installing on More Than One Architecture in a VMScluster 1.4.1 Installing AXP Architecture Support If you already have a version of ALL-IN-1 installed on a VAX system, you must upgrade it to ALL-IN-1 Version 3.1 before you can add AXP architecture support on the AXP system. Figure 1-1 shows which files are installed during each part of the installation. When you upgrade ALL-IN-1 Version 3.0 to ALL-IN-1 Version 3.1, directories are created for the following files: o VAX-specific files o AXP-specific files. The locations of these directories are derived from the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT. The shared files and VAX-specific files are installed into these directories during the upgrade but the AXP-specific files are not installed until you add AXP architecture support. When you install additional architecture support for AXP, the following files are installed: o AXP system files for ALL-IN-1 on the AXP system disk o AXP-specific files into the directories already created during the ALL-IN-1 Version 3.1 installation on the VAX system. When adding AXP support, the installation procedure prompts you for the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT, on the VAX that is already running ALL-IN-1 Version 3.1. The ALL-IN-1 startup file, A1V31START.COM reads the information in this file and defines the logicals to point to to the AXP-specific directories that were created during the ALL-IN-1 Version 3.1 installation on the VAX system. The AXP-specific files are then installed in the directories that have already been created during the upgrade installation on VAX. 1-16 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.4 Installing on More Than One Architecture in a VMScluster Figure 1-1 Installing AXP Architecture Support 1.4.2 Installing VAX Architecture Support If you do not have a version of ALL-IN-1 installed, you can install ALL-IN-1 Version 3.1 on an AXP system and then add VAX architecture support on the VAX. When you install a new ALL-IN-1 system on AXP, all the shared, architecture- independent, and AXP-specific files are installed on your data disk. AXP-specific system files are installed on your AXP system disk. The directories for VAX-specific files are created during the installation but they are left empty. When you add VAX architecture support, the VAX-specific system files are installed on the VAX system disk, and the VAX-specific files are installed in the VAX directories that have already been set up during the full installation on the AXP. See Figure 1-2. The installation procedure prompts you for the location of the ALL-IN-1 configuration file, OA$DATA_ SHARE:A1CONFIG.DAT, for the existing ALL-IN-1 Version 3.1 AXP system. The ALL-IN-1 startup file, A1V31START.COM reads the information in the configuration file and creates the pointers to the VAX-specific directories that were created during the ALL-IN-1 Version 3.1 installation on the AXP system. The VAX-specific files are installed in the directories that have already been created during the installation on AXP. Planning an ALL-IN-1 Version 3.1 Installation 1-17 Planning an ALL-IN-1 Version 3.1 Installation 1.4 Installing on More Than One Architecture in a VMScluster Figure 1-2 Installing VAX Architecture Support 1.4.3 Replacing a VAX System with an AXP System Read this section if you: o Have hardware that can be upgraded from VAX to Alpha AXP o Have an existing standalone VAX system that you are replacing with an AXP system Your strategy for installing ALL-IN-1 Version 3.1 will depend on whether ALL-IN-1 is already installed. ________________________ Note ________________________ If you have an existing ALL-IN-1 Version 3.0 system, you must upgrade it to ALL-IN-1 Version 3.1 before you change your hardware to Alpha AXP or replace your VAX. This ensures that you retain your ALL-IN-1 configuration and that the ability to support two architectures is installed. If you do not upgrade to ALL-IN-1 before changing your hardware to AXP or replace your VAX, ALL-IN-1 will not be available until you do a full installation on AXP. You will lose any customizations that you have made and you will have to set up ALL-IN-1 as a completely new system. ______________________________________________________ When you have upgraded your hardware to Alpha AXP, you can add AXP support for ALL-IN-1 to your existing ALL-IN-1 Version 3.1 system. If you have not installed a previous version of ALL-IN-1 on your Alpha-ready system, do a full ALL-IN-1 Version 3.1 installation when you have upgraded your hardware to Alpha AXP. 1-18 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.5 Mail System Planning 1.5 Mail System Planning This section describes the planning decisions that you need to make about your mail system before installing ALL-IN-1 Version 3.1. ________________________ Note ________________________ For the full implications of planning a mail system, you must read Chapters 1 and 2 in the ALL-IN-1 Mail Management Guide before starting the installation. ALL-IN-1 running on an AXP system must use a remote Message Router running on a VAX. This VAX can be in the same VMScluster or remote from the cluster. The ALL-IN-1 Mail Management Guide gives details of planning the use of a remote Message Router. Section 8.13 describes the postinstallation tasks that you must do in order to set up remote mail. ______________________________________________________ Table 1-4 lists the decisions that you need to make when planning your mail system. Table_1-4_Mail_System_Planning_Decisions___________________ Decision___________________Where_to_Find_Information_______ Which batch queue you See Section 1.5.1. want to use for running the job to check the mail Sender and Fetcher processes. Do you want ALL-IN-1 See Section 1.5.2. to be configured to use Message Router? Do you want to use a See Section 1.5.2 and remote Message Router? Section 1.5.4. What level of Mail See Section 1.5.3. directory support do you_want?__________________________________________________ Planning an ALL-IN-1 Version 3.1 Installation 1-19 Planning an ALL-IN-1 Version 3.1 Installation 1.5 Mail System Planning 1.5.1 Batch Queue for Mail ALL-IN-1 uses a system batch queue to run the job that checks the mail Sender and Fetcher processes. The default option at installation is to use SYS$BATCH, but you can specify the name of another batch queue that already exists. If you are installing ALL-IN-1 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. 1.5.2 Using Message Router ALL-IN-1 uses Message Router to send messages to, and receive messages from, other nodes and mail systems. The ALL-IN-1 Version 3.1 kit supplies: o Message Router Version 3.3A o Message Router VMSmail Gateway (MRGATE) Version 3.3. ALL-IN-1 uses the Message Router VMSmail Gateway to exchange messages with VMSmail users on other nodes. The gateway must be installed and configured before you install ALL-IN-1 Version 3.1. Message Router is known as a local Message Router when it is installed on the same node as ALL-IN-1 and a remote Message Router when it is installed on a different node. When Message Router is installed on a node that is not in the same VMScluster, it is known as the server node. Both VAX and AXP nodes in a VMScluster can use a remote Message Router. ________________________ Note ________________________ When you install ALL-IN-1 on an AXP system, you must use a remote Message Router. ______________________________________________________ If you are using a local Message Router, you must upgrade it to Version 3.3A before you install ALL-IN-1 Version 3.1. 1-20 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.5 Mail System Planning If you want to use a remote Message Router, you must do the following before installing ALL-IN-1 Version 3.1: 1. If a previous version of Message Router is installed on your system, you must upgrade it to Version 3.3A. Message Router Version 3.3A allows you to use the remote Message Router Directory Service and Transfer Service from ALL-IN-1 on a VAX system or an AXP system. 2. In order to use the remote Directory Service, Message Router must be correctly configured. To use a remote Message Router Directory Service, you must do a customized configuration of the Message Router Directory Service. See Section 1.5.4. 3. Decide if you want to use Message Router exception reporting. See Chapter 2 in the ALL-IN-1 Mail Management Guide for information about planning exception reporting. 4. If your ALL-IN-1 node or cluster will be using a remote Message Router server node, you must create a mailbox entry for ALL-IN-1 on the Message Router server node before you start the installation. See Section 3.10.1. If you do not do this, you will have problems when the Sender and Fetcher processes are started up by the installation procedure. 1.5.3 Level of Mail Directory Support Table 1-5 shows the installation options that are available for setting the level of Mail directory support. Directories allow users to look up names and electronic mail addresses of users in the network. There are two directories for addressing available with ALL-IN-1: o The ALL-IN-1 directory. This is provided with ALL-IN-1 and is always available. o The Mail directory This is provided by the Directory Service component of Message Router and it is optional. It contains the names, mail addresses and other details of all Mail directory subscribers on the network. Planning an ALL-IN-1 Version 3.1 Installation 1-21 Planning an ALL-IN-1 Version 3.1 Installation 1.5 Mail System Planning ________________________ Note ________________________ Digital recommends that you use the ALL-IN-1 directory as the primary directory and the Mail directory as the secondary directory to reduce the response time. For more information about the two types of directory, and for help with deciding which to use, see Chapter 2 in the ALL-IN-1 Mail Management Guide. In ALL-IN-1 Version 3.1, Message Router does not have to be installed on the same node as ALL-IN-1 in order to use the Mail directory. Remote Directory Service enquiries can be made from ALL-IN-1 Version 3.1 running on either a VAX system or an AXP system, provided that: o Message Router V3.3A is installed on a remote VAX node o The Directory Service component has a customized configuration to start up the query servers o The Directory Service node is a world search node You can update Directory Service entries remotely but this is not an automatic process. For the implications of updating remote Directory Service entries, see Chapter 4 in the ALL-IN-1 Mail Management Guide. ______________________________________________________ Table 1-5 Installation Options for Levels of Mail Directory __________Support__________________________________________ Level of Mail Directory Support__________Meaning___________________________________ 0 The ALL-IN-1 directory is the primary directory for users to look up mail addresses. The Mail directory is not available (continued on next page) 1-22 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.5 Mail System Planning Table 1-5 (Cont.) Installation Options for Levels of Mail __________________Directory_Support________________________ Level of Mail Directory Support__________Meaning___________________________________ 1 The ALL-IN-1 directory is the primary directory for users to look up names and mail addresses. The Mail directory is available as the secondary directory. 2 The Mail directory is the primary directory for users to look up names and addresses. The ALL-IN-1 directory is available as the _________________secondary_directory.______________________ The value 0, 1 or 2 is the value given to the logical OA$DDS_PRIME. You can change the value of this logical after installation. If you do not want to make the decision about the Mail directory when you install, you can set the value to 1 so that you can either ignore the Directory Service or set it up later. See the ALL-IN-1 Mail Management Guide. 1.5.4 Setting up a Remote Directory Service In order to use a remote Message Router Directory Service, you must do a customized configuration of the Directory Service to set up the query servers. When you do a customized configuration of the Directory Service, query servers are set up to service remote enquiries to the Directory Service node which must be a world search node. See the Message Router Configuration Guide for details of configuring Message Router using the MAILbus configuration procedure, MB$CONFIG. If you do a default configuration of the Directory Service component of Message Router instead of a customized configuration, the query servers are not set up and you cannot make remote enquiries. Planning an ALL-IN-1 Version 3.1 Installation 1-23 Planning an ALL-IN-1 Version 3.1 Installation 1.5 Mail System Planning Table 1-6 list some of the questions that you will be asked during the customized configuration: Table_1-6_Questions_Asked_During_a_Customized_Configuration Question________________________What_You_Must_Do___________ Do you want to enable Answer Y to enable the Directory Service exception exception reporting. reporting? The exception reporting routines monitor the Directory Service for errors and unusual occurrences. See Chapter 2 in the ALL-IN-1 Mail Management Guide for information about planning exception reporting. Do you want to allow remote Answer Y to allow remote Directory Service access? access to the Directory Service. You are prompted for the number of query servers that you want to ________________________________create.____________________ The Message Router Configuration Guide gives more detailed information about doing a customized configuration. Chapter 2 in the ALL-IN-1 Mail Management Guide gives further information about using a Remote Message Router. 1.5.5 Translating Outgoing Mail Messages to ASCII If all nodes in a network are running ALL-IN-1, then mail can be sent between the nodes in the same format in which it was created, for example, WPS-PLUS or ASCII text. Other user agents in different parts of a network may not be able to translate WPS-PLUS messages, so mail must be sent between the nodes in ASCII format. During the installation you are asked if you want to to translate outgoing messages to ASCII. The following options are available: o Messages are not translated to ASCII (MTI_TRNS is set to 0). 1-24 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.5 Mail System Planning o Only the message part is translated, leaving all document attachments in their original format (MTI_ TRNS is set to 1). o All of the message is translated to ASCII, including the message part and all document attachments (MTI_TRNS is set to 2). 1.6 Other Software Referenced by the Installation Procedure This section covers software that is referred to by the installation procedure. It includes: o Software that can be integrated (linked to the ALL-IN-1 image) during the installation. See Section 1.6.1. o CDA (Compound Document Architecture). See Section 1.6.2. o WPS-PLUS. See Section 1.6.3. o DEC TCP/IP Services. See Section 1.6.4. 1.6.1 Software Which can be Integrated During the Installation You are asked if you want to integrate the following products during the installation: o DATATRIEVE (VAX DATATRIEVE (on VAX systems) or DEC DATATRIEVE (on AXP systems)) If DATATRIEVE is only occasionally used within ALL-IN-1, it is recommended that you do not integrate it during the installation. You will still be able to use DATATRIEVE within ALL-IN-1, but you will avoid any performance impact of having it physically linked with the ALL-IN-1 image. However, if you use a DATATRIEVE image other than SYS$SHARE:DTRSHR.EXE, then you must integrate it during the installation and supply the name of the DATATRIEVE image. o Application Control Management System (ACMS). If you want to integrate these products during the installation, they should be installed and running before you start the ALL-IN-1 Version 3.1 installation. See Chapter 3. You can also integrate them after the installation, see Chapter 5 in the ALL-IN-1 Management Guide. Planning an ALL-IN-1 Version 3.1 Installation 1-25 Planning an ALL-IN-1 Version 3.1 Installation 1.6 Other Software Referenced by the Installation Procedure DEC Notes can also be integrated during the installation. You are not asked any questions about DEC Notes during the installation. If the required version of DEC Notes is already installed and running when you do the installation, DEC Notes is automatically integrated with ALL-IN-1. 1.6.2 Compound Document Architecture (CDA) Support CDA converters are provided with ALL-IN-1 and installed automatically during the ALL-IN-1 Version 3.1 installation. The CDA converters provided with ALL-IN-1 Version 3.1 are described in the CDA Converter Library documentation. The following converters are installed with ALL-IN-1 Version 3.1: o DX (WPS-PLUS Version 3.0) o MACWRITE[R] (MacWrite) o RTF (Microsoft[R] Word[TM] for Microsoft Windows[R]) o WORD5 (Microsoft Word for MS-DOS) o WPL (WPS-PLUS) o DIF[TM] (Data Interchange Format) o WK1 (Lotus 1-2-3[R] Version 2.0 and 2.01) o WK3 (Lotus 1-2-3 Version 3.0) o PICT (Image and graphical format used on the Macintosh[R]) o WORDP (WordPerfect[TM]) You can also install and use the additional CDA converters that are provided with the Version 2.2 CDA Converter Library for OpenVMS (VAX only). Other versions of the CDA Converter Library are not supported. In order to install the CDA converters, you must have Version 1.4-911015 or higher of the file SYS$SHARE:CDA$ACCESS.EXE installed. To check which version is currently installed, enter the following: $ ANALYZE/IMAGE/INTER SYS$SHARE:CDA$ACCESS.EXE 1-26 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.6 Other Software Referenced by the Installation Procedure Press RETURN until the image file identification is displayed. If you do not have V1.4-911015 or higher, you must install the CDA Interoperability kit that is supplied with your language kit. The saveset name is CDAPAT011.A. This kit can be installed with either DECwindows Version 2.0 or DECwindows Motif Version 1.0. To install full CDA support, this software must be running before you install ALL-IN-1 Version 3.1. If you do not have the correct sofware installed, the installation procedure ask you if you want to continue the installation without full CDA support. If you choose to continue without full CDA support, only the WPL (WPS-PLUS) to DDIF (Digital Document Interchange Format) converters are automatically provided. The CDA DOC_STYLE files are provided to CDA$LIBRARY, if that directory exists, or to OA$LIB_SHARE as a temporary location if CDA$LIBRARY does not exist. A script to update the format master record with the CDA format and the name of the converters is run as an automatic postinstallation task, if full CDA prerequisites are present. For more information about the use of converters, see Chapter 14 in the ALL-IN-1 Management Guide. To install CDA support after the installation, see Chapter 5 in the same book. 1.6.3 Installing WPS-PLUS as the Default Editor The WPS-PLUS Version 4.2 software is provided with ALL-IN-1 Version 3.1. If you want to use WPS-PLUS as the default editor, you can install the WPS-PLUS Version 4.2 software during the ALL-IN-1 Version 3.1 installation. Note that you cannot install WPS-PLUS unless you have a license that includes WPS-PLUS. If you want to install WPS-PLUS some time after the ALL-IN-1 Version 3.1 installation, you can do an ALL-IN-1 Version 3.1 update installation. The WPS-PLUS kit contains a library of encapsulated PostScript[TM] graphics and page overlay samples. If you specify that you want to install WPS-PLUS during the ALL-IN-1 Version 3.1 installation, you are asked if you wish to copy these files directly to the ALL-IN-1 library. Planning an ALL-IN-1 Version 3.1 Installation 1-27 Planning an ALL-IN-1 Version 3.1 Installation 1.6 Other Software Referenced by the Installation Procedure Some language kits provide international lexicons which are used by WPS-PLUS. The international lexicons are automatically installed during the ALL-IN-1 Version 3.1 installation. If lexicons are provided, you will be prompted for a device on which they can be installed. See the ALL-IN-1 Installation: Language and Market Supplement. If you are installing ALL-IN-1 for the first time and you have been using WPS-PLUS for VMS Version 4.0 or 4.1, you can copy users' files to ALL-IN-1 Version 3.1. Users can then access their WPS-PLUS for VMS files from ALL-IN-1. See Section 8.16. 1.6.4 Using TCP/IP to Communicate With Client Applications If you want client applications such as TeamLinks to connect to ALL-IN-1 using the TCP/IP network protocol, then you must have one of the following sofware packages installed: o DEC TCP/IP Services for OpenVMS (UCX) Version 2.0 or later o Other TCP/IP software that runs in UCX emulation If this software is installed and the logical name UCX$DEVICE is defined on your system when you install ALL-IN-1 Version 3.1, the installation procedure asks you if you want to use TCP/IP. If TCP/IP port numbers have not already been set up for the default AIDA (ALL-IN-1 Distributed Access) Server and File Cabinet Server, then you must supply them. Each server must have a different port number which can be in the range 1024 to 65535. Table 1-7 shows the default values for the servers. Table_1-7_TCP/IP_Service_Information_______________________ Default Port Server___________Number______Associated_Service_Name_______ AIDA Server 7300 OA$AIDA (continued on next page) 1-28 Planning an ALL-IN-1 Version 3.1 Installation Planning an ALL-IN-1 Version 3.1 Installation 1.6 Other Software Referenced by the Installation Procedure Table_1-7_(Cont.)_TCP/IP_Service_Information_______________ Default Port Server___________Number______Associated_Service_Name_______ File Cabinet 7373 OA$FCS[1] Server [1]The_service_name_for_the_File_Cabinet_Server_is_not_used in the ALL-IN-1 Management interface. ___________________________________________________________ 1.7 Running the IVP (Installation Verification Procedure) The Installation Verification Procedure (IVP) for ALL-IN-1 Version 3.1 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. ________________________ Note ________________________ Digital recommends that you run the IVP to ensure that ALL-IN-1 Version 3.1 is installed correctly. ______________________________________________________ After the IVP has run, your system may still require some postinstallation work before it is ready for use. See Chapter 8 for information about postinstallation tasks. After ALL-IN-1 Version 3.1 is installed, you can run the IVP independently to verify that the software is available on your system. You can also run the IVP after a system failure to ensure that users can access ALL-IN-1 Version 3.1. Instructions on running the IVP after installation are given in the ALL-IN-1 Management Guide. 1.8 Planning an Upgrade Installation If you are upgrading from ALL-IN-1 Version 3.0 you must ensure that any customizations that you have made to your system will continue to work with ALL-IN-1 Version 3.1. Planning an ALL-IN-1 Version 3.1 Installation 1-29 Planning an ALL-IN-1 Version 3.1 Installation 1.8 Planning an Upgrade Installation Digital recommends the use of a separate test system to verify your ALL-IN-1 customizations. This enables you to: o Learn about new features and plan user training o Evaluate new functionality o Migrate your customizations Follow the instructions in Chapter 2 if you are planning to upgrade a customized ALL-IN-1 Version 3.0 system. Chapter 2 explains how to use the Conflict Checking and Resolution Tool (CART) to assess the impact of an upgrade on your customizations and how to migrate your customizations to ALL-IN-1 Version 3.1. 1.9 What to do Next Table 1-8 shows you what to do next. Table_1-8_What_To_Do_Next__________________________________ Type_of_Installation__What_to_do_Next______________________ Full installations Go to Chapter 3 to prepare your and upgrades of non- system for the installation. customized ALL-IN-1 Version 3.0 systems Upgrade Go to Chapter 2 to find out how to installations of prepare your system for an upgrade customized ALL-IN-1 installation. Version 3.0 systems Additional language Go to Chapter 3. installations For minimal shutdown Go to Chapter 4. upgrades___________________________________________________ 1-30 Planning an ALL-IN-1 Version 3.1 Installation 2 _________________________________________________________________ Preparing to Upgrade a Customized System Read this chapter if you are upgrading a customized ALL-IN-1 Version 3.0 system to ALL-IN-1 Version 3.1. This chapter describes how to run the ALL-IN-1 Conflict Checking and Resolution Tool (CART) and how to interpret the reports that it produces. The CART reports help you to do the following: o Assess the implications that an upgrade will have on your system customizations. o Create an upgrade plan for migrating your customizations to ALL-IN-1 Version 3.1 so that you can continue to use them. o Prepare your system customizations ready for the upgrade. The CART is a migration tool that provides information to help you understand how the changes made in ALL-IN-1 Version 3.1 will affect the customizations at your site. When you run the CART, it compares the customized elements on your system with the list of base elements provided in ALL-IN-1 Version 3.1. If the customized element has the same name as a base element the CART reports that there is a conflict. The level of severity of the conflict is determined by the CART status code that is assigned to the base element. ________________________ Note ________________________ Digital recommends that you run the CART and take the appropriate actions on all systems that you will be upgrading to ALL-IN-1 Version 3.1. This will ensure that your Customization Management data files Preparing to Upgrade a Customized System 2-1 Preparing to Upgrade a Customized System accurately reflect the customizations at your site for ALL-IN-1 Version 3.1. If you are running a multilingual system, you must also run the CART for each additional language that is installed on your system. ______________________________________________________ It is recommended that you run the CART well in advance of the upgrade. This will allow you time to rerun the CART if necessary and to spend time reviewing the CART reports and deciding how to migrate your customizations. 2.1 Overview of the CART Table 2-1 gives the definitions of some terms that are used throughout this chapter. See Application Programming: Customization Management for information about Customization Management. Table_2-1_Terminology_used_by_the_CART_____________________ Term_____________Explanation_______________________________ Base element A base element is an element that is part of the ALL-IN-1 application. Customization Management defines the ALL-IN-1 application as the OA application area. (continued on next page) 2-2 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.1 Overview of the CART Table_2-1_(Cont.)_Terminology_used_by_the_CART_____________ Term_____________Explanation_______________________________ CART runid An identification string allocated to a specific CART data file. For example, V31$PRIMARY is the runid for the primary language data file for ALL-IN-1 Version 3.1 and V31$FRENCH is the runid for the French language data file for ALL-IN-1 Version 3.1. If you install other applications, they may also provide CART data files. After installation, you can run the CART from Customization Management. You select the runid for the CART data file that you want to use. See Chapter 21 in the ALL-IN-1 Management Guide for details of running the CART after installing ALL-IN-1 Version _________________3.1.______________________________________ The CART data file provides information about changes to Version 3.1 base elements. Base elements in ALL-IN-1 Version 3.1 may contain mandatory changes. They can be new, minimally changed, substantially changed, deleted, or moved. If you have customized a base element that has been modified in ALL-IN-1 Version 3.1, the CART reports that there is a conflict and assigns a status code to the customized element. The severity of the conflict determines what action you must take with your customizations. For example, if a major (mandatory) change has been made to a base element in ALL-IN-1 Version 3.1, and you have customized that base element, the CART report will give the customized element a mandatory status code. This means that there is a direct conflict between your customized element and the Version 3.1 base element and you must take some action with your customized element before upgrading. Other conflicts reported by the CART are due to customized elements that have the same name as new Version 3.1 base elements. The customized elements may be in the same area as the new element or in a different area. In each case the CART will report a conflict. Preparing to Upgrade a Customized System 2-3 Preparing to Upgrade a Customized System 2.1 Overview of the CART When you use Customization Management to customize a base element, the name of the customized element remains the same. ALL-IN-1 distinguishes between different versions of an element by their locations. Each time you use Customization Management to customize an element, a record is written to the site modification log, OA$DATA:CM$SITELOG.DAT. When you run the CART, it compares the customized elements listed in your site modification log with the list of base elements provided in the ALL-IN-1 Version 3.1 data file and creates a report detailing the differences. The data file is identified by the CART runid as described in Table 2-1. Figure 2-1 shows what the CART does. Figure 2-1 What the CART Does The CART does the following: 1 Gets the list of customized elements from the site modification log. 2 Checks in the live and site areas for the elements listed in the site modification log. If a customized element listed in the site modification log cannot be found, it is listed in the site elements report. If the CART finds elements in the site area which are not listed in the site modification log it adds an entry for these elements in the full CART report. 3 Checks the list of customized elements in the site and live areas against the list of base elements in the CART data file. 2-4 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.1 Overview of the CART If the customized element has the same name as an ALL-IN-1 Version 3.1 base element, the CART assigns the status code associated with the base element, to the customized element. 4 Produces the CART full report and summary reports which lists the status codes assigned to the customized elements. In addition to producing reports, the CART also provides an ALL-IN-1 script which is called the CART resolution procedure. This script can be edited and used after the upgrade, to resolve some of your conflicts automatically. See Section 2.6.6. 2.2 Modified ALL-IN-1 Systems You may have installed and integrated other software products that can be used with ALL-IN-1, for example, TeamRoute. Most applications that are installed and integrated with ALL-IN-1 add new elements in their own application area. The CART data file for ALL-IN-1 Version 3.1 does not contain a record of any new elements that have been added by installing additional software so you do not need to do any additional preparation tasks. If applications do add elements to the OA application area, an entry is made in the site modification log file. As the CART checks all elements in the site modification log file, it will report on these elements even if they are not customized. If any applications have added elements to the OA application base area and you have customized these elements, then the CART will report a conflict if the customized element has the same name as a new ALL-IN-1 Version 3.1 element. If you have previously installed ALL-IN-1 Version 3.0A, the CART full report will indicate which elements were changed in Version 3.0A. Preparing to Upgrade a Customized System 2-5 Preparing to Upgrade a Customized System 2.3 Understanding the CART Reports 2.3 Understanding the CART Reports To interpret the CART reports, you must be familiar with application programming and ALL-IN-1 Customization Management. Ideally, you should also be familiar with the customizations at your site. This section explains the types of CART report that are generated and the format of the reports. The CART status codes are described in more detail in Section 2.7, Section 2.8 and Section 2.9. The following topics are discussed in this section: o Types of CART report. See Section 2.3.1. o Format of the CART reports. See Section 2.3.2. o CART status codes and level of conflict. See Section 2.3.3. Note that the CART produces a separate set of reports for each additional language. 2.3.1 Types of CART Report When you run the CART, it produces four types of report and an ALL-IN-1 script (the CART resolution procedure) in your top-level site directory, for example, [ALLIN1.SITE]. Table 2-2 gives a description of each type of CART report. The CART resolution procedure is described in Section 2.6.6. 2-6 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.3 Understanding the CART Reports Table_2-2_CART_Reports_____________________________________ Type_of_Report________Description__________________________ CART full report CM_CART_FULL_runid.TXT For the primary language, the name of this report is CM_CART_FULL_ V31$PRIMARY.TXT, where V31$PRIMARY is the CART runid. This report gives detailed information about the conflicts between your customized elements and Version 3.1 base elements. It gives information on why the element has changed, and suggests resolutions for the conflicts. There is also a description of each status code at the beginning of each status code section. CART summary report CM_CART_SUMMARY_runid.TXT Lists which of your customized elements conflict with ALL-IN-1 Version 3.1 base elements, ordered by status code. As you become more experienced with using the CART, you may find that the summary report provides you with sufficient information. The summary report may also be useful as a checklist when you rerun the CART after upgrading, see Chapter 8. CART site elements CM_CART_SITE_ELEMENTS.TXT report Lists elements in your site areas that are not registered in your site modification log. (continued on next page) Preparing to Upgrade a Customized System 2-7 Preparing to Upgrade a Customized System 2.3 Understanding the CART Reports Table_2-2_(Cont.)_CART_Reports_____________________________ Type_of_Report________Description__________________________ CART error report CM_CART_ERR_runid.TXT Gives details of any errors that occur during the CART run. If there are no errors, this report is not ______________________produced.____________________________ 2.3.2 Format of the CART Reports In the CART reports, elements are listed in alphabetical order by status code, not by the severity of conflict. At the beginning of each set of status codes, there is an explanation of what the code means and the recommended action you should take to resolve the conflict. Additional information is also provided on the reason for a conflict, and information about the changed element itself. The elements are listed in alphabetical order with the element type and location. For example: ALL-IN-1 IOS Conflict Checking and Resolution Tool Full Report ----------- Page: 1 Run at: 18:52 on 30-Dec-1993 Element Status ------- ------ . ARCHIVE_MARK_DOCUMENT_PENDING SCP SHARE A 1 2 3 4 . FC_RESERVE_LIST_CREATE COM SHARE A . NETWORK$CREATE FRM ENGLISH A . TMEVCARG FRM ENGLISH A . 1 Element name 2 Element type 3 Location 2-8 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.3 Understanding the CART Reports 4 Status code Section 2.7, Section 2.8 and Section 2.9 describe each of the CART status codes in more detail. 2.3.3 CART Status Codes and the Severity of Conflict The CART reports give one or more status codes for each customized element. Each status code has an associated conflict level. The severity of the conflict determines the action that you must take to resolve the conflict both before and after the upgrade. There are three levels of severity of conflict: mandatory, recommended and informational. Table 2-3 shows the impact of each level of conflict severity and the action you must take to resolve the conflict. ________________________ Note ________________________ The severity of the conflict is only a guideline. You may find that conflicts listed as recommended action may be very important for your site. Use your knowledge of your system to determine this. ______________________________________________________ For guidelines for resolving conflicts, see Section 2.6.5. Preparing to Upgrade a Customized System 2-9 Preparing to Upgrade a Customized System 2.3 Understanding the CART Reports Table_2-3_CART_Conflict_Severity,_Status_Codes_and_Actions_ Conflict Status Severity____Codes_______Action_You_Must_Take_______________ Mandatory I K L M N You must resolve all mandatory conflicts before you upgrade to ALL-IN-1 Version 3.1. If the conflict is marked mandatory, the installation of ALL-IN-1 Version 3.1 will probably fail; even if it does succeed, you will not be able to run ALL-IN-1 Version 3.1 unless you resolve the conflict before upgrading. There are no automatic procedures for resolving conflicts for elements with status codes I and L. Recommended D E O P Q You must resolve the conflict soon after the upgrade to ALL-IN-1 Version 3.1. You will be able to run ALL-IN-1 Version 3.1 after the upgrade without resolving the conflict, but you will not have full functionality and users may also see inconsistencies within the system. For example, if you have modified the Electronic Messaging menu form but not the Word and Document Processing menu form, users may see new features in Word and Document Processing but not Electronic Messaging. Informational F G H R Resolve the conflict when convenient, after the upgrade to ________________________ALL-IN-1_Version_3.1.______________ 2-10 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.4 Preparing to Run the CART 2.4 Preparing to Run the CART Depending on the customizations on your system, you must do some or all of the tasks listed in this section to prepare your system before running the CART. Do the following before running the CART: o Check the value of JTQUOTA. See Section 3.8.1. o Print a system modification report. See Section 2.4.1 o Import elements and applications that were customized outside of the site areas. See Section 2.4.2. 2.4.1 Printing a System Modification Report To help you work through the CART reports, you should print out a system modification report. This report lists the changes made to elements in the live area. Run this once for the SHARE area and once for each additional language that is installed on your system. To create a system modification report: o Enter AM to go to the Application Maintenance menu o Use the Print modification report (PMR) option 2.4.2 Importing Elements from Outside Customization Management Before you run the CART, it is recommended that you import any elements or applications that were customized outside of Customization Management site areas, into Customization Management. The CART can only check for conflicts with customizations that have been made using Customization Management. The ALL-IN-1 Management Guide explains how to create an application area and move an application from OpenVMS into Customization Management. The CART checks all application areas. 2.4.3 Customized Help Modules When ALL-IN-1 Version 3.1 is installed, a new version of the base Help library, OAHELP.HLB is provided. If you have created or modified Help modules, you will need to add your customized Help modules to the new base Help library after installation. See the Application Programming: Guide. Preparing to Upgrade a Customized System 2-11 Preparing to Upgrade a Customized System 2.4 Preparing to Run the CART 2.4.4 Customized Message Files The message files ending in .MSG that are provided with ALL-IN-1 are not supported by Customization Management. Examples of these are OAMESS.MSG and OAMGRMESS.MSG. If you have customized any of these message files, you must take some action before upgrading, otherwise you will lose your customizations. Save your customized versions of any .MSG message files outside the ALL-IN-1 directory structure. Reapply your changes after the upgrade installation. 2.5 Running the CART You should have completed the preparatory tasks in Section 2.4 before running the CART from the ALL-IN-1 Version 3.1 installation procedure. Read the following notes before running the CART: o If you are upgrading additional languages to ALL-IN-1 Version 3.1, you you must run the CART for each additional language using the ALL-IN-1 Version 3.1 installation procedure for that language. o You do not need to shut down ALL-IN-1 while you run the CART, so your users can continue to use the system. o It may take several hours to run the CART depending on the following factors: o The number of users on your system o The amount of customizations on your system o The configuration of your system and the amount of processing power In addition to the time that the CART takes to run, you must set aside time to work through the reports and to decide on an upgrade plan for each of your customizations. To run the CART from the ALL-IN-1 Version 3.1 installation procedure: 1. Create a log of the installation: $ SET HOST 0/LOG=filename 2. Follow steps 1 to 4 in Table 5-2. 2-12 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.5 Running the CART 3. Press RETURN when the list of installation options are displayed: Using the FULL ALL-IN-1 V3.1 kit, the following installation types can be performed: (1) Upgrade of ALL-IN-1 V3.0 TO ALL-IN-1 V3.1 (2) Minimal Shutdown Upgrade of ALL-IN-1 V3.0 to ALL-IN-1 V3.1 (RL) Register licenses for prerequisite software * Which installation do you wish to perform [1]: ________________________ Note ________________________ Choosing this option does not install the software. ______________________________________________________ 4. Choose the Run conflict checking and resolution tool (RC) option by entering: RC: The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all preinstallation checks (RC) Run conflict and checking resolution tool (CART) * Which action do you wish to perform [I]: RC 5. Enter the language code (and dialect code if applicable) when prompted. When you have answered all of the questions asked by the installation procedure, the procedure restores the CART kit saveset. For example: %A1LUS-I-RESCARTSS, Restoring ENGLISH CART kit saveset The CART processes each of your customized elements in turn, and displays informational messages. When the CART has finished running, the installation procedure terminates. 6. Log out. 7. Check the installation log to find the location of the CART reports and the CART resolution script. Preparing to Upgrade a Customized System 2-13 Preparing to Upgrade a Customized System 2.6 What to do After Running the CART 2.6 What to do After Running the CART After running the CART, do the following: 1. Check the site elements report, CM_CART_SITE_ELEMENTS.TXT, and take appropriate action. See Section 2.6.1. 2. Check the full report, CM_CART_FULL_runid.TXT for missing elements (elements reported with status codes B or C) and take appropriate action. See Section 2.6.2. 3. Rerun the CART if necessary. See Section 2.6.3. 4. Prepare an upgrade plan. See Section 2.6.4. 2.6.1 Checking the Site Elements Report Check the CART site elements report, CM_CART_SITE_ELEMENTS.TXT, for references to supported Customization Management elements that are registered in your site modification log but which cannot be found by the CART. If the site elements report refers to any of these elements, you can either find them and import them into Customization Management, or remove the entries from the site modification log. See Chapter 20 in the ALL-IN-1 Management Guide. Elements that were not supported by Customization Management in ALL-IN-1 Version 3.0 may also be listed in this report. It is recommended that you put any newly- supported elements into Customization Management. Files with the extension .EXE or .FLC in site directories can be safely ignored. 2.6.2 Checking for Missing Elements (Status Codes B and C) Search the CART full report, CM_CART_FULL_runid.TXT, for all elements with status codes B and C. The CART reports any elements that it cannot find with these status codes. As the CART has not found these elements, it has not been able to check if the customized elements conflict with Version 3.1 elements. It is possible that elements which should be reported with a mandatory conflict are being reported with status B or C instead. Table 2-4 gives a more detailed description of these status codes and the action that you can take. 2-14 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.6 What to do After Running the CART You must take some action, for example, find and move the element to the correct location. You must then rerun the CART so that it can check for conflicts and ensure that all mandatory conflicts are identified and reported. See Section 2.6.3. Do not proceed any further until you can generate a CART report which does not have any elements reported with status code B or C. Table_2-4_CART_Status_Codes_B_and_C________________________ Code___Description___________Action________________________ B The site Check that the entry in the modification log site modification log is contains an entry correct. You can either: for this customized o Delete the entry in the element which site modification log. indicates that it is in the development o Locate the element and area but the element correct the problem, for cannot be found example recover or recreate at the specified the file. location. ___________________________________________________________ C The site Check that the entry in the modification log site modification log is contains an entry correct. You can either: for this customized o Delete the entry in the element which site modification log. indicates that it is in the live area but o Locate the element and the element cannot correct the problem, for be found at the example recover or recreate specified location. the file. ___________________________________________________________ Preparing to Upgrade a Customized System 2-15 Preparing to Upgrade a Customized System 2.6 What to do After Running the CART 2.6.3 Rerunning the CART It is recommended that you rerun the CART in the following cases: o If the CART reported elements with status code B or C and you have taken some action with those elements o If you had to import many elements into Customization Management because of information in the site elements report ________________________ Note ________________________ You should only continue with the tasks in the rest of this chapter when the CART generates a report that does not contain any elements reported with status code B or C. This is to ensure that all elements have been found and correctly processed by the CART. ______________________________________________________ Rerun the CART from the ALL-IN-1 Version 3.1 installation procedure as described in Section 2.5. When you rerun the CART, it overwrites all of the existing CART reports, except for the error report, which is appended to the original. If you want to retain old copies of the CART report files, rename them before running the CART. For example, to rename the full CART report: $ RENAME/LOG dev:[ALLIN1.SITE]CM_CART_FULL_REPORT_V31$PRIMARY.TXT - _$ dev:[ALLIN1.SITE]OLD_CART_FULL_PRIMARY.TXT 2.6.4 Preparing Your Upgrade Plan An upgrade plan details the action you are going to take for each of the customization conflicts that are reported. These are the actions that you will take for each customized element before and after the upgrade installation. In addition to the time needed to perform the upgrade, allow time to make mandatory changes, and time to decide how you are going to migrate your customizations. 2-16 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.6 What to do After Running the CART Use the supplementary information in the full report to help you decide how to migrate your customizations to ALL-IN-1 Version 3.1. Do the following: 1. Review the conflicts reported by the full CART report, CM_CART_FULL_runid.TXT, in the order of severity of conflict: a. Mandatory status codes o Find and review all customized elements with status codes: I, K, L, M and N. See Section 2.7. o Plan the action you will take before upgrading, and decide how you will resolve these conflicts after upgrading, see Section 2.6.5. b. Recommended status codes o Find and review all customized elements with status codes: D, E, O, P and Q. See Section 2.8. o Plan how to resolve these conflicts immediately after upgrading. c. Informational status codes o Find and review the customized elements with status codes: A, F, G, H and R. See Section 2.9. o Plan how you will resolve these conflicts after upgrading. 2. Plan postinstallation tasks, for example how you will use the CART resolution procedure. See Section 2.6.6 and Section 2.6.7. If an element is reported with two status codes, review its conflicts in severity order in the same way. For example, if an element is reported with status codes E and H, review the recommended conflict first, then the informational conflict. For guidelines on resolving conflicts, see Section 2.6.5. The actions that you need to take will depend on the customizations at your site. Preparing to Upgrade a Customized System 2-17 Preparing to Upgrade a Customized System 2.6 What to do After Running the CART 2.6.5 Guidelines for Resolving Conflicts To ensure that you have access to all the functionality of ALL-IN-1 Version 3.1, you will have to resolve each conflict in one of the following ways: o Delete your customized element, so that you use the Version 3.1 base element instead. Do this if you no longer require your customization, for example, if your customization fixed a problem or provided functionality that is now supplied as part of ALL-IN-1 Version 3.1. o Apply your customizations to the Version 3.1 element. Do this if you want to retain your customizations. o Customize your version of the base element to include the Version 3.1 changes. Do this if you want to retain your customizations, and there are fewer changes in the Version 3.1 element than in your customized element. You can only do this after the upgrade. 2.6.6 CART Resolution Procedure After the upgrade to ALL-IN-1 Version 3.1, the CART provides an ALL-IN-1 script in your top level site directory, for example, [ALLIN1.SITE]. This script is known as the CART resolution procedure, CM_CART_SCRIPT_runid.SCP. The script enables you to automatically resolve some of the conflicts reported by the CART. For these conflicts, the procedure performs the minimum steps necessary to ensure that your system works correctly and that you have access to all the ALL-IN-1 Version 3.1 features. ________________________ Note ________________________ You must customize the CART resolution procedure to do what is required for your site. The CART resolution procedure calls individual scripts to process elements for each of the CART status codes. To see what processing the CART resolution procedure does for each status code, refer to the relevant script (called OA$LIB:CM_CART_SCRIPT_n, where n is the status code). 2-18 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.6 What to do After Running the CART You can edit the script to customize it before you upgrade but you cannot run the script until you have completed the upgrade installation to ALL-IN-1 Version 3.1. See Chapter 8. ______________________________________________________ The CART resolution procedure marks obsolete files that are no longer required by ALL-IN-1 Version 3.1 for deletion. It deletes element records from the base elements file. You can delete these files automatically after upgrading by running a command procedure. See Section 8.10.2. It is not mandatory to use the CART resolution procedure to resolve conflicts. For example, if it does not do enough to resolve your particular conflicts, you may decide to resolve your conflicts directly, using Customization Management. 2.6.7 Planning Postinstallation Tasks You must allow some time in your upgrade plan for reviewing your customizations after the upgrade installation. The details of the tasks that you need to do are listed in Chapter 8. You will need to consider: o Reviewing and testing customizations to elements which require mandatory changes o Reviewing and testing customizations to elements which have recommended changes o Running the CART resolution procedure o Rerunning the CART from Customization Management after upgrading to check that all conflicts have been resolved After the upgrade, use the Check Conflicts (CC) option to rerun the CART. See Chapter 21 in the ALL-IN-1 Management Guide. Preparing to Upgrade a Customized System 2-19 Preparing to Upgrade a Customized System 2.7 Mandatory Status Codes (I, K, L, M and N) 2.7 Mandatory Status Codes (I, K, L, M and N) ________________________ Note ________________________ For all the status codes listed in this section, there is a direct conflict between your customized element and a Version 3.1 base element. You must resolve the conflict manually before you install ALL-IN-1 Version 3.1. ______________________________________________________ The following status codes require mandatory action: I K L M N Table 2-5 gives a detailed explanation of the status codes which require mandatory action and the action that you must take to resolve the conflict before upgrading. To review the customized elements with the mandatory status codes: 1. Search the full CART report, CM_CART_FULL_runid.TXT, for all elements with the status codes for mandatory actions. 2. Use the supplementary information provided in the full CART report to review the changes to the Version 3.1 base element. 3. Take any recommended actions as described in Table 2-5. 4. Use Customization Management to move these elements from the live area to the development area before you upgrade. Consider deleting these elements if appropriate. See Section 2.6.5. ________________________ Note ________________________ When mandatory elements are moved to the development area, they will still be included in any subsequent CART reports with a mandatory status code. It is however safe to proceed with the upgrade installation once all mandatory elements are in the development 2-20 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.7 Mandatory Status Codes (I, K, L, M and N) area and you have completed any other recommended actions. ______________________________________________________ 5. Decide how you want to resolve the conflict after the upgrade. Use the guidelines in Section 2.6.5 and the supplementary information provided in the full CART report. Add these actions to your upgrade plan. Table_2-5_Mandatory_Status_Codes_(I,_K,_L,_M_and_N)______________ Code___Explanation________________Action_________________________ I A new base element has Before you upgrade, do the been added to ALL-IN-1 following: Version 3.1 with the same 1. Check if the element is the name as this customized same as the base element. element. The base element It may have been added by is in a different area, additional software, for for example, SHARE example, a patch kit. instead of ENGLISH, but it may cause a conflict. 2. Use Customization Management to create a new element with a different name, using the existing element as a template. 3. Delete the original customized element. 4. Update any references to this customized element. _________________________________________________________________ (continued on next page) Preparing to Upgrade a Customized System 2-21 Preparing to Upgrade a Customized System 2.7 Mandatory Status Codes (I, K, L, M and N) Table_2-5_(Cont.)_Mandatory_Status_Codes_(I,_K,_L,_M_and_N)______ Code___Explanation________________Action_________________________ K A new base element has Take the same action as for been added to ALL-IN-1 status code I. Version 3.1 with the same name and in the same area as this customized element. Your customized element is in direct conflict with the new base element. _________________________________________________________________ L A base element that Do the following: contains mandatory 1. If the customized element changes has the same is live, use Customization name as this customized Management to move it from element but it is in the live area before you a different area (for upgrade to ALL-IN-1 Version example SHARE instead of 3.1. ENGLISH). 2. Review the changes to the base element as listed in the full report and see if they apply to your customized version. 3. Decide on how you want to resolve the customization conflict after installation using the guidelines in Section 2.6.5 and add the actions to your upgrade plan. The full CART report lists details of the base element. (continued on next page) 2-22 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.7 Mandatory Status Codes (I, K, L, M and N) Table_2-5_(Cont.)_Mandatory_Status_Codes_(I,_K,_L,_M_and_N)______ Code___Explanation________________Action_________________________ _________________________________________________________________ M A base element which Take the same action as for contains mandatory status code L changes has the same name and is in the same area as this customized element. You probably used an earlier version of the base element to create your customized element, so the customized element will not work properly with ALL-IN-1 Version 3.1. For example, if you have customized the forms PROFILn they will be reported with status code M. _________________________________________________________________ N A base element containing If the customized element mandatory changes has is live, use Customization changed areas in ALL-IN-1 Management to remove it from Version 3.1. The moved the live area before upgrading base element has the same to ALL-IN-1 Version 3.1. name as this customized The full CART report lists element but it is in a details of the base element. different area. In this version of ALL-IN-1, it is unlikely that you will encounter elements with this __________________________________status_code.___________________ Preparing to Upgrade a Customized System 2-23 Preparing to Upgrade a Customized System 2.8 Recommended Status Codes (D, E, O, P and Q) 2.8 Recommended Status Codes (D, E, O, P and Q) ________________________ Note ________________________ For all elements in this conflict category, you must resolve the conflict immediately after upgrading to ALL-IN-1 Version 3.1 and before allowing users access to ALL-IN-1 Version 3.1. ______________________________________________________ Using the full CART report, CM_CART_FULL_runid.TXT, find and review the elements with status codes which have recommended actions. The following status codes are in this category: D E O P Q Table 2-6 lists the recommended status codes and gives you the action you need to take to resolve the conflicts. You should consider using Customization Management to move these elements from the live area to the development area before you upgrade. This will avoid errors, for example, with customized elements with status code E, when forms are compiled. If you have a number of elements reported with status codes P and Q, you may want to use the CART resolution procedure, CM_CART_SCRIPT_runid.SCP to move them from the live area to the development area. In this case, you can leave them in the live area until you have upgraded to ALL-IN-1 Version 3.1. The CART resolution procedure can only be run after Version 3.1 is installed but you can edit the procedure before installation to customize it. See Section 2.6.6. Add the actions that you want to take after installation to your upgrade plan. 2-24 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.8 Recommended Status Codes (D, E, O, P and Q) Table_2-6_Recommended_Status_Codes_(D,_E,_O,_P_and_Q)____________ Code___Explanation________________Action_________________________ D Your customized element Inspect the contents of this calls a base element that element and use Customization no longer exists in the Management to make any base kit. necessary changes. You could The customized element do one of the following: may no longer be needed o Remove the element if it is or it may require no longer required. modification in order to work properly on an o Edit the element to remove upgraded system. the reference to the missing The full CART report element. provides the name of the o Make the called element into removed element that is a customization so that you called. can still use it. _________________________________________________________________ E This customized element Inspect the contents of this references a message element and use Customization symbol that has been Management to make any removed from the base necessary changes. You could kit. do one of the following: The full CART report o Edit the element to use the provides information new message symbol if one is about the removed message provided. symbol and, if a new message symbol has o Replace the message symbol replaced the old one, with text. the new symbol is given, o Customize the message symbol to help you evaluate the by adding it to one of the action required. site message files. _________________________________________________________________ (continued on next page) Preparing to Upgrade a Customized System 2-25 Preparing to Upgrade a Customized System 2.8 Recommended Status Codes (D, E, O, P and Q) Table_2-6_(Cont.)_Recommended_Status_Codes_(D,_E,_O,_P_and_Q)____ Code___Explanation________________Action_________________________ O A base element has After the upgrade, do the the same name as this following: customized element but 1. Print the differences it is in a different between the customized area. For example, SHARE element and the base instead of ENGLISH. element, using the Print (P) Customized elements option on the Customization in this category are Management menu. probably related to a layered application that 2. Evaluate the differences. uses its own areas. See Section 2.6.5. The full CART report lists details of the base element. _________________________________________________________________ P This customized element After the upgrade, do the is based on a base following: element that has been 1. If the element is live, changed in Version 3.1. remove it from the live The majority of area using Customization customizations will be Management. reported with this status code. 2. Print the differences The report provides between the customized details of the base element and the base element. element using the Print (P) option on the Customization Management menu. 3. Evaluate the differences See Section 2.6.5. CART resolution procedure: Removes the customized element from the live area. (continued on next page) 2-26 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.8 Recommended Status Codes (D, E, O, P and Q) Table_2-6_(Cont.)_Recommended_Status_Codes_(D,_E,_O,_P_and_Q)____ Code___Explanation________________Action_________________________ _________________________________________________________________ Q This customized element After the upgrade do the has the same name as a following: base element but it is o If the element is live, in a different area. The remove it from the live base element has been area using Customization changed and was moved Management. to its present area for ALL-IN-1 Version 3.1. o Print the differences For example, a base between the base element and element could have moved the customized element using from a language-dependent the Print (P) option on the to a language-independent Customization Management area. menu. o Evaluate the differences o Use Customization Management to make any necessary changes. CART resolution procedure: removes the customized element from the live area and adds a new entry to the site modification log linking this __________________________________customized_element_to_it.______ 2.9 Informational Status Codes (A, F, G, H and R) Identify and review elements in the informational category of conflicts that are listed in the full CART report. Decide how you want to resolve these conflicts and add the actions to your upgrade plan. Conflicts reported with these status codes can be resolved at a convenient time after the upgrade. Elements with the following status codes are in the informational category: A F G H R Preparing to Upgrade a Customized System 2-27 Preparing to Upgrade a Customized System 2.9 Informational Status Codes (A, F, G, H and R) Table 2-7 lists the informational conflicts and describes the action that you must take to resolve the conflict. Review the changes to these elements. Add the actions that you want to take to your upgrade plan. Table_2-7_Informational_Status_Codes_(A,_F,_G,_H_and_R)__________ Code___Explanation________________Action_________________________ A This element has been Your ALL-IN-1 Version 3.1 removed from the base system will work correctly if kit, but it is listed in you take no action, but Digital the base elements file. recommends that you remove There is no corresponding entries for these elements customized element. from the base elements file The CART reports all using the CART resolution uncustomized elements procedure after the upgrade. that have been removed This ensures that your base from the ALL-IN-1 Version elements file is consistent 3.1 base kit with a with ALL-IN-1 Version 3.1 status of A. for future reference to base elements. You must also run the delete obsolete files procedure after you have run the CART resolution procedure. See Chapter 8. You may wish to check any customized applications outside Customization Management to remove any existing references to any of these elements. CART resolution procedure: Removes the element from the base elements file. _________________________________________________________________ (continued on next page) 2-28 Preparing to Upgrade a Customized System Preparing to Upgrade a Customized System 2.9 Informational Status Codes (A, F, G, H and R) Table_2-7_(Cont.)_Informational_Status_Codes_(A,_F,_G,_H_and_R)__ Code___Explanation________________Action_________________________ F This element was You do not need to take any processed by a previous action. CART run.[1] _________________________________________________________________ G A base element with As the base element associated the same name as this with this customized element customized element, but is no longer a part of the in a different area, has standard ALL-IN-1 Version 3.1 been removed from the base kit, the existence of base kit in Version 3.1. this customized element will The CART report provides probably not conflict with the the name of the removed proper operation of an upgraded base element. system. The customized element is probably no longer needed and you may want to delete it. Inspect the contents of this element and use Customization Management to make any necessary changes. _________________________________________________________________ [1]If_you_want_to_rerun_CART_after_installation_and_ignore_any___ previous runs, use the Clear previous run details (CP) option on the Conflict Checking menu (MA CC CP). (continued on next page) Preparing to Upgrade a Customized System 2-29 Preparing to Upgrade a Customized System 2.9 Informational Status Codes (A, F, G, H and R) Table_2-7_(Cont.)_Informational_Status_Codes_(A,_F,_G,_H_and_R)__ Code___Explanation________________Action_________________________ H A base element with the Do the following: same name and in the same 1. If the customized element area as this customized is live, use Customization element has been removed Management to remove it from from the base kit. the live area. 2. Remove the entry for this element from the base elements file using the CART resolution procedure after the upgrade. 3. Mark the element as a site element rather than a customized version of a base element. CART resolution procedure: Removes the element from the live area, removes the entry from the base elements file and marks the element as a site element. _________________________________________________________________ R A record for this element No action is required. exists in the site This element should not cause a modification log but conflict on an ALL-IN-1 Version the element type is not 3.1 system. currently supported. You do however need to take some action to support this element type in ALL-IN-1 Version 3.1. Contact your local Digital office for more information about adding __________________________________support_for_element_types._____ 2-30 Preparing to Upgrade a Customized System 3 _________________________________________________________________ Preparing Your System for Installation This chapter describes the tasks that you must do to prepare your system for an ALL-IN-1 Version 3.1 installation. It assumes that you have read Chapter 1 and Chapter 2. The information in this chapter applies to all installations and it is assumed that you have made all your planning decisions and know what type of installation you are going to perform. 3.1 Preinstallation Checklist To prepare your system for an ALL-IN-1 Version 3.1 installation, you must do the tasks listed in Table 3-1. Table_3-1_Preinstallation_Checklist________________________ For further information, Task___Description________________see______________________ 1 Check the kit contents The Bill of Materials for a list of what the distribution kit should contain. Contact your Digital representative if your kit is damaged or incomplete. See Appendix A for details of the distribution media. ___________________________________________________________ (continued on next page) Preparing Your System for Installation 3-1 Preparing Your System for Installation 3.1 Preinstallation Checklist Table_3-1_(Cont.)_Preinstallation_Checklist________________ For further information, Task___Description________________see______________________ 2 Read the READ ME FIRST letter if one is supplied with your kit ___________________________________________________________ 3 Read the online product Section 3.2 for release notes provided instructions on accessing with the kit the release notes. ___________________________________________________________ 4 Check that you have the Section 3.3 correct versions of: o The prerequisite software for the installation o Any optional software that you want to install ___________________________________________________________ 5 Check that you have a Section 3.5 valid license for the installing account ___________________________________________________________ 6 Register the ALL-IN-1 Section 3.6 Version 3.1 License Product Authorization Key (PAK) ___________________________________________________________ (continued on next page) 3-2 Preparing Your System for Installation Preparing Your System for Installation 3.1 Preinstallation Checklist Table_3-1_(Cont.)_Preinstallation_Checklist________________ For further information, Task___Description________________see______________________ 7 Register the License Section 3.6.2 PAKs for the prerequisite and optional software provided with ALL-IN-1 Version 3.1 ___________________________________________________________ 8 Check the installation Section 3.8 for the procedure requirements: values required and o For the installing instructions for checking account and changing these parameters. o System parameters o Disk space o Logical names o Installed images o The location of DCLTABLES.EXE ___________________________________________________________ 9 For upgrade Section 3.9. installations, do any additional tasks. ___________________________________________________________ 10 Install prerequisite and Section 3.7. optional software ___________________________________________________________ (continued on next page) Preparing Your System for Installation 3-3 Preparing Your System for Installation 3.1 Preinstallation Checklist Table_3-1_(Cont.)_Preinstallation_Checklist________________ For further information, Task___Description________________see______________________ 11 If you will be using a Section 3.10. remote Message Router that is not in the same VMScluster, do any additional tasks. ___________________________________________________________ 12 Use the Perform all Section 3.11 preinstallation checks (PC) option to check that your system is prepared for the installation. (This is optional.) ___________________________________________________________ 13 Do the final system Section 3.12 preparation tasks: 1. Check that your housekeeping and system maintenance tasks are up to date and remove any invalid or obsolete accounts. 2. Start the queue manager. 3. For upgrade and update installations: a. Shut down ALL-IN-1. b. Run the Mail Sender and Fetcher. ___________________________________________________________ (continued on next page) 3-4 Preparing Your System for Installation Preparing Your System for Installation 3.1 Preinstallation Checklist Table_3-1_(Cont.)_Preinstallation_Checklist________________ For further information, Task___Description________________see______________________ 14 Back up your system and Section 3.12 _______target_disks._______________________________________ 3.2 Reading and Printing the Online Release Notes Online release notes are provided with the language and market components of ALL-IN-1 Version 3.1. The release notes contain information that was unavailable before the books went to print. It is recommended that you read the release notes, because they may contain information relating to the installation. You can access the release notes using the VMSINSTAL procedure before you install the ALL-IN-1 Version 3.1 software. There are two parts to the ALL-IN-1 Version 3.1 release notes: o Release Notes Part 1 Language This part contains the release notes specific to the ALL-IN-1 Version 3.1 language being installed. o Release Notes Part 2 Market This part contains the release notes specific to your ALL-IN-1 Version 3.1 market component. Note that this document may not exist for all market components. To read or print the release notes, do the following: 1. Log in to the privileged OpenVMS system manager's account and enter the following command lines: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL product device: OPTIONS N where device is the device on which the media containing the appropriate version of the release notes is mounted and product is the product code. The product codes are: o A1Llang031 for the Release Notes Part 1 Language, where lang is the 2-letter code for the language you are installing Preparing Your System for Installation 3-5 Preparing Your System for Installation 3.2 Reading and Printing the Online Release Notes o A1Cmarket031 for the Release Notes Part 2 Market, where market is the 2-letter code for the market component you are installing If you are performing an additional language installation, you need only print the ALL-IN-1 Release Notes Part 1 Language that is supplied with your kit. When you have read or printed the release notes, terminate the installation procedure. If you have accessed only one part of the release notes, repeat the procedure to access the other part. The following files are placed in SYS$HELP: o A1Llang031.RELEASE_NOTES, for the Release Notes Part 1 Language, where lang is the 2-letter code for the language you are installing o A1Cmarket031.RELEASE_NOTES, for the Release Notes Part 2 Market, where market is the 2-letter code for the market component you are installing 3.3 Checking Prerequisite and Optional Software Table 3-2 provides information about the prerequisite software for an ALL-IN-1 Version 3.1 installation. It also lists the software that is supplied with the ALL-IN-1 Version 3.1 kit, and optional software that you may want to install. The following definitions apply: o Prerequisite means that the software must be installed before you install ALL-IN-1 Version 3.1. The installation will fail if the prerequisite software is not installed. o Optional means that the software is not required for the ALL-IN-1 Version 3.1 installation. Optional software provides additional functionality and the optional software that you install depends on the requirements at your site. For example, if you want to use Group Conferencing, you must install DEC Notes. 3-6 Preparing Your System for Installation Preparing Your System for Installation 3.3 Checking Prerequisite and Optional Software ________________________ Note ________________________ Both the prerequisite software, and any optional software that you want to install, must be installed and running before you install ALL-IN-1 Version 3.1. ______________________________________________________ Table_3-2_Prerequisite_and_Optional_Software_______________ Supplied Software VAX AXP With Product__________Version__VersionKit?___Notes______________ OpenVMS VAX 5.5-2 - N Prerequisite for or installation on higher VAX. Must be a full untailored system OpenVMS AXP - 6.1 N Prerequisite for installation on AXP. Must be a full untailored system DECnet Phase IV 5.5 1.5 N Prerequisite or DECnet OSI for 5.6B[1] 5.6B N Prerequisite OpenVMS VAX Forms 2.4 - Y Prerequisite Management System (FMS)[2] [1]Required_for_the_VAX_Message_Router_X.400_Gateway,______ Version 2.3 [2]See the VAX FMS or DEC FMS Installation Guide and Release Notes. Note that you must have at least one compiler installed on your system in order to run the sample programs supplied with VAX FMS. (continued on next page) Preparing Your System for Installation 3-7 Preparing Your System for Installation 3.3 Checking Prerequisite and Optional Software Table_3-2_(Cont.)_Prerequisite_and_Optional_Software_______ Supplied Software VAX AXP With Product__________Version__VersionKit?___Notes______________ DEC Forms - 2.4 Y Prerequisite Management System (FMS)[2] DEC TCP/IP 2.0 3.0 N Optional. Services for Install if you want OpenVMS (UCX) to use the TCP/IP or other TCP/IP network protocol software that to communicate emulates UCX with client applications. Message Router 3.3A - Y Optional. Install and configure if you want to send remote mail. Message Router 3.3 - Y Optional VMSmail Gateway Install if you want to send mail to VMSmail users. DEC Notes 2.5 2.5 Y Optional. Install if you want to use Group Conferencing. [2]See_the_VAX_FMS_or_DEC_FMS_Installation_Guide_and_______ Release Notes. Note that you must have at least one compiler installed on your system in order to run the sample programs supplied with VAX FMS. ___________________________________________________________ 3-8 Preparing Your System for Installation Preparing Your System for Installation 3.3 Checking Prerequisite and Optional Software For information about the order of installing optional software, see Section 3.7. 3.4 Linking Software Products During the Installation Some products that you can use from ALL-IN-1 must be linked with the ALL-IN-1 image. The installation procedure allows you to link these products during the ALL-IN-1 Version 3.1 installation. The following products can be integrated with ALL-IN-1 during the installation: o DEC DATATRIEVE o VAX Application Control and Management System (ACMS) For the versions that are supported with ALL-IN-1 Version 3.1, see the Software Product Description (SPD) supplied with the ALL-IN-1 Version 3.1 kit. ________________________ Note ________________________ Any products that you want to link to ALL-IN-1 during the installation must be installed and running before you install ALL-IN-1 Version 3.1. You can also install and link these products to ALL-IN-1 after the installation. See the ALL-IN-1 Management Guide. ______________________________________________________ Language and specialized lexicons may also be available for the language that you are installing. See the ALL-IN-1 Installation: Language and Market Supplement. These are installed automatically during the language and market part of the installation. For a complete list of software that can be used from ALL-IN-1 Version 3.1, see the Software Product Description (SPD). If you have installed and integrated other products with ALL-IN-1, for example WordPerfect[R] or Lotus 1-2-3[R], please contact the suppliers of these products to check which versions can be used with ALL-IN-1 Version 3.1. Preparing Your System for Installation 3-9 Preparing Your System for Installation 3.5 Checking the Licence for the Installing Account 3.5 Checking the Licence for the Installing Account The installing account, from which you plan to do the installation, must have a valid ALL-IN-1 license. This means that you must have one of the following: o A Capacity licence o A Concurrent license with available units o A personal license with the name of the installation account in the reserve list of users. For example, if you are planning to do the installation from the SYSTEM account, SYSTEM must be listed in the reserve list. The installing account should be licensed with the maximum available license to ensure that all the required functionality can be installed. 3.6 Registering License Product Authorization Keys (PAKs) You must register the ALL-IN-1 License Product Authorization Key (PAK) before you start to install the ALL-IN-1 Version 3.1 software. The installation procedure checks for a registered ALL-IN-1 Version 3.1 license when you confirm that you are ready to install the software by choosing the Perform the installation (I) option from the menu of installation options. If a license is not found, the installation terminates. To register a license PAK for a full installation, see Section 3.6.1. When you have registered the ALL-IN-1 License PAK, you can use the Register licenses for prerequisite software (RL) option to automatically register License PAKs for additional software that is provided with the ALL-IN-1 Version 3.1 kit. See Section 3.6.2. ________________________ Note ________________________ You must make sure that all the License PAKs are registered on all nodes on which you intend to use the software. ______________________________________________________ 3-10 Preparing Your System for Installation Preparing Your System for Installation 3.6 Registering License Product Authorization Keys (PAKs) 3.6.1 Registering Before a Full Installation If you are installing ALL-IN-1 Version 3.1 on a newly licensed node or cluster, you must register a License PAK for ALL-IN-1 Version 3.1 before you install ALL-IN-1 Version 3.1. The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. License PAKs are registered using the License Management Facility (LMF). To register the ALL-IN-1 Version 3.1 License PAK, do the following: 1. Log in to the system manager's account, SYSTEM. 2. Register the License PAK in one of the following ways: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with information from your License PAK. o Issue the DCL command, LICENSE REGISTER, together with the appropriate qualifiers that correspond to information on the License PAK. For complete information on using the LMF, see the OpenVMS License Management Utility Manual. 3.6.2 Registering License PAKs for Software Provided with ALL-IN-1 Version 3.1 When you have registered the ALL-IN-1 Version 3.1 License PAK, you must register the License PAKS for the products supplied with the ALL-IN-1 Version 3.1 kit. The following License PAKs can be registered automatically using the ALL-IN-1 Version 3.1 installation procedure: o VAX FMS or DEC FMS o Message Router o Message Router VMSmail Gateway o DEC Notes Your ALL-IN-1 license must include Group Conferencing to install DEC Notes. Preparing Your System for Installation 3-11 Preparing Your System for Installation 3.6 Registering License Product Authorization Keys (PAKs) The License PAKs supplied for these products are for any processor and any number of users. If you already have a license for one of these products, it will be replaced by the license supplied with the ALL-IN-1 Version 3.1 kit. The ALL-IN-1 Version 3.1 License PAK must be registered first. To register the License PAKs automatically, follow Steps 1 to 5 in Table 5-2. Enter RL when the installation prompts you with the following question, * Which installation do you wish to perform [1]: ________________________ Note ________________________ Choosing the RL option does not start the installation. ______________________________________________________ The installation procedure checks your existing licenses, and if necessary registers and loads the appropriate licenses for the software products provided with the ALL-IN-1 Version 3.1 kit. The installation then terminates. 3.7 Example Order for Installing Optional Software After you have installed the prerequisite software, install and configure the optional software products. See the appropriate product documentation for installation and configuration instructions. The following installation order is suggested for installing optional software before the ALL-IN-1 Version 3.1 installation: 1. Install ACMS 2. Install VAX DATATRIEVE or DEC DATATRIEVE 3. Install and configure Message Router Version 3.3A Do a customized configuration of Message Router if you want to enable remote Directory Service access and configure Message Router exception reporting for the Directory Service and Transfer Service according to your planning decisions. See Chapters 2 and 3 in the ALL-IN-1 Mail Management Guide. 3-12 Preparing Your System for Installation Preparing Your System for Installation 3.7 Example Order for Installing Optional Software 4. Install and configure the Message Router VMSmail Gateway. See the Message Router VMSmail Gateway Management Guide. 5. Install the CDA interoperability kit if required. See Section 1.6.2. 6. Install DEC Notes 3.8 Installation Procedure Requirements This section describes the requirements for installing ALL-IN-1 Version 3.1. It explains how to check the values and how to change them if necessary. 3.8.1 Installing Account Requirements Use the SYSTEM account to install ALL-IN-1 Version 3.1. The installing account must have a valid rights identifier which is the same as the UIC for the account name. If you are using the SYSTEM account, the rights identifier must be the same as the UIC. To check the UIC and identifier values, do the following: $ RUN SYS$SYSTEM:AUTHORIZE UAF> SHOW/IDENTIFIER SYSTEM The value that is displayed is the UIC of the system account. To add the rights identifier, if it is not set up, do the following: UAF> ADD/IDENTIFIER SYSTEM/VALUE:UIC=[1,4] UAF> EXIT The installing account must also have sufficient quotas to enable you to perform the installation. Table 3-3 summarizes the requirements. Note that these values are sufficient for installation, but they may not be appropriate for running ALL-IN-1. When you create new user accounts for ALL-IN-1 Version 3.1 the process quotas are set to the appropriate values. See the ALL-IN-1 Management Guide. Preparing Your System for Installation 3-13 Preparing Your System for Installation 3.8 Installation Procedure Requirements Table_3-3_Process_Account_Quotas_for_the_Installing_Account Account Quota_________VAX_________AXP_________Notes________________ ASTLM 100 100 BIOLM 50 50 BYTLM 64 000 64 000 DIOLM 150 150 ENQLM 300 300 FILLM 200 200 JTQUOTA 1800 1800 JTQUOTA can be returned to its normal system running value after the installation has completed. PGFLQUOTA 25 000 65 000 pagelets PRCLM 10 10 TQELM 50 50 WSDEFAULT 600 2000 pagelets WSEXTENT 4500 9000 Value must be greater pagelets than for WSDEFAULT WSQUOTA 1500 3000 Must be greater than __________________________pagelets____for_WSDEFAULT________ 3.8.2 System Parameters Table 3-4 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you may need higher values for some settings. If necessary, modify the parameters to at least these values. 3-14 Preparing Your System for Installation Preparing Your System for Installation 3.8 Installation Procedure Requirements ________________________ Note ________________________ You must check the OpenVMS system parameters on each node in the cluster on which you install ALL-IN-1 Version 3.1. ______________________________________________________ The values for the system parameters and quotas given in this section are those specific to ALL-IN-1 Version 3.1 and are acceptable for most systems. The ALL-IN-1 Management Guide describes how to set system parameters for ALL-IN-1. Dynamic system parameters are labelled with a (D) after them. You do not need to reboot your system after changing dynamic system parameters. If you need to set new values for other system parameters, you must reboot your system in order for the changes to take effect. Table_3-4_Minimum_System_Parameter_Values_Required_________ System Parameter_____VAX_________________AXP______________________ CTLPAGES[1] 100 100 pagelets GBLPAGES Full: 20 000 Full: 35 000 pagelets Upgrade: 5000 GBLPAGFIL 5000 600 (CPU-specific pages) GBLSECTIONS Full: 250 Full installation: 250 Upgrade installation: 50 LOCKIDTBL 10 times the 10 times the number of number of active active users users [1]CTLPAGES_can_be_returned_to_the_normal_system_running___ value after the installation has completed (continued on next page) Preparing Your System for Installation 3-15 Preparing Your System for Installation 3.8 Installation Procedure Requirements Table_3-4_(Cont.)_Minimum_System_Parameter_Values_Required_ System Parameter_____VAX_________________AXP______________________ MAXBUF[2] 5000 8192 (D) PQL_DENQLM 150 150 (D) PQL_MENQLM 150 150 (D) PROCSECTCNT[3]50 50 RESHASHTBL Half the value of LOCKIDTBL STARTUP_ null null P1[4] TTY_TYPAHDSZ 1500 1500 VIRTUALPAGECNT50 000 100 000 pagelets SCSNODE Must be the same Must be the same as the as the DECnet node DECnet node name name SCSSYSTEMID DECnet area number DECnet area number multiplied by multiplied by 1024, plus 1024, plus the the DECnet node number DECnet node number [2]You_do_not_need_to_modify_MAXBUF_while_preparing_for____ the installation. If this parameter is too low during installation, you will receive an informational message and the installation will continue. However, you must set MAXBUF to at least the value shown here before ALL-IN-1 Version 3.1 is used. [3]If you integrate other software with ALL-IN-1 Version 3.1, you must increase the value of PROCSECTCNT by at least five. This ensures that shared images are accessible during installation. [4]You must ensure that the value for STARTUP_P1 is null before installing ALL-IN-1 Version 3.1. ___________________________________________________________ 3-16 Preparing Your System for Installation Preparing Your System for Installation 3.8 Installation Procedure Requirements ________________________ Note ________________________ For the majority of installations, the values for CTLPAGES are sufficient. If you are planning to reboot your system to change other system parameters, you can increase the value to 200 for the duration of the installation. ______________________________________________________ 3.8.3 Displaying Current System Parameters Run the SYSGEN utility to display the current parameter settings: 1. To display all the current system parameter settings, enter: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW /ALL 2. To show each system parameter setting separately enter: SYSGEN> SHOW parameter where parameter is the parameter you want to examine. 3. Press Ctrl/Z to leave SYSGEN. To check the number of free global pages and sections, enter the following commands: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") If the value of free global pages or global sections is less than the value in Table 3-4 you must increase the system parameter setting. If the values displayed by the system are greater than the required values, you do not need to change the values for these parameters. 3.8.4 Changing System Parameter Values Edit the file SYS$SYSTEM:MODPARAMS.DAT to change the system parameter values. The entry that you make in this file depends on which of the parameters you are modifying. See Table 3-5. Preparing Your System for Installation 3-17 Preparing Your System for Installation 3.8 Installation Procedure Requirements If you need to change and update non-dynamic system parameters, you must schedule time to reboot your system in order for the changes to take effect. The (D) after the system parameter value shows that they are dynamic parameters. Table_3-5_Changing_System_Parameter_Values_________________ To change the following parameters_______Do_the_following__________________________ PQL_DENQLM (D) Edit SYS$SYSTEM:MODPARAMS.DAT and specify PQL_MENQLM (D) new parameter values. Use assignment RMS_DFMBC (D) statements of the form: RMS_DFMBFIDX parameter = parameter-value (D) where parameter is the name of the TTY_TYPAHDSZ parameter you want to change and STARTUP_P1 parameter-value is the setting you want SCSNODE to change it to. See Table 3-4 for the SCSSYSTEMID required value. CTLPAGES Edit the file SYS$SYSTEM:MODPARAMS.DAT to GBLPAGES specify new values. Include a line of the GBLPAGFIL following format for each parameter to be GBLSECTIONS changed: LOCKIDTBL ADD_parameter = increase-value MAXBUF where parameter is the name of the PIOPAGES parameter you want to change, and PROCSECTCNT increase-value is the amount by which RESHASHTBL you want to increase the setting of this parameter. VIRTUALPAGECNT For example, to increase the value of LOCKIDTBL by 60, enter: ADD_LOCKIDTBL=60 _________________See_Table_3-4_for_the_required_values.____ If you change any of the system parameter values, you must update them using AUTOGEN. See Section 3.8.4.1 and Section 3.8.4.2. 3-18 Preparing Your System for Installation Preparing Your System for Installation 3.8 Installation Procedure Requirements 3.8.4.1 Updating Dynamic System Parameters with AUTOGEN To update the dynamic system parameter values, do the following: 1. Run AUTOGEN as follows: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS 2. Write the changes to the current system: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> WRITE ACTIVE 3. Press Ctrl/Z to leave SYSGEN You do not need to reboot your system to make your new values take effect. For more information, see the OpenVMS manual describing the AUTOGEN utility. 3.8.4.2 Updating Non-Dynamic System Parameter with AUTOGEN To update non-dynamic system parameter values, do the following: 1. Run AUTOGEN as follows: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS 2. Check the values 3. Manually reboot the system when convenient ________________________ Note ________________________ You must reboot your system in order for the new values to take effect. ______________________________________________________ For more information, see the OpenVMS manual describing the AUTOGEN utility. Preparing Your System for Installation 3-19 Preparing Your System for Installation 3.8 Installation Procedure Requirements 3.8.5 Disk Space on Your System Disk or Alternate Working Device This section discusses the disk space requirement for your kit working device during an ALL-IN-1 Version 3.1 installation. The default disk for your kit working device is your system disk. If your system disk does not have sufficient space, you can specify an alternate working device (AWD) when you start the installation. The disk space values for your kit are given in the ALL-IN-1 Installation: Language and Market Supplement. You must also check the disk space requirements on the target disks where ALL-IN-1 Version 3.1 will be installed. See Section 3.8.7. You can run the installation in either safety or non-safety mode. ________________________ Note ________________________ Digital recommends that you run your installation in safety mode (the default). ______________________________________________________ When you run the installation in safety mode, all of the ALL-IN-1 Version 3.1 kit is restored onto the system disk or AWD before the files are copied to their target locations. This means that you need a disk space requirement greater than the total size of the ALL-IN-1 Version 3.1 kit on your system disk. If you do not have enough disk space to run the installation in safety mode, you can run the installation in non-safety mode. In this case, each kit saveset is restored to the system disk before being copied to the target area. You need an amount of disk space on your system disk greater than the size of the largest saveset provided in the ALL-IN-1 Version 3.1 kit. 3-20 Preparing Your System for Installation Preparing Your System for Installation 3.8 Installation Procedure Requirements 3.8.6 Using the OA$LIB_SHARE Disk as the AWD If you have sufficient space on the target disk on which OA$LIB_SHARE will reside, Digital recommends that you use this disk as the AWD. If you do have sufficient space to install on this target disk, the installation time can be reduced by approximately 20%. This is because the majority of the ALL-IN-1 files reside in the OA$LIB_SHARE directory and therefore the installation procedure can move those files to their target directories by using a RENAME operation, rather than a COPY operation. 3.8.7 Disk Space for ALL-IN-1 Areas on Target Disks You can install ALL-IN-1 Version 3.1 in the following ways: o On a single target disk o Across several target disks by installing ALL-IN-1 areas on separate disks. For upgrade installations, the installation procedure assumes that the ALL-IN-1 disks and top-level directories for the ALL-IN-1 areas have not changed, and that the ALL-IN-1 directory tree is the same. If you have moved any of the directories, you must put them back to their correct locations before upgrading. You can install more than one ALL-IN-1 area on the same disk. If you do this, add the disk space values for the two areas together to find the total space required on that disk. See Section 1.2.6 for more information about ALL-IN-1 areas. The disk space requirements for ALL-IN-1 language and market areas that you are installing are in the ALL-IN-1 Installation: Language and Market Supplement. To calculate the total disk space requirements for your installation, add together the disk space requirements given in this section and the requirements given in the ALL-IN-1 Installation: Language and Market Supplement. The disk space requirements for each ALL-IN-1 area are listed in the following tables: o Table 3-6 for a full installation. See Section 3.8.9. Preparing Your System for Installation 3-21 Preparing Your System for Installation 3.8 Installation Procedure Requirements o Table 3-7 for an upgrade installation. See Section 3.8.10. o Table 3-8 for addition of VAX or AXP architecture support. See Section 3.8.11. You are prompted to specify the target disks for each ALL-IN-1 area during the installation. 3.8.8 Assigning Logical Names to Your Disks Digital recommends that you assign logical names to your disks where possible. ________________________ Note ________________________ To avoid conflicts with system logical names, do not assign logical names that start with: o A1$ o OA$ o OA1$ ______________________________________________________ In all types of installation, the installation procedure checks for conflicting system and process logical names, which could cause the installation to fail. You can check for conflicts before you start the installation. See Section 3.11 which describes how to run the Perform all preinstallation checks (PC) option. The logical name checking includes a check for any existing logical names that start with OA$. An informational message lists the names found, and a warning message warns you that these logical names may be redefined. If a logical name conflict is found, an informational message is displayed. If the conflicting logical name is defined in a system table, you can remove the conflicting logical name from another process, and then repeat the check. If the conflicting logical name is specific to the installing process, then you must abort the installation to fix the problem and then restart it. The installation will not continue until the logical name checking has passed. 3-22 Preparing Your System for Installation Preparing Your System for Installation 3.8 Installation Procedure Requirements For all upgrade or update installations, make sure that ALL-IN-1 logical names do not point to system root directories; for example, OA$LIB_SHARE must not be defined as SYS$SYSROOT:[ALLIN1.LIB_SHARE]. Do not use SYS$SYSDEVICE in directory specifications if you are installing on a mixed architecture cluster as the SYS$SYSDEVICE is different for each architecture. 3.8.9 Full Installation: Disk Space for ALL-IN-1 Areas Table 3-6 gives the disk space requirements for installing ALL-IN-1 areas on the system and target disks. The disk space requirements given are those used during the installation. The permanent space used when the installation has completed may be slightly less. ________________________ Note ________________________ If you do not choose to integrate WPS-PLUS during the installation, you can decrease the disk space in the shared library area by approximately 3000 blocks. If you choose to integrate WPS-PLUS without the associated PostScript files, you can decrease the disk space in the shared library area by approximately 3000 blocks. ______________________________________________________ Table_3-6_Full_Installation:_Disk_Space_for_ALL-IN-1_Areas_ ALL-IN-1_Area_for__________VAX_________AXP_________________ System disk files[1] 20 000 55 000 Shared library files 52 000 77 000 Shared data files 12 500 12 500 [1]Space_required_to_provide_ALL-IN-1_shared_files_to______ system directories. Add the value given in the ALL-IN-1 Installation: Language and Market Supplement to get the total value. (continued on next page) Preparing Your System for Installation 3-23 Preparing Your System for Installation 3.8 Installation Procedure Requirements Table 3-6 (Cont.) Full Installation: Disk Space for __________________ALL-IN-1_Areas___________________________ ALL-IN-1_Area_for__________VAX_________AXP_________________ Shared areas[2] 1000 1000 ALL-IN-1 Manager 1000 1000 account[3] [2]Multiply_the_disk_space_required_by_the_number_of_shared areas you wish to create during the installation. [3]Includes all utility accounts, for example, IVP and POSTMASTER. ___________________________________________________________ For the disk space values for the primary language files, see the ALL-IN-1 Installation: Language and Market Supplement. ________________________ Note ________________________ Do not create the ALL-IN-1 manager's account in a subdirectory of an OpenVMS system directory. ______________________________________________________ 3.8.10 Upgrade Installation: Disk Space for ALL-IN-1 Areas Table 3-7 gives the disk space requirements for upgrading ALL-IN-1 areas on the system and target disks. This applies to upgrades from ALL-IN-1 Version 3.0 and ALL-IN-1 STARTER Version 3.0. The disk space requirements given are those used during the installation. The permanent space used when the installation has completed may be slightly less. The values given in the table assume that you choose to purge files during the installation. If you choose not to purge replaced files, you must use the values given in Table 3-6. ________________________ Note ________________________ If you do not choose to integrate WPS-PLUS during the installation, you can decrease the disk space in the shared library area by 3000 blocks. 3-24 Preparing Your System for Installation Preparing Your System for Installation 3.8 Installation Procedure Requirements If you choose to integrate WPS-PLUS without the associated PostScript files, you can decrease the disk space in the shared library area by 2000 blocks. ______________________________________________________ Table 3-7 Upgrade Installations: Disk Space for ALL-IN-1 __________Areas____________________________________________ Disk Space ALL-IN-1_Area_for__________VAX_________Disk_Space_AXP[1]___ System files[2] 10 000 45 000[1] Shared library files 10 000 77 000[1] Shared data files 2000 2000[1] [1]Applies_to_update_installation_where_ALL-IN-1_Version___ 3.1 is already installed. [2]Space required to provide ALL-IN-1 shared files to system directories. Add the value given in the ALL-IN-1 Installation: Language and Market Supplement to get the total value ___________________________________________________________ For the disk space values for the primary language files, see the ALL-IN-1 Installation: Language and Market Supplement. 3.8.11 Addition of Architecture Support: Disk Space for ALL-IN-1 areas Table 3-8 gives the disk space requirements for installing architecture support on the system and ALL-IN-1 target disks. Preparing Your System for Installation 3-25 Preparing Your System for Installation 3.8 Installation Procedure Requirements Table 3-8 Addition of Architecture Support: Disk Space for __________ALL-IN-1_Areas___________________________________ ALL-IN-1_Area_for__________VAX___________AXP_______________ System files[1] 15 000 45 000 Shared library files 35 000 65 000 [1]Space_required_to_provide_ALL-IN-1_files_to_system______ directories. Add the value given in the ALL-IN-1 Installation: Language and Market Supplement to get the total value ___________________________________________________________ For the disk space values for the primary language files, see the ALL-IN-1 Installation: Language and Market Supplement. 3.8.12 Disk Quota Allocation If disk quota is enabled, the installation procedure adds sufficient disk quota for accounts and identifiers created during the installation. 3.8.13 Installed Images Make sure that the following shareable image and message files are installed on your system before you install ALL-IN-1. 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 certain processors, the file is SYS$SHARE:UVMTHRTL.EXE) o SYS$SHARE:NMLSHR.EXE o SYS$SHARE:PASRTL.EXE (VAX only) o SYS$SHARE:SCNRTL.EXE (VAX only) o SYS$SHARE:SCRSHR.EXE o SYS$SHARE:VMSRTL.EXE (VAX only) 3-26 Preparing Your System for Installation Preparing Your System for Installation 3.8 Installation Procedure Requirements o SYS$SHARE:VAXCRTL.EXE (VAX only) o SYS$SHARE:DECC$SHR.EXE (AXP only) To check which images are installed on your system, enter the following commands: $ INSTALL INSTALL> LIST imagename imagename; Open Shar Lnkbl imagename is the directory and file specification of the image to be checked. If there is no entry for the image or the qualifiers are incorrect, you must install the image with the correct qualifiers. To install: o FDVMSG.EXE and FDVSHR.EXE, see Section 3.8.14. o Other images, see Section 3.8.15. For more information about installing images, see the manual describing the Install Utility. 3.8.14 Installing FDVMSG.EXE and FDVSHR.EXE Images If the images FDVMSG.EXE and FDVSHR.EXE are not installed, do the following: 1. Edit the command procedure SYS$STARTUP:FMSTARTUP.COM to remove the EXIT command that appears before the entry: RUN SYS$SYSTEM:INSTALL 2. Execute the command procedure SYS$STARTUP:FMSTARTUP.COM 3.8.15 Installing Other Images Install other images as follows: $ INSTALL INSTALL> CREATE imagename /OPEN /SHARED /HEADER_RES INSTALL> EXIT Preparing Your System for Installation 3-27 Preparing Your System for Installation 3.8 Installation Procedure Requirements 3.8.16 Checking The Location of DCLTABLES.EXE Check that DCLTABLES.EXE is in the directory SYS$COMMON:[SYSLIB]. If it is in a different directory, move it to this location before starting the installation. To check if DCLTABLES.EXE is in the correct location, enter: $ INSTALL INSTALL> LIST/FULL SYS$COMMON:[SYSLIB]DCLTABLES.EXE If it is not in the correct location, remove it: INSTALL> REMOVE DCLTABLES.EXE Move DCLTABLES.EXE to the correct location and then replace it: INSTALL> CREATE DCLTABLES.EXE /OPEN/SHARED/HEADER_RES 3.9 Additional Tasks for Upgrade Installations If you are upgrading an existing ALL-IN-1 system, do the following: o Review your object libraries. Your object libraries may have been updated if you installed layered products. If you have any object libraries or files (.OLB or .OBJ) in the directories OA$SITE_BUILD_SHARE or OA$SITE_BUILD_LLV, check whether they are compatible with ALL-IN-1 Version 3.1. Remove any that are incompatible. Although they are not used during the installation, they will cause problems if you need to relink ALL-IN-1 after the installation. A warning is displayed if .OBJ or .OLB files are found in these directories during the installation. o If you have a multilingual system, check that the files OA$LLV*.EXE are not in SYS$COMMON:[SYSLIB]. If they are, move them to the SYS$SYSROOT:[SYSLIB] directory before upgrading. o Check that all files in your site areas have at least system write access (S:W) and that Digital ALL-IN-1 directories in non-site areas also have system delete access (S:D). 3-28 Preparing Your System for Installation Preparing Your System for Installation 3.9 Additional Tasks for Upgrade Installations o Make copies of customized data files. See Section 3.9.1. 3.9.1 Copying Customized Data Files ALL-IN-1 Version 3.1 uses modified versions of several data files: o PROFILE.DAT o SM_ACCOUNT_TYPES.DAT o SM_POLICIES.DAT o OAFC_SERVER_MASTER.DAT (this is already done if you have installed the TeamLinks Connection Package (TLC) o FORMAT.DAT ALL-IN-1 Version 3.1 also supplies new versions of the File Definition Language (FDL) files in OA$LIB_SHARE which are used to convert the corresponding data files to the new format. The old FDL files are not required after the upgrade. Before upgrading, make copies of any data files that you have customized as new versions of data files are provided with ALL-IN-1 Version 3.1. You must also return the data files to the Digital standard format before you upgrade. In the following instructions, the data file, PROFILE.DAT is used as an example. To make copies of your customized data file and return them back to the Digital standard format, do the following: 1. Make a backup copy of the modified PROFILE.DAT file, preferably outside the ALL-IN-1 directory structure: $ COPY OA$DATA_SHARE:PROFILE.DAT device:[directory]CUSTOM_PROFILE.DAT 2. Use Customization Management to make copies of the customized PROFILn forms. For example, copy the customized forms to CUSTOM_PROFILn and modify the named data so that the .FILE directive specifies the location of the backup copy of the file. 3. Make the copies of the customized forms live. 4. Remove the customized PROFILn forms and PROFIL.FDL from the live area. Preparing Your System for Installation 3-29 Preparing Your System for Installation 3.9 Additional Tasks for Upgrade Installations 5. Convert the modified PROFILE.DAT back to the standard format. This may temporarily lose some data, but you can reapply it from the backup copy of PROFILE.DAT later. To convert PROFILE.DAT back to the Digital standard format, enter the following from the choice field of a menu: ADD mailboxname /PASSWORD=password /COMPLETE_MESSAGES _ /IGNORE_SENDER _ /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS MRM> EXIT Note that you must not use the /OWNER qualifier when setting up the mailbox. 3.11 Preinstallation System Check The ALL-IN-1 Version 3.1 installation procedure provides a Perform all preinstallation checks (PC) option. Use this option to ensure that you have made all necessary system changes before installing the software. You can use this option while an existing ALL-IN-1 system is running so you do not have to ask your users to log out of the system. The option for preinstallation checks allows you to: o Run the phase of the installation in which you answer questions and the installation procedure performs system checks o Fix errors encountered by the installation procedure o Exit without performing the installation Where possible the installation checks are done in an order which finds fatal errors first. Section 3.11.1 describes the types of errors that are detected. Section 3.11.2 describes how to use the Perform all preinstallation checks (PC) option. Preparing Your System for Installation 3-31 Preparing Your System for Installation 3.11 Preinstallation System Check 3.11.1 Types of Errors Reported The following types of errors are detected: o Fatal errors These are errors which cannot be corrected without stopping the installation procedure. Fatal errors include: - Errors that require the machine to be rebooted - Errors that require an upgrade to prerequisite software, including OpenVMS, Message Router, and the Message Router VMSmail Gateway o Non-fatal errors These are errors that can be corrected from another process without stopping the installation procedure. Non-fatal errors include: - Shareable images that are not installed - Logical names that are not defined - System parameters that can be changed dynamically - Prerequisite software files that are missing - Insufficient disk space 3.11.2 Running the Perform all Preinstallation Checks (PC) Option To run the Perform all preinstallation checks (PC) option, follow Steps 1 to 5 in Table 5-2 until you are prompted with a list of installation options, for example: Using the FULL ALL-IN-1 V3.1 kit, the following installation types can be performed: (1) A full installation of ALL-IN-1 V3.1 (2) Add VAX architecture support to an existing AXP ALL-IN-1 system (RL) Register licenses for prerequisite software * Which installation do you wish to perform [1]: Do the following: 1. Press Return to choose the first option. 3-32 Preparing Your System for Installation Preparing Your System for Installation 3.11 Preinstallation System Check ________________________ Note ________________________ Choosing this option does not install the software. ______________________________________________________ The following message is displayed: The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all preinstallation checks * Which action do you wish to perform [I]: 2. Choose the Perform all preinstallation checks (PC) option by entering: PC. 3. If a check fails with an error that can be corrected without stopping the installation procedure, you are asked if you want to correct the error before continuing. If you answer yes, the installation checking procedure pauses so that you can fix the error from another process. When the error is fixed, you can resume the procedure, and the check is repeated. If you choose not to correct the error, you have the option of halting the procedure or continuing to perform the remaining checks. If you choose to continue, the installation procedure will terminate when all the checks are performed. 3.12 System Preparation Tasks To prepare your system for an upgrade installation of ALL-IN-1 Version 3.1, carry out the following steps before starting the installation. Each step is described in the following sections. For a full ALL-IN-1 Version 3.1 installation, you do not need to carry out all of these tasks. From the privileged SYSTEM account, do the following: 1. Shut down ALL-IN-1. Applies to upgrade installations only. See Section 3.12.1. Preparing Your System for Installation 3-33 Preparing Your System for Installation 3.12 System Preparation Tasks If you are running Calendar Manager[TM], you must shut it down before starting the installation. 2. Ensure that Message Router is running and is correctly configured. 3. Deinstall files in the site areas that are installed in memory. Applies to upgrade installations only. See Section 3.12.2. 4. Start the queue manager, if necessary. Applies to full and upgrade installations. 5. Run the Mail Sender and Fetcher from the ALL-IN-1 manager's ALL-IN-1 account to ensure that all mail messages have been processed. Applies to upgrade installations only. 6. Back up the system disk and any target disks. See Section 3.12.3. 3.12.1 Shut Down ALL-IN-1 Ask users currently on the system to log out, and then shut down ALL-IN-1. ________________________ Note ________________________ ALL-IN-1 must not be used by any batch jobs or users during the installation, or the installation will fail. ______________________________________________________ Do not allow anyone to log in again while the installation is in progress. You can allow OpenVMS users to remain on the system, but it is important to ensure that users do not use DCL HELP while the installation is in progress, as this can cause file locking problems when the DCL HELP library is updated during the installation. If possible, it is safer to ensure that there are no active users on the system. 3-34 Preparing Your System for Installation Preparing Your System for Installation 3.12 System Preparation Tasks 3.12.2 Deinstall Files Installed in Memory If you have any files in the site areas that are installed in memory, for example, SITE$OA.A1$SECTION, deinstall them on all nodes in the cluster before you start the installation. Deinstalling files from memory will prevent them from being write locked. The installation sets an ACL on all files in the site areas so you must ensure that all files in the site area have system write access (S:W). 3.12.3 Back Up Your System and Target Disks Digital recommends that you do a system disk backup before installing any software because: o If a system failure occurs at a critical point during installation, your ALL-IN-1 system 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. If you are going to install ALL-IN-1 Version 3.1 on more than one disk, back up the target disks that you will be using. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS System Management Subkit. At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Preparing Your System for Installation 3-35 4 _________________________________________________________________ Planning and Implementing a Minimal Shutdown Upgrade This chapter describes how the minimal shutdown upgrade works and includes all the steps for planning and implementing this type of upgrade. You should only consider using this option if the amount of time that your system is shut down is critical to your organization. If it is not critical, then it is recommended that you follow the conventional upgrade path as described in Section 1.3. The minimal shutdown upgrade reduces the time that ALL-IN-1 must be shut down during the installation to 20% of the conventional upgrade time. ________________________ Note ________________________ You must only use this option if you have the following expertise: o Experience of installing ALL-IN-1 o A thorough understanding of the ALL-IN-1 directory structure o A thorough understanding of how the ALL-IN-1 installation procedure works Read all of this chapter carefully before deciding to do a installation using this option. ______________________________________________________ If you are running a multilanguage system, you can only use this option to upgrade the primary language. you must upgrade the additional language using a conventional upgrade procedure. Planning and Implementing a Minimal Shutdown Upgrade 4-1 Planning and Implementing a Minimal Shutdown Upgrade 4.1 How the Minimal Shutdown Upgrade Works 4.1 How the Minimal Shutdown Upgrade Works During a conventional upgrade installation, files in an existing ALL-IN-1 Version 3.0 shared library and primary language areas are superseded by the Version 3.1 files. Providing new files to these target areas accounts for the majority of the time taken to do a conventional upgrade. The ALL-IN-1 system must be shut down while files are being updated to prevent users trying to access a constantly changing environment. The minimal shutdown upgrade has two installation phases: o In phase 1, the Version 3.1 installation procedure creates and populates new ALL-IN-1 shared library and primary language areas while your existing ALL-IN-1 Version 3.0 system is still running. ALL-IN-1 Version 3.1 system files are installed in a holding area until the second phase of the installation when they are copied to their target directories. Phase 1 is described in Section 4.1.1. o In phase 2, ALL-IN-1 is shut down while the installation procedure is rerun to copy files from the holding area into their target directories. Phase 2 is described in Section 4.1.3. In addition to the two-phase installation procedure, there is also a manual postinstallation phase. Two command procedures are provided which: o Copy the new Version 3.1 files into the existing Version 3.0 areas. o Redefine logicals to reference the Version 3.0 directory structure which now contains the ALL-IN-1 Version 3.1 files. Postinstallation tasks are described in more detail in Section 4.6. You must briefly shut down ALL-IN-1 during this postinstallation phase in order to start up the new ALL-IN-1 Version 3.1 system. 4-2 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.1 How the Minimal Shutdown Upgrade Works 4.1.1 Explanation of Phase 1 For phase 1, you must run the ALL-IN-1 Version 3.1 installation procedure. All system parameter and disk space checks are done during this phase. In phase 1 of the minimal shutdown upgrade, you do not need to shut down ALL-IN-1. When you run the ALL-IN-1 Version 3.1 installation procedure using VMSINSTAL, it does the following: o Creates new ALL-IN-1 shared library and primary language areas. See Figure 4-1. o Installs the Version 3.1 files to the new areas. These are areas 6 and 7 in Figure 4-1. o Installs ALL-IN-1 Version 3.1 system files in a holding directory, SYS$COMMON:[SYSUPD.A1031_HOLDING], on SYS$SYSDEVICE until they can be provided to their target directories. The holding directory will always be in this location, even if a AWD is specified. o Creates procedures that will be used in phase 2 to reset the installation environment. o Leaves the SITE and DATA_SHARE directories unchanged. Figure 4-1 shows an ALL-IN-1 Version 3.0 system with all areas installed on one disk under a common root directory, and all the SITE areas under a common site directory. Figure 4-1 Minimal Shutdown Upgrade: Phase 1 Planning and Implementing a Minimal Shutdown Upgrade 4-3 Planning and Implementing a Minimal Shutdown Upgrade 4.1 How the Minimal Shutdown Upgrade Works 4.1.2 Files and Directories Involved in Phase 1 To understand what is happening during the minimal shutdown upgrade, it is important to know which directories are affected. ________________________ Note ________________________ The ALL-IN-1 Version 3.0 system is unchanged during phase 1. ______________________________________________________ Mail areas may also exist under the ALL-IN-1 directory tree but they are are not shown in Figure 4-1 as they are not affected by the minimal shutdown upgrade. The ALL-IN-1 areas shown in Figure 4-1 contain the following directories: 1 LIB_SHARE ( ALL-IN-1 shared library files) area o ADMIN_DATA.DIR o BLP_SHARE.DIR o DO_SHARE.DIR o GROUP_SHARE.DIR o LIB_SHARE.DIR o LOG.DIR o PRINT.DIR o SCP_SHARE.DIR o SITE.DIR o SOURCES_SHARE.DIR o SYSTEM_DICTIONARIES.DIR o SYSTEM_LISTS.DIR 2 LIB_LLV ( ALL-IN-1 primary language files) area o BLP_ENGLISH.DIR o CBI_ENGLISH.DIR o DATA_ENGLISH.DIR o DO_ENGLISH.DIR 4-4 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.1 How the Minimal Shutdown Upgrade Works o IVP_ENGLISH.DIR o LIB_ENGLISH.DIR o SCP_ENGLISH.DIR o SITE.DIR o SOURCES_ENGLISH.DIR 3 DATA_SHARE ( ALL-IN-1 shared data files) area o DATA_SHARE.DIR 4 ALL-IN-1 SITE area, containing site directories and files 5 UTILITY area, which includes the ALL-IN-1 manager and utility accounts. o A1$SCRIPT_SYMBIONT.DIR o IVPUSER.DIR o MGR.DIR o POSTMASTE.DIR o TRANSFER_INCOMING.DIR o TRANSFER_OUTGOING.DIR The following directories are included for completeness, but they are not affected by the minimal shutdown upgrade: o ALL-IN-1 Mail area which contains the directories SHARED_*.DIR, where * is a letter between A and E. o ALL-IN-1 shared directories area which contains the directories SHARE*#.DIR, where * is a letter between A and E, and # is a number between 1 and 9999. The ALL-IN-1 Version 3.1 areas include all of the directories listed in the Version 3.0 areas (1 and 2 in Figure 4-1), plus the following new directories: 7 LIB_SHARE Version 3.1 area: o OA$EXE_AXP_SHARE.DIR o OA$EXE_VAX_SHARE.DIR o SOURCES_AXP_SHARE.DIR o SOURCES_VAX_SHARE.DIR Planning and Implementing a Minimal Shutdown Upgrade 4-5 Planning and Implementing a Minimal Shutdown Upgrade 4.1 How the Minimal Shutdown Upgrade Works 8 LIB_LLV Version 3.1 area: o OA$EXE_AXP_ENGLISH.DIR o OA$EXE_VAX_ENGLISH.DIR o SOURCES_AXP_ENGLISH.DIR o SOURCES_VAX_ENGLISH.DIR In addition, a new DATA_LLV directory is created under this new area. 4.1.3 Explanation of Phase 2 For the second phase of the minimal shutdown upgrade, you must shut down your ALL-IN-1 Version 3.0 system and rerun the ALL-IN-1 Version 3.1 installation procedure, using VMSINSTAL. In phase 2, the installation procedure does the following: o Copies ALL-IN-1 Version 3.1 system files from the holding area to their target directories. o Runs automatic postinstallation procedures to : - Update the file, OA$DATA_SHARE:A1CONFIG.DAT, to reference the new ALL-IN-1 Version 3.1 shared library and primary language areas (areas 6 and 7 in Figure 4-1). - Runs A1V31START.COM using the new data in OA$DATA_ SHARE:A1CONFIG.DAT. The ALL-IN-1 logicals are now defined to point to the new ALL-IN-1 Version 3.1 areas for the shared library and primary language areas (areas 6 and 7 in Figure 4-1) and to the existing ALL-IN-1 Version 3.0 areas (areas 3, 4 and 5 in Figure 4-1. - The following Customization Management files are also updated: CM$APP.DAT CM$MAF.DAT CM$AUTH$LOCATIONS.DAT 4-6 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.1 How the Minimal Shutdown Upgrade Works These files are updated as they contain hard-coded references to the shared library and primary language areas. The old versions of these files are preserved as MSU_*.DAT As an example, the situation at the end of phase 2 of the minimal shutdown upgrade can be illustrated by looking at the definition of the ALL-IN-1 logical, OA$DO: $ SHOW LOGICAL OA$DO "OA$DO" = "OA$SITE_DO_LLV" (LNM$SYSTEM_TABLE) = "OA$SITE_DO_SHARE" = "OA$DO_LLV" = "OA$DO_SHARE" 1 "OA$SITE_DO_LLV" = "DISK$ALLIN1:[ALLIN1_V30.SITE.DO_ENGLISH]" 1 "OA$SITE_DO_SHARE" = "DISK1$ALLIN1:[ALLIN1_V30.SITE.DO_SHARE]" 1 "OA$DO_LLV" = "DISK$ALLIN1_UPGRADE:[ALLIN1_V31.DO_ENGLISH]" 1 "OA$DO_SHARE" = "DISK$ALLIN1_UPGRADE:[ALLIN1_V31.DO_SHARE]" The OA$DO logical still references the DO_* directories in the [ALLIN1_V30.SITE...] area, but OA$DO_SHARE and OA$DO_ LLV reference the DO_* directories in the new V3.1 shared library and primary language areas. As a second example, look at the OA$DATA logical: $ SHOW LOGICAL OA$DATA "OA$DATA" = "OA$SITE_DATA_SHARE" (LNM$SYSTEM_TABLE) = "OA$SITE_DATA_LLV" = "OA$DATA_SHARE" = "OA$DATA_LLV" 1 "OA$SITE_DATA_SHARE" = "DISK$ALLIN1:[ALLIN1_V30.SITE.DATA_SHARE]" 1 "OA$SITE_DATA_LLV" = "DISK$ALLIN1:[ALLIN1_V30.SITE.DATA_ENGLISH]" 1 "OA$DATA_SHARE" = "DISK$ALLIN1:[ALLIN1_V30.DATA_SHARE]" 1 "OA$DATA_LLV" = "DISK$ALLIN1_UPGRADE:[ALLIN1_V31.DATA_ENGLISH]" All the DATA_* directories except OA$DATA_LLV are located in the old directory tree. A Version 3.1 DATA_LLV directory is created in the primary language area during phase 1. During phase 2, the files in the Version 3.0 DATA_LLV directory are moved into the new Version 3.1 DATA_LLV directory. Planning and Implementing a Minimal Shutdown Upgrade 4-7 Planning and Implementing a Minimal Shutdown Upgrade 4.2 Disadvantages of a Minimal Shutdown Upgrade 4.2 Disadvantages of a Minimal Shutdown Upgrade The minimal shutdown upgrade has the following disadvantages which must be carefully considered: o You need the same amount of disk space as for a new ALL-IN-1 installation. o You must do some additional postinstallation tasks to tidy up your system. o ALL-IN-1 Version 3.0 areas and ALL-IN-1 Version 3.1 areas will exist at the same time. o Shutdown is still necessary, although this is 20% of the time taken for a normal upgrade. An additional brief shutdown is also required to start ALL-IN-1 Version 3.1 after completing the manual postinstallation tasks. See Section 4.6. o It requires an experienced installer who fully understands the ALL-IN-1 installation and the ALL-IN-1 directory structure. o Users may experience some degradation in performance while the upgrade is occurring, although this is minimized by installing the ALL-IN-1 Version 3.1 areas on a different disk. o The site and base areas will be in different directory trees which may cause confusion. 4.3 Installation Planning Decisions Before running the installation, you must decide on the following: o The device on which the ALL-IN-1 Version 3.1 shared library area will be installed o A top-level directory for the shared library files o The device on which the ALL-IN-1 Version 3.1 primary language files will be installed 4-8 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.3 Installation Planning Decisions o A top-level directory for the primary language files ________________________ Note ________________________ It is recommended that you install ALL-IN-1 Version 3.1 on a different device to your ALL-IN-1 Version 3.0 system. This will minimize any performance impact during phase 1. If you have to install on the same device, the top- level directory name for your ALL-IN-1 Version 3.1 files must be different to the top-level directory name used for your ALL-IN-1 Version 3.0 system. It is recommended that you choose a different top- level directory name for all installations, in case there is a delay between running phase 1 and phase 2. ______________________________________________________ 4.4 Preparing Your System for a Minimal Shutdown Upgrade To prepare your system: o Follow the preparation tasks for a normal upgrade installation. See Chapter 3. o If you are upgrading a customized ALL-IN-1 Version 3.0 system, complete all the tasks in Chapter 2. o Use the total disk space requirements as for a full installation. See ALL-IN-1 Installation: Language and Market Supplement. o For the ALL-IN-1 areas, use the disk space values in Table 4-1. The postinstallation tasks for a minimal shutdown upgrade are described in more detail in Section 4.6. In addition, see Chapter 8 for additional postinstallation tasks. Planning and Implementing a Minimal Shutdown Upgrade 4-9 Planning and Implementing a Minimal Shutdown Upgrade 4.4 Preparing Your System for a Minimal Shutdown Upgrade Table 4-1 Minimal Shutdown Upgrade: Disk Space for __________ALL-IN-1_Areas___________________________________ Area__________________Disk_Space_(blocks)__________________ System files[1] 20 000 Shared library files 52 000 Primary language See the ALL-IN-1 Installation: files[1] Language and Market Supplement. [1]Installed_on_SYS$SYSDEVICE._____________________________ ___________________________________________________________ 4.5 Installation Procedure for Minimal Shutdown Upgrade _______________________ CAUTION _______________________ Do not start the installation until you have completed the system preparation tasks in Chapter 3. ______________________________________________________ Questions asked by installation procedure are marked with an asterisk (*) at the beginning of the line. For help on answering a particular question, enter a question mark (?). During the installation procedure a number of cautions and general informational messages are displayed. Read all the displayed messages carefully. Digital recommends that you keep a record of the installation. You can do this by using either a hard copy terminal or a log file. To keep a record in a log file, enter: $ SET HOST 0/LOG=filename where filename is the name of the log file. The log file is created in the directory where you enter the command. If you do not specify a filename, the file is called SETHOST.LOG. The installation log file will be about 200 blocks. 4-10 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.5 Installation Procedure for Minimal Shutdown Upgrade 4.5.1 Procedure for Phase 1 Table 4-2 gives all the steps for phase 1 of the minimal shutdown upgrade procedure. Table 4-2 Installation Procedure for Phase 1 of the Minimal __________Shutdown_Upgrade_______________________________________ 1 Load and mount the media that contains the software kit. This log shows an installation from tape. _________________________________________________________________ 2 Invoke the VMSINSTAL procedure from the SYSTEM account. Enter the following commands: $ SET DEFAULT SYS$UPDATE $ VMSINSTAL A1031 device To use an alternate working device (AWD), enter the following command lines: $ SET DEFAULT SYS$UPDATE $ VMSINSTAL A1031 device OPTIONS AWD=disk VAX/VMS Software Product Installation Procedure V5.5-2 It is 24-JAN-1994 at 17:16. Enter a question mark (?) at any time for help. device is the device on which you have mounted the distribution media. You can use a physical or a logical device name but do not use logical device names beginning with A1$, OA$, or OA1$. A1031 is the product identifier. _________________________________________________________________ 3 Verify your system backup. * Are you satisfied with the backup of your system disk [YES]? Press RETURN to continue. _________________________________________________________________ (continued on next page) Planning and Implementing a Minimal Shutdown Upgrade 4-11 Planning and Implementing a Minimal Shutdown Upgrade 4.5 Installation Procedure for Minimal Shutdown Upgrade Table 4-2 (Cont.) Installation Procedure for Phase 1 of the __________________Minimal_Shutdown_Upgrade_______________________ 4 Load the distribution media (first volume). Enter the product identifier at the prompt. Enter the products to be processed from the first distribution volume set: * Products: A1031 * Enter installation options you wish to use (none): Please mount the first volume of the set on device * Are you ready? Y _________________________________________________________________ 5 Enter 2 to choose the minimal shutdown installation. The following products will be processed: A1 V3.1 Beginning installation of A1 V3.1 at 17:16 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. This is a LOCAL ALL-IN-1 V3.1 BASE kit The current ALL-IN-1 image identification is ALL-IN-1 V3.0. Using the FULL ALL-IN-1 V3.1 kit, the following installation types can be performed: (1) Upgrade of ALL-IN-1 V3.0 to ALL-IN-1 V3.1 (2) Minimal Shutdown Upgrade of ALL-IN-1 V3.0 to ALL-IN-1 V3.1 (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: 2 _________________________________________________________________ (continued on next page) 4-12 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.5 Installation Procedure for Minimal Shutdown Upgrade Table 4-2 (Cont.) Installation Procedure for Phase 1 of the __________________Minimal_Shutdown_Upgrade_______________________ 6 Press RETURN to confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks (RC) Run conflict checking and resolution tool (CART) * Which action do you wish to perform [I]: The installation procedure creates a holding area for the Version 3.1 system files: %VMSINSTAL-I- SYSDIR, This product creates system disk directory VMI$ROOT:[SYSUPD.A1031_HOLDING]. _________________________________________________________________ 7 Follow steps 9 to 30 in Table 5-2. _________________________________________________________________ 8 Specify the devices for the new ALL-IN-1 Version 3.1 areas: * Which device will hold the ALL-IN- 1 shared library files [A1DISK1:]: * Which device will hold the ALL-IN- 1 ENGLISH language files [A1DISK1:]: _________________________________________________________________ 9 Follow steps 32 to 37 in Table 5-2 _________________________________________________________________ 10 Specify the top-level directories for the new ALL-IN-1 Version 3.1 areas: * Enter ALL-IN-1 top- level directory required for the shared library files: * Enter ALL-IN-1 top- level directory required for all primary language files: (continued on next page) Planning and Implementing a Minimal Shutdown Upgrade 4-13 Planning and Implementing a Minimal Shutdown Upgrade 4.5 Installation Procedure for Minimal Shutdown Upgrade Table 4-2 (Cont.) Installation Procedure for Phase 1 of the __________________Minimal_Shutdown_Upgrade_______________________ _________________________________________________________________ 11 Enter the VMS username for the ALL-IN-1 MANAGER'S account. * What is the existing VMS username for the ALL-IN- 1 account [ALLIN1]: Enter the VMS username for the ALL-IN-1 account. The account details are displayed. _________________________________________________________________ 12 Confirm that the details of the ALL-IN-1 Manager's account are correct. You are not asked if you want to run the IVP in phase 1. When the installation procedure finishes, run the second ______phase_of_the_minimal_shutdown_upgrade._See_Section_4.5.2.__ 4.5.2 Phase 2 Procedure Table 4-3 give the steps in phase 2 of the minimal shutdown upgrade. Table 4-3 Installation Procedure for Phase 2 of the Minimal __________Shutdown_Upgrade_______________________________________ 1 Follow steps 1 to 4 in Table 4-2. _________________________________________________________________ (continued on next page) 4-14 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.5 Installation Procedure for Minimal Shutdown Upgrade Table 4-3 (Cont.) Installation Procedure for Phase 2 of the __________________Minimal_Shutdown_Upgrade_______________________ 3 Press RETURN to confirm that you want to complete the minimal shutdown upgrade. The following products will be processed: A1 V3.1 Beginning installation of A1 V3.1 at 11:28 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. This is a LOCAL ALL-IN-1 V3.1 BASE kit The installation procedure has discovered the existence of the directory SYS$COMMON:[SYSUPD.A1031_HOLDING]. This directory is created by the first phase of a "Minimum Shutdown Upgrade". Answer YES to the following question if you have performed the first phase of a "Minimum Shutdown Upgrade" and wish to complete it. * Complete a minimum shutdown upgrade [YES]? _________________________________________________________________ 2 Press RETURN to confirm that you want to purge files replaced by this installation. * Do you want to purge files replaced by this installation [YES]? _________________________________________________________________ (continued on next page) Planning and Implementing a Minimal Shutdown Upgrade 4-15 Planning and Implementing a Minimal Shutdown Upgrade 4.5 Installation Procedure for Minimal Shutdown Upgrade Table 4-3 (Cont.) Installation Procedure for Phase 2 of the __________________Minimal_Shutdown_Upgrade_______________________ 4 Press RETURN to confirm that you want to run the IVP. * Do you want to run the IVP after the installation [YES]? %A1-I-SETENV, Restoring installation environment to conclude upgrade... The file OA$SITE_BUILD_LLV:SITEOALLV.OLB will be renamed to OA$SITE_BUILD_LLV_ARCH:OLD_SITEOALLV.OLB to preserve any customisations in this object library. The file OA$SITE_BUILD_SHARE:SITEOALIBR.OLB will be renamed to OA$SITE_BUILD_SHARE_ARCH:OLD_SITEOALIBR.OLB to preserve any customisations in this object library. The installation procedure: o Restores the installation environment which was saved during phase 1. o Checks that ALL-IN-1 is shut down. o Copies files from the holding area to their target locations. o Runs automatic postinstallation tasks. When the installation has finished, do the manual ______postinstallation_tasks_in_Section_4.6._____________________ 4.6 Manual Postinstallation Procedures The postinstallation command procedures restore your ALL-IN-1 directory structure back to that of the ALL-IN-1 Version 3.0 system. When you have completed the postinstallation tasks in this section, you will be running a ALL-IN-1 Version 3.1 system. Files placed in ALL-IN-1 Version 3.0 directories by other applications will not be affected by these postinstallation command procedures. 4-16 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.6 Manual Postinstallation Procedures Figure 4-2 Minimal Shutdown Postinstallation Phase Figure 4-2 shows how the Version 3.1 files are restored to the Version 3.0 directory structure. See Section 4.6.1. Table 4-4 gives an overview of the two postinstallation procedures. See Section 4.6.1 for instructions on how to run these procedures. Table_4-4_Minimal_Shutdown_Postinstallation_Procedures_____ (continued on next page) Planning and Implementing a Minimal Shutdown Upgrade 4-17 Planning and Implementing a Minimal Shutdown Upgrade 4.6 Manual Postinstallation Procedures Table 4-4 (Cont.) Minimal Shutdown Postinstallation __________________Procedures_______________________________ A1$MIN_SHUT_ This procedure: RESTORE.COM o Checks disk space on the ALL-IN-1 target disks for the shared library and primary language files. If you choose to purge files, 25 000 blocks are required on the shared library disk and 50 000 blocks are required on the primary language disk. If there is insufficient disk space, the procedure will not continue. o Copies the new Version 3.1 files from the new ALL-IN-1 shared library area to the old Version 3.0 shared library area. See Figure 4-2. o Copies the new Version 3.1 files from the new ALL-IN-1 primary language area to the old primary language area. See Figure 4-2. o Purges the old files if requested. o Updates OA$DATA_SHARE:A1CONFIG.DAT to reference the Version 3.0 shared library and primary language areas which now contain the Version 3.1 files. In Figure 4-2 these are areas 6 and 7. (continued on next page) 4-18 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.6 Manual Postinstallation Procedures Table 4-4 (Cont.) Minimal Shutdown Postinstallation __________________Procedures_______________________________ A1_MIN_SHUT_SWAP.COM The ALL-IN-1 system must be shut down while this procedure is run. It must be run on all nodes in a VMScluster. It: o Does a shutdown check. o Removes ALL-IN-1 images. On one of the nodes in the cluster, this procedure must be run with the parameter SWAP, which starts up the new ALL-IN-1 Version 3.1 system. ______________________See_Section_4.6.1.___________________ 4.6.1 Running the Postinstallation Procedures Log in to the privileged OpenVMS SYSTEM account and do the following: 1. Keep a log of the procedures by entering: $ SET HOST 0/LOG=filename 2. Run A1$MIN_SHUT_RESTORE.COM: $ @OA$LIB_SHARE:A1$MIN_SHUT_RESTORE.COM ************************************************************************ Running A1$MIN_SHUT_RESTORE.COM ... ************************************************************************ Digital advises that you keep a record of this procedure run. You can do this by: $ SET HOST 0/LOG=filename.LOG * Are you logging this procedure run? [NO]Y %A1-I-CHKLOG, Checking ALL-IN-1 logicals ... %A1-I-CALSPA, Calculating disk space requirements ... If you answer YES to the following question this procedure will automatically purge the target directories after files have been moved. Purging files reduces (by about fifty percent) the amount of free disk space required on the target disk(s). Planning and Implementing a Minimal Shutdown Upgrade 4-19 Planning and Implementing a Minimal Shutdown Upgrade 4.6 Manual Postinstallation Procedures IMPORTANT: All files in the target directories are purged, NOT just the old versions of the moved files. If you want to preserve previous versions of any files in the target directories answer NO to this question. * Do you want to purge files in target areas? [YES] *********************************************************************** Moving A1DISK4:[A1V31.ADMIN_DATA]*.* to A1DISK1:[ALLIN1.ADMIN_DATA]*.* *********************************************************************** %BACKUP-S-CREATED, created A1DISK1:[ALLIN1.ADMIN_DATA]*********** .. ... .. %OA-I-LASTLINE, Updating A1CONFIG.DAT ... ( end of restore procedure ) 3. Check the log file to ensure that all the files in the ALL-IN-1 Version 3.1 areas are copied to the ALL-IN-1 Version 3.0 areas. 4. Shut down ALL-IN-1. 5. On each node in the cluster, enter the following command: $ @OA$LIB_SHARE:A1$MIN_SHUT_SWAP.COM 6. On one node in the cluster, run A1$MIN_SHUT_SWAP.COM with the SWAP parameter to restart the ALL-IN-1 Version 3.1 system: $ @OA$LIB_SHARE:A1$MIN_SHUT_SWAP.COM SWAP *********************************************************************** Running A1$MIN_SHUT_SWAP.COM ... *********************************************************************** Digital advises that you keep a record of this procedure run. You can do this by: $ SET HOST 0/LOG=filename.LOG * Are you logging this procedure run? [NO] Y %A1-I-CHKSHUT, Checking that ALL-IN-1 is shut down .. %A1-I-REMGBL, Running ALL-IN-1 to remove installed global sections .. 4-20 Planning and Implementing a Minimal Shutdown Upgrade Planning and Implementing a Minimal Shutdown Upgrade 4.6 Manual Postinstallation Procedures %OA-I-LASTLINE, Deinstalling FLCs ... %OA-I-LASTLINE, Deinstalling TXL ... %OA-I-LASTLINE, Deinstalling Message section files ... %A1-I-REMIMG, Removing installed images ... *************************************************** ** Running Startup Procedure for ALL-IN-1 V3.1 ** *************************************************** Installing ALL-IN-1 images .. .......... .......... .. ------ ALL-IN-1 startup procedure completed ------ %OA-I-LASTLINE, Updating CM data files following a "Minimal Shutdown Upgrade" %OA-I-LASTLINE, Updating OA Base Root Directory in CM$APP %OA-I-LASTLINE, Updating CM$MAF %OA-I-LASTLINE, Updating OA SHARE Base Root Directory in CM$MAF %OA-I-LASTLINE, Updating OA ENGLISH Base Root Directory in CM$MAF %OA-I-LASTLINE, Updating Base logical translations in CM$AUTH$LOCATIONS 7. When it is convenient, you can delete the areas created for the Version 3.1 files. Planning and Implementing a Minimal Shutdown Upgrade 4-21 5 _________________________________________________________________ Installation Procedure: Full, Upgrade and Architecture Support This chapter describes the procedures for installing the ALL-IN-1 Version 3.1 base, language and market components. The following types of installation are described: o Full installation of ALL-IN-1 Version 3.1 on a VAX system or an AXP system. See Section 5.2. o Upgrade installation of ALL-IN-1 Version 3.0 or ALL-IN-1 STARTER Version 3.0 to ALL-IN-1 Version 3.1 on a VAX system. See Section 5.2. o Addition of VAX or AXP architecture support for ALL-IN-1 Version 3.1 on a different architecture in the same VMScluster. See Section 5.3. For the minimal shutdown upgrade procedure, see Chapter 4. __________________ Before You Start __________________ Do not start the installation until you have completed the system preparation tasks in Chapter 3. ______________________________________________________ Questions asked by installation procedure are marked with an asterisk (*) at the beginning of the line. For help on answering a particular question, enter a question mark (?). During the installation procedure a number of cautions and general informational messages are displayed. Read all the displayed messages carefully. Table 5-1 gives information which you may need during the installation. Installation Procedure: Full, Upgrade and Architecture Support 5-1 Table_5-1_Information_About_the_Installation_Procedure_____ Question_________Answer____________________________________ How long The installation can take from one to will the six hours, depending on the type of installation processor you are using. The performance take? specification of the disks has the greatest effect. For example, an installation on a VAX 4000-300 system takes approximately 3.5 hours when files are installed on an RF71 disk and 1.5 hours if files are installed on an RZ26 disk. The times for full and upgrade installations are approximately the same. How do I get Enter ? at any time help? What is A1031 the product identifier? What do I Restart the installation from the do if the beginning. See Chapter 7. installation fails before the automatic postinstalla- tion phase? How do I Press CTRL/Y. abort the The installation procedure deletes all installation? files in the installation temporary working directory. Note that this may take a long time. Any files that have been provided to target locations remain there. Note: VMSINSTAL does not delete any accounts, identifiers, or directory structures that are created. Restart the installation. (continued on next page) 5-2 Installation Procedure: Full, Upgrade and Architecture Support Table 5-1 (Cont.) Information About the Installation __________________Procedure________________________________ Question_________Answer____________________________________ How do I See Chapter 7. restart the installation?______________________________________________ 5.1 Keeping a Record of the Installation Digital recommends that you keep a record of the installation. You can do this by using either a hard copy terminal or a log file. To keep a record in a log file, enter: $ SET HOST 0/LOG=filename where filename is the name of the log file. The log file is created in the directory where you enter the command. If you do not specify a filename, the file is called SETHOST.LOG. The installation log file will be about 200 blocks. If you are running console management software, you can use this to record the installation. See your console management documentation for further information. 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 lists all the installation steps for a full or upgrade installation. There are minor differences in the display depending on whether the installation is being done on a VAX system or an AXP system. The example script in the table is for an installation on a VAX system. Depending on your distribution media, you may be prompted to change the tape or cartridge during the installation. Installation Procedure: Full, Upgrade and Architecture Support 5-3 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 Installation Procedure for Full and Upgrade __________Installations__________________________________________ Step__Action_____________________________________________________ 1 Load and mount the media that contains the software kit. If you are installing from a tape or cartridge, you will be prompted to change the tape or cartridge when required. You do not need to change the media when you are installing from a compact disc (CD). _________________________________________________________________ 2 Invoke the VMSINSTAL procedure from the SYSTEM account. Enter the following commands: $ SET DEFAULT SYS$UPDATE $ VMSINSTAL A1031 device To use an alternate working device (AWD), enter the following command lines: $ SET DEFAULT SYS$UPDATE $ VMSINSTAL A1031 device OPTIONS AWD=disk device is the device on which you have mounted the distribution media. You can use a physical or a logical device name but do not use logical device names beginning with A1$, OA$, or OA1$. A1031 is the product identifier and disk is the location of the alternate working device. _________________________________________________________________ 3 Verify your system backup. VAX/VMS Software Product Installation Procedure V5.5-2 It is 24-JAN-1994 at 17:16. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Press RETURN to continue. _________________________________________________________________ (continued on next page) 5-4 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 4 Load the distribution media (first volume). Enter the products to be processed from the first distribution volume set: * Products: A1031 * Enter installation options you wish to use (none): Please mount the first volume of the set on device * Are you ready? Enter the product identifier, A1031, at the prompt. Enter Y to confirm that the media is correctly mounted and you are ready to start. ___________________________________________________________ For installation type__________________Go_to________________________________ Full Step 5 Upgrade_______________Step_7_______________________________ _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-5 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 5 Full Installation: Enter the number for the type of installation that you want to do. The following products will be processed: A1 V3.1 Beginning installation of A1 V3.1 at 17:16 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. This is a LOCAL ALL-IN-1 V3.1 BASE kit Logical OA$IMAGE is not defined. No ALL-IN-1 image can be found using the default specification. Using the FULL ALL-IN-1 V3.1 kit, the following installation types can be performed: (1) A full installation of ALL-IN-1 V3.1 (2) Add VAX architecture support to an existing AXP ALL-IN-1 V3.1 system (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: ? Enter 1 to install a new ALL-IN-1 system. Press ? for help or refer to Chapter 1 for more information about installation options. _________________________________________________________________ (continued on next page) 5-6 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 6 Full Installation: Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks * Which action do you wish to perform [I]: Press RETURN to start the installation. Go to Step 9 to continue. _________________________________________________________________ 7 Upgrade Installation: Enter the number for the type of installation you want to perform. The following products will be processed: A1 V3.1 Beginning installation of A1 V3.1 at 17:16 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. This is a LOCAL ALL-IN-1 V3.1 BASE kit The current ALL-IN-1 image identification is ALL-IN-1 V3.0. Using the FULL ALL-IN-1 V3.1 kit, the following installation types can be performed: (1) Upgrade of ALL-IN-1 V3.0 to ALL-IN-1 V3.1 (2) Minimal Shutdown Upgrade of ALL-IN-1 V3.0 to ALL-IN-1 V3.1 (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: Enter 1 to upgrade an existing ALL-IN-1 system. Press ? for help or refer to Chapter 1 for more information about installation options. (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-7 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ _________________________________________________________________ 8 Upgrade Installation: Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks (RC) Run conflict checking and resolution tool (CART) * Which action do you wish to perform [I]: Press RETURN to continue with the installation. _________________________________________________________________ 9 Confirm that the License PAK is registered and loaded: * Does this product have an authorization key registered and loaded [YES]? Press RETURN to continue. Press ? for help or see Section 3.6. ___________________________________________________________ For installation type__________________Go_to________________________________ Full Step 11 Upgrade_______________Step_10______________________________ _________________________________________________________________ 10 Upgrade Installation: Confirm that you want to purge files. * Do you want to purge files replaced by this installation [YES]? Press RETURN to purge files. _________________________________________________________________ (continued on next page) 5-8 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 11 Indicate whether you want to integrate DATATRIEVE with ALL-IN-1. If DATATRIEVE is only occasionally used within ALL-IN-1 it is suggested that you answer NO to the next question. You will still be able to use DATATRIEVE within ALL-IN-1, but you will avoid any performance impact of having it physically linked with the ALL-IN-1 image. If you need to use a DATATRIEVE image other than SYS$SHARE:DTRSHR.EXE then you MUST answer YES to the following question. * Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]? Enter Y to integrate DATATRIEVE. Press RETURN if you do not want to integrate DATATRIEVE. Press ? for help or see Section 1.6.1. _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-9 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 12 Indicate whether you want to install WPS-PLUS with ALL-IN-1. If you do not have license which includes WPS-PLUS, you will not be asked this question. If you wish to have the WPS-PLUS editor available, answer YES to the following question. If you do not wish to install the WPS-PLUS editor, answer NO. NOTE: o If WPS-PLUS is not installed then the WPS-PLUS linguistics aids (SPELL CHECKER and THESAURUS) and the WPS-PLUS SORT and MERGE processing functionality will not be available. o You will be able to do an ALL-IN-1 update installation to add WPS-PLUS at a later time, should you choose not to install it now. * Do you want to install WPS-PLUS with ALL-IN-1 [YES]? Press RETURN to install WPS-PLUS. You are then asked if you want to install the graphics and page overlay samples: %A1-I-WPSLINK, The WPS-PLUS editor will be installed and linked with ALL-IN-1 This kit contains a library of Encapsulated PostScript(R) graphics and PostScript(R) Page Overlay samples. Their total size is approximately 3,000 blocks when they are copied to the ALL-IN-1 library directory. * Do you want these graphics copied to the ALL-IN-1 library directory [NO]? Enter Y to copy the files. _________________________________________________________________ (continued on next page) 5-10 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 13 Indicate whether you want to incorporate ACMS. If you wish to interface with ACMS, answer YES to the following questions. NOTE: o ACMS must be installed before ALL-IN-1. o If you answer YES and the relevant ACMS files are present then the interface to ACMS will be built. If the files are not present, then you may either continue the installation without linking with ACMS or abort the installation to correct the problem. * Do you want to integrate ACMS with ALL-IN-1 [NO]? Answer Y if you want to integrate ACMS. _________________________________________________________________ 14 Indicate whether to you want to build a multilanguage system. If you wish to use more than one ALL-IN-1 language, answer YES to the following question. * Do you want to build a MULTI-LANGUAGE system [YES]? Press RETURN if you will be installing additional languages and you want to build a multilanguage system. See Section 1.2.4. _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-11 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 15 Select a default date format. 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 each user through the Set Working Conditions option on the User Setup Menu. 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 7 ***** Reserved (Means system default) ***** 8 DD-MM-YYYY DD/MM/YY (Numeric format) 9 MM-DD-YYYY MM/DD/YY (Numeric format) * Which date format do you require [1]: Press RETURN to use the default format or enter the number for the date format that you want to use. See the ALL-IN-1 Installation: Language and Market Supplement for more details about date formats. _________________________________________________________________ (continued on next page) 5-12 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 16 Specify the greatest number of simultaneous ALL-IN-1 users. * What will be the greatest number of simultaneous ALL-IN-1 users: Specify the maximum number of ALL-IN-1 users that you expect at any one time. The installation procedure uses this entry to check that system parameters are large enough to support your intended number of users. _________________________________________________________________ 17 Specify a batch queue for running the job that checks the Mail Sender and Fetcher processes. * On which queue should the Sender/Fetcher check job run [SYS$BATCH]: Press RETURN to use the default queue. See Section 1.5.1. _________________________________________________________________ 18 Indicate if you want to use Message Router for remote mail. ALL-IN-1 on a VAX node can be configured to use a local Message Router which is installed on the same node or a remote Message Router which is installed on a different node. ALL-IN-1 on an AXP node can only use a remote Message Router. Answer Y if you want to use Message Router. * Do you want ALL-IN-1 to be configured to use Message Router [YES]? If you answer NO to this question, ALL-IN-1 users will only be able to exchange messages locally with other users on the same computer system. See Section 1.5. If you do not want to use Message Router, go to Step 24. _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-13 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 19 Confirm that you want to use a remote Message Router. If Message Router is not installed on this node, confirm that you want to use a remote Message Router. * Do you want to use a remote Message Router [YES]? Press RETURN to use a remote Message Router. _________________________________________________________________ 20 Enter the name of the remote Message Router node. * What node is the Message Router on: nodename Enter the name of the node, nodename on which the remote Message Router is installed. See Section 1.5 for more information about using a remote Message Router. The remote Message Router node must be in the network nodes database on the node on which you are installing ALL-IN-1. _________________________________________________________________ 21 Full Installation: Enter a password for the Message Router mailbox. * Enter a password for the Message Router mailbox: * Please confirm the password that you specified: The password must be a minimum of 8 characters and a maximum of 32 characters. Confirm the password. _________________________________________________________________ (continued on next page) 5-14 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 22 Indicate the level of Mail Directory support. * What level of Mail Directory support do you want [0/1/2] [0]: Use the following table to decide which option to choose. ___________________________________________________________ If you enter_______Then___________________________________________ 0 The ALL-IN-1 directory is the primary directory and the Mail directory is not available. 1 The ALL-IN-1 directory is the primary directory and the Mail directory is available as the secondary directory. 2 The Mail directory is the primary directory and the ALL-IN-1 directory is available as the ____________secondary_directory.___________________________ Enter 1 to use the Mail directory as the secondary directory. If you enter 0, go to Step 24. For upgrade installations go to Step 24. _________________________________________________________________ 23 Enter a password for the Mail Directory User Agent account and confirm it. The text that is displayed depends on whether you are using a remote Message Router, and whether that Message Router is in the same VMScluster. Read the informational messages carefully. * Press RETURN to continue the installation: * Enter a password for the Mail Directory user agent Account: * Please confirm the password which you specified: Press RETURN and then enter a password for the Mail Directory user agent account and confirm it. _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-15 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 24 Indicate if you want outgoing messages translated to ASCII. * Do you want to translate all outgoing messages to ASCII [NO]? Press RETURN if you do not want outgoing messages translated. Enter Y, if you want outgoing messages translated. You are then asked if you want all attachments to be translated. * Do you want to translate all message attachments [NO]? Enter Y if you want all message attachments translated. See Section 1.5.5. _________________________________________________________________ 25 System checking. The installation procedure checks mandatory and optional software prerequisites. _________________________________________________________________ (continued on next page) 5-16 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 26 Indicate if you want client applications to connect to ALL-IN-1 using TCP/IP network protocol. You are only asked the following question if DEC TCP/IP Services (UCX) or other TCP/IP network sofware that emulates UCX is installed on your system. * Do you want to use TCP/IP [YES]? Press RETURN if you want to use TCP/IP for client connections. If you do, you are asked the following questions if default service names for the AIDA Server and ALL-IN-1 File Cabinet Server are not registered in the Internet Services database. * Enter a port number for the AIDA Server [7300]: * Enter a port number for the ALL-IN- 1 File Cabinet Server [7373]: Enter a different TCP/IP port number for each server. The port numbers can be in the range 1024 to 65535. See Section 1.6.4. The installation procedure checks that the UCX$IPC_SHR.EXE image is installed. If it is not, you must install it after the installation. _________________________________________________________________ 27 System checking. The installation procedure checks system parameters, quotas and identifiers. For new installations, the ALL-IN-1 identifiers are created. The identifiers already exist for upgrade installations. _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-17 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 28 Enter the language code. * Enter language code for this installation (2 characters): US Enter the two-letter language code for your language component. In this example, US is the ENGLISH language code. See the ALL-IN-1 Installation: Language and Market Supplement supplied with your kit. _________________________________________________________________ (continued on next page) 5-18 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 29 Enter the dialect code. Your language kit may also contain one or more dialect components. Enter the dialect code that you want to use. If your language kit does not contain a dialect component, you are not asked this question. %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... If you wish to install a dialectal variation of ENGLISH language, enter the code for the dialect component you wish to use. If you do not wish to install a dialectal variation of ENGLISH language, then accept the answer of NO_DIALECT. * Enter dialect code for this installation (5 characters) [NO_DIALECT]: Press RETURN or enter the dialect code that you want to use. Press ? for more information or see the ALL-IN-1 Installation: Language and Market Supplement. The installation procedure continues with system checking. ___________________________________________________________ For installation type__________________Go_to________________________________ Full Step 30 Upgrade_______________Step_31______________________________ _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-19 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 30 Specify the devices for the ALL-IN-1 areas. * Which device will hold the ALL-IN-1 shared library files: * Which device will hold the ALL-IN- 1 shared data files [A1DISK1:]: * Which device will hold the ALL-IN- 1 ENGLISH language files [A1DISK1:]: * Which device will hold the ALL-IN- 1 mail area SDAF file [A1DISK1:]: * How many shared directories do you want to create [1]: * Which device will hold the ALL-IN- 1 shared directory SHARE1 [A1DISK1:]: * Which device will hold the ALL-IN- 1 lexicon files [A1DISK1:]: For shared directories, Digital recommends that you select the default value at installation time and then create additional shared directories after the installation, following the instructions in the ALL-IN-1 Management Guide. If lexicon files have already been installed by another product, you are not asked the question about lexicon files. _________________________________________________________________ 31 Enter the market code. * Enter market code for this installation (2 characters): US Enter the two-letter market code for the installation. See the ALL-IN-1 Installation: Language and Market Supplement. ___________________________________________________________ Installation_type_____Go_to________________________________ Full 33 Upgrade_______________39___________________________________ _________________________________________________________________ (continued on next page) 5-20 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 32 Full Installation: Specify an OpenVMS account and password for the ALL-IN-1 manager. %A1CUS-I-RECOUK, Restoring the MARKET kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... This installation creates a VMS account for the ALL-IN-1 manager. * What VMS username do you want to use for ALL-IN-1 MANAGER account [ALLIN1]: * Enter a password for the ALL-IN-1 MANAGER account: * Please confirm the password which you specified: _________________________________________________________________ 33 Full Installation: Enter a system group UIC and default device for the ALL-IN-1 manager. Do not create the ALL-IN-1 manager's account in a subdirectory of an OpenVMS system directory. * What UIC do you want to use for ALL-IN-1 MANAGER account: * What default device do you want to use for the ALL-IN 1 MANAGER'S account [A1DISK1:] _________________________________________________________________ 34 Full Installation: Enter a UIC for the accounts used by the Transfer User utility. The UIC must not be a system group UIC. * What UIC do you want to use for A1$XFER_IN account: * What UIC do you want to use for the A1$XFER_OUT account: _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-21 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 35 Full Installation: Enter a UIC for the account used by the Script Symbiont utility. The UIC must not be a system group UIC. * What UIC do you want to use for ALL-IN-1 OAFC$DEFAULT account: _________________________________________________________________ 36 Full Installation: Enter a UIC for the account used for running the ALL-IN-1 File Cabinet Server. The UIC must not be a system group UIC. * What UIC do you want to use for ALL-IN-1 OAFC$SERVER account: _________________________________________________________________ 37 Full Installation: Specify the top-level directories for the ALL-IN-1 areas. * Enter ALL-IN-1 top-level directory required for the shared library files [ALLIN1]: A1_V31 * Enter ALL-IN-1 top-level directory required for the shared data files [A1_V31]: * Enter ALL-IN-1 top-level directory required for all ENGLISH language files [A1_V31]: * Enter ALL-IN-1 top-level directory required for the mail area SDAF file [A1_V31]: * Enter the name required for the SHARED DIRECTORY on A1DISK1: [A1_V31]: Go to Step 40 to continue. _________________________________________________________________ (continued on next page) 5-22 Installation Procedure: Full, Upgrade and Architecture Support 5.2 Installation Procedure for Full and Upgrade Installations Table 5-2 (Cont.) Installation Procedure for Full and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 38 Upgrade Installation: Enter the OpenVMS username for the ALL-IN-1 manager'S account. * What is the existing VMS username for the ALL-IN-1 account [ALLIN1]: Enter the OpenVMS username for the ALL-IN-1 account. The account details are displayed. _________________________________________________________________ 39 Upgrade Installation: Confirm that the details of the ALL-IN-1 manager's account are correct. * Are all the specified account's characteristics correct [YES]? Press RETURN if all the information is correct. _________________________________________________________________ 40 Run the IVP (Installation Verification Procedure). * Do you want to run the IVP after the installation [YES]? ______Press_RETURN_to_run_the_IVP._______________________________ All the installation questions have now been completed. If you are installing ALL-IN-1 Version 3.1 on two architectures, see Section 5.3 for instructions on adding architecture support for a second architecture. If you are not installing on two architectures, go to Section 5.4. 5.3 Adding Architecture Support Table 5-3 explains when you can do an installation to add architecture support. Installation Procedure: Full, Upgrade and Architecture Support 5-23 5.3 Adding Architecture Support Table_5-3_When_to_Install_VAX_or_AXP_Architecture_Support__ Install_______________When_you_have_already_done___________ VAX architecture A full ALL-IN-1 Version 3.1 support installation on an AXP system in the same VMScluster AXP architecture A full or upgrade ALL-IN-1 Version support 3.1 installation on a VAX system in ______________________the_same_VMScluster._________________ The installation procedure in Table 5-4 shows the addition of AXP architecture support. ALL-IN-1 Version 3.1 is already installed on a VAX system in the same VMScluster. The questions that you are asked during the additional architecture installation depend on the responses that you gave during the full or upgrade installation. For example, if you did not install WPS-PLUS during the full or upgrade installation, you are not asked any additional questions about WPS-PLUS. 5.3.1 Before You Start Before you start the installation, you must do the following: o Make a note of the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT, on the VAX system. You will be asked for this information during the installation. o Run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP, to check for logicals containing SYS$SYSDEVICE. From the ALL-IN-1 manager's account on the node where ALL-IN-1 is already installed, run the script, OA$LIB:SM_ CHECK_SYS$SYSDEVICE.SCP, on the node where you have already installed ALL-IN-1: $ SET HOST 0/LOG=filename $ ALLIN1/NOINIT CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP 5-24 Installation Procedure: Full, Upgrade and Architecture Support 5.3 Adding Architecture Support If references to SYS$DEVICE are found, a warning message is displayed. You must remove the references as they will refer to different devices on a VAX system and an AXP system. If the references are not corrected, data may be lost on your system. 5.3.2 Installation Procedure for Adding Architecture Support In the example script shown in Table 5-4, the following configuration applies: o ALL-IN-1 Version 3.1 is already installed on a VAX machine in the same VMScluster. o WPS-PLUS is installed on the VAX machine. o ALL-IN-1 has been configured as a multilanguage system. o Message Router is installed on the VAX system. Table_5-4_Installation_Procedure_for_Adding_Architecture_Support_ Step____Action___________________________________________________ 1 to 4 Follow Steps 1 to 4 in Table 5-2. _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-25 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 5 Enter the number for the type of installation you want to perform. The following products will be processed: A1 V3.1 Beginning installation of A1 V3.1 at 19:59 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. This is a LOCAL ALL-IN-1 V3.1 BASE kit No ALL-IN-1 image can be found using the default specification. Using the FULL ALL-IN-1 V3.1 kit, the following installation types can be performed: (1) A full installation of ALL-IN-1 V3.1 (2) Add AXP architecture support to an existing VAX ALL-IN-1 V3.1 system (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: 2 Enter 2 to add AXP architecture support. _________________________________________________________________ 6 Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks * Which action do you wish to perform [I]: Press RETURN to start the installation. _________________________________________________________________ (continued on next page) 5-26 Installation Procedure: Full, Upgrade and Architecture Support 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 7 Supply the location of OA$DATA_SHARE:A1CONFIG.DAT, the ALL-IN-1 configuration file, for ALL-IN-1 Version 3.1 on the VAX system. You have chosen an architecture only installation. To continue you must specify the location of the existing ALL-IN-1 system's configuration file (A1CONFIG.DAT). The installation will read A1CONFIG.DAT to determine file target locations. * Please give the directory location of A1CONFIG.DAT: disk:[directory] Enter the location of the ALL-IN-1 configuration file in the format, disk:[directory]. You must always use this format to specify the location of this file. The installation script uses the configuration file to define logicals. %A1-I-DEFLOG, Running A1V31START.COM to define the logicals -A1-I-DEFLOG, for your existing ALL-IN-1 V3.1 VAX system. Defining language independent logical names Defining ENGLISH language logical names _________________________________________________________________ 8 Confirm that the License PAK is registered and loaded: * Does this product have an authorization key registered and loaded [YES]? Press RETURN to continue. _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-27 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 9 Indicate if you want to purge files. * Do you want to purge files replaced by this installation [YES]? Press RETURN to purge files. Where possible, the AXP architecture-only installation matches the configuration of ALL-IN-1 that is already installed on the VAX system. The informational messages that are displayed will depend on the existing configuration. _________________________________________________________________ 10 Indicate whether you want to integrate DATATRIEVE with ALL-IN-1. If DATATRIEVE is only occasionally used within ALL-IN-1 it is suggested that you answer NO to the next question. You will still be able to use DATATRIEVE within ALL-IN-1, but you will avoid any performance impact of having it physically linked with the ALL-IN-1 image. If you need to use a DATATRIEVE image other than SYS$SHARE:DTRSHR.EXE then you MUST answer YES to the following question. * Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]? Enter Y to integrate DATATRIEVE. Press RETURN if you do not want to integrate DATATRIEVE. Press ? for help or see Section 1.6.1. _________________________________________________________________ (continued on next page) 5-28 Installation Procedure: Full, Upgrade and Architecture Support 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 11 System checking for existing ALL-IN-1 configuration. The informational message depends on your existing configuration, for example: During your ALL-IN-1 installation on VAX you chose to install ALL-IN-1 with WPS-PLUS, therefore WPS-PLUS will also be installed during this AXP architecture only installation. _________________________________________________________________ 12 Indicate whether you want to incorporate ACMS. If you wish to interface with ACMS, answer YES to the following questions. If you wish to interface with ACMS, answer YES to the following questions. NOTE: o ACMS must be installed before ALL-IN-1. o If you answer YES and the relevant ACMS files are present then the interface to ACMS will be built. If the files are not present, then you may either continue the installation without linking with ACMS, or abort the installation to correct the problem. * Do you want to integrate ACMS with ALL-IN-1 [NO]? Press RETURN if you do not want to integrate ACMS. _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-29 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 13 System checking for existing ALL-IN-1 configuration. The informational message depends on your existing configuration, for example: ALL-IN-1 on the VAX is linked as a MULT-LANGUAGE system, therefore ALL-IN-1 on this AXP will also be linked as a MULTI-LANGUAGE system. _________________________________________________________________ 14 Specify the greatest number of simultaneous ALL-IN-1 users. * What will be the greatest number of simultaneous ALL-IN-1 users: Specify the maximum number of ALL-IN-1 users that you expect at any one time. The installation procedure uses this entry to check that system parameters are large enough to support your intended number of users. _________________________________________________________________ (continued on next page) 5-30 Installation Procedure: Full, Upgrade and Architecture Support 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 15 Message Router Checks. This part of the installation procedure is determined by the answers that you gave during the full installation on the VAX system. In this example script, the VAX system was configured to use a local Message Router on the VAX node on which you have already installed ALL-IN-1. The level of Mail directory support set up for the VAX system is also used. %A1-I-MRCHK, Performing Message Router checks... %A1-I-REMMR, Your ALL-IN-1 system running on the VAX is configured -A1-I-REMMR, to use a local Message Router on that node %A1-I-LOCMR, Therefore this AXP ALL-IN-1 system will be configured -A1-I-LOCMR, to use a remote Message Router %A1-I-DDSSUP, Your VAX ALL-IN-1 system is configured to use the -A1-I-DDSSUP, Mail Directory Service (DDS). This AXP architecture only -A1-I-DDSSUP, installation will use the same level (1) of DDS support . . . _________________________________________________________________ (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-31 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 16 Indicate if you want client applications to connect to ALL-IN-1 using TCP/IP network protocol. You are only asked the following question if DEC TCP /IP Services (UCX) or other TCP/IP network sofware that emulates UCX is installed on your system. * Do you want to use TCP/IP [YES]? Press RETURN if you want to use TCP/IP for client connections. If you do, you are asked the following questions if default service names for the AIDA Server and ALL-IN-1 File Cabinet Server are not registered in the Internet Services database. * Enter a port number for the AIDA Server [7300]: * Enter a port number for the ALL-IN- 1 File Cabinet Server [7373]: Enter a different TCP/IP port number for each server. The port numbers can be in the range 1024 to 65535. See Section 1.6.4. The installation procedure checks that the UCX$IPC_SHR.EXE image is installed. If it is not, you must install it after the installation. _________________________________________________________________ 17 System checking. The installation procedure checks system parameters, quotas and identifiers. _________________________________________________________________ 18 Enter the language code. * Enter language code for this installation (2 characters): US Enter the two-letter language code for your language component. See the ALL-IN-1 Installation: Language and Market Supplement supplied with your kit. _________________________________________________________________ (continued on next page) 5-32 Installation Procedure: Full, Upgrade and Architecture Support 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 19 Enter the dialect code. Your language kit may also contain one or more dialect components. Enter the dialect code that you want to use. %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... If you wish to install a dialectal variation of ENGLISH language, enter the code for the dialect component you wish to use. If you do not wish to install a dialectal variation of ENGLISH language, then accept the answer of NO_DIALECT. * Enter dialect code for this installation (5 characters) [NO_DIALECT]: _________________________________________________________________ 20 Enter the market code. * Enter market code for this installation (2 characters): US Enter the two-letter market code for the installation. See the ALL-IN-1 Installation: Language and Market Supplement. _________________________________________________________________ 21 Enter the name of the OpenVMS account for the ALL-IN-1 manager. * What is the existing VMS username for the ALL-IN-1 account [ALLIN1]: The account details are displayed. _________________________________________________________________ 22 Confirm that the details of the account are correct. * Are all the specified account's characteristics correct [YES]? Press RETURN if the details are correct. (continued on next page) Installation Procedure: Full, Upgrade and Architecture Support 5-33 5.3 Adding Architecture Support Table 5-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ _________________________________________________________________ 23 Run the IVP (Installation Verification Procedure). * Do you want to run the IVP after the installation [YES]? ______Press_RETURN_to_run_the_IVP._______________________________ All the installation questions have now been completed. 5.4 Automatic Postinstallation Tasks The installation procedure performs automatic postinstallation tasks, for example, converting data files. If a problem occurs during the postinstallation phase, see Chapter 7. The following tasks are done automatically: o Deassigns old ALL-IN-1 logicals and logicals created during the installation o Runs the ALL-IN-1 startup procedure, A1V31START.COM o Compiles, installs and sets protections on the following form libraries and their site versions: o OAFORM o MEMRES o OAN$FORMS o Installs message symbol files o Compiles TXLs o For upgrade installations, the following data files are upgraded: o PROFILE.DAT o SM_ACCOUNT_TYPES.DAT o SM_POLICIES.DAT 5-34 Installation Procedure: Full, Upgrade and Architecture Support 5.4 Automatic Postinstallation Tasks o OAFC_SERVER_MASTER.DAT (this will already be upgraded if you have installed the TeamLinks Connection Package) o FORMAT.DAT 5.5 Manual Postinstallation Tasks There are some manual tasks that you must complete after the installation. See Chapter 8. Installation Procedure: Full, Upgrade and Architecture Support 5-35 6 _________________________________________________________________ Installation Procedure: Additional Languages This chapter describes the installation of an additional language on an ALL-IN-1 Version 3.1 system that is configured as a multilanguage system. __________________ Before You Start __________________ Do not start the installation until you have completed the system preparation tasks in Chapter 3. ______________________________________________________ During the installation procedure a number of cautions and general informational messages are displayed. Read all the displayed messages carefully. 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 (?) for Help. ________________________ Note ________________________ If the installation fails, you must restart the installation from the beginning. To stop the installation at any point, press CTRL/Y. ______________________________________________________ If you are installing a new additional language or upgrading an existing additional language, see Section 6.2 If you are installing architecture support for an additional language, see Section 6.3. Installation Procedure: Additional Languages 6-1 6.1 Keeping a Record of the Installation 6.1 Keeping a Record of the Installation Digital recommends that you keep a record of the installation. You can do this by using either a hard copy terminal or a log file. To keep a record in a log file, enter: $ SET HOST 0/LOG=filename where filename is the name of the log file. The log file is created in the directory where you enter the command. If you do not specify a filename, the file is called SETHOST.LOG. To use the SET HOST command, you must have DECnet[TM] running on your system. The installation log file will be about 200 blocks. If you have a VAXcluster system, and you are running console management software, you can use this to record the installation. See your console management documentation for further information. 6.2 Installation Procedure for Additional Language Installations Follow the steps in Table 6-1 to install a new additional language or upgrade an existing additional language. There are minor differences in the display depending on whether the installation is being run on a VAX or AXP system. The example script shows the addition of BRITISH as an additional language on an ALL-IN-1 Version 3.1 AXP system that is configured as a multilanguage system. Depending on your distribution media, you may be prompted to change the tape or cartridge during the installation. 6-2 Installation Procedure: Additional Languages 6.2 Installation Procedure for Additional Language Installations Table_6-1_Installation_Procedure_for_An_Additional_Language______ Step__Action_____________________________________________________ 1 Load and mount the media that contains the language software kit. _________________________________________________________________ 2 Invoke the VMSINSTAL procedure from the SYSTEM account. Enter the following commands: $ SET DEFAULT SYS$UPDATE $ VMSINSTAL A1031 device To use an alternate working device (AWD), enter the following command lines: $ SET DEFAULT SYS$UPDATE $ VMSINSTAL A1LUS031 device OPTIONS AWD=disk device is the device on which you have mounted the distribution media. You can use a physical or a logical device name but do not use logical device names beginning with A1$, OA$, or OA1$. A1LUS031 is the product identifier and disk is the location of the alternate working device. _________________________________________________________________ 3 Verify your system backup. OpenVMS AXP Software Product Installation Procedure V6.1 It is 21-MAR-1994 at 21:27. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Press RETURN to continue. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 6-3 6.2 Installation Procedure for Additional Language Installations Table 6-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 4 Load the distribution media. Enter the product identifier, A1LUS031, at the prompt and then enter Y to confirm that the media is correctly mounted and you are ready to start. Enter the products to be processed from the first distribution volume set: * Products: A1LUS031 * Enter installation options you wish to use (none): Please mount the first volume of the set on device * Are you ready? Y _________________________________________________________________ (continued on next page) 6-4 Installation Procedure: Additional Languages 6.2 Installation Procedure for Additional Language Installations Table 6-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 5 Enter the number for the type of installation you want to do. The following products will be processed: A1 V3.1 Beginning installation of A1 V3.1 at 21:27 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. This is a LOCAL ALL-IN-1 V3.1 LANGUAGE kit The current ALL-IN-1 image identification is ALL-IN-1 V3.1. Using the LANGUAGE-only ALL-IN-1 V3.1 kit, the following installation types can be performed: (1) Installation of an additional ALL-IN-1 V3.1 language (2) Upgrade of an existing ALL-IN-1 V3.0 additional language (3) Update of an existing ALL-IN-1 V3.1 additional language (4) Add or Update AXP architecture specific components of an existing ALL-IN-1 V3.1 additional language (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: 1 Enter 1 to install a new additional ALL-IN-1 Version 3.1 language. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 6-5 6.2 Installation Procedure for Additional Language Installations Table 6-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 6 Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks * Which action do you wish to perform [I]: Press RETURN to start the installation. _________________________________________________________________ 7 Supply information about optional software as appropriate. During your first language installation you chose to install ALL-IN-1 without DATATRIEVE, therefore this tool will NOT be available from your ALL-IN-1 additional language. During your first language installation you chose to integrate WPS-PLUS, therefore you be be able to use WPS-PLUS as an additional editor from your ALL-IN-1 additional language. This kit contains a library of Encapsulated PostScript(R) graphics and PostScript(R) Page Overlay samples specific to the language component. * Do you want these graphics copied to the ALL-IN-1 library directory [NO]? Enter Y to copy the WPS-PLUS graphics library to the ALL-IN-1 directory. _________________________________________________________________ (continued on next page) 6-6 Installation Procedure: Additional Languages 6.2 Installation Procedure for Additional Language Installations Table 6-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 8 Configuration Checking. The message that you see depends on your primary language configuration, for example: During your first language installation you chose to install ALL-IN-1 without ACMS, therefore this tool will NOT be available from your ALL-IN-1 additional language. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 6-7 6.2 Installation Procedure for Additional Language Installations Table 6-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 9 Select a default date format. 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 each user through the Set Working Conditions option on the User Setup Menu. 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 7 ***** Reserved (Means system default) ***** 8 DD-MM-YYYY DD/MM/YY (Numeric format) 9 MM-DD-YYYY MM/DD/YY (Numeric format) * Which date format do you require [1]: Press RETURN to use the default format or enter the number for the date format that you want to use. See the ALL-IN-1 Installation: Language and Market Supplement for more details about date formats. The installation procedure now does system checks. _________________________________________________________________ 10 Enter the language code. * Enter language code for this installation (2 characters): US Enter the two-letter language code for your language component. See the ALL-IN-1 Installation: Language and Market Supplement supplied with your kit. (continued on next page) 6-8 Installation Procedure: Additional Languages 6.2 Installation Procedure for Additional Language Installations Table 6-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ _________________________________________________________________ 11 Enter the dialect code. %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... If you wish to install a dialectal variation of ENGLISH language, enter the code for the dialect component you wish to use. If you do not wish to install a dialectal variation of ENGLISH language, then accept the answer of NO_DIALECT. * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GB Enter the dialect code that you want to use. In this example, US_GB is the BRITISH dialect component. See the ALL-IN-1 Installation: Language and Market Supplement. _________________________________________________________________ 12 Confirm that the License PAK is registered and loaded. * Does this product have an authorization key registered and loaded [YES]? Press RETURN to continue. _________________________________________________________________ 13 Specify the device for the additional language files. * Which device will hold the ALL-IN-1 BRITISH language files: Enter the device name. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 6-9 6.2 Installation Procedure for Additional Language Installations Table 6-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 14 Enter the OpenVMS username for the ALL-IN-1 manager's account. * What is the existing VMS username for the ALL-IN-1 account [ALLIN1]: The details of the account are displayed. _________________________________________________________________ 15 Confirm that the account details are correct. * Are all the specified account's characteristics correct [YES]? Press RETURN to confirm that the account details are correct. _________________________________________________________________ 16 Specify the top-level directory for the ALL-IN-1 additional language files. * Enter ALL-IN-1 top-level directory required for all BRITISH language files [BRITISH]: _________________________________________________________________ 17 Run the IVP (Installation Verification Procedure). * Do you want to run the IVP after the installation [YES]? ______Press_RETURN_to_run_the_IVP._______________________________ All the installation questions have now been completed. The installation procedure does automatic postinstallation tasks. If a problem occurs during the postinstallation phase, see Chapter 7. For manual postinstallation tasks, see Chapter 8. If you are installing on a VMScluster and want to add additional architecture support for the additional language that you have installed, see Section 6.3. 6-10 Installation Procedure: Additional Languages 6.3 Installing Architecture Support for an Additional Language 6.3 Installing Architecture Support for an Additional Language Before you start the installation, you must do the following: o Make a note of the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT, on the VAX system. You will be asked for this information during the installation. o Run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP, to check for logicals containing SYS$SYSDEVICE. From the ALL-IN-1 manager's account on the node where you have already installed ALL-IN-1, run the script, OA$LIB:SM_ CHECK_SYS$SYSDEVICE.SCP: $ SET HOST 0/LOG=filename $ ALLIN1/NOINIT CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP If references to SYS$DEVICE are found, a warning message is displayed. You must remove the references as they will refer to different devices on a VAX system and an AXP system. If the references are not corrected, data may be lost on your system. Follow the steps in Table 6-2 to add architecture support for an additional language that you have already installed on a different architecture in the same VMScluster. The example script shows the addition of VAX architecture support for ALL-IN-1 BRITISH as an additional language. BRITISH is already installed as an additional language on an AXP system in the same VMScluster. Table 6-2 Installation Procedure for Addition of Architecture __________Support_for_an_Additional_Language_____________________ Step__Action_____________________________________________________ 1 to Follow Steps 1 to 4 in Table 6-1. 4 _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 6-11 6.3 Installing Architecture Support for an Additional Language Table 6-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 5 Enter the number for the type of installation you want to do. Using the LANGUAGE-only ALL-IN-1 V3.1 kit, the following installation types can be performed: (1) Installation of an additional ALL-IN-1 V3.1 language (2) Upgrade of an existing ALL-IN-1 V3.0 additional language (3) Update of an existing ALL-IN-1 V3.1 additional language (4) Add or Update VAX architecture specific components of an existing ALL-IN-1 V3.1 additional language (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: 4 Enter 4 to add VAX architecture support for an existing ALL-IN-1 Version 3.1 additional language. _________________________________________________________________ 6 Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks * Which action do you wish to perform [I]: Press RETURN to start the installation. _________________________________________________________________ (continued on next page) 6-12 Installation Procedure: Additional Languages 6.3 Installing Architecture Support for an Additional Language Table 6-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 7 Enter the location of OA$DATA_SHARE:A1CONFIG.DAT, the ALL-IN-1 configuration file, for the existing ALL-IN-1 Version 3.1 system. You have chosen an architecture only installation. To continue you must specify the location of the existing ALL-IN-1 system's configuration file (A1CONFIG.DAT). The installation will read A1CONFIG.DAT to determine file target locations. * Please give the directory location of A1CONFIG.DAT [OA$DATA_SHARE]: Enter the location of A1CONFIG.DAT in the format disk:[directory]. You must always specify the location of the configuration file in this format. %A1-I-DEFLOG, Running A1V31START.COM to define the logicals -A1-I-DEFLOG, for your existing ALL-IN-1 V3.1 AXP system. . . . _________________________________________________________________ 8 Indicate whether you want to purge files. * Do you want to purge files replaced by this installation [YES]? Press RETURN to purge files. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 6-13 6.3 Installing Architecture Support for an Additional Language Table 6-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 9 Configuration checking. You may be asked questions depending on the configuration of ALL-IN-1 on the AXP system. This VAX architecture only installation will where possible match the configuration of ALL-IN-1 already installed on the AXP system. During your first language installation you chose to install ALL-IN-1 without DATATRIEVE, therefore this tool will NOT be available from your ALL-IN-1 additional language. During your ALL-IN-1 installation on AXP you chose to install ALL-IN-1 with WPS-PLUS, therefore WPS-PLUS will also be installed during this VAX architecture only installation. During your first language installation you chose to install ALL-IN-1 without ACMS, therefore this tool will NOT be available from your ALL-IN-1 additional language. _________________________________________________________________ (continued on next page) 6-14 Installation Procedure: Additional Languages 6.3 Installing Architecture Support for an Additional Language Table 6-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 10 Select a default date format. 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 each user through the Set Working Conditions option on the User Setup Menu. 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 7 ***** Reserved (Means system default) ***** 8 DD-MM-YYYY DD/MM/YY (Numeric format) 9 MM-DD-YYYY MM/DD/YY (Numeric format) * Which date format do you require [1]: _________________________________________________________________ 11 Enter the language code. * Enter language code for this installation (2 characters): US Enter the 2-letter language code for your additional language. See the ALL-IN-1 Installation: Language and Market Supplement. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 6-15 6.3 Installing Architecture Support for an Additional Language Table 6-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 12 Enter the dialect code. %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... If you wish to install a dialectal variation of ENGLISH language, enter the code for the dialect component you wish to use. If you do not wish to install a dialectal variation of ENGLISH language, then accept the answer of NO_DIALECT. * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GB In this example, US_GB is the BRITISH dialect code. _________________________________________________________________ 13 Confirm that the License PAK is registered and loaded. * Does this product have an authorization key registered and loaded [YES]? Press RETURN to continue. _________________________________________________________________ 14 Enter the name of the OpenVMS username of the ALL-IN-1 manager's account. * What is the existing VMS username for the ALL-IN-1 account [ALLIN1]: The account details are displayed. _________________________________________________________________ 15 Confirm that the account details are correct. * Are all the specified account's characteristics correct [YES]? Press RETURN if the account information is correct. _________________________________________________________________ (continued on next page) 6-16 Installation Procedure: Additional Languages 6.3 Installing Architecture Support for an Additional Language Table 6-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 16 Run the IVP (Installation Verification Procedure). * Do you want to run the IVP after the installation [YES]? ______Press_RETURN_to_run_the_IVP._______________________________ All the installation questions have now been completed. The installation procedure will do postinstallation tasks. For manual postinstallation tasks, see Chapter 8. Installation Procedure: Additional Languages 6-17 7 _________________________________________________________________ Installation Errors and Failure This chapter deals with various error messages you may see while installing ALL-IN-1 Version 3.1 or while the Installation Verification Procedures (IVPs) are running, and explains what to do if the installation or the IVPs fail. While the installation is running it displays various informational messages. It may also display warning or error messages. Read all the messages displayed, and take whatever action they advise. 7.1 Common Error Message That Does Not Require Action The following error message may be ignored if it is displayed during the installation: %DELETE-W-SEARCHFAIL This error occurs randomly. A file is always specified in the error message, but the file has been correctly provided. 7.2 Common Errors Which Require Action Errors can occur during the installation if any of the following conditions exist: o There is a problem with the operating system. o There is a problem with prerequisite software. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The OpenVMS help library is currently in use. Installation Errors and Failure 7-1 7.2 Common Errors Which Require Action o SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB are not present. These files are removed if you tailor OpenVMS. For descriptions of the error messages generated by these conditions, see the OpenVMS books on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. 7.3 Failure During Postinstallation ________________________ Note ________________________ When the installation procedure reaches the postinstallation phase, the main installation has completed. If the postinstallation tasks fail, a message is displayed indicating that the installation has failed and that you need to reinstall ALL-IN-1. It is not necessary to do this; you need only rerun A1$POSTINSTALL.COM as described in this section. ______________________________________________________ The procedure used to execute the automatic postinstallation tasks is written during the installation. Its content depends on the installation type, and conditions specific to your system. The command file is called A1$POSTINSTALL.COM, and it is provided to OA$LIB_ language. If any postinstallation tasks fail, messages to aid investigation are displayed. If the installation has failed during the postinstallation phase, you can do one of the following: o Rerun A1$POSTINSTALL.COM. o Edit A1$POSTINSTALL.COM to create your own command procedure using only the commands for the tasks that have failed. When the installation has completed, there are still some manual postinstallation tasks to be performed. See Chapter 8. 7-2 Installation Errors and Failure 7.3 Failure During Postinstallation After the automatic postinstallation tasks have completed, the installation procedure displays: Installation of A1 V3.1 completed at Enter EXIT, or press CTRL/Z to exit from VMSINSTAL. Note that the installation procedure 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, you must log out and log in again. 7.4 Installation Failure If the installation fails before the postinstallation phase, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of ALL-IN-1 V3.1 has failed. ________________________ Note ________________________ If the installation fails, you must restart the installation from the beginning. ______________________________________________________ 7.4.1 Failure of Upgrade Installations in Safety Mode If your installation is being performed in Safety mode, you need take no further action if the failure happens before the message: Files will now be moved to target directories If the installation fails after this message, restore your original system from a backup. You can then go back to using the original system, or you can start the installation again. 7.4.2 Failure of Upgrade Installations in Non-Safety Mode If your installation is being performed in Non-safety mode, restore your original system from a backup. You can then go back to using the original system, or you can start the installation again. Installation Errors and Failure 7-3 7.4 Installation Failure 7.4.3 Full Installations If a full installation fails, delete all accounts, identifiers and directories that have been created, and start the installation again. 7.4.4 Failure Due to Insufficient Dynamic Memory An installation on an AXP system may fail with the following error message: %SYSTEM-F-INSFMEM, insufficient dynamic memory If this error occurs, you must check that the value for CTLPAGES is high enough. If you used the default value of 100, you must increase it to 200 and restart the installation. See Section 3.8.2. 7.5 Error Messages when Running the IVP The following informational and error messages are displayed when the IVP is run: %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found %OA-E-BADLIB, Error occurred while precompiling THIS_IS_A.TEST form library) You can ignore these messages as they are part of tests that are performed by the IVP. If any other error messages occur during the IVP, do the following: 1. Check the log of the installation for any errors that may have occurred during installation. 2. Check the file ALLIN1_IVP.LOG. This file does not contain the results of the IVP, but the results of invoking ALL-IN-1 when running the IVP. This file is in the directory where you run the installation. 3. Check for any errors in the following procedures. o During the execution of the startup file, SYS$STARTUP:A1V31START.COM: Creating logical names 7-4 Installation Errors and Failure 7.5 Error Messages when Running the IVP o Automatic postinstallation procedures Installing image files Compiling and installing form libraries 4. Make sure that the ALL-IN-1 TXL is compiled and installed successfully, and recompile it if you received any error messages when the postinstallation command file was run. 5. Check that you have not run out of quota on the disk(s) containing the OA$SHAREnnnn directories (refer to the manual describing OpenVMS utilities). 6. Check that the details for the IVP account are completed correctly, as follows: o All the ALL-IN-1 privileges are set to YES. o The IVP user directory points to the disk and subdirectory that you specified for the ALL-IN-1 manager's account. For example: a1device:[ALLIN1.IVPUSER] where a1device is the device that you specified during the installation. o The ALL-IN-1 account, IVP, is accessed from the ALL-IN-1 manager's OpenVMS account. 7. Run ALL-IN-1 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. ________________________ Note ________________________ The IVP runs in the language context of the current optional language being installed and also tests the international base system. Most IVPs are designed to exercise and test ALL- IN-1 at a level which is normally customization- independent. However, if you have customized the Phone Directory subsystem of ALL-IN-1, the display graphics Installation Errors and Failure 7-5 7.5 Error Messages when Running the IVP (IDG) procedure may fail. This is a demonstration test used to exercise the terminal graphics as a typical application. ______________________________________________________ 7.6 IVP Failure If the IVP fails, the following messages are displayed: The A1 V3.1 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for A1 V3.1 has failed. 7-6 Installation Errors and Failure 8 _________________________________________________________________ Postinstallation Tasks This chapter describes the tasks that you must do to complete the setup of ALL-IN-1. Some of these tasks are optional, or only apply to particular types of systems, or configurations. There are a number of additional setup tasks that the ALL-IN-1 manager must do to set up the users' working environment before ALL-IN-1 is used. These tasks are explained in detail in the ALL-IN-1 Management Guide. 8.1 Checklist of Manual Postinstallation Tasks Table 8-1 lists the manual postinstallation tasks. Table_8-1_Postinstallation_Tasks___________________________ Type of Task__________________Installation_____Information_________ Start ALL-IN-1 Full, upgrade See Section 8.2 on all nodes in or additional a VMScluster system architecture ___________________________________________________________ Create or modify Full or upgrade Section 8.3 the ALL-IN-1 site- specific startup procedure ___________________________________________________________ (continued on next page) Postinstallation Tasks 8-1 8.1 Checklist of Manual Postinstallation Tasks Table_8-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ Modify the OpenVMS Full, upgrade Section 8.4 site-specific or additional startup procedure architecture ___________________________________________________________ Replace the Full, upgrade Section 8.5 DCLTABLES on or additional VMScluster systems architecture ___________________________________________________________ Delete files that Upgrade Section 8.6 are no longer required ___________________________________________________________ Install any missing Full, upgrade Section 8.7 images or additional architecture ___________________________________________________________ Recompile form Upgrade See Section 8.8. libraries, including This section also application or lists form libraries site-specific form that are compiled libraries automatically after the installation. ___________________________________________________________ (continued on next page) 8-2 Postinstallation Tasks 8.1 Checklist of Manual Postinstallation Tasks Table_8-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ Migrate your Upgrade of Section 8.10 customizations: a customized o Run the CART system resolution procedure o Restore customizations to modified data files o Replace customized help files o Delete obsolete files ___________________________________________________________ Rename SITELINK30 Upgrade Section 8.9 using Customization Management ___________________________________________________________ Link ALL-IN-1 to Upgrades of Section 8.11 include code-level code-level customizations customized systems and additional architecture if also installed ___________________________________________________________ Check entries in the Upgrade Section 8.12 file, RIGHTSLIST.DAT (continued on next page) Postinstallation Tasks 8-3 8.1 Checklist of Manual Postinstallation Tasks Table_8-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ ___________________________________________________________ Set up remote mail Full, upgrade Section 8.13. and additional Table 8-3 gives a architecture list of tasks and Note that where they should be local mail done. is already set up after the installation. ___________________________________________________________ Restore Sender Upgrade Section 8.14 /Fetcher setup installations if you have customized OAMTISEND.COM or OAMTIMAIL.COM ___________________________________________________________ Delete or move old Upgrade Section 8.15 versions of the mail log files ___________________________________________________________ Convert WPS-PLUS for Migrating users Section 8.16 VMS files from WPS-PLUS for VMS to ALL-IN-1 ___________________________________________________________ (continued on next page) 8-4 Postinstallation Tasks 8.1 Checklist of Manual Postinstallation Tasks Table_8-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ Add WPS-PLUS login Full or upgrade Section 8.17. command procedure installations to the system login if you are command procedure using WPS-PLUS as the default editor ___________________________________________________________ Install the File Full or Upgrade Section 8.18 Cabinet Server distributed license, if required. ___________________________________________________________ Move the CDA DOC_ If CDA$LIBRARY Section 8.19 STYLE files to a does not exist suitable location, on your system. if necessary ___________________________________________________________ Update the Facility If DECtrace Section 8.20 Definition for is already DECtrace installed and you want to use it ___________________________________________________________ Set up the user Full and See the ALL-IN-1 environment Upgrade Management Guide An online file listing all of the user changes in ALL-IN-1 Version 3.1 is provided in OA$LIB_LLV:USER_CHANGES.TXT. ___________________________________________________________ (continued on next page) Postinstallation Tasks 8-5 8.1 Checklist of Manual Postinstallation Tasks Table_8-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ Tune the File Full or Upgrade Chapter 10 in the Cabinet Servers ALL-IN-1 Management Guide ___________________________________________________________ Decide how many mail Full or upgrade See Chapter 4 in Fetcher processes to the ALL-IN-1 Mail run____________________________________Management_Guide____ 8.2 Start ALL-IN-1 on all Nodes in a VMScluster System The ALL-IN-1 startup procedure, SYS$STARTUP:A1V31START.COM, is supplied with ALL-IN-1 and is executed automatically on the node used for the installation, once the installation has completed successfully. If you are running ALL-IN-1 on a VMScluster you must also run SYS$STARTUP:A1V31START.COM on each node in the cluster in order to start ALL-IN-1. If you run A1V31START.COM manually from the DCL prompt, you must include the location of the ALL-IN-1 configuration file, OA$DATA_ SHARE:A1CONFIG.DAT. OpenVMS prompts you for the location of this file if you do not specify it on the command line. If you are creating new shared directories from within ALL-IN-1, you must define new system logical names on each node in the cluster. For further information about running ALL-IN-1 on a VMScluster, see Chapter 5 in the ALL-IN-1 Management Guide. 8.3 Create or Modify the Site-specific ALL-IN-1 Startup Procedure To modify the ALL-IN-1 startup command procedure, you must create a site-specific command procedure. The site-specific startup command procedure will be automatically executed by the ALL-IN-1 startup command procedure when it is executed. 8-6 Postinstallation Tasks 8.3 Create or Modify the Site-specific ALL-IN-1 Startup Procedure You can create the following types of site-specific command procedures: o A language-independent, startup command procedure called A1V31_SITE_START.COM. Create this startup procedure in OA$SITE_BUILD_SHARE_IND. o A language-specific startup command procedure, OA$SITE_ language_START.COM, for each language installed in a multilanguage ALL-IN-1 system. Create this startup procedure in OA$SITE_BUILD_LLV_IND. device:[directory.SITE.SOURCES_language]) where: device is the device containing the language files, and directory is the name of the top-level directory of your ALL-IN-1 Version 3.1 system. You can specify the directory for your default language by using the logical name OA$SITE_BUILD_LLV_IND. If you are upgrading and you have a site-specific startup command procedure that you want to keep, rename it from A1V30_SITE_START.COM to A1V31_SITE_START.COM. 8.4 Edit the Site-specific Startup Procedure Table 8-2 describes how to edit the OpenVMS site-specific startup file to include the ALL-IN-1 startup procedure. This ensures that the ALL-IN-1 environment is reestablished following a shutdown. When you run A1V31START.COM from the DCL prompt, you must include the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT. OpenVMS prompts you for the location of this file if you do not specify it on the command line. When you include the ALL-IN-1 startup procedure in the OpenVMS site startup procedure, you must specify the location of the A1CONFIG.DAT file: $ @SYS$STARTUP:A1V31START.COM location where location is the location of A1CONFIG.DAT, which is specified as: device:[directory.DATA_SHARE] Postinstallation Tasks 8-7 8.4 Edit the Site-specific Startup Procedure device is the device that you specified for the ALL-IN-1 data files and directory is the top-level directory that you specified for the ALL-IN-1 data files. To find the location of OA$DATA_SHARE:A1CONFIG.DAT, refer to your installation log. ________________________ Note ________________________ If you use DEC Notes with ALL-IN-1, edit your site startup file so that DEC Notes is started before ALL-IN-1 is started. ______________________________________________________ Table_8-2_Editing_the_OpenVMS_Site-specific_Startup_File___ Installation Type_____________Do_the_Following__________________________ Full To edit the file: 1. Find the lines: $ @SYS$MANAGER:STARTNET.COM and $ @SYS$MANAGER:MB$CONTROL START=(DDS,TS,...,ER)1 2. After these lines, add the following line: $ @SYS$STARTUP:A1V31START.COM location2 Upgrade from Change the line ALL-IN-1 $ @SYS$STARTUP:A1V30START.COM location2 Version 3.0 to $ @SYS$STARTUP:A1V31START.COM location2 [1]The_exact_command_line_will_depend_on_which_Message_____ Router components are running. [2]location is the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT. (continued on next page) 8-8 Postinstallation Tasks 8.4 Edit the Site-specific Startup Procedure Table 8-2 (Cont.) Editing the OpenVMS Site-specific Startup __________________File_____________________________________ Installation Type_____________Do_the_Following__________________________ Upgrade from Change the line: ALL-IN-1 $ @SYS$STARTUP:A1S030START.COM location2 STARTER Version to 3.0 $ @SYS$STARTUP:A1V31START.COM location2 If you are Add the following entry before the entry running a for the ALL-IN-1 startup procedure: remote Message $ @SYS$STARTUP:DDS$STARTUP.COM node nodenumber Router where node is the name of the node on which the remote Message Router is installed and nodenumber is the Directory Service node number of the remote Message Router node. [2]location_is_the_location_of_the_ALL-IN-1_configuration__ file, OA$DATA_SHARE:A1CONFIG.DAT. ___________________________________________________________ 8.5 Replace the DCLTABLES on Cluster Systems If you installed ALL-IN-1 Version 3.1 on a VMScluster system, you must replace the DCLTABLES on the nodes in the cluster that are not installing ALL-IN-1 Version 3.1. Enter the following commands on each of these nodes: $ INSTALL INSTALL> REPLACE SYS$SHARE:DCLTABLES /OPEN /SHARE - _INSTALL> /HEADER_RES INSTALL> EXIT You need only do this once after you have installed ALL-IN-1 Version 3.1. The ALL-IN-1 installation procedure replaces the tables automatically for the node on which you are installing ALL-IN-1 Version 3.1. Postinstallation Tasks 8-9 8.6 Delete Files That Are No Longer Required 8.6 Delete Files That Are No Longer Required If you have upgraded or updated ALL-IN-1, various files remain in the SYSTEM directories which you can delete to increase your disk space. The files are: o For an ALL-IN-1 Version 3.0 upgrade: SYS$HELP:A1030.RELEASE_NOTES SYS$HELP:A1Llang030.RELEASE_NOTES SYS$HELP:A1Cmarket030.RELEASE_NOTES, if available SYS$STARTUP:A1V30START.COM SYS$HELP:TLC020.RELEASE_NOTES SYS$HELP:TLC021.RELEASE_NOTES SYS$HELP:A1_MUPA030.RELEASE_NOTES OA$BUILD_SHARE_IND:A1PATCH$JOURNALS.DIR You can delete this directory and its contents. o For an ALL-IN-1 STARTER Version 3.0 upgrade: SYS$HELP:AS030.RELEASE_NOTES SYS$HELP:ASLlang030.RELEASE_NOTES SYS$HELP:ASCmarket030.RELEASE_NOTES, if available 8.7 Install Missing Images 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 the startup procedure again. Images that you may need to install in this way are those referenced by optional products that you have integrated with the ALL-IN-1 image. For example, the following command installs the image RDBSHR, which is referenced by VAX DATATRIEVE: $ INSTALL INSTALL> ADD SYS$SHARE:RDBSHR /OPEN /HEADER_RES /SHARED For more details of the Install Utility, see the OpenVMS documentation. 8-10 Postinstallation Tasks 8.8 Recompile Form Libraries 8.8 Recompile Form Libraries If you are upgrading from ALL-IN-1 Version 3.0 and you have compiled form libraries on your old system which are not replaced by the upgrade, you may see the following error message: Obsolete form library please recompile If you see this message, delete the obsolete compiled form library and recompile the form library. ________________________ Note ________________________ You must also compile application or site-specific form libraries, for example, LOTUS 1-2-3 for ALL-IN-1 or your own applications. ______________________________________________________ The following form libraries are compiled automatically: o OAFORM o SITEOAFORM o MEMRES o SITEMEMRES o OAN$FORMS o SITEOAN$FORMS If you have added code or manual procedures to compile other form libraries, you must recompile them manually after the installation. Use the Precompile a form library (PCF) option from the System Customization Management (CSZ) menu. See the ALL-IN-1 Management Guide. 8.9 Migrate SITELINK30 Using Customization Management In ALL-IN-1 Version 3.1, the SITELINK31.COM file is under the control of Customization Management. Use Customization Management to edit the base template version of the site link file, SITELINK31.COM, to include your previous SITELINK30.COM. The SITELINK30.COM file is in the directory from which you last performed links. Review your customizations to SITELINK31.COM and then move your customized version to LIVE. Review your customizations Postinstallation Tasks 8-11 8.9 Migrate SITELINK30 Using Customization Management to make sure they are compatible with ALL-IN-1 Version 3.1. Do not relink ALL-IN-1 until you have done this. See Section 8.10. It is recommended that you do the following to relink: $ SET DEFAULT OA$BUILD_SHARE_ARCH $ @OA$BUILD:A1LNKDRV 8.10 Migrating Your Customizations After Upgrading Immediately after installing ALL-IN-1 Version 3.1, and before allowing your users to access ALL-IN-1, review your customizations to mandatory elements. You can rerun the CART after installing ALL-IN-1 Version 3.1 using the Check Conflicts (CC) option from the Application Maintenance menu. When you run the CART from within ALL-IN-1, it does not produce the site elements report. It does produce the full and summary reports, and the CART resolution procedure which are all stored as new elements in Customization Management. If you rerun the CART, it does not keep the previous CART full and summary reports. To keep them, use the Customization Management Copy (CO) option to save the elements with another name in the same area, for example, copy CM_CART_SUMMARY_V31$PRIMARY to CM_CART_SUMMARY_ V31$PRIMARY_19FEB. All of the elements that you have already processed will have status code F. To review your customizations: 1. From the Customization Management (CM) subsystem, select each element marked as a mandatory change and print the differences between it and the new base element. 2. Review the differences. Note where new functionality has been added or changes made. Note any symbol changes. Use the information in your upgrade plan to make the changes necessary to get your system running. 3. Test your customizations and, if they work correctly, move the elements back into the live area. 8-12 Postinstallation Tasks 8.10 Migrating Your Customizations After Upgrading 4. Before allowing your users back onto the system, review your customizations to recommended elements in the same way as you reviewed the mandatory elements. If you do not resolve conflicts to recommended elements, users may not have access to your customizations or will not have access to the full functionality of ALL-IN-1 Version 3.1. 5. Review conflicts with elements reported with status code D, see Table 2-6. Status code D indicates a customization that calls an element which has been removed from ALL-IN-1 Version 3.1. If the element that is called by your customized element has a status code of A, then no customized version of it exists. Your customization will fail if you delete the removed element, as described in Section 8.10.2. Edit the command procedure DELETE_OBSOLETE_FILES.COM so that these elements are not deleted. See Section 8.10.2. Using Customization Management, create a new customized element to replace the referenced base element that no longer exists in ALL-IN-1 Version 3.1. Use Customization Management to copy any elements reported with status code A into the development area. When you rerun the CART, these elements will be reported with status code H. 6. You can now allow your users to access ALL-IN-1 Version 3.1. When it is convenient, resolve the conflicts for informational elements. 8.10.1 Running the CART Resolution Procedure The CART resolution procedure calls individual scripts to process each status code. The scripts are called CM_CART_ SCRIPTn, where n is the CART status code. To run and edit the scripts called by the CART resolution procedure, you must have Application Maintainer privileges for the areas where the elements are stored. See the ALL-IN-1 Management Guide. To run the CART resolution procedure use the Execute procedure (EP) option from the Application Maintainer's Check Conflicts (CC) menu. Postinstallation Tasks 8-13 8.10 Migrating Your Customizations After Upgrading To change the way that the CART resolution procedure handles elements with a particular status code, do the following: 1. Enter the Customization Management (CM) subsystem. 2. Use the Access base element (ABE) option to select the CART resolution script. 3. Copy the script that you want to change into the development area. 4. Edit the script using Customization Management. It is not mandatory to use the CART resolution procedure to resolve conflicts. If the script does not provide appropriate actions to resolve the conflicts at your site, then you do not have to use it. You can use the CART resolution procedure to resolve some of the conflicts reported with an informational status code. You should review the CART resolution procedure carefully before running it. Check that your customized elements do not call a removed element, see Section 8.10 which describes how to resolve conflicts for elements reported with status code D. 8.10.2 Deleting Obsolete Files A command procedure, DELETE_OBSOLETE_FILES.COM, is provided to remove the files that are no longer required by ALL-IN-1 Version 3.1. ________________________ Note ________________________ Do not run this procedure immediately after running the CART resolution procedure. Allow time to check that all your customizations are working correctly and to ensure that your customizations do not call any elements that will be deleted by this procedure. ______________________________________________________ You can edit DELETE_OBSOLETE_FILES.COM to stop the deletion of certain files if required, for example, if one of your customizations calls an element that has been removed from the base kit and which would otherwise be deleted by this procedure. 8-14 Postinstallation Tasks 8.10 Migrating Your Customizations After Upgrading For example, the suggested resolution for elements with status code A is to: o Run the CART resolution procedure to delete the records for these elements from the Customization Management databases o Run the command procedure OA$LIB:DELETE_OBSOLETE_FILES.COM to delete the elements To run DELETE_OBSOLETE_FILES.COM, enter the following from DCL: $ @OA$LIB:DELETE_OBSOLETE_FILES.COM language where language is the language of the ALL-IN-1 system. If you have additional languages installed on your system, you can run this procedure for each additional languages. 8.10.3 Restoring Customizations to Data Files Read this section if you copied customized data files according to the instructions in Section 3.9.1. Throughout this section, the form PROFILE.DAT is used as an example. To restore your modifications to your data files, do the following: 1. Make a copy of the new base PROFILE.DAT file, preferably outside the ALL-IN-1 directory structure: $ COPY OA$DATA:PROFILE.DAT disk:[directory]BASE_PROFILE.DAT 2. Make copies of the new base PROFILn forms using Customization Management. For example, copy them to BASE_PROFILn and modify the named data so that the .FILE directive specifies the location of the backup copy of the base format PROFILE file. 3. Make the forms live. 4. Use Customization Management to add your customizations to the new base PROFILn forms and PROFIL.FDL. ________________________ Note ________________________ ALL-IN-1 Version 3.1 includes new customer specific fields in the PROFILn forms. It is recommended that Postinstallation Tasks 8-15 8.10 Migrating Your Customizations After Upgrading you use these new fields for your customizations. See Chapter 4 in the ALL-IN-1 Management Guide. ______________________________________________________ 5. Make the forms and the FDL files live. 6. Convert PROFILE.DAT to your customized format: prompt: MRM> ADD localnodeA1 /PASSWORD=password /COMPLETE_MESSAGES _ /IGNORE_SENDER /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS where: o localnode is the name of the ALL-IN-1 node or cluster. The name must be unique to the Message Router system. o password is the ALL-IN-1 mailbox password that you specified during the ALL-IN-1 installation on the remote system. ________________________ Note ________________________ The password that you specify here must be the same as you specified during the ALL-IN-1 installation. If you change the password when creating the mailbox, you Postinstallation Tasks 8-19 8.13 Setting up Remote Mail must also change it to the same value in ALL-IN-1 by using the Set operating conditions (SOC) option on the Manage Messaging menu. See Chapter 3 in the ALL-IN-1 Mail Management Guide. ______________________________________________________ 3. Exit from the Message Router management utility: MRM> EXIT Refer to the Message Router documentation for more information about mailboxes. 8.13.2 Modifying the Message Router Mailbox Entry You must modify the Message Router mailbox entry if you have a mixed-architecture cluster and you are using a Message Router in the same cluster. The installation procedure creates a mailbox entry on the Message Router node with the /OWNER=ALLIN1 qualifier. The AXP node will be unable to connect with this mailbox because the /OWNER qualifier is on the mailbox. Modify the ALL-IN-1 mailbox entry on the Message Router node to remove the qualifier. $ RUN SYS$SYSTEM:MBMAN MRM> MODIFY A1/NOOWNER MRM> EXIT where A1 is the name of the Message Router mailbox. 8.13.3 Setting Up Area Routing Follow the instructions in this section if your system: o Does not use the Mail directory o Does use area routing You must define the logical name OA$MTI_AREA which defines the area code for your system. This enables users on other systems to reply to mail from your system. This logical name is not defined during the installation. Define OA$MTI_AREA in the ALL-IN-1 site startup file: mailbox @primary_node @area_name where: o mailbox is the value for the logical name OA$MTI_MAILBX. 8-20 Postinstallation Tasks 8.13 Setting up Remote Mail o primary_node is the value for the logical name OA$PRIMARY_NODE. o area_name is the area code for your system. ________________________ Note ________________________ You must always use the commercial at character (@). Do not use AT. ______________________________________________________ If you do not know the area code, do the following on the Message Router node: 1. Run the MAILbus configuration procedure to display the current Transfer Service settings in use at your site: $ @SYS$MANAGER:MB$CONFIG 2. Display the settings for the Message Router Transfer Service: MBC> SHOW TS The area code is displayed, along with other settings, as follows: . . . Transfer Service uses area routing Area Code : areacode . . . where areacode is the area code in use at your site. 3. Enter EXIT, or press CTRL/Z, to exit from the MAILbus configuration procedure. For more details of this command, see the Message Router documentation. Postinstallation Tasks 8-21 8.13 Setting up Remote Mail 8.13.4 Configuring the VMSmail Gateway for Remote Access If you have installed the Message Router VMSmail Gateway on one of the nodes in a VMScluster you can set up other ALL-IN-1 nodes so that they can access it. On each of the nodes that does not have the gateway started, define the logical name MRGATE to the following: node::MR% where node is the node where the gateway is running. You can also use a VMSmail Gateway on a node in your network, that is remote to your cluster. You need Message Router to be installed on one of the nodes in your cluster in order to do this. Make an entry for the remote VMSmail Gateway in the mailbox directory of the Message Router Transfer Service on the VAX node in your cluster that is running Message Router: 1. Log in to the MBMANAGER account on the VAX node in your cluster that is running Message Router 2. Enter the following commands: $ RUN SYS$SYSTEM:MRMAN MRM> ADD MRGATE/REPLACE="MRGATE @node" where node is the node where the gateway is installed. 3. Exit from the Message Router management utility: MRM> EXIT See the Message Router documentation for more information. 8.13.5 Setting Up the Mail Directory The tasks that you need to do depend on the following: o If the Message Router node is in the same VMScluster and has ALL-IN-1 installed, see Section 8.13.5.1. o If the Message Router node is not in the same VMScluster or ALL-IN-1 is not installed on the Message Router node, see Section 8.13.5.2. 8-22 Postinstallation Tasks 8.13 Setting up Remote Mail 8.13.5.1 Message Router is in the Same VMScluster Read this section if ALL-IN-1 is installed in the same VMScluster as Message Router and ALL-IN-1 is installed on the Message Router node. You can be using the Mail directory as either the primary or the secondary directory. If, during the installation, you chose to use the Mail directory as the primary directory, OA$DDS_PRIME is set to 2. If, during the installation, you chose to use the Mail directory as the secondary directory with ALL-IN-1 as the primary directory, then OA$DDS_PRIME is set to 1. After installation, the following values are set up: 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. For example, OA$LYNX$ALLIN1. - The user agent entry password is the Mail directory password that you entered during the installation. 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 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. When you set up the Mail directory the values in the previous list are updated. To set up the Mail directory, do the following: 1. Log in to the ALL-IN-1 manager's ALL-IN-1 account as follows: $ ALLIN1 /USERNAME=MANAGER 2. Enter the following commands from ALL-IN-1: BUILD DDS UA /NAME="uaname"/PASSWORD="password" MBMAN> ADD DDS BUILT_OBJECT/LOG where: o uaname is the name of the user agent object. The name is in the form OA$node$ALLIN1, where node is either the node name or the cluster alias for the system on which you are setting up the Mail directory. o password is the password that ALL-IN-1 will use to access the user agent object. It must not be more than eight characters long. 3. Create and add a subscriber entry to the Mail directory for the ALL-IN-1 manager: MBMAN>BUILD DDS SUBSCRIBER /SURNAME="MANAGER" MBMAN>BUILD DDS SUBSCRIBER /PROXY="uaname" MBMAN>BUILD DDS SUBSCRIBER /SUBID="uaname" MBMAN>ADD DDS BUILT_OBJECT/LOG MBMAN>EXIT where: o MANAGER is the name of the ALL-IN-1 manager's ALL-IN-1 account and must be entered as shown. Do not enter any other account name. o uaname is the name of the user agent object that you specified, for example, OA$nodename$ALLIN1. o /PROXY="uaname" grants the local ALL-IN-1 user agent proxy access to the manager's subscriber entry. This enables the ALL-IN-1 user agent to access and update the manager's subscriber entry on behalf of the manager. o /SUBID="uaname" identifies the ALL-IN-1 manager's subscriber entry to ALL-IN-1, as there can be many entries called MANAGER. 4. On the ALL-IN-1 node (VAX or AXP), do the following from the ALL-IN-1 manager's ALL-IN-1 account: a. Enter the following commands to create temporary symbols required by the script which you will run in the next step: 8-26 Postinstallation Tasks 8.13 Setting up Remote Mail SHOW DDS node where node is the name of the Message Router node. Postinstallation Tasks 8-27 8.13 Setting up Remote Mail See Section 8.4 for more information about editing the site-specific startup file. 8.14 Restoring Your Sender and Fetcher Environment Read this section if you customized OAMTISEND.COM or OAMTIMAIL.COM in an earlier version of ALL-IN-1. As these files are no longer used by the Sender and Fetcher in ALL-IN-1 Version 3.1, you can delete any site versions of these files. You may have customized these files to allow the Sender or Fetcher to run from a different account or to allow the Sender and Fetcher to use separate data areas by changing the value of OA$MTI_DATA. To restore the same environment to Sender and Fetcher in ALL-IN-1 Version 3.1, use the Manage Sender/Fetcher (MSF) option from the Manage Messaging Menu in the System Management subsystem. See Chapter 3 in the ALL-IN-1 Mail Management Guide for more details. You may have also used your customized files to create new versions of the POSTMASTER DAF or DOCDB files to improve performance. Note that these changes are no longer appropriate as the Fetcher does not use these POSTMASTER files in ALL-IN-1 Version 3.1. 8.15 Delete or Remove Old Mail Log Files In ALL-IN-1 Version 3.1, the mail error log files MTIERR.LOG are now in OA$LOG:MTI$ERROR.SYS_LOG. The transaction log files MTILOG.LOG are also in OA$LOG and have been renamed to OA$LOG:MTI$SEND.SYS_LOG. Delete or move the old log files from the ALL-IN-1 system manager's directory to the new location. You can also delete OAMTISEND.LOG and OAMTIMAIL.LOG from the ALL-IN-1 system manager's directory. 8.16 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1 Read this section if users have been using WPS-PLUS for VMS and want to use the documents created with WPS-PLUS for VMS from within ALL-IN-1. 8-28 Postinstallation Tasks 8.16 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1 ________________________ Note ________________________ To use the converted documents in ALL-IN-1, the WPS-PLUS editor must be installed. ______________________________________________________ To convert WPS-PLUS for VMS documents, do the following: 1. Give each ALL-IN-1 user who wants to convert their WPS-PLUS for VMS documents the ALL-IN-1 DCL and CMD privileges. See the ALL-IN-1 Management Guide for details of setting these privileges. If you normally restrict this access, reset it after conversion is complete. 2. Check that the directory containing the WPS-PLUS for VMS File Cabinet exists by entering the following command: $ DIRECTORY /PROTECTION disk:[username.WPSPLUS...]*.* where disk is the name of the user's OpenVMS disk and username is the OpenVMS username This command lists all the files in the WPS-PLUS for VMS account belonging to the user. 3. Make sure that all files have the following minimum protection: (S:RWD,O:RWE,,) 4. Run ALL-IN-1 from the user account. 5. Enter WP to display the Word and Document Processing menu. 6. Enter the following command: : When conversion is complete, ALL-IN-1 returns you to the Word and Document Processing menu. 10.To convert the User-Defined Process [.UDP] files, do the following: a. From the Word and Document Processing menu, enter $. ALL-IN-1 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 OpenVMS directory, as recorded in the SYS$SYSTEM:SYSUAF.DAT file. c. When the copying is finished, press EXIT to return to ALL-IN-1. 11.Reset the users' privileges. 8.17 WPS-PLUS Login Command Procedure During the ALL-IN-1 Version 3.1 installation procedure, a login command procedure, A1WPSPLUS_LOGIN.COM, is created in SYS$MANAGER. Add this to the system login command procedure, SYS$SYLOGIN, if you want all users to run with these qualifiers. Alternately, you can make the file available to users to put into their own LOGIN.COM files. 8-30 Postinstallation Tasks 8.18 Install the File Cabinet Server Distributed License 8.18 Install the File Cabinet Server Distributed License The File Cabinet server handles access to the File Cabinet over the network. If you want to give remote users access to your node, you need the A1-DIST-SHR license. The A1- DIST-SHR license enables the File Cabinet server on your system to accept connections from a File Cabinet server on a remote system. Use the License Management Facility (LMF) to install the A1-DIST-SHR license. For information about LMF, see the LMF documentation. See Chapter 9 in the ALL-IN-1 Management Guide for more information about distributed sharing. 8.19 Moving the CDA DOC_STYLE Files If CDA$LIBRARY does not exist on your system, the CDA DOC_ STYLE files are installed in OA$LIB_SHARE. Move the files to a suitable location. 8.20 Update the Facility Definition to Use DECtrace During the installation of ALL-IN-1 Version 3.1, a Facility Definition file for DECtrace is provided to SYS$SHARE:EPC$FACILITY.TLB. If you install DECtrace after you have installed ALL-IN-1 Version 3.1, the Facility Definition is picked up automatically. If DECtrace is already installed on your system, and you wish to use it for collecting information about ALL-IN-1 Version 3.1, you must update the Facility Definition as follows: $ LIBRARY/TEXT/EXTRACT=OAV31/OUTPUT=EPC$A1V31-FAC-DEF.EPC$DEF - SYS$SHARE:EPC$FACILITY.TLB $ COLLECT INSERT DEFINITION EPC$A1V31-FAC-DEF.EPC$DEF/REPLACE Postinstallation Tasks 8-31 A _________________________________________________________________ ALL-IN-1 Version 3.1 Distribution Media The ALL-IN-1 kit is provided on magnetic tape, TK50 and Compact Disc Consolidated Software Distribution (CDROM) for VAX installations and on CDROM for AXP installations. A.1 Magnetic Tape and TK50 Kits (for VAX Installations) The ALL-IN-1 files are supplied on 6250 bpi magnetic tape or TK50 cartridge. There are two pieces of media, one for the base component and one for the language and market components. The media is labeled as follows: o Base component: ALL-IN-1 V3.1 BASE BIN media_type BASE COMPONENT A11031) (c) 1994 Digital Equipment Corp. media_type is the code for your distribution media. This media contains the following base component savesets: A1031.A A1031.B (used by VAX only) A1031.C (used by AXP only) A1031.D (used by VAX only) A1031.E (used by AXP only) A1031.F (used by VAX only) A1031.G (used by AXP only) A1031.H (used by VAX only) A1031.I (used by AXP only) A1031.J A1031.K A1031.L ALL-IN-1 Version 3.1 Distribution Media A-1 A.1 Magnetic Tape and TK50 Kits (for VAX Installations) o Language and market component: ALL-IN-1 V3.1 language BIN media_type LANGUAGE/MKT COMPONENT A12031 (c) 1994 Digital Equipment Corp. where media_type is the code for your distribution media and language is the name of the language that you are installing, for example, ENGLISH. This media contains the language, market and dialect (if provided) savesets. o The following language savesets are provided, where lang is the 2-letter code for the language that you are installing: A1Llang031.A (Contains the Release Notes: Part 1 Language) A1Llang031.B A1Llang031.C A1Llang031.D A1Llang031.E A1Llang031.F A1Llang031.G A1Llang031.H A1Llang031.I (used by VAX only) A1Llang031.J (used by AXP only) A1Llang031.K A1Llang031.L A1Llang031.M See your ALL-IN-1 Installation: Language and Market Supplement. o The market savesets are labeled: A1Cmarket031.A (contains the Release Notes: Part 2 Market) A1Cmarket031.B A1Cmarket031.C A1C031.A where market is the 2-letter market code for the market component you are installing. See your ALL-IN-1 Installation: Language and Market Supplement for the savesets provided with your market component. The A1C031.A saveset contains an index of the market and dialect components on the tape, and is used only during the installation. A-2 ALL-IN-1 Version 3.1 Distribution Media A.1 Magnetic Tape and TK50 Kits (for VAX Installations) o If the language you are installing has a separate dialect saveset, it will be labelled A1Ddialect031.A, where dialect is the 5-character dialect code. See your ALL-IN-1 Installation: Language and Market Supplement for the savesets provided with your dialect component. o VAX FMS (used by VAX only) o DEC FMS (used by AXP only) o CDA Interoperability kit, CDAPAT011.A Each saveset has a unique kit revision identifier, for example: A1031BASEA.REV_nnn. All other software provided with your ALL-IN-1 kit is supplied on separate tapes. A.2 Compact Disc Distribution Kits (VAX or AXP Installations) On the Compact Disc (CD) the base kit is in the directory A1031.KIT. The documentation is in a directory called A1031.DOCUMENTATION. For each language, there is a directory called A1lang031, where lang is the 2-letter code for the ALL-IN-1 language that you are installing. The subdirectories are: o A1lang031.KIT, where lang is the 2-letter code for the language that you are installing. See the ALL-IN-1 Installation: Language and Market Supplement. This directory contains all the save sets that are required to install the base, language, and market components of ALL-IN-1 Version 3.1: - Base component savesets: This media contains the following base component savesets: ALL-IN-1 Version 3.1 Distribution Media A-3 A.2 Compact Disc Distribution Kits (VAX or AXP Installations) A1031.A A1031.B (used by VAX only) A1031.C (used by VAX AXP only) A1031.D (used by VAX VAX only) A1031.E (used by VAX AXP only) A1031.F (used by VAX VAX only) A1031.G (used by VAX AXP only) A1031.H (used by VAX VAX only) A1031.I (used by VAX AXP only) A1031.J A1031.K A1031.L - The following language savesets are provided, where lang is the 2-letter code for the language that you are installing: A1Llang031.A (Contains the Release Notes: Part 1 Language) A1Llang031.B A1Llang031.C A1Llang031.D A1Llang031.E A1Llang031.F A1Llang031.G A1Llang031.H A1Llang031.I (used by VAX VAX only) A1Llang031.J (used by VAX AXP only) A1Llang031.K A1Llang031.L A1Llang031.M See your ALL-IN-1 Installation: Language and Market Supplement. - The market savesets are labelled: A1Cmarket031.A (contains the Release Notes: Part 2 Market) A1Cmarket031.B A1Cmarket031.C where market is the 2-letter market code for the market component you areinstalling. See your ALL-IN-1 Installation: Language and Market Supplement for the savesets provided with your market component. A-4 ALL-IN-1 Version 3.1 Distribution Media A.2 Compact Disc Distribution Kits (VAX or AXP Installations) - If the language you are installing has a separate dialect saveset it will be labelled A1Ddialect031.A, where dialect is the 5-character dialect code. o A1lang031.DOCUMENTATION This directory contains documentation in ASCII (.TXT) and PostScript (.PS) format. - The ALL-IN-1 Installation: Guide, INST_GUIDE_1.TXT and INST_GUIDE_1.PS - The ALL-IN-1 Installation: Language and Market Supplement, INST_GUIDE_2.TXT and INST_GUIDE_2.PS - The Read Me First letter, READ_ME_FIRST.TXT and READ_ ME_FIRST.PS - The Software Product Description (SPD). The CDROM also contains the following software in their own directories: o VAX Forms Management System (FMS) Version 2.4 (VAX only) o DEC FMS Version 2.4 (AXP only) o Message Router Version 3.3A (VAX only) o Message Router VMSmail Gateway Version 3.3 (VAX only) o DEC Notes Version 2.5 o CDA Interoperability Kit ALL-IN-1 Version 3.1 Distribution Media A-5 B _________________________________________________________________ ALL-IN-1 Version 3.1 Files and Directories This appendix lists new directories and logicals created in ALL-IN-1 Version 3.1 and files that are installed in directories other than the ALL-IN-1 directories. B.1 New Directories Created in ALL-IN-1 Version 3.1 For ALL-IN-1 Version 3.1, new directories have been created for the VAX and AXP architecture-specific files. See Table B-1. In the table, arch means either VAX or AXP and lang is the name of the language that is installed, for example, ENGLISH. The ALL-IN-1 files are organized into subdirectories of the top-level OpenVMS directory used by ALL-IN-1. Table B-1 New ALL-IN-1 Directories for Architecture Dependent __________Files__________________________________________________ Search_List________Logical_Name____________Directory_____________ OA$EXE OA$EXE_LLV OA$EXE_arch_lang OA$EXE_SHARE OA$EXE_arch_SHARE OA$BUILD_SHARE OA$BUILD_SHARE_ARCH SOURCES_arch_SHARE OA$BUILD_SHARE_IND SOURCES_SHARE OA$BUILD_LLV OA$BUILD_LLV_ARCH SOURCES_arch_lang OA$BUILD_LLV_IND SOURCES_lang (continued on next page) ALL-IN-1 Version 3.1 Files and Directories B-1 B.1 New Directories Created in ALL-IN-1 Version 3.1 Table B-1 (Cont.) New ALL-IN-1 Directories for Architecture __________________Dependent_Files________________________________ Search_List________Logical_Name____________Directory_____________ OA$SITE_BUILD_ OA$SITE_BUILD_SHARE_ SITE.SOURCES_arch_ SHARE ARCH SHARE OA$SITE_BUILD_SHARE_ SITE.SOURCES_SHARE IND OA$SITE_BUILD_LLV OA$SITE_BUILD_LLV_ARCH SITE.SOURCES_arch_lang OA$SITE_BUILD_LLV_IND SITE.SOURCES_lang _________________________________________________________________ B.2 Files in the ALL-IN-1 Kit For a complete list of all ALL-IN-1 directories and file names when the installation is complete, use the following command for each ALL-IN-1 area: $ DIR/SEC[a1dir...]*.*/out=a1dir.TXT where a1dir is the top level directory name for each area (for example ALLIN1.DIR). The list of files is a useful reference if you need to resolve any problems with file protections or ACLs. B.3 Files Installed in Non- ALL-IN-1 Directories The following list shows the files that are installed in directories other than the ALL-IN-1 directories. Where language is included in a file name, this is the name of the installed language, for example, ENGLISH. o SYS$COMMON:[SYSLIB] OA$AIDA_CSHR.EXE OA$AIDA_DSSHR.EXE OA$AIDA_GCMSHR.EXE OA$AIDA_RTLSHR.EXE OA$AIDA_SECSHR.EXE OAFC$CLIENT_SHR.EXE OA$DSL$SHR.EXE OA$TMAECOMM.EXE B-2 ALL-IN-1 Version 3.1 Files and Directories B.3 Files Installed in Non- ALL-IN-1 Directories DPESHR.EXE SYS$PROXY_SHR.EXE XPORT.L32 XPORT.OLB XPORT.REQ OAFCDEF.H OAFCDEF.R32 OAFCEXT.H OAFCEXT.R32 OAFC$LINK.OPT PRXDEF.H DDIF$READ_DX.EXE DDIF$READ_MACWRITE.EXE DDIF$READ_PICT.EXE DDIF$READ_RTF.EXE DDIF$READ_WORD5.EXE DDIF$READ_WORDP.EXE DDIF$READ_WPL.EXE DDIF$WRITE_DX.EXE DDIF$WRITE_MACWRITE.EXE DDIF$WRITE_PICT.EXE DDIF$WRITE_RTF.EXE DDIF$WRITE_WORD5.EXE DDIF$WRITE_WORDP.EXE DDIF$WRITE_WPL.EXE DTIF$READ_DIF.EXE DTIF$READ_TCV.EXE DTIF$READ_WK1.EXE DTIF$READ_WK3.EXE DTIF$WRITE_WK1.EXE DTIF$WRITE_WK3.EXE DDIF$READ_RNO.EXE (AXP Only) MRAPPSHAR.EXE (VAX Only) MRAXPSHAR.EXE (AXP Only) DDS$RMT_VAX.EXE (VAX Only) DDS$RMT_ALPHA.EXE (AXP Only) ALL-IN-1 Version 3.1 Files and Directories B-3 B.3 Files Installed in Non- ALL-IN-1 Directories LCI$ETHMCO.EXE } LCI$SCHMCO.EXE } LCI$SHARE.EXE } VAX Only LCI$UAHMCO.EXE } LCI$UDHMCO.EXE } LCI$ETHMCO_TV.EXE } LCI$SCHMCO_TV.EXE } LCI$SHARE_TV.EXE } AXP Only LCI$UAHMCO_TV.EXE } LCI$UDHMCO_TV.EXE } OA$LLVlanguage.EXE (On Multilingual systems only) ) OAHFLOAT_TV.EXE (AXP only) OA$WPL_ALL_TV.EXE (AXP with full WPS-PLUS support only) OA$WPL_FDP_TV.EXE (AXP without full WPS-PLUS support only) IMP$IMPSHR.EXE (VAX only) IMP$IMPSHRP.EXE (VAX only) o SYS$COMMON:[SYSEXE] OA$AIDA_CLI.EXE OA$AIDA_DDS.EXE OA$AIDA_SERVER.EXE OAFC$PRINT_TRACE_LOG.EXE OAFC$SYSFOLD_SEED.EXE OAFC$SERVER.EXE OA$SCRIPT_SYMBIONT.EXE OA$FORMATTER.EXE o SYS$COMMON:[SYSMSG] XPORTMSG.EXE OAFC$MESSAGES.OBJ CNV_MSG.DAT DPEMSG.EXE MRAPPMSG.EXE (VAX Only) MRAXPMSG.EXE (AXP Only) DDS$RMT_VAX.EXE (VAX Only) DDS$RMT_ALPHA.EXE (AXP Only) B-4 ALL-IN-1 Version 3.1 Files and Directories B.3 Files Installed in Non- ALL-IN-1 Directories o SYS$COMMON:[SYS$STARTUP] A1V31START.COM OA$AIDA_START.COM OAFC$STARTUP.COM DDS$STARTUP.COM o SYS$COMMON:[SYSMGR] A1WPSPLUS_LOGIN.COM o SYS$COMMON:[SYSHLP.EXAMPLES] EXAMPLE_READ_DIF.CDA$OPTIONS EXAMPLE_READ_DX.CDA$OPTIONS EXAMPLE_READ_MACWRITE.CDA$OPTIONS EXAMPLE_READ_PICT.CDA$OPTIONS EXAMPLE_READ_RTF.CDA$OPTIONS EXAMPLE_READ_WK1.CDA$OPTIONS EXAMPLE_READ_WK3.CDA$OPTIONS EXAMPLE_READ_WORD5.CDA$OPTIONS EXAMPLE_READ_WORD5_FONTMAP.CDA$OPTIONS EXAMPLE_READ_WORDP.CDA$OPTIONS EXAMPLE_READ_WPL.CDA$OPTIONS EXAMPLE_WRITE_DX.CDA$OPTIONS EXAMPLE_WRITE_MACWRITE.CDA$OPTIONS EXAMPLE_WRITE_PICT.CDA$OPTIONS EXAMPLE_WRITE_RTF.CDA$OPTIONS EXAMPLE_WRITE_WK1.CDA$OPTIONS EXAMPLE_WRITE_WK3.CDA$OPTIONS EXAMPLE_WRITE_WORD5.CDA$OPTIONS EXAMPLE_WRITE_WORDP.CDA$OPTIONS EXAMPLE_WRITE_WORDP_V5_0.CDA$OPTIONS EXAMPLE_WRITE_WORDP_V5_1.CDA$OPTIONS EXAMPLE_WRITE_WPL.CDA$OPTIONS Lexicon files in A1$DISK:[LCI.LEXICONS] are language specific and only installed if you install WPS-PLUS as the default editor. The files in the following table are for an American English system. For another language the files in this directory will be different. ALL-IN-1 Version 3.1 Files and Directories B-5 B.3 Files Installed in Non- ALL-IN-1 Directories ___________________________________________________________ VAX______________AXP_______________________________________ LCI$ETHMCO.EXE LCI$ETHMCO_TV.EXE LCI$HYHMCO.EXE LCI$HYHMCO_TV.EXE LCI$SCHMCO.EXE LCI$SCHMCO_TV.EXE LCI$SHARE.EXE LCI$SHARE_TV.EXE LCI$UAHMCO.EXE LCI$UAHMCO_TV.EXE LCI$UDHMCO.EXE___LCI$UDHMCO_TV.EXE_________________________ B-6 ALL-IN-1 Version 3.1 Files and Directories _________________________________________________________________ Index A______________________________ C______________________________ A1CONFIG.DAT, 8-7 Calendar Manager, 3-33 A1V31START.COM, 8-6, 8-7 CART, 2-1 ACMS definition of base element, integrating during 2-2 installation, 1-25 definition of runid, 2-2 Additional languages error report, 2-6 installing, 1-9 full report, 2-6 ALL-IN-1 output, 2-6 starting on all nodes, 8-6 overview, 2-2 ALL-IN-1 utility accounts, 1-9 preparing to run, 2-11 Alpha-ready systems, 1-18 resolution procedure, 2-6 Applications running, 2-12 replacing help modules, 8-16 running after installation, Architecture 8-12 supported, 1-7 running on multilingual Architecture-specific system, 2-1 directories, B-1 severity of conflicts, 2-9 Area routing site elements report, 2-6 define logical OA$MTI_AREA, status code A, 2-28 8-20 status code B, 2-15 setting up, 8-20 status code C, 2-15 AUTOGEN, 3-19 status code D, 2-25 AXP architecture status code E, 2-25 installing on, 1-7 status code F, 2-28 status code G, 2-29 B______________________________ status code H, 2-29 Backing up, 3-35 status code I, 2-21 Batch queue status code K, 2-21 for Sender/Fetcher check job, status code L, 2-22 1-20 status code M, 2-23 status code N, 2-23 status code O, 2-25 Index-1 CART (cont'd) DATATRIEVE status code P, 2-26 integrating during status code R, 2-30 installation, 1-25 status codes, 2-9 DCLTABLES summary report, 2-6 replacing, 8-9 when to run, 2-2 DDS$STARTUP CART resolution procedure adding to site-specific running and editing, 8-13 startup procedure, 8-27 CDA, 1-26 DEC FMS, A-5 Checklist DEC Notes installation decisions and starting before ALL-IN-1, information, 1-2 8-8 postinstallation tasks, 8-1 DELETE_OBSOLETE_FILES.COM, Cluster 8-14 VMSmail Gateway configuration Deleting files , 8-22 postinstallation, 8-10 Configuring Deleting obsolete files after VMSmail Gateway, 8-22 installation, 8-14 Conflict Checking and Dialect component, 1-8 Resolution Tool Directories See CART, 2-1 new for ALL-IN-1 Version 3.1, Conventions B-1 used in this guide, xiii Disk space requirements, 3-21 Correcting system set-up Disks errors, 3-31 backing up, 3-35 Customization Management Documents moving applications to, 2-11 related to this guide, xii moving elements to, 2-11 Customizations E______________________________ linking ALL-IN-1 to include, Error messages, 7-1, 7-4 8-17 Errors migrating, 8-12 fatal, 3-31 reviewing after installation, non-fatal, 3-32 8-12 Customized systems F conflict checking and _______________________________ resolution tool, 2-1 Fatal errors, 3-31 Fetcher D restoring setup, 8-28 _______________________________ Files, deleting Data files postinstallation, 8-10 restoring customizations to, Form libraries 8-15 recompiling, 8-11 Index-2 G______________________________ L______________________________ Global page file sections Language component, 1-8 (GBLPAGFIL), 3-17 Languages Global pages (GBLPAGES), 3-17 installing additional, 1-9 Global sections (GBLSECTIONS), License Management Facility, 3-17 3-10 Licenses H______________________________ prerequisite products, 3-11 Help modules registering, 3-10 replacing for your Linking ALL-IN-1 to include application, 8-16 customizations, 8-17 Logical names I assigning, 3-22 _______________________________ Logins Images disallow, 3-34 missing, 8-10 required, 3-26 M______________________________ Installation Mail directory aborting, 5-1 setting up with Message disk space required, 3-21 Router outside cluster, paths, 1-10 8-25 time required, 5-1 setup for Message Router in Installation of optional same cluster, 8-23 software starting up for remote use, order of, 3-12 8-27 Installation Verification Mail Directory Procedure (IVP) planning use of, 1-21 running, 1-29 Mailbox Installed images adding for remote ALL-IN-1 required, 3-26 systems, 8-19 Installing account modifying, 8-20 licensing, 3-10 Market component, 1-8 quotas required during Message files installation, 3-13 customized, 2-12 valid rights identifier, Message Router, A-5 3-13 and ALL-IN-1, 1-20 Installing missing images configuring, 8-20 postinstallation, 8-10 integrating, 1-19 IVP planning use of, 1-19 error messages, 7-4 setting up, 8-19 running, 1-29 Message Router mailbox Index-3 Message Router mailbox (cont'd) P______________________________ modifying for mixed- PC option, 3-31 architecture clusters, Perform all preinstallation 8-20 checks (PC) option, 3-31 Message Router VMSmail Gateway Personal licence , A-5 adding installing account to integrating, 1-19 reserve list, 3-10 Messages Planning error, 7-1 upgrade installation, 2-1 translating to ASCII, 1-24 use of Message Router, 1-19 warning, 7-1 Preinstallation Migrating checks, 3-31 customizations, 8-12 Preparing system for Migration tools installation, 3-33 Conflict Checking and Prerequisite software Resolution Tool, 2-1 licenses, 3-11 MR$NODE, 8-20 Product Authorization Key, MTIERR.LOG 3-10 renamed, 8-28 MTILOG.LOG R______________________________ renamed, 8-28 Recompiling Multilanguage system, 1-9 form libraries, 8-11 N Registering software licenses, _______________________________ 3-12 Non-fatal checks, repeating, Related documents 3-31 to this guide, xii Non-fatal errors, 3-32 Release notes, 3-5 printing, 3-5 O______________________________ reading, 3-5 OA$DDS_PRIME, 8-23 Relinking OA$MTI_AREA, 8-20 recommendations, 8-11 OAMTIMAIL.COM, 8-28 Remote OAMTISEND.COM, 8-28 VMSmail Gateway configuration Optional software , 8-22 order of installation, 3-12 Remote Mail directory Order of installation of starting up, 8-27 optional software, 3-12 Repeating non-fatal checks, 3-31 Rightslist entries checking after installation, 8-17 Index-4 TCP/IP network protocol S______________________________ using, 1-28 Sender Time required for installation restoring setup, 8-28 , 5-1 Setup Sender and Fetcher, 8-28 U______________________________ Site-specific startup Upgrade installation procedure, 8-6 running the CART, 2-1 adding DDS$STARTUP, 8-27 Users SITELINK31.COM, 8-11 log out, 3-34 Software license, 3-10 Software Product Description, V______________________________ A-5 VAX FMS, A-5 SPD, A-5 VMScluster Starting adding AXP support, 1-14, ALL-IN-1, 8-6 1-16 Startup procedure adding VAX support, 1-14, creating, 8-6 1-17 editing site-specific, 8-7 installing on AXP and VAX, site specific, 8-6 1-14 SYS$STARTUP:A1V31START.COM, VMSmail Gateway 8-6 configuring, 8-22 System preparing for installation, W 3-33 _______________________________ System disk Warning messages, 7-1 backing up, 3-35 WPL to DDIF converters, 1-26 System parameter values WPS-PLUS changing with AUTOGEN, 3-19 integrating, 1-27 WPS-PLUS for VMS T______________________________ converting documents to Target disk ALL-IN-1, 8-28 backing up, 3-35 Index-5