CONTENTS Title Page Copyright Page Preface 1 Planning an ALL-IN-1 Version 3.1 Installation 1.1 Checklist of Installation Decisions and Information 1.2 General Information About Installing ALL-IN-1 Version 3.1 1.2.1 Support for Different Architectures 1.2.2 Version 3.1 Architecture-Dependent Files and Directories 1.2.3 Components of ALL-IN-1 Version 3.1 1.2.4 Additional Languages 1.2.5 Accounts Needed for ALL-IN-1 1.2.6 Use of ALL-IN-1 Areas 1.3 Installation Paths 1.4 Installing on More Than One Architecture in a VMScluster 1.4.1 Installing AXP Architecture Support 1.4.2 Installing VAX Architecture Support 1.4.3 Replacing a VAX System with an AXP System 1.5 Mail System Planning 1.5.1 Batch Queue for Mail 1.5.2 Using Message Router 1.5.3 Level of Mail Directory Support 1.5.4 Setting up a Remote Directory Service 1.5.5 Translating Outgoing Mail Messages to ASCII 1.6 Other Software Referenced by the Installation Procedure 1.6.1 Software Which can be Integrated During the Installation 1.6.2 Compound Document Architecture (CDA) Support 1.6.3 Installing WPS-PLUS as the Default Editor 1.6.4 Using TCP/IP to Communicate With Client Applications 1.7 Running the IVP (Installation Verification Procedure) 1.8 Planning an Upgrade Installation 1.9 What to do Next 2 Preparing to Upgrade a Customized System 2.1 Overview of the CART 2.2 Modified ALL-IN-1 Systems 2.3 Understanding the CART Reports 2.3.1 Types of CART Report 2.3.2 Format of the CART Reports 2.3.3 CART Status Codes and the Severity of Conflict 2.4 Preparing to Run the CART 2.4.1 Printing a System Modification Report 2.4.2 Importing Elements from Outside Customization Management 2.4.3 Customized Help Modules 2.4.4 Customized Message Files 2.5 Running the CART 2.6 What to do After Running the CART 2.6.1 Checking the Site Elements Report 2.6.2 Checking for Missing Elements (Status Codes B and C) 2.6.3 Rerunning the CART 2.6.4 Preparing Your Upgrade Plan 2.6.5 Guidelines for Resolving Conflicts 2.6.6 CART Resolution Procedure 2.6.7 Planning Postinstallation Tasks 2.7 Mandatory Status Codes (I, K, L, M and N) 2.8 Recommended Status Codes (D, E, O, P and Q) 2.9 Informational Status Codes (A, F, G, H and R) 3 Preparing Your System for Installation 3.1 Preinstallation Checklist 3.2 Reading and Printing the Online Release Notes 3.3 Checking Prerequisite and Optional Software 3.4 Linking Software Products During the Installation 3.5 Checking the Licence for the Installing Account 3.6 Registering License Product Authorization Keys (PAKs) 3.6.1 Registering Before a Full Installation 3.6.2 Registering License PAKs for Software Provided with ALL-IN-1 Version 3.1 3.7 Example Order for Installing Optional Software 3.8 Installation Procedure Requirements 3.8.1 Installing Account Requirements 3.8.2 System Parameters 3.8.3 Displaying Current System Parameters 3.8.4 Changing System Parameter Values 3.8.4.1 Updating Dynamic System Parameters with AUTOGEN 3.8.4.2 Updating Non-Dynamic System Parameter with AUTOGEN 3.8.5 Disk Space on Your System Disk or Alternate Working Device 3.8.6 Using the OA$LIB_SHARE Disk as the AWD 3.8.7 Disk Space for ALL-IN-1 Areas on Target Disks 3.8.8 Assigning Logical Names to Your Disks 3.8.9 Full Installation: Disk Space for ALL-IN-1 Areas 3.8.10 Upgrade Installation: Disk Space for ALL-IN-1 Areas 3.8.11 Addition of Architecture Support: Disk Space for ALL-IN-1 areas 3.8.12 Disk Quota Allocation 3.8.13 Installed Images 3.8.14 Installing FDVMSG.EXE and FDVSHR.EXE Images 3.8.15 Installing Other Images 3.8.16 Checking The Location of DCLTABLES.EXE 3.9 Additional Tasks for Upgrade Installations 3.9.1 Copying Customized Data Files 3.10 Using a Remote Message Router 3.10.1 Create an ALL-IN-1 Mailbox on the Remote Message Router Node 3.11 Preinstallation System Check 3.11.1 Types of Errors Reported 3.11.2 Running the Perform all Preinstallation Checks (PC) Option 3.12 System Preparation Tasks 3.12.1 Shut Down ALL-IN-1 3.12.2 Deinstall Files Installed in Memory 3.12.3 Back Up Your System and Target Disks 4 Planning and Implementing a Minimal Shutdown Upgrade 4.1 How the Minimal Shutdown Upgrade Works 4.1.1 Explanation of Phase 1 4.1.2 Files and Directories Involved in Phase 1 4.1.3 Explanation of Phase 2 4.2 Disadvantages of a Minimal Shutdown Upgrade 4.3 Installation Planning Decisions 4.4 Preparing Your System for a Minimal Shutdown Upgrade 4.5 Installation Procedure for Minimal Shutdown Upgrade 4.5.1 Procedure for Phase 1 4.5.2 Phase 2 Procedure 4.6 Manual Postinstallation Procedures 4.6.1 Running the Postinstallation Procedures 5 Installation Procedure: Full, Upgrade and Addition of Architecture Support 5.1 Keeping a Record of the Installation 5.2 Installation Procedure for Full and Upgrade Installations 5.3 Adding Architecture Support 5.3.1 Before You Start 5.3.2 Installation Procedure for Adding Architecture Support 5.4 Automatic Postinstallation Tasks 5.5 Manual Postinstallation Tasks 6 Installation Procedure: Additional Languages 6.1 Keeping a Record of the Installation 6.2 Installation Procedure for Additional Language Installations 6.3 Installing Architecture Support for an Additional Language 7 Installation Errors and Failure 7.1 Common Error Message That Does Not Require Action 7.2 Common Errors Which Require Action 7.3 Failure During Postinstallation 7.4 Installation Failure 7.4.1 Failure of Upgrade Installations in Safety Mode 7.4.2 Failure of Upgrade Installations in Non-Safety Mode 7.4.3 Full Installations 7.4.4 Failure Due to Insufficient Dynamic Memory 7.5 Error Messages when Running the IVP 7.6 IVP Failure 8 Postinstallation Tasks 8.1 Checklist of Manual Postinstallation Tasks 8.2 Start ALL-IN-1 on all Nodes in a VMScluster System 8.3 Create or Modify the Site-specific ALL-IN-1 Startup Procedure 8.4 Edit the Site-specific Startup Procedure 8.5 Replace the DCLTABLES on Cluster Systems 8.6 Delete Files That Are No Longer Required 8.7 Install Missing Images 8.8 Recompile Form Libraries 8.9 Migrate SITELINK30 Using Customization Management 8.10 Migrating Your Customizations After Upgrading 8.10.1 Running the CART Resolution Procedure 8.10.2 Deleting Obsolete Files 8.10.3 Restoring Customizations to Data Files 8.10.4 Replacing the Help Modules for Your Application 8.11 Link ALL-IN-1 to Include Code-level Customizations 8.12 Check Entries in RIGHTSLIST.DAT 8.13 Setting up Remote Mail 8.13.1 Create a Mailbox for ALL-IN-1 8.13.2 Modifying the Message Router Mailbox Entry 8.13.3 Setting Up Area Routing 8.13.4 Configuring the VMSmail Gateway for Remote Access 8.13.5 Setting Up the Mail Directory 8.13.5.1 Message Router is in the Same VMScluster 8.13.5.2 Message Router is not in the Same VMScluster 8.13.6 Remote Mail Directory Startup Procedure 8.14 Restoring Your Sender and Fetcher Environment 8.15 Delete or Remove Old Mail Log Files 8.16 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1 8.17 WPS-PLUS Login Command Procedure 8.18 Install the File Cabinet Server Distributed License 8.19 Moving the CDA DOC_STYLE Files 8.20 Update the Facility Definition to Use DECtrace A ALL-IN-1 Version 3.1 Distribution Media A.1 Magnetic Tape and TK50 Kits (for VAX Installations) A.2 Compact Disc Distribution Kits (VAX or AXP Installations) B ALL-IN-1 Version 3.1 Files and Directories B.1 New Directories Created in ALL-IN-1 Version 3.1 B.2 Files in the ALL-IN-1 Kit B.3 Files Installed in Non- ALL-IN-1 Directories FIGURES 1-1 Installing AXP Architecture Support 1-2 Installing VAX Architecture Support 2-1 What the CART Does 4-1 Minimal Shutdown Upgrade: Phase 1 4-2 Minimal Shutdown Postinstallation Phase TABLES 1-1 Checklist of Installation Decisions and Information Required 1-2 Installation Paths 1-3 Strategy for Adding Architecture Support 1-4 Mail System Planning Decisions 1-5 Installation Options for Levels of Mail Directory Support 1-6 Questions Asked During a Customized Configuration 1-7 TCP/IP Service Information 1-8 What To Do Next 2-1 Terminology used by the CART 2-2 CART Reports 2-3 CART Conflict Severity, Status Codes and Actions 2-4 CART Status Codes B and C 2-5 Mandatory Status Codes (I, K, L, M and N) 2-6 Recommended Status Codes (D, E, O, P and Q) 2-7 Informational Status Codes (A, F, G, H and R) 3-1 Preinstallation Checklist 3-2 Prerequisite and Optional Software 3-3 Process Account Quotas for the Installing Account 3-4 Minimum System Parameter Values Required 3-5 Changing System Parameter Values 3-6 Full Installation: Disk Space for ALL-IN-1 Areas 3-7 Upgrade Installations: Disk Space for ALL-IN-1 Areas 3-8 Addition of Architecture Support: Disk Space for ALL-IN-1 Areas 4-1 Minimal Shutdown Upgrade: Disk Space for ALL-IN-1 Areas 4-2 Installation Procedure for Phase 1 of the Minimal Shutdown Upgrade 4-3 Installation Procedure for Phase 2 of the Minimal Shutdown Upgrade 4-4 Minimal Shutdown Postinstallation Procedures 5-1 Information About the Installation Procedure 5-2 Installation Procedure for Full and Upgrade Installations 5-3 When to Install VAX or AXP Architecture Support 5-4 Installation Procedure for Adding Architecture Support 6-1 Installation Procedure for An Additional Language 6-2 Installation Procedure for Addition of Architecture Support for an Additional Language 8-1 Postinstallation Tasks 8-2 Editing the OpenVMS Site-specific Startup File 8-3 Tasks for Setting up Remote Mail B-1 New ALL-IN-1 Directories for Architecture Dependent Files