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 for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations__________________________________ Step__Action_____________________________________________________ 9 Upgrade_Installation: Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks (RC) Run conflict checking and resolution tool (CART) * Which action do you wish to perform [I]: Press RETURN to continue with the installation. _________________________________________________________________ 10 Confirm that the License PAK is registered and loaded: * Does this product have an authorization key registered and loaded [YES]? Press RETURN to continue. ___________________________________________________________ For installation type__________________Go_to________________________________ Upgrade Step 11 New___________________Step_12______________________________ _________________________________________________________________ 11 Upgrade_Installation: Confirm that you want to purge files. * Do you want to purge files replaced by this installation [YES]? Press RETURN to purge files. _________________________________________________________________ (continued on next page) 2-8 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_____________________________________________________ 12 Indicate whether you want to integrate DATATRIEVE with ALL-IN-1. DATATRIEVE can be integrated into ALL-IN-1. On VAX systems with Deferred image activation enabled the DATATRIEVE image will be deferred. If you use the standard DATATRIEVE image SYS$SHARE:DTRSHR.EXE then you can select to dynamically activate DATATRIEVE. You will still be able to use DATATRIEVE within ALL-IN-1, but you will avoid any performance impact of having it physically linked with the ALL-IN-1 image. * Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]? Press RETURN if you do not want to integrate DATATRIEVE. If you want to integrate DATATRIEVE, enter Y. You are prompted to supply the name of the DATATRIEVE image that you want to link with. If you are using the standard DATATRIEVE image, SYS$SHARE:DTRSHR.EXE, you are asked if you want to dynamically activate DATATRIEVE during the ALL-IN-1 startup. It is recommended that you do. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-9 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_____________________________________________________ 13 Indicate whether you want to install WPS-PLUS with ALL-IN-1. If you do not have a license which includes WPS-PLUS, you will not be asked this question. If you wish to have the WPS-PLUS editor available, answer YES to the following question. If you do not wish to install the WPS-PLUS editor, answer NO. NOTE: o If WPS-PLUS is not installed then the WPS-PLUS linguistics aids (SPELL CHECKER and THESAURUS) and the WPS-PLUS SORT and MERGE processing functionality will not be available. o You will be able to do an ALL-IN-1 update installation to add WPS-PLUS at a later time, should you choose not to install it now. * Do you want to install WPS-PLUS with ALL-IN-1 [YES]? Press RETURN to install WPS-PLUS. You are then asked if you want to install the graphics and page overlay samples: %A1-I-WPSLINK, The WPS-PLUS editor will be installed and linked with ALL-IN-1 This kit contains a library of Encapsulated PostScript(R) graphics and PostScript(R) Page Overlay samples. Their total size is approximately 3,000 blocks when they are copied to the ALL-IN-1 library directory. * Do you want these graphics copied to the ALL-IN- 1 library directory [NO]? Press RETURN if you do not want to copy the files. Enter Y to copy the files. (continued on next page) 2-10 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_____________________________________________________ _________________________________________________________________ 14 Indicate whether you want to incorporate ACMS. If you wish to interface with ACMS, answer YES to the following questions. NOTE: o ACMS must be installed before ALL-IN-1. o If you answer YES and the relevant ACMS files are present then the interface to ACMS will be built. If the files are not present, then you may either continue the installation without linking with ACMS or abort the installation to correct the problem. * Do you want to integrate ACMS with ALL-IN-1 [NO]? Press RETURN if you do not want to integrate ACMS. Enter Y if you want to integrate ACMS. _________________________________________________________________ 15 Indicate whether to you want to build a multilanguage system. If you wish to use more than one ALL-IN-1 language, answer YES to the following question. * Do you want to build a MULTI-LANGUAGE system [NO]? Press RETURN if you do not want to build a multilanguage system. Enter Y if you plan to install additional languages and you want to build a multilanguage system. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-11 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_____________________________________________________ 16 Select a default date format. ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis.) This may be changed by each user through the Set Working Conditions option on the User Setup Menu. Alphanumeric Date Numeric Date 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD 7 ***** Reserved (Means system default) ***** 8 DD-MM-YYYY DD/MM/YY (Numeric format) 9 MM-DD-YYYY MM/DD/YY (Numeric format) * Which date format do you require [1]: Press RETURN to use the default format or enter the number for the date format that you want to use. _________________________________________________________________ (continued on next page) 2-12 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_____________________________________________________ 17 Specify the greatest number of simultaneous ALL-IN-1 users. * What will be the greatest number of simultaneous ALL-IN- 1 users: Upgrade_installation A default value is given. Press RETURN to accept the default value. New_installation Specify the maximum number of ALL-IN-1 users that you expect at any one time. The installation procedure uses this entry to check that system parameters are large enough to support your intended number of users. _________________________________________________________________ 18 Specify a batch queue for running the job that checks the Mail Sender and Fetcher processes. * Which batch queue do you want to use for the Sender/Fetcher check job? [SYS$BATCH]: Press RETURN to use the default queue or specify the name of an existing batch queue. For_an_upgrade_installation: Go to Step 20. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-13 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_____________________________________________________ 19 New_installation: Specify a batch queue for starting the AIDA and File Cabinet Servers, and the Sender and Fetcher processes. ALL-IN-1 must use a running batch queue on this node to start the AIDA and File Cabinet Servers, and the Sender and Fetcher processes. * Which queue do you want to use? [default]: Press RETURN to accept the default queue or enter the name of an existing batch queue on this node that is not generic and that is currently running. The queue that you specify will be added to the Node Specific Batch Queue Master file, and will be stored in the configuration files of any Servers created during this installation. You can change the queue later, or add queues for other nodes in your cluster, using the Manage node specific queues (MNQ) option from the System Management menu. _________________________________________________________________ (continued on next page) 2-14 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_____________________________________________________ 20 Indicate if you want to send and receive remote mail. The installation procedure checks the type and versions of the message transport and directory service software that are installed on your system. ALL-IN-1 Electronic Messaging can send and receive messages, to and from other computer systems using either the MAILbus 400 or Message Router products. * Do you want to be able to send and receive remote mail [YES]? Press RETURN if you want to use remote mail. If you answer NO to this question, ALL-IN-1 users will only be able to exchange messages locally with other users on the same computer system. ___________________________________________________________ If_You_______________________________Go_To_________________ Do not want to use remote mail Step 28 Are installing a new ALL-IN-1 Step 21 system with Digital X.500 and the MAILbus 400 MTA Are_upgrading_with_Message_Router____Step_22_______________ _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-15 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_____________________________________________________ 21 New_Installation with the MAILbus 400 MTA and Digital X.500: Confirm that you want to use the MAILbus 400 MTA for remote mail. If you plan to use MAILbus 400 as your MTA, then answer YES to this question. You will not have been offered this choice unless the installation checks have revealed that the product is installed. Note that even though MAILbus 400 appears to be installed and initially configured, it is unlikely that it will sucessfully process your mail until you have completed all the set up tasks described in the Mail Management Guide. If you answer NO to this question, ALL-IN-1 users will only be able to exchange messages locally, unless you subsequently choose to use Message Router (if it is available.) * Do you want to use MAILbus 400 for remote mail [YES]? Press RETURN to use the MAILbus 400 MTA for remote mail. It does make any difference to the installation if the MAILbus 400 MTA is installed on the same node as ALL-IN-1 or on a different node in the same VMScluster on a remote node outside the cluster, providing that you have completed all the configuration and set up tasks that are covered in the Overview and Planning Guide. To_continue: Go to Step 25. _________________________________________________________________ (continued on next page) 2-16 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_____________________________________________________ 22 Upgrade_Installation: Confirm that you want to use Message Router for remote mail. ALL-IN-1 on a VAX node can be configured to use a local Message Router which is installed on the same node or a remote Message Router which is installed on a different node. ALL-IN-1 on an Alpha node can only use a remote Message Router. This example script is on an Alpha system so it must be configured to use a remote Message Router. * Do you want ALL-IN- 1 to be configured to use Message Router [YES]? Answer Y to confirm that you want to use Message Router. _________________________________________________________________ 23 Upgrade_Installation: If Message Router is not installed on this node, confirm that you want to use a remote Message Router. * Do you want to use a remote Message Router [YES]? Enter Y to confirm that you want to use a remote Message Router. Note that the default value for this answer depends on whether you are doing the upgrade installation on a VAX system or an Alpha system. In this example, the upgrade is on an Alpha system, so the default is to use a remote Message Router. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-17 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_____________________________________________________ 24 Upgrade_Installation: Enter the name of the remote Message Router node. * What node is the Message Router on: Enter the DECnet node name of the remote Message Router node. Note that the remote Message Router node must be in the network nodes database on the node on which you are installing ALL-IN-1. As this is an upgrade you will not be asked for a password for the Message Router mailbox. Additional_Questions If you are installing a new ALL-IN-1 system with Message Router, you are prompted to enter a password for the Message Router mailbox. * Enter a password for the Message Router mailbox: * Please confirm the password that you specified: The password must be a minimum of 8 characters and a maximum of 32 characters. Confirm the password. _________________________________________________________________ (continued on next page) 2-18 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_____________________________________________________ 25 Indicate the type of Mail Directory support that you want. For new installations where Digital X.500 is installed, the following is displayed: * What type of Mail Directory support do you want [X]: The options that are available depend on the type of directory service software that is installed on your system. You are given the appropriate options and defaults from the following list, depending on what is installed. Press RETURN to accept the default or enter the value for the type of Mail directory support that you want. ___________________________________________________________ For__________________________________Option_to_Enter_______ No Mail directory support 0 The Message Router Directory M Service as the Mail directory The Digital X.500 Directory Service X as_the_Mail_directory______________________________________ When you are installing with Digital X.500, it does not matter whether Digital X.500 is installed on the same node as ALL-IN-1 or on a remote node outside the cluster, providing that you have done all the necessary setup and configuration tasks as outlined in the Overview and Planning Guide. If_you_have_specified_no_Mail_directory_support, go to Step 28. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-19 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_____________________________________________________ 26 Specify if you want the Mail directory to be the primary directory. Do you want the Mail Directory to be the primary directory [NO]? Press RETURN to use the Mail directory as the secondary directory. For new installations go to Step 28. _________________________________________________________________ 27 Installation_with_Message_Router: Enter a password for the Mail Directory User Agent account and confirm it. The text that is displayed depends on whether you are using a remote Message Router, and whether that Message Router is in the same VMScluster. Read the informational messages carefully and follow the instructions. The password length must between 6 and 8 characters. * Press RETURN to continue the installation: * Enter a password for the Message Router Directory user agent account: * Please confirm the password which you specified: Press RETURN and then enter a password for the Mail Directory user agent account and confirm it. _________________________________________________________________ (continued on next page) 2-20 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_____________________________________________________ 28 Indicate if you want outgoing messages translated to ASCII. * Do you want to translate all outgoing messages to ASCII [NO]? Press RETURN if you do not want outgoing messages translated. _____________________ Note _____________________ If you are using a remote MAILbus 400 MTA on Digital UNIX, you must answer Y to this question if WPS-PLUS to ASCII converters are not installed on the MAILbus 400 MTA node and you want to exchange messages with non-ALL-IN-1 users. ________________________________________________ Enter Y, if you want outgoing messages translated. You are then asked if you want all attachments to be translated. * Do you want to translate all message attachments [NO]? Press RETURN if you do not want to translate all message attachments. If you enter Y to this question, all message attachments are translated to ASCII if the appropriate converters are installed on your ALL-IN-1 system. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-21 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_____________________________________________________ 29 System checking. The installation procedure checks mandatory and optional software prerequisites. You may be asked additional questions depending on the software and licences that are installed on your system. If the prerequisite software for CDA support is not installed, you are asked if you want to continue the installation without CDA support. If DEC Notes is not installed and your ALL-IN-1 license supports Group Conferencing, you are asked if you want to continue without Group Conferencing support. _________________________________________________________________ (continued on next page) 2-22 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_____________________________________________________ 30 Indicate if you want client applications to connect to ALL-IN-1 using TCP/IP network protocol. You are only asked the following question if DEC TCP /IP Services (UCX) or other TCP/IP network sofware that emulates UCX is installed on your system. * Do you want to use TCP/IP [YES]? Press RETURN if you want to use TCP/IP for client connections. If you do, you are asked the following questions if default service names for the AIDA Server and ALL-IN-1 File Cabinet Server are not registered in the Internet Services database. * Enter a port number for the AIDA Server [7300]: * Enter a port number for the ALL-IN- 1 File Cabinet Server [7373]: Enter a different TCP/IP port number for each server. The port numbers can be in the range 1024 to 65535. You must use the default values if you are planning to use TeamLinks client software. The installation procedure checks that the UCX$IPC_SHR.EXE image is installed. If it is not, you must install it after the installation. _________________________________________________________________ 31 System checking. The installation procedure checks system parameters, quotas and identifiers. For new installations, the ALL-IN-1 identifiers are created. The identifiers already exist for upgrade installations. For ALL-IN-1 Version 3.2, the identifier OA$FS_ADMIN is required. If you do a new installation and this identifier already exists, you are asked to confirm whether you want to use the existing identifier. Follow the installation instructions. OA$FS_ADMIN is used for access control only. (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-23 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_____________________________________________________ _________________________________________________________________ 32 Enter the language code. * Enter language code for this installation (2 characters): US Enter the two-letter language code for your language component. In this example, US is the ENGLISH language code. See the ALL-IN-1 Installation: Language and Market Supplement supplied with your kit. _________________________________________________________________ (continued on next page) 2-24 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_____________________________________________________ 33 Enter the dialect code. Your language kit may also contain one or more dialect components. Enter the dialect code that you want to use. If your language kit does not contain a dialect component, you are not asked this question. %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... If you wish to install a dialectal variation of ENGLISH language, enter the code for the dialect component you wish to use. If you do not wish to install a dialectal variation of ENGLISH language, then accept the answer of NO_DIALECT. * Enter dialect code for this installation (5 characters) [NO_DIALECT]: Press RETURN or enter the dialect code that you want to use. See the ALL-IN-1 Installation: Language and Market Supplement. The installation procedure continues with system checking. ___________________________________________________________ For installation type__________________Go_to________________________________ New Step 34 Upgrade_______________Step_35______________________________ _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-25 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_____________________________________________________ 34 New_Installation: Specify the devices for the ALL-IN-1 areas. * Which device will hold the ALL-IN-1 shared library files: * Which device will hold the ALL-IN- 1 shared data files [A1DISK1:]: * Which device will hold the ALL-IN- 1 ENGLISH language files [A1DISK1:]: * Which device will hold the ALL-IN- 1 mail area SDAF file [A1DISK1:]: * How many shared directories do you want to create [1]: * Which device will hold the ALL-IN- 1 shared directory SHARE1 [A1DISK1:]: * Which device will hold the ALL-IN- 1 lexicon files [A1DISK1:]: For shared directories, Digital recommends that you select the default value at installation time and then create additional shared directories after the installation, following the instructions in the ALL-IN-1 Management Guide. If lexicon files have already been installed by another product, you are not asked the question about lexicon files. _________________________________________________________________ 35 Enter the market code. * Enter market code for this installation (2 characters): US Enter the two-letter market code for the installation. See the ALL-IN-1 Installation: Language and Market Supplement. ___________________________________________________________ Installation_type_____Go_to________________________________ New 36 Upgrade_______________43___________________________________ (continued on next page) 2-26 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_____________________________________________________ _________________________________________________________________ 36 New_Installation: Specify an OpenVMS account and password for the ALL-IN-1 manager. Confirm the password. %A1CUS-I-RECOUK, Restoring the MARKET kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... This installation creates a VMS account for the ALL-IN-1 manager. * What VMS username do you want to use for ALL-IN-1 MANAGER account [ALLIN1]: * Enter a password for the ALL-IN-1 MANAGER account: * Please confirm the password which you specified: _________________________________________________________________ 37 New_Installation: Enter a system group UIC and default device and directory for the ALL-IN-1 manager. Do not create the ALL-IN-1 manager's account in a subdirectory of an OpenVMS system directory. * What UIC do you want to use for ALL-IN- 1 MANAGER account: * What default device do you want to use for the ALL-IN- 1 MANAGER'S account [A1DISK1:] * What default directory do you want to use for ALL-IN- 1 MANAGER'S account? [ALLIN1:] _________________________________________________________________ 38 New_Installation: Enter a UIC for the accounts used by the Transfer User utility. The UIC must not be a system group UIC. * What UIC do you want to use for A1$XFER_IN account: * What UIC do you want to use for the A1$XFER_OUT account: (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-27 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_____________________________________________________ _________________________________________________________________ 39 New_Installation: Enter a UIC for the account used by the Script Symbiont utility. The UIC must not be a system group UIC. * What UIC do you want to use for ALL-IN- 1 SCRIPT SYMBIONT account: _________________________________________________________________ 40 New_Installation: Enter a UIC for the account used by the File Cabinet Server for authenticating remote clients into a non-privileged account. The UIC must not be a system group UIC. * What UIC do you want to use for ALL-IN- 1 OAFC$DEFAULT account: _________________________________________________________________ 41 New_Installation: Enter a UIC for the account used for running the ALL-IN-1 File Cabinet Server as a detached process. The UIC must not be a system group UIC. * What UIC do you want to use for ALL-IN- 1 OAFC$SERVER account: _________________________________________________________________ (continued on next page) 2-28 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_____________________________________________________ 42 New_Installation: Specify the top-level directories for the ALL-IN-1 areas. * Enter ALL-IN-1 top-level directory required for the shared library files [ALLIN1]: * Enter ALL-IN-1 top-level directory required for the shared data files [ALLIN1]: * Enter ALL-IN-1 top-level directory required for all ENGLISH language files [ALLIN1]: * Enter ALL-IN-1 top-level directory required for the mail area SDAF file [ALLIN1]: * Enter the name required for the SHARED DIRECTORY on A1DISK1: [ALLIN1]: Go to Step 45 to continue. _________________________________________________________________ 43 Upgrade_Installation: Enter the OpenVMS username for the ALL-IN-1 manager's account. * What is the existing VMS username for the ALL-IN- 1 account [ALLIN1]: Enter the OpenVMS username for the ALL-IN-1 account. The account details are displayed. _________________________________________________________________ 44 Upgrade_Installation: Confirm that the details of the ALL-IN-1 manager's account are correct. * Are all the specified account's characteristics correct [YES]? Press RETURN if all the information is correct. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-29 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_____________________________________________________ 45 Run the IVP (Installation Verification Procedure). * Do you want to run the IVP after the installation [YES]? ______Press_RETURN_to_run_the_IVP._______________________________ All the installation questions have now been completed. If you are installing ALL-IN-1 Version 3.2 on a mixed- architecture VMScluster, see Section 2.2 for instructions on adding architecture support for a second architecture. If you are not installing on a single-architecture VMScluster, go to Section 2.3. 2.2 Adding or Upgrading Architecture Support Table 2-3 explains when you can do an installation to add or upgrade architecture support. Table 2-3 When to Install/Upgrade VAX or Alpha Architecture __________Support__________________________________________ Install/Upgrade_______When_you_have_already_done___________ VAX architecture A new or upgrade ALL-IN-1 Version 3.2 support installation on an Alpha system in the same VMScluster Alpha architecture A new or upgrade ALL-IN-1 Version 3.2 support installation on a VAX system in the ______________________same_VMScluster._____________________ The questions that you are asked during the additional architecture installation depend on the responses that you gave during the new or upgrade installation. For example, if you did not install WPS-PLUS during the new or upgrade installation, you are not asked any additional questions about WPS-PLUS. 2-30 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support 2.2.1 Before You Start Before you start the installation, you must do the following: 1. If you are installing architecture support for the first time, make a note of the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT, on the system where you have already installed a new ALL-IN-1 Version 3.2 system or upgraded to an ALL-IN-1 Version 3.2 system. You will be asked for this information during the installation. 2. Run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP, to check for logicals containing SYS$SYSDEVICE. 3. From the ALL-IN-1 manager's account on the node where ALL-IN-1 is already installed, run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP: $ SET HOST 0/LOG=filename $ ALLIN1/NOINIT Enter CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP If references to SYS$DEVICE are found, a warning message is displayed. You must remove the references as they will refer to different devices on a VAX system and an Alpha system. If the references are not corrected, data may be lost on your system. The installation procedure also runs this script. 2.2.2 Installation Procedure for Adding Architecture Support Table 2-4 shows an example script for an additional- architecture installation on a VAX system. The following information is used: o ALL-IN-1 Version 3.2 is already installed on an Alpha system in the same VMScluster. o WPS-PLUS is installed on the Alpha system. o ALL-IN-1 has been configured as a multilanguage system on the Alpha system. o Message Router is installed on this VAX system. Installation Procedure: New, Upgrade and Architecture Support 2-31 Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support The example includes the script for both adding VAX support for the first time and upgrading existing VAX support. The installation questions and script are similar for the addition or upgrade of Alpha support. Table_2-4_Installation_Procedure_for_Adding_Architecture_Support_ Step__Action_____________________________________________________ 1 to Follow Steps 1 to 5 in Table 2-2. 5 ___________________________________________________________ For_Installation_Type________________Go_to_________________ Upgrade Step 6 New__________________________________Step_7________________ _________________________________________________________________ (continued on next page) 2-32 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 6 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.2. Using the FULL ALL-IN-1 V3.2 kit, the following installation types can be performed: (1) Add, upgrade, or update VAX components for an ALL-IN-1 V3.2 system (2) Install new ALL-IN-1 V3.2 additional language (3) Upgrade ALL-IN-1 V3.1 additional language (4) Update ALL-IN-1 V3.2 additional language (5) Add, upgrade, or update VAX components for an ALL-IN-1 V3.2 additional language (6) Update ALL-IN-1 V3.2 (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: Press RETURN to upgrade VAX components for an existing ALL-IN-1 Version 3.2 system that is already installed on an Alpha system in the same VMScluster. To_Continue: Go to Step 8. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-33 Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 7 New_Installation: Enter the number for the type of installation you want to perform. 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 (2) Add, upgrade, or update VAX components for an ALL-IN-1 V3.2 system (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: 2 Enter 2 to add VAX architecture support. _________________________________________________________________ 8 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. Upgrade_Installation: Go to Step 10. _________________________________________________________________ (continued on next page) 2-34 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 9 New_Installation: Supply the location of OA$DATA_ SHARE:A1CONFIG.DAT, the ALL-IN-1 configuration file, for ALL-IN-1 Version 3.2 on the existing system. You have chosen an architecture only installation. To continue you must specify the location of the existing ALL-IN-1 system's configuration file (A1CONFIG.DAT). The installation will read A1CONFIG.DAT to determine file target locations. * Please give the directory location of A1CONFIG.DAT: disk:[directory] Enter the location of the ALL-IN-1 configuration file in the format, disk:[directory]. You must always use this format to specify the location of this file. The installation script uses the configuration file to define logicals. %A1-I-DEFLOG, Running A1V32START.COM to define the logicals -A1-I-DEFLOG, for your existing ALL-IN-1 V3.2 VAX system. Defining language independent logical names Defining ENGLISH language logical names Where possible, the VAX architecture-only installation matches the configuration of ALL-IN-1 that is already installed on the Alpha system. The informational messages that are displayed will depend on the existing configuration. _________________________________________________________________ 10 Confirm that a license PAK is registered and loaded. * Does this product have an authorization key registered and loaded [YES]? Press RETURN to continue. New_Installation: Go to Step 12. (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-35 Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ _________________________________________________________________ 11 Upgrade_Installation: Confirm that you want to purge files. * Do you want to purge files replaced by this installation [YES]? Press RETURN to continue. _________________________________________________________________ 12 Indicate whether you want to integrate DATATRIEVE with ALL-IN-1. DATATRIEVE can be integrated into ALL-IN-1. On VAX systems with Deferred image activation enabled the DATATRIEVE image will be deferred. If you use the standard DATATRIEVE image SYS$SHARE:DTRSHR.EXE then you can select to dynamically activate DATATRIEVE. You will still be able to use DATATRIEVE within ALL-IN-1, but you will avoid any performance impact of having it physically linked with the ALL-IN-1 image. * Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]? Press RETURN if you do not want to integrate DATATRIEVE. Enter Y if you want to integrate DATATRIEVE. You are prompted to supply the name of the DATATRIEVE image that you want to link with. If you are using the standard DATATRIEVE image, SYS$SHARE:DTRSHR.EXE, you are asked if you want to dynamically activate DATATRIEVE during the ALL-IN-1 startup. It is recommended that you do. _________________________________________________________________ (continued on next page) 2-36 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 13 System checking for existing ALL-IN-1 configuration. The informational message depends on your existing configuration, for example: During your ALL-IN- 1 installation on Alpha you chose to install ALL-IN-1 with WPS-PLUS, therefore WPS- PLUS will also be installed during this VAX architecture only installation. _________________________________________________________________ 14 Indicate whether you want to incorporate ACMS. If you wish to interface with ACMS, answer YES to the following questions. If you wish to interface with ACMS, answer YES to the following questions. NOTE: o ACMS must be installed before ALL-IN-1. o If you answer YES and the relevant ACMS files are present then the interface to ACMS will be built. If the files are not present, then you may either continue the installation without linking with ACMS, or abort the installation to correct the problem. * Do you want to integrate ACMS with ALL-IN-1 [NO]? Press RETURN if you do not want to integrate ACMS. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-37 Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 15 System checking for existing ALL-IN-1 configuration. The informational message depends on your existing configuration, for example: ALL-IN-1 on the Alpha is linked as a MULTI- LANGUAGE system, therefore ALL-IN-1 on this VAX will also be linked as a MULTI-LANGUAGE system. _________________________________________________________________ 16 Specify the greatest number of simultaneous ALL-IN-1 users. * What will be the greatest number of simultaneous ALL-IN- 1 users: Upgrade_Installation: A default value is given. Press RETURN to accept this default value. New_Installation: Specify the maximum number of ALL-IN-1 users that you expect at any one time. The installation procedure uses this entry to check that system parameters are large enough to support your intended number of users. _________________________________________________________________ (continued on next page) 2-38 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 17 Message Router checks for upgrade installations. This part of the installation procedure is determined by the answers that you gave during the installation on the other system. In this example script, the Alpha system was configured to use a remote Message Router on this VAX node. The level of Mail directory support set up for the Alpha system is also used. %A1-I-MDCHK, Performing Mail and Directory checks... %A1-I-REMMR, Your ALL-IN-1 system running on the Alpha is configured -A1-I-REMMR, to use a Remote Message Router on this node %A1-I-LOCMR, Therefore this VAX ALL-IN-1 system will be configured -A1-I-LOCMR, to use a local Message Router %A1-I-DIROPP, Your Alpha ALL-IN-1 system is configured to use a -A1-I-DIROPP, Mail Directory Service. This VAX architecture only -A1-I-DIROPP, installation will use the same Message Router Directory Service. %A1-I- UPDATEDDS, As this is an update you will not be asked for a -A1-I-UPDATEDDS, Message Router Directory password . . . The installation procedure also checks for CDA support software. If it is not found, you are asked if you want to continue without CDA support or whether you want to install the appropriate software. Following the instruction in the installation script. Software support for Group Conferencing is also checked. If the appropriate version of DEC Notes is not installed, you are given instructions on what to do. (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-39 Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ _________________________________________________________________ 18 Indicate if you want client applications to connect to ALL-IN-1 using TCP/IP network protocol. You are only asked the following question if DEC TCP/IP Services (UCX) or other TCP/IP network sofware that emulates UCX is installed on your system. * Do you want to use TCP/IP [YES]? Press RETURN if you want to use TCP/IP for client connections. If you do, you are asked the following questions if default service names for the AIDA Server and ALL-IN-1 File Cabinet Server are not registered in the Internet Services database. * Enter a port number for the AIDA Server [7300]: * Enter a port number for the ALL-IN- 1 File Cabinet Server [7373]: Enter a different TCP/IP port number for each server. The port numbers can be in the range 1024 to 65535. You must use the default values if you plan to use the TeamLinks client software. The installation procedure checks that the UCX$IPC_SHR.EXE image is installed. If it is not, you must install it after the installation. _________________________________________________________________ 19 System checking. The installation procedure checks system parameters, quotas and identifiers. _________________________________________________________________ (continued on next page) 2-40 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 20 Enter the language code. * Enter language code for this installation (2 characters): US Enter the two-letter language code for your language component. See the ALL-IN-1 Installation: Language and Market Supplement supplied with your kit. _________________________________________________________________ 21 Enter the dialect code. Your language kit may also contain one or more dialect components. Enter the dialect code that you want to use. %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... If you wish to install a dialectal variation of ENGLISH language, enter the code for the dialect component you wish to use. If you do not wish to install a dialectal variation of ENGLISH language, then accept the answer of NO_DIALECT. * Enter dialect code for this installation (5 characters) [NO_DIALECT]: _________________________________________________________________ 22 Enter the market code. * Enter market code for this installation (2 characters): US Enter the two-letter market code for the installation. See the ALL-IN-1 Installation: Language and Market Supplement. _________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-41 Installation Procedure: New, Upgrade and Architecture Support 2.2 Adding or Upgrading Architecture Support Table 2-4 (Cont.) Installation Procedure for Adding Architecture __________________Support________________________________________ Step__Action_____________________________________________________ 23 Enter the name of the OpenVMS account for the ALL-IN-1 manager. * What is the existing VMS username for the ALL-IN- 1 account [ALLIN1]: The account details are displayed. _________________________________________________________________ 24 Confirm that the details of the account are correct. * Are all the specified account's characteristics correct [YES]? Press RETURN if the details are correct. _________________________________________________________________ 25 Run the IVP (Installation Verification Procedure). * Do you want to run the IVP after the installation [YES]? ______Press_RETURN_to_run_the_IVP._______________________________ All the installation questions have now been completed. 2.3 Automatic Postinstallation Tasks The installation procedure performs automatic postinstallation tasks, for example, converting data files. If a problem occurs during the postinstallation phase, see Chapter 4. The following tasks are done automatically: o Deassigns old ALL-IN-1 logicals and logicals created during the installation o Runs the ALL-IN-1 startup procedure, A1V32START.COM o Compiles, installs and sets protections on the following form libraries and their site versions: o OAFORM o MEMRES o OAN$FORMS 2-42 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.3 Automatic Postinstallation Tasks o Installs message symbol files o Compiles TXLs o For upgrade installations, the following data files are upgraded: o A1CONFIG.DAT o PROFILE.DAT o SM_ACCOUNT_TYPES.DAT o SM_POLICIES.DAT o FORMAT.DAT 2.4 Manual Postinstallation Tasks There are some manual tasks that you must complete after the installation. See Chapter 5. Installation Procedure: New, Upgrade and Architecture Support 2-43 3 _________________________________________________________________ Installation Procedure: Additional Languages This chapter describes the installation of an additional language on an ALL-IN-1 Version 3.2 system that is configured as a multilanguage system. __________________ Before You Start __________________ Do not start the installation until you have completed the system preparation tasks in Chapter 1. ______________________________________________________ During the installation procedure a number of cautions and general informational messages are displayed. Read all the displayed messages carefully. Each question in the installation is marked with an asterisk (*) at the beginning of the line. If you are unsure how to answer a question enter a question mark (?) for Help. ________________________ Note ________________________ If the installation fails, you must restart the installation from the beginning. To stop the installation at any point, press CTRL/Y. ______________________________________________________ If you are installing a new additional language or upgrading an existing additional language, see Section 3.1. If you are installing or upgrading architecture support for an additional language, see Section 3.2. Installation Procedure: Additional Languages 3-1 Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations 3.1 Installation Procedure for Additional Language Installations Follow the steps in Table 3-1 to install a new additional language or upgrade an existing additional language. There are minor differences in the display depending on whether the installation is being run on a VAX or Alpha system. The example script shows the addition of BRITISH as an additional language on an ALL-IN-1 Version 3.2 Alpha system that is configured as a multilanguage system. Depending on your distribution media, you may be prompted to change the tape or cartridge during the installation. 3-2 Installation Procedure: Additional Languages Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations Table_3-1_Installation_Procedure_for_An_Additional_Language______ 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 language software kit. _________________________________________________________________ 3 Invoke the VMSINSTAL procedure from the SYSTEM account. Enter the following commands: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL A1LUS032 device To use an alternate working device (AWD), enter the following command lines: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL A1LUS032 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$. A1LUS032 is the product identifier and disk is the location of the alternate working device. (continued on next page) Installation Procedure: Additional Languages 3-3 Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations Table 3-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ _________________________________________________________________ 4 Verify your system backup. OpenVMS Alpha Software Product Installation Procedure V6.1 It is 14-FEB-1996 at 21:27. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Press RETURN to continue. _________________________________________________________________ 5 Load the distribution media. Enter the product identifier, A1LUS032, at the prompt and then enter Y to confirm that the media is correctly mounted and you are ready to start. Enter the products to be processed from the first distribution volume set: * Products: A1LUS032 * Enter installation options you wish to use (none): Please mount the first volume of the set on device * Are you ready? Y _________________________________________________________________ (continued on next page) 3-4 Installation Procedure: Additional Languages Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations Table 3-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 6 Enter the number for the type of installation you want to do. This is a LOCAL ALL-IN-1 V3.2 LANGUAGE kit The current ALL-IN-1 image identification is ALL-IN-1 V3.2. Using the LANGUAGE-only ALL-IN-1 V3.2 kit, the following installation types can be performed: (1) Install new ALL-IN-1 V3.2 additional language (2) Upgrade ALL-IN-1 V3.1 additional language (3) Update ALL-IN-1 V3.2 additional language (4) Add, Upgrade or Update Alpha architecture specific components of an existing ALL-IN-1 V3.2 additional language (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: 1 Enter 1 to install a new additional ALL-IN-1 Version 3.2 language. _________________________________________________________________ 7 Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks * Which action do you wish to perform [I]: Press RETURN to start the installation. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 3-5 Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations Table 3-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 8 Supply information about optional software as appropriate. During your first language installation you chose to install ALL-IN-1 without DATATRIEVE, therefore this tool will NOT be available from your ALL-IN-1 additional language. During your first language installation you chose to integrate WPS-PLUS, therefore you be be able to use WPS-PLUS as an additional editor from your ALL-IN-1 additional language. This kit contains a library of Encapsulated PostScript(R) graphics and PostScript(R) Page Overlay samples specific to the language component. * Do you want these graphics copied to the ALL-IN- 1 library directory [NO]? Enter Y to copy the WPS-PLUS graphics library to the ALL-IN-1 directory. _________________________________________________________________ 9 Configuration Checking. The message that you see depends on your primary language configuration, for example: During your first language installation you chose to install ALL-IN-1 without ACMS, therefore this tool will NOT be available from your ALL-IN-1 additional language. _________________________________________________________________ (continued on next page) 3-6 Installation Procedure: Additional Languages Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations Table 3-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 10 Select a default date format. ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis.) This may be changed by each user through the Set Working Conditions option on the User Setup Menu. Alphanumeric Date Numeric Date 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD 7 ***** Reserved (Means system default) ***** 8 DD-MM-YYYY DD/MM/YY (Numeric format) 9 MM-DD-YYYY MM/DD/YY (Numeric format) * Which date format do you require [1]: Press RETURN to use the default format or enter the number for the date format that you want to use. See the ALL-IN-1 Installation: Language and Market Supplement for more details about date formats. The installation procedure now does system checks. _________________________________________________________________ 11 Enter the language code. * Enter language code for this installation (2 characters): US Enter the two-letter language code for your language component. See the ALL-IN-1 Installation: Language and Market Supplement supplied with your kit. (continued on next page) Installation Procedure: Additional Languages 3-7 Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations Table 3-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ _________________________________________________________________ 12 Enter the dialect code. %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... If you wish to install a dialectal variation of ENGLISH language, enter the code for the dialect component you wish to use. If you do not wish to install a dialectal variation of ENGLISH language, then accept the answer of NO_DIALECT. * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GB Enter the dialect code that you want to use. In this example, US_GB is the BRITISH dialect component. See the ALL-IN-1 Installation: Language and Market Supplement. _________________________________________________________________ 13 Confirm that the License PAK is registered and loaded. * Does this product have an authorization key registered and loaded [YES]? Press RETURN to continue. _________________________________________________________________ 14 Specify the device for the additional language files. * Which device will hold the ALL-IN- 1 BRITISH language files: Enter the device name. _________________________________________________________________ (continued on next page) 3-8 Installation Procedure: Additional Languages Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations Table 3-1 (Cont.) Installation Procedure for An Additional __________________Language_______________________________________ Step__Action_____________________________________________________ 15 Enter the OpenVMS username for the ALL-IN-1 manager's account. * What is the existing VMS username for the ALL-IN- 1 account [ALLIN1]: The details of the account are displayed. _________________________________________________________________ 16 Confirm that the account details are correct. * Are all the specified account's characteristics correct [YES]? Press RETURN to confirm that the account details are correct. _________________________________________________________________ 17 Specify the top-level directory for the ALL-IN-1 additional language files. * Enter ALL-IN-1 top-level directory required for all BRITISH language files [BRITISH]: _________________________________________________________________ 18 Run the IVP (Installation Verification Procedure). * Do you want to run the IVP after the installation [YES]? ______Press_RETURN_to_run_the_IVP._______________________________ All the installation questions have now been completed. The installation procedure does automatic postinstallation tasks. If a problem occurs during the postinstallation phase, see Chapter 4. For manual postinstallation tasks, see Chapter 5. If you are installing on a VMScluster and want to add additional architecture support for the additional language that you have installed, see Section 3.2. Installation Procedure: Additional Languages 3-9 Installation Procedure: Additional Languages 3.2 Installing Architecture Support for an Additional Language 3.2 Installing Architecture Support for an Additional Language Before you start the installation, you must do the following: o Make a note of the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT, on the VAX system. You will be asked for this information during the installation. o Run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP, to check for logicals containing SYS$SYSDEVICE. From the ALL-IN-1 manager's account on the node where you have already installed ALL-IN-1, run the script, OA$LIB:SM_ CHECK_SYS$SYSDEVICE.SCP: $ SET HOST 0/LOG=filename $ ALLIN1/NOINIT Enter CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP If references to SYS$DEVICE are found, a warning message is displayed. You must remove the references as they will refer to different devices on a VAX system and an Alpha system. If the references are not corrected, data may be lost on your system. Follow the steps in Table 3-2 to add architecture support for an additional language that you have already installed on a different architecture in the same VMScluster. The example script shows the addition of VAX architecture support for ALL-IN-1 BRITISH as an additional language. BRITISH is already installed as an additional language on an Alpha system in the same VMScluster. Table 3-2 Installation Procedure for Addition of Architecture __________Support_for_an_Additional_Language_____________________ Step__Action_____________________________________________________ 1 to Follow Steps 1 to 5 in Table 3-1. 5 _________________________________________________________________ (continued on next page) 3-10 Installation Procedure: Additional Languages Installation Procedure: Additional Languages 3.2 Installing Architecture Support for an Additional Language Table 3-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 6 Enter the number for the type of installation you want to do. Using the LANGUAGE-only ALL-IN-1 V3.2 kit, the following installation types can be performed: (1) Install new ALL-IN-1 V3.2 additional language (2) Upgrade ALL-IN-1 V3.1 additional language (3) Update ALL-IN-1 V3.2 additional language (4) Add, upgrade, or update VAX components for an ALL-IN-1 V3.2 additional language (RL) Register licenses for pre-requisite software * Which installation do you wish to perform [1]: 4 Enter 4 to add VAX architecture support for an existing ALL-IN-1 Version 3.2 additional language. _________________________________________________________________ 7 Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks * Which action do you wish to perform [I]: Press RETURN to start the installation. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 3-11 Installation Procedure: Additional Languages 3.2 Installing Architecture Support for an Additional Language Table 3-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 8 Enter the location of OA$DATA_SHARE:A1CONFIG.DAT, the ALL-IN-1 configuration file, for the existing ALL-IN-1 Version 3.2 system. You have chosen an architecture only installation. To continue you must specify the location of the existing ALL-IN-1 system's configuration file (A1CONFIG.DAT). The installation will read A1CONFIG.DAT to determine file target locations. * Please give the directory location of A1CONFIG.DAT [OA$DATA_SHARE]: Enter the location of A1CONFIG.DAT in the format disk:[directory]. You must always specify the location of the configuration file in this format. %A1LUS-I- DEFLOG, Running A1V32START.COM to define the logicals -A1LUS-I-DEFLOG, for your existing ALL-IN- 1 V3.2 Alpha system. . . . _________________________________________________________________ 9 Indicate whether you want to purge files. * Do you want to purge files replaced by this installation [YES]? Press RETURN to purge files. _________________________________________________________________ (continued on next page) 3-12 Installation Procedure: Additional Languages Installation Procedure: Additional Languages 3.2 Installing Architecture Support for an Additional Language Table 3-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 10 Configuration checking. You may be asked questions depending on the configuration of ALL-IN-1 on the Alpha system. This VAX architecture only installation will where possible match the configuration of ALL-IN-1 already installed on the Alpha system. During your first language installation you chose to install ALL-IN-1 without DATATRIEVE, therefore this tool will NOT be available from your ALL-IN-1 additional language. During your ALL-IN-1 installation on Alpha you chose to install ALL-IN-1 with WPS-PLUS, therefore WPS-PLUS will also be installed during this VAX architecture only installation. During your first language installation you chose to install ALL-IN-1 without ACMS, therefore this tool will NOT be available from your ALL-IN-1 additional language. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 3-13 Installation Procedure: Additional Languages 3.2 Installing Architecture Support for an Additional Language Table 3-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 11 Select a default date format. ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis.) This may be changed by each user through the Set Working Conditions option on the User Setup Menu. Alphanumeric Date Numeric Date 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD 7 ***** Reserved (Means system default) ***** 8 DD-MM-YYYY DD/MM/YY (Numeric format) 9 MM-DD-YYYY MM/DD/YY (Numeric format) * Which date format do you require [1]: _________________________________________________________________ 12 Enter the language code. * Enter language code for this installation (2 characters): US Enter the 2-letter language code for your additional language. See the ALL-IN-1 Installation: Language and Market Supplement. _________________________________________________________________ (continued on next page) 3-14 Installation Procedure: Additional Languages Installation Procedure: Additional Languages 3.2 Installing Architecture Support for an Additional Language Table 3-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 13 Enter the dialect code. %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets %VMSINSTAL-I-RESTORE, Restoring product save set B ... If you wish to install a dialectal variation of ENGLISH language, enter the code for the dialect component you wish to use. If you do not wish to install a dialectal variation of ENGLISH language, then accept the answer of NO_DIALECT. * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GB In this example, US_GB is the BRITISH dialect code. _________________________________________________________________ 14 Confirm that the License PAK is registered and loaded. * Does this product have an authorization key registered and loaded [YES]? Press RETURN to continue. _________________________________________________________________ 15 Enter the name of the OpenVMS username of the ALL-IN-1 manager's account. * What is the existing VMS username for the ALL-IN- 1 account [ALLIN1]: The account details are displayed. _________________________________________________________________ 16 Confirm that the account details are correct. * Are all the specified account's characteristics correct [YES]? Press RETURN if the account information is correct. _________________________________________________________________ (continued on next page) Installation Procedure: Additional Languages 3-15 Installation Procedure: Additional Languages 3.2 Installing Architecture Support for an Additional Language Table 3-2 (Cont.) Installation Procedure for Addition of __________________Architecture_Support_for_an_Additional_Language Step__Action_____________________________________________________ 17 Run the IVP (Installation Verification Procedure). * Do you want to run the IVP after the installation [YES]? ______Press_RETURN_to_run_the_IVP._______________________________ All the installation questions have now been completed. The installation procedure will do postinstallation tasks. For manual postinstallation tasks, see Chapter 5. 3-16 Installation Procedure: Additional Languages 4 _________________________________________________________________ Installation Errors and Failure This chapter deals with various error messages you may see while installing ALL-IN-1 Version 3.2 or while the Installation Verification Procedures (IVPs) are running, and explains what to do if the installation or the IVPs fail. While the installation is running it displays various informational messages. It may also display warning or error messages. Read all the messages displayed, and take whatever action they advise. 4.1 Common Error Message That Does Not Require Action The following error message may be ignored if it is displayed during the installation: %DELETE-W-SEARCHFAIL This error occurs randomly. A file is always specified in the error message, but the file has been correctly provided. 4.2 Common Errors Which Require Action Errors can occur during the installation if any of the following conditions exist: o There is a problem with the operating system. o There is a problem with prerequisite software. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The OpenVMS help library is currently in use. Installation Errors and Failure 4-1 4.2 Common Errors Which Require Action o SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB are not present. These files are removed if you tailor OpenVMS. For descriptions of the error messages generated by these conditions, see the OpenVMS books on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. 4.3 Failure During Postinstallation ________________________ Note ________________________ When the installation procedure reaches the postinstallation phase, the main installation has completed. If the postinstallation tasks fail, a message is displayed indicating that the installation has failed and that you need to reinstall ALL-IN-1. It is not necessary to do this; you need only rerun A1$POSTINSTALL.COM as described in this section. You must rerun A1$POSTINSTALL.COM on the node on which you originally ran the installation. ______________________________________________________ The procedure used to execute the automatic postinstallation tasks is written during the installation. Its content depends on the installation type, and conditions specific to your system. The command file is called A1$POSTINSTALL.COM, and it is provided to OA$LIB_ language. If any postinstallation tasks fail, messages to aid investigation are displayed. If the installation has failed during the postinstallation phase, you can do one of the following: o Rerun A1$POSTINSTALL.COM on the node on which you orginally ran the installation. o Edit A1$POSTINSTALL.COM to create your own command procedure using only the commands for the tasks that have failed. 4-2 Installation Errors and Failure 4.3 Failure During Postinstallation When the installation has completed, there are still some manual postinstallation tasks to be performed. See Chapter 5. After the automatic postinstallation tasks have completed, the installation procedure displays: Installation of A1 V3.2 completed at Enter EXIT, or press CTRL/Z to exit from VMSINSTAL. Note that the installation procedure deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account, you must log out and log in again. 4.4 Installation Failure If the installation fails before the postinstallation phase, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of ALL-IN-1 V3.2 has failed. ________________________ Note ________________________ If the installation fails, you must restart the installation from the beginning. ______________________________________________________ 4.4.1 Failure of Upgrade Installations in Safety Mode If your installation is being performed in Safety mode, you need take no further action if the failure happens before the message: Files will now be moved to target directories If the installation fails after this message, restore your original system from a backup. You can then go back to using the original system, or you can start the installation again. Installation Errors and Failure 4-3 4.4 Installation Failure 4.4.2 Failure of Upgrade Installations in Non-Safety Mode If your installation is being performed in non-safety mode, restore your original system from a backup. You can then go back to using the original system, or you can start the installation again. 4.4.3 Full Installations If a full installation fails, delete all accounts, identifiers and directories that have been created, and start the installation again. 4.4.4 Failure Due to Insufficient Dynamic Memory An installation on an Alpha system may fail with the following error message: %SYSTEM-F-INSFMEM, insufficient dynamic memory If this error occurs, you must check that the value for CTLPAGES is high enough. If you used the default value of 100, you must increase it to 200 and restart the installation. See Section 1.7.2. 4.5 Error Messages when Running the IVP The following informational and error messages are displayed when the IVP is run: %OA-I-LNF, Error opening form library "THIS_IS_A_TEST" -RMS-E-FNF, file not found %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not found %OA-E-BADLIB, Error occurred while precompiling THIS_IS_A.TEST form library You can ignore these messages as they are part of tests that are performed by the IVP. If any other error messages occur during the IVP, do the following: 1. Check the log of the installation for any errors that may have occurred during installation. 2. Check the file ALLIN1_IVP.LOG. This file does not contain the results of the IVP, but the results of invoking ALL-IN-1 when running the IVP. This file is in the directory where you run the installation. 4-4 Installation Errors and Failure 4.5 Error Messages when Running the IVP 3. Check for any errors in the following procedures. o During the execution of the startup file, SYS$STARTUP:A1V32START.COM: Creating logical names o Automatic postinstallation procedures Installing image files Compiling and installing form libraries 4. Make sure that the ALL-IN-1 TXL is compiled and installed successfully, and recompile it if you received any error messages when the postinstallation command file was run. 5. Check that you have not run out of quota on the disk(s) containing the OA$SHAREnnnn directories (refer to the manual describing OpenVMS utilities). 6. Check that the details for the IVP account are completed correctly, as follows: o All the ALL-IN-1 privileges are set to YES. o The IVP user directory points to the disk and subdirectory that you specified for the ALL-IN-1 manager's account. For example: a1device:[ALLIN1.IVPUSER] where a1device is the device that you specified during the installation. o The ALL-IN-1 account, IVP, is accessed from the ALL-IN-1 manager's OpenVMS account. 7. Run ALL-IN-1 and try to use those areas that failed during the IVP to find more information on the error. Log in to the ALL-IN-1 manager's IVP account: $ ALLIN1 /USERNAME=IVP Manually execute each IVP test as described in the ALL-IN-1 Management Guide. Installation Errors and Failure 4-5 4.5 Error Messages when Running the IVP ________________________ Note ________________________ The IVP runs in the language context of the current optional language being installed and also tests the international base system. Most IVPs are designed to exercise and test ALL- IN-1 at a level which is normally customization- independent. However, if you have customized the Phone Directory subsystem of ALL-IN-1, the display graphics (IDG) procedure may fail. This is a demonstration test used to exercise the terminal graphics as a typical application. ______________________________________________________ 4.6 IVP Failure If the IVP fails, the following messages are displayed: The A1 V3.2 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for A1 V3.2 has failed. 4-6 Installation Errors and Failure 5 _________________________________________________________________ Postinstallation Tasks This chapter describes the tasks that you must do to complete the setup of ALL-IN-1. Some of these tasks are optional, or only apply to particular types of systems, or configurations. There are a number of additional setup tasks that the ALL-IN-1 manager must do to set up the users' working environment before ALL-IN-1 is used. These tasks are explained in detail in the ALL-IN-1 Management Guide. You must run postinstallation from the node on which you are running ALL-IN-1. 5.1 Checklist of Manual Postinstallation Tasks Table 5-1 lists the manual postinstallation tasks. Table_5-1_Postinstallation_Tasks___________________________ Type of Task__________________Installation_____Information_________ Start ALL-IN-1 Full, upgrade See Section 5.2 on all nodes in or additional a VMScluster system architecture ___________________________________________________________ Create or modify Full or upgrade Section 5.3 the ALL-IN-1 site- specific startup procedure ___________________________________________________________ (continued on next page) Postinstallation Tasks 5-1 5.1 Checklist of Manual Postinstallation Tasks Table_5-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ Modify the OpenVMS Full, upgrade Section 5.4 site-specific or additional startup procedure architecture ___________________________________________________________ Replace the Full, upgrade Section 5.5 DCLTABLES on or additional VMScluster systems architecture ___________________________________________________________ Delete files that Upgrade or Section 5.6 are no longer additional required language ___________________________________________________________ Install any missing Full, upgrade Section 5.7 images or additional architecture ___________________________________________________________ Recompile form Upgrade See Section 5.8. libraries, including This section also application or lists form libraries site-specific form that are compiled libraries automatically after the installation. ___________________________________________________________ (continued on next page) 5-2 Postinstallation Tasks 5.1 Checklist of Manual Postinstallation Tasks Table_5-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ Migrate your Upgrade of Section 5.10 customizations: a customized o Run the CART system resolution procedure o Restore customizations to modified data files o Replace customized help files o Delete obsolete files ___________________________________________________________ Migrate SITELINK31 Upgrade, Section 5.9 using Customization additional Management language and architecture support ___________________________________________________________ Link ALL-IN-1 to Upgrades of Section 5.11 include code-level code-level customizations customized systems and additional architecture if also installed ___________________________________________________________ (continued on next page) Postinstallation Tasks 5-3 5.1 Checklist of Manual Postinstallation Tasks Table_5-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ Check entries in the Upgrade Section 5.12 file, RIGHTSLIST.DAT ___________________________________________________________ Set up remote mail Full or upgrade For new Note that installations with local mail the MAILbus 400 MTA is already set and Digital X.500, up after the see Section 5.13. installation. For upgrade or new installations with Message Router, see Section 5.14. ___________________________________________________________ Convert WPS-PLUS for Migrating users Section 5.15 VMS files from WPS-PLUS for VMS to ALL-IN-1 ___________________________________________________________ Add WPS-PLUS login Full or upgrade Section 5.16. command procedure installations to the system login if you are command procedure using WPS-PLUS as the default editor ___________________________________________________________ Install the File Full or upgrade Section 5.17 Cabinet Server distributed license, if required. ___________________________________________________________ (continued on next page) 5-4 Postinstallation Tasks 5.1 Checklist of Manual Postinstallation Tasks Table_5-1_(Cont.)_Postinstallation_Tasks___________________ Type of Task__________________Installation_____Information_________ Move the CDA DOC_ If CDA$LIBRARY Section 5.18 STYLE files to a does not exist suitable location, on your system if necessary ___________________________________________________________ Update the Facility If DECtrace Section 5.19 Definition for is already DECtrace installed and you want to use it ___________________________________________________________ Set up the user Full or upgrade ALL-IN-1 Management environment Guide ___________________________________________________________ Tune the File Full or upgrade ALL-IN-1 Managing Cabinet Servers Servers ___________________________________________________________ Decide how many mail Full or upgrade ALL-IN-1 Mail Sender and Fetcher Management Guide processes_to_run___________________________________________ 5.2 Start ALL-IN-1 on all Nodes in a VMScluster System The ALL-IN-1 startup procedure, SYS$STARTUP:A1V32START.COM, is supplied with ALL-IN-1 and is executed automatically on the node used for the installation, once the installation has completed successfully. If you are running ALL-IN-1 on a VMScluster you must also run SYS$STARTUP:A1V32START.COM on each node in the cluster in order to start ALL-IN-1. If you run A1V32START.COM manually from the DCL prompt, you must include the location of the ALL-IN-1 configuration file, OA$DATA_ SHARE:A1CONFIG.DAT. OpenVMS prompts you for the location of this file if you do not specify it on the command line. Postinstallation Tasks 5-5 5.2 Start ALL-IN-1 on all Nodes in a VMScluster System If you are creating new shared directories from within ALL-IN-1, you must define new system logical names on each node in the cluster. For further information about running ALL-IN-1 on a VMScluster, see Chapter 5 in the ALL-IN-1 Management Guide. 5.3 Create or Modify the Site-specific ALL-IN-1 Startup Procedure To modify the ALL-IN-1 startup command procedure, you must create a site-specific command procedure. The site-specific startup command procedure will be automatically executed by the ALL-IN-1 startup command procedure when it is executed. You can create the following types of site-specific command procedures: o A language-independent startup command procedure called A1V32_SITE_START.COM. Create this startup procedure in OA$SITE_BUILD_SHARE_IND. o A language-specific startup command procedure, OA$SITE_ language_START.COM, for each language installed in a multilanguage ALL-IN-1 system. Create this startup procedure in OA$SITE_BUILD_LLV_IND. device:[directory.SITE.SOURCES_language]) where: device is the device containing the language files, and directory is the name of the top-level directory of your ALL-IN-1 Version 3.2 system. You can specify the directory for your default language by using the logical name OA$SITE_BUILD_LLV_IND. If you are upgrading and you have a site-specific startup command procedure that you want to keep, rename it from A1V31_SITE_START.COM to A1V32_SITE_START.COM. Check that the contents of the command file are still valid and required for ALL-IN-1 Version 3.2. Note the following changes: o The OA$MTI_AREA logical is now defined in A1CONFIG o The OA$A1_CLUSTER_NODE is now defined in A1CONFIG 5-6 Postinstallation Tasks 5.4 Edit the Site-specific Startup Procedure 5.4 Edit the Site-specific Startup Procedure When you run A1V32START.COM from the DCL prompt, you must include the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT. OpenVMS prompts you for the location of this file if you do not specify it on the command line. When you include the ALL-IN-1 startup procedure in the OpenVMS site startup procedure, you must specify the location of the A1CONFIG.DAT file: $ @SYS$STARTUP:A1V32START.COM location where location is the location of A1CONFIG.DAT, which is specified as: device:[directory.DATA_SHARE] device is the device that you specified for the ALL-IN-1 data files and directory is the top-level directory that you specified for the ALL-IN-1 data files. To find the location of OA$DATA_SHARE:A1CONFIG.DAT, refer to your installation log. ________________________ Note ________________________ However you choose to set up your site-specific startup procedures, you must ensure that all the ALL-IN-1 prerequisite products are started before ALL-IN-1. This includes messaging software, DEC Notes, and DECwindows/Motif if you are using CDA converters with ALL-IN-1. ______________________________________________________ 5.4.1 Installations With Digital X.500 and the MAILbus 400 MTA If you have installed a new ALL-IN-1 system with Digital X.500 and the MAILbus 400 MTA, you must ensure that the prerequisite messaging products are started before ALL-IN-1. Make sure that the following 3 files are executed in the following order: 1. SYS$STARTUP:OSAK$START.COM 2. SYS$STARTUP:DXD$COMMON_STARTUP.COM 3. SYS$STARTUP:MTA$COMMON_STARTUP.COM Postinstallation Tasks 5-7 5.4 Edit the Site-specific Startup Procedure 5.4.2 Installations with Message Router For ALL-IN-1 systems using Message Router, you must ensure that the Message Router software is started before ALL-IN-1. As an example, Table 5-2 describes how to edit the OpenVMS site-specific startup file to include the ALL-IN-1 startup procedure after an upgrade installation from ALL-IN-1 Version 3.1. This ensures that the ALL-IN-1 environment is reestablished following a system reboot. Table_5-2_Editing_the_OpenVMS_Site-specific_Startup_File___ Installation Type_____________Do_the_Following__________________________ Full and To edit the file: addition 1. Find the lines: of second architecture $ @SYS$MANAGER:STARTNET.COM and (unless you are $ @SYS$MANAGER:MB$CONTROL START=(DDS,TS,...,ER)1 using common 2. After these lines, add the following startup files) line: $ @SYS$STARTUP:A1V32START.COM location2 ___________________________________________________________ Upgrade from Change the line ALL-IN-1 $ @SYS$STARTUP:A1V31START.COM location2 Version 3.1 to and addition of second $ @SYS$STARTUP:A1V32START.COM location2 architecture (unless you are using common startup files) [1]The_exact_command_line_will_depend_on_which_Message_____ Router components are running. [2]location is the location of the ALL-IN-1 configuration file, OA$DATA_SHARE:A1CONFIG.DAT. (continued on next page) 5-8 Postinstallation Tasks 5.4 Edit the Site-specific Startup Procedure Table 5-2 (Cont.) Editing the OpenVMS Site-specific Startup __________________File_____________________________________ Installation Type_____________Do_the_Following__________________________ ___________________________________________________________ If you are Add the following entry before the entry running a for the ALL-IN-1 startup procedure: remote Message $ @SYS$STARTUP:DDS$STARTUP.COM node nodenumber Router and where node is the name of the node using the on which the remote Message Router is Message Router installed and nodenumber is the Directory Directory Service node number of the remote Message Service Router node. ___________________________________________________________ 5.5 Replace the DCLTABLES on Cluster Systems If you installed ALL-IN-1 Version 3.2 on a VMScluster system, you must replace the DCLTABLES on any nodes in the cluster where you are not installing ALL-IN-1 Version 3.2. Enter the following commands on each of these nodes: $ INSTALL INSTALL> REPLACE SYS$SHARE:DCLTABLES /OPEN /SHARE - _INSTALL> /HEADER_RES INSTALL> EXIT You need only do this once after you have installed ALL-IN-1 Version 3.2. The ALL-IN-1 installation procedure replaces the tables automatically for the node on which you are installing ALL-IN-1 Version 3.2. 5.6 Delete Files That Are No Longer Required If you have upgraded or updated ALL-IN-1, various files remain in the SYSTEM directories which you can delete to increase your disk space. The files are: o For an ALL-IN-1 Version 3.1 upgrade: SYS$HELP:A1031.RELEASE_NOTES SYS$HELP:A1Llang031.RELEASE_NOTES SYS$HELP:A1Cmarket031.RELEASE_NOTES, if available SYS$STARTUP:A1V31START.COM Postinstallation Tasks 5-9 5.6 Delete Files That Are No Longer Required SYS$HELP:TLC025.RELEASE_NOTES 5.7 Install Missing Images On startup, if any error messages are displayed relating to images that are not installed, use the Install utility to install those images before executing the startup procedure again. Images that you may need to install in this way are those referenced by optional products that you have integrated with the ALL-IN-1 image. For example, the following command installs the image RDBSHR, which is referenced by VAX DATATRIEVE: $ INSTALL INSTALL> ADD SYS$SHARE:RDBSHR /OPEN /HEADER_RES /SHARED For more details of the Install Utility, see the OpenVMS documentation. 5.8 Recompile Form Libraries If you are upgrading from ALL-IN-1 Version 3.1 and you have compiled form libraries on your old system which are not replaced by the upgrade, you may see the following error message: Obsolete form library please recompile If you see this message, recompile the form library. ________________________ Note ________________________ You must also compile application or site-specific form libraries, and your own applications. ______________________________________________________ The following form libraries are compiled automatically: o OAFORM o SITEOAFORM o MEMRES o SITEMEMRES o OAN$FORMS o SITEOAN$FORMS 5-10 Postinstallation Tasks 5.8 Recompile Form Libraries If you have added code or manual procedures to compile other form libraries, you must recompile them manually after the installation. Use the Precompile a form library (PCF) option from the System Customization Management (CSZ) menu. See the ALL-IN-1 Management Guide. 5.9 Migrate SITELINK31 Using Customization Management The SITELINK32.COM file is under the control of Customization Management. It is important that you check that any customizations to SITELINK31.COM are compatible with SITELINK32.COM. Use Customization Management to edit the base template version of the site link file, SITELINK32.COM, to include your previous SITELINK31.COM from OA$SITE_BUILD. Review your customizations to SITELINK32.COM and then move your customized version to LIVE. Review your customizations to make sure they are compatible with ALL-IN-1 Version 3.2. Do not relink ALL-IN-1 until you have done this. See Section 5.10. It is recommended that you do the following to relink: $ SET DEFAULT OA$BUILD_SHARE_ARCH $ @OA$BUILD:A1LNKDRV 5.10 Migrating Your Customizations After Upgrading Immediately after installing ALL-IN-1 Version 3.2, and before allowing your users to access ALL-IN-1, review your customizations to mandatory elements. You can rerun the CART after installing ALL-IN-1 Version 3.2 using the Check Conflicts (CC) option from the Application Maintenance menu. When you run the CART from within ALL-IN-1, it does not produce the site elements report. It does produce the full and summary reports, and the CART resolution procedure, which are all stored as new elements in Customization Management. If you rerun the CART, it does not keep the previous CART full and summary reports. To keep them, use the Customization Management Copy (CO) option to save the elements with another name in the same area, for example, copy CM_CART_SUMMARY_V32$PRIMARY to CM_CART_SUMMARY_ Postinstallation Tasks 5-11 5.10 Migrating Your Customizations After Upgrading V32$PRIMARY_19FEB. All of the elements that you have already processed will have status code F. To review your customizations: 1. From the Customization Management (CM) subsystem, select each element marked as a mandatory change and print the differences between it and the new base element. 2. Review the differences. Note where new functionality has been added or changes made. Note any symbol changes. Use the information in your upgrade plan to make the changes necessary to get your system running. 3. Test your customizations and, if they work correctly, move the elements back into the live area. 4. Before allowing your users back onto the system, review your customizations to recommended elements in the same way as you reviewed the mandatory elements. If you do not resolve conflicts to recommended elements, users may not have access to your customizations or will not have access to the full functionality of ALL-IN-1 Version 3.2. 5. Review conflicts with elements reported with status code D, see the ALL-IN-1 Overview and Planning Guide. Status code D indicates a customization that calls an element which has been removed from ALL-IN-1 Version 3.2. If the element that is called by your customized element has a status code of A, then no customized version of it exists. Your customization will fail if you delete the removed element, as described in Section 5.10.2. Edit the command procedure DELETE_OBSOLETE_FILES.COM so that these elements are not deleted. See Section 5.10.2. Use Customization Management to create a new customized element to replace the referenced base element that no longer exists in ALL-IN-1 Version 3.2. Use Customization Management to copy any elements reported with status code A into the development area. When you rerun the CART, these elements will be reported with status code H. 5-12 Postinstallation Tasks 5.10 Migrating Your Customizations After Upgrading 6. You can now allow your users to access ALL-IN-1 Version 3.2. When it is convenient, resolve the conflicts for informational elements. 5.10.1 Running the CART Resolution Procedure The CART resolution procedure calls individual scripts to process each status code. The scripts are called CM_CART_ SCRIPTn, where n is the CART status code. To run and edit the scripts called by the CART resolution procedure, you must have Application Maintainer privileges for the areas where the elements are stored. See the ALL-IN-1 Management Guide. To run the CART resolution procedure use the Execute procedure (EP) option from the Application Maintainer's Check Conflicts (CC) menu. To change the way that the CART resolution procedure handles elements with a particular status code, do the following: 1. Enter the Customization Management (CM) subsystem. 2. Use the Access base element (ABE) option to select the CART resolution script. 3. Copy the script that you want to change into the development area. 4. Edit the script using Customization Management. It is not mandatory to use the CART resolution procedure to resolve conflicts. If the script does not provide appropriate actions to resolve the conflicts at your site, then you do not have to use it. You can use the CART resolution procedure to resolve some of the conflicts reported with an informational status code. You should review the CART resolution procedure carefully before running it. Check that your customized elements do not call a removed element, see Section 5.10 which describes how to resolve conflicts for elements reported with status code D. Postinstallation Tasks 5-13 5.10 Migrating Your Customizations After Upgrading 5.10.2 Deleting Obsolete Files A command procedure, DELETE_OBSOLETE_FILES.COM, is provided to remove the files that are no longer required by ALL-IN-1 Version 3.2. ________________________ Note ________________________ Do not run this procedure immediately after running the CART resolution procedure. You must always review this file before running it. Check that all your customizations are working correctly and ensure that your customizations do not call any elements that will be deleted by this procedure. ______________________________________________________ You can edit DELETE_OBSOLETE_FILES.COM to stop the deletion of certain files if required, for example, if one of your customizations calls an element that has been removed from the base kit and which would otherwise be deleted by this procedure. For example, the suggested resolution for elements with status code A is to: o Run the CART resolution procedure to delete the records for these elements from the Customization Management databases o Run the command procedure OA$LIB:DELETE_OBSOLETE_FILES.COM to delete the elements To run DELETE_OBSOLETE_FILES.COM, enter the following from DCL: $ @OA$LIB:DELETE_OBSOLETE_FILES.COM language where language is the language of the ALL-IN-1 system. If you have additional languages installed on your system, you can run this procedure for each additional languages. 5-14 Postinstallation Tasks 5.10 Migrating Your Customizations After Upgrading 5.10.3 Restoring Customizations to Data Files Read this section if you copied customized data files according to the instructions in Section 1.8.1. Throughout this section, the form PROFILE.DAT is used as an example. To restore your modifications to your data files, do the following: 1. Make a copy of the new base PROFILE.DAT file, preferably outside the ALL-IN-1 directory structure: $ COPY OA$DATA:PROFILE.DAT disk:[directory]BASE_PROFILE.DAT 2. Make copies of the new base PROFILn forms using Customization Management. For example, copy them to BASE_PROFILn and modify the named data so that the .FILE directive specifies the location of the backup copy of the base format PROFILE file. 3. Make the forms live. 4. Use Customization Management to add your customizations to the new base PROFILn forms and PROFILE.FDL. 5. Make the forms and the FDL files live. 6. Convert PROFILE.DAT to your customized format: prompt: MRM> ADD localnodeA1 /PASSWORD=password /COMPLETE_MESSAGES /IGNORE_SENDER /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS where: o localnode is the name of the ALL-IN-1 node or cluster. The name must be unique to the Message Router system. o password is the ALL-IN-1 mailbox password that you specified during the ALL-IN-1 installation on the remote system. The password that you specify here must be the same as you specified during the ALL-IN-1 installation. If you change the password when creating the mailbox, you must also change it to the same value in ALL-IN-1 by using the Set operating conditions (SOC) option on the Manage Messaging menu. See the ALL-IN-1 Mail Management Guide. ___________________________________________________________ 3 Exit from the Message Router management utility: _____MRM>_EXIT_____________________________________________ Refer to the Message Router documentation for more information about mailboxes. Postinstallation Tasks 5-19 5.14 Setting up Remote Mail When Using Message Router 5.14.2 Modifying the Message Router Mailbox Entry You must modify the Message Router mailbox entry if you have a mixed-architecture cluster and you are using a Message Router in the same cluster. The installation procedure creates a mailbox entry on the Message Router node with the /OWNER=ALLIN1 qualifier. The Alpha node will be unable to connect with this mailbox because the /OWNER qualifier is on the mailbox. Modify the ALL-IN-1 mailbox entry on the Message Router node to remove the qualifier. $ RUN SYS$SYSTEM:MBMAN MRM> MODIFY A1/NOOWNER MRM> EXIT where A1 is the name of the Message Router mailbox. 5.14.3 Configuring the VMSmail Gateway for Remote Access If you have installed the Message Router VMSmail Gateway on one of the nodes in a VMScluster you can set up other ALL-IN-1 nodes so that they can access it. On each of the nodes that does not have the gateway started, define the logical name MRGATE to the following: node::MR% where node is the node where the gateway is running. You can also use a VMSmail Gateway on a node in your network, that is remote to your cluster. You need Message Router to be installed on one of the nodes in your cluster in order to do this. Make an entry for the remote VMSmail Gateway in the mailbox directory of the Message Router Transfer Service on the VAX node in your cluster that is running Message Router: 1. Log in to the MBMANAGER account on the VAX node in your cluster that is running Message Router 2. Enter the following commands: $ RUN SYS$SYSTEM:MRMAN MRM> ADD MRGATE/REPLACE="MRGATE @node" where node is the node where the gateway is installed. 5-20 Postinstallation Tasks 5.14 Setting up Remote Mail When Using Message Router 3. Exit from the Message Router management utility: MRM> EXIT See the Message Router documentation for more information. 5.14.4 Setting Up the Message Router Directory Service as the Mail Directory The tasks that you need to do depend on the following: o If the Message Router node is in the same VMScluster and has ALL-IN-1 installed, see Section 5.14.4.1. o If the Message Router node is not in the same VMScluster or ALL-IN-1 is not installed on the Message Router node, see Section 5.14.4.2. 5.14.4.1 Message Router is in the Same VMScluster Read this section if ALL-IN-1 is installed in the same VMScluster as Message Router and ALL-IN-1 is installed on the Message Router node. You can be using the Mail directory as either the primary or the secondary directory. If, during the installation, you chose to use the Mail directory as the primary directory, OA$DDS_PRIME is set to 2. If, during the installation, you chose to use the Mail directory as the secondary directory with ALL-IN-1 as the primary directory, then OA$DDS_PRIME is set to 1. After installation, the following values are set up: o A user agent entry name and password. - The user agent entry name is OA$node$ALLIN1 for a new or upgrade installation, where node is either the node name or the cluster alias for the system on which you are installing ALL-IN-1. For example, OA$LYNX$ALLIN1. - The user agent entry password is the Mail directory password that you entered during the installation. o A subscriber entry for the ALL-IN-1 manager. The proxy attribute of the subscriber entry is the name of the local ALL-IN-1 user agent entry (OA$node$ALLIN1). This attribute gives ALL-IN-1 proxy access to the manager's entry, so that ALL-IN-1 can update and access the entry. Postinstallation Tasks 5-21 5.14 Setting up Remote Mail When Using Message Router o UAPASSWRD.DAT which contains the name of the user agent object and the user agent password, from the first item in this list. When you set up the Mail directory the values in the previous list are updated. To set up the Mail directory, do the following: ___________________________________________________________ Step_Action________________________________________________ 1 Log in to the ALL-IN-1 manager's ALL-IN-1 account: $ ALLIN1 /USERNAME=MANAGER ___________________________________________________________ 2 Enter the following commands from ALL-IN-1: SHOW TS The area code is displayed, along with other settings, as follows: . . . Transfer Service uses area routing Area Code : areacode . . . where areacode is the area code in use at your site. 3 Enter EXIT, or press CTRL/Z, to exit from the MAILbus configuration procedure. For more details of this command, see the Message Router _____documentation.___________________________________ ___________________________________________________________ 3 Update the user agent entry by entering the following command: BUILD DDS UA /NAME="uaname"/PASSWORD="password" MBMAN> ADD DDS BUILT_OBJECT/LOG where: o uaname is the name of the user agent object. The name is in the form OA$node$ALLIN1, where node is either the node name or the cluster alias for the system on which you are setting up the Mail directory. o password is the password that ALL-IN-1 will use to access the user agent object. It must not be more than eight characters long. ___________________________________________________________ 5-26 Postinstallation Tasks 5.14 Setting up Remote Mail When Using Message Router ___________________________________________________________ Step_Action________________________________________________ 3 Create and add a subscriber entry to the Mail directory for the ALL-IN-1 manager: MBMAN>BUILD DDS SUBSCRIBER /SURNAME="MANAGER" MBMAN>BUILD DDS SUBSCRIBER /PROXY="uaname" MBMAN>BUILD DDS SUBSCRIBER /SUBID="uaname" MBMAN>ADD DDS BUILT_OBJECT/LOG MBMAN>EXIT where: o MANAGER is the name of the ALL-IN-1 manager's ALL-IN-1 account and must be entered as shown. Do not enter any other account name. o uaname is the name of the user agent object that you specified, for example, OA$nodename$ALLIN1. o /PROXY="uaname" grants the local ALL-IN-1 user agent proxy access to the manager's subscriber entry. This enables the ALL-IN-1 user agent to access and update the manager's subscriber entry on behalf of the manager. o /SUBID="uaname" identifies the ALL-IN-1 manager's subscriber entry to ALL-IN-1, as there can be many entries called MANAGER. ___________________________________________________________ 4 On the ALL-IN-1 node (VAX or Alpha), do all the next steps from the ALL-IN-1 manager's ALL-IN-1 account: Enter the following commands to create temporary symbols required by the script which you will run in the next step: SHOW TS The area code is displayed, along with other settings, as follows: . . . Transfer Service uses area routing Area Code : areacode . . . where areacode is the area code in use at your site. c Enter EXIT, or press CTRL/Z, to exit from the MAILbus configuration procedure. For more details of this command, see the Message Router _____documentation.___________________________________ 5-28 Postinstallation Tasks 5.14 Setting up Remote Mail When Using Message Router ___________________________________________________________ Step_Action________________________________________________ ___________________________________________________________ 5 Run the following script: SHOW DDS NODE nodename where nodename is the name of the Message Router node. See Section 5.4 for more information about editing the site-specific startup file. 5.15 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1 Read this section if users have been using WPS-PLUS for VMS and want to use the documents created with WPS-PLUS for VMS from within ALL-IN-1. Postinstallation Tasks 5-29 5.15 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1 ________________________ Note ________________________ To use the converted documents in ALL-IN-1, the WPS-PLUS editor must be installed. ______________________________________________________ To convert WPS-PLUS for VMS documents, do the following: 1. Give each ALL-IN-1 user who wants to convert their WPS-PLUS for VMS documents the ALL-IN-1 DCL and CMD privileges. See the ALL-IN-1 Management Guide for details of setting these privileges. If you normally restrict this access, reset it after conversion is complete. 2. Check that the directory containing the WPS-PLUS for VMS File Cabinet exists by entering the following command: $ DIRECTORY /PROTECTION disk:[username.WPSPLUS...]*.* where disk is the name of the user's OpenVMS disk and username is the OpenVMS username This command lists all the files in the WPS-PLUS for VMS account belonging to the user. 3. Make sure that all files have the following minimum protection: (S:RWD,O:RWE,,) 4. Run ALL-IN-1 from the user account. 5. Enter WP to display the Word and Document Processing menu. 6. Enter the following command: : When conversion is complete, ALL-IN-1 returns you to the Word and Document Processing menu. 10.To convert the User-Defined Process [.UDP] files, do the following: a. From the Word and Document Processing menu, enter $. ALL-IN-1 places you in the subprocess. b. Enter the following command: $ COPY /LOG [username.WPSPLUS.UDP]*.UDP [.UDP]*.* where username is the user's top-level OpenVMS directory, as recorded in the SYS$SYSTEM:SYSUAF.DAT file. c. When the copying is finished, press EXIT to return to ALL-IN-1. 11.Reset the users' privileges. 5.16 WPS-PLUS Login Command Procedure During the ALL-IN-1 Version 3.2 installation procedure, a login command procedure, A1WPSPLUS_LOGIN.COM, is created in SYS$MANAGER. Add this to the system login command procedure, SYS$SYLOGIN, if you want all users to run with these qualifiers. Alternately, you can make the file available to users to put into their own LOGIN.COM files. Postinstallation Tasks 5-31 5.17 Install the File Cabinet Server Distributed License 5.17 Install the File Cabinet Server Distributed License The File Cabinet server handles access to the File Cabinet over the network. If you want to give remote users access to your node, you need the A1-DIST-SHR license. The A1- DIST-SHR license enables the File Cabinet server on your system to accept connections from a File Cabinet server on a remote system. You also need this license if you want to use the ALL-IN-1 Web Interface to make documents in your File Cabinet available to users of Web Browsers. Use the License Management Facility (LMF) to install the A1-DIST-SHR license. For information about LMF, see the LMF documentation. See Chapter 9 in the ALL-IN-1 Management Guide for more information about distributed sharing. 5.18 Moving the CDA DOC_STYLE Files If CDA$LIBRARY does not exist on your system, the CDA DOC_ STYLE files are installed in OA$LIB_SHARE. Move the files to a suitable location. 5.19 Update the Facility Definition to Use DECtrace During the installation of ALL-IN-1 Version 3.2, a Facility Definition file for DECtrace is provided to SYS$SHARE:EPC$FACILITY.TLB. If you install DECtrace after you have installed ALL-IN-1 Version 3.2, the Facility Definition is picked up automatically. 5-32 Postinstallation Tasks 5.19 Update the Facility Definition to Use DECtrace If DECtrace is already installed on your system, and you wish to use it for collecting information about ALL-IN-1 Version 3.2, you must update the Facility Definition as follows: $ LIBRARY/TEXT/EXTRACT=OAV32/OUTPUT=EPC$A1V32-FAC-DEF.EPC$DEF - SYS$SHARE:EPC$FACILITY.TLB $ COLLECT INSERT DEFINITION EPC$A1V32-FAC-DEF.EPC$DEF/REPLACE ________________________ Note ________________________ The Facility Definition File has not been updated for ALL-IN-1 Version 3.2. It is the same as provided in ALL-IN-1 Version 3.1. ______________________________________________________ Postinstallation Tasks 5-33 A _________________________________________________________________ ALL-IN-1 Version 3.2 Distribution Media The ALL-IN-1 kit is provided on its own CD-ROM or as part of the CD-ROM Consolidated Software Distribution. For VAX upgrades, the kit is also available on magnetic tape and TK50. The same ALL-IN-1 savesets are provided on all media. A separate CD-ROM is provided for the ALL-IN-1 Web Interface product. A.1 CD-ROM Distribution Kits (VAX or Alpha Installations) The notes in this section apply to both the ALL-IN-1 Version 3.2 CD-ROM and to the Consolidated Software Distribution CD-ROM. On the Compact Disc (CD-ROM), the base kit is in the directory A1032.KIT. The printable documentation is in a directory called A1032.DOCUMENTATION. For the ALL-IN-1 Version 3.2 CD-ROM, the online versions of the documentation for Bookreader are provided in the DECW$BOOK directory. For each language, there is a directory called A1lang032, where lang is the 2-letter code for the ALL-IN-1 language that you are installing. See the ALL-IN-1 Installation: Language and Market Supplement for a list of savesets for your language, market and dialect components. The base component savesets in the A1032.KIT directory are: ALL-IN-1 Version 3.2 Distribution Media A-1 A.1 CD-ROM Distribution Kits (VAX or Alpha Installations) A1032.A A1032.B (used by VAX only) A1032.C (used by Alpha only) A1032.D (used by VAX only) A1032.E (used by Alpha only) A1032.F (used by VAX only) A1032.G (used by Alpha only) A1032.H (used by VAX only) A1032.I (used by Alpha only) A1032.J A1032.K A1032.L The documentation directory, A1032.DOCUMENTATION contains ASCII (.TXT) and PostScript (.PS) versions of the following documentation: o The ALL-IN-1 Installation: Guide, INST_GUIDE_1.TXT and INST_GUIDE_1.PS o The ALL-IN-1 Installation: Language and Market Supplement, INST_GUIDE_2.TXT and INST_GUIDE_2.PS o The Read Me First letter, READ_ME_FIRST.TXT and READ_ME_ FIRST.PS o The Software Product Description (SPD), A1032_SPD.TXT and A1032_SPD.PS. The CDROM also contains the following software in their own directories: o VAX Forms Management System (FMS) (VAX only) o DEC FMS Version (Alpha only) o Message Router (VAX only) o Message Router VMSmail Gateway (VAX only) o DEC Notes A-2 ALL-IN-1 Version 3.2 Distribution Media A.2 Magnetic Tape and TK50 Kits (VAX Upgrades) A.2 Magnetic Tape and TK50 Kits (VAX Upgrades) The ALL-IN-1 files are supplied on 6250 bpi magnetic tape or TK50 cartridge for VAX upgrades. There are two pieces of media, one for the base component and one for the language and market components. The media is labeled as follows: o Base component: ALL-IN-1 V3.2 BASE BIN media_type BASE COMPONENT A11032 (c) 1996 Digital Equipment Corp. media_type is the code for your distribution media. This media contains the following base component savesets: A1032.A A1032.B (used by VAX only) A1032.C (used by Alpha only) A1032.D (used by VAX only) A1032.E (used by Alpha only) A1032.F (used by VAX only) A1032.G (used by Alpha only) A1032.H (used by VAX only) A1032.I (used by Alpha only) A1032.J A1032.K A1032.L o Language and market component: ALL-IN-1 V3.2 language BIN media_type LANGUAGE/MKT COMPONENT A12032 (c) 1996 Digital Equipment Corp. where media_type is the code for your distribution media and language is the name of the language that you are installing, for example, ENGLISH. This media contains the language, market and dialect (if provided) savesets. See your ALL-IN-1 Installation: Language and Market Supplement. VAX FMS is also included on the language and market media. ALL-IN-1 Version 3.2 Distribution Media A-3 A.2 Magnetic Tape and TK50 Kits (VAX Upgrades) Each saveset has a unique kit revision identifier, for example: A1032BASEA.REV_nnn. All other software provided with your ALL-IN-1 kit is supplied on separate tapes. A-4 ALL-IN-1 Version 3.2 Distribution Media B _________________________________________________________________ ALL-IN-1 Version 3.2 Files and Directories This appendix lists the files that are installed in directories other than the ALL-IN-1 directories. B.1 Files in the ALL-IN-1 Kit For a complete list of all ALL-IN-1 directories and file names when the installation is complete, use the following command for each ALL-IN-1 area: $ DIR/SEC[a1dir...]*.*/out=a1dir.TXT where a1dir is the top level directory name for each area (for example ALLIN1.DIR). The list of files is a useful reference if you need to resolve any problems with file protections or ACLs. B.2 Files Installed in Non-ALL-IN-1 Directories The following list shows the files that are installed in directories other than the ALL-IN-1 directories. Where language is included in a file name, this is the name of the installed language, for example, ENGLISH. o SYS$COMMON:[SYSLIB] OA$AIDA_CSHR.EXE OA$AIDA_DSSHR.EXE OA$AIDA_GCMSHR.EXE OA$AIDA_RTLSHR.EXE OA$AIDA_SECSHR.EXE OA$DSL$SHR.EXE OAFC$CLIENT_SHR.EXE OA$TMAECOMM.EXE ALL-IN-1 Version 3.2 Files and Directories B-1 B.2 Files Installed in Non-ALL-IN-1 Directories DDS$RMT_VAX.EXE (VAX Only) DDS$RMT_ALPHA.EXE (Alpha Only) DPESHR.EXE SYS$PROXY_SHR.EXE OAFCDEF.H OAFCDEF.L32 OAFCEXT.H OAFCEXT.L32 OAFCEXT.R32 OAFC$LINK.OPT PRXDEF.H DDIF$READ_DX.EXE DDIF$READ_MACWRITE.EXE DDIF$READ_PICT.EXE DDIF$READ_RTF.EXE DDIF$READ_WORD5.EXE DDIF$READ_WORDP.EXE DDIF$READ_WPL.EXE DDIF$WRITE_DX.EXE DDIF$WRITE_MACWRITE.EXE DDIF$WRITE_PICT.EXE DDIF$WRITE_RTF.EXE DDIF$WRITE_WORD5.EXE DDIF$WRITE_WORDP.EXE DDIF$WRITE_WPL.EXE DTIF$READ_DIF.EXE DTIF$READ_TCV.EXE DTIF$READ_WK1.EXE DTIF$READ_WK3.EXE DTIF$WRITE_WK1.EXE DTIF$WRITE_WK3.EXE DDIF$READ_RNO.EXE (Alpha Only) MRAPPSHAR.EXE (VAX Only) MRAXPSHAR.EXE (Alpha Only) OA$LLVlanguage.EXE (On Multilingual systems only) OA$WPL_ALL_TV.EXE (Alpha with full WPS-PLUS support only) OA$WPL_FDP_TV.EXE (Alpha without full WPS-PLUS support only) IMP$IMPSHR.EXE (VAX only) IMP$IMPSHRP.EXE (VAX only) B-2 ALL-IN-1 Version 3.2 Files and Directories B.2 Files Installed in Non-ALL-IN-1 Directories XPORT.L32 XPORT.OLB XPORT.REQ o SYS$COMMON:[SYSEXE] A1MAIL$CTI_BROKER.EXE OA$AIDA_CLI.EXE OA$AIDA_DDS.EXE OA$AIDA_PROP_SHARING.EXE OA$AIDA_SERVER.EXE OA$AIDA_X500.EXE OA$SCRIPT_SYMBIONT.EXE OAFC$SERVER.EXE OA$FORMATTER.EXE TLNK$REMOTE.EXE o SYS$COMMON:[SYSMSG] XPORTMSG.EXE OAFC$MESSAGES.OBJ CNV_MSG.DAT DPEMSG.EXE MRAPPMSG.EXE (VAX Only) MRAXPMSG.EXE (Alpha Only) DDS$MSG_ALPHA.EXE (Alpha Only) DDS$MSG_VAX.EXE (VAX Only) DDS$RMT_VAX.EXE (VAX Only) DDS$RMT_ALPHA.EXE (Alpha Only) o SYS$COMMON:[SYS$STARTUP] A1V32START.COM OA$AIDA_START.COM OAFC$STARTUP.COM DDS$STARTUP.COM o SYS$COMMON:[SYSMGR] A1WPSPLUS_LOGIN.COM ALL-IN-1 Version 3.2 Files and Directories B-3 B.2 Files Installed in Non-ALL-IN-1 Directories o SYS$COMMON:[SYSHLP.EXAMPLES] EXAMPLE_READ_DIF.CDA$OPTIONS EXAMPLE_READ_DX.CDA$OPTIONS EXAMPLE_READ_MACWRITE.CDA$OPTIONS EXAMPLE_READ_PICT.CDA$OPTIONS EXAMPLE_READ_RTF.CDA$OPTIONS EXAMPLE_READ_WK1.CDA$OPTIONS EXAMPLE_READ_WK3.CDA$OPTIONS EXAMPLE_READ_WORD5.CDA$OPTIONS EXAMPLE_READ_WORD5_FONTMAP.CDA$OPTIONS EXAMPLE_READ_WORDP.CDA$OPTIONS EXAMPLE_READ_WPL.CDA$OPTIONS EXAMPLE_WRITE_DX.CDA$OPTIONS EXAMPLE_WRITE_MACWRITE.CDA$OPTIONS EXAMPLE_WRITE_PICT.CDA$OPTIONS EXAMPLE_WRITE_RTF.CDA$OPTIONS EXAMPLE_WRITE_WK1.CDA$OPTIONS EXAMPLE_WRITE_WK3.CDA$OPTIONS EXAMPLE_WRITE_WORD5.CDA$OPTIONS EXAMPLE_WRITE_WORDP.CDA$OPTIONS EXAMPLE_WRITE_WORDP_V5_0.CDA$OPTIONS EXAMPLE_WRITE_WORDP_V5_1.CDA$OPTIONS EXAMPLE_WRITE_WPL.CDA$OPTIONS Language specific lexicon files are installed in LCI$LEXICONS if you install WPS-PLUS as the default editor. B-4 ALL-IN-1 Version 3.2 Files and Directories _________________________________________________________________ Index A Customizations (cont'd) _______________________________ reviewing after installation, A1CONFIG.DAT, 5-7 5-12 A1V32START.COM, 5-5, 5-6, 5-7 ALL-IN-1 D starting on all nodes, 5-5 _______________________________ Applications Data files replacing help modules, 5-15 restoring customizations to, AUTOGEN, 1-25 5-15 DCLTABLES B______________________________ replacing, 5-9 Backing up, 1-45 DDS$STARTUP adding to site-specific C startup procedure, 5-29 _______________________________ DEC FMS, A-2 CART DEC Notes running after installation, starting before ALL-IN-1, 5-11 5-7 CART resolution procedure DELETE_OBSOLETE_FILES.COM, running and editing, 5-13 5-14 Checklist Deleting files postinstallation tasks, 5-1 postinstallation, 5-9 Cluster Deleting obsolete files after VMSmail Gateway configuration installation, 5-14 , 5-20 Disk space requirements, 1-27 Configuring Disks VMSmail Gateway, 5-20 backing up, 1-45 Correcting system set-up errors, 1-42 E______________________________ Customizations Error messages, 4-1, 4-4 linking ALL-IN-1 to include, Errors 5-16 fatal, 1-42 migrating, 5-11 non-fatal, 1-42 Index-1 IVP F______________________________ error messages, 4-4 Fatal errors, 1-42 Files, deleting L______________________________ postinstallation, 5-9 License Management Facility, Form libraries 1-14 recompiling, 5-10 Licenses prerequisite products, 1-16 G______________________________ registering, 1-14 Global page file sections Linking ALL-IN-1 to include (GBLPAGFIL), 1-23 customizations, 5-16 Global pages (GBLPAGES), 1-23 Logical names Global sections (GBLSECTIONS), assigning, 1-28 1-23 Logins disallow, 1-45 H______________________________ M Help modules _______________________________ replacing for your Mail directory application, 5-15 setting up with Message Router outside cluster, I______________________________ 5-25 Images setup for Message Router in missing, 5-10 same cluster, 5-21 required, 1-32 starting up for remote use, Installation 5-29 aborting, 2-2 Mailbox disk space required, 1-27 adding for remote ALL-IN-1 time required, 2-2 systems, 5-18 Installation of optional modifying, 5-20 software Message Router, A-2 order of, 1-17 setting up, 5-18 Installed images Message Router mailbox required, 1-32 modifying for mixed- Installing account architecture clusters, licensing, 1-14 5-20 quotas required during Message Router VMSmail Gateway installation, 1-18 , A-2 valid rights identifier, Messages 1-18 error, 4-1 Installing missing images warning, 4-1 postinstallation, 5-10 Migrating customizations, 5-11 Index-2 Relinking N______________________________ recommendations, 5-11 Non-fatal checks, repeating, Remote 1-42 VMSmail Gateway configuration Non-fatal errors, 1-42 , 5-20 Remote mail O setting up with MAILbus 400 _______________________________ MTA and Digital X.500, OA$A1_CLUSTER_NODE 5-16 now defined in A1CONFIG, 5-6 setting up with Message OA$DDS_PRIME, 5-21 Router, 5-17 OA$MTI_AREA Remote Mail directory now defined in A1CONFIG, 5-6 starting up, 5-29 Optional software Repeating non-fatal checks, order of installation, 1-17 1-42 Order of installation of Rightslist entries optional software, 1-17 checking after installation, P 5-16 _______________________________ PC option, 1-42 S______________________________ Perform all preinstallation Site-specific startup checks (PC) option, 1-42 procedure, 5-6 Personal licence adding DDS$STARTUP, 5-29 adding installing account to SITELINK32.COM, 5-11 reserve list, 1-14 Software license, 1-14 Preinstallation Software Product Description, checks, 1-42 A-2 Preparing system for SPD, A-2 installation, 1-44 Starting Prerequisite software ALL-IN-1, 5-5 licenses, 1-16 Startup procedure Product Authorization Key, creating, 5-6 1-14 editing site-specific, 5-7 site specific, 5-6 R______________________________ SYS$STARTUP:A1V32START.COM, Recompiling 5-6 form libraries, 5-10 System Registering software licenses, preparing for installation, 1-16 1-44 Release notes, 1-6 System disk printing, 1-7 backing up, 1-45 reading, 1-7 System parameter values changing with AUTOGEN, 1-25 Index-3 T______________________________ V______________________________ Target disk VAX FMS, A-2 backing up, 1-45 VMSmail Gateway Time required for installation configuring, 5-20 , 2-2 W______________________________ U______________________________ Warning messages, 4-1 Users WPS-PLUS for VMS log out, 1-45 converting documents to ALL-IN-1, 5-29 Index-4