ALL-IN-1____________________________________________ Installation: Guide Order Number: AA-N323K-TE Revision/Update Information: Revised for ALL-IN-1 Version 3.2 Operating system: OpenVMS VAX Version 6.1 or higher and OpenVMS Alpha Version 6.1 or higher Software version: Version 3.2 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ January 1996 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 1996. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: ACMS, ALL-IN-1, CDA, DATATRIEVE, DEC, DEC Notes, DEClaser, DECmail, DECmate, DECnet, DECprint, DECstation, DECtrace, DECwindows, Digital, EDT, FMS, LA, LN03, LQP02, MAILbus, MailWorks, MicroVAX, OpenVMS, PATHWORKS, TeamLinks, ULTRIX, UNIBUS, VAX, VAXcluster, VAXmate, VAXstation, VMS, VMScluster, VMSmail, VT, WPS-PLUS, and the DIGITAL logo PostScript is a registered trademark of Adobe Systems Incorporated. Appletalk and Macintosh are registered trademarks of Apple Computer, Inc. MacWrite is a registered trademark of Claris Corporation. HP and LaserJet are registered trademarks of Hewlett- Packard Company. IBM and OfficeVision are registered trademarks of International Business Machines Corporation. 1-2-3 and Lotus are registered trademarks of Lotus Development Corporation. Microsoft, MS-DOS and Windows are registered trademarks of Microsoft Corporation. Motif is a registered trademark of Open Software Foundation, Inc. Vadic is a registered trademark of Racal-Vadic, Inc. WordPerfect is a trademark of WordPerfect Corp. UNIX is a registered trademark in the US and other countries, licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... ix 1 Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks............ 1-2 1.2 Reading and Printing the Online Release Notes......................................... 1-6 1.3 Checking Prerequisite and Optional Software... 1-8 1.4 Checking the License for the Installing Account....................................... 1-14 1.5 Registering License Product Authorization Keys (PAKs)........................................ 1-14 1.5.1 Registering the ALL-IN-1 License PAK Before a new Installation................. 1-15 1.5.2 Registering the ALL-IN-1 License PAK Before an Upgrade......................... 1-15 1.5.3 Registering License PAKs for Software Provided with ALL-IN-1 Version 3.2........ 1-16 1.6 Example Order for Installing Optional Software...................................... 1-17 1.7 Installation Procedure Requirements........... 1-18 1.7.1 Installing Account Requirements........... 1-18 1.7.2 System Parameters......................... 1-19 1.7.3 Displaying Current System Parameters...... 1-23 1.7.4 Changing System Parameter Values.......... 1-23 1.7.4.1 Updating Dynamic System Parameters with AUTOGEN................................. 1-25 1.7.4.2 Updating Non-Dynamic System Parameter with AUTOGEN............................ 1-25 1.7.5 Disk Space on Your System Disk or Alternate Working Device.................. 1-26 1.7.6 Using the OA$LIB_SHARE Disk as the AWD.... 1-27 iii 1.7.7 Disk Space for ALL-IN-1 Areas on Target Disks..................................... 1-27 1.7.8 Assigning Logical Names to Your Disks..... 1-28 1.7.9 New Installation: Disk Space for ALL-IN-1 Areas..................................... 1-29 1.7.10 Upgrade Installation: Disk Space for ALL-IN-1 Areas............................ 1-30 1.7.11 Addition of Architecture Support: Disk Space for ALL-IN-1 areas.................. 1-31 1.7.12 Disk Quota Allocation..................... 1-32 1.7.13 Installed Images.......................... 1-32 1.7.14 Installing FDVMSG.EXE and FDVSHR.EXE Images.................................... 1-36 1.7.15 Installing Other Images................... 1-37 1.7.16 Checking The Location of DCLTABLES.EXE.... 1-37 1.8 Additional Tasks for Upgrade Installations.... 1-37 1.8.1 Copying Customized Data Files............. 1-38 1.9 Using the MAILbus 400 MTA and Digital X.500... 1-40 1.10 Using a Remote Message Router................. 1-40 1.10.1 Create an ALL-IN-1 Mailbox on the Remote Message Router Node ...................... 1-41 1.11 Running the Preinstallation System Check...... 1-42 1.11.1 Types of Errors Reported.................. 1-42 1.11.2 Running the Perform all Preinstallation Checks (PC) Option........................ 1-43 1.12 Final System Preparation Tasks: New Installations................................. 1-44 1.13 Final System Preparation Tasks: Upgrade Installations ................................ 1-44 1.13.1 Shut Down ALL-IN-1........................ 1-45 1.13.2 Deinstall Files Installed in Memory....... 1-45 1.14 Back Up Your System and Target Disks.......... 1-45 2 Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations................................. 2-3 2.2 Adding or Upgrading Architecture Support...... 2-30 2.2.1 Before You Start.......................... 2-31 2.2.2 Installation Procedure for Adding Architecture Support...................... 2-31 2.3 Automatic Postinstallation Tasks.............. 2-42 iv 2.4 Manual Postinstallation Tasks................. 2-43 3 Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations................................. 3-2 3.2 Installing Architecture Support for an Additional Language........................... 3-10 4 Installation Errors and Failure 4.1 Common Error Message That Does Not Require Action........................................ 4-1 4.2 Common Errors Which Require Action............ 4-1 4.3 Failure During Postinstallation............... 4-2 4.4 Installation Failure.......................... 4-3 4.4.1 Failure of Upgrade Installations in Safety Mode...................................... 4-3 4.4.2 Failure of Upgrade Installations in Non-Safety Mode........................... 4-4 4.4.3 Full Installations........................ 4-4 4.4.4 Failure Due to Insufficient Dynamic Memory.................................... 4-4 4.5 Error Messages when Running the IVP........... 4-4 4.6 IVP Failure................................... 4-6 5 Postinstallation Tasks 5.1 Checklist of Manual Postinstallation Tasks.... 5-1 5.2 Start ALL-IN-1 on all Nodes in a VMScluster System........................................ 5-5 5.3 Create or Modify the Site-specific ALL-IN-1 Startup Procedure............................. 5-6 5.4 Edit the Site-specific Startup Procedure...... 5-7 5.4.1 Installations With Digital X.500 and the MAILbus 400 MTA........................... 5-7 5.4.2 Installations with Message Router......... 5-8 5.5 Replace the DCLTABLES on Cluster Systems...... 5-9 5.6 Delete Files That Are No Longer Required...... 5-9 5.7 Install Missing Images........................ 5-10 5.8 Recompile Form Libraries...................... 5-10 5.9 Migrate SITELINK31 Using Customization Management.................................... 5-11 v 5.10 Migrating Your Customizations After Upgrading..................................... 5-11 5.10.1 Running the CART Resolution Procedure..... 5-13 5.10.2 Deleting Obsolete Files................... 5-14 5.10.3 Restoring Customizations to Data Files.... 5-15 5.10.4 Replacing the Help Modules for Your Application............................... 5-15 5.11 Link ALL-IN-1 to Include Code-level Customizations................................ 5-16 5.12 Check Entries in RIGHTSLIST.DAT............... 5-16 5.13 Setting up Remote Mail When Using the MAILbus 400 MTA....................................... 5-16 5.14 Setting up Remote Mail When Using Message Router........................................ 5-17 5.14.1 Create a Mailbox for ALL-IN-1............. 5-18 5.14.2 Modifying the Message Router Mailbox Entry..................................... 5-20 5.14.3 Configuring the VMSmail Gateway for Remote Access.................................... 5-20 5.14.4 Setting Up the Message Router Directory Service as the Mail Directory............. 5-21 5.14.4.1 Message Router is in the Same VMScluster.............................. 5-21 5.14.4.2 Message Router is not in the Same VMScluster.............................. 5-25 5.14.5 Remote Message Router Directory Service Startup Procedure......................... 5-29 5.15 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1 ..................................... 5-29 5.16 WPS-PLUS Login Command Procedure.............. 5-31 5.17 Install the File Cabinet Server Distributed License....................................... 5-32 5.18 Moving the CDA DOC_STYLE Files................ 5-32 5.19 Update the Facility Definition to Use DECtrace...................................... 5-32 vi A ALL-IN-1 Version 3.2 Distribution Media A.1 CD-ROM Distribution Kits (VAX or Alpha Installations)................................ A-1 A.2 Magnetic Tape and TK50 Kits (VAX Upgrades).... A-3 B ALL-IN-1 Version 3.2 Files and Directories B.1 Files in the ALL-IN-1 Kit..................... B-1 B.2 Files Installed in Non-ALL-IN-1 Directories... B-1 Index Tables 1-1 Preinstallation Checklist................. 1-2 1-2 Prerequisite and Optional Software........ 1-9 1-3 Process Account Quotas for the Installing Account................................... 1-19 1-4 Minimum System Parameter Values Required.................................. 1-20 1-5 Changing System Parameter Values.......... 1-24 1-6 New Installation: Disk Space for ALL-IN-1 Areas..................................... 1-30 1-7 Upgrade Installations: Disk Space for ALL-IN-1 Areas ........................... 1-31 1-8 Addition, Upgrade or Update of Architecture Support: Disk Space for ALL-IN-1 Areas............................ 1-32 1-9 Installed Images Required on VAX.......... 1-32 1-10 Installed Images Required on Alpha........ 1-34 2-1 Information About the Installation Procedure................................. 2-2 2-2 Installation Procedure for New and Upgrade Installations............................. 2-4 2-3 When to Install/Upgrade VAX or Alpha Architecture Support...................... 2-30 2-4 Installation Procedure for Adding Architecture Support...................... 2-32 3-1 Installation Procedure for An Additional Language ................................. 3-3 vii 3-2 Installation Procedure for Addition of Architecture Support for an Additional Language.................................. 3-10 5-1 Postinstallation Tasks.................... 5-1 5-2 Editing the OpenVMS Site-specific Startup File...................................... 5-8 5-3 Tasks for Setting up Remote Mail.......... 5-17 viii _________________________________________________________________ Preface About This Book Before you use this book, you must plan your ALL-IN-1[TM] Version 3.2 installation by reading the ALL-IN-1 Overview and Planning Guide. This guide describes how to do the following: 1. Prepare your system for an ALL-IN-1 Version 3.2 installation. 2. Install ALL-IN-1 Version 3.2. 3. Set up ALL-IN-1 Version 3.2 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.2 kit, and information on the language and market components that you will need during the installation. Prerequisite Knowledge This guide assumes that you have read the ALL-IN-1 Overview and Planning Guide. To install ALL-IN-1 Version 3.2 you must be familiar with the VMSINSTAL utility. ix The ALL-IN-1 Management Documentation Set The following guides form the ALL-IN-1 management documentation set: o ALL-IN-1 Overview and Planning Guide o ALL-IN-1 Installation: Guide o ALL-IN-1 Installation: Language and Market Supplement o ALL-IN-1 Management Guide o ALL-IN-1 Mail Management Guide o ALL-IN-1 Managing Servers Terminology and Conventions Used in this Guide The following table lists the terminology and conventions used in this guide. ___________________________________________________________ Term____________Description________________________________ AIDA Server The ALL-IN-1 Distributed Access Server ALL-IN-1 Means the ALL-IN-1 software that is provided by the ALL-IN-1 Office Service Option that you have installed. For example, the ALL-IN-1 Integrated Office System (IOS) or the ALL-IN-1 Core Services. architecture Used to differentiate between OpenVMS[TM] VAX[TM] systems and OpenVMS Alpha systems. For example, architecture-independent files are files that can be used on both VAX and Alpha systems. _AXP Used to show ALL-IN-1 directories that are specific to Alpha systems. _VAX is used to show directories that are specific to VAX systems. Digital[TM] Means the Digital X.500 Directory Service X.500 product IOS Integrated Office System. This is the full ALL-IN-1 license that includes all components of the product. x ___________________________________________________________ Term____________Description________________________________ MAILbus[TM] Means the MAILbus 400 Message Transfer 400 MTA Agent mixed a VMScluster[TM] that contains both Alpha architecture and VAX nodes. cluster OpenVMS Alpha Means the OpenVMS Alpha operating system OpenVMS VAX Means the OpenVMS VAX operating system TCP/IP Transmission Control Protocol/Internet Protocol TLC TeamLinks[TM] Connection to ALL-IN-1 Integrated Office System for OpenVMS UCX Means DEC[TM] TCP/IP Services for OpenVMS VMScluster Discussions that refer to VMScluster environments apply to both VAXcluster[TM] systems that include only VAX nodes and VMScluster systems that include at least one Alpha node. Any differences are noted in the text. WPS-PLUS________WPS-PLUS[TM]_software._____________________ Related Documents You may also need to refer to the documentation on the following products: o VAX Message Router and its Gateways o DEC Notes[TM] o OpenVMS system management o The MAILbus 400 MTA and its Gateways o Digital X.500 o DECnet[TM]/OSI xi Returning Comments About This Guide If you have any comments or suggestions about this guide, please return them in one of the following ways: o Internet address: books@reo.mts.dec.com o X.400 address: C=GB;A=CWMAIL;P=DIGITAL;O=DIGITAL;OU1=REO;S=BOOKS;G=IDC; o Fax: (+44) 1734 206018 xii 1 _________________________________________________________________ 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.2 installation. The information in this chapter applies to all installations. You must read the ALL-IN-1 Overview and Planning Guide before you install ALL-IN-1 Version 3.2. The planning guide covers: o Information about this version of ALL-IN-1 o Mail system planning o Installation planning, including a checklist of all the decisions that you need to make before starting the installation In addition, if you are upgrading from ALL-IN-1 Version 3.1 and your system has been customized, you must read the chapter Planning the Upgrade of a Customized System in the Overview and Planning guide. This chapter explains how to run the Conflict Checking and Resolution Tool (CART) to check your customizations before you upgrade to ALL-IN-1 Version 3.2. This installation guide assumes that you have read the ALL-IN-1 Overview and Planning Guide, made all your planning decisions and know what type of installation you are going to perform. Preparing Your System for Installation 1-1 Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks 1.1 Checklist of Preinstallation Tasks To prepare your system for an ALL-IN-1 Version 3.2 installation, you must do the tasks listed in Table 1-1. Table_1-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. ___________________________________________________________ 2 Read the READ ME FIRST letter if one is supplied with your kit ___________________________________________________________ 3 Make sure that you have ALL-IN-1 Overview and planned your installation Planning Guide and ALL-IN-1 mail system. The ALL-IN-1 Overview and Planning Guide also lists any prerequisite configuration tasks that must be done for the messaging products that you plan to use with ALL-IN-1. These tasks must be completed before you start your installation. ___________________________________________________________ (continued on next page) 1-2 Preparing Your System for Installation Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks Table_1-1_(Cont.)_Preinstallation_Checklist________________ For further information, Task___Description________________see______________________ 4 Read the online product Section 1.2 for release notes provided instructions on accessing with the kit the release notes. ___________________________________________________________ 5 Check that you have the Section 1.3 correct versions of: o The prerequisite software for the installation o Any optional software that you want to install ___________________________________________________________ 6 Check that you have a Section 1.4 valid license for the installing account ___________________________________________________________ 7 Register the ALL-IN-1 Section 1.5 Version 3.2 License Product Authorization Key (PAK) ___________________________________________________________ 8 Register the License Section 1.5.3 PAKs for the prerequisite and optional software provided with ALL-IN-1 Version 3.2. ___________________________________________________________ (continued on next page) Preparing Your System for Installation 1-3 Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks Table_1-1_(Cont.)_Preinstallation_Checklist________________ For further information, Task___Description________________see______________________ 9 Check the installation Section 1.7 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 ___________________________________________________________ 10 For upgrade Section 1.8. installations, do any additional tasks. ___________________________________________________________ (continued on next page) 1-4 Preparing Your System for Installation Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks Table_1-1_(Cont.)_Preinstallation_Checklist________________ For further information, Task___Description________________see______________________ 11 Check that all Section 1.3 lists prerequisite and optional prerequisite and optional software is installed, software. In addition, configured and running you may want to install before you start the DATATRIEVE[TM] or ALL-IN-1 Version 3.2 ACMS[TM] if you are installation. planning to use these products with ALL-IN-1. All prerequisite messaging products such as Message Router or the MAILbus 400 MTA and Digital X.500 must be installed, configured and running before you install ALL-IN-1. See the ALL-IN-1 Overview and Planning Guide. For a suggested order of installing optional software, see Section 1.6. ___________________________________________________________ 12 If you are installing Section 1.9 a new ALL-IN-1 system with Digital X.500 and the MAILbus 400 MTA, check that these products have been installed and configured correctly. ___________________________________________________________ (continued on next page) Preparing Your System for Installation 1-5 Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks Table_1-1_(Cont.)_Preinstallation_Checklist________________ For further information, Task___Description________________see______________________ 13 If you will be using a Section 1.10. remote Message Router that is not in the same VMScluster, do any additional tasks. ___________________________________________________________ 14 It is recommended that Section 1.11 you run the Perform all preinstallation checks (PC) option to check that your system is prepared for the installation. The PC option runs through the installation to check that you have all the prerequisite licenses, software, disk space and installation parameters correctly set up on your system. ___________________________________________________________ 15 Do the final system Section 1.12 for new preparation tasks. installations and Section 1.13 for upgrade installations. ___________________________________________________________ 16 Back up your system and Section 1.14 _______target_disks._______________________________________ 1.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.2. The release notes contain information that was unavailable before the books went to print. It is recommended that you read 1-6 Preparing Your System for Installation Preparing Your System for Installation 1.2 Reading and Printing the Online Release Notes 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.2 software. There are two parts to the ALL-IN-1 Version 3.2 release notes: o Release Notes Part 1 Language This part contains the release notes specific to the ALL-IN-1 Version 3.2 language being installed. o Release Notes Part 2 Market This part contains the release notes specific to your ALL-IN-1 Version 3.2 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 A1Llang032 for the Release Notes Part 1 Language, where lang is the 2-letter code for the language you are installing o A1Cmarket032 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 A1Llang032.RELEASE_NOTES, 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 1-7 Preparing Your System for Installation 1.2 Reading and Printing the Online Release Notes o A1Cmarket032.RELEASE_NOTES, for the Release Notes Part 2 Market, where market is the 2-letter code for the market component you are installing 1.3 Checking Prerequisite and Optional Software Table 1-2 provides information about the prerequisite software for an ALL-IN-1 Version 3.2 installation. It also lists the software that is supplied with the ALL-IN-1 Version 3.2 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.2. 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.2 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. ________________________ Note ________________________ Both the prerequisite software, and any optional software that you want to install, must be installed, configured and running before you install ALL-IN-1 Version 3.2. ______________________________________________________ 1-8 Preparing Your System for Installation Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_Prerequisite_and_Optional_Software_______________ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes______________ OpenVMS VAX 6.1 or - N Prerequisite for higher installation on VAX. Must be a full untailored system OpenVMS Alpha - 6.1 N Prerequisite for or installation on higher Alpha. Must be a full untailored system ___________________________________________________________ DECnet-VAX 5.5 - N Prerequisite for end-node remote messaging using Message Router DECnet for - 1.5 N Prerequisite for OpenVMS Alpha remote messaging using Message Router (continued on next page) Preparing Your System for Installation 1-9 Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes______________ DECnet/OSI for 6.1 or 6.1 N Prerequisite[1] OpenVMS higher or for systems using higher Digital X.500 or Digital X.500 and the MAILbus 400 MTA. Optional alternative for systems using Message Router. ___________________________________________________________ VAX Forms 2.4 - Y Prerequisite Management System (FMS)[2] DEC Forms - 2.4 Y Prerequisite Management System (FMS)[2] ___________________________________________________________ [1]DECnet/OSI_is_a_prerequisite_for_Digital_X.500._If______ you plan to migrate to use Message Router with Digital X.500, you must install DECnet/OSI as the prerequisite for Digital X.500. For Digital X.500, you must also install the OSI Applications Kernel, OSAK[TM], from the DECnet/OSI Applications component. See the Digital X.500 installation documentation for more information. [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) 1-10 Preparing Your System for Installation Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes______________ DEC TCP/IP 3.1 or 3.1 N Optional. Services for higher or Install if you want OpenVMS (UCX) higher to use the TCP/IP or other TCP/IP network protocol software that to communicate emulates UCX[3] with client applications. ___________________________________________________________ Message Router 3.3A - Y Optional. Install and configure if you want to send remote mail using Message Router. ___________________________________________________________ Message Router 3.3 - Y Optional VMSmail Gateway Install if you want to send mail from ALL-IN-1 systems using Message Router to VMSmail users. ___________________________________________________________ [3]For_supported_versions_of_other_TCP/IP_software_________ that emulates UCX, see the ALL-IN-1 Software Product Description. (continued on next page) Preparing Your System for Installation 1-11 Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes______________ MAILbus 400 1.4A 1.4A N Optional MTA[4] Install and configure if you want to use the MAILbus 400 MTA for remote mail. Note that Digital X.500 is a prerequisite for the MAILbus 400 MTA. ___________________________________________________________ Digital 3.0 3.0 N Prerequisite if X.500[5] you plan to use the MAILbus 400 MTA. Optional if you plan to continue using Message Router. ___________________________________________________________ [4]_ALL-IN-1_can_also_connect_to_a_MAILbus_400_MTA_________ installed on a remote Digital UNIX node. [5]DECnet/OSI is a prerequisite for Digital X.500. If you plan to migrate to use Message Router with Digital X.500, you must install DECnet/OSI as the prerequisite for Digital X.500. For Digital X.500, you must also install the OSI Applications Kernel, OSAK[TM], from the DECnet/OSI Applications component. See the Digital X.500 installation documentation for more information. (continued on next page) 1-12 Preparing Your System for Installation Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes______________ MAILbus 400 1.2 - N Optional Message Router Install if you want Gateway to exchange mail between Message Router systems and MAILbus 400 MTA systems. ___________________________________________________________ DEC Notes 2.5 2.5 Y Optional. Install if you want to use Group Conferencing. ___________________________________________________________ CDA Converter 2.2 - N Optional Library[6] Install if you require full CDA support on OpenVMS VAX. DECwindows[R][7] - 1.2 N Optional or Install if you higher require full CDA support on OpenVMS Alpha. [6]The_installation_procedure_checks_for___________________ SYS$SHARE:CDA$ACCESS.EXE, Version 1.7 [7]The installation procedure checks for SYS$SHARE:CDA$ACCESS.EXE, Version 1.8 ___________________________________________________________ For information about the order of installing optional software, see Section 1.6. For a list of all supported versions of products that can be used with ALL-IN-1, see the ALL-IN-1 Software Product Description. Preparing Your System for Installation 1-13 Preparing Your System for Installation 1.4 Checking the License for the Installing Account 1.4 Checking the License 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. 1.5 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.2 software. The installation procedure checks for a registered ALL-IN-1 Version 3.2 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 an ALL-IN-1 license PAK for a new installation, see Section 1.5.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.2 kit. See Section 1.5.3. ________________________ Note ________________________ You must make sure that all the License PAKs are registered on all nodes on which you intend to use the software. For products that are not included in the ALL-IN-1 kit, for example the MAILbus 400 MTA or Digital X.500, 1-14 Preparing Your System for Installation Preparing Your System for Installation 1.5 Registering License Product Authorization Keys (PAKs) you must register the license PAKS manually using the License Management Facility (LMF). ______________________________________________________ 1.5.1 Registering the ALL-IN-1 License PAK Before a new Installation If you are installing ALL-IN-1 Version 3.2 on a newly- licensed node or cluster, you must register a License PAK for ALL-IN-1 Version 3.2 before you install ALL-IN-1 Version 3.2. 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.2 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. 1.5.2 Registering the ALL-IN-1 License PAK Before an Upgrade If you are installing ALL-IN-1 Version 3.2 as an upgrade or update installation on a node or cluster already licensed for this software, you must register the Service Update PAK (SUP) that is included in your Service Update Kit. If you have already registered a License PAK or a SUP for this product on this node or cluster, you do not need to register the SUP. If you are installing an update of ALL-IN-1 Version 3.2 but lack a service contract, call your Digital representative for instructions on how to get a License PAK. Preparing Your System for Installation 1-15 Preparing Your System for Installation 1.5 Registering License Product Authorization Keys (PAKs) 1.5.3 Registering License PAKs for Software Provided with ALL-IN-1 Version 3.2 When you have registered the ALL-IN-1 Version 3.2 License PAK, you must register the License PAKS for the products supplied with the ALL-IN-1 Version 3.2 kit. The following License PAKs can be registered automatically using the ALL-IN-1 Version 3.2 installation procedure: ___________________________________________________________ VAX________________________Alpha___________________________ VAX FMS DEC FMS DEC Notes[1] DEC Notes[1] Message Router - Message Router VMSmail - Gateway CDA Converter Library - [1]If_your_ALL-IN-1_license_does_not_include_Group_________ Conferencing,_the_DEC_Notes_PAK_is_not_registered._________ 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.2 kit. The ALL-IN-1 Version 3.2 License PAK must be registered first. To register the License PAKs automatically, follow Steps 1 to 5 in Table 2-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.2 kit. The installation then terminates. 1-16 Preparing Your System for Installation Preparing Your System for Installation 1.5 Registering License Product Authorization Keys (PAKs) For prerequisite or optional products that are not supplied with ALL-IN-1, you must register the license PAKs manually using the License Management Facility (LMF). 1.6 Example Order for Installing Optional Software After you have installed and configured 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.2 installation: 1. Install ACMS[TM] 2. Install VAX DATATRIEVE[TM] or DEC DATATRIEVE 3. Install and configure your message transport and directory service software. o For new or upgrade installations with Message Router, make sure that Message Router is installed, configured and running before you start the ALL-IN-1 installation. If you plan to use a remote Message Router Directory Service, you must do a customized Message Router configuration to enable remote Directory Service access and configure Message Router exception reporting for the Directory Service and Transfer Service according to your planning decisions. o For new installations with Digital X.500 and the MAILbus 400 MTA make sure that you have installed and configured all the required components on your ALL-IN-1 node or cluster. Digital X.500 and the MAILbus 400 MTA must be correctly installed, configured and running before you start the new ALL-IN-1 installation. See the MAILbus 400 MTA and Digital X.500 Planning chapter in the ALL-IN-1 Overview and Planning Guide. 4. Install and configure optional gateway products. o The Message Router VMSmail Gateway if required with Message Router. Preparing Your System for Installation 1-17 Preparing Your System for Installation 1.6 Example Order for Installing Optional Software o The MAILbus 400 Message Router Gateway if required with the MAILbus 400 MTA. o The MAILbus 400 SMTP Gateway if required with the MAILbus 400 MTA. 5. Install DEC Notes. 1.7 Installation Procedure Requirements This section describes the requirements for installing ALL-IN-1 Version 3.2. It explains how to check the values and how to change them if necessary. 1.7.1 Installing Account Requirements Use the SYSTEM account to install ALL-IN-1 Version 3.2. 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 1-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.2 the process quotas are set to the appropriate values. See the ALL-IN-1 Management Guide. 1-18 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-3_Process_Account_Quotas_for_the_Installing_Account Account Quota_________VAX_________Alpha_______Notes________________ BYTLM 64 000 64 000 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_________________________ 1.7.2 System Parameters Table 1-4 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you may need higher values for some settings. If necessary, modify the parameters to at least these values. ________________________ Note ________________________ You must check the OpenVMS system parameters on each node in the cluster on which you install ALL-IN-1 Version 3.2. ______________________________________________________ The values for the system parameters and quotas given in this section are those specific to ALL-IN-1 Version 3.2 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. Preparing Your System for Installation 1-19 Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-4_Minimum_System_Parameter_Values_Required_______________ System Parameter_____VAX_________________Alpha__________________________ CTLPAGES 100 100 _________________________________________________________________ GBLSECTIONS 250 (new) 250 (new) 50 (upgrade) 50 (upgrade) _________________________________________________________________ GBLPAGES 20000 (new) 35000 (new) 5000 (upgrade) 5000 (upgrade) _________________________________________________________________ GBLPAGFIL For new For new installations: installations: 1. Add 1 to the number of 1. Add 1 to the active users. There is an number of upper limit of 200 for this active users. value, so use 200 if your There is an value is greater than 200. upper limit 2. Add 32 of 200 for this value, so use 200 if your value is greater than 200. 2. Multiply your value by 16. 3. Add 500 ___________________________________________________ (continued on next page) 1-20 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-4_(Cont.)_Minimum_System_Parameter_Values_Required_______ System Parameter_____VAX_________________Alpha__________________________ GBLPAGFIL For upgrade For upgrade installations: installations: 1. Add together the number of 1. Add together global buffers[3] on the the number following files in OA$DATA_ of global SHARE: buffers[3] on o ATTENDEE.DAT the following files in o MEETING.DAT OA$DATA_SHARE: o PENDING.DAT o ATTENDEE.DAT o PROFILE.DAT o MEETING.DAT 2. Add the total from Step 1 to o PENDING.DAT the number of global buffers o PROFILE.DAT in the shared document attributes files, OA$DAF_ 2. Add the total n.DAT in OA$SHARn, where n from Step 1 to is a letter from A to E. the number 3. Divide the total by 4 to of global convert to global pages buffers in the shared document 4. Add 32 attributes files, OA$DAF_ n.DAT in OA$SHARn, where n is a letter from A to E. 3. Multiply the total by 4 to convert to global pages 4. Add 500 [3]To_find_the_number_of_global_buffers_do_a_DIR/FULL_for_each___ file. (continued on next page) Preparing Your System for Installation 1-21 Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-4_(Cont.)_Minimum_System_Parameter_Values_Required_______ System Parameter_____VAX_________________Alpha__________________________ _________________________________________________________________ LOCKIDTBL 100 multiplied 100 multiplied by the number of by the number of users active users _________________________________________________________________ MAXBUF (D) 5000 5000 _________________________________________________________________ MAXPROCESSCNT 50 plus the number 50 plus the number of active of active users users _________________________________________________________________ RESHASHTBL 50 multiplied 50 multiplied by the number of by the number of active users active users _________________________________________________________________ SCSNODE Must be the same Must be the same as the DECnet as the DECnet node node name name _________________________________________________________________ SCSSYSTEMID DECnet area number DECnet area number multiplied multiplied by by 1024, plus the DECnet node 1024, plus the number DECnet node number _________________________________________________________________ VIRTUALPAGECNT16]384 pages[5] 250 000 pagelets [4]A_high_value_of_VIRTUALPAGECNT_is_required_when_running_the___ File Cabinet test and repair procedure (FCVR program). [5]This value is approximately the same as 250 000 pagelets. _________________________________________________________________ ________________________ Note ________________________ For the majority of installations, the values for CTLPAGES are sufficient. If you are planning to reboot 1-22 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements your system to change other system parameters, you can increase the value to 200 for the duration of the installation. ______________________________________________________ 1.7.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 1-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. 1.7.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 1-5. 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. Preparing Your System for Installation 1-23 Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-5_Changing_System_Parameter_Values_________________ To change the following parameters_______Do_the_following__________________________ SCSNODE Edit SYS$SYSTEM:MODPARAMS.DAT and specify SCSSYSTEMID new parameter values. Use assignment statements of the form: parameter = parameter-value where parameter is the name of the parameter you want to change and parameter-value is the setting you want to change it to. See Table 1-4 for the 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 (D) where parameter is the name of the MAXPROCESSCNT parameter you want to change, and RESHASHTBL increase-value is the amount by which VIRTUALPAGECNT you want to increase the setting of this parameter. For example, to increase the value of LOCKIDTBL by 60, enter: ADD_LOCKIDTBL=60 _________________See_Table_1-4_for_the_required_values.____ If you change any of the system parameter values, you must update them using AUTOGEN. See Section 1.7.4.1 and Section 1.7.4.2. 1-24 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements 1.7.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. 1.7.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 1-25 Preparing Your System for Installation 1.7 Installation Procedure Requirements 1.7.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.2 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.2 will be installed. See Section 1.7.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.2 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.2 kit on your system disk. The disk space values for installing your kit in safety mode are given in the ALL-IN-1 Installation: Language and Market Supplement. 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.2 kit. The disk space values for installing your kit in non-safety mode are given in the ALL-IN-1 Installation: Language and Market Supplement. 1-26 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements 1.7.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. 1.7.7 Disk Space for ALL-IN-1 Areas on Target Disks You can install ALL-IN-1 Version 3.2 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 ALL-IN-1 Overview and Planning Guide 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 1-6 for a new installation. See Section 1.7.9. Preparing Your System for Installation 1-27 Preparing Your System for Installation 1.7 Installation Procedure Requirements o Table 1-7 for an upgrade installation. See Section 1.7.10. o Table 1-8 for the addition, upgrade or update of VAX or Alpha architecture support. See Section 1.7.11. These values can also be used for the addition, upgrade or update of architecture support for an additional language. You are prompted to specify the target disks for each ALL-IN-1 area during the installation. 1.7.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 1.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 1-28 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements fix the problem and then restart it. The installation will not continue until the logical name checking has passed. 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. 1.7.9 New Installation: Disk Space for ALL-IN-1 Areas Table 1-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 6000 blocks. If you choose to integrate WPS-PLUS, but without the associated PostScript[R] files, you can decrease the disk space in the shared library area by approximately 3000 blocks. ______________________________________________________ Preparing Your System for Installation 1-29 Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-6_New_Installation:_Disk_Space_for_ALL-IN-1_Areas__ ALL-IN-1_Area_for__________VAX_________Alpha_______________ System disk files[1] 21 000 61 000 Shared library files 55 000 86 000 Shared data files 12 500 12 500 Shared areas[2] 1000 1000 ALL-IN-1 Manager 1000 1000 account[3] [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. [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. ______________________________________________________ 1.7.10 Upgrade Installation: Disk Space for ALL-IN-1 Areas Table 1-7 gives the disk space requirements for upgrading 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. 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 1-6. 1-30 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements ________________________ 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 5000 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 2000 blocks. ______________________________________________________ Table 1-7 Upgrade Installations: Disk Space for ALL-IN-1 __________Areas____________________________________________ ALL-IN-1_Area_for__________VAX_________Alpha_______________ System files[1] 10 500 61 000 Shared library files 11 000 86 000 Shared data files 2000 2000 [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 ___________________________________________________________ For the disk space values for the primary language files, see the ALL-IN-1 Installation: Language and Market Supplement. 1.7.11 Addition of Architecture Support: Disk Space for ALL-IN-1 areas Table 1-8 gives the disk space requirements for adding, upgrading or updating architecture support on the system and ALL-IN-1 target disks. These values also apply to the addition, upgrade or update or architecture support for an additional language. Preparing Your System for Installation 1-31 Preparing Your System for Installation 1.7 Installation Procedure Requirements Table 1-8 Addition, Upgrade or Update of Architecture __________Support:_Disk_Space_for_ALL-IN-1_Areas___________ ALL-IN-1_Area_for__________VAX___________Alpha_____________ System files[1] 21 000 61 000 Shared library files 37 000 73 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. 1.7.12 Disk Quota Allocation If disk quota is enabled, the installation procedure adds sufficient disk quota for accounts and identifiers created during the installation. 1.7.13 Installed Images Make sure that the shareable image and message files listed in Table 1-9 are installed on your VAX system and Table 1-10 are installed on your Alpha system before you install ALL-IN-1. Note that this list of required images applies to the versions of the products listed in Table 1-2. Table_1-9_Installed_Images_Required_on_VAX_________________ Product_______Image_Required_on_VAX________________________ Always SYS$SHARE:CONVSHR.EXE required SYS$SHARE:CMA$TIS_SHR.EXE SYS$SHARE:DECC$SHR.EXE SYS$SHARE:FDLSHR.EXE SYS$MESSAGE:FDVMSG.EXE (continued on next page) 1-32 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-9_(Cont.)_Installed_Images_Required_on_VAX_________ Product_______Image_Required_on_VAX________________________ SYS$SHARE:FDVSHR.EXE[1] SYS$SHARE:LBRSHR.EXE SYS$SHARE:LIBRTL.EXE SYS$SHARE:MTHRTL.EXE[2] SYS$SHARE:PASRTL.EXE SYS$SHARE:PLIRTL.EXE SYS$SHARE:SCRSHR.EXE SYS$SHARE:VAXCRTL.EXE SYS$SHARE:VMSRTL.EXE ___________________________________________________________ ACMS SYS$SHARE:ACMSHR.EXE ___________________________________________________________ CDA SYS$SHARE:CDA$ACCESS.EXE SYS$SHARE:IMG$SHRLIB_NOX.EXE SYS$SHARE:DDIF$CC_VIEWSHR.EXE ___________________________________________________________ DATATRIEVE SYS$SHARE:DTRSHR.EXE (the standard). If you are using another DATATRIEVE image that you want to link with ALL-IN-1, you must make sure that image is installed before the installation. SYS$SHARE:CDDSHR.EXE SYS$MESSAGE:DTRMSGS.EXE SYS$SHARE:CDDEXC.EXE ___________________________________________________________ DEC Notes SYS$SHARE:NOTES$SHARE.EXE [1]This_is_a_language-specific_image_which_can_have_a______ different name on other language versions. [2]For certain processors, the logical is defined to point to SYS$SHARE:UVMTHRTL.EXE (continued on next page) Preparing Your System for Installation 1-33 Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-9_(Cont.)_Installed_Images_Required_on_VAX_________ Product_______Image_Required_on_VAX________________________ ___________________________________________________________ Digital SYS$SHARE:DXD$DUA_SHR.EXE X.500 SYS$SHARE:DXD$XDS_SHR.EXE ___________________________________________________________ The MAILbus SYS$SHARE:MTA$XAPI_SHR.EXE 400 MTA ___________________________________________________________ Message SYS$SYSTEM:MRTALK.EXE Router ___________________________________________________________ TCP/IP________SYS$SHARE:UCX$IPC_SHR.EXE____________________ Table_1-10_Installed_Images_Required_on_Alpha______________ Product__________Image_Required_on_Alpha___________________ Always required SYS$SHARE:CONVSHR.EXE SYS$SHARE:CMA$TIS_SHR.EXE SYS$SHARE:DECC$SHR.EXE SYS$SHARE:DPML$SHR.EXE SYS$SHARE:FDLSHR.EXE SYS$MESSAGE:FDVMSG.EXE SYS$SHARE:FDVSHR.EXE[1] SYS$SHARE:LBRSHR.EXE SYS$SHARE:LCI$SHARE_TV.EXE SYS$SHARE:LIBOTS.EXE SYS$SHARE:LIBRTL.EXE [1]This_is_a_language-specific_image_which_can_have_a______ different name on other language versions. (continued on next page) 1-34 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-10_(Cont.)_Installed_Images_Required_on_Alpha______ Product__________Image_Required_on_Alpha___________________ SYS$SHARE:LIBRTL_TV.EXE[2] SYS$SHARE:MTHRTL_TV.EXE[2] SYS$SHARE:PAS$RTL.EXE SYS$SHARE:SCRSHR.EXE SYS$SHARE:SECURESHR.EXE SYS$SHARE:SECURESHRP.EXE SYS$SHARE:SMGSHR.EXE SYS$SHARE:TIE$SHARE.EXE SYS$SHARE:VAXCRTL_TV.EXE[2] SYS$SHARE:VMS$IEEE_HANDLER.EXE ___________________________________________________________ ACMS SYS$SHARE:ACMSHR.EXE ___________________________________________________________ CDA SYS$SHARE:CDA$ACCESS.EXE SYS$SHARE:DDIF$CC_VIEWSHR.EXE SYS$SHARE:IMG$SHRLIB_NOX.EXE ___________________________________________________________ DATATRIEVE SYS$SHARE:DTRSHR.EXE (the standard). If you are using another DATATRIEVE image that you want to link with ALL-IN-1, you must make sure that image is installed before the installation. SYS$SHARE:CDDSHR.EXE SYS$MESSAGE:DTRMSGS.EX SYS$SHARE:CDDEXC.EXE ___________________________________________________________ DEC Notes SYS$SHARE:NOTES$SHARE.EXE [2]This_is_a_logical_which_typically_translates_to_________ something like the following example: LIBRTL_D56_TV.EXE (continued on next page) Preparing Your System for Installation 1-35 Preparing Your System for Installation 1.7 Installation Procedure Requirements Table_1-10_(Cont.)_Installed_Images_Required_on_Alpha______ Product__________Image_Required_on_Alpha___________________ ___________________________________________________________ Digital X.500 SYS$SHARE:DXD$DUA_SHR.EXE SYS$SHARE:DXD$XDS_SHR.EXE ___________________________________________________________ MAILbus 400 MTA SYS$SHARE:MTA$XAPI_SHR.EXE ___________________________________________________________ TCP/IP___________SYS$SHARE:UCX$IPC_SHR.EXE_________________ 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 SYS$MESSAGE:FDVMSG.EXE and SYS$SHARE:FDVSHR.EXE, see Section 1.7.14. o Other images, see Section 1.7.15. For more information about installing images, see the manual describing the Install Utility. 1.7.14 Installing FDVMSG.EXE and FDVSHR.EXE Images If the images SYS$MESSAGE:FDVMSG.EXE and SYS$SHARE: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 1-36 Preparing Your System for Installation Preparing Your System for Installation 1.7 Installation Procedure Requirements 2. Execute the command procedure SYS$STARTUP:FMSTARTUP.COM 1.7.15 Installing Other Images Install other images as follows: $ INSTALL INSTALL> CREATE imagename /OPEN /SHARED /HEADER_RES INSTALL> EXIT 1.7.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 1.8 Additional Tasks for Upgrade Installations If you are upgrading an existing ALL-IN-1 system, do the following: 1. Review your object libraries. Your object libraries may have been updated if you installed layered products. ALL-IN-1 provides two template .OLB files in the following directories: - OA$SITE_BUILD_SHARE:SITEOALIBR.OLB - OA$SITE_BUILD_LLV:SITEOALLV.OLB During the installation, a warning is displayed if there are additional .OBJ or .OLB files in these directories. Check that any additional object libraries or files in this directory are compatible with ALL-IN-1 Version 3.2. Remove any object libraries or files that are not Preparing Your System for Installation 1-37 Preparing Your System for Installation 1.8 Additional Tasks for Upgrade Installations compatible. Although these files are not used during the installation, they will cause problems if you need to relink ALL-IN-1 after the installation. 2. 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. 3. 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). 4. Make copies of customized data files. See Section 1.8.1. 1.8.1 Copying Customized Data Files ALL-IN-1 Version 3.2 uses modified versions of several data files: o In the base area: - A1CONFIG.DAT - OA$PC_NOTIFY.DAT (a secondary key has been added) - PROFILE.DAT - SM_ACCOUNT_TYPES.DAT (The form is SMTEMPLATE) o In the language areas: - FORMAT.DAT (New records have also been added) - OA$PRINTSTYLES.DAT (The form is SMPRINTERTYPES and new records have also been added) o In users' areas: - OA$USERPRINTERSTYLES.DAT (The form is USERPRINTSTYLES) o Files which have not been converted but their record layouts have changed: - ATTENDEE.DAT - DOCDB.DAT 1-38 Preparing Your System for Installation Preparing Your System for Installation 1.8 Additional Tasks for Upgrade Installations o Files which have not been converted but their records have changed or new ones have been added: o CM$SDC o CM$CART$RUNS.DAT o OA$SM_UTILITY_MASTER o X400COUNTRY_CODES.DAT This file has been replaced by a new one with additional records. ALL-IN-1 Version 3.2 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.2. 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 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 and FORM_SET directives specify the location of the backup copy of the file. The following example shows the parts of the named data that must be modified. ;;.FILE;; OA$DATA_SHARE:PROFILE.DAT,OA$LIB:PROFILE.FDL ;;.FORM_SET;; PROFIL2,PROFIL3,PROFIL4,PROFIL5,PROFIL6,PROFIL7,PROFIL8 3. Make the copies of the customized forms live. Preparing Your System for Installation 1-39 Preparing Your System for Installation 1.8 Additional Tasks for Upgrade Installations 4. Remove the customized PROFILn forms and PROFIL.FDL from the live area. 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. Preparing Your System for Installation 1-41 Preparing Your System for Installation 1.11 Running the Preinstallation System Check 1.11 Running the Preinstallation System Check The ALL-IN-1 Version 3.2 installation procedure provides a Perform all preinstallation checks (PC) option. Digital recommends that you use this option before installing ALL-IN-1 Version 3.2 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 1.11.1 describes the types of errors that are detected. Section 1.11.2 describes how to use the Perform all preinstallation checks (PC) option. 1.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, or Digital X.500, the MAILbus 400 MTA and Message Router Gateway. o Non-fatal errors 1-42 Preparing Your System for Installation Preparing Your System for Installation 1.11 Running the Preinstallation System Check 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 1.11.2 Running the Perform all Preinstallation Checks (PC) Option To run the Perform all preinstallation checks (PC) option, follow Steps 1 to 6 in Table 2-2 until you are prompted with a list of installation options. Do the following: 1. Press Return to choose the default option. ________________________ 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. Preparing Your System for Installation 1-43 Preparing Your System for Installation 1.11 Running the Preinstallation System Check 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. 1.12 Final System Preparation Tasks: New Installations To prepare your system for a new ALL-IN-1 Version 3.2 installation, do the following: 1. Check that all prerequisite software is installed, configured and running. 2. Start the queue manager, if necessary. 3. Back up the system disk and any target disks. See Section 1.14. 1.13 Final System Preparation Tasks: Upgrade Installations For an upgrade installation from ALL-IN-1 Version 3.1, carry out the following steps before starting the installation. Each step is described in the following sections. From the privileged SYSTEM account, do the following: 1. Shut down ALL-IN-1. See Section 1.13.1. 2. Ensure that Message Router is running and is correctly configured. 3. Deinstall files in the site areas that are installed in memory. See Section 1.13.2. 4. Start the queue manager, if necessary. 5. Back up the system disk and any target disks. See Section 1.14. 1-44 Preparing Your System for Installation Preparing Your System for Installation 1.13 Final System Preparation Tasks: Upgrade Installations 1.13.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. 1.13.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). Make sure that you deinstall any of your own code-level executable images that are installed in memory. 1.14 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. Preparing Your System for Installation 1-45 Preparing Your System for Installation 1.14 Back Up Your System and Target Disks If you are going to install ALL-IN-1 Version 3.2 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. 1-46 Preparing Your System for Installation 2 _________________________________________________________________ Installation Procedure: New, Upgrade and Architecture Support This chapter describes the procedures for installing the ALL-IN-1 Version 3.2 base, language and market components. The following installation examples are given: o A new installation of ALL-IN-1 Version 3.2 on an Alpha system with the MAILbus 400 MTA and Digital X.500. See Section 2.1. o Upgrade installation of ALL-IN-1 Version 3.1 to ALL-IN-1 Version 3.2 with Message Router and the Message Router Directory Service. The installation is done on the Alpha system in a mixed-architecture VMScluster, where Message Router is installed on a remote VAX node. See Section 2.1. o Addition or upgrade of additional architecture support on a mixed-architecture VMScluster. See Section 2.2. __________________ Before You Start __________________ Do not start the installation until you have done the following: 1. Planned your installation by reading the ALL-IN-1 Overview and Planning Guide. 2. Completed the system preparation tasks in Chapter 1 to check that your system is ready for the installation. ______________________________________________________ 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 (?). Installation Procedure: New, Upgrade and Architecture Support 2-1 Installation Procedure: New, Upgrade and Architecture Support During the installation procedure a number of cautions and general informational messages are displayed. Read all the displayed messages carefully. Table 2-1 gives information which you may need during the installation. Table_2-1_Information_About_the_Installation_Procedure_____ Question_________Answer____________________________________ How long On_Alpha will the As an example, installing on an Alpha installation 4000-610 system takes about 1 hour and 15 take? minutes for a full installation when the files are installed on an RZ28 disk using an alternate working directory (AWD). On_VAX The installation can take from one to six hours, depending on the type of processor you are using. The performance 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 new and upgrade installations are approximately the same. How do I get Enter ? at any time help? What is A1032 the product identifier? (continued on next page) 2-2 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support Table 2-1 (Cont.) Information About the Installation __________________Procedure________________________________ Question_________Answer____________________________________ What do I Restart the installation from the do if the beginning. See Chapter 4. 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. How do I See Chapter 4. restart the installation?______________________________________________ 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 lists all the installation steps for a new or upgrade installation. The example scripts in the table show extracts from a new installation on an Alpha system using the MAILbus 400 MTA and Digital X.500 and an upgrade installation from ALL-IN-1 Version 3.1 with Message Router. Depending on your distribution media, you may be prompted to change the tape or cartridge during the installation. Installation Procedure: New, Upgrade and Architecture Support 2-3 Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 Installation Procedure for New and Upgrade __________Installations__________________________________________ Step__Action_____________________________________________________ 1 Create a log file for the installation. Digital recommends that you keep a record of the installation in case of problems. You can keep a log 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. _________________________________________________________________ 2 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). _________________________________________________________________ (continued on next page) 2-4 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 3 Invoke the VMSINSTAL procedure from the SYSTEM account. Enter the following commands: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL A1032 device To use an alternate working device (AWD), enter the following command lines: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL A1032 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$. A1032 is the product identifier and disk is the location of the alternate working device. _________________________________________________________________ 4 Verify your system backup. OpenVMS VAX Software Product Installation Procedure V6.2 It is 19-MAR-1996 at 13:04. 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: New, Upgrade and Architecture Support 2-5 Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 5 Load the distribution media (first volume). Enter the products to be processed from the first distribution volume set: * Products: A1032 * 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, A1032, at the prompt. Enter Y to confirm that the media is correctly mounted and you are ready to start. ___________________________________________________________ For installation type__________________Go_to________________________________ New Step 6 Upgrade_______________Step_8_______________________________ _________________________________________________________________ 6 New_Installation: Enter the number for the type of installation that you want to do. This is a LOCAL ALL-IN-1 V3.2 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.2 kit, the following installation types can be performed: (1) A new installation of ALL-IN-1 V3.2 (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. (continued on next page) 2-6 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ _________________________________________________________________ 7 New_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. To_continue: go to Step 10. _________________________________________________________________ 8 Upgrade_Installation: Enter the number for the type of installation you want to perform. This is a LOCAL ALL-IN-1 V3.2 BASE kit The current ALL-IN-1 image identification is ALL-IN-1 V3.1. Using the FULL ALL-IN-1 V3.2 kit, the following installation types can be performed: (1) Upgrade of ALL-IN-1 V3.1 to ALL-IN-1 V3.2 (2) Add, upgrade, or update Alpha components for an ALL-IN-1 V3.2 system (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. If you are running ALL-IN-1 in a single-architecture VMScluster, you are not offered option (2). _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-7 Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure fo