                                             H                     Compaq_Office_Server________________________________&                     Installation Guide        D                     Revision/Update Information:  Updated for CompaqG                                                   Office Server Version 5                                                   6.1   I                     Operating system:             OpenVMS VAX Version 7.2 H                                                   or higher, and OpenVMSH                                                   Alpha Version 7.2-2 or8                                                   higher                 J           ________________________________________________________________           January 2002  B           Possession, use, or copying of the software described inC           this documentation is authorized only pursuant to a valid C           written license from Compaq or an authorized sublicensor.   @           While Compaq believes the information included in thisE           publication is correct as of the date of publication, it is +           subject to change without notice.   >           Compaq Computer Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  <            2002, Compaq Information Technologies Group, L.P  C           COMPAQ, the Compaq logo, the Digital logo, ALL-IN-1, DEC, C           DECnet, MAILbus and VAX are registered in U.S. Patent and            Trademark Office  D           DATATRIEVE, DECwindows, OpenVMS, Tru64, VMScluster, VT andA           WPS-PLUS are trademarks of Compaq Computer Corporation.   D           Other product names mentioned herein may be the trademarks(           of their respective companies.  E           This document was prepared using VAX DOCUMENT, Version 2.1.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................     ix   +   1  Preparing Your System for Installation   C         1.1   Checklist of Preinstallation Tasks............    1-1 5         1.2   Reading and Printing the Online Release C               Notes.........................................    1-7 C         1.3   Checking Prerequisite and Optional Software...    1-8 C         1.4   Licensing.....................................   1-15 7         1.4.1     Registering License PAKs for Software C                   Provided with Office Server Version 6.1...   1-15 3         1.5   Example Order for Installing Optional C               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 with C                     AUTOGEN.................................   1-25 9         1.6.4.2     Updating Non-Dynamic System Parameter C                     with AUTOGEN............................   1-25 3         1.6.5     Disk Space on Your System Disk or C                   Alternate Working Device..................   1-26 C         1.6.6     Using the OA$LIB_SHARE Disk as the AWD....   1-27 7         1.6.7     Disk Space for Office Server Areas on C                   Target Disks..............................   1-27 C         1.6.8     Assigning Logical Names to Your Disks.....   1-28 9         1.6.9     New Installation: Disk Space for Office C                   Server Areas..............................   1-29 6         1.6.10    Upgrade Installation: Disk Space forC                   Office Server Areas.......................   1-30     C                                                                 iii                    :           1.6.11    Addition of Architecture Support: DiskE                     Space for Office Server areas.............   1-31 E           1.6.12    Disk Quota Allocation.....................   1-32 E           1.6.13    Installed Images..........................   1-32 8           1.6.14    Installing FDVMSG.EXE and FDVSHR.EXEE                     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 4           1.8   Using the MAILbus 400 MTA and CompaqE                 Enterprise Directory for eBusiness............   1-39 E           1.9   Using a Remote Message Router.................   1-40 :           1.9.1     Create an Office Server Mailbox on theE                     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-42 ;           1.10.2    Running the Perform all Preinstallation E                     Checks(PC) Option.........................   1-42 3           1.11  Final System Preparation Tasks: New E                 Installations.................................   1-43 7           1.12  Final System Preparation Tasks: Upgrade E                 Installations ................................   1-44 E           1.12.1    Shut Down Office Server...................   1-44 E           1.12.2    Deinstall Files Installed in Memory.......   1-45 E           1.13  Back Up Your System and Target Disks..........   1-45   <     2  Installation Procedure: New, Upgrade and Architecture        Support  :           2.1   Installation Procedure for New and UpgradeE                 Installations.................................    2-3 E           2.2   Adding or Upgrading Architecture Support......   2-30 E           2.2.1     Before You Start..........................   2-31 5           2.2.2     Installation Procedure for Adding E                     Architecture Support......................   2-31 E           2.3   Automatic Postinstallation Tasks..............   2-39 E           2.4   Manual Postinstallation Tasks.................   2-40                    iv                   7         3  Installation Procedure: Additional Languages   B               3.1   Installation Procedure for Additional LanguageI                     Installations.................................    3-2 :               3.2   Installing Architecture Support for anI                     Additional Language...........................    3-9   *         4  Installation Errors and Failure  I               4.1   Common Errors.................................    4-1 I               4.2   Failure During Postinstallation...............    4-2 B               4.2.1     Failure of Upgrade Installations in SafetyI                         Mode......................................    4-2 ;               4.2.2     Failure of Upgrade Installations in I                         Non-Safety Mode...........................    4-2 I               4.2.3     Full Installations........................    4-2 ;               4.2.4     Failure Due to Insufficient Dynamic I                         Memory....................................    4-3 I               4.3   Error Messages when Running the IVP...........    4-3 I               4.4   IVP Failure...................................    4-5   !         5  Postinstallation Tasks   I               5.1   Checklist of Manual Postinstallation Tasks....    5-1 9               5.2   Start Office Server on all Nodes in a I                     VMScluster System.............................    5-5 =               5.3   Create or Modify the Site-specific Office I                     Server Startup Procedure......................    5-6 I               5.4   Edit the Site-specific Startup Procedure......    5-6 <               5.4.1     Installations With Compaq Enterprise?                         Directory for eBusiness and the MAILbus I                         400 MTA...................................    5-7 I               5.4.2     Installations with Message Router.........    5-7 I               5.5   Replace the DCLTABLES on Cluster Systems......    5-9 I               5.6   Delete Files That Are No Longer Required......    5-9 I               5.7   Install Missing Images........................    5-9 I               5.8   Recompile Form Libraries......................   5-10 7               5.9   Migrating Your Customizations After I                     Upgrading.....................................   5-10 I               5.9.1     Running the CART Resolution Procedure.....   5-12 I               5.9.2     Deleting Obsolete Files...................   5-13 ;               5.9.3     Replacing the Help Modules for Your I                         Application...............................   5-14     I                                                                         v                    6           5.10  Migrate SITELINK60 Using CustomizationE                 Management....................................   5-14 8           5.11  Link Office Server to Include Code-levelE                 Customizations................................   5-15 =           5.12  Setting up Remote Mail When Using the MAILbus E                 400 MTA.......................................   5-15 9           5.13  Setting up Remote Mail When Using Message E                 Router........................................   5-15 E           5.13.1    Create a Mailbox for Office Server........   5-17 8           5.13.2    Modifying the Message Router MailboxE                     Entry.....................................   5-19 >           5.13.3    Configuring the VMSmail Gateway for RemoteE                     Access....................................   5-19 ;           5.13.4    Setting Up the Message Router Directory E                     Service as the Mail Directory.............   5-20 3           5.13.4.1    Message Router is in the Same E                       VMScluster..............................   5-20 7           5.13.4.2    Message Router is not in the Same E                       VMScluster..............................   5-24 ;           5.13.5    Remote Message Router Directory Service E                     Startup Procedure.........................   5-28 E           5.14  WPS-PLUS Login Command Procedure..............   5-29 E           5.15  Moving the CDA DOC_STYLE Files................   5-29   6     A  Office Server Version 6.1 Files and Directories  E           A.1   Files in the Office Server Kit................    A-1 4           A.2   Files Installed in Non-Office ServerE                 Directories...................................    A-1        B  ENGLISH Kit  E           B.1   About Your ENGLISH Kit........................    B-2 E           B.1.1     Distribution Media........................    B-2 E           B.1.2     Savesets Provided.........................    B-2 E           B.2   Disk Space Requirements.......................    B-3 =           B.2.1     Disk Space Required on the System Disk or E                     Alternate Working Device (AWD)............    B-4 ;           B.2.2     Disk Space for Language Files on Target E                     Disks.....................................    B-4 3           B.3   Information on the English Language E                 Component.....................................    B-7            vi                   7               B.4   Information on the British Language I                     Component.....................................    B-7 I               B.5   Information on the US Market Component........    B-8 <               B.5.1     Keyboards Supported by the US MarketI                         Component.................................    B-8 9               B.5.2     Modems Supported by the US Market I                         Component.................................    B-9 I               B.6   Information on the GB Market Component........    B-9 <               B.6.1     Keyboards Supported by the GB MarketI                         Component.................................   B-10 9               B.6.2     Modems Supported by the GB Market I                         Component.................................   B-11   +         C  Information on Market Components   I               C.1   Belgian Market Component......................    C-2 I               C.2   Canadian Market Component.....................    C-2 I               C.3   Dutch Market Component........................    C-3 I               C.4   French Market Component.......................    C-4 I               C.5   German Market Component.......................    C-4 I               C.6   Swiss Market Component........................    C-5   
         Index              Tables  I               1-1       Preinstallation Checklist.................    1-2   I               1-2       Prerequisite and Optional Software........    1-9   A               1-3       Process Account Quotas for the Installing I                         Account...................................   1-18   7               1-4       Minimum System Parameter Values I                         Required..................................   1-19   I               1-5       Changing System Parameter Values..........   1-24   ?               1-6       New Installation: Disk Space for Office I                         Server Areas..............................   1-30   =               1-7       Upgrade Installations: Disk Space for I                         Office Server Areas ......................   1-31   6               1-8       Addition, Upgrade or Update of<                         Architecture Support: Disk Space forI                         Office Server Areas.......................   1-32   I               1-9       Installed Images Required on VAX..........   1-32   I                                                                       vii                    E           1-10      Installed Images Required on Alpha........   1-34   6           2-1       Information About the InstallationE                     Procedure.................................    2-2   >           2-2       Installation Procedure for New and UpgradeE                     Installations.............................    2-4   8           2-3       When to Install/Upgrade VAX or AlphaE                     Architecture Support......................   2-30   5           2-4       Installation Procedure for Adding E                     Architecture Support......................   2-32   <           3-1       Installation Procedure for An AdditionalE                     Language .................................    3-3   :           3-2       Installation Procedure for Addition of:                     Architecture Support for an AdditionalE                     Language..................................    3-9   E           5-1       Postinstallation Tasks....................    5-1   =           5-2       Editing the OpenVMS Site-specific Startup E                     File......................................    5-8   E           5-3       Tasks for Setting up Remote Mail..........   5-16   E           B-1       Savesets Provided with the ENGLISH Kit....    B-2   >           B-2        Disk Space Required on the System Disk orE                     AWD (Blocks)..............................    B-4   6           B-3       Disk Space for Language Files: NewE                     Installation..............................    B-5   :           B-4       Disk Space for Language Files: UpgradeE                     from Version 3.1..........................    B-6   7           B-5       Disk Space for Language Files: Add,OE                     Upgrade or Update Architecture Support....    B-6l  6           B-6       Useful Information for the EnglishE                     Language Component........................    B-7   6           B-7       Useful Information for the BritishE                     Language Component........................    B-7m  8           B-8       Useful Information for the US MarketE                     Component.................................    B-8   8           B-9       Useful Information for the GB MarketE                     Component.................................    B-9   =           C-1       Useful Information for the Belgian Market_E                     Component.................................    C-2y  >           C-2       Useful Information for the Canadian MarketE                     Component.................................    C-2m       viii r  d              ?               C-3       Useful Information for the Dutch MarkethI                         Component.................................    C-3   @               C-4       Useful Information for the French MarketI                         Component.................................    C-4r  @               C-5       Useful Information for the German MarketI                         Component.................................    C-5c  ?               C-6       Useful Information for the Swiss MarketgI                         Component.................................    C-5r                                                                    I                                                                        ixe g  l                        I         _________________________________________________________________   I                                                                   Prefacec               About This BookL  H               Before you use this book, you must plan your Office ServerC               Version 6.1 installation by reading the Compaq OfficesC               Server Planning and Setup Guide. Note that the CompaqDD               Office Server Planning and Setup Guide was not updatedI               for Office Server Version 6.1, but that the instructions it                 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.1a                  installation.  3               2. Install Office Server Version 6.1.   D               3. Set up Office Server Version 6.1 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 provides D               the disk space values for installing the Office ServerI               Version 6.1 kit, and information on the language and market.D               components that you will need during the installation.           Prerequisite Knowledge  E               This guide assumes that you have read the Compaq Office .               Server Planning and Setup Guide.  G               To install Office Server Version 6.1 you must be familiar.)               with the VMSINSTAL utility.   I                                                                        ixe a  e              2     The Office Server Management Documentation Set  @           The following guides form the Office Server management           documentation set:  :           o  Compaq Office Server Planning and Setup Guide  4           o  Compaq Office Server Installation Guide  <           o  The online help for Office Server Administrator  C              ________________________ Note ________________________.  ?              The V4.0 management guide may still be useful, butgA              the most up-to-date management information is in thes.              Office Server Administrator help.  C              ______________________________________________________   2     Terminology and Conventions Used in this Guide  C           The following table lists the terminology and conventions            used in this guide..  E           Office Server    Means the Compaq Office Server for OpenVMS 0                            Alpha and OpenVMS VAX  C           OpenVMS Alpha    Means the OpenVMS Alpha operating system   A           OpenVMS VAX      Means the OpenVMS VAX operating system   @           UCX              Means DEC TCP/IP Services for OpenVMS  >           AIDA Server      Means the Distributed Access Server  E           Client user      Means a user of a client of Office Server. 0                            Client users include:  C                            o  Users of personal computers (PCs) and1<                               workstations (PC client users)  >                            o  Users of the video terminal (VT)B                               interface to Office Server software,D                               when they choose options that make useC                               of an Office Server server (VT client.$                               users)  B           Architecture     Is a term used to differentiate between@                            OpenVMS VAX systems and OpenVMS Alpha"                            systems       x     .                       Related Documentse  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 Gatewayst  :               o  Compaq Enterprise Directory for eBusiness                 o  DECnet/OSIT                                                          I                                                                        xi. .  .                    I                                                                         1 I         _________________________________________________________________I  I                                    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.e  G               You must read the Compaq Office Server Planning and SetuplG               Guide before you install Office Server. The guide covers:.  @               o  Information about this version of Office Server  D               o  Installation planning, including a checklist of allH                  the decisions that you need to make before starting the                  installationd  A                  In addition, if your system has been customized,uD                  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 Checking.H                  and Resolution Tool (CART) to check your customizations2                  before you upgrade Office Server.  %               o  Mail system planning   .               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..  .         1.1 Checklist of Preinstallation Tasks  G               To prepare your system for an Office Server installation, 8               you must do the tasks listed in Table 1-1.      I                                Preparing Your System for Installation 1-1o e  g      *     Preparing Your System for Installation*     1.1 Checklist of Preinstallation Tasks    E           Table_1-1_Preinstallation_Checklist________________________   D                                             For further information,E           Task___Description________________see______________________   A           1      Check the kit contents     The Bill of Materials B                                             for a list of what theC                                             distribution kit should 4                                             contain.  ?                                             Contact your Compaqp=                                             representative ifAB                                             your kit is damaged or7                                             incomplete.h  E           ___________________________________________________________E  '           2      Read the READ ME FIRST *                  letter if one is supplied                  with your kit  E           ___________________________________________________________   @           3      Make sure that you have    Compaq Office ServerD                  planned your installation  Planning and Setup Guide'                  and Office Server mail.#                  system. The Compaq '                  Office Server Planningc%                  and Setup Guide also '                  lists any prerequisite.)                  configuration tasks thatc%                  must be done for the (                  messaging products that%                  you plan to use with %                  Office Server. These (                  tasks must be completed&                  before you start your                  installation.  E           ___________________________________________________________.  ;           4      Read the online product    Section 1.2 foruE                  release notes provided     instructions on accessinge>                  with the kit               the release notes.  E                                              (continued on next page)t  .     1-2 Preparing Your System for Installation    o      I                                    Preparing Your System for InstallationaI                                    1.1 Checklist of Preinstallation Tasksh    I               Table_1-1_(Cont.)_Preinstallation_Checklist________________.  H                                                 For further information,I               Task___Description________________see______________________   I               ___________________________________________________________   ;               5      Check that you have the    Section 1.3 )                      correct versions of:m  (                      o  The prerequisite(                         software for the$                         installation  -                      o  Any optional software.(                         that you want to                         installi  I               ___________________________________________________________.  ;               6      Check that you have a      Section 1.4.*                      valid license for the'                      installing account5  I               ___________________________________________________________.  =               7      Register the License       Section 1.4.1 .                      PAKs for the prerequisite*                      and optional software)                      provided with OfficeH                      Server.  I               ___________________________________________________________u  I                                                  (continued on next page)i                    I                                Preparing Your System for Installation 1-3. .         *     Preparing Your System for Installation*     1.1 Checklist of Preinstallation Tasks    E           Table_1-1_(Cont.)_Preinstallation_Checklist________________a  D                                             For further information,E           Task___Description________________see______________________g  ?           8      Check the installation     Section 1.6 for the.?                  procedure requirements:    values required and E                  o  For the installing      instructions for checkingp>                     account                 and changing these7                                             parameters. %                  o  System parameters                     o  Disk space  !                  o  Logical names.  $                  o  Installed images  #                  o  The location of !                     DCLTABLES.EXE   E           ___________________________________________________________n  8           9      For upgrade                Section 1.7.&                  installations, do any"                  additional tasks.  E           ___________________________________________________________.  E                                              (continued on next page)n                              .     1-4 Preparing Your System for Installation m  e      I                                    Preparing Your System for Installation I                                    1.1 Checklist of Preinstallation Tasks     I               Table_1-1_(Cont.)_Preinstallation_Checklist________________   H                                                 For further information,I               Task___Description________________see______________________   A               10     Check that all             Section 1.3 lists-I                      prerequisite and           prerequisite and optionalaF                      optional software is       software. In addition,G                      installed, configured      you may want to install I                      and running before you     DATATRIEVE or ACMS if younI                      start the Office Server    are planning to use theseiD                      installation.              products with Office7                                                 Server.   @                                                 All prerequisiteG                                                 messaging products such D                                                 as Message Router orC                                                 the MAILbus 400 MTA E                                                 and Compaq Enterprise G                                                 Directory for eBusinesshB                                                 must be installed,F                                                 configured and runningI                                                 before you install Office F                                                 Server. See the CompaqF                                                 Office Server Planning@                                                 and Setup Guide.  ?                                                 For a suggested C                                                 order of installing F                                                 optional software, see<                                                 Section 1.5.  I               ___________________________________________________________   ;               11     If you are installing a    Section 1.8r-                      new Office Server system +                      with Compaq Enterprisee,                      Directory for eBusiness-                      and the MAILbus 400 MTA, .                      check that these products,                      have been installed and*                      configured correctly.  I                                                  (continued on next page)o  I                                Preparing Your System for Installation 1-5n h  p      *     Preparing Your System for Installation*     1.1 Checklist of Preinstallation Tasks    E           Table_1-1_(Cont.)_Preinstallation_Checklist________________5  D                                             For further information,E           Task___Description________________see______________________r  E           ___________________________________________________________   8           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           ___________________________________________________________k  8           13     It is recommended that     Section 1.10(                  you run the Perform all'                  preinstallation checksi*                  (PC) option to check that(                  your system is prepared*                  for the installation. The'                  PC option runs througha*                  the installation to check&                  that you have all the'                  prerequisite licenses, )                  software, disk space and.(                  installation parameters)                  correctly set up on your                   system.  E           ___________________________________________________________f  @           14     Do the final system        Section 1.11 for new=                  preparation tasks.         installations andaD                                             Section 1.12 for upgrade:                                             installations.  E           ___________________________________________________________   8           15     Back up your system and    Section 1.13E           _______target_disks._______________________________________c        .     1-6 Preparing Your System for Installation .  .      I                                    Preparing Your System for Installation I                         1.2 Reading and Printing the Online Release Notes     9         1.2 Reading and Printing the Online Release Notesi  E               Online release notes are provided with the language and.C               market components of Office Server. The release notes G               contain information that was unavailable before the books H               went to print. It is recommended that you read the releaseI               notes, because they may contain information relating to the F               installation. You can access the release notes using theF               VMSINSTAL procedure before you install the Office Server               software.   E               There are two parts to the Office Server release notes:e  .               o  Release Notes Part 1 Language  E                  This part contains the release notes specific to the 8                  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.i  C               To read or print the release notes, do the following:   B               1. Log in to the privileged OpenVMS system manager's?                  account and enter the following command lines:   )                  $ SET DEFAULT SYS$UPDATEaB                  $ @VMSINSTAL product device:[directory] OPTIONS N  I                  where device:[directory] is the location of the languagelG                  kit and product is the product code. The product codes                   are:.  E                  o  A1Llang061 for the Release Notes Part 1 Language, H                     where lang is the 2-letter code for the language you"                     are installing  E                  o  A1Cmarket061 for the Release Notes Part 2 Market,fD                     where market is the 2-letter code for the market0                     component you are installing  =                  If you are performing an additional language D                  installation, you need only print the Office ServerI                  Release Notes Part 1 Language that is supplied with youro                  kit.C  I                                Preparing Your System for Installation 1-7r    t      *     Preparing Your System for Installation5     1.2 Reading and Printing the Online Release Notes_    D           When you have read or printed the release notes, terminateC           the installation procedure. If you have accessed only oneaC           part of the release notes, repeat the procedure to accessnE           the other part. The following files are placed in SYS$HELP:_  A           o  A1Llang061.RELEASE_NOTES, for the Release Notes Part @              1 Language, where lang is the 2-letter code for the(              language you are installing  E           o  A1Cmarket061.RELEASE_NOTES, for the Release Notes Part 2 E              Market, where market is the 2-letter code for the market )              component you are installing   3     1.3 Checking Prerequisite and Optional Softwaree  ?           Table 1-2 provides information about the prerequisitecC           software for an Office Server installation. It also listsc=           the optional software that you may want to install.n  *           The following definitions apply:  C           o  Prerequisite means that the software must be installedoD              before you install Office Server. The installation will@              fail if the prerequisite software is not installed.  E           o  Optional means that the software is not required for therC              Office Server installation. Optional software providesaD              additional functionality and the optional software thatB              you install depends on the requirements at your site.D              For example, if you want to use Group Conferencing, you$              must install DEC Notes.  C              ________________________ Note ________________________   =              Both the prerequisite software, and any optionaleB              software that you want to install, must be installed,=              configured and running before you install Office               Server.  C              ______________________________________________________           .     1-8 Preparing Your System for Installation m         I                                    Preparing Your System for Installation I                           1.3 Checking Prerequisite and Optional Software     I               Table_1-2_Prerequisite_and_Optional_Software_______________   -               Software         VAX      Alpha I               Product__________Version__Version_____Notes_________________  D               OpenVMS VAX      7.2 or   -           Prerequisite forH                                later                installation on VAX.  B                                                     Must be a fullE                                                     untailored systeml  D               OpenVMS Alpha    -        7.2-2 or    Prerequisite forC                                         later       installation onl:                                                     Alpha.  B                                                     Must be a fullE                                                     untailored systems  I               ___________________________________________________________d  D               DECnet (Phase    7.2      -           Prerequisite forD               IV) OpenVMS VAX                       remote messagingH                                                     using Message Router  D               DECnet (Phase    -        7.2         Prerequisite forD               IV) OpenVMS                           remote messagingH               Alpha                                 using Message Router  I               ___________________________________________________________   I                                                  (continued on next page)                             I                                Preparing Your System for Installation 1-9  w  a      *     Preparing Your System for Installation3     1.3 Checking Prerequisite and Optional Softwarea    E           Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______t  )           Software         VAX      AlphakE           Product__________Version__Version_____Notes________________Y  C           DECnet-Plus for  7.2      -           Prerequisite[1] foreD           OpenVMS VAX                           systems using CompaqD                                                 Enterprise Directory@                                                 for eBusiness orA                                                 Compaq Enterprise_=                                                 Directory forlA                                                 eBusiness and thei@                                                 MAILbus 400 MTA.  D                                                 Optional alternativeA                                                 for systems usingp?                                                 Message Router.   C           DECnet-Plus for  -        7.2-1 ECO2  Prerequisite[1] for D           OpenVMS Alpha                         systems using CompaqD                                                 Enterprise Directory@                                                 for eBusiness orA                                                 Compaq Enterprise_=                                                 Directory for A                                                 eBusiness and the @                                                 MAILbus 400 MTA.  D                                                 Optional alternativeA                                                 for systems usingi?                                                 Message Router.   E           ___________________________________________________________   E           [1]DECnet-Plus_is_a_prerequisite_for_Compaq_Enterprise_____t  @           Directory for eBusiness. If you plan to migrate to use=           Message Router with Compaq Enterprise Directory for E           eBusiness, you must install DECnet-Plus as the prerequisite_C           for Compaq Enterprise Directory for eBusiness. For CompaqtC           Enterprise Directory for eBusiness, you must also installt=           the OSI Applications Kernel, OSAK, from the DECnet- @           Plus Applications component. See the Compaq EnterpriseE           Directory for eBusiness installation documentation for moret           information.  E                                              (continued on next page)a  /     1-10 Preparing Your System for Installationo r  s      I                                    Preparing Your System for Installation_I                           1.3 Checking Prerequisite and Optional Softwaree    I               Table_1-2_(Cont.)_Prerequisite_and_Optional_Software________  -               Software         VAX      Alpha_I               Product__________Version__Version_____Notes________________o  =               TCP/IP Services  V5.1 or  V5.1 or     Optional. G               for OpenVMS      later    later       Install if you want E               or other TCP                          to use the TCP/IP D               /IP software                          network protocolG               that emulates                         to communicate with_H               this[2]                               client applications.  I               ___________________________________________________________   =               Message Router   3.5      -           Optional._  I                                                     Install and configureRG                                                     if you want to sendhE                                                     remote mail using C                                                     Message Router.   I               ___________________________________________________________   <               Message Router   3.5      -           OptionalG               VMSmail Gateway                       Install if you wanty  E                                                     to send mail fromnI                                                     Office Server systems_H                                                     using Message RouterE                                                     to VMSmail users.D  I               ___________________________________________________________k  I               [2]For_supported_versions_of_other_TCP/IP_software_that____e  I               emulates TCP/IP Services for OpenVMS, see the Office Servern+               Software Product Description.   I                                                  (continued on next page)             I                               Preparing Your System for Installation 1-11i s  e      *     Preparing Your System for Installation3     1.3 Checking Prerequisite and Optional Softwareh    E           Table_1-2_(Cont.)_Prerequisite_and_Optional_Software________  )           Software         VAX      Alpha_E           Product__________Version__Version_____Notes________________   8           MAILbus 400      2.0c-    2.0c-150    OptionalE           MTA[3]           150 or   or later    Install and configure_B                            later                if you want to use  C                                                 the MAILbus 400 MTAs@                                                 for remote mail.@                                                 Note that CompaqD                                                 Enterprise DirectoryB                                                 for eBusiness is aD                                                 prerequisite for the@                                                 MAILbus 400 MTA.  E           ___________________________________________________________.  E           [3]Office_Server_can_also_connect_to_a_MAILbus_400_MTA_____d  >           installed on a remote node (OpenVMS or Tru64 UNIX) .  E                                              (continued on next page)                                           /     1-12 Preparing Your System for Installationn           I                                    Preparing Your System for Installation I                           1.3 Checking Prerequisite and Optional Software     I               Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______   -               Software         VAX      Alpha I               Product__________Version__Version_____Notes________________   C               Compaq           3.1 ECO  5.0         Prerequisite if G               Enterprise       3[5]                 you plan to use the D               Directory for                         MAILbus 400 MTA.H               eBusiness[4]                          Optional if you plan  E                                                     to continue using C                                                     Message Router.   I               ___________________________________________________________   <               MAILbus 400      1.2      -           OptionalG               Message Router                        Install if you want D               Gateway                               to exchange mail  C                                                     between Message F                                                     Router systems andC                                                     MAILbus 400 MTA <                                                     systems.  I               [4]DECnet-Plus_is_a_prerequisite_for_Compaq_Enterprise_____n  D               Directory for eBusiness. If you plan to migrate to useA               Message Router with Compaq Enterprise Directory for I               eBusiness, you must install DECnet-Plus as the prerequisite G               for Compaq Enterprise Directory for eBusiness. For Compaq G               Enterprise Directory for eBusiness, you must also install E               the OSI Applications Kernel, OSAK, from the DECnet-Plus A               Applications component. (Your directyory can run on E               either OpenVMS or Tru64 UNIX; see the Compaq Enterprise I               Directory for eBusiness installation documentation for morea               information.)_F               [5]After V3.0 had been released, Digital X.500 DirectoryD               Service became Compaq X.500. A further change happenedC               during the lifetime of Office Server Version 6.0. The_G               directory service, with added LDAP functions, was bundled @               with OpenVMS Alpha V7.3, with the new name 'CompaqB               Enterprise Directory for eBusiness'. This product isH               unlicensed and freely available with the operating system.C               On systems where only VAX machines are available, thetE               (licensed) V3.1 will still be a prerequisite for Officee               Server.   I                                                  (continued on next page)p  I                               Preparing Your System for Installation 1-13r    o      *     Preparing Your System for Installation3     1.3 Checking Prerequisite and Optional Software     E           Table_1-2_(Cont.)_Prerequisite_and_Optional_Software_______   )           Software         VAX      Alpha E           Product__________Version__Version_____Notes________________   E           ___________________________________________________________   9           DEC Notes        2.5      2.5         Optional.   >                                                 Install if youA                                                 want to use Group =                                                 Conferencing.   E           ___________________________________________________________   8           CDA Converter    2.2      -           Optional>           Library[6]                            Install if you  @                                                 require full CDAB                                                 support on OpenVMS4                                                 VAX.  8           DECwindows[7]    -        1.2         Optional  >                                                 Install if you@                                                 require full CDAB                                                 support on OpenVMS6                                                 Alpha.E           [6]The_installation_procedure_checks_for___________________   /           SYS$SHARE:CDA$ACCESS.EXE, Version 1.7m2           [7]The installation procedure checks for/           SYS$SHARE:CDA$ACCESS.EXE, Version 1.8 E           ___________________________________________________________   E           Note that if FMS is not installed, or the version installedvE           is not sufficiently recent for Office Server, the necessary "           files will be installed.  @           For information about the order of installing optional$           software, see Section 1.5.  C           For a list of all supported versions of products that cannD           be used with Office Server, see the Office Server Software           Product Description.  /     1-14 Preparing Your System for Installationr    p      I                                    Preparing Your System for Installation I                                                             1.4 Licensing              1.4 Licensingr  H               The way that your Office Server system is licensed dependsC               on the whether you are migrating from ALL-IN-1 or are &               installing a new system:  I               1. If you already have an ALL-IN-1 license, all appropriate C                  subsets for Office Server are enabled, and current G                  license Product Authorization Keys (PAKs) are honored.   >               2. If you are installing a new system, licensing@                  is controlled by Client Access Licenses (CALs).E                  Functionality is restricted to Electronic Messaging,t@                  Group Services, Directories, File Cabinet, WordD                  Processing (not including the WPS-PLUS editor), and                  User Setup.  H         1.4.1 Registering License PAKs for Software Provided with Office                Server Version 6.1  H               You must register the License PAKS for additional products>               supplied with the Office Server Version 6.1 kit.  A               The License PAKs for Message Router, Message RouteriH               gateway, DEC Notes, VAX FMS, and the CDA Converter LibraryE               can be registered automatically using the Office Servery0               Version 6.1 installation procedure  F               The License PAKs supplied for these products are for VAXI               installations only, and are for any number of users. If youEG               already have a license for one of these products, it willnH               be replaced by the license supplied with the Office Server               Version 6.1 kit.  H               To register the License PAKs automatically, follow Steps 1                to 5 in Table 2-2.  A               Enter RL when the installation prompts you with thee!               following question:   >               * Which installation do you wish to perform [1]:  F                 ________________________ Note ________________________  9                 Choosing the RL option does not start the                  installation.i  F                 ______________________________________________________  I                               Preparing Your System for Installation 1-15l           *     Preparing Your System for Installation     1.4 Licensing     C           The installation procedure checks your existing licenses, >           and if necessary registers and loads the appropriateE           licenses for the software products provided with the Office C           Server Version 6.1 kit. The installation then terminates.   E           For prerequisite or optional products that are not supplied @           with Office Server, you must register the license PAKs?           manually using the License Management Facility (LMF).i  6     1.5 Example Order for Installing Optional Software  B           After you have installed and configured the prerequisite?           software, install and configure the optional software A           products. See the appropriate product documentation for 6           installation and configuration instructions.  ;           The following installation order is suggested fory?           installing optional software before the Office Servere#           Version 6.1 installation:              1. Install ACMSq  5           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 MessageqC                 Router, make sure that Message Router is installed,lB                 configured and running before you start the Office@                 Server installation. If you plan to use a remote?                 Message Router Directory Service, you must do a A                 customized Message Router configuration to enable E                 remote Directory Service access and configure Message D                 Router exception reporting for the Directory Service?                 and Transfer Service according to your planning                  decisions.  <              o  For new installations with Compaq Enterprise?                 Directory for eBusiness and the MAILbus 400 MTA @                 make sure that you have installed and configuredA                 all the required components on your Office Server @                 node or cluster. Compaq Enterprise Directory forC                 eBusiness and the MAILbus 400 MTA must be correctly B                 installed, configured and running before you startC                 the new Office Server installation. See the MAILbus_E                 400 MTA and Compaq Enterprise Directory for eBusiness   /     1-16 Preparing Your System for Installation            I                                    Preparing Your System for InstallationsI                        1.5 Example Order for Installing Optional Software     I                     Planning chapter in the Compaq Office Server Planningn$                     and Setup Guide.  A               4. Install and configure optional gateway products.d  G                  o  The Message Router VMSmail Gateway if required witht#                     Message Router.q  F                  o  The MAILbus 400 Message Router Gateway if required-                     with the MAILbus 400 MTA.   E                  o  The MAILbus 400 SMTP Gateway if required with the $                     MAILbus 400 MTA.  #               5. Install DEC Notes.p  /         1.6 Installation Procedure Requirements   D               This section describes the requirements for installingE               Office Server Version 6.1. 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.1.  H               The installing account must have a valid rights identifierG               which is the same as the UIC for the account name. If yousF               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   B               The value that is displayed is the UIC of the systemE               account. To add the rights identifier, if it is not set #               up, do the following:   8               UAF> ADD/IDENTIFIER SYSTEM/VALUE:UIC=[1,4]               UAF> EXITy  E               The installing account must also have sufficient quotastB               to enable you to perform the installation. Table 1-3*               summarizes the requirements.  I                               Preparing Your System for Installation 1-17.           *     Preparing Your System for Installation+     1.6 Installation Procedure Requirements     E           Note that these values are sufficient for installation, butoE           they may not be appropriate for running Office Server. WheneD           you create new user accounts for Office Server Version 6.1?           the process quotas are set to the appropriate values.A  E           Table_1-3_Process_Account_Quotas_for_the_Installing_Account              AccountnE           Quota_________VAX____Alpha__Notes__________________________   !           BYTLM         64     64n"                         000    000  "           ENQLM         300    300  "           FILLM         200    200  D           JTQUOTA       1800   1800   JTQUOTA can be returned to itsA                                       normal system running valuea@                                       after the installation has0                                       completed.  !           PGFLQUOTA     25     65s"                         000    000E           _____________________pagelets______________________________        1.6.2 System Parametersa  ?           Table 1-4 lists the minimum required system parameter @           values for the installation. Depending on the kinds ofA           programs and applications running at your site, you may D           need higher values for some settings. If necessary, modify2           the parameters to at least these values.  C              ________________________ Note _________________________  A              You must check the OpenVMS system parameters on each C              node in the cluster on which you install Office Serverf              Version 6.1.   C              ______________________________________________________   B           The values for the system parameters and quotas given inB           this section are those specific to Office Server Version2           6.1 and are acceptable for most systems.  /     1-18 Preparing Your System for Installation            I                                    Preparing Your System for InstallationuI                                   1.6 Installation Procedure Requirementsf    E               Dynamic system parameters are labelled with a (D) aftertH               them. You do not need to reboot your system after changingF               dynamic system parameters. If you need to set new valuesI               for other system parameters, you must reboot your system in_3               order for the changes to take effect.o  I         Table_1-4_Minimum_System_Parameter_Values_Required_______________O           SystemI         Parameter_____VAX_________________Alpha__________________________   -         CTLPAGES      100                 100n  I         _________________________________________________________________o  3         GBLSECTIONS   250 (new)           250 (new)S  6                       50 (upgrade)        50 (upgrade)  I         __________________________________________________________________  8         GBLPAGES      20000 (new)         35000 (new)[1]  ;                       5000 (upgrade)      5000 (upgrade)[1]_  I         _________________________________________________________________   I         [1]The_value_of_GBLPAGES_is_dynamic._____________________________   I                                                  (continued on next page)                               I                               Preparing Your System for Installation 1-19o m  .      *     Preparing Your System for Installation+     1.6 Installation Procedure Requirements     E     Table_1-4_(Cont.)_Minimum_System_Parameter_Values_Required_______   
     SystemE     Parameter_____VAX_________________Alpha__________________________r  <     GBLPAGFIL     For new             For new installations:?                   installations:      1. Add 1 to the number of_  B                   1. Add 1 to the        active users. There is anD                      number of           upper limit of 200 for thisB                      active users.       value, so use 200 if yourC                      There is an         value is greater than 200. /                      upper limit      2. Add 32t                      of 200 for                        this value,"                      so use 200 if"                      your value is!                      greater than                       200.n  "                   2. Multiply your!                      value by 16.                      3. Add 500  E                   ___________________________________________________   E                                              (continued on next page)                                   /     1-20 Preparing Your System for Installatione r  o      I                                    Preparing Your System for Installation I                                   1.6 Installation Procedure Requirements     I         Table_1-4_(Cont.)_Minimum_System_Parameter_Values_Required_______            SystemI         Parameter_____VAX_________________Alpha___________________________  D         GBLPAGFIL     For upgrade         For upgrade installations:G                       installations:      1. Add together the number of   E                       1. Add together        global buffers[2] on the H                          the number          following files in OA$DATA_3                          of global           SHARE:s<                          buffers[2] on       o  ATTENDEE.DAT&                          the following;                          files in            o  MEETING.DATD;                          OA$DATA_SHARE:      o  PENDING.DAT   ;                          o  ATTENDEE.DAT     o  PROFILE.DATu  I                          o  MEETING.DAT   2. Add the total from Step 1 to   I                          o  PENDING.DAT      the number of global buffers C                          o  PROFILE.DAT      in the shared document F                                              attributes files, OA$DAF_G                       2. Add the total       n.DAT in OA$SHARn, where n E                          from Step 1 to      is a letter from A to J. E                          the number       3. Divide the total by 4 to D                          of global           convert to global pages'                          buffers in the 3                          shared document  4. Add 32o#                          attributesa'                          files, OA$DAF_ !                          n.DAT inc(                          OA$SHARn, where&                          n is a letter%                          from A to J.O  %                       3. Multiply thep#                          total by 4y&                          to convert to%                          global pages                           4. Add 500  I         [2]To_find_the_number_of_global,_buffers_do_a_DIR/FULL_for_each__l  
         file.l  I                                                  (continued on next page)   I                               Preparing Your System for Installation 1-21            *     Preparing Your System for Installation+     1.6 Installation Procedure Requirementso    E     Table_1-4_(Cont.)_Minimum_System_Parameter_Values_Required_______   
     SystemE     Parameter_____VAX_________________Alpha__________________________t  E     __________________________________________________________________  E     LOCKIDTBL     100 multiplied      100 multiplied by the number of_+                   by the number of    userso                   active users  E     _________________________________________________________________y  *     MAXBUF (D)    5000                5000  E     _________________________________________________________________   B     MAXPROCESSCNT 50 plus the number  50 plus the number of active+                   of active users     users   E     _________________________________________________________________   D     RESHASHTBL    50 multiplied       50 multiplied by the number of2                   by the number of    active users                   active users  E     _________________________________________________________________w  D     SCSNODE       Must be the same    Must be the same as the DECnet/                   as the DECnet node  node name                    name  E     _________________________________________________________________   C     SCSSYSTEMID   DECnet area number  DECnet area number multiplied C                   multiplied by       by 1024, plus the DECnet node_,                   1024, plus the      number$                   DECnet node number  E     _________________________________________________________________   6     VIRTUALPAGECNT16 384 pages[3]     250 000 pageletsE     [3]This_value_is_approximately_the_same_as_250_000_pagelets._____h  E     _________________________________________________________________v  C              ________________________ Note ________________________   >              For the majority of installations, the values forC              CTLPAGES are sufficient. If you are planning to rebooto?              your system to change other system parameters, youe  /     1-22 Preparing Your System for Installationc t  .      I                                    Preparing Your System for Installation I                                   1.6 Installation Procedure Requirements     E                 can increase the value to 200 for the duration of the.                 installation.h  F                 ______________________________________________________  2         1.6.3 Displaying Current System Parameters  E               Run the SYSGEN utility to display the current parameter                settings:   F               1. To display all the current system parameter settings,                  enter:   (                  $ RUN SYS$SYSTEM:SYSGEN"                  SYSGEN> SHOW /ALL  H               2. To show each system parameter setting separately enter:  '                  SYSGEN> SHOW parameter   F                  where parameter is the parameter you want to examine.  .               3. Press Ctrl/Z to leave SYSGEN.  D               To check the number of free global pages and sections,+               enter the following commands:   :               $ 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 isdD               less than the value in Table 1-4 you must increase theF               system parameter setting. If the values displayed by theE               system are greater than the required values, you do note=               need to change the values for these parameters.o  .         1.6.4 Changing System Parameter Values  I               Edit the file SYS$SYSTEM:MODPARAMS.DAT to change the systemiD               parameter values. The entry that you make in this fileG               depends on which of the parameters you are modifying. Seer               Table 1-5.  A               If you need to change and update non-dynamic system F               parameters, you must schedule time to reboot your systemD               in order for the changes to take effect. The (D) afterD               the system parameter value shows that they are dynamic               parameters.a  I                               Preparing Your System for Installation 1-23N    _      *     Preparing Your System for Installation+     1.6 Installation Procedure Requirements     E           Table_1-5_Changing_System_Parameter_Values__________________             To change            the following E           parameters_______Do_the_following__________________________n  D           SCSNODE          Edit SYS$SYSTEM:MODPARAMS.DAT and specify?           SCSSYSTEMID      new parameter values. Use assignmentn2                            statements of the form:  6                            parameter = parameter-value  =                            where parameter is the name of thet;                            parameter you want to change andoB                            parameter-value is the setting you wantA                            to change it to. See Table 1-4 for then*                            required value.  E           ___________________________________________________________l  D           CTLPAGES         Edit the file SYS$SYSTEM:MODPARAMS.DAT toD           GBLPAGES         specify new values. Include a line of theD           GBLPAGFIL        following format for each parameter to be#           GBLSECTIONS      changed:n  9           LOCKIDTBL        ADD_parameter = increase-valueo  =           MAXBUF (D)       where parameter is the name of the <           MAXPROCESSCNT    parameter you want to change, and@           RESHASHTBL       increase-value is the amount by whichC           VIRTUALPAGECNT   you want to increase the setting of thisi%                            parameter.   @                            For example, to increase the value of2                            LOCKIDTBL by 60, enter:  +                            ADD_LOCKIDTBL=60h  E           _________________See_Table_1-4_for_the_required_values.____e  ?           If you change any of the system parameter values, you A           must update them using AUTOGEN. See Section 1.6.4.1 and            Section 1.6.4.2.    /     1-24 Preparing Your System for Installation     o      I                                    Preparing Your System for InstallationSI                                   1.6 Installation Procedure Requirements     ?         1.6.4.1 Updating Dynamic System Parameters with AUTOGENi  C               To update the dynamic system parameter values, do ther               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 SYSGEN   D               You do not need to reboot your system to make your new!               values take effect.i  I               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 thep               following:  (               1. Run AUTOGEN as follows:  :                  $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS  "               2. Check the values.  <               3. Manually reboot the system when convenient.  F                 ________________________ Note ________________________  @                 You must reboot your system in order for the new&                 values to take effect.  F                 ______________________________________________________  I               For more information, see the OpenVMS manual describing thee               AUTOGEN utility.  I                               Preparing Your System for Installation 1-25e o  .      *     Preparing Your System for Installation+     1.6 Installation Procedure Requirements     D     1.6.5 Disk Space on Your System Disk or Alternate Working Device  D           This section discusses the disk space requirement for your@           kit working device during an Office Server Version 6.1           installation.   E           The default disk for your kit working device is your systemsC           disk. If your system disk does not have sufficient space,tD           you can specify an alternate working device (AWD) when you!           start the installation.   =           The disk space values for your kit are given in theIB           documentation provided with your kit. You must check theB           disk space requirements on the target disks where OfficeB           Server Version 6.1 will be installed. See Section 1.6.7.  E           You can run the installation in either safety or non-safety            mode.h  C              ________________________ Note ________________________o  @              Compaq recommends that you run your installation in'              safety mode (the default).   C              ______________________________________________________   >           When you run the installation in safety mode, all of@           the Office Server Version 6.1 kit is restored onto theA           system disk or AWD before the files are copied to theirpA           target locations. This means that you need a disk spacew?           requirement greater than the total size of the OfficesD           Server Version 6.1 kit on your system disk. The disk spaceD           values for installing your kit in safety mode are given inE           Appendix B, or the documentation that is supplied with your            kit, if not US or GB.   9           If you do not have enough disk space to run the C           installation in safety mode, you can run the installationT?           in non-safety mode. In this case, each kit saveset is @           restored to the system disk before being copied to the?           target area. You need an amount of disk space on your B           system disk greater than the size of the largest savesetA           provided in the Office Server Version 6.1 kit. The disk_E           space values for installing your kit in non-safety mode aremD           given in Appendix B, or the documentation that is supplied)           with your kit, if not US or GB.l  /     1-26 Preparing Your System for Installations d  p      I                                    Preparing Your System for InstallationeI                                   1.6 Installation Procedure Requirementsl    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 besH               reduced by approximately 20%. This is because the majorityE               of the Office Server files reside on the shared librarysE               files disk and therefore the installation procedure can E               move those files to their target directories by using aa=               RENAME operation, rather than a COPY operation.o  @         1.6.7 Disk Space for Office Server Areas on Target Disks  H               You can install Office Server Version 6.1 in the following               ways:n  (               o  On a single target disk  H               o  Across several target disks by installing Office Server)                  areas on separate disks.   C               For upgrade installations, the installation procedure_@               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. If_F               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 required0G               on that disk. See Compaq Office Server Planning and Setup_C               Guide for more information about Office Server areas._  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.a  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 inaD               Appendix B, or the documentation that is supplied with(               your kit, if not US or GB.  I               The disk space requirements for each Office Server area arer-               listed in the following tables:   E               o  Table 1-6 for a new installation. See Section 1.6.9.r  I                               Preparing Your System for Installation 1-27e 0         *     Preparing Your System for Installation+     1.6 Installation Procedure Requirements     7           o  Table 1-7 for an upgrade installation. See               Section 1.6.10.  D           o  Table 1-8 for the addition, upgrade or update of VAX or<              Alpha architecture support. See Section 1.6.11.  D              These values can also be used for the addition, upgrade@              or update of architecture support for an additional              language.  ?           You are prompted to specify the target disks for each 5           Office Server area during the installation.   /     1.6.8 Assigning Logical Names to Your Disksl  A           Compaq recommends that you assign logical names to youru           disks where possible.   C              ________________________ Note ________________________   A              To avoid conflicts with system logical names, do not_2              assign logical names that start with:                o  A1$_                o  OA$_                o  OA1$  C              ______________________________________________________   B           In all types of installation, the installation procedureB           checks for conflicting system and process logical names,C           which could cause the installation to fail. You can check >           for conflicts before you start the installation. SeeA           Section 1.10 which describes how to run the Perform all -           preinstallation checks (PC) option.i  E           The logical name checking includes a check for any existing E           logical names that start with OA$. An informational messageFE           lists the names found, and a warning message warns you thatf/           these logical names may be redefined.D  ?           If a logical name conflict is found, an informational B           message is displayed. If the conflicting logical name isC           defined in a system table, you can remove the conflicting @           logical name from another process, and then repeat theC           check. If the conflicting logical name is specific to the E           installing process, then you must abort the installation to   /     1-28 Preparing Your System for Installationl g         I                                    Preparing Your System for InstallationtI                                   1.6 Installation Procedure Requirements     H               fix the problem and then restart it. The installation willF               not continue until the logical name checking has 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 if G               you are installing on a mixed architecture cluster as the ?               SYS$SYSDEVICE is different for each architecture.   B         1.6.9 New Installation: Disk Space for Office Server Areas  H               Table 1-6 gives the disk space requirements for installingA               Office Server areas on the system and target disks._  E               The disk space requirements given are those used during_A               the installation. The permanent space used when theu>               installation has completed may be slightly less.  F                 ________________________ Note ________________________  A                 If you do not choose to integrate WPS-PLUS duringAD                 the installation, you can decrease the disk space inD                 the shared library area by approximately 6000 blocks1                 (11,000 blocks on Alpha OpenVMS).   D                 If you choose to integrate WPS-PLUS, but without theF                 associated PostScript files, you can decrease the diskF                 space in the shared library area by approximately 30007                 blocks (9,000 blocks on Alpha OpenVMS)._  F                 ______________________________________________________                      I                               Preparing Your System for Installation 1-29o    e      *     Preparing Your System for Installation+     1.6 Installation Procedure Requirements_    B           Table 1-6 New Installation: Disk Space for Office ServerE           __________Areas____________________________________________t  E           Office_Server_Area_for_____VAX_________Alpha_______________E  7           System disk files[1]       21 000      61 000_  8           Shared library files       71 500      112 000  7           Shared data files          12 500      12 500a  5           Shared areas[2]            1000        1000_  5           Office Server Manager      1000        1000            account[3]E           [1]Space_required_to_provide_Office_Server_shared_files_to_e  C           system directories. Add the value given in the Appendix BuB           (or the documentation that is supplied with your kit, if/           not US or GB) to get the total value.2E           [2]Multiply the disk space required by the number of shared ;           areas you wish to create during the installation. @           [3]Includes all utility accounts, for example, IVP and           POSTMASTER. E           ___________________________________________________________   C           For the disk space values for the primary language files,_D           see Appendix B, or the documentation that is supplied with$           your kit, if not US or GB.  C              ________________________ Note ________________________   C              Do not create the Office Server manager's account in a 9              subdirectory of an OpenVMS system directory.:  C              ______________________________________________________e  C     1.6.10 Upgrade Installation: Disk Space for Office Server AreasE  C           Table 1-7 gives the disk space requirements for upgrading =           Office Server areas on the system and target disks.S  A           The disk space requirements given are those used durings=           the installation. The permanent space used when the :           installation has completed may be slightly less.  A           The values given in the table assume that you choose to @           purge files during the installation. If you choose notC           to purge replaced files, you must use the values given in            Table 1-6.  /     1-30 Preparing Your System for Installation     y      I                                    Preparing Your System for InstallationnI                                   1.6 Installation Procedure Requirementse    F                 ________________________ Note ________________________  E                 If you do not choose to integrate WPS-PLUS during thetD                 installation, you can decrease the disk space in the3                 shared library area by 5000 blocks.   ?                 If you choose to integrate WPS-PLUS without the A                 associated PostScript files, you can decrease the E                 disk space in the shared library area by 2000 blocks.   F                 ______________________________________________________  D               Table 1-7 Upgrade Installations: Disk Space for OfficeI               __________Server_Areas_____________________________________n  I               Office_Server_Area_for_____VAX_________Alpha_______________i  ;               System files[1]            10 500      61 000a  <               Shared library files       14 500      112 000  9               Shared data files          2000        2000 I               [1]Space_required_to_provide_Office_Server_shared_files_to_   G               system directories. Add the value given in Appendix B (ortI               the documentation that is supplied with your kit, if not US +               or GB) to get the total value I               ___________________________________________________________n  G               For the disk space values for the primary language files, H               see Appendix B, 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-8 gives the disk space requirements for adding,vI               upgrading or updating of architecture support on the systemo-               and Office Server target disks.   H               These values also apply to the addition, upgrade or updateA               or architecture support for an additional language.       I                               Preparing Your System for Installation 1-31     c      *     Preparing Your System for Installation+     1.6 Installation Procedure Requirements     ?           Table 1-8 Addition, Upgrade or Update of Architecture E           __________Support:_Disk_Space_for_Office_Server_Areas______   E           Office_Server_Area_for_____VAX___________Alpha_____________h  9           System files[1]            21 000        61 000_  9           Shared library files       48 500        95 000aE           [1]Space_required_to_provide_Office_Server_files_to_system_o  @           directories. Add the value given in Appendix B (or theD           documentation that is supplied with your kit, if not US or$           GB) to get the total valueE           ___________________________________________________________e  C           For the disk space values for the primary language files,wD           see Appendix B, or the documentation that is supplied with$           your kit, if not US or GB.        1.6.12 Disk Quota Allocation  C           If disk quota is enabled, the installation procedure addsSD           sufficient disk quota for accounts and identifiers created"           during the installation.       1.6.13 Installed ImagesC  >           Make sure that the shareable image and message filesB           listed in Table 1-9 are installed on your VAX system andB           Table 1-10 are installed on your Alpha system before you@           install Office Server. Note that this list of requiredB           images applies to the versions of the products listed in           Table 1-2.  E           Table_1-9_Installed_Images_Required_on_VAX_________________p  E           Product_______Image_Required_on_VAX________________________n  -           Always        SYS$SHARE:CONVSHR.EXEP           required  1                         SYS$SHARE:CMA$TIS_SHR.EXE   .                         SYS$SHARE:DECC$SHR.EXE  ,                         SYS$SHARE:FDLSHR.EXE  .                         SYS$MESSAGE:FDVMSG.EXE  E                                              (continued on next page)a  /     1-32 Preparing Your System for Installation_ _  _      I                                    Preparing Your System for Installation I                                   1.6 Installation Procedure Requirements     I               Table_1-9_(Cont.)_Installed_Images_Required_on_VAX_________   I               Product_______Image_Required_on_VAX________________________q  3                             SYS$SHARE:FDVSHR.EXE[1]k  0                             SYS$SHARE:LBRSHR.EXE  0                             SYS$SHARE:LIBRTL.EXE  3                             SYS$SHARE:MTHRTL.EXE[2]i  0                             SYS$SHARE:PASRTL.EXE  0                             SYS$SHARE:PLIRTL.EXE  0                             SYS$SHARE:SCRSHR.EXE  1                             SYS$SHARE:VAXCRTL.EXEt  0                             SYS$SHARE:VMSRTL.EXE  I               ___________________________________________________________n  0               ACMS          SYS$SHARE:ACMSHR.EXE  I               ___________________________________________________________k  4               CDA           SYS$SHARE:CDA$ACCESS.EXE  8                             SYS$SHARE:IMG$SHRLIB_NOX.EXE  9                             SYS$SHARE:DDIF$CC_VIEWSHR.EXE   I               ___________________________________________________________   G               DATATRIEVE    SYS$SHARE:DTRSHR.EXE (the standard). If youfG                             are using another DATATRIEVE image that you_E                             want to link with Office Server, you mustfH                             make sure that image is installed before the)                             installation.r  0                             SYS$SHARE:CDDSHR.EXE  3                             SYS$MESSAGE:DTRMSGS.EXE   0                             SYS$SHARE:CDDEXC.EXE  I               ___________________________________________________________   5               DEC Notes     SYS$SHARE:NOTES$SHARE.EXEr  I               [1]This_is_a_language-specific_image_which_can_have_a______y  8               different name on other language versions.H               [2]For certain processors, the logical is defined to point'               to SYS$SHARE:UVMTHRTL.EXE   I                                                  (continued on next page)r  I                               Preparing Your System for Installation 1-33n    a      *     Preparing Your System for Installation+     1.6 Installation Procedure Requirementst    E           Table_1-9_(Cont.)_Installed_Images_Required_on_VAX_________   E           Product_______Image_Required_on_VAX________________________   E           ___________________________________________________________i  1           Compaq        SYS$SHARE:DXD$DUA_SHR.EXEY           Enterprise           Directory 
           for            eBusinesse  1                         SYS$SHARE:DXD$XDS_SHR.EXE   E           ___________________________________________________________.  2           The MAILbus   SYS$SHARE:MTA$XAPI_SHR.EXE           400 MTAu  E           ___________________________________________________________l  -           Message       SYS$SYSTEM:MRTALK.EXE            Router  E           ___________________________________________________________i  1           TCP/IP        SYS$SHARE:UCX$IPC_SHR.EXE   E           ___________________________________________________________   0           WPS-PLUS [3]  SYS$SHARE:LCI$SCLHSP.EXEE           [3]This_image_is_required_only_on_systems_that_have_the____c             German kit installed.eE           ___________________________________________________________e  E           Table_1-10_Installed_Images_Required_on_Alpha______________f  E           Product__________Image_Required_on_Alpha___________________S  0           Always required  SYS$SHARE:CONVSHR.EXE  4                            SYS$SHARE:CMA$TIS_SHR.EXE  1                            SYS$SHARE:DECC$SHR.EXEg  1                            SYS$SHARE:DPML$SHR.EXEs  /                            SYS$SHARE:FDLSHR.EXEe  1                            SYS$MESSAGE:FDVMSG.EXEt  E                                              (continued on next page)f  /     1-34 Preparing Your System for Installation     t      I                                    Preparing Your System for InstallationaI                                   1.6 Installation Procedure Requirementsc    I               Table_1-10_(Cont.)_Installed_Images_Required_on_Alpha______f  I               Product__________Image_Required_on_Alpha___________________s  6                                SYS$SHARE:FDVSHR.EXE[1]  3                                SYS$SHARE:LBRSHR.EXE   :                                SYS$SHARE:LCI$SCLHSP_TV.EXE  3                                SYS$SHARE:LIBOTS.EXEs  3                                SYS$SHARE:LIBRTL.EXEi  9                                SYS$SHARE:LIBRTL_TV.EXE[2]r  9                                SYS$SHARE:MTHRTL_TV.EXE[2]   4                                SYS$SHARE:PAS$RTL.EXE  3                                SYS$SHARE:SCRSHR.EXE   6                                SYS$SHARE:SECURESHR.EXE  7                                SYS$SHARE:SECURESHRP.EXEv  3                                SYS$SHARE:SMGSHR.EXEt  6                                SYS$SHARE:TIE$SHARE.EXE  :                                SYS$SHARE:VAXCRTL_TV.EXE[2]  =                                SYS$SHARE:VMS$IEEE_HANDLER.EXEs  I               ___________________________________________________________   3               ACMS             SYS$SHARE:ACMSHR.EXEo  I               ___________________________________________________________n  7               CDA              SYS$SHARE:CDA$ACCESS.EXE   <                                SYS$SHARE:DDIF$CC_VIEWSHR.EXE  ;                                SYS$SHARE:IMG$SHRLIB_NOX.EXEa  I               ___________________________________________________________1  I               [1]This_is_a_language-specific_image_which_can_have_a______e  8               different name on other language versions.@               [2]This is a logical which typically translates toE               something like the following example: LIBRTL_D56_TV.EXEh  I                                                  (continued on next page)   I                               Preparing Your System for Installation 1-35  r  o      *     Preparing Your System for Installation+     1.6 Installation Procedure Requirements     E           Table_1-10_(Cont.)_Installed_Images_Required_on_Alpha______   E           Product__________Image_Required_on_Alpha___________________   B           DATATRIEVE       SYS$SHARE:DTRSHR.EXE (the standard). IfA                            you are using another DATATRIEVE imageaD                            that you want to link with Office Server,E                            you must make sure that image is installeda3                            before the installation.   /                            SYS$SHARE:CDDSHR.EXEe  1                            SYS$MESSAGE:DTRMSGS.EX   /                            SYS$SHARE:CDDEXC.EXE   E           ___________________________________________________________   4           DEC Notes        SYS$SHARE:NOTES$SHARE.EXE  E           ___________________________________________________________s  4           Compaq           SYS$SHARE:DXD$DUA_SHR.EXE           Enterprise           Directory for            eBusinessa  4                            SYS$SHARE:DXD$XDS_SHR.EXE  E           ___________________________________________________________o  5           MAILbus 400 MTA  SYS$SHARE:MTA$XAPI_SHR.EXEa  E           ___________________________________________________________p  4           TCP/IP           SYS$SHARE:UCX$IPC_SHR.EXE  E           ___________________________________________________________a  3           WPS-PLUS [3]     SYS$SHARE:LCI$SCLHSP.EXE E           [3]This_image_is_required_only_on_systems_that_have_the____              German kit installed.qE           ___________________________________________________________i  C           To check which images are installed on your system, enterc!           the following commands:o             $ INSTALL !           INSTALL> LIST imagename *           imagename;       Open Shar Lnkbl  B           imagename is the directory and file specification of the           image to be checked.  /     1-36 Preparing Your System for Installation            I                                    Preparing Your System for Installation I                                   1.6 Installation Procedure RequirementsV    F               If there is no entry for the image or the qualifiers areD               incorrect, you must install the image with the correct               qualifiers.o                 To install:f  E               o  SYS$MESSAGE:FDVMSG.EXE and SYS$SHARE:FDVSHR.EXE, seei                   Section 1.6.14.  2               o  Other images, see Section 1.6.15.  C               For more information about installing images, see thed4               manual describing the Install Utility.  :         1.6.14 Installing FDVMSG.EXE and FDVSHR.EXE Images  6               If the images SYS$MESSAGE:FDVMSG.EXE andE               SYS$SHARE:FDVSHR.EXE are already present on the system, F               but have not been installed with the Install utility, 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:INSTALLi  H               2. Execute the command procedure SYS$STARTUP:FMSTARTUP.COM  &         1.6.15 Installing Other Images  .               Install other images as follows:                 $ INSTALL A               INSTALL> CREATE imagename /OPEN /SHARED /HEADER_RES                INSTALL> EXITo  5         1.6.16 Checking The Location of DCLTABLES.EXEe  :               Check that DCLTABLES.EXE is in the directoryE               SYS$COMMON:[SYSLIB]. If it is in a different directory,_H               move it to this 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.EXE0  >               If it is not in the correct location, remove it:  +               INSTALL> REMOVE DCLTABLES.EXE1  I                               Preparing Your System for Installation 1-37e f  _      *     Preparing Your System for Installation+     1.6 Installation Procedure Requirementsu    E           Move DCLTABLES.EXE to the correct location and then replace 
           it:B  ?           INSTALL> CREATE DCLTABLES.EXE /OPEN/SHARED/HEADER_RESq  2     1.7 Additional Tasks for Upgrade Installations  C           If you are upgrading an existing Office Server system, dot           the following:  *           1. Review your object libraries.  ?              Your object libraries may have been updated if you C              installed layered products. Office Server provides two >              template .OLB files in the following directories:                                                            /     1-38 Preparing Your System for Installation            I                                    Preparing Your System for InstallationeI                            1.7 Additional Tasks for Upgrade Installations_    6                  -  OA$SITE_BUILD_SHARE:SITEOALIBR.OLB  3                  -  OA$SITE_BUILD_LLV:SITEOALLV.OLB   I                  During the installation, a warning is displayed if thereiH                  are additional .OBJ or .OLB files in these directories.G                  Check that any additional object libraries or files in I                  this directory are compatible with Office Server VersionyG                  6.1. Remove any object libraries or files that are not I                  compatible. Although these files are not used during theeF                  installation, they will cause problems if you need to=                  relink Office Server after the installation.I  F               2. Check that all files in your site areas have at leastH                  system write access (S:W) and that Compaq Office ServerF                  directories in non-site areas also have system delete                  access (S:D).  I               3. Make copies of customized data files. See Section 1.7.1.   +         1.7.1 Copying Customized Data Filest  I               Office Server Version 6.1 uses modified versions of several                data files:s  E               o  Files that have not been converted but their recordsp:                  have changed or new ones have been added:                    o  CM$SDC.DAT  $                  o  CM$CART$RUNS.DAT  #                  o  POP3$MASTER.DAT_  F               Before upgrading, make copies of any data files that youH               have customized as new versions of data files are providedB               with Office Server Version 6.1. You must also returnE               the data files to the Compaq standard format before you                upgrade.  I         1.8 Using the MAILbus 400 MTA and Compaq Enterprise Directory fore             eBusiness2  I               You can install a new Office Server Version 6.1 system withoE               the MAILbus 400 MTA and Compaq Enterprise Directory for                eBusiness.  I                               Preparing Your System for Installation 1-39)           *     Preparing Your System for InstallationO     1.8 Using the MAILbus 400 MTA and Compaq Enterprise Directory for eBusinessl    @           For a new Office Server Version 6.1 installation, withC           Compaq Enterprise Directory for eBusiness and the MAILbusnD           400 MTA you must make sure that you have installed all theB           required MAILbus 400 MTA and Compaq Enterprise Directory@           for eBusiness components on your Office Server system,C           configured them and completed any additional setup tasks. =           See the checklist in the MAILbus 400 MTA and Compaq @           Enterprise Directory for eBusiness Planning chapter in<           the Compaq Office Server Planning and Setup Guide.  %     1.9 Using a Remote Message Routero  E           If you will be using a remote Message Router that is not in 9           the same VMScluster, you must do the following:t  @           1. On the remote Message Router node, create an OfficeB              Server mailbox for the node (or cluster) on which you=              are installing Office Server. See Section 1.9.1.A  B           2. Create an entry for the remote Message Router node inE              the network nodes database on the local machine on whicha.              you are installing Office Server.  E           3. Ensure that Message Router is running on the remote node E              before you start the installation. If it is not running,k@              you will see errors when the installation procedure8              starts up the Sender and Fetcher processes.  ?     1.9.1 Create an Office Server Mailbox on the Remote Messagef           Router Nodep  E           Do this if you are planning to use a remote Message Router. E           If you do not create a mailbox before the installation, yousE           will see problems when the installation procedure starts upe+           the Sender and Fetcher processes.e  B           Message Router must be running and configured before you!           start the installation.s  E           If you are using a remote Message Router which is on a nodelC           in the same VMScluster as Office Server the Office Serverr"           mailbox name will be A1.  E           If the remote Message Router is not in the same VMScluster,aE           other Office Server systems may be sharing the same Message @           Router. The name of the Message Router mailbox must be@           unique for your system. For example, the mailbox name,B           mailboxname, could be localnodeA1 where localnode is the  /     1-40 Preparing Your System for InstallationR M  I      I                                    Preparing Your System for Installation I                                         1.9 Using a Remote Message RouterE    I               name of the node or the cluster on which you are installing F               Office Server. password is the password that you want toF               use for the Message Router mailbox. You are prompted for4               this password during the installation.  H               On the Message Router node, do the following to create the$               Office Server mailbox:  $               $ RUN SYS$SYSTEM:MRMANY               MRM> ADD mailboxname /PASSWORD=password /COMPLETE_MESSAGES /IGNORE_SENDER _ ?                    /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS                MRM> EXIT   B               Note that you must not use the /OWNER qualifier when%               setting up the mailbox.   5         1.10 Running the Preinstallation System Check   B               The Office Server Version 6.1 installation procedure@               provides a Perform all preinstallation checks (PC)G               option. Compaq recommends that you use this option before_E               installing Office Server Version 6.1 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 ServerLG               system is running so you do not have to ask your users to $               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 answerI                  questions and the installation procedure performs systema                  checksr  E               o  Fix errors encountered by the installation procedurel  9               o  Exit without performing the installation   I               Where possible the installation checks are done in an order F               which finds fatal errors first. Section 1.10.1 describesC               the types of errors that are detected. Section 1.10.2_I               describes how to use the Perform all preinstallation checks                (PC) option.  I                               Preparing Your System for Installation 1-41e    e      *     Preparing Your System for Installation1     1.10 Running the Preinstallation System Check     #     1.10.1 Types of Errors Reported   5           The following types of errors are detected:n             o  Fatal errors   ?              These are errors which cannot be corrected withouta>              stopping the installation procedure. Fatal errors              include:i  >              -  Errors that require the machine to be rebooted  >              -  Errors that require an upgrade to prerequisiteC                 software, including OpenVMS, Message Router and the_D                 Message Router VMSmail Gateway, or Compaq Enterprise@                 Directory for eBusiness, the MAILbus 400 MTA and'                 Message Router Gateway.              o  Non-fatal errors_  @              These are errors that can be corrected from anotherA              process without stopping the installation procedure.E&              Non-fatal errors include:  7              -  Shareable images that are not installed   2              -  Logical names that are not defined  A              -  System parameters that can be changed dynamically_  <              -  Prerequisite software files that are missing  '              -  Insufficient disk space_  D     1.10.2 Running the Perform all Preinstallation Checks(PC) Option  D           To run the Perform all preinstallation checks (PC) option,A           follow Steps 1 to 6 in Table 2-2 until you are prompted_.           with a list of installation options.             Do the following:s  7           1. Press Return to choose the default option.   C              ________________________ Note ________________________   @              Choosing this option does not install the software.  C              ______________________________________________________C  /     1-42 Preparing Your System for InstallationD $  .      I                                    Preparing Your System for Installation I                             1.10 Running the Preinstallation System Check     4                  The following message is displayed:  Z                    The installation procedure allows you to perform the following actions:  1                    (I)   Perform the installation.;                    (PC)  Perform all preinstallation checksl  ;                  * Which action do you wish to perform [I]:   C               2. Choose the Perform all preinstallation checks (PC) (                  option by entering: PC.  E               3. If a check fails with an error that can be corrected A                  without stopping the installation procedure, you B                  are asked if you want to correct the error before                  continuing.  G                  If you answer yes, the installation checking procedure B                  pauses so that you can fix the error from anotherE                  process. When the error is fixed, you can resume the 6                  procedure, and the check is repeated.  E                  If you choose not to correct the error, you have theCI                  option of halting the procedure or continuing to perform E                  the remaining checks. If you choose to continue, the C                  installation procedure will terminate 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.1-               installation, do the following:_  C               1. Check that all prerequisite software is installed,S(                  configured and running.  7               2. Start the queue manager, if necessary.   B               3. Back up the system disk and any target disks. See                  Section 1.13.          I                               Preparing Your System for Installation 1-43e           *     Preparing Your System for Installation>     1.12 Final System Preparation Tasks: Upgrade Installations    >     1.12 Final System Preparation Tasks: Upgrade Installations  @           For an upgrade installation from Office Server Version@           6.0, carry out the following steps before starting the?           installation. Each step is described in the followingS           sections.n  ?           From the privileged SYSTEM account, do the following:_  9           1. Shut down Office Server. See Section 1.12.1.   C           2. Ensure that Message Router is running and is correctly               configured.  D           3. Deinstall files in the site areas that are installed in(              memory. See Section 1.12.2.  3           4. Start the queue manager, if necessary.S  >           5. Back up the system disk and any target disks. See              Section 1.13.  "     1.12.1 Shut Down Office Server  E           Ask users currently on the system to log out, and then shut            down Office Server.   C              ________________________ Note _________________________  @              Office Server must not be used by any batch jobs or?              users during the installation, or the installation_              will fail._  C              ______________________________________________________A  D           Do not allow anyone to log in again while the installationB           is in progress. You can allow OpenVMS users to remain onA           the system, but it is important to ensure that users dooA           not use DCL HELP while the installation is in progress, C           as this can cause file locking problems when the DCL HELP B           library is updated during the installation. If possible,E           it is safer to ensure that there are no active users on theP           system.S    /     1-44 Preparing Your System for Installationi _  y      I                                    Preparing Your System for Installation_H               1.12 Final System Preparation Tasks: Upgrade Installations    2         1.12.2 Deinstall Files Installed in Memory  H               If you have any files in the site areas that are installedC               in memory, for example, SITE$OA.A1$SECTION, deinstall C               them on all nodes in the cluster before you start the G               installation. Deinstalling files from memory will preventoD               them from being write locked. The installation sets anH               ACL on all files in the site areas so you must ensure thatH               all files in the site area have system write access (S:W).E               Make sure that you deinstall any of your own code-levelh=               executable images that are installed in memory.   1         1.13 Back Up Your System and Target DisksV  G               Compaq recommends that you do a system disk backup before .               installing any software because:  F               o  If a system failure occurs at a critical point duringI                  installation, your Office Server system could be left ins'                  an inconsistent state.   G               o  You can verify that the backup copy contains a working$G                  system image and then replace the system disk with it.a  I               o  There is more contiguous free space, which may be neededn"                  for installation.  F               If you are going to install Office Server Version 6.1 onH               more than one disk, back up the target disks that you will               be using.   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 Systemg                Management Subkit.  I               At the beginning of the installation, VMSINSTAL asks if youB.               have backed up your system disk.              I                               Preparing Your System for Installation 1-45o _                       I                                                                         2kI         _________________________________________________________________   I             Installation Procedure: New, Upgrade and Architecture SupportT    B               This chapter describes the procedures for installingE               the Office Server Version 6.1 base, language and market H               components. The following installation examples are given:  C               o  A new installation of Office Server Version 6.1 onuD                  an Alpha system with the MAILbus 400 MTA and CompaqE                  Enterprise Directory for eBusiness. See Section 2.1.T  E               o  Upgrade installation of Office Server Version 6.0 toeF                  Office Server Version 6.1 with Message Router and theC                  Message Router Directory Service. The installationoD                  is done on the Alpha system in a mixed-architectureC                  VMScluster, where Message Router is installed on ar2                  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.   F                 __________________ Before You Start __________________  E                 Do not start the installation until you have done thea                 following:  B                 1. Planned your installation by reading the Compaq:                    Office Server Planning and Setup Guide.  F                 2. Completed the system preparation tasks in Chapter 1=                    to check that your system is ready for thee                     installation.  F                 ______________________________________________________  G               Questions asked by installation procedure are marked withfG               an asterisk (*) at the beginning of the line. For help on I               answering a particular question, enter a question mark (?).m  I         Installation Procedure: New, Upgrade and Architecture Support 2-1n           A     Installation Procedure: New, Upgrade and Architecture Support       D           During the installation procedure a number of cautions andD           general informational messages are displayed. Read all theC           displayed messages carefully. Table 2-1 gives informationz5           which you may need during the installation.y  E           Table_2-1_Information_About_the_Installation_Procedure_____s  E           Question_________Answer____________________________________   #           How long         On_Alpha @           will the         As an example, installing on an AlphaD           installation     4000-610 system takes about 1 hour and 15C           take?            minutes for a full installation when the   D                            files are installed on an RZ28 disk using@                            an alternate working directory (AWD).  !                            On_VAXn  @                            The installation can take from one to>                            six hours, depending on the type ofC                            processor you are using. The performance =                            specification of the disks has thef;                            greatest effect. For example, anu@                            installation on a VAX 4000-300 systemC                            takes approximately 3.5 hours when filest@                            are installed on an RF71 disk and 1.5B                            hours if files are installed on an RZ26                             disk.  8                            The times for new and upgradeD                            installations are approximately the same.  .           How do I get     Enter ? at any time           help?               What is          A1061           the productr           identifier?B  E                                              (continued on next page)e        E     2-2 Installation Procedure: New, Upgrade and Architecture Supporte I  s      I             Installation Procedure: New, Upgrade and Architecture Supporte      B               Table 2-1 (Cont.) Information About the InstallationI               __________________Procedure________________________________t  I               Question_________Answer____________________________________t  @               What do I        Restart the installation from the8               do if the        beginning. See Chapter 4.               installation               fails before               the automatic1               postinstalla-e               tion phase?   ,               How do I         Press CTRL/Y.E               abort the        The installation procedure deletes all B               installation?    files in the installation temporary  D                                working directory. Note that this mayD                                take a long time. Any files that haveG                                been provided to target locations remain.E                                there. Note: VMSINSTAL does not delete F                                any accounts, identifiers, or directory;                                structures that are created.b  8                                Restart the installation.  -               How do I         See Chapter 4.                restart therI               installation?______________________________________________o  D         2.1 Installation Procedure for New and Upgrade Installations  E               Table 2-2 lists all the installation steps for a new oruI               upgrade installation. The example scripts in the table show.G               extracts from a new installation on an Alpha system usingaE               the MAILbus 400 MTA and Compaq Enterprise Directory for F               eBusiness and an upgrade installation from Office Server.               Version 6.0 with Message Router.              I         Installation Procedure: New, Upgrade and Architecture Support 2-3- P  a      A     Installation Procedure: New, Upgrade and Architecture Support @     2.1 Installation Procedure for New and Upgrade Installations    8     Table 2-2 Installation Procedure for New and UpgradeE     __________Installations__________________________________________a  E     Step__Action_____________________________________________________n  C     1     Create a log file for the installation. Compaq recommendsd?           that you keep a record of the installation in case of B           problems. You can keep a log by using either a hard copyA           terminal or a log file. To keep a record in a log file,Y           enter:  $           $  SET HOST 0/LOG=filename  B           where filename is the name of the log file. The log fileB           is created in the directory where you enter the command.>           If you do not specify a filename, the file is calledB           SETHOST.LOG. The installation log file will be about 200           blocks.n  A           If you are running console management software, you cana?           use this to record the installation. See your consolei;           management documentation for further information.y  E     _________________________________________________________________n  ?     2     Load and mount the CD that contains the software kit.t  E     _________________________________________________________________   A     3     Invoke the VMSINSTAL procedure from the SYSTEM account.   '           Enter the following commands:   "           $ SET DEFAULT SYS$UPDATE#           $ @VMSINSTAL A1061 deviceh  =           To use an alternate working device (AWD), enter the "           following command lines:  "           $ SET DEFAULT SYS$UPDATE4           $ @VMSINSTAL A1061 device OPTIONS AWD=disk  <           device is the device on which you have mounted theA           distribution media. You can use a physical or a logical C           device name but do not use logical device names beginningtE           with A1$, OA$, or OA1$. A1061 is the product identifier and ?           disk is the location of the alternate working device.y  E                                              (continued on next page)   E     2-4 Installation Procedure: New, Upgrade and Architecture Supportt .         I             Installation Procedure: New, Upgrade and Architecture SupporteI              2.1 Installation Procedure for New and Upgrade Installationse    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________e  I         Step__Action_____________________________________________________   I         _________________________________________________________________c  (         4     Verify your system backup.  I                  OpenVMS VAX Software Product Installation Procedure V7.2e  )               It is 19-JAN-2002 at 13:04.n  =               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. I               ___________________________________________________________                For installationI               type__________________Go_to________________________________a  *               New                   Step 5  I               Upgrade_______________Step_8_______________________________   I         _________________________________________________________________m  @         5     New_Installation: Enter the number for the type of/               installation that you want to do.   .               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.1 kit, the following installation typesy                 can be performed:l  <                (1)  A new installation of Office Server V6.1  @                (RL) Register licenses for pre-requisite software  >               * Which installation do you wish to perform [1]:  <               Enter 1 to install a new Office Server system.  I         _________________________________________________________________   I                                                  (continued on next page)   I         Installation Procedure: New, Upgrade and Architecture Support 2-5            A     Installation Procedure: New, Upgrade and Architecture Supportf@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________r  E     Step__Action_____________________________________________________u  >     6     New_Installation: Confirm that you want to start the           installation.C  U               The installation procedure allows you to perform the following actions:   ,               (I)   Perform the installation7               (PC)  Perform all pre-installation checks   4           * Which action do you wish to perform [I]:  1           Press RETURN to start the installation.I  E     _________________________________________________________________p  C     7     New_installation: Specify whether you want a File Cabinete           only system.  T           * Do you wish to install Office Server as a File Cabinet Only system [NO]?  =           You should be aware that if you answer Y any futureCE           installation will take this option automatically. If, afterfA           installing Office Server as a File Cabinet only system,nE           you want to revert to a full Office Server system, you willl5           need to contact your Compaq Support Center.   >           Press RETURN to install a full Office Server system.  %           To_continue: go to Step 11.O  E     _________________________________________________________________   E                                              (continued on next page)                 E     2-6 Installation Procedure: New, Upgrade and Architecture Supportn s  y      I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installationso    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________t  I         Step__Action_____________________________________________________   D         8     Upgrade_Installation: Enter the number for the type of/               installation you want to perform.i  ?               The current product image identification is V6.0.w  U               Using the FULL Office Server V6.1 kit, the following installation typesi                 can be performed:c  H                 (1)  Upgrade of Office Server V6.0 to Office Server V6.1  D                 (2)  Add, upgrade, or update Alpha components for an.                      Office Server V6.1 system  A                 (RL) Register licenses for pre-requisite softwaret  @               * 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-architectureo9               VMScluster, you are not offered option (2).   I         _________________________________________________________________   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.s  I         _________________________________________________________________s  I                                                  (continued on next page)r  I         Installation Procedure: New, Upgrade and Architecture Support 2-7e i  Y      A     Installation Procedure: New, Upgrade and Architecture Support @     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________   E     Step__Action_____________________________________________________e  ?     10    Upgrade_installation: Specify whether you want a Fileo           Cabinet only system.  A           This question is asked only for upgrades to full OfficewE           Server systems. If the system you last installed was a Filei>           Cabinet only system, this question is not displayed.  T           * Do you wish to install Office Server as a File Cabinet Only system [NO]?  =           You should be aware that if you answer Y any futurenE           installation will take this option automatically. If, afteroA           installing Office Server as a File Cabinet only system, E           you want to revert to a full Office Server system, you will 5           need to contact your Compaq Support Center.   >           Press RETURN to install a full Office Server system.  E     _________________________________________________________________   @     11    In some cases, the following licensing question may be           displayed:  U           %A1-I-NOLICENSE, No license PAK was found for this product so it is assumedw  K           %A1-I-NOLICENSE, that you are using Client Access Licensing (CAL)n  F           * Do you have enough CALs licenses to run this system? [YES]  /           * How many CALs licenses do you have:   B           Enter the number of CALs licenses that you have for this           system.   E     _________________________________________________________________   E     12    Upgrade_Installation: Confirm that you want to purge files.   K           * Do you want to purge files replaced by this installation [YES]?   &           Press RETURN to purge files.  E     _________________________________________________________________   E                                              (continued on next page)   E     2-8 Installation Procedure: New, Upgrade and Architecture Support            I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________   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.O  Y                If you use the standard DATATRIEVE image SYS$SHARE:DTRSHR.EXE then you cana  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 are_F               prompted to supply the name of the DATATRIEVE image thatB               you want to link with. If you are using the standardF               DATATRIEVE image, SYS$SHARE:DTRSHR.EXE, you are asked ifD               you want to dynamically activate DATATRIEVE during theC               Office Server startup. It is recommended that you do.m  I         __________________________________________________________________  I                                                  (continued on next page)s                      I         Installation Procedure: New, Upgrade and Architecture Support 2-9     e      A     Installation Procedure: New, Upgrade and Architecture Supporte@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________s  E     Step__Action_____________________________________________________o  ?     14    If you are using a license that allows WPS-PLUS (CALsgD           licenses do not allow WPS-PLUS), indicate whether you wantD           to install WPS-PLUS with Office Server. If you do not haveB           a license which includes WPS-PLUS, you will not be asked           this question.  R               If you wish to have the WPS-PLUS editor available, answer YES to the  U               following question.  If you do not wish to install the WPS-PLUS editor,1                 answer NO.                 NOTE:r  S                   o If WPS-PLUS is not installed then the WPS-PLUS linguistics aidsR  Q                     (SPELL CHECKER and THESAURUS) and the WPS-PLUS SORT and MERGE   C                     processing functionality will not be available.a  V                   o You will be able to do an Office Server update installation to add  V                     WPS-PLUS at a later time, should you choose not to install it now.  D           * Do you want to install WPS-PLUS with Office Server [NO]?  B           Enter YES to install WPS-PLUS. You are then asked if you@           want to install the graphics and page overlay samples:  T               This kit contains a library of Encapsulated PostScript(R) graphics and  T               PostScript(R) Page Overlay samples.  Their total size is approximately  W               3,000 blocks when they are copied to the Office Server library directory.   K           * Do you want these graphics copied to the OA$LIB directory [NO]?   <           Press RETURN if you do not want to copy the files.  $           Enter Y to copy the files.  E     _________________________________________________________________   E                                              (continued on next page)e  F     2-10 Installation Procedure: New, Upgrade and Architecture Support i  P      I             Installation Procedure: New, Upgrade and Architecture SupportCI              2.1 Installation Procedure for New and Upgrade Installationsr    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________g  C         15    Indicate whether to you want to build a multilanguagee               system.o  \                   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.   I               Enter Y if you plan to install additional languages and yous3               want to build a multilanguage system.d  I         _________________________________________________________________M  I                                                  (continued on next page)f                                            I        Installation Procedure: New, Upgrade and Architecture Support 2-11a t  i      A     Installation Procedure: New, Upgrade and Architecture Support @     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________n  E     Step__Action_____________________________________________________x  '     16    Select a default date format.   X               Office Server allows you to select a default date format for each language  X               you have installed. This will become the default Office Server date format  R               for each user (on a per language basis.) This may be changed by each  T               user through the Set Working Conditions option on the User Setup Menu.  3                   Alphanumeric Date    Numeric Datet  G                   1   DD-MMM-YYYY      MM/DD/YY      (Standard Default)o  /                   2   DD-MMM-YYYY      DD/MM/YYw/                   3   DD-MMM-YYYY      YY/MM/DD_/                   4   YYYY-MMM-DD      MM/DD/YYc/                   5   YYYY-MMM-DD      DD/MM/YY_/                   6   YYYY-MMM-DD      YY/MM/DDnA                   7   ***** Reserved (Means system default) ***** E                   8   DD-MM-YYYY       DD/MM/YY      (Numeric format) E                   9   MM-DD-YYYY       MM/DD/YY      (Numeric format)e  1           * Which date format do you require [1]:   D           Press RETURN to use the default format or enter the number3           for the date format that you want to use.i  E     _________________________________________________________________i  E                                              (continued on next page)i                  F     2-12 Installation Procedure: New, Upgrade and Architecture Support o  a      I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installations_    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations___________________________________  I         Step__Action_____________________________________________________N  G         17    Specify the greatest number of simultaneous Office Servero               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.  I         _________________________________________________________________n  G         18    Specify a batch queue for running the job that checks ther0               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 namea)               of an existing batch queue._  9               For_an_upgrade_installation: Go to Step 20._  I         __________________________________________________________________  I                                                  (continued on next page)u          I        Installation Procedure: New, Upgrade and Architecture Support 2-13u V  e      A     Installation Procedure: New, Upgrade and Architecture Supportu@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations___________________________________  E     Step__Action_____________________________________________________   @     19    New_installation: Specify batch queue for starting theC           AIDA, File Cabinet, POP3 and IMAP Servers, and the Sender_            and Fetcher processes.  K           * A running batch queue on this node is needed to start the Aida,_  V             File Cabinet, POP3 and IMAP Servers, and the Sender and Fetcher processes.  K           It is suggested that a separate queue is used for this, which theo  /           installation will create if you wish.n  C           * Do you want OA$SERVER_START_nodename to be created [Y]?U  @           If you answer N, the installation returns this prompt:  6           * Which queue do you want to use? [default]:  D           Press RETURN to accept the default queue or enter the nameE           of an existing batch queue on this node that is not generic (           and that is currently running.  >           The queue that you specify will be added to the NodeA           Specific Batch Queue Master file, and will be stored in D           the configuration files of any Servers created during thisE           installation. You can change the queue later, or add queues @           for other nodes in your cluster, using the Manage nodeA           specific queues (MNQ) option from the System Managementg           menu.s  E     _________________________________________________________________   E                                              (continued on next page)               F     2-14 Installation Procedure: New, Upgrade and Architecture Support t  a      I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________e  I         Step__Action______________________________________________________  E         20    Select whether to let the installation procedure create                SDAF files.h  M               This version of Office Server allows for separate FDLs for each J               mail area SDAF file. By having separately optimized FDLs theN               performance of Office Server is improved. Creation of these FDLsL               may be performed during installation, but may take a long timeM               depending on the size of the SDAF files. Alternatively the FDLs O               can be created at any later convenient time when Office Server is <               shut down. The command for creating an FDL is:  X               $ANALYZE/RMS_FILE/FDL OA$SHARx:OA$DAF_x.DAT/OUTPUT=OA$LIB_SHARE:SDAF_x.FDL  :               where x is a letter in the range 'A' to 'J'.  H               * Do you wish to create FDLs for mail area SDAF files [Y]?  <               Press RETURN to accept the default (Y) answer.  I         _________________________________________________________________   I                                                  (continued on next page)                             I        Installation Procedure: New, Upgrade and Architecture Support 2-15l i  _      A     Installation Procedure: New, Upgrade and Architecture Support_@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________n  E     Step__Action_____________________________________________________i  C     21    Indicate if you want to send and receive remote mail. ThecD           installation procedure checks the type and versions of theC           message transport and directory service software that aret#           installed on your system.   O           Electronic Messaging can be used to send and receive messages, to andw  M           from other computer systems using either the MAILbus 400 or Message              Router products.  I           * Do you want to be able to send and receive remote mail [YES]?v  6           Press RETURN if you want to use remote mail.  E           If you answer NO to this question, Office Server users will_D           only be able to exchange messages locally with other users&           on the same computer system.  E           ___________________________________________________________uE           If_You_______________________________Go_To_________________I  6           Do not want to use remote mail       Step 29  6           Are installing a new Office Server   Step 22'           system with Compaq Enterprise )           Directory for eBusiness and theo           MAILbus 400 MTA   E           Are_upgrading_with_Message_Router____Step_23________________  E     _________________________________________________________________   E                                              (continued on next page)             F     2-16 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture SupportiI              2.1 Installation Procedure for New and Upgrade Installationsn    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations___________________________________  I         Step__Action_____________________________________________________f  B         22    New_Installation with the MAILbus 400 MTA and CompaqG               Enterprise Directory for eBusiness: Confirm that you wantv9               to use the MAILbus 400 MTA 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 thed  P                 installation checks have revealed that the product is installed.  W                 Note that even though MAILbus 400 appears to be installed and initiallyy  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 Planningf                    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 use   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 Office G               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 arenD               covered in the Compaq Office Server Planning and Setup               Guide.  )               To_continue: Go to Step 26.   I         _________________________________________________________________l  I                                                  (continued on next page)   I        Installation Procedure: New, Upgrade and Architecture Support 2-17     1      A     Installation Procedure: New, Upgrade and Architecture Supporta@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations___________________________________  E     Step__Action_____________________________________________________r  D     23    Upgrade_Installation: Confirm that you want to use Message!           Router for remote mail.t  @           Office Server on a VAX node can be configured to use aE           local Message Router which is installed on the same node orOC           a remote Message Router which is installed on a different:D           node. Office Server on an Alpha node can only use a remoteC           Message Router. This example script is on an Alpha systemTB           so it must be configured to use a remote Message Router.  S           * Do you want Office Server to be configured to use Message Router [YES]?   B           Answer Y to confirm that you want to use Message Router.  E     _________________________________________________________________V  B     24    Upgrade_Installation: If Message Router is not installedE           on this node, confirm that you want to use a remote Message            Router.   =           * Do you want to use a remote Message Router [YES]?   B           Enter Y to confirm that you want to use a remote Message           Router.a  @           Note that the default value for this answer depends onA           whether you are doing the upgrade installation on a VAX_A           system or an Alpha system. In this example, the upgrade B           is on an Alpha system, so the default is to use a remote           Message Router.t  E     _________________________________________________________________   E                                              (continued on next page)             F     2-18 Installation Procedure: New, Upgrade and Architecture Support .  n      I             Installation Procedure: New, Upgrade and Architecture Support_I              2.1 Installation Procedure for New and Upgrade Installations_    D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________   H         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 Router                node.l  E               Note that the remote Message Router node must be in therA               network nodes database on the node on which you areLF               installing Office Server. As this is an upgrade you willI               not be asked for a password for the Message Router mailbox.o  "               Additional_Questions  C               If you are installing a new Office Server system withtF               Message Router, you are prompted to enter a password for)               the Message Router mailbox.   @               * Enter a password for the Message Router mailbox:?               * Please confirm the password that you specified:   B               The password must be a minimum of 8 characters and a=               maximum of 32 characters. Confirm the password.   I         _________________________________________________________________l  I                                                  (continued on next page)t                        I        Installation Procedure: New, Upgrade and Architecture Support 2-19  e  r      A     Installation Procedure: New, Upgrade and Architecture Support @     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________t  E     Step__Action_____________________________________________________   D     26    Indicate the type of Mail Directory support that you want.  E           For new installations where Compaq Enterprise Directory for B           eBusiness or an LDAP directory service is installed, the!           following is displayed:t  @           * What type of Mail Directory support do you want [X]:  >           The options that are available depend on the type of>           directory service software that is installed on yourD           system. You are given the appropriate options and defaultsB           from the following list, depending on what is installed.  C           Press RETURN to accept the default or enter the value forN;           the type of Mail directory support that you want.tE           ___________________________________________________________ E           For__________________________________Option_to_Enter_______   0           No Mail directory support            0  0           The Message Router Directory         M'           Service as the Mail directory   0           The Compaq Enterprise Directory for  X,           eBusiness Directory Service as the           Mail directory  0           An LDAP Directory Service as the     LE           Mail_directory_____________________________________________u  B           When you are installing with Compaq Enterprise DirectoryE           for eBusiness, it does not matter whether Compaq EnterpriseeB           Directory for eBusiness is installed on the same node as@           Office Server or on a remote node outside the cluster,>           providing that you have done all the necessary setupA           and configuration tasks as outlined in the Overview andf           Planning Guide.   E           If_you_have_specified_no_Mail_directory_support, go to Step 
           29.   E     _________________________________________________________________a  E                                              (continued on next page)   F     2-20 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture Support I              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________   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 secondarye               directory.  2               For new installations go to Step 29.  I         _________________________________________________________________   H         28    Installation_with_Message_Router: Enter a password for the?               Mail Directory User Agent account and confirm it.p  I               The text that is displayed depends on whether you are usingiF               a remote Message Router, and whether that Message RouterH               is in the same VMScluster. Read the informational messages4               carefully and follow the instructions.  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 Maill:               Directory user agent account and confirm it.  I         _________________________________________________________________   I                                                  (continued on next page)n              I        Installation Procedure: New, Upgrade and Architecture Support 2-21s t         A     Installation Procedure: New, Upgrade and Architecture Supports@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________   E     Step__Action_____________________________________________________   E     29    Indicate if you want outgoing messages translated to ASCII.   I           * Do you want to translate all outgoing messages to ASCII [NO]?   ;           Press RETURN if you do not want outgoing messages_           translated.n  C                    _____________________ Note ______________________  <                    If you are using a remote MAILbus 400 MTA;                    on Tru64 UNIX, you must answer Y to this ?                    question if WPS-PLUS to ASCII converters areu@                    not installed on the MAILbus 400 MTA node and@                    you want to exchange messages with non-Office                     Server users.  C                    ________________________________________________   D           Enter Y, if you want outgoing messages translated. You areB           then asked if you want all attachments to be translated.  B           * Do you want to translate all message attachments [NO]?  B           Press RETURN if you do not want to translate all messageC           attachments. If you enter Y to this question, all messageu@           attachments are translated to ASCII if the appropriate@           converters are installed on your Office Server system.  E     _________________________________________________________________h       30    System checking.  B           The installation procedure checks mandatory and optional=           software prerequisites. You may be asked additionaltC           questions depending on the software and licenses that areu#           installed on your system.   =           If the prerequisite software for CDA support is not >           installed, you are asked if you want to continue the+           installation without CDA support.   E     _________________________________________________________________   E                                              (continued on next page)o  F     2-22 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture SupportsI              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________d  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/IPnH               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 clientwA               connections. If you do, you are asked the followingFD               questions if default service names for the AIDA ServerI               and Office Server File Cabinet Server are not registered inl-               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]:   G               Enter a different TCP/IP port number for each server. TheeF               port numbers can be in the range 1024 to 65535. You mustI               use the default values if you are planning to use TeamLinksE               client software.  C               The installation procedure checks that the TCPIP$IPC_ H               SHR.EXE image is installed. If it is not, you must install(               it after the installation.  I         __________________________________________________________________           32    System checking.  I               The installation procedure checks system parameters, quotas G               and identifiers. For new installations, the Office Server:H               identifiers are created. The identifiers already exist for$               upgrade installations.  I         _________________________________________________________________o  I                                                  (continued on next page)   I        Installation Procedure: New, Upgrade and Architecture Support 2-23p c  n      A     Installation Procedure: New, Upgrade and Architecture Supporta@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________t  E     Step__Action_____________________________________________________e  "     33    Enter the language code.  H           * Enter language code for this installation (2 characters): US  >           Enter the two-letter language code for your language@           component. In this example, US is the ENGLISH language           code. See Appendix C..  E     __________________________________________________________________  E     34    If your language kit contains a dialect component, you will -           be asked to enter the dialect code.   @           Your language kit may also contain one or more dialectE           components. Enter the dialect code that you want to use. If E           your language kit does not contain a dialect component, youn&           are not asked this question.  >           %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets@           %VMSINSTAL-I-RESTORE, Restoring product save set B ...  O               If you wish to install a dialectal variation of ENGLISH language,_  R               enter the code for the dialect component you wish to use.  If you do  L               not wish to install a dialectal variation of ENGLISH language,  3               then accept the answer of NO_DIALECT.   Q           * Enter dialect code for this installation (5 characters) [NO_DIALECT]:2  A           Press RETURN or enter the dialect code that you want to            use. See Appendix C.  D           The installation procedure continues with system checking.E           ____________________________________________________________           For installationE           type__________________Go_to________________________________T  '           New                   Step 35c  E           Upgrade_______________Step_36______________________________b  E                                              (continued on next page)s  F     2-24 Installation Procedure: New, Upgrade and Architecture Support i  n      I             Installation Procedure: New, Upgrade and Architecture SupportkI              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________a  I         Step__Action_____________________________________________________   I         _________________________________________________________________u  I         35    New_Installation: Specify the devices for the Office Server H               areas. The initial default is the non-system disk with the               most space.g  N               * Which device will hold the Office Server shared library files:  \               * Which device will hold the Office Server shared data files       [A1DISK1:]:  \               * Which device will hold the Office Server ENGLISH language files  [A1DISK1:]:  \               * Which device will hold the Office Server mail area SDAF file     [A1DISK1:]:  F               * How many shared directories do you want to create [1]:\               * Which device will hold the Office Server shared directory SHARE1 [A1DISK1:]:  \               * Which device will hold the Office Server lexicon files           [A1DISK1:]:  G               For shared directories, Compaq recommends that you select_D               the default value at installation time and then createC               additional shared directories after the installation, E               following the instructions in the DIGITAL Office Server :               Managing from a VT Terminal (the V4.0 book).  E               If lexicon files have already been installed by anothersC               product, you are not asked the question about lexicona               files.  I         _________________________________________________________________i  I                                                  (continued on next page)_                I        Installation Procedure: New, Upgrade and Architecture Support 2-25            A     Installation Procedure: New, Upgrade and Architecture Supporte@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________s  E     Step__Action_____________________________________________________u  D     36    Enter the market code. (This is defaulted for an upgrade.)  F           * Enter market code for this installation (2 characters): US  D           Enter the two-letter market code for the installation. See           Appendix C._E           ___________________________________________________________nE           Installation_type_____Go_to________________________________h  '           New                   Step 37   E           Upgrade_______________Step_44______________________________E  E     _________________________________________________________________e  C     37    New_Installation: Specify an OpenVMS account and passworda>           for the Office Server manager. Confirm the password.  <           %A1CUS-I-RECOUK, Restoring the MARKET kit savesets@           %VMSINSTAL-I-RESTORE, Restoring product save set B ...@           %VMSINSTAL-I-RESTORE, Restoring product save set C ...  J                 Creating an OpenVMS account for the Office Server manager.  V           * What OpenVMS username do you want to use for Office Server Manager account             [OFFICE]:rC           * Enter a password for the Office Server Manager account:P  <           * Please confirm the password which you specified:  E     _________________________________________________________________   E                                              (continued on next page)_            F     2-26 Installation Procedure: New, Upgrade and Architecture Support _  _      I             Installation Procedure: New, Upgrade and Architecture SupportaI              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________   I         Step__Action_____________________________________________________   D         38    New_Installation: Enter a system group UIC and defaultA               device and directory for the Office Server manager. D               Do not create the Office Server manager's account in a:               subdirectory of an OpenVMS system directory.  N               * 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 account                   [A1DISK1:]^               * What default directory do you want to use for Office Server Manager's account?                   [OFFICE:]e  I         _________________________________________________________________f  H         39    New_Installation: Enter a UIC for the accounts used by theG               Transfer User utility. The UIC must not be a system group(               UIC.  C               * What UIC do you want to use for A1$XFER_IN account:dH               * What UIC do you want to use for the A1$XFER_OUT account:  I         _________________________________________________________________N  G         40    New_Installation: Enter a UIC for the account used by theuI               Script Symbiont utility. The UIC must not be a system group_               UIC.  H               * What UIC do you want to use for SCRIPT SYMBIONT account:  I         _________________________________________________________________   I                                                  (continued on next page)B            I        Installation Procedure: New, Upgrade and Architecture Support 2-27d           A     Installation Procedure: New, Upgrade and Architecture Support @     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________e  E     Step__Action_____________________________________________________N  C     41    New_Installation: Enter a UIC for the account used by theaD           File Cabinet Server for authenticating remote clients intoB           a non-privileged account, and a UIC for the account used@           for running the Office Server File Cabinet Server as aE           detached process. . The UICs must not be system group UICs.   A           * What UIC do you want to use for OAFC$DEFAULT account:o@           * What UIC do you want to use for OAFC$SERVER account:  E     _________________________________________________________________v  D     42    New_Installation: If you are prompted, enter a UIC for theA           WEB$ACCESS account. You are prompted only if WEB$ACCESSn!           does not already exist.B  D           WEB$ACCESS is created automatically in a new installation.C           The account is used to control access to the File CabinetSC           drawers by the Compaq Office Server Web Interface and thehC           IMAP and POP3 Servers. The WEB$ACCESS account is not used @           for interactive logins, so you will not be asked for a           password.h  ?           * What UIC do you want to use for WEB$ACCESS account:   E     _________________________________________________________________a  E                                              (continued on next page)                           F     2-28 Installation Procedure: New, Upgrade and Architecture Support    t      I             Installation Procedure: New, Upgrade and Architecture SupportaI              2.1 Installation Procedure for New and Upgrade Installations     D         Table 2-2 (Cont.) Installation Procedure for New and UpgradeI         __________________Installations__________________________________n  I         Step__Action_____________________________________________________f  I         43    New_Installation: Specify the top-level directories for the "               Office Server areas.  O               * Enter top-level directory required for the shared library files                    [OFFICE]:oL               * Enter top-level directory required for the shared data files                   [OFFICE]:_Q               * Enter top-level directory required for all ENGLISH language filesi                   [OFFICE]: N               * Enter top-level directory required for the mail area SDAF file                   [OFFICE]:tV               * Enter the name required for the SHARED DIRECTORY on A1DISK1: [OFFICE]:  (               Go to Step 46 to continue.  I         _________________________________________________________________   F         44    Upgrade_Installation: Enter the OpenVMS username for the.               Office Server manager's account.  S               * What is the existing OpenVMS username for the Office Server accountf                   [ALLIN1]:r  G               Enter the OpenVMS username for the Office Server account. 0               The account details are displayed.  I         _________________________________________________________________t  C         45    Upgrade_Installation: Confirm that the details of the_:               Office Server manager's account are correct.  N               * Are all the specified account's characteristics correct [YES]?  =               Press RETURN if all the information is correct.   I         _________________________________________________________________t  I                                                  (continued on next page).  I        Installation Procedure: New, Upgrade and Architecture Support 2-29i _  _      A     Installation Procedure: New, Upgrade and Architecture Support_@     2.1 Installation Procedure for New and Upgrade Installations    @     Table 2-2 (Cont.) Installation Procedure for New and UpgradeE     __________________Installations__________________________________N  E     Step__Action_____________________________________________________   =     46    If you choose to, you can run the IVP (Installation "           Verification Procedure).  C           * Do you want to run the IVP after the installation [NO]?e  -           Enter Y if you want to run the IVP.P  A           All the installation questions have now been completed.   E           If you are installing Office Server Version 6.1 on a mixed-sC           architecture VMScluster, see Section 2.2 for instructions C           on adding architecture support for a second architecture.e  <           If you are not installing on a single-architectureE     ______VMScluster,_go_to_Section_2.3._____________________________   0     2.2 Adding or Upgrading Architecture Support  C           Table 2-3 explains when you can do an installation to adda*           or upgrade architecture support.  E           Table 2-3 When to Install/Upgrade VAX or Alpha ArchitectureIE           __________Support__________________________________________   E           Install/Upgrade_______When_you_have_already_done____________  >           VAX architecture      A new or upgrade Office ServerD           support               Version 6.1 installation on an Alpha=                                 system in the same VMScluster   >           Alpha architecture    A new or upgrade Office ServerA           support               Version 6.1 installation on a VAXCE           ______________________system_in_the_same_VMScluster._______o  @           The questions that you are asked during the additionalD           architecture installation depend on the responses that youC           gave during the new or upgrade installation. For example, C           if you did not install WPS-PLUS during the new or upgradetB           installation, you are not asked any additional questions           about WPS-PLUS.   F     2-30 Installation Procedure: New, Upgrade and Architecture Support           I             Installation Procedure: New, Upgrade and Architecture Support_I                              2.2 Adding or Upgrading Architecture Supportc             2.2.1 Before You Start  @               Before you start the installation, you must do the               following:  I               1. If you are installing architecture support for the first G                  time, make a note of the location of the Office ServereG                  configuration file, OA$DATA_SHARE:A1CONFIG.DAT, on thehE                  system where you have already installed a new OfficewC                  Server Version 6.1 system or upgraded to an Office F                  Server Version 6.1 system. You will be asked for this5                  information during the installation.s  E               2. From the Office Server manager's account on the nodebB                  where Office Server is already installed, run the;                  script, OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP:   *                  $ SET HOST 0/LOG=filename&                  $ OFFICESERVER/NOINIT@                  Enter CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCP  I                  If references to SYS$DEVICE are found, a warning messagenE                  is displayed. You must remove the references as they G                  will refer to different devices on a VAX system and an H                  Alpha system. If the references are not corrected, data,                  may be lost on your system.  B                  The installation procedure also runs this script.  D         2.2.2 Installation Procedure for Adding Architecture Support  B               Table 2-4 shows an example script for an additional-F               architecture installation on a VAX system. The following"               information is used:  E               o  Office Server Version 6.1 is already installed on anr5                  Alpha system in the same VMScluster._  ;               o  WPS-PLUS is installed on the Alpha system.   E               o  Office Server has been configured as a multilanguage ,                  system on the Alpha system.  @               o  Message Router is installed on this VAX system.  I               The example includes the script for both adding VAX supporteD               for the first time and upgrading existing VAX support.G               The installation questions and script are similar for the_3               addition or upgrade of Alpha support._  I        Installation Procedure: New, Upgrade and Architecture Support 2-31a a  c      A     Installation Procedure: New, Upgrade and Architecture Supportr0     2.2 Adding or Upgrading Architecture Support        E     Table_2-4_Installation_Procedure_for_Adding_Architecture_Support_   E     Step__Action______________________________________________________  +     1 to  Follow Steps 1 to 5 in Table 2-2. E     5     ___________________________________________________________ E           For_Installation_Type________________Go_to_________________   5           Upgrade                              Step 6n  E           New__________________________________Step_7________________n  E     _________________________________________________________________s  @     6     Upgrade_Installation: Enter the number for the type of+           installation you want to perform.O  ;           The current product image identification is V6.0.s  Q           Using the FULL Office Server V6.1 kit, the following installation typeso             can be performed:u  A             (1)  Upgrade Office Server V6.0 to Office Server V6.1c  >             (2)  Add, upgrade, or update VAX components for an*                  Office Server V6.1 system  =             (RL) Register licenses for pre-requisite software2  :           * Which installation do you wish to perform [1]:  @           Press RETURN to upgrade VAX components for an existingD           Office Server Version 6.1 system that is already installed4           on an Alpha system in the same VMScluster.  $           To_Continue: Go to Step 8.  E     _________________________________________________________________   E                                              (continued on next page)_    F     2-32 Installation Procedure: New, Upgrade and Architecture Support e  n      I             Installation Procedure: New, Upgrade and Architecture SupportpI                              2.2 Adding or Upgrading Architecture Supportc    H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support________________________________________N  I         Step__Action______________________________________________________  @         7     New_Installation: Enter the number for the type of/               installation you want to perform._  .               Logical OA$IMAGE is not defined.L               No product image can be found using the default specification.  U               Using the FULL Office Server V6.1 kit, the following installation types                  can be performed:c  <                (1)  A new installation of Office Server V6.1  A                (2)  Add, upgrade, or update VAX components for anl.                      Office Server V6.1 system  @                (RL) Register licenses for pre-requisite software  @               * Which installation do you wish to perform [1]: 2  6               Enter 2 to add VAX architecture support.  I         _________________________________________________________________l  >         8     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 checksa  9               *  Which action do you wish to perform [I]:   5               Press RETURN to start the installation.w  2               Upgrade_Installation: Go to Step 10.  I         _________________________________________________________________l  I                                                  (continued on next page)y  I        Installation Procedure: New, Upgrade and Architecture Support 2-33  _  _      A     Installation Procedure: New, Upgrade and Architecture Support 0     2.2 Adding or Upgrading Architecture Support    D     Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureE     __________________Support________________________________________e  E     Step__Action_____________________________________________________f  ;     9     New_Installation: Supply the location of OA$DATA_tC           SHARE:A1CONFIG.DAT, the Office Server configuration file,a?           for Office Server Version 6.1 on the existing system._  Q               You have chosen an architecture only installation.  To continue you(  N               must specify the location of the existing system's configuration  N               file (A1CONFIG.DAT).  The installation will read A1CONFIG.DAT to  .               determine file target locations.  P           * Please give the directory location of A1CONFIG.DAT: disk:[directory]  D           Enter the location of the Office Server configuration fileC           in the format, disk:[directory]. You must always use this_6           format to specify the location of this file.  @           The installation script uses the configuration file to           define logicals.  E           %A1-I-DEFLOG, Running A1V61START.COM to define the logicalseK           -A1-I-DEFLOG, from your existing Office Server V6.0 Alpha system.   6            Defining language independent logical names  2            Defining ENGLISH language logical names  E     _________________________________________________________________f  @     10    Where possible, the VAX architecture-only installation<           matches the configuration of Office Server that isB           already installed on the Alpha system. The informationalA           messages that are displayed will depend on the existinge           configuration.  E     _________________________________________________________________   E     11    Upgrade_Installation: Confirm that you want to purge files.I  K           * Do you want to purge files replaced by this installation [YES]?   #           Press RETURN to continue.g  E                                              (continued on next page)o  F     2-34 Installation Procedure: New, Upgrade and Architecture Support P  e      I             Installation Procedure: New, Upgrade and Architecture Support_I                              2.2 Adding or Upgrading Architecture Support_    H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support________________________________________n  I         Step__Action_____________________________________________________   I         _________________________________________________________________   G         12    System checking for existing Office Server configuration.   @               The informational message depends on your existing)               configuration, for example:1  U                  During your Office Server installation on Alpha you chose to install   W                  Office Server with WPS-PLUS, therefore WPS-PLUS will also be installed_  @                  during this VAX architecture only installation.  I         _________________________________________________________________C  G         13    System checking for existing Office Server configuration.C  @               The informational message depends on your existing)               configuration, for example:c  A                  Office Server on the Alpha is linked as a MULTI-_               LANGUAGE system,Q                  therefore Office Server on this VAX will also be linked the samem                    way.s  I         _________________________________________________________________o  G         14    Specify the greatest number of simultaneous Office Server_               users.  G               * What will be the greatest number of simultaneous users:(  C               Upgrade_Installation: A default value is given. Pressw2               RETURN to accept this default value.  D               New_Installation: Specify the maximum number of OfficeA               Server users that you expect at any one time. (This H               number refers predominantly to VT users.) The installationG               procedure uses this entry to check that system parameterstH               are large enough to support your intended number of users.  I         _________________________________________________________________e  I                                                  (continued on next page)l  I        Installation Procedure: New, Upgrade and Architecture Support 2-35e r         A     Installation Procedure: New, Upgrade and Architecture Support 0     2.2 Adding or Upgrading Architecture Support    D     Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureE     __________________Support_________________________________________  E     Step__Action_____________________________________________________u  :     15    Message Router checks for upgrade installations.  B           This part of the installation procedure is determined byB           the answers that you gave during the installation on theD           other system. In this example script, the Alpha system wasE           configured to use a remote Message Router on this VAX node. B           The level of Mail directory support set up for the Alpha           system is also used.  >           %A1-I-MDCHK, Performing Mail and Directory checks...  S           %A1-I-REMMR, Your Office Server system running on the Alpha is configured_  B           -A1-I-REMMR, to use a Remote Message Router on this nodeQ           %A1-I-LOCMR, Therefore this VAX Office Server system will be configured   4           -A1-I-LOCMR, to use a local Message Router  N           %A1-I-DIROPP, Your Alpha Office Server system is configured to use a  J           -A1-I-DIROPP, Mail Directory Service. This VAX architecture only  X           -A1-I-DIROPP, installation will use the same Message Router Directory Service.             %A1-I-E           UPDATEDDS, As this is an update you will not be asked for a <           -A1-I-UPDATEDDS, Message Router Directory password           .            .n           .p  E     _________________________________________________________________a  E                                              (continued on next page)i            F     2-36 Installation Procedure: New, Upgrade and Architecture Support e  r      I             Installation Procedure: New, Upgrade and Architecture Support I                              2.2 Adding or Upgrading Architecture Support     H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support________________________________________a  I         Step__Action_____________________________________________________o  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.r  0               * Do you want to use TCP/IP [YES]?  ?               Press RETURN if you want to use TCP/IP for clientpA               connections. If you do, you are asked the following_D               questions if default service names for the AIDA ServerI               and Office Server File Cabinet Server are not registered inc-               the Internet Services database.o  ?               * Enter a port number for the AIDA Server [7300]:iU               * Enter a port number for the Office Server File Cabinet Server [7373]:_  G               Enter a different TCP/IP port number for each server. The F               port numbers can be in the range 1024 to 65535. You mustE               use the default values if you plan to use the TeamLinksu               client software.  C               The installation procedure checks that the TCPIP$IPC_tH               SHR.EXE image is installed. If it is not, you must install(               it after the installation.  I         __________________________________________________________________           17    System checking.  I               The installation procedure checks system parameters, quotasa               and identifiers.  I         _________________________________________________________________   &         18    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 C.  I         _________________________________________________________________e  I                                                  (continued on next page)M  I        Installation Procedure: New, Upgrade and Architecture Support 2-37o p  d      A     Installation Procedure: New, Upgrade and Architecture Supporta0     2.2 Adding or Upgrading Architecture Support    D     Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureE     __________________Support_________________________________________  E     Step__Action______________________________________________________  !     19    Enter the dialect code.h  @           Your language kit may also contain one or more dialectB           components. Enter the dialect code that you want to use.  >           %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets@           %VMSINSTAL-I-RESTORE, Restoring product save set B ...  O               If you wish to install a dialectal variation of ENGLISH language,m  R               enter the code for the dialect component you wish to use.  If you do  L               not wish to install a dialectal variation of ENGLISH language,  3               then accept the answer of NO_DIALECT.t  Q           * Enter dialect code for this installation (5 characters) [NO_DIALECT]:d  E     _________________________________________________________________         20    Enter the market code.  F           * Enter market code for this installation (2 characters): US  D           Enter the two-letter market code for the installation. See           the Appendix C.   E     _________________________________________________________________   E     21    Enter the name of the OpenVMS account for the Office Serverm           manager.  O           * What is the existing OpenVMS username for the Office Server account                [OFFICE]:   ,           The account details are displayed.  E     _________________________________________________________________A  >     22    Confirm that the details of the account are correct.  J           * Are all the specified account's characteristics correct [YES]?  2           Press RETURN if the details are correct.  E                                              (continued on next page)l  F     2-38 Installation Procedure: New, Upgrade and Architecture Support n  b      I             Installation Procedure: New, Upgrade and Architecture Support I                              2.2 Adding or Upgrading Architecture SupportH    H         Table 2-4 (Cont.) Installation Procedure for Adding ArchitectureI         __________________Support________________________________________e  I         Step__Action_____________________________________________________e  I         _________________________________________________________________f  @         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.c  I         ______All_the_installation_questions_have_now_been_completed.____n  ,         2.3 Automatic Postinstallation Tasks  ;               The installation procedure performs automatichI               postinstallation tasks, for example, converting data files.t  H               If a problem occurs during the postinstallation phase, see               Chapter 4.  9               The following tasks are done automatically:W  B               o  Deassigns old Office Server logicals and logicals0                  created during the installation  I               o  Runs the Office Server startup procedure, A1V61START.COM   I               o  Compiles, installs and sets protections on the followingr8                  form libraries and their site versions:                    -  OAFORM                    -  MEMRES                    -  OAN$FORMSr  .               o  Installs message symbol files                 o  Compiles TXLs  I               o  For upgrade installations, FORMAT.DAT and OA$SM_UTILITY_ (                  MASTER.DAT are updated.  I        Installation Procedure: New, Upgrade and Architecture Support 2-39S o         A     Installation Procedure: New, Upgrade and Architecture Supporto%     2.4 Manual Postinstallation Tasks_    %     2.4 Manual Postinstallation Tasks   B           There are some manual tasks that you must complete after*           the installation. See Chapter 5.                                                                                  F     2-40 Installation Procedure: New, Upgrade and Architecture Support _  _                    I                                                                         3_I         _________________________________________________________________r  I                              Installation Procedure: Additional Languagesu    F               This chapter describes the installation of an additionalE               language on an Office Server Version 6.1 system that is 3               configured as a multilanguage system.v  F                 __________________ Before You Start __________________  F                 Do not start the installation until you have completed:                 the system preparation tasks in Chapter 1.  F                 ______________________________________________________  H               During the installation procedure a number of cautions andH               general informational messages are displayed. Read all the+               displayed messages carefully.C  A               Each question in the installation is marked with an_C               asterisk (*) at the beginning of the line. If you are G               unsure how to answer a question enter a question mark (?)                for Help.S  F                 ________________________ Note ________________________  ?                 If the installation fails, you must restart theU<                 installation from the beginning. To stop the8                 installation at any point, press CTRL/Y.  F                 ______________________________________________________  @               If you are installing a new additional language orI               upgrading an existing additional language, see Section 3.1.   I               If you are installing or upgrading architecture support fori6               an additional language, see Section 3.2.      I                          Installation Procedure: Additional Languages 3-1r .  i      0     Installation Procedure: Additional LanguagesD     3.1 Installation Procedure for Additional Language Installations    D     3.1 Installation Procedure for Additional Language Installations  C           Follow the steps in Table 3-1 to install a new additional >           language or upgrade an existing additional language.  A           There are minor differences in the display depending on A           whether the installation is being run on a VAX or Alpha_           system._  @           The example script shows the addition of BRITISH as anC           additional language on an Office Server Version 6.1 Alphap>           system that is configured as a multilanguage system.                                                                  4     3-2 Installation Procedure: Additional Languages    i      I                              Installation Procedure: Additional Languages I          3.1 Installation Procedure for Additional Language Installations     I         Table_3-1_Installation_Procedure_for_An_Additional_Language______   I         Step__Action_____________________________________________________   G         1     Create a log file for the installation. Compaq recommends_C               that you keep a record of the installation in case ofpF               problems. You can keep a log by using either a hard copyE               terminal or a log file. To keep a record in a log file,_               enter:  (               $  SET HOST 0/LOG=filename  F               where filename is the name of the log file. The log fileF               is created in the directory where you enter the command.B               If you do not specify a filename, the file is calledF               SETHOST.LOG. The installation log file will be about 200               blocks.t  E               If you are running console management software, you caneC               use this to record the installation. See your consolee?               management documentation for further information.   I         _________________________________________________________________i  G         2     Load and mount the CD that contains the language softwareo               kit.  I         _________________________________________________________________s  E         3     Invoke the VMSINSTAL procedure from the SYSTEM account..  +               Enter the following commands:c  &               $ SET DEFAULT SYS$UPDATE*               $ @VMSINSTAL A1LUS061 device  A               To use an alternate working device (AWD), enter theu&               following command lines:  &               $ SET DEFAULT SYS$UPDATE;               $ @VMSINSTAL A1LUS061 device OPTIONS AWD=diskl  D               device is the device on which you have mounted the CD.H               You can use a physical or a logical device name but do notH               use logical device names beginning with A1$, OA$, or OA1$.I               A1LUS061 is the product identifier and disk is the location .               of the alternate working device.  I                                                  (continued on next page)_  I                          Installation Procedure: Additional Languages 3-3t u  n      0     Installation Procedure: Additional LanguagesD     3.1 Installation Procedure for Additional Language Installations    >     Table 3-1 (Cont.) Installation Procedure for An AdditionalE     __________________Language_______________________________________   E     Step__Action_____________________________________________________e  E     _________________________________________________________________d  $     4     Verify your system backup.  E            OpenVMS Alpha Software Product Installation Procedure V7.3u  %           It is 14-FEB-2002 at 21:27._  9           Enter a question mark (?) at any time for help._H           * Are you satisfied with the backup of your system disk [YES]?  #           Press RETURN to continue._  E     _________________________________________________________________v  C     5     Enter the number for the type of installation you want ton
           do.   ?               The current product image identification is V6.1.n  K               Using the LANGUAGE-only Office Server V6.1 kit, the following   2               installation types can be performed:  E               (1)  Install new Office Server V6.1 additional languagenA               (2)  Upgrade Office Server V6.0 additional language_@               (3)  Update Office Server V6.1 additional languageS               (4)  Add, Upgrade or Update Alpha architecture specific components ofd  E                    an existing Office Server V6.1 additional language   ?               (RL) Register licenses for pre-requisite software   <           * Which installation do you wish to perform [1]: 1  C           Enter 1 to install a new additional Office Server Version            6.1 language._  E     _________________________________________________________________   E                                              (continued on next page)   4     3-4 Installation Procedure: Additional Languages t  o      I                              Installation Procedure: Additional LanguageswI          3.1 Installation Procedure for Additional Language Installationsn    B         Table 3-1 (Cont.) Installation Procedure for An AdditionalI         __________________Language_______________________________________r  I         Step__Action_____________________________________________________   >         6     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   8               * Which action do you wish to perform [I]:  5               Press RETURN to start the installation.e  I         _________________________________________________________________e  H         7     Supply information about optional software as appropriate.  O                  During your first language installation you chose to integrate   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 anda  W                  PostScript(R) Page Overlay samples specific to the language component.   ^               * Do you want these graphics copied to the Office Server library directory [NO]?  I               Enter Y to copy the WPS-PLUS graphics library to the Office                Server directory.d  I         _________________________________________________________________i  I                                                  (continued on next page)a              I                          Installation Procedure: Additional Languages 3-5l e  n      0     Installation Procedure: Additional LanguagesD     3.1 Installation Procedure for Additional Language Installations    >     Table 3-1 (Cont.) Installation Procedure for An AdditionalE     __________________Language_______________________________________w  E     Step__Action_____________________________________________________   '     8     Select a default date format.   O               Office Server allows you to select a default date format for eacho  N               language you have installed. This will become the default Office  R               Server date format for each user (on a per language basis.) This may  R               be changed by each user through the Set Working Conditions option on  "               the User Setup Menu.  3                   Alphanumeric Date    Numeric Datec  G                   1   DD-MMM-YYYY      MM/DD/YY      (Standard Default)c  /                   2   DD-MMM-YYYY      DD/MM/YYn/                   3   DD-MMM-YYYY      YY/MM/DD /                   4   YYYY-MMM-DD      MM/DD/YY_/                   5   YYYY-MMM-DD      DD/MM/YY_/                   6   YYYY-MMM-DD      YY/MM/DD A                   7   ***** Reserved (Means system default) ***** E                   8   DD-MM-YYYY       DD/MM/YY      (Numeric format) E                   9   MM-DD-YYYY       MM/DD/YY      (Numeric format)   1           * Which date format do you require [1]:w  D           Press RETURN to use the default format or enter the number3           for the date format that you want to use.?  @           See Appendix B (or, if not US or GB, the documentation=           provided with your kit) for more details about datew           formats.  <           The installation procedure now does system checks.  E     _________________________________________________________________   E                                              (continued on next page)n  4     3-6 Installation Procedure: Additional Languages    t      I                              Installation Procedure: Additional Languages I          3.1 Installation Procedure for Additional Language Installationsm    B         Table 3-1 (Cont.) Installation Procedure for An AdditionalI         __________________Language_______________________________________w  I         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 C.  I         _________________________________________________________________   %         10    Enter the dialect code._  B               %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesetsD               %VMSINSTAL-I-RESTORE, Restoring product save set B ...  S                   If you wish to install a dialectal variation of ENGLISH language,g  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.I  [               * 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 C.r  I         __________________________________________________________________  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.  I         _________________________________________________________________I  I                                                  (continued on next page)   I                          Installation Procedure: Additional Languages 3-7a t  v      0     Installation Procedure: Additional LanguagesD     3.1 Installation Procedure for Additional Language Installations    >     Table 3-1 (Cont.) Installation Procedure for An AdditionalE     __________________Language_______________________________________   E     Step__Action_____________________________________________________   D     12    Enter the OpenVMS username for the Office Server manager's           account.  O           * What is the existing OpenVMS username for the Office Server accountr               [OFFICE]:   3           The details of the account are displayed.   E     __________________________________________________________________  7     13    Confirm that the account details are correct.   J           * Are all the specified account's characteristics correct [YES]?  >           Press RETURN to confirm that the account details are           correct.  E     __________________________________________________________________  ?     14    Specify the top-level directory for the Office Servero$           additional language files.  Q           * Enter the top-level directory required for all BRITISH language filesY  W                                                                              [BRITISH]:   E     _________________________________________________________________r  <     15    Run the IVP (Installation Verification Procedure).  D           * Do you want to run the IVP after the installation [YES]?  &           Press RETURN to run the IVP.  A           All the installation questions have now been completed.i  D           The installation procedure does automatic postinstallation@           tasks. If a problem occurs during the postinstallationB           phase, see Chapter 4. For manual postinstallation tasks,           see Chapter 5.  ?           If you are installing on a VMScluster and want to addIE           additional architecture support for the additional languagerE     ______that_you_have_installed,_see_Section_3.2.__________________y  4     3-8 Installation Procedure: Additional Languages i  q      I                              Installation Procedure: Additional LanguagesTI            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 Server C                  configuration file, OA$DATA_SHARE:A1CONFIG.DAT, on G                  the VAX system. You will be asked for this informationf)                  during the installation.O  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=filename$               $ OFFICE/NOINITM=               Enter CMD: DO OA$LIB:SM_CHECK_SYS$SYSDEVICE.SCPp  F               If references to SYS$DEVICE are found, a warning messageG               is displayed. You must remove the references as they willtE               refer to different devices on a VAX system and an AlpharF               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 support H               for an additional language that you have already installedE               on a different architecture in the same VMScluster. The C               example script shows the addition of VAX architecture_@               support for Office Server BRITISH as an additionalE               language. BRITISH is already installed as an additionaltA               language on an Alpha system in the same VMScluster.a  E         Table 3-2 Installation Procedure for Addition of ArchitecturerI         __________Support_for_an_Additional_Language_____________________   I         Step__Action_____________________________________________________   /         1 to  Follow Steps 1 to 5 in Table 3-1.m	         5n  I         __________________________________________________________________  I                                                  (continued on next page)o  I                          Installation Procedure: Additional Languages 3-9e a  t      0     Installation Procedure: Additional LanguagesB     3.2 Installing Architecture Support for an Additional Language    <     Table 3-2 (Cont.) Installation Procedure for Addition ofE     __________________Architecture_Support_for_an_Additional_Language   E     Step__Action_____________________________________________________t  C     6     Enter the number for the type of installation you want to,
           do.r  W              Using the LANGUAGE-only Office Server V6.1 kit, the following installationl  $              types can be performed:  E               (1)  Install new Office Server V6.1 additional language A               (2)  Upgrade Office Server V6.0 additional language @               (3)  Update Office Server V6.1 additional language@               (4)  Add, upgrade, or update VAX components for an;                      Office Server V6.1 additional languagee  ?               (RL) Register licenses for pre-requisite softwareA  <           * Which installation do you wish to perform [1]: 4  A           Enter 4 to add VAX architecture support for an existinga8           Office Server Version 6.1 additional language.  E     _________________________________________________________________   :     7     Confirm that you want to start the installation.  U               The installation procedure allows you to perform the following actions:d  ,               (I)   Perform the installation7               (PC)  Perform all pre-installation checksm  4           * Which action do you wish to perform [I]:  1           Press RETURN to start the installation.f  E     _________________________________________________________________m  E                                              (continued on next page)         5     3-10 Installation Procedure: Additional Languagesg           I                              Installation Procedure: Additional LanguageseI            3.2 Installing Architecture Support for an Additional Languagen    @         Table 3-2 (Cont.) Installation Procedure for Addition ofI         __________________Architecture_Support_for_an_Additional_Language_  I         Step__Action_____________________________________________________q  C         8     Enter the location of OA$DATA_SHARE:A1CONFIG.DAT, theiG               Office Server configuration file, for the existing Officeh(               Server Version 6.1 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]:   >               Enter the location of A1CONFIG.DAT in the formatD               disk:[directory]. You must always specify the location7               of the configuration file in this format.r                 %A1LUS-I-_C               DEFLOG, Running A1V41START.COM to define the logicals C               -A1LUS-I-DEFLOG, for your existing V6.1 Alpha system.o               .i               ._               ._  I         _________________________________________________________________N  7         9     Indicate whether you want to purge files.n  O               * Do you want to purge files replaced by this installation [YES]?   *               Press RETURN to purge files.  I         _________________________________________________________________n  I                                                  (continued on next page)V        I                         Installation Procedure: Additional Languages 3-11  c  o      0     Installation Procedure: Additional LanguagesB     3.2 Installing Architecture Support for an Additional Language    <     Table 3-2 (Cont.) Installation Procedure for Addition ofE     __________________Architecture_Support_for_an_Additional_Language   E     Step__Action_____________________________________________________   !     10    Configuration checking.   C           You may be asked questions depending on the configuration /           of Office Server on the Alpha system.d  F            This VAX architecture only installation will where possible  H            match the configuration of Office Server already installed on              the Alpha system.  O            During your Office Server installation on Alpha you chose to install_  Q            Office Server with WPS-PLUS, therefore WPS-PLUS will also be installed_  :            during this VAX architecture only installation.  E     _________________________________________________________________.  E                                              (continued on next page)n                                        5     3-12 Installation Procedure: Additional Languagesd    S      I                              Installation Procedure: Additional Languages_I            3.2 Installing Architecture Support for an Additional Languagep    @         Table 3-2 (Cont.) Installation Procedure for Addition ofI         __________________Architecture_Support_for_an_Additional_LanguageG  I         Step__Action_____________________________________________________n  +         11    Select a default date format.I  \                   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)w  3                       2   DD-MMM-YYYY      DD/MM/YYa3                       3   DD-MMM-YYYY      YY/MM/DD_3                       4   YYYY-MMM-DD      MM/DD/YY 3                       5   YYYY-MMM-DD      DD/MM/YY-3                       6   YYYY-MMM-DD      YY/MM/DDoE                       7   ***** Reserved (Means system default) ***** I                       8   DD-MM-YYYY       DD/MM/YY      (Numeric format)tI                       9   MM-DD-YYYY       MM/DD/YY      (Numeric format)i  5               * Which date format do you require [1]:_  I         __________________________________________________________________  &         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 C.i  I         _________________________________________________________________   I                                                  (continued on next page)t      I                         Installation Procedure: Additional Languages 3-13_ _  _      0     Installation Procedure: Additional LanguagesB     3.2 Installing Architecture Support for an Additional Language    <     Table 3-2 (Cont.) Installation Procedure for Addition ofE     __________________Architecture_Support_for_an_Additional_Languagen  E     Step__Action_____________________________________________________.  !     13    Enter the dialect code.s  >           %A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets@           %VMSINSTAL-I-RESTORE, Restoring product save set B ...  O               If you wish to install a dialectal variation of ENGLISH language,e  R               enter the code for the dialect component you wish to use.  If you do  L               not wish to install a dialectal variation of ENGLISH language,  3               then accept the answer of NO_DIALECT.   W           * Enter dialect code for this installation (5 characters) [NO_DIALECT]: US_GB   =           In this example, US_GB is the BRITISH dialect code.e  E     _________________________________________________________________   E     14    Enter the name of the OpenVMS username of the Office Server            manager's account.  U           * What is the existing VMS username for the Office Server account [OFFICE]:_  ,           The account details are displayed.  E     _________________________________________________________________   7     15    Confirm that the account details are correct.t  J           * Are all the specified account's characteristics correct [YES]?  =           Press RETURN if the account information is correct.   E     _________________________________________________________________   @     16    If you want to, run the IVP (Installation Verification           Procedure).s  C           * Do you want to run the IVP after the installation [NO]?   /           Enter YES if you want to run the IVP.   E                                              (continued on next page)n  5     3-14 Installation Procedure: Additional Languages            I                              Installation Procedure: Additional LanguagesYI            3.2 Installing Architecture Support for an Additional Language     @         Table 3-2 (Cont.) Installation Procedure for Addition ofI         __________________Architecture_Support_for_an_Additional_Language-  I         Step__Action_____________________________________________________o  E               All the installation questions have now been completed.   H               The installation procedure will do postinstallation tasks.I         ______For_manual_postinstallation_tasks,_see_Chapter_5.__________r                                                                        I                         Installation Procedure: Additional Languages 3-15_ _  _                    I                                                                         4 I         _________________________________________________________________l  I                                           Installation Errors and Failure:    H               This chapter deals with various error messages you may seeE               while installing Office Server Version 6.1 or while theuF               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 Errors_  D               Errors can occur during the installation if any of the)               following conditions exist:g  >               o  There is a problem with the operating system.  ?               o  There is a problem with prerequisite software.i  A               o  Quotas necessary for successful installation are                   insufficient.  H               o  System parameter values for successful installation are                  insufficient.  >               o  The OpenVMS help library is currently in use.  I               o  SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB arec                  not present.   G               For descriptions of the error messages generated by these C               conditions, see the OpenVMS books on system messages, E               recovery procedures, and OpenVMS software installation._E               If you are notified that any of these conditions exist,oH               you should take the appropriate action as described in the               message.  I                                       Installation Errors and Failure 4-1_ _  _      '     4.2 Failure During Postinstallation       '     4.2 Failure During Postinstallationt  C              ________________________ Note ________________________:  8              When the installation procedure reaches the>              postinstallation phase, the main installation has=              completed. If the postinstallation tasks fail, a B              message is displayed indicating that the installation=              has failed and that you need to reinstall OfficenB              Server. It is not necessary to do this; you need onlyC              rerun A1$POSTINSTALL.COM as described in this section.   C              You must rerun A1$POSTINSTALL.COM on the node on whichf1              you originally ran the installation.   C              _______________________________________________________  9     4.2.1 Failure of Upgrade Installations in Safety Mode3  E           If your installation is being performed in Safety mode, you C           need take no further action if the failure happens beforer           the message:  7           Files will now be moved to target directories_  ?           If the installation fails after this message, restore =           your original system from a backup. You can then go A           back to using the original system, or you can start thee           installation again.I  =     4.2.2 Failure of Upgrade Installations in Non-Safety Mode   E           If your installation is being performed in non-safety mode,_B           restore your original system from a backup. You can thenD           go back to using the original system, or you can start the           installation again.l       4.2.3 Full Installations  <           If a full installation fails, delete all accounts,A           identifiers and directories that have been created, ande'           start the installation again.       '     4-2 Installation Errors and Failuret a  n      I                                       4.2 Failure During Postinstallatione      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 IVPu  @               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 found   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 filerI                  does not contain the results of the IVP, but the resultsd@                  of invoking Office Server when running the IVP.  B               3. Check for any errors in the following procedures.  =                  o  During the execution of the startup file, /                     SYS$STARTUP:A1V61START.COM:t  -                        Creating logical names   9                  o  Automatic postinstallation proceduresa  -                        Installing image filese>                        Compiling and installing form libraries  I                                       Installation Errors and Failure 4-3r    T      +     4.3 Error Messages when Running the IVPS      A           4. Make sure that the Office Server TXL is compiled andpE              installed successfully, and recompile it if you receivedoA              any error messages when the postinstallation command_              file was run.  D           5. Check that you have not run out of quota on the disk orD              disks containing the OA$SHAREnnnn directories (refer to6              the manual describing OpenVMS utilities).  E           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.  =              o  The IVP user directory points to the disk andnE                 subdirectory that you specified for the Office Server /                 manager's account. For example:P  )                 a1device:[OFFICE.IVPUSER]_  ?                 where a1device is the device that you specifiedi(                 during the installation.  D              o  The Office Server account, IVP, is accessed from the8                 Office Server manager's OpenVMS account.  E           7. Run Office Server and try to use those areas that failed B              during the IVP to find more information on the error.  ?              Log in to the Office Server manager's IVP account:f  #              $ OFFICE /USERNAME=IVP   C              Manually execute each IVP test as described in DIGITAL @              Office Server Managing from a VT Terminal (the V4.0              book).e  C              ________________________ Note ________________________f  @              The IVP runs in the language context of the currentA              optional language being installed and also tests the '              international base system.e  ?              Most IVPs are designed to exercise and test Office_?              Server at a level which is normally customization-r=              independent. However, if you have customized the <              Phone Directory subsystem of Office Server, the?              display graphics (IDG) procedure may fail. This is   '     4-4 Installation Errors and Failurek           I                                   4.3 Error Messages when Running the IVPt      B                 a demonstration test used to exercise the terminal2                 graphics as a typical application.  F                 ______________________________________________________           4.4 IVP Failureg  E               If the IVP fails, the following messages are displayed::  P               The Office Server V6.1 Installation Verification Procedure failed.  N               %VMSINSTAL-E-IVPFAIL, The IVP for Office Server V6.1 has failed.                                                                  I                                       Installation Errors and Failure 4-5_ _  _                    I                                                                         5fI         _________________________________________________________________v  I                                                    Postinstallation Tasksn    B               This chapter describes the tasks that you must do toF               complete the setup of Office Server. Some of these tasksI               are optional, or only apply to particular types of systems,                 or configurations.  C               There are a number of additional setup tasks that thenH               Office Server manager must do to set up the users' workingG               environment before Office Server is used. These tasks areyG               explained in detail in the DIGITAL Office Server Managingo0               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.  I               Table_5-1_Postinstallation_Tasks___________________________   +                                     Type ofaI               Task__________________Installation_____Information_________e  D               Start Office Server   Full, upgrade    See Section 5.21               on all nodes in a     or additional 0               VMScluster system     architecture  I               ___________________________________________________________   @               Create or modify the  Full or upgrade  Section 5.3!               Office Server site-A               specific startup               proceduren  I                                                  (continued on next page)_  I                                                Postinstallation Tasks 5-1_ _  _      2     5.1 Checklist of Manual Postinstallation Tasks      E           Table_5-1_(Cont.)_Postinstallation_Tasks___________________f  '                                 Type of E           Task__________________Installation_____Information_________   E           ___________________________________________________________   <           Modify the OpenVMS    Full, upgrade    Section 5.4-           site-specific         or additional ,           startup procedure     architecture  E           ___________________________________________________________e  <           Replace the           Full, upgrade    Section 5.5-           DCLTABLES on          or additional ,           VMScluster systems    architecture  E           ___________________________________________________________t  <           Delete files that     Upgrade or       Section 5.6*           are no longer         additional(           required              language  E           ___________________________________________________________-  <           Install any missing   Full, upgrade    Section 5.7-           images                or additionaln,                                 architecture  E           ___________________________________________________________f  A           Recompile form        Upgrade          See Section 5.8.eB           libraries, including                   This section alsoE           application or                         lists form librariestB           site-specific form                     that are compiledD           libraries                              automatically afterB                                                  the installation.  E           ___________________________________________________________Y  E                                              (continued on next page)D             5-2 Postinstallation Tasks           I                            5.1 Checklist of Manual Postinstallation TasksY      I               Table_5-1_(Cont.)_Postinstallation_Tasks___________________   +                                     Type of I               Task__________________Installation_____Information_________   @               Migrate your          Upgrade of       Section 5.90               customizations:       a customized*               o  Run the CART       system                    resolution                   procedure                 o  Restore                  customizationsn!                  to modified data                   files                 o  Replace                   customized help                  files                  o  Delete obsolete                  files  I               ____________________________________________________________  A               Migrate               Upgrade,         Section 5.10e.               SITELINK60.com        additional0               to SITELINK61.COM     language and0               using Customization   architecture+               Management            supportr  I               ___________________________________________________________P  A               Link Office Server    Upgrades of      Section 5.11f.               to include code-      code-level.               level customizations  customized/                                     systems and .                                     additional3                                     architecture if 2                                     also installed  I               ___________________________________________________________   I                                                  (continued on next page)   I                                                Postinstallation Tasks 5-3     n      2     5.1 Checklist of Manual Postinstallation Tasks      E           Table_5-1_(Cont.)_Postinstallation_Tasks___________________   '                                 Type ofiE           Task__________________Installation_____Information__________  8           Set up remote mail    Full or upgrade  For new>                                 Note that        installationsA                                 local mail       with the MAILbuscC                                 is already set   400 MTA and Compaq E                                 up after the     Enterprise Directory C                                 installation.    for eBusiness, see >                                                  Section 5.12.  C                                                  For upgrade or new C                                                  installations with D                                                  Message Router, see>                                                  Section 5.13.  E           ___________________________________________________________e  >           Add WPS-PLUS login    Full or upgrade  Section 5.14.-           command procedure     installationsr*           to the system login   if you are.           command procedure     using WPS-PLUS.                                 as the default&                                 editor  E           ___________________________________________________________t  =           Move the CDA DOC_     If CDA$LIBRARY   Section 5.15i.           STYLE files to a      does not exist.           suitable location,    on your system           if necessary  E           ___________________________________________________________t  ?           Set up the user       Full or upgrade  DIGITAL Officeo@           environment                            Server ManagingC                                                  from a VT Terminal @                                                  (the V4.0 book)  E           ___________________________________________________________   E                                              (continued on next page)_       5-4 Postinstallation Tasks           I                            5.1 Checklist of Manual Postinstallation Tasks       I               Table_5-1_(Cont.)_Postinstallation_Tasks___________________   +                                     Type of I               Task__________________Installation_____Information_________u  C               Tune the File         Full or upgrade  DIGITAL OfficeeD               Cabinet Servers                        Server ManagingG                                                      from a VT TerminalmD                                                      (the V4.0 book)  I               ___________________________________________________________   C               Decide how many mail  Full or upgrade  DIGITAL Office D               Sender and Fetcher                     Server ManagingG               processes to run                       from a VT Terminal I               _______________________________________(the_V4.0_book)_____   C         5.2 Start Office Server on all Nodes in a VMScluster System   2               The Office Server startup procedure,A               SYS$STARTUP:A1V61START.COM, is supplied with Office.C               Server and is executed automatically on the node used G               for the installation, once the installation has completedc               successfully.t  B               If you are running Office Server on a VMScluster youF               must also run SYS$STARTUP:A1V61START.COM on each node inE               the cluster in order to start Office Server. If you runaC               A1V61START.COM manually from the DCL prompt, you mustsE               include the location of the Office Server configurationiG               file, OA$DATA_SHARE:A1CONFIG.DAT. OpenVMS prompts you for G               the location of this file if you do not specify it on thei               command line.   D               If you are creating new shared directories from withinE               Office Server, you must define new system logical namesaH               on each node in the cluster. For further information aboutD               running Office Server on a VMScluster, see the DIGITALH               Office Server Managing from a VT Terminal (the V4.0 book).            I                                                Postinstallation Tasks 5-5e I  s      J     5.3 Create or Modify the Site-specific Office Server Startup Procedure      @     5.3 Create or Modify the Site-specific Office Server Startup         Procedureo  D           To modify the Office Server startup command procedure, youB           must create a site-specific command procedure. The site-B           specific startup command procedure will be automaticallyA           executed by the Office Server startup command procedure            when it is executed.  E           You can create the following types of site-specific command            procedure:  D           o  A language-independent startup command procedure calledC              A1V61_SITE_START.COM. Create this startup procedure in %              OA$SITE_BUILD_SHARE_IND.r  D           o  A language-specific startup command procedure, OA$SITE_A              language_START.COM, for each language installed in a D              multilanguage Office Server system. Create this startup0              procedure in OA$SITE_BUILD_LLV_IND.  6              device:[directory.SITE.SOURCES_language])  @              where: device is the device containing the language>              files, and directory is the name of the top-level@              directory of your Office Server Version 6.1 system.  D              You can specify the directory for your default language=              by using the logical name OA$SITE_BUILD_LLV_IND.   C           If you are upgrading and you have a site-specific startup A           command procedure that you want to keep, rename it from 7           A1V60_SITE_START.COM to A1V61_SITE_START.COM.i  0     5.4 Edit the Site-specific Startup Procedure  C           When you run A1V61START.COM from the DCL prompt, you must A           include the location of the Office Server configuration C           file, OA$DATA_SHARE:A1CONFIG.DAT. OpenVMS prompts you for C           the location of this file if you do not specify it on the B           command line. When you include the Office Server startupC           procedure in the OpenVMS site startup procedure, you mustn8           specify the location of the A1CONFIG.DAT file:  0           $ @SYS$STARTUP:A1V61START.COM location       5-6 Postinstallation Tasks           I                              5.4 Edit the Site-specific Startup ProcedureT      F               where location is the location of A1CONFIG.DAT, which is               specified as:   +               device:[directory.DATA_SHARE]e  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, referu'               to your installation log.   F                 ________________________ Note ________________________  ?                 However you choose to set up your site-specific @                 startup procedures, you must ensure that all theF                 Office Server prerequisite products are started before@                 Office Server. This includes messaging software,D                 DEC Notes, and DECwindows/Motif if you are using CDA.                 converters with Office Server.  F                 ______________________________________________________  @         5.4.1 Installations With Compaq Enterprise Directory for/               eBusiness and the MAILbus 400 MTAn  C               If you have installed a new Office Server system withsG               Compaq Enterprise Directory for eBusiness and the MAILbuseF               400 MTA, you must ensure that the prerequisite messagingG               products are started before Office Server. Make sure thataH               the following 3 files are executed in the following order:  +               1. SYS$STARTUP:OSAK$START.COM   3               2. SYS$STARTUP:DXD$COMMON_STARTUP.COM(  3               3. SYS$STARTUP:MTA$COMMON_STARTUP.COMi  /         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 before                Office Server.  H               As an example, Table 5-2 describes how to edit the OpenVMSE               site-specific startup file to include the Office Server I               startup procedure after an upgrade installation from OfficeiE               Server Version 6.1. This ensures that the Office ServerlE               environment is reestablished following a system reboot.r  I                                                Postinstallation Tasks 5-7  R  O      0     5.4 Edit the Site-specific Startup Procedure      E           Table_5-2_Editing_the_OpenVMS_Site-specific_Startup_File___              InstallationE           Type_____________Do_the_Following__________________________   ,           Full and         To edit the file:-           addition         1. Find the lines:r           of seconde:           architecture     $ @SYS$MANAGER:STARTNET.COM andK           (unless you are  $ @SYS$MANAGER:MB$CONTROL START=(DDS,TS,...,ER)1n  B           using common     2. After these lines, add the following#           startup files)      line:   B                            $ @SYS$STARTUP:A1V61START.COM location2  E           ___________________________________________________________w  *           Upgrade from     Change the lineB           Office Server    $ @SYS$STARTUP:A1V60START.COM location2           Version 6.0      toe           and additionB           of second        $ @SYS$STARTUP:A1V61START.COM location2             architecture           (unless you are            using common           startup files)  E           ___________________________________________________________c  C           If you are       Add the following entry before the entry C           running a        for the Office Server startup procedure:_I           remote Message   $ @SYS$STARTUP:DDS$STARTUP.COM node nodenumbern=           Router and       where node is the name of the node6@           using the        on which the remote Message Router isD           Message Router   installed and nodenumber is the DirectoryD           Directory        Service node number of the remote Message'           Service          Router node.E  E           [1]The_exact_command_line_will_depend_on_which_Message_____   (           Router components are running.:           [2]location is the location of the Office Server           configuration file, %           OA$DATA_SHARE:A1CONFIG.DAT. E           ___________________________________________________________s       5-8 Postinstallation Tasks           I                              5.5 Replace the DCLTABLES on Cluster Systemsp      4         5.5 Replace the DCLTABLES on Cluster Systems  H               If you installed Office Server Version 6.1 on a VMSclusterH               system, you must replace the DCLTABLES on any nodes in theH               cluster where you are not installing Office Server VersionG               6.1. Enter the following commands on each of these nodes:L                 $ INSTALL A               INSTALL> REPLACE SYS$SHARE:DCLTABLES /OPEN /SHARE - #               _INSTALL> /HEADER_RESd               INSTALL> EXIT   A               You need only do this once after you have installedtG               Office Server Version 6.1. The Office Server installationoI               procedure replaces the tables automatically for the node on_A               which you are installing Office Server Version 6.1.   4         5.6 Delete Files That Are No Longer Required  D               If you have upgraded or updated Office Server, variousI               files remain in the SYSTEM directories which you can delete 9               to increase your disk space. The files are:_  :               o  For an Office Server Version 6.0 upgrade:  3                     SYS$HELP:A1060.RELEASE_NOTES orn5                     SYS$HELP:A1Llang060.RELEASE_NOTES E                     SYS$HELP:A1Cmarket060.RELEASE_NOTES, if available .                     SYS$STARTUP:A1V60START.COM  "         5.7 Install Missing Images  I               On startup, if any error messages are displayed relating toMG               images that are not installed, use the Install utility tolI               install those images before executing the startup procedure D               again. Images that you may need to install in this wayE               are those referenced by optional products that you have_C               integrated with the Office Server image. For example, D               the following command installs the image RDBSHR, which.               is referenced by VAX DATATRIEVE:                 $ INSTALL_E               INSTALL> ADD SYS$SHARE:RDBSHR /OPEN /HEADER_RES /SHARED   F               For more details of the Install Utility, see the OpenVMS               documentation.  I                                                Postinstallation Tasks 5-9                  5.8 Recompile Form Libraries            5.8 Recompile Form Libraries  A           If you are upgrading from Office Server Version 6.0 and C           you have compiled form libraries on your old system which D           are not replaced by the upgrade, you may see the following           error message:  7           Obsolete form library <name> please recompile   >           If you see this message, recompile the form library.  C              ________________________ Note ________________________8  ?              You must also compile application or site-specificl7              form libraries, and your own applications.s  C              ______________________________________________________   B           The following form libraries are compiled automatically:             o  OAFORM              o  SITEOAFORM              o  MEMRESt             o  SITEMEMRES_             o  OAN$FORMS             o  SITEOAN$FORMS  @           If you have added code or manual procedures to compile@           other form libraries, you must recompile them manuallyC           after the installation. Use the Precompile a form library E           (PCF) option from the System Customization Management (CSZ)_@           menu. See the DIGITAL Office Server Managing from a VT#           Terminal (the V4.0 book)._  5     5.9 Migrating Your Customizations After Upgrading   E           Immediately after installing Office Server Version 6.1, and D           before allowing your users to access Office Server, review4           your customizations to mandatory elements.  ?           You can rerun the CART after installing Office Server D           Version 6.1 using the Check Conflicts (CC) option from theB           Application Maintenance menu. When you run the CART fromE           within Office Server, it does not produce the site elements_C           report. It does produce the full and summary reports, and        5-10 Postinstallation Tasks,           I                         5.9 Migrating Your Customizations After UpgradingS      H               the CART resolution procedure, which are all stored as new3               elements in Customization Management.   B               If you rerun the CART, it does not keep the previousB               CART full and summary reports. To keep them, use theC               Customization Management Copy (CO) option to save theeG               elements with another name in the same area, for example, B               copy CM_CART_SUMMARY_V60$PRIMARY to CM_CART_SUMMARY_B               V60$PRIMARY_19SEP. All of the elements that you have8               already processed will have status code F.  ,               To review your customizations:  I               1. From the Customization Management (CM) subsystem, select H                  each element marked as a mandatory change and print theA                  differences between it and the new base element.   (               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 get %                  your system running.a  F               3. Test your customizations and, if they work correctly,;                  move the elements back into the live area.a  H               4. Before allowing your users back onto the system, reviewH                  your customizations to recommended elements in the same<                  way as you reviewed the mandatory elements.  I                  If you do not resolve conflicts to recommended elements, D                  users may not have access to your customizations orI                  will not have access to the full functionality of Office $                  Server Version 6.1.  D               5. Review conflicts with elements reported with statusH                  code D, see the Compaq Office Server Planning and SetupD                  Guide. Status code D indicates a customization thatD                  calls an element which has been removed from Office$                  Server Version 6.1.  I                  If the element that is called by your customized element_F                  has a status code of A, then no customized version ofF                  it exists. Your customization will fail if you deleteD                  the removed element, as described in Section 5.9.2.H                  Edit the command procedure DELETE_OBSOLETE_FILES.COM soG                  that these elements are not deleted. Use Customization I                  Management to create a new customized element to replaceS  I                                               Postinstallation Tasks 5-11r a         5     5.9 Migrating Your Customizations After Upgradingo      A              the referenced base element that no longer exists in_'              Office Server Version 6.1.   >              Use Customization Management to copy any elementsC              reported with status code A into the development area.PE              When you rerun the CART, these elements will be reportedl               with status code H.  A           6. You can now allow your users to access Office Server_<              Version 6.1. When it is convenient, resolve the2              conflicts for informational elements.  /     5.9.1 Running the CART Resolution Procedure   C           The CART resolution procedure calls individual scripts to C           process each status code. The scripts are called CM_CART_ 3           SCRIPTn, where n is the CART status code._  C           To run and edit the scripts called by the CART resolution D           procedure, you must have Application Maintainer privileges>           for the areas where the elements are stored. See theE           DIGITAL Office Server Managing from a VT Terminal (the V4.0 E           book). To run the CART resolution procedure use the Execute A           procedure (EP) option from the Application Maintainer's $           Check Conflicts (CC) menu.  >           To change the way that the CART resolution procedure@           handles elements with a particular status code, do the           following:  ?           1. Enter the Customization Management (CM) subsystem.p  C           2. Use the Access base element (ABE) option to select theg$              CART resolution script.  =           3. Copy the script that you want to change into the               development area.  <           4. Edit the script using Customization Management.  B           It is not mandatory to use the CART resolution procedure>           to resolve conflicts. If the script does not provideD           appropriate actions to resolve the conflicts at your site,)           then you do not have to use it.o  C           You can use the CART resolution procedure to resolve somey@           of the conflicts reported with an informational status?           code. You should review the CART resolution procedure A           carefully before running it. Check that your customized        5-12 Postinstallation Tasksn V  l      I                         5.9 Migrating Your Customizations After Upgradingt      E               elements do not call a removed element, see Section 5.9sC               which describes how to resolve conflicts for elementsS*               reported with status code D.  %         5.9.2 Deleting Obsolete Files-  I               A command procedure, DELETE_OBSOLETE_FILES.COM, is provided G               to remove the files that are no longer required by Officee!               Server Version 6.1.t  F                 ________________________ Note ________________________  C                 Do not run this procedure immediately after running E                 the CART resolution procedure. You must always reviews@                 this file before running it. Check that all yourD                 customizations are working correctly and ensure thatF                 your customizations do not call any elements that will-                 be deleted by this procedure.g  F                 ______________________________________________________  I               You can edit DELETE_OBSOLETE_FILES.COM to stop the deletioneG               of certain files if required, for example, if one of your_H               customizations calls an element that has been removed fromG               the base kit and which would otherwise be deleted by this                procedure.  E               For example, the suggested resolution for elements withr"               status code A is to:  H               o  Run the CART resolution procedure to delete the recordsE                  for these elements from the Customization Managementi                  databases                 o  Run theF                  command procedure OA$LIB:DELETE_OBSOLETE_FILES.COM to$                  delete the elements  H               To run DELETE_OBSOLETE_FILES.COM, enter the following from               DCL:  :               $ @OA$LIB:DELETE_OBSOLETE_FILES.COM language  I               where language is the language of the Office Server system.TH               If you have additional languages installed on your system,G               you can run this procedure for each additional languages.c  I                                               Postinstallation Tasks 5-13y m  n      5     5.9 Migrating Your Customizations After Upgrading       9     5.9.3 Replacing the Help Modules for Your Applicationn  >           For more information about customizing Help, see the2           ALL-IN-1 Application Programming: Guide.  ;           After the upgrade, copy the Office Server Version <           6.1 standard Help libraries, OA$LIB:OAHELP.HLB andA           OA$LIB:SITEHLPSOURCE.HLB from the base area to the livepC           area, OA$SITE_LIB_language. Customization Management will B           inform you that the live and development versions of theE           Help libraries are the same and ask you whether you wish toD+           continue. Answer yes to continue.   E           You must recreate your customizations to Help modules usingt@           Customization Management. Use the Access base elementsC           (ABE) option to get the base version of your Help module. C           Use the Copy (CO) option to copy the customized module topE           the development area where you can make changes to it. WhensB           you save the module Office Server formats it and puts itC           into the appropriate development Help libraries. When you.D           have tested the Help, mark it to be moved to the live area!           so that it can be used.   :     5.10 Migrate SITELINK60 Using Customization Management  9           The SITELINK61.COM file is under the control ofeB           Customization Management. It is important that you checkB           that any customizations to SITELINK60.COM are compatible           with SITELINK61.COM.  @           Use Customization Management to edit the base templateC           version of the site link file, SITELINK61.COM, to includeiA           your previous SITELINK60.COM from OA$SITE_BUILD. ReviewOB           your customizations to SITELINK61.COM and then move yourC           customized version to LIVE. Review your customizations tolB           make sure they are compatible with Office Server VersionD           6.1. Do not relink Office Server until you have done this.           See Section 5.9.  @           It is recommended that you do the following to relink:  +           $ SET DEFAULT OA$BUILD_SHARE_ARCHS           $ @OA$BUILD:A1LNKDRV         5-14 Postinstallation Taskse           I              5.11 Link Office Server to Include Code-level Customizations       D         5.11 Link Office Server to Include Code-level Customizations  I               Office Server Version 6.1 is linked during the installation B               without any customizations you may have made to yourC               existing system. Therefore, it is important to relink F               Office Server after the installation if you wish to linkF               with your customizations when you have checked them. SeeI               Chapter 2 of Compaq Office Server Planning and Setup Guide.d  B         5.12 Setting up Remote Mail When Using the MAILbus 400 MTA  F               You must complete the set up tasks for Compaq EnterpriseD               Directory for eBusiness and the MAILbus 400 MTA beforeF               you can send and receive mail using the MAILbus 400 MTA.E               The setup tasks are covered in the Compaq Office ServerT'               Planning and Setup Guide._  =         5.13 Setting up Remote Mail When Using Message Routerd  F               After the installation, local mail is already set up. IfE               you want to use Message Router for remote mail, you mayiF               need to do some or all of the tasks listed in Table 5-3,9               depending on the requirements at your site.   E               The tasks that you must do depend on the type of remote_*               Message Router which can be:  @               o  Installed on a VAX node in the same VMScluster:  F                  -  With Office Server installed on the Message Router                     node  I                  -  Without Office Server installed on the Message Router                      node  @               o  Installed on a VAX node that is not in the same,                  VMScluster as Office Server                I                                               Postinstallation Tasks 5-15o M  a      9     5.13 Setting up Remote Mail When Using Message Routere      E           Table_5-3_Tasks_for_Setting_up_Remote_Mail_________________o  E           Task_______________________For_Information_See_____________e  3           If you are using a remote  Section 5.13.1_           Message Router server_           node, make sure that"           there is a mailbox entry           on that node for your             Office Server mailbox.             You may have already#           done this as part of yourc            preinstallation tasks.  3           If you have installed      Section 5.13.2n#           Office Server Version 6.1y!           on a mixed architectureS"           cluster, you must modify"           the mailbox entry on the           Message Router node.  3           If you are using MRGATE    Section 5.13.3e"           on a remote node, set up            each node that will be           using MRGATE./  E                                              (continued on next page)I                                       5-16 Postinstallation Tasksl t         I                     5.13 Setting up Remote Mail When Using Message Router       I               Table_5-3_(Cont.)_Tasks_for_Setting_up_Remote_Mail_________h  I               Task_______________________For_Information_See_____________s  H               Set up the remote Mail     Section 5.13.4 if Office ServerE               directory                  is using a Message Router incG                                          the same VMScluster and OfficeTC                                          Server is installed on thep<                                          Message Router node  C                                          Section 5.13.4.2 if Office B                                          Server is using a MessageG                                          Router that is not in the samesG                                          VMScluster or Office Server isgE                                          not installed on the Messagei4                                          Router node  @                                          If you are using CompaqA                                          Enterprise Directory forbE                                          eBusiness after a new OfficefH                                          Server Version 6.1 installationF                                          with Message Router, you mustD                                          follow the instructions forE                                          setting up Compaq Enterprise G                                          Directory for eBusiness in the F                                          Compaq Office Server Planning9                                          and Setup Guide..  7               Edit the site-specific     Section 5.13.5g"               startup procedure to&               start up the remote MailI               directory._________________________________________________y  1         5.13.1 Create a Mailbox for Office Server   H               This section applies when Office Server is using a MessageE               Router that is not in the same VMScluster. You may have_H               already done this as part of the preinstallation tasks. IfG               you have already created a mailbox, you do not need to dod               it again.   C               Your Office Server mailbox for your node (or cluster) I               requires a mailbox entry on the remote Message Router node.     I                                               Postinstallation Tasks 5-17     T      9     5.13 Setting up Remote Mail When Using Message Router                  To add a mailbox:o  E           ___________________________________________________________rE           Step_Action________________________________________________m  @           1    Log in to the MBMANAGER account on the node whereA                Message Router is running, and enter the followingr                command:   %                $ RUN SYS$SYSTEM:MRMAN   E           ___________________________________________________________l  6           2    Enter the following at the MRM> prompt:  #                MRM> ADD localnodeA1s;                       /PASSWORD=password /COMPLETE_MESSAGESaQ                       /IGNORE_SENDER /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS                   where:n  A                o  localnode is the name of the Office Server nodenD                   or cluster. The name must be unique to the Message                    Router system.  E                o  password is the Office Server mailbox password that E                   you specified during the Office Server installation '                   on the remote system.   @                   The password that you specify here must be the@                   same as you specified during the Office Server?                   installation. If you change the password whennB                   creating the mailbox, you must also change it toB                   the same value in Office Server by using the SetA                   operating conditions (SOC) option on the Manage D                   Messaging menu. See DIGITAL Office Server Managing5                   from a VT Terminal (the V4.0 book).9  E           ___________________________________________________________i  ?           3    Exit from the Message Router management utility:n  E           _____MRM>_EXIT_____________________________________________s  <           Refer to the Message Router documentation for more&           information about mailboxes.       5-18 Postinstallation Taskse e         I                     5.13 Setting up Remote Mail When Using Message Routeru      9         5.13.2 Modifying the Message Router Mailbox Entryt  E               You must modify the Message Router mailbox entry if youdC               have a mixed-architecture cluster and you are using ayB               Message Router in the same cluster. The installationE               procedure creates a mailbox entry on the Message RouterlH               node with the /OWNER=ALLIN1 qualifier. The Alpha node willG               be unable to connect with this mailbox because the /OWNERsC               qualifier is on the mailbox. Modify the Office ServereD               mailbox entry on the Message Router node to remove the               qualifier.  $               $ RUN SYS$SYSTEM:MBMAN$               MRM> MODIFY A1/NOOWNER               MRM> EXITf  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.f  A               On each of the nodes that does not have the gateway G               started, define the logical name MRGATE to the following:a                 node::MR%c  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 MessageEH               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:   H               1. Log in to the MBMANAGER account on the VAX node in your7                  cluster that is running Message Routeri  .               2. Enter the following commands:  '                  $ RUN SYS$SYSTEM:MRMANe7                  MRM> ADD MRGATE/REPLACE="MRGATE @node"s  G                  where node is the node where the gateway is installed.   I                                               Postinstallation Tasks 5-19n 1  h      9     5.13 Setting up Remote Mail When Using Message Routerr      =           3. Exit from the Message Router management utility:                 MRM> EXIT  D           See the Message Router documentation for more information.  A     5.13.4 Setting Up the Message Router Directory Service as thee            Mail Directory_  @           The tasks that you need to do depend on the following:  E           o  If the Message Router node is in the same VMScluster ands?              has Office Server installed, see Section 5.13.4.1.   E           o  If the Message Router node is not in the same VMScluster D              or Office Server is not installed on the Message Router(              node, see Section 5.13.4.2.  5     5.13.4.1 Message Router is in the Same VMSclusterm  E           Read this section if Office Server is installed in the same E           VMScluster as Message Router and Office Server is installed ?           on the Message Router node. You can be using the MailCE           directory as either the primary or the secondary directory. @           If, during the installation, you chose to use the Mail@           directory as the primary directory, OA$DIRECT_PRIME isA           set to 2. If, during the installation, you chose to useiC           the Mail directory as the secondary directory with OfficeuB           Server as the primary directory, then OA$DIRECT_PRIME is           set to 1.   >           After installation, the following values are set up:  2           o  A user agent entry name and password.  A              -  The user agent entry name is OA$node$ALLIN1 for atA                 new or upgrade installation, where node is either D                 the node name or the cluster alias for the system onD                 which you are installing Office Server. For example,                 OA$LYNX$ALLIN1.   C              -  The user agent entry password is the Mail directory B                 password that you entered during the installation.  >           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 entrydA              (OA$node$ALLIN1). This attribute gives Office Serverv@              proxy access to the manager's entry, so that Office4              Server can update and access the entry.       5-20 Postinstallation Tasks_ _         I                     5.13 Setting up Remote Mail When Using Message Router       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               ___________________________________________________________CI               Step_Action________________________________________________x  F               1    Log in to the Office Server manager's Office Server                    account:   3                    $ OFFICESERVER /USERNAME=MANAGERe  I               ___________________________________________________________t  C               2    Enter the following commands from Office Server:   (                    <GET #ORGNAME=orgname*                    <GET #LOCATION=location                      where:e  I                    o  orgname is the name of your company or organizationn  <                    o  location is the location of your users  H                    If area routing is in use at your site, you must also                    enter:n  )                    <GET #AREA="area_code"   H                    area_code is the area code for the area that includes                    your system.                 I                                               Postinstallation Tasks 5-21r s  ,      9     5.13 Setting up Remote Mail When Using Message Routern    E           ___________________________________________________________TE           Step_Action________________________________________________p  D                If you do not know the area code, do the following on'                the Message Router node:tE                ______________________________________________________ E                Step_Action___________________________________________   >                a    Run the MAILbus configuration procedure toA                     display the current Transfer Service settings (                     in use at your site:  ,                     $ @SYS$MANAGER:MB$CONFIG  ?                b    Display the settings for the Message Routers%                     Transfer Service:i                        MBC> SHOW TS  @                     The area code is displayed, along with other)                     settings, as follows:t                           .s                         .A                         .v6                     Transfer Service uses area routing(                     Area Code : areacode                           .r                         .e                         .o  B                     where areacode is the area code in use at your                     site.t  =                3    Enter EXIT, or press CTRL/Z, to exit fromiA                     the MAILbus configuration procedure. For more C                     details of this command, see the Message Router E                _____documentation.___________________________________z  E           ___________________________________________________________o  D           3    Update the user agent entry by entering the following                command:m  (                <DO OA$LIB:USERAGENT_POST       5-22 Postinstallation Tasksk l  S      I                     5.13 Setting up Remote Mail When Using Message RouterU    I               ___________________________________________________________rI               Step_Action________________________________________________   5                    This DO script does the following:r  5                    o  Updates the user agent entry inuI                       OA$DATA_SHARE:UAPASSWRD.DAT with the Mail directory I                       identity obtained from the user agent object in theA%                       Mail directory.V  G                       The Office Server user agent is now available fork                        all users.  H                    o  Sets the Mail directory field in the Office Server5                       manager's account details to Y.o  E                    o  Copies details from the Office Server manager'sm=                       profile entry, which was created duringeE                       installation, into the manager's Mail directoryf'                       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 forL5                       organization name and location.i  H                    o  Creates a mail address (OA$DDS_AREA_ROUTE) that isG                       used for all the Mail directory subscribers owned I                       by the user agent (Office Server). The mail address E                       comprises the name of the Office Server Message E                       Router mailbox (OA$MTI_MAILBX), and the name of G                       the node or cluster (OA$PRIMARY_NODE) running the I                       Message Router to be used by Office Server. If area I                       routing is in use at your site, the network addressrE                       also includes the area code that you specified.V  I               ___________________________________________________________   H               4    Restart Office Server on all nodes in the VMScluster.  I               ___________________________________________________________     I                                               Postinstallation Tasks 5-23  O  c      9     5.13 Setting up Remote Mail When Using Message Router     E           ___________________________________________________________eE           Step_Action________________________________________________e  <           5    If you are performing an upgrade or an updateA                installation in which you have elected to use MailuC                directory addressing for the first time, see DIGITAL_B                Office Server Managing from a VT Terminal (the V4.0C                book) for information about how to populate the Mail E           _____directory.____________________________________________   9     5.13.4.2 Message Router is not in the Same VMSclustert  D           Read this section if the Message Router that you are usingE           is not in the same VMScluster as Office Server, or it is in C           the same VMScluster but Office Server is not installed on "           the Message Router Node.  (           You must create the following:  2           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 thei=              name of the local Office Server user agent entryiA              (OA$node$ALLIN1). This attribute gives Office Servera@              proxy access to the manager's entry, so that Office4              Server can update and access the entry.  A           o  Update the OA$DATA_SHARE:UAPASSWRD.DAT file with the58              name of the user agent object and password.  B           You must do some tasks on the remote Message Router node3           and some tasks on the Office Server node.   E           ___________________________________________________________ E           Step_Action________________________________________________   ?           1    On the remote Message Router node, log in to the ?                MBMANAGER account and run the MAILbus Management                 Utility, MBMAN:  %                $ RUN SYS$SYSTEM:MBMAN   E           ___________________________________________________________          5-24 Postinstallation Tasks     s      I                     5.13 Setting up Remote Mail When Using Message Router     I               ___________________________________________________________ I               Step_Action________________________________________________e  G               2    Create the user agent object that Office Server willeI                    use to access the Mail directory and add the object toe&                    the Mail directory:  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 Mail                         directory.  F                    o  password is the password that Office Server willI                       use to access the user agent object. It must not bei6                       more than eight characters long.  I               ___________________________________________________________d                                              I                                               Postinstallation Tasks 5-25o d         9     5.13 Setting up Remote Mail When Using Message Routerx    E           ___________________________________________________________ E           Step_Action________________________________________________   <           3    Create and add a subscriber entry to the Mail7                directory for the Office Server manager:   <                MBMAN>BUILD DDS SUBSCRIBER /SURNAME="MANAGER"9                MBMAN>BUILD DDS SUBSCRIBER /PROXY="uaname"_9                MBMAN>BUILD DDS SUBSCRIBER /SUBID="uaname" -                MBMAN>ADD DDS BUILT_OBJECT/LOGe                MBMAN>EXITa                  where:   D                o  MANAGER is the name of the Office Server manager'sE                   Office Server account and must be entered as shown._6                   Do not enter any other account name.  B                o  uaname is the name of the user agent object thatA                   you specified, for example, OA$nodename$ALLIN1.   @                o  /PROXY="uaname" grants the local Office ServerE                   user agent proxy access to the manager's subscriberfE                   entry. This enables the Office Server user agent toeE                   access and update the manager's subscriber entry on (                   behalf of the manager.  >                o  /SUBID="uaname" identifies the Office ServerA                   manager's subscriber entry to Office Server, as ;                   there can be many entries called MANAGER.t  E           ___________________________________________________________   C           4    On the Office Server node (VAX or Alpha), do all the A                next steps from the Office Server manager's Office                 Server account:  ?                Enter the following commands to create temporaryO@                symbols required by the script which you will run                 in the next step:  $                <GET #ORGNAME=orgname&                <GET #LOCATION=location                  where:_  E                o  orgname is the name of your company or organizatione  8                o  location is the location of your users       5-26 Postinstallation Tasks     e      I                     5.13 Setting up Remote Mail When Using Message Routero    I               ___________________________________________________________3I               Step_Action________________________________________________d  H                    If area routing is in use at your site, you must also                    enter:t  )                    <GET #AREA="area_code"e  H                    area_code is the area code for the area that includes                    your system.   H                    If you do not know the area code, do the following on+                    the Message Router node:eI                    ______________________________________________________uI                    Step_Action___________________________________________e  B                    a    Run the MAILbus configuration procedure toE                         display the current Transfer Service settingsM,                         in use at your site:  0                         $ @SYS$MANAGER:MB$CONFIG  C                    b    Display the settings for the Message Routere)                         Transfer Service:   $                         MBC> SHOW TS  D                         The area code is displayed, along with other-                         settings, as follows:S                               .s                             .                              . :                         Transfer Service uses area routing,                         Area Code : areacode                               .o                             .y                             .o  F                         where areacode is the area code in use at your                         site..  A                    c    Enter EXIT, or press CTRL/Z, to exit fromeE                         the MAILbus configuration procedure. For moreyG                         details of this command, see the Message RouteroI                    _____documentation.___________________________________r  I                                               Postinstallation Tasks 5-27L i  o      9     5.13 Setting up Remote Mail When Using Message Routerc    E           ___________________________________________________________iE           Step_Action________________________________________________   E           ___________________________________________________________   (           5    Run the following script:  (                <DO OA$LIB:USERAGENT_POST  ?                A mail message will be sent to the Office ServeruE                manager's account which contains detailed instructionst"                on what to do next.  E           ___________________________________________________________a  D           6    For details of populating the Mail Directory, see theE                DIGITAL Office Server Managing from a VT Terminal (theaE           _____V4.0_book).___________________________________________   D     5.13.5 Remote Message Router Directory Service Startup Procedure  E           On each Office Server node that will be using a remote MailgB           directory, add the following entry to your site-specificB           startup procedure before the entry for the Office Server           startup procedure:  8           $ @SYS$STARTUP:DDS$STARTUP.COM node nodenumber  @           where node is the name of the node on which the remoteE           Message Router is installed and nodenumber is the Directory 1           Service node number of the remote node.t  E           To find the Directory Service node number, do the followingc%           on the Message Router node:l              $ RUN SYS$SYSTEM:MBMAN'           MBMAN> SHOW DDS NODE nodenamey  @           where nodename is the name of the Message Router node.  @           See Section 5.4 for more information about editing the%           site-specific startup file.r             5-28 Postinstallation Tasks_ M  s      I                                     5.14 WPS-PLUS Login Command Procedures      -         5.14 WPS-PLUS Login Command Procedures  ?               During the Office Server Version 6.1 installationNH               procedure, a login command procedure, A1WPSPLUS_LOGIN.COM,E               is created in SYS$MANAGER. Add this to the system loginnF               command procedure, SYS$SYLOGIN, if you want all users toF               run with these qualifiers. Alternately, you can make theE               file available to users to put into their own LOGIN.COMe               files.  +         5.15 Moving the CDA DOC_STYLE Filesh  H               If CDA$LIBRARY does not exist on your system, the CDA DOC_G               STYLE files are installed in OA$LIB_SHARE. Move the filesn%               to a suitable location.i                                                            I                                               Postinstallation Tasks 5-29a s  h                    I                                                                         A I         _________________________________________________________________T  I                           Office Server Version 6.1 Files and Directoriess    A               This appendix lists the files that are installed in C               directories other than the Office Server directories.   *         A.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:  E               $ DIRECTORY/SECURITY device:[a1dir...]*.*/out=a1dir.TXTc  G               where a1dir is the top level directory name for each area '               (for example OFFICE.DIR)._  D               The list of files is a useful reference if you need toA               resolve any problems with file protections or ACLs.   <         A.2 Files Installed in Non-Office Server Directories  F               The following list shows the files that are installed inI               directories other than the Office Server directories. WhereiF               language is included in a file name, this is the name of;               the installed language, for example, ENGLISH.r  $               o  SYS$COMMON:[SYSLIB]  !                  OA$AIDA_CSHR.EXEo"                  OA$AIDA_DSSHR.EXE#                  OA$AIDA_GCMSHR.EXEy#                  OA$AIDA_RTLSHR.EXE #                  OA$AIDA_SECSHR.EXEn                  OA$DSL$SHR.EXE $                  OAFC$CLIENT_SHR.EXE                   OA$TMAECOMM.EXE    I                       Office Server Version 6.1 Files and Directories A-1t A  o      8     A.2 Files Installed in Non-Office Server Directories        '              DDS$RMT_VAX.EXE (VAX Only)l,              DDS$RMT_ALPHA.EXE  (Alpha Only)              DPESHR.EXE_              SYS$PROXY_SHR.EXE              OAFCDEF.H              OAFCDEF.L32              OAFCEXT.H              OAFCEXT.L32              OAFCEXT.R32              OAFC$LINK.OPT              PRXDEF.H                 DDIF$READ_DX.EXEi#              DDIF$READ_MACWRITE.EXEu              DDIF$READ_PICT.EXE               DDIF$READ_RTF.EXE               DDIF$READ_WORD5.EXE               DDIF$READ_WORDP.EXE              DDIF$READ_WPL.EXE              DDIF$WRITE_DX.EXE$              DDIF$WRITE_MACWRITE.EXE               DDIF$WRITE_PICT.EXE              DDIF$WRITE_RTF.EXEn!              DDIF$WRITE_WORD5.EXE !              DDIF$WRITE_WORDP.EXE               DDIF$WRITE_WPL.EXE               DTIF$READ_DIF.EXE              DTIF$READ_TCV.EXE              DTIF$READ_WK1.EXE              DTIF$READ_WK3.EXE              DTIF$WRITE_WK1.EXE               DTIF$WRITE_WK3.EXE +              DDIF$READ_RNO.EXE (Alpha Only)e  %              MRAPPSHAR.EXE (VAX Only) '              MRAXPSHAR.EXE (Alpha Only)R  D              FDVSHR.EXE (FMS image, added on new installations only)  >              OA$LLVlanguage.EXE (On Multilingual systems only)  F              OA$WPL_ALL_TV.EXE (Alpha with full WPS-PLUS support only)+              OA$WPL_FDP_TV.EXE (Alpha only)_  7     A-2 Office Server Version 6.1 Files and Directories  U  t      I                      A.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_LDAP.EXE_)                  OA$AIDA_PROP_SHARING.EXE_#                  OA$AIDA_SERVER.EXE !                  OA$AIDA_X500.EXEp#                  OA$IMAP$SERVER.EXE '                  OA$SCRIPT_SYMBIONT.EXEu                   OAFC$SERVER.EXE!                  OA$FORMATTER.EXEe  G                  FMSFAA.EXE (FMS image added on new installations only)iW                  FMSFCV.EXE (FMS image added on new installations on VAX machines only) G                  FMSFED.EXE (FMS image added on new installations only) G                  FMSFLG.EXE (FMS image added on new installations only) G                  FMSFLI.EXE (FMS image added on new installations only)oG                  FMSFTE.EXE (FMS image added on new installations only) G                  FMSFUU.EXE (FMS image added on new installations only)i  $               o  SYS$COMMON:[SYSMSG]                    XPORTMSG.EXEe"                  OAFC$MESSAGES.OBJ                  CNV_MSG.DAT                  DPEMSG.EXE   (                  MRAPPMSG.EXE (VAX Only)*                  MRAXPMSG.EXE (Alpha Only)  /                  DDS$MSG_ALPHA.EXE (Alpha Only)h+                  DDS$MSG_VAX.EXE (VAX Only)   H                  FDVMSG.EXE (FMS image, added on new installations only)H                  FMSMSG.EXE (FMS image, added on new installations only)  )               o  SYS$COMMON:[SYS$STARTUP]                     A1V61START.COMa"                  OA$AIDA_START.COM!                  OAFC$STARTUP.COMu                   DDS$STARTUP.COM  I                       Office Server Version 6.1 Files and Directories A-3s           8     A.2 Files Installed in Non-Office Server Directories                  o  SYS$COMMON:[SYSMGR]                 A1WPSPLUS_LOGIN.COM  )           o  SYS$COMMON:[SYSHLP.EXAMPLES]e  )              EXAMPLE_READ_DIF.CDA$OPTIONS (              EXAMPLE_READ_DX.CDA$OPTIONS.              EXAMPLE_READ_MACWRITE.CDA$OPTIONS*              EXAMPLE_READ_PICT.CDA$OPTIONS)              EXAMPLE_READ_RTF.CDA$OPTIONS_)              EXAMPLE_READ_WK1.CDA$OPTIONS )              EXAMPLE_READ_WK3.CDA$OPTIONSo+              EXAMPLE_READ_WORD5.CDA$OPTIONS_3              EXAMPLE_READ_WORD5_FONTMAP.CDA$OPTIONS +              EXAMPLE_READ_WORDP.CDA$OPTIONS )              EXAMPLE_READ_WPL.CDA$OPTIONS )              EXAMPLE_WRITE_DX.CDA$OPTIONSU/              EXAMPLE_WRITE_MACWRITE.CDA$OPTIONS_+              EXAMPLE_WRITE_PICT.CDA$OPTIONSe*              EXAMPLE_WRITE_RTF.CDA$OPTIONS*              EXAMPLE_WRITE_WK1.CDA$OPTIONS*              EXAMPLE_WRITE_WK3.CDA$OPTIONS,              EXAMPLE_WRITE_WORD5.CDA$OPTIONS,              EXAMPLE_WRITE_WORDP.CDA$OPTIONS1              EXAMPLE_WRITE_WORDP_V5_0.CDA$OPTIONS 1              EXAMPLE_WRITE_WORDP_V5_1.CDA$OPTIONSm*              EXAMPLE_WRITE_WPL.CDA$OPTIONS  :           Language specific lexicon files are installed inE           LCI$LEXICONS if you install WPS-PLUS as the default editor.a                            7     A-4 Office Server Version 6.1 Files and Directoriese u                       I                                                                         B I         _________________________________________________________________   I                                                               ENGLISH Kit     E               This supplement describes the Office Server Version 6.1nD               ENGLISH kit. This kit provides the language and marketD               components for Office Server Version 6.1. This chapterG               lists the disk space requirements for an English languagei               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:R  C                 o  English, install the English language component.   F                 o  British, install the English language component and1                    the British dialect component._  @                 o  The GB or the US market component with either?                    language, see the market information in thiss                    chapter.U  @                 If your license and support agreements are for a?                 market component other than the GB or US market <                 component with the English language kit, seeD                 Appendix C, and the documentation provided with yourA                 kit, for the market-specific information that you_                 need.p  F                 ______________________________________________________  I               The language and market components are installed during the F               Office Server Version 6.1 installation procedure. FollowG               the instructions in the Compaq Office Server Installation"(               Guide to install this kit.  I                                                           ENGLISH Kit B-1                    D           Use the information in this supplement to plan and prepareA           for the Office Server Version 6.1 installation. See thes2           Compaq Office Server Installation Guide.       B.1 About Your ENGLISH Kit  7           The ENGLISH kit has the following components:e  '           o  English language component               o  US market component              o  GB market component  &           o  British dialect component       B.1.1 Distribution Media  =           The ENGLISH kit is supplied with the Compaq OpenVMS_#           Software Product Library.        B.1.2 Savesets Provided   A           Table B-1 lists the savesets provided with your ENGLISHa           kit.  E           Table_B-1_Savesets_Provided_with_the_ENGLISH_Kit___________x  E           Component________Savesets___________________________________  E                                              (continued on next page)                                  B-2 ENGLISH Kitt t  h      I                                                B.1 About Your ENGLISH Kit       I               Table_B-1_(Cont.)_Savesets_Provided_with_the_ENGLISH_Kit___B  I               Component________Savesets__________________________________a  E               English          A1LUS061.A (Contains the Release NotesM0               language         Part 1: Language)  )                                A1LUS061.Br  )                                A1LUS061.Cc  )                                A1LUS061.D   )                                A1LUS061.E.  )                                A1LUS061.Fh  )                                A1LUS061.Go  )                                A1LUS061.H   <                                A1LUS061.I (used on VAX only)  >                                A1LUS061.J (used on Alpha only)  )                                A1LUS061.Kb  )                                A1LUS061.L   )                                A1LUS061.Ms  E               US market        A1CUS061.A (Contains the Release Notes .                                Part 2: Market)  )                                A1CUSO61.Bt  )                                A1CUS061.Ch  E               GB market        A1CGB061.A (Contains the Release Notes_.                                Part 2: Market)  B                                A1CGB061.B A1CUS061.A (Contains theG                                Release Notes Part 2: Market) A1CGB061.C   I               British_dialect__A1DUS_GB061.A_and_A1DUS_GB061.B___________   #         B.2 Disk Space Requirementsi  H               The values given in this section are required when you areD               preparing your system for installation. See Chapter 1.  I                                                           ENGLISH Kit B-3u o  n           B.2 Disk Space Requirements       E     B.2.1 Disk Space Required on the System Disk or Alternate Working            Device (AWD)  C           Table B-2 gives the disk space requirement for installing D           all the components of the Office Server Version 6.1 kit onB           the system disk or alternate working device (AWD) during@           the installation. The values for safety and non-safetyE           mode apply to both full and upgrade installations of OfficeEC           Server Version 6.1. For more information about safety and )           non-safety mode, see Chapter 1.   B           Table B-2  Disk Space Required on the System Disk or AWDE           __________(Blocks)_________________________________________   ?           Installation Type             VAX               Alpha_B                                           Non-                Non-E           ______________________Safety____safety____Safety____safety_r  D           English or British    176 000   46 200    253 000   72 600           as the primary           language  D           Addition of           60 500    34 650    137 500   72 600           architecture support           for English or           British as the           primary language  D           English or British    81 400    34 650    91 300    36 300           as an additional           language  D           Addition of           13 200    13 200    22 000    17 050           architecture support           for English or           British as an E           additional_language________________________________________   7     B.2.2 Disk Space for Language Files on Target Disks   D           This section gives the disk space requirements, in blocks,E           for installing the language files in Office Server areas on E           target disks. The following disk space tables are provided:x         B-4 ENGLISH Kit            I                                               B.2 Disk Space Requirementsf    I               ____________________________________________________________I               Type_of_Installation_________________Disk_Space_Table______   =               New installation of Office Server    Table B-3.i1               Version 6.1 with English or British 1               as the primary language, or English_,               or British as a new additional               language._  <               Upgrade installation from ALL-IN-1   Table B-4-               Version 3.2 or update of Officen0               Server Version 6.1 with English or1               British as the primary language, ori1               English or British as an additionaln               language  =               Addition, upgrade or update of VAX   Table B-5. I               or_Alpha_architecture_support._____________________________   F                 ________________________ Note ________________________  A                 If you do not install WPS-PLUS with Office Server <                 Version 6.1, you can decrease the disk spaceA                 requirement on the language disk by approximatelyp                 2000 blocks.  F                 ______________________________________________________  I               Table_B-3_Disk_Space_for_Language_Files:_New_Installation__   I               Office_Server_Area____VAX______________Alpha_______________   ;               Language disk         58 000           67 000   9               LCI$lexicon disk[1]   1500             1500   9               System disk[2]        5500             5500rI               [1]Only_required_if_you_install_WPS-PLUS_with_Office_Server                  Version 6.1.G               [2]Space required to provide Office Server language files C               to system directories when using an alternate working                device (AWD).hI               ___________________________________________________________f    I                                                           ENGLISH Kit B-5  8  s           B.2 Disk Space Requirements       ?           Table B-4 Disk Space for Language Files: Upgrade from E           __________Version_3.1______________________________________u  E           Office_Server_Area____VAX______________Alpha_______________,  7           Language disk         12 000           21 000   5           LCI$lexicon disk[1]   1500             1500i  5           System disk[2]        5500             5500wE           [1]Only_required_if_you_install_WPS-PLUS_with_Office_Server              Version 6.1.C           [2]Space required to provide Office Server language files ?           to system directories when using an alternate working            device (AWD).AE           ___________________________________________________________e  B           Table B-5 Disk Space for Language Files: Add, Upgrade orE           __________Update_Architecture_Support______________________   E           Office_Server_Area____VAX______________Alpha_______________s  7           Language disk         6000             12 000   5           System disk[1]        5500             5500 E           [1]Space_required_to_provide_Office_Server_language_files__   ?           to system directories when using an alternate workinge           device (AWD). E           ___________________________________________________________i                                 B-6 ENGLISH Kits           I                         B.3 Information on the English Language Componenta      9         B.3 Information on the English Language Componenth  H               Table B-6 lists information about your language component.  C               Table B-6 Useful Information for the English LanguagedI               __________Component________________________________________c  I               Information______Value____________Used_For_________________   <               Product name     A1LUS061         Installation  C               Language name    ENGLISH          File, directory and F                                                 logical names, and forG                                                 the /LANGUAGE qualifier   I               Language_code____US_______________During_installation______a  9         B.4 Information on the British Language Component   D               Table B-7 lists information about the British language               component.  C               Table B-7 Useful Information for the British Language I               __________Component________________________________________   I               Information______Value____________Used_For_________________   <               Product name     A1LUS061         Installation  C               Language name    BRITISH          File, directory andrF                                                 logical names, and forG                                                 the /LANGUAGE qualifierD  <               Language code    US               Installation  I               Dialect_Code_____US_GB____________Installation_____________   E               The British dialect component contains a United Kingdom C               (UK) addendum file which contains information that isID               specific to the UK. The file is provided in OA$LIB:UK_               ADDENDUM.TXT        I                                                           ENGLISH Kit B-7P E         .     B.5 Information on the US Market Component      .     B.5 Information on the US Market Component  =           Table B-8 provides information about your US market            component.  E           Table_B-8_Useful_Information_for_the_US_Market_Component___X  E           Information___________Value____________Used_For____________   A           Product name          A1CUS061         Installation and C                                                  naming of savesetsD  ?           Market name           US               Media labelingn  D           Market code           US               During installation  *                 Office Server date format:  >           Alphanumeric          DD-MMM-YYYY      Office Server  >           Numeric               MM/DD/YY         Office Server  9           WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUS   9           WPS-PLUS time         colon (:)        WPS-PLUS            separator   %                      Currency format:r  9           Currency              Dollar ($)       WPS-PLUS   9           Decimal separator     dot (.)          WPS-PLUS   9           Thousand separator    comma (,)        WPS-PLUS   E           Page_size_____________66_______________Printer_settings____   8     B.5.1 Keyboards Supported by the US Market Component  A           The US market component supports the following keyboardO           mapping tables:   C           FRENCH_A1_LK201-AA.A1KMT        FRENCH_WPS_LK201-AA.A1KMT C           FRENCH_A1_LK201-AP.A1KMT        FRENCH_WPS_LK201-AP.A1KMTaC           FRENCH_A1_LK201-BA.A1KMT        FRENCH_WPS_LK201-BA.A1KMTSC           FRENCH_A1_LK201_BP.A1KMT        FRENCH_WPS_LK201-BP.A1KMT C           FRENCH_A1_LK201-NA.A1KMT        FRENCH_WPS_LK201-NA.A1KMT C           FRENCH_A1_LK260-AA.A1KMT        FRENCH_WPS_LK250-AA.A1KMT C           FRENCH_A1_LK250-AP.A1KMT        FRENCH_WPS_LK250-AP.A1KMT   C           GERMAN_A1_LK201-AG.A1KMT        GERMAN_WPS_LK201-AG.A1KMT C           GERMAN_A1_LK201-BA.A1KMT        GERMAN_WPS_LK201-BG.A1KMTnC           GERMAN_A1_LK201-BG.A1KMT        GERMAN_WPS_LK201-BA.A1KMTTC           GERMAN_A1_LK250-AG.A1KMT        GERMAN_WPS_LK250-AG.A1KMTG       B-8 ENGLISH KitD S  X      I                                B.5 Information on the US Market Componentp      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.e  ;               To invoke the keyboard mapping tables, enter:   6               $ OFFICESERVER/KEYBOARD=keyboard_mapping  D               where keyboard_mapping is the identity of the required               keyboard.S  9         B.5.2 Modems Supported by the US Market Component   >               Hayes and Hayes-compatible modems are supported.  2         B.6 Information on the GB Market Component  >               Table B-9 lists information about your GB market               component.  I               Table_B-9_Useful_Information_for_the_GB_Market_Component___A  I               Information___________Value____________Used_For____________   E               Product name          A1CGB061         Installation and.G                                                      naming of savesetsA  C               Market name           GB               Media labelingP  H               Market code           GB               During installation  -                    Office Server date format:3  B               Alphanumeric          DD-MMM-YYYY      Office Server  B               Numeric               DD/MM/YY         Office Server  =               WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUSN  =               WPS-PLUS time         colon (:)        WPS-PLUSa               separator   (                         Currency format:  =               Currency              Pound ()        WPS-PLUS   I                                                  (continued on next page)   I                                                           ENGLISH Kit B-9            .     B.6 Information on the GB Market Component      @           Table B-9 (Cont.) Useful Information for the GB MarketE           __________________Component________________________________c  E           Information___________Value____________Used_For____________   9           Decimal separator     dot (.)          WPS-PLUSr  9           Thousand separator    comma (,)        WPS-PLUS   E           Page_size_____________66_______________Printer_settings____l  8     B.6.1 Keyboards Supported by the GB Market Component  A           The GB market component supports the following keyboardt           mapping tables:   C           FRENCH_A1_LK201-AA.A1KMT        FRENCH_WPS_LK201-AA.A1KMT C           FRENCH_A1_LK201-AP.A1KMT        FRENCH_WPS_LK201-AP.A1KMTaC           FRENCH_A1_LK201-BA.A1KMT        FRENCH_WPS_LK201-BA.A1KMToC           FRENCH_A1_LK201_BP.A1KMT        FRENCH_WPS_LK201-BP.A1KMTmC           FRENCH_A1_LK201-NA.A1KMT        FRENCH_WPS_LK201-NA.A1KMT C           FRENCH_A1_LK250-AA.A1KMT        FRENCH_WPS_LK250-AA.A1KMT C           FRENCH_A1_LK250-AP.A1KMT        FRENCH_WPS_LK250-AP.A1KMT   C           GERMAN_A1_LK201-AG.A1KMT        GERMAN_WPS_LK201-AG.A1KMTnC           GERMAN_A1_LK201-BA.A1KMT        GERMAN_WPS_LK201-BG.A1KMTSC           GERMAN_A1_LK201-BG.A1KMT        GERMAN_WPS_LK201-BA.A1KMTeC           GERMAN_A1_LK250-AG.A1KMT        GERMAN_WPS_LK250-AG.A1KMTr  D           SPANISH_A1_LK201-AA.A1KMT       SPANISH_WPS_LK201-AA.A1KMTD           SPANISH_A1_LK201-BA.A1KMT       SPANISH_WPS_LK201-BA.A1KMTD           SPANISH_A1_LK201-BS.A1KMT       SPANISH_WPS_LK201-BS.A1KMTD           SPANISH_A1_LK201-LS.A1KMT       SPANISH_WPS_LK201-LS.A1KMTD           SPANISH_A1_LK250-AS.A1KMT       SPANISH_WPS_LK250-AS.A1KMT  2           A list of supported keyboards is held in)           OA$DATA_SHARE:OA$KEYBOARDS.DAT.   7           To invoke the keyboard mapping tables, enter:   2           $ OFFICESERVER/KEYBOARD=keyboard_mapping  @           where keyboard_mapping is the identity of the required           keyboard.l       B-10 ENGLISH Kit    p      I                                B.6 Information on the GB Market Component       9         B.6.2 Modems Supported by the GB Market ComponentE  >               Hayes and Hayes-compatible modems are supported.                                                                                    I                                                          ENGLISH Kit B-11m    n                    I                                                                         C-I         _________________________________________________________________   I                                          Information on Market Componentso    E               If your Office Server license and support agreement are G               for a market component other than the US or GB components D               with the English language kit, you can find the marketI               information that you need in this appendix. You can installa@               the market component from the Office Server media.  H               For information on the US or GB components, see Appendix B  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.   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  A1Cmc061.A                  o  A1Cmc061.B                  o  A1Cmc061.Ce  C               where mc is the two-letter market code defined in the E               tables in this chapter, for example, BE for the Belgiann               market component.     I                                      Information on Market Components C-16    U            C.1 Belgian Market Component            C.1 Belgian Market Component  C           Table C-1 lists useful information for the Belgian marketS1           component of Office Server Version 6.1.i  =           Table C-1 Useful Information for the Belgian MarketqE           __________Component________________________________________n  E           Information___________Value____________Use_________________   A           Product name          A1CBE061         Installation and C                                                  naming of savesetso  D           Market code           BE               During installation  *                 Office Server date format:  >           Alphanumeric          DD-MMM-YYYY      Office Server  >           Numeric               DD-MM-YY         Office Server  9           WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUS   9           WPS-PLUS time         colon (:)        WPS-PLUSf           separatorr  %                      Currency format:s  9           Currency symbol       BEF              WPS-PLUS   9           Decimal separator     comma (,)        WPS-PLUSD  E           Thousand_separator____dot_(.)__________WPS-PLUS____________   !     C.2 Canadian Market Component   D           Table C-2 lists useful information for the Canadian market1           component of Office Server Version 6.1._  >           Table C-2 Useful Information for the Canadian MarketE           __________Component________________________________________i  E           Information___________Value____________Use_________________6  A           Product name          A1CCA061         Installation and C                                                  naming of savesets   D           Market code           CA               During installation  *                 Office Server date format:  E                                              (continued on next page)   (     C-2 Information on Market Components s  r      I                                             C.2 Canadian Market Component_      C               Table C-2 (Cont.) Useful Information for the Canadian I               __________________Market_Component_________________________   I               Information___________Value____________Use_________________   B               Alphanumeric          DD MMM YYYY      Office Server  B               Numeric               DD/MM/YY         Office Server  =               WPS-PLUS date format  dd mmmmmm yyyy   WPS-PLUS_  =               WPS-PLUS time         colon (:)        WPS-PLUS                separator_  (                         Currency format:  =               Currency symbol       $                WPS-PLUS   =               Decimal separator     comma (,)        WPS-PLUSe  I               Thousand_separator____dot_(.)__________WPS-PLUS____________   "         C.3 Dutch Market Component  E               Table C-3 lists useful information for the Dutch market 5               component of Office Server Version 6.1.6  I               Table_C-3_Useful_Information_for_the_Dutch_Market_Component   I               Information___________Value____________Use_________________   E               Product name          A1CNL061         Installation andrG                                                      naming of savesets   H               Market code           NL               During installation  -                    Office Server date format:e  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-PLUSa               separatorw  (                         Currency format:  =               Currency symbol       F                WPS-PLUS   =               Decimal separator     comma (,)        WPS-PLUS   I                                                  (continued on next page)   I                                      Information on Market Components C-3P L  w           C.3 Dutch Market Component      C           Table C-3 (Cont.) Useful Information for the Dutch MarketgE           __________________Component________________________________o  E           Information___________Value____________Use__________________  E           Thousand_separator____dot_(.)__________WPS-PLUS____________        C.4 French Market Component   B           Table C-4 lists useful information for the French market1           component of Office Server Version 6.1.e  <           Table C-4 Useful Information for the French MarketE           __________Component________________________________________a  E           Information___________Value____________Use_________________0  A           Product name          A1CFR061         Installation and C                                                  naming of savesetse  D           Market code           FR               During installation  *                 Office Server date format:  >           Alphanumeric          DD-MMM-YYYY      Office Server  >           Numeric               DD/MM/YY         Office Server  9           WPS-PLUS date format  dd-mmm-yyyy      WPS-PLUS   9           WPS-PLUS time         colon (:)        WPS-PLUSr           separator_  %                      Currency format:_  9           Currency symbol       FF               WPS-PLUS_  9           Decimal separator     comma (,)        WPS-PLUS   E           Thousand_separator____blank_(_)________WPS-PLUS____________        C.5 German Market Componente  B           Table C-5 lists useful information for the German market1           component of Office Server Version 6.1.   (     C-4 Information on Market Components _  _      I                                               C.5 German Market Component       @               Table C-5 Useful Information for the German MarketI               __________Component________________________________________g  I               Information___________Value____________Use_________________   E               Product name          A1CDE061         Installation andLG                                                      naming of savesets_  H               Market code           DE               During installation  -                    Office Server date format:L  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-PLUSc               separatoru  (                         Currency format:  =               Currency symbol       DM               WPS-PLUS   =               Decimal separator     comma (,)        WPS-PLUSo  =               Thousand separator    dot (.)          WPS-PLUSi  I               Page_size_____________72_______________Printer_settings_____  "         C.6 Swiss Market Component  E               Table C-6 lists useful information for the Swiss marketd5               component of Office Server Version 6.1.   I               Table_C-6_Useful_Information_for_the_Swiss_Market_Component   I               Information___________Value____________Use_________________   E               Product name          A1CCH061         Installation andeG                                                      naming of savesetsU  H               Market code           CH               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   I                                                  (continued on next page)e  I                                      Information on Market Components C-5                 C.6 Swiss Market Component      C           Table C-6 (Cont.) Useful Information for the Swiss MarketaE           __________________Component_________________________________  E           Information___________Value____________Use_________________   9           WPS-PLUS time         colon (:)        WPS-PLUS            separator   %                      Currency format:n  9           Currency symbol       SFr              WPS-PLUSa  9           Decimal separator     dot (.)          WPS-PLUS   E           Thousand_separator____apostrophe_(')___WPS-PLUS____________                                                             (     C-6 Information on Market Components                                 F      _________________________________________________________________  F                                                                  Index      F      A______________________________   D______________________________  0      A1CONFIG.DAT,  5-6                DCLTABLES8      A1V61START.COM,  5-5, 5-6           replacing,  5-92      Applications                      DDS$STARTUP@        replacing help modules, 5-14      adding to site-specificC      AUTOGEN,  1-25                         startup procedure, 5-28l  0      B                                 DEC NotesF      _______________________________     starting before Office Server1      Backing up,  1-45                      , 5-71A                                        DELETE_OBSOLETE_FILES.COM,2.      C______________________________      5-135      CART                              Deleting files_?        running after installation,       postinstallation,  5-9HD          5-10                          Deleting obsolete files after=      CART resolution procedure            installation,  5-13 ,        running and editing, 5-12       Disks:      Checklist                           backing up,  1-45E        postinstallation tasks, 5-1     Disk space requirements,  1-27M  (      Cluster                           EF        VMSmail Gateway configuration   _______________________________;          ,  5-19                       Error messages,  4-3n-      Configuring                       Errors 5        VMSmail Gateway, 5-19             fatal,  1-41A9      Correcting system set-up            non-fatal,  1-42_         errors, 1-41F      Customizations                    F______________________________:        linking Office Server to        Fatal errors,  1-416          include,  5-15                Files, deleting?        migrating, 5-10                   postinstallation,  5-9e$        reviewing after installation,
          5-11A  F                                                                Index-1 r                      Form librariesF       recompiling,  5-10               L______________________________  /                                        Licenses D     G______________________________     prerequisite products,  1-15  6     Global page file sections          Licensing, 1-15?        (GBLPAGFIL), 1-23               Linking Office Server to @     Global pages (GBLPAGES),  1-23       include customizations,-     Global sections (GBLSECTIONS),       5-15f4        1-23                            Logical names8                                         assigning,  1-28-     H______________________________    Logins17     Help modules                        disallow,  1-44   (       replacing for your               MF          application, 5-14             _______________________________.                                        Mailbox@     I                                   adding for remote Office?     _______________________________        Server systems, 5-18Y8     Images                              modifying,  5-195       missing,  5-9                    Mail directoryL?       required,  1-32                   setting up with MessageLB     Installation                           Router outside cluster,/       aborting,  2-2                       5-24 C       disk space required,  1-27        setup for Message Router in =       time required,  2-2                  same cluster, 5-20aC     Installation of optional            starting up for remote use,L/        software                            5-28n5       order of,  1-16                  Message Routern9     Installed images                    setting up,  5-18_=       required,  1-32                  Message Router mailbox <     Installing account                  modifying for mixed-A       quotas required during               architecture clusters, /          installation, 1-17                5-19S0       valid rights identifier,         Migrating=          1-17                           customizations,  5-10      Installing missing images (        postinstallation, 5-9           NF     IVP                                _______________________________C       error messages,  4-3             Non-fatal checks, repeating,A-                                          1-41M=                                        Non-fatal errors, 1-42B         Index-2  R  H              ?                                           Remote Mail directory-=         O______________________________     starting up, 5-28_E         OA$DIRECT_PRIME, 5-20             Repeating non-fatal checks,K1         Office Server                        1-41   $          starting on all nodes,  5-5I         Optional software                 S______________________________N?          order of installation,  1-16     SITELINK61.COM,  5-14E?         Order of installation of          Site-specific startup ;           optional software,  1-16           procedure, 5-6.  D                                             adding DDS$STARTUP, 5-282         P______________________________   Starting  >         PC option, 1-41                     Office Server, 5-5;         Perform all preinstallation       Startup procedure 9           checks (PC) option,  1-41         creating, 5-6SF         Preinstallation                     editing site-specific, 5-6>          checks,  1-41                      site specific, 5-6E         Preparing system for              SYS$STARTUP:A1V61START.COM,a0           installation,  1-43, 1-44          5-60         Prerequisite software             SystemG          licenses,  1-15                    preparing for installation,68                                               1-43, 1-445         R______________________________   System disk <         Recompiling                         backing up, 1-45A          form libraries,  5-10            System parameter values G         Registering software licenses,      changing with AUTOGEN, 1-25G  I           1-15                            T______________________________ 5         Release notes, 1-7                Target disk_<          printing,  1-7                     backing up, 1-45H          reading,  1-7                    Time required for installation         Relinking 2          recommendations,  5-14              , 2-2           RemoteI          VMSmail Gateway configuration    U______________________________   /             ,  5-19                       Usersa9         Remote mail                         log out, 1-44d$          setting up with MAILbus 400I             MTA and Compaq Enterprise     V______________________________m9             Directory for eBusiness,      VMSmail Gateway =             5-15                            configuring, 5-19            setting up with Message             Router,  5-15n  I                                                                   Index-3e