





                                                              AA-FX80E-TE









             VAX TEAMDATA
             ____________________________________________
             Installation Guide




             May 1990

             This manual contains information on installing VAX TEAMDATA.




             OPERATING SYSTEM:             VMS Version 5.0 or higher

             SOFTWARE VERSION:             VAX TEAMDATA Version 1.4









             digital equipment corporation
             maynard, massachusetts

 






             May 1990

             The information in this document is subject to change without
             notice and should not be construed as a commitment by Digital
             Equipment Corporation. Digital Equipment Corporation assumes
             no responsibility for any errors that may appear in this
             document.

             The software described in this document is furnished under a
             license and may be used or copied only in accordance with the
             terms of such license.

             No responsibility is assumed for the use or reliability
             of software on equipment that is not supplied by Digital
             Equipment Corporation or its affiliated companies.

             Restricted Rights: Use, duplication, or disclosure by the
             U.S. Government is subject to restrictions as set forth in
             subparagraph (c)(1)(ii)  of the Rights in Technical Data and
             Computer Software clause at DFARS 252.227-7013.

              Digital Equipment Corporation 1986, 1987, 1988, 1990.

             All Rights Reserved.
             Printed in U.S.A.

             The postpaid Reader's Comments forms at the end of this
             document request your critical evaluation to assist in
             preparing future documentation.

             The following are trademarks of Digital Equipment Corporation:

             ALL-IN-1         MicroVAX         VAXcluster
             CDD              PDP              VIDA
             DATATRIEVE       RALLY            VMS
             DEC              Rdb/VMS          VT
             DECalc           TEAMDATA         WPS-PLUS
             DECgraph         UNIBUS           Xway
             DECnet           VAX
             DECslide         VAX DBMS
             DECUS            VAX RMS          DIGITAL
                                                                    ZK5397

             Lotus 1-2-3 is a registered trademark of Lotus Development
             Corporation.
             Multiplan and SYLK are registered trademarks of Microsoft
             Corporation.
             Supercomp-Twenty and 20/20 are trademarks of Access
             Technology, Inc.
             VisiCalc is a registered trademark of VisiCorp, Inc.
             dBase III is a trademark of Ashton-Tate.
             R:base 5000 is a trademark of Microrim.
             IBM and DB2 are registered trademarks of International
             Business Machines Corporation.
             IDMS/R is a trademark of Cullinet Software, Inc.

 















          ________________________________________________________________


                                                                  Contents




          Preface..................................................    vii


          1  Preparing for Installation

              1.1  Checking the Distribution Kit...................    1-2
              1.2  Prerequisite Hardware...........................    1-2
              1.3  Required Operating System Components............    1-3
              1.4  Prerequisite Software...........................    1-3
              1.4.1  TEAMDATA and VAX Rdb/VMS .....................    1-4
              1.5  Optional Software...............................    1-4
              1.5.1  TEAMDATA and VAX DATATRIEVE ..................    1-5
              1.5.2  TEAMDATA and VAX RALLY .......................    1-5
              1.5.3  TEAMDATA and VAX Xway ........................    1-5
              1.5.4  TEAMDATA and VIDA ............................    1-5
              1.6  Registering Your License........................    1-5
              1.7  VAXcluster Considerations.......................    1-6
              1.8  Preparing Your System and the Installing
                   Account.........................................    1-6
              1.8.1  Checking Privileges of the Installing
                     Account......................................     1-7
              1.8.2  Checking and Setting User Process Quotas .....    1-8


                                                                       iii

 






              1.8.3  Disk Space Requirements ......................    1-9
              1.8.4  Checking and Setting System Parameters .......   1-10
              1.8.5  Changing System Parameters ...................   1-12
              1.9  Performance Considerations......................   1-13
              1.9.1  Memory Management ............................   1-14
              1.9.2  Paging and Swapping Files ....................   1-14
              1.9.3  System Parameters ............................   1-15
              1.10 Backing Up Your System Disk.....................   1-16


          2  Installing TEAMDATA

              2.1  Running the VMSINSTAL Command Procedure.........    2-2


          3  Post-Installation Procedures

              3.1  Moving TEAM$LIBRARY.............................    3-1
              3.2  Editing SYSTARTUP_V5.COM........................    3-2
              3.3  Activating TEAMDATA on a VAXcluster.............    3-2
              3.4  Running TEAMDATA................................    3-3
              3.5  Running the Installation Verification Procedure
                   Separately......................................    3-3
              3.6  DATATRIEVE Versions.............................    3-3
              3.7  Granting Required User Privileges...............    3-4
              3.8  Authorizing User Quotas.........................    3-4
              3.9  Managing Run Unit Journal Files.................    3-4
              3.10 Granting Database Access to Users on Other
                   Systems.........................................    3-5
              3.11 TEAMDATA Shutdown Procedure.....................    3-6










          iv

 






          4  Maintaining TEAMDATA

              4.1  Reading a Bugcheck Dump File....................    4-1
              4.2  Insufficient Parameter Values...................    4-3
              4.3  Reporting Problems to Digital...................    4-4


          5  Installing TEAMDATA in ALL-IN-1 Menus

              5.1  Copying the TEAMDATA Command Files..............    5-1
              5.2  Linking TEAMDATA to the ALL-IN-1 Menu...........    5-2
              5.3  Recompiling the Forms Library...................    5-4
              5.4  Running TEAMDATA from the ALL-IN-1 Menu.........    5-4


          A  TEAMDATA Files


          B  Sample TEAMDATA Installation


          Index


          Tables

              1-1  Required Installer Privileges...................    1-7

              1-2  Required User Process Quotas....................    1-8

              1-3  Disk Requirements...............................    1-9

              1-4  Required System Parameters......................   1-11

              A-1  TEAMDATA Files..................................    A-1





                                                                         v

 














          ________________________________________________________________


                                                                   Preface




          Purpose of This Guide

             This guide describes how to install VAX TEAMDATA on the VMS
             operating system. You should review the entire guide before
             you start the installation.

          Who Should Use This Guide

             This guide is for VMS system managers or others responsible
             for installing and maintaining system software. To install
             the VAX TEAMDATA software, you must have access to a
             privileged account such as the SYSTEM account, and you
             must be familiar with the VMS installation procedure,
             VMSINSTAL.COM.










                                                                       vii

 






          Structure of This Guide

             This manual includes five chapters and two appendixes:

             Chapter 1     Explains how to plan the installation and
                           prepare your system.

             Chapter 2     Explains how to install the software and run
                           the Installation Verification Procedure (IVP).

             Chapter 3     Explains how to change your VMS system by
                           adjusting the required characteristics for
                           running TEAMDATA.

             Chapter 4     Explains how to detect, solve, and report
                           problems you may encounter after installing
                           TEAMDATA.

             Chapter 5     Explains how to install TEAMDATA in an ALL-IN-1
                           menu.

             Appendix A    Lists the files included in the TEAMDATA kit.

             Appendix B    Presents the log of a sample installation of
                           TEAMDATA.

          For More Information

             For more information on TEAMDATA, refer to:

              _ Introduction to VAX TEAMDATA

              _ Using VAX TEAMDATA

              _ VAX TEAMDATA Command Summary

              _ VAX TEAMDATA Quick Reference Guide



          viii

 






             For more information about the VMSINSTAL procedure, refer to:

              _ VMS System Manager's Manual, in the VMS base documentation
                set

              _ Guide to Setting Up a VMS System, in the VMS system
                management kit.

             For information on running RALLY applications from TEAMDATA,
             refer to the VAX RALLY Application User's Guide.

             For more information on VAX Xway, refer to the VAX Xway
             User's Guide. Xway is used in the TRANSFER IMPORT and
             TRANSFER EXPORT commands.

             For more information on VIDA, refer to the VIDA with IDMS
             /R Handbook. VIDA is used in the TRANSFER MAKE_KNOWN TABLE
             command when accessing IBM databases.

             For more information on VIDA for DB2, refer to the VIDA
             Client for DB2 Handbook.

             For more information on managing Rdb/VMS databases and using
             the RDO utility, refer to the VAX Rdb/VMS Guide to Database
             Maintenance and Performance.

             For more information about using TEAMDATA with ALL-IN-1,
             refer to the ALL-IN-1 Office Menu System Manager's Guide.

          Conventions

             The following conventions are used in this guide:

             <Return>          In procedures, key names are shown enclosed
                               to indicate that you press a key on the
                               keyboard.


                                                                        ix

 







             <Ctrl/x>          A sequence such as <Ctrl/x> indicates that
                               you must hold down the key labeled Ctrl
                               while you press another key or a pointing
                               device button.

             ()                In format descriptions, parentheses
                               indicate that, if you choose more than
                               one option, you must enclose the choices in
                               parentheses.

             []                In format descriptions, brackets indicate
                               that whatever is enclosed is optional;
                               you can select none, one, or all of the
                               choices.

             {}                In format descriptions, braces surround a
                               required choice of options; you must choose
                               one of the options listed.

             user input        Red ink indicates information that you must
                               enter from the keyboard or a screen object
                               that you must choose or click on. In the
                               Bookreader, information you must enter from
                               the keyboard is indicated by boldface text.

             italic text       Italic text represents information that
                               can vary in system messages (for example,
                               Internal error number).

             UPPERCASE TEXT    Uppercase letters indicate that you must
                               enter a command (for example, enter OPEN
                               /READ). Uppercase letters also indicate
                               the name of a routine, the name of a file,
                               the name of a file protection code, or the
                               abbreviation of a system privilege.



            x
   

 






             In examples, an implied carriage return occurs at the end of
             each line, unless otherwise noted. You must press the RETURN
             key at the end of a line of input.





































                                                                        xi

 

















                                                                              1
               ________________________________________________________________

                                                     Preparing for Installation




                  This chapter describes tasks that you must complete before
                  installing TEAMDATA. Installing TEAMDATA is similar to
                  installing other VMS layered products. You must do the
                  following:

                   _ Take an inventory of the software distribution kit.

                   _ Make sure that your system has the prerequisite hardware,
                     and that is has enough memory and available disk space to
                     install and run TEAMDATA.

                   _ Make sure that your system has the required VMS operating
                     system components and the prerequisite software.

                   _ If you are installing on a VAXcluster, decide where to
                     install TEAMDATA, depending on your configuration.

                   _ Register and load your TEAMDATA license.

                   _ Check that the account you use to install the software has
                     the required privileges and quotas.

                   _ Decide what values your VMS system parameters should have.

                   _ Back up your system disk.





                                                Preparing for Installation  1-1

 











                   _ Advise your users when the installation will take

                     place and how long it will take. The installation takes
                     approximately 50 minutes, depending on your type of media
                     and your system configuration.

                  Once you have prepared your system, you can then perform
                  the installation procedure as described in Chapter 2 and
                  any necessary post-installation procedures as described in
                  Chapter 3.

               1.1  Checking the Distribution Kit

                  Each VAX TEAMDATA distribution kit contains:

                   _ A bill of materials (BOM) and indented bills report (BIL)

                   _ The distribution medium for the TEAMDATA software

                   _ Documentation for the product.

                     Media Only kits include just the installation guide.

                   _ The TEAMDATA LMF license

                  To ensure that you have a complete kit, check the kit
                  contents against the bill of materials and the indented bills
                  report.

                  Check also that you received the correct distribution medium,
                  labeled as TEAMDATA V1.4.

                  If your kit is damaged or if you find that parts of it are
                  missing, contact your Digital representative.

               1.2  Prerequisite Hardware

                  You need the following hardware and memory to install and run
                  TEAMDATA:

                  Hardware       TEAMDATA runs on all VAX systems, except the
                  required:      VAX-11/725, VAX-11/782, MicroVAX I, VAXstation
                                 I, and VAXstation 8000. For a complete list
                                 of processors, see the VAX TEAMDATA Software
                                 Product Description.

                  Memory         4 megabytes.
                  required:

               1-2  Preparing for Installation

 












                  Disk space     See Table 1-3.
                  required:


               1.3  Required Operating System Components

                  TEAMDATA requires the following VMS Version 5.0 components:

                   _ VMS required files (BASE)

                   _ Network support (NETWORK), if you intend to use remote
                     databases or send reports to other systems using the Mail
                     utility

                  If your system does not meet these requirements, the
                  installation will fail. You must install the required
                  software using VMSTAILOR before performing the TEAMDATA
                  installation.

               1.4  Prerequisite Software

                  To install TEAMDATA Version 1.4, you need the following
                  software installed on your system:

                   _ A valid VMS operating system configuration running VMS
                     Version 5.0 or higher.

                   _ Your VAX TEAMDATA Software License registered. See
                     Section 1.6 for more information.

                   _ One of the following Rdb/VMS kits:

                      _ Rdb/VMS Full Development Kit Version 3.0-B or higher

                      _ Rdb/VMS Interactive Kit Version 3.0-B or higher

                      _ Rdb/VMS Run-Time Kit Version 3.0-B or higher

                  Contact your DIGITAL representative if you have questions
                  about the compatibility of other software products with this
                  version of TEAMDATA. You can request the most recent copy of
                  the VAX System Support Addendum, SPD 27.02.04-A, which will
                  verify which versions of your operating system are compatible
                  with this version of TEAMDATA.

                                                Preparing for Installation  1-3

 











                  1.4.1  TEAMDATA and VAX Rdb/VMS

                  VAX Rdb/VMS is a prerequisite for TEAMDATA. You must have
                  either the full development, interactive, or the run-time
                  license for Rdb/VMS. If you do not have VAX Rdb/VMS installed
                  on your system, or if you have only the remote kit, TEAMDATA
                  will not run.

                  To find out which version of Rdb/VMS is running on your
                  system, type at the DCL prompt:

                    $ RUN SYS$SYSTEM:RDO

                  The RDO prompt is displayed. To see what version of Rdb/VMS
                  is installed on your system, use the SHOW VERSION command, as
                  in the example that follows. RDO displays the version number.
                  Use the exit command to exit from RDO.

                    RDO> SHOW VERSION
                    Current version of RDO is:  Rdb/VMS V3.0-B
                    RDO> EXIT

               1.5  Optional Software

                  You can use the following software with VAX TEAMDATA Version
                  1.4:

                   _ ALL-IN-1 Version 2.1 or higher

                   _ VAX RALLY Version 2.1 or higher

                   _ VAX DATATRIEVE Version 4.0 or higher

                   _ VAX CDD/Plus Version 3.4 or higher

                   _ VAX DBMS Version 3.0 or higher

                   _ VAX Xway Version 1.1

                   _ VIDA with IDMS/R Version 2.0

                   _ VIDA for DB2 Version 1.0

                  However, none of this software is required to run TEAMDATA.
                  If you do not have the optional software described in the
                  following sections, you do not need to read those sections.


               1-4  Preparing for Installation

 











                  1.5.1  TEAMDATA and VAX DATATRIEVE

                  If you want to use DATATRIEVE domains through TEAMDATA, you
                  must have DATATRIEVE Version 4.0 or higher installed on
                  your system. DATATRIEVE requires VAX CDD/Plus Version 3.4
                  or higher.

                  1.5.2  TEAMDATA and VAX RALLY

                  If you want to run VAX RALLY applications from TEAMDATA,
                  you must have RALLY Version 2.1 or higher installed on your
                  system.

                  1.5.3  TEAMDATA and VAX Xway

                  If you want to use the TRANSFER IMPORT and TRANSFER EXPORT
                  commands in TEAMDATA, you must have VAX Xway Version 1.1
                  installed on your system.

                  1.5.4  TEAMDATA and VIDA

                  If you want to use TEAMDATA to access information stored in
                  IBM databases, you must have VIDA with IDMS/R Version 2.0 or
                  VIDA for DB2 Version 1.0 installed on your system.

               1.6  Registering Your License

                  You must register and load your TEAMDATA Software License.
                  The information you need is in the Product Authorization
                  Key (PAK) shipped with the product. The PAK is a paper
                  certificate that contains data about your license.

                  You must register the license before you install TEAMDATA.
                  TEAMDATA asks you early in the installation procedure if
                  you have an authorization key registered and loaded. You
                  can install TEAMDATA Version 1.4 without the authorization
                  information, but you will not be able to run TEAMDATA or the
                  IVP (Installation Verification Procedure) until you register
                  and load the license.

             Note If you are reinstalling TEAMDATA, do not reregister the
                  Software License.

                  To register the license for initial installation, first log
                  in to a privileged account such as the system manager's
                  account, SYSTEM. Then use the License Management Facility
                  to perform the registration, choosing one of the following
                  procedures (the second method is faster for experienced
                  users):

                                                Preparing for Installation  1-5










                   _ Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When
                     prompted for information, respond with data from your
                     Product Authorization Key (PAK).

                   _ Issue the DCL command LICENSE REGISTER with the appro-
                     priate qualifiers that correspond to information on the
                     PAK.

                  If you plan to use TEAMDATA on more than one node in a
                  VAXcluster, you must perform a LICENSE LOAD on the other
                  nodes after you complete this installation.

                  For complete information on using the License Management
                  Facility, see your VMS documentation set.

               1.7  VAXcluster Considerations

                  You can install TEAMDATA on a VAXcluster.

                  In a common-environment VAXcluster, you can install TEAMDATA
                  on the VAXcluster boot node. This allows more than one VAX
                  processor to share the same TEAMDATA software.

                  In a multiple-system VAXcluster, you can install TEAMDATA on
                  each system disk in the cluster.

                  You must check the number of global sections and global pages
                  on each node in the VAXcluster where you plan to install
                  TEAMDATA. See Section 1.8.4 for more information.

                  After you install TEAMDATA, you must run the TEAMDATA startup
                  command procedure (SYS$STARTUP:TDA$STARTUP.COM) on every
                  cluster node where you want to run TEAMDATA. See Section 3.3
                  for details.

               1.8  Preparing Your System and the Installing Account

                  This section tells you which characteristics of your system
                  and installing account you need to check before you install
                  TEAMDATA. These characteristics include:

                   _ Account privileges

                   _ Account quotas

                   _ Disk space requirements

                   _ System parameters

                  You must adjust those characteristics of your system and
                  account that do not match the minimum values required for
                  installing and running TEAMDATA.

               1-6  Preparing for Installation

 









                  1.8.1  Checking Privileges of the Installing Account

                  The account you use to install TEAMDATA must have the user
                  privilege SETPRV. As one of the first actions, the VMSINSTAL
                  command procedure grants all privileges (except BYPASS) to
                  the process that invokes it. This command succeeds only if
                  the account has SETPRV.

                  On most systems, the SYSTEM account has SETPRV and is used
                  to install software. The procedures described in this
                  installation guide refer to the SYSTEM account, but they
                  are the same for any account with SETPRV.

                  Before you start the VMSINSTAL command procedure, however,
                  you might need to prepare your system for the installation.
                  For example, you might have to run SYSGEN or AUTHORIZE. Some
                  of these preparations require that your account have specific
                  user privileges, which might not be among default privileges
                  assigned to your account.

                  Table 1-1 shows you what privileges you need for various
                  installation tasks.

                  Table 1-1    Required Installer Privileges

                  Name      Privilege Granted
                  _____________________________________________________________
                  CMKRNL    Change mode to kernel

                  EXQUOTA   Allow disk space to exceed established quotas

                  NETMBX    Allow user to perform network-related functions

                  OPER      Perform operator functions

                  SETPRV    Enable any privilege

                  SYSNAM    Insert system logical names in the name table

                  SYSPRV    Access resources as if process has a system UIC

                  TMPMBX    Create temporary mailbox

                  WORLD     Allow access to other processes
                  _____________________________________________________________

                  To check the privileges of the installing account, use the
                  SHOW PROCESS/PRIVILEGES command. If the SYSTEM account does

                                                Preparing for Installation  1-7

 











                  not have the privileges listed in Table 1-1, use AUTHORIZE
                  to grant them permanently or use the SET PROCESS/PRIVILEGES
                  command to grant them for this installation.

                  1.8.2  Checking and Setting User Process Quotas

                  In order to run TEAMDATA and the TEAMDATA Installation
                  Verification Procedure (IVP), your process quotas must be
                  equal to or greater than the values shown in Table 1-2.

                  Table 1-2    Required User Process Quotas

                  Process            Recommended  Controlling  Defining
                  Quotas             Minimum      Qualifier    Utility
                  _____________________________________________________________
                  Buffered I/O byte  20,480       BYTLM        AUTHORIZE
                  count quota

                  Enqueue quota      600          ENQLM        AUTHORIZE

                  Open file quota    60           FILLM        AUTHORIZE

                  Maximum number     2[1]         MAXDETACH    AUTHORIZE
                  of detached
                  processes

                  Maximum number of  3[1]         MAXJOBS      AUTHORIZE
                  jobs

                  Subprocess quota   1            PRCLM        AUTHORIZE

                  Working set        1024         WSEXTENT     AUTHORIZE
                  /Extent

                  Working set/Quota  512          WSQUOTA      AUTHORIZE

                  Page file quota    20,000       PGFLQUO      AUTHORIZE
                  _____________________________________________________________
                  [1]A value of zero for these parameters indicates no limit
                  _____________________________________________________________

                  These are minimum values. In some cases, you might need
                  higher quotas. For example:

                   _ If many users on your system are doing many database
                     operations at the same time, you might need to increase
                     the ENQLM parameter.

               1-8  Preparing for Installation

 











                   _ If you plan to run TEAMDATA from ALL-IN-1, you might want
                     to increase these quotas, especially BYTLM and PRCLM.

                   _ If users are working with large tables or sheets, TEAMDATA
                     may use more virtual memory than usual. You might want to
                     increase the Page File Quota (PGFLQUO) in AUTHORIZE to a
                     value greater than 20,000.

                  Note the MAXDETACH and MAXJOBS quotas. These parameters limit
                  the number of TEAMDATA entries a user can have open at one
                  time. A value of 0 for these parameters indicates that there
                  is no limit on the number of entries a user can have open.

                  If one or more of your quotas do not match or exceed the
                  required quotas, note the quotas you must change, and plan
                  to make the changes before you run TEAMDATA. To change these
                  quotas, you or your system manager must use the AUTHORIZE
                  utility. If you change any process quotas, you must log out
                  of the account and log in again so that the new values become
                  active.

                  1.8.3  Disk Space Requirements

                  Your system must have sufficient disk storage space to
                  accommodate the installation. Table 1-3 lists the required
                  free disk blocks.

                  You can reduce the disk allocation required to install and
                  run TEAMDATA by installing the TEAMDATA directory on a disk
                  other than your system disk.

                  Table 1-3    Disk Requirements

                                             Blocks on
                                             System Disk  Blocks on
                                             (To          System Disk
                  Installation Option        Install)     (To Run)
                  _____________________________________________________________
                  TEAMDATA entirely on       13,700       12,900
                  system disk

                  TEAMDATA directory on      13,700       8,300
                  another disk
                  _____________________________________________________________

                  Use the DCL command SHOW DEVICE to determine the number of
                  free blocks that are presently available on the target disk.

                                                Preparing for Installation  1-9

 











                  For example, to display the number of free blocks on the
                  system disk, type:

                    $ SHOW DEVICE SYS$SYSDEVICE

                  If the disk does not have enough free blocks, delete
                  unnecessary files to provide space.

                  1.8.4  Checking and Setting System Parameters

                  Before you install TEAMDATA, you should compare the values
                  of the system parameters listed in Table 1-4 with the values
                  on your system. The installation procedure checks all system
                  parameters and stops if any one parameter does not meet the
                  values listed in Table 1-4. You can avoid the halting of
                  the installation at that point by checking the parameters
                  beforehand. Instructions for making the comparison and
                  changing parameters follow the table.

                  If the parameter is labeled Dynamic, you can make a change in
                  the parameter effective without rebooting the system.



























               1-10  Preparing for Installation

 











                  Table 1-4    Required System Parameters

                                   Required
                  Parameter Name   Minimum   Unit      Type
                  _____________________________________________________________
                  CLISYMTBL        500[2]    Pages     Dynamic

                  GBLPAGES         5800[1]   Pages

                  GBLPAGFIL        2048      Pages

                  GBLSECTIONS      53[1]     Sections

                  LOCKIDTBL        256       Entries

                  LOCKIDTBL_MAX    2048      Entries   Dynamic

                  MAXBUF           1584      Bytes     Dynamic

                  RESHASHTBL       512       Entries

                  SRPCOUNT         1024      Packets

                  SRPCOUNTV        2048      Packets

                  VIRTUALPAGECNT   19,000    Pages
                  _____________________________________________________________
                  [1]In addition to the current value.
                  [2]Required only for installation.
                  _____________________________________________________________

                  Note that the CLISYMTBL value of 500 is required only for
                  the installation and not as a permanent change. To set this
                  parameter to the proper value for installation, use the
                  SYSGEN Utility as follows:

                    $ RUN SYS$SYSTEM:SYSGEN
                    SYSGEN > SET CLISYMTBL 500
                    SYSGEN > WRITE ACTIVE
                    SYSGEN > EXIT

                  After setting the CLISYMTBL parameter, log out and log back
                  in again.




                                               Preparing for Installation  1-11

 









                  To check the parameters listed in Table 1-4, except for
                  GBLSECTIONS and GBLPAGES, log in to the SYSTEM account, and
                  compare them with the output of the SYSGEN utility's SHOW
                  command.

                  The first number on the left is the current parameter value.

                  For example:

                    $ RUN SYS$SYSTEM:SYSGEN
                     SYSGEN> USE CURRENT
                     SYSGEN> SHOW LOCKIDTBL

Parameter Name          Current   Default   Minimum   Maximum Unit  Dynamic
--------------          -------   -------   -------   ------- ----  -------
LOCKIDTBL                  4096       128        16     16000 Entries

                     SYSGEN> EXIT
                     $

                  The procedure for checking global sections and global pages
                  is somewhat different. To calculate the number of unused
                  global pages and global sections on your system, perform
                  these steps:

                   1 Use the DCL F$GETSYI lexical function to determine the
                     number of free global pages and global sections:

                       $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")
                       $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")

                   2 If the number of unused global pages or global sections
                     is less than the number specified in Table 1-4, you must
                     increase the value using the AUTOGEN command procedure.
                     See the following section for details.

                  See Section 4.2 for more information on the global sections
                  and global pages parameters.

                  1.8.5  Changing System Parameters

                  If you must change these or any other system parameters, plan
                  to change them before you begin the installation procedure.
                  To modify these values, edit SYS$SYSTEM:MODPARAMS.DAT, the
                  parameter data file used by AUTOGEN. For example, to provide
                  additional global sections and set the LOCKIDTBL to 256,
                  edit MODPARAMS.DAT and add the following lines, or change the
                  existing lines as follows:


               1-12  Preparing for Installation

 











                    ADD_GBLSECTIONS=53

                    MIN_LOCKIDTBL=256

                  Because these system parameters are not dynamic, you must run
                  AUTOGEN to recompute them. If you wish, you can reboot, or
                  you can use AUTOGEN to activate the new parameters for the
                  installation without bringing your system down. Use one of
                  the following two procedures:

                  Procedure 1:

                  The following command sequence shuts down the system and
                  reboots, activating the new system parameters:

                    $ @SYS$UPDATE:AUTOGEN SAVPARAMS GENPARAMS
                    $ @SYS$UPDATE:AUTOGEN SETPARAMS REBOOT

                  Procedure 2:

                  To set the system parameters for the installation without
                  shutting down and rebooting the system, enter the following
                  commands:

                    $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS

                  Note that you can continue with the installation. However,
                  TEAMDATA will not run properly until after you reboot the
                  system.

                  If you choose this method, you can reboot the system later,
                  using this command:

                    $ @SYS$UPDATE:AUTOGEN REBOOT

               1.9  Performance Considerations

                  The major factors to consider when supporting many TEAMDATA
                  users are physical memory size and system parameter settings.
                  Each TEAMDATA user requires approximately 3/4 megabyte of
                  memory, based on two servers per active user. Therefore,
                  it is important that enough free memory is available on the
                  system.

                  Several system parameters can affect TEAMDATA performance.
                  This section describes parameters that you can modify to
                  improve performance. The following sections discuss these
                  performance topics:

                   _ Memory management

                                               Preparing for Installation  1-13

 











                   _ Paging and swapping files

                   _ System parameters

             Note The quotas suggested in this section are minimum values.
                  If you frequently perform operations such as accessing large
                  tables, joining large tables, or importing and exporting
                  large amounts of data, larger quotas might be necessary to
                  enhance performance.

                  For additional information on VMS performance, see the Guide
                  to VMS Performance Management.

                  For information on the parameters and quotas required to
                  run VAX Rdb/VMS and for information on tuning your Rdb
                  /VMS database system, see the VAX Rdb/VMS Installation
                  Guide and the VAX Rdb/VMS Guide to Database Maintenance and
                  Performance.

                  1.9.1  Memory Management

                  TEAMDATA requires large user working sets to run optimally.
                  As a result, you should set the following process account
                  parameters to the indicated values:

                   _ WSDEFAULT=256

                   _ WSQUOTA=512

                   _ WSEXTENT=1024 to 4096

                  Note that the SYSGEN parameter WSMAX must at least equal
                  the largest value of any user's WSEXTENT account parameter.
                  Specify a large value for WSEXTENT to minimize paging on the
                  system.

                  1.9.2  Paging and Swapping Files

                  Each TEAMDATA user requires approximately 6000 pages of
                  paging file space. As a result, you may need to increase the
                  size of your system's paging files. If the page file is too
                  small, page file fragmentation can occur. This significantly
                  degrades system performance.

                  To obtain an initial size for the system swap file, multiply
                  the maximum number of all concurrent users by their average
                  WSQUOTA value.

               1-14  Preparing for Installation

 







                  If several TEAMDATA users are active on the system at the
                  same time, you might want to set up multiple paging and
                  swapping files, distributed across multiple disks. Base this
                  decision on normal VMS performance considerations such as I/O
                  activity and disk space availability.

                  1.9.3  System Parameters

                  Table 1-4 lists the minimum system parameter values required
                  to install TEAMDATA. These values are satisfactory for
                  a small number of active users. However, if there are
                  many concurrent TEAMDATA users and many Rdb/VMS users,
                  you may need to adjust some system parameters to obtain
                  better performance. The recommended values for these system
                  parameters are listed here. You can adjust these parameters
                  independently by using the SYSGEN facility, or by using the
                  feedback mechanism of AUTOGEN.COM:

                   _ LOCKIDTBL - Determines the total number of resources that
                     can be locked on the system at one time.

                     Suggested setting: 2048

                   _ RESHASHTBL - Defines the number of entries in the lock

                     management resource name hash table. This value should be
                     set to one-fourth the value of LOCKIDTBL, rounded up to
                     the closest power of 2.

                     Suggested setting: 512

                   _ SRPCOUNT, SRPCOUNTV - These parameters control the number

                     of small request packets. You should monitor the use of
                     SRPs on the system using the DCL command SHOW MEMORY. If
                     the size of the Small Packet (SRP) List "In Use" value is
                     greater than the "Total" value, then you should set the
                     value of SRPCOUNT to the greater value. This eliminates
                     some process resource waits and decreases response time.

                     SRPCOUNTV should be set to LOCKIDTBL plus the previous
                     value of SRPCOUNTV. The number of SRPs on the system can
                     grow to the value of SRPCOUNTV.

                     Suggested settings: SRPCOUNTV = 4096, SRPCOUNT = 2048.

                   _ IRPCOUNT, IRPCOUNTV - These parameters control the number

                     of I/O request packets. You should use the DCL command
                     SHOW MEMORY to monitor the use of IRPs on the system.
                     If the size of the I/O Request Packet (IRP) List "In
                     Use" value is greater than the "Total" value, then you
                     should set the value of IRPCOUNT to the greater value.

                                               Preparing for Installation  1-15

 











                     This eliminates some process resource waits and decreases
                     response time.

                     The number of IRPs on the system can grow to the value of
                     IRPCOUNTV.

                     Suggested settings: IRPCOUNTV = 1000, IRPCOUNT = 256.

                   _ NPAGEDYN, NPAGEVIR - NPAGEDYN sets the size of the

                     nonpaged dynamic pool in bytes. This pool can grow
                     dynamically to the limit set by NPAGEVIR. You should
                     use the DCL command SHOW MEMORY to monitor the size of
                     nonpaged pool on the system. If the size of the Nonpaged
                     Dynamic Memory "Total" value is greater than the value of
                     NPAGEDYN, then you should set the value of NPAGEDYN to the
                     greater value. This eliminates some process resource waits
                     and decreases response time.

                     The size of nonpaged dynamic pool can grow to the value of
                     NPAGEVIR.

               1.10  Backing Up Your System Disk

                  At the beginning of the installation, VMSINSTAL asks if you
                  have backed up your system disk. Digital recommends that
                  you do a system disk backup before installing any software.
                  If a system failure occurs at a critical point during
                  the installation, some of the files could be corrupted.
                  Therefore, you should back up your system disk before
                  attempting any software installation.

                  For more information on backing up your system disk, see the
                  section on the Backup Utility in the VMS System Management
                  Subkit documentation.













               1-16  Preparing for Installation

 

















                                                                              2
               ________________________________________________________________

                                                            Installing TEAMDATA




                  This chapter describes the procedure for installing VAX
                  TEAMDATA and running the Installation Verification Procedure
                  (IVP).

                  Before you begin installing TEAMDATA, make sure that your
                  system meets the requirements outlined in Chapter 1.

                  You should allow approximately 50 minutes to complete the
                  installation. The actual time required depends on the
                  configuration of your system, the choices you make during
                  the installation, and the type of media you use.

                  This installation uses the VMSINSTAL command procedure. For
                  more information about VMSINSTAL, refer to the following
                  books in your VMS documentation set:

                   _ VMS System Manager's Manual, in the VMS base documentation
                     set

                   _ Guide to Setting Up a VMS System, in the VMS system
                     management kit.

             Note If you already have another version of TEAMDATA installed
                  on your system, and you want to change the location
                  of TEAM$LIBRARY, make the change before you begin the
                  installation. See Section 3.1 for instructions.






                                                       Installing TEAMDATA  2-1











               2.1  Running the VMSINSTAL Command Procedure

                  Use the VMSINSTAL command procedure to install TEAMDATA.
                  Follow these steps to begin the installation:

                 1   Log in to the SYSTEM account.

                     Log in at the operator's console terminal under the system
                     manager's account, SYSTEM.

                 2   Notify the users.

                     Send a message requesting that all users log out. Use the
                     DCL REPLY command to inform users of the schedule for the
                     installation. Use the SET LOGINS command to prevent others
                     from logging in:

             $ REPLY/USER "Installation starting in 5 minutes. Please log out."
             $ SET LOGINS/INTERACTIVE=0

                 3   Check that the Rdb/VMS monitor is running.

                     If you are certain that the Rdb/VMS monitor is running,
                     proceed with the installation. If you are not certain,
                     enter the following command:

                       $ @SYS$MANAGER:RMONSTART

                     If the monitor is not running, this command starts it. If
                     the monitor is running, this command has no effect; the
                     monitor continues to run.

                 4   Invoke VMSINSTAL.

                     Enter the following command line to run VMSINSTAL.COM:

                       $ @SYS$UPDATE:VMSINSTAL TDA014 ddcu: OPTIONS N

                     where:

                      _ @SYS$UPDATE:VMSINSTAL invokes VMSINSTAL

                      _ TDA014 is the save set name for the TEAMDATA software

                      _ ddcu: is the device specification for the distribution
                        medium, for example, MUA0:.

                      _ OPTIONS N is an optional parameter that indicates you
                        want to see the release notes question. If you do not
                        include the OPTIONS N parameter, VMSINSTAL does not
                        ask you about the release notes. You should review the
                        release notes before proceeding with the installation

               2-2  Installing TEAMDATA











                        in case they contain important information about the
                        installation.

                     After you invoke VMSINSTAL, you see the following message:

                       VAX/VMS Software Product Installation Procedure V5.3

                       It is 05-JAN-1990 at 09:55.

                       Enter a question mark (?) at any time for help.

                 5   Answer the backup question.

                     The installation procedure asks if you have backed up your
                     system disk:

                 * Are you satisfied with the backup of your system disk [YES]?

                     If you have not backed up your system disk, you should
                     not continue with the installation until you do so. If you
                     need to back up the system disk, type NO. VMSINSTAL exits
                     and returns you to the DCL prompt. Back up your system
                     disk, and then start VMSINSTAL again.

                     If you have already backed up the system disk, press
                     RETURN to continue.

                 6   Mount the media.

                     You receive instructions to mount the distribution medium
                     on the device you specified when you invoked VMSINSTAL
                     (MUA0: in this example).

                       Please mount the first volume of the set on MUA0:.
                       * Are you ready?

                     Mount the distribution medium and enter YES to indicate
                     that you are ready to continue.

                     The following messages appear on your terminal:

                       %MOUNT-I-MOUNTED, TDA014          mounted on _MUA0:

                       The following products will be processed:

                         TDA V1.4

                               Beginning installation of TDA V1.4 at 10:00

                       %VMSINSTAL-I-RESTORE, Restoring product save set A...



                                                       Installing TEAMDATA  2-3

 






                 7   Print and read the Release Notes.

                     If you specified OPTIONS N when you invoked VMSINSTAL,
                     you are now asked to choose one of the four options for
                     reviewing the Release Notes.

                Note If your system is running VMS V5.0 or V5.1, this
                     question is slightly different. You can choose from five
                     additional options.

             Release notes included with this kit are always copied to SYS$HELP.

                       Additional Release Notes Options:

                               1.  Display release notes
                               2.  Print release notes
                               3.  Both 1 and 2
                               4.  None of the above

                       * Select option [2]:

                     You should review the Release Notes in case they contain
                     any information about changes in the installation
                     procedures. Selecting option 2 prints a copy of the
                     Release Notes.

                     If you choose to print the Release Notes, you are prompted
                     for a print queue:

                       * Queue name [SYS$PRINT]:

                     Press RETURN to print the Release Notes on SYS$PRINT, or
                     type a different queue name and press RETURN. You receive
                     a message similar to the following:

                     Job 810 (queue SYS$PRINT, entry 1295) started on SYS$PRINT

                     If you selected options 1 or 3, the Release Notes display.

                 8   Decide whether or not to continue.

                     The installation procedure now asks if you want to
                     continue:

                        * Do you want to continue the installation? [N]?

                   %VMSINSTAL-I-RELMOVED, The product's Release Notes have been
                    successfully moved to SYS$HELP.

                     Enter YES to continue. Otherwise, press RETURN. In
                     either case, the Release Notes are moved to the SYS$HELP
                     directory. The Release Notes are contained in the
                     following file: SYS$HELP:TDA$014.RELEASE_NOTES.

               2-4  Installing TEAMDATA

 











                     You then see the following message:

                 ***************************************************************
                 *                                                             *
                 *                   TEAMDATA version: V1.4                    *
                 *                                                             *
                 *                   Installation Procedure                    *
                 *                       on Node: MYNODE                       *
                 *                 on 05-JAN-1990 10:02:24.71                  *
                 *                                                             *
                 *     Copyright (c) 1990 by Digital Equipment Corporation     *
                 *                                                             *
                 ***************************************************************

                 9   Answer the license registration question.

                     The installation procedure asks if you have registered
                     a TEAMDATA product authorization key, using the License
                     Management Facility (LMF).

                               Product:      TEAMDATA
                               Producer:     DEC
                               Version:      V1.4
                               Release Date: 26-APR-1990

           * Does this product have an authorization key registered and loaded?

                     Answer YES if your PAK is registered and loaded. The
                     installation then proceeds in the usual manner. If you
                     answer NO, you then respond to the following prompt:

                        * Do you want to continue with the installation [YES]?

                     If you answer YES, you see the following message:

             *******************************************************************
             *                                                                 *
             *  The installation can proceed, but you will not be able to run  *
             *  TEAMDATA or the IVP (Installation Verification Procedure)      *
             *  until the authorization key is registered and loaded.          *
             *                                                                 *
             *******************************************************************

                     If you answer NO to this question, the installation halts.
                     Refer to Section 1.6 for information about registering
                     your product authorization key.



                                                       Installing TEAMDATA  2-5

 






                10   Check any system requirements error messages.

                     The installation procedure displays the following message:

           *********************************************************************
           *                                                                   *
           *  Please wait while the system environment is checked out.         *
           *                                                                   *
           *********************************************************************

                     The installation procedure checks several system
                     characteristics, including:

                      _ The number of blocks available on your system disk

                      _ The VAX/VMS version your system is running

                      _ The current value of process quotas

                      _ The current value of system parameters

                     If any system characteristic does not meet the minimum
                     required value, the installation displays an error message
                     and may ask if you want to continue with the installation.

                     For example:

        ***********************************************************************
        *                                                                     *
        *                        Warnings and Errors                          *
        *                        -------------------                          *
        *                                                                     *
        *                                                                     *
        * [SYSGEN parameter] LOCKIDTBL_MAX is 1361 ... required minimum: 2048 *
        *                                                                     *
        *                                                                     *
        *   In order for the installation to succeed, you need to correct     *
        *   what's listed above.                                              *
        *                                                                     *
        ***********************************************************************

                     Depending on the type of error, you should correct
                     a problem either before continuing the installation
                     procedure or before running TEAMDATA or the IVP.

                     For example:

        *********************************************************************
        *                                                                   *
        *  The installation can proceed, but you will not be able to run    *
        *  TEAMDATA or the IVP (Installation Verification Procedure).       *
        *                                                                   *
        *********************************************************************

               2-6  Installing TEAMDATA

 











                       * Do you want to continue with the installation? [YES]?

                     If you answer NO, you can fix the problem and begin again
                     at Step 4.

                11   Choose the location of TEAM$LIBRARY.

                     You see this message:

        **********************************************************************
        *                                                                    *
        *   TEAMDATA creates a directory to put product specific files in.   *
        *      The logical TEAM$LIBRARY will point to this directory.        *
        *      These files amount to about 4600 disk blocks.                 *
        *      The default is recommended.                                   *
        *                                                                    *
        **********************************************************************

           * Where should the TEAMDATA directory go [SYS$COMMON:[TEAMDATA]]:

                  Note If you are upgrading from a previous version of
                     TEAMDATA, you see this additional message:

         *      This directory already exists in: SYS$COMMON:[TEAMDATA]       *

                By default, TEAMDATA creates a directory SYS$COMMON:[TEAMDATA]
                     with the logical name TEAM$LIBRARY on your system disk.
                     TEAM$LIBRARY contains files necessary to run TEAMDATA.

                     If system disk space is low, you have the option of
                     placing this library on another disk. If you decide
                     to place TEAM$LIBRARY elsewhere, you must modify your
                     SYSTARTUP_V5.COM file. See Section 3.1 for instructions.

                     Press RETURN to create the default library, or enter
                     another directory. You see the following message:

                %VMSINSTAL-I-SYSDIR, This product creates system disk directory
                       SYS$COMMON:[TEAMDATA].

                12   Replace or keep TDADEFDB.

                     The TDADEFDB TEAMDATA database contains the sample
                     database that is copied to user's folders when they
                     first run TEAMDATA. If you already have another version
                     of TEAMDATA installed on your system, the following
                     information applies. If you are installing TEAMDATA for
                     the first time, the following information does not apply,
                     and you do not see the message shown below.

                                                       Installing TEAMDATA  2-7

 










               ****************************************************************
               *                                                              *
               *   TEAMDATA has a "default" database.                         *
               *   This is copied to new user's accounts when they first use  *
               *   TEAMDATA.                                                  *
               *                                                              *
               *   This database is installed in TEAM$LIBRARY.                *
               *                                                              *
               ****************************************************************

                       Your system has a default user database:
                       SYS$COMMON:[TEAMDATA]TDADEFDB.RDB;1

                       * Do you want to replace it [No]?

                     If you have modified TDADEFDB, you may want to keep using
                     your version of TDADEFDB, instead of installing the new
                     version. However, you will not be working with the latest
                     version of the default database.

                     If you have not modified TDADEFDB, you should install the
                     new database by entering YES.

                13   Decide whether on not to purge files.

                     VMSINSTAL asks whether you want to purge (delete) old
                     versions of files replaced by this installation:

              * Do you want to purge files replaced by this installation [YES]?

                     Purging is recommended. Press RETURN to purge the old
                     files. However, if you need to keep files from the
                     previous version, enter NO.

                14   Decide whether or not to run the IVP.

                     The installation procedure asks whether you want to run
                     the Installation Verification Procedure (IVP):

                     * Do you want to run the IVP after the installation [YES]?

                     The TEAMDATA IVP checks to be sure the installation is
                     successful. Digital recommends that you run the IVP. Press
                     RETURN.

                15   Check informational messages.

                     The installation procedure displays a message that reminds
                     you to edit the SYSTARTUP_V5.COM file to add a command
                     that invokes TDA$STARTUP.COM:

               2-8  Installing TEAMDATA

 











           *********************************************************************
           *                                                                   *
           *   SYSTEM MANAGER:                                                 *
           *                                                                   *
           *   Add to the system startup file: SYS$MANAGER:SYSTARTUP_V5.COM:   *
           *                                                                   *
           *           $ @SYS$STARTUP:TDA$STARTUP.COM                          *
           *                                                                   *
           *   (For clusters, add this to the startup for each node)           *
           *                                                                   *
           *********************************************************************
 
                     You must edit SYSTARTUP_V5.COM on all nodes that run
                     TEAMDATA. If you do not do this, TEAMDATA will not be
                     available when the system is rebooted.

                16   Check file transfer messages.

                     The installation procedure displays a series of informa-
                     tional messages as it creates directories, transfers files
                     and installs databases.

           *********************************************************************
           *                                                                   *
           *  You've answered ALL the questions for the installation.          *
           *                                                                   *
           *  The installation takes about 30 to 45 more minutes to complete.  *
           *                                                                   *
           *********************************************************************

                       %VMSINSTAL-I-RESTORE, Restoring product save set B...
                       %VMSINSTAL-I-RESTORE, Restoring product save set C...
                       %VMSINSTAL-I-RESTORE, Restoring product save set D...
                       %VMSINSTAL-I-RESTORE, Restoring product save set E...

           *********************************************************************
           *                                                                   *
           *   Installing Sample Database...                                   *
           *                                                                   *
           *********************************************************************
           *                                                                   *
           *   Installing Default User Database...                             *
           *                                                                   *
           *********************************************************************
           *                                                                   *
           *   Installing Public Folder Database...                            *
           *                                                                   *
           *********************************************************************


                                                       Installing TEAMDATA  2-9

 








                %VMSINSTAL-I-SYSDIR, This product creates system disk directory
                  VMI$ROOT:[SYSTEST.TDA$IVP].
                %VMSINSTAL-I-MOVEFILES, Files will now be moved to their 
                  target directories...
                       VAX TEAMDATA: Installing TEAMDATA images
                       VAX TEAMDATA: Starting System Interconnect

                     If the installation fails and displays the following error
                     message, you need to raise the number of pages defined by
                     the system parameter CLISYMTBL:

            %DCL-W-SYMOVF, no room for symbol definitions - delete some symbols

                     Use SYSGEN to change this parameter and restart the
                     installation at step 4. See Section 1.8.2 for more
                     information about the CLISYMTBL parameter.

                17   Run the TEAMDATA IVP.

                     The installation procedure runs the TEAMDATA Installation
                     Verification Procedure.

                       **** Executing IVP for: VAX TEAMDATA V1.4

                               **** Running Folder Test

                               **** Folder Test Succeeded

                               **** Running Table Test

                               **** Table Test Succeeded

                               **** Running Spreadsheet Test

                               **** Spreadsheet Test Succeeded

                               ********************************

                               VAX TEAMDATA V1.4

                               IVP COMPLETED SUCCESSFULLY

                               ********************************

                       **** IVP completed for: VAX TEAMDATA V1.4

                18   End the installation procedure.

                     The installation procedure ends automatically with the
                     following message:

                               Installation of TDA V1.4 completed at 10:50

                               VMSINSTAL procedure done at 10:51

               2-10  Installing TEAMDATA

 











                     At the end of the installation, VMSINSTAL returns you to
                     DCL command level.

                19   Make the system available to users.

                     After the installation completes successfully, you should
                     reset system logins to your system default (64 in this
                     example). Then send a message to all users stating that
                     the system is again available. Use the following DCL
                     commands:

                  $ SET LOGINS/INTERACTIVE=64
                  $ REPLY/USER "Installation complete. System is ready for use."



































                                                      Installing TEAMDATA  2-11

 

















                                                                              3
               ________________________________________________________________

                                                   Post-Installation Procedures




                  This chapter describes the tasks you must complete after
                  TEAMDATA is installed. These tasks are:

                   _ Deciding where to put TEAM$LIBRARY

                   _ Editing the SYSTARTUP_V5.COM file

                   _ Activating TEAMDATA on a VAXcluster

                   _ Running TEAMDATA

                   _ Granting required user privileges to TEAMDATA users

                   _ Granting required quotas to TEAMDATA users

                   _ Setting the limit on Run Unit Journal files

                   _ Granting users on other systems access to your TEAMDATA
                     databases

                   _ Shutting down TEAMDATA

               3.1  Moving TEAM$LIBRARY

                  If you want to save space on your system disk, you can
                  move the TEAMDATA directory to another disk. The TEAMDATA
                  directory is defined by the logical name TEAM$LIBRARY.

                  For example, assume you have a logical named USER$DISK that
                  points to a disk other than the system disk. To move the
                  TEAMDATA directory to USER$DISK, use these commands:


                                              Post-Installation Procedures  3-1

 











               $ CREATE/DIRECTORY USER$DISK:[BIZ_PRODS.TEAMDATA]
               $ COPY/LOG TEAM$LIBRARY:*.*;* USER$DISK:[BIZ_PRODS.TEAMDATA]*.*;*
               $ DELETE TEAM$LIBRARY:*.*;*
               $ DEFINE/SYSTEM/EXEC TEAM$LIBRARY USER$DISK:[BIZ_PRODS.TEAMDATA]
               $ DELETE SYS$COMMON:[000000]TEAMDATA.DIR


               3.2  Editing SYSTARTUP_V5.COM

                  To have VAX TEAMDATA V1.4 started automatically when your
                  system is booted, edit the site-specific startup file,
                  SYS$MANAGER:SYSTARTUP_V5.COM.

                  Add the following line to the file:

                    $ @SYS$STARTUP:TDA$STARTUP

                  If you redefined TEAM$LIBRARY to refer to a disk other than
                  the system disk, you must add the definition to SYSTARTUP_
                  V5.COM.

                  For example, if you redefined the TEAM$LIBRARY logical so
                  that TEAM$LIBRARY resides on USER$DISK:[BIZ_PRODS.TEAMDATA],
                  add the following lines in the order they appear to
                  SYSTARTUP_V5.COM:

               $ @SYS$STARTUP:TDA$STARTUP
               $ DEFINE/SYSTEM/EXEC TEAM$LIBRARY USER$DISK:[BIZ_PRODS.TEAMDATA]

                  Because TDA$STARTUP.COM, defines TEAM$LIBRARY to be
                  SYS$COMMON:[TEAMDATA], this command must follow the command
                  that starts TEAMDATA when you edit the site-specific startup
                  file.

               3.3  Activating TEAMDATA on a VAXcluster

                  To run TEAMDATA on any type of VAXcluster, you must first
                  install TEAMDATA on each system disk that is commonly
                  shared among nodes in the cluster. Then you must perform
                  the following procedure to load the license, replace the DCL
                  tables, and run the startup procedure on all other nodes in
                  the cluster:






               3-2  Post-Installation Procedures

 











                    $  MCR SYSMAN
                    SYSMAN>  SET ENVIRONMENT/CLUSTER/USER=SYSTEM
                    Remote Password:  <system password for the cluster nodes>
                    SYSMAN>  DO LICENSE LOAD TEAMDATA
                    SYSMAN>  DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE
                    SYSMAN>  DO @SYS$STARTUP:TDA$STARTUP.COM
                    SYSMAN>  EXIT


               3.4  Running TEAMDATA

                  You do not need to reboot your system to run TEAMDATA.
                  However, any user who was logged in during the TEAMDATA
                  installation must first log out and then log in again before
                  running TEAMDATA.

                  To run TEAMDATA, type the following command at the DCL
                  prompt:

                    $ TEAMDATA

               3.5  Running the Installation Verification Procedure Separately

                  If you answered YES to the IVP question during the TEAMDATA
                  installation, the Installation Verification Procedure ran
                  automatically at the end of the installation. You received a
                  message indicating whether the IVP succeeded or failed.

                  You can also run the IVP separately. The account from which
                  you run the IVP must have the same privileges and account
                  quotas required to install TEAMDATA. See Section 1.8 for more
                  information.

                  To run the IVP, use the following DCL command:

                    $ @SYS$TEST:TDA$IVP

               3.6  DATATRIEVE Versions

                  The installation procedure warns you if you have DATATRIEVE
                  installed, but do not have a file called SYS$SHARE:DTRSHR.EXE.
                  Some systems have multiple versions of DATATRIEVE running at
                  the same time. On these systems, instead of DTRSHR.EXE, there
                  might be files such as DTRSHRV4.EXE. In this case, TEAMDATA
                  asks you which file you want to use as your DATATRIEVE
                  shareable image. It then defines a logical name DTRSHR,
                  pointing to the file you have chosen. To make this choice

                                              Post-Installation Procedures  3-3

 











                  permanent, you must place the following line in SYSTARTUP_
                  V5.COM:

                    $ DEFINE/SYSTEM/EXEC DTRSHR SYS$SHARE:DTRSHRV4.EXE

                  If you change SYSTARTUP_V5.COM to include this line, TEAMDATA
                  uses DTRSHRV4.EXE when TEAMDATA users work with DATATRIEVE
                  domains.

               3.7  Granting Required User Privileges

                  TEAMDATA uses temporary mailboxes to communicate with
                  users. You must therefore grant TMPMBX privilege to all
                  TEAMDATA users. In addition, those who use TEAMDATA to access
                  databases on other nodes of a network need NETMBX privilege.
                  Use AUTHORIZE, the user authorization utility, to grant these
                  privileges.

                  For example:

                    $ SET DEFAULT SYS$SYSTEM
                    $ RUN AUTHORIZE
                    UAF> MODIFY WILLIAMSON/PRIV=(TMPMBX,NETMBX)
                    UAF> EXIT
                    $

               3.8  Authorizing User Quotas

                  The process quotas listed in Table 1-2 apply to user accounts
                  as well as to the installation account. Therefore, make sure
                  all user accounts have these minimum quotas.

               3.9  Managing Run Unit Journal Files

                  Rdb/VMS creates a journal file for each folder, table or
                  sheet that a user opens. It is possible for Rdb/VMS to create
                  and maintain more than one journal file simultaneously.

                  These files are placed in the user's SYS$LOGIN directory and
                  have the file name TEAMDB.RUJ. The number of versions of a
                  file that a user may have in a directory can be limited. If
                  the user has several TEAMDATA entries open simultaneously,
                  this limit might be exceeded. As a result, the user will
                  not be able to open additional tables or sheets. You can
                  solve this problem by making sure that the user's SYS$LOGIN
                  directory has a high file version limit.


               3-4  Post-Installation Procedures

 











                  You can solve this problem in one of two ways:

                   _ Make sure that the user's SYS$LOGIN directory has a
                     version limit equal to twice the number of entries the
                     user is allowed to open. The number of entries that users
                     can open can be limited by the logical name TEAM$MAX_
                     SERVERS. If TEAM$MAX_SERVERS is defined, then the file
                     version limit should be set to at least twice the value
                     of TEAM$MAX_SERVERS. If TEAM$MAX_SERVERS is not defined,
                     the default value of three is used. In this case, you
                     should set the file version limit to at least six. For
                     more information on the TEAM$MAX_SERVERS logical, see
                     Using VAX TEAMDATA.

                     To change the version limit of a directory file, use the
                     SET FILE command, as in the following example:

                       $ SET FILE USER$DISK:[000000]USER.DIR/VERSION_LIMIT=6

                     Note that a version limit of zero means that there is no
                     limit on the number of files.

                   _ If you do not want to increase the file version limit
                     for the user's SYS$LOGIN directory, create a special
                     subdirectory for the user's RUJ files. Then, set the file
                     version limit on that directory and have the user define
                     a job logical that points to that directory, as in the
                     following example:

                       $ DEFINE/JOB RDMS$RUJ USER$DISK:[USER.RUJ]

               3.10  Granting Database Access to Users on Other Systems

                  If users on other systems are allowed to access databases
                  stored on your system, the account associated with RDBSERVER
                  must contain at least the minimum quotas recommended for
                  TEAMDATA user accounts. These quotas are listed in Table 1-2.

                  To find out which account is associated with RDBSERVER, enter
                  the following commands:

                    $ RUN SYS$SYSTEM:NCP
                    NCP> SHOW OBJECT RDBSERVER

                  NCP displays information about the account associated with
                  RDBSERVER. If NCP does not display the information, then
                  the DECnet account is the account used for remote access
                  requests. In this case, the DECnet account should have the
                  quotas listed in Table 1-2. Enter EXIT to leave NCP.

                                              Post-Installation Procedures  3-5

 











               3.11  TEAMDATA Shutdown Procedure

                  TEAMDATA provides a shutdown procedure, TDA$SHUTDOWN.COM.
                  The installation procedure copies this file to SYS$MANAGER.
                  You do not need to run TDA$SHUTDOWN.COM every time you shut
                  down your system, but you can run it manually to shut down
                  TEAMDATA. For example, you would want to run TDA$SHUTDOWN.COM
                  if you need to reinstall the TEAMDATA kit.








































               3-6  Post-Installation Procedures

 

















                                                                              4
               ________________________________________________________________

                                                           Maintaining TEAMDATA




                  This chapter explains some procedures you may need to follow
                  if problems arise after installing TEAMDATA. The following
                  sections explain how to:

                   _ Read a bugcheck dump file

                   _ Handle a problem of insufficient global pages

                   _ Report a problem to the Customer Support Center

                  For information on restoring the TEAMDATA sample database,
                  default database, and public folder database, see Appendix A
                  of Using VAX TEAMDATA.

               4.1  Reading a Bugcheck Dump File

                  Occasionally, a TEAMDATA fatal internal error generates
                  a file called a bugcheck dump file. This file contains
                  essential information about the error that occurred and
                  the state of the system at the time of the error. This
                  information becomes vital in tracking down the cause of the
                  error; it is also important to Digital in fixing possible
                  internal TEAMDATA problems. If such an error occurs, the
                  message reports that TEAMDATA is creating a file called:

                    TDABUGCHK.DMP

                  This file is normally created in the directory associated
                  with the SYS$LOGIN logical name.





                                                      Maintaining TEAMDATA  4-1

 











                  To find the error that caused the dump, use the following
                  command:

                    $ SEARCH/WIN TDABUGCHK.DMP "****"

                  Asterisks mark the location of the error message in the
                  file. The /WIN qualifier results in a five-line window. For
                  example:

                  $ SEARCH/WIN TDABUGCHK.DMP "****"
     2 7FF2548C: 00000003 03000001 00379120 00000000 0000000C 7FF25A90 00000004

                    ***** Exception at 0008618B : TUT$$SCR_W_COPY + 00000CCA
                    %NONAME-W-NOMSG, Message number 00000000

                  You can use this information in three ways:

                   _ Sometimes, this information can help you determine the
                     cause of the error and work around it.

                   _ You can use this information when you call the Customer
                     Support Center.

                   _ You should always include the entire bugcheck dump file
                     when you submit an SPR to Digital.

                     When reporting a problem to Digital, also include the
                     database file and a description of the sequence of steps
                     that caused the problem, if possible. This information
                     will help Digital identify the cause of the problem.

                  The error may have been generated by part of system
                  interconnect that is included in TEAMDATA. In this case,
                  the error line in the dump file begins:

                    %RPC-E-

                  In this case, more information is contained in the RPC log
                  file. To extract this information, follow these steps:

                    $ RUN SYS$SYSTEM:RPC$SWLUP
                    SWLUP> LIST EVENTS /SINCE=TODAY /OUTPUT=RPC.EVENTS
                    SWLUP> EXIT
                    $ SEARCH/WIN RPC.EVENTS "%"

                  The error line in the file is marked with the percent sign
                  (%).

               4-2  Maintaining TEAMDATA

 











                  Another file that contains helpful information is the
                  RDMMON.LOG file. This file contains information about
                  Rdb transactions, including user name, date, and time of
                  transaction. This file records both normal and abnormal
                  activity.

                  If a problem occurs, search this file for a message
                  indicating a problem, such as users exceeding their quotas.

               4.2  Insufficient Parameter Values

                  After you have successfully installed and run TEAMDATA for a
                  while, you might find that, when you run TEAMDATA, it returns
                  to the DCL command level without initializing or displaying
                  the Main Folder. Your display would look like this:

                    $ TEAMDATA
                    $

                  If this happens, check the SYS$LOGIN directory for a bugcheck
                  dump file called TDABUGCHK.DMP. Check the date to make sure
                  the file was just created. Search the dump file for the
                  error:

                  $ SEARCH/WINDOW TDABUGCHK.DMP "***"
      2 7FF2548C: 00000003 03000001 00379120 00000000 0000000C 7FF25A90 00000004

                    ***** Exception at 0008618B : ........
                    %RPC-E-INTERNAL, Internal error

                  If the results indicate an RPC error, use the RPC log to
                  pinpoint the exact cause of the error:

                    $ RUN SYS$SYSTEM:RPC$SWLUP
                    SWLUP> LIST EVENTS /SINCE=TODAY /OUTPUT=RPC.EVENTS
                    SWLUP> EXIT
                    $ SEARCH/WIN RPC.EVENTS "%"

                  The error message will typically indicate that TEAMDATA ran
                  out of global pages:

                    %SYSTEM-F-......, insufficient GBLPAGES

                  This indicates that subsequent software installations have
                  caused TEAMDATA to run out of global pages. To fix this
                  problem, use AUTOGEN to increase the value of GBLPAGES
                  as appropriate. The same problem can occur because of an
                  insufficient GBLSECTIONS or GBLPAGFIL parameter.

                                                      Maintaining TEAMDATA  4-3

 











             Note On a system that was rebooted recently and where 
                  TDA$STARTUP.COM was used, you should see at least 10 free 
                  GBLSECTIONS and 800 free GBLPAGES, if there are no users 
                  currently using TEAMDATA. If you have these quotas, and 
                  some users still cannot start TEAMDATA, increase the value 
                  of GBLPAGFIL by 500.


               4.3  Reporting Problems to Digital

                  Make sure you know your access number before you call the
                  Customer Support Center (CSC). Use the access number to
                  identify yourself when you call. Treat the access number
                  and the telephone numbers of the CSC confidentially. You
                  should designate CSC contact people in your organization, and
                  only these people should know the CSC access numbers.

                  The contact people you designate may speak directly with a
                  CSC team specialist. The CSC will call the contact people
                  directly to deliver a solution, request more information, or
                  confirm a solution previously delivered.

                  The CSC will be able to respond faster and more accurately
                  if you have complete information available when you call.
                  Preparing a statement of the problem and thinking through the
                  sequence of events that led to its occurrence can eliminate
                  the need for calls from the CSC to gather more information.
                  The specialist can focus immediately on isolating and
                  analyzing the problem, rather than on defining it.

                  The following list of questions helps you collect supporting
                  data that is often overlooked, but is essential to under-
                  standing a problem in its context. Try to write down an
                  answer to each question and have the list of answers ready
                  when you call the CSC.

                   1 What versions of the software are you running (VMS
                     operating system, prerequisite or optional software)?
                     Are these the most current versions available?

                   2 In what environment or under what conditions does the
                     problem occur (for example, interactive, network, loaded
                     or single user system)?

                   3 Have any changes occurred with the software or its usage
                     that might correlate with the incidence of the problem,
                     such as:

                      _ Installing new prerequisite or optional software

               4-4  Maintaining TEAMDATA

 











                      _ Upgrading existing software

                   4 Can you reproduce the problem with a short example? This
                     will help the CSC team specialist in reproducing the
                     problem.











































                                                      Maintaining TEAMDATA  4-5

 

















                                                                              5
               ________________________________________________________________

                                          Installing TEAMDATA in ALL-IN-1 Menus




                  This chapter describes how to install TEAMDATA in an ALL-IN-1
                  menu, including:

                   1 Copying the TEAMDATA command files to OA$LIB:

                   2 Linking TEAMDATA to the ALL-IN-1 menu

                   3 Recompiling and relinking the forms library

                  The rest of this chapter illustrates in detail one method of
                  incorporating TEAMDATA into an ALL-IN-1 submenu. This chapter
                  assumes that you want to include TEAMDATA in the Information
                  Management submenu for all the ALL-IN-1 users on your system.

             Note Because ALL-IN-1 provides many ways to customize your
                  installation, your own configuration may be different from
                  the one assumed here. If your installation is substantially
                  different, you may need to contact your Digital Software
                  Services representative for assistance.

               5.1  Copying the TEAMDATA Command Files

                  Follow these steps to copy the TEAMDATA command files:

                   1 Make sure that your process has the following privileges:

                       SYSPRV
                       PRMGBL
                       SYSGBL

                     Your process also needs sufficient privileges to write to
                     the ALL-IN-1 forms library, OA$LIB:OAFORM.FLB.


                                     Installing TEAMDATA in ALL-IN-1 Menus  5-1

 











                     During this installation, you must recompile the forms
                     library. To do this, you need approximately 2500 free
                     blocks on the disk containing OA$LIB. Check now to make
                     sure this space is available.

                   2 Copy the TEAMDATA command files to OA$LIB, and give
                     OA$LIB:TDAA1.COM WORLD:READ protection. Use the following
                     command to do so:

                   $ COPY/PROT=W:R TEAM$LIBRARY:TDAA1.COM,TDAWPSXAL.COM OA$LIB:*

                     Note that, in V1.0 of TEAMDATA, the ALL-IN-1 files were
                     stored in SYS$UPDATE:TDAA1.COM.

               5.2  Linking TEAMDATA to the ALL-IN-1 Menu

                  Follow these steps to link TEAMDATA to the ALL-IN-1 menu:

                   1 Run ALL-IN-1 from the ALL-IN-1 account on your system.

                   2 At the ALL-IN-1 Main Menu, enter:

                       FD

                     This choice indicates that you want to work on Forms
                     Development. Note that this choice does not appear on
                     the main menu.

                   3 At the Forms Development menu, enter:

                       SEL

                   4 Under Select Current Items, enter:

                       Library:  OA$LIB:OAFORM.FLB

                       Form:  IM

                     OAFORM.FLB is the forms library that contains forms for
                     submenus. IM indicates the Information Management submenu.

                   5 Enter E to edit the form description.

                   6 Under Edit a Form Description, enter S (Screen Image).

                   7 When the main screen for forms editing appears:

                      _ Choose LAYOUT. When you make this choice, ALL-IN-1 runs
                        the FMS forms editor to let you edit the screen display
                        of the form. Press HELP (PF2) for help.

               5-2  Installing TEAMDATA in ALL-IN-1 Menus

 











                      _ Add the following to the list of menu choices on this
                        menu:

                           TD   TEAMDATA

                      _ When you are finished, press Gold-Keypad 7 to return to
                        the main menu of the forms editor.

                   8 Enter DATA in the Phase Choice field.

                   9 Press TAB to move to the entry labeled NAME and enter:

                       TD

                  10 Press TAB to move to the next line and enter:

                       COMMAND OA$LIB:TDAA1.COM\CLEAR FORM

                     Be sure to use the backslash character (\). CLEAR FORM
                     displays the original form when TEAMDATA exits and returns
                     control to ALL-IN-1.

                  11 Press Gold-Keypad 7 to exit from the forms editor and
                     return to the menu.

                  12 Exit from the menu by entering EX.

                  13 Choose Y to save the form and exit. If you have suc-
                     cessfully modified the Information Management form
                     in OA$LIB:OAFORM.FLB, ALL-IN-1 displays the following
                     message:

                       FORM IM   updated in OA$LIB:OAFORM.FLB library

                     If you do not see this success message, the form has not
                     been modified. Check to make sure you have the required
                     privileges and repeat the previous steps.

                  14 After you have modified the forms library, press RETURN to
                     return to the Forms Development menu. At this time, you
                     will receive the following message:

                       Obsolete version of OAFORM.FLB - Continuing

                     Disregard this message. When you recompile the forms
                     library, the version will be updated and this message
                     will no longer appear.

                                     Installing TEAMDATA in ALL-IN-1 Menus  5-3

 









               5.3  Recompiling the Forms Library

                  Follow these steps to recompile the forms library:

                   1 To recompile the library, you need approximately 2500 free
                     blocks on the disk containing OA$LIB. Begin by entering:

                       PCF

                     This operation takes a few minutes. If you need more
                     information about it, see the ALL-IN-1 System Manager's
                     Guide.

                   2 Remove and reinstall the newly compiled forms library:

                       <OA$FBTREMOVELIBRARY OA$LIB:OAFORM
                       <OA$FBTINSTALLLIBRARY OA$LIB:OAFORM

                     The result is a compiled forms library, OA$LIB:OAFORM.FLC.

                   3 Exit from ALL-IN-1.

                   4 Make sure that this library has WORLD:READ protection:

                       $ DIRECTORY/PROTECTION OA$LIB:OAFORM.FLC

                       Directory DISK2$:[ALLIN1.LIBRARY]

                       OAFORM.FLC;19     (RWED,RE,RE,R)
                       OAFORM.FLC;18     (RWED,RE,RE,R)

                       Total of 2 files.

               5.4  Running TEAMDATA from the ALL-IN-1 Menu

                  Follow these steps to run TEAMDATA from the ALL-IN-1 menu:

                   1 Choose IM (or the choice under which you have installed
                     TEAMDATA) from the ALL-IN-1 menu.

                   2 Select TD to run TEAMDATA. You are now in the TEAMDATA
                     environment. The only differences between using TEAMDATA
                     through ALL-IN-1 and using TEAMDATA from DCL are:

                      _ You use Gold-I to take you to the ALL-IN-1 Interrupt
                        Menu instead of your current folder.

                      _ You can press either keypad 0 (KP0) or the EXIT
                        function key (F10) to return to TEAMDATA from ALL-IN-1.

                      _ You can use the A1_SCRATCH_PAD option to write reports
                        and graphs to the ALL-IN-1 Scratch Pad.

               5-4  Installing TEAMDATA in ALL-IN-1 Menus

 











                   3 Use the EXIT SYSTEM command to exit from TEAMDATA and
                     return to the ALL-IN-1 menu.

                   4 Enter EX to exit from ALL-IN-1.












































                                     Installing TEAMDATA in ALL-IN-1 Menus  5-5

 

















                                                                              A
               ________________________________________________________________

                                                                 TEAMDATA Files




                  Table A-1 lists the files that are transferred to your
                  system when you install TEAMDATA. The files are organized
                  by directory. Table A-1 lists the file name, a brief
                  description, and the approximate file size in blocks for
                  each file.



                  Table A-1    TEAMDATA Files

                  File                  Description             Size (Blocks)
                  _____________________________________________________________
                  In SYS$HELP:

                  RPC$SWLUP.HLB         System interconnect     18

                  TDA$014.RELEASE_      Release notes           117
                  NOTES

                  TDA$HELP.HLB          Main help library       1484

                  TDA$TRAIN.HLB         Training library        247

                  _____________________________________________________________
                  In SYS$STARTUP:

                  TDA$STARTUP.COM       Startup command file    7

                                                       (continued on next page)




                                                            TEAMDATA Files  A-1

 











                  Table A-1 (Cont.)    TEAMDATA Files

                  File                  Description             Size (Blocks)
                  _____________________________________________________________
                  In SYS$MANAGER:

                  RPC$STARTUP.COM       System interconnect     6

                  TDA$SHUTDOWN.COM      Shutdown command file   4

                  _____________________________________________________________
                  In SYS$MESSAGE:

                  RPC$MSG.EXE           System interconnect     31

                  RPC$SWLMSG.EXE        System interconnect     40

                  TDA$MSGSHR.EXE        Message shareable       104
                                        image

                  _____________________________________________________________
                  In SYS$SHARE:

                  RPC$SHR.EXE           System interconnect     255

                  TDA$GRFSHR.EXE        Graph shareable image   279

                  TDA$MENSHR.EXE        Menu definitions        570

                  TDA$PRVSHR.EXE        Terminal control        6

                  TDA$SHR.EXE           Main shareable image    480

                  TDA$SRVDTE.EXE        Table server            916

                  TDA$SRVFTE.EXE        Spreadsheet server      852

                  TDA$SRVRGA.EXE        RALLY server            287

                                                       (continued on next page)







               A-2  TEAMDATA Files

 











                  Table A-1 (Cont.)    TEAMDATA Files

                  File                  Description             Size (Blocks)
                  _____________________________________________________________
                  In SYS$SYSTEM:

                  RPC$SWLPROC.EXE       System interconnect     17

                  RPC$SWLUP.EXE         System interconnect     122

                  TEAMDATA.EXE          Main TEAMDATA image     1733

                  _____________________________________________________________
                  In SYS$TEST:

                  TDA$IVP.COM           Installation            8
                                        Verification Procedure

                  TDA$IVP.DIR           IVP files directory     1

                  _____________________________________________________________
                  In SYS$COMMON:[SYSTEST.TDA$IVP]:

                  TDA$IVP_FOLDER.TDA    IVP test file           1

                  TDA$IVP_PROFILE.DAT   IVP test file           1

                  TDA$IVP_SHEET.REP     IVP test file           2

                  TDA$IVP_SHEET.TDA     IVP test file           1

                  TDA$IVP_TABLE.REP     IVP test file           25

                  TDA$IVP_TABLE.TDA     IVP test file           1

                                                       (continued on next page)











                                                            TEAMDATA Files  A-3

 











                  Table A-1 (Cont.)    TEAMDATA Files

                  File                  Description             Size (Blocks)
                  _____________________________________________________________
                  In TEAM$LIBRARY:

                  TDAA1.COM             ALL-IN-1 control        6

                  TDACREDB.COM          Create new user         5
                                        database

                  TDADCL.COM            DCL subprocess control  10

                                                       (continued on next page)

































               A-4  TEAMDATA Files

 










                  Table A-1 (Cont.)    TEAMDATA Files

                  File                  Description             Size (Blocks)
                  _____________________________________________________________
                  In TEAM$LIBRARY:

                  TDADEFDB.RBR          Default database        30

                  TDADEFDB.RDB          Default database        1084

                  TDADEFDB.SNP          Default database        202

                  TDASAMPLE.RBR         Sample database         194

                  TDASAMPLE.RDB         Sample database         1528

                  TDASAMPLE.SNP         Sample database         202

                  TDASYSDB.RDB          Public folder database  1084

                  TDASYSDB.SNP          Public folder database  202

                  TDASYSDB_NEW.RBR      Public folder database  46
                                        (ori.)

                  TDATSKCTL.COM         DCL subprocess control  5

                  TDAWPSXAL.COM         WPS+ XAL control        13

                  TDA_CLUST.GRG         Graph control file      2

                  TDA_HISTO.GRG         Graph control file      2

                  TDA_LINE.GRG          Graph control file      2

                                                       (continued on next page)











                                                            TEAMDATA Files  A-5

 











                  Table A-1 (Cont.)    TEAMDATA Files

                  File                  Description             Size (Blocks)
                  _____________________________________________________________
                  In TEAM$LIBRARY:

                  TDA_PAL1.GRP          Graph pallette file     1

                  TDA_PAL10.GRP         Graph pallette file     1

                  TDA_PAL11.GRP         Graph pallette file     1

                  TDA_PAL12.GRP         Graph pallette file     1

                  TDA_PAL2.GRP          Graph pallette file     1

                  TDA_PAL3.GRP          Graph pallette file     1

                  TDA_PAL4.GRP          Graph pallette file     1

                  TDA_PAL5.GRP          Graph pallette file     1

                  TDA_PAL6.GRP          Graph pallette file     1

                  TDA_PAL7.GRP          Graph pallette file     1

                  TDA_PAL8.GRP          Graph pallette file     1

                  TDA_PAL9.GRP          Graph pallette file     1

                  TDA_PIE.GRG           Graph control file      2

                  TDA_SCAT.GRG          Graph control file      2

                  TDA_SHOW_PROC.TDA     Show procedures UDP     1

                  TDA_STACK.GRG         Graph control file      2
                  _____________________________________________________________









               A-6  TEAMDATA Files

 

















                                                                              B
               ________________________________________________________________

                                                   Sample TEAMDATA Installation




               This appendix shows a typical new installation of TEAMDATA on
               a VMS Version 5.3 system. If you are upgrading from a previous
               version of TEAMDATA, your own installation may differ slightly
               from this example. See Chapter 2 for information specific to
               upgrading TEAMDATA.


               Username:  SYSTEM<Return>
               Password:        <Return>

                       Welcome to VAX/VMS version V5.3 on node MYNODE

                   Last interactive login on Thursday,  04-JAN-1990 08:32
                   Last non-interactive login on Wednesday, 03-JAN-1990 12:32

     $  REPLY/USER "Installation starting in 5 minutes. Please log out."<Return>
     $  SET LOGINS/INTERACTIVE=0<Return>
     $  @SYS$UPDATE:VMSINSTAL TDA014 MUA0: OPTIONS N<Return>

                VAX/VMS Software Product Installation Procedure V5.3

               It is 05-JAN-1990 at 09:55.

               Enter a question mark (?) at any time for help.
         * Are you satisfied with the backup of your system disk [YES]? <Return>

               Please mount the first volume of the set on MUA0:.
               * Are you ready?  YES<Return>
               %MOUNT-I-MOUNTED, TDA014 mounted on _MUA0:

               The following products will be processed:
                  TDA V1.4

                Beginning installation of TDA V1.4 at 10:00

               %VMSINSTAL-I-RESTORE, Restoring product save set A ...

                                              Sample TEAMDATA Installation  B-1

 











                   Release Notes Options:

                1.  Display release notes
                2.  Print release notes
                3.  Both 1 and 2
                4.  None of the above

               * Select option [2]:  <Return>

               * Queue name [SYS$PRINT]: <Return>
               Job 810 (queue SYS$PRINT, entry 1295) started on SYS$PRINT

               * Do you want to continue the installation [NO]?  YES<Return>
               %VMSINSTAL-I-RELMOVED , The product's release notes have been
               successfully moved to SYS$HELP.

               ***************************************************************
               *                                                             *
               *                   TEAMDATA version: V1.4                    *
               *                                                             *
               *                   Installation Procedure                    *
               *                       on Node: MYNODE                       *
               *                 on 05-JAN-1990 10:02:24.71                  *
               *                                                             *
               *     Copyright (c) 1990 by Digital Equipment Corporation     *
               *                                                             *
               ***************************************************************

                       Product:      TEAMDATA
                       Producer:     DEC
                       Version:      1.4
                       Release Date: 26-APR-1990

          * Does this product have an authorization key registered and loaded?  
            YES<Return>

           *********************************************************************
           *                                                                   *
           *   Please wait while the system environment is checked out.        *
           *                                                                   *
           *********************************************************************

           *********************************************************************
           *                                                                   *
           *   TEAMDATA creates a directory to put product specific files in.  *
           *      The logical TEAM$LIBRARY will point to this directory.       *
           *      These files amount to about 4600 disk blocks.                *
           *      The default is recommended.                                  *
           *                                                                   *
           *********************************************************************

               B-2  Sample TEAMDATA Installation

 











     * Where should the TEAMDATA directory go [SYS$COMMON:[TEAMDATA]]:  <Return>

     * Do you want to purge files replaced by this installation [YES]?  <Return>
     * Do you want to run the IVP the installation [YES]?  <Return>

           *********************************************************************
           *                                                                   *
           *   SYSTEM MANAGER:                                                 *
           *                                                                   *
           *   Add to the system startup file: SYS$MANAGER:SYSTARTUP_V5.COM:   *
           *                                                                   *
           *            $ @SYS$STARTUP:TDA$STARTUP.COM                         *
           *                                                                   *
           *    (For clusters, add this to the startup for each node)          *
           *                                                                   *
           *********************************************************************

           *********************************************************************
           *                                                                   *
           *   You've answered ALL the questions for the installation.         *
           *                                                                   *
           *   The installation takes 30 to 45 more minutes to complete.       *
           *                                                                   *
           *********************************************************************

               %VMSINSTAL-I-RESTORE, Restoring product save set  B...
               %VMSINSTAL-I-RESTORE, Restoring product save set  C...
               %VMSINSTAL-I-RESTORE, Restoring product save set  D...
               %VMSINSTAL-I-RESTORE, Restoring product save set  E...

           *********************************************************************
           *                                                                   *
           *   Installing Sample Database...                                   *
           *                                                                   *
           *********************************************************************
           *                                                                   *
           *   Installing Default User Database...                             *
           *                                                                   *
           *********************************************************************
           *                                                                   *
           *   Installing Public Folder Database...                            *
           *                                                                   *
           *********************************************************************





                                              Sample TEAMDATA Installation  B-3

 











  %VMSINSTAL-I-SYSDIR, This product creates system disk directory
               VMI$ROOT:[SYSTEST.TDA$IVP].
  %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

               VAX TEAMDATA: Installing TEAMDATA images
               VAX TEAMDATA: Starting System Interconnect

               **** Executing IVP for: VAX TEAMDATA V1.4

                       **** Running Folder Test

                       **** Folder Test Succeeded

                       **** Running Table Test

                       **** Table Test Succeeded

                       **** Running Spreadsheet Test

                       **** Spreadsheet Test Succeeded

                       ********************************

                       VAX TEAMDATA V1.4

                       IVP COMPLETED SUCCESSFULLY

                       ********************************

               **** IVP completed for: VAX TEAMDATA V1.4

                Installation of TDA V1.4 completed at 10:50

                VMSINSTAL procedure done at 10:51

               $ SET LOGINS/INTERACTIVE=64
               $ REPLY/USER "Installation complete. System is ready for use."












               B-4  Sample TEAMDATA Installation

 




















               ___________________________________________________________


                                                                      Index



               A                               CDD (Cont.)

               Access                            and TEAMDATA, 1-5
                 granting remote, 3-5          Changing system parameters,
               Accessing IBM databases,           1-12
                  1-5                          Checking privileges, 1-7
               ALL-IN-1, 1-9                   Checking process quotas,
                 Installing TEAMDATA under        1-8
                    , 5-1  to 5-5              Checking system parameters,
               AUTHORIZE Utility, 1-9             1-10
               Authorizing quotas              Checking the distribution
                 user, 3-4                        kit, 1-2
               AUTOGEN                         CLISYMTBL
                 setting system parameters       SYSGEN parameter, 2-10
                    , 1-13                     Cluster
                                                 installing TEAMDATA, 1-6
               B                                 running TEAMDATA, 3-2

               BUGCHECK dump file, 4-1         Components supported
                                                 operating system, 1-3
               C                                 VMS, 1-3

                                               Conventions
               CDD                               keys, ix

                                                                    Index-1

 






          CSC                             G

            See Customer Support          GBLPAGES parameter
               Center                       checking and setting,
          Customer Support Center,            1-12
             4-4                            insufficient, 4-3

          D                               GBLSECTIONS parameter
                                            checking and setting,
          Databases                           1-12
            sample, 4-1                   Global pages, 1-6, 1-12
          DATATRIEVE                      Global sections, 1-6, 1-12
            and TEAMDATA, 1-5, 3-3        Granting remote access, 3-5
          DCL-W-SYMOVF error, 2-10        Granting user privileges,
          Directories                        3-4
            logical names, A-1            H
          Disk blocks
            displaying number of free     Hardware
               disk blocks, 1-10            required, 1-2
          Disk requirements, 1-9
          Distribution kit                I

            contents of, 1-2              IBM databases
          Dump file, 4-1                    accessing, 1-5

          E                               Improving performance, 1-13

          Editing SYSTARTUP_V5.COM,       Installation
             3-2                            kit,missing or damaged
                                              parts, 1-2
          F                                 preparing for, 1-1
                                          Installation Verification
          Files                              Procedure
            RDMMON.LOG, 4-2                 running after
            Run Unit Journal, 3-4             installation, 3-3
            TDABUGCHK.DMP, 4-1            Installer privileges, 1-7t
            transferred from kit, A-1     Installing TEAMDATA
          Free disk blocks                  under ALL-IN-1, 5-1
            displaying number of,
               1-10

          Index-2

 






          K                               Optional software, 1-4

          Key conventions, ix               CDD, 1-5
                                            DATATRIEVE, 1-5, 3-3
          L                                 RALLY, 1-5

                                            VIDA, 1-5
          Labels                            Xway, 1-5
            on distribution media,        P
               1-2
          License Management Facility     Page file quota, 1-9
             , 1-5, 2-5                   Paging and swapping files,
          LMF                                1-14
            See License Management        PAK
               Facility, 1-5                See Product Authorization
          Log files                           Key, 1-5
            RDMMON.LOG, 4-2               Parameters
          Logical names                     system, 1-10t
            files transferred from             checking, 1-10
               kit, A-1                   Performance considerations,
            TEAM$LIBRARY, 2-7                1-13

          M                                 memory management, 1-14

                                            paging and swapping files
          MAXDETACH quota, 1-9                , 1-14
          MAXJOBS quota, 1-9                system parameters, 1-15
          Media labels, 1-2               PGFLQUO, 1-9
          Memory management, 1-14         Preparing account, 1-6
            WSDEFAULT value, 1-14         Preparing for installation,
            WSEXTENT value, 1-14             1-1
            WSMAX value, 1-14             Prerequisite hardware, 1-2
            WSQUOTA value, 1-14           Prerequisite software, 1-3,

          N                                  1-4
                                          Privileges
          NETMBX privilege, 3-4             checking installing, 1-7

          O                                 granting to users, 3-4
                                            installer, 1-7t
          Operating system components     Problems
             supported, 1-3                 reporting, 4-4

                                                              Index-3

 






          Process quotas, 1-8t            Sample installation, B-1
            checking, 1-8                 SHOW DEVICE command
          Product Authorization Key,        displaying number of free
             1-5                              disk blocks, 1-10
          Q                               Shutdown procedure, 3-6
                                          Software
          Quotas                            optional, 1-4
            MAXDETACH, 1-9                     CDD, 1-5
            MAXJOBS, 1-9                       DATATRIEVE, 1-5, 3-3
            process                            RALLY, 1-5
               checking, 1-8                   VIDA, 1-5
            user, 3-4                          Xway, 1-5
          R                                 required, 1-3
                                               Rdb/VMS, 1-4
          RALLY                           Startup procedure
            and TEAMDATA, 1-5               editing SYSTARTUP_V5.COM,
          Rdb/VMS                             3-2
            and TEAMDATA, 1-4             Swapping file, 1-14
          RDMMON.LOG file, 4-2            Symbol definitions
          Reading BUGCHECK dump file,       overflow error, 2-10
             4-1                          SYSGEN parameters
          Release notes, 2-4                CLISYMTBL, 2-10
          Remote access                   SYSTARTUP_V5.COM
            granting, 3-5                   editing, 3-2
          Reporting problems, 4-4         System disk
          Required disk space, 1-9          backing up, 1-16
          Required hardware, 1-2          System parameters, 1-10t,
          Required software, 1-3             1-15
            Rdb/VMS, 1-4                    changing, 1-12
          Restoring the sample              checking, 1-10

             database, 4-1                T
          RUJ files, 3-4
          Run Unit Journal files, 3-4     TDABUGCHK.DMP
          S                                 bugcheck dump file, 4-1
                                          TDADEFDB.RDB, 4-1
          Sample database, 4-1            TDASAMPLE.RDB, 4-1



          Index-4

 






          TDASYSDBNEW.RDB, 4-1            WSMAX value, 1-14
          TEAM$LIBRARY logical name,      WSQUOTA value, 1-14
             2-7                          X
            moving, 3-1
          TEAMDATA                        Xway
            running, 3-3                    and TEAMDATA, 1-5
          TMPMBX privilege, 3-4

          U

          User quotas
            authorizing, 3-4

          V

          VAXcluster
            installing TEAMDATA, 1-6
            running TEAMDATA, 3-2
          VAX DATATRIEVE

            See DATATRIEVE
          VAX RALLY

            See RALLY
          VAX Rdb/VMS

            See Rdb/VMS
          VAX Xway

            See Xway
          VIDA
            and TEAMDATA, 1-5
          VMS components supported,
             1-3
          VMSINSTAL command procedure
             , 2-2  to 2-11
            preparing to run, 2-2

          W

          WSDEFAULT value, 1-14
          WSEXTENT value, 1-14

                                                              Index-5
