Order Number: AA-N323H-TE Revision/Update Information: Revised for ALL-IN-1 Version 3.0 Operating system: VMS Version 5.4 and higher Software version: Version 3.0 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Possession, use, duplication, or dissemination of the software described in this document is authorized only pursuant to a valid written license from Digital or the third-party owner of the software copyright. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation. © Digital Equipment Corporation 1985 to 1992. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, CDA, DECdx/RSTS, DECmail, DECnet, DECpage, DECtalk, DECwindows, DX, EDT, MicroVAX, TOPS- 20, VAX, VAXcluster, VAX DATATRIEVE, VAX FMS, VAX Notes, VAX RALLY, VAX TEAMDATA, VAX VTX, VMS, WPS-PLUS, and the DIGITAL logo. ACMS is a trademark of McDonnell Douglas H.I.S. Division. Bell is a trademark of Bell telephone companies. Ethernet is a trademark of Xerox Corporation. PostScript is a registered trademark of Adobe Systems, Inc. Vadic is a trademark of Racal-Vadic. Motif is a registered trademark of Open Software Foundation, Inc. WordPerfect is a trademark of WordPerfect Corp. This document was prepared using VAX DOCUMENT, Version 2.0. ________________________________________________________________ Contents Preface.................................................. xiv 1 Introduction 1.1 Before You Begin................................ 1-1 1.2 Types of Installation Procedures................ 1-2 1.3 Installing Additional Languages................. 1-3 1.4 Contents of the Distribution Kit................ 1-4 1.5 VMSINSTAL....................................... 1-4 1.5.1 Keeping a Record of the Installation ......... 1-5 1.5.2 Time Needed for the Installation ............. 1-6 1.6 Running the Installation Verification Procedure (IVP)........................................... 1-6 1.7 Aborting the Installation....................... 1-6 1.8 Directory for ALL-IN-1 Examples................. 1-7 2 Accessing the Online Release Notes 2.1 Accessing the Release Notes..................... 2-1 3 Installing ALL-IN-1 on VAXcluster Systems 3.1 Licenses........................................ 3-1 3.2 Common-Environment Clusters..................... 3-1 3.3 Multiple-Environment Clusters................... 3-2 3.4 Installing ALL-IN-1 on a Local Area VAXcluster System.......................................... 3-5 iii 4 Prerequisite and Optional Software 4.1 Prerequisite Software and Software Supplied with your ALL-IN-1 System............................ 4-1 4.1.1 Licenses for Prerequisite Software ........... 4-3 4.1.2 Integrating Message Router and the Message Router VMSmail Gateway with ALL-IN-1.......... 4-4 4.1.2.1 The Mail Directory and the ALL-IN-1 Directory.................................. 4-5 4.1.2.2 Order of Installation...................... 4-5 4.1.3 CDA Support .................................. 4-6 4.1.4 Integrating WPS-PLUS with ALL-IN-1 ........... 4-7 4.2 Optional Software Products...................... 4-7 4.2.1 Integrating VAX DATATRIEVE with ALL-IN-1 ..... 4-9 4.2.2 Integrating ACMS with ALL-IN-1 ............... 4-9 4.3 Order of Software Installation.................. 4-10 5 Migration Tools 5.1 Conflict Checking and Resolution Tool........... 5-1 5.2 Coexistent Systems.............................. 5-3 5.2.1 Installing a Coexistent System ............... 5-4 5.2.2 Running a Coexistent System .................. 5-4 5.2.3 Deleting a Coexistent System ................. 5-5 6 Preparing Your System 6.1 Register the ALL-IN-1 Version 3.0 License....... 6-1 6.2 Assign Logical Names............................ 6-2 6.2.1 Installed Images ............................. 6-3 6.3 Save PROFILE.DAT and PROFILE.FDL if you have made Customizations............................. 6-4 6.4 Review Object Libraries......................... 6-4 6.5 Review Your Customizations...................... 6-5 6.6 Shared File Cabinet Prototype migration......... 6-5 6.7 Review Printer Tables........................... 6-5 6.8 Prepare Layered Products........................ 6-5 6.9 Ensure Your System is Tidy...................... 6-6 6.10 System Preparation Tasks........................ 6-6 6.10.1 Back Up Your System and Target Disks ......... 6-7 6.10.2 Shut Down ALL-IN-1 ........................... 6-7 6.10.3 Ensure Message Router Directory Service is Running....................................... 6-7 iv 6.10.4 Deinstall Files Installed in Memory .......... 6-8 6.10.5 Move Your Applications to ALL-IN-1 Customization Management...................... 6-8 6.10.6 Start the Queue Manager ...................... 6-9 6.10.7 Run the Mail Sender and Fetcher .............. 6-10 6.10.8 Check and Calculate the Values for GBLPAGES, GBLSECTIONS and GBLPAGFIL..................... 6-10 6.10.8.1 GBLPAGES and GBLSECTIONS................... 6-11 6.10.8.2 Global Pages............................... 6-12 6.10.9 Check the System Parameter Values ............ 6-13 6.10.10 Check Process Account Quotas ................. 6-17 6.10.11 Check the Disk Space ......................... 6-18 6.10.11.1 Disk Quota Allocation...................... 6-20 6.11 Additional Upgrade and Update Installation Preparation Tasks............................... 6-22 6.12 Preinstallation System and Account Checks Option.......................................... 6-23 7 The Installation Procedure: Installations of the Base Component and Base Language 7.1 Invoke VMSinstal................................ 7-2 7.2 Verify Your System Backup....................... 7-3 7.3 Load the Distribution Media (First Volume)...... 7-3 7.4 Indicate the Installation Type.................. 7-4 7.5 Product Authorization Key (PAK)................. 7-5 7.6 Incorporate VAX DATATRIEVE...................... 7-5 7.7 Incorporate WPS-PLUS............................ 7-6 7.8 Incorporate ACMS................................ 7-7 7.9 Indicate Whether to Build a Multilingual System.......................................... 7-7 7.10 Select the Date Format.......................... 7-8 7.11 Greatest Number of Simultaneous ALL-IN-1 Users.. 7-8 7.12 Specify the Batch Queue to Run the Sender and Fetcher......................................... 7-9 7.13 Indicate Whether Your System Should Send and Receive Messages................................ 7-10 7.14 Level of Use of the Mail Directory.............. 7-10 7.15 Password for the ALL-IN-1 Message Router Mailbox......................................... 7-11 7.16 Indicate if you Want Outgoing Messages Translated to ASCII............................. 7-12 7.17 First Check Phase............................... 7-12 v 7.18 Load the Distribution Media - Second Volume..... 7-14 7.19 Dialect Code.................................... 7-15 7.20 Second Check Phase.............................. 7-16 7.21 Devices to Hold the ALL-IN-1 Shared Library, Shared Data, Language and Mail Area Files....... 7-17 7.22 Number of Shared Directories.................... 7-17 7.23 Device for Each Shared Directory................ 7-18 7.24 Device for the Lexicon Files.................... 7-18 7.25 Market Code..................................... 7-19 7.26 Identify or Create a VMS account for ALL-IN-1... 7-20 7.27 UIC for the ALL-IN-1 Transfer Accounts.......... 7-21 7.28 UIC for the Script Symbiont Account............. 7-22 7.29 UIC for the File Cabinet Server Accounts........ 7-22 7.30 Directory for the Shared Files.................. 7-23 7.31 Indicate Whether to Run the IVPs................ 7-24 7.32 All Questions Have Been Completed............... 7-24 7.33 Automatic Postinstallation Tasks................ 7-25 8 The Installation Procedure: Installations of Additional Languages 8.1 Invoke VMSINSTAL................................ 8-2 8.2 Verify Your System Backup....................... 8-2 8.3 Load the Distribution Media..................... 8-3 8.4 Indicate the Installation Type.................. 8-4 8.5 Incorporate VAX DATATRIEVE...................... 8-4 8.6 Incorporate WPS-PLUS............................ 8-4 8.7 Incorporate ACMS................................ 8-5 8.8 Select the Date Format.......................... 8-5 8.9 First Check Phase............................... 8-6 8.10 Product Authorization Key (PAK)................. 8-7 8.11 Dialect Code.................................... 8-7 8.12 Second Check Phase.............................. 8-8 8.13 Identify the VMS Account for ALL-IN-1........... 8-8 8.14 Directory for Language Files.................... 8-9 8.15 Indicate Whether to Run the IVPs................ 8-9 8.16 Wait for the Installation to Complete........... 8-10 8.17 Automatic Postinstallation Tasks................ 8-10 vi 9 Installation Errors and Failure 9.1 Common Error Message That Does Not Require Action.......................................... 9-1 9.2 Common Errors Which Require Action.............. 9-1 9.3 Installation Failure............................ 9-2 9.3.1 All Upgrade Installations .................... 9-2 9.3.2 Upgrade Installations in Safety Mode ......... 9-3 9.3.3 Upgrade Installations in Non-Safety Mode ..... 9-3 9.3.4 Fresh Installations .......................... 9-3 9.4 Error Messages and Failure when Running the IVP............................................. 9-3 9.4.1 Error Messages ............................... 9-3 9.4.2 IVP Failure .................................. 9-5 10 Manual Postinstallation Procedures 10.1 Start ALL-IN-1 on all nodes in a VAXcluster System.......................................... 10-2 10.2 Replace the DCLTABLES on VAXcluster Systems..... 10-2 10.3 Delete Files That Are No Longer Required........ 10-2 10.4 Modify the Manager's ALL-IN-1 Site Startup Command Procedure............................... 10-3 10.5 Modify the VMS System Manager's Site Startup Command Procedure............................... 10-4 10.6 Install Missing Images.......................... 10-6 10.7 Recompile Obsolete Form Libraries............... 10-6 10.8 Link ALL-IN-1 to Include Customizations......... 10-6 10.9 Migrate from SFCP to Version 3.0 Shared Filing.. 10-6 10.10Add a Mailbox Entry to use a Remote Message Router.......................................... 10-11 10.11Setting Up the Message Router Transfer Service.. 10-12 10.11.1 Configuring the VMSmail Gateway .............. 10-13 10.12Setting Up the Mail Directory................... 10-13 10.13Replacing the Help Modules for Your Application..................................... 10-16 10.14Set up the ALL-IN-1 User Environment............ 10-16 10.15Convert WPS-PLUS/VMS Documents to ALL-IN-1...... 10-16 10.16Reapply Customizations to PROFILE.DAT and PROFILE.FDL..................................... 10-20 10.17Rename Sitelink24............................... 10-20 10.18Install the File Cabinet Server Distributed License......................................... 10-20 vii 10.19Update the Facility Definition to Use DECtrace.. 10-21 A ALL-IN-1 V3.0 Distribution Media A.1 Magnetic Tape and TK50 Kits..................... A-1 A.2 Compact Disc Consolidated Software Distribution Kits............................................ A-2 A.3 Files in the ALL-IN-1 Kit....................... A-3 B Files Installed in Non-ALL-IN-1 Directories B.1 Files Installed in Non-ALL-IN-1 Directories..... B-1 Index Tables 1-1 Types of Installation Procedures ............. 1-2 4-1 Prerequisite Software ........................ 4-1 6-1 Values for GBLPAGES and GBLSECTIONS .......... 6-11 6-2 Minimum System Parameter Values Required ..... 6-14 6-3 Process Account Quotas for the Installing Account....................................... 6-17 6-4 Disk Space Required for Each ALL-IN-1 Area For a Fresh Installation.......................... 6-19 6-5 Disk Space Required for Each ALL-IN-1 Area For an Upgrade Installation....................... 6-19 viii ________________________________________________________________ Preface Product: ALL-IN-1 Version 3.0 Purpose of This Guide This guide is Part 1 of two parts. This part describes how to: 1. Prepare the VMS[TM] system for the installation of ALL-IN-1[TM] 2. Install ALL-IN-1 3. Set up ALL-IN-1 so that the ALL-IN-1 manager can log in to ALL-IN-1 and use ALL-IN-1 locally All other tasks required to complete the set up of ALL-IN-1, and for ongoing management, are described in the ALL-IN-1 Management Guide and ALL-IN-1 Mail Management Guide, for example: o Printer setup o Creating accounts o Setting up Message Router and Message Router VMSmail Gateway, if mail messages need to be sent to other systems or VMS users Audience This guide is primarily intended for: o Managers who want to install ALL-IN-1 Version 3.0 and set it up for use xiv o Managers who want to upgrade to ALL-IN-1 Version 3.0 from ALL-IN-1 Version 2.3 or Version 2.4, or ALL-IN-1 STARTER Version 1.0 or Version 2.4 o Managers who want to update their existing ALL-IN-1 Version 3.0 system How To Use This Guide Use this guide as follows: 1. Carry out the steps described in Chapter 2 to access the Release Notes. You must print and read the Release Notes before starting the installation as they may contain information which applies to installation. 2. Read Chapter 6 which describes the tasks you must do before installing ALL-IN-1. 3. Carry out the steps required for the type of instal- lation you are going to perform. These steps are described in Chapter 7 for all installations not involving a second language, and in Chapter 8 for additions, upgrades and updates of second languages. 4. Read Chapter 10 which describes post-installation tasks to complete the set-up of ALL-IN-1 for use on your system. Books in the Management Documentation Set The following documents make up the ALL-IN-1 Management documentation set: o ALL-IN-1 Installation Guide Part 1 Base Installation This part describes the steps required to install ALL-IN-1 and contains information specific to the base component. o ALL-IN-1 Installation Guide Part 2 Language and Market Installation This part contains information specific to the language and market components that you are installing; a version is supplied with each language/market component. Refer to this part as indicated in the ALL-IN-1 Installation Guide Part 1 Base Installation. xv o ALL-IN-1 Release Notes Release Notes contain information about problems in ALL-IN-1 Version 3.0. Where possible, workarounds to the problems are also described. o ALL-IN-1 Management Guide This guide describes the tasks for setting up and managing an ALL-IN-1 system, so that it operates efficiently. The guide also explains how to improve performance, how to incorporate customizations, and how the ALL-IN-1 files are organized within VMS. o ALL-IN-1 Mail Management Guide This guide describes how to manage an ALL-IN-1 mail system. The major management concern is to ensure that all messages sent to and from local ALL-IN-1 users are delivered. o ALL-IN-1 Printer Characteristics This guide describes the use of printer tables, and teaches you how to use the printer table utility to customize existing printer tables to meet your needs. Related Books In addition to the ALL-IN-1 Management documentation set, your ALL-IN-1 kit contains a user documentation set, a superuser documentation set, and an application programming documentation set. You may also need to refer to the documentation on the following products: o VAX FMS[TM] Version 2.4 o ALL-IN-1 Voice Messaging Support Version 1.0 o VAX Message Router Version 3.2 o VAX DATATRIEVE[TM] Version 5.1 o VAX Application Control and Management System (ACMS[TM])Version 3.1 o VAX DECpage[TM] Version 3.1 o DECtalk[TM] Mail Access Version 1.1 xvi o VAX VTX[TM] Version 4.0 o VAX TEAMDATA[TM] Version 1.3 o VAX RALLY[TM] Version 2.1 o DECdx/VMS[TM] Version 1.1 o VAX Notes[TM] Version 2.0 You may need to refer to the VMS books for the version of VMS running on your system. Document Structure ALL-IN-1 Installation Guide Part 1 Base Installation This part describes the installation of ALL-IN-1 Version 3.0. ALL-IN-1 Installation Guide Part 2 Language and Market Installation This part contains language-specific and market-specific information, for the language and market component you are installing. There is a version of this part for each language and market supported by ALL-IN-1 Version 3.0. Your ALL-IN-1 Version 3.0 kit contains a version of this part for each language and market included with the kit. Conventions_____________________________________________________ Convention_______Description____________________________________ Ctrl/x Ctrl/x indicates that you hold down the Ctrl key while you press another key or mouse button (indicated here by x). GOLD x The key sequence GOLD x indicates that you press and release the GOLD key (sometimes labeled PF1) and then you press and release another key (indicated here by x). A key name enclosed in a rectangle indicates that you press that key. xvii ________________________________________________________________ Convention_______Description____________________________________ { } In format descriptions, braces indicate required elements. You must choose one of the elements. [ ] In format descriptions, brackets indicate optional elements. You can choose none, one, or all of the options. Brackets are not optional in the syntax of a VMS directory name or in a data set reference (DSR). ( ) In format descriptions, parentheses delimit the parameter or argument list. . Vertical ellipses indicate the omission of . information from an example because it is not .________________important_to_the_topic_being_discussed.________ xviii 1 ________________________________________________________________ Introduction 1.1 Before You Begin The key to a succesful installation of ALL-IN-1 is thorough preparation and planning. It is important to read all the sections in this guide that are relevant to the type of installation you are performing. If your installation is an upgrade, and your system has any of the following modifications, do not proceed with the installation until you have satisfied yourself that the software will operate correctly after the installation is complete. o Customizations (see Chapter 5) o Other software, for example ALL-IN-1 Desktop products or Wordperfect o Additional printer tables for non-standard printers Digital recommends the use of a separate test system to verify ALL-IN-1 customizations. (See Chapter 5). You should also review your system for non-system wide customizations (those in users' directories), and ensure that system maintenance tasks are up to date, and invalide or obsolete files and accounts have been removed before you start the installation. This chapter contains general information about the different types of installation you can perform, and about making the migration from a previous ALL-IN-1 system to ALL-IN-1 Version 3.0 run smoothly. Introduction 1-1 1.2 Types of Installation Procedures 1.2 Types of Installation Procedures Table 1-1 shows the possible types of installation procedures for Version 3.0. Table_1-1_Types_of_Installation_Procedures________________ Installation_Type_____Additional_Installation_Requirements Install a New ALL- none IN-1 V3.0 system Install Additional none Languages for ALL- IN-1 V3.0 Upgrade ALL-IN-1 Upgrade any existing additional V2.3 or V2.4 to languages to the corresponding ALL-IN-1 V3.0 ALL-IN-1 V3.0 languages. Upgrading ALL- Upgrade your base ALL-IN-1 system IN-1 V2.3 or V2.4 to V3.0 before upgrading additional additional languages languages. to ALL-IN-1 V3.0 languages Upgrade from ALL- Upgrade any existing additional IN-1 STARTER V1.0 languages to the corresponding or V2.4 to ALL-IN-1 ALL-IN-1 V3.0 languages. V3.0 Upgrade ALL-IN-1 Upgrade your base ALL-IN-1 STARTER STARTER V1.0 or V2.4 system to V3.0 before upgrading additional languages additional languages. to ALL-IN-1 V3.0 additional languages Update an Existing Update other languages, if necessary ALL-IN-1 V3.0 System Update an ALL-IN- none 1 V3.0 additional language__________________________________________________ It is not possible to upgrade or add an additional ALL-IN- 1 Version 3.0 language to an ALL-IN-1 Version 2.3 or 2.4 system. 1-2 Introduction 1.2 Types of Installation Procedures For certain changes to your existing ALL-IN-1 Version 3.0 system you do not need to perform an update installation (for example, if you want to reconfigure ALL-IN-1 to use VAX DATATRIEVE). See the chapter on configuring in the ALL-IN-1 Management Guide. 1.3 Installing Additional Languages Read this section only if you are planning to do one of the following types of installation: o Installing additional languages for ALL-IN-1 Version 3.0 o Upgrading ALL-IN-1 Version 2.3 or Version 2.4 additional languages to ALL-IN-1 Version 3.0 additional languages o Upgrading ALL-IN-1 STARTER Version 1.0 or Version 2.4 additional languages to ALL-IN-1 Version 3.0 additional languages o Update of an ALL-IN-1 Version 3.0 additional language Your basic ALL-IN-1 Version 3.0 kit is supplied with the language component for your market. You can use other languages with your ALL-IN-1 Version 3.0 system, in addition to the one supplied with your kit. If you want to install additional languages, you must have specified that you wanted to build a multi-language system when you installed the original language. See the System Support Addendum for a list of the languages supported by your ALL-IN-1 Version 3.0 system. If, during the installation of the original language, you answered NO to the prompt Do you want to build a multi-language system? you must relink ALL-IN-1 Version 3.0 and answer YES to this prompt. See the ALL-IN-1 Management Guide for details on linking the ALL-IN-1 image. Introduction 1-3 1.3 Installing Additional Languages You can install available languages, including the one supplied with your kit, in any order. However, the language that you install when the main ALL-IN-1 Version 3.0 kit is installed is the default language: that is, the one provided by default in the language field of the user's account details, and used by ALL-IN-1 if you do not use the /LANGUAGE qualifier (see Section 10.4) when logging in to ALL-IN-1. You install other languages separately by performing an additional language installation (see Chapter 8). These languages are additional to the default language. The ALL-IN-1 Installation Guide Part 2 Language and Market Installation for the language you want to install tells you: o The language name used for language-specific file, directory, and logical names. o The size of the ALL-IN-1 Version 3.0 language component. You need this information to determine the disk space required for installing that language (see Section 6.10.11). 1.4 Contents of the Distribution Kit To make sure that you have a complete kit, check the contents of your distribution kit against the bill of materials. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. 1.5 VMSINSTAL You install ALL-IN-1 Version 3.0 using VMSINSTAL, from the VMS system manager's account, with full privileges. VMSINSTAL is a DCL utility used to install optional software products on the VMS operating system. It invokes the product's own installation procedure provided on the distribution media, and that procedure controls the rest of the installation. Note that the VMSINSTAL turns off the BYPASS privilege at the start of the installation. 1-4 Introduction 1.5 VMSINSTAL VMSINSTAL requires at least two parameters: o The name(s) of the product(s) being installed. o The name of the device where the distribution media are to be mounted or loaded. You can use either a physical or logical device name. VMSINSTAL invokes a command procedure on the distribution media and that command procedure controls the rest of the installation. 1.5.1 Keeping a Record of the Installation When you install ALL-IN-1 Version 3.0, Digital recommends that you keep a permanent record of the installation. You can do this either by using a hard copy terminal, or by keeping a record of the installation in a log file. If you want to keep a record in a log file enter the command: $ SET HOST 0/LOG=filename where filename is the name of the log file. For example, you might use ALLIN1_INSTALL.LOG. The default is SETHOST.LOG, if filename is omitted. The log file is created in the directory where you entered the command. To use the SET HOST command, you must have DECnet[TM] running on your system. Make a note of the directory where you entered the SET HOST command. If you decide to keep a record of the installation in a log file, you need to allow at least 200 blocks, in addition to the space required for ALL-IN-1 (see Section 6.10.11). If you have a VAXcluster[TM] system, and you are running the VAXcluster Console System (VCS), you can use this to record the installation of ALL-IN-1 Version 3.0. This does not require DECnet to be running, does not use any disk space on the system where the installation is performed, and does not echo any passwords that you enter during the installation. See the manual for the VAXcluster Console System. Introduction 1-5 1.5 VMSINSTAL 1.5.2 Time Needed for the Installation The installation of ALL-IN-1 Version 3.0 can take from two to twelve hours, depending on the type of processor you are using. For example, the installation will take longer on a MicroVAX[TM] system than on a VAX system. The installation of an additional language takes approximately one to three hours. 1.6 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for ALL-IN-1 Version 3.0 verifies the installation. During the installation, you are asked if you want to run the IVP as part of the installation. If you respond YES, VMSINSTAL runs the IVP. Digital recommends that you run the IVP to ensure that ALL-IN-1 Version 3.0 is installed correctly. After the IVP has run, your system may still require some postinstallation work before it is ready for use. See Section 7.33 for information about postinstallation tasks. After ALL-IN-1 Version 3.0 is installed, you can run the IVP independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to ensure that users can access ALL-IN-1 Version 3.0. Instructions on running the IVP are given in the ALL-IN-1 Management Guide. 1.7 Aborting the Installation To abort the installation procedure at any time, press . When you press , the installation procedure deletes all files in the installation temprorary working directory. Any files that have been provided to target locations remain there. See Chapter 9 for information on how to restart the installation. ________________________Note ________________________ VMSINSTAL does not delete any accounts, identifiers, or directory structures that are created. _____________________________________________________ 1-6 Introduction 1.8 Directory for ALL-IN-1 Examples 1.8 Directory for ALL-IN-1 Examples During the installation, a directory is created for ALL- IN-1 examples, such as a sample conference for Group Conferencing. The directory is called ALLIN1_EXAMPLES, and is a subdirectory of the VMS SYS$HELP directory. A subdirectory of ALLIN1_EXAMPLES, lang_EXAMPLES, is created for every language installed. The command file, A1V30START.COM, sets up logical names that point to these directories, as follows: In the system logical name table: o OA$EXAMPLES points to the directory ALLIN1_EXAMPLES o OA$EXAMPLES_LLV points to the subdirectory lang_ EXAMPLES, where lang is the base language. o OA$EXAMPLES_LANG points to the subdirectory lang_ EXAMPLES, where lang is the secondary language. In the language logical name table: o OA$EXAMPLES_LLV points to the subdirectory lang_ EXAMPLES, where lang is the secondary language. You might find it useful to create your own examples specific to your system or to your organization's procedures, for example, a monthly report format. You can place your own examples in these directories. Introduction 1-7 2 ________________________________________________________________ Accessing the Online Release Notes ALL-IN-1 Version 3.0 provides online Release Notes. The Release Notes contain information that was unavailable before the books went to print. It is important to read the Release Notes, because they may contain information relating to the installation. There are two parts to the Release Notes: o Release Notes Part 1 Language This part contains the release notes specific to the ALL-IN-1 Version 3.0 international base component and to the language being installed. o Release Notes Part 2 Market This part contains the release notes specific to your ALL-IN-1 Version 3.0 market component. ________________________Note ________________________ This document may not exist for all market compo- nents. _____________________________________________________ 2.1 Accessing the Release Notes To access the Release Notes: 1. Log in to the privileged VMS system manager's account. 2. Establish the following default directory: $ SET DEFAULT SYS$UPDATE 3. Enter the following command: $ @VMSINSTAL product device: OPTIONS N Accessing the Online Release Notes 2-1 2.1 Accessing the Release Notes product is the product code: A1Llang030 for the Release Notes Part 1 Language or A1Cmarket030 for the Release Notes Part 2 Market device is the device on which the tape containing the appropriate version of the Release Notes is mounted. The following message is displayed: VAX/VMS Software Product Installation Procedure V. It is at . and are the current date and time, and is the version of VMS that your system is running. Enter a question mark (?) at any time for help. 4. VMSINSTAL displays: * Are you satisfied with the backup of your system disk [YES]? As you are only printing the Release Notes, it is safe to continue, so press . 5. VMSINSTAL then prompts you to mount the distribution media: Please mount the first volume of the set on : where is the device you specified. If you are performing an additional language installa- tion, you need only print the ALL-IN-1 Release Notes Part 1 Language that is supplied with your kit. VMSINSTAL displays: * Are you ready? At this prompt, mount the language volume of the distribution media. (If you are unfamiliar with the loading of media, refer to the VMS software installation documentation.) 2-2 Accessing the Online Release Notes 2.1 Accessing the Release Notes When you have mounted the volume, enter YES and press . VMSINSTAL tries to mount the distribution volume. If it succeeds, a message is displayed, for example: %MOUNT-I-MOUNTED, A12030 mounted on : where is 3 for the ALL-IN-1 Release Notes Part 1 Language and 2 for the ALL-IN-1 Release Notes Part 2 Market, and is the device where the media is mounted. The following message is then displayed: The following products will be processed: V3.0 Beginning installation of V3.0 at where is the current time and is: o A1Llanguage for the ALL-IN-1 Release Notes Part 1 Language o A1Rmarket for the ALL-IN-1 Release Notes Part 2 Market 6. VMSINSTAL displays: %VMSINSTAL-I-RESTORE, Restoring product saveset A... Release Notes Options: 1 Display Release Notes 2 Print Release Notes 3 Both 1 and 2 4 Copy release notes to SYS$HELP 5 Do not display, print, or copy the release notes * Select option [3]: Enter the number of the option that you require. If you enter 2, or 3, to print the Release Notes, the following message is displayed: * Queue name [SYS$PRINT]: Press if you want to print the Release Notes on SYS$PRINT. If you do not want to print on SYS$PRINT, enter the name of the printer queue you want to use. Accessing the Online Release Notes 2-3 2.1 Accessing the Release Notes The following message is then displayed: * Do you want to continue the installation [N]? Press to accept the default answer of NO. The following messages are displayed: %VMSINSTAL-I-RELMOVED, The product Release Notes have been successfully moved to SYS$HELP. Installation of V3.0 completed at VMSINSTAL procedure done at where is the current time and is: A1Llanguage for the ALL-IN-1 Release Notes Part 1 Language A1Cmarket for the ALL-IN-1 Release Notes Part 2 Market If you have accessed only one part of the Release Notes, repeat steps 3 to 8 for the other part. If you chose to print the Release Notes, or copy them to SYS$HELP, the following files are placed in SYS$HELP: o A1Llang030.RELEASE_NOTES, for the Release Notes Part 1 Language o A1Cmarket030.RELEASE_NOTES, for the Release Notes Part 2 Market ________________________Note ________________________ It is important to read the Release Notes before installing ALL-IN-1. _____________________________________________________ 2-4 Accessing the Online Release Notes 3 ________________________________________________________________ Installing ALL-IN-1 on VAXcluster Systems ALL-IN-1 Version 3.0 can be installed on a common-environment cluster, a multiple-environment cluster, or a Local Area VAXcluster. 3.1 Licenses If you are planning to run ALL-IN-1 on a VAXcluster system, you must make sure that all the licenses you need are registered on all nodes on which you intend to use the software. 3.2 Common-Environment Clusters In a common-environment cluster, the operating environment is identical on each member node, because the nodes are run from the same system files. The nodes are set up with identical user accounts, the same known images (such as the ALL-IN-1 image) are installed, the same logical names are defined, and mass storage devices and queues are shared. In effect, users in a common-environment cluster can log in to any node and work in the same operating environment. For example, ALL-IN-1 will be installed on one node only, but will be available to users on all nodes. When running ALL-IN-1 on a common-environment cluster: o You can spread the ALL-IN-1 areas around your VAXcluster disks, just as you would for a single-node system (see Section 6.10.11). o You must check the VMS system parameters, as described in Section 6.10, on each node in the VAXcluster on which you are going to run ALL-IN-1. Installing ALL-IN-1 on VAXcluster Systems 3-1 3.2 Common-Environment Clusters o The housekeeping procedure which creates new shared directories has to define new system logical names on each node in a VAXcluster. You must ensure that the new names are defined on every node in the cluster for which the new shared directories will be created. Use the Manage node specific batch queues (MNQ) option on the Manage Mail Areas menu to do this. See the ALL-IN-1 Management Guide for details. o The default value of the logical name OA$PRIMARY_NODE is set by A1V30START.COM after the installation has completed, as follows: - If you are using a remote Message Router, OA$PRIMARY_NODE is set to the name of the node on which the Message Router is resident. - If you are installing ALL-IN-1 on a VAXcluster, and cluster aliasing is enabled, OA$PRIMARY_NODE is set to the cluster alias. - If you are using a local Message Router and cluster aliasing is not enabled, OA$PRIMARY_NODE is the name of the node on which the Message Router is resident. The node name represented by this logical name is used in ALL-IN-1 directory addressing as the node name for all users on the cluster. It is also used by Electronic Messaging in the return address for all mail sent to other computer systems via Message Router. For further information about clusters, see the VMS VAXcluster documentation. 3.3 Multiple-Environment Clusters In a multiple-environment cluster, the environment varies from node to node, and users can work in environments that are specific to the node that they are logged in to. A multiple-environment cluster is effective when you want to share data among member nodes, but when you want certain nodes to serve specialized needs. A multiple-environment cluster can be considered as having different parts, each part providing a different environment. 3-2 Installing ALL-IN-1 on VAXcluster Systems 3.3 Multiple-Environment Clusters For example, you might want to set up a three-node cluster in which ALL-IN-1 can be used on two nodes, while the third node is set up exclusively for batch processing of large inventory jobs. In this case, the nodes from which ALL-IN-1 is available are set up with a common environment, sharing users, queues, and access to mass storage devices, while the third node runs in its own restricted environment and ALL-IN-1 is unavailable. However, you must run the ALL-IN-1 startup command procedure, SYS$STARTUP:A1V30START.COM, on all the nodes in the part of the cluster with the common environment. Another configuration might have four nodes split into two parts (two nodes in each part), with both parts providing distinct common environments. If you want to run ALL-IN-1 on all four nodes, you must install ALL-IN-1 in each part. However, the ALL-IN-1 system on one part is available only to users logged in to that part of the cluster. The two ALL-IN-1 systems are managed separately. When running ALL-IN-1 on a multiple-environment cluster: o You must check the VMS system parameters, as described in Section 6.10, on each node in the part of the cluster on which you are going to run ALL-IN-1. o ALL-IN-1 is only available to users that are logged in to the part on which ALL-IN-1 is installed. If a part of the cluster does not have ALL-IN-1 installed, users logged in to a node in that part of the cluster cannot use ALL-IN-1. Therefore, users (including batch jobs) of an ALL-IN-1 system must make sure that they are running on the part of the cluster containing the ALL-IN-1 system that they want to use. o The ALL-IN-1 housekeeping procedures and the Sender and Fetcher must be assigned to a batch queue. You must use a queue specific to the part of the cluster on which the ALL-IN-1 system is running. If your system has a cluster-wide generic queue which points to all queues in the cluster you must not use that queue. Installing ALL-IN-1 on VAXcluster Systems 3-3 3.3 Multiple-Environment Clusters o The housekeeping procedure which creates new shared directories has to define new system logical names on each node in a VAXcluster. You must ensure that the new names are defined on every node in the part of the cluster containing the ALL-IN-1 system for which the new shared directories will be created. Use the Manage node specific batch queues (MNQ) option on the Management menu to do this. See the ALL-IN-1 Management Guide for details. o You must install Message Router, if you want to send and receive remote mail. If you want to use Mail directory addressing, you must install Message Router Version 3.1 on the same part of the cluster on which you are going to install the ALL-IN-1 system. In this case, Message Router is referred to as a local Message Router. ________________________Note ________________________ Mail directory addressing can only be used on certain multiple-environment cluster configurations. See the Message Router Installation Guide for details. _____________________________________________________ You can use Message Router on another part of the cluster, or on another system, if you do not have enough disk space on the part where you are going to install ALL-IN-1. In this case, Message Router is referred to as a remote Message Router. You cannot use Mail directory addressing with a remote Message Router. The main points to remember when running ALL-IN-1 in a multiple-environment cluster are: o Users must log in to the right part of the cluster to use ALL-IN-1. o Batch queue names should be specific to the part of the cluster running ALL-IN-1. 3-4 Installing ALL-IN-1 on VAXcluster Systems 3.3 Multiple-Environment Clusters o To use the Mail directory, you must install Message Router Version 3.1 in the same part as ALL-IN-1. However, the Mail directory can only be used on certain multiple-environment cluster configurations (see the Message Router Installation Guide for details). You can use a remote Message Router, but you cannot use the Mail directory. For further information about clusters, see the VMS VAXcluster documentation. 3.4 Installing ALL-IN-1 on a Local Area VAXcluster System You can install ALL-IN-1 Version 3.0 on a local area VAXcluster system. A local area VAXcluster system consists of a boot node (a VAX system or MicroVAX system containing all the disks from which ALL-IN-1 is run) connected by Ethernet to a number of satellite nodes, usually MicroVAX systems. If you are using a local area VAXcluster system, Digital recommends that you install ALL-IN-1 on the boot node. This node is likely to be the only node where disk space is available to run ALL-IN-1. The satellite nodes are for the individual work groups only, and they use the boot node to access ALL-IN-1 files. You must check the VMS system parameters as described in Section 6.10, on each node in the local area VAXcluster system on which you are going to run ALL-IN-1. Installing ALL-IN-1 on VAXcluster Systems 3-5 4 ________________________________________________________________ Prerequisite and Optional Software You can install a variety of other software with ALL- IN-1. Some of this software is necessary in order to run ALL-IN-1, and ALL-IN-1 can be integrated other software optionally. 4.1 Prerequisite Software and Software Supplied with your ALL-IN-1 System Table 4-1 shows the software that must be installed on your system in order to run ALL-IN-1. Table_4-1_Prerequisite_Software___________________________ Minimum Software_Product______Version_____Comment_________________ Prerequisite_base_software________________________________ VMS Operating System V5.4 Must be a full, untailored system. DECnet-VAX V5.1 DECnet-VAX must be running and configured before you install ALL-IN-1 VAX FMS+ V2.4 FMS must be running before you install ALL-IN-1. +This_software_is_supplied_with_ALL-IN-1__________________ (continued on next page) Prerequisite and Optional Software 4-1 4.1 Prerequisite Software and Software Supplied with your ALL-IN-1 System Table_4-1_(Cont.)_Prerequisite_Software___________________ Minimum Software_Product______Version_____Comment_________________ Prerequisite_base_software________________________________ VAX Notes+ V2.1 ALL-IN-1 Version 3.0 can be installed without VAX Notes but cannot support Group Conferencing until VAX Notes is installed and started. Message Router+ V3.1 ALL-IN-1 Version 3.0 can be installed without this product but cannot then be used to send remote mail. If you want to send remote mail, the product must be running before you install ALL-IN-1. Message Router V3.1 ALL-IN-1 Version 3.0 VMSmail Gateway+ can be installed without this product but cannot then be used to send mail to VMSmail users. If you want to send mail directly to VMSmail users, Message Router VMSmail Gateway must be running before you install ALL-IN-1. __________________________________________________________ Prerequisite_software_for_CDA[TM]_support_________________ +This_software_is_supplied_with_ALL-IN-1__________________ (continued on next page) 4-2 Prerequisite and Optional Software Prerequisite Software and Software Supplied with your ALL-IN-1 System Table_4-1_(Cont.)_Prerequisite_Software___________________ Minimum Software_Product______Version_____Comment_________________ Prerequisite_software_for_CDA[TM]_support_________________ CDA V1.3 (supplied with DECWindows on VMS V5.4) CDA Converter V1.1 libraries+ CDA Interoperability CDAPAT011 Contains CDA base Kit services. Required for full CDA support. You can have limited CDA support without this kit +This_software_is_supplied_with_ALL-IN-1__________________ __________________________________________________________ See the VAX FMS Installation Guide and Release Notes for details of installing VAX FMS. (If you want to run the sample programs supplied with VAX FMS you must have at least one compiler installed on your system.) 4.1.1 Licenses for Prerequisite Software If you want to install any of the following products from the kits supplied with ALL-IN-1, you must register the licenses for these products, before you install them. o VAX FMS o Message Router o Message Router VMSmail Gateway o CDA Converter Library The licenses 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 kit. Prerequisite and Optional Software 4-3 4.1 Prerequisite Software and Software Supplied with your ALL-IN-1 System Register the licenses as follows: 1. Invoke VMSINSTAL: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL A1030 device: where device: is the device on which the distribution media is to be mounted. You can use either a physical or logical device name. Logical device names must not begin with either A1$, OA$ or OA1$. 2. Answer YES to the prompt: * Are you satisfied with the backup of your system disk [YES]? 3. VMSINSTAL subsequently displays a list of installation options. Enter RL at the prompt: * What type of installation do you wish to perform [1]: VMSINSTAL checks your existing licences, and if necessary registers and loads the appropriate licenses for the prerequisite and integrated products provided with the ALL-IN-1 kit. VMSINSTAL then exits. 4.1.2 Integrating Message Router and the Message Router VMSmail Gateway with ALL-IN-1 Before you install ALL-IN-1, read the chapter on planning in the ALL-IN-1 Mail Management Guide, to decide how to set up the mail system. Message Router Version 3.1 and Message Router VMSmail Gateway (MRGATE) Version 3.1 are supplied with ALL-IN-1 Version 3.0. The ALL-IN-1 installation procedure will not allow you to integrate with an earlier version of Message Router. If you install Message Router and MRGATE on the same node as your ALL-IN-1 Version 3.0 system, you can: o Use Mail directory addressing o Send mail to users of remote ALL-IN-1 systems o Send mail to local and remote VMSmail users 4-4 Prerequisite and Optional Software Prerequisite Software and Software Supplied with your ALL-IN-1 System If you only install Message Router, you can: o Use Mail directory addressing o Send mail to users of remote ALL-IN-1 systems You are unable to send mail to local or remote VMSmail users. If you do not install Message Router you can only send mail to ALL-IN-1 users on your node and you cannot use Mail Directory addressing. However, it is possible to integrate ALL-IN-1 with a Message Router installed on a remote node. If you integrate with a remote Message Router, you can send mail to remote ALL-IN-1 users (on any node), but you cannot use Mail Directory addressing. 4.1.2.1 The Mail Directory and the ALL-IN-1 Directory There are two directories for addressing available with ALL-IN-1: the Mail directory and the ALL-IN-1 directory. Both hold names and electronic mail addresses of users in the network. The Mail directory is provided by the Directory Service component of Message Router, while the ALL-IN-1 directory is provided with ALL-IN-1. For more information about the two types of directory, and for help with deciding which one to use, see the chapter on planning in the ALL-IN-1 Mail Management Guide. 4.1.2.2 Order of Installation If you want to use the Mail Directory, you must install Message Router on your local system before you install ALL-IN-1. If you already have Message Router Version 3.1 installed on your system, make sure it is configured before you install ALL-IN-1 Version 3.0. If you want to install Message Router after you have installed ALL-IN-1 Version 3.0, you must install and configure Message Router and then perform an update installation of ALL-IN-1. For more information on installing and using Message Router and MRGATE, refer to the Message Router and Message Router VMSmail Gateway books, and the ALL-IN-1 Mail Management Guide. Prerequisite and Optional Software 4-5 4.1 Prerequisite Software and Software Supplied with your ALL-IN-1 System 4.1.3 CDA Support CDA support is available as for ALL-IN-1 Version 2.4 if you install CDA Version 1.3 and CDA Converter libraries Version 1.1. However a higher level of support is available if you install the CDA Interoperability kit. The CDA Interoperability kit allows you to store CDA documents as unpacked individual files in the File Cabinet, rather than in the DOTS format. The installation procedure checks whether the minimum CDA support software is installed, and if it is, checks whether the CDA patch is also installed. If the patch is not installed, the procedure asks if you want to continue without full CDA support. If you choose to continue without CDA support, or without full CDA support, you can install the missing CDA product after you have installed ALL-IN-1. You must relink ALL-IN-1 if you install CDA after the ALL-IN-1 installation. Installing the CDA Interoperability kit upgrades CDA support to that available with DECWindows Motif[TM] Version 1.0. If you install DECWindows Motif Version 1.0 after you have installed the patch, you need to reinstall the patch. WPL to DDIF converters are provided whether or not you choose to have CDA support. The CDA DOC_STYLE files are proveded to CDA$LIBRARY, if that directory exists, or to OA$LIB_SHARE as a temporary location if CDA$LIBRARY does not exist. A script to update the format master record with the CDA format and the name of the converters is run as an automatic postinstallation task, if full CDA prerequisites are present. If you do not have CDA installed, but install it subsequently, you must run the WPL to DDIF postinstallation script manually. 4-6 Prerequisite and Optional Software Prerequisite Software and Software Supplied with your ALL-IN-1 System 4.1.4 Integrating WPS-PLUS with ALL-IN-1 You can install WPS-PLUS Version 4.1 when you install ALL-IN-1. An installation question asks whether you want to integrate WPS-PLUS. If you choose to integrate WPS-PLUS it is fully integrated with ALL-IN-1 and is available as the default editor. You do not need additional software to integrate WPS-PLUS, as everything required is provided in the ALL-IN-1 kit. After installation there are a number of tasks you must perform before users can use WPS-PLUS, for example, setting terminal and queue characteristics (see the ALL-IN-1 Management Guide for details). If WPS-PLUS/VMS already exists on your system, you can still integrate and use WPS-PLUS with ALL-IN-1 (see Section 10.15 for details). If you integrate WPS-PLUS with ALL-IN-1, you may be able to use various spell-checking lexicons. See the ALL-IN-1 Installation Guide Part 2 Language and Market Installation for the spell-checking lexicon that is supplied with your kit, and for any other optional products. ________________________Note ________________________ Lexicons are only available for certain language versions of ALL-IN-1 Version 3.0. _____________________________________________________ 4.2 Optional Software Products Read this section only if you are planning to do one of the following types of installation: o New ALL-IN-1 Version 3.0 installation o Upgrade from ALL-IN-1 Version 2.3 or 2.4 o Upgrade from ALL-IN-1 STARTER Version 1.0 or 2.4 o Update of ALL-IN-1 Version 3.0 Prerequisite and Optional Software 4-7 4.2 Optional Software Products You can integrate some other Digital software products with ALL-IN-1. These products fall into two categories: o Products that are linked with the ALL-IN-1 image. The installation procedure asks if you want to integrate these products. o Products that can be used from ALL-IN-1, but are not linked to the ALL-IN-1 image. There are no questions about these products in the installation procedure. The following products can be purchased separately and linked with the ALL-IN-1 image: o VAX DATATRIEVE Version 5.0 or higher. See Section 4.2.1. Digital does not support the use of any earlier version of VAX DATATRIEVE with ALL-IN-1 Version 3.0. o VAX Application Control and Management System (ACMS) Version 3.1 or higher. See Section 4.2.2 Digital does not support the use of any earlier version of ACMS with ALL-IN-1 Version 3.0. The following products can be used from ALL-IN-1: o VAX DECpage Version 3.1 DECpage is an ALL-IN-1 option that you install separately. When VAX DECpage Version 3.1 is installed after ALL-IN-1, it is accessible from the Word and Document Processing (WP) menu within ALL-IN-1. It is not necessary to link VAX DECpage software to ALL-IN-1. o VAX VTX Version 4.0 VTX is an ALL-IN-1 option that you install separately. When VAX VTX Version 4.0 is installed after ALL-IN-1, it is accessible from the Information Management (IM) menu within ALL-IN-1. It is not necessary to link VAX VTX software to ALL-IN-1. o VAX TEAMDATA Version 1.3 o VAX RALLY Version 2.1 4-8 Prerequisite and Optional Software 4.2 Optional Software Products o Language and Specialized Lexicons. See the ALL-IN-1 Installation Guide Part 2 Language Installation for the language and specialized lexicons supported. (The language and specialized lexicons are only available for certain languages.) o DECtalk Mail Access Version 1.1. o DECdx/VMS Version 1.1 DECdx/VMS is required only to allow users to transfer DX[TM] documents between Digital's mainframe computers (in conjunction with DECdx/RSTS, DECdx/RSX and DECdx/TOPS-20) If you are upgrading to ALL-IN-1 Version 3.0, and you are currently running any ALL-IN-1 layered products, you may need to prepare the layered product(s) before you install ALL-IN-1 Version 3.0 (see your layered product documentation). 4.2.1 Integrating VAX DATATRIEVE with ALL-IN-1 If you integrate VAX DATATRIEVE Version 5.0 with ALL-IN-1, you can use the ALL-IN-1 DTR function to make VAX DATATRIEVE applications available from ALL-IN-1. See ALL-IN-1 Application Programming: Reference Volume 2 for details. The ALL-IN-1 installation procedure asks if you want to integrate VAX DATATRIEVE with ALL-IN-1. If you plan to answer yes to this question, make sure that DATATRIEVE is installed and started before you install ALL-IN-1. 4.2.2 Integrating ACMS with ALL-IN-1 ACMS is a software tool that makes online applications easier to develop. If you want to integrate ACMS with ALL-IN-1 make sure that ACMS is installed and started before you install ALL-IN-1. Prerequisite and Optional Software 4-9 4.3 Order of Software Installation 4.3 Order of Software Installation The following installation order is recommended: 1. Install VAX FMS Version 2.4, if it is not already installed on your system. 2. Install ACMS Version 3.1, or higher, if you want to incorporate it with ALL-IN-1 Version 3.0. 3. Install VAX DATATRIEVE Version 5.1, or higher, if you want to incorporate it with ALL-IN-1 Version 3.0. 4. Install Message Router Version 3.1, if you want to send and receive messages to and from other systems, or you want to use Mail directory addressing, or you want to send mail to VMSmail users, either on the local system or to remote systems. 5. Configure Message Router Version 3.1, if it is installed and not yet configured. 6. Install Message Router VMSmail Gateway Version 3.1, if you want to send mail to VMSmail users, either on the local system or remotely. 7. Configure Message Router VMSmail Gateway Version 3.1, if it is installed and not yet configured. 8. Install CDA Converter Library Version 1.1. 9. Install the CDA Interoperability kit, CDAPAT011. 10.Install VAX Notes Version 2.1 11.Install ALL-IN-1 Version 3.0. 12.Configure exception reporting routines for ALL-IN-1 Version 3.0 Electronic Messaging subsystem. ________________________Note ________________________ WPS-PLUS Version 4.1 is supplied with ALL-IN-1. If you choose to integrate WPS-PLUS with ALL-IN-1, it is available as the default editor in ALL-IN-1. _____________________________________________________ 4-10 Prerequisite and Optional Software 5 ________________________________________________________________ Migration Tools ALL-IN-1 Version 3.0 helps you to assess the implications that an upgrade will have on customizations you have made to your previous ALL-IN-1 system in the following ways: o The Conflict Checking and Resolution Tool (CART) reports on conflicts between your cutomized elements and ALL-IN-1 Version 3.0 elements. o You can run ALL-IN-1 Version 3.0 as a coexistent system while you assess the impact on your customizations. 5.1 Conflict Checking and Resolution Tool The Conflict Checking and Resolution Tool (CART) is a tool you can use if you are upgrading from ALL-IN-1 Version 2.3 or Version 2.4, to check customizations you have made to your ALL-IN-1 system. You run the CART before you upgrade your customized ALL-IN-1 system, using an option from the installation procedure. The CART compares the names of your customized elements with the Version 3.0 new, changed, and deleted elements, and produces reports that show you any conflicts. There are two reports available: o Summary report This report tells you which of your customized elements conflict with ALL-IN-1 Version 3.0 elements. o Full report Migration Tools 5-1 5.1 Conflict Checking and Resolution Tool This report tells you which of your customized elements conflict with ALL-IN-1 Version 3.0 elements, gives the reason the Digital element was changed, and suggests resolutions for the conflict. The report also tells you if your customized elements call files or messages that have been deleted. The CART also produces an ALL-IN-1 script to implement all the suggested resolutions given in the Full report. You can run this script to make the changes suggested, or, if you want, you can edit the script to incorporate your own solutions. The script is available, but you do not have to use it. To run the CART, start the installation procedure for ALL- IN-1 as given in Chapter 7. When you reach the list of possible installation types and other options, choose the option to run the CART (RC) in response to the question: * What type of installation do you wish to perform ________________________Note ________________________ You must make sure that the value of JTQUOTA is sufficient for installation before you run the CART. See Table 6-3 for the value required. _____________________________________________________ The installation procedure does not continue after it has run the CART. Start the installation procedure again, and choose the appropriate option when you are ready to install ALL-IN-1 Version 3.0. It is also possible to run the CART after you have installed ALL-IN-1 Version 3.0. See the ALL-IN-1 Management Guide for more information. ________________________Note ________________________ For ALL-IN-1 Version 2.4, the information supplied in the reports produced by the CART was contained in Differences Between ALL-IN-1 Version 2.3 and ALL-IN-1 Version 2.4. This book has not been produced for ALL-IN-1 Version 3.0. _____________________________________________________ 5-2 Migration Tools 5.2 Coexistent Systems 5.2 Coexistent Systems If your current system is a single language ALL-IN-1 Version 2.4 system, it is possible to install ALL-IN-1 Version 3.0 along with your existing system, and to have them running together while you familiarize yourself with the new features and assess the impact on your customizations. While you are running the coexistent system, you can transfer your customized files to it and make any modifications necessary. Transfer your customized files by creating new elements on your coexistent system and use GOLD GET to import the customized element. When you have completed the changes to your customizations you can perform an upgrade and then transfer the customized files to your upgraded system. Do not delete the coexistent ALL-IN-1 Version 3.0 system until you have transferred your customized files to your new system. ________________________Note ________________________ Do not transfer your customized files to your previous system before upgrading. The system is unlikely to work after you have done so, and you may encounter difficulties when you perform the upgrade. _____________________________________________________ You can transfer the cutomized files from your coexistent system to your live system by packaging them as an application in Customization Management (see the ALL-IN-1 Management Guide for information). ________________________Note ________________________ There are no procedures provided to move your customizations from your previous ALL-IN-1 system to ALL-IN-1 Version 3.0. _____________________________________________________ ______________________ Caution ______________________ It is not possible to merge your coexistent system with your previous ALL-IN-1 system. You must perform Migration Tools 5-3 5.2 Coexistent Systems an upgrade installation when you are ready to use ALL-IN-1 Version 3.0 as your main system. _____________________________________________________ 5.2.1 Installing a Coexistent System The installation procedure for a coexistent system is similar to the procedure for installing a full ALL-IN-1 Version 3.0 system. 1. Complete the preparation tasks described in Chapter 6. Where calculations are necessary treat the installation as a fresh installation, for example when calculating the amount of free disk space required. 2. Start the installation procedure as shown in Chapter 7. 3. When you reach the menu of possible types of instal- lations, choose the option to install a coexistent system. The installation procedure continues as for a full ALL-IN-1 Version 3.0 installation. 5.2.2 Running a Coexistent System When the coexistent system is installed, you can run it by typing the following command: $ @SETOA 1 The command is included in the file LOGIN.COM for the coexistent system's ALL-IN-1 manager's account, so logging in to this account will allow you to run the coexistent system automatically. Users are not transferred to the coexistent system, so if you want users to have access to it you will have to create new user accounts for them. 5-4 Migration Tools 5.2 Coexistent Systems 5.2.3 Deleting a Coexistent System When you have finished assessing the impact of the new system on your customizations, you should delete the coexistent system completely. To delete the coexistent system do the following: 1. Log in to the ALL-IN-1 manager's account for the coexistent system 2. Enter the command: $ @OA$LIB DELETE_CO-EX device name:[directory]A1CONFIG.DAT where device name:[directory] is the location of the file A1CONFIG.DAT The command procedure deletes most files, directories, logicals, and so on, created for the coexistent system, but there are some exceptions, for example installed images that are necessary for ALL-IN-1, but may also be used by other products. If the coexistent system is installed on a VAXcluster, the deletion procedure only deassigns logicals, removes installed images, and so on, on the node that that it is being run on. While the procedure is running, error messages are displayed on the screen if manual actions are required. You may find it useful to keep a log of the procedure in order to capture the messages. Read the error messages carefully, as you will need to take decisions and perform actions manually if required. The deletion procedure deletes the ALL-IN-1 manager's account and the deletion command procedure, DELETE_CO- EX.COM. The deletion procedure does not remove any disk quota that has been allocated. Migration Tools 5-5 6 ________________________________________________________________ Preparing Your System This chapter describes the preparations you need to make to your system before you install ALL-IN-1 Version 3.0. 6.1 Register the ALL-IN-1 Version 3.0 License You must ensure that you have an ALL-IN-1 license registered. If you are installing a new ALL-IN-1 Version 3.0 system, then register your ALL-IN-1 Version 3.0 software license, using the VMS License Management Facility (LMF). The license registration information you need is contained in the Product Authorization Key (PAK) is supplied with ALL-IN-1 Version 3.0. The PAK is a paper certificate that contains information about the license you must have in order to run a particular piece of software. You must register your ALL-IN-1 Version 3.0 license before you perform the installation. During the installation, you are asked if you have registered and loaded the ALL-IN-1 Version 3.0 license. To register a license, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with information from your Product Authorization Key (PAK). o Issue the DCL command, LICENSE REGISTER, together with the appropriate qualifiers that correspond to information on the PAK. If you are upgrading from ALL-IN-1 Version 2.4, you already have a license registered and loaded. ALL-IN-1 Version 3.0 uses this license. Preparing Your System 6-1 6.1 Register the ALL-IN-1 Version 3.0 License A license was issued with ALL-IN-1 Version 2.3. If you are upgrading from Version 2.3, ensure that the license is registered and loaded. The ALL-IN-1 Version 3.0 installation checks for a registered license when it begins. If a license is not found, the installation terminates. ________________________Note ________________________ You cannot use the Register Licenses for Prerequisite Products (RL) option offered at the beginning of the installation procedure, unless you have a valid ALL-IN-1 license registered. _____________________________________________________ For complete information on using LMF, see the manual on the License Management Utility in the VMS documentation set. 6.2 Assign Logical Names Digital recommends that you assign logical names wherever possible. For example, you should assign logical names to your disks. To avoid creating logical names that might conflict with the system logicals, make sure to assign logical names that do not start with A1$, OA$, or OA1$. (For example, do not assign the logical name A1$DEVICE.) In all types of installation, the procedure checks for conflicting logical names which could cause the installation to fail. An informational message displays any conflicting logical names that are found. You can remove the conflicting logical names from another process, and then repeat the check. The installation will not continue until the logical name checking has passed. In a full ALL-IN-1 Version 3.0 installation, the logical name checking includes a check for any existing logical names which start with OA$. An informational message lists the names found, and a warning message warns you that these logical names may be redefined. 6-2 Preparing Your System 6.2 Assign Logical Names 6.2.1 Installed Images Make sure that the shareable image and message files in the following list are installed on your system before installing ALL-IN-1. o SYS$MESSAGE:FDVMSG.EXE o SYS$SHARE:CONVSHR.EXE o SYS$SHARE:FDLSHR.EXE o SYS$SHARE:FDVSHR.EXE o SYS$SHARE:LBRSHR.EXE o SYS$SHARE:MTHRTL.EXE (for a MicroVAX II, or a MicroVAX 2000, the file is SYS$SHARE:UVMTHRTL.EXE) o SYS$SHARE:NMLSHR.EXE o SYS$SHARE:PASRTL.EXE o SYS$SHARE:SCNRTL.EXE o SYS$SHARE:SCRSHR.EXE o SYS$SHARE:VMSRTL.EXE o SYS$SHARE:VAXCRTL.EXE o DNS$SHR.EXE o DNS$RTL.EXE To check whether these images are installed on your system, enter the following: $ INSTALL INSTALL> LIST image image is the image to be checked. For example, SYS$SHARE:CONVSHR. If the Install Utility cannot find an entry for an image, install the image as follows: INSTALL> CREATE image /OPEN /SHARED /HEADER_RES INSTALL> EXIT ________________________Note ________________________ If the images FDVMSG.EXE and FDVSHR.EXE are not in- stalled, edit the command procedure SYS$STARTUP:FMSTARTUP.COM, Preparing Your System 6-3 6.2 Assign Logical Names to remove the EXIT command before the entry RUN SYS$SYSTEM:INSTALL, and then execute the command procedure. _____________________________________________________ If there is an entry for the image, check that the display shows the following information: imagename.EXE Open Hdr Shar imagename is the name of the image. For example, CONVSHR. If the display does not show this information, change the way that the image is installed as follows: INSTALL> REPLACE image /OPEN /SHARED /HEADER_RES INSTALL> EXIT For details of installing shareable image files, see the VMS manual describing the Install Utility. 6.3 Save PROFILE.DAT and PROFILE.FDL if you have made Customizations If you are performing an upgrade and you have tuned OA$DATA:PROFILE.DAT by modifying OA$LIB:PROFILE.FDL, save the .FDL file before upgrading. A new PROFILE.FDL file is provided during installation, and this is used to convert the existing PROFILE.DAT to the ALL-IN-1 Version 3.0 format. You will need to reapply any modifications to the new .FDL file after the installation is complete, by referring to the .FDL file you saved before upgrading. Note that the saved .FDL file cannot be used directly. 6.4 Review Object Libraries If you are performing an upgrade, and you have any object libraries or files (.OLB or.OBJ) in the directories OA$SITE_BUILD_SHARE or OA$SITE_BUILD_LLV, check whether they are incompatible with ALL-IN-1 Version 3.0. Remove any that are incompatible, because although they are not used during the installation, they will cause problems if you need to relink ALL-IN-1 later. If .OBJ or .OLB files are found in these directories during the installation, a warning is displayed. 6-4 Preparing Your System 6.5 Review Your Customizations 6.5 Review Your Customizations If your installation is an upgrade and you have customized your system, review your customizations, to ensure that they are not incompatible with ALL-IN-1 Version 3.0. You can use the Conflict Checking and Resolution Tool (CART) to help you with this task (see Chapter 5). Digital recommends the use of a separate test system to check your customizations. If you do not have a system available to dedicate to testing, you can run ALL-IN-1 Version 3.0 as a coexistent system (see Chapter 5). If individual users of your system have customized their own environment, check that these customizations are not incompatible with ALL-IN-1 Version 3.0. The installation sets an ACL on all files in the site areas. You must ensure that all files on every node in the cluster have system write access (s:w) and deinstall any files that are installed in memory since this will prevent them being write locked. 6.6 Shared File Cabinet Prototype migration There is a manual postinstallation task to convert from the Shared File Cabinet Prototype (SFCP) to ALL-IN-1 Version 3.0 drawers. If you have customized the SFCP, you need to plan to edit the postinstallation script as necessary. 6.7 Review Printer Tables If you are performing an upgrade, and you have added or changed any printer tables, with the printer table utility (PTU), make a note of their contents as you will probably need to remake the changes after the upgrade. 6.8 Prepare Layered Products If you run any ALL-IN-1 layered products, for example ALL-IN-1 Desktop products, or Wordperfect, you may need to prepare the layered products before you install ALL-IN-1 Version 3.0 (see your layered product documentation). Preparing Your System 6-5 6.9 Ensure Your System is Tidy 6.9 Ensure Your System is Tidy Make sure that general system maintenance tasks are up to date, and that invalid or obsolete files and accounts have been removed before you start the installation. This will contribute to the smooth running of the installation procedure. 6.10 System Preparation Tasks To prepare your system for the installation of ALL-IN-1 Version 3.0, carry out the following steps before starting the installation, and mark off each action as you complete it. Each step is described in the following sections. You must carry out these actions from a privileged SYSTEM account. 1. Back up the system disk and any target disks, if applicable. 2. Shut down ALL-IN-1 3. Ensure that the Message Router Directory Service is running if you want to use the Mail directory. 4. Deinstall files in the site areas that are installed in memory. 5. If you are doing an upgrade or update installation, move your applications to ALL-IN-1 Customization Management. 6. Start the queue manager, if necessary. 7. If you are doing an upgrade or update installation, run the Mail Sender and Fetcher. 8. Check and calculate adequate values for global pages, global sections, and global page file sections. 9. Check the system parameter values and modify them, if necessary. 10.Check the process quotas and increase them, if necessary. 11.Check the required disk space. 6-6 Preparing Your System 6.10 System Preparation Tasks 6.10.1 Back Up Your System and Target Disks You should back up your system disk and, if you are going to install ALL-IN-1 Version 3.0 on more than one disk, back up those disks that are to be used during the installation. Do this because: o If a system failure occurs at a critical point during installation, 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. 6.10.2 Shut Down ALL-IN-1 Ask users currently on the system to log out and then shutdown ALL-IN-1. Do not allow anyone to log into ALL-IN-1 again while the installation is in progress. You can allow VMS 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. Shut down ALL-IN-1. 6.10.3 Ensure Message Router Directory Service is Running If you want to use Mail directory addressing (see Section 4.1.2.1), make sure that the Message Router Directory Service is running. If you are installing ALL-IN-1 on a multiple-environment cluster, the Message Router Directory Service must be running on the part on which you are installing ALL-IN-1 (see Section 3.3). Preparing Your System 6-7 6.10 System Preparation Tasks 6.10.4 Deinstall Files Installed in Memory If you have any files in the site areas that are installed in memory, deinstall them before you start the installation. Also check that all files have system write access. 6.10.5 Move Your Applications to ALL-IN-1 Customization Management Read this section only if you plan to do an upgrade or update installation. If you have an application that was not created using the ALL-IN-1 Customization Management subsystem, and you want to move the application to ALL-IN-1 Customization Management, you must save the appropriate elements as customizations. As explained below, this includes any applications (elements) that are supported by Customization Management, whether or not they have been customized as yet, and any types that are not supported by Customization Management. Uncustomized Elements Supported by Customization Management If your application contains uncustomized elements, do the following: 1. From the Customization Management menu of ALL-IN-1 Version 2.3 or Version 2.4, select the Access DIGITAL Elements (ADE) option to display the Access DIGITAL Elements menu. 2. Press