                                     C                      Compaq_Office_Server__________________________ '                      Installation Guide         D                      Revision/Update Information: Updated for CompaqG                                                   Office Server Version 5                                                   6.0   E                      Operating system:            OpenVMS VAX Version D                                                   7.1 or higher, andG                                                   OpenVMS Alpha Version A                                                   7.1-2 or higher                                 0                      Compaq Computer Corporation#                      Houston, Texas                  E            __________________________________________________________             January 2001   C            Possession, use, or copying of the software described in D            this documentation is authorized only pursuant to a validD            written license from Compaq or an authorized sublicensor.  A            While Compaq believes the information included in this C            publication is correct as of the date of publication, it /            is subject to change without notice.   ?            Compaq Computer Corporation makes no representations ?            that the use of its products in the manner described ?            in this publication will not infringe on existing or E            future patent rights, nor do the descriptions contained in C            this publication imply the granting of licenses to make, D            use, or sell equipment or software in accordance with the            description.   .             2000, Compaq Computer Corporation  D            COMPAQ, the Compaq logo, the Digital logo, ALL-IN-1, DEC,D            DECnet, MAILbus and VAX are registered in U.S. Patent and            Trademark Office   =            Datatrieve, DECwindows, MailWorks, OpenVMS, Tru64, ?            VMScluster, VT and WPS-PLUS are trademarks of Compaq              Computer Corporation.  E            Other product names mentioned herein may be the trademarks )            of their respective companies.   A            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 6          1.2   Reading and Printing the Online ReleaseC                Notes........................................    1-7 1          1.3   Checking Prerequisite and Optional C                Software.....................................    1-8 C          1.4   Licensing....................................   1-14 8          1.4.1     Registering License PAKs for Software6                    Provided with Office Server VersionC                    6.0......................................   1-15 4          1.5   Example Order for Installing OptionalC                Software.....................................   1-16 C          1.6   Installation Procedure Requirements..........   1-17 C          1.6.1     Installing Account Requirements..........   1-17 C          1.6.2     System Parameters........................   1-18 C          1.6.3     Displaying Current System Parameters.....   1-23 C          1.6.4     Changing System Parameter Values.........   1-23 <          1.6.4.1     Updating Dynamic System Parameters withC                      AUTOGEN................................   1-25 :          1.6.4.2     Updating Non-Dynamic System ParameterC                      with AUTOGEN...........................   1-25 4          1.6.5     Disk Space on Your System Disk orC                    Alternate Working Device.................   1-26 C          1.6.6     Using the OA$LIB_SHARE Disk as the AWD...   1-27 8          1.6.7     Disk Space for Office Server Areas onC                    Target Disks.............................   1-27 C          1.6.8     Assigning Logical Names to Your Disks....   1-28 :          1.6.9     New Installation: Disk Space for OfficeC                    Server Areas.............................   1-29   C                                                                 iii                  9            1.6.10    Upgrade Installation: Disk Space for E                      Office Server Areas......................   1-30 ;            1.6.11    Addition of Architecture Support: Disk E                      Space for Office Server areas............   1-31 E            1.6.12    Disk Quota Allocation....................   1-32 E            1.6.13    Installed Images.........................   1-32 9            1.6.14    Installing FDVMSG.EXE and FDVSHR.EXE E                      Images...................................   1-37 E            1.6.15    Installing Other Images..................   1-37 E            1.6.16    Checking The Location of DCLTABLES.EXE...   1-37 E            1.7   Additional Tasks for Upgrade Installations...   1-38 E            1.7.1     Copying Customized Data Files............   1-39 E            1.8   Using the MAILbus 400 MTA and Compaq X.500...   1-39 E            1.9   Using a Remote Message Router................   1-39 ;            1.9.1     Create an Office Server Mailbox on the E                      Remote Message Router Node ..............   1-40 E            1.10  Running the Preinstallation System Check.....   1-41 E            1.10.1    Types of Errors Reported.................   1-41 <            1.10.2    Running the Perform all PreinstallationE                      Checks (PC) Option.......................   1-42 4            1.11  Final System Preparation Tasks: NewE                  Installations................................   1-43 8            1.12  Final System Preparation Tasks: UpgradeE                  Installations ...............................   1-43 E            1.12.1    Shut Down Office Server..................   1-44 E            1.12.2    Deinstall Files Installed in Memory......   1-44 E            1.13  Back Up Your System and Target Disks.........   1-44     =      2  Installation Procedure: New, Upgrade and Architecture          Support   ;            2.1   Installation Procedure for New and Upgrade E                  Installations................................    2-3 E            2.2   Adding or Upgrading Architecture Support.....   2-31 E            2.2.1     Before You Start.........................   2-32 6            2.2.2     Installation Procedure for AddingE                      Architecture Support.....................   2-32 E            2.3   Automatic Postinstallation Tasks.............   2-41 E            2.4   Manual Postinstallation Tasks................   2-42                 iv                  7         3  Installation Procedure: Additional Languages   9               3.1   Installation Procedure for Additional H                     Language Installations.......................    3-2:               3.2   Installing Architecture Support for anH                     Additional Language..........................    3-9  *         4  Installation Errors and Failure  H               4.1   Common Errors................................    4-1H               4.2   Failure During Postinstallation..............    4-2;               4.2.1     Failure of Upgrade Installations in H                         Safety Mode..............................    4-2;               4.2.2     Failure of Upgrade Installations in H                         Non-Safety Mode..........................    4-2H               4.2.3     Full Installations.......................    4-2;               4.2.4     Failure Due to Insufficient Dynamic H                         Memory...................................    4-3H               4.3   Error Messages when Running the IVP..........    4-3H               4.4   IVP Failure..................................    4-5  !         5  Postinstallation Tasks   H               5.1   Checklist of Manual Postinstallation Tasks...    5-19               5.2   Start Office Server on all Nodes in a H                     VMScluster System............................    5-5=               5.3   Create or Modify the Site-specific Office H                     Server Startup Procedure.....................    5-6H               5.4   Edit the Site-specific Startup Procedure.....    5-6?               5.4.1     Installations With Compaq X.500 and the H                         MAILbus 400 MTA..........................    5-7H               5.4.2     Installations with Message Router........    5-7H               5.5   Replace the DCLTABLES on Cluster Systems.....    5-9H               5.6   Delete Files That Are No Longer Required.....    5-9H               5.7   Install Missing Images.......................   5-10H               5.8   Recompile Form Libraries.....................   5-107               5.9   Migrating Your Customizations After H                     Upgrading....................................   5-11H               5.9.1     Running the CART Resolution Procedure....   5-12H               5.9.2     Deleting Obsolete Files..................   5-13;               5.9.3     Replacing the Help Modules for Your H                         Application..............................   5-14      H                                                                        v                 7            5.10  Migrate SITELINK50 Using Customization E                  Management...................................   5-15 9            5.11  Link Office Server to Include Code-level E                  Customizations...............................   5-15 >            5.12  Setting up Remote Mail When Using the MAILbusE                  400 MTA......................................   5-15 :            5.13  Setting up Remote Mail When Using MessageE                  Router.......................................   5-16 E            5.13.1    Create a Mailbox for Office Server.......   5-17r9            5.13.2    Modifying the Message Router MailboxlE                      Entry....................................   5-19 8            5.13.3    Configuring the VMSmail Gateway forE                      Remote Access............................   5-19 <            5.13.4    Setting Up the Message Router DirectoryE                      Service as the Mail Directory............   5-20 4            5.13.4.1    Message Router is in the SameE                        VMScluster.............................   5-20 8            5.13.4.2    Message Router is not in the SameE                        VMScluster.............................   5-24 <            5.13.5    Remote Message Router Directory ServiceE                      Startup Procedure........................   5-29 E            5.14  WPS-PLUS Login Command Procedure.............   5-30tE            5.15  Moving the CDA DOC_STYLE Files...............   5-30r    4      A  Office Server Version 6.0 Distribution Media  7            A.1   CD-ROM Distribution Kits (VAX or AlphaiE                  Installations)...............................    A-1c  7      B  Office Server Version 6.0 Files and Directories   E            B.1   Files in the Office Server Kit...............    B-1s5            B.2   Files Installed in Non-Office ServeroE                  Directories..................................    B-1                           vi     f                     C  ENGLISH Kit  H               C.1   About Your ENGLISH Kit.......................    C-2H               C.1.1     Distribution Media.......................    C-2H               C.1.2     Savesets Provided........................    C-2H               C.2   Disk Space Requirements......................    C-3A               C.2.1     Disk Space Required on the System Disk orUH                         Alternate Working Device (AWD)...........    C-4?               C.2.2     Disk Space for Language Files on TargetnH                         Disks....................................    C-47               C.3   Information on the English LanguageeH                     Component....................................    C-77               C.4   Information on the British Language H                     Component....................................    C-7H               C.5   Information on the US Market Component.......    C-8<               C.5.1     Keyboards Supported by the US MarketH                         Component................................    C-89               C.5.2     Modems Supported by the US Market H                         Component................................    C-9H               C.6   Information on the GB Market Component.......    C-9<               C.6.1     Keyboards Supported by the GB MarketH                         Component................................   C-109               C.6.2     Modems Supported by the GB Market.H                         Component................................   C-11  +         D  Information on Market ComponentsV  H               D.1   Belgian Market Component.....................    D-2H               D.2   Brazilian Market Component...................    D-2H               D.3   Canadian Market Component....................    D-3H               D.4   Dutch Market Component.......................    D-4H               D.5   French Market Component......................    D-4H               D.6   German Market Component......................    D-5H               D.7   Swiss Market Component.......................    D-6  
         Index.                  H                                                                      vii    T                  Tables.  E            1-1       Preinstallation Checklist................    1-2m  E            1-2       Prerequisite and Optional Software.......    1-9   E            1-3       Licenses for Migrating from MailWorks....   1-14   >            1-4       Process Account Quotas for the InstallingE                      Account..................................   1-18   4            1-5       Minimum System Parameter ValuesE                      Required.................................   1-19   E            1-6       Changing System Parameter Values.........   1-24N  <            1-7       New Installation: Disk Space for OfficeE                      Server Areas.............................   1-30   :            1-8       Upgrade Installations: Disk Space forE                      Office Server Areas .....................   1-31   3            1-9       Addition, Upgrade or Update of 9                      Architecture Support: Disk Space forrE                      Office Server Areas......................   1-32.  E            1-10      Installed Images Required on VAX.........   1-32   E            1-11      Installed Images Required on Alpha.......   1-341  7            2-1       Information About the Installation.E                      Procedure................................    2-21  7            2-2       Installation Procedure for New and.E                      Upgrade Installations....................    2-4E  9            2-3       When to Install/Upgrade VAX or AlphadE                      Architecture Support.....................   2-31a  6            2-4       Installation Procedure for AddingE                      Architecture Support.....................   2-33t  =            3-1       Installation Procedure for An AdditionaleE                      Language ................................    3-3g  ;            3-2       Installation Procedure for Addition oft;                      Architecture Support for an Additional.E                      Language.................................    3-9.  E            5-1       Postinstallation Tasks...................    5-1   >            5-2       Editing the OpenVMS Site-specific StartupE                      File.....................................    5-8.  E            5-3       Tasks for Setting up Remote Mail.........   5-16   E            C-1       Savesets Provided with the ENGLISH Kit...    C-2.  <            C-2        Disk Space Required on the System DiskE                      or AWD (Blocks)..........................    C-4   	      viii  4               :               C-3       Disk Space for Language Files: NewH                         Installation.............................    C-5  >               C-4       Disk Space for Language Files: UpgradeH                         from Version 3.1.........................    C-6  ;               C-5       Disk Space for Language Files: Add,rH                         Upgrade or Update Architecture Support...    C-6  :               C-6       Useful Information for the EnglishH                         Language Component.......................    C-7  :               C-7       Useful Information for the BritishH                         Language Component.......................    C-7  <               C-8       Useful Information for the US MarketH                         Component................................    C-8  <               C-9       Useful Information for the GB MarketH                         Component................................    C-9  A               D-1       Useful Information for the Belgian MarketgH                         Component................................    D-2  <               D-2       Useful Information for the BrazilianH                         Market Component.........................    D-2  ;               D-3       Useful Information for the CanadianIH                         Market Component.........................    D-3  ?               D-4       Useful Information for the Dutch MarketlH                         Component................................    D-4  @               D-5       Useful Information for the French MarketH                         Component................................    D-5  @               D-6       Useful Information for the German MarketH                         Component................................    D-5  ?               D-7       Useful Information for the Swiss Market.H                         Component................................    D-6        H                                                                       ix f  e                      H         ________________________________________________________________  H                                                                  Preface               About This Booko  H               Before you use this book, you must plan your Office ServerC               Version 6.0 installation by reading the Compaq OfficenC               Server Planning and Setup Guide. Note that the Compaq.H               Office Server Planning and Setup Guide was not updated forE               Office Server Version 6.0, but that the instructions itB                gives still apply.  G               The Compaq Office Server Installation Guide describes how "               to do the following:  E               1. Prepare your system for an Office Server Version 6.0L                  installation.  3               2. Install Office Server Version 6.0.   D               3. Set up Office Server Version 6.0 so that the Office>                  Server manager can log in and use it locally.  C         Office Server Installation: Language and Market Information.  G               The documentation provided with non-ENGLISH kits providesrD               the disk space values for installing the Office Server>               Version 6.0 kit, and information on the languageA               and market components that you will need during theg               installation.z           Prerequisite Knowledge  E               This guide assumes that you have read the Compaq Officee.               Server Planning and Setup Guide.  G               To install Office Server Version 6.0 you must be familiart)               with the VMSINSTAL utility.   H                                                                       ix    5            3      The Office Server Management Documentation SetR  A            The following guides form the Office Server management.            documentation set:e  ;            o  Compaq Office Server Planning and Setup Guidea  5            o  Compaq Office Server Installation Guide.  =            o  The online help for Office Server Administratorg  C               ________________________Note ________________________.  @               The V4.0 management guide may still be useful, butB               the most up-to-date management information is in the/               Office Server Administrator help.s  C               _____________________________________________________.  3      Terminology and Conventions Used in this Guidea  D            The following table lists the terminology and conventions            used in this guide.  >            Office Server    Means the Compaq Office Server for9                             OpenVMS Alpha and OpenVMS VAX5  D            OpenVMS Alpha    Means the OpenVMS Alpha operating system  B            OpenVMS VAX      Means the OpenVMS VAX operating system  A            UCX              Means DEC TCP/IP Services for OpenVMS   ?            AIDA Server      Means the Distributed Access Server   >            Client user      Means a user of a client of Office9                             Server. Client users include:   D                             o  Users of personal computers (PCs) and=                                workstations (PC client users)   ?                             o  Users of the video terminal (VT) C                                interface to Office Server software, E                                when they choose options that make use D                                of an Office Server server (VT client%                                users)o        x .  .              F               Architecture     Is a term used to differentiate betweenD                                OpenVMS VAX systems and OpenVMS Alpha&                                systems             Related Documents   D               You may also need to refer to the documentation on the!               following products:.  4               o  VAX Message Router and its Gateways                 o  DEC Notes  *               o  OpenVMS system management  5               o  The MAILbus 400 MTA and its Gateways                  o  Compaq X.500u                 o  DECnet/OSIn                                              H                                                                       xi                       H                                                                        1H         ________________________________________________________________  H                                   Preparing Your System for Installation      B               This chapter describes the tasks that you must do toH               prepare your system for an Office Server installation. TheG               information in this chapter applies to all installations..  G               You must read the Compaq Office Server Planning and Setup G               Guide before you install Office Server. The guide covers:   @               o  Information about this version of Office Server  %               o  Mail system planning   D               o  Installation planning, including a checklist of allH                  the decisions that you need to make before starting the                  installationu  A                  In addition, if your system has been customized, D                  you must read the chapter Planning the Upgrade of aF                  Customized System in the Overview and Planning Guide.G                  This chapter explains how to run the Conflict CheckingnH                  and Resolution Tool (CART) to check your customizations5                  before you upgrade to Office Server..  %               o  Mail system planningC  .               o  System policies and licensing  D               This installation guide assumes that you have read theE               Compaq Office Server Planning and Setup Guide, made all H               your planning decisions and know what type of installation'               you are going to perform..          H                               Preparing Your System for Installation 1-1 R  i      +      Preparing Your System for Installation +      1.1 Checklist of Preinstallation Tasksl  +      1.1 Checklist of Preinstallation Tasksw  D            To prepare your system for an Office Server installation,5            you must do the tasks listed in Table 1-1.   E            Table_1-1_Preinstallation_Checklist_______________________e  E                                              For further information,,E            Task___Description________________see_____________________   B            1      Check the kit contents     The Bill of MaterialsC                                              for a list of what the.D                                              distribution kit should5                                              contain.n  @                                              Contact your Compaq>                                              representative if@                                              your kit is damaged;                                              or incomplete.o  E            __________________________________________________________.  (            2      Read the READ ME FIRST+                   letter if one is supplied                    with your kitu  E            __________________________________________________________r  A            3      Make sure that you have    Compaq Office Server.E                   planned your installation  Planning and Setup Guided(                   and Office Server mail$                   system. The Compaq(                   Office Server Planning&                   and Setup Guide also(                   lists any prerequisite*                   configuration tasks that&                   must be done for the)                   messaging products that.&                   you plan to use with&                   Office Server. These)                   tasks must be completedC'                   before you start yourS                   installation.2  E                                              (continued on next page)W  /      1-2 Preparing Your System for Installation  i         H                                   Preparing Your System for InstallationH                                   1.1 Checklist of Preinstallation Tasks  H               Table_1-1_(Cont.)_Preinstallation_Checklist_______________  H                                                 For further information,H               Task___Description________________see_____________________  H               __________________________________________________________  ?               4      Read the online product    Section 1.2 fora?                      release notes provided     instructions on E                      with the kit               accessing the releasee6                                                 notes.  H               __________________________________________________________  ;               5      Check that you have the    Section 1.3 )                      correct versions of:k  (                      o  The prerequisite(                         software for the$                         installation  -                      o  Any optional softwareo(                         that you want to                         installs  H               __________________________________________________________  ;               6      Check that you have a      Section 1.4f*                      valid license for the'                      installing account.  H               __________________________________________________________  =               7      Register the License       Section 1.4.1..                      PAKs for the prerequisite*                      and optional software)                      provided with Office.                      Server.  H               __________________________________________________________  H                                                 (continued on next page)      H                               Preparing Your System for Installation 1-3 p  n      +      Preparing Your System for Installation +      1.1 Checklist of Preinstallation Tasks   E            Table_1-1_(Cont.)_Preinstallation_Checklist________________  E                                              For further information, E            Task___Description________________see_____________________   @            8      Check the installation     Section 1.6 for the@                   procedure requirements:    values required and=                   o  For the installing      instructions for B                      account                 checking and changing>                                              these parameters.&                   o  System parameters                     o  Disk space   "                   o  Logical names  %                   o  Installed imageso  $                   o  The location of"                      DCLTABLES.EXE  E            __________________________________________________________   9            9      For upgrade installa-      Section 1.7. *                   tions, do any additional                   tasks.  E            __________________________________________________________S  E                                              (continued on next page)                               /      1-4 Preparing Your System for Installations e  l      H                                   Preparing Your System for InstallationH                                   1.1 Checklist of Preinstallation Tasks  H               Table_1-1_(Cont.)_Preinstallation_Checklist_______________  H                                                 For further information,H               Task___Description________________see_____________________  A               10     Check that all pre-        Section 1.3 listsh@                      requisite and optional     prerequisite andE                      software is installed,     optional software. In F                      configured and running     addition, you may wantH                      before you start           to install DATATRIEVE orH                      the Office Server          ACMS if you are planningE                      installation.              to use these productslC                                                 with Office Server._  @                                                 All prerequisiteG                                                 messaging products suchaD                                                 as Message Router orG                                                 the MAILbus 400 MTA and_D                                                 Compaq X.500 must beE                                                 installed, configured F                                                 and running before youF                                                 install Office Server.E                                                 See the Compaq OfficenC                                                 Server Planning andn<                                                 Setup Guide.  ?                                                 For a suggestedeC                                                 order of installingeF                                                 optional software, see<                                                 Section 1.5.  H               __________________________________________________________  ;               11     If you are installing a    Section 1.8T-                      new Office Server system *                      with Compaq X.500 and)                      the MAILbus 400 MTA,m.                      check that these products,                      have been installed and*                      configured correctly.  H               __________________________________________________________  H                                                 (continued on next page)  H                               Preparing Your System for Installation 1-5           +      Preparing Your System for Installationt+      1.1 Checklist of Preinstallation Tasks.  E            Table_1-1_(Cont.)_Preinstallation_Checklist_______________   E                                              For further information, E            Task___Description________________see_____________________.  9            12     If you will be using a     Section 1.9. '                   remote Message Router $                   that is not in the)                   same VMScluster, do any #                   additional tasks.   E            ___________________________________________________________  9            13     It is recommended that     Section 1.10 )                   you run the Perform alli(                   preinstallation checks+                   (PC) option to check that )                   your system is preparedr+                   for the installation. The (                   PC option runs through+                   the installation to checkq'                   that you have all the (                   prerequisite licenses,*                   software, disk space and)                   installation parameterse*                   correctly set up on your                   system.a  E            __________________________________________________________s  A            14     Do the final system        Section 1.11 for newa>                   preparation tasks.         installations andE                                              Section 1.12 for upgrade ;                                              installations.i  E            __________________________________________________________   9            15     Back up your system and    Section 1.13(E            _______target_disks.______________________________________             /      1-6 Preparing Your System for Installation            H                                   Preparing Your System for InstallationH                        1.2 Reading and Printing the Online Release Notes  9         1.2 Reading and Printing the Online Release Notese  E               Online release notes are provided with the language andoC               market components of Office Server. The release notessG               contain information that was unavailable before the bookssH               went to print. It is recommended that you read the releaseE               notes, because they may contain information relating to F               the installation. You can access the release notes usingC               the VMSINSTAL procedure before you install the Office_               Server software.  E               There are two parts to the Office Server release notes:T  .               o  Release Notes Part 1 Language  E                  This part contains the release notes specific to ther8                  Office Server language being installed.  ,               o  Release Notes Part 2 Market  F                  This part contains the release notes specific to yourH                  Office Server market component. Note that this document9                  may not exist for all market components.   C               To read or print the release notes, do the following:i  B               1. Log in to the privileged OpenVMS system manager's?                  account and enter the following command lines:_  )                  $ SET DEFAULT SYS$UPDATEA7                  $ @VMSINSTAL product device: OPTIONS N   >                  where device is the device on which the mediaH                  containing the appropriate version of the release notesH                  is mounted and product is the product code. The product                  codes are:u  E                  o  A1Llang060 for the Release Notes Part 1 Language, H                     where lang is the 2-letter code for the language you"                     are installing  E                  o  A1Cmarket060 for the Release Notes Part 2 Market, D                     where market is the 2-letter code for the market0                     component you are installing  E                  If you are performing an additional language instal-oF                  lation, you need only print the Office Server ReleaseF                  Notes Part 1 Language that is supplied with your kit.  H                               Preparing Your System for Installation 1-7           +      Preparing Your System for Installatione6      1.2 Reading and Printing the Online Release Notes  E            When you have read or printed the release notes, terminater@            the installation procedure. If you have accessed onlyA            one part of the release notes, repeat the procedure tokC            access the other part. The following files are placed in             SYS$HELP:  B            o  A1Llang060.RELEASE_NOTES, for the Release Notes PartA               1 Language, where lang is the 2-letter code for then)               language you are installing   D            o  A1Cmarket060.RELEASE_NOTES, for the Release Notes PartA               2 Market, where market is the 2-letter code for the_1               market component you are installing_  4      1.3 Checking Prerequisite and Optional Software  @            Table 1-2 provides information about the prerequisiteD            software for an Office Server installation. It also listsD            the software that is supplied with the Office Server kit,>            and optional software that you may want to install.  +            The following definitions apply:   D            o  Prerequisite means that the software must be installedE               before you install Office Server. The installation will A               fail if the prerequisite software is not installed.   B            o  Optional means that the software is not required for?               the Office Server installation. Optional software.@               provides additional functionality and the optionalC               software that you install depends on the requirementsfA               at your site. For example, if you want to use Group_7               Conferencing, you must install DEC Notes.   C               ________________________Note ________________________   >               Both the prerequisite software, and any optional<               software that you want to install, must be in-@               stalled, configured and running before you install               Office Server.  C               _____________________________________________________       /      1-8 Preparing Your System for Installationo _  _      H                                   Preparing Your System for InstallationH                          1.3 Checking Prerequisite and Optional Software  H               Table_1-2_Prerequisite_and_Optional_Software______________  7                                                Suppliedn3               Software         VAX      Alpha  With H               Product__________Version__VersionKit?___Notes_____________  F               OpenVMS VAX      7.1 or   -      N      Prerequisite forE                                higher                 installation on :                                                       VAX.  D                                                       Must be a fullG                                                       untailored systemi  F               OpenVMS Alpha    -        7.1-2  N      Prerequisite forE                                         or            installation on <                                         higher        Alpha.  D                                                       Must be a fullG                                                       untailored system   H               __________________________________________________________  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  H                                                 (continued on next page)                        H                               Preparing Your System for Installation 1-9           +      Preparing Your System for Installation 4      1.3 Checking Prerequisite and Optional Software  E            Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______r  4                                             Supplied0            Software         VAX      Alpha  WithE            Product__________Version__VersionKit?___Notes_____________   B            DECnet/OSI for   7.1 or   7.1    N      Prerequisite[1]D            OpenVMS          higher   or            for systems usingB                                      higher        Compaq X.500 orC                                                    Compaq X.500 and B                                                    the MAILbus 4007                                                    MTA.n  ;                                                    Optional.B                                                    alternative for@                                                    systems usingB                                                    Message Router.  E            __________________________________________________________   <            TCP/IP Services  4.2 or   5.0    N      Optional.A            for OpenVMS      higher   or            Install if you B            or other TCP              higher        want to use theA            /IP software                            TCP/IP networkM>            that emulates                           protocol to>            this[3]                                 communicate  >                                                    with client@                                                    applications.  E            __________________________________________________________r  E            [1]DECnet/OSI_is_a_prerequisite_for_Compaq_X.500._If______y  @            you plan to migrate to use Message Router with CompaqA            X.500, you must install DECnet/OSI as the prerequisite_D            for Compaq X.500. For Compaq X.500, you must also installA            the OSI Applications Kernel, OSAK, from the DECnet/OSI_D            Applications component. See the Compaq X.500 installation.            documentation for more information.B            [3]For supported versions of other TCP/IP software that?            emulates TCP/IP Services for OpenVMS, see the Office /            Server Software Product Description._  E                                              (continued on next page)   0      1-10 Preparing Your System for Installation           H                                   Preparing Your System for InstallationH                          1.3 Checking Prerequisite and Optional Software  H               Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______  7                                                Supplied 3               Software         VAX      Alpha  With H               Product__________Version__VersionKit?___Notes_____________  ?               Message Router   3.5      -      Y      Optional.y  A                                                       Install and_B                                                       configure ifF                                                       you want to sendG                                                       remote mail usingdE                                                       Message Router.   H               __________________________________________________________  >               Message Router   3.5      -      Y      OptionalD               VMSmail Gateway                         Install if you  G                                                       want to send mail H                                                       from Office ServerC                                                       systems using G                                                       Message Router tonD                                                       VMSmail users.  H               __________________________________________________________  >               MAILbus 400      2.0b     2.0b   N      OptionalA               MTA[4]                                  Install and   B                                                       configure ifE                                                       you want to use E                                                       the MAILbus 400 D                                                       MTA for remoteE                                                       mail. Note thataG                                                       Compaq X.500 is atF                                                       prerequisite forE                                                       the MAILbus 400c:                                                       MTA.  H               __________________________________________________________  H               [4]Office_Server_can_also_connect_to_a_MAILbus_400_MTA____  4               installed on a remote Tru64 UNIX node.  H                                                 (continued on next page)  H                              Preparing Your System for Installation 1-11 U  T      +      Preparing Your System for InstallationP4      1.3 Checking Prerequisite and Optional Software  E            Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______   4                                             Supplied0            Software         VAX      Alpha  WithE            Product__________Version__VersionKit?___Notes_____________t  B            Compaq X.500[5]  3.1[6]   3.1    N      Prerequisite ifB                                                    you plan to useB                                                    the MAILbus 4007                                                    MTA.   B                                                    Optional if youC                                                    plan to continue @                                                    using Message:                                                    Router.  E            __________________________________________________________n  E            [5]DECnet/OSI_is_a_prerequisite_for_Compaq_X.500._If______e  @            you plan to migrate to use Message Router with CompaqA            X.500, you must install DECnet/OSI as the prerequisite D            for Compaq X.500. For Compaq X.500, you must also installA            the OSI Applications Kernel, OSAK, from the DECnet/OSI D            Applications component. See the Compaq X.500 installation.            documentation for more information.C            [6]After V3.0 had been released, Digital X.500 DirectoryaD            Service became Compaq X.500. A further change will happen@            during the lifetime of Office Server Version 6.0. The=            directory service, with added LDAP functions, willt@            be bundled with OpenVMS Alpha V7.3, with the new nameE            'OpenVMS Enterprise Directory for eBusiness'. This product E            will be unlicensed and freely available with the operatingwD            system. On systems where only VAX machines are available,?            the (licensed) V3.1 will still be a prerequisite fora            Office Server.o  E                                              (continued on next page)               0      1-12 Preparing Your System for Installation d         H                                   Preparing Your System for InstallationH                          1.3 Checking Prerequisite and Optional Software  H               Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______  7                                                Suppliedr3               Software         VAX      Alpha  With H               Product__________Version__VersionKit?___Notes_____________  >               MAILbus 400      1.2      -      N      OptionalD               Message Router                          Install if youF               Gateway                                 want to exchange  B                                                       mail betweenD                                                       Message RouterA                                                       systems and E                                                       MAILbus 400 MTA >                                                       systems.  H               __________________________________________________________  ?               DEC Notes        2.5      2.5    Y      Optional.o  D                                                       Install if youG                                                       want to use Group C                                                       Conferencing.d  H               __________________________________________________________  >               CDA Converter    2.2      -      N      OptionalD               Library[7]                              Install if you  F                                                       require full CDAH                                                       support on OpenVMS:                                                       VAX.  >               DECwindows[8]    -        1.2    N      OptionalD                                         or            Install if youF                                         higher        require full CDA  H                                                       support on OpenVMS<                                                       Alpha.H               [7]The_installation_procedure_checks_for__________________  3               SYS$SHARE:CDA$ACCESS.EXE, Version 1.7r6               [8]The installation procedure checks for3               SYS$SHARE:CDA$ACCESS.EXE, Version 1.8 H               __________________________________________________________  D               For information about the order of installing optional(               software, see Section 1.5.  H                              Preparing Your System for Installation 1-13           +      Preparing Your System for Installation 4      1.3 Checking Prerequisite and Optional Software  D            For a list of all supported versions of products that canE            be used with Office Server, see the Office Server Softwarep            Product Description.n        1.4 Licensing  =            The way that your Office Server system is licensedrA            depends on the whether you are migrating from ALL-IN-1e8            or MailWorks, or are installing a new system:  D            1. If you already have an ALL-IN-1 license, all appropri-D               ate subsets for Office Server are enabled, and currentD               license Product Authorization Keys (PAKs) are honored.  B               If you are migrating from MailWorks, a Client AccessC               License must be acquired for every user of the systemm$               as shown in Table 1-3.  E            Table_1-3_Licenses_for_Migrating_from_MailWorks___________               MigratingE            from________To__________Licensing_Required________________n  A            MailWorks   Office      100 Client Access Licenses are @            on VAX      Server on   supplied at no cost with eachD                        VAX         Office Server License. If you areE                                    migrating more than 100 users, you E                                    must purchase an additional Client E                                    Access License for each additionalO(                                    user.  ?            MailWorks   Office      Update Client Access LicenseoD            on VAX      Server on   must be purchased for every user.D                        Alpha       After migration to Office Server,B                                    you must purchase an additionalB                                    Client Access License for every3                                    additional user.a  E                                              (continued on next page)_            0      1-14 Preparing Your System for Installation .  .      H                                   Preparing Your System for InstallationH                                                            1.4 Licensing  H               Table_1-3_(Cont.)_Licenses_for_Migrating_from_MailWorks___                 Migrating H               from________To__________Licensing_Required________________  H               MailWorks   Office      Existing Capacity or User licensesG               on Alpha    Server on   can be traded for the appropriate G                           Alpha       number of Client Access Licenses, B                                       equal to the number of usersE                                       supported during the migration. G                                       After migration to Office Server,nE                                       you must purchase an additionalrE                                       Client Access License for everyrH               ________________________additional_user.__________________  >               2. If you are installing a new system, licensing@                  is controlled by Client Access Licenses (CALs).E                  Functionality is restricted to Electronic Messaging, @                  Group Services, Directories, File Cabinet, WordD                  Processing (not including the WPS-PLUS editor), and                  User Setup.  A         1.4.1 Registering License PAKs for Software Provided with '               Office Server Version 6.0   H               You must register the License PAKS for additional products>               supplied with the Office Server Version 6.0 kit.  A               The License PAKs for Message Router, Message Router H               gateway, DEC Notes, VAX FMS, and the CDA Converter LibraryE               can be registered automatically using the Office Server 0               Version 6.0 installation procedure  F               The License PAKs supplied for these products are for VAXE               installations only, and are for any number of users. If F               you already have a license for one of these products, itF               will be replaced by the license supplied with the Office%               Server Version 6.0 kit._  H               To register the License PAKs automatically, follow Steps 1                to 5 in Table 2-2.        H                              Preparing Your System for Installation 1-15           +      Preparing Your System for Installation       1.4 Licensing  >            Enter RL when the installation prompts you with the            following question:  ;            * Which installation do you wish to perform [1]:   C               ________________________Note ________________________   A               Choosing the RL option does not start the installa-                tion.   C               _____________________________________________________   D            The installation procedure checks your existing licenses,?            and if necessary registers and loads the appropriate_?            licenses for the software products provided with theO?            Office Server Version 6.0 kit. The installation then             terminates.  =            For prerequisite or optional products that are not E            supplied with Office Server, you must register the licensegE            PAKs manually using the License Management Facility (LMF).y  7      1.5 Example Order for Installing Optional SoftwareO  C            After you have installed and configured the prerequisiten@            software, install and configure the optional softwareB            products. See the appropriate product documentation for7            installation and configuration instructions._  <            The following installation order is suggested for@            installing optional software before the Office Server$            Version 6.0 installation:              1. Install ACMS  6            2. Install VAX DATATRIEVE or DEC DATATRIEVE  >            3. Install and configure your message transport and)               directory service software.   >               o  For new or upgrade installations with MessageD                  Router, make sure that Message Router is installed,C                  configured and running before you start the Office_A                  Server installation. If you plan to use a remote_@                  Message Router Directory Service, you must do aB                  customized Message Router configuration to enable>                  remote Directory Service access and configureE                  Message Router exception reporting for the DirectoryA  0      1-16 Preparing Your System for Installation    A      H                                   Preparing Your System for InstallationH                       1.5 Example Order for Installing Optional Software  B                     Service and Transfer Service according to your'                     planning decisions.h  C                  o  For new installations with Compaq X.500 and theiE                     MAILbus 400 MTA make sure that you have installedSF                     and configured all the required components on yourC                     Office Server node or cluster. Compaq X.500 andeD                     the MAILbus 400 MTA must be correctly installed,C                     configured and running before you start the new C                     Office Server installation. See the MAILbus 400 G                     MTA and Compaq X.500 Planning chapter in the Compaq ;                     Office Server Planning and Setup Guide.   A               4. Install and configure optional gateway products.l  G                  o  The Message Router VMSmail Gateway if required witht#                     Message Router..  F                  o  The MAILbus 400 Message Router Gateway if required-                     with the MAILbus 400 MTA.t  E                  o  The MAILbus 400 SMTP Gateway if required with then$                     MAILbus 400 MTA.  #               5. Install DEC Notes.   /         1.6 Installation Procedure Requirementsr  D               This section describes the requirements for installingE               Office Server Version 6.0. It explains how to check the 9               values and how to change them if necessary.   -         1.6.1 Installing Account Requirements   E               Use the SYSTEM account to install Office Server Version                6.0.  H               The installing account must have a valid rights identifierG               which is the same as the UIC for the account name. If you_F               are using the SYSTEM account, the rights identifier mustE               be the same as the UIC. To check the UIC and identifier '               values, do the following:   (               $ RUN SYS$SYSTEM:AUTHORIZE)               UAF> SHOW/IDENTIFIER SYSTEM   H                              Preparing Your System for Installation 1-17 _  _      +      Preparing Your System for Installation ,      1.6 Installation Procedure Requirements  ?            The value that is displayed is the UIC of the system B            account. To add the rights identifier, if it is not set             up, do the following:  5            UAF> ADD/IDENTIFIER SYSTEM/VALUE:UIC=[1,4]             UAF> EXIT  B            The installing account must also have sufficient quotas?            to enable you to perform the installation. Table 1-4 '            summarizes the requirements.   B            Note that these values are sufficient for installation,E            but they may not be appropriate for running Office Server. >            When you create new user accounts for Office ServerD            Version 6.0 the process quotas are set to the appropriate            values.  >            Table 1-4 Process Account Quotas for the InstallingE            __________Account_________________________________________o              AccountE            Quota_________VAX____Alpha__Notes_________________________   "            BYTLM         64     64#                          000    000o  #            ENQLM         300    300   #            FILLM         200    200f  E            JTQUOTA       1800   1800   JTQUOTA can be returned to itslB                                        normal system running valueA                                        after the installation has 1                                        completed.   "            PGFLQUOTA     25     65#                          000    000 E            _____________________pagelets_____________________________         1.6.2 System Parameters  @            Table 1-5 lists the minimum required system parameterA            values for the installation. Depending on the kinds ofiB            programs and applications running at your site, you mayE            need higher values for some settings. If necessary, modifys3            the parameters to at least these values.a  0      1-18 Preparing Your System for Installation e         H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  F                 ________________________Note  ________________________  ?                 You must check the OpenVMS system parameters on0D                 each node in the cluster on which you install Office#                 Server Version 6.0.   E                 _____________________________________________________   F               The values for the system parameters and quotas given inF               this section are those specific to Office Server Version6               6.0 and are acceptable for most systems.  E               Dynamic system parameters are labelled with a (D) after H               them. You do not need to reboot your system after changingF               dynamic system parameters. If you need to set new valuesF               for other system parameters, you must reboot your system6               in order for the changes to take effect.  H         Table_1-5_Minimum_System_Parameter_Values_Required______________           SystemH         Parameter_____VAX_________________Alpha_________________________  -         CTLPAGES      100                 100l  H         ________________________________________________________________  3         GBLSECTIONS   250 (new)           250 (new)   6                       50 (upgrade)        50 (upgrade)  H         ________________________________________________________________  8         GBLPAGES      20000 (new)         35000 (new)[1]  ;                       5000 (upgrade)      5000 (upgrade)[1]x  H         ________________________________________________________________  H         [1]For_Alpha_systems_after_OpenVMS_Version_7.1,_the_value_of____           GBLPAGES is dynamic.  H                                                 (continued on next page)  H                              Preparing Your System for Installation 1-19           +      Preparing Your System for Installation ,      1.6 Installation Procedure Requirements  E      Table_1-5_(Cont.)_Minimum_System_Parameter_Values_Required______c        System E      Parameter_____VAX_________________Alpha__________________________  =      GBLPAGFIL     For new installa-   For new installations:l@                    tions:              1. Add 1 to the number of  C                    1. Add 1 to the        active users. There is ansE                       number of           upper limit of 200 for thisoC                       active users.       value, so use 200 if youraD                       There is an         value is greater than 200.0                       upper limit      2. Add 32                        of 200 for!                       this value,s#                       so use 200 if #                       your value ise"                       greater than                       200.  #                    2. Multiply your "                       value by 16.                      3. Add 500   E                    __________________________________________________   E                                              (continued on next page)p                                  0      1-20 Preparing Your System for Installation    b      H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  H         Table_1-5_(Cont.)_Minimum_System_Parameter_Values_Required______           SystemH         Parameter_____VAX_________________Alpha_________________________  D         GBLPAGFIL     For upgrade         For upgrade installations:G                       installations:      1. Add together the number ofn  E                       1. Add together        global buffers[2] on the H                          the number          following files in OA$DATA_3                          of global           SHARE:_<                          buffers[2] on       o  ATTENDEE.DAT&                          the following;                          files in            o  MEETING.DAT_;                          OA$DATA_SHARE:      o  PENDING.DATl  ;                          o  ATTENDEE.DAT     o  PROFILE.DATi  F                          o  MEETING.DAT   2. Add the total from Step 1  D                          o  PENDING.DAT      to the number of globalB                          o  PROFILE.DAT      buffers in the sharedG                                              document attributes files,lF                       2. Add the total       OA$DAF_n.DAT in OA$SHARn,G                          from Step 1 to      where n is a letter from Ae2                          the number          to E.E                          of global        3. Divide the total by 4 to D                          buffers in the      convert to global pages(                          shared document3                          attributes       4. Add 32 '                          files, OA$DAF_g!                          n.DAT inr(                          OA$SHARn, where&                          n is a letter%                          from A to E.   %                       3. Multiply the #                          total by 4 &                          to convert to%                          global pagesr                          4. Add 500  H         [2]To_find_the_number_of_global_buffers_do_a_DIR/FULL_for_each__  
         file.e  H                                                 (continued on next page)  H                              Preparing Your System for Installation 1-21 a  m      +      Preparing Your System for Installationv,      1.6 Installation Procedure Requirements  E      Table_1-5_(Cont.)_Minimum_System_Parameter_Values_Required______r        SystemsE      Parameter_____VAX_________________Alpha_________________________   E      ________________________________________________________________A  C      LOCKIDTBL     100 multiplied      100 multiplied by the numbert/                    by the number of    of users                     active users   E      ________________________________________________________________   +      MAXBUF (D)    5000                5000   E      ________________________________________________________________   C      MAXPROCESSCNT 50 plus the number  50 plus the number of active ,                    of active users     users  E      ________________________________________________________________.  E      RESHASHTBL    50 multiplied       50 multiplied by the number ofl3                    by the number of    active usersr                    active users   E      ________________________________________________________________   E      SCSNODE       Must be the same    Must be the same as the DECnet 0                    as the DECnet node  node name                    named  E      ________________________________________________________________   D      SCSSYSTEMID   DECnet area number  DECnet area number multipliedD                    multiplied by       by 1024, plus the DECnet node-                    1024, plus the      numbers%                    DECnet node numberA  E      ________________________________________________________________   7      VIRTUALPAGECNT16]384 pages[4]     250 000 pagelets E      [3]A_high_value_of_VIRTUALPAGECNT_is_required_when_running_the__d  ?      File Cabinet test and repair procedure (FCVR program). ForeA      versions of OpenVMS after Version 7.0, VIRTUALPAGECNT is nota      required.A      [4]This value is approximately the same as 250 000 pagelets.tE      ________________________________________________________________s  0      1-22 Preparing Your System for Installation g  c      H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  F                 ________________________Note  ________________________  =                 For the majority of installations, the valueso@                 for CTLPAGES are sufficient. If you are planning<                 to reboot your system to change other systemA                 parameters, you can increase the value to 200 fora1                 the duration of the installation.l  E                 _____________________________________________________   2         1.6.3 Displaying Current System Parameters  E               Run the SYSGEN utility to display the current parameter                settings:I  F               1. To display all the current system parameter settings,                  enter:a  (                  $ 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:b  :               $ 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 is_D               less than the value in Table 1-5 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.6.4 Changing System Parameter Values  B               Edit the file SYS$SYSTEM:MODPARAMS.DAT to change theF               system parameter values. The entry that you make in thisH               file depends on which of the parameters you are modifying.               See Table 1-6.  H                              Preparing Your System for Installation 1-23 m  r      +      Preparing Your System for Installation ,      1.6 Installation Procedure Requirements  >            If you need to change and update non-dynamic systemC            parameters, you must schedule time to reboot your system A            in order for the changes to take effect. The (D) afterrA            the system parameter value shows that they are dynamic             parameters.    E            Table_1-6_Changing_System_Parameter_Values________________a              To change            the followingE            parameters_______Do_the_following_________________________   E            SCSNODE          Edit SYS$SYSTEM:MODPARAMS.DAT and specifyn@            SCSSYSTEMID      new parameter values. Use assignment3                             statements of the form:_  7                             parameter = parameter-value   >                             where parameter is the name of the<                             parameter you want to change andC                             parameter-value is the setting you want B                             to change it to. See Table 1-5 for the+                             required value.e  E            __________________________________________________________   E            CTLPAGES         Edit the file SYS$SYSTEM:MODPARAMS.DAT totE            GBLPAGES         specify new values. Include a line of the E            GBLPAGFIL        following format for each parameter to be_$            GBLSECTIONS      changed:  :            LOCKIDTBL        ADD_parameter = increase-value  >            MAXBUF (D)       where parameter is the name of the=            MAXPROCESSCNT    parameter you want to change, and A            RESHASHTBL       increase-value is the amount by which D            VIRTUALPAGECNT   you want to increase the setting of this&                             parameter.  A                             For example, to increase the value of 3                             LOCKIDTBL by 60, enter:x  ,                             ADD_LOCKIDTBL=60  E            _________________See_Table_1-5_for_the_required_values.___S  @            If you change any of the system parameter values, youB            must update them using AUTOGEN. See Section 1.6.4.1 and            Section 1.6.4.2.   0      1-24 Preparing Your System for Installation           H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  ?         1.6.4.1 Updating Dynamic System Parameters with AUTOGEN_  C               To update the dynamic system parameter values, do thel               following:  (               1. Run AUTOGEN as follows:  :                  $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS  9               2. Write the changes to the current system:b  (                  $ RUN SYS$SYSTEM:SYSGEN$                  SYSGEN> USE CURRENT%                  SYSGEN> WRITE ACTIVE   -               3. Press Ctrl/Z to leave SYSGENt  D               You do not need to reboot your system to make your new!               values take effect.   E               For more information, see the OpenVMS manual describing "               the AUTOGEN utility.  B         1.6.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.  E                 ______________________________________________________  E               For more information, see the OpenVMS manual describing_"               the AUTOGEN utility.  H                              Preparing Your System for Installation 1-25    t      +      Preparing Your System for Installation ,      1.6 Installation Procedure Requirements  >      1.6.5 Disk Space on Your System Disk or Alternate Working            Devicei  E            This section discusses the disk space requirement for your A            kit working device during an Office Server Version 6.0             installation.  ?            The default disk for your kit working device is your D            system disk. If your system disk does not have sufficientC            space, you can specify an alternate working device (AWD) +            when you start the installation.   >            The disk space values for your kit are given in theC            documentation provided with your kit. You must check the C            disk space requirements on the target disks where OfficerC            Server Version 6.0 will be installed. See Section 1.6.7..  @            You can run the installation in either safety or non-            safety mode.   C               ________________________Note ________________________   A               Compaq recommends that you run your installation in (               safety mode (the default).  C               _____________________________________________________   ?            When you run the installation in safety mode, all ofDA            the Office Server Version 6.0 kit is restored onto theOB            system disk or AWD before the files are copied to theirB            target locations. This means that you need a disk space@            requirement greater than the total size of the OfficeE            Server Version 6.0 kit on your system disk. The disk space B            values for installing your kit in safety mode are givenD            in Appendix C, or the documentation that is supplied with%            your kit, if not US or GB.e  B            If you do not have enough disk space to run the instal->            lation in safety mode, you can run the installation@            in non-safety mode. In this case, each kit saveset isA            restored to the system disk before being copied to the @            target area. You need an amount of disk space on yourC            system disk greater than the size of the largest saveset_B            provided in the Office Server Version 6.0 kit. The diskB            space values for installing your kit in non-safety mode@            are given in Appendix C, or the documentation that is3            supplied with your kit, if not US or GB.   0      1-26 Preparing Your System for Installation _  _      H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  4         1.6.6 Using the OA$LIB_SHARE Disk as the AWD  F               If you have sufficient space on the target disk on whichF               OA$LIB_SHARE will reside, Compaq recommends that you useF               this disk as the AWD. If you do have sufficient space toG               install on this target disk, the installation time can beEH               reduced by approximately 20%. This is because the majorityC               of the Office Server files reside in the OA$LIB_SHARE_D               directory and therefore the installation procedure canE               move those files to their target directories by using a =               RENAME operation, rather than a COPY operation.e  @         1.6.7 Disk Space for Office Server Areas on Target Disks  H               You can install Office Server Version 6.0 in the following               ways:   (               o  On a single target disk  H               o  Across several target disks by installing Office Server)                  areas on separate disks.i  C               For upgrade installations, the installation proceduren@               assumes that the Office Server disks and top-levelG               directories for the Office Server areas have not changed,_G               and that the Office Server directory tree is the same. IfSF               you have moved any of the directories, you must put them?               back to their correct locations before upgrading.   E               You can install more than one Office Server area on the_F               same disk. If you do this, add the disk space values forE               the two areas together to find the total space requiredaG               on that disk. See Compaq Office Server Planning and Setup C               Guide for more information about Office Server areas.t  H               The disk space requirements for Office Server language andF               market areas that you are installing are provided in the3               documentation supplied with your kit.   E               To calculate the total disk space requirements for your D               installation, add together the disk space requirementsA               given in this section and the requirements given in D               Appendix C, or the documentation that is supplied with(               your kit, if not US or GB.  H                              Preparing Your System for Installation 1-27           +      Preparing Your System for Installationt,      1.6 Installation Procedure Requirements  B            The disk space requirements for each Office Server area.            are listed in the following tables:  B            o  Table 1-7 for a new installation. See Section 1.6.9.  H            o  Table 1-8 for an upgrade installation. See Section 1.6.10.  E            o  Table 1-9 for the addition, upgrade or update of VAX or =               Alpha architecture support. See Section 1.6.11.e  E               These values can also be used for the addition, upgrade A               or update of architecture support for an additionalo               language.   @            You are prompted to specify the target disks for each6            Office Server area during the installation.  0      1.6.8 Assigning Logical Names to Your Disks  B            Compaq recommends that you assign logical names to your             disks where possible.  C               ________________________Note ________________________   B               To avoid conflicts with system logical names, do not3               assign logical names that start with:                  o  A1$                 o  OA$                 o  OA1$h  C               _____________________________________________________e  C            In all types of installation, the installation procedureoC            checks for conflicting system and process logical names,hD            which could cause the installation to fail. You can check?            for conflicts before you start the installation. See B            Section 1.10 which describes how to run the Perform all.            preinstallation checks (PC) option.  D            The logical name checking includes a check for any exist-B            ing logical names that start with OA$. An informationalE            message lists the names found, and a warning message warns 9            you that these logical names may be redefined.   0      1-28 Preparing Your System for Installation           H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  C               If a logical name conflict is found, an informationallF               message is displayed. If the conflicting logical name isG               defined in a system table, you can remove the conflictingDD               logical name from another process, and then repeat theG               check. If the conflicting logical name is specific to the F               installing process, then you must abort the installationF               to fix the problem and then restart it. The installationC               will not continue until the logical name checking haso               passed.   E               For all upgrade or update installations, make sure that E               Office Server 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 ifBG               you are installing on a mixed architecture cluster as the.?               SYS$SYSDEVICE is different for each architecture.e  B         1.6.9 New Installation: Disk Space for Office Server Areas  H               Table 1-7 gives the disk space requirements for installingA               Office Server areas on the system and target disks.n  E               The disk space requirements given are those used duringaA               the installation. The permanent space used when theS>               installation has completed may be slightly less.  F                 ________________________Note  ________________________  A                 If you do not choose to integrate WPS-PLUS duringAA                 the installation, you can decrease the disk space @                 in the shared library area by approximately 6000                 blocks.U  @                 If you choose to integrate WPS-PLUS, but withoutA                 the associated PostScript files, you can decreaseo<                 the disk space in the shared library area by*                 approximately 3000 blocks.  E                 _____________________________________________________t        H                              Preparing Your System for Installation 1-29           +      Preparing Your System for Installationh,      1.6 Installation Procedure Requirements  C            Table 1-7 New Installation: Disk Space for Office ServerVE            __________Areas___________________________________________   E            Office_Server_Area_for_____VAX_________Alpha_______________  8            System disk files[1]       21 000      61 000  9            Shared library files       71 500      112 000   8            Shared data files          12 500      12 500  6            Shared areas[2]            1000        1000  6            Office Server Manager      1000        1000            account[3] E            [1]Space_required_to_provide_Office_Server_shared_files_tof  D            system directories. Add the value given in the Appendix CC            (or the documentation that is supplied with your kit, ifD0            not US or GB) to get the total value.?            [2]Multiply the disk space required by the number ofkC            shared areas you wish to create during the installation. A            [3]Includes all utility accounts, for example, IVP andT            POSTMASTER.E            __________________________________________________________s  D            For the disk space values for the primary language files,E            see Appendix C, or the documentation that is supplied with %            your kit, if not US or GB.y  C               ________________________Note ________________________i  B               Do not create the Office Server manager's account in<               a subdirectory of an OpenVMS system directory.  C               _____________________________________________________o  D      1.6.10 Upgrade Installation: Disk Space for Office Server Areas  D            Table 1-8 gives the disk space requirements for upgrading>            Office Server areas on the system and target disks.  B            The disk space requirements given are those used during>            the installation. The permanent space used when the;            installation has completed may be slightly less.v  B            The values given in the table assume that you choose toA            purge files during the installation. If you choose not.D            to purge replaced files, you must use the values given in            Table 1-7.   0      1-30 Preparing Your System for Installation y  m      H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  F                 ________________________Note  ________________________  A                 If you do not choose to integrate WPS-PLUS duringtD                 the installation, you can decrease the disk space in7                 the shared library area by 5000 blocks.t  ?                 If you choose to integrate WPS-PLUS without the =                 associated PostScript files, you can decreasekA                 the disk space in the shared library area by 2000                  blocks.i  E                 _____________________________________________________n  D               Table 1-8 Upgrade Installations: Disk Space for OfficeH               __________Server_Areas____________________________________  H               Office_Server_Area_for_____VAX_________Alpha______________  ;               System files[1]            10 500      61 000   <               Shared library files       14 500      112 000  9               Shared data files          2000        2000 H               [1]Space_required_to_provide_Office_Server_shared_files_to  G               system directories. Add the value given in Appendix C (or F               the documentation that is supplied with your kit, if not.               US or GB) to get the total valueH               __________________________________________________________  G               For the disk space values for the primary language files,IH               see Appendix C, or the documentation that is supplied with(               your kit, if not US or GB.  F         1.6.11 Addition of Architecture Support: Disk Space for Office                Server areas   E               Table 1-9 gives the disk space requirements for adding, F               upgrading or updating architecture support on the system-               and Office Server target disks.t  H               These values also apply to the addition, upgrade or updateA               or architecture support for an additional language.     H                              Preparing Your System for Installation 1-31    t      +      Preparing Your System for Installation ,      1.6 Installation Procedure Requirements  @            Table 1-9 Addition, Upgrade or Update of ArchitectureE            __________Support:_Disk_Space_for_Office_Server_Areas_____e  E            Office_Server_Area_for_____VAX___________Alpha____________e  :            System files[1]            21 000        61 000  :            Shared library files       48 500        95 000E            [1]Space_required_to_provide_Office_Server_files_to_systemr  A            directories. Add the value given in Appendix C (or theoE            documentation that is supplied with your kit, if not US orf%            GB) to get the total value E            __________________________________________________________d  D            For the disk space values for the primary language files,E            see Appendix C, or the documentation that is supplied with %            your kit, if not US or GB.r  !      1.6.12 Disk Quota Allocationl  D            If disk quota is enabled, the installation procedure addsE            sufficient disk quota for accounts and identifiers created #            during the installation.         1.6.13 Installed Images  ?            Make sure that the shareable image and message filesm@            listed in Table 1-10 are installed on your VAX systemC            and Table 1-11 are installed on your Alpha system before E            you install Office Server. Note that this list of required C            images applies to the versions of the products listed in             Table 1-2.   E            Table_1-10_Installed_Images_Required_on_VAX_______________e  E            Product_______Image_Required_on_VAX_______________________u  .            Always        SYS$SHARE:CONVSHR.EXE            required   2                          SYS$SHARE:CMA$TIS_SHR.EXE  /                          SYS$SHARE:DECC$SHR.EXEt  -                          SYS$SHARE:FDLSHR.EXE   E                                              (continued on next page)   0      1-32 Preparing Your System for Installation e  s      H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  H               Table_1-10_(Cont.)_Installed_Images_Required_on_VAX_______  H               Product_______Image_Required_on_VAX_______________________  2                             SYS$MESSAGE:FDVMSG.EXE  3                             SYS$SHARE:FDVSHR.EXE[1]   0                             SYS$SHARE:LBRSHR.EXE  0                             SYS$SHARE:LIBRTL.EXE  3                             SYS$SHARE:MTHRTL.EXE[2]d  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  H               __________________________________________________________  0               ACMS          SYS$SHARE:ACMSHR.EXE  H               __________________________________________________________  4               CDA           SYS$SHARE:CDA$ACCESS.EXE  8                             SYS$SHARE:IMG$SHRLIB_NOX.EXE  9                             SYS$SHARE:DDIF$CC_VIEWSHR.EXEl  H               __________________________________________________________  G               DATATRIEVE    SYS$SHARE:DTRSHR.EXE (the standard). If youdG                             are using another DATATRIEVE image that you E                             want to link with Office Server, you mustlH                             make sure that image is installed before the)                             installation.f  0                             SYS$SHARE:CDDSHR.EXE  3                             SYS$MESSAGE:DTRMSGS.EXEt  0                             SYS$SHARE:CDDEXC.EXE  H               [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.EXEm  H                                                 (continued on next page)  H                              Preparing Your System for Installation 1-33 f  d      +      Preparing Your System for Installation ,      1.6 Installation Procedure Requirements  E            Table_1-10_(Cont.)_Installed_Images_Required_on_VAX_______r  E            Product_______Image_Required_on_VAX_______________________e  E            __________________________________________________________c  2            DEC Notes     SYS$SHARE:NOTES$SHARE.EXE  E            __________________________________________________________n  2            Compaq X.500  SYS$SHARE:DXD$DUA_SHR.EXE  2                          SYS$SHARE:DXD$XDS_SHR.EXE  E            __________________________________________________________   3            The MAILbus   SYS$SHARE:MTA$XAPI_SHR.EXE             400 MTA  E            __________________________________________________________f  .            Message       SYS$SYSTEM:MRTALK.EXE            Router   E            __________________________________________________________a  2            TCP/IP        SYS$SHARE:UCX$IPC_SHR.EXE  E            __________________________________________________________t  1            WPS-PLUS [3]  SYS$SHARE:LCI$SCLHSP.EXE,E            [3]This_image_is_required_only_on_systems_that_have_the___y               German kit installed.E            ___________________________________________________________  E            Table_1-11_Installed_Images_Required_on_Alpha_____________y  E            Product__________Image_Required_on_Alpha__________________I  1            Always required  SYS$SHARE:CONVSHR.EXEm  5                             SYS$SHARE:CMA$TIS_SHR.EXE   2                             SYS$SHARE:DECC$SHR.EXE  2                             SYS$SHARE:DPML$SHR.EXE  0                             SYS$SHARE:FDLSHR.EXE  2                             SYS$MESSAGE:FDVMSG.EXE  E                                              (continued on next page)   0      1-34 Preparing Your System for Installation 5         H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  H               Table_1-11_(Cont.)_Installed_Images_Required_on_Alpha_____  H               Product__________Image_Required_on_Alpha__________________  6                                SYS$SHARE:FDVSHR.EXE[1]  3                                SYS$SHARE:LBRSHR.EXEu  :                                SYS$SHARE:LCI$SCLHSP_TV.EXE  3                                SYS$SHARE:LIBOTS.EXE   3                                SYS$SHARE:LIBRTL.EXEp  9                                SYS$SHARE:LIBRTL_TV.EXE[2]_  9                                SYS$SHARE:MTHRTL_TV.EXE[2]F  4                                SYS$SHARE:PAS$RTL.EXE  3                                SYS$SHARE:SCRSHR.EXEi  6                                SYS$SHARE:SECURESHR.EXE  7                                SYS$SHARE:SECURESHRP.EXE_  3                                SYS$SHARE:SMGSHR.EXEr  6                                SYS$SHARE:TIE$SHARE.EXE  :                                SYS$SHARE:VAXCRTL_TV.EXE[2]  =                                SYS$SHARE:VMS$IEEE_HANDLER.EXEt  H               __________________________________________________________  3               ACMS             SYS$SHARE:ACMSHR.EXEf  H               __________________________________________________________  7               CDA              SYS$SHARE:CDA$ACCESS.EXEi  <                                SYS$SHARE:DDIF$CC_VIEWSHR.EXE  ;                                SYS$SHARE:IMG$SHRLIB_NOX.EXEv  H               __________________________________________________________  H               [1]This_is_a_language-specific_image_which_can_have_a_____  8               different name on other language versions.@               [2]This is a logical which typically translates toE               something like the following example: LIBRTL_D56_TV.EXEi  H                                                 (continued on next page)  H                              Preparing Your System for Installation 1-35           +      Preparing Your System for InstallationS,      1.6 Installation Procedure Requirements  E            Table_1-11_(Cont.)_Installed_Images_Required_on_Alpha_____   E            Product__________Image_Required_on_Alpha__________________i  @            DATATRIEVE       SYS$SHARE:DTRSHR.EXE (the standard).?                             If you are using another DATATRIEVE C                             image that you want to link with Office_D                             Server, you must make sure that image is>                             installed before the installation.  0                             SYS$SHARE:CDDSHR.EXE  2                             SYS$MESSAGE:DTRMSGS.EX  0                             SYS$SHARE:CDDEXC.EXE  E            __________________________________________________________   5            DEC Notes        SYS$SHARE:NOTES$SHARE.EXE   E            __________________________________________________________f  5            Compaq X.500     SYS$SHARE:DXD$DUA_SHR.EXEo  5                             SYS$SHARE:DXD$XDS_SHR.EXE   E            __________________________________________________________   6            MAILbus 400 MTA  SYS$SHARE:MTA$XAPI_SHR.EXE  E            __________________________________________________________   5            TCP/IP           SYS$SHARE:UCX$IPC_SHR.EXE   E            __________________________________________________________   4            WPS-PLUS [3]     SYS$SHARE:LCI$SCLHSP.EXEE            [3]This_image_is_required_only_on_systems_that_have_the___r               German kit installed.E            __________________________________________________________n  D            To check which images are installed on your system, enter"            the following commands:              $ INSTALL"            INSTALL> LIST imagename+            imagename;       Open Shar Lnkblo  C            imagename is the directory and file specification of theY            image to be checked.   0      1-36 Preparing Your System for Installation o         H                                   Preparing Your System for InstallationH                                  1.6 Installation Procedure Requirements  F               If there is no entry for the image or the qualifiers areD               incorrect, you must install the image with the correct               qualifiers.                  To install:   E               o  SYS$MESSAGE:FDVMSG.EXE and SYS$SHARE:FDVSHR.EXE, seee                   Section 1.6.14.  2               o  Other images, see Section 1.6.15.  C               For more information about installing images, see the 4               manual describing the Install Utility.  :         1.6.14 Installing FDVMSG.EXE and FDVSHR.EXE Images  K               If the images SYS$MESSAGE:FDVMSG.EXE and SYS$SHARE:FDVSHR.EXE 2               are not installed, do the following:  H               1. Edit the command procedure SYS$STARTUP:FMSTARTUP.COM toG                  remove the EXIT command that appears before the entry:   '                  RUN SYS$SYSTEM:INSTALLq  H               2. Execute the command procedure SYS$STARTUP:FMSTARTUP.COM  &         1.6.15 Installing Other Images  .               Install other images as follows:                 $ INSTALLsA               INSTALL> CREATE imagename /OPEN /SHARED /HEADER_REST               INSTALL> EXITu  5         1.6.16 Checking The Location of DCLTABLES.EXEv  O               Check that DCLTABLES.EXE is in the directory SYS$COMMON:[SYSLIB].t@               If it is in a different directory, move it to this8               location before starting the installation.  C               To check if DCLTABLES.EXE is in the correct location,                enter:                 $ INSTALL A               INSTALL> LIST/FULL SYS$COMMON:[SYSLIB]DCLTABLES.EXES  >               If it is not in the correct location, remove it:  +               INSTALL> REMOVE DCLTABLES.EXE   H                              Preparing Your System for Installation 1-37 3  r      +      Preparing Your System for Installation ,      1.6 Installation Procedure Requirements  >            Move DCLTABLES.EXE to the correct location and then            replace it:  @            INSTALL> CREATE DCLTABLES.EXE /OPEN/SHARED/HEADER_RES  3      1.7 Additional Tasks for Upgrade Installations_  D            If you are upgrading an existing Office Server system, do            the following:   +            1. Review your object libraries.   @               Your object libraries may have been updated if youD               installed layered products. Office Server provides two?               template .OLB files in the following directories:A  3               -  OA$SITE_BUILD_SHARE:SITEOALIBR.OLBL  0               -  OA$SITE_BUILD_LLV:SITEOALLV.OLB  @               During the installation, a warning is displayed if>               there are additional .OBJ or .OLB files in theseE               directories. Check that any additional object libraries C               or files in this directory are compatible with Office_@               Server Version 6.0. Remove any object libraries orA               files that are not compatible. Although these filesHC               are not used during the installation, they will causeCD               problems if you need to relink Office Server after the               installation.   E            2. If you have a multilingual system, check that the files A               OA$LLV*.EXE are not in SYS$COMMON:[SYSLIB]. If they B               are, move them to the SYS$SYSROOT:[SYSLIB] directory               before upgrading.a  C            3. Check that all files in your site areas have at least E               system write access (S:W) and that Compaq Office Server C               directories in non-site areas also have system delete                access (S:D).E  F            4. Make copies of customized data files. See Section 1.7.1.        0      1-38 Preparing Your System for Installation n         H                                   Preparing Your System for InstallationH                           1.7 Additional Tasks for Upgrade Installations  +         1.7.1 Copying Customized Data Files   A               Office Server Version 6.0 uses modified versions of !               several data files:m  E               o  Files that have not been converted but their records :                  have changed or new ones have been added:                    o  CM$SDC  $                  o  CM$CART$RUNS.DAT                    o  FORMAT.DAT  )                  o  SM_UTILITY_MASTER.DAT_  B               Before upgrading, make copies of any data files thatC               you have customized as new versions of data files are D               provided with Office Server Version 6.0. You must alsoH               return the data files to the Compaq standard format before               you upgrade.  6         1.8 Using the MAILbus 400 MTA and Compaq X.500  D               You can install a new Office Server Version 6.0 systemC               with the MAILbus 400 MTA and Compaq X.500. You cannotEE               upgrade from ALL-IN-1 Version 3.1 using these products._  D               For a new Office Server Version 6.0 installation, withE               Compaq X.500 and the MAILbus 400 MTA you must make sure_F               that you have installed all the required MAILbus 400 MTAG               and Compaq X.500 components on your Office Server system, G               configured them and completed any additional setup tasks._G               See the checklist in the MAILbus 400 MTA and Compaq X.500nG               Planning chapter in the Compaq Office Server Planning andh               Setup Guide.  )         1.9 Using a Remote Message Routerm  F               If you will be using a remote Message Router that is not@               in the same VMScluster, you must do the following:  D               1. On the remote Message Router node, create an OfficeF                  Server mailbox for the node (or cluster) on which youA                  are installing Office Server. See Section 1.9.1.   C               2. Create an entry for the remote Message Router node F                  in the network nodes database on the local machine on8                  which you are installing Office Server.  H                              Preparing Your System for Installation 1-39 _         +      Preparing Your System for InstallationA&      1.9 Using a Remote Message Router  A            3. Ensure that Message Router is running on the remote B               node before you start the installation. If it is not@               running, you will see errors when the installationC               procedure starts up the Sender and Fetcher processes.   @      1.9.1 Create an Office Server Mailbox on the Remote Message            Router Node  >            Do this if you are planning to use a remote Message<            Router. If you do not create a mailbox before theD            installation, you will see problems when the installation@            procedure starts up the Sender and Fetcher processes.  C            Message Router must be running and configured before you "            start the installation.  A            If you are using a remote Message Router which is on a B            node in the same VMScluster as Office Server the Office*            Server mailbox name will be A1.  F            If the remote Message Router is not in the same VMScluster,>            other Office Server systems may be sharing the sameA            Message Router. The name of the Message Router mailboxCC            must be unique for your system. For example, the mailboxEB            name, mailboxname, could be localnodeA1 where localnodeB            is the name of the node or the cluster on which you areB            installing Office Server. password is the password thatB            you want to use for the Message Router mailbox. You are>            prompted for this password during the installation.  E            On the Message Router node, do the following to create theT!            Office Server mailbox:   !            $ RUN SYS$SYSTEM:MRMANeV            MRM> ADD mailboxname /PASSWORD=password /COMPLETE_MESSAGES /IGNORE_SENDER _<                 /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS            MRM> EXIT  ?            Note that you must not use the /OWNER qualifier whens"            setting up the mailbox.          0      1-40 Preparing Your System for Installation           H                                   Preparing Your System for InstallationH                            1.10 Running the Preinstallation System Check  5         1.10 Running the Preinstallation System Check   B               The Office Server Version 6.0 installation procedure@               provides a Perform all preinstallation checks (PC)G               option. Compaq recommends that you use this option beforeEE               installing Office Server Version 6.0 to ensure that you F               have made all necessary system changes before installing               the software.   E               You can use this option while an existing Office Server_G               system is running so you do not have to ask your users toU$               log out of the system.  B               The option for preinstallation checks allows you to:  F               o  Run the phase of the installation in which you answerB                  questions and the installation procedure performs                  system checks  E               o  Fix errors encountered by the installation procedure_  9               o  Exit without performing the installation   C               Where possible the installation checks are done in aniB               order which finds fatal errors first. Section 1.10.1>               describes the types of errors that are detected.A               Section 1.10.2 describes how to use the Perform alll1               preinstallation checks (PC) option.c  '         1.10.1 Types of Errors Reported   9               The following types of errors are detected:a                 o  Fatal errorsi  C                  These are errors which cannot be corrected withoutcB                  stopping the installation procedure. Fatal errors                  include:   B                  -  Errors that require the machine to be rebooted  B                  -  Errors that require an upgrade to prerequisiteC                     software, including OpenVMS, Message Router and H                     the Message Router VMSmail Gateway, or Compaq X.500,C                     the MAILbus 400 MTA and Message Router Gateway.M  !               o  Non-fatal errorsR  H                              Preparing Your System for Installation 1-41 s  S      +      Preparing Your System for Installationn2      1.10 Running the Preinstallation System Check  A               These are errors that can be corrected from anotherMB               process without stopping the installation procedure.'               Non-fatal errors include:   8               -  Shareable images that are not installed  3               -  Logical names that are not definedR  B               -  System parameters that can be changed dynamically  =               -  Prerequisite software files that are missing   (               -  Insufficient disk space  ?      1.10.2 Running the Perform all Preinstallation Checks (PC)              Option  E            To run the Perform all preinstallation checks (PC) option,NB            follow Steps 1 to 6 in Table 2-2 until you are prompted/            with a list of installation options.i  =            If you are migrating from MailWorks, the MailWorks B            migration tool is installed as part of the installation!            desribed in Table 2-2.s              Do the following:  8            1. Press Return to choose the default option.  C               ________________________Note ________________________   A               Choosing this option does not install the software.]  C               _____________________________________________________e  1               The following message is displayed:X  W                 The installation procedure allows you to perform the following actions:   .                 (I)   Perform the installation8                 (PC)  Perform all preinstallation checks  8               * Which action do you wish to perform [I]:  @            2. Choose the Perform all preinstallation checks (PC)%               option by entering: PC.a  B            3. If a check fails with an error that can be corrected>               without stopping the installation procedure, you?               are asked if you want to correct the error beforer               continuing.b  0      1-42 Preparing Your System for Installation d  s      H                                   Preparing Your System for InstallationH                            1.10 Running the Preinstallation System Check  G                  If you answer yes, the installation checking procedureeB                  pauses so that you can fix the error from anotherE                  process. When the error is fixed, you can resume thet6                  procedure, and the check is repeated.  A                  If you choose not to correct the error, you havevB                  the option of halting the procedure or continuingB                  to perform the remaining checks. If you choose toD                  continue, the installation procedure will terminate3                  when all the checks are performed.   >         1.11 Final System Preparation Tasks: New Installations  H               To prepare your system for a new Office Server Version 6.0-               installation, do the following:v  C               1. Check that all prerequisite software is installed,a(                  configured and running.  7               2. Start the queue manager, if necessary.w  B               3. Back up the system disk and any target disks. See                  Section 1.13.  B         1.12 Final System Preparation Tasks: Upgrade Installations  D               For an upgrade installation from Office Server VersionD               4.0, carry out the following steps before starting theC               installation. Each step is described in the following                sections.l  C               From the privileged SYSTEM account, do the following:t  =               1. Shut down Office Server. See Section 1.12.1.   G               2. Ensure that Message Router is running and is correctlyt                  configured.  H               3. Deinstall files in the site areas that are installed in,                  memory. See Section 1.12.2.  7               4. Start the queue manager, if necessary.   B               5. Back up the system disk and any target disks. See                  Section 1.13.  H                              Preparing Your System for Installation 1-43 r         +      Preparing Your System for Installation.?      1.12 Final System Preparation Tasks: Upgrade Installationsa  #      1.12.1 Shut Down Office Server   A            Ask users currently on the system to log out, and then0#            shut down Office Server.e  C               ________________________Note ________________________M  A               Office Server must not be used by any batch jobs or @               users during the installation, or the installation               will fail.  C               _____________________________________________________m  E            Do not allow anyone to log in again while the installationIC            is in progress. You can allow OpenVMS users to remain oneB            the system, but it is important to ensure that users doB            not use DCL HELP while the installation is in progress,D            as this can cause file locking problems when the DCL HELPC            library is updated during the installation. If possible, B            it is safer to ensure that there are no active users on            the system.  /      1.12.2 Deinstall Files Installed in Memoryu  E            If you have any files in the site areas that are installede@            in memory, for example, SITE$OA.A1$SECTION, deinstall@            them on all nodes in the cluster before you start theD            installation. Deinstalling files from memory will preventA            them from being write locked. The installation sets aneE            ACL on all files in the site areas so you must ensure thatuE            all files in the site area have system write access (S:W).gB            Make sure that you deinstall any of your own code-level:            executable images that are installed in memory.  .      1.13 Back Up Your System and Target Disks  D            Compaq recommends that you do a system disk backup before+            installing any software because:,  C            o  If a system failure occurs at a critical point duringrC               installation, your Office Server system could be leftc'               in an inconsistent state.   D            o  You can verify that the backup copy contains a workingD               system image and then replace the system disk with it.  0      1-44 Preparing Your System for Installation w         H                                   Preparing Your System for InstallationH                                1.13 Back Up Your System and Target Disks  B               o  There is more contiguous free space, which may be)                  needed for installation.   F               If you are going to install Office Server Version 6.0 onH               more than one disk, back up the target disks that you will               be using.s  D               Use the backup procedures that are established at yourG               site. For details on performing a system disk backup, see E               the section on the Backup Utility in the OpenVMS System                 Management Subkit.  E               At the beginning of the installation, VMSINSTAL asks if 2               you have backed up your system disk.                                                              H                              Preparing Your System for Installation 1-45    i                  H                                                                        2H         ________________________________________________________________  H            Installation Procedure: New, Upgrade and Architecture Support      B               This chapter describes the procedures for installingE               the Office Server Version 6.0 base, language and marketOH               components. The following installation examples are given:  F               o  A new installation of Office Server Version 6.0 on anH                  Alpha system with the MAILbus 400 MTA and Compaq X.500.!                  See Section 2.1.a  E               o  Upgrade installation of Office Server Version 5.0 tohF                  Office Server Version 6.0 with Message Router and theC                  Message Router Directory Service. The installation D                  is done on the Alpha system in a mixed-architectureC                  VMScluster, where Message Router is installed on a 2                  remote VAX node. See Section 2.1.  G               o  Addition or upgrade of additional architecture support E                  on a mixed-architecture VMScluster. See Section 2.2.t  F                 __________________Before  You Start __________________  A                 Do not start the installation until you have donee                 the following:  B                 1. Planned your installation by reading the Compaq:                    Office Server Planning and Setup Guide.  <                 2. Completed the system preparation tasks inC                    Chapter 1 to check that your system is ready forh$                    the installation.  E                 _____________________________________________________   G               Questions asked by installation procedure are marked with D               an asterisk (*) at the beginning of the line. For helpG               on answering a particular question, enter a question markt               (?).  H        Installation Procedure: New, Upgrade and Architecture Support 2-1    e      B      Installation Procedure: New, Upgrade and Architecture Support    E            During the installation procedure a number of cautions and E            general informational messages are displayed. Read all thecD            displayed messages carefully. Table 2-1 gives information6            which you may need during the installation.    E            Table_2-1_Information_About_the_Installation_Procedure____a  E            Question_________Answer___________________________________r  $            How long         On_AlphaA            will the         As an example, installing on an AlphanE            installation     4000-610 system takes about 1 hour and 15rD            take?            minutes for a full installation when the  E                             files are installed on an RZ28 disk using A                             an alternate working directory (AWD).   "                             On_VAX  A                             The installation can take from one to ?                             six hours, depending on the type of D                             processor you are using. The performance>                             specification of the disks has the<                             greatest effect. For example, anA                             installation on a VAX 4000-300 systemiD                             takes approximately 3.5 hours when filesA                             are installed on an RF71 disk and 1.5 C                             hours if files are installed on an RZ26i!                             disk.   C                             The times for new and upgrade installa-m=                             tions are approximately the same.   /            How do I get     Enter ? at any timel            help?  !            What is          A1060u            the product            identifier?  E                                              (continued on next page)d      F      2-2 Installation Procedure: New, Upgrade and Architecture Support _  _      H            Installation Procedure: New, Upgrade and Architecture Support    B               Table 2-1 (Cont.) Information About the InstallationH               __________________Procedure_______________________________  H               Question_________Answer___________________________________  @               What do I        Restart the installation from the8               do if the        beginning. See Chapter 4.               installation               fails before               the automatic                postinstalla-e               tion phase?u  ,               How do I         Press CTRL/Y.E               abort the        The installation procedure deletes alloB               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 remainpE                                there. Note: VMSINSTAL does not deleteeF                                any accounts, identifiers, or directory;                                structures that are created.h  8                                Restart the installation.  -               How do I         See Chapter 4.                restart the H               installation?_____________________________________________  D         2.1 Installation Procedure for New and Upgrade Installations  E               Table 2-2 lists all the installation steps for a new oraD               upgrade installation. The example scripts in the tableF               show extracts from a new installation on an Alpha systemG               using the MAILbus 400 MTA and Compaq X.500 and an upgrade F               installation from Office Server Version 5.0 with Message               Router.               H        Installation Procedure: New, Upgrade and Architecture Support 2-3 1  .      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationsn  G      Table_2-2_Installation_Procedure_for_New_and_Upgrade_Installations   E      Step__Action____________________________________________________   D      1     Create a log file for the installation. Compaq recommends@            that you keep a record of the installation in case ofC            problems. You can keep a log by using either a hard copynB            terminal or a log file. To keep a record in a log file,            enter:s  %            $  SET HOST 0/LOG=filename   C            where filename is the name of the log file. The log filetC            is created in the directory where you enter the command.e?            If you do not specify a filename, the file is called C            SETHOST.LOG. The installation log file will be about 200             blocks.  B            If you are running console management software, you can@            use this to record the installation. See your console<            management documentation for further information.  E      ________________________________________________________________   @      2     Load and mount the CD that contains the software kit.  E      ________________________________________________________________   B      3     Invoke the VMSINSTAL procedure from the SYSTEM account.  (            Enter the following commands:  #            $ SET DEFAULT SYS$UPDATE $            $ @VMSINSTAL A1060 device  >            To use an alternate working device (AWD), enter the#            following command lines:   #            $ SET DEFAULT SYS$UPDATEa5            $ @VMSINSTAL A1060 device OPTIONS AWD=disk   =            device is the device on which you have mounted theuB            distribution media. You can use a physical or a logicalD            device name but do not use logical device names beginningB            with A1$, OA$, or OA1$. A1060 is the product identifierD            and disk is the location of the alternate working device.  E      ________________________________________________________________o  E                                              (continued on next page)d  F      2-4 Installation Procedure: New, Upgrade and Architecture Support    e      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  (         4     Verify your system backup.  I                  OpenVMS VAX Software Product Installation Procedure V7.1   )               It is 19-JAN-2001 at 13:04.   =               Enter a question mark (?) at any time for help. L               * Are you satisfied with the backup of your system disk [YES]?  '               Press RETURN to continue. H               __________________________________________________________               For installationH               type__________________Go_to_______________________________  *               New                   Step 5  H               Upgrade_______________Step_8______________________________  H         ________________________________________________________________  @         5     New_Installation: Enter the number for the type of/               installation that you want to do.n  .               Logical OA$IMAGE is not defined.R               No Office Server image can be found using the default specification.  U               Using the FULL Office Server V6.0 kit, the following installation typesi                 can be performed:t  <                (1)  A new installation of Office Server V6.0  @                (RL) Register licenses for pre-requisite software  4                (MM) Install MailWorks Migration Tool  >               * Which installation do you wish to perform [1]:  <               Enter 1 to install a new Office Server system.  H         ________________________________________________________________  H                                                 (continued on next page)  H        Installation Procedure: New, Upgrade and Architecture Support 2-5 _  _      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationse  A      Table 2-2 (Cont.) Installation Procedure for New and UpgradeaE      __________________Installations_________________________________n  E      Step__Action____________________________________________________v  ?      6     New_Installation: Confirm that you want to start thes            installation.  V                The installation procedure allows you to perform the following actions:  -                (I)   Perform the installationv8                (PC)  Perform all pre-installation checks  5            * Which action do you wish to perform [I]:   2            Press RETURN to start the installation.  E      ________________________________________________________________l  D      7     New_installation: Specify whether you want a File Cabinet            only system.a  U            * Do you wish to install Office Server as a File Cabinet Only system [NO]?e  >            You should be aware that if you answer Y any future@            installation will take this option automatically. If,@            after installing Office Server as a File Cabinet onlyE            system, you want to revert to a full Office Server system, ?            you will need to contact your Compaq Support Center.   ?            Press RETURN to install a full Office Server system.   &            To_continue: go to Step 11.  E      _________________________________________________________________  E                                              (continued on next page)s                F      2-6 Installation Procedure: New, Upgrade and Architecture Support e  g      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  D         8     Upgrade_Installation: Enter the number for the type of/               installation you want to perform.n  ?               The current product image identification is V5.0.   U               Using the FULL Office Server V6.0 kit, the following installation types_                 can be performed:_  H                 (1)  Upgrade of Office Server V5.0 to Office Server V6.0  D                 (2)  Add, upgrade, or update Alpha components for an.                      Office Server V6.0 system  A                 (RL) Register licenses for pre-requisite software   5                 (MM) Install MailWorks Migration Tool8  @               * Which installation do you wish to perform [1]: ?  B               Enter 1 to upgrade an existing Office Server system.  G               If you are running Office Server in a single-architecture 9               VMScluster, you are not offered option (2).   H         ________________________________________________________________  F         9     Upgrade_Installation: 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 checks H                   (RC)  Run conflict checking and resolution tool (CART)  8               * Which action do you wish to perform [I]:  =               Press RETURN to continue with the installation.   H         ________________________________________________________________  H                                                 (continued on next page)  H        Installation Procedure: New, Upgrade and Architecture Support 2-7           B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationsl  A      Table 2-2 (Cont.) Installation Procedure for New and Upgrade E      __________________Installations_________________________________   E      Step__Action____________________________________________________   @      10    Upgrade_installation: Specify whether you want a File            Cabinet only system.t  B            This question is asked only for upgrades to full OfficeA            Server systems. If the system you last installed was aoD            File Cabinet only system, this question is not displayed.  U            * Do you wish to install Office Server as a File Cabinet Only system [NO]?   >            You should be aware that if you answer Y any future@            installation will take this option automatically. If,@            after installing Office Server as a File Cabinet onlyE            system, you want to revert to a full Office Server system, ?            you will need to contact your Compaq Support Center.   ?            Press RETURN to install a full Office Server system.t  E      ________________________________________________________________y  A      11    In some cases, the following licensing question may be             displayed:   V            %A1-I-NOLICENSE, No license PAK was found for this product so it is assumed  L            %A1-I-NOLICENSE, that you are using Client Access Licensing (CAL)  G            * Do you have enough CALs licenses to run this system? [YES]l  0            * How many CALs licenses do you have:  C            Enter the number of CALs licenses that you have for thisx            system.  E      ________________________________________________________________y  ?      12    Upgrade_Installation: Confirm that you want to purgea            files.   L            * Do you want to purge files replaced by this installation [YES]?  '            Press RETURN to purge files.r  E      ________________________________________________________________s  E                                              (continued on next page)a  F      2-8 Installation Procedure: New, Upgrade and Architecture Support l  o      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  F         13    If DATATRIEVE is already installed, indicate whether you>               want to integrate DATATRIEVE with Office Server.  T                DATATRIEVE can be integrated into Office Server.  On VAX systems with  W                Deferred image activation enabled the DATATRIEVE image will be deferred.h  Y                If you use the standard DATATRIEVE image SYS$SHARE:DTRSHR.EXE then you cann  X                select to dynamically activate DATATRIEVE.  You will still be able to use  R                DATATRIEVE within Office Server, but you will avoid any performance  R                impact of having it physically linked with the Office Server image.  L               * Do you want to integrate DATATRIEVE with Office Server [NO]?  F               Press RETURN if you do not want to integrate DATATRIEVE.  C               If you want to integrate DATATRIEVE, enter Y. You aremF               prompted to supply the name of the DATATRIEVE image thatB               you want to link with. If you are using the standardC               DATATRIEVE image, SYS$SHARE:DTRSHR.EXE, you are askedDG               if you want to dynamically activate DATATRIEVE during the C               Office Server startup. It is recommended that you do.   H         ________________________________________________________________  H                                                 (continued on next page)                      H        Installation Procedure: New, Upgrade and Architecture Support 2-9 r  e      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationso  A      Table 2-2 (Cont.) Installation Procedure for New and UpgradedE      __________________Installations_________________________________d  E      Step__Action____________________________________________________P  @      14    If you are using a license that allows WPS-PLUS (CALsE            licenses do not allow WPS-PLUS), indicate whether you want_E            to install WPS-PLUS with Office Server. If you do not havenC            a license which includes WPS-PLUS, you will not be asked             this question.   S                If you wish to have the WPS-PLUS editor available, answer YES to the   V                following question.  If you do not wish to install the WPS-PLUS editor,                  answer NO.r                  NOTE:  T                    o If WPS-PLUS is not installed then the WPS-PLUS linguistics aids  R                      (SPELL CHECKER and THESAURUS) and the WPS-PLUS SORT and MERGE  D                      processing functionality will not be available.  W                    o You will be able to do an Office Server update installation to add_  W                      WPS-PLUS at a later time, should you choose not to install it now._  E            * Do you want to install WPS-PLUS with Office Server [NO]?u  C            Enter YES to install WPS-PLUS. You are then asked if you A            want to install the graphics and page overlay samples:O  U                This kit contains a library of Encapsulated PostScript(R) graphics andh  U                PostScript(R) Page Overlay samples.  Their total size is approximatelyp  X                3,000 blocks when they are copied to the Office Server library directory.  L            * Do you want these graphics copied to the OA$LIB directory [NO]?  =            Press RETURN if you do not want to copy the files.d  %            Enter Y to copy the files.   E                                              (continued on next page)_  G      2-10 Installation Procedure: New, Upgrade and Architecture Support            H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  H         ________________________________________________________________  C         15    Indicate whether to you want to build a multilanguagem               system.   \                   If you wish to use more than one Office Server 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.s  E               Enter Y if you plan to install additional languages and_7               you want to build a multilanguage system.a  H         ________________________________________________________________  H                                                 (continued on next page)                                        H       Installation Procedure: New, Upgrade and Architecture Support 2-11 s  t      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationsi  A      Table 2-2 (Cont.) Installation Procedure for New and UpgradeuE      __________________Installations_________________________________e  E      Step__Action_____________________________________________________  (      16    Select a default date format.  Y                Office Server allows you to select a default date format for each language   Y                you have installed. This will become the default Office Server date format   S                for each user (on a per language basis.) This may be changed by each   U                user through the Set Working Conditions option on the User Setup Menu.t  4                    Alphanumeric Date    Numeric Date  H                    1   DD-MMM-YYYY      MM/DD/YY      (Standard Default)  0                    2   DD-MMM-YYYY      DD/MM/YY0                    3   DD-MMM-YYYY      YY/MM/DD0                    4   YYYY-MMM-DD      MM/DD/YY0                    5   YYYY-MMM-DD      DD/MM/YY0                    6   YYYY-MMM-DD      YY/MM/DDB                    7   ***** Reserved (Means system default) *****F                    8   DD-MM-YYYY       DD/MM/YY      (Numeric format)  F                    9   MM-DD-YYYY       MM/DD/YY      (Numeric format)  2            * Which date format do you require [1]:  E            Press RETURN to use the default format or enter the numberR4            for the date format that you want to use.  E      ________________________________________________________________   E                                              (continued on next page)g                G      2-12 Installation Procedure: New, Upgrade and Architecture Supporti    g      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  G         17    Specify the greatest number of simultaneous Office Servera               users.  G               * What will be the greatest number of simultaneous users:   "               Upgrade_installation  B               A default value is given. Press RETURN to accept the               default value.                 New_installation  D               Specify the maximum number of Office Server users thatF               you expect at any one time. (This principally affects VTD               access.) The installation procedure uses this entry toF               check that system parameters are large enough to support,               your intended number of users.  H         ________________________________________________________________  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 namet)               of an existing batch queue.o  9               For_an_upgrade_installation: Go to Step 21.i  H         ________________________________________________________________  H                                                 (continued on next page)          H       Installation Procedure: New, Upgrade and Architecture Support 2-13    a      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationsw  A      Table 2-2 (Cont.) Installation Procedure for New and UpgradeRE      __________________Installations__________________________________  E      Step__Action____________________________________________________s  A      19    New_installation: Specify batch queue for starting the D            AIDA, File Cabinet, POP3 and IMAP Servers, and the Sender!            and Fetcher processes.1  L            * A running batch queue on this node is needed to start the Aida,  W              File Cabinet, POP3 and IMAP Servers, and the Sender and Fetcher processes.c  L            It is suggested that a separate queue is used for this, which the  0            installation will create if you wish.  D            * Do you want OA$SERVER_START_nodename to be created [Y]?  A            If you answer N, the installation returns this prompt:   7            * Which queue do you want to use? [default]:i  @            Press RETURN to accept the default queue or enter theC            name of an existing batch queue on this node that is not 1            generic and that is currently running.t  ?            The queue that you specify will be added to the NodedB            Specific Batch Queue Master file, and will be stored in@            the configuration files of any Servers created during@            this installation. You can change the queue later, or@            add queues for other nodes in your cluster, using theC            Manage node specific queues (MNQ) option from the System             Management menu._  E      ________________________________________________________________V  E                                              (continued on next page)r              G      2-14 Installation Procedure: New, Upgrade and Architecture SupportO c  e      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  A         20    New_installation: Specify whether you are migratingdF               from MailWorks, and, if you are, whether you want to use%               MailWorks folder names.   O               If you are not migrating from a MailWorks system, press Return to                  continue.a  T               If you are migrating from a MailWorks system, you may wish to continue  V               to use the default MailWorks folder names. If so, please type "?" to see  9               the help before answering the next questione  E               *Do you want to use the default MailWorks folder names?h  H               Enter Y if you want to use default MailWorks folder names.  H         ________________________________________________________________  H                                                 (continued on next page)                                      H       Installation Procedure: New, Upgrade and Architecture Support 2-15 s  l      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installations(  A      Table 2-2 (Cont.) Installation Procedure for New and Upgrade_E      __________________Installations_________________________________o  E      Step__Action____________________________________________________o  D      21    Indicate if you want to send and receive remote mail. TheE            installation procedure checks the type and versions of the D            message transport and directory service software that are$            installed on your system.  P            Electronic Messaging can be used to send and receive messages, to and  N            from other computer systems using either the MAILbus 400 or Message              Router products.h  J            * Do you want to be able to send and receive remote mail [YES]?  7            Press RETURN if you want to use remote mail.S  A            If you answer NO to this question, Office Server usersSD            will only be able to exchange messages locally with other-            users on the same computer system.   E            __________________________________________________________iE            If_You_______________________________Go_To________________   7            Do not want to use remote mail       Step 29t  7            Are installing a new Office Server   Step 22E+            system with Compaq X.500 and thek            MAILbus 400 MTA  E            Are_upgrading_with_Message_Router____Step_23______________   E      ________________________________________________________________   E                                              (continued on next page)x              G      2-16 Installation Procedure: New, Upgrade and Architecture Supportr i  t      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  B         22    New_Installation with the MAILbus 400 MTA and CompaqE               X.500: Confirm that you want to use the MAILbus 400 MTAa               for remote mail.  S                 If you plan to use MAILbus 400 as your MTA, then answer YES to this_  O                 question. You will not have been offered this choice unless the_  P                 installation checks have revealed that the product is installed.  W                 Note that even though MAILbus 400 appears to be installed and initially   V                 configured, it is unlikely that it will successfully process your mail  W                 until you have completed all the set up tasks described in the PlanningM                    and Setup Guide.  X                 If you answer NO to this question, Office Server users will only be able  S                 to exchange messages locally, unless you subsequently choose to useo  4                 Message Router (if it is available.)  E               * Do you want to use MAILbus 400 for remote mail [YES]?   F               Press RETURN to use the MAILbus 400 MTA for remote mail.  H               It does not make any difference to the installation if theE               MAILbus 400 MTA is installed on the same node as OfficeNG               Server or on a different node in the same VMScluster on a F               remote node outside the cluster, providing that you haveG               completed all the configuration and set up tasks that are_D               covered in the Compaq Office Server Planning and Setup               Guide.  )               To_continue: Go to Step 26.f  H         ________________________________________________________________  H                                                 (continued on next page)  H       Installation Procedure: New, Upgrade and Architecture Support 2-17 a  r      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installations   A      Table 2-2 (Cont.) Installation Procedure for New and Upgrade E      __________________Installations_________________________________   E      Step__Action____________________________________________________   E      23    Upgrade_Installation: Confirm that you want to use Message "            Router for remote mail.  ?            Office Server on a VAX node can be configured to use @            a local Message Router which is installed on the sameB            node or a remote Message Router which is installed on aB            different node. Office Server on an Alpha node can onlyA            use a remote Message Router. This example script is oneC            an Alpha system so it must be configured to use a remotef            Message Router.  T            * Do you want Office Server to be configured to use Message Router [YES]?  C            Answer Y to confirm that you want to use Message Router.g  E      ________________________________________________________________i  C      24    Upgrade_Installation: If Message Router is not installed >            on this node, confirm that you want to use a remote            Message Router.  >            * Do you want to use a remote Message Router [YES]?  C            Enter Y to confirm that you want to use a remote Message_            Router.  A            Note that the default value for this answer depends on_B            whether you are doing the upgrade installation on a VAXB            system or an Alpha system. In this example, the upgradeC            is on an Alpha system, so the default is to use a remoted            Message Router.  E      ________________________________________________________________e  E                                              (continued on next page)h          G      2-18 Installation Procedure: New, Upgrade and Architecture Supporti    i      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  H         25    Upgrade_Installation: Enter the name of the remote Message               Router node.  3               * What node is the Message Router on::  E               Enter the DECnet node name of the remote Message Routerm               node.a  A               Note that the remote Message Router node must be in:A               the network nodes database on the node on which you_E               are installing Office Server. As this is an upgrade you E               will not be asked for a password for the Message Routere               mailbox.  "               Additional_Questions  C               If you are installing a new Office Server system withIF               Message Router, you are prompted to enter a password for)               the Message Router mailbox.n  @               * Enter a password for the Message Router mailbox:?               * Please confirm the password that you specified:_  B               The password must be a minimum of 8 characters and a=               maximum of 32 characters. Confirm the password.   H         ________________________________________________________________  H                                                 (continued on next page)                      H       Installation Procedure: New, Upgrade and Architecture Support 2-19 I  s      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade InstallationsO  A      Table 2-2 (Cont.) Installation Procedure for New and UpgraderE      __________________Installations_________________________________d  E      Step__Action____________________________________________________e  E      26    Indicate the type of Mail Directory support that you want.h  >            For new installations where Compaq X.500 or an LDAP;            directory service is installed, the following is             displayed:   A            * What type of Mail Directory support do you want [X]:t  ?            The options that are available depend on the type ofi?            directory service software that is installed on yourdE            system. You are given the appropriate options and defaultsoC            from the following list, depending on what is installed.n  D            Press RETURN to accept the default or enter the value for<            the type of Mail directory support that you want.E            __________________________________________________________ E            For__________________________________Option_to_Enter______l  1            No Mail directory support            0t  1            The Message Router Directory         MU(            Service as the Mail directory  1            The Compaq X.500 Directory Service   X              as the Mail directory  1            An LDAP Directory Service as the     L_E            Mail_directory____________________________________________0  A            When you are installing with Compaq X.500, it does not ?            matter whether Compaq X.500 is installed on the same @            node as Office Server or on a remote node outside theB            cluster, providing that you have done all the necessaryD            setup and configuration tasks as outlined in the Overview            and Planning Guide.  A            If_you_have_specified_no_Mail_directory_support, go toe            Step 29.   E      ________________________________________________________________   E                                              (continued on next page)   G      2-20 Installation Procedure: New, Upgrade and Architecture Support_ _  _      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  F         27    Specify if you want the Mail directory to be the primary               directory.  P               * Do you want the Mail Directory to be the primary directory [NO]?  E               Press RETURN to use the Mail directory as the secondaryu               directory.  2               For new installations go to Step 29.  H         ________________________________________________________________  H         28    Installation_with_Message_Router: Enter a password for the?               Mail Directory User Agent account and confirm it.s  C               The text that is displayed depends on whether you areLE               using a remote Message Router, and whether that MessageoF               Router is in the same VMScluster. Read the informational=               messages carefully and follow the instructions.o  B               The password length must between 6 and 8 characters.  :               * Press RETURN to continue the installation:U               * Enter a password for the Message Router Directory user agent account:_  @               * Please confirm the password which you specified:  A               Press RETURN and then enter a password for the Maili:               Directory user agent account and confirm it.  H         ________________________________________________________________  H                                                 (continued on next page)              H       Installation Procedure: New, Upgrade and Architecture Support 2-21           B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationsr  A      Table 2-2 (Cont.) Installation Procedure for New and UpgraderE      __________________Installations_________________________________r  E      Step__Action____________________________________________________P  ?      29    Indicate if you want outgoing messages translated ton            ASCII._  J            * Do you want to translate all outgoing messages to ASCII [NO]?  <            Press RETURN if you do not want outgoing messages            translated.  C                     _____________________Note _____________________   =                     If you are using a remote MAILbus 400 MTAM<                     on Tru64 UNIX, you must answer Y to this@                     question if WPS-PLUS to ASCII converters areA                     not installed on the MAILbus 400 MTA node andpA                     you want to exchange messages with non-Officeu!                     Server users.n  C                     _______________________________________________c  E            Enter Y, if you want outgoing messages translated. You arelC            then asked if you want all attachments to be translated.e  C            * Do you want to translate all message attachments [NO]?   C            Press RETURN if you do not want to translate all messagelD            attachments. If you enter Y to this question, all messageA            attachments are translated to ASCII if the appropriateuA            converters are installed on your Office Server system.N  E      ________________________________________________________________         30    System checking.a  C            The installation procedure checks mandatory and optionaln>            software prerequisites. You may be asked additional@            questions depending on the software and licenses that(            are installed on your system.  >            If the prerequisite software for CDA support is not?            installed, you are asked if you want to continue thep,            installation without CDA support.  E                                              (continued on next page)_  G      2-22 Installation Procedure: New, Upgrade and Architecture Support  n  u      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  H         ________________________________________________________________  D         31    Indicate if you want client applications to connect to:               Office Server using TCP/IP network protocol.  E               You are only asked the following question if DEC TCP/IPMH               Services (formerly 'UCX') or other TCP/IP network software;               that emulates it is installed on your system.n  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 ServerF               and Office Server File Cabinet Server are not registered0               in the Internet Services database.  ?               * Enter a port number for the AIDA Server [7300]: U               * Enter a port number for the Office Server File Cabinet Server [7373]:s  C               Enter a different TCP/IP port number for each server..E               The port numbers can be in the range 1024 to 65535. You D               must use the default values if you are planning to use(               TeamLinks client software.  C               The installation procedure checks that the TCPIP$IPC_eH               SHR.EXE image is installed. If it is not, you must installH               it after the installation. (In case the system uses a pre_G               v5.0 product, and uses the old filename, the installation_A               also checks for UCX$IPC_SHR.EXE if it does not find !               TCPIP$IPC_SHR.EXE.)   H         ________________________________________________________________           32    System checking.  B               The installation procedure checks system parameters,G               quotas and identifiers. For new installations, the OfficeUE               Server identifiers are created. The identifiers alreadye.               exist for upgrade installations.  H                                                 (continued on next page)  H       Installation Procedure: New, Upgrade and Architecture Support 2-23 a  n      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationsn  A      Table 2-2 (Cont.) Installation Procedure for New and Upgrade E      __________________Installations_________________________________e  E      Step__Action____________________________________________________   E      ________________________________________________________________   #      33    Enter the language code.s  I            * Enter language code for this installation (2 characters): USn  ?            Enter the two-letter language code for your languagerA            component. In this example, US is the ENGLISH language              code. See Appendix D.  E      ________________________________________________________________e  E                                              (continued on next page)t                                                      G      2-24 Installation Procedure: New, Upgrade and Architecture Support  f         H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  D         34    If your language kit contains a dialect component, you6               will be asked to 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.H               If your language kit does not contain a dialect component,.               you 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,   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.a  U               * Enter dialect code for this installation (5 characters) [NO_DIALECT]:h  E               Press RETURN or enter the dialect code that you want to_"               use. See Appendix D.  H               The installation procedure continues with system checking.H               __________________________________________________________               For installationH               type__________________Go_to_______________________________  +               New                   Step 35D  H               Upgrade_______________Step_36_____________________________  H         ________________________________________________________________  H                                                 (continued on next page)        H       Installation Procedure: New, Upgrade and Architecture Support 2-25           B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationsa  A      Table 2-2 (Cont.) Installation Procedure for New and UpgradeoE      __________________Installations__________________________________  E      Step__Action____________________________________________________   ?      35    New_Installation: Specify the devices for the OfficenC            Server areas. The initial default is the non-system disk             with the most space.w  K            * Which device will hold the Office Server shared library files:N  Y            * Which device will hold the Office Server shared data files       [A1DISK1:]:U  Y            * Which device will hold the Office Server ENGLISH language files  [A1DISK1:]:t  Y            * Which device will hold the Office Server mail area SDAF file     [A1DISK1:]:u  C            * How many shared directories do you want to create [1]: Y            * Which device will hold the Office Server shared directory SHARE1 [A1DISK1:]:   Y            * Which device will hold the Office Server lexicon files           [A1DISK1:]:   D            For shared directories, Compaq recommends that you selectA            the default value at installation time and then create @            additional shared directories after the installation,B            following the instructions in the DIGITAL Office Server7            Managing from a VT Terminal (the V4.0 book).o  B            If lexicon files have already been installed by another@            product, you are not asked the question about lexicon            files.   E      ________________________________________________________________   E                                              (continued on next page)                     G      2-26 Installation Procedure: New, Upgrade and Architecture SupportR e  i      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  H         36    Enter the market code. (This is defaulted for an upgrade.)  J               * Enter market code for this installation (2 characters): US  H               Enter the two-letter market code for the installation. See               Appendix D.2H               __________________________________________________________H               Installation_type_____Go_to_______________________________  +               New                   Step 37_  H               Upgrade_______________Step_44_____________________________  H         ________________________________________________________________  G         37    New_Installation: Specify an OpenVMS account and passwordsB               for the Office Server 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 ...  N                     Creating an OpenVMS account for the Office Server manager.  Z               * What OpenVMS username do you want to use for Office Server Manager account                 [OFFICE]: G               * Enter a password for the Office Server Manager account:E  @               * Please confirm the password which you specified:  H         ________________________________________________________________  H                                                 (continued on next page)            H       Installation Procedure: New, Upgrade and Architecture Support 2-27 r  t      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installations   A      Table 2-2 (Cont.) Installation Procedure for New and Upgrade_E      __________________Installations_________________________________   E      Step__Action____________________________________________________f  A      38    New_Installation: Enter a system group UIC and defaults>            device and directory for the Office Server manager.A            Do not create the Office Server manager's account in ao7            subdirectory of an OpenVMS system directory.   K            * What UIC do you want to use for Office Server Manager account:   [            * What default device do you want to use for the Office Server Manager's accountP                [A1DISK1:]A[            * What default directory do you want to use for Office Server Manager's account?t                [OFFICE:]  E      ________________________________________________________________   E      39    New_Installation: Enter a UIC for the accounts used by the_D            Transfer User utility. The UIC must not be a system group            UIC._  @            * What UIC do you want to use for A1$XFER_IN account:E            * What UIC do you want to use for the A1$XFER_OUT account:   E      ________________________________________________________________f  @      40    New_Installation: Enter a UIC for the account used byD            the Script Symbiont utility. The UIC must not be a system            group UIC.o  E            * What UIC do you want to use for SCRIPT SYMBIONT account:   E      ________________________________________________________________   E                                              (continued on next page)             G      2-28 Installation Procedure: New, Upgrade and Architecture Supportd u  s      H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  C         41    New_Installation: Enter a UIC for the account used by5G               the File Cabinet Server for authenticating remote clientsuF               into a non-privileged account, and a UIC for the accountG               used for running the Office Server File Cabinet Server as E               a detached process. . The UICs must not be system groupe               UICs.s  E               * What UIC do you want to use for OAFC$DEFAULT account:lD               * What UIC do you want to use for OAFC$SERVER account:  H         ________________________________________________________________  H         42    New_Installation: If you are prompted, enter a UIC for theE               WEB$ACCESS account. You are prompted only if WEB$ACCESSt%               does not already exist.d  H               WEB$ACCESS is created automatically in a new installation.G               The account is used to control access to the File CabinetrG               drawers by the Compaq Office Server Web Interface and thenG               IMAP and POP3 Servers. The WEB$ACCESS account is not usedcD               for interactive logins, so you will not be asked for a               password.e  C               * What UIC do you want to use for WEB$ACCESS account:i  H         ________________________________________________________________  H                                                 (continued on next page)                        H       Installation Procedure: New, Upgrade and Architecture Support 2-29 _  _      B      Installation Procedure: New, Upgrade and Architecture SupportA      2.1 Installation Procedure for New and Upgrade Installationsr  A      Table 2-2 (Cont.) Installation Procedure for New and UpgraderE      __________________Installations_________________________________n  E      Step__Action_____________________________________________________  B      43    New_Installation: Specify the top-level directories for#            the Office Server areas.   L            * Enter top-level directory required for the shared library files                [OFFICE]:I            * Enter top-level directory required for the shared data filesr                [OFFICE]:N            * Enter top-level directory required for all ENGLISH language files                [OFFICE]:K            * Enter top-level directory required for the mail area SDAF file_                [OFFICE]:S            * Enter the name required for the SHARED DIRECTORY on A1DISK1: [OFFICE]:_  %            Go to Step 46 to continue.a  E      ________________________________________________________________   C      44    Upgrade_Installation: Enter the OpenVMS username for thec+            Office Server manager's account.p  P            * What is the existing OpenVMS username for the Office Server account                [ALLIN1]:  D            Enter the OpenVMS username for the Office Server account.-            The account details are displayed.G  E      ________________________________________________________________e  @      45    Upgrade_Installation: Confirm that the details of the7            Office Server manager's account are correct.   K            * Are all the specified account's characteristics correct [YES]?   :            Press RETURN if all the information is correct.  E      ________________________________________________________________   E                                              (continued on next page)L  G      2-30 Installation Procedure: New, Upgrade and Architecture Supportt _         H            Installation Procedure: New, Upgrade and Architecture SupportH             2.1 Installation Procedure for New and Upgrade Installations  D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeH         __________________Installations_________________________________  H         Step__Action____________________________________________________  A         46    If you choose to, you can run the IVP (Installation_&               Verification Procedure).  G               * Do you want to run the IVP after the installation [NO]?g  1               Enter Y if you want to run the IVP.e  E               All the installation questions have now been completed.:  B               If you are installing Office Server Version 6.0 on a@               mixed-architecture VMScluster, see Section 2.2 forF               instructions on adding architecture support for a second               architecture._  @               If you are not installing on a single-architectureH         ______VMScluster,_go_to_Section_2.3.____________________________  4         2.2 Adding or Upgrading Architecture Support  G               Table 2-3 explains when you can do an installation to addW.               or upgrade architecture support.  I               Table 2-3 When to Install/Upgrade VAX or Alpha ArchitecturedH               __________Support_________________________________________  H               Install/Upgrade_______When_you_have_already_done__________  B               VAX architecture      A new or upgrade Office ServerH               support               Version 6.0 installation on an AlphaA                                     system in the same VMSclustery  B               Alpha architecture    A new or upgrade Office ServerE               support               Version 6.0 installation on a VAXiH               ______________________system_in_the_same_VMScluster.______  D               The questions that you are asked during the additionalH               architecture installation depend on the responses that youG               gave during the new or upgrade installation. For example,4G               if you did not install WPS-PLUS during the new or upgradeaF               installation, you are not asked any additional questions               about WPS-PLUS._  H       Installation Procedure: New, Upgrade and Architecture Support 2-31           B      Installation Procedure: New, Upgrade and Architecture Support1      2.2 Adding or Upgrading Architecture SupportA        2.2.1 Before You Start   =            Before you start the installation, you must do theu            following:   @            1. If you are installing architecture support for theC               first time, make a note of the location of the Office D               Server configuration file, OA$DATA_SHARE:A1CONFIG.DAT,B               on the system where you have already installed a new@               Office Server Version 6.0 system or upgraded to anE               Office Server Version 6.0 system. You will be asked fort7               this information during the installation.t  C            2. Run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP, to :               check for logicals containing SYS$SYSDEVICE.  B            3. From the Office Server manager's account on the node?               where Office Server is already installed, run the 8               script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP:  '               $ SET HOST 0/LOG=filename_#               $ OFFICESERVER/NOINIT_=               Enter CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCPa  >               If references to SYS$DEVICE are found, a warningB               message is displayed. You must remove the references>               as they will refer to different devices on a VAXC               system and an Alpha system. If the references are nott9               corrected, data may be lost on your system.g  ?               The installation procedure also runs this script.   A      2.2.2 Installation Procedure for Adding Architecture Supporta  ?            Table 2-4 shows an example script for an additional-dC            architecture installation on a VAX system. The followingn            information is used:f  B            o  Office Server Version 6.0 is already installed on an2               Alpha system in the same VMScluster.  8            o  WPS-PLUS is installed on the Alpha system.  B            o  Office Server has been configured as a multilanguage)               system on the Alpha system.r  =            o  Message Router is installed on this VAX system.   G      2-32 Installation Procedure: New, Upgrade and Architecture Supportd           H            Installation Procedure: New, Upgrade and Architecture SupportH                             2.2 Adding or Upgrading Architecture Support  A               The example includes the script for both adding VAX C               support for the first time and upgrading existing VAXeH               support. The installation questions and script are similar;               for the addition or upgrade of Alpha support.       @         Table 2-4 Installation Procedure for Adding ArchitectureH         __________Support_______________________________________________  H         Step__Action____________________________________________________  /         1 to  Follow Steps 1 to 5 in Table 2-2.nH         5     __________________________________________________________H               For_Installation_Type________________Go_to________________  9               Upgrade                              Step 6e  H               New__________________________________Step_7_______________  H         ________________________________________________________________  D         6     Upgrade_Installation: Enter the number for the type of/               installation you want to perform._  ?               The current product image identification is V5.0.t  U               Using the FULL Office Server V6.0 kit, the following installation types                  can be performed:I  E                 (1)  Upgrade Office Server V5.0 to Office Server V6.0_  B                 (2)  Add, upgrade, or update VAX components for an.                      Office Server V6.0 system  A                 (RL) Register licenses for pre-requisite softwared  5                 (MM) Install MailWorks Migration Toolt  >               * Which installation do you wish to perform [1]:  D               Press RETURN to upgrade VAX components for an existingH               Office Server Version 6.0 system that is already installed8               on an Alpha system in the same VMScluster.  (               To_Continue: Go to Step 8.  H                                                 (continued on next page)  H       Installation Procedure: New, Upgrade and Architecture Support 2-33 n  a      B      Installation Procedure: New, Upgrade and Architecture Support1      2.2 Adding or Upgrading Architecture Supportt  E      Table 2-4 (Cont.) Installation Procedure for Adding ArchitecturesE      __________________Support_______________________________________   E      Step__Action____________________________________________________   E      _________________________________________________________________  =      7     New_Installation: Enter the number for the type of ,            installation you want to perform.  +            Logical OA$IMAGE is not defined.EI            No product image can be found using the default specification.r  R            Using the FULL Office Server V6.0 kit, the following installation types              can be performed:  9             (1)  A new installation of Office Server V6.0r>             (2)  Add, upgrade, or update VAX components for an+                   Office Server V6.0 system   =             (RL) Register licenses for pre-requisite softwareu1             (MM) Install MailWorks Migration Tool   =            * Which installation do you wish to perform [1]: 2u  3            Enter 2 to add VAX architecture support._  E      ________________________________________________________________   ;      8     Confirm that you want to start the installation.l  V                The installation procedure allows you to perform the following actions:  -                (I)   Perform the installationo8                (PC)  Perform all pre-installation checks  6            *  Which action do you wish to perform [I]:  2            Press RETURN to start the installation.  /            Upgrade_Installation: Go to Step 10.S  E      ________________________________________________________________4  E                                              (continued on next page)t  G      2-34 Installation Procedure: New, Upgrade and Architecture Support            H            Installation Procedure: New, Upgrade and Architecture SupportH                             2.2 Adding or Upgrading Architecture Support  H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureH         __________________Support_______________________________________  H         Step__Action____________________________________________________  ?         9     New_Installation: Supply the location of OA$DATA_ G               SHARE:A1CONFIG.DAT, the Office Server configuration file,_C               for Office Server Version 6.0 on the existing system.t  U                   You have chosen an architecture only installation.  To continue you   R                   must specify the location of the existing system's configuration  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]  H               Enter the location of the Office Server configuration fileG               in the format, disk:[directory]. You must always use thisd:               format to specify the location of this file.  D               The installation script uses the configuration file to               define logicals.  I               %A1-I-DEFLOG, Running A1V60START.COM to define the logicalsn  O               -A1-I-DEFLOG, from your existing Office Server V5.0 Alpha system.r  :                Defining language independent logical names  6                Defining ENGLISH language logical names  H         ________________________________________________________________  D         10    Where possible, the VAX architecture-only installation@               matches the configuration of Office Server that isF               already installed on the Alpha system. The informationalE               messages that are displayed will depend on the existingi               configuration.  H         ________________________________________________________________  H                                                 (continued on next page)  H       Installation Procedure: New, Upgrade and Architecture Support 2-35    i      B      Installation Procedure: New, Upgrade and Architecture Support1      2.2 Adding or Upgrading Architecture Supportd  E      Table 2-4 (Cont.) Installation Procedure for Adding Architecture E      __________________Support_______________________________________   E      Step__Action____________________________________________________   ?      11    Upgrade_Installation: Confirm that you want to purgel            files.   L            * Do you want to purge files replaced by this installation [YES]?  $            Press RETURN to continue.  E      _________________________________________________________________  D      12    System checking for existing Office Server configuration.  =            The informational message depends on your existing &            configuration, for example:  R               During your Office Server installation on Alpha you chose to install  T               Office Server with WPS-PLUS, therefore WPS-PLUS will also be installed  =               during this VAX architecture only installation.p  E      _________________________________________________________________  D      13    System checking for existing Office Server configuration.  =            The informational message depends on your existing &            configuration, for example:  >               Office Server on the Alpha is linked as a MULTI-            LANGUAGE system, N               therefore Office Server on this VAX will also be linked the same                 way.  E      _________________________________________________________________  E                                              (continued on next page)-        G      2-36 Installation Procedure: New, Upgrade and Architecture Supporto           H            Installation Procedure: New, Upgrade and Architecture SupportH                             2.2 Adding or Upgrading Architecture Support  H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureH         __________________Support_______________________________________  H         Step__Action____________________________________________________  G         14    Specify the greatest number of simultaneous Office Server                users.  G               * What will be the greatest number of simultaneous users:y  C               Upgrade_Installation: A default value is given. Press 2               RETURN to accept this default value.  D               New_Installation: Specify the maximum number of OfficeA               Server users that you expect at any one time. (ThisgH               number refers predominantly to VT users.) The installationG               procedure uses this entry to check that system parameters:H               are large enough to support your intended number of users.  H         ________________________________________________________________  H                                                 (continued on next page)                                              H       Installation Procedure: New, Upgrade and Architecture Support 2-37           B      Installation Procedure: New, Upgrade and Architecture Support1      2.2 Adding or Upgrading Architecture Support   E      Table 2-4 (Cont.) Installation Procedure for Adding Architecture2E      __________________Support_______________________________________   E      Step__Action____________________________________________________e  ;      15    Message Router checks for upgrade installations.i  C            This part of the installation procedure is determined byaC            the answers that you gave during the installation on the.A            other system. In this example script, the Alpha system D            was configured to use a remote Message Router on this VAXC            node. The level of Mail directory support set up for thei%            Alpha system is also used.   ?            %A1-I-MDCHK, Performing Mail and Directory checks...d  T            %A1-I-REMMR, Your Office Server system running on the Alpha is configured  C            -A1-I-REMMR, to use a Remote Message Router on this nodeoR            %A1-I-LOCMR, Therefore this VAX Office Server system will be configured  5            -A1-I-LOCMR, to use a local Message Routere  O            %A1-I-DIROPP, Your Alpha Office Server system is configured to use a   K            -A1-I-DIROPP, Mail Directory Service. This VAX architecture onlyn  Y            -A1-I-DIROPP, installation will use the same Message Router Directory Service._  L            %A1-I-UPDATEDDS, As this is an update you will not be asked for a  =            -A1-I-UPDATEDDS, Message Router Directory passworde            .            .            .  E      ________________________________________________________________p  E                                              (continued on next page)             G      2-38 Installation Procedure: New, Upgrade and Architecture Support_ _  _      H            Installation Procedure: New, Upgrade and Architecture SupportH                             2.2 Adding or Upgrading Architecture Support  H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureH         __________________Support_______________________________________  H         Step__Action____________________________________________________  D         16    Indicate if you want client applications to connect to:               Office Server using TCP/IP network protocol.  E               You are only asked the following question if DEC TCP/IP H               Services (formerly 'UCX') or other TCP/IP network software;               that emulates it is installed on your system.   0               * Do you want to use TCP/IP [YES]?  ?               Press RETURN if you want to use TCP/IP for clientsA               connections. If you do, you are asked the followingaD               questions if default service names for the AIDA ServerF               and Office Server File Cabinet Server are not registered0               in the Internet Services database.  ?               * Enter a port number for the AIDA Server [7300]:tU               * Enter a port number for the Office Server File Cabinet Server [7373]:u  G               Enter a different TCP/IP port number for each server. TheeF               port numbers can be in the range 1024 to 65535. You mustE               use the default values if you plan to use the TeamLinkse               client software.  C               The installation procedure checks that the TCPIP$IPC__H               SHR.EXE image is installed. If it is not, you must installH               it after the installation. (In case the system uses a pre_G               v5.0 product, and uses the old filename, the installation A               also checks for UCX$IPC_SHR.EXE if it does not findt!               TCPIP$IPC_SHR.EXE.)   H         ________________________________________________________________           17    System checking.  B               The installation procedure checks system parameters,%               quotas and identifiers.   H         ________________________________________________________________  H                                                 (continued on next page)  H       Installation Procedure: New, Upgrade and Architecture Support 2-39 r  t      B      Installation Procedure: New, Upgrade and Architecture Support1      2.2 Adding or Upgrading Architecture Supportt  E      Table 2-4 (Cont.) Installation Procedure for Adding Architecture E      __________________Support_______________________________________r  E      Step__Action____________________________________________________   #      18    Enter the language code.   I            * Enter language code for this installation (2 characters): US.  ?            Enter the two-letter language code for your language_%            component. See Appendix D._  E      ________________________________________________________________n  "      19    Enter the dialect code.  A            Your language kit may also contain one or more dialect C            components. Enter the dialect code that you want to use.p  ?            %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesetsuA            %VMSINSTAL-I-RESTORE, Restoring product save set B ...A  P                If you wish to install a dialectal variation of ENGLISH language,  S                enter the code for the dialect component you wish to use.  If you do   M                not wish to install a dialectal variation of ENGLISH language,H  4                then accept the answer of NO_DIALECT.  R            * Enter dialect code for this installation (5 characters) [NO_DIALECT]:  E      ________________________________________________________________   !      20    Enter the market code.e  G            * Enter market code for this installation (2 characters): US(  E            Enter the two-letter market code for the installation. See             the Appendix D.  E      ________________________________________________________________F  E                                              (continued on next page)e  G      2-40 Installation Procedure: New, Upgrade and Architecture SupportY m         H            Installation Procedure: New, Upgrade and Architecture SupportH                             2.2 Adding or Upgrading Architecture Support  H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureH         __________________Support_______________________________________  H         Step__Action____________________________________________________  B         21    Enter the name of the OpenVMS account for the Office               Server manager._  S               * What is the existing OpenVMS username for the Office Server accounte                   [OFFICE]:n  0               The account details are displayed.  H         ________________________________________________________________  B         22    Confirm that the details of the account are correct.  N               * Are all the specified account's characteristics correct [YES]?  6               Press RETURN if the details are correct.  H         ________________________________________________________________  @         23    Run the IVP (Installation Verification Procedure).  G               * Do you want to run the IVP after the installation [NO]?o  3               Enter YES if you want to run the IVP.   H         ______All_the_installation_questions_have_now_been_completed.___  ,         2.3 Automatic Postinstallation Tasks  G               The installation procedure performs automatic postinstal-_?               lation tasks, for example, converting data files.a  H               If a problem occurs during the postinstallation phase, see               Chapter 4.  9               The following tasks are done automatically:   B               o  Deassigns old Office Server logicals and logicals0                  created during the installation  I               o  Runs the Office Server startup procedure, A1V60START.COMr  ?               o  Compiles, installs and sets protections on the B                  following form libraries and their site versions:                    -  OAFORM                    -  MEMRES  H       Installation Procedure: New, Upgrade and Architecture Support 2-41    t      B      Installation Procedure: New, Upgrade and Architecture Support)      2.3 Automatic Postinstallation Tasksr                 -  OAN$FORMS  +            o  Installs message symbol filese              o  Compiles TXLs   >            o  For upgrade installations, FORMAT.DAT and OA$SM_-               UTILITY_MASTER.DAT are updated.L  &      2.4 Manual Postinstallation Tasks  C            There are some manual tasks that you must complete after +            the installation. See Chapter 5._                                                                G      2-42 Installation Procedure: New, Upgrade and Architecture Supportn o  u                  H                                                                        3H         ________________________________________________________________  H                             Installation Procedure: Additional Languages      F               This chapter describes the installation of an additionalE               language on an Office Server Version 6.0 system that is_3               configured as a multilanguage system.   F                 __________________Before  You Start __________________  <                 Do not start the installation until you haveD                 completed the system preparation tasks in Chapter 1.  E                 _____________________________________________________.  H               During the installation procedure a number of cautions andH               general informational messages are displayed. Read all the+               displayed messages carefully..  A               Each question in the installation is marked with antC               asterisk (*) at the beginning of the line. If you arerG               unsure how to answer a question enter a question mark (?)_               for Help._  F                 ________________________Note  ________________________  ?                 If the installation fails, you must restart thei<                 installation from the beginning. To stop the8                 installation at any point, press CTRL/Y.  E                 _____________________________________________________   H               If you are installing a new additional language or upgrad-C               ing an existing additional language, see Section 3.1.   E               If you are installing or upgrading architecture support :               for an additional language, see Section 3.2.    H                         Installation Procedure: Additional Languages 3-1    t      1      Installation Procedure: Additional Languages E      3.1 Installation Procedure for Additional Language Installations   7      3.1 Installation Procedure for Additional Languages          Installations  D            Follow the steps in Table 3-1 to install a new additional?            language or upgrade an existing additional language.   B            There are minor differences in the display depending onB            whether the installation is being run on a VAX or Alpha            system.  A            The example script shows the addition of BRITISH as anfD            additional language on an Office Server Version 6.0 Alpha?            system that is configured as a multilanguage system.f                                                                5      3-2 Installation Procedure: Additional Languagesl           H                             Installation Procedure: Additional LanguagesH         3.1 Installation Procedure for Additional Language Installations  H         Table_3-1_Installation_Procedure_for_An_Additional_Language_____  H         Step__Action____________________________________________________  G         1     Create a log file for the installation. Compaq recommends C               that you keep a record of the installation in case oftF               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,o               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               If you are running console management software, you can C               use this to record the installation. See your console ?               management documentation for further information.   H         ________________________________________________________________  G         2     Load and mount the CD that contains the language softwaret               kit.  H         ________________________________________________________________  E         3     Invoke the VMSINSTAL procedure from the SYSTEM account.   +               Enter the following commands:   &               $ SET DEFAULT SYS$UPDATE*               $ @VMSINSTAL A1LUS060 device  A               To use an alternate working device (AWD), enter then&               following command lines:  &               $ SET DEFAULT SYS$UPDATE;               $ @VMSINSTAL A1LUS060 device OPTIONS AWD=diske  D               device is the device on which you have mounted the CD.D               You can use a physical or a logical device name but doF               not use logical device names beginning with A1$, OA$, orF               OA1$. A1LUS060 is the product identifier and disk is the7               location of the alternate working device.t  H                                                 (continued on next page)  H                         Installation Procedure: Additional Languages 3-3 o  C      1      Installation Procedure: Additional LanguagesPE      3.1 Installation Procedure for Additional Language Installations_  ?      Table 3-1 (Cont.) Installation Procedure for An Additional E      __________________Language______________________________________t  E      Step__Action_____________________________________________________  E      ________________________________________________________________   %      4     Verify your system backup.a  F             OpenVMS Alpha Software Product Installation Procedure V7.1  &            It is 14-FEB-2001 at 21:27.  :            Enter a question mark (?) at any time for help.I            * Are you satisfied with the backup of your system disk [YES]?A  $            Press RETURN to continue.  E      _________________________________________________________________  D      5     Enter the number for the type of installation you want to            do.  @                The current product image identification is V5.0.  L                Using the LANGUAGE-only Office Server V6.0 kit, the following  3                installation types can be performed:_  F                (1)  Install new Office Server V6.0 additional language  B                (2)  Upgrade Office Server V5.0 additional languageA                (3)  Update Office Server V6.0 additional languagetT                (4)  Add, Upgrade or Update Alpha architecture specific components of  F                     an existing Office Server V6.0 additional language  @                (RL) Register licenses for pre-requisite software  =            * Which installation do you wish to perform [1]: 1n  D            Enter 1 to install a new additional Office Server Version            6.0 language.  E      ________________________________________________________________   E                                              (continued on next page)O  5      3-4 Installation Procedure: Additional Languages_ _  _      H                             Installation Procedure: Additional LanguagesH         3.1 Installation Procedure for Additional Language Installations  B         Table 3-1 (Cont.) Installation Procedure for An AdditionalH         __________________Language______________________________________  H         Step__Action____________________________________________________  >         6     Confirm that you want to start the installation.  Y                   The installation procedure allows you to perform the following actions:c  0                   (I)   Perform the installation;                   (PC)  Perform all pre-installation checks.  8               * Which action do you wish to perform [I]:  5               Press RETURN to start the installation._  H         ________________________________________________________________  H         7     Supply information about optional software as appropriate.  O                  During your first language installation you chose to integraten  V                  WPS-PLUS, therefore you will be able to use WPS-PLUS as an additional  D                  editor from your Office Server additional language.  W                  This kit contains a library of Encapsulated PostScript(R) graphics and   W                  PostScript(R) Page Overlay samples specific to the language component.   ^               * Do you want these graphics copied to the Office Server library directory [NO]?  B               Enter Y to copy the WPS-PLUS graphics library to the&               Office Server directory.  H         ________________________________________________________________  H                                                 (continued on next page)              H                         Installation Procedure: Additional Languages 3-5 T  s      1      Installation Procedure: Additional LanguagesoE      3.1 Installation Procedure for Additional Language Installations   ?      Table 3-1 (Cont.) Installation Procedure for An AdditionalsE      __________________Language______________________________________l  E      Step__Action____________________________________________________f  (      8     Select a default date format.  P                Office Server allows you to select a default date format for each  O                language you have installed. This will become the default Officeo  S                Server date format for each user (on a per language basis.) This may   S                be changed by each user through the Set Working Conditions option one  #                the User Setup Menu.   4                    Alphanumeric Date    Numeric Date  H                    1   DD-MMM-YYYY      MM/DD/YY      (Standard Default)  0                    2   DD-MMM-YYYY      DD/MM/YY0                    3   DD-MMM-YYYY      YY/MM/DD0                    4   YYYY-MMM-DD      MM/DD/YY0                    5   YYYY-MMM-DD      DD/MM/YY0                    6   YYYY-MMM-DD      YY/MM/DDB                    7   ***** Reserved (Means system default) *****F                    8   DD-MM-YYYY       DD/MM/YY      (Numeric format)  F                    9   MM-DD-YYYY       MM/DD/YY      (Numeric format)  2            * Which date format do you require [1]:  E            Press RETURN to use the default format or enter the number 4            for the date format that you want to use.  A            See Appendix C (or, if not US or GB, the documentation >            provided with your kit) for more details about date            formats.r  =            The installation procedure now does system checks.a  E      ________________________________________________________________r  E                                              (continued on next page)e  5      3-6 Installation Procedure: Additional Languagess t  e      H                             Installation Procedure: Additional LanguagesH         3.1 Installation Procedure for Additional Language Installations  B         Table 3-1 (Cont.) Installation Procedure for An AdditionalH         __________________Language______________________________________  H         Step__Action____________________________________________________  &         9     Enter the language code.  L               * Enter language code for this installation (2 characters): US  B               Enter the two-letter language code for your language(               component. See Appendix D.  H         ________________________________________________________________  %         10    Enter the dialect code.l  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.a  [               * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GBi  B               Enter the dialect code that you want to use. In thisB               example, US_GB is the BRITISH dialect component. See               Appendix D.3  H         ________________________________________________________________  C         11    Specify the device for the additional language files.   P               * Which device will hold the Office Server BRITISH language files:  $               Enter the device name.  H         ________________________________________________________________  H                                                 (continued on next page)  H                         Installation Procedure: Additional Languages 3-7 0  p      1      Installation Procedure: Additional LanguagesgE      3.1 Installation Procedure for Additional Language Installations   ?      Table 3-1 (Cont.) Installation Procedure for An Additional E      __________________Language______________________________________n  E      Step__Action____________________________________________________l  E      12    Enter the OpenVMS username for the Office Server manager'su            account.t  P            * What is the existing OpenVMS username for the Office Server account                [OFFICE]:  4            The details of the account are displayed.  E      ________________________________________________________________a  8      13    Confirm that the account details are correct.  K            * Are all the specified account's characteristics correct [YES]?   ?            Press RETURN to confirm that the account details area            correct.   E      ________________________________________________________________o  @      14    Specify the top-level directory for the Office Server%            additional language files.H  R            * Enter the top-level directory required for all BRITISH language files  X                                                                               [BRITISH]:  E      ________________________________________________________________m  =      15    Run the IVP (Installation Verification Procedure)._  E            * Do you want to run the IVP after the installation [YES]?u  '            Press RETURN to run the IVP.r  B            All the installation questions have now been completed.  E            The installation procedure does automatic postinstallationuA            tasks. If a problem occurs during the postinstallationoC            phase, see Chapter 4. For manual postinstallation tasks,V            see Chapter 5.   @            If you are installing on a VMScluster and want to add=            additional architecture support for the additionalEE      ______language_that_you_have_installed,_see_Section_3.2.________D  5      3-8 Installation Procedure: Additional Languages  e  u      H                             Installation Procedure: Additional LanguagesH           3.2 Installing Architecture Support for an Additional Language  F         3.2 Installing Architecture Support for an Additional Language  @               Before you start the installation, you must do the               following:  A               o  Make a note of the location of the Office ServertC                  configuration file, OA$DATA_SHARE:A1CONFIG.DAT, onaG                  the VAX system. You will be asked for this information )                  during the installation.   F               o  Run the script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP, to=                  check for logicals containing SYS$SYSDEVICE.   H               From the Office Server manager's account on the node whereG               you have already installed Office Server, run the script, 0               OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP:  '               $ SET HOST 0/LOG=filenameo               $ OFFICE/NOINITI=               Enter CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP(  F               If references to SYS$DEVICE are found, a warning messageG               is displayed. You must remove the references as they will E               refer to different devices on a VAX system and an Alpha F               system. If the references are not corrected, data may be"               lost on your system.  G               Follow the steps in Table 3-2 to add architecture supportUH               for an additional language that you have already installedE               on a different architecture in the same VMScluster. TheSC               example script shows the addition of VAX architectureS@               support for Office Server BRITISH as an additionalE               language. BRITISH is already installed as an additionalpA               language on an Alpha system in the same VMScluster.   E         Table 3-2 Installation Procedure for Addition of ArchitectureLH         __________Support_for_an_Additional_Language____________________  H         Step__Action____________________________________________________  /         1 to  Follow Steps 1 to 5 in Table 3-1.l	         5   H                                                 (continued on next page)  H                         Installation Procedure: Additional Languages 3-9 4  s      1      Installation Procedure: Additional Languages C      3.2 Installing Architecture Support for an Additional Languageg  =      Table 3-2 (Cont.) Installation Procedure for Addition ofs=                        Architecture Support for an AdditionalfE      __________________Language_______________________________________  E      Step__Action_____________________________________________________  E      ________________________________________________________________i  D      6     Enter the number for the type of installation you want to            do.  X               Using the LANGUAGE-only Office Server V6.0 kit, the following installation  %               types can be performed:   F                (1)  Install new Office Server V6.0 additional language  B                (2)  Upgrade Office Server V5.0 additional languageA                (3)  Update Office Server V6.0 additional languageuA                (4)  Add, upgrade, or update VAX components for an <                       Office Server V6.0 additional language  @                (RL) Register licenses for pre-requisite software  =            * Which installation do you wish to perform [1]: 4y  B            Enter 4 to add VAX architecture support for an existing9            Office Server Version 6.0 additional language.   E      ________________________________________________________________a  ;      7     Confirm that you want to start the installation.s  V                The installation procedure allows you to perform the following actions:  -                (I)   Perform the installationf8                (PC)  Perform all pre-installation checks  5            * Which action do you wish to perform [I]:   2            Press RETURN to start the installation.  E      ________________________________________________________________i  E                                              (continued on next page)   6      3-10 Installation Procedure: Additional Languages n  g      H                             Installation Procedure: Additional LanguagesH           3.2 Installing Architecture Support for an Additional Language  @         Table 3-2 (Cont.) Installation Procedure for Addition of@                           Architecture Support for an AdditionalH         __________________Language______________________________________  H         Step__Action____________________________________________________  C         8     Enter the location of OA$DATA_SHARE:A1CONFIG.DAT, theaG               Office Server configuration file, for the existing Officee(               Server Version 6.0 system.  T                   You have chosen an architecture only installation. To continue you  R                   must specify the location of the existing Office Server system's  P                   configuration file (A1CONFIG.DAT).  The installation will read  B                   A1CONFIG.DAT to determine file target locations.  S               * Please give the directory location of A1CONFIG.DAT [OA$DATA_SHARE]:D  >               Enter the location of A1CONFIG.DAT in the formatD               disk:[directory]. You must always specify the location7               of the configuration file in this format.   L               %A1LUS-I-DEFLOG, Running A1V41START.COM to define the logicals  C               -A1LUS-I-DEFLOG, for your existing V6.0 Alpha system.                .d               .o               .   H         ________________________________________________________________  7         9     Indicate whether you want to purge files.   O               * Do you want to purge files replaced by this installation [YES]?   *               Press RETURN to purge files.  H         ________________________________________________________________  H                                                 (continued on next page)      H                        Installation Procedure: Additional Languages 3-11 l  n      1      Installation Procedure: Additional Languages C      3.2 Installing Architecture Support for an Additional Languagee  =      Table 3-2 (Cont.) Installation Procedure for Addition of_=                        Architecture Support for an Additional_E      __________________Language______________________________________a  E      Step__Action____________________________________________________   "      10    Configuration checking.  D            You may be asked questions depending on the configuration0            of Office Server on the Alpha system.  G             This VAX architecture only installation will where possiblei  I             match the configuration of Office Server already installed one               the Alpha system.R  P             During your Office Server installation on Alpha you chose to install  R             Office Server with WPS-PLUS, therefore WPS-PLUS will also be installed  ;             during this VAX architecture only installation.   E      ________________________________________________________________   E                                              (continued on next page)                                       6      3-12 Installation Procedure: Additional Languages e  h      H                             Installation Procedure: Additional LanguagesH           3.2 Installing Architecture Support for an Additional Language  @         Table 3-2 (Cont.) Installation Procedure for Addition of@                           Architecture Support for an AdditionalH         __________________Language______________________________________  H         Step__Action____________________________________________________  +         11    Select a default date format._  \                   Office Server allows you to select a default date format for each language  \                   you have installed. This will become the default Office Server date format  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 Date   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/YYr3                       5   YYYY-MMM-DD      DD/MM/YYd3                       6   YYYY-MMM-DD      YY/MM/DD_E                       7   ***** Reserved (Means system default) *****CI                       8   DD-MM-YYYY       DD/MM/YY      (Numeric format)e  I                       9   MM-DD-YYYY       MM/DD/YY      (Numeric format)o  5               * Which date format do you require [1]:t  H         ________________________________________________________________  &         12    Enter the language code.  L               * Enter language code for this installation (2 characters): US  B               Enter the 2-letter language code for your additional'               language. See Appendix D.   H         ________________________________________________________________  H                                                 (continued on next page)  H                        Installation Procedure: Additional Languages 3-13           1      Installation Procedure: Additional Languages C      3.2 Installing Architecture Support for an Additional Languagew  =      Table 3-2 (Cont.) Installation Procedure for Addition oft=                        Architecture Support for an Additional E      __________________Language______________________________________a  E      Step__Action____________________________________________________o  "      13    Enter the dialect code.  ?            %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesetstA            %VMSINSTAL-I-RESTORE, Restoring product save set B ...2  P                If you wish to install a dialectal variation of ENGLISH language,  S                enter the code for the dialect component you wish to use.  If you do   M                not wish to install a dialectal variation of ENGLISH language,i  4                then accept the answer of NO_DIALECT.  X            * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GB  >            In this example, US_GB is the BRITISH dialect code.  E      ________________________________________________________________   ?      14    Enter the name of the OpenVMS username of the Officeo$            Server manager's account.  V            * What is the existing VMS username for the Office Server account [OFFICE]:  -            The account details are displayed.E  E      ________________________________________________________________o  8      15    Confirm that the account details are correct.  K            * Are all the specified account's characteristics correct [YES]?   >            Press RETURN if the account information is correct.  E      ________________________________________________________________   A      16    If you want to, run the IVP (Installation Verification             Procedure).  D            * Do you want to run the IVP after the installation [NO]?  0            Enter YES if you want to run the IVP.  E                                              (continued on next page)   6      3-14 Installation Procedure: Additional Languages s         H                             Installation Procedure: Additional LanguagesH           3.2 Installing Architecture Support for an Additional Language  @         Table 3-2 (Cont.) Installation Procedure for Addition of@                           Architecture Support for an AdditionalH         __________________Language______________________________________  H         Step__Action____________________________________________________  E               All the installation questions have now been completed.d  H               The installation procedure will do postinstallation tasks.H         ______For_manual_postinstallation_tasks,_see_Chapter_5._________                                                                      H                        Installation Procedure: Additional Languages 3-15 d                     H                                                                        4H         ________________________________________________________________  H                                          Installation Errors and Failure      H               This chapter deals with various error messages you may seeE               while installing Office Server Version 6.0 or while the_F               Installation Verification Procedures (IVPs) are running,E               and explains what to do if the installation or the IVPs_               fail._  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 Errorsa  D               Errors can occur during the installation if any of the)               following conditions exist:e  >               o  There is a problem with the operating system.  ?               o  There is a problem with prerequisite software.f  A               o  Quotas necessary for successful installation arel                  insufficient.  H               o  System parameter values for successful installation are                  insufficient.  >               o  The OpenVMS help library is currently in use.  E               o  SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB_!                  are not present.   G               For descriptions of the error messages generated by theseiC               conditions, see the OpenVMS books on system messages, E               recovery procedures, and OpenVMS software installation.rE               If you are notified that any of these conditions exist,sH               you should take the appropriate action as described in the               message.  H                                      Installation Errors and Failure 4-1           (      4.2 Failure During Postinstallation    (      4.2 Failure During Postinstallation  C               ________________________Note ________________________d  9               When the installation procedure reaches thep;               postinstallation phase, the main installationn:               has completed. If the postinstallation tasks:               fail, a message is displayed indicating that>               the installation has failed and that you need to=               reinstall Office Server. It is not necessary to_@               do this; you need only rerun A1$POSTINSTALL.COM as(               described in this section.  >               You must rerun A1$POSTINSTALL.COM on the node on8               which you originally ran the installation.  C               _____________________________________________________u  :      4.2.1 Failure of Upgrade Installations in Safety Mode  B            If your installation is being performed in Safety mode,A            you need take no further action if the failure happenst            before the message:  8            Files will now be moved to target directories  @            If the installation fails after this message, restore>            your original system from a backup. You can then goB            back to using the original system, or you can start the            installation again.  >      4.2.2 Failure of Upgrade Installations in Non-Safety Mode  @            If your installation is being performed in non-safety@            mode, restore your original system from a backup. YouD            can then go back to using the original system, or you can(            start the installation again.        4.2.3 Full Installationsn  =            If a full installation fails, delete all accounts, B            identifiers and directories that have been created, and(            start the installation again.    (      4-2 Installation Errors and Failure    c      H                                      4.2 Failure During Postinstallation    8         4.2.4 Failure Due to Insufficient Dynamic Memory  B               An installation on an Alpha system may fail with the&               following error message:  <               %SYSTEM-F-INSFMEM, insufficient dynamic memory  E               If this error occurs, you must check that the value for_D               CTLPAGES is high enough. If you used the default valueA               of 100, you must increase it to 200 and restart the .               installation. See Section 1.6.2.  /         4.3 Error Messages when Running the IVP   @               The following informational and error messages are,               displayed when the IVP is run:  D               %OA-I-LNF, Error opening form library "THIS_IS_A_TEST"(               -RMS-E-FNF, file not found  =               %OA-W-INVGET, Symbol "THIS_IS_A_TEST" not foundl  L               %OA-E-BADLIB, Error occurred while precompiling THIS_IS_A.TEST               form library  E               You can ignore these messages as they are part of tests ,               that are performed by the IVP.  F               If any other error messages occur during the IVP, do the               following:  F               1. Check the log of the installation for any errors that7                  may have occurred during installation.   E               2. Check the file SYS$MANAGER:OFFICE_IVP.LOG. This filecA                  does not contain the results of the IVP, but theCC                  results of invoking Office Server when running the                   IVP.f  B               3. Check for any errors in the following procedures.  =                  o  During the execution of the startup file,_/                     SYS$STARTUP:A1V60START.COM:e  -                        Creating logical names   9                  o  Automatic postinstallation procedurese  -                        Installing image filesl>                        Compiling and installing form libraries  H                                      Installation Errors and Failure 4-3    h      ,      4.3 Error Messages when Running the IVP    >            4. Make sure that the Office Server TXL is compiledA               and installed successfully, and recompile it if youMC               received any error messages when the postinstallation #               command file was run.   E            5. Check that you have not run out of quota on the disk or E               disks containing the OA$SHAREnnnn directories (refer toD7               the manual describing OpenVMS utilities).M  <            6. Check that the details for the IVP account are.               completed correctly, as follows:  A               o  All the Office Server privileges are set to YES.   C               o  The IVP user directory points to the disk and sub-cC                  directory that you specified for the Office Server_0                  manager's account. For example:  *                  a1device:[OFFICE.IVPUSER]  @                  where a1device is the device that you specified)                  during the installation.   E               o  The Office Server account, IVP, is accessed from the 9                  Office Server manager's OpenVMS account._  ?            7. Run Office Server and try to use those areas thatuC               failed during the IVP to find more information on thed               error.  @               Log in to the Office Server manager's IVP account:  $               $ OFFICE /USERNAME=IVP  D               Manually execute each IVP test as described in DIGITALA               Office Server Managing from a VT Terminal (the V4.0                book).  C               ________________________Note ________________________   A               The IVP runs in the language context of the currentoB               optional language being installed and also tests the(               international base system.  @               Most IVPs are designed to exercise and test Office@               Server at a level which is normally customization->               independent. However, if you have customized the=               Phone Directory subsystem of Office Server, thes@               display graphics (IDG) procedure may fail. This is  (      4-4 Installation Errors and Failure           H                                  4.3 Error Messages when Running the IVP    B                 a demonstration test used to exercise the terminal2                 graphics as a typical application.  E                 _____________________________________________________m             4.4 IVP FailureS  E               If the IVP fails, the following messages are displayed:e  P               The Office Server V6.0 Installation Verification Procedure failed.  N               %VMSINSTAL-E-IVPFAIL, The IVP for Office Server V6.0 has failed.                                                                H                                      Installation Errors and Failure 4-5                       H                                                                        5H         ________________________________________________________________  H                                                   Postinstallation Tasks      B               This chapter describes the tasks that you must do to@               complete the setup of Office Server. Some of theseC               tasks are optional, or only apply to particular typesP,               of systems, or configurations.  C               There are a number of additional setup tasks that thesH               Office Server manager must do to set up the users' workingG               environment before Office Server is used. These tasks are G               explained in detail in the DIGITAL Office Server Managing_0               from a VT Terminal (the V4.0 book)  F               You must run postinstallation from the node on which you(               are running Office Server.  6         5.1 Checklist of Manual Postinstallation Tasks  @               Table 5-1 lists the manual postinstallation tasks.  H               Table_5-1_Postinstallation_Tasks__________________________  +                                     Type of H               Task__________________Installation_____Information________  D               Start Office Server   Full, upgrade    See Section 5.21               on all nodes in a     or additional 0               VMScluster system     architecture  H               __________________________________________________________  @               Create or modify the  Full or upgrade  Section 5.3!               Office Server site-                specific startup               procedure   H                                                 (continued on next page)  H                                               Postinstallation Tasks 5-1           3      5.1 Checklist of Manual Postinstallation Tasksn    E            Table_5-1_(Cont.)_Postinstallation_Tasks__________________i  (                                  Type ofE            Task__________________Installation_____Information________a  E            __________________________________________________________c  =            Modify the OpenVMS    Full, upgrade    Section 5.4l.            site-specific         or additional-            startup procedure     architecture   E            __________________________________________________________   =            Replace the           Full, upgrade    Section 5.5 .            DCLTABLES on          or additional-            VMScluster systems    architecturen  E            __________________________________________________________   =            Delete files that     Upgrade or       Section 5.6E+            are no longer         additional )            required              language   E            __________________________________________________________   =            Install any missing   Full, upgrade    Section 5.7 .            images                or additional-                                  architecture   E            __________________________________________________________p  B            Recompile form        Upgrade          See Section 5.8.>            libraries, including                   This sectionA            application or                         also lists form @            site-specific form                     libraries that>            libraries                              are compiledE                                                   automatically afternC                                                   the installation.o  E            __________________________________________________________n  E                                              (continued on next page)             5-2 Postinstallation Tasks  n  n      H                           5.1 Checklist of Manual Postinstallation Tasks    H               Table_5-1_(Cont.)_Postinstallation_Tasks__________________  +                                     Type ofcH               Task__________________Installation_____Information________  @               Migrate your          Upgrade of       Section 5.90               customizations:       a customized*               o  Run the CART       system                    resolutione                  procedure                 o  Restore                  customizationsF!                  to modified datar                  files                 o  Replace                   customized help                  files                  o  Delete obsolete                  files  H               __________________________________________________________  A               Migrate SITELINK50.comUpgrade,         Section 5.10 .               to SITELINK60.COM     additional0               using Customization   language and0               Management            architecture+                                     supportn  H               __________________________________________________________  A               Link Office Server    Upgrades of      Section 5.11 .               to include code-      code-level.               level customizations  customized/                                     systems andF.                                     additional3                                     architecture if 2                                     also installed  H               __________________________________________________________  H                                                 (continued on next page)  H                                               Postinstallation Tasks 5-3 t         3      5.1 Checklist of Manual Postinstallation Taskso    E            Table_5-1_(Cont.)_Postinstallation_Tasks__________________   (                                  Type ofE            Task__________________Installation_____Information________   A            Set up remote mail    Full or upgrade  For new instal- B                                  Note that        lations with theE                                  local mail       MAILbus 400 MTA andFC                                  is already set   Compaq X.500, seeE?                                  up after the     Section 5.12.e  D                                  installation.    For upgrade or newD                                                   installations withE                                                   Message Router, seem?                                                   Section 5.13.   E            __________________________________________________________   ?            Add WPS-PLUS login    Full or upgrade  Section 5.14. .            command procedure     installations+            to the system login   if you arei/            command procedure     using WPS-PLUS /                                  as the default '                                  editor   E            __________________________________________________________   >            Move the CDA DOC_     If CDA$LIBRARY   Section 5.15/            STYLE files to a      does not exist /            suitable location,    on your system             if necessaryl  E            __________________________________________________________   @            Set up the user       Full or upgrade  DIGITAL OfficeA            environment                            Server Managing D                                                   from a VT TerminalA                                                   (the V4.0 book)   E            __________________________________________________________e  E                                              (continued on next page)n            5-4 Postinstallation Tasks  t  u      H                           5.1 Checklist of Manual Postinstallation Tasks    H               Table_5-1_(Cont.)_Postinstallation_Tasks__________________  +                                     Type ofdH               Task__________________Installation_____Information________  C               Tune the File         Full or upgrade  DIGITAL OfficeSD               Cabinet Servers                        Server ManagingG                                                      from a VT Terminal_D                                                      (the V4.0 book)  H               __________________________________________________________  C               Decide how many mail  Full or upgrade  DIGITAL Office D               Sender and Fetcher                     Server ManagingG               processes to run                       from a VT TerminaluH               _______________________________________(the_V4.0_book)____  C         5.2 Start Office Server on all Nodes in a VMScluster System   N               The Office Server startup procedure, SYS$STARTUP:A1V60START.COM,E               is supplied with Office Server and is executed automat- D               ically on the node used for the installation, once the6               installation has completed successfully.  B               If you are running Office Server on a VMScluster youC               must also run SYS$STARTUP:A1V60START.COM on each node D               in the cluster in order to start Office Server. If youG               run A1V60START.COM manually from the DCL prompt, you mustrE               include the location of the Office Server configuration G               file, OA$DATA_SHARE:A1CONFIG.DAT. OpenVMS prompts you fordG               the location of this file if you do not specify it on the                command line.D  D               If you are creating new shared directories from withinH               Office Server, you must define new system logical names onE               each node in the cluster. For further information aboutcD               running Office Server on a VMScluster, see the DIGITALH               Office Server Managing from a VT Terminal (the V4.0 book).              H                                               Postinstallation Tasks 5-5 d  l      K      5.3 Create or Modify the Site-specific Office Server Startup Proceduref    A      5.3 Create or Modify the Site-specific Office Server Startup           Procedure  E            To modify the Office Server startup command procedure, you C            must create a site-specific command procedure. The site- C            specific startup command procedure will be automatically B            executed by the Office Server startup command procedure            when it is executed.   >            You can create the following types of site-specific            command procedure:a  E            o  A language-independent startup command procedure calledsD               A1V60_SITE_START.COM. Create this startup procedure in&               OA$SITE_BUILD_SHARE_IND.  E            o  A language-specific startup command procedure, OA$SITE_uB               language_START.COM, for each language installed in aE               multilanguage Office Server system. Create this startupn1               procedure in OA$SITE_BUILD_LLV_IND.   7               device:[directory.SITE.SOURCES_language])r  A               where: device is the device containing the language ?               files, and directory is the name of the top-level A               directory of your Office Server Version 6.0 system.f  E               You can specify the directory for your default languagel>               by using the logical name OA$SITE_BUILD_LLV_IND.  D            If you are upgrading and you have a site-specific startupB            command procedure that you want to keep, rename it from8            A1V50_SITE_START.COM to A1V60_SITE_START.COM.  1      5.4 Edit the Site-specific Startup Procedurel  D            When you run A1V60START.COM from the DCL prompt, you mustB            include the location of the Office Server configurationD            file, OA$DATA_SHARE:A1CONFIG.DAT. OpenVMS prompts you forD            the location of this file if you do not specify it on theC            command line. When you include the Office Server startup D            procedure in the OpenVMS site startup procedure, you must9            specify the location of the A1CONFIG.DAT file:   1            $ @SYS$STARTUP:A1V60START.COM locationa        5-6 Postinstallation Taskst P  i      H                             5.4 Edit the Site-specific Startup Procedure    F               where location is the location of A1CONFIG.DAT, which is               specified as:_  +               device:[directory.DATA_SHARE]   D               device is the device that you specified for the OfficeH               Server data files and directory is the top-level directoryB               that you specified for the Office Server data files.  G               To find the location of OA$DATA_SHARE:A1CONFIG.DAT, refer '               to your installation log.   F                 ________________________Note  ________________________  ?                 However you choose to set up your site-specific @                 startup procedures, you must ensure that all the?                 Office Server prerequisite products are started =                 before Office Server. This includes messaging_@                 software, DEC Notes, and DECwindows/Motif if you<                 are using CDA converters with Office Server.  E                 ______________________________________________________  E         5.4.1 Installations With Compaq X.500 and the MAILbus 400 MTAR  C               If you have installed a new Office Server system withaH               Compaq X.500 and the MAILbus 400 MTA, you must ensure thatD               the prerequisite messaging products are started beforeE               Office Server. Make sure that the following 3 files are .               executed in the following order:  +               1. SYS$STARTUP:OSAK$START.COMf  3               2. SYS$STARTUP:DXD$COMMON_STARTUP.COM   3               3. SYS$STARTUP:MTA$COMMON_STARTUP.COM_  /         5.4.2 Installations with Message Router   F               For Office Server systems using Message Router, you mustG               ensure that the Message Router software is started beforec               Office Server.  H               As an example, Table 5-2 describes how to edit the OpenVMSE               site-specific startup file to include the Office Server B               startup procedure after an upgrade installation fromE               Office Server Version 6.0. This ensures that the Office D               Server environment is reestablished following a system               reboot.   H                                               Postinstallation Tasks 5-7           1      5.4 Edit the Site-specific Startup Procedured    E            Table_5-2_Editing_the_OpenVMS_Site-specific_Startup_File__c              Installation E            Type_____________Do_the_Following_________________________   -            Full and         To edit the file:_.            addition         1. Find the lines:            of second;            architecture     $ @SYS$MANAGER:STARTNET.COM and L            (unless you are  $ @SYS$MANAGER:MB$CONTROL START=(DDS,TS,...,ER)1  C            using common     2. After these lines, add the followingu$            startup files)      line:  C                             $ @SYS$STARTUP:A1V60START.COM location2c  E            __________________________________________________________-  +            Upgrade from     Change the linetC            Office Server    $ @SYS$STARTUP:A1V50START.COM location2             Version 5.0      to            and addition C            of second        $ @SYS$STARTUP:A1V60START.COM location2               architecture             (unless you are            using common_            startup files)   E            __________________________________________________________   E            [1]The_exact_command_line_will_depend_on_which_Message____   )            Router components are running.a;            [2]location is the location of the Office Servert            configuration file,&            OA$DATA_SHARE:A1CONFIG.DAT.  E                                              (continued on next page)                   5-8 Postinstallation Tasksg e  o      H                             5.4 Edit the Site-specific Startup Procedure    A               Table 5-2 (Cont.) Editing the OpenVMS Site-specificnH               __________________Startup_File____________________________                 InstallationH               Type_____________Do_the_Following_________________________  G               If you are       Add the following entry before the entry G               running a        for the Office Server startup procedure: M               remote Message   $ @SYS$STARTUP:DDS$STARTUP.COM node nodenumbertA               Router and       where node is the name of the node_D               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.a  H               __________________________________________________________  4         5.5 Replace the DCLTABLES on Cluster Systems  H               If you installed Office Server Version 6.0 on a VMSclusterH               system, you must replace the DCLTABLES on any nodes in theH               cluster where you are not installing Office Server VersionG               6.0. Enter the following commands on each of these nodes:                  $ INSTALL A               INSTALL> REPLACE SYS$SHARE:DCLTABLES /OPEN /SHARE -n#               _INSTALL> /HEADER_RES                INSTALL> EXIT   A               You need only do this once after you have installed G               Office Server Version 6.0. The Office Server installation_F               procedure replaces the tables automatically for the nodeD               on which you are installing Office Server Version 6.0.  4         5.6 Delete Files That Are No Longer Required  D               If you have upgraded or updated Office Server, variousB               files remain in the SYSTEM directories which you can@               delete to increase your disk space. The files are:  :               o  For an Office Server Version 5.0 upgrade:  3                     SYS$HELP:A1050.RELEASE_NOTES or 5                     SYS$HELP:A1Llang050.RELEASE_NOTES E                     SYS$HELP:A1Cmarket050.RELEASE_NOTES, if available .                     SYS$STARTUP:A1V50START.COM  H                                               Postinstallation Tasks 5-9                 5.7 Install Missing Imagesr          5.7 Install Missing Imagese  C            On startup, if any error messages are displayed relatingcD            to images that are not installed, use the Install utility?            to install those images before executing the startup B            procedure again. Images that you may need to install inB            this way are those referenced by optional products that@            you have integrated with the Office Server image. ForD            example, the following command installs the image RDBSHR,1            which is referenced by VAX DATATRIEVE:m              $ INSTALLB            INSTALL> ADD SYS$SHARE:RDBSHR /OPEN /HEADER_RES /SHARED  C            For more details of the Install Utility, see the OpenVMS             documentation.i  !      5.8 Recompile Form Librariesu  B            If you are upgrading from Office Server Version 5.0 andD            you have compiled form libraries on your old system whichE            are not replaced by the upgrade, you may see the following             error message:   8            Obsolete form library <name> please recompile  ?            If you see this message, recompile the form library.h  C               ________________________Note ________________________i  @               You must also compile application or site-specific8               form libraries, and your own applications.  C               _____________________________________________________r  C            The following form libraries are compiled automatically:               o  OAFORM              o  SITEOAFORM              o  MEMRES              o  SITEMEMRES              o  OAN$FORMSS              o  SITEOAN$FORMS          5-10 Postinstallation Tasks i  f      H                                             5.8 Recompile Form Libraries    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 librarysC               (PCF) option from the System Customization Management G               (CSZ) menu. See the DIGITAL Office Server Managing from ad*               VT Terminal (the V4.0 book).  9         5.9 Migrating Your Customizations After Upgrading6  E               Immediately after installing Office Server Version 6.0,_E               and before allowing your users to access Office Server,r?               review your customizations to mandatory elements.n  C               You can rerun the CART after installing Office Server D               Version 6.0 using the Check Conflicts (CC) option fromE               the Application Maintenance menu. When you run the CART E               from within Office Server, it does not produce the site C               elements report. It does produce the full and summary G               reports, and the CART resolution procedure, which are all A               stored as new 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 theSG               elements with another name in the same area, for example, B               copy CM_CART_SUMMARY_V50$PRIMARY to CM_CART_SUMMARY_B               V50$PRIMARY_19SEP. All of the elements that you have8               already processed will have status code F.  ,               To review your customizations:  B               1. From the Customization Management (CM) subsystem,E                  select each element marked as a mandatory change andoB                  print the differences between it and the new base                  element.A  (               2. Review the differences.  G                  Note where new functionality has been added or changes F                  made. Note any symbol changes. Use the information inG                  your upgrade plan to make the changes necessary to geth%                  your system running.   F               3. Test your customizations and, if they work correctly,;                  move the elements back into the live area.v  H                                              Postinstallation Tasks 5-11 s  i      6      5.9 Migrating Your Customizations After Upgrading    E            4. Before allowing your users back onto the system, review E               your customizations to recommended elements in the same_9               way as you reviewed the mandatory elements.t  A               If you do not resolve conflicts to recommended ele- E               ments, users may not have access to your customizationsoB               or will not have access to the full functionality of(               Office Server Version 6.0.  A            5. Review conflicts with elements reported with status E               code D, see the Compaq Office Server Planning and Setup_A               Guide. Status code D indicates a customization thathA               calls an element which has been removed from Office !               Server Version 6.0.m  >               If the element that is called by your customized@               element has a status code of A, then no customized@               version of it exists. Your customization will fail@               if you delete the removed element, as described in?               Section 5.9.2. Edit the command procedure DELETE_ ?               OBSOLETE_FILES.COM so that these elements are notS?               deleted. Use Customization Management to create a C               new customized element to replace the referenced base D               element that no longer exists in Office Server Version               6.0.  ?               Use Customization Management to copy any elementsl>               reported with status code A into the development@               area. When you rerun the CART, these elements will-               be reported with status code H.t  B            6. You can now allow your users to access Office Server=               Version 6.0. When it is convenient, resolve theo3               conflicts for informational elements.   0      5.9.1 Running the CART Resolution Procedure  D            The CART resolution procedure calls individual scripts toD            process each status code. The scripts are called CM_CART_4            SCRIPTn, where n is the CART status code.  D            To run and edit the scripts called by the CART resolutionE            procedure, you must have Application Maintainer privileges ?            for the areas where the elements are stored. See theSA            DIGITAL Office Server Managing from a VT Terminal (theN?            V4.0 book). To run the CART resolution procedure use          5-12 Postinstallation Tasks w  u      H                        5.9 Migrating Your Customizations After Upgrading    D               the Execute procedure (EP) option from the Application5               Maintainer's Check Conflicts (CC) menu.o  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.c  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.   G               You can use the CART resolution procedure to resolve some D               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_E               elements do not call a removed element, see Section 5.9dC               which describes how to resolve conflicts for elements *               reported with status code D.  %         5.9.2 Deleting Obsolete FilesR  @               A command procedure, DELETE_OBSOLETE_FILES.COM, isF               provided to remove the files that are no longer required+               by Office Server Version 6.0.   F                 ________________________Note  ________________________  C                 Do not run this procedure immediately after running >                 the CART resolution procedure. You must alwaysB                 review this file before running it. Check that allD                 your customizations are working correctly and ensureA                 that your customizations do not call any elementso7                 that will be deleted by this procedure.   E                 _____________________________________________________   H                                              Postinstallation Tasks 5-13           6      5.9 Migrating Your Customizations After Upgrading    =            You can edit DELETE_OBSOLETE_FILES.COM to stop the A            deletion of certain files if required, for example, ifuD            one of your customizations calls an element that has beenA            removed from the base kit and which would otherwise beu%            deleted by this procedure.   B            For example, the suggested resolution for elements with            status code A is to:e  E            o  Run the CART resolution procedure to delete the recordsrB               for these elements from the Customization Management               databasese  H            o  Run the command procedure OA$LIB:DELETE_OBSOLETE_FILES.COM$               to delete the elements  E            To run DELETE_OBSOLETE_FILES.COM, enter the following from$            DCL:E  7            $ @OA$LIB:DELETE_OBSOLETE_FILES.COM languageE  >            where language is the language of the Office ServerE            system. If you have additional languages installed on yournA            system, you can run this procedure for each additional             languages.a  :      5.9.3 Replacing the Help Modules for Your Application  ?            For more information about customizing Help, see thee3            ALL-IN-1 Application Programming: Guide.b  <            After the upgrade, copy the Office Server Version=            6.0 standard Help libraries, OA$LIB:OAHELP.HLB and B            OA$LIB:SITEHLPSOURCE.HLB from the base area to the liveD            area, OA$SITE_LIB_language. Customization Management willC            inform you that the live and development versions of the C            Help libraries are the same and ask you whether you wish$/            to continue. Answer yes to continue.   @            You must recreate your customizations to Help modules>            using Customization Management. Use the Access baseE            elements (ABE) option to get the base version of your Help B            module. Use the Copy (CO) option to copy the customizedD            module to the development area where you can make changes@            to it. When you save the module Office Server formats?            it and puts it into the appropriate development Helpl         5-14 Postinstallation Tasks _  _      H                        5.9 Migrating Your Customizations After Upgrading    E               libraries. When you have tested the Help, mark it to ber<               moved to the live area so that it can be used.  >         5.10 Migrate SITELINK50 Using Customization Management  K               The SITELINK60.COM file is under the control of CustomizationEA               Management. It is important that you check that any B               customizations to SITELINK50.COM are compatible with               SITELINK60.COM.   D               Use Customization Management to edit the base templateG               version of the site link file, SITELINK60.COM, to includeiE               your previous SITELINK40.COM from OA$SITE_BUILD. ReviewyF               your customizations to SITELINK60.COM and then move yourG               customized version to LIVE. Review your customizations to F               make sure they are compatible with Office Server VersionH               6.0. Do not relink Office Server until you have done this.               See Section 5.9.  D               It is recommended that you do the following to relink:  /               $ SET DEFAULT OA$BUILD_SHARE_ARCH "               $ @OA$BUILD:A1LNKDRV  D         5.11 Link Office Server to Include Code-level Customizations  D               Office Server Version 6.0 is linked during the instal-A               lation without any customizations you may have madehD               to your existing system. Therefore, it is important toH               relink Office Server after the installation if you wish toG               link with your customizations when you have checked them.tF               See Chapter 2 of Compaq Office Server Planning and Setup               Guide.  B         5.12 Setting up Remote Mail When Using the MAILbus 400 MTA  E               You must complete the set up tasks for Compaq X.500 andTF               the MAILbus 400 MTA before you can send and receive mailG               using the MAILbus 400 MTA. The setup tasks are covered ina@               the Compaq Office Server Planning and Setup Guide.          H                                              Postinstallation Tasks 5-15 e         :      5.13 Setting up Remote Mail When Using Message Router    :      5.13 Setting up Remote Mail When Using Message Router  C            After the installation, local mail is already set up. IfhB            you want to use Message Router for remote mail, you mayC            need to do some or all of the tasks listed in Table 5-3,A6            depending on the requirements at your site.  B            The tasks that you must do depend on the type of remote'            Message Router which can be:s  =            o  Installed on a VAX node in the same VMScluster:a  C               -  With Office Server installed on the Message Router                   nodes  ?               -  Without Office Server installed on the Message                   Router node  =            o  Installed on a VAX node that is not in the sames)               VMScluster as Office Server   E            Table_5-3_Tasks_for_Setting_up_Remote_Mail________________o  E            Task_______________________For_Information_See____________c  4            If you are using a remote  Section 5.13.1             Message Router server            node, make sure that #            there is a mailbox entryo             on that node for your!            Office Server mailbox.               You may have already $            done this as part of your!            preinstallation tasks.e  4            If you have installed      Section 5.13.2$            Office Server Version 6.0"            on a mixed architecture#            cluster, you must modify #            the mailbox entry on thet            Message Router node.   E                                              (continued on next page)          5-16 Postinstallation Tasks f  e      H                    5.13 Setting up Remote Mail When Using Message Router    H               Table_5-3_(Cont.)_Tasks_for_Setting_up_Remote_Mail________  H               Task_______________________For_Information_See____________  7               If you are using MRGATE    Section 5.13.3d&               on a remote node, set up$               each node that will be               using MRGATE.C  H               Set up the remote Mail     Section 5.13.4 if Office ServerE               directory                  is using a Message Router iniG                                          the same VMScluster and OfficetC                                          Server is installed on thet<                                          Message Router node  C                                          Section 5.13.4.2 if OfficehB                                          Server is using a MessageG                                          Router that is not in the sameoG                                          VMScluster or Office Server is9E                                          not installed on the Messagei4                                          Router node  F                                          If you are using Compaq X.500B                                          after a new Office ServerF                                          Version 6.0 installation withH                                          Message Router, you must followE                                          the instructions for settinggF                                          up Compaq X.500 in the CompaqC                                          Office Server Planning and 5                                          Setup Guide.t  7               Edit the site-specific     Section 5.13.5r"               startup procedure to&               start up the remote MailH               directory.________________________________________________  1         5.13.1 Create a Mailbox for Office Servert  H               This section applies when Office Server is using a MessageE               Router that is not in the same VMScluster. You may haveeH               already done this as part of the preinstallation tasks. IfG               you have already created a mailbox, you do not need to do                it again.   C               Your Office Server mailbox for your node (or cluster)sC               requires a mailbox entry on the remote Message Routere               node.e  H                                              Postinstallation Tasks 5-17           :      5.13 Setting up Remote Mail When Using Message Router                To add a mailbox:  E            __________________________________________________________rE            Step_Action_______________________________________________o  A            1    Log in to the MBMANAGER account on the node where B                 Message Router is running, and enter the following                 command:  &                 $ RUN SYS$SYSTEM:MRMAN  E            __________________________________________________________s  7            2    Enter the following at the MRM> prompt:   $                 MRM> ADD localnodeA1<                        /PASSWORD=password /COMPLETE_MESSAGESR                        /IGNORE_SENDER /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS                   where:  E                 o  localnode is the name of the Office Server node or_B                    cluster. The name must be unique to the Message!                    Router system.   A                 o  password is the Office Server mailbox passwordw>                    that you specified during the Office Server5                    installation on the remote system.   A                    The password that you specify here must be the A                    same as you specified during the Office Server @                    installation. If you change the password whenC                    creating the mailbox, you must also change it to C                    the same value in Office Server by using the Set B                    operating conditions (SOC) option on the ManageE                    Messaging menu. See DIGITAL Office Server Managing 6                    from a VT Terminal (the V4.0 book).  E            __________________________________________________________u  @            3    Exit from the Message Router management utility:  E            _____MRM>_EXIT____________________________________________o  =            Refer to the Message Router documentation for moreh'            information about mailboxes.n         5-18 Postinstallation Tasks           H                    5.13 Setting up Remote Mail When Using Message Router    9         5.13.2 Modifying the Message Router Mailbox Entry   E               You must modify the Message Router mailbox entry if you C               have a mixed-architecture cluster and you are using a B               Message Router in the same cluster. The installationE               procedure creates a mailbox entry on the Message Router H               node with the /OWNER=ALLIN1 qualifier. The Alpha node willG               be unable to connect with this mailbox because the /OWNERnC               qualifier is on the mailbox. Modify the Office Server D               mailbox entry on the Message Router node to remove the               qualifier.  $               $ RUN SYS$SYSTEM:MBMAN$               MRM> MODIFY A1/NOOWNER               MRM> EXIT:  A               where a1 is the name of the Message Router mailbox.$  @         5.13.3 Configuring the VMSmail Gateway for Remote Access  F               If you have installed the Message Router VMSmail GatewayF               on one of the nodes in a VMScluster you can set up other=               Office Server nodes so that they can access it.u  A               On each of the nodes that does not have the gatewaynG               started, define the logical name MRGATE to the following:v                 node::MR%   B               where node is the node where the gateway is running.  B               You can also use a VMSmail Gateway on a node in yourG               network, that is remote to your cluster. You need MessagenH               Router to be installed on one of the nodes in your clusterG               in order to do this. Make an entry for the remote VMSmailmD               Gateway in the mailbox directory of the Message RouterF               Transfer Service on the VAX node in your cluster that is%               running Message Router:g  H               1. Log in to the MBMANAGER account on the VAX node in your7                  cluster that is running Message Router   .               2. Enter the following commands:  '                  $ RUN SYS$SYSTEM:MRMAN 7                  MRM> ADD MRGATE/REPLACE="MRGATE @node"K  G                  where node is the node where the gateway is installed.p  H                                              Postinstallation Tasks 5-19           :      5.13 Setting up Remote Mail When Using Message Router    >            3. Exit from the Message Router management utility:                 MRM> EXITz  E            See the Message Router documentation for more information.r  B      5.13.4 Setting Up the Message Router Directory Service as the             Mail Directory  A            The tasks that you need to do depend on the following:   B            o  If the Message Router node is in the same VMSclusterD               and has Office Server installed, see Section 5.13.4.1.  ;            o  If the Message Router node is not in the same A               VMScluster or Office Server is not installed on the 8               Message Router node, see Section 5.13.4.2.  6      5.13.4.1 Message Router is in the Same VMScluster  A            Read this section if Office Server is installed in the >            same VMScluster as Message Router and Office Server>            is installed on the Message Router node. You can be@            using the Mail directory as either the primary or the@            secondary directory. If, during the installation, youD            chose to use the Mail directory as the primary directory,D            OA$DIRECT_PRIME is set to 2. If, during the installation,?            you chose to use the Mail directory as the secondary A            directory with Office Server as the primary directory,c,            then OA$DIRECT_PRIME is set to 1.  ?            After installation, the following values are set up:   3            o  A user agent entry name and password.e  B               -  The user agent entry name is OA$node$ALLIN1 for aB                  new or upgrade installation, where node is eitherE                  the node name or the cluster alias for the system onoE                  which you are installing Office Server. For example,                    OA$LYNX$ALLIN1.  D               -  The user agent entry password is the Mail directoryC                  password that you entered during the installation.a  ?            o  A subscriber entry for the Office Server manager.t@               The proxy attribute of the subscriber entry is the>               name of the local Office Server user agent entryB               (OA$node$ALLIN1). This attribute gives Office Server         5-20 Postinstallation Tasks d  h      H                    5.13 Setting up Remote Mail When Using Message Router    D                  proxy access to the manager's entry, so that Office8                  Server can update and access the entry.  H               o  UAPASSWRD.DAT which contains the name of the user agentH                  object and the user agent password, from the first item                  in this list.  B               When you set up the Mail directory the values in the(               previous list are updated.  =               To set up the Mail directory, do the following:I  H               __________________________________________________________H               Step_Action_______________________________________________  F               1    Log in to the Office Server manager's Office Server                    account:   3                    $ OFFICESERVER /USERNAME=MANAGER1  H               __________________________________________________________  C               2    Enter the following commands from Office Server:.  (                    <GET #ORGNAME=orgname*                    <GET #LOCATION=location                      where:_  F                    o  orgname is the name of your company or organiza-                       tion  <                    o  location is the location of your users  H                    If area routing is in use at your site, you must also                    enter:   )                    <GET #AREA="area_code"i  H                    area_code is the area code for the area that includes                    your system.         H                                              Postinstallation Tasks 5-21 R  e      :      5.13 Setting up Remote Mail When Using Message Router  E            __________________________________________________________ME            Step_Action_______________________________________________t  E                 If you do not know the area code, do the following one(                 the Message Router node:E                 _____________________________________________________ E                 Step_Action__________________________________________   ?                 a    Run the MAILbus configuration procedure totE                      display the current Transfer Service settings inn&                      use at your site:  -                      $ @SYS$MANAGER:MB$CONFIG   @                 b    Display the settings for the Message Router&                      Transfer Service:  !                      MBC> SHOW TSo  A                      The area code is displayed, along with other *                      settings, as follows:                            .                          .                          .7                      Transfer Service uses area routingm)                      Area Code : areacode_                            .                          .                          .  C                      where areacode is the area code in use at yourg                      site.  >                 3    Enter EXIT, or press CTRL/Z, to exit fromB                      the MAILbus configuration procedure. For moreD                      details of this command, see the Message RouterE                 _____documentation.__________________________________r  E            __________________________________________________________e  E            3    Update the user agent entry by entering the following                  command:  )                 <DO OA$LIB:USERAGENT_POSTe         5-22 Postinstallation Tasks    t      H                    5.13 Setting up Remote Mail When Using Message Router  H               __________________________________________________________H               Step_Action_______________________________________________  5                    This DO script does the following:   Q                    o  Updates the user agent entry in OA$DATA_SHARE:UAPASSWRD.DATYH                       with the Mail directory identity obtained from the>                       user agent object in the Mail directory.  G                       The Office Server user agent is now available for/                        all users.  H                    o  Sets the Mail directory field in the Office Server5                       manager's account details to Y.   E                    o  Copies details from the Office Server manager's G                       profile entry, which was created during installa-eH                       tion, into the manager's Mail directory subscriber                       entry.  D                    o  Copies the manager's Mail directory identifierB                       from the subscriber entry into the manager's4                       Office Server account details.  H                    o  Updates the Office Server user agent object in theE                       Mail directory with the values you supplied for,5                       organization name and location.m  E                    o  Creates a mail address (OA$DDS_AREA_ROUTE) thatcD                       is used for all the Mail directory subscribersG                       owned by the user agent (Office Server). The mailiE                       address comprises the name of the Office Server_E                       Message Router mailbox (OA$MTI_MAILBX), and themC                       name of the node or cluster (OA$PRIMARY_NODE)_E                       running the Message Router to be used by OfficenE                       Server. If area routing is in use at your site, E                       the network address also includes the area codep)                       that you specified.   H               __________________________________________________________  H               4    Restart Office Server on all nodes in the VMScluster.  H               __________________________________________________________    H                                              Postinstallation Tasks 5-23 l         :      5.13 Setting up Remote Mail When Using Message Router  E            __________________________________________________________wE            Step_Action_______________________________________________   =            5    If you are performing an upgrade or an updatenB                 installation in which you have elected to use MailD                 directory addressing for the first time, see DIGITALC                 Office Server Managing from a VT Terminal (the V4.0oD                 book) for information about how to populate the MailE            _____directory.___________________________________________   :      5.13.4.2 Message Router is not in the Same VMScluster  E            Read this section if the Message Router that you are usingeC            is not in the same VMScluster as Office Server, or it istD            in the same VMScluster but Office Server is not installed&            on the Message Router Node.  )            You must create the following:   3            o  A user agent entry name and password.   ?            o  A subscriber entry for the Office Server manager. @               The proxy attribute of the subscriber entry is the>               name of the local Office Server user agent entryB               (OA$node$ALLIN1). This attribute gives Office ServerA               proxy access to the manager's entry, so that Office 5               Server can update and access the entry.h  B            o  Update the OA$DATA_SHARE:UAPASSWRD.DAT file with the9               name of the user agent object and password.   C            You must do some tasks on the remote Message Router nodeR4            and some tasks on the Office Server node.  E            __________________________________________________________ E            Step_Action_______________________________________________d  @            1    On the remote Message Router node, log in to the@                 MBMANAGER account and run the MAILbus Management                 Utility, MBMAN:n  &                 $ RUN SYS$SYSTEM:MBMAN  E            __________________________________________________________            5-24 Postinstallation Tasks t  o      H                    5.13 Setting up Remote Mail When Using Message Router  H               __________________________________________________________H               Step_Action_______________________________________________  G               2    Create the user agent object that Office Server willlF                    use to access the Mail directory and add the object)                    to the Mail directory:r  I                    MBMAN> BUILD DDS UA /NAME="uaname"/PASSWORD="password",  2                    MBMAN> ADD DDS BUILT_OBJECT/LOG                      where:   F                    o  uaname is the name of the user agent object. TheD                       name is in the form OA$node$ALLIN1, where nodeF                       is either the node name or the cluster alias forE                       the system on which you are setting up the Mailc                        directory.  F                    o  password is the password that Office Server willF                       use to access the user agent object. It must not9                       be more than eight characters long.d  H               __________________________________________________________                                            H                                              Postinstallation Tasks 5-25    o      :      5.13 Setting up Remote Mail When Using Message Router  E            __________________________________________________________rE            Step_Action_______________________________________________o  =            3    Create and add a subscriber entry to the Mailu8                 directory for the Office Server manager:  =                 MBMAN>BUILD DDS SUBSCRIBER /SURNAME="MANAGER"s:                 MBMAN>BUILD DDS SUBSCRIBER /PROXY="uaname":                 MBMAN>BUILD DDS SUBSCRIBER /SUBID="uaname".                 MBMAN>ADD DDS BUILT_OBJECT/LOG                 MBMAN>EXIT                   where:  E                 o  MANAGER is the name of the Office Server manager's ?                    Office Server account and must be entered asr>                    shown. Do not enter any other account name.  C                 o  uaname is the name of the user agent object that B                    you specified, for example, OA$nodename$ALLIN1.  A                 o  /PROXY="uaname" grants the local Office Server ;                    user agent proxy access to the manager's C                    subscriber entry. This enables the Office Serverm@                    user agent to access and update the manager's=                    subscriber entry on behalf of the manager.s  ?                 o  /SUBID="uaname" identifies the Office ServereB                    manager's subscriber entry to Office Server, as<                    there can be many entries called MANAGER.  E            __________________________________________________________c                                   5-26 Postinstallation Tasks           H                    5.13 Setting up Remote Mail When Using Message Router  H               __________________________________________________________H               Step_Action_______________________________________________  G               4    On the Office Server node (VAX or Alpha), do all the E                    next steps from the Office Server manager's Officer"                    Server account:  C                    Enter the following commands to create temporary G                    symbols required by the script which you will run in !                    the next step:   (                    <GET #ORGNAME=orgname*                    <GET #LOCATION=location                      where:   F                    o  orgname is the name of your company or organiza-                       tion  <                    o  location is the location of your users  H                    If area routing is in use at your site, you must also                    enter:S  )                    <GET #AREA="area_code"_  H                    area_code is the area code for the area that includes                    your system.e                                    H                                              Postinstallation Tasks 5-27 A  o      :      5.13 Setting up Remote Mail When Using Message Router  E            __________________________________________________________lE            Step_Action_______________________________________________a  E                 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 to E                      display the current Transfer Service settings in &                      use at your site:  -                      $ @SYS$MANAGER:MB$CONFIGA  @                 b    Display the settings for the Message Router&                      Transfer Service:  !                      MBC> SHOW TS   A                      The area code is displayed, along with other *                      settings, as follows:                            .                          .                          .7                      Transfer Service uses area routing )                      Area Code : areacode_                            .                          .                          .  C                      where areacode is the area code in use at youry                      site.  >                 c    Enter EXIT, or press CTRL/Z, to exit fromB                      the MAILbus configuration procedure. For moreD                      details of this command, see the Message RouterE                 _____documentation.__________________________________   E            __________________________________________________________                  5-28 Postinstallation Tasks g         H                    5.13 Setting up Remote Mail When Using Message Router  H               __________________________________________________________H               Step_Action_______________________________________________  ,               5    Run the following script:  ,                    <DO OA$LIB:USERAGENT_POST  H                    A mail message will be sent to the Office Server man-F                    ager's account which contains detailed instructions&                    on what to do next.  H               __________________________________________________________  D               6    For details of populating the Mail Directory, seeH                    the DIGITAL Office Server Managing from a VT TerminalH               _____(the_V4.0_book)._____________________________________  >         5.13.5 Remote Message Router Directory Service Startup                Procedure  D               On each Office Server node that will be using a remoteC               Mail directory, add the following entry to your site-uH               specific startup procedure before the entry for the Office'               Server startup procedure:e  <               $ @SYS$STARTUP:DDS$STARTUP.COM node nodenumber  D               where node is the name of the node on which the remote?               Message Router is installed and nodenumber is thes?               Directory Service node number of the remote node.   ?               To find the Directory Service node number, do the 3               following on the Message Router node:   $               $ RUN SYS$SYSTEM:MBMAN+               MBMAN> SHOW DDS NODE nodename   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.           H                                              Postinstallation Tasks 5-29 t  f      *      5.14 WPS-PLUS Login Command Procedure    *      5.14 WPS-PLUS Login Command Procedure  <            During the Office Server Version 6.0 installationE            procedure, a login command procedure, A1WPSPLUS_LOGIN.COM,RB            is created in SYS$MANAGER. Add this to the system loginC            command procedure, SYS$SYLOGIN, if you want all users to_C            run with these qualifiers. Alternately, you can make theuB            file available to users to put into their own LOGIN.COM            files.e  (      5.15 Moving the CDA DOC_STYLE Files  E            If CDA$LIBRARY does not exist on your system, the CDA DOC_rD            STYLE files are installed in OA$LIB_SHARE. Move the files"            to a suitable location.                                                                   5-30 Postinstallation Tasks e  g                  H                                                                        AH         ________________________________________________________________  H                             Office Server Version 6.0 Distribution Media      G               The Office Server kit is provided on its own CD-ROM or aseD               part of the CD-ROM Consolidated Software Distribution.  E               A separate CD-ROM is provided for the Office Server Web                 Interface product.  A         A.1 CD-ROM Distribution Kits (VAX or Alpha Installations)S  @               The notes in this section apply to both the Office?               Server Version 6.0 CD-ROM and to the Consolidated'D               Software Distribution CD-ROM. On the Compact Disc (CD-?               ROM), the base kit is in the directory A1060.KIT.TB               The printable documentation is in a directory called"               A1060.DOCUMENTATION.  B               For the Office Server Version 6.0 CD-ROM, the onlineG               versions of the documentation for Bookreader are provided_)               in the DECW$BOOK directory._  G               For each language, there is a directory called A1lang060,nC               where lang is the 2-letter code for the Office ServerAD               language that you are installing. See Appendix D for a               list of codes.  D               The base component savesets in the A1060.KIT directory               are:                  H                         Office Server Version 6.0 Distribution Media A-1    l      >      A.1 CD-ROM Distribution Kits (VAX or Alpha Installations)                A1060.A%            A1060.B (used by VAX only)_'            A1060.C (used by Alpha only)_%            A1060.D (used by VAX only)a'            A1060.E (used by Alpha only) %            A1060.F (used by VAX only)i'            A1060.G (used by Alpha only) %            A1060.H (used by VAX only) '            A1060.I (used by Alpha only)a            A1060.J            A1060.K            A1060.L.            A1060.M (MailWorks migration files)  D            The documentation directory, A1060.DOCUMENTATION contains<            ASCII (.TXT) and PostScript (.PS) versions of the#            following documentation:e  B            o  The Office Server Installation Guide, INST_GUIDE.TXT               and INST_GUIDE.PS   C            o  The Read Me First letter, READ_ME_FIRST.TXT and READ_                ME_FIRST.PSa  C            o  The Software Product Description (SPD), A1060_SPD.TXTt               and A1060_SPD.PS.   B            The CDROM also contains the following software in their            own directories:_  '            o  Message Router (VAX only)   7            o  Message Router VMSmail Gateway (VAX only)               o  DEC Notesa                    5      A-2 Office Server Version 6.0 Distribution Media  t                     H                                                                        BH         ________________________________________________________________  H                          Office Server Version 6.0 Files and Directories      A               This appendix lists the files that are installed in/C               directories other than the Office Server directories.=  *         B.1 Files in the Office Server Kit  F               For a complete list of all Office Server directories andC               file names when the installation is complete, use the <               following command for each Office Server area:  2               $ DIR/SEC[a1dir...]*.*/out=a1dir.TXT  G               where a1dir is the top level directory name for each area '               (for example OFFICE.DIR).u  D               The list of files is a useful reference if you need toA               resolve any problems with file protections or ACLs.   <         B.2 Files Installed in Non-Office Server Directories  C               The following list shows the files that are installedhF               in directories other than the Office Server directories.D               Where language is included in a file name, this is theC               name of the installed language, for example, ENGLISH.e  $               o  SYS$COMMON:[SYSLIB]  !                  OA$AIDA_CSHR.EXE "                  OA$AIDA_DSSHR.EXE#                  OA$AIDA_GCMSHR.EXE_#                  OA$AIDA_RTLSHR.EXE_#                  OA$AIDA_SECSHR.EXE                   OA$DSL$SHR.EXEn$                  OAFC$CLIENT_SHR.EXE                   OA$TMAECOMM.EXE  H                      Office Server Version 6.0 Files and Directories B-1 _  _      9      B.2 Files Installed in Non-Office Server Directories_        (               DDS$RMT_VAX.EXE (VAX Only)-               DDS$RMT_ALPHA.EXE  (Alpha Only)                DPESHR.EXE               SYS$PROXY_SHR.EXEg               OAFCDEF.H                OAFCDEF.L32                OAFCEXT.He               OAFCEXT.L32t               OAFCEXT.R32                OAFC$LINK.OPTs               PRXDEF.H                 DDIF$READ_DX.EXE$               DDIF$READ_MACWRITE.EXE                DDIF$READ_PICT.EXE               DDIF$READ_RTF.EXE !               DDIF$READ_WORD5.EXE !               DDIF$READ_WORDP.EXE                DDIF$READ_WPL.EXE                DDIF$WRITE_DX.EXE %               DDIF$WRITE_MACWRITE.EXEu!               DDIF$WRITE_PICT.EXEr                DDIF$WRITE_RTF.EXE"               DDIF$WRITE_WORD5.EXE"               DDIF$WRITE_WORDP.EXE                DDIF$WRITE_WPL.EXE               DTIF$READ_DIF.EXEh               DTIF$READ_TCV.EXE                DTIF$READ_WK1.EXE                DTIF$READ_WK3.EXE                 DTIF$WRITE_WK1.EXE                DTIF$WRITE_WK3.EXE,               DDIF$READ_RNO.EXE (Alpha Only)  &               MRAPPSHAR.EXE (VAX Only)(               MRAXPSHAR.EXE (Alpha Only)  E               FDVSHR.EXE (FMS image, added on new installations only)_  ?               OA$LLVlanguage.EXE (On Multilingual systems only)t  G               OA$WPL_ALL_TV.EXE (Alpha with full WPS-PLUS support only) J               OA$WPL_FDP_TV.EXE (Alpha without full WPS-PLUS support only)  8      B-2 Office Server Version 6.0 Files and Directories           H                     B.2 Files Installed in Non-Office Server Directories                      XPORT.L32                  XPORT.OLB                  XPORT.REQ  $               o  SYS$COMMON:[SYSEXE]                     OA$AIDA_CLI.EXE                   OA$AIDA_DDS.EXE)                  OA$AIDA_PROP_SHARING.EXE #                  OA$AIDA_SERVER.EXE !                  OA$AIDA_X500.EXEe'                  OA$SCRIPT_SYMBIONT.EXE                    OAFC$SERVER.EXE!                  OA$FORMATTER.EXE                    TLNK$REMOTE.EXE  G                  FMSFAA.EXE (FMS image added on new installations only) W                  FMSFCV.EXE (FMS image added on new installations on VAX machines only) G                  FMSFED.EXE (FMS image added on new installations only)cG                  FMSFLG.EXE (FMS image added on new installations only) G                  FMSFLI.EXE (FMS image added on new installations only) G                  FMSFTE.EXE (FMS image added on new installations only)dG                  FMSFUU.EXE (FMS image added on new installations only)m  $               o  SYS$COMMON:[SYSMSG]                    XPORTMSG.EXE_"                  OAFC$MESSAGES.OBJ                  CNV_MSG.DAT                  DPEMSG.EXE   (                  MRAPPMSG.EXE (VAX Only)*                  MRAXPMSG.EXE (Alpha Only)  /                  DDS$MSG_ALPHA.EXE (Alpha Only)_+                  DDS$MSG_VAX.EXE (VAX Only)_+                  DDS$RMT_VAX.EXE (VAX Only) /                  DDS$RMT_ALPHA.EXE (Alpha Only)   H                  FDVMSG.EXE (FMS image, added on new installations only)H                  FMSMSG.EXE (FMS image, added on new installations only)        H                      Office Server Version 6.0 Files and Directories B-3           9      B.2 Files Installed in Non-Office Server Directories_    &            o  SYS$COMMON:[SYS$STARTUP]                 OA$AIDA_START.COM                OAFC$STARTUP.COM               DDS$STARTUP.COMm  !            o  SYS$COMMON:[SYSMGR]o  !               A1WPSPLUS_LOGIN.COM_  *            o  SYS$COMMON:[SYSHLP.EXAMPLES]  *               EXAMPLE_READ_DIF.CDA$OPTIONS)               EXAMPLE_READ_DX.CDA$OPTIONSo/               EXAMPLE_READ_MACWRITE.CDA$OPTIONSl+               EXAMPLE_READ_PICT.CDA$OPTIONSi*               EXAMPLE_READ_RTF.CDA$OPTIONS*               EXAMPLE_READ_WK1.CDA$OPTIONS*               EXAMPLE_READ_WK3.CDA$OPTIONS,               EXAMPLE_READ_WORD5.CDA$OPTIONS4               EXAMPLE_READ_WORD5_FONTMAP.CDA$OPTIONS,               EXAMPLE_READ_WORDP.CDA$OPTIONS*               EXAMPLE_READ_WPL.CDA$OPTIONS*               EXAMPLE_WRITE_DX.CDA$OPTIONS0               EXAMPLE_WRITE_MACWRITE.CDA$OPTIONS,               EXAMPLE_WRITE_PICT.CDA$OPTIONS+               EXAMPLE_WRITE_RTF.CDA$OPTIONSe+               EXAMPLE_WRITE_WK1.CDA$OPTIONS +               EXAMPLE_WRITE_WK3.CDA$OPTIONS -               EXAMPLE_WRITE_WORD5.CDA$OPTIONS -               EXAMPLE_WRITE_WORDP.CDA$OPTIONSo2               EXAMPLE_WRITE_WORDP_V5_0.CDA$OPTIONS2               EXAMPLE_WRITE_WORDP_V5_1.CDA$OPTIONS+               EXAMPLE_WRITE_WPL.CDA$OPTIONSi  ;            Language specific lexicon files are installed inC>            LCI$LEXICONS if you install WPS-PLUS as the default            editor.              8      B-4 Office Server Version 6.0 Files and Directories    m                  H                                                                        CH         ________________________________________________________________  H                                                              ENGLISH Kit      E               This supplement describes the Office Server Version 6.0 D               ENGLISH kit. This kit provides the language and marketD               components for Office Server Version 6.0. This chapterG               lists the disk space requirements for an English languaget               installation.   F                 ________________________Note  ________________________  A                 This kit can be used to install American English, D                 which is referred to as English, or British English,0                 which is referred to as British.                   To install:i  C                 o  English, install the English language component.e  B                 o  British, install the English language component5                    and the British dialect component.   @                 o  The GB or the US market component with either?                    language, see the market information in thiso                    chapter.t  @                 If your license and support agreements are for a?                 market component other than the GB or US marketi<                 component with the English language kit, see?                 Appendix D, and the documentation provided withoB                 your kit, for the market-specific information that                 you need.   E                 _____________________________________________________   E               The language and market components are installed duringeC               the Office Server Version 6.0 installation procedure. A               Follow the instructions in the Compaq Office Servern5               Installation Guide to install this kit.   H                                                          ENGLISH Kit C-1 f  a            E            Use the information in this supplement to plan and prepareAB            for the Office Server Version 6.0 installation. See the3            Compaq Office Server Installation Guide.M        C.1 About Your ENGLISH Kit-  8            The ENGLISH kit has the following components:  (            o  English language component  !            o  US market componentb  !            o  GB market components  '            o  British dialect componentb        C.1.1 Distribution MediaF  @            The ENGLISH kit is supplied on compact disc (CD-ROM).        C.1.2 Savesets Provided  B            Table C-1 lists the savesets provided with your ENGLISH            kit.   E            Table_C-1_Savesets_Provided_with_the_ENGLISH_Kit__________   E            Component________Savesets_________________________________   E                                              (continued on next page)d                                    C-2 ENGLISH Kit l  i      H                                               C.1 About Your ENGLISH Kit    H               Table_C-1_(Cont.)_Savesets_Provided_with_the_ENGLISH_Kit__  H               Component________Savesets_________________________________  E               English          A1LUS060.A (Contains the Release Notesf0               language         Part 1: Language)  )                                A1LUS060.Bn  )                                A1LUS060.CG  )                                A1LUS060.Da  )                                A1LUS060.EV  )                                A1LUS060.F   )                                A1LUS060.G   )                                A1LUS060.H   <                                A1LUS060.I (used on VAX only)  >                                A1LUS060.J (used on Alpha only)  )                                A1LUS060.Ki  )                                A1LUS060.L   )                                A1LUS060.Me  E               US market        A1CUS050.A (Contains the Release Notes .                                Part 2: Market)  )                                A1CUSO60.Be  )                                A1CUS060.C   E               GB market        A1CGB060.A (Contains the Release Notes .                                Part 2: Market)  B                                A1CGB060.B A1CUS060.A (Contains theG                                Release Notes Part 2: Market) A1CGB060.Cs  H               British_dialect__A1DUS_GB060.A_and_A1DUS_GB060.B__________  #         C.2 Disk Space Requirements.  H               The values given in this section are required when you areD               preparing your system for installation. See Chapter 1.  H                                                          ENGLISH Kit C-3 i  n             C.2 Disk Space Requirements    >      C.2.1 Disk Space Required on the System Disk or Alternate            Working Device (AWD)I  D            Table C-2 gives the disk space requirement for installingE            all the components of the Office Server Version 6.0 kit onLC            the system disk or alternate working device (AWD) duringSA            the installation. The values for safety and non-safetyO?            mode apply to both full and upgrade installations ofF@            Office Server Version 6.0. For more information about5            safety and non-safety mode, see Chapter 1.   C            Table C-2  Disk Space Required on the System Disk or AWDyE            __________(Blocks)________________________________________   @            Installation Type             VAX               AlphaC                                            Non-                Non- E            ______________________Safety____safety____Safety____safetyX  E            English or British    176 000   46 200    253 000   72 600E            as the primary_            language   E            Addition of           60 500    34 650    137 500   72 600             architecture support             for English or             British as theX            primary languageP  E            English or British    81 400    34 650    91 300    36 3005            as an additionalE            language   E            Addition of           13 200    13 200    22 000    17 050T            architecture supportT            for English or             British as anE            additional_language_______________________________________   8      C.2.2 Disk Space for Language Files on Target Disks  E            This section gives the disk space requirements, in blocks, C            for installing the language files in Office Server areas ?            on target disks. The following disk space tables are             provided:        C-4 ENGLISH Kit S  U      H                                              C.2 Disk Space Requirements  H               __________________________________________________________H               Type_of_Installation_________________Disk_Space_Table_____  =               New installation of Office Server    Table C-3.T1               Version 6.0 with English or British 1               as the primary language, or EnglishI,               or British as a new additional               language.H  <               Upgrade installation from ALL-IN-1   Table C-4-               Version 3.2 or update of OfficeT0               Server Version 6.0 with English or1               British as the primary language, or 1               English or British as an additionalS               language  =               Addition, upgrade or update of VAX   Table C-5. H               or_Alpha_architecture_support.____________________________  F                 ________________________Note  ________________________  A                 If you do not install WPS-PLUS with Office Server <                 Version 6.0, you can decrease the disk spaceA                 requirement on the language disk by approximately                  2000 blocks.  E                 _____________________________________________________   H               Table_C-3_Disk_Space_for_Language_Files:_New_Installation_  H               Office_Server_Area____VAX______________Alpha______________  ;               Language disk         58 000           67 000)  9               LCI$lexicon disk[1]   1500             1500   9               System disk[2]        5500             5500TH               [1]Only_required_if_you_install_WPS-PLUS_with_Office______  !               Server Version 6.0.eG               [2]Space required to provide Office Server language fileseC               to system directories when using an alternate workingc               device (AWD).dH               __________________________________________________________    H                                                          ENGLISH Kit C-5 A  _             C.2 Disk Space Requirements    @            Table C-4 Disk Space for Language Files: Upgrade fromE            __________Version_3.1_____________________________________Y  E            Office_Server_Area____VAX______________Alpha______________   8            Language disk         12 000           21 000  6            LCI$lexicon disk[1]   1500             1500  6            System disk[2]        5500             5500E            [1]Only_required_if_you_install_WPS-PLUS_with_Office______C              Server Version 6.0.D            [2]Space required to provide Office Server language files@            to system directories when using an alternate working            device (AWD).E            ___________________________________________________________  C            Table C-5 Disk Space for Language Files: Add, Upgrade orSE            __________Update_Architecture_Support_____________________R  E            Office_Server_Area____VAX______________Alpha______________   8            Language disk         6000             12 000  6            System disk[1]        5500             5500E            [1]Space_required_to_provide_Office_Server_language_files_O  @            to system directories when using an alternate working            device (AWD).E            __________________________________________________________t                                  C-6 ENGLISH Kit 4  f      H                        C.3 Information on the English Language Component    9         C.3 Information on the English Language ComponentC  D               Table C-6 lists information about your language compo-               nent.   C               Table C-6 Useful Information for the English Language H               __________Component_______________________________________  H               Information______Value____________Used_For________________  <               Product name     A1LUS060         Installation  C               Language name    ENGLISH          File, directory and F                                                 logical names, and forG                                                 the /LANGUAGE qualifier   H               Language_code____US_______________During_installation_____  9         C.4 Information on the British Language Component.  D               Table C-7 lists information about the British language               component.  C               Table C-7 Useful Information for the British LanguageoH               __________Component_______________________________________  H               Information______Value____________Used_For________________  <               Product name     A1LUS060         Installation  C               Language name    BRITISH          File, directory andeF                                                 logical names, and forG                                                 the /LANGUAGE qualifier   <               Language code    US               Installation  H               Dialect_Code_____US_GB____________Installation____________  E               The British dialect component contains a United Kingdom_C               (UK) addendum file which contains information that issD               specific to the UK. The file is provided in OA$LIB:UK_               ADDENDUM.TXT      H                                                          ENGLISH Kit C-7 G  e      /      C.5 Information on the US Market Component     /      C.5 Information on the US Market Component   >            Table C-8 provides information about your US market            component.   E            Table_C-8_Useful_Information_for_the_US_Market_Component__m  E            Information___________Value____________Used_For___________-  B            Product name          A1CUS060         Installation andD                                                   naming of savesets  @            Market name           US               Media labeling  E            Market code           US               During installationI  +                  Office Server date format:   ?            Alphanumeric          DD-MMM-YYYY      Office Servers  ?            Numeric               MM/DD/YY         Office Servere  :            WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUS  :            WPS-PLUS time         colon (:)        WPS-PLUS            separator  &                       Currency format:  :            Currency              Dollar ($)       WPS-PLUS  :            Decimal separator     dot (.)          WPS-PLUS  :            Thousand separator    comma (,)        WPS-PLUS  E            Page_size_____________66_______________Printer_settings____  9      C.5.1 Keyboards Supported by the US Market Component   B            The US market component supports the following keyboard            mapping tables:  D            FRENCH_A1_LK201-AA.A1KMT        FRENCH_WPS_LK201-AA.A1KMTD            FRENCH_A1_LK201-AP.A1KMT        FRENCH_WPS_LK201-AP.A1KMTD            FRENCH_A1_LK201-BA.A1KMT        FRENCH_WPS_LK201-BA.A1KMTD            FRENCH_A1_LK201_BP.A1KMT        FRENCH_WPS_LK201-BP.A1KMTD            FRENCH_A1_LK201-NA.A1KMT        FRENCH_WPS_LK201-NA.A1KMTD            FRENCH_A1_LK260-AA.A1KMT        FRENCH_WPS_LK250-AA.A1KMTD            FRENCH_A1_LK250-AP.A1KMT        FRENCH_WPS_LK250-AP.A1KMT  D            GERMAN_A1_LK201-AG.A1KMT        GERMAN_WPS_LK201-AG.A1KMTD            GERMAN_A1_LK201-BA.A1KMT        GERMAN_WPS_LK201-BG.A1KMTD            GERMAN_A1_LK201-BG.A1KMT        GERMAN_WPS_LK201-BA.A1KMTD            GERMAN_A1_LK250-AG.A1KMT        GERMAN_WPS_LK250-AG.A1KMT        C-8 ENGLISH Kit    A      H                               C.5 Information on the US Market Component    H               SPANISH_A1_LK201-AA.A1KMT       SPANISH_WPS_LK201-AA.A1KMTH               SPANISH_A1_LK201-BA.A1KMT       SPANISH_WPS_LK201-BA.A1KMTH               SPANISH_A1_LK201-BS.A1KMT       SPANISH_WPS_LK201-BS.A1KMTH               SPANISH_A1_LK201-LS.A1KMT       SPANISH_WPS_LK201-LS.A1KMTH               SPANISH_A1_LK250-AS.A1KMT       SPANISH_WPS_LK250-AS.A1KMT  6               A list of supported keyboards is held in-               OA$DATA_SHARE:OA$KEYBOARDS.DAT.   ;               To invoke the keyboard mapping tables, enter:   6               $ OFFICESERVER/KEYBOARD=keyboard_mapping  D               where keyboard_mapping is the identity of the required               keyboard.T  9         C.5.2 Modems Supported by the US Market Component   >               Hayes and Hayes-compatible modems are supported.  2         C.6 Information on the GB Market Component  >               Table C-9 lists information about your GB market               component.  H               Table_C-9_Useful_Information_for_the_GB_Market_Component__  H               Information___________Value____________Used_For___________  E               Product name          A1CGB060         Installation and G                                                      naming of savesets_  C               Market name           GB               Media labelingX  H               Market code           GB               During installation  -                    Office Server date format:S  B               Alphanumeric          DD-MMM-YYYY      Office Server  B               Numeric               DD/MM/YY         Office Server  =               WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUS   =               WPS-PLUS time         colon (:)        WPS-PLUS                separator   (                         Currency format:  =               Currency              Pound ()        WPS-PLUS   H                                                 (continued on next page)  H                                                          ENGLISH Kit C-9    a      /      C.6 Information on the GB Market Component     A            Table C-9 (Cont.) Useful Information for the GB Market_E            __________________Component_______________________________t  E            Information___________Value____________Used_For___________l  :            Decimal separator     dot (.)          WPS-PLUS  :            Thousand separator    comma (,)        WPS-PLUS  E            Page_size_____________66_______________Printer_settings___   9      C.6.1 Keyboards Supported by the GB Market Componentp  B            The GB market component supports the following keyboard            mapping tables:  D            FRENCH_A1_LK201-AA.A1KMT        FRENCH_WPS_LK201-AA.A1KMTD            FRENCH_A1_LK201-AP.A1KMT        FRENCH_WPS_LK201-AP.A1KMTD            FRENCH_A1_LK201-BA.A1KMT        FRENCH_WPS_LK201-BA.A1KMTD            FRENCH_A1_LK201_BP.A1KMT        FRENCH_WPS_LK201-BP.A1KMTD            FRENCH_A1_LK201-NA.A1KMT        FRENCH_WPS_LK201-NA.A1KMTD            FRENCH_A1_LK250-AA.A1KMT        FRENCH_WPS_LK250-AA.A1KMTD            FRENCH_A1_LK250-AP.A1KMT        FRENCH_WPS_LK250-AP.A1KMT  D            GERMAN_A1_LK201-AG.A1KMT        GERMAN_WPS_LK201-AG.A1KMTD            GERMAN_A1_LK201-BA.A1KMT        GERMAN_WPS_LK201-BG.A1KMTD            GERMAN_A1_LK201-BG.A1KMT        GERMAN_WPS_LK201-BA.A1KMTD            GERMAN_A1_LK250-AG.A1KMT        GERMAN_WPS_LK250-AG.A1KMT  E            SPANISH_A1_LK201-AA.A1KMT       SPANISH_WPS_LK201-AA.A1KMT E            SPANISH_A1_LK201-BA.A1KMT       SPANISH_WPS_LK201-BA.A1KMTcE            SPANISH_A1_LK201-BS.A1KMT       SPANISH_WPS_LK201-BS.A1KMT E            SPANISH_A1_LK201-LS.A1KMT       SPANISH_WPS_LK201-LS.A1KMT E            SPANISH_A1_LK250-AS.A1KMT       SPANISH_WPS_LK250-AS.A1KMT   3            A list of supported keyboards is held ino*            OA$DATA_SHARE:OA$KEYBOARDS.DAT.  8            To invoke the keyboard mapping tables, enter:  3            $ OFFICESERVER/KEYBOARD=keyboard_mapping   A            where keyboard_mapping is the identity of the requiredd            keyboard.        C-10 ENGLISH Kit     O      H                               C.6 Information on the GB Market Component    9         C.6.2 Modems Supported by the GB Market Component   >               Hayes and Hayes-compatible modems are supported.                                                                                    H                                                         ENGLISH Kit C-11                       H                                                                        DH         ________________________________________________________________  H                                         Information on Market Components      E               If your Office Server license and support agreement are G               for a market component other than the US or GB componentsdD               with the English language kit, you can find the marketA               information that you need in this appendix. You canPH               install the market component from the Office Server media.  H               For information on the US or GB components, see Appendix C  F               The Office Server installation procedure prompts you forF               the two-letter market code for the market component thatD               you want to install. Follow the installation procedure%               described in Chapter 2.S  H               For all market components, the keyboard mapping tables are"               invoked by entering:  6               $ OFFICESERVER/KEYBOARD=keyboard_mapping  D               where keyboard_mapping is the identity of the requiredD               keyboard. A list of these keywords is held in OA$DATA_H               SHARE:OA$KEYBOARDS.DAT (see DIGITAL Office Server Managing"               from a VT Terminal).  2               Each of the kits has three savesets:                 o  A1Cmc060.At                 o  A1Cmc060.B                  o  A1Cmc060.Cn  C               where mc is the two-letter market code defined in thenE               tables in this chapter, for example, BE for the Belgianr               market component.e  H                                     Information on Market Components D-1           !      D.1 Belgian Market Component_    !      D.1 Belgian Market Component   D            Table D-1 lists useful information for the Belgian market2            component of Office Server Version 6.0.  >            Table D-1 Useful Information for the Belgian MarketE            __________Component_______________________________________a  E            Information___________Value____________Use________________l  B            Product name          A1CBE060         Installation andD                                                   naming of savesets  E            Market code           BE               During installationa  +                  Office Server date format:a  ?            Alphanumeric          DD-MMM-YYYY      Office Server   ?            Numeric               DD-MM-YY         Office Server   :            WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUS  :            WPS-PLUS time         colon (:)        WPS-PLUS            separator  &                       Currency format:  :            Currency symbol       BEF              WPS-PLUS  :            Decimal separator     comma (,)        WPS-PLUS  E            Thousand_separator____dot_(.)__________WPS-PLUS___________   #      D.2 Brazilian Market Component   ?            Table D-2 lists useful information for the Brazilian 9            market component of Office Server Version 6.0.   @            Table D-2 Useful Information for the Brazilian MarketE            __________Component_______________________________________A  E            Information___________Value____________Used_For___________   B            Product name          A1CBZ060         Installation andD                                                   naming of savesets  E            Market code           BZ               During installationo  E                                              (continued on next page)m  )      D-2 Information on Market Components     f      H                                           D.2 Brazilian Market Component    D               Table D-2 (Cont.) Useful Information for the BrazilianH               __________________Market_Component________________________  H               Information___________Value____________Used_For___________  =               WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUSv  =               WPS-PLUS time         colon (:)        WPS-PLUS                separator   -                    Office Server date format:i  B               Alphanumeric          DD-MMM-YYYY      Office Server  B               Numeric               YY-MM-DD         Office Server  (                         Currency format:  =               Currency              Esc              WPS-PLUS   =               Decimal separator     dot (.)          WPS-PLUSP  H               Thousand_separator____comma_(,)________WPS-PLUS___________  %         D.3 Canadian Market Component_  H               Table D-3 lists useful information for the Canadian market5               component of Office Server Version 6.0.t  B               Table D-3 Useful Information for the Canadian MarketH               __________Component_______________________________________  H               Information___________Value____________Use________________  E               Product name          A1CCA060         Installation andBG                                                      naming of savesets1  H               Market code           CA               During installation  -                    Office Server date format:_  B               Alphanumeric          DD MMM YYYY      Office Server  B               Numeric               DD/MM/YY         Office Server  =               WPS-PLUS date format  dd mmmmmm yyyy   WPS-PLUSG  =               WPS-PLUS time         colon (:)        WPS-PLUS                separatorM  (                         Currency format:  H                                                 (continued on next page)  H                                     Information on Market Components D-3 P  S      "      D.3 Canadian Market Component    @            Table D-3 (Cont.) Useful Information for the CanadianE            __________________Market_Component________________________   E            Information___________Value____________Use________________   :            Currency symbol       $                WPS-PLUS  :            Decimal separator     comma (,)        WPS-PLUS  E            Thousand_separator____dot_(.)__________WPS-PLUS___________e        D.4 Dutch Market Component   B            Table D-4 lists useful information for the Dutch market2            component of Office Server Version 6.0.  <            Table D-4 Useful Information for the Dutch MarketE            __________Component_______________________________________m  E            Information___________Value____________Use________________t  B            Product name          A1CNL060         Installation andD                                                   naming of savesets  E            Market code           NL               During installation_  +                  Office Server date format:   ?            Alphanumeric          DD-MMM-YYYY      Office Server   ?            Numeric               DD-MM-YY         Office Server   :            WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUS  :            WPS-PLUS time         colon (:)        WPS-PLUS            separator  &                       Currency format:  :            Currency symbol       F                WPS-PLUS  :            Decimal separator     comma (,)        WPS-PLUS  E            Thousand_separator____dot_(.)__________WPS-PLUS___________          D.5 French Market Component  C            Table D-5 lists useful information for the French market 2            component of Office Server Version 6.0.  )      D-4 Information on Market ComponentsW P         H                                              D.5 French Market Component    @               Table D-5 Useful Information for the French MarketH               __________Component_______________________________________  H               Information___________Value____________Use________________  E               Product name          A1CFR060         Installation and G                                                      naming of savesets   H               Market code           FR               During installation  -                    Office Server date format:P  B               Alphanumeric          DD-MMM-YYYY      Office Server  B               Numeric               DD/MM/YY         Office Server  =               WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUSp  =               WPS-PLUS time         colon (:)        WPS-PLUS_               separator   (                         Currency format:  =               Currency symbol       FF               WPS-PLUSE  =               Decimal separator     comma (,)        WPS-PLUS   H               Thousand_separator____blank_(_)________WPS-PLUS___________  #         D.6 German Market Component_  F               Table D-6 lists useful information for the German market5               component of Office Server Version 6.0.   @               Table D-6 Useful Information for the German MarketH               __________Component_______________________________________  H               Information___________Value____________Use________________  E               Product name          A1CDE060         Installation andIG                                                      naming of savesetsH  H               Market code           DE               During installation  -                    Office Server date format:   B               Alphanumeric          DD.MMM.YYYY      Office Server  B               Numeric               DD.MM.YY         Office Server  =               WPS-PLUS date format  dd.mmm.yyyy      WPS-PLUS   H                                                 (continued on next page)  H                                     Information on Market Components D-5                  D.6 German Market Component    >            Table D-6 (Cont.) Useful Information for the GermanE            __________________Market_Component________________________G  E            Information___________Value____________Use________________o  :            WPS-PLUS time         colon (:)        WPS-PLUS            separator  &                       Currency format:  :            Currency symbol       DM               WPS-PLUS  :            Decimal separator     comma (,)        WPS-PLUS  :            Thousand separator    dot (.)          WPS-PLUS  E            Page_size_____________72_______________Printer_settings____        D.7 Swiss Market Component   B            Table D-7 lists useful information for the Swiss market2            component of Office Server Version 6.0.  <            Table D-7 Useful Information for the Swiss MarketE            __________Component_______________________________________,  E            Information___________Value____________Use________________   B            Product name          A1CCH060         Installation andD                                                   naming of savesets  E            Market code           CH               During installationi  +                  Office Server date format:   ?            Alphanumeric          DD.MMM.YYYY      Office Server   ?            Numeric               DD.MM.YY         Office Server   :            WPS-PLUS date format  dd.mmm.yyyy      WPS-PLUS  :            WPS-PLUS time         colon (:)        WPS-PLUS            separator  &                       Currency format:  :            Currency symbol       SFr              WPS-PLUS  :            Decimal separator     dot (.)          WPS-PLUS  E            Thousand_separator____apostrophe_(')___WPS-PLUS___________I  )      D-6 Information on Market Componentsm V  e                          E      ________________________________________________________________   E                                                                 Index     A      A                                    Customizations (cont'd) ;      ___________________________           migrating,  5-11 :      A1CONFIG.DAT,  5-6                    reviewing afterA      A1V50START.COM,  5-5                     installation,  5-11D      A1V60START.COM,  5-6_+      Applications                         D E        replacing help modules,            ___________________________ 3          5-14                             DCLTABLES :      AUTOGEN,  1-25                        replacing,  5-95                                           DDS$STARTUP_B      B                                     adding to site-specific@      ___________________________              startup procedure,2      Backing up,  1-44                        5-29  3                                           DEC Notes A      C__________________________           starting before Office   :      CART                                     Server,  5-7D        running after                      DELETE_OBSOLETE_FILES.COM,0          installation,  5-11                5-138      CART resolution procedure            Deleting filesA        running and editing, 5-12           postinstallation,  5-9 A      Checklist                            Deleting obsolete files E        postinstallation tasks,              after installation,  5-13l/          5-1                              Disks <      Cluster                               backing up,  1-44B        VMSmail Gateway                    Disk space requirements,0          configuration,  5-19               1-27      ConfiguringE        VMSmail Gateway, 5-19              E__________________________m=      Correcting system set-up             Error messages, 4-3_0         errors, 1-41                      Errors7      Customizations                        fatal,  1-41_;        linking Office Server to            non-fatal,  1-41t          include,  5-15   E                                                               Index-1r    e            C                                           Installing missing images C      F__________________________            postinstallation,  5-10a-      Fatal errors,  1-41                  IVP ?      Files, deleting                       error messages,  4-3           postinstallation, 5-9E      Form libraries                       L__________________________t  2        recompiling, 5-10                  Licenses  A                                            prerequisite products, 2      G__________________________              1-15  9      Global page file sections            Licensing, 1-14PB         (GBLPAGFIL), 1-23                 Linking Office Server toC      Global pages (GBLPAGES),               include customizations,O0         1-23                                5-157      Global sections                      Logical names ;         (GBLSECTIONS), 1-23                assigning,  1-28 0                                           Logins:      H                                     disallow,  1-44       ___________________________E      Help modules                         M__________________________ 1        replacing for your                 MailboxCC          application,  5-14                adding for remote Officet  C      I                                        Server systems,  5-18 ;      ___________________________           modifying,  5-19_8      Images                               Mail directoryB        missing, 5-10                       setting up with MessageE        required, 1-32                         Router outside cluster, 2      Installation                             5-24C        aborting, 2-2                       setup for Message Router D        disk space required, 1-27              in same cluster,  5-20A        time required, 2-2                  starting up for remote 8      Installation of optional                 use,  5-293         software                          MailWorks ;        order of, 1-16                      migration,  1-42 =      Installed images                     Message Router, A-2f<        required, 1-32                      setting up,  5-18@      Installing account                   Message Router mailbox?        quotas required during              modifying for mixed-aD          installation,  1-17                  architecture clusters,2        valid rights identifier,               5-19@          1-17                             Message Router VMSmail  9                                             Gateway,  A-2e        Index-2                 2         Migrating                           Remote=          customizations,  5-11                VMSmail Gateway_D                                                  configuration, 5-197         N__________________________         Remote mailaE         Non-fatal checks, repeating           setting up with MAILbusTC           ,  1-41                                400 MTA and Compaq_<         Non-fatal errors, 1-41                   X.500, 5-15E                                               setting up with Message =         O__________________________              Router, 5-16 A         OA$DIRECT_PRIME, 5-20               Remote Mail directory @         Office Server                         starting up,  5-29G          starting on all nodes,             Repeating non-fatal checks,a3             5-5                                1-41   -         Optional software                   SfG          order of installation,             ___________________________SA             1-16                            SITELINK60.COM,  5-15 A         Order of installation of            Site-specific startup =           optional software,  1-16             procedure, 5-6 G                                               adding DDS$STARTUP,  5-29_<         P                                   Software Product?         ___________________________            Description, A-2o5         PC option, 1-41                     SPD,  A-2 4         Perform all preinstallation         StartingA           checks (PC) option,  1-41           Office Server,  5-5 =         Preinstallation                     Startup procedure <          checks,  1-41                        creating,  5-6D         Preparing system for                  editing site-specific,4           installation,  1-43                    5-6A         Prerequisite software                 site specific,  5-6sG          licenses,  1-15                    SYS$STARTUP:A1V60START.COM,n  2                                                5-62         R__________________________         System  ;         Recompiling                           preparing forcC          form libraries,  5-10                   installation, 1-43 7         Registering software                System disk ?           licenses,  1-15                     backing up,  1-44 C         Release notes, 1-7                  System parameter valuesaD          printing,  1-7                       changing with AUTOGEN,5          reading,  1-7                           1-25            Relinkingo          recommendations,  5-15   H                                                                  Index-3                   E      T__________________________          U__________________________r  /      Target disk                          Usersc9        backing up, 1-44                    log out,  1-44f      Time required forE         installation, 2-2                 V___________________________  9                                           VMSmail Gateway_=                                            configuring,  5-191                                                                            Index-4                                                                                                                                            