                                             H                     ALL-IN-1____________________________________________'                     Installation: Guide     -                     Order Number: AA-N323K-TE       F                     Revision/Update Information:  Revised for ALL-IN-1=                                                   Version 3.2   I                     Operating system:             OpenVMS VAX Version 6.1 G                                                   or higher and OpenVMS F                                                   Alpha Version 6.1 or8                                                   higher  =                     Software version:             Version 3.2                       1                     Digital Equipment Corporation *                     Maynard, Massachusetts                 J           ________________________________________________________________           January 1996  B           Possession, use, or copying of the software described inC           this documentation is authorized only pursuant to a valid D           written license from Digital or an authorized sublicensor.  A           While Digital believes the information included in this E           publication is correct as of the date of publication, it is +           subject to change without notice.   @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           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,A           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. D           Appletalk and Macintosh are registered trademarks of Apple           Computer, Inc.C           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 6           International Business Machines Corporation.<           1-2-3 and Lotus are registered trademarks of Lotus"           Development Corporation.D           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.9           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.   E           This document was prepared using VAX DOCUMENT, Version 2.1.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................     ix   +   1  Preparing Your System for Installation   C         1.1   Checklist of Preinstallation Tasks............    1-2 5         1.2   Reading and Printing the Online Release C               Notes.........................................    1-6 C         1.3   Checking Prerequisite and Optional Software...    1-8 5         1.4   Checking the License for the Installing C               Account.......................................   1-14 <         1.5   Registering License Product Authorization KeysC               (PAKs)........................................   1-14 6         1.5.1     Registering the ALL-IN-1 License PAKC                   Before a new Installation.................   1-15 6         1.5.2     Registering the ALL-IN-1 License PAKC                   Before an Upgrade.........................   1-15 7         1.5.3     Registering License PAKs for Software C                   Provided with ALL-IN-1 Version 3.2........   1-16 3         1.6   Example Order for Installing Optional C               Software......................................   1-17 C         1.7   Installation Procedure Requirements...........   1-18 C         1.7.1     Installing Account Requirements...........   1-18 C         1.7.2     System Parameters.........................   1-19 C         1.7.3     Displaying Current System Parameters......   1-23 C         1.7.4     Changing System Parameter Values..........   1-23 ;         1.7.4.1     Updating Dynamic System Parameters with C                     AUTOGEN.................................   1-25 9         1.7.4.2     Updating Non-Dynamic System Parameter C                     with AUTOGEN............................   1-25 3         1.7.5     Disk Space on Your System Disk or C                   Alternate Working Device..................   1-26 C         1.7.6     Using the OA$LIB_SHARE Disk as the AWD....   1-27     C                                                                 iii                    ;           1.7.7     Disk Space for ALL-IN-1 Areas on Target E                     Disks.....................................   1-27 E           1.7.8     Assigning Logical Names to Your Disks.....   1-28 =           1.7.9     New Installation: Disk Space for ALL-IN-1 E                     Areas.....................................   1-29 8           1.7.10    Upgrade Installation: Disk Space forE                     ALL-IN-1 Areas............................   1-30 :           1.7.11    Addition of Architecture Support: DiskE                     Space for ALL-IN-1 areas..................   1-31 E           1.7.12    Disk Quota Allocation.....................   1-32 E           1.7.13    Installed Images..........................   1-32 8           1.7.14    Installing FDVMSG.EXE and FDVSHR.EXEE                     Images....................................   1-36 E           1.7.15    Installing Other Images...................   1-37 E           1.7.16    Checking The Location of DCLTABLES.EXE....   1-37 E           1.8   Additional Tasks for Upgrade Installations....   1-37 E           1.8.1     Copying Customized Data Files.............   1-38 E           1.9   Using the MAILbus 400 MTA and Digital X.500...   1-40 E           1.10  Using a Remote Message Router.................   1-40 <           1.10.1    Create an ALL-IN-1 Mailbox on the RemoteE                     Message Router Node ......................   1-41 E           1.11  Running the Preinstallation System Check......   1-42 E           1.11.1    Types of Errors Reported..................   1-42 ;           1.11.2    Running the Perform all Preinstallation E                     Checks (PC) Option........................   1-43 3           1.12  Final System Preparation Tasks: New E                 Installations.................................   1-44 7           1.13  Final System Preparation Tasks: Upgrade E                 Installations ................................   1-44 E           1.13.1    Shut Down ALL-IN-1........................   1-45 E           1.13.2    Deinstall Files Installed in Memory.......   1-45 E           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 UpgradeE                 Installations.................................    2-3 E           2.2   Adding or Upgrading Architecture Support......   2-30 E           2.2.1     Before You Start..........................   2-31 5           2.2.2     Installation Procedure for Adding E                     Architecture Support......................   2-31 E           2.3   Automatic Postinstallation Tasks..............   2-42          iv                   I               2.4   Manual Postinstallation Tasks.................   2-43   7         3  Installation Procedure: Additional Languages   B               3.1   Installation Procedure for Additional LanguageI                     Installations.................................    3-2 :               3.2   Installing Architecture Support for anI                     Additional Language...........................   3-10   *         4  Installation Errors and Failure  >               4.1   Common Error Message That Does Not RequireI                     Action........................................    4-1 I               4.2   Common Errors Which Require Action............    4-1 I               4.3   Failure During Postinstallation...............    4-2 I               4.4   Installation Failure..........................    4-3 B               4.4.1     Failure of Upgrade Installations in SafetyI                         Mode......................................    4-3 ;               4.4.2     Failure of Upgrade Installations in I                         Non-Safety Mode...........................    4-4 I               4.4.3     Full Installations........................    4-4 ;               4.4.4     Failure Due to Insufficient Dynamic I                         Memory....................................    4-4 I               4.5   Error Messages when Running the IVP...........    4-4 I               4.6   IVP Failure...................................    4-6   !         5  Postinstallation Tasks   I               5.1   Checklist of Manual Postinstallation Tasks....    5-1 ?               5.2   Start ALL-IN-1 on all Nodes in a VMScluster I                     System........................................    5-5n?               5.3   Create or Modify the Site-specific ALL-IN-1KI                     Startup Procedure.............................    5-6LI               5.4   Edit the Site-specific Startup Procedure......    5-7 @               5.4.1     Installations With Digital X.500 and theI                         MAILbus 400 MTA...........................    5-7nI               5.4.2     Installations with Message Router.........    5-8rI               5.5   Replace the DCLTABLES on Cluster Systems......    5-9 I               5.6   Delete Files That Are No Longer Required......    5-9 I               5.7   Install Missing Images........................   5-10,I               5.8   Recompile Form Libraries......................   5-10_:               5.9   Migrate SITELINK31 Using CustomizationI                     Management....................................   5-11     I                                                                         ve i  s              3           5.10  Migrating Your Customizations AfteriE                 Upgrading.....................................   5-11sE           5.10.1    Running the CART Resolution Procedure.....   5-13aE           5.10.2    Deleting Obsolete Files...................   5-14oE           5.10.3    Restoring Customizations to Data Files....   5-15d7           5.10.4    Replacing the Help Modules for YoureE                     Application...............................   5-15s3           5.11  Link ALL-IN-1 to Include Code-levelrE                 Customizations................................   5-16rE           5.12  Check Entries in RIGHTSLIST.DAT...............   5-16 =           5.13  Setting up Remote Mail When Using the MAILbus E                 400 MTA.......................................   5-16 9           5.14  Setting up Remote Mail When Using Message E                 Router........................................   5-17 E           5.14.1    Create a Mailbox for ALL-IN-1.............   5-1838           5.14.2    Modifying the Message Router MailboxE                     Entry.....................................   5-20m>           5.14.3    Configuring the VMSmail Gateway for RemoteE                     Access....................................   5-20a;           5.14.4    Setting Up the Message Router DirectorylE                     Service as the Mail Directory.............   5-21t3           5.14.4.1    Message Router is in the SamekE                       VMScluster..............................   5-21e7           5.14.4.2    Message Router is not in the Same E                       VMScluster..............................   5-25o;           5.14.5    Remote Message Router Directory Service E                     Startup Procedure.........................   5-29 =           5.15  Convert WPS-PLUS for VMS Documents For Use inkE                 ALL-IN-1 .....................................   5-29 E           5.16  WPS-PLUS Login Command Procedure..............   5-31 ;           5.17  Install the File Cabinet Server DistributeddE                 License.......................................   5-32tE           5.18  Moving the CDA DOC_STYLE Files................   5-32s5           5.19  Update the Facility Definition to Use E                 DECtrace......................................   5-32p                         vi s                 3         A   ALL-IN-1 Version 3.2 Distribution Medias  :               A.1   CD-ROM Distribution Kits (VAX or AlphaI                     Installations)................................    A-1_I               A.2   Magnetic Tape and TK50 Kits (VAX Upgrades)....    A-3   6         B   ALL-IN-1 Version 3.2 Files and Directories  I               B.1   Files in the ALL-IN-1 Kit.....................    B-1aI               B.2   Files Installed in Non-ALL-IN-1 Directories...    B-1   
         Index              Tables  I               1-1       Preinstallation Checklist.................    1-2.  I               1-2       Prerequisite and Optional Software........    1-9   A               1-3       Process Account Quotas for the Installing I                         Account...................................   1-19   7               1-4       Minimum System Parameter Values I                         Required..................................   1-20   I               1-5       Changing System Parameter Values..........   1-24l  A               1-6       New Installation: Disk Space for ALL-IN-1-I                         Areas.....................................   1-30.  =               1-7       Upgrade Installations: Disk Space forrI                         ALL-IN-1 Areas ...........................   1-31   6               1-8       Addition, Upgrade or Update of<                         Architecture Support: Disk Space forI                         ALL-IN-1 Areas............................   1-32   I               1-9       Installed Images Required on VAX..........   1-32.  I               1-10      Installed Images Required on Alpha........   1-34i  :               2-1       Information About the InstallationI                         Procedure.................................    2-2   B               2-2       Installation Procedure for New and UpgradeI                         Installations.............................    2-4n  <               2-3       When to Install/Upgrade VAX or AlphaI                         Architecture Support......................   2-30e  9               2-4       Installation Procedure for Adding.I                         Architecture Support......................   2-32D  @               3-1       Installation Procedure for An AdditionalI                         Language .................................    3-3r  I                                                                       vii. .  .              :           3-2       Installation Procedure for Addition of:                     Architecture Support for an AdditionalE                     Language..................................   3-10.  E           5-1       Postinstallation Tasks....................    5-1   =           5-2       Editing the OpenVMS Site-specific Startup1E                     File......................................    5-8   E           5-3       Tasks for Setting up Remote Mail..........   5-17                                                                            viii    t                        I         _________________________________________________________________R  I                                                                   Preface                About This BookO  G               Before you use this book, you must plan your ALL-IN-1[TM]cH               Version 3.2 installation by reading the  ALL-IN-1 Overview!               and Planning Guide.   ;               This guide describes how to do the following:1  @               1. Prepare your system for an ALL-IN-1 Version 3.2                  installation.  .               2. Install ALL-IN-1 Version 3.2.  I               3. Set up ALL-IN-1 Version 3.2 so that the ALL-IN-1 manager /                  can log in and use it locally.1  =         ALL-IN-1 Installation: Language and Market Supplement.  H               The  ALL-IN-1 Installation: Language and Market SupplementH               is provided with your language and market kit. It providesG               the disk space values for installing the ALL-IN-1 Version A               3.2 kit, and information on the language and markettD               components that you will need during the installation.           Prerequisite Knowledge  A               This guide assumes that you have read the  ALL-IN-1 *               Overview and Planning Guide.  G               To install ALL-IN-1 Version 3.2 you must be familiar witht$               the VMSINSTAL utility.      I                                                                        ixl o  r              -     The ALL-IN-1 Management Documentation Set   ;           The following guides form the ALL-IN-1 management            documentation set:  2           o   ALL-IN-1 Overview and Planning Guide  *           o   ALL-IN-1 Installation: Guide  C           o   ALL-IN-1 Installation: Language and Market Supplement2  '           o   ALL-IN-1 Management Guidee  ,           o   ALL-IN-1 Mail Management Guide  '           o   ALL-IN-1 Managing Servers   2     Terminology and Conventions Used in this Guide  C           The following table lists the terminology and conventionsa           used in this guide..  E           ___________________________________________________________gE           Term____________Description________________________________g  @           AIDA Server     The ALL-IN-1 Distributed Access Server  =           ALL-IN-1        Means the ALL-IN-1 software that is A                           provided by the ALL-IN-1 Office Service.=                           Option that you have installed. For A                           example, the ALL-IN-1 Integrated Office E                           System (IOS) or the ALL-IN-1 Core Services.   C           architecture    Used to differentiate between OpenVMS[TM]-D                           VAX[TM] systems and OpenVMS Alpha systems.E                           For example, architecture-independent files.D                           are files that can be used on both VAX and(                           Alpha systems.  D           _AXP            Used to show ALL-IN-1 directories that areD                           specific to Alpha systems. _VAX is used toC                           show directories that are specific to VAXl"                           systems.  C           Digital[TM]     Means the Digital X.500 Directory Service !           X.500           product.  ?           IOS             Integrated Office System. This is the A                           full ALL-IN-1 license that includes all 4                           components of the product.       x     P            I               ___________________________________________________________sI               Term____________Description________________________________e  D               MAILbus[TM]     Means the MAILbus 400 Message Transfer#               400 MTA         Agent   G               mixed           a VMScluster[TM] that contains both Alpha.,               architecture    and VAX nodes.               cluster-  F               OpenVMS Alpha   Means the OpenVMS Alpha operating system  D               OpenVMS VAX     Means the OpenVMS VAX operating system  D               TCP/IP          Transmission Control Protocol/Internet&                               Protocol  B               TLC             TeamLinks[TM] Connection to ALL-IN-1B                               Integrated Office System for OpenVMS  G               UCX             Means DEC[TM] TCP/IP Services for OpenVMS.  B               VMScluster      Discussions that refer to VMSclusterG                               environments apply to both VAXcluster[TM]iE                               systems that include only VAX nodes and.F                               VMScluster systems that include at leastG                               one Alpha node. Any differences are notedC*                               in the text.  I               WPS-PLUS________WPS-PLUS[TM]_software._____________________            Related Documents.  D               You may also need to refer to the documentation on the!               following products:e  4               o  VAX Message Router and its Gateways                 o  DEC Notes[TM]  *               o  OpenVMS system management  5               o  The MAILbus 400 MTA and its Gateways1                 o  Digital X.500                 o  DECnet[TM]/OSIs  I                                                                        xiG L  .              '     Returning Comments About This GuideR  C           If you have any comments or suggestions about this guide,.:           please return them in one of the following ways:  4           o  Internet address: books@reo.mts.dec.com             o  X.400 address:.E              C=GB;A=CWMAIL;P=DIGITAL;O=DIGITAL;OU1=REO;S=BOOKS;G=IDC;.  #           o  Fax: (+44) 1734 206018                                                                          xii. .  .                    I                                                                         1 I         _________________________________________________________________.  I                                    Preparing Your System for Installation     ?               This chapter describes the tasks that you must dos@               to prepare your system for an ALL-IN-1 Version 3.2F               installation. The information in this chapter applies to                all installations.  E               You must read the  ALL-IN-1 Overview and Planning Guide5I               before you install ALL-IN-1 Version 3.2. The planning guider               covers:.  ;               o  Information about this version of ALL-IN-1m  %               o  Mail system planning1  D               o  Installation planning, including a checklist of allH                  the decisions that you need to make before starting the                  installatione  H                  In addition, if you are upgrading from ALL-IN-1 VersionB                  3.1 and your system has been customized, you mustF                  read the chapter Planning the Upgrade of a CustomizedH                  System in the Overview and Planning guide. This chapterI                  explains how to run the Conflict Checking and ResolutionbD                  Tool (CART) to check your customizations before you1                  upgrade to ALL-IN-1 Version 3.2..  D               This installation guide assumes that you have read theA               ALL-IN-1 Overview and Planning Guide, made all your2G               planning decisions and know what type of installation you.#               are going to perform.               I                                Preparing Your System for Installation 1-1     a      *     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.2B           installation, you must do the tasks listed in Table 1-1.  E           Table_1-1_Preinstallation_Checklist________________________m  D                                             For further information,E           Task___Description________________see______________________e  A           1      Check the kit contents     The Bill of MaterialsiB                                             for a list of what theC                                             distribution kit shouldd4                                             contain.  @                                             Contact your Digital=                                             representative if B                                             your kit is damaged or7                                             incomplete.   E           ___________________________________________________________   '           2      Read the READ ME FIRSTq*                  letter if one is supplied                  with your kit  E           ___________________________________________________________.  B           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 prerequisite2$                  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.  E           ___________________________________________________________   E                                              (continued on next page)   .     1-2 Preparing Your System for Installation           I                                    Preparing Your System for Installation I                                    1.1 Checklist of Preinstallation Tasksd    I               Table_1-1_(Cont.)_Preinstallation_Checklist________________.  H                                                 For further information,I               Task___Description________________see______________________   ?               4      Read the online product    Section 1.2 for I                      release notes provided     instructions on accessing B                      with the kit               the release notes.  I               ___________________________________________________________   ;               5      Check that you have the    Section 1.3.)                      correct versions of:r  (                      o  The prerequisite(                         software for the$                         installation  -                      o  Any optional software (                         that you want to                         install   I               ___________________________________________________________a  ;               6      Check that you have a      Section 1.4 *                      valid license for the'                      installing account-  I               ___________________________________________________________h  ;               7      Register the ALL-IN-1      Section 1.5i(                      Version 3.2 License*                      Product Authorization                      Key (PAK)  I               ___________________________________________________________   =               8      Register the License       Section 1.5.3t.                      PAKs for the prerequisite*                      and optional software+                      provided with ALL-IN-1 !                      Version 3.2.M  I               ___________________________________________________________   I                                                  (continued on next page)e  I                                Preparing Your System for Installation 1-3            *     Preparing Your System for Installation*     1.1 Checklist of Preinstallation Tasks    E           Table_1-1_(Cont.)_Preinstallation_Checklist________________   D                                             For further information,E           Task___Description________________see______________________n  ?           9      Check the installation     Section 1.7 for thee?                  procedure requirements:    values required andnE                  o  For the installing      instructions for checking_>                     account                 and changing these7                                             parameters. %                  o  System parametersb                    o  Disk space  !                  o  Logical namesw  $                  o  Installed images  #                  o  The location of.!                     DCLTABLES.EXEt  E           ___________________________________________________________I  8           10     For upgrade                Section 1.8.&                  installations, do any"                  additional tasks.  E           ___________________________________________________________   E                                              (continued on next page)e                              .     1-4 Preparing Your System for Installation    h      I                                    Preparing Your System for InstallationsI                                    1.1 Checklist of Preinstallation Tasksc    I               Table_1-1_(Cont.)_Preinstallation_Checklist________________t  H                                                 For further information,I               Task___Description________________see______________________   A               11     Check that all             Section 1.3 listsmI                      prerequisite and optional  prerequisite and optionaleF                      software is installed,     software. In addition,G                      configured and running     you may want to install_A                      before you start the       DATATRIEVE[TM] or_C                      ALL-IN-1 Version 3.2       ACMS[TM] if you arehE                      installation.              planning to use these G                                                 products with ALL-IN-1.   @                                                 All prerequisiteG                                                 messaging products suchmD                                                 as Message Router orG                                                 the MAILbus 400 MTA andtE                                                 Digital X.500 must be E                                                 installed, configurednF                                                 and running before youI                                                 install ALL-IN-1. See thecE                                                 ALL-IN-1 Overview andm?                                                 Planning Guide.   ?                                                 For a suggested C                                                 order of installing F                                                 optional software, see<                                                 Section 1.6.  I               ___________________________________________________________   ;               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.  I               ___________________________________________________________   I                                                  (continued on next page)T    I                                Preparing Your System for Installation 1-5e           *     Preparing Your System for Installation*     1.1 Checklist of Preinstallation Tasks    E           Table_1-1_(Cont.)_Preinstallation_Checklist________________L  D                                             For further information,E           Task___Description________________see______________________   9           13     If you will be using a     Section 1.10. &                  remote Message Router#                  that is not in the_(                  same VMScluster, do any"                  additional tasks.  E           ___________________________________________________________   8           14     It is recommended that     Section 1.11(                  you run the Perform all'                  preinstallation checksa*                  (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,i)                  software, disk space andM(                  installation parameters)                  correctly set up on your                   system.  E           ___________________________________________________________i  @           15     Do the final system        Section 1.12 for new=                  preparation tasks.         installations andbD                                             Section 1.13 for upgrade:                                             installations.  E           ___________________________________________________________o  8           16     Back up your system and    Section 1.14E           _______target_disks._______________________________________u  5     1.2 Reading and Printing the Online Release Notess  A           Online release notes are provided with the language and1@           market components of ALL-IN-1 Version 3.2. The release?           notes contain information that was unavailable before B           the books went to print. It is recommended that you read  .     1-6 Preparing Your System for Installation a         I                                    Preparing Your System for InstallationiI                         1.2 Reading and Printing the Online Release Notese    E               the release notes, because they may contain informationuF               relating to the installation. You can access the releaseH               notes using the VMSINSTAL procedure before you install the,               ALL-IN-1 Version 3.2 software.  E               There are two parts to the ALL-IN-1 Version 3.2 release                notes:  .               o  Release Notes Part 1 Language  E                  This part contains the release notes specific to the ?                  ALL-IN-1 Version 3.2 language being installed.   ,               o  Release Notes Part 2 Market  F                  This part contains the release notes specific to yourF                  ALL-IN-1 Version 3.2 market component. Note that thisB                  document may not exist for all market components.  C               To read or print the release notes, do the following:_  B               1. Log in to the privileged OpenVMS system manager's?                  account and enter the following command lines:   )                  $ SET DEFAULT SYS$UPDATE_7                  $ @VMSINSTAL product device: OPTIONS N   I                  where device is the device on which the media containing H                  the appropriate version of the release notes is mountedH                  and product is the product code. The product codes are:  E                  o  A1Llang032 for the Release Notes Part 1 Language, H                     where lang is the 2-letter code for the language you"                     are installing  E                  o  A1Cmarket032 for the Release Notes Part 2 Market, D                     where market is the 2-letter code for the market0                     component you are installing  =                  If you are performing an additional language_H                  installation, you need only print the  ALL-IN-1 ReleaseF                  Notes Part 1 Language that is supplied with your kit.  H               When you have read or printed the release notes, terminateG               the installation procedure. If you have accessed only onekG               part of the release notes, repeat the procedure to access_I               the other part. The following files are placed in SYS$HELP:o  E               o  A1Llang032.RELEASE_NOTES, for the Release Notes Part_D                  1 Language, where lang is the 2-letter code for the,                  language you are installing  I                                Preparing Your System for Installation 1-7            *     Preparing Your System for Installation5     1.2 Reading and Printing the Online Release Notes     E           o  A1Cmarket032.RELEASE_NOTES, for the Release Notes Part 2 E              Market, where market is the 2-letter code for the market )              component you are installing   3     1.3 Checking Prerequisite and Optional Software   ?           Table 1-2 provides information about the prerequisiteo?           software for an ALL-IN-1 Version 3.2 installation. It_D           also lists the software that is supplied with the ALL-IN-1E           Version 3.2 kit, and optional software that you may want toc           install.  *           The following definitions apply:  C           o  Prerequisite means that the software must be installed 9              before you install ALL-IN-1 Version 3.2. The @              installation will fail if the prerequisite software              is not installed.  E           o  Optional means that the software is not required for the_A              ALL-IN-1 Version 3.2 installation. Optional software ?              provides additional functionality and the optionaliB              software that you install depends on the requirements@              at your site. For example, if you want to use Group6              Conferencing, you must install DEC Notes.  C              ________________________ Note ________________________o  =              Both the prerequisite software, and any optionalgB              software that you want to install, must be installed,?              configured and running before you install ALL-IN-1s              Version 3.2._  C              ______________________________________________________                       .     1-8 Preparing Your System for Installation r  i      I                                    Preparing Your System for InstallationlI                           1.3 Checking Prerequisite and Optional Software     I               Table_1-2_Prerequisite_and_Optional_Software_______________f  7                                                Suppliedn3               Software         VAX      Alpha  With I               Product__________Version__VersionKit?___Notes______________   F               OpenVMS VAX      6.1 or   -      N      Prerequisite forE                                higher                 installation on :                                                       VAX.  D                                                       Must be a fullG                                                       untailored system   F               OpenVMS Alpha    -        6.1    N      Prerequisite forE                                         or            installation on <                                         higher        Alpha.  D                                                       Must be a fullG                                                       untailored system   I               ___________________________________________________________   F               DECnet-VAX       5.5      -      N      Prerequisite forF               end-node                                remote messagingC                                                       using Message_<                                                       Router  F               DECnet for       -        1.5    N      Prerequisite forF               OpenVMS Alpha                           remote messagingC                                                       using Message <                                                       Router  I                                                  (continued on next page)C                        I                                Preparing Your System for Installation 1-9            *     Preparing Your System for Installation3     1.3 Checking Prerequisite and Optional Software     E           Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______g  3                                            Supplied /           Software         VAX      Alpha  With E           Product__________Version__VersionKit?___Notes______________   A           DECnet/OSI for   6.1 or   6.1    N      Prerequisite[1] C           OpenVMS          higher   or            for systems using B                                     higher        Digital X.500 orC                                                   Digital X.500 and A                                                   the MAILbus 400n6                                                   MTA.  :                                                   OptionalA                                                   alternative for ?                                                   systems using A                                                   Message Router.   E           ____________________________________________________________  >           VAX Forms        2.4      -      Y      Prerequisite           Management           System (FMS)[2]w  >           DEC Forms        -        2.4    Y      Prerequisite           Management           System (FMS)[2]   E           ___________________________________________________________s  E           [1]DECnet/OSI_is_a_prerequisite_for_Digital_X.500._If_______  @           you plan to migrate to use Message Router with DigitalD           X.500, you must install DECnet/OSI as the prerequisite forA           Digital X.500. For Digital X.500, you must also installlD           the OSI Applications Kernel, OSAK[TM], from the DECnet/OSID           Applications component. See the Digital X.500 installation-           documentation for more information.L>           [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 thee0           sample programs supplied with VAX FMS.  E                                              (continued on next page)r  /     1-10 Preparing Your System for Installation     _      I                                    Preparing Your System for Installation I                           1.3 Checking Prerequisite and Optional Softwarea    I               Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______h  7                                                Supplied 3               Software         VAX      Alpha  WithPI               Product__________Version__VersionKit?___Notes______________   ?               DEC TCP/IP       3.1 or   3.1    N      Optional.sI               Services for     higher   or            Install if you wanttG               OpenVMS (UCX)             higher        to use the TCP/IP F               or other TCP/IP                         network protocolD               software that                           to communicateA               emulates UCX[3]                         with clientn  C                                                       applications.g  I               ___________________________________________________________   ?               Message Router   3.3A     -      Y      Optional.   A                                                       Install and_F                                                       configure if youI                                                       want to send remoteaH                                                       mail using Message=                                                       Router.   I               ___________________________________________________________e  >               Message Router   3.3      -      Y      OptionalI               VMSmail Gateway                         Install if you wantf  G                                                       to send mail fromnF                                                       ALL-IN-1 systemsC                                                       using Message G                                                       Router to VMSmail <                                                       users.  I               ___________________________________________________________s  I               [3]For_supported_versions_of_other_TCP/IP_software_________   C               that emulates UCX, see the  ALL-IN-1 Software Product                Description.  I                                                  (continued on next page)   I                               Preparing Your System for Installation 1-11o           *     Preparing Your System for Installation3     1.3 Checking Prerequisite and Optional Softwarex    E           Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______e  3                                            Suppliedo/           Software         VAX      Alpha  With E           Product__________Version__VersionKit?___Notes______________   :           MAILbus 400      1.4A     1.4A   N      Optional=           MTA[4]                                  Install andt  B                                                   configure if youA                                                   want to use thepE                                                   MAILbus 400 MTA foroC                                                   remote mail. Note D                                                   that Digital X.500C                                                   is a prerequisitelE                                                   for the MAILbus 400e6                                                   MTA.  E           ___________________________________________________________l  A           Digital          3.0      3.0    N      Prerequisite ifLE           X.500[5]                                you plan to use the B                                                   MAILbus 400 MTA.  A                                                   Optional if youyB                                                   plan to continue?                                                   using Messageh9                                                   Router.   E           ___________________________________________________________   E           [4]_ALL-IN-1_can_also_connect_to_a_MAILbus_400_MTA_________n  2           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 DigitalD           X.500, you must install DECnet/OSI as the prerequisite forA           Digital X.500. For Digital X.500, you must also installrD           the OSI Applications Kernel, OSAK[TM], from the DECnet/OSID           Applications component. See the Digital X.500 installation-           documentation for more information.o  E                                              (continued on next page)a    /     1-12 Preparing Your System for Installationi u  i      I                                    Preparing Your System for InstallationaI                           1.3 Checking Prerequisite and Optional Software:    I               Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______   7                                                Supplied 3               Software         VAX      Alpha  WithtI               Product__________Version__VersionKit?___Notes______________e  >               MAILbus 400      1.2      -      N      OptionalI               Message Router                          Install if you wanttF               Gateway                                 to exchange mail  E                                                       between MessagenH                                                       Router systems andE                                                       MAILbus 400 MTA >                                                       systems.  I               ___________________________________________________________   ?               DEC Notes        2.5      2.5    Y      Optional.   D                                                       Install if youG                                                       want to use GroupnC                                                       Conferencing.g  I               ___________________________________________________________u  >               CDA Converter    2.2      -      N      OptionalD               Library[6]                              Install if you  F                                                       require full CDAH                                                       support on OpenVMS:                                                       VAX.  >               DECwindows[R][7] -        1.2    N      OptionalD                                         or            Install if youF                                         higher        require full CDA  H                                                       support on OpenVMS<                                                       Alpha.I               [6]The_installation_procedure_checks_for___________________   3               SYS$SHARE:CDA$ACCESS.EXE, Version 1.7 6               [7]The installation procedure checks for3               SYS$SHARE:CDA$ACCESS.EXE, Version 1.8 I               ___________________________________________________________   D               For information about the order of installing optional(               software, see Section 1.6.  G               For a list of all supported versions of products that can G               be used with ALL-IN-1, see the  ALL-IN-1 Software Product                Description.  I                               Preparing Your System for Installation 1-13  n  f      *     Preparing Your System for Installation7     1.4 Checking the License for the Installing Accounto    7     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. This8           means that you must have one of the following:             o  A Capacity licenceY  6           o  A Concurrent license with available units  A           o  A personal license with the name of the installationp2              account in the reserve list of users.  D              For example, if you are planning to do the installationB              from the SYSTEM account, SYSTEM must be listed in the              reserve list.  <           The installing account should be licensed with theC           maximum available license to ensure that all the requiredp)           functionality can be installed.y  =     1.5 Registering License Product Authorization Keys (PAKs)i  8           You must register the ALL-IN-1 License ProductA           Authorization Key (PAK) before you start to install the C           ALL-IN-1 Version 3.2 software. The installation procedure C           checks for a registered ALL-IN-1 Version 3.2 license whennC           you confirm that you are ready to install the software by C           choosing the Perform the installation (I) option from the B           menu of installation options. If a license is not found,&           the installation terminates.  E           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, youA           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.   C              ________________________ 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-1tC              kit, for example the MAILbus 400 MTA or Digital X.500,e  /     1-14 Preparing Your System for Installation     t      I                                    Preparing Your System for Installation_I                 1.5 Registering License Product Authorization Keys (PAKs)     E                 you must register the license PAKS manually using the 2                 License Management Facility (LMF).  F                 ______________________________________________________  ?         1.5.1 Registering the ALL-IN-1 License PAK Before a new                Installation  D               If you are installing ALL-IN-1 Version 3.2 on a newly-C               licensed node or cluster, you must register a License F               PAK for ALL-IN-1 Version 3.2 before you install ALL-IN-1D               Version 3.2. The License PAK may be shipped along withD               the kit if you ordered the license and media together;H               otherwise, it is shipped separately to a location based onG               your license order. License PAKs are registered using the 0               License Management Facility (LMF).  F               To register the ALL-IN-1 Version 3.2 License PAK, do the               following:  @               1. Log in to the system manager's account, SYSTEM.  G               2. Register the License PAK in one of the following ways:c  C                  o  Invoke the SYS$UPDATE:VMSLICENSE.COM procedure._E                     When it prompts you for information, respond with 6                     information from your License PAK.  E                  o  Issue the DCL command, LICENSE REGISTER, together F                     with the appropriate qualifiers that correspond to3                     information on the License PAK.   H               For complete information on using the LMF, see the OpenVMS0               License Management Utility Manual.  D         1.5.2 Registering the ALL-IN-1 License PAK Before an Upgrade  I               If you are installing ALL-IN-1 Version 3.2 as an upgrade oriG               update installation on a node or cluster already licensed E               for this software, you must register the Service Update D               PAK (SUP) that is included in your Service Update Kit.G               If you have already registered a License PAK or a SUP for F               this product on this node or cluster, you do not need to               register the SUP.   I               If you are installing an update of ALL-IN-1 Version 3.2 but_G               lack a service contract, call your Digital representativeo;               for instructions on how to get a License PAK.   I                               Preparing Your System for Installation 1-15            *     Preparing Your System for Installation=     1.5 Registering License Product Authorization Keys (PAKs)a    =     1.5.3 Registering License PAKs for Software Provided withn           ALL-IN-1 Version 3.2  C           When you have registered the ALL-IN-1 Version 3.2 LicensedB           PAK, you must register the License PAKS for the productsC           supplied with the ALL-IN-1 Version 3.2 kit. The following @           License PAKs can be registered automatically using the6           ALL-IN-1 Version 3.2 installation procedure:  E           ___________________________________________________________ E           VAX________________________Alpha___________________________   ,           VAX FMS                    DEC FMS  1           DEC Notes[1]               DEC Notes[1]   &           Message Router             -  &           Message Router VMSmail     -           Gateway   &           CDA Converter Library      -E           [1]If_your_ALL-IN-1_license_does_not_include_Group_________   E           Conferencing,_the_DEC_Notes_PAK_is_not_registered._________   B           The License PAKs supplied for these products are for anyB           processor and any number of users. If you already have aC           license for one of these products, it will be replaced byrE           the license supplied with the ALL-IN-1 Version 3.2 kit. ThelD           ALL-IN-1 Version 3.2 License PAK must be registered first.  D           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]:  C              ________________________ Note _________________________  6              Choosing the RL option does not start the              installation.  C              ______________________________________________________5  C           The installation procedure checks your existing licenses,n>           and if necessary registers and loads the appropriate>           licenses for the software products provided with theE           ALL-IN-1 Version 3.2 kit. The installation then terminates.   /     1-16 Preparing Your System for InstallationO           I                                    Preparing Your System for InstallationeI                 1.5 Registering License Product Authorization Keys (PAKs)     I               For prerequisite or optional products that are not suppliedoH               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  F               After you have installed and configured the prerequisiteC               software, install and configure the optional software E               products. See the appropriate product documentation forK:               installation and configuration instructions.  ?               The following installation order is suggested for F               installing optional software before the ALL-IN-1 Version               3.2 installation:g  !               1. Install ACMS[TM]   =               2. Install VAX DATATRIEVE[TM] or DEC DATATRIEVE   A               3. Install and configure your message transport and ,                  directory service software.  A                  o  For new or upgrade installations with Message.G                     Router, make sure that Message Router is installed,_H                     configured and running before you start the ALL-IN-1E                     installation. If you plan to use a remote Message F                     Router Directory Service, you must do a customizedA                     Message Router configuration to enable remotegB                     Directory Service access and configure MessageH                     Router exception reporting for the Directory ServiceC                     and Transfer Service according to your planningf                     decisions.  D                  o  For new installations with Digital X.500 and theE                     MAILbus 400 MTA make sure that you have installed A                     and configured all the required components on[D                     your ALL-IN-1 node or cluster. Digital X.500 andD                     the MAILbus 400 MTA must be correctly installed,C                     configured and running before you start the new F                     ALL-IN-1 installation. See the MAILbus 400 MTA andC                     Digital X.500 Planning chapter in the  ALL-IN-1r0                     Overview and Planning Guide.  A               4. Install and configure optional gateway products.s  G                  o  The Message Router VMSmail Gateway if required withs#                     Message Router._  I                               Preparing Your System for Installation 1-17o b         *     Preparing Your System for Installation6     1.6 Example Order for Installing Optional Software    B              o  The MAILbus 400 Message Router Gateway if required)                 with the MAILbus 400 MTA.c  A              o  The MAILbus 400 SMTP Gateway if required with ther                  MAILbus 400 MTA.             5. Install DEC Notes.o  +     1.7 Installation Procedure Requirementse  @           This section describes the requirements for installingC           ALL-IN-1 Version 3.2. It explains how to check the valuesr.           and how to change them if necessary.  )     1.7.1 Installing Account Requirementss  A           Use the SYSTEM account to install ALL-IN-1 Version 3.2.   D           The installing account must have a valid rights identifierC           which is the same as the UIC for the account name. If yousB           are using the SYSTEM account, the rights identifier mustA           be the same as the UIC. To check the UIC and identifier #           values, do the following:   $           $ RUN SYS$SYSTEM:AUTHORIZE%           UAF> SHOW/IDENTIFIER SYSTEMl  >           The value that is displayed is the UIC of the systemA           account. To add the rights identifier, if it is not sett           up, do the following:e  4           UAF> ADD/IDENTIFIER SYSTEM/VALUE:UIC=[1,4]           UAF> EXITg  A           The installing account must also have sufficient quotas >           to enable you to perform the installation. Table 1-3&           summarizes the requirements.  A           Note that these values are sufficient for installation, D           but they may not be appropriate for running ALL-IN-1. WhenC           you create new user accounts for ALL-IN-1 Version 3.2 the C           process quotas are set to the appropriate values. See the $           ALL-IN-1 Management Guide.    /     1-18 Preparing Your System for Installation     t      I                                    Preparing Your System for InstallationeI                                   1.7 Installation Procedure Requirementsr        I               Table_1-3_Process_Account_Quotas_for_the_Installing_Accountr                 AccountfI               Quota_________VAX_________Alpha_______Notes________________c  .               BYTLM         64 000      64 000  +               ENQLM         300         300   +               FILLM         200         200   B               JTQUOTA       1800        1800        JTQUOTA can beC                                                     returned to itstI                                                     normal system runningTC                                                     value after theoD                                                     installation has>                                                     completed.  .               PGFLQUOTA     25 000      65 000I               __________________________pagelets_________________________            1.7.2 System Parameters.  C               Table 1-4 lists the minimum required system parameter_D               values for the installation. Depending on the kinds ofE               programs and applications running at your site, you may-H               need higher values for some settings. If necessary, modify6               the parameters to at least these values.  F                 ________________________ Note ________________________  D                 You must check the OpenVMS system parameters on eachA                 node in the cluster on which you install ALL-IN-1s                 Version 3.2.  F                 ______________________________________________________  F               The values for the system parameters and quotas given inI               this section are those specific to ALL-IN-1 Version 3.2 and G               are acceptable for most systems. The  ALL-IN-1 ManagementSH               Guide describes how to set system parameters for ALL-IN-1.  E               Dynamic system parameters are labelled with a (D) afteruH               them. You do not need to reboot your system after changingF               dynamic system parameters. If you need to set new valuesI               for other system parameters, you must reboot your system in 3               order for the changes to take effect.   I                               Preparing Your System for Installation 1-19  p  e      *     Preparing Your System for Installation+     1.7 Installation Procedure Requirements.    E     Table_1-4_Minimum_System_Parameter_Values_Required_______________   
     SystemE     Parameter_____VAX_________________Alpha__________________________   )     CTLPAGES      100                 100a  E     _________________________________________________________________S  /     GBLSECTIONS   250 (new)           250 (new)l  2                   50 (upgrade)        50 (upgrade)  E     _________________________________________________________________p  1     GBLPAGES      20000 (new)         35000 (new)   4                   5000 (upgrade)      5000 (upgrade)  E     _________________________________________________________________a  <     GBLPAGFIL     For new             For new installations:?                   installations:      1. Add 1 to the number of   B                   1. Add 1 to the        active users. There is anD                      number of           upper limit of 200 for thisB                      active users.       value, so use 200 if yourC                      There is an         value is greater than 200.i/                      upper limit      2. Add 32A                      of 200 for                        this value,"                      so use 200 if"                      your value is!                      greater than                       200.t  "                   2. Multiply your!                      value by 16.                      3. Add 500  E                   ____________________________________________________  E                                              (continued on next page)   /     1-20 Preparing Your System for Installation            I                                    Preparing Your System for Installation I                                   1.7 Installation Procedure Requirements     I         Table_1-4_(Cont.)_Minimum_System_Parameter_Values_Required_______            SystemI         Parameter_____VAX_________________Alpha__________________________e  D         GBLPAGFIL     For upgrade         For upgrade installations:G                       installations:      1. Add together the number off  E                       1. Add together        global buffers[3] on thewH                          the number          following files in OA$DATA_3                          of global           SHARE:g<                          buffers[3] on       o  ATTENDEE.DAT&                          the following;                          files in            o  MEETING.DATl;                          OA$DATA_SHARE:      o  PENDING.DATh  ;                          o  ATTENDEE.DAT     o  PROFILE.DAT_  I                          o  MEETING.DAT   2. Add the total from Step 1 tot  I                          o  PENDING.DAT      the number of global buffers_C                          o  PROFILE.DAT      in the shared documenteF                                              attributes files, OA$DAF_G                       2. Add the total       n.DAT in OA$SHARn, where neE                          from Step 1 to      is a letter from A to E.eE                          the number       3. Divide the total by 4 to D                          of global           convert to global pages'                          buffers in then3                          shared document  4. Add 32 #                          attributesl'                          files, OA$DAF_ !                          n.DAT int(                          OA$SHARn, where&                          n is a letter%                          from A to E.   %                       3. Multiply the #                          total by 4i&                          to convert to%                          global pagesn                          4. Add 500  I         [3]To_find_the_number_of_global_buffers_do_a_DIR/FULL_for_each___a  
         file.i  I                                                  (continued on next page)o  I                               Preparing Your System for Installation 1-21            *     Preparing Your System for Installation+     1.7 Installation Procedure RequirementsT    E     Table_1-4_(Cont.)_Minimum_System_Parameter_Values_Required_______u  
     SystemE     Parameter_____VAX_________________Alpha__________________________   E     _________________________________________________________________   E     LOCKIDTBL     100 multiplied      100 multiplied by the number of +                   by the number of    users                    active users  E     _________________________________________________________________t  *     MAXBUF (D)    5000                5000  E     _________________________________________________________________   B     MAXPROCESSCNT 50 plus the number  50 plus the number of active+                   of active users     userst  E     _________________________________________________________________t  D     RESHASHTBL    50 multiplied       50 multiplied by the number of2                   by the number of    active users                   active users  E     _________________________________________________________________a  D     SCSNODE       Must be the same    Must be the same as the DECnet/                   as the DECnet node  node name                    name  E     _________________________________________________________________r  C     SCSSYSTEMID   DECnet area number  DECnet area number multipliedeC                   multiplied by       by 1024, plus the DECnet nodet,                   1024, plus the      number$                   DECnet node number  E     _________________________________________________________________   6     VIRTUALPAGECNT16]384 pages[5]     250 000 pageletsE     [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.E     _________________________________________________________________s  C              ________________________ Note ________________________A  >              For the majority of installations, the values forC              CTLPAGES are sufficient. If you are planning to rebootN  /     1-22 Preparing Your System for Installationt           I                                    Preparing Your System for Installation1I                                   1.7 Installation Procedure Requirementsa    B                 your system to change other system parameters, youE                 can increase the value to 200 for the duration of the                  installation.m  F                 ______________________________________________________  2         1.7.3 Displaying Current System Parameters  E               Run the SYSGEN utility to display the current parametere               settings:d  F               1. To display all the current system parameter settings,                  enter:   (                  $ RUN SYS$SYSTEM:SYSGEN"                  SYSGEN> SHOW /ALL  H               2. To show each system parameter setting separately enter:  '                  SYSGEN> SHOW parameter   F                  where parameter is the parameter you want to examine.  .               3. Press Ctrl/Z to leave SYSGEN.  D               To check the number of free global pages and sections,+               enter the following commands:i  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")  E               If the value of free global pages or global sections isID               less than the value in Table 1-4 you must increase theF               system parameter setting. If the values displayed by theE               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  I               Edit the file SYS$SYSTEM:MODPARAMS.DAT to change the systemfD               parameter values. The entry that you make in this fileG               depends on which of the parameters you are modifying. See                Table 1-5.  A               If you need to change and update non-dynamic system F               parameters, you must schedule time to reboot your systemD               in order for the changes to take effect. The (D) afterD               the system parameter value shows that they are dynamic               parameters.e  I                               Preparing Your System for Installation 1-23h           *     Preparing Your System for Installation+     1.7 Installation Procedure Requirements     E           Table_1-5_Changing_System_Parameter_Values_________________              To change_           the followingaE           parameters_______Do_the_following__________________________   D           SCSNODE          Edit SYS$SYSTEM:MODPARAMS.DAT and specify?           SCSSYSTEMID      new parameter values. Use assignmentf2                            statements of the form:  6                            parameter = parameter-value  =                            where parameter is the name of thes;                            parameter you want to change and_B                            parameter-value is the setting you wantA                            to change it to. See Table 1-4 for the *                            required value.  E           ____________________________________________________________  D           CTLPAGES         Edit the file SYS$SYSTEM:MODPARAMS.DAT toD           GBLPAGES         specify new values. Include a line of theD           GBLPAGFIL        following format for each parameter to be#           GBLSECTIONS      changed:n  9           LOCKIDTBL        ADD_parameter = increase-values  =           MAXBUF (D)       where parameter is the name of thee<           MAXPROCESSCNT    parameter you want to change, and@           RESHASHTBL       increase-value is the amount by whichC           VIRTUALPAGECNT   you want to increase the setting of thist%                            parameter.t  @                            For example, to increase the value of2                            LOCKIDTBL by 60, enter:  +                            ADD_LOCKIDTBL=60   E           _________________See_Table_1-4_for_the_required_values.____.  ?           If you change any of the system parameter values, you_A           must update them using AUTOGEN. See Section 1.7.4.1 and_           Section 1.7.4.2.    /     1-24 Preparing Your System for Installation_ _  _      I                                    Preparing Your System for Installation I                                   1.7 Installation Procedure Requirementsr    ?         1.7.4.1 Updating Dynamic System Parameters with AUTOGEN_  C               To update the dynamic system parameter values, do the                following:  (               1. Run AUTOGEN as follows:  :                  $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS  9               2. Write the changes to the current system:   (                  $ RUN SYS$SYSTEM:SYSGEN$                  SYSGEN> USE CURRENT%                  SYSGEN> WRITE ACTIVEi  -               3. Press Ctrl/Z to leave SYSGENp  D               You do not need to reboot your system to make your new!               values take effect.   I               For more information, see the OpenVMS manual describing theu               AUTOGEN utility.  B         1.7.4.2 Updating Non-Dynamic System Parameter with AUTOGEN  C               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.  F                 ________________________ Note ________________________  @                 You must reboot your system in order for the new&                 values to take effect.  F                 ______________________________________________________  I               For more information, see the OpenVMS manual describing the_               AUTOGEN utility.  I                               Preparing Your System for Installation 1-25_ _  _      *     Preparing Your System for Installation+     1.7 Installation Procedure Requirements     D     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.   E           The default disk for your kit working device is your systemnC           disk. If your system disk does not have sufficient space, D           you can specify an alternate working device (AWD) when you!           start the installation.E  =           The disk space values for your kit are given in theF@           ALL-IN-1 Installation: Language and Market Supplement.@           You must also check the disk space requirements on theD           target disks where ALL-IN-1 Version 3.2 will be installed.           See Section 1.7.7.  E           You can run the installation in either safety or non-safety_           mode.   C              ________________________ Note ________________________   A              Digital recommends that you run your installation in '              safety mode (the default).h  C              ______________________________________________________t  >           When you run the installation in safety mode, all of;           the ALL-IN-1 Version 3.2 kit is restored onto the A           system disk or AWD before the files are copied to their A           target locations. This means that you need a disk spacewA           requirement greater than the total size of the ALL-IN-1 D           Version 3.2 kit on your system disk. The disk space valuesA           for installing your kit in safety mode are given in the @           ALL-IN-1 Installation: Language and Market Supplement.  9           If you do not have enough disk space to run theoC           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 yournB           system disk greater than the size of the largest savesetB           provided in the ALL-IN-1 Version 3.2 kit. The disk space?           values for installing your kit in non-safety mode are B           given in the  ALL-IN-1 Installation: Language and Market           Supplement.0  /     1-26 Preparing Your System for Installation            I                                    Preparing Your System for Installation_I                                   1.7 Installation Procedure Requirements(    4         1.7.6 Using the OA$LIB_SHARE Disk as the AWD  F               If you have sufficient space on the target disk on whichG               OA$LIB_SHARE will reside, Digital recommends that you usesC               this disk as the AWD. If you do have sufficient space_C               to install on this target disk, the installation timelF               can be reduced by approximately 20%. This is because theG               majority of the ALL-IN-1 files reside in the OA$LIB_SHARE_I               directory and therefore the installation procedure can moveuG               those files to their target directories by using a RENAMEn6               operation, rather than a COPY operation.  ;         1.7.7 Disk Space for ALL-IN-1 Areas on Target DisksI  I               You can install ALL-IN-1 Version 3.2 in the following ways:t  (               o  On a single target disk  I               o  Across several target disks by installing ALL-IN-1 areasd#                  on separate disks._  C               For upgrade installations, the installation procedure4G               assumes that the ALL-IN-1 disks and top-level directoriesrC               for the ALL-IN-1 areas have not changed, and that theeD               ALL-IN-1 directory tree is the same. If you have movedE               any of the directories, you must put them back to their_1               correct locations before upgrading._  E               You can install more than one ALL-IN-1 area on the sameiE               disk. If you do this, add the disk space values for theyI               two areas together to find the total space required on thatoF               disk. See  ALL-IN-1 Overview and Planning Guide for more/               information about ALL-IN-1 areas.   C               The disk space requirements for ALL-IN-1 language andrG               market areas that you are installing are in the  ALL-IN-1a;               Installation: Language and Market Supplement.   E               To calculate the total disk space requirements for your_D               installation, add together the disk space requirementsE               given in this section and the requirements given in theeD               ALL-IN-1 Installation: Language and Market Supplement.  D               The disk space requirements for each ALL-IN-1 area are-               listed in the following tables:S  E               o  Table 1-6 for a new installation. See Section 1.7.9.g  I                               Preparing Your System for Installation 1-27     e      *     Preparing Your System for Installation+     1.7 Installation Procedure RequirementsS    7           o  Table 1-7 for an upgrade installation. Sees              Section 1.7.10.  D           o  Table 1-8 for the addition, upgrade or update of VAX or<              Alpha architecture support. See Section 1.7.11.  D              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 0           ALL-IN-1 area during the installation.  /     1.7.8 Assigning Logical Names to Your Disks   B           Digital recommends that you assign logical names to your           disks where possible.   C              ________________________ Note ________________________   A              To avoid conflicts with system logical names, do not 2              assign logical names that start with:                o  A1$                 o  OA$                 o  OA1$  C              ______________________________________________________u  B           In all types of installation, the installation procedureB           checks for conflicting system and process logical names,C           which could cause the installation to fail. You can check >           for conflicts before you start the installation. SeeA           Section 1.11 which describes how to run the Perform alli-           preinstallation checks (PC) option.   E           The logical name checking includes a check for any existing_E           logical names that start with OA$. An informational messageeE           lists the names found, and a warning message warns you thatD/           these logical names may be redefined.i  ?           If a logical name conflict is found, an informationalfB           message is displayed. If the conflicting logical name isC           defined in a system table, you can remove the conflicting @           logical name from another process, and then repeat theC           check. If the conflicting logical name is specific to thetE           installing process, then you must abort the installation toi  /     1-28 Preparing Your System for Installation     q      I                                    Preparing Your System for Installation_I                                   1.7 Installation Procedure Requirementso    H               fix the problem and then restart it. The installation willF               not continue until the logical name checking has passed.  @               For all upgrade or update installations, make sureE               that ALL-IN-1 logical names do not point to system root H               directories; for example, OA$LIB_SHARE must not be defined0               as SYS$SYSROOT:[ALLIN1.LIB_SHARE].  E               Do not use SYS$SYSDEVICE in directory specifications if G               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   H               Table 1-6 gives the disk space requirements for installing<               ALL-IN-1 areas on the system and target disks.  E               The disk space requirements given are those used duringtA               the installation. The permanent space used when theg>               installation has completed may be slightly less.  F                 ________________________ Note ________________________  E                 If you do not choose to integrate WPS-PLUS during the.D                 installation, you can decrease the disk space in theA                 shared library area by approximately 6000 blocks.   D                 If you choose to integrate WPS-PLUS, but without theD                 associated PostScript[R] files, you can decrease theF                 disk space in the shared library area by approximately                 3000 blocks.  F                 ______________________________________________________                        I                               Preparing Your System for Installation 1-29  r  w      *     Preparing Your System for Installation+     1.7 Installation Procedure Requirementsu    E           Table_1-6_New_Installation:_Disk_Space_for_ALL-IN-1_Areas__i  E           ALL-IN-1_Area_for__________VAX_________Alpha_______________o  7           System disk files[1]       21 000      61 000o  7           Shared library files       55 000      86 000   7           Shared data files          12 500      12 500   5           Shared areas[2]            1000        1000a  5           ALL-IN-1 Manager           1000        1000            account[3]E           [1]Space_required_to_provide_ALL-IN-1_shared_files_to______r  B           system directories. Add the value given in the  ALL-IN-1A           Installation: Language and Market Supplement to get the_           total value.E           [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.iE           ___________________________________________________________a  C           For the disk space values for the primary language files,c=           see the  ALL-IN-1 Installation: Language and Marketk           Supplement.g  C              ________________________ Note ________________________a  >              Do not create the ALL-IN-1 manager's account in a9              subdirectory of an OpenVMS system directory.   C              ______________________________________________________   >     1.7.10 Upgrade Installation: Disk Space for ALL-IN-1 Areas  C           Table 1-7 gives the disk space requirements for upgradingg8           ALL-IN-1 areas on the system and target disks.  A           The disk space requirements given are those used during-=           the installation. The permanent space used when the :           installation has completed may be slightly less.  A           The values given in the table assume that you choose to_@           purge files during the installation. If you choose notC           to purge replaced files, you must use the values given ine           Table 1-6.  /     1-30 Preparing Your System for Installation_ _         I                                    Preparing Your System for InstallationLI                                   1.7 Installation Procedure Requirementsb    F                 ________________________ Note ________________________  E                 If you do not choose to integrate WPS-PLUS during thelD                 installation, you can decrease the disk space in the3                 shared library area by 5000 blocks.   ?                 If you choose to integrate WPS-PLUS without theoA                 associated PostScript files, you can decrease theeE                 disk space in the shared library area by 2000 blocks.u  F                 ______________________________________________________  F               Table 1-7 Upgrade Installations: Disk Space for ALL-IN-1I               __________Areas____________________________________________n  I               ALL-IN-1_Area_for__________VAX_________Alpha_______________   ;               System files[1]            10 500      61 000   ;               Shared library files       11 000      86 000   9               Shared data files          2000        2000kI               [1]Space_required_to_provide_ALL-IN-1_shared_files_to______o  F               system directories. Add the value given in the  ALL-IN-1E               Installation: Language and Market Supplement to get theP               total value I               ___________________________________________________________u  G               For the disk space values for the primary language files,AA               see the  ALL-IN-1 Installation: Language and Markets               Supplement.   H         1.7.11 Addition of Architecture Support: Disk Space for ALL-IN-1                areas  E               Table 1-8 gives the disk space requirements for adding, F               upgrading or updating architecture support on the system(               and ALL-IN-1 target disks.  H               These values also apply to the addition, upgrade or updateA               or architecture support for an additional language.C      I                               Preparing Your System for Installation 1-31            *     Preparing Your System for Installation+     1.7 Installation Procedure Requirementsg    ?           Table 1-8 Addition, Upgrade or Update of ArchitecturetE           __________Support:_Disk_Space_for_ALL-IN-1_Areas___________   E           ALL-IN-1_Area_for__________VAX___________Alpha_____________   9           System files[1]            21 000        61 000   9           Shared library files       37 000        73 000aE           [1]Space_required_to_provide_ALL-IN-1_files_to_system______m  ;           directories. Add the value given in the  ALL-IN-1aA           Installation: Language and Market Supplement to get the            total valuenE           ___________________________________________________________y  C           For the disk space values for the primary language files, =           see the  ALL-IN-1 Installation: Language and Market            Supplement.v        1.7.12 Disk Quota Allocation  C           If disk quota is enabled, the installation procedure addsiD           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 systemB           and Table 1-10 are installed on your Alpha system before?           you install ALL-IN-1. Note that this list of required B           images applies to the versions of the products listed in           Table 1-2.  E           Table_1-9_Installed_Images_Required_on_VAX_________________i  E           Product_______Image_Required_on_VAX________________________t  -           Always        SYS$SHARE:CONVSHR.EXE            required  1                         SYS$SHARE:CMA$TIS_SHR.EXEr  .                         SYS$SHARE:DECC$SHR.EXE  ,                         SYS$SHARE:FDLSHR.EXE  .                         SYS$MESSAGE:FDVMSG.EXE  E                                              (continued on next page)g  /     1-32 Preparing Your System for Installatione r  u      I                                    Preparing Your System for InstallationaI                                   1.7 Installation Procedure Requirementsi    I               Table_1-9_(Cont.)_Installed_Images_Required_on_VAX_________g  I               Product_______Image_Required_on_VAX________________________.  3                             SYS$SHARE:FDVSHR.EXE[1]   0                             SYS$SHARE:LBRSHR.EXE  0                             SYS$SHARE:LIBRTL.EXE  3                             SYS$SHARE:MTHRTL.EXE[2]_  0                             SYS$SHARE:PASRTL.EXE  0                             SYS$SHARE:PLIRTL.EXE  0                             SYS$SHARE:SCRSHR.EXE  1                             SYS$SHARE:VAXCRTL.EXE   0                             SYS$SHARE:VMSRTL.EXE  I               ___________________________________________________________   0               ACMS          SYS$SHARE:ACMSHR.EXE  I               ___________________________________________________________   4               CDA           SYS$SHARE:CDA$ACCESS.EXE  8                             SYS$SHARE:IMG$SHRLIB_NOX.EXE  9                             SYS$SHARE:DDIF$CC_VIEWSHR.EXE   I               ___________________________________________________________t  G               DATATRIEVE    SYS$SHARE:DTRSHR.EXE (the standard). If youeG                             are using another DATATRIEVE image that you E                             want to link with ALL-IN-1, you must makecC                             sure that image is installed before thes)                             installation.   0                             SYS$SHARE:CDDSHR.EXE  3                             SYS$MESSAGE:DTRMSGS.EXEr  0                             SYS$SHARE:CDDEXC.EXE  I               ___________________________________________________________h  5               DEC Notes     SYS$SHARE:NOTES$SHARE.EXEi  I               [1]This_is_a_language-specific_image_which_can_have_a______   8               different name on other language versions.H               [2]For certain processors, the logical is defined to point'               to SYS$SHARE:UVMTHRTL.EXE.  I                                                  (continued on next page)c  I                               Preparing Your System for Installation 1-33k u         *     Preparing Your System for Installation+     1.7 Installation Procedure Requirementse    E           Table_1-9_(Cont.)_Installed_Images_Required_on_VAX_________O  E           Product_______Image_Required_on_VAX________________________t  E           ___________________________________________________________t  1           Digital       SYS$SHARE:DXD$DUA_SHR.EXEs           X.500c  1                         SYS$SHARE:DXD$XDS_SHR.EXEi  E           ___________________________________________________________a  2           The MAILbus   SYS$SHARE:MTA$XAPI_SHR.EXE           400 MTAm  E           ___________________________________________________________   -           Message       SYS$SYSTEM:MRTALK.EXEn           Router  E           ___________________________________________________________t  E           TCP/IP________SYS$SHARE:UCX$IPC_SHR.EXE_____________________  E           Table_1-10_Installed_Images_Required_on_Alpha______________r  E           Product__________Image_Required_on_Alpha___________________n  0           Always required  SYS$SHARE:CONVSHR.EXE  4                            SYS$SHARE:CMA$TIS_SHR.EXE  1                            SYS$SHARE:DECC$SHR.EXE   1                            SYS$SHARE:DPML$SHR.EXE   /                            SYS$SHARE:FDLSHR.EXEe  1                            SYS$MESSAGE:FDVMSG.EXE   2                            SYS$SHARE:FDVSHR.EXE[1]  /                            SYS$SHARE:LBRSHR.EXE   5                            SYS$SHARE:LCI$SHARE_TV.EXE1  /                            SYS$SHARE:LIBOTS.EXEn  /                            SYS$SHARE:LIBRTL.EXEe  E           [1]This_is_a_language-specific_image_which_can_have_a______r  4           different name on other language versions.  E                                              (continued on next page)   /     1-34 Preparing Your System for Installation5 0         I                                    Preparing Your System for Installation I                                   1.7 Installation Procedure Requirementsr    I               Table_1-10_(Cont.)_Installed_Images_Required_on_Alpha_______  I               Product__________Image_Required_on_Alpha___________________d  9                                SYS$SHARE:LIBRTL_TV.EXE[2]a  9                                SYS$SHARE:MTHRTL_TV.EXE[2]u  4                                SYS$SHARE:PAS$RTL.EXE  3                                SYS$SHARE:SCRSHR.EXEd  6                                SYS$SHARE:SECURESHR.EXE  7                                SYS$SHARE:SECURESHRP.EXE   3                                SYS$SHARE:SMGSHR.EXE_  6                                SYS$SHARE:TIE$SHARE.EXE  :                                SYS$SHARE:VAXCRTL_TV.EXE[2]  =                                SYS$SHARE:VMS$IEEE_HANDLER.EXE   I               ___________________________________________________________   3               ACMS             SYS$SHARE:ACMSHR.EXE   I               ____________________________________________________________  7               CDA              SYS$SHARE:CDA$ACCESS.EXEU  <                                SYS$SHARE:DDIF$CC_VIEWSHR.EXE  ;                                SYS$SHARE:IMG$SHRLIB_NOX.EXE   I               ___________________________________________________________a  F               DATATRIEVE       SYS$SHARE:DTRSHR.EXE (the standard). IfE                                you are using another DATATRIEVE imagedG                                that you want to link with ALL-IN-1, youtE                                must make sure that image is installedo7                                before the installation.   3                                SYS$SHARE:CDDSHR.EXE-  5                                SYS$MESSAGE:DTRMSGS.EX   3                                SYS$SHARE:CDDEXC.EXEm  I               ___________________________________________________________u  8               DEC Notes        SYS$SHARE:NOTES$SHARE.EXE  I               [2]This_is_a_logical_which_typically_translates_to_________n  E               something like the following example: LIBRTL_D56_TV.EXEa  I                                                  (continued on next page)   I                               Preparing Your System for Installation 1-35            *     Preparing Your System for Installation+     1.7 Installation Procedure Requirementsb    E           Table_1-10_(Cont.)_Installed_Images_Required_on_Alpha_______  E           Product__________Image_Required_on_Alpha___________________:  E           ____________________________________________________________  4           Digital X.500    SYS$SHARE:DXD$DUA_SHR.EXE  4                            SYS$SHARE:DXD$XDS_SHR.EXE  E           ___________________________________________________________   5           MAILbus 400 MTA  SYS$SHARE:MTA$XAPI_SHR.EXE   E           ___________________________________________________________e  E           TCP/IP___________SYS$SHARE:UCX$IPC_SHR.EXE_________________t  C           To check which images are installed on your system, entert!           the following commands:e             $ INSTALL !           INSTALL> LIST imagename *           imagename;       Open Shar Lnkbl  B           imagename is the directory and file specification of the           image to be checked.  B           If there is no entry for the image or the qualifiers are@           incorrect, you must install the image with the correct           qualifiers.N             To install:   A           o  SYS$MESSAGE:FDVMSG.EXE and SYS$SHARE:FDVSHR.EXE, seeg              Section 1.7.14.  .           o  Other images, see Section 1.7.15.  ?           For more information about installing images, see thea0           manual describing the Install Utility.  6     1.7.14 Installing FDVMSG.EXE and FDVSHR.EXE Images  2           If the images SYS$MESSAGE:FDVMSG.EXE andC           SYS$SHARE:FDVSHR.EXE are not installed, do the following:s  D           1. Edit the command procedure SYS$STARTUP:FMSTARTUP.COM toC              remove the EXIT command that appears before the entry:   #              RUN SYS$SYSTEM:INSTALL_  /     1-36 Preparing Your System for Installatione o  _      I                                    Preparing Your System for Installation2I                                   1.7 Installation Procedure Requirements7    H               2. Execute the command procedure SYS$STARTUP:FMSTARTUP.COM  &         1.7.15 Installing Other Images  .               Install other images as follows:                 $ INSTALLtA               INSTALL> CREATE imagename /OPEN /SHARED /HEADER_RES_               INSTALL> EXIT_  5         1.7.16 Checking The Location of DCLTABLES.EXE   :               Check that DCLTABLES.EXE is in the directoryE               SYS$COMMON:[SYSLIB]. If it is in a different directory,uH               move it to this location before starting the installation.  C               To check if DCLTABLES.EXE is in the correct location,e               enter:                 $ INSTALL A               INSTALL> LIST/FULL SYS$COMMON:[SYSLIB]DCLTABLES.EXEb  >               If it is not in the correct location, remove it:  +               INSTALL> REMOVE DCLTABLES.EXE-  I               Move DCLTABLES.EXE to the correct location and then replace                it:   C               INSTALL> CREATE DCLTABLES.EXE /OPEN/SHARED/HEADER_RESl  6         1.8 Additional Tasks for Upgrade Installations  F               If you are upgrading an existing ALL-IN-1 system, do the               following:  .               1. Review your object libraries.  C                  Your object libraries may have been updated if you$B                  installed layered products. ALL-IN-1 provides twoB                  template .OLB files in the following directories:  6                  -  OA$SITE_BUILD_SHARE:SITEOALIBR.OLB  3                  -  OA$SITE_BUILD_LLV:SITEOALLV.OLB   I                  During the installation, a warning is displayed if there H                  are additional .OBJ or .OLB files in these directories.D                  Check that any additional object libraries or filesG                  in this directory are compatible with ALL-IN-1 Version G                  3.2. Remove any object libraries or files that are not.  I                               Preparing Your System for Installation 1-37            *     Preparing Your System for Installation2     1.8 Additional Tasks for Upgrade Installations    E              compatible. Although these files are not used during theLB              installation, they will cause problems if you need to4              relink ALL-IN-1 after the installation.  D           2. If you have a multilingual system, check that the filesE              OA$LLV*.EXE are not in SYS$COMMON:[SYSLIB]. If they are,_C              move them to the SYS$SYSROOT:[SYSLIB] directory beforeC              upgrading.   B           3. Check that all files in your site areas have at least@              system write access (S:W) and that Digital ALL-IN-1B              directories in non-site areas also have system delete              access (S:D).  E           4. Make copies of customized data files. See Section 1.8.1._  '     1.8.1 Copying Customized Data FilesY  E           ALL-IN-1 Version 3.2 uses modified versions of several datar           files:             o  In the base area:                -  A1CONFIG.DAT  A              -  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)   B              -  OA$PRINTSTYLES.DAT (The form is SMPRINTERTYPES and1                 new records have also been added)              o  In users' areas:$  5              -  OA$USERPRINTERSTYLES.DAT (The form isc                  USERPRINTSTYLES)  A           o  Files which have not been converted but their record "              layouts have changed:                -  ATTENDEE.DAT                -  DOCDB.DAT.  /     1-38 Preparing Your System for Installation     o      I                                    Preparing Your System for Installation I                            1.8 Additional Tasks for Upgrade Installationsn    F               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   A                     This file has been replaced by a new one with '                     additional records.   D               ALL-IN-1 Version 3.2 also supplies new versions of theH               File Definition Language (FDL) files in OA$LIB_SHARE whichE               are used to convert the corresponding data files to the F               new format. The old FDL files are not required after the               upgrade.  F               Before upgrading, make copies of any data files that youH               have customized as new versions of data files are providedF               with ALL-IN-1 Version 3.2. You must also return the dataF               files to the Digital standard format before you upgrade.  G               In the following instructions, the data file, PROFILE.DATEF               is used as an example. To make copies of your customizedG               data file and return them to the Digital standard format,A               do the following:   E               1. Make a backup copy of the modified PROFILE.DAT file,EE                  preferably outside the ALL-IN-1 directory structure:   V                  $ COPY OA$DATA_SHARE:PROFILE.DAT device:[directory]CUSTOM_PROFILE.DAT  C               2. Use Customization Management to make copies of the @                  customized PROFILn forms. For example, copy theB                  customized forms to CUSTOM_PROFILn and modify theE                  named data so that the .FILE and FORM_SET directives I                  specify the location of the backup copy of the file. The I                  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;;  H                  PROFIL2,PROFIL3,PROFIL4,PROFIL5,PROFIL6,PROFIL7,PROFIL8  >               3. Make the copies of the customized forms live.  I                               Preparing Your System for Installation 1-39E S  L      *     Preparing Your System for Installation2     1.8 Additional Tasks for Upgrade Installations    D           4. Remove the customized PROFILn forms and PROFIL.FDL from              the live area.   B           5. Convert the modified PROFILE.DAT back to the standardE              format. This may temporarily lose some data, but you can.E              reapply it from the backup copy of PROFILE.DAT later. To E              convert PROFILE.DAT back to the Digital standard format,_A              enter the following from the choice field of a menu:   1              <OA$CNV_CONVERT CUSTOM_PROFIL,PROFIL_  E              This creates a new version of OA$DATA:PROFILE.DAT to use.               during the upgrade.  -           6. Upgrade to ALL-IN-1 Version 3.2.   8           7. Follow the postinstallation instructions in;              Section 5.10.3 to restore your customizations._  3     1.9 Using the MAILbus 400 MTA and Digital X.500.  D           You can install a new ALL-IN-1 Version 3.2 system with theD           MAILbus 400 MTA and Digital X.500. You cannot upgrade from4           ALL-IN-1 Version 3.1 using these products.  C           For a new ALL-IN-1 Version 3.2 installation, with Digital C           X.500 and the MAILbus 400 MTA you must make sure that youSE           have installed all the required MAILbus 400 MTA and DigitalEC           X.500 components on your ALL-IN-1 system, configured them E           and completed any additional setup tasks. See the checklist C           in the MAILbus 400 MTA and Digital X.500 Planning chapter 7           in the  ALL-IN-1 Overview and Planning Guide._  &     1.10 Using a Remote Message Router  E           If you will be using a remote Message Router that is not in 9           the same VMScluster, you must do the following:   B           1. On the remote Message Router node, create an ALL-IN-1?              mailbox for the node (or cluster) on which you arei5              installing ALL-IN-1. See Section 1.10.1.o  B           2. Create an entry for the remote Message Router node inE              the network nodes database on the local machine on which_)              you are installing ALL-IN-1._  /     1-40 Preparing Your System for InstallationD A  R      I                                    Preparing Your System for Installation_I                                        1.10 Using a Remote Message Router0    I               3. Ensure that Message Router is running on the remote node_I                  before you start the installation. If it is not running,CD                  you will see errors when the installation procedure<                  starts up the Sender and Fetcher processes.  F         1.10.1 Create an ALL-IN-1 Mailbox on the Remote Message Router                Node   I               Do this if you are planning to use a remote Message Router.tI               If you do not create a mailbox before the installation, youeI               will see problems when the installation procedure starts upg/               the Sender and Fetcher processes.   F               Message Router must be running and configured before you%               start the installation.7  I               If you are using a remote Message Router which is on a nodeiE               in the same VMScluster as ALL-IN-1 the ALL-IN-1 mailboxn               name will be A1.  I               If the remote Message Router is not in the same VMScluster,YD               other ALL-IN-1 systems may be sharing the same MessageD               Router. The name of the Message Router mailbox must beD               unique for your system. For example, the mailbox name,F               mailboxname, could be localnodeA1 where localnode is theI               name of the node or the cluster on which you are installing E               ALL-IN-1. password is the password that you want to use G               for the Message Router mailbox. You are prompted for this /               password during the installation.A  H               On the Message Router node, do the following to create the               ALL-IN-1 mailbox::  $               $ RUN SYS$SYSTEM:MRMANY               MRM> ADD mailboxname /PASSWORD=password /COMPLETE_MESSAGES /IGNORE_SENDER _ ?                    /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS                MRM> EXITE  B               Note that you must not use the /OWNER qualifier when%               setting up the mailbox.           I                               Preparing Your System for Installation 1-41i C  B      *     Preparing Your System for Installation1     1.11 Running the Preinstallation System Check     1     1.11 Running the Preinstallation System Check   D           The ALL-IN-1 Version 3.2 installation procedure provides aA           Perform all preinstallation checks (PC) option. DigitalL?           recommends that you use this option before installingt?           ALL-IN-1 Version 3.2 to ensure that you have made allAB           necessary system changes before installing the software.  C           You can use this option while an existing ALL-IN-1 systemeD           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:  B           o  Run the phase of the installation in which you answerE              questions and the installation procedure performs system               checksR  A           o  Fix errors encountered by the installation procedureL  5           o  Exit without performing the installation   E           Where possible the installation checks are done in an ordersB           which finds fatal errors first. Section 1.11.1 describes?           the types of errors that are detected. Section 1.11.2cE           describes how to use the Perform all preinstallation checksc           (PC) option.  #     1.11.1 Types of Errors Reported   5           The following types of errors are detected:              o  Fatal errorse  ?              These are errors which cannot be corrected withouto>              stopping the installation procedure. Fatal errors              include:   >              -  Errors that require the machine to be rebooted  >              -  Errors that require an upgrade to prerequisiteC                 software, including OpenVMS, Message Router and the$E                 Message Router VMSmail Gateway, or Digital X.500, thev;                 MAILbus 400 MTA and Message Router Gateway.              o  Non-fatal errorsC  /     1-42 Preparing Your System for Installationt           I                                    Preparing Your System for InstallationiI                             1.11 Running the Preinstallation System Check     D                  These are errors that can be corrected from anotherE                  process without stopping the installation procedure.3*                  Non-fatal errors include:  ;                  -  Shareable images that are not installed   6                  -  Logical names that are not defined  E                  -  System parameters that can be changed dynamically   @                  -  Prerequisite software files that are missing  +                  -  Insufficient disk spaceO  I         1.11.2 Running the Perform all Preinstallation Checks (PC) OptionS  H               To run the Perform all preinstallation checks (PC) option,E               follow Steps 1 to 6 in Table 2-2 until you are promptedE2               with a list of installation options.                 Do the following:s  ;               1. Press Return to choose the default option.l  F                 ________________________ Note ________________________  C                 Choosing this option does not install the software.   F                 ______________________________________________________  4                  The following message is displayed:  Z                    The installation procedure allows you to perform the following actions:  1                    (I)   Perform the installatione;                    (PC)  Perform all preinstallation checks   ;                  * Which action do you wish to perform [I]:R  C               2. Choose the Perform all preinstallation checks (PC)h(                  option by entering: PC.  E               3. If a check fails with an error that can be correctedrA                  without stopping the installation procedure, younB                  are asked if you want to correct the error before                  continuing.  G                  If you answer yes, the installation checking procedure B                  pauses so that you can fix the error from anotherE                  process. When the error is fixed, you can resume thes6                  procedure, and the check is repeated.  I                               Preparing Your System for Installation 1-43     e      *     Preparing Your System for Installation1     1.11 Running the Preinstallation System Checkt    A              If you choose not to correct the error, you have theeE              option of halting the procedure or continuing to performtA              the remaining checks. If you choose to continue, the ?              installation procedure will terminate when all thee"              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:m  ?           1. Check that all prerequisite software is installed,m$              configured and running.  3           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.O  ?           From the privileged SYSTEM account, do the following:6  4           1. Shut down ALL-IN-1. See Section 1.13.1.  C           2. Ensure that Message Router is running and is correctlyo              configured.  D           3. Deinstall files in the site areas that are installed in(              memory. See Section 1.13.2.  3           4. Start the queue manager, if necessary.s  >           5. Back up the system disk and any target disks. See              Section 1.14.          /     1-44 Preparing Your System for Installatione r  l      I                                    Preparing Your System for InstallationRH               1.13 Final System Preparation Tasks: Upgrade Installations    !         1.13.1 Shut Down ALL-IN-1t  I               Ask users currently on the system to log out, and then shutT               down ALL-IN-1.  F                 ________________________ Note ________________________  D                 ALL-IN-1 must not be used by any batch jobs or usersA                 during the installation, or the installation will                  fail..  F                 ______________________________________________________  H               Do not allow anyone to log in again while the installationF               is in progress. You can allow OpenVMS users to remain onE               the system, but it is important to ensure that users do E               not use DCL HELP while the installation is in progress, G               as this can cause file locking problems when the DCL HELP F               library is updated during the installation. If possible,I               it is safer to ensure that there are no active users on theo               system.s  2         1.13.2 Deinstall Files Installed in Memory  H               If you have any files in the site areas that are installedC               in memory, for example, SITE$OA.A1$SECTION, deinstallrC               them on all nodes in the cluster before you start thetG               installation. Deinstalling files from memory will prevent D               them from being write locked. The installation sets anH               ACL on all files in the site areas so you must ensure thatH               all files in the site area have system write access (S:W).E               Make sure that you deinstall any of your own code-levelb=               executable images that are installed in memory.l  1         1.14 Back Up Your System and Target DisksI  H               Digital recommends that you do a system disk backup before.               installing any software because:  F               o  If a system failure occurs at a critical point duringG                  installation, your ALL-IN-1 system could be left in an $                  inconsistent state.  G               o  You can verify that the backup copy contains a workingtG                  system image and then replace the system disk with it.c  I               o  There is more contiguous free space, which may be neededt"                  for installation.  I                               Preparing Your System for Installation 1-45     y      *     Preparing Your System for Installation-     1.14 Back Up Your System and Target Diskse    B           If you are going to install ALL-IN-1 Version 3.2 on moreB           than one disk, back up the target disks that you will be           using.  @           Use the backup procedures that are established at yourC           site. For details on performing a system disk backup, seetA           the section on the Backup Utility in the OpenVMS System            Management Subkit.  E           At the beginning of the installation, VMSINSTAL asks if you *           have backed up your system disk.                                                                    /     1-46 Preparing Your System for Installation  t                       I                                                                         2 I         _________________________________________________________________a  I             Installation Procedure: New, Upgrade and Architecture Support     F               This chapter describes the procedures for installing theH               ALL-IN-1 Version 3.2 base, language and market components.<               The following installation examples are given:  G               o  A new installation of ALL-IN-1 Version 3.2 on an Alpha G                  system with the MAILbus 400 MTA and Digital X.500. SeeE                  Section 2.1.C  I               o  Upgrade installation of ALL-IN-1 Version 3.1 to ALL-IN-1 G                  Version 3.2 with Message Router and the Message RoutereC                  Directory Service. The installation is done on therG                  Alpha system in a mixed-architecture VMScluster, whereSF                  Message Router is installed on a remote VAX node. See                  Section 2.1.e  G               o  Addition or upgrade of additional architecture supportoE                  on a mixed-architecture VMScluster. See Section 2.2.C  F                 __________________ Before You Start __________________  E                 Do not start the installation until you have done thel                 following:  E                 1. Planned your installation by reading the  ALL-IN-1o/                    Overview and Planning Guide.   F                 2. Completed the system preparation tasks in Chapter 1=                    to check that your system is ready for the                      installation.  F                 ______________________________________________________  G               Questions asked by installation procedure are marked with G               an asterisk (*) at the beginning of the line. For help on I               answering a particular question, enter a question mark (?).e  I         Installation Procedure: New, Upgrade and Architecture Support 2-1r s  r      A     Installation Procedure: New, Upgrade and Architecture Supportc      D           During the installation procedure a number of cautions andD           general informational messages are displayed. Read all theC           displayed messages carefully. Table 2-1 gives information 5           which you may need during the installation.e  E           Table_2-1_Information_About_the_Installation_Procedure_____l  E           Question_________Answer____________________________________   #           How long         On_Alphae@           will the         As an example, installing on an AlphaD           installation     4000-610 system takes about 1 hour and 15C           take?            minutes for a full installation when the5  D                            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 ofC                            processor you are using. The performancer=                            specification of the disks has theh;                            greatest effect. For example, an @                            installation on a VAX 4000-300 systemC                            takes approximately 3.5 hours when files @                            are installed on an RF71 disk and 1.5B                            hours if files are installed on an RZ26                             disk.  8                            The times for new and upgradeD                            installations are approximately the same.  .           How do I get     Enter ? at any time           help?s              What is          A1032           the product            identifier?t  E                                              (continued on next page)s        E     2-2 Installation Procedure: New, Upgrade and Architecture Support_ N         I             Installation Procedure: New, Upgrade and Architecture Support       B               Table 2-1 (Cont.) Information About the InstallationI               __________________Procedure________________________________   I               Question_________Answer____________________________________n  @               What do I        Restart the installation from the8               do if the        beginning. See Chapter 4.               installation               fails before               the automaticC               postinstalla-a               tion phase?   ,               How do I         Press CTRL/Y.E               abort the        The installation procedure deletes all B               installation?    files in the installation temporary  D                                working directory. Note that this mayD                                take a long time. Any files that haveG                                been provided to target locations remainoE                                there. Note: VMSINSTAL does not deletecF                                any accounts, identifiers, or directory;                                structures that are created.t  8                                Restart the installation.  -               How do I         See Chapter 4.n               restart the I               installation?______________________________________________t  D         2.1 Installation Procedure for New and Upgrade Installations  E               Table 2-2 lists all the installation steps for a new ortD               upgrade installation. The example scripts in the tableF               show extracts from a new installation on an Alpha systemH               using the MAILbus 400 MTA and Digital X.500 and an upgradeI               installation from ALL-IN-1 Version 3.1 with Message Router.i  G               Depending on your distribution media, you may be prompted F               to change the tape or cartridge during the installation.          I         Installation Procedure: New, Upgrade and Architecture Support 2-3l s         A     Installation Procedure: New, Upgrade and Architecture Supporta@     2.1 Installation Procedure for New and Upgrade Installations    8     Table 2-2 Installation Procedure for New and UpgradeE     __________Installations__________________________________________r  E     Step__Action_____________________________________________________   D     1     Create a log file for the installation. Digital recommends?           that you keep a record of the installation in case of B           problems. You can keep a log by using either a hard copyA           terminal or a log file. To keep a record in a log file,q           enter:  $           $  SET HOST 0/LOG=filename  B           where filename is the name of the log file. The log fileB           is created in the directory where you enter the command.>           If you do not specify a filename, the file is calledB           SETHOST.LOG. The installation log file will be about 200           blocks.   A           If you are running console management software, you canr?           use this to record the installation. See your consolen;           management documentation for further information._  E     _________________________________________________________________y  B     2     Load and mount the media that contains the software kit.  B           If you are installing from a tape or cartridge, you willD           be prompted to change the tape or cartridge when required.E           You do not need to change the media when you are installingi#           from a compact disc (CD).r  E     _________________________________________________________________h  E                                              (continued on next page)                     E     2-4 Installation Procedure: New, Upgrade and Architecture Support            I             Installation Procedure: New, Upgrade and Architecture SupporteI              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________m  I         Step__Action_____________________________________________________o  E         3     Invoke the VMSINSTAL procedure from the SYSTEM account.n  +               Enter the following commands:   &               $ SET DEFAULT SYS$UPDATE'               $ @VMSINSTAL A1032 devicen  A               To use an alternate working device (AWD), enter thel&               following command lines:  &               $ SET DEFAULT SYS$UPDATE8               $ @VMSINSTAL A1032 device OPTIONS AWD=disk  @               device is the device on which you have mounted theE               distribution media. You can use a physical or a logicalnG               device name but do not use logical device names beginningsI               with A1$, OA$, or OA1$. A1032 is the product identifier andaC               disk is the location of the alternate working device.o  I         _________________________________________________________________Y  (         4     Verify your system backup.  I                  OpenVMS VAX Software Product Installation Procedure V6.2t  )               It is 19-MAR-1996 at 13:04.i  =               Enter a question mark (?) at any time for help.aL               * Are you satisfied with the backup of your system disk [YES]?  '               Press RETURN to continue.S  I         _________________________________________________________________   I                                                  (continued on next page)h          I         Installation Procedure: New, Upgrade and Architecture Support 2-5            A     Installation Procedure: New, Upgrade and Architecture Supportl@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________i  E     Step__Action_____________________________________________________   5     5     Load the distribution media (first volume).e  H           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?  E           Enter the product identifier, A1032, at the prompt. Enter YtD           to confirm that the media is correctly mounted and you are           ready to start. E           ___________________________________________________________n           For installationE           type__________________Go_to________________________________M  &           New                   Step 6  E           Upgrade_______________Step_8_______________________________s  E     _________________________________________________________________d  <     6     New_Installation: Enter the number for the type of+           installation that you want to do.A  0           This is a LOCAL ALL-IN-1 V3.2 BASE kit  *           Logical OA$IMAGE is not defined.I           No ALL-IN-1 image can be found using the default specification.   L           Using the FULL ALL-IN-1 V3.2 kit, the following installation types             can be performed:e  3            (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]:  3           Enter 1 to install a new ALL-IN-1 system.l  E                                              (continued on next page)g  E     2-6 Installation Procedure: New, Upgrade and Architecture SupportC t  1      I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installations_    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________e  I         Step__Action_____________________________________________________o  I         _________________________________________________________________   B         7     New_Installation: Confirm that you want to start the               installation.   Y                   The installation procedure allows you to perform the following actions:o  0                   (I)   Perform the installation;                   (PC)  Perform all pre-installation checkso  8               * Which action do you wish to perform [I]:  5               Press RETURN to start the installation.P  )               To_continue: go to Step 10.A  I         _________________________________________________________________l  D         8     Upgrade_Installation: Enter the number for the type of/               installation you want to perform.a  4               This is a LOCAL ALL-IN-1 V3.2 BASE kit  I               The current ALL-IN-1 image identification is ALL-IN-1 V3.1.a  P               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.2D                 (2)  Add, upgrade, or update Alpha components for an)                      ALL-IN-1 V3.2 systemr  A                 (RL) Register licenses for pre-requisite softwarea  @               * Which installation do you wish to perform [1]: ?  =               Enter 1 to upgrade an existing ALL-IN-1 system.a  B               If you are running ALL-IN-1 in a single-architecture9               VMScluster, you are not offered option (2).l  I         _________________________________________________________________t  I                                                  (continued on next page)   I         Installation Procedure: New, Upgrade and Architecture Support 2-7e p  i      A     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 UpgradeE     __________________Installations__________________________________e  E     Step__Action_____________________________________________________l  B     9     Upgrade_Installation: Confirm that you want to start the           installation.   U               The installation procedure allows you to perform the following actions:_  ,               (I)   Perform the installation7               (PC)  Perform all pre-installation checks D               (RC)  Run conflict checking and resolution tool (CART)  4           * Which action do you wish to perform [I]:  9           Press RETURN to continue with the installation.   E     _________________________________________________________________   @     10    Confirm that the License PAK is registered and loaded:  T           * Does this product have an authorization key registered and loaded [YES]?  #           Press RETURN to continue. E           ___________________________________________________________            For installationE           type__________________Go_to________________________________   '           Upgrade               Step 11   E           New___________________Step_12______________________________   E     _________________________________________________________________   E     11    Upgrade_Installation: Confirm that you want to purge files.   K           * Do you want to purge files replaced by this installation [YES]?t  &           Press RETURN to purge files.  E     _________________________________________________________________   E                                              (continued on next page)   E     2-8 Installation Procedure: New, Upgrade and Architecture Support            I             Installation Procedure: New, Upgrade and Architecture SupporttI              2.1 Installation Procedure for New and Upgrade Installationsu    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________y  I         Step__Action_____________________________________________________e  D         12    Indicate whether you want to integrate DATATRIEVE with               ALL-IN-1.d  X                DATATRIEVE can be integrated into ALL-IN-1.  On VAX systems with Deferred  V                image activation enabled the DATATRIEVE image will be deferred.  If you  R                use the standard DATATRIEVE image SYS$SHARE:DTRSHR.EXE then you can  X                select to dynamically activate DATATRIEVE.  You will still be able to use  W                DATATRIEVE within ALL-IN-1, but you will avoid any performance impact ofn  C                having it physically linked with the ALL-IN-1 image.   G               * Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]?   F               Press RETURN if you do not want to integrate DATATRIEVE.  C               If you want to integrate DATATRIEVE, enter Y. You are F               prompted to supply the name of the DATATRIEVE image thatB               you want to link with. If you are using the standardF               DATATRIEVE image, SYS$SHARE:DTRSHR.EXE, you are asked ifD               you want to dynamically activate DATATRIEVE during the>               ALL-IN-1 startup. It is recommended that you do.  I         _________________________________________________________________n  I                                                  (continued on next page)_                      I         Installation Procedure: New, Upgrade and Architecture Support 2-9.           A     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 UpgradeE     __________________Installations___________________________________  E     Step__Action_____________________________________________________   <     13    Indicate whether you want to install WPS-PLUS with?           ALL-IN-1. If you do not have a license which includes 8           WPS-PLUS, you will not be asked this question.  R               If you wish to have the WPS-PLUS editor available, answer YES to the  U               following question.  If you do not wish to install the WPS-PLUS editor,a                 answer NO.                 NOTE:_  S                   o If WPS-PLUS is not installed then the WPS-PLUS linguistics aids_  Q                     (SPELL CHECKER and THESAURUS) and the WPS-PLUS SORT and MERGEu  C                     processing functionality will not be available.   Q                   o You will be able to do an ALL-IN-1 update installation to addu  V                     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]?  E           Press RETURN to install WPS-PLUS. You are then asked if youh@           want to install the graphics and page overlay samples:  W           %A1-I-WPSLINK, The WPS-PLUS editor will be installed and linked with ALL-IN-1e  T               This kit contains a library of Encapsulated PostScript(R) graphics and  T               PostScript(R) Page Overlay samples.  Their total size is approximately  R               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.  E                                              (continued on next page)   F     2-10 Installation Procedure: New, Upgrade and Architecture Support _  _      I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade InstallationsP    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________l  I         Step__Action_____________________________________________________   I         _________________________________________________________________n  <         14    Indicate whether you want to incorporate ACMS.  M               If you wish to interface with ACMS, answer YES to the following                  questions.                 NOTE:c:                  o ACMS must be installed before ALL-IN-1.Q                  o If you answer YES and the relevant ACMS files are present theny  U                    the interface to ACMS will be built. If the files are not present,   P                    then you may either continue the installation without linking  N                    with ACMS or abort the installation to correct the problem.  A               * Do you want to integrate ACMS with ALL-IN-1 [NO]?_  @               Press RETURN if you do not want to integrate ACMS.  4               Enter Y if you want to integrate ACMS.  I         __________________________________________________________________  C         15    Indicate whether to you want to build a multilanguage_               system._  W                   If you wish to use more than one ALL-IN-1 language, answer YES to the   %                   following question.   B               * Do you want to build a MULTI-LANGUAGE system [NO]?  F               Press RETURN if you do not want to build a multilanguage               system.i  I               Enter Y if you plan to install additional languages and youn3               want to build a multilanguage system.(  I         _________________________________________________________________   I                                                  (continued on next page)e  I        Installation Procedure: New, Upgrade and Architecture Support 2-11            A     Installation Procedure: New, Upgrade and Architecture Supporta@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________n  E     Step__Action_____________________________________________________w  '     16    Select a default date format.t  S               ALL-IN-1 allows you to select a default date format for each language_  S               you have installed. This will become the default ALL-IN-1 date format_  R               for each user (on a per language basis.) This may be changed by each  T               user through the Set Working Conditions option on the User Setup Menu.  3                   Alphanumeric Date    Numeric Date   G                   1   DD-MMM-YYYY      MM/DD/YY      (Standard Default)l  /                   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_A                   7   ***** Reserved (Means system default) *****uE                   8   DD-MM-YYYY       DD/MM/YY      (Numeric format) E                   9   MM-DD-YYYY       MM/DD/YY      (Numeric format)   1           * Which date format do you require [1]:   D           Press RETURN to use the default format or enter the number3           for the date format that you want to use.   E     _________________________________________________________________   E                                              (continued on next page)                   F     2-12 Installation Procedure: New, Upgrade and Architecture Support s  w      I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installationsf    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations___________________________________  I         Step__Action_____________________________________________________   I         17    Specify the greatest number of simultaneous ALL-IN-1 users.,  H               * What will be the greatest number of simultaneous ALL-IN-               1 users:  "               Upgrade_installation  B               A default value is given. Press RETURN to accept the               default value.                 New_installation  C               Specify the maximum number of ALL-IN-1 users that youcE               expect at any one time. The installation procedure uses I               this entry to check that system parameters are large enougha7               to support your intended number of users.   I         _________________________________________________________________t  G         18    Specify a batch queue for running the job that checks the 0               Mail Sender and Fetcher processes.  V               * Which batch queue do you want to use for the Sender/Fetcher check job?                   [SYS$BATCH]:  G               Press RETURN to use the default queue or specify the name_)               of an existing batch queue.P  9               For_an_upgrade_installation: Go to Step 20.   I         _________________________________________________________________U  I                                                  (continued on next page)_            I        Installation Procedure: New, Upgrade and Architecture Support 2-13_ _  _      A     Installation Procedure: New, Upgrade and Architecture Supporte@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________   E     Step__Action_____________________________________________________E  B     19    New_installation: Specify a batch queue for starting theC           AIDA and File Cabinet Servers, and the Sender and Fetcher            processes.  T           ALL-IN-1 must use a running batch queue on this node to start the AIDA and  E           File Cabinet Servers, and the Sender and Fetcher processes.,  6           * Which queue do you want to use? [default]:  D           Press RETURN to accept the default queue or enter the nameE           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 NodeA           Specific Batch Queue Master file, and will be stored inwD           the configuration files of any Servers created during thisE           installation. You can change the queue later, or add queues @           for other nodes in your cluster, using the Manage nodeA           specific queues (MNQ) option from the System Management            menu.S  E     _________________________________________________________________a  E                                              (continued on next page)T                              F     2-14 Installation Procedure: New, Upgrade and Architecture Support l  i      I             Installation Procedure: New, Upgrade and Architecture SupportII              2.1 Installation Procedure for New and Upgrade Installationso    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________T  I         Step__Action_____________________________________________________t  G         20    Indicate if you want to send and receive remote mail. The H               installation procedure checks the type and versions of theG               message transport and directory service software that are '               installed on your system._  Q               ALL-IN-1 Electronic Messaging can send and receive messages, to ande  Q               from other computer systems using either the MAILbus 400 or Messagea                 Router products.  M               * Do you want to be able to send and receive remote mail [YES]?   :               Press RETURN if you want to use remote mail.  I               If you answer NO to this question, ALL-IN-1 users will only_F               be able to exchange messages locally with other users on'               the same computer system._  I               ___________________________________________________________PI               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 thes               MAILbus 400 MTAs  I               Are_upgrading_with_Message_Router____Step_22________________  I         _________________________________________________________________s  I                                                  (continued on next page)L              I        Installation Procedure: New, Upgrade and Architecture Support 2-15            A     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 UpgradeE     __________________Installations__________________________________S  E     Step__Action_____________________________________________________p  ?     21    New_Installation with the MAILbus 400 MTA and DigitalrA           X.500: Confirm that you want to use the MAILbus 400 MTAk           for remote mail.  O             If you plan to use MAILbus 400 as your MTA, then answer YES to thism  K             question. You will not have been offered this choice unless they  L             installation checks have revealed that the product is installed.  S             Note that even though MAILbus 400 appears to be installed and initially   Q             configured, it is unlikely that it will sucessfully process your mail   O             until you have completed all the set up tasks described in the Mail0               Management Guide.r  O             If you answer NO to this question, ALL-IN-1 users will only be able,  O             to exchange messages locally, unless you subsequently choose to use   0             Message Router (if it is available.)  A           * Do you want to use MAILbus 400 for remote mail [YES]?_  B           Press RETURN to use the MAILbus 400 MTA for remote mail.  @           It does make any difference to the installation if theC           MAILbus 400 MTA is installed on the same node as ALL-IN-1_C           or on a different node in the same VMScluster on a remote E           node outside the cluster, providing that you have completedlD           all the configuration and set up tasks that are covered in*           the Overview and Planning Guide.  %           To_continue: Go to Step 25.S  E     _________________________________________________________________i  E                                              (continued on next page)   F     2-16 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations___________________________________  I         Step__Action_____________________________________________________   H         22    Upgrade_Installation: Confirm that you want to use Message%               Router for remote mail.-  E               ALL-IN-1 on a VAX node can be configured to use a local E               Message Router which is installed on the same node or a E               remote Message Router which is installed on a different C               node. ALL-IN-1 on an Alpha node can only use a remotelG               Message Router. This example script is on an Alpha systemgF               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]?   F               Answer Y to confirm that you want to use Message Router.  I         _________________________________________________________________   F         23    Upgrade_Installation: If Message Router is not installedI               on this node, confirm that you want to use a remote Message_               Router._  A               * Do you want to use a remote Message Router [YES]?_  F               Enter Y to confirm that you want to use a remote Message               Router.   D               Note that the default value for this answer depends onE               whether you are doing the upgrade installation on a VAX-E               system or an Alpha system. In this example, the upgrade)F               is on an Alpha system, so the default is to use a remote               Message Router.r  I         _________________________________________________________________   I                                                  (continued on next page)           I        Installation Procedure: New, Upgrade and Architecture Support 2-17M           A     Installation Procedure: New, Upgrade and Architecture SupportY@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________m  E     Step__Action_____________________________________________________t  D     24    Upgrade_Installation: Enter the name of the remote Message           Router node.  /           * What node is the Message Router on:   A           Enter the DECnet node name of the remote Message Router_           node._  A           Note that the remote Message Router node must be in the(=           network nodes database on the node on which you areoA           installing ALL-IN-1. As this is an upgrade you will not A           be asked for a password for the Message Router mailbox.p             Additional_Questions  B           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:c  >           The password must be a minimum of 8 characters and a9           maximum of 32 characters. Confirm the password.A  E     _________________________________________________________________   E                                              (continued on next page)                         F     2-18 Installation Procedure: New, Upgrade and Architecture Support o  L      I             Installation Procedure: New, Upgrade and Architecture SupportoI              2.1 Installation Procedure for New and Upgrade Installationsl    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________   H         25    Indicate the type of Mail Directory support that you want.  I               For new installations where Digital X.500 is installed, the %               following is displayed:E  D               * What type of Mail Directory support do you want [X]:  B               The options that are available depend on the type ofB               directory service software that is installed on yourH               system. You are given the appropriate options and defaultsF               from the following list, depending on what is installed.  G               Press RETURN to accept the default or enter the value forn?               the type of Mail directory support that you want.lI               ___________________________________________________________.I               For__________________________________Option_to_Enter_______a  4               No Mail directory support            0  4               The Message Router Directory         M+               Service as the Mail directorya  4               The Digital X.500 Directory Service  XI               as_the_Mail_directory______________________________________   E               When you are installing with Digital X.500, it does notdC               matter whether Digital X.500 is installed on the samesG               node as ALL-IN-1 or on a remote node outside the cluster, B               providing that you have done all the necessary setupE               and configuration tasks as outlined in the Overview and                Planning Guide.n  I               If_you_have_specified_no_Mail_directory_support, go to Step                28.e  I         _________________________________________________________________a  I                                                  (continued on next page)e    I        Installation Procedure: New, Upgrade and Architecture Support 2-19M g  o      A     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 UpgradeE     __________________Installations__________________________________a  E     Step__Action_____________________________________________________   B     26    Specify if you want the Mail directory to be the primary           directory.  J           Do you want the Mail Directory to be the primary directory [NO]?  A           Press RETURN to use the Mail directory as the secondary_           directory.  .           For new installations go to Step 28.  E     _________________________________________________________________   D     27    Installation_with_Message_Router: Enter a password for the;           Mail Directory User Agent account and confirm it.   E           The text that is displayed depends on whether you are usingaB           a remote Message Router, and whether that Message RouterD           is in the same VMScluster. Read the informational messages0           carefully and follow the instructions.  >           The password length must between 6 and 8 characters.  6           * Press RETURN to continue the installation:Q           * Enter a password for the Message Router Directory user agent account:i  <           * Please confirm the password which you specified:  =           Press RETURN and then enter a password for the Maill6           Directory user agent account and confirm it.  E     __________________________________________________________________  E                                              (continued on next page)_              F     2-20 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture Support.I              2.1 Installation Procedure for New and Upgrade Installations_    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________s  I         28    Indicate if you want outgoing messages translated to ASCII.   M               * Do you want to translate all outgoing messages to ASCII [NO]?t  ?               Press RETURN if you do not want outgoing messages                translated.o  F                       _____________________ Note _____________________  ?                       If you are using a remote MAILbus 400 MTA_@                       on Digital UNIX, you must answer Y to thisB                       question if WPS-PLUS to ASCII converters areC                       not installed on the MAILbus 400 MTA node and E                       you want to exchange messages with non-ALL-IN-1i                       users.  F                       ________________________________________________  H               Enter Y, if you want outgoing messages translated. You areF               then asked if you want all attachments to be translated.  F               * Do you want to translate all message attachments [NO]?  F               Press RETURN if you do not want to translate all messageG               attachments. If you enter Y to this question, all messageyD               attachments are translated to ASCII if the appropriate?               converters are installed on your ALL-IN-1 system.h  I         _________________________________________________________________   I                                                  (continued on next page)E                  I        Installation Procedure: New, Upgrade and Architecture Support 2-21t i  a      A     Installation Procedure: New, Upgrade and Architecture Supports@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________   E     Step__Action_____________________________________________________o       29    System checking.  B           The installation procedure checks mandatory and optional=           software prerequisites. You may be asked additionalnC           questions depending on the software and licences that aret#           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.n  A           If DEC Notes is not installed and your ALL-IN-1 licensenC           supports Group Conferencing, you are asked if you want ton6           continue without Group Conferencing support.  E     _________________________________________________________________e  E                                              (continued on next page)A                                            F     2-22 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installationst    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________   D         30    Indicate if you want client applications to connect to5               ALL-IN-1 using TCP/IP network protocol._  B               You are only asked the following question if DEC TCPE               /IP Services (UCX) or other TCP/IP network sofware thatn7               emulates UCX is installed on your system.   0               * Do you want to use TCP/IP [YES]?  ?               Press RETURN if you want to use TCP/IP for client A               connections. If you do, you are asked the following D               questions if default service names for the AIDA ServerH               and ALL-IN-1 File Cabinet Server are not registered in the)               Internet Services database.)  ?               * Enter a port number for the AIDA Server [7300]:e3               * Enter a port number for the ALL-IN-_+               1 File Cabinet Server [7373]:_  G               Enter a different TCP/IP port number for each server. TheeF               port numbers can be in the range 1024 to 65535. You mustI               use the default values if you are planning to use TeamLinkse               client software.  H               The installation procedure checks that the UCX$IPC_SHR.EXEI               image is installed. If it is not, you must install it after_               the installation._  I         __________________________________________________________________           31    System checking.  I               The installation procedure checks system parameters, quotasrB               and identifiers. For new installations, the ALL-IN-1D               identifiers are created. The identifiers already exist(               for upgrade installations.  E               For ALL-IN-1 Version 3.2, the identifier OA$FS_ADMIN is H               required. If you do a new installation and this identifierG               already exists, you are asked to confirm whether you wantoE               to use the existing identifier. Follow the installationeH               instructions. OA$FS_ADMIN is used for access control only.  I                                                  (continued on next page)   I        Installation Procedure: New, Upgrade and Architecture Support 2-23e n  m      A     Installation Procedure: New, Upgrade and Architecture Supportn@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________   E     Step__Action_____________________________________________________   E     _________________________________________________________________   "     32    Enter the language code.  H           * 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 languageC           code. See the  ALL-IN-1 Installation: Language and Market_,           Supplement supplied with your kit.  E     _________________________________________________________________y  E                                              (continued on next page)s                                                    F     2-24 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture SupporteI              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________t  I         Step__Action_____________________________________________________d  %         33    Enter the dialect code.   D               Your language kit may also contain one or more dialectI               components. Enter the dialect code that you want to use. If I               your language kit does not contain a dialect component, yous*               are not asked this question.  B               %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesetsD               %VMSINSTAL-I-RESTORE, Restoring product save set B ...  S                   If you wish to install a dialectal variation of ENGLISH language,t  V                   enter the code for the dialect component you wish to use.  If you do  P                   not wish to install a dialectal variation of ENGLISH language,  7                   then accept the answer of NO_DIALECT.   U               * Enter dialect code for this installation (5 characters) [NO_DIALECT]:e  E               Press RETURN or enter the dialect code that you want tooF               use. See the  ALL-IN-1 Installation: Language and Market               Supplement._  H               The installation procedure continues with system checking.I               ___________________________________________________________p               For installationI               type__________________Go_to________________________________l  +               New                   Step 34o  I               Upgrade_______________Step_35______________________________   I         _________________________________________________________________p  I                                                  (continued on next page)p        I        Installation Procedure: New, Upgrade and Architecture Support 2-25     o      A     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 UpgradeE     __________________Installations__________________________________   E     Step__Action_____________________________________________________   @     34    New_Installation: Specify the devices for the ALL-IN-1           areas.  E           * Which device will hold the ALL-IN-1 shared library files:R.           * Which device will hold the ALL-IN-/           1 shared data files       [A1DISK1:]:a.           * Which device will hold the ALL-IN-/           1 ENGLISH language files  [A1DISK1:]:t.           * Which device will hold the ALL-IN-/           1 mail area SDAF file     [A1DISK1:]: B           * How many shared directories do you want to create [1]:.           * Which device will hold the ALL-IN-/           1 shared directory SHARE1 [A1DISK1:]:d.           * Which device will hold the ALL-IN-/           1 lexicon files           [A1DISK1:]:   D           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.  A           If lexicon files have already been installed by anotherr?           product, you are not asked the question about lexicon.           files.  E     __________________________________________________________________        35    Enter the market code.  F           * Enter market code for this installation (2 characters): US  D           Enter the two-letter market code for the installation. SeeE           the  ALL-IN-1 Installation: Language and Market Supplement. E           ___________________________________________________________mE           Installation_type_____Go_to_________________________________  "           New                   36  E           Upgrade_______________43___________________________________   E                                              (continued on next page)   F     2-26 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture SupporthI              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________   I         _________________________________________________________________   G         36    New_Installation: Specify an OpenVMS account and passwordt=               for the ALL-IN-1 manager. Confirm the password.   @               %A1CUS-I-RECOUK, Restoring the MARKET kit savesetsD               %VMSINSTAL-I-RESTORE, Restoring product save set B ...D               %VMSINSTAL-I-RESTORE, Restoring product save set C ...  U                     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]:t  B               * Enter a password for the ALL-IN-1 MANAGER account:  @               * Please confirm the password which you specified:  I         __________________________________________________________________  D         37    New_Installation: Enter a system group UIC and defaultC               device and directory for the ALL-IN-1 manager. Do nottE               create the ALL-IN-1 manager's account in a subdirectoryn-               of an OpenVMS system directory.o  7               * What UIC do you want to use for ALL-IN-n                1 MANAGER account:F               * What default device do you want to use for the ALL-IN-!               1 MANAGER'S account                  [A1DISK1:]E               * What default directory do you want to use for ALL-IN-s"               1 MANAGER'S account?                 [ALLIN1:]L  I         _________________________________________________________________a  H         38    New_Installation: Enter a UIC for the accounts used by theG               Transfer User utility. The UIC must not be a system group                UIC.  C               * What UIC do you want to use for A1$XFER_IN account: H               * What UIC do you want to use for the A1$XFER_OUT account:  I                                                  (continued on next page)d  I        Installation Procedure: New, Upgrade and Architecture Support 2-27p d  n      A     Installation Procedure: New, Upgrade and Architecture Supportw@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________i  E     Step__Action_____________________________________________________r  E     _________________________________________________________________f  C     39    New_Installation: Enter a UIC for the account used by theaE           Script Symbiont utility. The UIC must not be a system group            UIC.  3           * What UIC do you want to use for ALL-IN-E$           1 SCRIPT SYMBIONT account:  E     _________________________________________________________________   C     40    New_Installation: Enter a UIC for the account used by the D           File Cabinet Server for authenticating remote clients into@           a non-privileged account. The UIC must not be a system           group UIC.  3           * What UIC do you want to use for ALL-IN-n!           1 OAFC$DEFAULT account:   E     _________________________________________________________________P  @     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.  3           * What UIC do you want to use for ALL-IN-p            1 OAFC$SERVER account:  E     _________________________________________________________________i  E                                              (continued on next page)_                  F     2-28 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture SupportdI              2.1 Installation Procedure for New and Upgrade Installationsr    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________M  I         Step__Action_____________________________________________________i  I         42    New_Installation: Specify the top-level directories for the                ALL-IN-1 areas.n  X               * Enter ALL-IN-1 top-level directory required for the shared library files                   [ALLIN1]: U               * Enter ALL-IN-1 top-level directory required for the shared data filest                   [ALLIN1]:nZ               * Enter ALL-IN-1 top-level directory required for all ENGLISH language files                   [ALLIN1]:nW               * Enter ALL-IN-1 top-level directory required for the mail area SDAF filea                   [ALLIN1]:gV               * Enter the name required for the SHARED DIRECTORY on A1DISK1: [ALLIN1]:  (               Go to Step 45 to continue.  I         __________________________________________________________________  F         43    Upgrade_Installation: Enter the OpenVMS username for the)               ALL-IN-1 manager's account.a  A               * What is the existing VMS username for the ALL-IN-a!               1 account [ALLIN1]:s  F               Enter the OpenVMS username for the ALL-IN-1 account. The,               account details are displayed.  I         __________________________________________________________________  C         44    Upgrade_Installation: Confirm that the details of the 5               ALL-IN-1 manager's account are correct.   N               * Are all the specified account's characteristics correct [YES]?  =               Press RETURN if all the information is correct.e  I         _________________________________________________________________d  I                                                  (continued on next page)a  I        Installation Procedure: New, Upgrade and Architecture Support 2-29_ _  _      A     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 UpgradeE     __________________Installations__________________________________t  E     Step__Action_____________________________________________________m  <     45    Run the IVP (Installation Verification Procedure).  D           * Do you want to run the IVP after the installation [YES]?  E     ______Press_RETURN_to_run_the_IVP._______________________________   A           All the installation questions have now been completed.a  @           If you are installing ALL-IN-1 Version 3.2 on a mixed-C           architecture VMScluster, see Section 2.2 for instructions C           on adding architecture support for a second architecture.c  <           If you are not installing on a single-architecture(           VMScluster, go to Section 2.3.  0     2.2 Adding or Upgrading Architecture Support  C           Table 2-3 explains when you can do an installation to addN*           or upgrade architecture support.  E           Table 2-3 When to Install/Upgrade VAX or Alpha ArchitecturesE           __________Support___________________________________________  E           Install/Upgrade_______When_you_have_already_done___________   E           VAX architecture      A new or upgrade ALL-IN-1 Version 3.2 B           support               installation on an Alpha system in3                                 the same VMScluster   E           Alpha architecture    A new or upgrade ALL-IN-1 Version 3.2 C           support               installation on a VAX system in theeE           ______________________same_VMScluster._____________________e  @           The questions that you are asked during the additionalD           architecture installation depend on the responses that youC           gave during the new or upgrade installation. For example,eC           if you did not install WPS-PLUS during the new or upgrade_B           installation, you are not asked any additional questions           about WPS-PLUS._  F     2-30 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture SupportRI                              2.2 Adding or Upgrading Architecture Supporti             2.2.1 Before You Start  @               Before you start the installation, you must do the               following:  C               1. If you are installing architecture support for the H                  first time, make a note of the location of the ALL-IN-1G                  configuration file, OA$DATA_SHARE:A1CONFIG.DAT, on thehG                  system where you have already installed a new ALL-IN-1eF                  Version 3.2 system or upgraded to an ALL-IN-1 VersionC                  3.2 system. You will be asked for this information )                  during the installation.t  F               2. Run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP, to=                  check for logicals containing SYS$SYSDEVICE.e  @               3. From the ALL-IN-1 manager's account on the nodeE                  where ALL-IN-1 is already installed, run the script,t3                  OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP:_  *                  $ SET HOST 0/LOG=filename                   $ ALLIN1/NOINIT@                  Enter CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP  I                  If references to SYS$DEVICE are found, a warning messagesE                  is displayed. You must remove the references as theyeG                  will refer to different devices on a VAX system and an_H                  Alpha system. If the references are not corrected, data,                  may be lost on your system.  B                  The installation procedure also runs this script.  D         2.2.2 Installation Procedure for Adding Architecture Support  B               Table 2-4 shows an example script for an additional-F               architecture installation on a VAX system. The following"               information is used:  F               o  ALL-IN-1 Version 3.2 is already installed on an Alpha/                  system in the same VMScluster.e  ;               o  WPS-PLUS is installed on the Alpha system._  G               o  ALL-IN-1 has been configured as a multilanguage system_%                  on the Alpha system.   @               o  Message Router is installed on this VAX system.  I        Installation Procedure: New, Upgrade and Architecture Support 2-31r           A     Installation Procedure: New, Upgrade and Architecture Support 0     2.2 Adding or Upgrading Architecture Support    E           The example includes the script for both adding VAX support @           for the first time and upgrading existing VAX support.C           The installation questions and script are similar for theh/           addition or upgrade of Alpha support.u      E     Table_2-4_Installation_Procedure_for_Adding_Architecture_Support_   E     Step__Action_____________________________________________________   +     1 to  Follow Steps 1 to 5 in Table 2-2.fE     5     ____________________________________________________________E           For_Installation_Type________________Go_to_________________a  5           Upgrade                              Step 6L  E           New__________________________________Step_7________________n  E     _________________________________________________________________   E                                              (continued on next page)A                                              F     2-32 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture SupportsI                              2.2 Adding or Upgrading Architecture Support:    H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support________________________________________t  I         Step__Action_____________________________________________________   D         6     Upgrade_Installation: Enter the number for the type of/               installation you want to perform.o  4               This is a LOCAL ALL-IN-1 V3.2 BASE kit  I               The current ALL-IN-1 image identification is ALL-IN-1 V3.2.s  P               Using the FULL ALL-IN-1 V3.2 kit, the following installation types                 can be performed:e  B                 (1)  Add, upgrade, or update VAX components for an)                      ALL-IN-1 V3.2 systemCB                 (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 B                 (5)  Add, upgrade, or update VAX components for an:                          ALL-IN-1 V3.2 additional language)                 (6)  Update ALL-IN-1 V3.2   A                 (RL) Register licenses for pre-requisite software   >               * Which installation do you wish to perform [1]:  D               Press RETURN to upgrade VAX components for an existingI               ALL-IN-1 Version 3.2 system that is already installed on ano2               Alpha system in the same VMScluster.  (               To_Continue: Go to Step 8.  I         _________________________________________________________________.  I                                                  (continued on next page)F              I        Installation Procedure: New, Upgrade and Architecture Support 2-33     1      A     Installation Procedure: New, Upgrade and Architecture Supportn0     2.2 Adding or Upgrading Architecture Support    D     Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureE     __________________Support________________________________________o  E     Step__Action______________________________________________________  <     7     New_Installation: Enter the number for the type of+           installation you want to perform.s  0           This is a LOCAL ALL-IN-1 V3.2 BASE kit  *           Logical OA$IMAGE is not defined.I           No ALL-IN-1 image can be found using the default specification.l  L           Using the FULL ALL-IN-1 V3.2 kit, the following installation types             can be performed:w  3            (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  2           Enter 2 to add VAX architecture support.  E     _________________________________________________________________   :     8     Confirm that you want to start the installation.  U               The installation procedure allows you to perform the following actions:o  ,               (I)   Perform the installation7               (PC)  Perform all pre-installation checkst  5           *  Which action do you wish to perform [I]:   1           Press RETURN to start the installation.h  .           Upgrade_Installation: Go to Step 10.  E     __________________________________________________________________  E                                              (continued on next page)3  F     2-34 Installation Procedure: New, Upgrade and Architecture Support L  N      I             Installation Procedure: New, Upgrade and Architecture SupporthI                              2.2 Adding or Upgrading Architecture Supportp    H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support_________________________________________  I         Step__Action_____________________________________________________s  ?         9     New_Installation: Supply the location of OA$DATA_ F               SHARE:A1CONFIG.DAT, the ALL-IN-1 configuration file, for:               ALL-IN-1 Version 3.2 on the existing system.  U                   You have chosen an architecture only installation.  To continue youd  [                   must specify the location of the existing ALL-IN-1 system's configurationl  R                   file (A1CONFIG.DAT).  The installation will read A1CONFIG.DAT to  2                   determine file target locations.  T               * Please give the directory location of A1CONFIG.DAT: disk:[directory]  F               Enter the location of the ALL-IN-1 configuration file inD               the format, disk:[directory]. You must always use this:               format to specify the location of this file.  D               The installation script uses the configuration file to               define logicals.  I               %A1-I-DEFLOG, Running A1V32START.COM to define the logicals_G               -A1-I-DEFLOG, for your existing ALL-IN-1 V3.2 VAX system.   :                Defining language independent logical names  6                Defining ENGLISH language logical names  D               Where possible, the VAX architecture-only installationC               matches the configuration of ALL-IN-1 that is alreadyn>               installed on the Alpha system. The informationalE               messages that are displayed will depend on the existinga               configuration.  I         _________________________________________________________________   B         10    Confirm that a license PAK is registered and loaded.  X               * Does this product have an authorization key registered and loaded [YES]?  '               Press RETURN to continue._  .               New_Installation: Go to Step 12.  I                                                  (continued on next page)o  I        Installation Procedure: New, Upgrade and Architecture Support 2-35            A     Installation Procedure: New, Upgrade and Architecture Support 0     2.2 Adding or Upgrading Architecture Support    D     Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureE     __________________Support________________________________________n  E     Step__Action_____________________________________________________   E     _________________________________________________________________   E     11    Upgrade_Installation: Confirm that you want to purge files.   K           * Do you want to purge files replaced by this installation [YES]?-  #           Press RETURN to continue.r  E     _________________________________________________________________l  @     12    Indicate whether you want to integrate DATATRIEVE with           ALL-IN-1.2  U             DATATRIEVE can be integrated into ALL-IN-1.  On VAX systems with Deferred   S             image activation enabled the DATATRIEVE image will be deferred.  If you   O             use the standard DATATRIEVE image SYS$SHARE:DTRSHR.EXE then you can   U             select to dynamically activate DATATRIEVE.  You will still be able to usef  T             DATATRIEVE within ALL-IN-1, but you will avoid any performance impact of  @             having it physically linked with the ALL-IN-1 image.  C           * Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]?e  B           Press RETURN if you do not want to integrate DATATRIEVE.  >           Enter Y if you want to integrate DATATRIEVE. You areB           prompted to supply the name of the DATATRIEVE image that>           you want to link with. If you are using the standardB           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.  E     _________________________________________________________________S  E                                              (continued on next page)   F     2-36 Installation Procedure: New, Upgrade and Architecture Support n         I             Installation Procedure: New, Upgrade and Architecture Support_I                              2.2 Adding or Upgrading Architecture Support     H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support________________________________________e  I         Step__Action_____________________________________________________s  B         13    System checking for existing ALL-IN-1 configuration.  @               The informational message depends on your existing)               configuration, for example:a  $                  During your ALL-IN-:               1 installation on Alpha you chose to install7                  ALL-IN-1 with WPS-PLUS, therefore WPS- )               PLUS will also be installedg@                  during this VAX architecture only installation.  I         _________________________________________________________________   <         14    Indicate whether you want to incorporate ACMS.  C               If you wish to interface with ACMS, answer YES to the "               following questions.  Q                   If you wish to interface with ACMS, answer YES to the followingp                     questions.                     NOTE:A  =                     o ACMS must be installed before ALL-IN-1.i  T                     o If you answer YES and the relevant ACMS files are present then  X                       the interface to ACMS will be built. If the files are not present,  U                         then you may either continue the installation without linking   T                         with ACMS, or abort the installation to correct the problem.  A               * Do you want to integrate ACMS with ALL-IN-1 [NO]?d  @               Press RETURN if you do not want to integrate ACMS.  I         __________________________________________________________________  I                                                  (continued on next page)   I        Installation Procedure: New, Upgrade and Architecture Support 2-37            A     Installation Procedure: New, Upgrade and Architecture Support 0     2.2 Adding or Upgrading Architecture Support    D     Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureE     __________________Support________________________________________t  E     Step__Action_____________________________________________________p  >     15    System checking for existing ALL-IN-1 configuration.  <           The informational message depends on your existing%           configuration, for example:h  8              ALL-IN-1 on the Alpha is linked as a MULTI-           LANGUAGE system,D              therefore ALL-IN-1 on this VAX will also be linked as a#              MULTI-LANGUAGE system.L  E     _________________________________________________________________w  E     16    Specify the greatest number of simultaneous ALL-IN-1 users.   D           * What will be the greatest number of simultaneous ALL-IN-           1 users:  ?           Upgrade_Installation: A default value is given. Pressa.           RETURN to accept this default value.  B           New_Installation: Specify the maximum number of ALL-IN-1A           users that you expect at any one time. The installationcC           procedure uses this entry to check that system parametersaD           are large enough to support your intended number of users.  E     _________________________________________________________________c  E                                              (continued on next page)t                        F     2-38 Installation Procedure: New, Upgrade and Architecture Support    t      I             Installation Procedure: New, Upgrade and Architecture Support I                              2.2 Adding or Upgrading Architecture Support_    H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support________________________________________N  I         Step__Action_____________________________________________________o  >         17    Message Router checks for upgrade installations.  F               This part of the installation procedure is determined byF               the answers that you gave during the installation on theH               other system. In this example script, the Alpha system wasI               configured to use a remote Message Router on this VAX node.bF               The level of Mail directory support set up for the Alpha"               system is also used.  B               %A1-I-MDCHK, Performing Mail and Directory checks...  R               %A1-I-REMMR, Your ALL-IN-1 system running on the Alpha is configured  F               -A1-I-REMMR, to use a Remote Message Router on this nodeP               %A1-I-LOCMR, Therefore this VAX ALL-IN-1 system will be configured  8               -A1-I-LOCMR, to use a local Message Router  M               %A1-I-DIROPP, Your Alpha ALL-IN-1 system is configured to use at  N               -A1-I-DIROPP, Mail Directory Service. This VAX architecture only  \               -A1-I-DIROPP, installation will use the same Message Router Directory Service.                 %A1-I-I               UPDATEDDS, As this is an update you will not be asked for a @               -A1-I-UPDATEDDS, Message Router Directory password               .                .e               .a  D               The installation procedure also checks for CDA supportH               software. If it is not found, you are asked if you want toI               continue without CDA support or whether you want to install1H               the appropriate software. Following the instruction in the"               installation script.  I               Software support for Group Conferencing is also checked. IfNH               the appropriate version of DEC Notes is not installed, you3               are given instructions on what to do.   I                                                  (continued on next page)   I        Installation Procedure: New, Upgrade and Architecture Support 2-39     _      A     Installation Procedure: New, Upgrade and Architecture Support 0     2.2 Adding or Upgrading Architecture Support    D     Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureE     __________________Support________________________________________i  E     Step__Action_____________________________________________________   E     _________________________________________________________________o  @     18    Indicate if you want client applications to connect to1           ALL-IN-1 using TCP/IP network protocol.   A           You are only asked the following question if DEC TCP/IP.=           Services (UCX) or other TCP/IP network sofware that 3           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 ServerD           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-L'           1 File Cabinet Server [7373]:   C           Enter a different TCP/IP port number for each server. The B           port numbers can be in the range 1024 to 65535. You mustA           use the default values if you plan to use the TeamLinksgE           client software. The installation procedure checks that thepD           UCX$IPC_SHR.EXE image is installed. If it is not, you must,           install it after the installation.  E     __________________________________________________________________       19    System checking.  E           The installation procedure checks system parameters, quotas            and identifiers.  E     _________________________________________________________________E  E                                              (continued on next page)     F     2-40 Installation Procedure: New, Upgrade and Architecture Support    I      I             Installation Procedure: New, Upgrade and Architecture Support I                              2.2 Adding or Upgrading Architecture Support     H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support_________________________________________  I         Step__Action______________________________________________________  &         20    Enter the language code.  L               * Enter language code for this installation (2 characters): US  B               Enter the two-letter language code for your languageE               component. See the  ALL-IN-1 Installation: Language and 7               Market Supplement supplied with your kit._  I         _________________________________________________________________r  %         21    Enter the dialect code.   D               Your language kit may also contain one or more dialectF               components. Enter the dialect code that you want to use.  B               %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesetsD               %VMSINSTAL-I-RESTORE, Restoring product save set B ...  S                   If you wish to install a dialectal variation of ENGLISH language,   V                   enter the code for the dialect component you wish to use.  If you do  P                   not wish to install a dialectal variation of ENGLISH language,  7                   then accept the answer of NO_DIALECT.   U               * Enter dialect code for this installation (5 characters) [NO_DIALECT]:u  I         _________________________________________________________________   $         22    Enter the market code.  J               * Enter market code for this installation (2 characters): US  H               Enter the two-letter market code for the installation. SeeI               the  ALL-IN-1 Installation: Language and Market Supplement.n  I         __________________________________________________________________  I                                                  (continued on next page)x  I        Installation Procedure: New, Upgrade and Architecture Support 2-41p t  n      A     Installation Procedure: New, Upgrade and Architecture Supportt0     2.2 Adding or Upgrading Architecture Support    D     Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureE     __________________Support________________________________________u  E     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-a           1 account [ALLIN1]:i  ,           The account details are displayed.  E     _________________________________________________________________l  >     24    Confirm that the details of the account are correct.  J           * Are all the specified account's characteristics correct [YES]?  2           Press RETURN if the details are correct.  E     _________________________________________________________________   <     25    Run the IVP (Installation Verification Procedure).  D           * Do you want to run the IVP after the installation [YES]?  E     ______Press_RETURN_to_run_the_IVP._______________________________t  A           All the installation questions have now been completed.u  (     2.3 Automatic Postinstallation Tasks  7           The installation procedure performs automatic E           postinstallation tasks, for example, converting data files.r  D           If a problem occurs during the postinstallation phase, see           Chapter 4.  5           The following tasks are done automatically:e  A           o  Deassigns old ALL-IN-1 logicals and logicals created $              during the installation  @           o  Runs the ALL-IN-1 startup procedure, A1V32START.COM  E           o  Compiles, installs and sets protections on the followingn4              form libraries and their site versions:                o  OAFORM                o  MEMRES                o  OAN$FORMS   F     2-42 Installation Procedure: New, Upgrade and Architecture Support w  p      I             Installation Procedure: New, Upgrade and Architecture SupporteI                                      2.3 Automatic Postinstallation Tasksu    .               o  Installs message symbol files                 o  Compiles TXLs  H               o  For upgrade installations, the following data files are                  upgraded:                     o  A1CONFIG.DAT                    o  PROFILE.DATo  (                  o  SM_ACCOUNT_TYPES.DAT  #                  o  SM_POLICIES.DATn                    o  FORMAT.DAT  )         2.4 Manual Postinstallation Tasks   F               There are some manual tasks that you must complete after.               the installation. See Chapter 5.                                                I        Installation Procedure: New, Upgrade and Architecture Support 2-43     6                    I                                                                         3eI         _________________________________________________________________p  I                              Installation Procedure: Additional Languagese    F               This chapter describes the installation of an additional@               language on an ALL-IN-1 Version 3.2 system that is3               configured as a multilanguage system.r  F                 __________________ Before You Start __________________  F                 Do not start the installation until you have completed:                 the system preparation tasks in Chapter 1.  F                 ______________________________________________________  H               During the installation procedure a number of cautions andH               general informational messages are displayed. Read all the+               displayed messages carefully.n  A               Each question in the installation is marked with annC               asterisk (*) at the beginning of the line. If you are_G               unsure how to answer a question enter a question mark (?)n               for Help._  F                 ________________________ Note ________________________  ?                 If the installation fails, you must restart the <                 installation from the beginning. To stop the8                 installation at any point, press CTRL/Y.  F                 ______________________________________________________  @               If you are installing a new additional language orI               upgrading an existing additional language, see Section 3.1.y  I               If you are installing or upgrading architecture support fory6               an additional language, see Section 3.2.      I                          Installation Procedure: Additional Languages 3-1e e  s      0     Installation Procedure: Additional LanguagesD     3.1 Installation Procedure for Additional Language Installations    D     3.1 Installation Procedure for Additional Language Installations  C           Follow the steps in Table 3-1 to install a new additional->           language or upgrade an existing additional language.  A           There are minor differences in the display depending oneA           whether the installation is being run on a VAX or AlphaD           system.d  @           The example script shows the addition of BRITISH as anE           additional language on an ALL-IN-1 Version 3.2 Alpha system 7           that is configured as a multilanguage system.a  C           Depending on your distribution media, you may be prompted B           to change the tape or cartridge during the installation.                                                            4     3-2 Installation Procedure: Additional Languages           I                              Installation Procedure: Additional Languages I          3.1 Installation Procedure for Additional Language Installations     I         Table_3-1_Installation_Procedure_for_An_Additional_Language______   I         Step__Action_____________________________________________________   H         1     Create a log file for the installation. Digital recommendsC               that you keep a record of the installation in case ofuF               problems. You can keep a log by using either a hard copyE               terminal or a log file. To keep a record in a log file,_               enter:  (               $  SET HOST 0/LOG=filename  F               where filename is the name of the log file. The log fileF               is created in the directory where you enter the command.B               If you do not specify a filename, the file is calledF               SETHOST.LOG. The installation log file will be about 200               blocks.e  E               If you are running console management software, you canfC               use this to record the installation. See your console ?               management documentation for further information.U  I         _________________________________________________________________o  A         2     Load and mount the media that contains the languagem               software kit.   I         _________________________________________________________________e  E         3     Invoke the VMSINSTAL procedure from the SYSTEM account.S  +               Enter the following commands:   &               $ SET DEFAULT SYS$UPDATE*               $ @VMSINSTAL A1LUS032 device  A               To use an alternate working device (AWD), enter thec&               following command lines:  &               $ SET DEFAULT SYS$UPDATE;               $ @VMSINSTAL A1LUS032 device OPTIONS AWD=diski  @               device is the device on which you have mounted theE               distribution media. You can use a physical or a logicaleG               device name but do not use logical device names beginning_H               with A1$, OA$, or OA1$. A1LUS032 is the product identifierG               and disk is the location of the alternate working device.   I                                                  (continued on next page)   I                          Installation Procedure: Additional Languages 3-3  0  s      0     Installation Procedure: Additional LanguagesD     3.1 Installation Procedure for Additional Language Installations    >     Table 3-1 (Cont.) Installation Procedure for An AdditionalE     __________________Language_______________________________________i  E     Step__Action______________________________________________________  E     __________________________________________________________________  $     4     Verify your system backup.  E            OpenVMS Alpha Software Product Installation Procedure V6.1g  %           It is 14-FEB-1996 at 21:27.t  9           Enter a question mark (?) at any time for help.fH           * Are you satisfied with the backup of your system disk [YES]?  #           Press RETURN to continue.p  E     __________________________________________________________________  &     5     Load the distribution media.  C           Enter the product identifier, A1LUS032, at the prompt and E           then enter Y to confirm that the media is correctly mountedh%           and you are ready to start.   H           Enter the products to be processed from the first distribution             volume set:E           * Products: A1LUS032>           * Enter installation options you wish to use (none):<           Please mount the first volume of the set on device           * Are you ready? Y  E     _________________________________________________________________c  E                                              (continued on next page)n                4     3-4 Installation Procedure: Additional Languages l  i      I                              Installation Procedure: Additional Languages_I          3.1 Installation Procedure for Additional Language Installations     B         Table 3-1 (Cont.) Installation Procedure for An AdditionalI         __________________Language_______________________________________   I         Step__Action_____________________________________________________   G         6     Enter the number for the type of installation you want to                do.   <                   This is a LOCAL ALL-IN-1 V3.2 LANGUAGE kit  M                   The current ALL-IN-1 image identification is ALL-IN-1 V3.2.   W                   Using the LANGUAGE-only ALL-IN-1 V3.2 kit, the following installationp  )                   types can be performed:-  D                   (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 W                   (4)  Add, Upgrade or Update Alpha architecture specific components of   D                        an existing ALL-IN-1 V3.2 additional language  C                   (RL) Register licenses for pre-requisite software   @               * Which installation do you wish to perform [1]: 1  F               Enter 1 to install a new additional ALL-IN-1 Version 3.2               language.p  I         _________________________________________________________________   >         7     Confirm that you want to start the installation.  Y                   The installation procedure allows you to perform the following actions:e  0                   (I)   Perform the installation;                   (PC)  Perform all pre-installation checksV  8               * Which action do you wish to perform [I]:  5               Press RETURN to start the installation.u  I         _________________________________________________________________m  I                                                  (continued on next page)f  I                          Installation Procedure: Additional Languages 3-5e           0     Installation Procedure: Additional LanguagesD     3.1 Installation Procedure for Additional Language Installations    >     Table 3-1 (Cont.) Installation Procedure for An AdditionalE     __________________Language_______________________________________C  E     Step__Action_____________________________________________________r  D     8     Supply information about optional software as appropriate.  I              During your first language installation you chose to installd  I              ALL-IN-1 without DATATRIEVE, therefore this tool will NOT bea  >              available from your ALL-IN-1 additional language.  K              During your first language installation you chose to integrate   P              WPS-PLUS, therefore you be be able to use WPS-PLUS as an additional  ;              editor from your ALL-IN-1 additional language.   S              This kit contains a library of Encapsulated PostScript(R) graphics andR  S              PostScript(R) Page Overlay samples specific to the language component.E  <           * 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.h  E     _________________________________________________________________t  E     9     Configuration Checking. The message that you see depends on ;           your primary language configuration, for example:   G            During your first language installation you chose to install_  K            ALL-IN-1 without ACMS, therefore this tool will NOT be availabler  2            from your ALL-IN-1 additional language.  E     _________________________________________________________________   E                                              (continued on next page)t    4     3-6 Installation Procedure: Additional Languages r  o      I                              Installation Procedure: Additional Languages I          3.1 Installation Procedure for Additional Language Installations     B         Table 3-1 (Cont.) Installation Procedure for An AdditionalI         __________________Language_______________________________________s  I         Step__Action_____________________________________________________e  +         10    Select a default date format.   W                   ALL-IN-1 allows you to select a default date format for each languagek  W                   you have installed. This will become the default ALL-IN-1 date formato  V                   for each user (on a per language basis.) This may be changed by each  X                   user through the Set Working Conditions option on the User Setup Menu.  7                       Alphanumeric Date    Numeric Daten  K                       1   DD-MMM-YYYY      MM/DD/YY      (Standard Default)   3                       2   DD-MMM-YYYY      DD/MM/YY_3                       3   DD-MMM-YYYY      YY/MM/DD 3                       4   YYYY-MMM-DD      MM/DD/YYn3                       5   YYYY-MMM-DD      DD/MM/YY 3                       6   YYYY-MMM-DD      YY/MM/DDeE                       7   ***** Reserved (Means system default) *****.I                       8   DD-MM-YYYY       DD/MM/YY      (Numeric format)aI                       9   MM-DD-YYYY       MM/DD/YY      (Numeric format)   5               * Which date format do you require [1]:a  H               Press RETURN to use the default format or enter the number7               for the date format that you want to use.a  A               See the  ALL-IN-1 Installation: Language and Marketi=               Supplement for more details about date formats.d  @               The installation procedure now does system checks.  I         _________________________________________________________________s  &         11    Enter the language code.  L               * Enter language code for this installation (2 characters): US  B               Enter the two-letter language code for your languageE               component. See the  ALL-IN-1 Installation: Language ando7               Market Supplement supplied with your kit.   I                                                  (continued on next page)i  I                          Installation Procedure: Additional Languages 3-7d :  d      0     Installation Procedure: Additional LanguagesD     3.1 Installation Procedure for Additional Language Installations    >     Table 3-1 (Cont.) Installation Procedure for An AdditionalE     __________________Language_______________________________________   E     Step__Action_____________________________________________________   E     _________________________________________________________________   !     12    Enter the dialect code.   >           %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets@           %VMSINSTAL-I-RESTORE, Restoring product save set B ...  O               If you wish to install a dialectal variation of ENGLISH language,e  R               enter the code for the dialect component you wish to use.  If you do  L               not wish to install a dialectal variation of ENGLISH language,  3               then accept the answer of NO_DIALECT.t  W           * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GBe  >           Enter the dialect code that you want to use. In thisB           example, US_GB is the BRITISH dialect component. See the@           ALL-IN-1 Installation: Language and Market Supplement.  E     _________________________________________________________________o  @     13    Confirm that the License PAK is registered and loaded.  T           * Does this product have an authorization key registered and loaded [YES]?  #           Press RETURN to continue.c  E     _________________________________________________________________   ?     14    Specify the device for the additional language files.   .           * Which device will hold the ALL-IN-#           1 BRITISH language files:l              Enter the device name.  E     _________________________________________________________________T  E                                              (continued on next page)u  4     3-8 Installation Procedure: Additional Languages h  c      I                              Installation Procedure: Additional LanguageseI          3.1 Installation Procedure for Additional Language Installationsn    B         Table 3-1 (Cont.) Installation Procedure for An AdditionalI         __________________Language_______________________________________n  I         Step__Action_____________________________________________________g  C         15    Enter the OpenVMS username for the ALL-IN-1 manager'sg               account.  A               * What is the existing VMS username for the ALL-IN-C!               1 account [ALLIN1]:   7               The details of the account are displayed._  I         __________________________________________________________________  ;         16    Confirm that the account details are correct._  N               * Are all the specified account's characteristics correct [YES]?  B               Press RETURN to confirm that the account details are               correct.  I         _________________________________________________________________   I         17    Specify the top-level directory for the ALL-IN-1 additional                language files.   Z               * Enter ALL-IN-1 top-level directory required for all BRITISH language files  [                                                                                  [BRITISH]:   I         _________________________________________________________________   @         18    Run the IVP (Installation Verification Procedure).  H               * Do you want to run the IVP after the installation [YES]?  I         ______Press_RETURN_to_run_the_IVP._______________________________o  E               All the installation questions have now been completed.   H               The installation procedure does automatic postinstallationD               tasks. If a problem occurs during the postinstallationF               phase, see Chapter 4. For manual postinstallation tasks,               see Chapter 5.  C               If you are installing on a VMScluster and want to add I               additional architecture support for the additional languaget7               that you have installed, see Section 3.2.o  I                          Installation Procedure: Additional Languages 3-9_ _  _      0     Installation Procedure: Additional LanguagesB     3.2 Installing Architecture Support for an Additional Language    B     3.2 Installing Architecture Support for an Additional Language  <           Before you start the installation, you must do the           following:  8           o  Make a note of the location of the ALL-IN-1?              configuration file, OA$DATA_SHARE:A1CONFIG.DAT, onoC              the VAX system. You will be asked for this information %              during the installation.-  B           o  Run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP, to9              check for logicals containing SYS$SYSDEVICE.N  C           From the ALL-IN-1 manager's account on the node where youdE           have already installed ALL-IN-1, run the script, OA$LIB:SM_ "           CHECK_SYS$SYSDEVICE.SCP:  #           $ SET HOST 0/LOG=filenameg           $ ALLIN1/NOINITi9           Enter CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP   B           If references to SYS$DEVICE are found, a warning messageC           is displayed. You must remove the references as they will_A           refer to different devices on a VAX system and an Alpha B           system. If the references are not corrected, data may be           lost on your system.  C           Follow the steps in Table 3-2 to add architecture support D           for an additional language that you have already installedA           on a different architecture in the same VMScluster. Theh?           example script shows the addition of VAX architecturelA           support for ALL-IN-1 BRITISH as an additional language._C           BRITISH is already installed as an additional language on 1           an Alpha system in the same VMScluster.   A     Table 3-2 Installation Procedure for Addition of Architecture E     __________Support_for_an_Additional_Language_____________________o  E     Step__Action_____________________________________________________n  +     1 to  Follow Steps 1 to 5 in Table 3-1._     5_  E     _________________________________________________________________n  E                                              (continued on next page)y  5     3-10 Installation Procedure: Additional Languages            I                              Installation Procedure: Additional LanguagesAI            3.2 Installing Architecture Support for an Additional Language     @         Table 3-2 (Cont.) Installation Procedure for Addition ofI         __________________Architecture_Support_for_an_Additional_Language   I         Step__Action_____________________________________________________   G         6     Enter the number for the type of installation you want to                do.a  W                   Using the LANGUAGE-only ALL-IN-1 V3.2 kit, the following installationa  )                   types can be performed:   D                   (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 D                   (4)  Add, upgrade, or update VAX components for an:                          ALL-IN-1 V3.2 additional language  C                   (RL) Register licenses for pre-requisite software   @               * Which installation do you wish to perform [1]: 4  E               Enter 4 to add VAX architecture support for an existingT7               ALL-IN-1 Version 3.2 additional language.l  I         __________________________________________________________________  >         7     Confirm that you want to start the installation.  Y                   The installation procedure allows you to perform the following actions:   0                   (I)   Perform the installation;                   (PC)  Perform all pre-installation checksi  8               * Which action do you wish to perform [I]:  5               Press RETURN to start the installation._  I         __________________________________________________________________  I                                                  (continued on next page)         I                         Installation Procedure: Additional Languages 3-11  a         0     Installation Procedure: Additional LanguagesB     3.2 Installing Architecture Support for an Additional Language    <     Table 3-2 (Cont.) Installation Procedure for Addition ofE     __________________Architecture_Support_for_an_Additional_Languageg  E     Step__Action_____________________________________________________n  ?     8     Enter the location of OA$DATA_SHARE:A1CONFIG.DAT, theY@           ALL-IN-1 configuration file, for the existing ALL-IN-1           Version 3.2 system.   P               You have chosen an architecture only installation. To continue you  W               must specify the location of the existing ALL-IN-1 system's configuration   N               file (A1CONFIG.DAT).  The installation will read A1CONFIG.DAT to  .               determine file target locations.  O           * Please give the directory location of A1CONFIG.DAT [OA$DATA_SHARE]:M  :           Enter the location of A1CONFIG.DAT in the format@           disk:[directory]. You must always specify the location3           of the configuration file in this format.              %A1LUS-I-a?           DEFLOG, Running A1V32START.COM to define the logicals-4           -A1LUS-I-DEFLOG, for your existing ALL-IN-           1 V3.2 Alpha system.           .d           .            .l  E     __________________________________________________________________  3     9     Indicate whether you want to purge files.   K           * Do you want to purge files replaced by this installation [YES]?i  &           Press RETURN to purge files.  E     _________________________________________________________________   E                                              (continued on next page)a      5     3-12 Installation Procedure: Additional Languages            I                              Installation Procedure: Additional LanguagesaI            3.2 Installing Architecture Support for an Additional Languagen    @         Table 3-2 (Cont.) Installation Procedure for Addition ofI         __________________Architecture_Support_for_an_Additional_Languageo  I         Step__Action______________________________________________________  %         10    Configuration checking._  G               You may be asked questions depending on the configuration_.               of ALL-IN-1 on the Alpha system.  J                This VAX architecture only installation will where possible  G                match the configuration of ALL-IN-1 already installed onc                 the Alpha system.K                During your first language installation you chose to install   K                ALL-IN-1 without DATATRIEVE, therefore this tool will NOT be   @                available from your ALL-IN-1 additional language.  N                During your ALL-IN-1 installation on Alpha you chose to install  P                ALL-IN-1 with WPS-PLUS, therefore WPS-PLUS will also be installed  >                during this VAX architecture only installation.  K                During your first language installation you chose to installs  O                ALL-IN-1 without ACMS, therefore this tool will NOT be available_  6                from your ALL-IN-1 additional language.  I         _________________________________________________________________a  I                                                  (continued on next page)N                    I                         Installation Procedure: Additional Languages 3-13     p      0     Installation Procedure: Additional LanguagesB     3.2 Installing Architecture Support for an Additional Language    <     Table 3-2 (Cont.) Installation Procedure for Addition ofE     __________________Architecture_Support_for_an_Additional_Language   E     Step__Action_____________________________________________________   '     11    Select a default date format.s  S               ALL-IN-1 allows you to select a default date format for each languagee  S               you have installed. This will become the default ALL-IN-1 date format   R               for each user (on a per language basis.) This may be changed by each  T               user through the Set Working Conditions option on the User Setup Menu.  3                   Alphanumeric Date    Numeric Date5  G                   1   DD-MMM-YYYY      MM/DD/YY      (Standard Default)c  /                   2   DD-MMM-YYYY      DD/MM/YYu/                   3   DD-MMM-YYYY      YY/MM/DD /                   4   YYYY-MMM-DD      MM/DD/YYc/                   5   YYYY-MMM-DD      DD/MM/YY_/                   6   YYYY-MMM-DD      YY/MM/DD A                   7   ***** Reserved (Means system default) ***** E                   8   DD-MM-YYYY       DD/MM/YY      (Numeric format)YE                   9   MM-DD-YYYY       MM/DD/YY      (Numeric format)a  1           * Which date format do you require [1]:_  E     _________________________________________________________________f  "     12    Enter the language code.  H           * 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.  E     __________________________________________________________________  E                                              (continued on next page)     5     3-14 Installation Procedure: Additional Languagesa t         I                              Installation Procedure: Additional Languages_I            3.2 Installing Architecture Support for an Additional Language     @         Table 3-2 (Cont.) Installation Procedure for Addition ofI         __________________Architecture_Support_for_an_Additional_Languagen  I         Step__Action_____________________________________________________   %         13    Enter the dialect code.   B               %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesetsD               %VMSINSTAL-I-RESTORE, Restoring product save set B ...  S                   If you wish to install a dialectal variation of ENGLISH language,o  V                   enter the code for the dialect component you wish to use.  If you do  P                   not wish to install a dialectal variation of ENGLISH language,  7                   then accept the answer of NO_DIALECT.   [               * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GB   A               In this example, US_GB is the BRITISH dialect code.   I         _________________________________________________________________s  D         14    Confirm that the License PAK is registered and loaded.  X               * Does this product have an authorization key registered and loaded [YES]?  '               Press RETURN to continue.S  I         _________________________________________________________________o  D         15    Enter the name of the OpenVMS username of the ALL-IN-1                manager's account.  A               * What is the existing VMS username for the ALL-IN-I!               1 account [ALLIN1]:S  0               The account details are displayed.  I         _________________________________________________________________t  ;         16    Confirm that the account details are correct.e  N               * Are all the specified account's characteristics correct [YES]?  A               Press RETURN if the account information is correct.   I         _________________________________________________________________n  I                                                  (continued on next page)t  I                         Installation Procedure: Additional Languages 3-15e d  o      0     Installation Procedure: Additional LanguagesB     3.2 Installing Architecture Support for an Additional Language    <     Table 3-2 (Cont.) Installation Procedure for Addition ofE     __________________Architecture_Support_for_an_Additional_Languaget  E     Step__Action______________________________________________________  <     17    Run the IVP (Installation Verification Procedure).  D           * Do you want to run the IVP after the installation [YES]?  E     ______Press_RETURN_to_run_the_IVP.________________________________  A           All the installation questions have now been completed.e  D           The installation procedure will do postinstallation tasks.;           For manual postinstallation tasks, see Chapter 5.r                                                            5     3-16 Installation Procedure: Additional Languages     l                    I                                                                         4pI         __________________________________________________________________  I                                           Installation Errors and Failuret    D               This chapter deals with various error messages you mayD               see while installing ALL-IN-1 Version 3.2 or while theF               Installation Verification Procedures (IVPs) are running,E               and explains what to do if the installation or the IVPsU               fail.a  C               While the installation is running it displays variousnD               informational messages. It may also display warning orG               error messages. Read all the messages displayed, and take *               whatever action they advise.  =         4.1 Common Error Message That Does Not Require Actiond  A               The following error message may be ignored if it isi0               displayed during the installation:  "               %DELETE-W-SEARCHFAIL  D               This error occurs randomly. A file is always specifiedC               in the error message, but the file has been correctlyt               provided.   .         4.2 Common Errors Which Require Action  D               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.i  A               o  Quotas necessary for successful installation are_                  insufficient.  H               o  System parameter values for successful installation are                  insufficient.  >               o  The OpenVMS help library is currently in use.  I                                       Installation Errors and Failure 4-1  A  t      *     4.2 Common Errors Which Require Action      A           o  SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLBtC              are not present. These files are removed if you tailor_              OpenVMS._  C           For descriptions of the error messages generated by these ?           conditions, see the OpenVMS books on system messages,-A           recovery procedures, and OpenVMS software installation.eA           If you are notified that any of these conditions exist, D           you should take the appropriate action as described in the           message.  '     4.3 Failure During Postinstallationw  C              ________________________ Note ________________________n  8              When the installation procedure reaches the>              postinstallation phase, the main installation has=              completed. If the postinstallation tasks fail, aaB              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.   C              You must rerun A1$POSTINSTALL.COM on the node on which_1              you originally ran the installation.n  C              ______________________________________________________p  5           The procedure used to execute the automatic D           postinstallation tasks is written during the installation.;           Its content depends on the installation type, and A           conditions specific to your system. The command file issB           called A1$POSTINSTALL.COM, and it is provided to OA$LIB_           language.s  =           If any postinstallation tasks fail, messages to aidlE           investigation are displayed. If the installation has failed B           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 commandaA              procedure using only the commands for the tasks that               have failed.s  '     4-2 Installation Errors and Failuree l  n      I                                       4.3 Failure During PostinstallationN      B               When the installation has completed, there are stillE               some manual postinstallation tasks to be performed. See                Chapter 5.  H               After the automatic postinstallation tasks have completed,2               the installation procedure displays:  :               Installation of A1 V3.2 completed at <hh:mm>  A               Enter EXIT, or press CTRL/Z to exit from VMSINSTAL.l  =               Note that the installation procedure deletes or E               changes entries in the process symbol tables during theaI               installation. Therefore, if you are going to continue usingrG               the system manager's account, you must log out and log ind               again.            4.4 Installation Failure  C               If the installation fails before the postinstallation 8               phase, the following message is displayed:  Q               %VMSINSTAL-E-INSFAIL, The installation of ALL-IN-1 V3.2 has failed.   F                 ________________________ Note ________________________  ?                 If the installation fails, you must restart thel0                 installation from the beginning.  F                 ______________________________________________________  =         4.4.1 Failure of Upgrade Installations in Safety Mode_  I               If your installation is being performed in Safety mode, you1G               need take no further action if the failure happens before                the message:  ;               Files will now be moved to target directories   C               If the installation fails after this message, restore A               your original system from a backup. You can then gohE               back to using the original system, or you can start thet!               installation again.Y    I                                       Installation Errors and Failure 4-3     /           4.4 Installation Failure      =     4.4.2 Failure of Upgrade Installations in Non-Safety Modec  E           If your installation is being performed in non-safety mode, B           restore your original system from a backup. You can thenD           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,A           identifiers and directories that have been created, and_'           start the installation again.2  4     4.4.4 Failure Due to Insufficient Dynamic Memory  >           An installation on an Alpha system may fail with the"           following error message:  8           %SYSTEM-F-INSFMEM, insufficient dynamic memory  A           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  9           %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not foundg  H           %OA-E-BADLIB, Error occurred while precompiling THIS_IS_A.TEST           form library  A           You can ignore these messages as they are part of testse(           that are performed by the IVP.  B           If any other error messages occur during the IVP, do the           following:  B           1. Check the log of the installation for any errors that3              may have occurred during installation.e  >           2. Check the file ALLIN1_IVP.LOG. This file does not?              contain the results of the IVP, but the results ofhA              invoking ALL-IN-1 when running the IVP. This file ist=              in the directory where you run the installation.   '     4-4 Installation Errors and Failure  l         I                                   4.5 Error Messages when Running the IVP_      B               3. Check for any errors in the following procedures.  =                  o  During the execution of the startup file,e/                     SYS$STARTUP:A1V32START.COM:   -                        Creating logical names_  9                  o  Automatic postinstallation procedures5  -                        Installing image files >                        Compiling and installing form libraries  @               4. Make sure that the ALL-IN-1 TXL is compiled andI                  installed successfully, and recompile it if you received E                  any error messages when the postinstallation command                   file was run.  H               5. Check that you have not run out of quota on the disk(s)F                  containing the OA$SHAREnnnn directories (refer to the6                  manual describing OpenVMS utilities).  I               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.d  A                  o  The IVP user directory points to the disk anddD                     subdirectory that you specified for the ALL-IN-13                     manager's account. For example:i  -                     a1device:[ALLIN1.IVPUSER]_  C                     where a1device is the device that you specified_,                     during the installation.  C                  o  The ALL-IN-1 account, IVP, is accessed from the 7                     ALL-IN-1 manager's OpenVMS account.l  D               7. Run ALL-IN-1 and try to use those areas that failedF                  during the IVP to find more information on the error.  >                  Log in to the ALL-IN-1 manager's IVP account:  '                  $ ALLIN1 /USERNAME=IVPs  C                  Manually execute each IVP test as described in the +                  ALL-IN-1 Management Guide.o  I                                       Installation Errors and Failure 4-5            +     4.5 Error Messages when Running the IVPp      C              ________________________ Note _________________________  @              The IVP runs in the language context of the currentA              optional language being installed and also tests the '              international base system.   =              Most IVPs are designed to exercise and test ALL-l=              IN-1 at a level which is normally customization- C              independent. However, if you have customized the Phone B              Directory subsystem of ALL-IN-1, the display graphicsC              (IDG) procedure may fail. This is a demonstration testp@              used to exercise the terminal graphics as a typical              application.   C              ______________________________________________________a       4.6 IVP Failuree  A           If the IVP fails, the following messages are displayed:i  A           The A1 V3.2 Installation Verification Procedure failed.   ?           %VMSINSTAL-E-IVPFAIL, The IVP for A1 V3.2 has failed.m                                            '     4-6 Installation Errors and Failureb    r                    I                                                                         5 I         _________________________________________________________________o  I                                                    Postinstallation Taskse    B               This chapter describes the tasks that you must do toE               complete the setup of ALL-IN-1. Some of these tasks aretH               optional, or only apply to particular types of systems, or               configurations.l  C               There are a number of additional setup tasks that theVC               ALL-IN-1 manager must do to set up the users' working B               environment before ALL-IN-1 is used. These tasks areD               explained in detail in the  ALL-IN-1 Management Guide.  F               You must run postinstallation from the node on which you#               are running ALL-IN-1.   6         5.1 Checklist of Manual Postinstallation Tasks  @               Table 5-1 lists the manual postinstallation tasks.  I               Table_5-1_Postinstallation_Tasks___________________________s  +                                     Type oftI               Task__________________Installation_____Information_________p  D               Start ALL-IN-1        Full, upgrade    See Section 5.21               on all nodes in       or additional_0               a VMScluster system   architecture  I               ___________________________________________________________i  @               Create or modify      Full or upgrade  Section 5.3                the ALL-IN-1 site-               specific startup               procedure   I               ___________________________________________________________I  I                                                  (continued on next page)   I                                                Postinstallation Tasks 5-1m    u      2     5.1 Checklist of Manual Postinstallation Tasks      E           Table_5-1_(Cont.)_Postinstallation_Tasks____________________  '                                 Type of E           Task__________________Installation_____Information_________n  <           Modify the OpenVMS    Full, upgrade    Section 5.4-           site-specific         or additional ,           startup procedure     architecture  E           ___________________________________________________________o  <           Replace the           Full, upgrade    Section 5.5-           DCLTABLES on          or additionale,           VMScluster systems    architecture  E           ___________________________________________________________f  <           Delete files that     Upgrade or       Section 5.6*           are no longer         additional(           required              language  E           ___________________________________________________________o  <           Install any missing   Full, upgrade    Section 5.7-           images                or additionaln,                                 architecture  E           ___________________________________________________________   A           Recompile form        Upgrade          See Section 5.8. B           libraries, including                   This section alsoE           application or                         lists form librariessB           site-specific form                     that are compiledD           libraries                              automatically afterB                                                  the installation.  E           ___________________________________________________________   E                                              (continued on next page)                  5-2 Postinstallation Tasks c  i      I                            5.1 Checklist of Manual Postinstallation Tasksi      I               Table_5-1_(Cont.)_Postinstallation_Tasks___________________t  +                                     Type ofoI               Task__________________Installation_____Information_________   A               Migrate your          Upgrade of       Section 5.10 0               customizations:       a customized*               o  Run the CART       system                    resolutionm                  procedure                 o  Restore                  customizations_!                  to modified data_                  files                 o  Replace                   customized help                  files                  o  Delete obsolete                  files  I               ___________________________________________________________   @               Migrate SITELINK31    Upgrade,         Section 5.9.               using Customization   additional0               Management            language and0                                     architecture+                                     supports  I               ___________________________________________________________   A               Link ALL-IN-1 to      Upgrades of      Section 5.11 .               include code-level    code-level.               customizations        customized/                                     systems and .                                     additional3                                     architecture ifh2                                     also installed  I               ___________________________________________________________l  I                                                  (continued on next page)   I                                                Postinstallation Tasks 5-3     t      2     5.1 Checklist of Manual Postinstallation Tasks      E           Table_5-1_(Cont.)_Postinstallation_Tasks___________________t  '                                 Type of E           Task__________________Installation_____Information_________t  =           Check entries in the  Upgrade          Section 5.12T           file, RIGHTSLIST.DAT  E           ___________________________________________________________e  8           Set up remote mail    Full or upgrade  For newC                                 Note that        installations with D                                 local mail       the MAILbus 400 MTAC                                 is already set   and Digital X.500,AB                                 up after the     see Section 5.13.  C                                 installation.    For upgrade or new C                                                  installations with D                                                  Message Router, see>                                                  Section 5.14.  E           ___________________________________________________________   =           Convert WPS-PLUS for  Migrating users  Section 5.15 -           VMS files             from WPS-PLUSn*                                 for VMS to(                                 ALL-IN-1  E           ___________________________________________________________L  >           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  E           ___________________________________________________________t  =           Install the File      Full or upgrade  Section 5.17            Cabinet Server           distributed license,           if required.  E           ___________________________________________________________e  E                                              (continued on next page)        5-4 Postinstallation Tasks N  T      I                            5.1 Checklist of Manual Postinstallation Tasksy      I               Table_5-1_(Cont.)_Postinstallation_Tasks___________________n  +                                     Type of I               Task__________________Installation_____Information_________   A               Move the CDA DOC_     If CDA$LIBRARY   Section 5.18 2               STYLE files to a      does not exist2               suitable location,    on your system               if necessary  I               ___________________________________________________________i  A               Update the Facility   If DECtrace      Section 5.19p.               Definition for        is already1               DECtrace              installed and 3                                     you want to use &                                     it  I               ___________________________________________________________   I               Set up the user       Full or upgrade   ALL-IN-1 Management1:               environment                            Guide  I               ___________________________________________________________o  G               Tune the File         Full or upgrade   ALL-IN-1 Managingi<               Cabinet Servers                        Servers  I               ___________________________________________________________   C               Decide how many mail  Full or upgrade   ALL-IN-1 Mail E               Sender and Fetcher                     Management Guide I               processes_to_run___________________________________________   >         5.2 Start ALL-IN-1 on all Nodes in a VMScluster System  I               The ALL-IN-1 startup procedure, SYS$STARTUP:A1V32START.COM,lH               is supplied with ALL-IN-1 and is executed automatically onG               the node used for the installation, once the installation )               has completed successfully.   G               If you are running ALL-IN-1 on a VMScluster you must alsonH               run SYS$STARTUP:A1V32START.COM on each node in the clusterC               in order to start ALL-IN-1. If you run A1V32START.COM @               manually from the DCL prompt, you must include theC               location of the ALL-IN-1 configuration file, OA$DATA_ F               SHARE:A1CONFIG.DAT. OpenVMS prompts you for the locationH               of this file if you do not specify it on the command line.  I                                                Postinstallation Tasks 5-5a n  r      :     5.2 Start ALL-IN-1 on all Nodes in a VMScluster System      @           If you are creating new shared directories from withinD           ALL-IN-1, you must define new system logical names on eachD           node in the cluster. For further information about runningB           ALL-IN-1 on a VMScluster, see Chapter 5 in the  ALL-IN-1           Management Guide.   E     5.3 Create or Modify the Site-specific ALL-IN-1 Startup Procedure   D           To modify the ALL-IN-1 startup command procedure, you mustE           create a site-specific command procedure. The site-specific E           startup command procedure will be automatically executed by E           the ALL-IN-1 startup command procedure when it is executed.n  E           You can create the following types of site-specific commandp           procedures:   D           o  A language-independent startup command procedure calledC              A1V32_SITE_START.COM. Create this startup procedure in %              OA$SITE_BUILD_SHARE_IND.   D           o  A language-specific startup command procedure, OA$SITE_?              language_START.COM, for each language installed in A              a multilanguage ALL-IN-1 system. Create this startup 0              procedure in OA$SITE_BUILD_LLV_IND.  6              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.d  D              You can specify the directory for your default language=              by using the logical name OA$SITE_BUILD_LLV_IND.i  C           If you are upgrading and you have a site-specific startup A           command procedure that you want to keep, rename it from 7           A1V31_SITE_START.COM to A1V32_SITE_START.COM._  E           Check that the contents of the command file are still valid C           and required for ALL-IN-1 Version 3.2. Note the following            changes:  ?           o  The OA$MTI_AREA logical is now defined in A1CONFIGf  >           o  The OA$A1_CLUSTER_NODE is now defined in A1CONFIG       5-6 Postinstallation Tasks _  _      I                              5.4 Edit the Site-specific Startup Proceduret      4         5.4 Edit the Site-specific Startup Procedure  B               When you run A1V32START.COM from the DCL prompt, youE               must include the location of the ALL-IN-1 configuration C               file, OA$DATA_SHARE:A1CONFIG.DAT. OpenVMS prompts you D               for the location of this file if you do not specify itH               on the command line. When you include the ALL-IN-1 startupG               procedure in the OpenVMS site startup procedure, you must_<               specify the location of the A1CONFIG.DAT file:  4               $ @SYS$STARTUP:A1V32START.COM location  F               where location is the location of A1CONFIG.DAT, which is               specified as:_  +               device:[directory.DATA_SHARE]u  F               device is the device that you specified for the ALL-IN-1F               data files and directory is the top-level directory that8               you specified for the ALL-IN-1 data files.  G               To find the location of OA$DATA_SHARE:A1CONFIG.DAT, referr'               to your installation log.e  F                 ________________________ Note ________________________  ?                 However you choose to set up your site-specific @                 startup procedures, you must ensure that all theA                 ALL-IN-1 prerequisite products are started beforeiF                 ALL-IN-1. This includes messaging software, DEC Notes,D                 and DECwindows/Motif if you are using CDA converters                 with ALL-IN-1.  F                 ______________________________________________________  F         5.4.1 Installations With Digital X.500 and the MAILbus 400 MTA  F               If you have installed a new ALL-IN-1 system with DigitalA               X.500 and the MAILbus 400 MTA, you must ensure thatnD               the prerequisite messaging products are started beforeI               ALL-IN-1. Make sure that the following 3 files are executed %               in the following order:R  +               1. SYS$STARTUP:OSAK$START.COM   3               2. SYS$STARTUP:DXD$COMMON_STARTUP.COM   3               3. SYS$STARTUP:MTA$COMMON_STARTUP.COMo  I                                                Postinstallation Tasks 5-7     s      0     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 C           ensure that the Message Router software is started before            ALL-IN-1.u  D           As an example, Table 5-2 describes how to edit the OpenVMSD           site-specific startup file to include the ALL-IN-1 startup?           procedure after an upgrade installation from ALL-IN-1_A           Version 3.1. This ensures that the ALL-IN-1 environmentI5           is reestablished following a system reboot.   E           Table_5-2_Editing_the_OpenVMS_Site-specific_Startup_File___u             InstallationE           Type_____________Do_the_Following__________________________d  ,           Full and         To edit the file:-           addition         1. Find the lines:            of second :           architecture     $ @SYS$MANAGER:STARTNET.COM andK           (unless you are  $ @SYS$MANAGER:MB$CONTROL START=(DDS,TS,...,ER)1   B           using common     2. After these lines, add the following#           startup files)      line:   B                            $ @SYS$STARTUP:A1V32START.COM location2  E           ___________________________________________________________   *           Upgrade from     Change the lineB           ALL-IN-1         $ @SYS$STARTUP:A1V31START.COM location2           Version 3.1      to            and additionB           of second        $ @SYS$STARTUP:A1V32START.COM location2             architecture           (unless you arep           using common           startup files)  E           [1]The_exact_command_line_will_depend_on_which_Message_____   (           Router components are running.C           [2]location is the location of the ALL-IN-1 configurationg+           file, OA$DATA_SHARE:A1CONFIG.DAT.   E                                              (continued on next page)t       5-8 Postinstallation Tasks           I                              5.4 Edit the Site-specific Startup Procedure       I               Table 5-2 (Cont.) Editing the OpenVMS Site-specific Startup I               __________________File______________________________________                 InstallationI               Type_____________Do_the_Following__________________________   I               ___________________________________________________________   G               If you are       Add the following entry before the entry_B               running a        for the ALL-IN-1 startup procedure:M               remote Message   $ @SYS$STARTUP:DDS$STARTUP.COM node nodenumberlA               Router and       where node is the name of the nodemD               using the        on which the remote Message Router isH               Message Router   installed and nodenumber is the DirectoryH               Directory        Service node number of the remote Message+               Service          Router node.   I               ___________________________________________________________.  4         5.5 Replace the DCLTABLES on Cluster Systems  C               If you installed ALL-IN-1 Version 3.2 on a VMSclustertD               system, you must replace the DCLTABLES on any nodes inG               the cluster where you are not installing ALL-IN-1 VersionyG               3.2. Enter the following commands on each of these nodes:_                 $ INSTALL A               INSTALL> REPLACE SYS$SHARE:DCLTABLES /OPEN /SHARE -n#               _INSTALL> /HEADER_RES                INSTALL> EXITD  A               You need only do this once after you have installedaG               ALL-IN-1 Version 3.2. The ALL-IN-1 installation procedure I               replaces the tables automatically for the node on which you_2               are installing ALL-IN-1 Version 3.2.  4         5.6 Delete Files That Are No Longer Required  E               If you have upgraded or updated ALL-IN-1, various files F               remain in the SYSTEM directories which you can delete to6               increase your disk space. The files are:  5               o  For an ALL-IN-1 Version 3.1 upgrade:_  0                     SYS$HELP:A1031.RELEASE_NOTES5                     SYS$HELP:A1Llang031.RELEASE_NOTES E                     SYS$HELP:A1Cmarket031.RELEASE_NOTES, if available_.                     SYS$STARTUP:A1V31START.COM  I                                                Postinstallation Tasks 5-9     i      0     5.6 Delete Files That Are No Longer Required      -                 SYS$HELP:TLC025.RELEASE_NOTES_       5.7 Install Missing Images  E           On startup, if any error messages are displayed relating tod@           images that are not installed, use the Install utility>           to install those images before executing the startupA           procedure again. Images that you may need to install in A           this way are those referenced by optional products thatlC           you have integrated with the ALL-IN-1 image. For example,lC           the following command installs the image RDBSHR, which isa'           referenced by VAX DATATRIEVE:c             $ INSTALL A           INSTALL> ADD SYS$SHARE:RDBSHR /OPEN /HEADER_RES /SHARED   B           For more details of the Install Utility, see the OpenVMS           documentation.        5.8 Recompile Form Libraries  E           If you are upgrading from ALL-IN-1 Version 3.1 and you have B           compiled form libraries on your old system which are notB           replaced by the upgrade, you may see the following error           message:  7           Obsolete form library <name> please recompile   >           If you see this message, recompile the form library.  C              ________________________ Note ________________________l  ?              You must also compile application or site-specifico7              form libraries, and your own applications.   C              ______________________________________________________r  B           The following form libraries are compiled automatically:             o  OAFORM1             o  SITEOAFORMe             o  MEMRES              o  SITEMEMRESL             o  OAN$FORMS             o  SITEOAN$FORMS       5-10 Postinstallation Tasks  t         I                                              5.8 Recompile Form Librariest      D               If you have added code or manual procedures to compileD               other form libraries, you must recompile them manuallyG               after the installation. Use the Precompile a form librarycI               (PCF) option from the System Customization Management (CSZ)a7               menu. See the  ALL-IN-1 Management Guide.t  =         5.9 Migrate SITELINK31 Using Customization Management   =               The SITELINK32.COM file is under the control of F               Customization Management. It is important that you checkF               that any customizations to SITELINK31.COM are compatible"               with SITELINK32.COM.  D               Use Customization Management to edit the base templateG               version of the site link file, SITELINK32.COM, to includesE               your previous SITELINK31.COM from OA$SITE_BUILD. Review F               your customizations to SITELINK32.COM and then move yourD               customized version to LIVE. Review your customizationsD               to make sure they are compatible with ALL-IN-1 VersionG               3.2. Do not relink ALL-IN-1 until you have done this. See                Section 5.10.   D               It is recommended that you do the following to relink:  /               $ SET DEFAULT OA$BUILD_SHARE_ARCHi"               $ @OA$BUILD:A1LNKDRV  :         5.10 Migrating Your Customizations After Upgrading  D               Immediately after installing ALL-IN-1 Version 3.2, andH               before allowing your users to access ALL-IN-1, review your3               customizations to mandatory elements.   F               You can rerun the CART after installing ALL-IN-1 Version@               3.2 using the Check Conflicts (CC) option from theF               Application Maintenance menu. When you run the CART fromD               within ALL-IN-1, it does not produce the site elementsG               report. It does produce the full and summary reports, andnH               the CART resolution procedure, which are all stored as new3               elements in Customization Management.   B               If you rerun the CART, it does not keep the previousB               CART full and summary reports. To keep them, use theC               Customization Management Copy (CO) option to save thenG               elements with another name in the same area, for example, B               copy CM_CART_SUMMARY_V32$PRIMARY to CM_CART_SUMMARY_  I                                               Postinstallation Tasks 5-11s d  r      6     5.10 Migrating Your Customizations After Upgrading      >           V32$PRIMARY_19FEB. All of the elements that you have4           already processed will have status code F.  (           To review your customizations:  E           1. From the Customization Management (CM) subsystem, select D              each element marked as a mandatory change and print the=              differences between it and the new base element.   $           2. Review the differences.  C              Note where new functionality has been added or changeseB              made. Note any symbol changes. Use the information inC              your upgrade plan to make the changes necessary to get_!              your system running._  B           3. Test your customizations and, if they work correctly,7              move the elements back into the live area.   D           4. Before allowing your users back onto the system, reviewD              your customizations to recommended elements in the same8              way as you reviewed the mandatory elements.  E              If you do not resolve conflicts to recommended elements,lE              users may not have access to your customizations or will B              not have access to the full functionality of ALL-IN-1              Version 3.2.U  E           5. Review conflicts with elements reported with status code E              D, see the  ALL-IN-1 Overview and Planning Guide. StatusuC              code D indicates a customization that calls an elemento>              which has been removed from ALL-IN-1 Version 3.2.  E              If the element that is called by your customized elementNB              has a status code of A, then no customized version ofB              it exists. Your customization will fail if you deleteA              the removed element, as described in Section 5.10.2.AD              Edit the command procedure DELETE_OBSOLETE_FILES.COM soE              that these elements are not deleted. See Section 5.10.2. D              Use Customization Management to create a new customizedC              element to replace the referenced base element that no_3              longer exists in ALL-IN-1 Version 3.2.T  >              Use Customization Management to copy any elementsC              reported with status code A into the development area.NE              When you rerun the CART, these elements will be reported(               with status code H.       5-12 Postinstallation Tasksa t  f      I                        5.10 Migrating Your Customizations After UpgradingY      H               6. You can now allow your users to access ALL-IN-1 VersionF                  3.2. When it is convenient, resolve the conflicts for(                  informational elements.  4         5.10.1 Running the CART Resolution Procedure  G               The CART resolution procedure calls individual scripts to3G               process each status code. The scripts are called CM_CART_p7               SCRIPTn, where n is the CART status code.   G               To run and edit the scripts called by the CART resolution H               procedure, you must have Application Maintainer privilegesB               for the areas where the elements are stored. See theC               ALL-IN-1 Management Guide. To run the CART resolutionnF               procedure use the Execute procedure (EP) option from theA               Application Maintainer's Check Conflicts (CC) menu.   B               To change the way that the CART resolution procedureD               handles elements with a particular status code, do the               following:  C               1. Enter the Customization Management (CM) subsystem._  G               2. Use the Access base element (ABE) option to select the_(                  CART resolution script.  A               3. Copy the script that you want to change into the "                  development area.  @               4. Edit the script using Customization Management.  F               It is not mandatory to use the CART resolution procedureB               to resolve conflicts. If the script does not provideH               appropriate actions to resolve the conflicts at your site,-               then you do not have to use it.e  G               You can use the CART resolution procedure to resolve somecD               of the conflicts reported with an informational statusC               code. You should review the CART resolution procedure E               carefully before running it. Check that your customized.F               elements do not call a removed element, see Section 5.10C               which describes how to resolve conflicts for elementsi*               reported with status code D.    I                                               Postinstallation Tasks 5-13            6     5.10 Migrating Your Customizations After Upgrading      "     5.10.2 Deleting Obsolete Files  E           A command procedure, DELETE_OBSOLETE_FILES.COM, is providedyE           to remove the files that are no longer required by ALL-IN-1s           Version 3.2.  C              ________________________ Note _________________________  @              Do not run this procedure immediately after runningB              the CART resolution procedure. You must always review=              this file before running it. Check that all youreA              customizations are working correctly and ensure that C              your customizations do not call any elements that will *              be deleted by this procedure.  C              ______________________________________________________L  E           You can edit DELETE_OBSOLETE_FILES.COM to stop the deletion_C           of certain files if required, for example, if one of your D           customizations calls an element that has been removed fromC           the base kit and which would otherwise be deleted by thisd           procedure.  A           For example, the suggested resolution for elements with            status code A is to:  D           o  Run the CART resolution procedure to delete the recordsA              for these elements from the Customization Management               databases             o  Run theB              command procedure OA$LIB:DELETE_OBSOLETE_FILES.COM to               delete the elements  D           To run DELETE_OBSOLETE_FILES.COM, enter the following from           DCL:  6           $ @OA$LIB:DELETE_OBSOLETE_FILES.COM language  C           where language is the language of the ALL-IN-1 system. IfLE           you have additional languages installed on your system, you ?           can run this procedure for each additional languages.V           5-14 Postinstallation Tasks  o  l      I                        5.10 Migrating Your Customizations After Upgradingy      5         5.10.3 Restoring Customizations to Data Filesm  C               Read this section if you copied customized data fileso=               according to the instructions in Section 1.8.1.r  I               Throughout this section, the form PROFILE.DAT is used as aneH               example. To restore your modifications to your data files,               do the following:m  I               1. Make a copy of the new base PROFILE.DAT file, preferablya:                  outside the ALL-IN-1 directory structure:  L                  $ COPY OA$DATA:PROFILE.DAT disk:[directory]BASE_PROFILE.DAT  @               2. Make copies of the new base PROFILn forms usingD                  Customization Management. For example, copy them toI                  BASE_PROFILn and modify the named data so that the .FILEtG                  directive specifies the location of the backup copy of8.                  the base format PROFILE file.  %               3. Make the forms live.e  H               4. Use Customization Management to add your customizations?                  to the new base PROFILn forms and PROFILE.FDL.a  7               5. Make the forms and the FDL files live.C  ?               6. Convert PROFILE.DAT to your customized format:-  3                  <OA$CNV_CONVERT BASE_PROFIL,PROFILU  A               7. If it is necessary to recover some data from thelE                  original customized PROFILE.DAT, write a script thatiG                  loops through the CUSTOM_PROFIL dataset and writes theL0                  new data to the PROFIL dataset.                    For example:u  ;                  FOR CUSTOM_PROFIL DO WRITE CHANGE PROFIL - C                  %KEY = .%KEY, additional_field = .additional_field   >         5.10.4 Replacing the Help Modules for Your Application  B               For more information about customizing Help, see the-               Application Programming: Guide.y  >               After the upgrade, copy the ALL-IN-1 Version 3.2<               standard Help libraries, OA$LIB:OAHELP.HLB andE               OA$LIB:SITEHLPSOURCE.HLB from the base area to the live G               area, OA$SITE_LIB_language. Customization Management will F               inform you that the live and development versions of the  I                                               Postinstallation Tasks 5-15            6     5.10 Migrating Your Customizations After Upgrading      E           Help libraries are the same and ask you whether you wish to +           continue. Answer yes to continue.   E           You must recreate your customizations to Help modules using @           Customization Management. Use the Access base elementsC           (ABE) option to get the base version of your Help module. C           Use the Copy (CO) option to copy the customized module to E           the development area where you can make changes to it. WhennB           you save the module ALL-IN-1 formats it and puts it intoC           the appropriate development Help libraries. When you have B           tested the Help, mark it to be moved to the live area so           that it can be used.  ;     5.11 Link ALL-IN-1 to Include Code-level Customizationse  @           ALL-IN-1 Version 3.2 is linked during the installation>           without any customizations you may have made to your?           existing system. Therefore, it is important to relink B           ALL-IN-1 after the installation if you wish to link withE           your customizations when you have checked them. See Chapter .           2 in the  ALL-IN-1 Management Guide.  (     5.12 Check Entries in RIGHTSLIST.DAT  8           OpenVMS usernames used with ALL-IN-1 must have9           corresponding entries with the same name in theu?           RIGHTSLIST.DAT file, so that shared filing and system >           management can operate correctly. After upgrading to?           ALL-IN-1 Version 3.2, run the script OA$LIB:SM_CHECK_ E           PROFILE, which generates a report indicating those accounts 4           which may not conform to this requirement.  >     5.13 Setting up Remote Mail When Using the MAILbus 400 MTA  B           You must complete the set up tasks for Digital X.500 andB           the MAILbus 400 MTA before you can send and receive mailC           using the MAILbus 400 MTA. The setup tasks are covered ingB           the Setting up a New System with the MAILbus 400 MTA and@           Digital X.500 chapter in the  ALL-IN-1 Mail Management           Guide.               5-16 Postinstallation Tasksn r  l      I                     5.14 Setting up Remote Mail When Using Message Router       =         5.14 Setting up Remote Mail When Using Message Routerl  F               After the installation, local mail is already set up. IfE               you want to use Message Router for remote mail, you may F               need to do some or all of the tasks listed in Table 5-3,9               depending on the requirements at your site.   E               The tasks that you must do depend on the type of remoteI*               Message Router which can be:  @               o  Installed on a VAX node in the same VMScluster:  F                  -  With ALL-IN-1 installed on the Message Router node  D                  -  Without ALL-IN-1 installed on the Message Router                     node  @               o  Installed on a VAX node that is not in the same'                  VMScluster as ALL-IN-1   I               Table_5-3_Tasks_for_Setting_up_Remote_Mail_________________d  I               Task_______________________For_Information_See_____________   7               If you are using a remote  Section 5.14.1 #               Message Router serverp"               node, make sure that&               there is a mailbox entry#               on that node for your                ALL-IN-1 mailbox.r  "               You may have already'               done this as part of your $               preinstallation tasks.  7               If you have installed      Section 5.14.2 "               ALL-IN-1 Version 3.2%               on a mixed architecture &               cluster, you must modify&               the mailbox entry on the"               Message Router node.  7               If you are using MRGATE    Section 5.14.3 &               on a remote node, set up$               each node that will be               using MRGATE.h  I                                                  (continued on next page)a  I                                               Postinstallation Tasks 5-17s t         9     5.14 Setting up Remote Mail When Using Message Routerr      E           Table_5-3_(Cont.)_Tasks_for_Setting_up_Remote_Mail_________   E           Task_______________________For_Information_See_____________   B           Set up the remote Mail     Section 5.14.4 if ALL-IN-1 isB           directory                  using a Message Router in theD                                      same VMScluster and ALL-IN-1 isD                                      installed on the Message Router)                                      nodeE  D                                      Section 5.14.4.2 if ALL-IN-1 isC                                      using a Message Router that is B                                      not in the same VMScluster orE                                      ALL-IN-1 is not installed on the 8                                      Message Router node  C                                      If you are using Digital X.500eA                                      after a new ALL-IN-1 VersionoB                                      3.2 installation with Message@                                      Router, you must follow the@                                      instructions for setting upC                                      Digital X.500 in the  ALL-IN-1t;                                      Mail Management Guide.   3           Edit the site-specific     Section 5.14.5C           startup procedure to"           start up the remote MailE           directory._________________________________________________s  (     5.14.1 Create a Mailbox for ALL-IN-1  ?           This section applies when ALL-IN-1 is using a Message A           Router that is not in the same VMScluster. You may havegD           already done this as part of the preinstallation tasks. IfC           you have already created a mailbox, you do not need to doS           it again.   E           Your ALL-IN-1 mailbox for your node (or cluster) requires a :           mailbox entry on the remote Message Router node.             To add a mailbox:              5-18 Postinstallation Tasksi d  e      I                     5.14 Setting up Remote Mail When Using Message Routeri    I               ___________________________________________________________ I               Step_Action________________________________________________u  D               1    Log in to the MBMANAGER account on the node whereE                    Message Router is running, and enter the following_                    command:   )                    $ RUN SYS$SYSTEM:MRMAN   I               ___________________________________________________________n  :               2    Enter the following at the MRM> prompt:  '                    MRM> ADD localnodeA1a?                           /PASSWORD=password /COMPLETE_MESSAGES.U                           /IGNORE_SENDER /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTSs                      where:   C                    o  localnode is the name of the ALL-IN-1 node orfE                       cluster. The name must be unique to the Messageb$                       Router system.  H                    o  password is the ALL-IN-1 mailbox password that youG                       specified during the ALL-IN-1 installation on the $                       remote system.  I                       The password that you specify here must be the sameeH                       as you specified during the ALL-IN-1 installation.B                       If you change the password when creating theH                       mailbox, you must also change it to the same valueG                       in ALL-IN-1 by using the Set operating conditionsaH                       (SOC) option on the Manage Messaging menu. See the5                       ALL-IN-1 Mail Management Guide.p  I               ___________________________________________________________c  C               3    Exit from the Message Router management utility:.  I               _____MRM>_EXIT_____________________________________________o  @               Refer to the Message Router documentation for more*               information about mailboxes.      I                                               Postinstallation Tasks 5-19            9     5.14 Setting up Remote Mail When Using Message Router       5     5.14.2 Modifying the Message Router Mailbox Entryu  A           You must modify the Message Router mailbox entry if youe?           have a mixed-architecture cluster and you are using at>           Message Router in the same cluster. The installationA           procedure creates a mailbox entry on the Message RouterfD           node with the /OWNER=ALLIN1 qualifier. The Alpha node willC           be unable to connect with this mailbox because the /OWNER B           qualifier is on the mailbox. Modify the ALL-IN-1 mailboxC           entry on the Message Router node to remove the qualifier.P              $ RUN SYS$SYSTEM:MBMAN            MRM> MODIFY A1/NOOWNER           MRM> EXITI  =           where A1 is the name of the Message Router mailbox.o  <     5.14.3 Configuring the VMSmail Gateway for Remote Access  B           If you have installed the Message Router VMSmail GatewayB           on one of the nodes in a VMScluster you can set up other4           ALL-IN-1 nodes so that they can access it.  =           On each of the nodes that does not have the gatewayEC           started, define the logical name MRGATE to the following:p             node::MR%   >           where node is the node where the gateway is running.  >           You can also use a VMSmail Gateway on a node in yourC           network, that is remote to your cluster. You need Message3D           Router to be installed on one of the nodes in your clusterC           in order to do this. Make an entry for the remote VMSmail @           Gateway in the mailbox directory of the Message RouterB           Transfer Service on the VAX node in your cluster that is!           running Message Router:   D           1. Log in to the MBMANAGER account on the VAX node in your3              cluster that is running Message Router   *           2. Enter the following commands:  #              $ RUN SYS$SYSTEM:MRMANo3              MRM> ADD MRGATE/REPLACE="MRGATE @node"t  C              where node is the node where the gateway is installed.z       5-20 Postinstallation Taskss l  n      I                     5.14 Setting up Remote Mail When Using Message Router       A               3. Exit from the Message Router management utility:h                    MRM> EXIT  H               See the Message Router documentation for more information.  E         5.14.4 Setting Up the Message Router Directory Service as thes                Mail Directoryt  D               The tasks that you need to do depend on the following:  I               o  If the Message Router node is in the same VMScluster and >                  has ALL-IN-1 installed, see Section 5.14.4.1.  I               o  If the Message Router node is not in the same VMScluster I                  or ALL-IN-1 is not installed on the Message Router node,a&                  see Section 5.14.4.2.  9         5.14.4.1 Message Router is in the Same VMSclusterh  D               Read this section if ALL-IN-1 is installed in the sameD               VMScluster as Message Router and ALL-IN-1 is installedC               on the Message Router node. You can be using the MailsI               directory as either the primary or the secondary directory.sD               If, during the installation, you chose to use the MailH               directory as the primary directory, OA$DDS_PRIME is set toG               2. If, during the installation, you chose to use the Mail G               directory as the secondary directory with ALL-IN-1 as thee?               primary directory, then OA$DDS_PRIME is set to 1.t  B               After installation, the following values are set up:  6               o  A user agent entry name and password.  E                  -  The user agent entry name is OA$node$ALLIN1 for a E                     new or upgrade installation, where node is eitherhE                     the node name or the cluster alias for the system F                     on which you are installing ALL-IN-1. For example,#                     OA$LYNX$ALLIN1.e  G                  -  The user agent entry password is the Mail directoryeF                     password that you entered during the installation.  G               o  A subscriber entry for the ALL-IN-1 manager. The proxy E                  attribute of the subscriber entry is the name of the,G                  local ALL-IN-1 user agent entry (OA$node$ALLIN1). This G                  attribute gives ALL-IN-1 proxy access to the manager's I                  entry, so that ALL-IN-1 can update and access the entry.i  I                                               Postinstallation Tasks 5-21M a  R      9     5.14 Setting up Remote Mail When Using Message Routerh      D           o  UAPASSWRD.DAT which contains the name of the user agentD              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.  9           To set up the Mail directory, do the following:i  E           ___________________________________________________________ E           Step_Action________________________________________________   A           1    Log in to the ALL-IN-1 manager's ALL-IN-1 account:   )                $ ALLIN1 /USERNAME=MANAGER   E           ___________________________________________________________   :           2    Enter the following commands from ALL-IN-1:  $                <GET #ORGNAME=orgname&                <GET #LOCATION=location                  where:o  E                o  orgname is the name of your company or organizationr  8                o  location is the location of your users  D                If area routing is in use at your site, you must also                enter:   %                <GET #AREA="area_code"   D                area_code is the area code for the area that includes                your system.                        5-22 Postinstallation Tasks. S  i      I                     5.14 Setting up Remote Mail When Using Message Routera    I               ____________________________________________________________I               Step_Action________________________________________________S  H                    If you do not know the area code, do the following on+                    the Message Router node: I                    ______________________________________________________ I                    Step_Action___________________________________________   B                    a    Run the MAILbus configuration procedure toE                         display the current Transfer Service settingsh,                         in use at your site:  0                         $ @SYS$MANAGER:MB$CONFIG  C                    b    Display the settings for the Message Router )                         Transfer Service:   $                         MBC> SHOW TS  D                         The area code is displayed, along with other-                         settings, as follows:                                .s                             .                              .l:                         Transfer Service uses area routing,                         Area Code : areacode                               .-                             .                              .   F                         where areacode is the area code in use at your                         site.   A                    3    Enter EXIT, or press CTRL/Z, to exit from_E                         the MAILbus configuration procedure. For more G                         details of this command, see the Message RouteroI                    _____documentation.___________________________________o  I               ___________________________________________________________c  H               3    Update the user agent entry by entering the following                    command:r  ,                    <DO OA$LIB:USERAGENT_POST  I                                               Postinstallation Tasks 5-23            9     5.14 Setting up Remote Mail When Using Message Router     E           ____________________________________________________________E           Step_Action________________________________________________   1                This DO script does the following:_  1                o  Updates the user agent entry inRE                   OA$DATA_SHARE:UAPASSWRD.DAT with the Mail directorygE                   identity obtained from the user agent object in the !                   Mail directory.   B                   The ALL-IN-1 user agent is now available for all                   users.  ?                o  Sets the Mail directory field in the ALL-IN-1D1                   manager's account details to Y.=  D                o  Copies details from the ALL-IN-1 manager's profileD                   entry, which was created during installation, into@                   the manager's Mail directory subscriber entry.  E                o  Copies the manager's Mail directory identifier from B                   the subscriber entry into the manager's ALL-IN-1"                   account details.  ?                o  Updates the ALL-IN-1 user agent object in theIA                   Mail directory with the values you supplied for 1                   organization name and location.e  D                o  Creates a mail address (OA$DDS_AREA_ROUTE) that isC                   used for all the Mail directory subscribers ownedoA                   by the user agent ( ALL-IN-1). The mail addresscC                   comprises the name of the ALL-IN-1 Message RoutergC                   mailbox (OA$MTI_MAILBX), and the name of the node B                   or cluster (OA$PRIMARY_NODE) running the Message@                   Router to be used by ALL-IN-1. If area routingB                   is in use at your site, the network address also<                   includes the area code that you specified.  E           ___________________________________________________________e  ?           4    Restart ALL-IN-1 on all nodes in the VMScluster.o  E           ___________________________________________________________            5-24 Postinstallation Tasks            I                     5.14 Setting up Remote Mail When Using Message Routerf    I               ___________________________________________________________ I               Step_Action________________________________________________n  @               5    If you are performing an upgrade or an updateE                    installation in which you have elected to use MailaC                    directory addressing for the first time, see theaG                    ALL-IN-1 Mail Management Guide for information about/I               _____how_to_populate_the_Mail_directory.___________________   =         5.14.4.2 Message Router is not in the Same VMSclusterr  H               Read this section if the Message Router that you are usingD               is not in the same VMScluster as ALL-IN-1, or it is inF               the same VMScluster but ALL-IN-1 is not installed on the"               Message Router Node.  ,               You must create the following:  6               o  A user agent entry name and password.  G               o  A subscriber entry for the ALL-IN-1 manager. The proxycE                  attribute of the subscriber entry is the name of thenG                  local ALL-IN-1 user agent entry (OA$node$ALLIN1). This G                  attribute gives ALL-IN-1 proxy access to the manager's I                  entry, so that ALL-IN-1 can update and access the entry.a  E               o  Update the OA$DATA_SHARE:UAPASSWRD.DAT file with thes<                  name of the user agent object and password.  F               You must do some tasks on the remote Message Router node2               and some tasks on the ALL-IN-1 node.  I               ___________________________________________________________ I               Step_Action________________________________________________   C               1    On the remote Message Router node, log in to the C                    MBMANAGER account and run the MAILbus ManagementS"                    Utility, MBMAN:  )                    $ RUN SYS$SYSTEM:MBMANw  I               ___________________________________________________________l        I                                               Postinstallation Tasks 5-25i M  a      9     5.14 Setting up Remote Mail When Using Message Routera    E           ___________________________________________________________eE           Step_Action________________________________________________i  B           2    Create the user agent object that ALL-IN-1 will useE                to access the Mail directory and add the object to theh                Mail directory:  E                MBMAN> BUILD DDS UA /NAME="uaname"/PASSWORD="password" .                MBMAN> ADD DDS BUILT_OBJECT/LOG                  where:h  B                o  uaname is the name of the user agent object. The@                   name is in the form OA$node$ALLIN1, where nodeB                   is either the node name or the cluster alias forA                   the system on which you are setting up the MailL                   directory.  D                o  password is the password that ALL-IN-1 will use toC                   access the user agent object. It must not be more -                   than eight characters long.r  E           ___________________________________________________________u                                                   5-26 Postinstallation TasksS I  i      I                     5.14 Setting up Remote Mail When Using Message Router     I               ___________________________________________________________ I               Step_Action________________________________________________   @               3    Create and add a subscriber entry to the Mail6                    directory for the ALL-IN-1 manager:  @                    MBMAN>BUILD DDS SUBSCRIBER /SURNAME="MANAGER"=                    MBMAN>BUILD DDS SUBSCRIBER /PROXY="uaname"e=                    MBMAN>BUILD DDS SUBSCRIBER /SUBID="uaname"t1                    MBMAN>ADD DDS BUILT_OBJECT/LOGs                    MBMAN>EXIT                       where:L  C                    o  MANAGER is the name of the ALL-IN-1 manager's D                       ALL-IN-1 account and must be entered as shown.:                       Do not enter any other account name.  F                    o  uaname is the name of the user agent object thatE                       you specified, for example, OA$nodename$ALLIN1.e  D                    o  /PROXY="uaname" grants the local ALL-IN-1 userD                       agent proxy access to the manager's subscriberD                       entry. This enables the ALL-IN-1 user agent toI                       access and update the manager's subscriber entry ong,                       behalf of the manager.  G                    o  /SUBID="uaname" identifies the ALL-IN-1 manager's H                       subscriber entry to ALL-IN-1, as there can be many-                       entries called MANAGER.u  I               ___________________________________________________________   G               4    On the ALL-IN-1 node (VAX or Alpha), do all the next_F                    steps from the ALL-IN-1 manager's ALL-IN-1 account:  C                    Enter the following commands to create temporary D                    symbols required by the script which you will run$                    in the next step:  (                    <GET #ORGNAME=orgname*                    <GET #LOCATION=location                      where:r  I                    o  orgname is the name of your company or organizationC  <                    o  location is the location of your users  I                                               Postinstallation Tasks 5-27i i  h      9     5.14 Setting up Remote Mail When Using Message Routeru    E           ___________________________________________________________EE           Step_Action________________________________________________h  D                If area routing is in use at your site, you must also                enter:   %                <GET #AREA="area_code"   D                area_code is the area code for the area that includes                your system._  D                If you do not know the area code, do the following on'                the Message Router node: E                ______________________________________________________ E                Step_Action____________________________________________  >                a    Run the MAILbus configuration procedure toA                     display the current Transfer Service settings (                     in use at your site:  ,                     $ @SYS$MANAGER:MB$CONFIG  ?                b    Display the settings for the Message Router %                     Transfer Service:                         MBC> SHOW TS  @                     The area code is displayed, along with other)                     settings, as follows:                            .B                         .                          .d6                     Transfer Service uses area routing(                     Area Code : areacode                           .                          .                          .   B                     where areacode is the area code in use at your                     site.   =                c    Enter EXIT, or press CTRL/Z, to exit from A                     the MAILbus configuration procedure. For moreoC                     details of this command, see the Message Router E                _____documentation.___________________________________        5-28 Postinstallation Tasksf r  o      I                     5.14 Setting up Remote Mail When Using Message RouterM    I               ____________________________________________________________I               Step_Action_________________________________________________  I               ___________________________________________________________e  ,               5    Run the following script:  ,                    <DO OA$LIB:USERAGENT_POST  H                    A mail message will be sent to the ALL-IN-1 manager'sG                    account which contains detailed instructions on what                     to do next.  I               ____________________________________________________________  H               6    For details of populating the Mail Directory, see theI               _____ALL-IN-1_Mail_Management_Guide._______________________   H         5.14.5 Remote Message Router Directory Service Startup Procedure  D               On each ALL-IN-1 node that will be using a remote MailF               directory, add the following entry to your site-specificI               startup procedure before the entry for the ALL-IN-1 startupM               procedure:  <               $ @SYS$STARTUP:DDS$STARTUP.COM node nodenumber  D               where node is the name of the node on which the remoteI               Message Router is installed and nodenumber is the Directory 5               Service node number of the remote node.r  I               To find the Directory Service node number, do the following )               on the Message Router node:   $               $ RUN SYS$SYSTEM:MBMAN+               MBMAN> SHOW DDS NODE nodenamee  D               where nodename is the name of the Message Router node.  D               See Section 5.4 for more information about editing the)               site-specific startup file.e  C         5.15 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1r  I               Read this section if users have been using WPS-PLUS for VMSnI               and want to use the documents created with WPS-PLUS for VMSh#               from within ALL-IN-1.   I                                               Postinstallation Tasks 5-29  c  t      ?     5.15 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1e      C              ________________________ Note ________________________e  <              To use the converted documents in ALL-IN-1, the/              WPS-PLUS editor must be installed._  C              ______________________________________________________a  B           To convert WPS-PLUS for VMS documents, do the following:  ?           1. Give each ALL-IN-1 user who wants to convert theirs@              WPS-PLUS for VMS documents the ALL-IN-1 DCL and CMD?              privileges. See the  ALL-IN-1 Management Guide for_A              details of setting these privileges. If you normally ?              restrict this access, reset it after conversion isn              complete.  E           2. Check that the directory containing the WPS-PLUS for VMStC              File Cabinet exists by entering the following command:o  B              $ DIRECTORY /PROTECTION disk:[username.WPSPLUS...]*.*  B              where disk is the name of the user's OpenVMS disk and-              username is the OpenVMS username_  E              This command lists all the files in the WPS-PLUS for VMS +              account belonging to the user.e  @           3. Make sure that all files have the following minimum              protection:                (S:RWD,O:RWE,,)  0           4. Run ALL-IN-1 from the user account.  A           5. Enter WP to display the Word and Document Processingw              menu.  )           6. Enter the following command:                 <DO OA$LIB:WPCOPY  6           7. Enter the full directory specification of9              the WPS-PLUS for VMS directory (for example, =              DISK1:[HUDSON.WPSPLUS]) at the following prompt:i  0              Enter directory of old File Cabinet  C           8. Enter the full directory specification of the ALL-IN-1u>              directory (for example, DISK1:[HUDSON.A1]) at the              following prompt:       5-30 Postinstallation Taskse e  g      H              5.15 Convert WPS-PLUS for VMS Documents For Use in ALL-IN-1      4                  Enter directory of new File Cabinet  F                 ________________________ Note ________________________  A                 You cannot have the ALL-IN-1 and WPS-PLUS for VMS_C                 versions of the DOCDB.DAT files in the same OpenVMSe                 directory.  F                 ______________________________________________________  E               9. Enter A to copy all documents at once, or C to check ;                  before each file is copied, at the prompt:_  H                  Copy All documents at once or Check each one <A/C> <A>:  I                  When conversion is complete, ALL-IN-1 returns you to thei3                  Word and Document Processing menu._  I               10.To convert the User-Defined Process [.UDP] files, do the_                  following:_  H                  a. From the Word and Document Processing menu, enter $.  :                     ALL-IN-1 places you in the subprocess.  0                  b. Enter the following command:  E                     $ COPY /LOG [username.WPSPLUS.UDP]*.UDP [.UDP]*.*   B                     where username is the user's top-level OpenVMSG                     directory, as recorded in the SYS$SYSTEM:SYSUAF.DAT                      file.   I                  c. When the copying is finished, press EXIT to return toc                     ALL-IN-1.   -               11.Reset the users' privileges.i  -         5.16 WPS-PLUS Login Command Procedure   G               During the ALL-IN-1 Version 3.2 installation procedure, acF               login command procedure, A1WPSPLUS_LOGIN.COM, is createdB               in SYS$MANAGER. Add this to the system login commandB               procedure, SYS$SYLOGIN, if you want all users to runG               with these qualifiers. Alternately, you can make the file G               available to users to put into their own LOGIN.COM files.   I                                               Postinstallation Tasks 5-31  t  A      <     5.17 Install the File Cabinet Server Distributed License      <     5.17 Install the File Cabinet Server Distributed License  D           The File Cabinet server handles access to the File CabinetC           over the network. If you want to give remote users accessDA           to your node, you need the A1-DIST-SHR license. The A1-SB           DIST-SHR license enables the File Cabinet server on yourD           system to accept connections from a File Cabinet server onD           a remote system. You also need this license if you want toB           use the ALL-IN-1 Web Interface to make documents in your:           File Cabinet available to users of Web Browsers.  B           Use the License Management Facility (LMF) to install theE           A1-DIST-SHR license. For information about LMF, see the LMFnB           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   D           If CDA$LIBRARY does not exist on your system, the CDA DOC_C           STYLE files are installed in OA$LIB_SHARE. Move the files !           to a suitable location.   7     5.19 Update the Facility Definition to Use DECtracea  <           During the installation of ALL-IN-1 Version 3.2, a>           Facility Definition file for DECtrace is provided toC           SYS$SHARE:EPC$FACILITY.TLB. If you install DECtrace after_?           you have installed ALL-IN-1 Version 3.2, the Facility)0           Definition is picked up automatically.                                     5-32 Postinstallation Taskst t  f      I                       5.19 Update the Facility Definition to Use DECtracee      F               If DECtrace is already installed on your system, and youF               wish to use it for collecting information about ALL-IN-1E               Version 3.2, you must update the Facility Definition ase               follows:  M               $ LIBRARY/TEXT/EXTRACT=OAV32/OUTPUT=EPC$A1V32-FAC-DEF.EPC$DEF - 3                          SYS$SHARE:EPC$FACILITY.TLBtK               $ COLLECT INSERT DEFINITION EPC$A1V32-FAC-DEF.EPC$DEF/REPLACEg  F                 ________________________ Note ________________________  E                 The Facility Definition File has not been updated for_C                 ALL-IN-1 Version 3.2. It is the same as provided ins%                 ALL-IN-1 Version 3.1.r  F                 ______________________________________________________                                                          I                                               Postinstallation Tasks 5-33o w                       I                                                                         A_I         __________________________________________________________________  I                                   ALL-IN-1 Version 3.2 Distribution Mediar    G               The ALL-IN-1 kit is provided on its own CD-ROM or as part G               of the CD-ROM Consolidated Software Distribution. For VAXRF               upgrades, the kit is also available on magnetic tape andI               TK50. The same ALL-IN-1 savesets are provided on all media.S  @               A separate CD-ROM is provided for the ALL-IN-1 Web                Interface product.  A         A.1 CD-ROM Distribution Kits (VAX or Alpha Installations)   B               The notes in this section apply to both the ALL-IN-1A               Version 3.2 CD-ROM and to the Consolidated Software D               Distribution CD-ROM. On the Compact Disc (CD-ROM), theC               base kit is in the directory A1032.KIT. The printableeI               documentation is in a directory called A1032.DOCUMENTATION.p  F               For the ALL-IN-1 Version 3.2 CD-ROM, the online versionsE               of the documentation for Bookreader are provided in thet"               DECW$BOOK directory.  G               For each language, there is a directory called A1lang032,aG               where lang is the 2-letter code for the ALL-IN-1 languageMF               that you are installing. See the  ALL-IN-1 Installation:G               Language and Market Supplement for a list of savesets for_;               your language, market and dialect components._  I               The base component savesets in the A1032.KIT directory are:                   I                               ALL-IN-1 Version 3.2 Distribution Media A-1  A  i      =     A.1 CD-ROM Distribution Kits (VAX or Alpha Installations)a                 A1032.Aa$           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.Jr           A1032.Kt           A1032.L   C           The documentation directory, A1032.DOCUMENTATION contains E           ASCII (.TXT) and PostScript (.PS) versions of the following            documentation:  D           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.PSo  E           o  The Read Me First letter, READ_ME_FIRST.TXT and READ_ME_               FIRST.PSt  B           o  The Software Product Description (SPD), A1032_SPD.TXT              and A1032_SPD.PS.  E           The CDROM also contains the following software in their own            directories:  9           o  VAX Forms Management System (FMS) (VAX only)o  )           o  DEC FMS Version (Alpha only)e  &           o  Message Router (VAX only)  6           o  Message Router VMSmail Gateway (VAX only)             o  DEC Notes        0     A-2  ALL-IN-1 Version 3.2 Distribution Media e  t      I                            A.2 Magnetic Tape and TK50 Kits (VAX Upgrades)       6         A.2 Magnetic Tape and TK50 Kits (VAX Upgrades)  G               The ALL-IN-1 files are supplied on 6250 bpi magnetic tapeoI               or TK50 cartridge for VAX upgrades. There are two pieces of H               media, one for the base component and one for the languageE               and market components. The media is labeled as follows:o                  o  Base component:  2                  ALL-IN-1 V3.2 BASE BIN media_type&                  BASE COMPONENT A110321                  (c) 1996 Digital Equipment Corp.o  D                  media_type is the code for your distribution media.  A                  This media contains the following base componentt                  savesets:                    A1032.A+                  A1032.B (used by VAX only) -                  A1032.C (used by Alpha only)u+                  A1032.D (used by VAX only),-                  A1032.E (used by Alpha only)m+                  A1032.F (used by VAX only)r-                  A1032.G (used by Alpha only) +                  A1032.H (used by VAX only)g-                  A1032.I (used by Alpha only)I                  A1032.J                  A1032.K                  A1032.L  /               o  Language and market component:t  6                  ALL-IN-1 V3.2 language BIN media_type.                  LANGUAGE/MKT COMPONENT A120321                  (c) 1996 Digital Equipment Corp.M  I                  where media_type is the code for your distribution media F                  and language is the name of the language that you are2                  installing, for example, ENGLISH.  E                  This media contains the language, market and dialecteI                  (if provided) savesets. See your  ALL-IN-1 Installation:rI                  Language and Market Supplement. VAX FMS is also includede2                  on the language and market media.  I                               ALL-IN-1 Version 3.2 Distribution Media A-3C n         2     A.2 Magnetic Tape and TK50 Kits (VAX Upgrades)      @           Each saveset has a unique kit revision identifier, for           example:             A1032BASEA.REV_nnn.i  ?           All other software provided with your ALL-IN-1 kit isS%           supplied on separate tapes.                                                                             0     A-4  ALL-IN-1 Version 3.2 Distribution Media _                       I                                                                         BoI         _________________________________________________________________   I                                ALL-IN-1 Version 3.2 Files and Directories     A               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 KitC  F               For a complete list of all ALL-IN-1 directories and fileH               names when the installation is complete, use the following-               command for each ALL-IN-1 area:r  2               $ DIR/SEC[a1dir...]*.*/out=a1dir.TXT  G               where a1dir is the top level directory name for each area '               (for example ALLIN1.DIR).-  D               The list of files is a useful reference if you need toA               resolve any problems with file protections or ACLs..  7         B.2 Files Installed in Non-ALL-IN-1 Directoriesi  F               The following list shows the files that are installed inD               directories other than the ALL-IN-1 directories. WhereF               language is included in a file name, this is the name of;               the installed language, for example, ENGLISH.s  $               o  SYS$COMMON:[SYSLIB]  !                  OA$AIDA_CSHR.EXE "                  OA$AIDA_DSSHR.EXE#                  OA$AIDA_GCMSHR.EXE #                  OA$AIDA_RTLSHR.EXES#                  OA$AIDA_SECSHR.EXE                   OA$DSL$SHR.EXEy$                  OAFC$CLIENT_SHR.EXE                   OA$TMAECOMM.EXE    I                            ALL-IN-1 Version 3.2 Files and Directories B-1t f         3     B.2 Files Installed in Non-ALL-IN-1 DirectoriesG        '              DDS$RMT_VAX.EXE (VAX Only) ,              DDS$RMT_ALPHA.EXE  (Alpha Only)              DPESHR.EXEa              SYS$PROXY_SHR.EXE              OAFCDEF.H              OAFCDEF.L32              OAFCEXT.H              OAFCEXT.L32              OAFCEXT.R32              OAFC$LINK.OPT              PRXDEF.Ht                DDIF$READ_DX.EXEu#              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.EXEc!              DDIF$WRITE_WORD5.EXEn!              DDIF$WRITE_WORDP.EXEr              DDIF$WRITE_WPL.EXEa              DTIF$READ_DIF.EXE              DTIF$READ_TCV.EXE              DTIF$READ_WK1.EXE              DTIF$READ_WK3.EXE              DTIF$WRITE_WK1.EXEL              DTIF$WRITE_WK3.EXE +              DDIF$READ_RNO.EXE (Alpha Only)g  %              MRAPPSHAR.EXE (VAX Only)i'              MRAXPSHAR.EXE (Alpha Only)   >              OA$LLVlanguage.EXE (On Multilingual systems only)  F              OA$WPL_ALL_TV.EXE (Alpha with full WPS-PLUS support only)I              OA$WPL_FDP_TV.EXE (Alpha without full WPS-PLUS support only)u  &              IMP$IMPSHR.EXE (VAX only)'              IMP$IMPSHRP.EXE (VAX only)e  3     B-2  ALL-IN-1 Version 3.2 Files and DirectoriesA I  T      I                           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.EXEo#                  OA$AIDA_SERVER.EXEh!                  OA$AIDA_X500.EXEo'                  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.EXEE  (                  MRAPPMSG.EXE (VAX Only)*                  MRAXPMSG.EXE (Alpha Only)  /                  DDS$MSG_ALPHA.EXE (Alpha Only)t+                  DDS$MSG_VAX.EXE (VAX Only)V+                  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      I                            ALL-IN-1 Version 3.2 Files and Directories B-3_ _  _      3     B.2 Files Installed in Non-ALL-IN-1 DirectoriesN      )           o  SYS$COMMON:[SYSHLP.EXAMPLES]   )              EXAMPLE_READ_DIF.CDA$OPTIONSD(              EXAMPLE_READ_DX.CDA$OPTIONS.              EXAMPLE_READ_MACWRITE.CDA$OPTIONS*              EXAMPLE_READ_PICT.CDA$OPTIONS)              EXAMPLE_READ_RTF.CDA$OPTIONS )              EXAMPLE_READ_WK1.CDA$OPTIONSe)              EXAMPLE_READ_WK3.CDA$OPTIONSe+              EXAMPLE_READ_WORD5.CDA$OPTIONS 3              EXAMPLE_READ_WORD5_FONTMAP.CDA$OPTIONSs+              EXAMPLE_READ_WORDP.CDA$OPTIONS )              EXAMPLE_READ_WPL.CDA$OPTIONSp)              EXAMPLE_WRITE_DX.CDA$OPTIONSs/              EXAMPLE_WRITE_MACWRITE.CDA$OPTIONS +              EXAMPLE_WRITE_PICT.CDA$OPTIONSp*              EXAMPLE_WRITE_RTF.CDA$OPTIONS*              EXAMPLE_WRITE_WK1.CDA$OPTIONS*              EXAMPLE_WRITE_WK3.CDA$OPTIONS,              EXAMPLE_WRITE_WORD5.CDA$OPTIONS,              EXAMPLE_WRITE_WORDP.CDA$OPTIONS1              EXAMPLE_WRITE_WORDP_V5_0.CDA$OPTIONSi1              EXAMPLE_WRITE_WORDP_V5_1.CDA$OPTIONS *              EXAMPLE_WRITE_WPL.CDA$OPTIONS  :           Language specific lexicon files are installed inE           LCI$LEXICONS if you install WPS-PLUS as the default editor.                                     3     B-4  ALL-IN-1 Version 3.2 Files and Directoriese d  r                            F      _________________________________________________________________  F                                                                  Index      >      A                                 Customizations (cont'd)F      _______________________________     reviewing after installation,0      A1CONFIG.DAT,  5-7                     5-12#      A1V32START.COM,  5-5, 5-6, 5-7e(      ALL-IN-1                          DF        starting on all nodes, 5-5      _______________________________1      Applications                      Data filesoE        replacing help modules, 5-15      restoring customizations to,y0      AUTOGEN,  1-25                         5-150                                        DCLTABLES8      B______________________________     replacing,  5-92      Backing up,  1-45                 DDS$STARTUP@                                          adding to site-specificC      C                                      startup procedure, 5-29T4      _______________________________   DEC FMS,  A-20      CART                              DEC NotesB        running after installation,       starting before ALL-IN-1,/          5-11                               5-7TA      CART resolution procedure         DELETE_OBSOLETE_FILES.COM,r.        running and editing, 5-13          5-145      Checklist                         Deleting filesc?        postinstallation tasks, 5-1       postinstallation,  5-9eD      Cluster                           Deleting obsolete files after=        VMSmail Gateway configuration      installation,  5-14eE          ,  5-20                       Disk space requirements,  1-27o,      Configuring                       Disks:        VMSmail Gateway, 5-20             backing up,  1-45      Correcting system set-upgF         errors, 1-42                   E______________________________@      Customizations                    Error messages,  4-1, 4-4-        linking ALL-IN-1 to include,    Errors 5          5-16                            fatal,  1-42w9        migrating, 5-11                   non-fatal,  1-42n  F                                                                Index-1    e              *                                        IVP<     F______________________________     error messages,  4-4       Fatal errors,  1-42 F     Files, deleting                    L______________________________  C       postinstallation,  5-9           License Management Facility,T-     Form libraries                       1-14t/       recompiling,  5-10               LicensesA  D                                         prerequisite products,  1-16:     G______________________________     registering,  1-14  B     Global page file sections          Linking ALL-IN-1 to include>        (GBLPAGFIL), 1-23                 customizations,  5-164     Global pages (GBLPAGES),  1-23     Logical names8     Global sections (GBLSECTIONS),      assigning,  1-28-        1-23                            Logins 7                                         disallow,  1-45n  (     H______________________________    MF     Help modules                       _______________________________5       replacing for your               Mail directoryq?          application, 5-15              setting up with MessageoB                                            Router outside cluster,/     I______________________________        5-25iC     Images                              setup for Message Router ini=       missing,  5-10                       same cluster, 5-21iC       required,  1-32                   starting up for remote use,n/     Installation                           5-29u.       aborting,  2-2                   MailboxB       disk space required,  1-27        adding for remote ALL-IN-18       time required,  2-2                  systems, 5-188     Installation of optional            modifying,  5-20:        software                        Message Router, A-29       order of,  1-17                   setting up,  5-18o=     Installed images                   Message Router mailboxo<       required,  1-32                   modifying for mixed-A     Installing account                     architecture clusters,t/       licensing,  1-14                     5-20 E       quotas required during           Message Router VMSmail Gateway /          installation, 1-18              ,  A-2_/       valid rights identifier,         Messages 3          1-18                           error,  4-1 5     Installing missing images           warning,  4-1i0        postinstallation, 5-10          Migrating=                                         customizations,  5-11        Index-2     o              3                                           Relinking A         N______________________________     recommendations, 5-11 0         Non-fatal checks, repeating,      RemoteI           1-42                              VMSmail Gateway configurations5         Non-fatal errors, 1-42                ,  5-20 5                                           Remote mailtG         O                                   setting up with MAILbus 400 D         _______________________________       MTA and Digital X.500,2         OA$A1_CLUSTER_NODE                    5-16C          now defined in A1CONFIG,  5-6      setting up with Messagei;         OA$DDS_PRIME, 5-21                    Router,  5-17 ?         OA$MTI_AREA                       Remote Mail directory =          now defined in A1CONFIG,  5-6      starting up, 5-29 E         Optional software                 Repeating non-fatal checks, 1          order of installation,  1-17        1-42 <         Order of installation of          Rightslist entriesH           optional software,  1-17          checking after installation,  2         P                                     5-16'         _______________________________ I         PC option, 1-42                   S______________________________ ?         Perform all preinstallation       Site-specific startup ;           checks (PC) option,  1-42          procedure, 5-6 D         Personal licence                    adding DDS$STARTUP, 5-29?          adding installing account to     SITELINK32.COM,  5-11OA             reserve list,  1-14           Software license,  1-14 G         Preinstallation                   Software Product Description,.0          checks,  1-42                       A-23         Preparing system for              SPD,  A-2F2           installation,  1-44             Starting9         Prerequisite software               ALL-IN-1, 5-5 ;          licenses,  1-16                  Startup procedureE9         Product Authorization Key,          creating, 5-6_F           1-14                              editing site-specific, 5-7  >                                             site specific, 5-6E         R______________________________   SYS$STARTUP:A1V32START.COM,E  0         Recompiling                          5-60          form libraries,  5-10            SystemG         Registering software licenses,      preparing for installation,E2           1-16                                1-445         Release notes, 1-6                System disks<          printing,  1-7                     backing up, 1-45A          reading,  1-7                    System parameter valueshG                                             changing with AUTOGEN, 1-25)  I                                                                   Index-3i                     F     T______________________________    V______________________________  3     Target disk                        VAX FMS, A-2 6       backing up,  1-45                VMSmail Gateway:     Time required for installation      configuring,  5-20        , 2-2F                                        W______________________________<     U______________________________    Warning messages, 4-1  7     Users                              WPS-PLUS for VMS ?       log out,  1-45                    converting documents toE9                                            ALL-IN-1, 5-29N                                                                     Index-4T